This is a static archive of our old OpenStreetMap Help Site. Please post any new questions and answers at community.osm.org.

Why does a GPX import report “Issue while inserting job into database”?

Hello. I want to upload a GPX file, but I get the error "Issue while inserting job into database". Not very descriptive IMO. There's nothing about this in the documentation. What should I do? The file is exported from Sports Tracker 4.12 for Nokia.

import gpx error

asked 27 Apr '11, 19:32

haael
152●4●4●9
accept rate: 0%

edited 28 Apr '11, 21:31

TomH ♦♦
3.3k●8●39●43

Did you receive an email from OSM server about success or failure of your GPX upload?

You can also check https://wiki.openstreetmap.org/wiki/Platform_Status

(27 Apr '11, 19:41) stephan75

I have successfully uploaded lots of GPX traces but one bounced the other day because it had a dash or back slash in the name. I removed it and the file uploaded ok. but It took me a few minutes to guess the problem

(27 Apr '11, 21:31) andy mackey

2 Answers:

If you open your GPX file with a text editor it should consist of a few lines of name and creator informtion followed by a large list on lats and longs each with date and time. if it does not have these time stamps it will not upload. you can see a good trace by down loading one from the traces list and then opening with a text editor.

answered 27 Apr '11, 23:16

andy mackey
13.2k●87●143●285
accept rate: 4%

I have reinstalled SportsTracker and now it works. It seems that the timestamps were the problem. Both good and bad GPX files had timestamps, but the latter had only zeroes in them.

The good file:

<trkpt lat="51.140517" lon="16.890212">
<ele>157.5</ele>
<desc>Speed 2.7 km/h Distance 0.00 km</desc>
<time>2011-04-28T20:44:54.02</time>
<name>2</name>
<sym>Dot</sym>
</trkpt>

The bad file:

<trkpt lat="51.121407" lon="16.879287">
<ele>161.0</ele>
<desc>Speed 2.3 km/h Distance 0.00 km</desc>
<time>0-01-01T00:00:00.00</time>
<name>2</name>
<sym>Dot</sym>
</trkpt>

So much walking for nothing, so sad :). The web interface should return a little boit more descriptive error message, though.

Thanks for help for all.

(28 Apr '11, 21:03) haael

I've checked the logs, and those dodgy timestamps were indeed the problem because the database rejected them as invalid.

(28 Apr '11, 21:30) TomH ♦♦

A quick web search finds eactly three hits:

In the previous two cases it appears that dodgy data** was the problem, so it may be in your case as well. Perhaps you could check that or upload it somewhere else so that someone could have a look?

** specifically NaN or nan (i.e. "not a number") in fields that should have been numeric

answered 27 Apr '11, 22:21

SomeoneElse ♦
36.9k●71●370●866
accept rate: 16%