GPX parsing error messages shown in the console aren't shown in the UI

[avarab@…]

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.

[Cobra]

Ticket #4592 has been marked as a duplicate of this ticket.

[Cobra]

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.

[xeen]

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?

[Cobra]

The most common errors I have seen were missing </trk>, </trkseg>, </gpx> tags caused by a crashed application (mostly loggers).
Files with such trivial errors are now loaded anyway so imo it's not a defect anymore.

But I still think it would be nice to offer some more details like the line number where an error was detected if there is some possibility to get this information while trying to load the file. This could be "hidden" behind a "details" button.

Because of that I'm changing this to enhancement.