-
Notifications
You must be signed in to change notification settings - Fork 16
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 measurement field type #15
Comments
As of openstreetmap/iD#8769, Here are some existing fields that commonly require the unit to be explicitly indicated:
Here are some existing fields that have an implied metric unit, which presents a usability challenge to users in the United States and to some extent the United Kingdom. A dedicated
|
Possible values to allow in
Looking at the CLDR unit preference data, I wonder if it makes more sense for iD to store the regional unit preferences directly instead of getting them from country-coder. It seems like a JSON port of the LDML unit preference format would have much less overhead. Footnotes
|
For some tags (e.g. |
Some fields such as Max Stay ( |
Copying openstreetmap/id-tagging-schema#1234 (comment) here so we don't forget
|
iD’s implementations of the
roadheight
androadspeed
field types share a lot in common. Meanwhile, other fields would benefit from unit dropdowns too but would need a different set of units, for example the Max Weight field: openstreetmap/iD#6707. This category has more examples of measurement-typed keys. We should replace theroadheight
androadspeed
field types with a more generalmeasurement
field type, along with adimension
property that can be set to one of several values likearea
andduration
.For dimension naming ideas, this CLDR file lists industry-recognized measure units, each of which starts with a category subtag.
The text was updated successfully, but these errors were encountered: