I’m using this Overpass routine to download all golf=tee nodes which are a part of golf=tee ways.
area(id:3600058447,3600058437,3600058446);
way[golf=tee](area);
node(w)[golf=tee](if:count_tags()==1);
(._;>;); out meta;
Within JOSM I delete the golf=tee tag from the node (not delete the node).
When I upload the resulting amendments why is it giving the warning:
Unconnected nodes without physical tags. No tags.
They’re not unconnected, they’re a part of the tee ways.
have you downloaded also ways?
If not, how JOSM is supposed to magically know about them?
If it doesn’t know about them why is it issuing the definitive warning?
If you leave the node without any tags you get this warning " Unconnected nodes without physical tags. No tags." If that node is part of a way you won’t.
Taking it that you remove them tee nodes because the tee boxes have been mapped as an area a well.
JOSM actually has a merge/tag transfer function of node > area and area > area moving the history on the go with the Ctrl+Shft+G keys (Utils2plugin required).
Regrettable not found a function to move the tags from an area to a new node while preserving the chronology/history of the object. Doing that a lot moving the info to a POI. e.g. a building is also tagged with a shop or a fuel station roof has all the station details on it but has to be moved to a centre POI node below.
how JOSM is supposed to magically know that it may not know about them? And if it does not know whether way exist, why it should not issue this warning?
if you do complex operation like partial data fetching it is your responsibility to avoid breaking data
I would strongly recommend to download also ways, that will reduce risk that you will break data AND stop the warning
JOSM is warning you that it is possible that you damage data, you really should fetch also ways to confirm it is not happening
The OSM API does not have the ability to preserve history between objects, individual node/way/relation objects all have their separate change history that cannot be merged or moved between them.
The node → area (=closed way) transfer function might re-use use the node as one of the nodes in the way (and thereby replace one of the existing way nodes in the process), but it cannot transfer the object history. That is immutably linked to the combination of object type + id.
When merging two ways, one of them inevitably needs to be removed, including its history.
Interesting, thanks for that. It remains if for instance a parking node POI in Ctrl+Sht+G’d onto a newly mapped parking outline, the history appears on the outline. Yes, had determined one of the nodes has the history too.
It gets strange if something was mapped in past both as node and area. When selecting both it will merge the node into the polygon, and if there are tags on the former POI node, not on the area, they will be added. Not paid attention who’s history was kept. Just happy the function exists… hate loosing chronology which constantly happens in splitting objects.
(My AI friend had a 4 step solution to include DB xml editing… several bridges too far for me).