GPSoverIP GPSAUGE GPSeye IN1, Manual, Page: 318 / 421

318
19. Open Interfaces
19.4. How does GPSoverIP function?
For an easier understanding of the functionality of GPSoverIP we explain a request and
response example at this place.
19.4.1. The Request
After the compressed data have been processed by the GPSoverIP gateway, these are, in
simple terms, available as HTTP-websites.
Through a fixed request mechanism which occurs via a HTTP-request to the gateway,
one gets a HTTP response which will be used for analysis.
The HTTP request can look as follows:
http://www.gps-explorer.de/mssqlclient/gpsshowposition.php?kdid=32044
&pwd=5d56394343ed33c388ad66e3aa28eb9b&geraet=200049
In this request an authentication, a device and a gateway selection is included.
An assignment can be found at “kdid” (User-ID), followed by an authentication via “pwd”
(Password), as well as the identification of the respective device at “device”.
19.4.2. The Response
The HTTP response to be processed then contains a standardized NMEA string with
receive confirmation if successful, the device ID, date and time real form.
Additionally one also gets the number of received satellites, the altitude and, if desired,
8bit user data, which can contain information about vehicle conditions (temperature,
alarm, etc.)
© GPSoverIP GmbH GPSeye IN1 (InOne) Service level: October 2008