Proposal:Changeset tags in osmChange file
Changeset tags in osmChange file | |
---|---|
Proposal status: | Proposed (under way) |
Proposed by: | Kylenz |
Applies to: | editor software |
Definition: | Proposal to allow changeset tags to be included in osmChange (.osc) files |
Draft started: | 2024-01-30 |
RFC start: | 2024-01-30 |
Introduction
OsmChange is an informally defined file format, based on XML. The file extension is .osc
. OSM editors like iD and JOSM supports exporting and/or importing your edits as an OsmChange file.
Proposal
I propose that we allow changeset tags to be included within the OsmChange file format. This proposal does not affect how the OSM API works, and editing software is not obliged to support importing/exporting changeset tags.
Rationale
Using an OsmChange file, it is possible to export your edits from an editor like iD, and import those edits it into another editor like JOSM or Level0.
However, changeset tags are currently lost when you export your edits into another editor.
Tagging
N/A
Examples
An OsmChange file currently has the following structure, with three main sections (<create>
, <modify>
, and <delete>
).
This proposal would introduce a new optional section, called <changeset>
. This section can only contain <tag />
elements. This new section is highlighted in green below:
<osmChange version="0.6" generator="example osm editor">
<create>
...
</create>
<modify>
<node id="1234" changeset="42" version="2" lat="12.1234567" lon="-8.7654321">
<tag k="amenity" v="school" />
</node>
</modify>
<delete>
...
</delete>
+ <changeset>
+ <tag k="imagery_used" v="Bing Maps Aerial" />
+ ...
+ </changeset>
</osmChange>
Note that this proposal only affects the OsmChange file format, not the almost identical format used when uploading your changes to the v0.6 API. When uploading your changes to the API, you should not include the <changeset>
section.
Alternatives
Metadata can already be included in the root tag (<osmChange>
). However, it is not safe to assume that all attributes in the root element are meant to be changeset tags. Therefore, this optional is suboptimal.
Features/Pages affected
External discussions
- Discussion on the forum
- Message sent to the #dev channel in the OSM US Slack
- Message sent to the #dev channel in the OSM Discord
Comments
Please comment on the discussion page.