nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Tracker showing two locations for same account

MatthewKing

We're trying out tracker with 4 different users/accounts and for some reason one of the accounts is showing up in two locations. See the screenshot below. The one circled in red is the extra location and it's "stale"...hasn't moved, with the current location further to the right (east) Is there anyway to remove that old location?

I've looked at the table and there are two records, but have the same device ID & session ID, so I'm not sure why that happened.

Thanks!

Trouver plus de publications taguées avec

Accepted answers

Anonymous User

@MatthewKingWe installed a potential fix for 21.2 so if you upgrade hopefully you won't see the issue anymore. It was really difficult to reproduce but we believe it should be fixed in 21.2.X or later.

As for deleting the feature, in ArcGIS Online, you can only delete an entire users tracks, last known location, and track lines with single operation. There's no way to delete just the last known location. Here is a link describing how to do it.

For ArcGIS Enterprise, you can delete the last known location separately from the tracks. The same link provided instructions for that, just switch the layer id from 0 to 1 so it's using the correct layer.

All comments

ColinLawrence

@MatthewKing Extended periods of time where the device is offline/with no signal shouldnt be an issue, in general. Based on the logs it appears that an upload happened to be attempted during a momentary blip in connectivity. We are likely not handling this failure correctly in some specific scenarios but its been hard to track down. Your feedback is certainly helpful.

After this last instance, have you cleared the tracking service for this user? You mentioned you didnt have any additional issues this past Friday but I wasnt sure if you still had the existing triplicates or not.

MatthewKing

@ColinLawrence It could be that they would be moving in/out of connectivity. We are out in the woods, but it's not too remote, but it is a possibility. Also, there are areas of somewhat heavy tree canopy, but I'm not sure that would cause connectivity issues, though it might interfere with getting a good GPS signal.

We did another burn this past Friday and everything went ok, there were no duplicates even though I know of one time where one of the devices didn't get a cell signal.

ColinLawrence

@MatthewKing Comparing the device logs vs your screenshot of the multiple LKLs and timestamps at least one example seems to align with the stationary scenario I mentioned but that could be a coincidence. I also noticed a few failed uploads in the logs around that time as it appears the device is moving in/out of connectivity frequently. Is this common in the work areas? To have spotty connectivity?

MatthewKing

@ColinLawrence See attached logs. I named them after the first set of digits of the device ID.

Also, an update about anything unique...when setting up the devices in the morning before the burn, we do turn on the tracking and they do sit around a bit (around 1 hour) while we're conducting our pre-burn briefing and getting the rest of our gear setup.

Thanks!

64FB2A56.txt

D7DA52AF.txt

MatthewKing

@ColinLawrence I'll work on getting the logs, I guess I'll have to get them from both devices?

As for anything unique...this device/account was assigned to a "suppression" engine that monitors an area for fire going somewhere where it shouldn't. It would/could be idle for sometime, but probably no more than 10-15 minutes at the most.

ColinLawrence

@MatthewKing Do you happen to have the troubleshooting logs from the device on 7/21? They will be cleared after 7 days so it would be good to export those if you have access to the device. The fullname part is definitely strange. Looking into this on our end...

Is there anything unique about the movements of this fieldworker when this happens? Historically we saw this after the device was moving for some time but then went idle (with tracking on) and after an idle period started moving again; at this point a new LKL was created. Any hints to track this down and reproduce on our end. Thanks!

MatthewKing

@ColinLawrence thanks for the response. Yes for the same devices and all have the same version of Field Maps. However, in addition we did add some new devices (both iphone and android) so not sure about their version of FM.

The two duplicates with the same account for created_user & full_name have different device ID and the triplicate with the different full_name from the created_user as the same device ID as one of the above....all very confusing 🙂 Attached is a screenshot of the table (excel export) and I changed the account names. The other person is within our organization and was on the rx burn that day being tracked using a different device and that worked fine.

Like I mentioned I can maybe see where we messed up with one of the duplicates since we were adding new devices, but I can't figure out how there's one with a different full_name since to the best of my knowledge that field isn't editable.

Tracker_Triplicate3.PNG

ColinLawrence

Hi @MatthewKing. Are you still using the same devices on Android that you reported previously? What version of Field Maps are you running? Is the erroneous Full Name that is displaying registered to another user in your organization? Does the deviceID field match for all 3 features?

If you have the troubleshooting logs from this device still it would be good to compare the timestamp from when the new LKL was created vs what occurs at that timestamp in the troubleshooting logs on the device. Feel free to share them here if you are willing. We haven't seen this reported in some time.

Regards,

Colin

MatthewKing

@Anonymous User It's been a while and everything has been working well in the sense of no duplicates...until a few days ago. We had 10 devices/accounts out at the same time, no account was logged into the more than one device, however, the duplicate was specific to only one account. Actually, it was a triplicate.

When looking at the attribute table for LKL, for some reason for the triplicate account, one of the triplicates has a different name in the "Full Name" field (as opposed to the account name in the Created User field). For the other two records, the name in the Full Name field aligns with the account name in the Created User field.

Do you know why the triplicates may be happening and how did the Full Name field end up with a different account name in there? That's the one that really stumps me.

If this isn't making sense I can send you a csv of the attribute table, or share the feature layer with you.

Thanks!

Anonymous User

It will not just disappear after X days. The tracks have a retention period but the last known locations do not. So what you should do is:

Have the user sign out of the app and close it.
Update the app to the latest version
Delete the last known location
Sign back into the app and start tracking.

You don't have to change any Track Views.

MatthewKing

Great & thanks! We'll update the app and see if that works. @Anonymous User a few questions about the deleting...

If we do nothing except for updating Field Maps will that outlier Last Known Location eventually disappear or do we need to delete as noted in the link you provided?
If we need to delete to remove that stray location, is that just deleting the history and the next time that user turns on tracking everything is hunky-dory or do we need to add that user back using the Tracker Viewer settings?

-Matt

Anonymous User

MatthewKing

@Anonymous User it's version 21.1.0 build 347. Which version fixed this issue?

MatthewKing

@Anonymous User We're using Field Maps on Android 8 (Trimble TDC600). I'm not sure what version of Field Maps it is but I believe it's fairly recent as we updated all the Trimble units recently (~ one month ago) ....it's actually being used right now, I'll see if I can find out. Thanks!

Anonymous User

Hi Matthew,

Are you using Tracker or Field Maps with location tracking?

Do you know which version of Field Maps and which Operating System the user is using?

We have seen this issue before and believe we've fixed this in Field Maps so it'd be good to know if you are still seeing this in a recent version of Field Maps.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.