Read one GPX file produces division by zero

[Luka Koprivc]

When I mass imported a mass collection, exported from strava, a large ammount of them failed. It would appear, when parsing the file a point is somehow read twice but differently - picture provided bellow.

These different points are actually one the the XML

[Iztok Fister Jr.]

assigned to @alenrajsp

[Iztok Fister Jr.]

Thanks @KoprivcLuka for raising this issue.

[alenrajsp]

I've checked the code and fixed it so that it still works even if two timestamps were somehow recorded with the same time.
Pull request #84 should fix this issue #83 !

[Iztok Fister Jr.]

@KoprivcLuka, please install the latest release.

[Luka Koprivc]

The fix works, however i have to warn you, that it appears that used library gpxpy has trouble parsing some files.

[alenrajsp]

@KoprivcLuka can you please upload the troubled GPX files so I can check them out.

[Luka Koprivc]

L_Koprivc_2021_03_23_Brnica.zip

This is an example of an unparsable file which produces above error.

[Iztok Fister Jr.]

@alenrajsp, please check it out.

[Luka Koprivc]

BrokenFiles.zip
I have found several more files which should be valid XML, exported from https://www.gpsvisualizer.com that seem to cause issues

[Iztok Fister Jr.]

@KoprivcLuka, @alenrajsp, any progress regarding this issue?

[alenrajsp]

#120 PR should work with "https://l_koprivc_2021_03_23_brnica.zip/".

[alenrajsp]

PR #121 adds tests for UTF-8 formatting fixed in PR #120. The tests are passing and will no longer happen in the future so this issue can be closed.