fix: align junction crossings and round pedestrian islands

This commit is contained in:
que01 committed 2026-09-11 17:35:32 +08:00
1 parent 76f81d024a
commit 7a7912f302
18 files changed
+491 -96

No files matched your search

@@ -0,0 +1,56 @@
# Junction island contact
## Status and scope
Confirmed user requirement, 2026-09-11; implementation pending. Applies to the
complex-junction composition with two adjacent arm crossings and one crossing
beside the inward-curved hypotenuse. This is not a universal traffic-island
definition. Simple junction behavior is unchanged.
## Geometry contract
- A contact is the complete short edge of a crossing rectangle, not an arbitrary
white stripe, a point, or only the portion that happens to intersect the island.
- Each of the three crossings contributes one contact segment and two endpoints.
All three complete segments must be shared with the island outer boundary.
- Contact positions are geometry-dependent. The two perpendicular leg lengths
are solved from the contacts and available space; twice crossing depth is not
a hard constraint.
- Preserve six distinct contact endpoints in boundary order. Connecting them
forms the green hexagon on the island. Its three contact edges coincide with
the crossing contacts; its other three edges connect adjacent contacts.
The green region and rounded island outer boundary are distinct geometries.
- Rounded corners and inward curves occupy non-contact boundary portions.
A straight contact edge must remain straight over its full length, including
the hypotenuse-side landing. Rounding must not trim away contact endpoints.
- Solve in local metric coordinates and reuse coordinates across consumers.
Preserve consistent stripe dimensions and spacing, avoid positive-area
crossing/island intersection, and maintain stop-line separation.
- If the available space cannot satisfy the composition, report the object and
failed constraint. Do not shorten a crossing, detach it, or report the partial
composition as valid.
## Required validation
For each complete contact segment S and published island boundary B, measure
the length of S covered by B, not polygon intersection area alone. Require
uncovered length and endpoint-to-boundary distance <= 0.01 m; this tolerance
is numerical, not a design gap. Also check interior samples to catch an arc
touching only at the endpoints.
The six green vertices must equal the six contact endpoints within metric
tolerance, with each used once; the ring must be simple, have positive area,
lie inside the outer island, and retain all three full contact edges. An
independently fitted polygon or a hull dropping vertices fails this contract.
Required cases: orthogonal base case; unequal contact offsets and crossing
depths; translated/rotated equivalents; changed available space; roundovers
that would cut into contacts; and an infeasible composition. On the current
real OSM, verify all contacts and all six vertices for every published island,
not just feature counts or a hand-picked corner. Retain image evidence showing
the outer boundary, green hexagon, complete crossing rectangles and stop lines.
Wrong: move a stripe until it touches an arc at one point and declare success
because overlap area is zero. Correct: share the complete crossing short-edge
segment with the island boundary, then derive the green polygon from those
same endpoints and verify non-contact curves separately.