Opened 10 years ago

Closed 10 years ago

#2736 closed defect (invalid)

Polygons cannot be split by selecting a non-end node

Reported by: Eugene Alvin Villar Owned by: cbro@…
Priority: minor Milestone:
Component: merkaartor Version:
Keywords: Cc: merkaartor@…


version: 0.15-svn(19940)

An area way (polygon) could not be split by just selecting a node that is not the common endpoint as the split point. In this scenario, what is expected is that there would be two ways each having the same end nodes: the original common end node and the new end node that was selected. Instead what seems to happen is that the selected node becomes the new end node of the polygon and that there is a new node on top of the selected node.

Change History (5)

comment:1 Changed 10 years ago by Chris Browet

This is not very clear.

Are you trying to break the area? Breaking would duplicating the selected node of the area, effectively "opening" it. Is this what you actually did?

Are you actually trying to split it? In this case, you have to select the area and 2 points, the result being 2 roads, attached by the common 2 nodes.

comment:2 Changed 10 years ago by Eugene Alvin Villar

I know that you can split the area by selecting two nodes. But I think that you should also be able to split the area by selecting just one node (which is not the common end node of the area). When you split a way with just one node selected as stated, the effect is as if the common end node was also selected and the area is split into two ways sharing common end nodes: the selected node and the original common end node. This is the behavior in Potlatch and I would imagine that many people coming from Potlatch would expect this.

comment:3 Changed 10 years ago by Eugene Alvin Villar

Anyway, when I try the scenario above in Merkaartor I get weird behavior:

  1. Create a 4-node area.
  2. Select the area and a node (which is not the common end node).
  3. Use the split tool.
  4. The effect is as if the break tool was applied, not the split tool since there are now two separate nodes on the same location.

comment:4 Changed 10 years ago by Chris Browet

Cc: merkaartor@… added

That's on purpose, because, IMHO, that's the logical exectation when selecting 1 node, to actually break. But I should disable the menu item altogether to avoid confusion.

Call me thick but I don't get it. I don't understand what would be the start and end node of the 2 segment by selecting only 1 node. I think I understand that the second node would be assumed to be the closing node of the area? How is the user supposed to know which node it is? Do Potlach highlight it differently?

I never used Potlach so I cannot understand from experience.

If I'm wrong, could you (or someone else) make me a little explanatory drawing, please, or Potlach screenshots?

If I'm right, this seems to be rather cumbersome and error-prone just to avoid selecting a 2nd node...

comment:5 Changed 10 years ago by Chris Browet

Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.