Modify

Opened 3 years ago

Last modified 3 years ago

#16710 new defect

Move Node onto Way more difficult at high zoom

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 onto Way" (N key) requires that the node be excessively near the way.
And BTW, function "Merge Nodes" (M key) 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.
EDIT: off-topic

Attachments (2)

M24.osm (4.1 KB) - added by A_Pirard 3 years ago.
N 25.osm (2.8 KB) - added by A_Pirard 3 years ago.

Download all attachments as: .zip

Change History (13)

comment:1 Changed 3 years ago by A_Pirard

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 Changed 3 years ago by Don-vip

Owner: changed from team to A_Pirard
Status: newneedinfo

Please provide a sample file showing the problem. Thanks.

comment:3 Changed 3 years ago by A_Pirard

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.

Changed 3 years ago by A_Pirard

Attachment: M24.osm added

Changed 3 years ago by A_Pirard

Attachment: N 25.osm added

comment:4 Changed 3 years ago by A_Pirard

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 Changed 3 years ago by Don-vip

Owner: changed from A_Pirard to team
Status: needinfonew

comment:6 Changed 3 years ago by Don-vip

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

comment:7 Changed 3 years ago by Don-vip

Type: defectenhancement

comment:8 Changed 3 years ago by Don-vip

Description: modified (diff)
Keywords: distance added
Summary: Move node to nearest way more difficult at high zoomMove Node onto Way more difficult at high zoom

comment:9 Changed 3 years ago by Don-vip

Type: enhancementdefect

I can reproduce the problem for N with file N25.osm but not with M with file M24.osm. At maximum zoom level I'm still able to merge the nodes.

comment:10 Changed 3 years ago by A_Pirard

Hi Don,

You probably select the two nodes. I wrote I select only one because
1) of speed : alternating way/node selections twice dozens of times takes time
2) selecting a single one makes sure which node is moving

Thanks for looking into this issue.
TIA.

Last edited 3 years ago by A_Pirard (previous) (diff)

comment:11 Changed 3 years ago by Don-vip

OK I didn't even know we could merge nodes by selecting only one of them. I confirm I can reproduce both problems now.

Last edited 3 years ago by Don-vip (previous) (diff)

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain team.
as The resolution will be set.
to The owner will be changed from team to the specified user.
The owner will change to A_Pirard
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.