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.
Author: Matt [Added to the original trac issue at 4.56pm, Sunday, 8th February 2009]
Fixed in r13603. Deletions no longer require anything more than the id, version and changeset. Although according to the osmChange spec it is "traditional" to supply more information, we cannot guarantee that all clients will do so.
Reporter: ivansanchez[at]escomposlinux.org
[Submitted to the original trac issue database at 9.40am, Sunday, 8th February 2009]
I'm using the Rails port rev. 13597 (2008-02-08) and JOSM 1378 in a test environment. I'm not able to delete nodes with JOSM.
How to reproduce: launch JOSM, download a test area, delete some nodes, click "upload".
Tracking down the problem, it seems that either the Rails port 'or' JOSM are not implementing the osmChange standard properly.
Using a network sniffer, this is how the failed diff uploads look:
I don't know whether the "right" implementation of the osmChange format is the one JOSM follows or the one the Rails port follows.
On a related note, JOSM will fail to notify the user that something went wrong during the upload.
The text was updated successfully, but these errors were encountered: