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: p.weber[at]ucl.ac.uk [Submitted to the original trac issue database at 8.10pm, Wednesday, 1st February 2012]
Ran a mapping party with newbie users.
One user was recording GPX tracks with OSM Tracker for Android. WHen it came to upload the tracks to OSM, the user managed to select some jpg's instead of the GPX files!
Unfortunately, OSM didnt complain that it was the wrong filetype at upload, but only at the processing stage failed with a generic XML Parser error.
Could you check on upload for file extensions, or if this is not doable, have a more descriptive error message on processing than a generic XML parser error ?
The text was updated successfully, but these errors were encountered:
Author: TomH [Added to the original trac issue at 9.41pm, Wednesday, 1st February 2012]
Unfortunately I don't think the extension would be a reliable way of determining whether it was likely to be a valid GPS trace or not, especially given the wide variety of wrapper formats (gz. bz2, zip, etc) that we support.
Reporter: p.weber[at]ucl.ac.uk
[Submitted to the original trac issue database at 8.10pm, Wednesday, 1st February 2012]
Ran a mapping party with newbie users.
One user was recording GPX tracks with OSM Tracker for Android. WHen it came to upload the tracks to OSM, the user managed to select some jpg's instead of the GPX files!
Unfortunately, OSM didnt complain that it was the wrong filetype at upload, but only at the processing stage failed with a generic XML Parser error.
Could you check on upload for file extensions, or if this is not doable, have a more descriptive error message on processing than a generic XML parser error ?
The text was updated successfully, but these errors were encountered: