Bake district boundaries #30

Closed
opened 2026-10-17 20:40:35 +00:00 by sermuns · 3 comments
Owner

Three boundary relations in the extract:

Slaka                            6 ways
Ryds distrikt                     3 ways
Linkopings domkyrkodistrikt      6 ways

These are real, walkable edges -- the campus sits where Ryds district and Slaka
meet, which is a decent chunk of why it is there at all -- and nothing draws
them.

barrier_tris already draws a closed line standing 1.1 m off the ground and is
never collided, which is exactly right for a boundary: visible, and never a
thing a stray line can trap you behind. But barrier_tris takes BakedPath, so
a boundary wants assembling into a ring first.

Worth a distinct, low, translucent treatment rather than a hedge, so it does not
read as a fence. Depends on #8, the relation parser.


Related

  • #8 needs the relation parser
  • #19 a boundary is drawn like a barrier
  • #46 Vallaskogen is one of them
Three `boundary` relations in the extract: ``` Slaka 6 ways Ryds distrikt 3 ways Linkopings domkyrkodistrikt 6 ways ``` These are real, walkable edges -- the campus sits where Ryds district and Slaka meet, which is a decent chunk of why it is there at all -- and nothing draws them. `barrier_tris` already draws a closed line standing 1.1 m off the ground and is never collided, which is exactly right for a boundary: visible, and never a thing a stray line can trap you behind. But `barrier_tris` takes `BakedPath`, so a boundary wants assembling into a ring first. Worth a distinct, low, translucent treatment rather than a hedge, so it does not read as a fence. Depends on #8, the relation parser. --- **Related** - #8 needs the relation parser - #19 a boundary is drawn like a barrier - #46 Vallaskogen is one of them
sermuns added this to the Terrain & paths milestone 2026-10-19 22:18:42 +00:00
Author
Owner

District boundaries are administrative, not physical — there is nothing to see on the ground where Ryds distrikt meets Slaka. The boundary may follow real paths, but the boundary itself is not a visible feature. Drawing it as a 1.1 m line would be a debug overlay dressed as world geometry. If this is wanted at all, it belongs in the M map view as a thin overlay, not in the 3D bake. I'd close it or move it to a map-mode issue.

District boundaries are administrative, not physical — there is nothing to see on the ground where Ryds distrikt meets Slaka. The boundary may follow real paths, but the boundary itself is not a visible feature. Drawing it as a 1.1 m line would be a debug overlay dressed as world geometry. If this is wanted at all, it belongs in the `M` map view as a thin overlay, not in the 3D bake. I'd close it or move it to a map-mode issue.
Author
Owner

Status check: the three type=boundary relations are still ignored because OsmMap has no relation field. They are administrative boundaries (Slaka, Ryds distrikt, Linköpings domkyrkodistrikt), not a physical edge on the ground. If this is wanted at all it belongs in the M map as a thin overlay, not in the 3D bake as a barrier-height line.

Status check: the three `type=boundary` relations are still ignored because `OsmMap` has no relation field. They are administrative boundaries (Slaka, Ryds distrikt, Linköpings domkyrkodistrikt), not a physical edge on the ground. If this is wanted at all it belongs in the `M` map as a thin overlay, not in the 3D bake as a barrier-height line.
Author
Owner

Closing as out of scope. District boundaries are administrative, not physical: there is nothing visible on the ground where Ryds distrikt meets Slaka, so drawing them would be a debug overlay dressed as world geometry.

Closing as out of scope. District boundaries are administrative, not physical: there is nothing visible on the ground where Ryds distrikt meets Slaka, so drawing them would be a debug overlay dressed as world geometry.
Sign in to join this conversation.
No description provided.