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

Add direction field to benches #342

Merged
merged 1 commit into from
Jan 11, 2022
Merged

Add direction field to benches #342

merged 1 commit into from
Jan 11, 2022

Conversation

fdr
Copy link
Contributor

@fdr fdr commented Jan 10, 2022

I've noticed a number of benches with directions already in OSM, but without this set, it's something of a hassle to do while using GoMap.

Copy link
Member

@tyrasd tyrasd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm wondering if this one would be better included as an optional field (in "moreFields")? Currently, about 1.65% of benches have the direction tag specified (for comparison, the other fields backrest, seats, material all all well above 10%).

@tordans
Copy link
Collaborator

tordans commented Jan 10, 2022

+1 fore moreFields. AFAIK GoMap does not distinguish between fields and moreFields (just lists them all in one list), so this change would not affect the goal of getting the tag in the default-list of GoMap.

@fdr
Copy link
Contributor Author

fdr commented Jan 10, 2022

Maybe, is it more customary to have "direction" in fields vs moreFields? This is how I determined where to put it, by looking at a couple of other things that had direction defined as a field. I did not aggregate them, just skimmed a few examples.

@tyrasd
Copy link
Member

tyrasd commented Jan 10, 2022

There are no hard rules here. Usually, "fields" are only used for the essential properties of map features. This is because mappers (especially beginners) sometimes feel urged to fill out all fields that are displayed. Now, if the direction of a bench should count as essential or not is of course quite a subjective matter. From my personal experience (and going by the numbers mentioned above), the direction is just not very often mapped for benches, that's why I suggested "moreFields".

PS: Looking through the other presets, I can see that there are quite a few more presets where the "direction" could be made optional by using the same argument.

I've noticed a number of benches with directions already in OSM, but
without this set, it's something of a hassle to do while using GoMap.
@fdr
Copy link
Contributor Author

fdr commented Jan 10, 2022

Alright, well, done that way, as you suggest.

@tyrasd tyrasd merged commit 848b283 into openstreetmap:main Jan 11, 2022
@tyrasd
Copy link
Member

tyrasd commented Jan 11, 2022

thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants