#19932 closed defect (duplicate)
wrong with the load of one of gpx file
Reported by: | anonymous | Owned by: | anonymous |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | tested |
Keywords: | template_report | Cc: | simon04 |
Description
What steps will reproduce the problem?
- read one of gpx files
What is the expected result?
What happens instead?
Please provide any additional information below. Attach a screenshot if possible.
URL:https://josm.openstreetmap.de/svn/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2020-10-03 13:42:38 +0200 (Sat, 03 Oct 2020) Build-Date:2020-10-04 01:30:47 Revision:17084 Relative:URL: ^/trunk Identification: JOSM/1.5 (17084 zh_CN) Windows 10 64-Bit OS Build number: Windows 10 Home China 1903 (18362) Memory Usage: 247 MB / 989 MB (151 MB allocated, but free) Java version: 1.8.0_251-b08, Oracle Corporation, Java HotSpot(TM) Client VM Look and Feel: com.sun.java.swing.plaf.windows.WindowsLookAndFeel Screen: \Display0 1920x1080 (scaling 1.0x1.0) Maximum Screen Size: 1920x1080 Best cursor sizes: 16x16 -> 32x32, 32x32 -> 32x32 Plugins: + imagery_offset_db (35405) + turnrestrictions (35577) Last errors/warnings: - 00012.035 W: java.nio.file.FileSystemException: %UserProfile%\AppData\Local\Temp\josm_exec_powershell_4931276397840899449.txt: 另一个程序正在使用此文件,进程无法访问。 - 00012.036 W: Unable to request certificate of https://www.certigna.fr - 00020.965 W: java.nio.file.FileSystemException: %UserProfile%\AppData\Local\Temp\josm_exec_powershell_5743641272318353549.txt: 另一个程序正在使用此文件,进程无法访问。 - 00020.966 W: Unable to request certificate of https://grca.nat.gov.tw - 00026.053 W: java.nio.file.FileSystemException: %UserProfile%\AppData\Local\Temp\josm_exec_powershell_4206478707689965742.txt: 另一个程序正在使用此文件,进程无法访问。 - 00026.054 W: Unable to request certificate of https://grca.nat.gov.tw - 00027.621 W: 更新插件 - 您已经更新了 JOSM 软件。 为了避免问题也应该更新插件。 是否立即更新? - 00157.648 E: Region [TMS_BLOCK_v2] : Problem loading keys for file TMS_BLOCK_v2 - 00178.099 E: Handled by bug report queue: java.time.DateTimeException: Invalid value for SecondOfMinute (valid values 0 - 59): 60 - 00463.942 E: Handled by bug report queue: java.time.DateTimeException: Invalid value for SecondOfMinute (valid values 0 - 59): 60 === REPORTED CRASH DATA === BugReportExceptionHandler#handleException: No data collected. Warning issued by: BugReportExceptionHandler#handleException === STACK TRACE === Thread: main-worker-0 (61) of main java.time.DateTimeException: Invalid value for SecondOfMinute (valid values 0 - 59): 60 at java.time.temporal.ValueRange.checkValidValue(Unknown Source) at java.time.temporal.ChronoField.checkValidValue(Unknown Source) at java.time.LocalTime.of(Unknown Source) at java.time.LocalDateTime.of(Unknown Source) at java.time.ZonedDateTime.of(Unknown Source) at org.openstreetmap.josm.tools.date.DateUtils.tsFromString(DateUtils.java:114) at org.openstreetmap.josm.io.GpxReader$Parser.endElement(GpxReader.java:478) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(Unknown Source) at org.openstreetmap.josm.tools.XmlUtils.parseSafeSAX(XmlUtils.java:123) at org.openstreetmap.josm.io.GpxReader.parse(GpxReader.java:642) at org.openstreetmap.josm.gui.io.importexport.GpxImporter.importData(GpxImporter.java:125) at org.openstreetmap.josm.gui.io.importexport.FileImporter.importDataHandleExceptions(FileImporter.java:98) at org.openstreetmap.josm.actions.OpenFileAction$OpenFileTask.importData(OpenFileAction.java:370) at org.openstreetmap.josm.actions.OpenFileAction$OpenFileTask.realRun(OpenFileAction.java:320) at org.openstreetmap.josm.gui.PleaseWaitRunnable.doRealRun(PleaseWaitRunnable.java:94) at org.openstreetmap.josm.gui.PleaseWaitRunnable.run(PleaseWaitRunnable.java:142) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
Attachments (0)
Change History (7)
comment:1 by , 4 years ago
Owner: | changed from | to
---|---|
Status: | new → needinfo |
Version: | → tested |
follow-up: 4 comment:3 by , 4 years ago
Resolution: | → duplicate |
---|---|
Status: | needinfo → closed |
comment:4 by , 4 years ago
follow-up: 6 comment:5 by , 4 years ago
The exception is happening immediately after JOSM has read the timestamp string from the GPX file. I wonder what kind of rounding issue in the GPX generating software would lead to a SecondOfMinute=60… Having an example file would help to resolve this mystery. :-)
follow-up: 7 comment:6 by , 4 years ago
Replying to simon04:
The exception is happening immediately after JOSM has read the timestamp string from the GPX file. I wonder what kind of rounding issue in the GPX generating software would lead to a SecondOfMinute=60… Having an example file would help to resolve this mystery. :-)
Seen the same lately with other data at work. Probably they had timestamps like 2020-09-13 13:12:59.675 that get 2020-09-13 13:12:60 when output as int without proper care of the time handling. Interestingly our dataset also contained 24:00:00 (probably for same reason).
Never underestimate lazy programmers.
comment:7 by , 4 years ago
I guess the same software also generated this:
Replying to #19914:
Invalid value for MonthOfYear (valid values 1 - 12): 17434
so there seems to be something a bit more broken than just rounding in this software :)
The file seems to have an invalid format as seconds are only allowed between 0 and 59 but your file contains fields with 60.
How was this file generated?
Is it possible to attach it to the ticket, thanks ?