Anyone mapping in Manchester might want to take a look for strange
fractional building:levels.
It's possible that some commercial editors found that they got better
results with open source 3D renderers by using ~0.75 per building level,
rather than the documented value of 1.
We recently had a
That’s parkland, surely?
Sent from my iPhone
On 16 Mar 2019, at 14:32, Martin Wynne wrote:
>> To me the simplest rule of thumb
>> is that a park is fenced, allowing the authorities to control access, while
>> a common is unfenced allowing anyone to access it at any time.
>
> The local
To me the simplest rule of thumb
is that a park is fenced, allowing the authorities to control access, while
a common is unfenced allowing anyone to access it at any time.
The local municipal park here is unfenced, just a row of low wooden
bollards to prevent vehicle incursions. Access on foot
On 16/03/2019 13:23, SK53 wrote:
OSM tagging is not analogous to the syntax and semantics of a computer
language or API.
Whilst there is possibly a valid point about Plain English, OSM tagging
is, very much, a computer API, albeit one where the semantics are fuzzy.
No, Carto is just one way of viewing OSM data. It has a small number of
maintainers and although highly visible does not represent any 'official'
view. Nor, incidentally, does the OSM wiki. Re-tagging things to make them
render on Carto is very poor practice. Use of park would be reprehensible &
And yes, I'm aware that tagging for the renderer is wrong, and that a
common isn't a park. But by making this change carto have effectively
redefined the common tag as deprecated.
On Sat, 16 Mar 2019, 12:54 Edward Catmur, wrote:
> They're going to be retagged anyway to get them to render in the
They're going to be retagged anyway to get them to render in the main map,
so I doubt that's a solution.
Any conclusion on how to tag them now?
Perhaps leisure=park, park=common?
On Sat, 16 Mar 2019, 12:51 SK53, wrote:
> Yup, it's gone. I think the standard thing is use Andy's (SomeoneElse)
Link to tagging thread:
https://lists.openstreetmap.org/pipermail/tagging/2019-March/043380.html
On Sat, 16 Mar 2019, 12:46 Dave F via Talk-GB,
wrote:
> https://github.com/gravitystorm/openstreetmap-carto/commit/4df96c4e4927c
>
> Plus a discussion in Tagging 05/03
>
> Unsure if this is a step
Yup, it's gone. I think the standard thing is use Andy's (SomeoneElse) map
which is likely to retain features of value & relevance to British & Irish
map users.
On Sat, 16 Mar 2019 at 12:35, Ian Caldwell via Talk-GB <
talk-gb@openstreetmap.org> wrote:
> In the last day or two the standard
https://github.com/gravitystorm/openstreetmap-carto/commit/4df96c4e4927c
Plus a discussion in Tagging 05/03
Unsure if this is a step forward. If it's being "misused", the common
tags should be amended to accurately represent the areas, not deprecate
the render. Seems like the tail wagging the
In the last day or two the standard renderer as stop rendering common land
(leisure=common) see https://www.openstreetmap.org/way/311973831
Ian
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb
11 matches
Mail list logo
