Good afternoon,
We work with a routing service which makes use of the map for waste trucks. And we have found an issue where it would not drive over “Way: Coolsingel (1120483925)”. It seems like something is stopping it from driving over there. Does anyone know if there are any weird abnormalities which might cause systems to not be able to see this as an drivable road?
There’s a nearby service road that looks like it might need reversing as the one-way doesn’t match the adjacent sections.
I don’t see anything else obviously wrong though. OSRM will let me drive a car along there, but not sure if the waste trucks use a different profile.
The oneway in the building passage (does not need layer-1), is in the wrong direction as noted so it’s surprising any vehicle can be routed through. Given it is a building passage (does not need layer=-1), it might not meet the (assumed) vehicle height limitation of that passage either. I’d not be surprised it will not be high enough to even let a motorhome through. Needs on-sight verification or recent ground imagery. (We have a lot of small/low waste trucks here to deal with these situations of height and width restrictions)
There is another part of that same road which goes the same way as Dezza’s example making the score 2 to 3 for the segments of that road that are marked as oneway=yes. I would not be able to say which ones are correct.
That said the road above is only indirectly connected to the way DKloppenburg-WV is asking about. So I don’t know if that has any relevance. As DKloppenburg-WV is not saying where the route is supposed to go, continue on the Coolsingel or going into Doelwater, I think we have insufficient information.
A test with GraphHopper in truck mode going from Coolsingel to Doelwater fails to route. While car routes just fine.
Valhalla demo in truck mode has no problem routing.
Edit: Funny thing - GraphHopper can’t route straight on staying on the Coolsingel either. Neither for truck nor car.
Some northbound parts of Coolsingel were tagged as under construction until 7 days ago (one southbound part still is but that shouldn’t matter here). GraphHopper is using data from a couple of days before that. So maybe routing in that area is just unreliable until the data is updated.
3 Likes
Hi,
For context it let’s you route to a stop just before that section of road (does a U-Turn) to the end destination.
The moment you put the stop on that section, it will no longer be able to route anymore.
For example:
Doesn’t work:
Start: 51.92197873310046,4.4791915490177745
Stop: 51.922941024253156,4.478741884231568
End: 51.923668909259824,4.477909652379536
Works:
Start: 51.92197873310046,4.4791915490177745
Stop: 51.92292780011242,4.478741885065341
End: 51.923668909259824,4.477909652379536
Hi,
I think that could be it as our system only updates this ones a month, usually around the 5th and the issues have appeared since a couple of weeks. As the roads there are only straight I think it won’t be able to route past the point where it turns to the way I mentioned.
1 Like