Opened 7 years ago

Last modified 7 years ago

#16710 new defect

Move node to nearest way more difficult at high zoom — at Version 6

Reported by: A_Pirard Owned by: team
Priority: normal Milestone:
Component: Core Version:
Keywords: distance Cc:

Description (last modified by Don-vip)

At high zoom, function "Move node to nearest way" requires that the node be excessively near the way.
And BTW, function "Merge nodes" has the same excessive proximity requirement; maybe same problem.
Both should work at even a large distance if there is no confusion with another way or node.

May I be off topic very shortly with asking a technical advice?
Would I sound idiot by suggesting that a tool could invoke another tool?
Is it possible?
Best is to explain the specifics if you don't tell everybody.
It's about AreaSelector.
I would like it to invoke Replace Geometry of a being replaced object.
Only problem I think is returning to AS environment, but AS can do it.

Change History (8)

comment:1 by A_Pirard, 7 years ago

Update: I'm not sure about "since 14178" after all.
What I'm sure of is that when I use AreaSelect to create a new house, that AS should put some nodes on (merge with) ways or nodes of the next house but does not, then I must drag those nodes extremely near these to be able to use N or M.
Hence the request is to do it over "a large distance".

TIA.

comment:2 by Don-vip, 7 years ago

Owner: changed from team to A_Pirard
Status: newneedinfo

Please provide a sample file showing the problem. Thanks.

comment:3 by A_Pirard, 7 years ago

Hi, thanks,

The layer is BE SPW PICC.
It's about correcting AreaSelector imprecision.
Hence, I'm working at high zooms.
This is speed tagging (1 house/~10 sec complete if no touch up is needed).
I just noticed that the inconvenience occurs above some zoom level.
In N25.OSM, the 2 north corners of south house cannot be N'ed to the way at zoom ≥25.
In M24.OSM the NW corner of south house cannot be M'ed to nearby node at zoom ≥24.
Unless time is spent to select both nodes, of course.
So, either the nodes have to be moved or zoom must constantly change: time loss.
Maybe also other node "gluing" functions that I don't use often.
Not sure why I feel this as a new inconvenience.
A higher maximum distance distance would be welcome. Maybe it was before.
Or depending on zoom.
TIA.

by A_Pirard, 7 years ago

Attachment: M24.osm added

by A_Pirard, 7 years ago

Attachment: N 25.osm added

comment:4 by A_Pirard, 7 years ago

Description: modified (diff)
Summary: N = Move node to nearest way became too stringentN = Move node to nearest way more difficult at high zoom

comment:5 by Don-vip, 7 years ago

Owner: changed from A_Pirard to team
Status: needinfonew

comment:6 by Don-vip, 7 years ago

Description: modified (diff)
Summary: N = Move node to nearest way more difficult at high zoomMove node to nearest way more difficult at high zoom
Note: See TracTickets for help on using tickets.