MicroMap – Horizontal & Vertical Layers

MicroMap files are organized in both horizontal layers (regions) as well as vertical layers (features).


Horizontal Layering

Large geospatial data like vector maps require a server-side decomposition into smaller data chunks. By default we divide the world map in many non-overlapping regions, preferably by continents, countries and even further down the hierarchy. For a hybrid solution we successively divide those regions in even smaller tiles until we reach a well manageable file size, with a target of let’s say 100 kbytes. MicroMap maps are created automatically from UMDB, our unified mapping database technology which supports literally any vector-based map. Since MicroMap comes with an API developers can easily implement spatial or map based applications without dealing with vector map data directly.


Vertical Layering

The vertical layers are by content type and/or data source and each layer can have different latency periods and update frequencies, this can mean (depending on the specific layer) that we indicate that the cache of that layer should be removed after a certain period of time or that its normal lifetime is up to a certain period of time so that the application can make a determination if the data should be trusted. The lowest priority in any sync would be data blocks that have changed but are inside their lifetime.

MicroMap API

With MicroMap we provide a low-level access library (API) that allows you to develop your own embedded, desktop or web application:

  • Provides abstraction layer and programing interface.
  • Application developers don’t have to deal with raw map data anymore.
  • Ultra-compact spatial map format which comes with a very fast data access interface.


Extremely Customizable

  • Both input and output is highly customizable though XML-like compiler configuration.
  • Composite Maps: extend area coverage by adding new MicroMap file to existing file set.
  • Customized details: pick the attributes, accuracy, richness, coverage you want.



  • Platform independent binary stream format.
  • The MicroMap library supports Windows CE/x86/amd64, Linux x86/amd64, Android, iOS and more CPU architectures.
  • No Little Endian / Big Endian hassle

Compression Rate

Whenever you deal with large vector maps, like street and road maps which are widely used in a variety of mobile applications, you need well compressed, but still fast accessible, maps. The relatively large size of vector maps has a negative impact on their usage on mobile devices, even if they are stored locally and not delivered wireless over the air. With MicroMap we provide a cutting-edge technology to compress large vector maps which can be stored on various mobile devices.

  • Loss-free map compression
  • Customizable/configurable map compression
  • Lossy compression available (if desired)
  • Breaks “sonic barrier” of loss-free street map compression
  • High compression rate: in average 93% to 95% of the original map source (GDF, SHP, XML)