[Tagging] Let's get (quite) rid of units and their multiples in OSM values

Hi all, Yet another discussion about values with units in the database. In particular situations of keys implying particular units (like voltage=* with Volt), would it be good to improve tools, editors, websites or any other stuff dedicated to human reading to get voltage=40 displayed as volta

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

sent from a phone > On 26. Jul 2018, at 21:26, François Lacombe wrote: > > I don't want to break things but only improve them, all the best one issue with using only one unit for a tag is that they can’t always be transformed without rounding. E.g. maxspeed=55mph cannot be converted to kph

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

On 27/07/18 21:11, Martin Koppenhoefer wrote: sent from a phone On 26. Jul 2018, at 21:26, François Lacombe wrote: I don't want to break things but only improve them, all the best one issue with using only one unit for a tag is that they can’t always be transformed without rounding. E.g.

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

ct: Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values On 27/07/18 21:11, Martin Koppenhoefer wrote: > > sent from a phone > >> On 26. Jul 2018, at 21:26, François Lacombe >> wrote: >> >> I don't want to break things but only improve

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

On 27/07/2018 13:19, Andrew Hain wrote: ... and unit management support in editors. ... and presumably also in every data consumer that uses OSM data too? ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tag

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

gement support in editors. > > -- > Andrew > > *From:* Warin <61sundow...@gmail.com> > *Sent:* 27 July 2018 12:27:04 > *To:* tagging@openstreetmap.org > *Subject:* Re: [Tagging] Let's get (quit

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

ent support in editors. >> >> -- >> Andrew >> >> *From:* Warin <61sundow...@gmail.com> >> *Sent:* 27 July 2018 12:27:04 >> *To:* tagging@openstreetmap.org >> *Subject:* Re: [Tagging] Let's get

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

On 27/07/2018 16:20, marc marc wrote: I agree maybe with the exeption of case like maxspeed And maxheight and maxwidth. Phil (trigpoint) ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

Data consumers would convert to units they are interested in, no others. -- Andrew From: Andy Townsend Sent: 27 July 2018 14:34:41 To: tagging@openstreetmap.org Subject: Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values On

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

--------- >>> *From:* Warin <61sundow...@gmail.com> >>> *Sent:* 27 July 2018 12:27:04 >>> *To:* tagging@openstreetmap.org >>> *Subject:* Re: [Tagging] Let's get (quite) rid of units and their >>> multiples in OSM

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

>> Le 27. 07. 18 à 14:19, Andrew Hain a écrit : > >>> My own preference is to have no (zero) units in the database, decimals > >>> where wanted (maxwidth=2.2) and unit management support in editors. > >>> > >>> -- > >>> Andrew > >>> ----------

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

ndrew Hain a écrit : > > >>> My own preference is to have no (zero) units in the database, > decimals > > >>> where wanted (maxwidth=2.2) and unit management support in editors. > > >>> > > >>> -- > > >>> Andrew > > &

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

On Fri, Jul 27, 2018 at 6:48 PM, Kevin Kenny wrote: > I'm all for SI units for things like voltages and elevations. I'm > perfectly fine with tagging the elevation of Slide Mountain as 1274 > metres and letting a US data consumer convert that to 4180 feet. > I respectfully disagree. One reason

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

On 26.07.2018 21:26, François Lacombe wrote: > Then store voltage=40 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 m

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

Well okay Given problem is how can we query maxspeed like : [Maxspeed>25] ? It's not possible while units are stored with values. Then i agree that human display is a matter of tools, not database François Le ven. 27 juil. 2018 à 22:21, Tobias Knerr a écrit : > On 26.07.2018 21:26, François L

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

On Fri, Jul 27, 2018 at 5:33 PM, François Lacombe wrote: > Well okay > Given problem is how can we query maxspeed like : > [Maxspeed>25] ? Maybe the query tools could simply implement a function that converts number+unit to a numeric value only? [to_number(maxspeed) > 25] __

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

