Opened 11 years ago
Closed 11 years ago
#9510 closed enhancement (wontfix)
Changeset source from source osm file
Reported by: | Polyglot | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 14.01 |
Component: | Core | Version: | |
Keywords: | Cc: |
Description
I'm running josm-latest. Lately it became more convenient to add sources to
changesets. With the very latest, it takes the names of the imagery layers,
instead of the one used the last time.
Maybe this makes sense the very first time JOSM is started, but having to
change it to what I want to put there on every upload gets a bit annoying.
I have several imagery layers, Bing of course, but for the region I map in
mostly we have better imagery available. We also have a WMS with
streetnames, city borders, which I simply called AGIV ALL, since I selected
most of its available layers. That wouldn't mean anything in the source
tag, though.
My imagery layers don't have suitable names anyway and the layer I'm using
as a source, is an .osm layer (one I created with a Python script). Is
there an xml tag one could use to indicate it is 'source' data?
I'm using:
<?xml version='1.0' encoding='UTF-8'?>
<osm version="0.6" upload="no" generator="Python script">
Maybe source="Origin of data"?
Attachments (0)
Change History (4)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
Hi Simon,
I added
<changeset>
<tag k="source" v="My datasource"/>
</changeset>
to my OSM XML file.
This doesn't have an effect on the source tag which gets proposed in the upload dialog though. I'm using version 6581. (It took forever for it to simply display that about screen...)
There might be a misunderstanding: I'm never uploading from that generated OSM file directly, hence the upload=no on it.
I'm selectively copy/pasting information from it to my work layer. (a file with relevant data downloaded with Overpass). So the file generated by the Python script can be seen as a source, like imagery.
Anyway, the first message in this thread was to indicate I don't like it that the source tag on the changeset always gets filled with the names of the imagery layers when the upload dialog is shown. It was better when it showed the latest value the user put there, as it was 2 weeks ago in josm-latest.
Polyglot
comment:3 by , 11 years ago
The pre-filling with current layers has been requested in #9484. It's difficult to have both modes at the same time. ;-)
<tag k="source" v="My datasource"/>
will not work in your setting, but after defining a key use-this-as-source-for-other-layers
(with a conciser name ) the desired effect can be implemented easily (cf. method getLayerInformationForSourceTag
at the bottom of source:trunk/src/org/openstreetmap/josm/gui/MapView.java).
comment:4 by , 11 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Since #9514 is fixed, I assume this feature request is no longer needed.
For local files that are being uploaded, one can set changeset tags, see ticket:6471#comment:4.
But you would like to indicate a changeset
source
in a source OSM file which is to be used as changesetsource
for another layer?