Skip to main content
Released

Full GeoJSON support in GeometryReplacer

Related products:Transformers
jkr_wrk
mark2atsafe
  • jkr_wrk
    jkr_wrk
  • mark2atsafe
    mark2atsafe

nic_ran
Contributor

The GeometryReplacer accepts GeoJSON as an input format but will fail if _full _ compliant GeoJSON is supplied. Instead, the GeometryReplacer expects just the geometry component of the GeoJSON, which means this needs to be extracted from the JSON somehow prior to being passed into the GeometryReplacer.

It would be great if the GeometryReplacer could be enhanced to accept any valid GeoJSON.

If the GeoJSON is a multi-feature object, then the GeometryReplacer could either create aggregate geometry, or provide an option to create multiple FME features.


There are several questions in the FME Community about this. Here's an example:

https://community.safe.com/s/question/0D54Q00008IYY6fSAH/error-converting-geojson-to-geometry-using-geometryreplacer-invalidparametergeometrysource


3 replies

redgeographics
Celebrity
Forum|alt.badge.img+50

That's interesting, especially considering that the GML option of the GeometryReplacer is actually capable of processing just the geometry part of a feature.


LizAtSafe
Safer
Forum|alt.badge.img+15
  • Safer
  • October 25, 2024
OpenIn Development

LizAtSafe
Safer
Forum|alt.badge.img+15
  • Safer
  • November 5, 2024
In DevelopmentReleased

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings