feat: complete carriageway direction interaction
This commit is contained in:
1 parent
a5089220b5
commit
067c0e370d
10 files changed
+251
-41
No files matched your search
@@ -412,6 +412,27 @@ Regression evidence: solver rejects out-of-range/source-mismatched values;
|
||||
API preview measures the requested length and preserves the outer seam;
|
||||
save/read/replay reproduces preview geometry; browser input sends the new kind.
|
||||
|
||||
## Complex carriageway direction and edge bounds
|
||||
|
||||
`cluster-carriageway-direction` remains persisted as
|
||||
`value.offsetDegrees`, including for numeric input and existing documents. Its
|
||||
manifest handle declares `interaction.kind = rotation`, an EPSG:4326 `center`
|
||||
at the effective inner entry section, and `radiusMeters`. Pointer projection is
|
||||
the signed shortest azimuth change around that center; pointer metres must never
|
||||
be interpreted as degrees. The direction ghost follows the declared circle and
|
||||
uses degree units.
|
||||
|
||||
Position and width handles use the same effective inner entry section as the
|
||||
BoundaryGraph. Direction edits rotate the width axis and both edge handles at
|
||||
that section.
|
||||
|
||||
The manifest and solver share the carriageway edge range. For one side, with
|
||||
effective width `W`, opposite offset `O`, and minimum lane total `M`, the range
|
||||
is `max(-W/2, M-W-O)..W/2`. Both endpoints are accepted; a value outside the
|
||||
range is rejected with a blocking geometry diagnostic. Independent side
|
||||
constraints and legacy constraints containing both offsets must be evaluated
|
||||
with both effective offsets present.
|
||||
|
||||
Boundary closure reports `sharedSeamErrors` per carriageway and
|
||||
`maxSharedSeamErrorMeters` as the maximum endpoint distance in local metres
|
||||
between the core ring edge and its BoundaryGraph `inner` edge. Missing or
|
||||
|
||||
Reference in new issue
Block a user