-
Notifications
You must be signed in to change notification settings - Fork 160
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
parking:orientation
field is showing additional undocumented rare values
#553
Labels
bug
Something isn't working
Comments
Yeah, it looks like these are fetched from Taginfo: |
jdhoek
added a commit
to jdhoek/id-tagging-schema
that referenced
this issue
Aug 1, 2022
The `parking:orientation` tag has three common and documented values. Currently no other values are in common use. With `autoSuggestions` turned on, two rare values (`orthogonal`, 80 uses, ostensibly a synonym of `perpendicular` and `marking` with only 16 uses) are included in the combo-box, making these seem like common and valid options. Fixes openstreetmap#553.
@arch0345 Interesting. Weird how that is pulling in tag values used only 80 and 16 times. That's bound to cause mappers to choose bad values. |
tyrasd
pushed a commit
that referenced
this issue
Aug 1, 2022
The `parking:orientation` tag has three common and documented values. Currently no other values are in common use. With `autoSuggestions` turned on, two rare values (`orthogonal`, 80 uses, ostensibly a synonym of `perpendicular` and `marking` with only 16 uses) are included in the combo-box, making these seem like common and valid options. Fixes #553.
tyrasd
added a commit
that referenced
this issue
Aug 1, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've noticed that ID is suggesting two additional undocumented and nearly unused values for
parking:orientation
:The value
orthogonal
(85 uses) seems like an undocumented alternative forperpendicular
andmarking
is used just 16 times (no idea what that means).Why are these showing up in the list? Is this automated based on TagInfo data?
Is it possible to leave them out?
The text was updated successfully, but these errors were encountered: