id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
10955	Uploading change-set with DELETE actions results in empty changeset (JOSM guru needed)	brycenesbitt	team	"The following file when uploaded via JOSM results in an empty change set:
{{{
<?xml version='1.0' encoding='UTF-8'?>
<osm version='0.6' generator='Osmsync_CCS'>
<note>test</note>
<node action='delete' id='1409407267' version='2'
user='Bryce C Nesbitt' uid='355242' changeset='9241456'
timestamp='2011-09-07T22:22:05Z'>
</node>
</osm>
}}}

The procedure is:
1) Load ""ccs.osm"" into JOSM.
2) Observe JOSM reports one deleted node.  Press upload, note JOSM says one node will be deleted.
3) Note the changeset number. Check the changeset on the server side, and note it is empty.
4) Note the node (here http://www.openstreetmap.org/node/1409407267 ) is untouched.


The node to be deleted is marked as ""incomplete"" in AbstractPrimative/setIncomplete(), though it is not clear why.  Adding or removing properties from the delete action above seems to make no difference.


------------------------------------------------------------------
My goal is to use JOSM for human review of changes prior to final upload to the osm servers.  The actions ""add"" and ""update"" work fine, only ""delete"" does not.

JOSM is good for this task, but not ideal, due to limited ways to highlight deleted data."	defect	new	normal		Core	latest