Opened 11 years ago

Closed 9 years ago

#1411 closed defect (fixed)

Cannot import GPX file, error description is a bit vague

Reported by: openstreetmap@… Owned by: dsilvers@…
Priority: trivial Milestone:
Component: website Version:
Keywords: gpx import Cc:

Description

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

Change History (5)

comment:1 Changed 11 years ago by openstreetmap@…

Priority: majortrivial

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

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

comment:2 Changed 11 years ago by Tom Hughes

Owner: changed from Tom Hughes to dsilvers@…

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

comment:3 Changed 11 years ago by openstreetmap@…

Summary: Cannot import GPX file, error description a bit vagueCannot import GPX file, error description is a bit vague

Thanks, it works now.

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

comment:4 Changed 10 years ago by account@…

I had this problem too. I use a bluetooth GPS with my laptop, and in the trace there was a single NaN in an <ele> 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

comment:5 Changed 9 years ago by tomhughes

Resolution: fixed
Status: newclosed

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

Note: See TracTickets for help on using tickets.