Closed GoogleCodeExporter closed 9 years ago
It seems that the route file i was experimenting with does not conform to the
rules i had set out to adhere to. The filename should be identical to the name
of the route in the gpx file, in this case it was not.
That does not make this issue solved though, since it should be handled more
gracefully, either by renaming the route on the fly on import (e.g. to make it
identical to the filename).
A similar issue exists for track files, and this also needs to be solved
gracefully for importing gpx files. Importing causes another potential problem
here, routes/tracks may have names with characters not allowed in filenames.
This too needs to be handled gracefully.
Original comment by mark.hur...@xs4all.nl
on 2 Sep 2010 at 7:33
Won't be fixed in the 0.7 and 0.8 branches. The new qml based code deals with
gpx files differently, and will import the mentioned gpx files into its
database.
Original comment by mark.hur...@xs4all.nl
on 18 Jun 2011 at 4:26
Original issue reported on code.google.com by
mark.hur...@xs4all.nl
on 28 Aug 2010 at 8:06