What version FME do you use? When I read it as text and use a GeometryReplacer in 2024.2 it just works?

Hi mattebridges,

I also have a example for you :) 

Similar to what Niels is doing he was just a minute quicker…. 

Edit: apperantly Niels changed his awnser… but I still have a working example for you  haha

Thanks so much ​@nielsgerrits and ​@jobvdnoort for your suggestions.

We’re on 2023.1 - so nothing ancient.

I’ll have a go with both suggestions now - really appreciate your help here :-)

Thanks again to @nielsgerrits and ​@jobvdnoort,

I was able to get this to work using serial JSONFragmenters. I’m not sure I understand why the second Fragmenter produces geometry but hey I’ll take it!

​​​​​​​Best wishes.

Hi ​@mattebridges ,

We’re on 2023.1 - so nothing ancient.

Originally GeometryReplacer (Geometry Encoding: GeoJSON) only supports replacing a “geometry” object with a geometry, not support replacing full GeoJSON document.

However, GeometryReplacer in FME 2024.2 or heigher supports replacing full GeoJSON document. You can find when the enhancement has been introduced in the Change Log, linked from the FME Downloads page.

Hi ​@mattebridges ,

We’re on 2023.1 - so nothing ancient.

Originally GeometryReplacer (Geometry Encoding: GeoJSON) only supports replacing a “geometry” object with a geometry, not support replacing full GeoJSON document.

However, GeometryReplacer in FME 2024.2 or heigher supports replacing full GeoJSON document. You can find when the enhancement has been introduced in the Change Log, linked from the FME Downloads page.

 

Awesome.

Hello ​@takashi - thank you so much for taking the trouble to explain this.

I’m relieved to know there was a reason why I couldn’t get the GeometryReplacer approach to work.

Best wishes!