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
|
||||
|
||||
@@ -332,3 +332,13 @@ A grouped scalar is available only if the individual ranges intersect. Otherwise
|
||||
show why a common value is unavailable and expand individual controls; never
|
||||
render a minimum larger than the maximum. Transition length uses the same input,
|
||||
preview, history, and persistence path as other geometry parameters.
|
||||
|
||||
### Rotational direction handles
|
||||
|
||||
`cluster-carriageway-direction` keeps `value.current` and persisted
|
||||
`offsetDegrees` in degrees. Its manifest declares
|
||||
`interaction: { kind: 'rotation', center, radiusMeters }`. Project pointer input
|
||||
as the shortest signed azimuth change around `center`, clamp it to the manifest
|
||||
range, and place the ghost on the declared circle. Never convert linear pointer
|
||||
metres directly into degrees. The ghost label uses `°`; numeric input continues
|
||||
through the shared scalar edit session and save path.
|
||||
@@ -87,6 +87,10 @@ complex-junction.js / native-road.js:构建与全部消费者;direct-edit-so
|
||||
|
||||
方向控件仍以沿切线的线性拖动米数映射角度,且位置/方向自身手柄仍显示旧收口点。完整旋转交互需要单独明确手柄契约,本轮不据此关闭 A4/A5。
|
||||
|
||||
后续已补齐该缺口:方向手柄发布有效内断面中心和旋转半径,客户端按最短方位角变化生成 `offsetDegrees`,ghost 沿圆周移动并显示角度;位置、方向和宽度手柄统一使用有效内断面。左右边界范围由有效宽度、另一侧偏移和最小车道总宽共同推导,manifest 与 solver 共用端点且越界阻塞。兼容数值输入及既有 `offsetDegrees` 文档。
|
||||
|
||||
本轮同时修复成功闭合且接缝合格的核心仍被误报为 `complex-junction-core-closure-unsupported` 的条件分支。npm test、191 项客户端单测、类型检查、生产构建、11 项 E2E、format:check 与 git diff --check 通过。区域邻接和排除区共同决定的更大向外边界仍留给区域级求解,不用固定范围冒充完整可行域。
|
||||
|
||||
本轮质量门:npm test 通过;npm run test:client 通过;npm run test:client:unit 15 文件/188 测试通过;npm run test:e2e(包含 production build)11 测试通过,包含保存后重置与放弃恢复;npm run format:check 与 git diff --check 通过。构建仍有既有 bundle 大小提示。遵循用户“整体任务完成再提交”,本轮未提交、未归档父任务。
|
||||
|
||||
下一阶段已实现共享内边的实际米制端点误差:`sharedSeamErrors` 逐车行道报告,缺失/非邻接为 Infinity;回归通过人为 2 米偏移验证指标变化。显式过渡站点统一限制在来源折线范围,超长请求标记来源长度不足并由 solver 拒绝。全图层接缝、凹形多区域和真实 OSM 视觉验收仍未完成。
|
||||
|
||||
Reference in new issue
Block a user