I am building a mapping app for car drivers in London, England, but I have run into some problems with Open Street Maps routing– namely, I have been routed through several modal filters at intersections (an exit of which prohibit cars without a certain neighborhood parking permit), or routed in directions only buses can go, or asked to turn right at intersections where right turns are explicitly prohibited.
Is there a setting i need to to configure, or is there another mapping application or plug-in I should be building on top of, which is able to give followable routes ?
Something like motor_vehicle=privatepsv=yes would be my first guess, but ask people from the Communities > United Kingdom what tags they normally use for this.
Access tags in the UK permitting PSVs are usually wrong, based on the flawed assumption that it’s shorthand for taxi=yes + bus=yes . This may be true in other places, but doesn’t work with the UK definition of a PSV.
You might see non-standard signs prohibiting all PSVs, which are usually based on the “vehicles prohibited” sign with the text “No public service vehicles” in place of a pictogram.
1 Like
Mammi71
(One feature, Six mappers and still More ways to map it)
5
Ok. OSMnx and networkX are absolutely not my specialist subject, but my guess is that they are not as sophisticated as a fully-fledged routing engine at parsing OSM’s tags which describe the access possibilities for any given way.
I’d suggest you start by trying to plot the same routes on the web interface on osm.org and see if it gets them “right”. osm.org provides an interface to the three most common routing engines (OSRM, Graphhopper, Valhalla) and all of these will parse OSM tags correctly.
If it’s right on osm.org, but wrong with your code, that suggests the map data is correct and it’s your code (i.e. OSMnx/networkX) which is lacking. On the other hand, if it’s wrong on osm.org, that suggests the map data is wrong.
Generally, for production use, most people will use a high-performance routing engine with proper tag parsing like the three mentioned above, rather than something like networkX which is written in a scripting language.
It looks like a section of the east end of Bryony Road already has a motor_vehicle=permit tag on it. Would it be sufficient to split the other affected roads in a similar way and use that tagging?
AFAIK we don’t have any tags for some sort of permit ref to record exactly which permits are permissible. It would be difficult to implement unless local governments had already agreed to a unified system for recording them. I don’t even recall such a thing in the description of the new digital TROs they’re hoping to introduce but I could be wrong there.[1]
Edit: a quick search of the Tour of the Data Model suggests that schemeIdentifier and permitIdentifierare both optional and seem to be free text so even if this does happen we might be in the same situation we are with PROW refs where it’s all a little vague. Obviously I haven’t just read that entire document in the last few minutes so I might have the wrong end of the stick. ↩︎
No, anyone with an account can make an edit and it goes live in the database immediately (although the services using OSM data usually only update periodically). If you would like someone to review your edit there’s generally a tickbox for that in the editing software, but this is just a flag for any other mappers who might be interested and not a guarantee it will get looked at.
In this case you may need to add nodes to the ways you would like to split to add the filter and then split them and add the tag only to the relevant bit. I can’t remember how much of a built in tutorial there is in the in browser iD editor these days but there are also resources like LearnOSM if you need a more detailed tutorial (or you can ask here if something doesn’t make sense).
