You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: ajashton [Submitted to the original trac issue database at 12.00pm, Friday, 10th August 2012]
Currently, aeroway=aerodrome nodes are only visible at 3 zoom levels-- Z10 as an icon and Z11-12 as text. Something along these lines in inc/layer-amenity-symbols.xml.inc would be good to increase their visibility: https://gist.github.com/3318292
I think this is important because I suspect the lack of visibility at higher zoom levels is causing confusion with mappers. I see airports duplicated in the database very frequently; more so than other types of objects.
When these objects are rendered at higher zoomlevels, duplicates are very easy to spot. Here are some particularly bad examples that were not difficult to find:
Reporter: ajashton
[Submitted to the original trac issue database at 12.00pm, Friday, 10th August 2012]
Currently, aeroway=aerodrome nodes are only visible at 3 zoom levels-- Z10 as an icon and Z11-12 as text. Something along these lines in inc/layer-amenity-symbols.xml.inc would be good to increase their visibility: https://gist.github.com/3318292
I think this is important because I suspect the lack of visibility at higher zoom levels is causing confusion with mappers. I see airports duplicated in the database very frequently; more so than other types of objects.
When these objects are rendered at higher zoomlevels, duplicates are very easy to spot. Here are some particularly bad examples that were not difficult to find:
http://api.tiles.mapbox.com/v2/mapbox.mapbox-streets.html#16.00/32.7316/-117.1935 [[br]]
http://api.tiles.mapbox.com/v2/mapbox.mapbox-streets.html#14.00/49.1928/-123.1810 [[br]]
http://api.tiles.mapbox.com/v2/mapbox.mapbox-streets.html#14.00/33.6333/-84.4348
The text was updated successfully, but these errors were encountered: