Opened 3 months ago
#23972 new defect
Source is not Displayed in Pop-up Window when Importing Data Manually via the HOT Tasking Manager
Reported by: | Gregory | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | |
Keywords: | Import Remote Manual Confirm Data Source HOT | Cc: |
Description
What steps will reproduce the problem?
Reproduction Instructions;
1.Log in to HOT TM, or the Staging Site.
2.Find a project (on which you are permitted to map or validate).
3.Run JOSM and allow it to load.
4.Ensure that manual confirmation of remote control actions is enabled, via JOSM remote preferences.
5.Select a task(s) and press to begin mapping or validating, pop-ups should now begin appearing in JOSM asking for your confirmation to import data.
6.One by one, accept the requests by clicking the “yes once” button on all of the pop-ups.
If the yes always button is used on task data requests, then it will alter the behaviour, and JOSM will have to be reloaded to load task data individually.
What is the expected result?
The import request pop-up clearly shows the source of the data and information which can be used to identify requests e.g. when opening a changeset in JOSM via OSMCha [1].
The full request url does not need to be displayed (like when importing bing aerial imagery [4]), but the source (in this case "Tasking Manager Backend API") and information like the project ID, taskId, boundary, or imagery should be stated.
What happens instead?
The import request pop-up does not explicitly state the source in the case of task boundaries [2] and does not sate the API being used to download data within a bounding box [3].
Please provide any additional information below. Attach a screenshot if possible.
Making the source clear will make it possible for users to identify requests, track and manage data imports.
The co-ordination of projects on the HOT TM is project and task oriented, so it would be useful to know the project and task ID the data import request is for. This task ID could perhaps be used to name the OSM Data layer(s) when importing into new layers (similar to the way that boundary layers are automatically named currently).
The documentation of the HOT TM API can be found here https://tasks.hotosm.org/api-docs/
Revision:19228 Is-Local-Build:true Identification: JOSM/1.5 (19228 SVN en_GB) Windows 10 64-Bit OS Build number: Windows 10 Home 22H2 (19045) Memory Usage: 880 MB / 6080 MB (531 MB allocated, but free) Java version: 22.0.2+9, Azul Systems, Inc., OpenJDK 64-Bit Server VM System property file.encoding: UTF-8 System property sun.jnu.encoding: Cp1252 Locale info: en_GB Numbers with default locale: 1234567890 -> 1234567890 VM arguments: [-Djpackage.app-version=1.5.19228, -XX:MaxRAMPercentage=75.0, --add-modules=java.scripting,java.sql,javafx.controls,javafx.media,javafx.swing,javafx.web, --add-exports=java.base/sun.security.action=ALL-UNNAMED, --add-exports=java.desktop/com.sun.imageio.plugins.jpeg=ALL-UNNAMED, --add-exports=java.desktop/com.sun.imageio.spi=ALL-UNNAMED, --add-opens=java.base/java.lang=ALL-UNNAMED, --add-opens=java.base/java.nio=ALL-UNNAMED, --add-opens=java.base/jdk.internal.loader=ALL-UNNAMED, --add-opens=java.base/jdk.internal.ref=ALL-UNNAMED, --add-opens=java.desktop/javax.imageio.spi=ALL-UNNAMED, --add-opens=java.desktop/javax.swing.text.html=ALL-UNNAMED, --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED, -Djpackage.app-path=%UserProfile%\AppData\Local\JOSM\JOSM.exe] Dataset consistency test: No problems found Last errors/warnings: - 02059.876 E: at org.openstreetmap.josm.tools.ListenerList.fireEvent(ListenerList.java:154) - 02059.876 E: at org.openstreetmap.josm.data.osm.DataSet.doSelectionChange(DataSet.java:833) - 02059.876 E: at org.openstreetmap.josm.data.osm.DataSet.addSelected(DataSet.java:779) - 02059.876 E: at org.openstreetmap.josm.data.osm.DataSet.addSelected(DataSet.java:770) - 02059.877 E: at org.openstreetmap.josm.plugins.mapathoner.SelectNonOrthogonalBuildingAction.lambda$actionPerformed$0(SelectNonOrthogonalBuildingAction.java:116) - 02059.877 E: at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) - 02059.877 E: at java.base/java.util.concurrent.FutureTask.run(Unknown Source) - 02059.877 E: at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) - 02059.877 E: at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) - 02059.877 E: at java.base/java.lang.Thread.run(Unknown Source)
Screenshots of the current import process to be used with the numbers enclosed by square brackets