You are not logged in.

#1 2019-03-28 14:33:28

FulanoHerminio
Member
Registered: 2019-03-21
Posts: 12

Solved JOSM uploading delete with visible=false

Hi all

Recently we encountered a changeset in which a JOSM upload resulted in apparently deleted relations.
E.g. the red elements in the south of the area in question, rendered in https://overpass-api.de/achavi/?changeset=66937021

Looking closer, it is becomes obvious that rev 1 of all the "red" highlighted elements in question is still valid and in place, as rev 2 with its delete was uploaded with "visible=false".
E.g. https://osmlab.github.io/osm-deep-histo … /667327612

Does anyone know when or how these happen? Just an JOSM>API glitch in which somehow a double delete/undelete action is included in the same API request? (somehow similar to the good old "manual undelete")

Cheers!

Edit: I should add that no delete was intended by the editor uploading the CS with rev2.

Last edited by FulanoHerminio (2019-03-28 16:00:12)

Offline

#2 2019-03-28 14:49:11

GerdP
Member
Registered: 2015-12-18
Posts: 890

Re: Solved JOSM uploading delete with visible=false

Not sure if I understand the problem. All deleted objects have the visible=false flag.
An unintented delete can happen when you e.g. search for building=yes and press Del.

Offline

#3 2019-03-28 14:50:23

FulanoHerminio
Member
Registered: 2019-03-21
Posts: 12

Re: Solved JOSM uploading delete with visible=false

Or only a bug in Overpass with the following issue still open? https://github.com/drolbr/Overpass-API/issues/106

Offline

#4 2019-03-28 14:52:49

FulanoHerminio
Member
Registered: 2019-03-21
Posts: 12

Re: Solved JOSM uploading delete with visible=false

GerdP wrote:

Not sure if I understand the problem.

Sorry added the information on the delete not being intended only in a edit.

Offline

#5 2019-03-28 15:01:12

GerdP
Member
Registered: 2015-12-18
Posts: 890

Re: Solved JOSM uploading delete with visible=false

Please explain what you mean with "elements in question is still valid and in place". The database says that way
https://www.openstreetmap.org/way/667327612 was deleted, so I assume you want to express that the mapper did not intent to remove the way. It is VERY unlikely that JOSM sends a delete to the api without telling the user that this will happen, so I assume the mapper simply did not double check the list of changes before uploading.
The next thing to do is to revert eihter the full changeset or only a part.

Offline

#6 2019-03-28 15:21:20

PHerison
Member
From: Rhein-Main
Registered: 2008-04-04
Posts: 1,512

Re: Solved JOSM uploading delete with visible=false

OSM never remove objects from the database. Deleting an object in OSM means basicaly changing the tag "visible" to false so it won't show up in the map and won't be transmitted if you download data from the database.

Offline

#7 2019-03-28 15:45:57

FulanoHerminio
Member
Registered: 2019-03-21
Posts: 12

Re: Solved JOSM uploading delete with visible=false

SOLVED

All correct, it was my (rather stupid) fault. iD somehow managed to submit a changeset twice and thus created duplicate entries. Obviously a later JOSM edit in the same area filtered the duplicates. Only now noticed there existed 2 identical entries at some point. Will refrain from using iD on bad network link, promised.

Thanks!

Offline

#8 2019-03-28 15:58:18

GerdP
Member
Registered: 2015-12-18
Posts: 890

Re: Solved JOSM uploading delete with visible=false

Please add Solved to the title (edit the first post)

Offline

Board footer

Powered by FluxBB