[josm-dev] Data management
Lester Caine
lester at lsces.co.uk
Sun Mar 2 12:59:45 UTC 2014
Richard Z. wrote:
> On Fri, Feb 28, 2014 at 10:41:16AM +0000, Lester Caine wrote:
>> >There is currently a discussion on the osm talk list about 'Not
>> >attaching polygons to roads'. The discussion has opened up a little,
>> >but as I see it the main problem is that of managing multiple
>> >overlapping ways? Personally I would prefer to enhance 'area' with a
>> >basic structure which uses existing ways to identify an area. This
>> >will allow correctly tagging - for example - the boundaries of a
>> >field or property lot without ending up with three ways all stacked
>> >one on top of another.
> there is also the related problem of admin boundaries tied to waterways.
> If one of the ways tied to such a boundary needs to insert a bridge,
> tunnel or culvert it easily gets very hairy.
>
> https://josm.openstreetmap.de/ticket/9390
I would say that is rather a restricted view of the whole problem :)
While the nodes are automatically merged to a single node element, any tool
which moves a node without knowledge of exactly which higher elements are being
affected should be prevented for uploading that change?
The correct way of processing such a change is perhaps to automatically
disconnect the selected node from the other objects, much as the 'G' shortcut
does? This would dovetail in with what I'm thinking, and providing a means of
selecting a sub-set of the affected elements relating to a set of nodes? One has
to physically select an area to edit it ... otherwise the area is left in it's
old location. Where this falls flat on it's face is the fact that 'relations'
simply use the waterway or other way element as part of the relation. THAT is
the change that my own view is needed to the core API, Although it may be that
'G' could provide a means of creating a duplicate new way element to be retained
by the higher relation while at the same time allowing the modifications to the
original way.
The description for the 'G' shortcut does not seem to cover or document all that
it is capable of! Having been pointed to it off list, it does do a good part of
what I want but is restricted to the nodes of a single entities cross linking
with other objects?
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
More information about the josm-dev
mailing list