Asset Tracking Model Summary
Asset tracking is a growing use case for spatial database systems, with performance requirements that differ from traditional use cases. Traditionally, spatial databases are loaded with data infrequently and queried frequently. Traditionally, spatial databases store information that can be indexed in two dimensions. Traditionally, spatial databases do not have to deal with rapidly growing data sets, or data sets with more than several million records.
Asset tracking turns all those assumption on their heads. Data comes in quickly and continuously. Data cover the same areas over and over, requiring indexing on time as well as space. Data continuously grow, and huge spatial tables need to be managed and queried.
A general model for asset tracking can encapsulate the requirements for:
- Maintaining up-to-date information about current and recent asset locations and properties.
- Maintaining historical information about asset locations and properties.
- Firing events when assets enter and leave spatio-temporal alarm regions.
- Managing the continuous growth of historical data through partitioning.
- Providing support functions for temporal operations.
This road map item would deliver:
- Data model
- Testing framework for performance
- Implementation documentation
- Temporal utility functions
- Example web-mapping configuration
- Data management scripts
Funding
This roadmap item is currently unfunded.
Get a quote now!
Get a quote or read more about core development to add your support to a road-map item.
Other Roadmap Items
Indexed Nearest Neighbor Searches
Currently nearest-neighbor searching is carried out with ad hoc tricks that expand a search radius until a candidate set is generated, then finding the closest value in the candidate set. A directly indexed approach would be optimally fast.
The PostGIS spatial index currently works exclusively in the X/Y plane. For data such as fleet tracking the “Z” or “time” dimension can serve as a useful query restriction. Higher dimensional indexes are needed.
The ISO SQL/MM model includes an extension for a topological coverage: a geometry model in which nodes and edges are the basic building blocks and area covers are built up from those primitives. This allows very fast tests for adjacency and geometry unions, as well as editing and simplifying shared lines.