Trajectory Management and Analysis : Différence entre versions

De Transport
Ligne 12 : Ligne 12 :
 
* Generic interface to different database engines, possibly with spatial extensions (eg PostgreSQL with PostGIS, SQLite with SpatiaLite)
 
* 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
 
* Representation of clusters, motion patterns: prototypes, paths, Gaussian processes
 +
** motion prediction from historical data / large datasets
 
* Use of Catch for tests (https://github.com/philsquared/Catch): [https://raw.github.com/philsquared/Catch/master/single_include/catch.hpp header] only
 
* Use of Catch for tests (https://github.com/philsquared/Catch): [https://raw.github.com/philsquared/Catch/master/single_include/catch.hpp header] only
  

Version du 20 décembre 2012 à 18: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
    • motion prediction from historical data / large datasets
  • Use of Catch for tests (https://github.com/philsquared/Catch): header only

Data Sources

Resources

Récupérée de « https://www.polymtl.ca/wikitransport/index.php?title=Trajectory_Management_and_Analysis&oldid=285 »