@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class UpdateTrackerRequest extends AmazonWebServiceRequest implements Serializable, Cloneable
NOOP
Constructor and Description |
---|
UpdateTrackerRequest() |
Modifier and Type | Method and Description |
---|---|
UpdateTrackerRequest |
clone()
Creates a shallow clone of this object for all fields except the handler context.
|
boolean |
equals(Object obj) |
String |
getDescription()
Updates the description for the tracker resource.
|
String |
getPositionFiltering()
Updates the position filtering for the tracker resource.
|
String |
getPricingPlan()
Deprecated.
|
String |
getPricingPlanDataSource()
Deprecated.
|
String |
getTrackerName()
The name of the tracker resource to update.
|
int |
hashCode() |
void |
setDescription(String description)
Updates the description for the tracker resource.
|
void |
setPositionFiltering(String positionFiltering)
Updates the position filtering for the tracker resource.
|
void |
setPricingPlan(String pricingPlan)
Deprecated.
|
void |
setPricingPlanDataSource(String pricingPlanDataSource)
Deprecated.
|
void |
setTrackerName(String trackerName)
The name of the tracker resource to update.
|
String |
toString()
Returns a string representation of this object.
|
UpdateTrackerRequest |
withDescription(String description)
Updates the description for the tracker resource.
|
UpdateTrackerRequest |
withPositionFiltering(PositionFiltering positionFiltering)
Updates the position filtering for the tracker resource.
|
UpdateTrackerRequest |
withPositionFiltering(String positionFiltering)
Updates the position filtering for the tracker resource.
|
UpdateTrackerRequest |
withPricingPlan(PricingPlan pricingPlan)
Deprecated.
|
UpdateTrackerRequest |
withPricingPlan(String pricingPlan)
Deprecated.
|
UpdateTrackerRequest |
withPricingPlanDataSource(String pricingPlanDataSource)
Deprecated.
|
UpdateTrackerRequest |
withTrackerName(String trackerName)
The name of the tracker resource to update.
|
addHandlerContext, getCloneRoot, getCloneSource, getCustomQueryParameters, getCustomRequestHeaders, getGeneralProgressListener, getHandlerContext, getReadLimit, getRequestClientOptions, getRequestCredentials, getRequestCredentialsProvider, getRequestMetricCollector, getSdkClientExecutionTimeout, getSdkRequestTimeout, putCustomQueryParameter, putCustomRequestHeader, setGeneralProgressListener, setRequestCredentials, setRequestCredentialsProvider, setRequestMetricCollector, setSdkClientExecutionTimeout, setSdkRequestTimeout, withGeneralProgressListener, withRequestCredentialsProvider, withRequestMetricCollector, withSdkClientExecutionTimeout, withSdkRequestTimeout
public void setDescription(String description)
Updates the description for the tracker resource.
description
- Updates the description for the tracker resource.public String getDescription()
Updates the description for the tracker resource.
public UpdateTrackerRequest withDescription(String description)
Updates the description for the tracker resource.
description
- Updates the description for the tracker resource.public void setPositionFiltering(String positionFiltering)
Updates 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 distance 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 helps educe the effects of GPS noise when displaying device
trajectories on a map, and can help control costs by reducing the number of geofence evaluations.
positionFiltering
- Updates 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 distance 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 helps educe the effects of GPS noise when
displaying device trajectories on a map, and can help control costs by reducing the number of geofence
evaluations.
PositionFiltering
public String getPositionFiltering()
Updates 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 distance 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 helps educe the effects of GPS noise when displaying device
trajectories on a map, and can help control costs by reducing the number of geofence evaluations.
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 distance 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 helps educe the effects of GPS
noise when displaying device trajectories on a map, and can help control costs by reducing the number of
geofence evaluations.
PositionFiltering
public UpdateTrackerRequest withPositionFiltering(String positionFiltering)
Updates 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 distance 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 helps educe the effects of GPS noise when displaying device
trajectories on a map, and can help control costs by reducing the number of geofence evaluations.
positionFiltering
- Updates 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 distance 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 helps educe the effects of GPS noise when
displaying device trajectories on a map, and can help control costs by reducing the number of geofence
evaluations.
PositionFiltering
public UpdateTrackerRequest withPositionFiltering(PositionFiltering positionFiltering)
Updates 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 distance 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 helps educe the effects of GPS noise when displaying device
trajectories on a map, and can help control costs by reducing the number of geofence evaluations.
positionFiltering
- Updates 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 distance 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 helps educe the effects of GPS noise when
displaying device trajectories on a map, and can help control costs by reducing the number of geofence
evaluations.
PositionFiltering
@Deprecated public void setPricingPlan(String pricingPlan)
No longer used. If included, the only allowed value is RequestBasedUsage
.
pricingPlan
- No longer used. If included, the only allowed value is RequestBasedUsage
.PricingPlan
@Deprecated public String getPricingPlan()
No longer used. If included, the only allowed value is RequestBasedUsage
.
RequestBasedUsage
.PricingPlan
@Deprecated public UpdateTrackerRequest withPricingPlan(String pricingPlan)
No longer used. If included, the only allowed value is RequestBasedUsage
.
pricingPlan
- No longer used. If included, the only allowed value is RequestBasedUsage
.PricingPlan
@Deprecated public UpdateTrackerRequest withPricingPlan(PricingPlan pricingPlan)
No longer used. If included, the only allowed value is RequestBasedUsage
.
pricingPlan
- No longer used. If included, the only allowed value is RequestBasedUsage
.PricingPlan
@Deprecated public void setPricingPlanDataSource(String pricingPlanDataSource)
This parameter is no longer used.
pricingPlanDataSource
- This parameter is no longer used.@Deprecated public String getPricingPlanDataSource()
This parameter is no longer used.
@Deprecated public UpdateTrackerRequest withPricingPlanDataSource(String pricingPlanDataSource)
This parameter is no longer used.
pricingPlanDataSource
- This parameter is no longer used.public void setTrackerName(String trackerName)
The name of the tracker resource to update.
trackerName
- The name of the tracker resource to update.public String getTrackerName()
The name of the tracker resource to update.
public UpdateTrackerRequest withTrackerName(String trackerName)
The name of the tracker resource to update.
trackerName
- The name of the tracker resource to update.public String toString()
toString
in class Object
Object.toString()
public UpdateTrackerRequest clone()
AmazonWebServiceRequest
clone
in class AmazonWebServiceRequest
Object.clone()