Can you explain a bit how the geo-fencing is working in the project?
Usually, we need to set the geo-fence inside the tracking device itself, and the tracking device will send a notification once it is in or out of the geo-fence. Is this how things work in the opengts project? or the 'checking' is done on the server side and not in the tracking device?
Thank you.
Regards,
--houssam
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Houssam,
Geofencing within OpenGTS works by examing incoming events to see if they fall within a created Geozone, and it it does, the Geozone "description" is used as the custom address for the event.
The device may also send a Geofence arrive/depart message, which can be tagged in the EventData record with the appropriate Arrive/Depart status code. This would up to the specific device communication server which accepts/parses the data from the device, identifies the arrive/depart message type from the device, sets the appropriate status code, and inserts it into the EventData table.
Some devices do not support reporting geofence arrive/depart, and in this case the device communication server can use the Geozone table to determine actual geofence arrival/departure events and generate additional EventData records with the appropriate 'simulated' Arrive/Depart status codes.
Best Regards,
- Martin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Martin,
Can you explain a bit how the geo-fencing is working in the project?
Usually, we need to set the geo-fence inside the tracking device itself, and the tracking device will send a notification once it is in or out of the geo-fence. Is this how things work in the opengts project? or the 'checking' is done on the server side and not in the tracking device?
Thank you.
Regards,
--houssam
Hi Houssam,
Geofencing within OpenGTS works by examing incoming events to see if they fall within a created Geozone, and it it does, the Geozone "description" is used as the custom address for the event.
The device may also send a Geofence arrive/depart message, which can be tagged in the EventData record with the appropriate Arrive/Depart status code. This would up to the specific device communication server which accepts/parses the data from the device, identifies the arrive/depart message type from the device, sets the appropriate status code, and inserts it into the EventData table.
Some devices do not support reporting geofence arrive/depart, and in this case the device communication server can use the Geozone table to determine actual geofence arrival/departure events and generate additional EventData records with the appropriate 'simulated' Arrive/Depart status codes.
Best Regards,
- Martin