1. Oracle Fusion Field Service Questions and Answers
  2. What does the GPS data fields (gpstracks) data set contain?

What does the GPS data fields (gpstracks) data set contain?

The 'GPS Track Fields' ('gpstracks') contains data calculated based on the GPS data in Oracle Field Service in fixed format native for the application. All GPS data collected for each resource in the course of extraction period is gathered.

Important: This information only applies to Oracle Field Service environments. You can verify whether you've Oracle Field Service or Oracle Fusion Field Service, by signing in and checking on the About page.

GPS Track Fields are exported in the Daily Extract file for which 'GPS Track Fields' is selected as the entity. Any GPS Track fields available in Oracle Field Service (for example, 'distance', 'idle', 'status', etc.) can be included in the Daily Extract by adding them to the file structure.

Note: You can't edit the Field name for this entity.

Depending on the requirements of the company, the list of exported properties and fields can be changed at any time by removing or adding certain fields.

Data can be retrieved as one or more XML files consisting of 'tracks' root element that contains 'track' elements. 'track' elements are sets of 'Field' elements whose attributes are names of GPS Track fields and whose contents are their corresponding values.

This table provides the label and description of fields in the GPS Track Fields data set:

Field Label Description

Activity ID

gps_tracks.aid

The ID of the activity started at the moment of the data collection or if there were no started activities at the moment of the next activity in the resource' route

Distance

gps_tracks.distance

Distance from the resource's location to the activity. This field is measured in the unit of measurement set on the Business Rules page, Distance measurement units field.

Idle Time

gps_tracks.idle

Number of seconds the resource spent in the point.

Latitude

gps_tracks.latitude

The Y coordinate of the position.

Longitude

gps_tracks.longitude

The X coordinate of the position.

Resource External ID

provider.external_id

External identifier for the resource

Status

gps_tracks.status
Location status. Possible values are:

  • 0 - a position without warnings

  • 1 - a position has the alert "Started outside the location" (Started at driving)

  • 2 - a position has the alert "Completed outside the location" (Finish at driving)

  • 4 - a position has the alert "Resource left the activity location" (Driving at working time)

  • 8 - an 'idling' position (See Business rules to understand what position is considered as 'Idle' )

    Sometimes you might see values such as 5, 7, 9, which refer to a combination of two or more bits set:

    5 = 1+4

    7 = 1+2+4

    9 = 1+8

    For example, a status value = 5 means that both values 1 and 4 are set as follows:

    1 - a position has the alert "Started outside the location" (Started at driving)

    AND

    4 - a position has the alert "Resource left the activity location" (Driving at working time)

Time

gps_tracks.time

Timestamp received along with the GPS data.

Track Route ID

gps_tracks.queue_id

The ID of the route for which the geolocation data has been received.
Note: No changes and custom properties for this data set.

Example: GPS Track Fields File

The following data is collected. Provide a meaningful name to the report.

  • The ID of the queue for which the geolocation data has been received, for example, queue_id

  • The ID of the activity started at the moment of the data collection or if there were no started activities at the moment of the next activity in the resource queue, for example, aid

  • Timestamp received along with the GPS data, for example, time

  • The x coordinate of the position, for example, longitude

  • The y coordinate of the position, for example, latitude

  • Distance from the resource's location to the aid activity, for example, distance

  • Location status, for example, status

  • Number of seconds the resource spent in the point, for example, idle

The example provides details of two positions for a resource. On 10 October, 2012 , which corresponds to queue 00234, at 09:08:15, 10 October, 2013 the resource was at (41° 22' 51" North; 02° 07' 22" East) performing activity 89765 and the location of the resource fully complied with the route. On the same day at 10:25:45 the resource was at (41° 25' 49" North; 02° 27' 25" East) 5230 meters away from the next activity 96754. The resource had spent 36000 seconds at this point, which exceeds the idle threshold.

<?xml version="1.0" encoding="UTF-8"?>
<tracks>
   <track>
      <Field name=”queue_id”>00234</Field>
      <Field name=”aid”>89765</Field>
      <Field name=”time”>2012-04-10 09:08:15</Field>
      <Field name=”longitude”>41.380833</Field>
      <Field name=”latitude”>2.122778</Field>
      <Field name=”distance”>0</Field>
      <Field name=”status”>0</Field>
      <Field name=”latitude” />
   </track>
   <track>
      <Field name=”queue_id”>00234</Field>
      <Field name=”aid”>96754</Field>
      <Field name=”time”>2012-04-10 10:25:45</Field>
      <Field name=”longitude”>41.430278</Field>
      <Field name=”latitude”>2.456944</Field>
      <Field name=”distance”>5230</Field>
      <Field name=”status”>8</Field>
      <Field name=”latitude”>36000</Field>
   </track>
</tracks>