I’ve mapped a number of shopping centers that look like this with a covered walkway along the front of the building:
I’ve been mapping these walkways within the building footprint and tagging them as covered=yes[1]. Then I place POI nodes for each shop also within the building footprint and that is usually detailed enough for me. I’ve been wondering though: If I were to place entrance nodes for each shop, where should they go? The wiki says an entrance should be placed on a building’s outline, but in this sort of building the entrances are set back underneath an overhang behind a walkway which, despite being covered, is outdoors. If the entrances are placed on the building outline it would imply that the walkway is indoors. How do we handle this?
I can imagine a similar situation where an entrance inside a tunnel=building_passage might also exist somewhere. Are these potentially exceptions where an entrance within a building area rather than along its outline can be seen as valid? Other ideas?
While I agree with Entrances covered by parts of a building - #3 by Fizzie-DWG the tension between mapping the cadastral building footprint and roof outline remains an unsolved problem (and S3DB only partially solves it as it doesn’t map functional building parts, but more lego bricks that create the outer hull of a building).
It’s a constant issue in the Swiss community that we haven’t resolved.
This is also a quite common situation around here, if it is a single building like in this example I mostly use “floating” entrances at their actual position, but not part of the outline, for lazyness, but I agree that the best solution is mapping different parts (this is not limited to overhanging roofs, but also quite common with arcades, shopping malls, buildings on pylons etc.).
examples of even prominent buildings mapped with floating entrances (the housenumbers are implicit entrances):
In this example, the roof covering the sidewalk is not integral to the main building structure and thus seems more reasonable to not include as part of the main building footprint and potentially mapped as a separate building=roof. It’s not really a separate building but this bending of the truth feels less bad with a small roof extension than it would in a multi-story building like this:
Here the covered sidewalk is under an integral part of the building structure. Shrinking the main building footprint and mapping a thin separate building just over the sidewalk would feel quite wrong here. Thank you for this good example, @dieterdreist.
It is, but this situation seems common enough that requiring 3D building mapping before entrances can be properly placed would be unfortunate. I’m hoping there can be a reasonable guideline for how mappers should place entrance nodes even if they aren’t ready to get into 3D buildings.
Thank you for these examples. I’m glad to see that neither the JOSM or iD validators complain that the entrance nodes are not on a building outline. I did a little testing and found that if the entrances nodes are completely free floating both validators show a warning that an entrance node should be connected to a way. So mapping a series of entrances along a walkway like this is going to get flagged:
Does it seem reasonable that an entrance node within a building outline should always be connected to a highway=* (likely footway)? If so, that can be documented on the wiki. Or should validators and QA tools be ok with fully disconnected entrance nodes inside building areas?
Within OSM-speak, colonnades use columns, where as arcades use arches: Key:covered - OpenStreetMap Wiki - usage and definitions in the real world may vary.
If there is just a roof attached to to a building on one side, I would just tag the roof as building=roof and the path as covered=yes.
I think an important test would be what is above the colonnade, just a canopy or rooms in the building.
actually, while the term colonnade comes from column, it does not imply that arcades cannot have columns as well.
colonnades have beams while arcades have arcades, these are the structures carrying the load from the ceiling (while the columns carry these loads to the ground).
Ideally, entrance=* nodes are always connected to a highway=* (usually highway=footway) way that connects to the wider routing network, whether the entrance is a member of a building=*/building:part=* area (ideal) or would otherwise be “floating” (acceptable, with caveat that the highway=* segments inside the building=* area are tagged covered=yes).
In reality, in most parts of the world (afaik) we are far from that ideal, so validators should be OK with entrances that are connected to something: a building outline or a way.
_18.jpg)
