home api list

Hexostore API Documentation

trackpoint

/api/trackpoint/

List methods: get, post, patch

Detail methods: get, put, patch, delete

A trackpoint represents a GPS location. This model is mostly based on the representations found in Android and OSX devices.

On a list view, the meta attribute will contain two additional attributes: distance and total_tracks. The distance attribute is an object keyed by track URI of the distances covered by the query. To protect the server against unbounded queries, only the 10 latest tracks are included. The total_tracks attribute tells you how many tracks are covered by the query.

Fields

altitude:

Floating point numeric data. Ex: 26.73

This field may be null

This field will default to: None

course:

Floating point numeric data. Ex: 26.73

This field may be null

This field will default to: None

horizontal_accuracy:

Floating point numeric data. Ex: 26.73

This field may be null

This field will default to: None

id:

The primary key for this resource. Integer data. Ex: 2673

This field is readonly.

position:

Geometry data.

This field is required.

resource_uri:

The unique URI where the object resides.

This field is readonly.

speed:

Floating point numeric data. Ex: 26.73

This field may be null

This field will default to: None

track:

A reference to the resource. Maybe specified by URI or ID. Using a URI is recommended.

This field is required.

vertical_accuracy:

Floating point numeric data. Ex: 26.73

This field may be null

This field will default to: None

Filtering Options

end: exact

id: exact, in, gt, gte, lt, lte, range

range: exact, in, gt, gte, lt, lte, range

record: exact, in, gt, gte, lt, lte, range

start: exact

time: exact, range, gt, gte, lt, lte

timestamp: range, gt, gte, lt, lte

A hexotimestamp so that trackpoints may be queried in the same way as data

track: ALL_WITH_RELATIONS

user: exact

Sorting Options

id, track, time

© 2024 by CarrĂ© Technologies Inc.