Map Tile Version Management via Compatibility Tables
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing consistency between different versions of map data tiles in incremental compilation of geographic databases is challenging, as not all tiles include changes, leading to issues in maintaining compatibility across various versions.
Innovation Solution
A single monotonically ascending map version number is assigned to the map, and a tile compatibility table tracks updates, allowing users to determine compatible tiles by indexing versions relative to this global index, ensuring compatibility and identifying changed tiles between versions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of substance
If incremental compilation is used to update only certain portions of map data, then storage space is saved, but maintaining consistency between tiles with different versions becomes problematic
Solution Approach 1:
The map data is divided into discrete tiles that can be independently versioned and updated. Each tile is identified by unique coordinates and can be tracked separately through version identifiers, allowing selective updates without requiring full dataset redistribution.
Solution Approach 2:
Version identifiers are assigned to map data and tiles to track changes over time. By comparing version identifiers, the system determines which tiles have been updated and which remain compatible, enabling consistency maintenance through parameter comparison rather than complete data validation.
2Reliability
If all map data is recompiled and replaced with a new version, then data consistency is ensured, but significant storage space is consumed and update efficiency is reduced
Solution Approach 1:
Only the changed portions of map data (specific tiles) are extracted and updated, while the majority of unchanged tiles retain their existing versions. This selective extraction approach avoids the need to store and distribute complete dataset replacements.
Solution Approach 2:
Instead of performing complete data recompilation and replacement, the system applies partial updates only to affected tiles. This partial action approach achieves sufficient consistency for operational needs without the overhead of full dataset processing.
3Adaptability or versatility
If multiple versions of map data are maintained for different clients, then client-specific needs are met, but complexity of version management increases
Solution Approach 1:
A single global version identifier serves multiple functions: it tracks overall map data versioning, enables client-specific version selection, and facilitates compatibility determination across different tile versions. This universal versioning mechanism replaces the need for separate tracking systems.
Solution Approach 2:
The version identifier acts as an intermediary between the map data system and diverse clients, enabling compatibility determination without direct complex interactions. Clients can use version identifiers to autonomously determine which tiles to download or use, reducing server-side management complexity.
Data Source
AI summary
A map developer may maintain multiple versions of a geographic database including map tile data. Map tile data may be organized according to a versioning schema. A server, or an endpoint device in communication with the server, may receive a request for map data for a tile associated with a tile identifier and access a tile compatibility table with the tile identifier. The tile compatible table includes multiple tile version identifiers for the tile indexed by global map version identifiers and returns a compatible tile identifier and a compatible map version in response to the request for map data.