Rio Tinto Track Navigation - Meeting Notes

Explore

2025 Meetings

April 11 - Route Recalculation Update

Auto-Route Recalculation Build (April 16, 2025)

⁠

com.hema.android.1.5.0.aab.zip

82.5 MB

⁠

Auto-Route Recalculation Video

Close-up Demo for Rerouting

⁠

Loading…

⁠

Zoomed-out Overview of Rerouting

⁠

Loading…

⁠

Recommendation for the Feature

Manual Re-calculation

If the GPS signal is weak at the start, the app might give an incorrect route—especially when tracks are close together.

Recommendation: add a “Recalculate Route” button to manually trigger the route recalculation; such that if the chosen route seems to be incorrect since it was based on bad GPS data, the button triggers the app to reset and recheck, and choose the right route and the right track you are on.

Considerations

Possibility of U-turns

While not a normal use case given our purposes, just noting in cases such as if the wrong track was selected initially from poor gps, or if there really is a necessity to switch between north and south lanes (U-turns) with the app active, or possibilities of operators going down the wrong track, these are some considerations to look at:

Case 1: If the user passes near the LoA but is still on a different track and hasn't reached the track yet where the destination signal is, the LoA alarm will be triggered and the End Journey prompt UI will appear, since the user entered the Proximity Radius of the LoA.

⁠

Triggerring_LoA_within_vicinity_but_still_needs_uturn_close_up.jpeg

Zoomed In

Zoomed In

⁠

Trigerring LoA within vicinity but still uturn zoomed out [focus on uturn point].jpeg

View of the entire route it needs to take

View of the entire route it needs to take

⁠

Possible Solution: Instead of using the point-to-point distance between the user location and the destination signal, we will have to use the route navigation distance instead — to indicate that the user still has to traverse the route before reaching the LoA.

Case 2: When tracks run close together, users might pass through the same Proximity Radius of alarms more than once. HOWEVER, alarms only trigger the first time—they won’t go off again if the user passes through the same area later.

⁠

ALX and other alarms existing for both lanes close up.jpeg

Zoomed In

Zoomed In

⁠

ALX and other alarms existig for both lanes zoomed out [focus on where the uturn is].jpeg

View of the entire route it needs to take

View of the entire route it needs to take

⁠

Possible Solution: Once the user leaves the Proximity Radius of the alarms, we will allow the alarm to go off again once the user passes the same area after doing a turnaround.

SUMMARY

Auto-rerouting works when users go off-route. However, when there are weak GPS signals, specifically at the start of the trip or in areas with closely placed tracks, this can result in incorrect routes. To address this possible issue, we proposed to add a manual “Recalculate Route” button. This allows users to trigger rerouting when needed for better control and recovery.

Meeting Notes (April 11, 2025):

Decisions Made:

Add a “Recalculate Route” button to allow users to manually trigger route recalculation.

Initially, the button will be included in the build but can be hidden through configuration when not needed.

Action Items:

Design team → Send the design of the Recalculate Route button for confirmation via email.

Engineering team → Implement the Recalculate Route button in the next build.

Gallery

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.