AVL not appearing on Resgrid WebUI map or BigBoard

[toddmay222]

I recalled being able to see mobile units within the WebUI app nd the BigBoard.

Recently we do not see any units or devices appearing. Regardless if they are responding to a call or in standby mode.

Does anyone know if this is an issue with the CLIENT app NOT sending data to the cloud? The WebUI not being able to get the data fro the cloud? Or the middleware layer not processing the data?

Any help regarding documentation or debugging would be appreciated.

[ucswift]

Hey @toddmay222,

Locations are tracked in 2 ways for Personnel and Units.

1. The location is saved with events when they are submitted from the apps with geolocation coordinates. For personnel this may also require disabling Auto-Available in the Department Settings as the Autoavailable status does not have coordinates attached to it. These coordinates are stored in the main database.

2. Every 30s each app will get a new location and see if the it has moved compared to the previous location timestamp. These location updates are stored in a separate document database. (See https://github.com/Resgrid/Unit/blob/master/src/app/providers/geolocation.ts#L132 and https://github.com/Resgrid/Unit/blob/master/src/app/features/home/effects/home.effects.ts#L331).

When the map loads up currently is pulls statuses and their locations from the primary database, but they don't get the latest known location from the document db. Instead they listen for updates and reflect them on the map in near real-time. So if you keep the map up and it keeps it's connection open to the server it'll receive location updates from the units (for the 30s location update pings) and move or display the marker on the map.

[toddmay222]

Does this logic happen all the time?  Ir only when personnel are in route to call? The hope is that units would appear all the time regardless if responding to call.  As this allows dispatch to select the closest unit to call. Sent from Yahoo Mail on Android On Wed, Oct 11, 2023 at 19:31, Shawn ***@***.***> wrote: Hey @toddmay222, Locations are tracked in 2 ways for Personnel and Units. - The location is saved with events when they are submitted from the apps with geolocation coordinates. For personnel this may also require disabling Auto-Available in the Department Settings as the Autoavailable status does not have coordinates attached to it. These coordinates are stored in the main database. - Every 30s each app will get a new location and see if the it has moved compared to the previous location timestamp. These location updates are stored in a separate document database. (See https://github.com/Resgrid/Unit/blob/master/src/app/providers/geolocation.ts#L132 and https://github.com/Resgrid/Unit/blob/master/src/app/features/home/effects/home.effects.ts#L331). When the map loads up currently is pulls statuses and their locations from the primary database, but they don't get the latest known location from the document db. Instead they listen for updates and reflect them on the map in near real-time. So if you keep the map up and it keeps it's connection open to the server it'll receive location updates from the units (for the 30s location update pings) and move or display the marker on the map. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[ucswift]

It should happen all the time as long as there is geolocation data in the status payload and while the map is open and connected (to receive real-time location updates). I have a todo item to pull the latest location updates from the document db on map load which should help some of the issues.

Background geolocation, when the app is not active app or when the screen is off does have some limitations that could impact delivery of geolocation updates that way.

If you have a department on the hosted platform open up a ticket and supply your department id and a unit that wasn't showing geolocation and I can take a look for you. I've also created a ticket to circle back on the mapping module to dive into the logic to ensure it's properly handling those locations.