Which encoding formats does FME support for the geometry parameter?

• A. OGC Well Known Text
• B. GeoJSON
• C. GML
• D. Esri JSON

Answer: (B)

Understanding how geometry is provided to a transformer parameter in FME hinges on the encoding format used to describe that geometry. For the geometry parameter, GeoJSON is the supported encoding because the parameter expects a JSON-encoded geometry string. This fits nicely with FME’s handling of JSON data and lets you describe any geometry type by its type (Point, LineString, Polygon, etc.) and coordinates, for example: {"type":"Point","coordinates":[30.0,10.0]}. It scales to more complex shapes like MultiPolygons as well, and it stays readable within configuration text.

Other formats exist in the ecosystem—WKT is a traditional text representation, GML is XML-based, and Esri JSON is a variant used in Esri ecosystems—but they aren’t the encoding used by the geometry parameter itself. They may be encountered in data sources or other parts of a workflow, but GeoJSON is the format that the parameter supports for providing geometry directly.