track
/api/track/
List methods: get, post, patch
Detail methods: get, put, patch, delete
Tracks work like the other API Resources with the exception that you may
supply a trackpionts argument to populate the associated Track. If
trackpoints are specified while modifying an existing Track, note that
they will replace the existing trackpoints.
Fields
- area:
-
Geometry data.
This field may be null
- distance:
-
Floating point numeric data. Ex: 26.73
This field is readonly.
- end_date:
-
A date & time as a string. Ex: "2010-11-10T03:07:43"
This field is readonly.
- id:
-
The primary key for this resource. Integer data. Ex: 2673
This field is readonly.
- importfile:
-
A single related resource. Can be either a URI or set of nested resource data.
This field is readonly.
- name:
-
Unicode string data. Ex: "Hello World"
This field may be blank
This field will default to: '' (empty string)
- range:
-
A reference to the resource. Maybe specified by URI or ID. Using a URI is recommended.
This field may be blank
This field may be null
- resource_uri:
-
The unique URI where the object resides.
This field is readonly.
- start_date:
-
A date & time as a string. Ex: "2010-11-10T03:07:43"
This field is readonly.
- user:
-
A user. Maybe specified by URI, email, or ID. Using a URI is recommended.
This field is required.
Filtering Options
- end_date: exact, gt, gte, lt, lte
- id: exact, in, gt, gte, lt, lte, range
- range: exact, in, gt, gte, lt, lte, range
- start_date: exact, gt, gte, lt, lte
- user: exact, in, gt, gte, lt, lte, range
Sorting Options
- id, user, range, start_date, end_date
© 2024 by Carré Technologies Inc.