You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: Harry Wood [Submitted to the original trac issue database at 4.05pm, Tuesday, 31st March 2009]
A .osm file saved from JOSM can include elements with action="delete" set on them. It represents a delete which hasn't been 'uploaded' yet. I've just updated the example here to illustrate this http://wiki.openstreetmap.org/wiki/JOSM_file_format
Currently if you run that example through Osmosis it just leaves in the node which has action="delete" set. A more expected behaviour would be to drop the element as osmosis flattens the changes.
The text was updated successfully, but these errors were encountered:
Author: brett[at]bretth.com [Added to the original trac issue at 9.03am, Tuesday, 14th July 2009]
Osmosis is not fully compatible with JOSM files. JOSM allows changes to be represented in the OSM file using the action attribute. Osmosis does not support the action attribute because it uses the alternative OSM Change format (ie. osc files) to achieve the same thing.
I'd rather not add Osmosis support for additional attributes that it doesn't require. It adds additional complexity that must be maintained.
Reporter: Harry Wood
[Submitted to the original trac issue database at 4.05pm, Tuesday, 31st March 2009]
A .osm file saved from JOSM can include elements with action="delete" set on them. It represents a delete which hasn't been 'uploaded' yet. I've just updated the example here to illustrate this http://wiki.openstreetmap.org/wiki/JOSM_file_format
Currently if you run that example through Osmosis it just leaves in the node which has action="delete" set. A more expected behaviour would be to drop the element as osmosis flattens the changes.
The text was updated successfully, but these errors were encountered: