#11310 closed enhancement (fixed)
Support setting changeset tags during /import call
Reported by: | StefanB | Owned by: | simon04 |
---|---|---|---|
Priority: | normal | Milestone: | 20.05 |
Component: | Core remotecontrol | Version: | |
Keywords: | changeset upload | Cc: |
Description
It would make much sense to specify source tag for the changeset during /import remote control call
I know it can be set on load_and_zoom, but that requires exact bbox as a parameter and calling that would prevent users from inspecting the imported data before it is merged with existing data downloaded via API.
It can also support setting changeset comment, but source tag is the most crucial one for imports.
Attachments (1)
Change History (18)
comment:1 Changed 8 years ago by
comment:2 Changed 8 years ago by
Since the data is loaded from an OSM file, the changeset comment could be specified there:
<osm version='0.6' upload='true' generator='JOSM'> <changeset><tag k="comment" v="This will show up when uploading"/></changeset> <!-- ... --> </osm>
comment:3 Changed 8 years ago by
Thanks for a nice hint, but we're importing zipped shapefiles, not .osm xml files.
comment:4 Changed 8 years ago by
We could in theory use OpenData plugin to convert all the shapefiles to OSM xml format in the data preparation phase, but I don't know yet how to do that in a script.
comment:5 Changed 8 years ago by
Would it be possible to use zip file comment or some ShapeFile comment (if it exists at all, not sure)? Or a text file within in zip? Extra import parameter would be easiest, i guess.
comment:6 Changed 4 years ago by
The recently closed #18038 "[PATCH] Arbitrary changeset tags should be able to be added via remote control" gave me some hope, but unfortunately the changeset_tags
parameter is only applicable for /load_and_zoom
command.
Our import project (https://raba.openstreetmap.si/) could really use the changeset_source
(and optionally changeset_comment
) or just a generic changeset_tags
also on the /import
remote control API command to specify the source of the import.
The changeset_source
parameter could also be required for all /import
calls, as any import should specify the source!
Changed 4 years ago by
Attachment: | 11310.patch added |
---|
Initial quick and dirty patch. Needs deduplication of code (for changeset_tags
) and parseUrlTagsToKeyValues
should probably be moved to RequestHandler
.
comment:7 Changed 3 years ago by
Keywords: | changeset upload added |
---|---|
Milestone: | → 20.03 |
Owner: | changed from team to Don-vip |
Status: | new → assigned |
comment:8 Changed 3 years ago by
Milestone: | 20.03 → 20.04 |
---|
comment:9 Changed 3 years ago by
Owner: | changed from Don-vip to simon04 |
---|---|
Status: | assigned → new |
comment:11 Changed 3 years ago by
I'm pretty sure there is a wiki page where changes to remote control should be documented.
comment:12 Changed 3 years ago by
comment:13 Changed 3 years ago by
Thanks. Done via Help/RemoteControlCommands?action=diff&version=13
comment:14 Changed 3 years ago by
Great, thanks!
Can you please add this also to the:
- import
- load_data
- open_file
...and possibly other calls?
Or just make a separate call just for that.
It is needed there to set source tags and meaningful comments.
comment:15 Changed 3 years ago by
I'm working on a refactoring of remote control parameters handling to share parameters between different handlers.
comment:16 Changed 3 years ago by
That would be great, and would simplify the API considerably. Thanks!
Ooops, probably a duplicate of #11045. Didn't remember mentioning this in a comment there.