So since we're a weekend before the maps become free (https://www.swisstopo.admin.ch/en/swisstopo/free-geodata.html), I though I can post my map definition file with my favourite layers here:
SWISSTOPOMAPS.AQX
However, DO NOT download or use it before 01.03.2021. You have been warned. :)
Yes, one could read the "require any effort" part like that. But I think they mean "additional" or "manual" effort, such as non-standard products from their database, converting to some GIS formats, transformations into other systems and such. Let's see what they say in the mailing list. I wonder ...
Hmm. Why do you think that? The (draft of) the legal text (German) explicitly mentions use of the _service(s)_ as one of the free things. I'll ask in the mailinglist.
If i understand it correctly https://www.swisstopo.admin.ch/en/swisstopo/free-geodata.html says that we can use Swisstopo maps in Alpine Quest officially and legally from 31.03.2021: "[...] from 1 March 2021, swisstopo's standard digital products will be available online free of charge."
Mark asks in a PM: I have about 200 LDK files which I want to convert to GPX (so I end up with about 200 GPX files). I am not too techy but reading your post on the forum I think you have developed something. Is this right? If so I need to work out how to use your program on a Windows 10 machine ...
I think there's a bug when importing GPX files with timestamps. AlpineQuest (2.0.7) ignores timestamps in the format "yyyy-mm-ddThh:mm:ss+00:00", i.e. with the "+hh:mm" timezone specifier. This is what I get from other software. It seems it only understands the "yyyy-mm-ddThh:mm:ssZ" ones (it ...
I've identified the WPT and other files within the LDK format. I could probably work out the structure around it. But if you can document it, that would be easier.
Thanks for the update on the TRK format. This raises another question: I have a real-world track. I extract this ...
I've got something working for the TRK, WPT, SET, RTE and ARE files. I've noticed that the specs don't seem to be up-to-date:
- There seems to be a 0xffffffff (-1?) after every {Metadata} in newer files. I have an old version 2 trk file that doesn't have that but with otherwise ...