osrm-backend icon indicating copy to clipboard operation
osrm-backend copied to clipboard

Osmosis-merged ways not routable?

Open alexanderzatko opened this issue 2 years ago • 2 comments

My workflow requires appending new ways to existing .pbf. I am using Osmosis to combine .osm file with .pbf file to produce a new .pbf file. After appending and starting OSRM, using the tile service, I see the new ways were added to the routing graph, but fail to find a route over the newly-added ways when querying OSRM directly, or through the osrm frontend.

here is a piece of my .osm file:

...
<node timestamp="2023-10-23T09:26:18+02:00" version="1" id="901698046036" action="modify" lat="48.773767246464" lon="19.020828542855" />
<node timestamp="2023-10-23T09:26:18+02:00" version="1" id="901698046037" action="modify" lat="48.773833502256" lon="19.021076080397" />
<way timestamp="2023-10-23T09:26:18+02:00" version="1" id="901698055978" action="modify">
<nd ref="901698045978" />
<nd ref="901698045979" />
<nd ref="901698045980" />
<nd ref="901698045981" />
<nd ref="901698045982" />
<nd ref="901698045983" />
<tag k="highway" v="track" />
</way>
...

my .lua profile allows routing on highway=track.

Any ideas what could I try to troubleshoot the issue?

alexanderzatko avatar Oct 23 '23 08:10 alexanderzatko

You’ll need to make sure that the new ways are also connected to the rest of the network. Meaning, connecting ways need to have the same node ID referenced.

nilsnolde avatar Oct 23 '23 11:10 nilsnolde

It did cross my mind, but I also thought the appended ways should be routable independently of the rest, which is not the case. Thank you for the suggestion anyways, I will try that.

alexanderzatko avatar Oct 24 '23 03:10 alexanderzatko