I added an entrance at Node: 13484582195 | OpenStreetMap
Does it have any effect on routing when simply selecting the building? (I’m aware that each of the 3 routers on OSM works a bit differently and takes time to update). Ideally routing would lead there and not anywhere else around the building.
There is no info on Tag:entrance=main
Historically it hasn’t been routing per se that’s the challenge, but geocoding. A router would generally just find the best route between two pairs of co-ordinates. It’s the role of the geocoder to turn your text input into co-ordinates.
But Nominatim (the best-known router) has recently added support for entrance nodes. So the task, I think, is for websites/apps which provide an interface to routing engines - and one of those sites is, of course, openstreetmap.org - to make use of this new feature. I’d be interested to hear of any such sites or apps which have done that.
Maybe I need to draw a footpath within the building.
If anyone is interested in implementing routing to entrances, please see this openstreetmap-website issue.
Interesting. Access for separate wheelchair entrances might need such tags.
I gave it a try with an internal area and connected this to the entrance at Way: 1471485439 | OpenStreetMap . Either it needs more tags or takes time to update to work.
The internal area didn’t seem to help, even for pedestrian routing (GraphHopper, OSRM, Valhalla)
Regarding mapping, I have always wondered whether there is a way to map beyond just adding an entrance node to an area.
I have found these two relation types. Does anyone have any experience with them? Does the new Nominatim feature support them?
Relation:provides_feature - OpenStreetMap Wiki & Relation:preferredEntry - OpenStreetMap Wiki
None of these routers support indoor routing via indoor=room or indoor=area, only via highway=footway/steps indoor=yes or highway=corridor, maybe highway=elevator as well. GraphHopper and Valhalla are tracking indoor navigation as a longstanding feature request. OSRM was too, until Stalebot got involved.
None of these routers supports routing through an area yet, so even if the area were tagged something like highway=pedestrian area=yes, the routers would route you around the walls rather than through the middle. Of the three, only OSRM is currently working on an implementation. That implementation is focused on feature types that OSRM already supports for pedestrian routing, namely, highway=* areas.
No, so far, Nominatim only indicates the location of an entrance=* or routing:entrance=* node along the perimeter of the area element associated with the search result. It’s primarily useful for buildings.
preferredEntry is extremely rare, apparently an experiment several years ago that never saw any traction. provides_feature is more common as of the last couple of years, but it appears to be nearly exclusive to Brussels, Nice, and Stockholm, for the purpose of associating an address point with the POIs that the address belongs to. (I guess the idea is to avoid tagging the same addr:housenumber=* on multiple features, which in my neck of the woods would be totally normal and preferred.) Only 1,271 provides_feature relations have an entrance member, more or less in the same cities.
site relations with entrance members are much more common at 3,346 occurrences. Here’s a proposal to index entrances based on site relations:
