Ticket #3885 (closed defect: wontfix)

Opened 3 years ago

Last modified 4 days ago

[landcover] landuse=military covers leisure=pitch

Reported by: flaimo Owned by: mapnik-team@…
Priority: minor Milestone:
Component: mapnik Version:
Keywords: Cc:

Description

the (ugly) lines from landuse=military cover areas with leisure=pitch, sports=x.

see:  http://osm.org/go/0JhLXApnD-

Change History

comment:1 Changed 3 years ago by TomH

  • Owner changed from tom@… to mapnik-team@…
  • Component changed from admin to mapnik

comment:2 Changed 3 years ago by bbauer

I think both ways (painting the pitch above the area marks of the military area or the other way round) are reasonable and have their advantages. I think the actual way is more logical for the following reason:

The pitch is part of the area that has military landuse. As far as I know military areas are typically not accessible by the public and therefore also the pitch is not acessible. This is shown by the light red overlay and the red "strike-out".

If you would allow the pitch to berendered above the military style it would look like it was not part of the surrounding military area.

comment:3 Changed 3 years ago by flaimo

i don't agree with that: a) landuse describes something logical, leisure=pith describes something physical. b) the style should be consistent. other areas don't draw over leisure=pitch, so why should landuse=military. for example landuse=allotments also count as private property, still leisure=pitch is drawn above the landuse.

comment:4 Changed 3 years ago by flaimo

to precise point a: the kind of access should be determinated by the access tag on the actual element, not by the landuse below.

comment:5 Changed 6 days ago by math1985

  • Summary changed from landuse=military covers leisure=pitch to [landcover] landuse=military covers leisure=pitch

comment:6 Changed 4 days ago by math1985

  • Status changed from new to closed
  • Resolution set to wontfix

In this case, the pitch is actually part of the military landuse, so I think the current rendering is correct.

I will therefore close this ticket as wontfix.

Note: See TracTickets for help on using tickets.