feat: complete complex junction transition editing
This commit is contained in:
1 parent
801d8be980
commit
79f83412e6
18 files changed
+400
-59
No files matched your search
@@ -379,3 +379,20 @@ projectJunctionStructure({ model, layers });
|
||||
projectJunctionStructure({ model, layers, trafficSignals,
|
||||
junctionRef: { type: 'cluster', id: selectedClusterId } });
|
||||
```
|
||||
|
||||
## Complex carriageway transition length
|
||||
|
||||
`cluster-carriageway-transition-length` uses the source-checked
|
||||
`cluster-carriageway` anchor and `value.transitionLengthMeters`. Replay verifies
|
||||
source road/node membership before solving. The resolved `clusterTransitions`
|
||||
map is separate from `clusterCutbacks`: the outer source seam is fixed, and the
|
||||
inner station is `outerStation - transitionLengthMeters` along the source
|
||||
polyline. Radial distance differences are not lengths on curved approaches.
|
||||
The maximum is the available outer station; the minimum is the smaller of the
|
||||
configured minimum and the existing source-derived transition (short existing
|
||||
approaches remain representable). Impossible surface geometry still requires
|
||||
compiler validation. A saved transition is never silently clamped.
|
||||
|
||||
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.
|
||||
Reference in new issue
Block a user