Skip to content

Add positioning log and navigation analytics artifacts - #156

Merged
abrignoni merged 1 commit into
mainfrom
feat/ford-positioning-logs
Aug 27, 2026
Merged

Add positioning log and navigation analytics artifacts#156
abrignoni merged 1 commit into
mainfrom
feat/ford-positioning-logs

Conversation

@abrignoni

Copy link
Copy Markdown
Owner

Adds two artifacts from the head unit's own service logs.

  • Positioning Log Coordinates (fdplog.np.txt): the coordinate lines in the log. The existing GPS speed artifact reads the same file but parses only the dead reckoning lines, which carry speed and heading and no coordinates, so these went unread. Four line shapes are covered and the Source column says which stage produced each row. The Result column is reported as stored, and every Trimble Output line recorded Failure on the tested image, so those rows are not confirmed fixes. Emits KML.
  • Navigation Analytics Events (fdplog.vn.txt): events from the hmi.analytics lines, with phase, attributes and identifiers. The application logs the names of the fields it withholds and redacts the coordinates itself, so those names are reported and no position is recoverable from them.

Also corrects the GPS speed artifact's note, which said the records carry no latitude or longitude. That is true of the lines it parses but reads as a statement about the whole file.

Positioning Log Coordinates reads the coordinate lines in fdplog.np.txt. The
existing GPS speed artifact reads the same file but parses only the dead
reckoning lines, which carry speed and heading and no coordinates, so those
lines went unread. Four line shapes are covered and the Source column says
which stage produced each row, since they are not equivalent. The Result column
is reported as stored; every Trimble Output line recorded Failure on the tested
image, so those rows are not confirmed fixes. KML is emitted.

Navigation Analytics Events reads the hmi.analytics lines in fdplog.vn.txt. An
event spans several consecutive lines on one thread. The application logs the
names of the fields it withholds and redacts the coordinates itself, so those
field names are reported and no position is recoverable from them. Most events
are searches and one records a system shutdown.

Also corrects the GPS speed artifact's note. It said the records carry no
latitude or longitude, which is true of the lines it parses but reads as a
statement about the whole file, which does contain coordinates.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@abrignoni
abrignoni force-pushed the feat/ford-positioning-logs branch from 5e37c66 to 9d97da9 Compare August 27, 2026 07:02
@abrignoni
abrignoni merged commit 37ad848 into main Aug 27, 2026
10 checks passed
@abrignoni
abrignoni deleted the feat/ford-positioning-logs branch August 27, 2026 07:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant