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

100%

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

✓ Published0🌍 Public

Last edited Mar 12, 2019

Created on Mar 12, 2019

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.

AI-generated description

Similar vizzes

Loading thumbnail…

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

This example demonstrates how to extract XML data stored in an Access database table and convert it into a well-formed XML document using FME. The workspace uses a Creator transformer to generate a feature, followed by an AttributeCreator to populate the `ReportDataXML` attribute with a static XML string. The key transformation involves cleaning the raw XML content—removing invalid characters, ensuring proper encoding declarations, and structuring it into a well-formed XML document. The workspace is configured with enhanced geometry handling and a straightforward linear flow, making it a minimal yet effective template for extracting and normalizing XML from database fields.

FFrieseWoudloper

62% match

Loading thumbnail…

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.

FFrieseWoudloper

51% match

Loading thumbnail…

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.

FFrieseWoudloper

51% match

Loading thumbnail…

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.

FFrieseWoudloper

49% match

Loading thumbnail…

FLICKR API Example

This example visualizes Flickr photo search results for the query "David Bowie" by querying the Flickr API’s `flickr.photos.search` method with a supplied API key and authentication token. The XQuery code constructs a REST endpoint URL to fetch raw XML responses, which are then rendered as a network graph of matching photos. It uses the standard `fn:doc` function to retrieve the data, while the visualization layer relies on D3’s `forceSimulation` for layout and `d3.geoPath` for any geographic mapping, though the specific rendering logic is not shown. The result is a dynamic, data-driven exploration of Flickr’s public photo metadata.

CCliffordAnderson

47% match

Loading thumbnail…

FOAM API Example - CSC search

This map visualization demonstrates searching and displaying FOAM beacon locations using the Mapbox GL JS API. It shows beacon data as points on a dark basemap, with a search menu that queries the FOAM API for specific beacon names and displays the first result. The code uses Axios for API requests and the latlon-geohash library for geographic calculations, while Mapbox GL JS renders the map with a GeoJSON source. The initial view covers a bounding box across North America, and the search functionality dynamically updates the map by removing and re-adding layers when a beacon is found.

WWill Carter

46% match

Loading thumbnail…

Adapted the script by Yonhah: https://github.com/yonghah/esri2sf/blob/master/R/esri2sf.R

This example demonstrates how to fetch GIS feature data from an ArcGIS REST server and convert it into simple features for spatial analysis in R. It shows a workflow that queries a specified layer, retrieves object IDs, and then pulls the corresponding attributes and geometries as GeoJSON. The code relies on the `httr` package for HTTP requests, `jsonlite` for parsing JSON responses, and `sf` for handling spatial data. It also includes a helper function to generate authentication tokens when the server requires login. The implementation uses the ArcGIS REST API's `query` endpoint to request data in batches of 500 IDs, ensuring efficient retrieval of large datasets.

FFrieseWoudloper

46% match

Loading thumbnail…

API request OData CBS

This example demonstrates the structure and querying of CBS (Statistics Netherlands) open data via its OData API, showing how different URL patterns access metadata, raw datasets, and filtered subsets. The visualization highlights the API’s flexibility by contrasting `$top`, `$skip`, `$filter`, and `$format` parameters across both untyped and typed data feeds. It uses the `$metadata` endpoint to reveal the dataset schema, while the queries return JSON-formatted rows for geographic units like neighborhoods. The rendering relies on standard browser fetch or XMLHttpRequest for these OData requests, with no external visualization libraries—the focus is purely on data retrieval patterns and response structures.

FFrieseWoudloper

46% match