Metadata Definitions support creating an arbitrary number of metadata properties to associate with Features, and support the following property types:

• primitive: A string, number, or boolean
• date: A date time in one of the following formats: epoch_millis, epoch_seconds, or iso8601
• array: An array of one of the primitive types listed above

When a Metadata Definition is associated with a Feature Collection, a JSON schema is generated from the Metadata Definition properties and is applied to validate the metadata object included in Feature ingest requests. Additionally, all metadata properties can be used as query criteria, with the following functionality:

• primitive
  • string
    • equals
    • like
    • does_not_equal
  • number
    • equals
    • greater_than
    • greater_than_or_equal_to
    • less_than
    • less_than_or_equal_to
    • does_not_equal
  • boolean
    • equals
    • does_not_equal
• date
  • equals
  • greater_than
  • greater_than_or_equal_to
  • less_than
  • less_than_or_equal_to
  • does_not_equal
• array
  • contains
  • does_not_contain

Feature Collections can support one of the following two geography types: polygon or point.

Feature Collections can also (optionally) be associated with a Metadata Definition.

Feature Collections also support "masked mode", which when enabled prevents query results or fetch responses from including the geography of features. Masked mode effectively prevents you from ever seeing the location data of any Feature in the Feature Collection.

Geofences allow for near-realtime webhooks when a point is ingested that matches specific criteria. The supported criteria modes are Point-to-Point distance and Point-in-Polygon. The supported events are documented as follows:

• enter: A Point has entered a specific Polygon or is within the specified distance of another Point, when it was previously outside
• exit: A Point has exited a specific Polygon or is outside of the specified distance of another Point, when it was previously inside
• inside: A Point is inside a specific Polygon or is within the specified distance of another Point, and there is no previous state for the Point

Webhooks will be sent on any of the following events: enter, exit, and inside via an HTTP POST request with a application/json request body. For example, if a Feature with the external_identifier vehicle_0001 entered a Geofence with the UUID 4d1695e5-85d2-4d81-8428-4dddc93b5d23, the following request body would be sent:

{
  "webhook_uuid": "2b946253-eccf-4015-a411-b9d806008147",
  "geofence_uuid": "4d1695e5-85d2-4d81-8428-4dddc93b5d23",
  "point_feature_collection": "0d9b7659-084c-4fc9-9be8-b66b01ada3a9",
  "point_external_identifier": "vehicle_0001",
  "event": "enter",
  "ingested": "2021-07-12T05:40:50+00:00"
}

Search all events for your account. Geofence matches, entity changes, and more are logged as events. This endpoint will return at max 100 items, use the before/after filters to scroll through the events.

Fetch a specific event