Opened 15 years ago
Closed 15 years ago
#4625 closed defect (worksforme)
JOSM does not delete all nodes on upload
Reported by: | skyper | Owned by: | team |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | upload node | Cc: | skyper |
Description
Hi.
Yesterday I have finally uploaded again and it worked. Thanks a lot. After the upload I downloaded the same area again. I found many nodes without connection or tag.
- I did first merge my file with a downloaded layer of the same area.
- Solved all conflicts.
- corrected some errors.
- validator: -> no "unconnected nodes without tag" in downloaded area.
- "update data" , check on server -> conlicts solved
- I am not sure if I explicitly look for "unconnencted nodes without tag" after "update data" but it is a bug anyway.
- upload.
This nodes are either the rest of deleted objects from auto-solving conflicts or somewhere else in the upload routine.
I attach 4 osm-file (1. my; 2. merged; 3. save after upload. 4. fresh download after upload.
Attachments (2)
Change History (5)
by , 15 years ago
Attachment: | josm_bug_4625_merge.osm added |
---|
comment:1 by , 15 years ago
There is only one file.
Please, be more specific in your descriptions. It is hard to figure out what went wrong otherwise. You need to provide exact steps on how to reproduce the error, possibly even create a special test file that only contains the data relevant for the issue. Something like:
- open data.osm
- update from API (or better merge data2.osm into data.osm)
- solve conflice on way yyy
- node zzz should have been deleted but it wasn't
comment:2 by , 15 years ago
Sorry for that file.
I found out about that bug offline, not just after upload. It is not that easy to report bugs offline right now.
Yes, I should have wrote the id --- sorry.
Anyway with all four files, it will work, just investigate the nodes without connenction nor tag on the .._server.osm.
Regards skyper
comment:3 by , 15 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Maybe this was my fault not updating or it is fixed. Did not happen to me again.
4 osms