AlpineQuest & OfflineMaps

Absolutely, there is new data!
I've updated the [url=https://psyberia.net/res/specs/psyberia_landmarks_files_specs.pdf]specs file[/url] accordingly.

Hi Psyberia

Related to http://forum.psyberia.net/viewtopic.php?t=3319, but this topic has the better title :-)

With some of my newer .trk files I get additional data in the {Location} records. Specifically, I get {LocationValue}s data that I don't know what it is. I'm getting types 0x65 and 0x61 as expected for the first two {LocationValue}s. But there's more, unknown data. It appears to be type 0x62, which isn't documented in the current spec (Update 6 ~ 2021.05.25).

For example (hex dump):

5 bytes spurious data: 62 41 6e 29 2a (type 0x62 int?)
14 bytes spurious data: 62 41 73 00 05 00 03 00 03 00 00 6e 29 2a (type 0x62 int and type 0x00 long?)

I'm just ignoring it for now as I get useful tracks anyway. But I'm curious... :)

Regards,
flipflip

I've added the specification of the new files.
As a reminder, the document is available here: https://psyberia.net/res/specs/psyberia_landmarks_files_specs.pdf

Hello,

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

Best regards.

[quote]Did the specification of the trk files changed?[/quote]
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/landmarks/explorer#how_to_display_export_copy_edit_or_delete_multiple_items

I'm trying to use this Python script [url]https://github.com/jachetto/alp2gpx[/url] 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. [url]http://psyberia.net/res/specs/psyberia_landmarks_files_specs.pdf[/url]