Select to view content in your preferred language

Location Tracking - How to reduce data retention or disable Tracks?

116
1
Wednesday
faronyoung68
New Contributor

Hi everyone!

With the surprise release of Tasks we are working to migrate from a glitchy workforce project to this new Field Maps option. The problem is, we need to know where our workers are when assigning tasks in order to efficiently assign work to our mobile workers. In workforce we could see the current location of workers, but Tasks doesn't have this option built in.

We instead had to use Location Tracking for the organization, and create a Geofence in our service area so that we can track worker location. 

This works for showing current location, but it also ends up storing Tracks and Track Lines by default. We know from experience, and from a little bit of testing, that these two layers will end up creating an absurd number of points and lines. We don't need to see the history of where our workers have been, and the retention time for the Tracks layer is defaulted to 30 days, which would leave us with potentially over a million points by the end of the month. That's quite costly from a credits perspective.

I have tried to edit the retention days for the Tracks and Track Line layers using the Admin REST services, but when I do I get an error telling my that the Operation is Not Supported.

Is there a way to reduce the retention time for the Tracks and Track Lines layers, or to remove these from location tracking entirely?

Thank you!

0 Kudos
1 Reply
JustinColville
Esri Contributor

Hello @faronyoung68 ,

 

In Field Maps, you can turn off location history and just share the last know location of the user with an app link or an MDM setting, called locationSharingShareLKLOnly.  You can find documentation for these settings in Deploy your map.

 

As you found, modifying the retention period for location data is not supported in ArcGIS Online (this is an option in ArcGIS Enterprise).  However, storage credits are not changed for location data stored in the location sharing feature service.

Regards,

Justin

0 Kudos