Skip to content
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

Closed
1ec5 opened this issue May 11, 2014 · 6 comments
Closed

Level field for features likely to be within buildings #2218

1ec5 opened this issue May 11, 2014 · 6 comments
Labels
field An issue with a field in the user interface

Comments

@1ec5
Copy link
Collaborator

1ec5 commented May 11, 2014

Below the tag presets, there’s a button to set the selected feature’s elevation in the ele tag. 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 level tag for POIs likely to be inside buildings. It might be too confusing to have it replace the elevation button, though.

@1ec5 1ec5 changed the title Level preset for features likely to be within a building Level preset for features likely to be within buildings May 11, 2014
@1ec5
Copy link
Collaborator Author

1ec5 commented May 11, 2014

Another likely source of confusion is that, according to the wiki, level=1 corresponds to the floor above the ground floor, per British usage.

@bhousel bhousel changed the title Level preset for features likely to be within buildings Level field for features likely to be within buildings Oct 24, 2014
@bhousel bhousel added the field An issue with a field in the user interface label Oct 24, 2014
@pavlo-dudka
Copy link

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.

@bhousel
Copy link
Member

bhousel commented May 28, 2015

@pavlo-dudka That does seem odd that a user would enter building levels in the elevation field, especially when we provide a visible building:levels field for buildings, and the elevation field is hidden. Can you (or somebody who knows) check on the translations for these fields in this area (Ukraine?)

@pavlo-dudka
Copy link

@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.
http://www.openstreetmap.org/node/2842085937/history

@1ec5
Copy link
Collaborator Author

1ec5 commented May 28, 2015

The user who incorrectly put the level in ele on that building was likely using iD in English. I think they probably were aware that the building:levels tag was for the total number of floors. Being a new mapper who was mainly there to add Bitcoin tags, they wouldn't've known about the ability to specify custom tags.

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 level tag. But we'd have to account for regional differences about how to number the ground floor.

@bhousel bhousel closed this as completed in 58cb66f Jul 1, 2015
@bhousel
Copy link
Member

bhousel commented Jul 1, 2015

I added this as a 'universal' field, so mappers can add this to any feature that happens to be indoors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
field An issue with a field in the user interface
Projects
None yet
Development

No branches or pull requests

3 participants