Posts: 1035
Joined: Mon Feb 04, 2008 8:05 pm
Location: Thailand
Contact: Website

import of non-realtime tracks ?

Wed Jul 30, 2008 6:04 am

is it possible "on connect" to deliver historical tracks via GlobalsatProtocol ?

as example, if a unit goes out of GSM Coverage (we have this issue with boats on the Ocean)

as example last connection was 12:00 ... the boat goes for 2 hours arround ... and come back then at 14:00 the unit installed will reconnect and send _ALL_ recorded tracks back to the server ...

will there then later the track "completed with timestamps between 12:00 and 14:00 or will all updates apear at the reconnect time ?

antother thing is ...

is it also possible to have tracks in the past .. where realtime updates submited already ?
like update from 14:01 ... and then poistions follow from 12:10 ?
the reason is .. its may take a while to start/trigger the "download" .. so the unit may send already new realtime informations .. before the downoad is actually happening.

Backups are for WIMPS! (website position GpsGate Powered)

User avatar
Posts: 15145
Joined: Wed Aug 04, 2004 10:40 pm
Location: Sweden
Contact: Website

RE: import of non-realtime tracks ?

Wed Jul 30, 2008 12:02 pm

If you have the correct UTC time stamp on the buffered messages you send, then it will work for any of the supported protocol, including GlobalSat.

Here are the exact rules for GGS 2.0:
If you send data that goes forward in time, things will work as normally according to the track recording rules..
If you send historical data, this data will be saved in the current track, if it is within the current tracks time limits. If it is outside the current tracks time a new track will be created. This can lead to that many tracks are created if you alternate sending historical data, and real time data with a larger time difference.

If you use GpsGate Protocol (v.1.1), there are special features to support buffering. Using this protocol you will have exact control over how tracks are created. You can either implement GpsGate Protocol in the device, or in a proxy. The 2.0 protocol (unreleased) also contains many more features like status messages, etc.

(GGS 2.0 also have a plugin architecture, where rules for track recording and very much about anything can be replaced by custom .NET plugins. This is the most powerful way to customize the behavior of GGS 2.0. We will release SDK information about this step by step.)


Franson Support

Return to “GpsGate Server - How to setup and use”