-
Notifications
You must be signed in to change notification settings - Fork 1
[admin] Hide administrative boundaries in default mapnik layer #3588
Comments
Author: katpatuka -1: I need them. |
Author: stanton Google Maps does show administrative boundaries above a certain level, also depending on zoom. National boundaries are shown even at low zoom levels, region/county/canton boundaries are shown at higher zoom levels. Suggestion:
|
Author: ponzu Agree with the above comments: leave boundaries visible up to admin level 8 for the reasons stated. Hide for level 9 and higher. |
Author: Kozuch I am happy to see some replies here. I do not know what "admin level 8" means, but I guess we should rise the bar for the zoom that all admin. boundaries can be seen in - I mean the zoom level when viewing the map online. I guess moving the whole view few zooms up is a good idea like other online maps have it. |
Author: Kozuch The density of administrative boundary marking also probably depends on location. In CZ for instance such boundaries are heavily displayed all accross the country. Example is here: http://www.openstreetmap.org/?mlat=50.4167&mlon=16.16289&zoom=13 If you scroll the map a bit towards the CZ inland, you almost do not see roads through the boundaries at certain zoom levels. |
Author: Kozuch Somewhat related: "Administrative borders are too bold" (http://trac.openstreetmap.org/ticket/3973) |
Author: math1985 This is now being discussed on Github: gravitystorm/openstreetmap-carto#619 |
Reporter: Kozuch
[Submitted to the original trac issue database at 2.25pm, Tuesday, 15th March 2011]
Administrative boundaries that are rendered in default mapnik layer are disturbing and ugly. They interfere with roads and ways and make the overall map-reading experience a nightmare. Do we really need them? No major mapping service like Google Maps, Bing or Yahoo Maps uses such a feature in default view. I really do not see any particular benefit to have these boundaries displayed in such visibility as they are now. Lets hide them from the default render on openstreetmap.org.
The text was updated successfully, but these errors were encountered: