Rio Tinto Track Navigation - Meeting Notes

Explore

Jan 20 - UAT Feedback Responses

Post UAT-Testing Android Build

Newest Build (February 06, 2025)

⁠

com.hema.android.m5.1.4.0.apk

84.1 MB

⁠

This APK has the reduced size

Build (Jan 31, 2025)

⁠

build-013125.zip

157 MB

⁠

Partial Build (Jan 24, 2025)

⁠

partial-build-012425.zip

157 MB

⁠

Updated Documents

Proximity Alarm Test Cases:

⁠

Proximity Alarm Hema Test Cases- Submitted on Feb 06, 2025.xlsx

25.5 kB

⁠

User Guide

⁠

Doc not available https://coda.io/d/_djNlTWf1wPW/Running-the-Hema-Track-Navigation-App_suGy1ItW⁠

⁠

Onboarding Video

⁠

Jan 15 - Onboarding Video⁠

⁠

Fixes as of Jan 23, 2025

Improvement: End of Journey Trigger

Replaced the trigger for the End Trip view from ArcGIS’ built-in Route Tracking Status to explicitly check current location data to the Signal Destination asset, showing the End Trip view when at 100m or below.

Added a “Stop Now” label in the End Trip view.

Flashing LOA Indicator

Starts at 100m or below

Ends when the journey is ended either by selecting End Journey or choosing to Set New LoA

Does not end when the alarm for LOA is dismissed.

Improvement: Graphics Handling

Adds a separate GraphicsManager class

This partially aligns with changes related to:

fixed the NBS and Bridge bug from the UAT Feedback

Added NBS and Bridge tracks only for sections that overlap on the previewed/selected route.

Similar to assets with markers, the visibility should retroactively reflect on the map depending on the visibility settings.

NBS and Bridge should trigger an Asset Alarm regarding its proximity and alarm settings.

Alarm Trigger for NBS and Bridges should start at the closest point from the start location.

fixed a bug in the ALX Proximity, where it retains the Graphic, causing the app to draw multiple and duplicate layers.

Fix: ALX Alarm Notification

added an Alarm Notification when an ALX Alarm starts, similar to the LOA Alarm Notification

removed the LOA Alarm Notification (from January 22, 2025 meeting)

Improvement: Map Layers - Track Chainages

added a special case for Track Chainages Visibility Settings, where both High Level and Low Level (unofficial term) should reflect the Track Chainage (KM Markings) setting in the Asset Layer List settings.

The issue was that there were two different layers for the High and Low-level chainages and that we only handled one layer — matching the list of layers from the UI to the existing feature layers.

⁠

Track Chainage (High Level)

Track Chainage (High Level)

⁠

Track Chainage

Track Chainage

⁠

Improvement: LoA Options

Added separate proximity radius options for LOA consisting of:

200m, 300m, 400m, 500m, 1000m, 1500m, 2000m

Improvement: Screen Orientation - Pan to Location Update

Added an auto trigger to go back into Navigation mode after 5 seconds of idle from panning the map.

Note: Once you start to journey in a direction, we have the screen oriented going upwards

This would be the behavior if they clicked on the pan to location button after changing the map orientation/zoom.

Updated zoom behavior when using the Pan to Location button, when panning to location, the zoom level is retained except for the initial load that zooms at a default scale.

Improvement: Close Buttons + LOA State

added a close button on the Signal List view

updated Asset List view close button dimension for consistency

added a new default state for the top bar LOA

New Fixes (as of Jan 31, 2025)

Improvement: Navigation - Location Override

from UAT Feedbacks:

GPS Jumping Issue (#13)⁠

Wrong Track (#14)⁠

⁠

Context

Initially, we’ve used the ArcGIS SDK’s built-in

RouteTrackerLocationDataSource⁠

which automatically snaps the location puck to the route when the location is closed enough. Unfortunately, the algorithm to snap the location to route is not exposed for overrides nor does it accept some tolerance parameter.

The GPS Jumping and Wrong Track issues occur during navigation when the GPS goes beyond the internal distance tolerance used by ArcGIS and removes the automatic snapping-to-route until the GPS updates to be within it again.

Solution

To work around this, we used a

CustomLocationDataSource⁠

that accepts updates from the default location data source (

SystemLocationDataSource⁠

) and checks if the current location is within a given distance tolerance from the current route. If true, we pass the closest point from the current location and the current route and treat it as if it is the current location — this data is then processed by the built-in Location Display.

Distance Tolerance

As mentioned earlier, the implemented CustomLocationDataSource has a set distance tolerance that helps trigger the automatic snap-to-route behavior. For Hema’s decision, what should be the set distance tolerance (in meters)?

By default, the built-in ArcGIS distance tolerance is estimated to be at 14m-17m. From recent discussions and checking through Google Maps distance computations, the distance of a track to a bypass track is roughly 15m, give-or-take.

⁠

Google Maps

Google Maps

⁠

⁠

Given the right (and expected) conditions, the current build works where the automatic snap-to-route behavior is triggered.

However, from testing, we noticed that it may be better to have a distance tolerance of 30 meters. This covers a distance of at most the closer side of a nearby road from the rail track.

⁠