-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Level field for features likely to be within buildings #2218
Comments
|
Another likely source of confusion is that, according to the wiki, |
|
It seems that lot of users confuse elevation with level or height(e.g. http://overpass-turbo.eu/s/9BE). Since it is used quite rarely, I would remove elevation as optional tag. |
|
@pavlo-dudka That does seem odd that a user would enter building levels in the |
|
@bhousel Some ukrainian people filled ele-tag with building height(height-tag), not with building levels. You are right, that was probably done because of incorrect translation of elevation to ukrainian. Incorrect understanding of elevation also occured in USA. It was confused with level(shop level above the ground floor). See initial post of @1ec5. |
|
The user who incorrectly put the level in In the U.S. at least, the floor can be considered an informal part of the address, so that would be a good place for a |
|
I added this as a 'universal' field, so mappers can add this to any feature that happens to be indoors. |
Below the tag presets, there’s a button to set the selected feature’s elevation in the
eletag. Because new users tend to map POIs like shops, they are likely to think this field indicates what floor the POI is on. For example, changeset 22192377 set the elevation of a shop to “1” (1 m) in a city that sits at an elevation of 482 feet.There should be a separate button for setting the
leveltag for POIs likely to be inside buildings. It might be too confusing to have it replace the elevation button, though.The text was updated successfully, but these errors were encountered: