Open dhicks opened 3 years ago
I didn't think to check memory usage, but it's claiming dozens of GB within a few seconds of starting the script.
As indicated by the author of AlpineQuest on his forum, the format of TRK files has changed.
By comparing new and old TRK files, I was able to partially find the new format.
Now I have a version of alp2gpx which is able to create GPX file for my TRK. My TRK files contains only track segments.
If someone is interrested, I can shar my findings.
Yes, I'd be interested in taking a look.
It looks like you might be new to Github? If so, welcome! From my perspective, the easiest option would be if you created a fork of alp2gpx
with your changes, then provided a link in this issue thread. If you don't know how to do that and don't want to take the time to learn, maybe the easiest option would be for you to email me a zip file with your code, and I can set up the fork under my account.
Thanks for sending me the code! I've incorporated the elements most relevant to parsing the new file specification, and it appears to work successfully.
@dhicks , @ydespond everything is merged on master. I added a line to readme to thanks everyone for the contribute. Feel free to mod the README if something is wrong or if you think could be written better
I'm trying to convert some trk files that were recorded recently. The files aren't notably large (example), but the script appears to claim a lot of processor resources and freezes (I let it run for 5 minutes and it hadn't finished).
I don't know which version of AlpineQuest was used to record these, but currently I have AlpineQuest 2.2.8c.