Valor Naram wrote:
> some long time ago I wondered why we have two tags for one
> purpose sometimes? For example: A mapper can use either the
> tag `contact:phone`or `phone` to add a phone number to the
> database. I think this makes the database dirty and for
> developers - like me - it's
om different worlds. More-Than-One-World Secrets. This connection
> I can try to create also among OSM folks (societies).
>
> Best regards
>
> Sören Reinecke alias Valor Naram
>
>
> Original Message
> Subject: Re: [Tagging] Multiple tags for one purpose
&g
tion I can try to create also among OSM folks (societies).
>
That is seriously OT.
> Best regards
>
> Sören Reinecke alias Valor Naram
>
>
> Original Message
> Subject: Re: [Tagging] Multiple tags for one purpose
> From: Paul Allen
> To: "Tag discu
I want to involve all user groups. Mappers, developers and local> communities.>> Cheerio>> Sören Reinecke alias Valor Naram>>> ---- Original Message ----> Subject: Re: [Tagging] Multiple tags for one purpose> From: marc marc> To: tagging@openstreetmap.org> C
----
Subject: Re: [Tagging] Multiple tags for one purpose
From: marc marc
To: tagging@openstreetmap.org
CC:
Le 24.08.19 à 18:04, Valor Naram a écrit :
why we have two tags for one purpose sometimes?
many (almost all bad) reasons can explain it :
- one key exist, a new schema is
rote:
> That's why I want to involve all user groups. Mappers, developers and local
> communities.
>
> Cheerio
>
> Sören Reinecke alias Valor Naram
>
>
> Original Message ----
> Subject: Re: [Tagging] Multiple tags for one purpose
> From: marc marc
>
That's why I want to involve all user groups. Mappers, developers and local communities.CheerioSören Reinecke alias Valor Naram Original Message Subject: Re: [Tagging] Multiple tags for one purposeFrom: marc marc To: tagging@openstreetmap.orgCC: Le 24.08.19 à 18:04, Valor Naram a
24 Aug 2019, 18:39 by pla16...@gmail.com:
> Editors won't (in general)
> implement tags in presets unless they're widely used.
>
This is not true. Barrier for support in editors
is really low.
Many tags that are not widely used are
supported.
For example man_made=obelisk
support was just
Le 24.08.19 à 18:04, Valor Naram a écrit :
> why we have two tags for one purpose sometimes?
many (almost all bad) reasons can explain it :
- one key exist, a new schema is born with a new tag for the same
feature/meaning, but the new schema never got a proposal or the proposal
never go into
> Editors won't (in general) implement tags in presets unless they're widely used. Unless editors and carto support tags, they won't get widely used, so editors and carto won't support them. Chicken and egg.Yes, you're right. But I was the author of "changing_table" and the guy who lead it throw
The tagging Community (this list) will negotiate it and it's the office at the same time. The process should be like the process for proposals but only discussion and vote.RegardsSören Reinecke alias Valor Naram Original Message Subject: Re: [Tagging] Multiple tags for one
Valor Naram het volgende geschreven:
>
> We need a system to prevent or instinct the usage of two or more tags for one
> purpose. I suggest the following behaviour:
> 1. Negotiating which key can be considered as official.
Who will negotiate, what do they have to negiate with?
What office
On Sat, 24 Aug 2019 at 17:06, Valor Naram wrote:
>
> In my opinion this is a topic we should consider working on and creating a
> wikipage to describe the "defragemtation" process in general.
>
Doing so is probably not going to achieve much. First we need to
defragment OSM itself.
It doesn't
Hey,
some long time ago I wondered why we have two tags for one purpose
sometimes? For example: A mapper can use either the tag `contact:phone`
or `phone` to add a phone number to the database. I think this makes
the database dirty and for developers - like me - it's annoying to
support two or
14 matches
Mail list logo
