Hi Matti,
no AFAIK there is no standard way to share unit and value infos. Using
an additional field sounds good to me. Other PGIS communities as
OpenStreetMap have similar problems with unit-metadata and use just one
field (e.g. height = 60m).
Other approaches are more complex, as creating an catalog of dimensions
(heigths, widths, deephs, ...) for typisation, similar how XForms deals
with it:
https://www.w3.org/community/xformsusers/wiki/XForms_2.0#Constraining_Values
regards,
Matthias
P.S: Think also about the references e.g. reference systems, water
gauges, ...
>>> "Matti Lindholm" <<email obscured>> 26.04.2017 09:53
>>>
Hi,
in Finland (Finnish Environment Institute) we are building an Open311
api for collecting citizen observations on environmental issues, ie.
water temperature, algal blooming and ice thickness. We will be using
attributes of datatype number for getting numeral values (like water
temperature).
So, the question is: is there an established way of handling units? It
would be convinient, if the end-user application could somehow get the
required unit together with the attribute definition. The application
could then let the user input data in his or her preferred unit, and do
the necessary transformation before sending the attribute. If the
end-user application uses sliders for input, it would also need a
minimun, maximum and a step value.
We are thinking of using the datatype-description field for delivering
these to the end-user application. Would this be ok? Maybe an escaped
json: '{ "unit": "cm", "minValue": 0, "maxValue": 100, "step": 1 }'. Any
thoughts on this?
Best,
Matti Lindholm
ββ
View topic http://lists.open311.org/r/topic/4i73wN5ZxAU02Dvf17IA7c
Leave group mailto:discuss@lists.open311.org?subject=Unsubscribe
Start groups https://OnlineGroups.net
no AFAIK there is no standard way to share unit and value infos. Using
an additional field sounds good to me. Other PGIS communities as
OpenStreetMap have similar problems with unit-metadata and use just one
field (e.g. height = 60m).
Other approaches are more complex, as creating an catalog of dimensions
(heigths, widths, deephs, ...) for typisation, similar how XForms deals
with it:
https://www.w3.org/community/xformsusers/wiki/XForms_2.0#Constraining_Values
regards,
Matthias
P.S: Think also about the references e.g. reference systems, water
gauges, ...
>>> "Matti Lindholm" <<email obscured>> 26.04.2017 09:53
>>>
Hi,
in Finland (Finnish Environment Institute) we are building an Open311
api for collecting citizen observations on environmental issues, ie.
water temperature, algal blooming and ice thickness. We will be using
attributes of datatype number for getting numeral values (like water
temperature).
So, the question is: is there an established way of handling units? It
would be convinient, if the end-user application could somehow get the
required unit together with the attribute definition. The application
could then let the user input data in his or her preferred unit, and do
the necessary transformation before sending the attribute. If the
end-user application uses sliders for input, it would also need a
minimun, maximum and a step value.
We are thinking of using the datatype-description field for delivering
these to the end-user application. Would this be ok? Maybe an escaped
json: '{ "unit": "cm", "minValue": 0, "maxValue": 100, "step": 1 }'. Any
thoughts on this?
Best,
Matti Lindholm
ββ
View topic http://lists.open311.org/r/topic/4i73wN5ZxAU02Dvf17IA7c
Leave group mailto:discuss@lists.open311.org?subject=Unsubscribe
Start groups https://OnlineGroups.net