Skip to main content
  • EN

Hello,

There have been some previous posts about converting OSM data in FME, but I’m hoping to breath some new life into the conversation. I have an Overpass Turbo query here meant to query ski area boundaries, lifts, and runs within Colorado. The query works just fine in Overpass Turbo, and I’m able to read the raw XML data into FME with the HTTP Caller no problem. The issue I’m running into is visualizing the data beyond that. I’m aware of the example workflow that is similar to my process, but I don’t understand how the XSLT Processor and XML Fragmenter transformers work. If I use those transformers in my workflow, all the coordinate information seems to disappear when the data is fragmented.

Does anyone know how to properly display the XML data in FME? I might need a geometry filter to split out points, lines, and polygons, but I don’t think that’s what is holding me back currently. Any help would be greatly appreciated!

Have not updated you process, but you should be able to see how this fits into your process. What you want to do is save the XML returned by Overpass and use an OSM Reader to bring the features in.

 

In this case, I am using a temppathnamecreator to create a temporary file that the xml is saved to. Then reading that in by the featurereader. If you are only after specific attributes you can just expose them after.

Cheers,

Todd

Reply


Community Stats

30,159
Posts
114,480
Replies
37,806
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.