You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes it happens, that the bridge scenario is not working properly and the "scenario" isochrone basically looks like the "standard" one. I think I now understood why: the network that the circle tool shows seems to be not in line with the routing network. At Wittelsbacherstraße for example.
The text was updated successfully, but these errors were encountered:
First, the network on OSM is, from my point of view, wrongly classified. The paths are labeled as "use_sidepath", but no separate sidepaths are drawn. This is causing connectivity problems.
We were fetching the whole network, including the parts that are labeled e.g. foot=use_sidepath or bicycle=use_sidepath.
Though we are excluding these classes for the routing.
I am now filtering by the foot categories to exclude. Though this is not the perfect solution as we are not handling the ones excluded for bikes. The best would be styling the features to show whether they are usable by foot and bike. And show features that are not suitable for one or the other. Though this would require some more changes. So I have patched this temporary fix.
EPajares
changed the title
routing network and fetched network with circle tool not in line?
Style scenario network features to show if they are usable by foot and bicycle
Aug 13, 2022
Sometimes it happens, that the bridge scenario is not working properly and the "scenario" isochrone basically looks like the "standard" one. I think I now understood why: the network that the circle tool shows seems to be not in line with the routing network. At Wittelsbacherstraße for example.
The text was updated successfully, but these errors were encountered: