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: skippern[at]gimnechiske.org [Submitted to the original trac issue database at 5.41pm, Saturday, 2nd January 2010]
As of today the mapnik is a raster map, though the map data is indeed optimal for a vectorised map. I know that we can add a few vector layers on top of the raster map (whether Mapnik, Osmarender, Tiles@Home, OpenCycleMap, or whatever) such as the Maplint layer, but what about breaking it further down into more vector layers, such as different types of amenities, sac_level, mtb:scale, power grid, landuse, natural, isotopes (obviously not derived from OSM data), nautical objects, aeronautical objects, etc. This can allow us to see "all" objects on the map without overcrowding the map with too many objects.
It would also be a benefit if one could raise and lower the various layers in the vector map, and have names stick to layer or float (as independent layer).
Allowing this than the slippymap will behave prety much like the intention of fully vectorised ECDIS or other advanced vector maps.
The text was updated successfully, but these errors were encountered:
Reporter: skippern[at]gimnechiske.org
[Submitted to the original trac issue database at 5.41pm, Saturday, 2nd January 2010]
As of today the mapnik is a raster map, though the map data is indeed optimal for a vectorised map. I know that we can add a few vector layers on top of the raster map (whether Mapnik, Osmarender, Tiles@Home, OpenCycleMap, or whatever) such as the Maplint layer, but what about breaking it further down into more vector layers, such as different types of amenities, sac_level, mtb:scale, power grid, landuse, natural, isotopes (obviously not derived from OSM data), nautical objects, aeronautical objects, etc. This can allow us to see "all" objects on the map without overcrowding the map with too many objects.
It would also be a benefit if one could raise and lower the various layers in the vector map, and have names stick to layer or float (as independent layer).
Allowing this than the slippymap will behave prety much like the intention of fully vectorised ECDIS or other advanced vector maps.
The text was updated successfully, but these errors were encountered: