Moving Objects Databases and Tracking
Spatio-Temporal Databases; Trajectory Databases
Moving objects database systems provide concepts in their data model and data structures in the implementation to represent moving objects, i.e., continuously changing geometries. Two important abstractions are moving point, representing an entity for which only the time dependent position is of interest, and moving region, representing an entity for which also the time dependent shape and extent is relevant. Examples of moving points are cars, trucks, air planes, ships, mobile phone users, RFID equipped goods, or polar bears; examples of moving regions are forest fires, deforestation of the Amazon rain forest, oil spills in the sea, armies, epidemic diseases, hurricanes, and so forth.
There are two flavors of such databases. The first represents information about a set of currently moving objects. Basically, one is interested in efficiently maintaining their location information and asking queries about the current...
- 1.Almeida VT, Güting RH, Behr T. Querying moving objects in SECONDO. In: Proceedings of the International Conference Mobile Data Management; 2006. p. 47–51.Google Scholar
- 4.Giannotti F, Pedreschi D, editors. Mobility, data mining and privacy. Berlin: Springer; 2008.Google Scholar
- 8.Lu J, Güting RH. Parallel SECONDO: a practical system for large-scale processing of moving objects. Proceedings of the 30th International Conference on Data Engineering; 2014. p. 1190–3.Google Scholar
- 15.Sistla AP, Wolfson O, Chamberlain S, Dao S. Modeling and querying moving objects. In: Proceedings of the 13th International Conference on Data Engineering; 1997. p. 422–32.Google Scholar
- 16.Speicys L, Jensen CS, Kligys A. Computational data modeling for network-constrained moving objects. In: Proceedings of the 11th ACM Symposium on Advances in Geographic Information Systems; 2003. p. 118–25.Google Scholar
- 18.Wolfson O, Chamberlain S, Dao S, Jiang L, Mendez G. Cost and imprecision in modeling the position of moving objects. In: Proceedings of the 14th International Conference on Data Engineering; 1998. p. 588–96.Google Scholar