Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

CreateTrackerRequest

import type { CreateTrackerRequest } from "https://aws-api.deno.dev/v0.3/services/location.ts?docs=full";
interface CreateTrackerRequest {
Description?: string | null;
KmsKeyId?: string | null;
PositionFiltering?: PositionFiltering | null;
PricingPlan?: PricingPlan | null;
PricingPlanDataSource?: string | null;
Tags?: {
[key: string]: string | null | undefined;
}
| null;
TrackerName: string;
}

§Properties

§
Description?: string | null
[src]

An optional description for the tracker resource.

§
KmsKeyId?: string | null
[src]

A key identifier for an AWS KMS customer managed key. Enter a key ID, key ARN, alias name, or alias ARN.

§
PositionFiltering?: PositionFiltering | null
[src]

Specifies the position filtering for the tracker resource.

Valid values:

  • TimeBased - Location updates are evaluated against linked geofence collections, but not every location update is stored. If your update frequency is more often than 30 seconds, only one update per 30 seconds is stored for each unique device ID.
  • DistanceBased - If the device has moved less than 30 m (98.4 ft), location updates are ignored. Location updates within this area are neither evaluated against linked geofence collections, nor stored. This helps control costs by reducing the number of geofence evaluations and historical device positions to paginate through. Distance-based filtering can also reduce the effects of GPS noise when displaying device trajectories on a map.
  • AccuracyBased - If the device has moved less than the measured accuracy, location updates are ignored. For example, if two consecutive updates from a device have a horizontal accuracy of 5 m and 10 m, the second update is ignored if the device has moved less than 15 m. Ignored location updates are neither evaluated against linked geofence collections, nor stored. This can reduce the effects of GPS noise when displaying device trajectories on a map, and can help control your costs by reducing the number of geofence evaluations.

This field is optional. If not specified, the default value is TimeBased.

§
PricingPlan?: PricingPlan | null
[src]

No longer used. If included, the only allowed value is RequestBasedUsage.

§
PricingPlanDataSource?: string | null
[src]

This parameter is no longer used.

§
Tags?: {
[key: string]: string | null | undefined;
}
| null
[src]

Applies one or more tags to the tracker resource. A tag is a key-value pair helps manage, identify, search, and filter your resources by labelling them.

Format: "key" : "value"

Restrictions:

  • Maximum 50 tags per resource
  • Each resource tag must be unique with a maximum of one value.
  • Maximum key length: 128 Unicode characters in UTF-8
  • Maximum value length: 256 Unicode characters in UTF-8
  • Can use alphanumeric characters (A–Z, a–z, 0–9), and the following characters: + - = . _ : / @.
  • Cannot use "aws:" as a prefix for a key.
§
TrackerName: string
[src]

The name for the tracker resource.

Requirements:

  • Contain only alphanumeric characters (A-Z, a-z, 0-9) , hyphens (-), periods (.), and underscores (_).
  • Must be a unique tracker resource name.
  • No spaces allowed. For example, ExampleTracker.