Hi Steve,
in the context of Locus et.al. .map indicates a VECTOR map following Mapsforge format definition.
Such maps are crappy up to zoom level 10 or so, yet highly efficient when it comes to storage requirements, because the rendering is done on the dvice. Up to ZL 22 if you want.
Your description tells that you are dealing with RASTER maps. They are "costly" (size) for higher (detail) zoom levels.
The map your second link is pointing to is a raster map, i.e. an array on images.
I am sure that NZ has all data that you see as discrete value sets in a huge database, which is the source for the ArcGIS rendering.
If you get access to this data AND they can provide that in OpenStreetMap format, then you win. Even if they would give you a text export and their data model, you could convert to OSM, so you can use the OSM tools to build VECTOR maps.
They would be easy to digest for Locus, but need real processing power (and knowledge) to produce ...
in the context of Locus et.al. .map indicates a VECTOR map following Mapsforge format definition.
Such maps are crappy up to zoom level 10 or so, yet highly efficient when it comes to storage requirements, because the rendering is done on the dvice. Up to ZL 22 if you want.
Your description tells that you are dealing with RASTER maps. They are "costly" (size) for higher (detail) zoom levels.
The map your second link is pointing to is a raster map, i.e. an array on images.
I am sure that NZ has all data that you see as discrete value sets in a huge database, which is the source for the ArcGIS rendering.
If you get access to this data AND they can provide that in OpenStreetMap format, then you win. Even if they would give you a text export and their data model, you could convert to OSM, so you can use the OSM tools to build VECTOR maps.
They would be easy to digest for Locus, but need real processing power (and knowledge) to produce ...
The following users thanked this post: Steve_