benmichael/gods-eye-view
1
0 Fork 0
mirror of https://github.com/bilawalsidhu/gods-eye-view.git synced 2026-11-04 10:24:02 +00:00
Code Issues Packages Projects Releases Wiki Activity
2,062 Commits 27 Branches 5 Tags
c13c2fc1f0ffb2a46eab0e568dbf28e275f3a023
Commit Graph
2062 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
quanticsoul4772 c13c2fc1f0 Merge remote-tracking branch 'origin/main' into upstream/geocode-place-region 
# Conflicts:
#	docs/CURRENT-STATE.md
#	src/keylessGeocoder.test.mjs
 2026-10-25 17:32:07 -07:00
quanticsoul4772andClaude Opus 5.5 91769d74b8 fix(geocode): keep a nearby whole-name match as the last choice, and document the region rule 
A query with a comma counted as "place, region", so a nearby place whose
own name has a comma ("Bed, Bath & Beyond") no longer won the nearby pass
and the unbiased pass could fly to a namesake far away. Its whole-name
match is now kept as the last choice, after the region checks of both
passes. CURRENT-STATE describes the place-region rule.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
 2026-10-25 17:07:46 -07:00
Said Turksever a43ff8619e fix(search): normalize geocoder bias across the antimeridian (#1272) 
Keep geocoder viewport bias near the antimeridian and omit misleading wrapped viewboxes.

Contribution by @asturksever.
 2026-10-25 17:04:43 -07:00
quanticsoul4772 ba292ce475 fix(flights): keep ground-snap sampling after the clock steps back (#1399) 
Recover aircraft ground-height sampling after backward wall-clock changes while preserving sampling budgets.

Contribution by @quanticsoul4772.
 2026-10-25 16:58:14 -07:00
quanticsoul4772andClaude Opus 5.5 7775f6007d fix(geocode): a region match takes the place itself, not a name starting with it 
A name that only started with the place word also matched, so from Lyon
"Paris, France" picked "Paris Gare de Lyon" in the biased pass, where main
fell through to the unbiased answer and reached Paris. Only an exact name
matches now. Adds a test for the UK alias.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
 2026-10-25 16:56:33 -07:00
quanticsoul4772 a7da90fdfc fix(effects): run no sharpen pass when its slider is at 0 (#1398) 
Disable the sharpen pass when its intensity is zero.

Contribution by @quanticsoul4772.
 2026-10-25 16:51:56 -07:00
Sameh Khamis 5103ff672c fix(gbfs): exclude stations with invalid coordinates (#1232) 
Reject invalid bike-share station coordinates while preserving genuine zero coordinates and numeric aliases.

Contribution by @Bortlesboat.
 2026-10-25 16:47:51 -07:00
Sameh Khamis a07b5a65fd Merge current public main with PR #1232 2026-10-25 16:40:20 -07:00
quanticsoul4772andClaude Opus 5.5 5ef78b975c docs(changelog): note #1401 
Co-Authored-By: Claude Opus 5.5 <[email protected]>
 2026-10-25 16:38:42 -07:00
quanticsoul4772 52c6401483 Merge branch 'main' into upstream/geocode-place-region 2026-10-25 16:37:25 -07:00
quanticsoul4772andClaude Opus 5.5 1a61d02b7d fix(geocode): a 'place, region' query lands in the region, not on a namesake 
From Denver, 'Paris, Texas' flew to a pub in Budapest at rooftop range. The
camera-biased Photon answer listed the town first, but the pub's name equals
the whole query, and the biased path matched names only. A query with a
region now takes a candidate named for the place whose city, county, state,
country or country code (or USA/UK for US/GB) contains every word of the
region, in both the biased and the unbiased pass; with no such candidate
the existing name rules decide. A query with no region after its comma
keeps the biased name match.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
 2026-10-25 16:31:08 -07:00
Rudy Mizrahi Celekli 7bc86224e9 fix(route): phrase ramp and lane modifiers as directions (#1343) 
Correct ramp and lane instructions consistently in server output and localized browser text.

Contribution by @rudycelekli.
 2026-10-25 16:28:09 -07:00
Sameh Khamis 5ae22ac333 fix(awareness): wrap north-bound bearings (#1390) 
Wrap awareness bearing and course labels at north and register the formatting helper in package boundaries.

Contribution by @rudycelekli.
 2026-10-25 16:21:50 -07:00
Sameh Khamis f4b3517e9b Merge main into PR #1390 2026-10-25 16:15:38 -07:00
Said Turksever 2a3e0d669f Merge pull request #1395 from rudycelekli/fix/fires-tool-acquired-time 2026-10-25 21:32:37 +00:00
Sameh Khamis 9b52e83fd7 Merge main into PR #1395 2026-10-25 14:14:33 -07:00
Sameh Khamis 8886e063e6 fix(local-adsb): show a 359.7° track as TRK 0°, not TRK 360° (#1396) 
Wrap rounded local ADS-B track labels at north.

Contribution by @rudycelekli.
 2026-10-25 14:14:28 -07:00
Sameh Khamis 1ad472fecf fix(awareness): register and document bearing presentation 2026-10-25 14:08:32 -07:00
Sameh Khamis 6642176de5 docs: document Local ADS-B track rounding 2026-10-25 14:08:32 -07:00
Sameh Khamis 3de745bd33 fix(fires): reject rolled-over acquisition dates and document UTC times 2026-10-25 14:08:25 -07:00
Sameh Khamis d987149f17 Merge PR #1390 contribution for review 2026-10-25 14:07:14 -07:00
Sameh Khamis 9aeeb37ccf Merge PR #1396 contribution for review 2026-10-25 14:07:13 -07:00
Sameh Khamis 5ae18032fc Merge PR #1395 contribution for review 2026-10-25 14:07:10 -07:00
Rudy Celekli 224d71753b fix(fires): parse the detection time inside the tools package 
The tools package cannot import firmsCsv. Pad the FIRMS clock here so 00:45 UTC still reads as 00:45.
 2026-10-25 16:01:26 -04:00
Rudy Celekli 315c0f5dc6 fix(local-adsb): show a 359.7° track as TRK 0°, not TRK 360° 
The Local ADS-B card rounded the track without wrapping, so an aircraft
tracking 359.5° or more read "TRK 360°". The rounded track now wraps
to 0°.
 2026-10-25 15:58:46 -04:00
Rudy Celekli 57df5f61ba fix(fires): report a 00:45 UTC detection as 00:45, not "45" 
get_active_fires joined FIRMS acq_date and the unpadded acq_time, so a
detection at 00:45 UTC came back as "2026-01-01 45". The row now uses
acquisitionMsUtc, which pads the time, and reports an ISO UTC timestamp
like the other tool times.
 2026-10-25 15:58:45 -04:00
Said Turksever ac8dc84f3c docs: require screenshots, recording, category and data licence on new-layer PRs (#957) 
Document visual evidence, category and data licensing requirements for new layers, using the changelog fragment workflow.

Contribution by @asturksever.
 2026-10-25 12:43:01 -07:00
quanticsoul4772 69fba2ebbe fix(perf): free a turned-off layer's entities that Cesium keeps (#1367) 
Release stale Cesium command references after disabling a layer while preserving current-frame commands.

Contribution by @quanticsoul4772.
 2026-10-25 12:36:50 -07:00
Sameh Khamis 405c7f0d20 fix(cockpit): show wind from 359.6° as 0°, not 360° (#1389) 
Wrap rounded cockpit wind direction to zero degrees at north.

Contribution by @rudycelekli.
 2026-10-25 12:30:37 -07:00
Sameh Khamis e6e8bb0e95 Merge main into PR #1389 2026-10-25 12:26:21 -07:00
Sameh Khamis db74129eb0 fix(draw): show a 999.6 m line as 1.0 km, not 1000 m (#1388) 
Select drawn-line distance units after rounding metres.

Contribution by @rudycelekli.
 2026-10-25 12:26:14 -07:00
Sameh Khamis 8f02541657 docs: document PR #1389 rounding behavior 2026-10-25 12:11:49 -07:00
Sameh Khamis 1244ec1332 Merge PR #1389 contribution for review 2026-10-25 12:11:49 -07:00
Sameh Khamis 6ebdee6710 docs: document PR #1388 rounding behavior 2026-10-25 12:11:19 -07:00
Sameh Khamis 1031569f47 Merge PR #1388 contribution for review 2026-10-25 12:11:19 -07:00
Said Turksever 769ecbfe98 Merge branch 'main' into fix/cockpit-wind-north 2026-10-25 18:51:44 +00:00
Rudy Celekli 63866c201a fix(awareness): wrap north-bound bearings 2026-10-25 13:28:23 -04:00
Rudy Celekli 5ef12391e1 fix(cockpit): show wind from 359.6° as 0°, not 360° 
formatCockpitWindDirection rounded the bearing and printed that number, so wind from 359.5° or more read "N · 360°". Take the rounded degrees modulo 360 so north reads 0°.
 2026-10-25 12:32:18 -04:00
Rudy Celekli 99429904d4 fix(draw): show a 999.6 m line as 1.0 km, not 1000 m 
formatMeasure checked the raw length against 1000 but printed it rounded, so a drawn line of 999.5 m or more read "1000 m" in the hint. Compare the rounded metres so it moves to kilometres.
 2026-10-25 12:32:10 -04:00
quanticsoul4772 496d024431 fix(hud): drop a summary reply once the camera starts moving (#1384) 
Discard stale HUD summaries when camera movement starts and allow cancelled requests to retry for unchanged place context.

Contribution by @quanticsoul4772.
 2026-10-25 09:18:22 -07:00
Sameh Khamis 5b6c52437e fix(awareness): show a 999.6 m contact as 1.0 km, not 1000 m (#1387) 
Choose awareness distance units after rounding so nearby contacts never display as 1000 metres.

Contribution by @rudycelekli.
 2026-10-25 09:07:36 -07:00
Sameh Khamis ba783b4eea Merge main into PR #1387 2026-10-25 09:01:32 -07:00
Sameh Khamis 81af549ad7 fix(directions): show a 996 m leg as 1.0 km, not 1000 m (#1386) 
Choose route distance units after rounding so near-kilometre legs display in kilometres.

Contribution by @rudycelekli.
 2026-10-25 09:01:26 -07:00
Sameh Khamis 3cd795527c Merge main into PR #1386 2026-10-25 08:55:23 -07:00
Sameh Khamis 3f9b44ecc8 fix(directions): show a 59.6-second leg as 1 min, not 60 s (#1385) 
Choose route duration units after rounding so near-minute legs display as one minute.

Contribution by @rudycelekli.
 2026-10-25 08:55:17 -07:00
Sameh Khamis 48e649a95e docs(directions): scope the distance rounding threshold precisely 2026-10-25 08:50:11 -07:00
Sameh Khamis 455dbf2b5f docs: clarify unit transition examples 2026-10-25 08:49:00 -07:00
Sameh Khamis 4d64ac48bc docs: clarify unit transition examples 2026-10-25 08:48:58 -07:00
Sameh Khamis c30d2d3473 docs: document PR #1387 rounding behavior 2026-10-25 08:48:37 -07:00
Sameh Khamis d8d3ac85b6 Merge PR #1387 contribution for review 2026-10-25 08:48:36 -07:00