Caching & Offline Data
Last updated
Last updated
MapsIndoors has three levels of caching:
Basic Data: All descriptions, geometries and metadata about POIs, rooms, areas, buildings and venues.
Detailed Data: The same as Basic Data, plus images referenced by the data.
Full Dataset: The same as Detailed Data, plus Map Tiles.
Full Dataset caching requires that Map Tiles are prepared specifically for this purpose. Contact MapsPeople in order to arrange this.
Out of the box, MapsIndoors automatically caches all basic data for the active dataset on the device, whereas images and Map Tiles are cached only as they are used.
This means all MapsIndoors-specific data is cached automatically, but images are only cached after they have been needed for map display. Likewise, Map Tiles are only cached when needed for map display, so all parts of the map that has been shown are cached. Areas and Zoom Levels that have not been shown as part of user interaction are not cached.
Applications have a few ways to change the default caching behaviour:
The synchronization process can be started manually:
The level of caching can be changed:
The most common use of MapsIndoors involves only one dataset, but for large deployments, data may be partitioned into multiple datasets.
Offline caching of multiple simultaneous datasets is fully supported, and is mostly limited by the available storage space on device.
NOTE: Only one dataset is active at any point in time.
Management of multiple datasets is done via MPDataSetCacheManager
, which allows querying, adding, modifying and removing datasets.
All datasets currently managed are accessible via the MPDataSetCacheManager
:
This can be used to build a management user interface, and information about individual datasets can be accessed from the MPDataSetCache
and MPDataSetCacheItem
classes.
Datasets are scheduled for caching using MPDataSetCacheManager
:
The current MapsIndoors API key is automatically added as a managed dataset with MPDataSetCacheScope.BASIC
.
Datasets are removed from caching using MPDataSetCacheManager.getInstance().removeDataSetCache(MPDataSetCache);
:
NOTE: The currently active dataset is not removed.
To change the extent of caching, for example in a management menu:
The estimated and cached size of a dataset is available via:
To refresh or get the size of a synced dataset:
This is an asynchronous process, and a MPDataSetCacheManagerSizeListener
is needed for getting information about progress and results.
The MPDataSetCacheManager
allows for detailed control over which datasets are synchronized, and allows for cancellation:
Listing Managed Datasets
Adding Datasets for Offline Caching
Removing Datasets
Changing Caching Parameters
Determining the Caching Size of a Dataset
Synchronizing Data with MPDataSetCacheManager
Listing Managed Datasets
Adding Datasets for Offline Caching
Removing Datasets
Changing Caching Parameters
Determining the Caching Size of a Dataset
Synchronizing Data with MPDataSetCacheManager