Le 27. 07. 18 à 22:44, Nelson A. de Oliveira a écrit : > On Fri, Jul 27, 2018 at 5:33 PM, François Lacombe > wrote: >> Well okay >> Given problem is how can we query maxspeed like : >> [Maxspeed>25] ? > > Maybe the query tools could simply implement a function that converts > number+unit to a num

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

2018-07-27 22:44 GMT+02:00 Nelson A. de Oliveira : > On Fri, Jul 27, 2018 at 5:33 PM, François Lacombe > wrote: > > Well okay > > Given problem is how can we query maxspeed like : > > [Maxspeed>25] ? > > Maybe the query tools could simply implement a function that converts > number+unit to a nume

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

I agree with François and Marc. Le ven. 27 juil. 2018 à 13:28, Warin <61sundow...@gmail.com> a écrit : > Unfortunately not everyone uses the same units... heights are in meters, > feet .. depending on where you come from or what activity you follow. > You're right, but as OSM is an international

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

On Fri, 27 Jul 2018 22:33:10 +0200 François Lacombe wrote: > Well okay > Given problem is how can we query maxspeed like : > [Maxspeed>25] ? > Which situation do we want to optimize for? The rare case, or the common case? It's common to want to document legal restrictions such as "speed limi

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

To avoid problems when querying, in case of explicitly add units, I would prefer to use a separate tag like maxspeed:units=mph, for example. Javier El sáb., 28 jul. 2018 10:30, Mark Wagner escribió: > On Fri, 27 Jul 2018 22:33:10 +0200 > François Lacombe wrote: > > > Well okay > > Given proble

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

sent from a phone > On 27. Jul 2018, at 19:48, Kevin Kenny wrote: > > I'm all for SI units for things like voltages and elevations. I'm > perfectly fine with tagging the elevation of Slide Mountain as 1274 > metres and letting a US data consumer convert that to 4180 feet. > > Regulatory thing

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

sent from a phone > On 29. Jul 2018, at 09:57, Javier Sánchez Portero > wrote: > > To avoid problems when querying, in case of explicitly add units, I would > prefer to use a separate tag like maxspeed:units=mph, for example. spreading the information over 2 tags creates another point of p

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

That sounds right but would not be clearer to use spacename instead of underscore? Like maxspeed:mph=25 That way you have to deal with main keys instead of split them into one key per unit. El lun., 30 jul. 2018 0:22, Martin Koppenhoefer escribió: > > > sent from a phone > > > On 29. Jul 2018, a

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

he format. -- Andrew From: Philip Barnes Sent: 27 July 2018 17:52:31 To: tagging@openstreetmap.org Subject: Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values On 27/07/2018 16:20, marc marc wrote: > I agree maybe with the exe

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

30. Lipiec 2018 01:00 od dieterdre...@gmail.com : >  elevations should be with respect to the EGM96 sea level Where it is written on Wiki? Nobody is really following that. ___ Tagging mailing list Tagging@openstreetm

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

There is a relatively simple solution that could satisfy everybody. (Except maybe the people paying for the storage, but let's say tags are cheap) For each tag that describes a measurement, add a counterpart tag with the values converted to SI units, meter, second, km/h (or even m/s, everybody equ

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

sent from a phone > On 30. Jul 2018, at 10:18, Mateusz Konieczny wrote: > > Where it is written on Wiki? ele tag definition > Nobody is really following that. I did not check any numbers, but I would also expect a lot of data not following this definition. Cheers, Martin

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

On Mon, Jul 30, 2018 at 11:39 AM Martin Koppenhoefer wrote: > I did not check any numbers, but I would also expect a lot of data not > following this definition. [of the ele=* tag meaining EGM96] Uhm, yeah. I've been using NAVD88 as orthometric datum. I have the tables loaded in my GPS app, an

Re: [Tagging] Let's get (quite) rid of units and their multiples in OSM values

On 31/07/18 02:33, Kevin Kenny wrote: On Mon, Jul 30, 2018 at 11:39 AM Martin Koppenhoefer wrote: I did not check any numbers, but I would also expect a lot of data not following this definition. [of the ele=* tag meaining EGM96] Uhm, yeah. I've been using NAVD88 as orthometric datum. I ha