Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Storing location tracking data [closed]

Tags:

database

I am working on a project that requires me to store the history of a GPS device that sends its location every second. The application has to save and ultimately show the tracked route while the GPS device is active.

My main concern is saving all this data. Having multiple devices and saving all their positions throughout time seems like a difficult task.

How would I go about storing and retrieving the locations. Storing all this in a database doesn't sound logical to me. I would appreciate any help.

Thanks in advance

like image 911
AliAkbo Avatar asked Jul 21 '13 19:07

AliAkbo


2 Answers

It would make sense to only store a location if it's changed wrt the previous measurement. GPS devices are not on the move constantly after all.

You'd also have to think about things as:

  • how long will I store this data for? so can i recycle data spots?
  • if i only store changes, should i store a delta (not recommended) or an actual position?
  • how do i store the position in the least amount of space, whilst still being able to use the data to effictively calculate travelling paths (if need be), draw maps and what not

Basically - you'd have to look at all the requirements that this data will be used for, before stomping it all in a box...

like image 196
user1914292 Avatar answered Sep 22 '22 11:09

user1914292


Do you have a requirement to create reports on this routing data? If yes then have to persist data.

I can think of a couple of options to save this data.

  1. Using Cache blocks from Ms. Enterprise Library
  2. NoSQL databases

NoSQL databases like db40. Key/Value Storage more appropriate to use here.

  1. Lightweight database. SQLite or Google's LevelDB.

Frequency - Initially I will opt-in to store this data for every half mile. i.e to calculate the distance between first recorded location to the second location

like image 36
swapneel Avatar answered Sep 26 '22 11:09

swapneel