Opened 16 years ago
Last modified 13 years ago
#3417 new enhancement
GPX parsing error messages shown in the console aren't shown in the UI — at Version 3
| Reported by: | Owned by: | team | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | latest |
| Keywords: | gpx | Cc: | xeen, Cobra |
Description (last modified by )
When opening an invalid GPX file I might get something like this in the console:
org.xml.sax.SAXParseException: The element type "gpx" must be terminated by the matching end-tag "</gpx>"
However the UI only says that the file couldn't be opened due to a parsing error.
It would be helpful to have more specific error messages in the UI.
Change History (3)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
The error message and the line in which this error occured are really interesting in most cases. Most errors are simply caused by files not being finished or otherwise corrupted by crashed devices or applications. These errors can be fixed very easily - if you know where you have to look for oddities.
Bug is still existing in today's latest.
comment:3 by , 14 years ago
| Cc: | added |
|---|---|
| Description: | modified (diff) |
I checked today, and JOSM parses everything correctly until the file becomes malformed. It doesn’t print any error message to the console anymore and I don’t see how it will be helpful to print an error message this complicated. Most of the GPX files are created by an application, so if the file is broken your chances to fix it manually are very slim. The most likely solution would be to try to download or export the GPX again; and for this the “broken” message seems fine.
If you agree with me here, please close the ticket. Otherwise, can you explain?
Ticket #4592 has been marked as a duplicate of this ticket.