trace_log_summary.py is a small, standalone example for reviewing a KALMIX Trace session. It reads the three logs written by the application and creates a JSON summary of receiver-reported NMEA status, application events, and RTCM3 frame counts.
It uses only Python 3.9+ standard-library modules. It is not part of KALMIX Trace and does not expose Trace source code.
The script is licensed under the MIT License. KALMIX Trace remains proprietary software; this repository does not grant a license to the Trace binary, source code, receiver firmware, or KALMIX trademarks.
- APP log: local application events, such as correction-service connection and disconnection.
- NMEA log: timestamped receiver messages; the script summarizes GGA solution-quality values, satellite count, HDOP, and correction age.
- RTCM log: binary RTCM3 correction data; the script validates CRC-24Q frames and counts message types without exporting payload bytes.
python trace_log_summary.py `
--app APP_20260904_101006_852.log `
--nmea NMEA_20260904_101006_852.log `
--rtcm RTCM_20260904_101006_852.log `
--output session_summary.json `
--redacted-nmea nmea_sample_redacted.logThe resulting session_summary.json intentionally excludes latitude, longitude, route geometry, raw RTCM payloads, and correction-service credentials. The optional NMEA sample retains timestamps and message structure but removes coordinates and recalculates the NMEA checksum.
Publish the script, this README, and a redacted NMEA sample. Do not publish the original APP, NMEA, or RTCM files without review:
- Original NMEA records contain the driven route and exact coordinates.
- RTCM messages can carry provider/station identifiers and are subject to the correction service's terms.
- APP logs must be checked for server URLs, mountpoints, usernames, and credentials before release.
The JSON summary is diagnostic evidence only. It is not an accuracy report and must not be used to claim RTK accuracy, DR drift, availability, or correction-service performance.