Commit Graph
4000 Commits
Author SHA1 Message Date
Sameh Khamis 15d1855dd3 Merge pull request #1757 from bilawalsidhu/perf/vessel-labels-merge
vessels: cheaper label pass and fix merge during playback
2026-11-15 17:41:27 -08:00
Sameh Khamis 3909c7735a changelog: vessel labels and fix merge 2026-11-15 16:13:56 -08:00
Sameh Khamis 121b69561a timeline: read each entry's time once when merging runs
mergeTimelineRuns read an entry's time again on every comparison, and the
vessel layer passed a new arrow for every vessel. Times are now read once
into arrays, the leading older entries the loop would keep one by one are
sliced in one step, and the layer passes one function. The result is the
same entries in the same order; a test checks 3,000 random merges against
the previous algorithm.

Measured in the browser, one implementation per page, 9,000 vessels with
240 kept fixes each, 5 alternating pairs: 65-87 ms -> 57-61 ms per snapshot.
2026-11-15 16:13:28 -08:00
Sameh Khamis b65bb86db3 vessels: project label candidates with the camera read once per pass
The label pass projects every vessel in view each time it runs. It asked
Cesium for each one, which reads the camera and allocates for every point.
createWindowProjector reads the camera's matrices and the canvas size once
and runs the same arithmetic in the same order, so the window positions are
the same numbers (a test compares them bit for bit with Cesium); outside a
3D perspective view it asks Cesium as before.

Grid cells are keyed by number, a cell's candidate is made only for its
first vessel and updated in place, and whether a name is worth a card is
kept per vessel until its name, MMSI or id changes.

Measured in the browser (perf harness, 9,000 vessels, 1 min/s): the label
pass 33 ms -> 11 ms, the forced visibility pass 42 ms -> 27 ms.
2026-11-15 16:13:28 -08:00
Sameh Khamis 663b56f620 Merge pull request #1755 from bilawalsidhu/render/world-time-hold
Vessels following the clock: draw at the display's rate, move drawn vessels on a half-pixel step
2026-11-15 13:45:49 -08:00
Sameh Khamis 9a568020fb changelog: vessel playback frames 2026-11-15 13:35:35 -08:00
Sameh Khamis 1f6e8914f2 vessels: move drawn vessels following the clock once they would move half a pixel
A profile of about 9,000 vessels following a playing world clock spent
~13 ms of every frame in the clock pass, moving every drawn vessel a
fraction of a pixel, and ~4 ms more re-uploading their billboards.

- Drawn vessels move again once the fastest would have moved half a pixel
  on screen at the speed each last moved (measured from the world time it
  was drawn at), at least once a second, and at once when the camera moves
  or changes height by a tenth of its height or the view zooms. A pass that
  holds them back asks for a frame, so a paused clock settles on the time.
- Hidden vessels move a share of them each pass, each within 250 ms, rather
  than all of them in one frame; the visibility pass moves one coming into
  view to the time first.
