Example workspace for https://knowledge.safe.com/questions/88158/extract-xml-data-from-an-access-database-table.html

Prototype for https://knowledge.safe.com/questions/88427/using-xfmap-to-create-multiple-values-for-one-attr.html

This prototype demonstrates how to use the XFMAP (XML Feature Mapping) to generate multiple attribute values from a single XML source within an FME workspace. It reads an XML file, parses its structure, and produces features with repeated attributes—enabling the transformation of nested XML elements into flat, multi-valued table rows. The workspace visually maps out the data flow with reader, transformer, and writer nodes, showing how list attributes and feature merging can be orchestrated to flatten hierarchical data. The visualization highlights the workflow logic, not the data itself, serving as a template for FME users seeking to handle similar XML-to-attribute transformations.

66% match

Prototype for https://knowledge.safe.com/questions/88427/using-xfmap-to-create-multiple-values-for-one-attr.html

This prototype demonstrates how to use FME’s XML reader with an XFMAP (XML Mapping File) to flatten nested XML data into multiple attributes on a single feature. The workspace reads an XML dataset, exposes a set of FME-specific and XML-derived attributes, and includes parameters for configuring feature types, dataset paths, and XML parsing options. The visualization shows how the XML structure is transformed through the mapping process, highlighting the attribute definitions and the generated feature types.

63% match

FME workspace for https://knowledge.safe.com/questions/88318/api-watch.html

This example uses an FME workspace to demonstrate how to monitor an ArcGIS Open Data REST API for changes. A Creator transformer initiates the workflow, and an HTTPCaller sends a request to the API endpoint with query parameters for the catalog and page size. The workspace is designed to retrieve data from the specified ArcGIS portal, showcasing a pattern for API polling or scheduled data extraction within FME.

62% match

Prototype for https://knowledge.safe.com/questions/88427/using-xfmap-to-create-multiple-values-for-one-attr.html

This prototype demonstrates how to use the XFMAP (XML Feature Mapping) technique in FME to expand a single XML attribute into multiple output attribute values. The workspace reads an XML source dataset and applies an XML mapping strategy to split or repeat values based on structure, showing how one input element can generate several output attributes. The visualization highlights the flow from the XML reader through the mapping logic to the resulting feature attributes, making it clear how repeated or complex XML content is transformed into multiple discrete attributes.

61% match

Power Query Table to XML

This example demonstrates a Power Query M function that converts a table into a nested XML structure, using a recursive custom function named `tab2xmlREC` to handle tables, records, and scalar values. The initial sample table, created with `#table(null,{{1,2},{3,4}})` and typed via `Value.ReplaceType`, is transformed into a string of XML elements. The implementation relies on `Table.ToRecords`, `List.Accumulate`, and `Record.FieldNames` to iterate over rows and fields, while `Text.Format` builds the XML tags. The output shows a flat representation for simple values, and the recursive call handles nested tables or records, producing a hierarchical XML string.

HHugoberry

fn:xml-to-json example

This example demonstrates the transformation of a nested XML document into JSON using the XQuery 3.1 function `fn:xml-to-json`. The XML input encodes workshop information, including leaders and institutions, within a structured `<map>` and `<array>` hierarchy using the XPath Functions namespace. The function converts this XML representation directly into its JSON equivalent, preserving the nested array and map structure. The code relies on the standard XQuery 3.1 function library, with the source document defined inline and the transformed JSON output returned as the query result.

CCliffordAnderson

Gist 47d998760fa7271ac3157ce7d9555612

This example demonstrates how to query and load data from external sources using Power Query's OleDb.Query function, specifically connecting to a local CSV file and an XML catalog. The code shows two approaches: one using Microsoft's ACE OLEDB provider to read a delimited text file, and another using the MSDAOSP provider with MSXML2.DSOControl to access XML data. The visualization highlights the raw query definitions rather than rendering graphical output, focusing on the data-acquisition layer. Both queries reference file paths on the local system, with the CSV query specifying the file directory and the XML query pointing to a catalog file.

HHugoberry

PowerQuery an alternative to opening XML files

This example demonstrates how PowerQuery can serve as an alternative to manually opening and parsing XML files. It shows a direct query that uses the `OleDb.Query` function with the `MSDAOSP` provider and the `MSXML2.DSOControl` data source to access an XML catalog. The code specifies a file path, `c:\code\catalog.xml`, and executes the query to load its contents. This approach highlights a practical way to integrate XML data into data-analysis workflows without a separate parser. The visualization makes the data-access method visible, emphasizing the tool's role in bridging XML files and PowerQuery’s querying capabilities.

HHugoberry