Which statement is true about geometry parameter encoding formats in FME?

Which statement is true about geometry parameter encoding formats in FME?

• A. GeoJSON, OGC Well Known Text, GML, Esri JSON are all supported
• B. Only GeoJSON is supported
• C. None are supported
• D. All geometry parameters must use WKT

Answer: (A)

FME allows geometry parameters to be supplied in multiple textual encodings, so you can work with the format that matches your data source or target system. GeoJSON, OGC Well Known Text, GML, and Esri JSON are all supported as geometry parameter encodings. This flexibility means you can feed a polygon or other geometry into a workflow using GeoJSON for web services, WKT for a compact human-readable form, GML for compatibility with certain standards, or Esri JSON for Esri-based workflows. In practice, you can choose the encoding that fits your data source and, if needed, convert between formats within the workspace. The important point is that FME supports these common geometry encodings for parameters.

FME allows geometry parameters to be supplied in multiple textual encodings, so you can work with the format that matches your data source or target system. GeoJSON, OGC Well Known Text, GML, and Esri JSON are all supported as geometry parameter encodings. This flexibility means you can feed a polygon or other geometry into a workflow using GeoJSON for web services, WKT for a compact human-readable form, GML for compatibility with certain standards, or Esri JSON for Esri-based workflows. In practice, you can choose the encoding that fits your data source and, if needed, convert between formats within the workspace. The important point is that FME supports these common geometry encodings for parameters.