[Tagging] Straw pole Temperature=objective default unit?
erringtona at gmail.com
Thu Apr 9 06:49:42 UTC 2015
There is no regional default if the units are not specified.
In the case of maxspeed it is always km/h if the units are not specified.
If mph is intended then "mph" must be specified.
So, for your example of temperature, if the units are not specified then
the value should be interpreted as, say, Celsius. If a mapper intends the
units to be Fahrenheit then they must include a unit identifier *regardless
of the physical location of the tag*.
On 9 April 2015 at 15:42, Warin <61sundowner at gmail.com> wrote:
> Sorry .. I have not made that clear ..
> The default speed limit for motorways on OSM in, say, Australia would be
> taking regionally, while that for USA would be different and taken for that
> See http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing/Maxspeed ?
> On 9/04/2015 4:16 PM, Lukas Sommer wrote:
>> b) values would interpreted by region. Most of the world would be
>>> Celsius, USA would be Fahrenheit. (Similar to defaults for speed on roads.)
>> Please note that speed limits are _not_ interpreted by regions.
>> http://wiki.openstreetmap.org/wiki/Key:maxspeed states that the unit
>> has to be added explicitly when it’s not km/h – independent of the
>> region where you are mapping.
>> Region-dependent interpretation of units is IMHO a quite bad idea.
>> 2015-04-09 5:41 GMT, Bryce Nesbitt <bryce2 at obviously.com>:
>>> How it's entered into the database, and how it's displayed, are two
>>> separate things. Humans are messy. Unless the API starts validating
>>> entries, entries will vary in format, even if we officially say that "46
>>> is the official format. But software can parse and normalize numbers.
>>> That said: temperature=___ is a problematic tag regardless of the
>>> formatting of the data.
> Tagging mailing list
> Tagging at openstreetmap.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Tagging