Skip to content

Shared boundary between landuse areas not working #996

Description

@troNpo

Shared boundary between two landuse areas (Go Map!!)

Hi, and thanks for your great work on Go Map!!

I’m trying to create a shared boundary between two landuse areas, and I’m not sure whether the app currently supports this or if I’m doing something wrong.

What I’m trying to do

I have an existing landuse=farmland polygon.
Then I created a new landuse=orchard polygon.

My goal is for the new landuse=orchard polygon to use a segment of the existing landuse=farmland polygon as a shared boundary, exactly like in JOSM or iD:

  • same nodes
  • same line segment
  • no duplicated geometry
  • orchard polygon closed using that shared segment

What happens in Go Map!!

I connect the orchard’s endpoints to the farmland’s boundary.
In the app, the nodes appear connected, and Go Map!! even shows options like “Divide” or “Incorporate”.

However:

  • the orchard polygon does not actually close using the farmland boundary
  • the shared segment is not incorporated into the orchard polygon
  • when I upload and check the data in the OSM web editor, I get errors such as:
    • “unknown way”
    • “close ends”

This indicates that the orchard polygon is still open and not using the farmland segment as part of its geometry.

Question

Is it currently possible in Go Map!! to make two landuse polygons share the same boundary segment (same nodes and same line), and to close the new polygon using that shared segment?

If it is possible, could you explain the exact workflow?

If not, would it be possible to add this functionality?
It’s essential for editing adjacent landuse areas without duplicating geometry.

Thanks again for maintaining this app — it’s incredibly useful for editing OSM from iPhone.

Image Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions