Device motion-activity when this location was recorded (eg: still
, on_foot
, in_vehicle
).
The age of the location in milliseconds, relative to the Device system-time when the location was received.
For example, if the reported age
is 10000
, that location was recorded 10s ago, relative to the system-time.
location.timestamp
+ location.age
= Device system-time when location was recorded.
Device battery level when the location was recorded.
latitude
, longitude
, speed
, heading
, etc.
Event responsible for generating this location (motionchange
, providerchange
, geofence
, heartbeat
).
Optional arbitrary meta-data attached to this location.
If this location was recorded due to a geofence transition, the corresponding geofence-event.
true
if location was recorded while plugin is in the moving state.
Present (and true
) if the location was generated by a "Fake Location" application or simulator.
Distance-traveled in meters. ℹ️
If this location was recorded due to ProviderChangeEvent, this is a reference to the location-provider state.
true
if the plugin is currently waiting for the best possible location to arrive. Samples are recorded when the plugin is transitioning between motion-states (moving vs stationary) or BackgroundGeolocation.getCurrentPosition.
If you're manually posting location to your server, you should not persist these "samples".
ISO-8601 UTC
timestamp provided by the native location API.
Universally Unique Identifier. You can use this to match locations recorded at your server with those in the logs. It can also be used to ensure if the plugin has ever posted the same location twice.
Generated using TypeDoc
Javascript Callback Schema
HTTP POST Schema
The location-data schema POSTed to your server takes the following form: