Opened 9 years ago

Closed 6 years ago

#3302 closed enhancement (duplicate)

[landcover] "mapnik" rendering: residential or private gardens: reduce visibility at low zoom

Reported by: achadwick Owned by: achadwick
Priority: minor Milestone:
Component: mapnik Version:
Keywords: residential, private, garden, visibility, zoom, level of detail Cc:


A user in my area has recently been adding residential housing and gardens from high-resolution OOC mapping.

These are tagged



Could these be made a little less obvious at low zoom? By "low", I mean at around z14 or z15. To be perfectly honest I don't think private gardens should render at all at anything less than z18 or higher, and it may be wise to render residential gardens with a variation on the same sort of grey used for landuse=residential.

Rationale: the general public visiting the OSM website aren't going to be interested in residential gardens. The 80:20 rule applies for most zooms. For the detail-obsessed visitor and mappers like me, there's always z18.

Change History (7)

comment:1 Changed 9 years ago by Andrew Chadwick

More examples:

And a long thread in the German OSM forums:

The German example uses access=private to distinguish private gardens from interesting ones that we want on the map (IMO!). The Czech one uses, oddly, barrier=fence around the area... but I suppose that has a meaning of "private", given the nature of barriers.

Could "don't render if access={no or private}, or barrier=*" be used as part of a rule for rendering leisure=* areas?

comment:2 Changed 9 years ago by Andrew Chadwick

Maybe not the barrier criterion, since for the renderer you get into horrible logic like "does the barrier have an entrance and if so what are its access tags?" Far better to stick with plain old access=<no or private or get_orff_moi_laaarnd>.

comment:3 Changed 9 years ago by Andrew Chadwick

Corner cases like large and notable but nominally private estate gardens exist.

Can Mapnik rendering or db loads make use of hints hints from enclosing areas? If so, then surrounding the garden area with a larger landuse=residential ought to provide enough clue. But I'm not sure if this can be done.

Could look for landuse=residential on the object itself of course, and just render that with a higher priority. It's *true* of course - a residential garden has residential landuse - but it's not one feature:one OSM object, so it might not be great tagging.

comment:4 Changed 9 years ago by Andrew Chadwick

Another possibility (for tagging) which came up during discussion here: residential=garden, which is probably best described by its proposal: It has the distinct advantage of being backwards-compatible.

comment:5 Changed 9 years ago by achadwick

Owner: changed from mapnik-team@… to achadwick
Status: newaccepted

Okay, I'll just assume there's no great will to fix this in the renderer then. Let's address the problem by gathering some consensus among taggers and fix up the new, confusing documentation on the wiki page.

comment:6 Changed 6 years ago by math1985

Summary: "mapnik" rendering: residential or private gardens: reduce visibility at low zoom[landcover] "mapnik" rendering: residential or private gardens: reduce visibility at low zoom

comment:7 Changed 6 years ago by math1985

Resolution: duplicate
Status: acceptedclosed

This issue is now being discussed on Github:

Therefore, I will close the issue here.

Note: See TracTickets for help on using tickets.