[Tagging] Let's get (quite) rid of units and their multiples in OSM values
fl.infosreseaux at gmail.com
Fri Jul 27 20:33:10 UTC 2018
Given problem is how can we query maxspeed like :
It's not possible while units are stored with values.
Then i agree that human display is a matter of tools, not database
Le ven. 27 juil. 2018 à 22:21, Tobias Knerr <osm at tobias-knerr.de> a écrit :
> On 26.07.2018 21:26, François Lacombe wrote:
> > Then store voltage=400000 is far way better but harder to be read by
> > humans also.
> I currently prefer explicit units in the database because they document
> the mapper's intent and avoid ambiguity.
> Defaults aren't always obvious. For example, people mapping pipelines
> have documented millimetres as the default for diameter=*, but it seems
> tree mappers haven't gotten the memo and (reasonably) assume it's
> defaulting to metres like height=*, width=* or circumference=*.
> When a value is actually signposted on the ground, it's most likely
> preferable to use the original unit and avoid conversions. Apart from
> that particular case, I can see some benefits of your suggestion – _if_
> you can convince the community to reliably agree on how unit-less values
> are interpreted.
> > https://wiki.openstreetmap.org/wiki/Map_Features/Units doesn't help
> > regarding such issues.
> It helps by providing data consumers with information they need to
> support both explicit and implicit units. Some have gotten around to
> implementing that feature, others haven't yet – but in principle, it
> seems entirely possible to support queries like [voltage>20 kV], to use
> your example.
> Tagging mailing list
> Tagging at openstreetmap.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Tagging