Document hotspots, and the new ?hotspots=1 review overlay (EN + HE)
Hotspots were not in the wiki at all: not what the ring means in flight, not the
rule that derives them from the route graph, not the per-node override. Added to
Waypoints and notes (what it means), Nav waypoints dataset (how it is derived and
overridden) and Hidden tools (the new flag, beside ?graphlegs=1).
Say the AI assistant is off on the live site, not merely hidden by default
featureAssistant ships false and the deployed gist does not override it, so
there is no launcher on navaid.supino.org at all. The page now opens with that,
and explains how to switch it on (?tune=1, or the gist for your own copy).
Cross-references in The map and Hidden tools match (EN + HE).
Wiki: frequency NOTAMs, the mail preamble, and the editor's new export shape
Sweep of all 81 pages against what shipped since the last one. Three real gaps, one
of them advice that had become wrong.
Frequency-Changes: documents the airfield-inspector marker for an active NOTAM that
mentions a frequency, and — more importantly — why it names the NOTAM and never a
value. A NOTAM frequency is true today, not in general, and a mis-parse would put a
pilot on the wrong frequency. The app points; the pilot reads and decides.
Submit-Flight-Plan: the filed mail now opens with a plain-language summary above the
ICAO block. Records the split that matters: the preamble follows the UI language, the
(FPL-...) block is never translated because its contents are codes. Also that a
landing time is dropped rather than invented when departure or EET is missing.
Hidden-Tools: the editor advice was WRONG, not merely stale. The page said point mode
"exports JSON for pasting back into a dataset"; it now exports a route-graph `nodes`
fragment that must be MERGED into the nodes map. Pasting it over a graph would destroy
the file. Also notes the ride-through of unedited fields, UNNAMED_n placeholders for
un-named points, and that edges are not exported.
Checked and clean: no page quotes the corrected 125.60, and nothing documents
closedHint (removed from CVFR) or the one-way corrections, so nothing there went
stale. Changelog left alone — it is generated.
Route-graph review overlay, dataset correction, and the clearance-leg refusal
Nav-Waypoints-Dataset: the page documented three files that no longer exist.
Reporting points are projected from the layer's route graph now
(navWaypointsFromGraph), not read from *-nav-waypoints.json. The CVFR count 172
was also stale: the graph holds 172 nodes of which 170 project, ZRANA and RANNO
being locality labels the chart-image rebuild misread as mandatory points and now
carrying active:false. Documents that active is absent-means-true (a missing flag
can only ever show a label, never hide a published point), and noSegmentsReason
for published points that legitimately have no segment, such as military-route
ones -- they look identical to a locality label in the data, which is why the
reason is required.
Hidden-Tools: adds ?graphlegs=1, the route-graph review overlay -- what the marks
mean, why arrow and altitude sit together at the end a direction starts from (the
chart prints the figure there, so the two read side by side), why a two-way leg
shows two figures, and what an em-dash means. Notes that it reads the same fields
routing reads, which is how `blocked` was found on the wrong entry of 7 of the 21
CVFR one-way legs.
Submit-Flight-Plan: army airways and ATC-approval corridors cannot appear in a
filed plan, so the app refuses rather than warns -- the plan would come back
rejected, so there is nothing to acknowledge. Also states plainly what is NOT
restricted: the legs stay on the map with their altitudes and a hand-placed point
is always kept; only the app's own choice changed.
The cache-bust line already on the dataset page is correct as written and left
alone -- deploy.yml rewrites every data/*.json?v= to the commit SHA.
Add Hidden Tools page (EN + HE)
Documents the three URL-gated surfaces (?tune=1, ?editor=1, ?align=1), what the
map-data editor and overlay-align modes actually do, the ?nogist switch, and the
visible-but-unlabelled entry points (simulator, assistant bubble, GPS icons,
magnifier settings, mosaic, the reference-link overflow). Linked from both
sidebars under For developers, after Tuning Panel.