Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#12734 closed defect (fixed)

Issue with the data update option in file menu

Reported by: Jothirnadh Owned by: Jothirnadh
Priority: normal Milestone: 16.04
Component: Core Version: tested
Keywords: data_update_error_report Cc:


What steps will reproduce the problem?

  1. Update the existing data in my system with the data from the OpenStreetMap server.

What is the expected result?

When I load the data into JOSM and click on update data option in file menu, JOSM should update the existing data with the updated data in OpenStreetMap server.

What happens instead?

Instead of updating the data, JOSM is throwing me the below an error.

![screen shot 2016-04-07 at 11 30 52 am](

I am not sure why this error is popping up. Please help me in solving this error.

Please provide any additional information below. Attach a screenshot if possible.

![screen shot 2016-04-07 at 11 30 52 am](

Screen shot of the error popup

Dropbox link of the data I'm using-

Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2016-03-13 01:17:21 +0100 (Sun, 13 Mar 2016)
Build-Date:2016-03-13 02:35:00
Relative:URL: ^/trunk

Identification: JOSM/1.5 (9979 en) Mac OS X 10.11.3
Memory Usage: 526 MB / 910 MB (159 MB allocated, but free)
Java version: 1.8.0_77-b03, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
VM arguments: [ Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/lib/security/javaws.policy, -DtrustProxy=true, -Djnlpx.home=<java.home>/bin,, -Djnlpx.origFilenameArg=/Users/Jothi/Library/Application Support/Oracle/Java/Deployment/cache/6.0/56/1ee8cfb8-518fbb33, -Djnlpx.remove=false, -Dsun.awt.warmup=true, -Djava.util.Arrays.useLegacyMergeSort=true,, -Dmacosx.jnlpx.dock.icon=/Users/Jothi/Library/Application Support/Oracle/Java/Deployment/cache/6.0/16/47ee53d0-4200328a.icns, -Djnlp.application.href= , -Djnlpx.jvm="/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java", -Djnlpx.vmargs=LURqYXZhLnV0aWwuQXJyYXlzLnVzZUxlZ2FjeU1lcmdlU29ydD10cnVlAC1Eam5scC5hcHBsaWNhdGlvbi5ocmVmPWh0dHBzOi8vam9zbS5vcGVuc3RyZWV0bWFwLmRlL2Rvd25sb2FkL2pvc20uam5scCAA]
Dataset consistency test: No problems found

- BuildingGeneralization (UNKNOWN)
- FastDraw (31895)
- ImportImagePlugin (31772)
- Mapillary (32040)
- PicLayer (31895)
- apache-commons (31895)
- apache-http (31895)
- buildings_tools (31895)
- changesetID (UNKNOWN)
- continuosDownload (1446070193)
- editgpx (31772)
- ejml (31895)
- geotools (31895)
- jna (31877)
- josm-config (1449603193)
- jts (31772)
- log4j (31895)
- measurement (31895)
- opendata (32071)
- reltoolbox (31895)
- scripting (30722)
- todo (29154)
- turnlanes (31772)
- turnrestrictions (31895)
- undelete (31895)
- utilsplugin2 (32099)
- walkingpapers (31603)
- waydownloader (31772)
- wikipedia (32058)

Last errors/warnings:
- W: Failed to parse Mappaint styles from ''. Error was: Reached end of file while parsing
- E: org.openstreetmap.josm.gui.mappaint.mapcss.parsergen.ParseException: Reached end of file while parsing
- W: Initializing map style completed in 3 ms (2 errors, 0 warnings)
- W: Failed to add resource://data/validator/power.mapcss to tag checker
- W: Failed to open input stream for resource 'resource://data/validator/power.mapcss'

Attachments (0)

Change History (5)

comment:1 Changed 4 years ago by anonymous

The above screenshot is

comment:2 Changed 4 years ago by Don-vip

Priority: blockernormal

comment:3 Changed 4 years ago by Don-vip

Milestone: 16.04

comment:4 Changed 4 years ago by Don-vip

Resolution: fixed
Status: newclosed

In 10135/josm:

fix #12734 - display less intrusive warning message when an updated area contains no data

comment:5 Changed 4 years ago by Don-vip

Update works as expected. Only the error message was too intrusive. See #12583 for related display bug.

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain Jothirnadh.
as The resolution will be set.
The resolution will be deleted.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.