Skip to main content

Hi,

I'm trying to create a shortest path from point A to B, yet FME is not outputting any path. I've looked at similar questions asked on here, and I've adapted my workbench accordinly, but still no luck.

I'm using an OpenStreetMap highway layer as input. I've explicitely set my snapping tolerance as relatively high in the shortespathfinder, just so that I could just get some output. But it didn't work either.

Printscreen of my workbench:

 

Weren't no features output from the "NoPath" port?

If all network lines don't belong to a single connected network, there could be no path between specified from-to. You can use the NetworkTopologyCalculator to check if the lines belong to a single network.


For some reason I've had much better results using a stand-alone Snapper before building the topology, rather than relying on the ShortestPathFinder tolerance.


Weren't no features output from the "NoPath" port?

If all network lines don't belong to a single connected network, there could be no path between specified from-to. You can use the NetworkTopologyCalculator to check if the lines belong to a single network.

All the features are output through the unused port. There's also one output though the nopath port, which is just the from-to line. And of course the from-to also outputs the line I created with the creator transformer

 

 


For some reason I've had much better results using a stand-alone Snapper before building the topology, rather than relying on the ShortestPathFinder tolerance.

Yes, this worked... Thank you !

 

 


Not helpful, but I wouldn't try routing with Open Street Map....

 

 


Not helpful, but I wouldn't try routing with Open Street Map....

 

 

Thanks.... why not? Because of the quality?

 

 


Thanks.... why not? Because of the quality?

 

 

Yes, its not designed for routing so you might get some odd results

 

 


For some reason I've had much better results using a stand-alone Snapper before building the topology, rather than relying on the ShortestPathFinder tolerance.

@david_r Snapping within the ShortestPathFinder is only for snapping "points of the From-To line to the closest end points of the Network lines". Snapping From-To points to segments isn't possible yet and the ShortestPathFinder needs a clean network for input.

 


@david_r Snapping within the ShortestPathFinder is only for snapping "points of the From-To line to the closest end points of the Network lines". Snapping From-To points to segments isn't possible yet and the ShortestPathFinder needs a clean network for input.

 

Thank you!

 

 

And how would this whole "shortest path finder" process with the same parameters (by lenght, by costs etc) be accomplished with raster data?

 

@takashi

 

@david_r

 

@owen

 

@DanAtSafe

 

 


@david_r Snapping within the ShortestPathFinder is only for snapping "points of the From-To line to the closest end points of the Network lines". Snapping From-To points to segments isn't possible yet and the ShortestPathFinder needs a clean network for input.

 

Thanks for clarifying, I should've had another coffee before before writing that answer 🙂
Thank you!

 

 

And how would this whole "shortest path finder" process with the same parameters (by lenght, by costs etc) be accomplished with raster data?

 

@takashi

 

@david_r

 

@owen

 

@DanAtSafe

 

 

@fmenco You'd have to convert the raster data to vector first - the ShortestPathFinder only accepts line features.

 


Reply