Spatio-temporal data reduction with deterministic error bounds

Hu Cao*, Ouri Wolfson, Goce Trajcevski

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

138 Scopus citations

Abstract

A common way of storing spatio-temporal information about mobile devices is in the form of a 3D (2D geography + time) trajectory. We argue that when cellular phones and Personal Digital Assistants become location-aware, the size of the spatio-temporal information generated may prohibit efficient processing. We propose to adopt a technique studied in computer graphics, namely line-simplification, as an approximation technique to solve this problem. Line simplification will reduce the size of the trajectories. Line simplification uses a distance function in producing the trajectory approximation. We postulate the desiderata for such a distance-function: it should be sound, namely the error of the answers to spatio-temporal queries must be bounded. We analyze several distance functions, and prove that some are sound in this sense for some types of queries, while others are not. A distance function that is sound for all common spatio-temporal query types is introduced and analyzed. Then we propose an aging mechanism which gradually shrinks the size of the trajectories as time progresses. We also propose to adopt existing linguistic constructs to manage the uncertainty introduced by the trajectory approximation. Finally, we analyze experimentally the effectiveness of line-simplification in reducing the size of a trajectories database.

Original languageEnglish (US)
Pages (from-to)211-228
Number of pages18
JournalVLDB Journal
Volume15
Issue number3
DOIs
StatePublished - Sep 2006

Keywords

  • Data reduction
  • Line simplification
  • Moving objects database
  • Uncertainty

ASJC Scopus subject areas

  • Information Systems
  • Hardware and Architecture

Fingerprint Dive into the research topics of 'Spatio-temporal data reduction with deterministic error bounds'. Together they form a unique fingerprint.

Cite this