« Trajectory Management and Analysis » : différence entre les versions

Version du 20 décembre 2012 à 21:41

Data structure for trajectories?
- dimention: 2D, 3D?
- time dimension: constant sampling rate?
Application data:
- GPS: potentially different sampling rate
- fixed point detection (eg, BT)
- mobile id detection (BT from mobile sensors such as smartphones (Y. Malinovskiy))
- tracking from video data: potential missing points (occlusion)
- uncertain positions (spatial and time)
Exceptions ??
Python bindings: inspiration from OpenCV?
Generic interface to different database engines, possibly with spatial extensions (eg PostgreSQL with PostGIS, SQLite with SpatiaLite)
Representation of clusters, motion patterns: prototypes, paths, Gaussian processes
Use of Catch for tests (https://github.com/philsquared/Catch): header only

@@ Ligne 7 : / Ligne 7 : @@
 ** mobile id detection (BT from mobile sensors such as smartphones (Y. Malinovskiy))
 ** tracking from video data: potential missing points (occlusion)
+** uncertain positions (spatial and time)
 * Exceptions ??
 * Python bindings: inspiration from OpenCV?