1.3 KiB
Design: Lane Maneuver Position Drag
Selection And Gesture
The selected arrow group remains one logical target: lane_id + maneuver. A new
display-only selection layer will become the drag hit target, while its members are
never moved independently. Pointer coordinates are projected onto the lane centerline
and converted to a distance from the lane's junction end, matching the compiler's
placement_distance_meters convention.
Contract
The existing lane-maneuver override gains optional finite, non-negative
placementDistanceMeters, measured from the lane's junction end. The compiler uses
it when present, otherwise keeps its current candidate-placement algorithm
byte-for-byte. Maneuver and position are updated together by lane id so an old
maneuver override cannot shadow a newer position entry.
Validation And Preview
The server remains authoritative for collision checks and final geometry. The client may project and clamp the ghost for responsive feedback, but it must submit the position through the existing save/recompile boundary and never mutate baseline GeoJSON. The candidate position must clear control features and leave the compiler's endpoint safety buffer.
Rotation is intentionally absent from the contract; adding it later must not require reinterpretation of the position field.