Greasy Fork 还支持 简体中文。
Show the angle between two connected (or selected) segments — experimental branch adding Junction Box and Path (far turn) support
These are versions of this script where the code was updated. Паказаць усе версіі.
Small UI fix
Implement real-time marker updates during segment dragging
Add live marker updates as users drag segment nodes, eliminating the delay that previously showed angle changes only after mouse-up. The feature uses SVG polyline polling to extract current segment geometry and patches the segment object with live coordinates before angle calculations.
Technical approach:
New infrastructure:
No impact on continuous scanning or existing angle calculation logic.
Tame logging level
scanning mode evaluates all pair directions, so it catches PROBLEM angles regardless of segment order in the angles array.
Continuous scanning feature: background detection of PROBLEM angles with caching and incremental batching; restored previous routing logic (removed Ambiguous KEEP zone)
Extended BC evaluation zone from <44° to <47° (TURN_ANGLE ± GRAY_ZONE) to catch fragile gray-zone angles; added gray zone PROBLEM detection for 44-47° angles with ambiguous BC matching'
Gray zone detection for Best Continuation ambiguity — flags angles in 22–30° and 44–47° zones as PROBLEM when BC matching fails, skips flagging for EXIT instructions
Fix to limit item select to segments and nodes only
he fix builds the complete angles context at each intermediate node (all connected segments), then uses ja_guess_routing_instruction() — the same function that colors regular local turns. This ensures intermediate breadcrumbs inherit all the routing logic: road type hierarchy (Primary vs Street), left-hand traffic, best-continuation detection, and Keep/Exit classification. Now the breadcrumb trail shows consistent colors along the path, matching what you'd see if selecting each segment individually.
Bumb version and message
small ajustment for marker placment
More robust marker overlap prevention system
Implement roundabout turn restriction detection via exit segment query
Add BigJunction path traversal to detect local turn restrictions at roundabout exits. Replaces direct SDK turn checks (which have LHT direction quirks) with query-based approach:
Works for both RHT (US) and LHT (UK) roundabouts. Exits with restrictions display as NO_TURN (gray), others show normal markers (colored arrows or ordinal numbers).
Roundabout turn restriction detection — exits with local restrictions display as NO_TURN (gray), works for RHT and LHT countries
Fixed CW Roundabout logic
Bumb Version and tame logging
Refactor: Centralize Waze spec thresholds and implement full U-turn rules
This is a comprehensive refactoring that improves code maintainability and correctness by centralizing all magic numbers as named constants and implementing the complete Waze U-turn qualification rules.
CONSTANTS (NEW):
U-TURN LOGIC (MAJOR FIX):
DOCUMENTATION:
OPTIMIZATIONS:
OTHER:
All changes maintain backward compatibility while improving code clarity and correctness.
New Waze double-turn restriction: apply ≤15 m and ±5° parallelism criteria to mark Waze-blocked U-turn paths
Layer visibility state now persists to localStorage — JAI remembers if you turned it off
Automatic marker refresh when turn instructions or restrictions are edited (no deselect/reselect needed)
Bug fix
Version 2.2.9 Layer toggler updateJAI now uses the "new" Layer menu. Many thanks to Jason (fuji2086) for his support
Паказаць усе версіі скрыпта
