→ Vehicle Tracker can compute an average traffic state on the streets based on GPS points coming from:
- GPS points
- FCD probes
- ANPR portals
- Bluetooth portals
Important: If you have in your system both FCD data and portal data, you have two different endpoints.
Request
Request to servers different from Optima AS
In general, for FCD data, use:
POST <vehicletracker_hostname>[:port]/fcd/In general, for portal data, use:
POST <vehicletracker_hostname>[:port]/portal/Request if Vehicle Tracker is exposed only through the Optima AS
For FCD data, use:
POST optima-as/optima-wsi/proxy/fcdFor portal data, use:
POST optima-as/optima-wsi/proxy/portalRequest parameters
Not applicable
Request content-type
application/text
Request body (payload)
The request content-type leads to define the payload as CSV text message.
In the message, each row contains the following entries in the listed order:
- ID: Unique identifier of a vehicle trajectory. The identifier is a string.
- DATE: Timestamp of the point.
- XCOO: X coordinate (longitude) of the point. The decimal separator is a period.
- YCOO: Y coordinate (latitude) of the point. The decimal separator is a period.
- MODE: Optional data input corresponding to the transportation mode of the data feed.
Response
Response status
| HTTP status | Description |
|---|---|
|
200 OK |
Result of the processed request. |
Response content-type
Not applicable
Response entity
Not applicable
Example: Vehicle Tracker input
Request
http://hostname:1800/fcd/Request content-type
application/text
Request input
00535ea631b85594b4a8,2015-11-18T17:21:06Z,-100.545384,20.521201
00535ea631b85594b4a8,2015-11-18T17:24:27Z,-100.586678,20.501171
0427d15e7730e972b11f,2015-11-18T17:26:32Z,-100.219004,20.55482
081df06577e415ac592b,2015-11-18T17:26:30Z,-100.271793,20.62557
Response status
| HTTP status | Description |
|---|---|
|
200 OK |
Result of the processed request. |