Opened 3 years ago
Closed 3 years ago
#22015 closed defect (othersoftware)
OSM data layer missing
Reported by: | TeBaMa | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | template_report | Cc: |
Description
What steps will reproduce the problem?
OSM data layer is no longer loaded in JOSM when I activate a task in the tasking manager
URL:https://josm.openstreetmap.de/svn/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2022-04-04 22:26:00 +0200 (Mon, 04 Apr 2022) Build-Date:2022-04-05 01:30:55 Revision:18427 Relative:URL: ^/trunk Identification: JOSM/1.5 (18427 nl) Windows 10 64-Bit OS Build number: Windows 10 Pro 2009 (19043) Memory Usage: 664 MB / 1813 MB (412 MB allocated, but free) Java version: 1.8.0_261-b12, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM Look and Feel: com.sun.java.swing.plaf.windows.WindowsLookAndFeel Screen: \Display0 1920×1200 (scaling 1.00×1.00) Maximum Screen Size: 1920×1200 Best cursor sizes: 16×16→32×32, 32×32→32×32 System property file.encoding: Cp1252 System property sun.jnu.encoding: Cp1252 Locale info: nl_NL Numbers with default locale: 1234567890 -> 1234567890 Dataset consistency test: No problems found Plugins: + BuildingGeneralization (36) + CADTools (1008) + FastDraw (35893) + Mapillary (2.0.0-beta.6-3-g192a88c) + ShapeTools (1250) + apache-commons (35924) + apache-http (35924) + buildings_tools (35951) + changeset-viewer (v0.0.4) + colorscheme (35893) + fieldpapers (v0.5.0) + imagery_offset_db (35893) + jna (35924) + mapwithai (1.9.10) + measurement (35893) + merge-overlap (35893) + scripting (30798) + todo (30306) + turnrestrictions (35893) + undelete (35893) + utilsplugin2 (35951) Tagging presets: + https://josm.openstreetmap.de/josmfile?page=Presets/NewTags&zip=1 Map paint styles: - https://josm.openstreetmap.de/josmfile?page=Styles/MapWithAI&zip=1 Last errors/warnings: - 00010.442 W: Cannot lock cache directory. Will not use disk cache - 00011.675 E: Lokaliseren van afbeelding 'MapWithAI' mislukt - 00013.179 W: Cannot start IPv4 remotecontrol server on port 8111: Address already in use: JVM_Bind - 00013.187 W: Cannot start IPv6 remotecontrol server on port 8111: Address already in use: JVM_Bind
Attachments (5)
Change History (18)
by , 3 years ago
Attachment: | DataLayer.pdf added |
---|
comment:1 by , 3 years ago
by , 3 years ago
Attachment: | DataLayer1.pdf added |
---|
by , 3 years ago
Attachment: | ErrorReport.docx added |
---|
comment:2 by , 3 years ago
I installed the latest version 18427.
The problem remains the same : no OSM data layer.
See a new print screen DataLayer1 and an error report.
comment:3 by , 3 years ago
To be honest, I don't understand what's missing. I've never used a tasking manager with JOSM, so I don't know what you can expect.
Did you try to reboot?
by , 3 years ago
Attachment: | Screen.JPG added |
---|
comment:4 by , 3 years ago
See the 'screen.jpg' image.
In the upper corner at the right we have the window 'lagen' (= layers) with all open layers.
When a task is activated, normaly we have also a DATA-layer of OSM which include all features mapped previously for this task. The boundary-layer (2) exists and is mapped (the red square), but the data-layer is missing since yesterday here. There are no existing features mapped.
comment:5 by , 3 years ago
I see different java versions in the two reports. Does that mean there are two different machines with the same problem? Does it still work anywhere?
by , 3 years ago
Attachment: | Screen1.JPG added |
---|
comment:7 by , 3 years ago
I installed JOSM from another site in the hope this could have solve the problem. Maybe that's the reason of the different java versions. I am not an IT specialist.
I will also send a mail to the HOT Technical support.
See 'screen1.jpg', an image of an earlier task with the OSM-layer (2) of the task in the upper right corner and the existing features (roads, buildings ...) mapped. The boundry layer didn't exist yet at that moment.
comment:8 by , 3 years ago
I have the same problem. I also use another TaskingManager tasks.openstreetmap.es/ to import buildings in Spain and it works fine there.
I have marked in the preferences of the remote that it asks me for permission for each action. With the Spanish taskingManager, when it asks me for permission, I see that it wants to access the url that has the data to import from github. When I do the same thing with the tasking manager the space where the address to access should be is blank.
Occasionally it has worked well for me.
I have tried with different browsers and the same thing happens with all
comment:9 by , 3 years ago
I found out that this problem was reported 2 days ago to the hotosm/tasking-manager as a [BUG] "JOSM doesn't load OSM data when attempting to map a task #5097"
follow-up: 11 comment:10 by , 3 years ago
OK, so my understanding is that this is not a problem in JOSM but in the tasking manager?
comment:11 by , 3 years ago
Replying to GerdP:
OK, so my understanding is that this is not a problem in JOSM but in the tasking manager?
Could be both. :-)
comment:12 by , 3 years ago
I did a bit of investigation into this, and I'm inclined to think it is the TM. I've got an older copy of TM4 running, and that worked. The version of the TM running on tasks.hotosm.org did not work.
Copy-paste from HOT Slack:
I suspect this is a Tasking Manager issue. It worked with an older version of TM4 (I'd have to check the git tag), but not with the current version on tasks.hotosm.org. hotosm.org had a single call to 127.0.0.1 which loads the boundaries. The older version of TM4 had 5 calls to 127.0.0.1, which (1) checked the JOSM version, (2) created a new layer, (3) loaded the boundary into the new layer, (4) created a new layer for OSM data, and (5) loaded the osm data into the layer.
This is odd, since the code for TM remote control doesn't appear to have changed (see https://github.com/hotosm/tasking-manager/blob/develop/frontend/src/utils/openEditor.js ).
I'm looking into doing a git bisect
on the TM to see where things broke. But I'm thinking that it is due to the TM triggering a page reload when you use the Reload editor
action. This is supported by only some calls to JOSM remote control being made (the first ones that the TM has coded), but not the later calls.
comment:13 by , 3 years ago
Resolution: | → othersoftware |
---|---|
Status: | new → closed |
Quick update: It looks like the problem has been fixed in https://github.com/hotosm/tasking-manager/pull/5096 .
Looking at the "Last errors/warning" section in the report:
Seems you have another instance of JOSM running?