Page 1 of 1

trk file specification

Posted: Sun May 02, 2021 11:41 pm
by danhicks
I'm trying to use this Python script https://github.com/jachetto/alp2gpx to batch convert trk files to gpx. The script works correctly with a recording made on February 27. But starting with a recording made on March 21 the script has a lot of weird behavior — it reads the file version as 1347423745, can't find any metadata fields, and raises UTF-8 encoding errors once it starts trying to parse the segments.

Did the specification of the trk files change in March? All I've been able to find is this document, which is dated from 2017 but time-stamped last July. http://psyberia.net/res/specs/psyberia_ ... _specs.pdf

Re: trk file specification

Posted: Mon May 03, 2021 4:17 pm
by Psyberia-Support
Did the specification of the trk files changed?
Yes absolutely, sorry for the lack of advertisement.
Since AQ 2.2.8 / OM 3.7, the files are saved in a new format version which is slightly different. Changes include fastest read/write support, multi-areas with holes support, additional data field bound to locations.
I'll update the specification file as soon as possible.
Until then, you can still bulk export your items from the app: https://www.alpinequest.net/en/help/v2/ ... iple_items

Re: trk file specification

Posted: Thu May 13, 2021 2:30 pm
by ydespond
Hello,

I have the same issue as 'danhicks' and I am interrested to have the new file format too.

Best regards.

Re: trk file specification

Posted: Tue May 25, 2021 2:49 pm
by Psyberia-Support
I've added the specification of the new files.
As a reminder, the document is available here: https://psyberia.net/res/specs/psyberia ... _specs.pdf