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

GUIDE: Best practice for track recorder.

Sun Oct 07, 2012 8:37 pm

Note: for an updated version of this and other articles, we recommend you to check our knowledge base here

GUIDE: Best practice for track recorder.

GpsGate will show all updates live whichever rate the GPS tracker sends them to the server. Live Event Rules will also be processed in any rate.

However it is not always necessary to store all track data in the database. Only data needed to process reports correctly and to display tracks correctly is needed. Most data sent to the server is redundant and can be filtered away once used for Live purposes.

The mechanism in GpsGate doing this is called the "Track Recorder". It has now been improved to display tracks better, and still using less database storage and CPU. If you have a faster update rate than once per 60 seconds it is important you read this for best performance. You can get as many as 5 times more GPS trackers on one server if you do this right. Tracks will also load and draw much faster, and reports will be processed faster.

Here are the best practices.

Make sure your Plugins are up to date

Make sure all plugins are "green" under SiteAdmin -> Plugins.

Note that the Track Recorder will not filter any Live data! It only removes redundant data you don't need, which wastes database storage and CPU required to store the data!

Set the TimeFilter to 60 seconds. This is the default value.

You can do this manually for each user, or by using this SQL query

UPDATE track_recorder SET time_filter = 60;

Note that even if you have a 10 second update rate, you should have the TimeFilter at 60.

If you want to prevent your users to set a lower TimeFilter value, use this SQL query:

UPDATE settings SET value_data = '60' WHERE value_name = 'MinTimeFilter';


Set the DirectionFilter to 30 degrees.

First you need to allow a new minimum value with this SQL query:

UPDATE settings SET value_data = '30' WHERE value_name = 'MinDirectionFilter';

You can then set the DirectionFilter manually for each user, or by using this SQL query

UPDATE track_recorder SET direction_filter = 30;

If you have a larger server in production and want advise, contact support.

Related topics

TIPS: Improve GpsGate Server performance!
http://forum.gpsgate.com/topic.asp?TOPIC_ID=14953

Regards,
Johan

GpsGate Support

vadr24
Posts: 155
Joined: Mon Apr 26, 2010 2:23 am

RE: GUIDE: Best practice for track recorder.

Sat Oct 13, 2012 5:41 am

¿Where can i find the "TimeFilter" and "DirectionFilter"?

In vehicle tracker under "Admin-> User-> Track recorder" just see "Direction change" and not the describe in lines above.

Thanks in advance.
Regards.

way4net_krumnow
Posts: 38
Joined: Thu Mar 07, 2013 1:31 pm
Location: Germany

RE: GUIDE: Best practice for track recorder.

Fri Jul 26, 2013 2:33 pm

To manually edit the TrackRecorder Settings in the Edit-User Window you need to set the User Type to "Empty(Advanced). Now you can see all the possible Values in the Accordeon.

Choose "TrackRecorder" there you have the settings for all the update frequencies, minimum distances etc. :)

sene
Posts: 113
Joined: Sun Sep 08, 2013 1:58 am

RE: GUIDE: Best practice for track recorder.

Tue May 06, 2014 3:32 pm

Hi Johan,

I have installed a demo on another server and the track recorder update interval is set to a minimum of 60 secs. How can i set it to say 10 sec?.

sene

Ultramarine
Posts: 6
Joined: Thu Oct 16, 2014 10:33 am
Contact: Website

RE: GUIDE: Best practice for track recorder.

Thu Oct 16, 2014 11:03 am

Yes,
I have the same question. How can I make GpsGate (now in demo mode for testing purposes) show tracks with 5 sec refresh rate?

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

RE: GUIDE: Best practice for track recorder.

Thu Oct 16, 2014 11:36 am

GpsGate only saves data necessary to generate reports and display historical tracks. Redundant data is sometimes filtered to improve performance.

Those are the default rules for historical and live data:

The distance change is 500 meters,
or the time change is 60 seconds,
or the heading change is 30 degrees,
or the speed change is 10 kph (requires latest Patch.v4)
or any of the inputs has changed value.

Please contact support @ gpsgate.com for more info on how to change those values.



Regards,
Johan

GpsGate Support

sg09
Posts: 95
Joined: Mon Feb 01, 2010 12:33 am

RE: GUIDE: Best practice for track recorder.

Tue Mar 24, 2015 11:03 am

Could you please help me implement the following:

Lets say we have a tracker that is configured to send data according to the following rules:
The distance change is 300 meters,
or the time change is 30 seconds,
or the heading change is 20 degrees

What shall we do have the system only store when track recorder parameters are met, and filter out / discard the rest?
track recorder parameters:
The distance change is 500 meters
or the time change is 60 seconds
or the heading change is 30 degrees

Only speed and ignition are mapped on the device.

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

RE: GUIDE: Best practice for track recorder.

Tue Mar 24, 2015 12:01 pm

Please contact support @ gpsgate.com for more info on how to change those values.


Regards,
Johan

GpsGate Support

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