Jim Ginn wrote:
Not sure why you you need the trucks location 'every second' ie:
31,536,000 rows per year per truck ?
doing every 30 seconds seems more manageable at 1,051,200 rows per year
per truck? Maybe better at 60 seconds?
OpenGGD is also designed to deliver GPS data in real time; we have
Juan:
Still seems excessive but in that case, ignore inserts that have no change
in lat / lon ...
Jim
Jim Ginn wrote:
Not sure why you you need the trucks location 'every second' ie:
31,536,000 rows per year per truck ?
doing every 30 seconds seems more manageable at 1,051,200 rows per year
Hello,
I'm currently developing a program for centralizing the vehicle fleet GPS
information -http://openggd.sourceforge.net-, written in C++.
The database should have these requirements:
- The schema for this kind of data consists of several arguments -latitude,
longitude, time, speed. etc-,
Juan
I don't think it really matters, doesn't look like you'll need any
features which are only available in one or the other!
The main issue you will have is supporting the application and the RDBMS
so go for the one you are most comfortable with and can support/configure
best.
Regards
John
Juan,
On Wed, Mar 18, 2009 at 11:14 AM, Juan Pereira
juankarlos.open...@gmail.com wrote:
Hello,
I'm currently developing a program for centralizing the vehicle fleet GPS
information -http://openggd.sourceforge.net-, written in C++.
The database should have these requirements:
- The schema
Juan:
We've had success with spatial indexes and mysql on our sites however our
numbers are smaller:
http://brokersnetwork.com (200,000+ records)
http://yearlyrentals.com (200,000+ records)
http://avalonrealestate.com/map.php (4,400+ records)
...
Not sure why you you need the trucks location
