Skip to content
hema-maps
Rio Tinto Track Navigation - Meeting Notes
Share
Explore
Jan 20 - submitted first version
Jan 21 - added visuals for flashing LoA
Issues Reported
Search
Column
RT Reported Issue
Dev Team Feedback
Jan 22 Meeting Notes
Dev Team Additional Media
Issue Type
Status
1
Flashing of screen
This is visible in the day one video.
The page is flashing locations about once a minute.
We would like to ask for the video mentioned so we can visualize the bug.
​
2
LOA options
Current LOA options to select are: Choose from values: 50m, 100m, 200m, 400m, 500m, 1000m. the 50m and 100m are just too short and close.
is it possible to remove the 50m and 100m options
and replace them with 1500m and 2000m options?
So just shift the options to = 200m, 400m, 500m, 1000m, 1500m, 2000m
Are these options intended only for LOA or for all items with a Proximity Setting? If the latter, what would you like as the new default, given that 100m is the current default for assets?
Only for LoA
= 200m, 400m, 500m, 1000m, 1500m, 2000m
3
LOA End of Journey
Right now the end of Journey comes up when we reach the Selected LOA signal. We don’t want them to reach the actual signal as that is too far. I have mentioned this in some of our meetings. In conjunction with the above 1. LOA options the minimum LOA to be 200m.
Can we have the end of Journey pop up when it is 100m away instead of 0m away?
⁠
unnamed.png
⁠
⁠
We can do this, but just note that we won’t be using ArcGIS’ built-in destination reached detection.
Understood that we will implement our own destination radius for this to occur.
6
Flashing and adding of text “You are 100m away from your LoA - STOP NOW”
and adding it to the screen below
Add text in red and the same size as the Destination text and bold.
⁠
unnamed.png
⁠
⁠
We can do this. Since it’s a new feature, we’ll just need the go-ahead from Brett.

Please see the video demo here→

We altered the requested design position a bit, because users are more likely to focus on the top section first, following the standard reading pattern (top to bottom).
Also for consistency with the rest of the UI and immediate visibility.
Confirming we will re-enable it for both states
More refined design below:
⁠
image.png
⁠
⁠
flashing_preview.webm
4
NBS
When there is a LoA in progress the NBS is very difficult to see. Can we make them a little wider or something so that they can still be seen across the Blue LOA line?
I don’t believe it alarmed when we crossed the NBS either. Please check.
NBS are actually tracks instead of points, so there wasn’t any difference override-wise so it’s not that distinguishable. Will add the described override, but we’ll also verify if the alarms for these are functioning correctly.
​
5
Bridges
Same as above
Alarm of a bridge I don’t think I can verify with
Same case with NBS, but we’ll also check.
​
7
ALX POP UP
The ALX pop-up is not happening
It is popping up for the LOA which we actually said was not needed. Please look into this as it might just be the wrong way around.
⁠
image.png
⁠
⁠
I think we misunderstood prominence over LoA for removal in one test case, we’ll fix this right away.

Decision: hide LoA popup
Make sure ALX popup is visible
​
8
Map Layers
Track Chainage is turning the high level KM on/off
The lower KM markers are not turning off
⁠
image.png
⁠
⁠
We used the layers available in the MMPK. We’ll double-check the current toggling settings and, if necessary, coordinate with Scott to confirm which layers should be enabled or disabled.
Brett to manage
9
Settings page
Version and updates are not there.
⁠
image.png
⁠
⁠
The "Check for Updates" AKA over-the-air updates is outside of our current scope, but we’ll add in the Map version label.
​
Since it’s a new feature, we’ll just need the go-ahead from Brett.
Brett to manage
10
Orientation on screen
I know when we are stationary GPS may not know which way you are facing.
But once you start to journey in a direction can, we have the screen orient going upwards
If you manually change the orientation on the screen, then after 5 seconds It snaps back to going upwards on the screen
Would like to confirm if you’re requesting a compass for navigation? The behavior described appears to be due to ArcGIS’ built-in navigation mode.
​
This will be a new feature since it wasn’t part of the planned scope.
We want the zoom level to adjust, and the angle should adjust to align with the GPS device’s movement so it almost stays stationary.
11
Driving off the screen
If you touch the screen the Icon will drive off the screen as it loses where you are.
Need to be able to just keep your location on screen and as per the above after 5seconds snap it back to normal starting orientation
We’d appreciate more context on this point—could you share a video to clarify? Though if you are requesting for auto-panning the location back into view every 5 seconds, this can be implemented.
If I’ve touched it, or looked somewhere else, can we wait 5 seconds before snapping back to the original location.
12
Re-center button
When you press the re-center button. It actually re-zooms you in also.
Can we either…
Recenter and not change the zoom level?
If a zoom level is required can we do 3 x button presses zoom out to be the normal level when the button is pressed?
The current zoom-in behavior is intentional. If preferred, we can remove the zoom feature entirely, which is simpler to implement.
Decision is to remove the zoom that is triggered when the user presses the recenter button
13
GPS jumping around.
So there was a point on the track where the application thought we were on the other side of the track.
I took a video of it and it is in teams page (under Day 2/3 videos)
It seemed to be in the cab that was the issue. Other end of the train the cab was fine. As soon as I stepped out of the cab the GPS managed to get me more accurately and put me on the right track.
Not sure how much we can do about this? As it seemed to happen on one side of the train and not the other it could of just been the particular canyon we were in. the work area was literally less than 1km so very little journey was happening at this point.
Something to discuss for options though.
This issue is difficult to diagnose without replication. Can you share the videos that reflect this issue? We’ll also investigate if ArcGIS can be forced to stay aligned with the route.

Update: investigating a possible fix, but a video would still be appreciated
​
14
If you are on the wrong track will it ever correct itself with the GPS and switch?
I had a report back from track inspectors on the MLEDD. Sorry I was not on this journey so I don’t have the full details of it all.
They started on 9 Road and got on track at the X9.2 non active level crossing
Heading south on the MLEDD line the application pushed them to cross at AR28A to the other side of the track even though the LOA they had picked was on MLEDD line.
They were staying on the Mainline but the application pushed them to the other track and then planned the LOA still by pushing them back to the MLEDD track further down.
On this instance they cancelled the journey and started it again.
After this again at the 40km mark it pushed them to the west side again at HG28A - cancelled and started again
Then with EM13 as the LoA it pushed them into the back track at EM53A instead of staying on the main line.
I would of thought it would keep you on the main line more than push to the back tracks.
This seems to be related to the GPS jumping issue. We’ll look into it further.
​
15
X to close buttons
Settings has an X to close
Assets have an X to Close
Is it missing on the LOA?
To keep it uniform if we can’t fit the X on the LOA page we could just remove it from the settings and Assets pages to keep uniform.
If we keep please ensure the sizes are the same as they differ currently
We’ll adjust these for consistency across the Settings, Assets, and LOA pages. We’ll also consult with Design to determine the best solution for the device.
​
21
Symbol Consistency
Symbols changed are only on the planned journey and not on the maps when there is no planned journey.
Is it the intention to change all the symbols to match?
⁠
image.png
⁠
⁠
Was the latest MMPK from Scott (Jan 10, 2025 4:28 PM) used for this?

Let’s check on the device.
​
22
New Updated Map
Active level Crossing X67.3 is currently down as a ALX but in the next version it will become a Non ALX
Understood. Once we receive the updated MMPK, we’ll ensure this change is reflected.
​
23
ArcGIS license before next build that goes to Alpine
​
​
There are no rows in this table
⁠


Want to print your doc?
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.