- A vessel's three positions are written from one surface point and normal
  (Cesium's own formula) instead of three fromDegrees calls; the unused
  normal is dropped. The great-circle step builds no arrays.

The pass falls from 4.6 ms to 0.37 ms a frame on average in a benchmark of
9,000 vessels (3,000 drawn) at 240 frames a second.
2026-11-15 13:35:11 -08:00
Sameh Khamis 8af8c086a6 render: hold continuous render while the world clock plays away from live
Playback moves something every frame, so it draws at the display's rate
rather than the parked scene's 60 FPS cap. followWorldTime reports when the
clock starts and stops playing (not live, not stepped, not waiting for data).
2026-11-15 13:35:11 -08:00
Bilawal Sidhu cb3be34283 Merge pull request #1754 from bilawalsidhu/claude/project-thread-2tz5yv
README: lead with the official site and its clips, fold the reference sections
2026-11-15 13:52:32 -06:00
Bilawal SidhuandClaude 04d08d1c7e README: lead with the official site, the site's clips and copy; fold reference sections; drop launch-era GIFs
The top of the README now matches godseyeview.ai: official-site line, hero clip, a twelve-tile feature
grid and the video series. Docker, Codespaces, the layer table, Street Level and the voice provider
notes are folded into collapsed sections with their text unchanged. The Field Missions and Cockpit
showcase sections and the 17 launch-era GIFs are removed (68 MB of media down to under 8 MB).
package.json homepage points at godseyeview.ai.

Co-Authored-By: Claude <[email protected]>
2026-11-15 19:41:33 +00:00
Sameh Khamis 4ad94592e9 Merge pull request #1753 from bilawalsidhu/flights/course-from-fixes
An aircraft with no track or true heading faces the way it moved
2026-11-15 11:36:35 -08:00
Sameh Khamis d49552af57 Merge remote-tracking branch 'origin/main' into flights/course-from-fixes
# Conflicts:
#	docs/CURRENT-STATE.md
#	scripts/package-boundaries.json
2026-11-15 11:26:28 -08:00
Sameh Khamis fc4db81d0b Course from fixes only moves forward in time, from an anchor fix, and not for a standing contact; military contacts too
A fix that is not a second newer (a repeat, or an older position from another
feed) never gives a course, so a source switch cannot turn an aircraft
around. The course runs from an anchor fix that moves only when a course is
read, so frequent short steps add up, and a contact reported under 2 m/s
reads none. The helper moves to src/data/courseFromFixes.js and the military
records use it as well.
2026-11-15 11:19:58 -08:00
Sameh Khamis 46ccce3396 Merge pull request #1752 from bilawalsidhu/render/uncap-frame-rate
Draw at the display's refresh rate while anything moves
2026-11-15 11:16:11 -08:00
Sameh Khamis e08dcd0326 Changelog fragment for #1753 2026-11-15 11:11:42 -08:00
Sameh Khamis 537a5d6e0f fix(flights): an aircraft with no track or true heading faces the way it moved, not north
Some feed rows carry neither a ground track nor a true heading for an
aircraft on the ground. Its course then fell back to 0, and an aircraft
taxiing south was drawn facing north, moving backwards or sideways. With
neither reported, the course is now read from its last fix to this one when
they are at least 30 m apart; nearer fixes are position noise and keep the
last course.
2026-11-15 11:11:35 -08:00
Sameh Khamis e469844896 Followed-contact fade starts from one 60 Hz step after a pause 2026-11-15 11:05:22 -08:00
Sameh Khamis d54bed9cd9 Followed-contact mark fade scales with elapsed time; camera pose sampling runs until moveEnd; reinstalling drops the camera hold 2026-11-15 10:58:45 -08:00
Sameh Khamis 30cc22fbef Own src/time/frameWait.js in the packages that import it 2026-11-15 10:48:37 -08:00
Sameh Khamis be77434ddd Merge branch 'main' into render/uncap-frame-rate 2026-11-15 10:43:12 -08:00
Sameh Khamis d31511e9af Changelog fragment for #1752 2026-11-15 10:41:54 -08:00
Sameh Khamis 9f4254e962 perf: draw at the display's refresh rate while anything moves
Remove the fixed 60 FPS cap. The render governor caps a parked scene at
60 ticks a second, since Cesium still runs the clock, data sources and update
listeners on every animation frame when it skips the draw, and holds
continuous render while the camera moves (moveStart to moveEnd, with pose
sampling for cameras that drift by rounding errors and never raise moveEnd).
Waits that counted frames (a tracked contact's first position, a shared
follow view, a trail's temporary copy) now count drawn time through
src/time/frameWait.js, so they last the same at any refresh rate.
2026-11-15 10:41:36 -08:00
Sameh Khamis 967477ee0f Merge pull request #1751 from bilawalsidhu/gnss/h3-cells
GNSS Integrity on H3 resolution-4 hexagons, as gpsjam.org
2026-11-15 10:41:27 -08:00
Sameh Khamis 101b92f088 Merge branch 'main' into gnss/h3-cells 2026-11-15 10:30:31 -08:00
Sameh Khamis d519d70ae3 Changelog fragment for #1751 2026-11-15 10:20:08 -08:00
Sameh Khamis 317d06adf6 GNSS Integrity on H3 resolution-4 hexagons, as gpsjam.org
Aircraft are binned into H3 resolution-4 cells (h3-js) and each cell is
drawn as its hexagon instead of a 0.5 degree square. As on gpsjam.org,
every hexagon with an aircraft is shown: the three-aircraft minimum is
gone, and discounting one bad aircraft is the only small-sample guard.
Cells are keyed by their H3 index and carry their centre and boundary.
2026-11-15 10:19:59 -08:00
Sameh Khamis 8d9c907133 Merge pull request #1750 from bilawalsidhu/search/coordinate-formats
Search reads degrees-minutes-seconds, UTM, MGRS and plus codes
2026-11-15 10:10:22 -08:00
Sameh Khamis b952ca0e1c Merge branch 'main' into search/coordinate-formats 2026-11-15 09:59:44 -08:00
Sameh Khamis 6a4202242d MGRS squares touching the antimeridian read: the zone check compares longitudes unwrapped 2026-11-15 09:50:44 -08:00
Sameh Khamis 262de71fec Grid references decline dates and short words in capitals: MGRS to 100 m or finer, within its zone, not spelling a month; UTM N reads as the northern hemisphere 2026-11-15 09:48:35 -08:00
Sameh Khamis d91c513e07 Changelog fragment for #1750 2026-11-15 09:41:43 -08:00
Sameh Khamis 4a61c755d9 Search reads degrees-minutes-seconds, UTM, MGRS and plus codes 2026-11-15 09:41:01 -08:00
Sameh Khamis 574d873e6b Merge pull request #1749 from bilawalsidhu/sameh/smooth-rewind
Contacts move back as smoothly as they move on
2026-11-15 09:38:34 -08:00
Sameh Khamis e027fc3794 Changelog fragment for #1749 2026-11-15 09:27:48 -08:00
Sameh Khamis 2b5fb51684 Contacts move back as smoothly as they move on
A snapshot timeline may declare spanMs: each record of a snapshot at a
time then carries its own fixes from spanMs before the time to spanMs
after it. Flights, military flights and vessels following the clock are
placed on those fixes, so a seek or a move back within the fixes loaded
is no jump: nothing is cleared and play does not wait. The step there is
asked for once and stands in for every contact; those it has keep their
place. Fixes are merged across snapshots at least 20 s apart, at most
240 a contact, and a contact is not drawn more than a minute before its
first fix.
2026-11-15 09:27:31 -08:00
Sameh Khamis b8a320edce Merge pull request #1748 from bilawalsidhu/weather/frame-maximum-level
Global clouds drawn from a feed's tiles to the level it names
2026-11-15 09:25:47 -08:00
Sameh Khamis dc045859f7 Changelog fragment for #1748 2026-11-15 09:14:49 -08:00
Sameh Khamis 97bce938c4 Global clouds drawn from a feed's tiles to the level it names
A weather feed that supplies its own tiles may name, per product, the
deepest level of the geographic tiling its tiles hold detail at
(frameMaximumLevel, 0-12). Global infrared is then drawn from those tiles
to that level, each given the regional infrared display transfer, rather
than from one 2048x1024 image cut to level 3. Other tiled products take
the named level in place of 6. A feed naming no usable level keeps the
layer's own detail.
2026-11-15 09:14:33 -08:00
Sameh Khamis 3d25a284f9 Merge pull request #1747 from bilawalsidhu/motion/vessels-frame-cadence
Move vessels every frame and ask for frames as they move
2026-11-14 23:46:38 -08:00
Sameh Khamis c2fa15b205 Merge branch 'main' into motion/vessels-frame-cadence 2026-11-14 23:37:10 -08:00
Sameh Khamis ec63345b3b Merge pull request #1746 from bilawalsidhu/motion/satellites-dead-reckon
Move satellites every frame between SGP4 samples
2026-11-14 23:36:59 -08:00
Sameh Khamis 52695daf5c fix(vessels): world-clock motion moves only drawn vessels, once per world time
Vessels out of view move on every 250 ms so one coming into view is current;
vessels at the end of their fixes ask for no frames; nothing moves while the
layer is off; 2D views judge the half-pixel step across the view's width; a
re-floor redraws vessels where they are on the next pass.
2026-11-14 23:30:38 -08:00
Sameh Khamis 7bea88b395 Add the changelog fragment for #1747 2026-11-14 23:19:27 -08:00
Sameh Khamis e4afde3317 Add the changelog fragment for #1746 2026-11-14 23:19:26 -08:00
Sameh Khamis 57bacd98a8 Move vessels every frame and ask for frames as they move
Vessels between two fixes, and live vessels a host placement places, were
redrawn at most every 250 ms, and a frame was asked for only once a second.
With nothing else asking for frames the scene drew vessels at about 1 to
2 fps live, and none at all while the world clock played at 1x.

They are now redrawn every frame the scene draws, moved in place without
new allocations. After each pass the layer works out how far the fastest
drawn vessel moved on screen and asks for the next frame for when it will
have moved another half pixel, at least once a second while any drawn
vessel moves. A vessel crossing the view close up therefore glides, and
one far away lets the scene idle. A frame already asked for later is
brought forward when a vessel speeds up.
2026-11-14 23:18:57 -08:00
Sameh Khamis e31de29ccc Move satellites every frame between SGP4 samples
Satellite points were propagated once a second and held still in between,
so while the world clock plays faster than real time they jumped: at
1 min/s, about 45 px once a second at globe scale.

Each SGP4 call now keeps a sample of the satellite's inertial position,
velocity, gravity and its rate of change (src/layers/satellites/motion.js).
Every frame each shown point is reckoned from its sample to the world time
and turned into the Earth-fixed frame by the sidereal angle, so points
glide at any play speed. Core satellites still take a fresh sample every
second, and at once when the world time is 30 s from it (fast play, a
seek), which keeps every point within about 10 m of SGP4. Starlink extras
take their first sample as they load and are resampled round-robin, more
per frame the faster time plays (up to 2,000 a frame); a point more than
two minutes from its sample waits for the next one. Hidden points are
moved when shown again, and the tracked satellite keeps its per-frame path.

Measured at globe scale: at 1 min/s points move on every frame, 0.4 px a
frame and at most 1.4 px (before: once a second, 45 px). With 11,880
satellites (Starlink on) the scene holds 60 fps, frames 16.7 ms median and
19.7 ms p95; reckoning costs 0.02 ms a frame for 1,342 points.
2026-11-14 23:18:28 -08:00
Sameh Khamis e4708a815d Merge pull request #1745 from bilawalsidhu/timeline/one-control-and-marks
One time control; the timeline marks launches and strong earthquakes, with labels
2026-11-14 21:24:45 -08:00
Sameh Khamis ac04812db2 A row plays only with a timeline to play; the speed shown follows the world clock; mark labels merge whole and cut by character
A weather row's play started the world clock even with no time to show,
where there is no timeline; it now does nothing then, as the timeline's
own Play cannot be reached. A weather layer made without a weather clock
does nothing once destroyed, so enabling it after builds no clock.

The timeline's speed follows the world clock's rate whoever set it, and
its Play runs at that rate, so it and a row's play never run at different
rates; a rate not offered shows as the nearest offered speed. Choosing a
speed sets the clock's rate first, also while a driver steps.

Marks merge on their whole label and are cut for showing after, so two
whose labels only differ past the cut stay two, and the cut counts
graphemes (code points where the runtime cannot tell them), so an emoji is
never split.

Tests that compared a DOM element with null built an assertion message
from the element when they failed, which hung the run; they compare plain
values now, so they fail at once. The timeline tests put the clock back to
real time after each.
2026-11-14 21:12:43 -08:00
Sameh Khamis 1dc2dbe4ea Name the changelog fragment for #1745 2026-11-14 20:55:43 -08:00
Sameh Khamis 620a337ce8 Weather rows play at the timeline's speed; the frame time shows under reduced motion; tidy the timeline's mark label
A weather row's play ran the world clock at whatever rate it had, and
going live set that back to 1, so the speed chosen on the timeline was
lost. The world clock now keeps its rate while paused and live, and the
timeline's speed sets it whenever it is chosen, so any play runs at it.
A row's play starts from the start of the covered time when live or at
its end, as the timeline's does, and does nothing while every product the
row shows is suspended, as its reduced-motion note says.

Live, the Weather panel's frame time is the newest of each product's
frames, suspended or not, so it no longer goes away under reduced motion,
on a hidden page or without an imagery host.

A weather layer made without a weather clock builds its own when first
enabled rather than when made, so a layer never turned on leaves the
world clock alone, and its own clock (createWeatherClock({ shared: false }))
leaves the world's time where it is when destroyed; only the last shared
weather clock sends the world live.

On the timeline, a zoom or a pan clears the hovered tick's label, a label
is never wider than the track and ends in an ellipsis, and a mark's label
is cut to 60 characters (WORLD_CLOCK_MARK_LABEL_LENGTH).

The changelog entry says what a row's step does, names the earthquake
layer's new exports and says it registers with the world clock.
2026-11-14 20:52:45 -08:00