Visible now! :-)
On 2018-12-19 03:30, Sergio Manzi wrote:
>
> Thank-you Claudius,
>
> I've posted an answer in the forum, but I'm afraid it is awaiting for
> moderation (I'm new to the forum...).
>
> Cheers,
>
> Sergio
>
>
> On 2018-12-18 22:20, Claudius Henrichs wrote:
>> I couldn't be happier t
Thank-you Claudius,
I've posted an answer in the forum, but I'm afraid it is awaiting for
moderation (I'm new to the forum...).
Cheers,
Sergio
On 2018-12-18 22:20, Claudius Henrichs wrote:
> I couldn't be happier to have the "Benefits of namespaces" discussion
> happening right now on this M
Thank you for the clarification.
(Tagging the Y-junctions and traffic circle entrances results in a small
rendering issue with the current Openstreetmap-carto style, but if is a
tagging mistake we don’t need to change anything.)
On Wed, Dec 19, 2018 at 7:52 AM Michael Booth wrote:
> Agreed, a sh
Agreed, a short Y section before a roundabout because there is a small
bit of painted or physical separation doesn't mean they are _link roads
- it's still the same through road.
The wiki says "The _link tags are used to identify ... 'channelised'
(physically separated) at-grade turning lanes
I couldn't be happier to have the "Benefits of namespaces" discussion happening right now on this ML.
I am about to finalize a tagging proposal for a new sub-tag. I am wondering about the pros and cons of the traditional "OSM tag chain" (foo=bar + bar=baz) versus "Laymans namespacing" (foo=bar + b
> On Dec 17, 2018, at 2:17 PM, Martin Koppenhoefer
> wrote:
>
>
> The bigger problem could be verifiability. OSM is about crowd sourced geodata
> while this property seems to require expert capabilities and additional
> information you cannot get non-destructively on the ground?
>
For what
On Mon, Dec 17, 2018 at 2:19 PM Martin Koppenhoefer
wrote:
> It is at least debatable, I know there are some people who love long
> structured tags, although this idea is in a minority in Osm tagging, most
> people do not use tags like this. It doesn’t seem necessary in this case to
> use a struc
