Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Cannot import GPX file, error description is a bit vague #1411

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 5 comments
Closed

Cannot import GPX file, error description is a bit vague #1411

openstreetmap-trac opened this issue Jul 23, 2021 · 5 comments

Comments

@openstreetmap-trac
Copy link

Reporter: openstreetmap[at]wenix.dk
[Submitted to the original trac issue database at 6.44pm, Tuesday, 16th December 2008]

Hi,

I have troubles importing my GPX file, and the error doesn't really provide any clues for me on how to debug it.

I've attaced the file to this ticket.

Error recieved by mail:

Hi,

It looks like your GPX file

20081216_2121.gpx

with the description

m241/new/20081216_2121.gpx

and no tags.

failed to import. Here's the error:

Issue while inserting job into database

@openstreetmap-trac
Copy link
Author

Author: openstreetmap[at]wenix.dk
[Added to the original trac issue at 9.55pm, Tuesday, 16th December 2008]

The file was too big to attach, so here is a link instead:

http://jrc.wenix.dk/jrc/osm/20081216_2121.gpx.bz2

@openstreetmap-trac
Copy link
Author

Author: tom[at]compton.nu
[Added to the original trac issue at 10.37pm, Tuesday, 16th December 2008]

You've got a bogus point in the trace with lat, lon and elevation of "nan".

@openstreetmap-trac
Copy link
Author

Author: openstreetmap[at]wenix.dk
[Added to the original trac issue at 1.16am, Wednesday, 17th December 2008]

Thanks, it works now.

Is it possible to make the importer specify which line is causing troubles in the future?

@openstreetmap-trac
Copy link
Author

Author: account[at]osm.datendelphin.net
[Added to the original trac issue at 10.46am, Thursday, 12th February 2009]

I had this problem too. I use a bluetooth GPS with my laptop, and in the trace there was a single NaN in an tag. That's very hard to find. I had to search quite a long time to find the reason why my gpx trace wasn't accepted.

It would help a lot and save time if an appropriate error message was returned for this error. (For example line of the error, or the reason: Not a Number (NaN) as value found)
Thanks

@openstreetmap-trac
Copy link
Author

Author: tomhughes
[Added to the original trac issue at 12.55pm, Monday, 1st March 2010]

(In [20236]) Ignore elevations of "nan" when parsing GPX files. Closes #1411.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant