You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: post[at]guttormflatabo.com [Submitted to the original trac issue database at 9.05am, Saturday, 11th August 2012]
Yesterday I uploaded two gps traces ([http://www.openstreetmap.org/user/Guttorm%20Flatab%C3%B8/traces/1289236 1289236] and [http://www.openstreetmap.org/user/Guttorm%20Flatab%C3%B8/traces/1289148 1289148]) with 421 and 237 points.
They uploaded fine, but if I try to download them back I get a gpx with two points, and the generated thumbnail for the traces is also a line between two points. [https://dl.dropbox.com/u/234927/screenshots/proper%20trace%20in%20potlatch.png In potlatch, though, the trace will load fine] (trace shown is 1289236).
I uploaded the traces as private, but have made them identifiable to easy the bug hunt.
Notice that both traces have the same trace thumbnail, but I am positive that they should be different traces (and so the point count seem to indicate too).
There are problems with [http://www.openstreetmap.org/user/Guttorm%20Flatab%C3%B8/traces/1286624 1286624] and [http://www.openstreetmap.org/user/Guttorm%20Flatab%C3%B8/traces/1286535 1286535] also. The downloads are different (and perhaps valid, but probably not), but the thumbnails are identical.
The text was updated successfully, but these errors were encountered:
Author: TomH [Added to the original trac issue at 10.23am, Saturday, 11th August 2012]
I agree that the thumbnails look wrong, but the downloads of the traces look fine to me, which is what I would expect as it is just returning the original file.
When you say "download them back" are you actually talking about downloading GPS data in that area with the tracepoints call rather than downloading the raw trace?
Author: post[at]guttormflatabo.com [Added to the original trac issue at 9.37pm, Saturday, 11th August 2012]
Sorry to have wasted your time.
It looks like the gpx is somehow corrupted which makes all software display the second last point as a point with lat and lon 0.0. I cannot find this point in the gpx, and can't see any obvious syntax errors at the end of the file, but I'm no gpx expert either.
Anyway, the thumbnail is the way it is because of the point, and they look identical because they cover the same area and both have this line to lat/lon 0.0. The download is as it should be, it just looks like there are only two points in it when you open it in JOSM and don't zoom in.
So all is good on OSM's side, but something is wrong with GPS Logger or the combination of GPS Logger and GPS that I have on my phone.
Reporter: post[at]guttormflatabo.com
[Submitted to the original trac issue database at 9.05am, Saturday, 11th August 2012]
Yesterday I uploaded two gps traces ([http://www.openstreetmap.org/user/Guttorm%20Flatab%C3%B8/traces/1289236 1289236] and [http://www.openstreetmap.org/user/Guttorm%20Flatab%C3%B8/traces/1289148 1289148]) with 421 and 237 points.
They uploaded fine, but if I try to download them back I get a gpx with two points, and the generated thumbnail for the traces is also a line between two points. [https://dl.dropbox.com/u/234927/screenshots/proper%20trace%20in%20potlatch.png In potlatch, though, the trace will load fine] (trace shown is 1289236).
I uploaded the traces as private, but have made them identifiable to easy the bug hunt.
Notice that both traces have the same trace thumbnail, but I am positive that they should be different traces (and so the point count seem to indicate too).
There are problems with [http://www.openstreetmap.org/user/Guttorm%20Flatab%C3%B8/traces/1286624 1286624] and [http://www.openstreetmap.org/user/Guttorm%20Flatab%C3%B8/traces/1286535 1286535] also. The downloads are different (and perhaps valid, but probably not), but the thumbnails are identical.
The text was updated successfully, but these errors were encountered: