Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Vectorised map vs raster map #2596

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Closed

Vectorised map vs raster map #2596

openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment

Comments

@openstreetmap-trac
Copy link

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.

@openstreetmap-trac
Copy link
Author

Author: Ldp
[Added to the original trac issue at 10.05pm, Wednesday, 16th March 2011]

Sounds like a wonderful project for someone to develop, test and demonstrate on a testbed server somewhere.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant