- Context reads what is under the pointer when the button goes down. The
flights layer acts on the click first and swaps the plane's icon for its
model, so a pick at click time found a different plane behind it.
- For flights, military, satellites and live vessels, whose own click
already follows the craft, Context no longer starts a second follow: the
flights layer read that as a click on empty map and let go. The card is
marked as following once the camera has taken hold.
- The card's following state resets when the camera stops following, so
picking the same item again follows it again.
- A click on open ground, sea, sky or the photorealistic ground clears the
card.
Clicking anything a layer can identify opens one card in Context: a hero
tile (route globe and 3D model for a flight, the camera for CCTV, headline
figures otherwise), its facts, actions with Cockpit or the orbital view as
the primary one, and a standard set of nearby blocks (weather and local
time, flights, vessels, hazards, alerts) within one radius the user sets.
Aircraft show altitude as a graph. Things that move are followed when
picked, and a card closes when its layer is turned off.
With nothing selected the panel describes the view: the layers that are on
with a breakdown of what each holds, the camera's height, what is in view,
then time, weather and local news. From far out it shows worldwide counts
per layer. A search field in the header narrows whatever the panel shows.
Prototype. Context reads weather and hazard feeds while its panel is closed,
the two 3D previews on a flight card repaint continuously, Follow can show
pressed after tracking has ended elsewhere, and most new strings are fixed
English. Same-named sites are told apart by position, not by a stable id.
A resumed hold waited only its rest unless the layer gave a media gate,
and only trimmed clips have one, so an untrimmed clip started again (as
on Gyirong) was cut short. The layer now says when a run going on from a
seek started its clip again, and the hold then plays out as from its
start: through the media gate when there is one, else for the whole hold.
For a shot whose path runs during the camera move, a seek in the hold
showed its evidence sequence at the start and a resumed run jumped to
its end. The sequence now stands where its own clock has it (after the
clip and its exit), and a resumed run carries on from there.
The corner controls are the ACTIVE STYLE readout and any element marked
with data-stories-corner, looked for again for 20 s after Stories mounts,
in place of an element id this app never has.
The director's own pointerdown listener, added first, stops a run whose
camera it drives before Stories heard the press, so the tap still played
the story again. Stories now reads the press in the capture phase, and
its tap listeners are removed on teardown.
Three fixes to how the globe draws and reports loading.
**The idle frame rate is the app's rule.** The Cesium frame port capped the loop at `IDLE_FRAME_RATE` whenever nothing held it, so the rule lived inside the renderer. The render governor now sets the rate: the display's own while the loop is held, `IDLE_FRAME_RATE` while not. The frame port gains `onHeldChange(cb)`, which says when its first hold is taken and its last released (animated visual styles included), so the governor hears every hold. The quality setting's frame-rate cap is kept apart from the governor's rate, and the loop draws at the lower of the two, so neither overwrites the other.
**Line batching is timed.** A line set waited 30 drawn frames before its unchanged lines settled into a static batch (300 for the long wait), so the batch built twice as fast at 120 Hz as at 60 Hz, and took seconds at the idle rate. It now waits `SETTLE_MS` (500 ms) and `LONG_SETTLE_MS` (5 s), and moved shapes go back into their batches on the same timing.
**KEY REQUIRED.** A layer that cannot load without a provider key ended the global status chip LOAD FAILED. The chip now has a KEY REQUIRED outcome, ranked below a real failure: a layer whose stats say `keyRequired` ends KEY REQUIRED, any other failure still ends LOAD FAILED. Vessels report a missing AISStream key as `keyRequired` and name the key in the panel; a later outage clears it, as it is no longer the key that is missing.
Checked: the full suite (new tests for `onHeldChange`, the quality cap against the governor's rate, timed settling, and the chip with and without a key), format, boundaries, build, the stub renderer boot and the Cesium conformance run; in the browser, the idle and held frame rates; and the first-run check now asserts that with no keys set the chip never says LOAD FAILED.
Early Stories builds wrote stories, storyThumb and storyTags in version 6
projects, so those projects load again; the fields stay refused before
version 6. The version 6 round trip is tested again.
A camera move the scene drives frame by frame (an authored move, or a
flight resumed partway) stops the run on pointerdown, so the story read
as stopped when the tap ended and the tap played it again. The tap now
goes by whether the story was playing when it began.
Back or Forward into such an entry from Explore or an open story clears
the story and its time from the address and the entry's history state,
keeping the globe hash and, when the entry is Explore, Explore itself.
After placing the layers at the seek's moment, the hold settles them
without the seek, so the reveal continues from where the seek put it and
a clip the moment falls in starts again from its beginning (a clip
cannot be joined partway); one the moment is past stays finished.
The selected vessel's track drew every fix it held. Following the world
clock, it ran ahead of the icon to the vessel's newest fix; live, it
stopped at the last fix while the icon moved on from it. A change of time
restarted it from a single point until the track at the new time arrived,
so it went blank at every step.
- The track draws the fixes at or before the time the vessel is drawn at;
live, every fix.
- Each frame a head joins its last drawn fix to the icon where it is drawn,
as flight tracks do; none past TRAIL_HEAD_MAX_M (20 km), where the clock
has moved beyond the fixes the track holds.
- A change of time keeps the track, drawn up to the new time, until the
track at that time replaces it.
GEV stories never explore, carry no world time and are never live:
drop the resume play state, Jump to live, the exploring branches and
world-time arguments, the overridden play button rules, and the hidden
rail and fill. The legend reads a plain field instead of a mock one.
directorSettled now tells a timeout from settlement, and on a timeout
revokes the scene's layer cleanup still in flight before Close puts the
view back.
Restores the scene picker and its selection on load, after a delete and
after an import, so PLAY and NEXT work after a reload. Open in GEV
selecting a shot and NEW SCENE stay as they are.
Pressing Live while a timed snapshot load was in flight left the live poll
waiting on that load. The live poll returned early, so the map showed no
vessels until the next refresh. The live poll now drops a timed load still
in flight, and loadAt shares the same dropLoad helper.
startScene takes fromProgress and starts partway into a shot: the camera
goes on along the rest of the flight, the hold waits only what is left
and the scene clock carries on from the same point.
- On GEV's phone layout, where neither the style readout nor the account
avatar shows, the Stories button goes icon-only under the corner-actions
column instead of covering the top row of icon buttons.
- Explore frames its start view and a picked story in the middle of the
map it leaves visible (beside the feed, above the phone sheet), with one
short correction if that area moved during the flight.
- The share icon stays visible in icon-only header buttons.
- A world clock nothing moved while Stories was open (no jump, same mode
and rate) is left alone on Close.
- Card images use the globe's own Esri tile URL; the credit list keeps the
application's full-screen placement on phones.
- Tests cover the live and playing clock restores, the clock coming back
after the share state, the tile-settling hold being released (settled,
10 s, Close), the visible-map aim, and the near-end Play fix in the
director's real order. One changelog fragment covers the PR.
Focused follow-up to manjunath22466's Stories contribution.
A paused share link in the final 250 ms is not a completed scene.
Add node:test coverage for near-end Play and true-end replay; update
current-state documentation and the #1724 changelog fragment.
Main now keeps Cesium behind the renderer contract, so Stories stops
reaching Cesium and the viewer directly.
- Camera: flights, the -60 degree story framing, cancel, the pose saved
on open and put back on Close go through the camera port; a follow is
released with stopFollowing.
- Pins: placed in the frame port's postRender from the query port's
projection and horizon test, still written straight to each pin's
transform on every drawn frame.
- Tile settling: a continuous-render hold until the globe port reports
the base settled, for at most 10 s.
- Clock: Close and Back to Explore put back the page's world clock (live,
or the time it showed, playing on), and leave a clock that is still
where it should be alone.
- Card images: drawn from Esri World Imagery's own Web Mercator tiles
while the Esri map stack is active, read as images; no Cesium imagery
provider is touched.
- THUMBNAIL: the director hands captureStoryThumb the frame port and the
renderer's canvas, so the scene document's module stays renderer-free.
- Credits: Stories places and keeps visible the application's credit
line (#gev-credits) and its list as well as the renderer's own display.
- Tests fake the ports instead of a Cesium viewer, and cover pins per
frame, the flights, the settling bound and the clock restore; the
share link tests Stories added build their manager over a camera port.
A Stories button (top right) opens Explore: a feed of GEV scenes over
GEV's own Cesium globe, with a pin per story. Explore opens at country
level over the first story and, while idle, flies on from story to story
for a minute. A picked story is framed in the middle of the view; a pin
plays its story on a second click. The Story page plays the scene through
SceneDirector with a timeline, chapters, key moments, sources and
background, then Close (or Back) puts the person's camera, clock, layers,
style and AUTHORING selection back. Open in GEV hands the scene to the
Scenes panel at its current shot.
Stories lists the scenes GEV ships with a camera path (while they are in
the project), the scenes saved with SAVE TO STORIES in AUTHORING, and the
person's other scenes as drafts. The person's own stories live in the
project on this device, so they have no Share; a link to a story that is
not here opens Explore and says so. Each shipped story's
context comes from what GEV knows: what it shows, the place each shot goes,
and each layer's data sources as DATA_SOURCES.md lists them; the Nepal
story carries the event pack's facts and CC BY-NC sources. Card images are
a captured THUMBNAIL or drawn from the keyless Esri World Imagery.
AUTHORING has no scene picker: it starts with no scene, NEW SCENE (or
CAPTURE SHOT) makes one, and Stories' Open in GEV selects one. Before SAVE
TO STORIES it offers topic tags and THUMBNAIL. A scene's stories flag,
storyThumb and storyTags are saved with the project and kept through
export and import.
Only the closed state loads with the page; the screens, styles, story data
and controller load on first open. Stories keeps its place in the query
(one history entry per screen) and holds the share link's hash writes
while open. Keyboard input and voice tools stay with Stories while it is
open. Explore's pins move on every drawn frame without asking for frames;
the idle tour and tile settling are bounded.
All strings are translated in the 13 locales.
While the timeline plays or is scrubbed, each vessel icon is handed to the
renderer as a motion segment along its track (a straight piece of at most
10 km between two fixes, on the scene clock), as aircraft already are. The
layer writes an icon again only when its segment runs out or the time
moves back before it, instead of moving every icon on the CPU every frame.
Behaviour is kept:
- Icons follow the same great-circle track between fixes (a 10 km chord
stays within 2 m of it) with the same course.
- A vessel still appears TIMELINE_UNSEEN_MS before its first fix and
hides again when the time moves back before that.
- Cards, the selected vessel, ship models and the vessel the bridge camera
rides are read where they are every frame; the rest within
HIDDEN_FOLLOW_MS, as before.
- Position reads (getAllPositions, getNearby, the focus pass, the
detection overlay, single-vessel lookups) return where the icon is drawn
at the world time.
- Going live, each icon holds where its segment last drew it, unless a
live update has drawn it since.
- Trails are unchanged: they are built from the feed's fixes, not from the
per-frame position.
- Live mode and renderers without the motionSegments capability take the
previous path unchanged.
On Node 26 the engine inlined the projection pass's helpers in another order and left distanceScale out, so every label's paint scale allocated a number: 158 B per candidate per frame against the 154 B budget, where main measures 136 B. The curve now sits beside the altitude curve in snapshotAndProject, with the same arithmetic.