The case I had in mind was Carto-OSM's claim to require the highest
level boundary admin_level tag to be on ways & within relations.
I'm unsure I'd describe it as a bug, as they haven't written any code
for it yet.
Those involved claim this is not possible within Carto-OSM:
http://overpass-turb
As a possible alternative, Imposm creates a relation_member tables that make it
fast and efficient to do whatever you want with routes (and even sites!) with a
trivial JOIN: you know which elements belongs to which relation and which
relation contains which element.
It's a bit like the planet_os
t;
>
> *From:* Paul Johnson
> *Sent:* Saturday, 19 May 2018 12:12
> *To:* Tag discussion, strategy and related tools <
> tagging@openstreetmap.org>
> *Subject:* Re: [Tagging] tagging arbiters (gone OT)
>
>
>
> On Mon, May 14, 2018 at 8:03 AM, Dave F
> wro
related tools
Subject: Re: [Tagging] tagging arbiters (gone OT)
On Mon, May 14, 2018 at 8:03 AM, Dave F wrote:
On 13/05/2018 22:34, Kevin Kenny wrote:
I've long said that the final arbiters of tagging should be... the people who
implement the routers, renderers, navigation sy
On Mon, May 14, 2018 at 8:03 AM, Dave F wrote:
> On 13/05/2018 22:34, Kevin Kenny wrote:
>
> I've long said that the final arbiters of tagging should be... the people
> who implement the routers, renderers, navigation systems,. search engines,
> and so on
>
>
> No.
>
> We already have the case wh
On 13/05/2018 22:34, Kevin Kenny wrote:
I've long said that the final arbiters of tagging should be... the
people who implement the routers, renderers, navigation systems,.
search engines, and so on
No.
We already have the case where Carto-OSM are requesting duplicated tags
on ways that are
