Issue while importing GPX-File with wrong version about routeconverter HOT 3 CLOSED

Hi watchingJu,

that's actually 2 effects:

1. As you already found out, the GPX file is invalid as it uses the wrong version attribute value. Whoever produces such files should be notified.
2. Upon failing to reading invalid GPX 1.0 and 1.1 RouteConverter tries to be more relaxed to read crappy files. This produces the funny output from the screenshot. I don't see an issue here since it's clearly visible that the input data is broken.

Best regards
Christian

from routeconverter.

Hello Christian,

thanks for your fast response.

1. Yes, the first thing I did when finding that bug.
2. When something in software is visibly broken it let me, as a tech person, interpret it in 2 ways:
   a) the input data is broken
   b) the output data (software) is broken

Some background:
I used this file in different programs and online tools before in search of a fitting tool, I did surprisingly not ran into this problem (means the other programs are less strict/accurate with parsing - a decision in design). This software (RouteConveter) did not produce any error, or other visible user feedback than a broken output, so my first thought was b) - either code wise (wrong parsing), or UX wise - no user feedback, that something went wrong while processing the data.

So my suggestion is - give some user feedback (alert box, message in the status bar,... like "Error in the input data, trying to parse the file anyway") that the program knows something is wrong with the input data, so the user knows it is not the program itself.

3. I guess the "400 response" because of the " at the end is either wrong parsing, or wrong logs (?).

Cheers,
Ju

from routeconverter.

Thank you for pointing out a bug in the decision logic whether the greedy Garmin POI Database format has correctly identified a file.

You can find the latest prerelease with the fix here: https://www.routeconverter.com/prereleases/en

from routeconverter.