Open Waters: Releases

Earth perihelion and aphelion (Almanac 0.11.0)

Sun, 18 Oct 2026 13:05:46 GMT

Almanac 0.11.0 adds Earth perihelion and aphelion events in TypeScript, Swift, and Kotlin.

earthApsides(startUtc, endUtc) / earthApsides(from:to:) returns the sorted perihelion and aphelion events in a half-open window. Each carries its time, its kind (perihelion or aphelion; EarthApsisKind in Swift and Kotlin), and distanceKm, the geometric Sun–Earth centre distance at that instant.
The search brackets each root in fixed cells anchored at J2000, as the season and lunar apsis searches do, so every window containing an event reports the same millisecond.
The contract defines the model and tolerances, and the README shows the call in each language.

The search translates Astronomy Engine's SearchPlanetApsis for Earth. A pinned, independently compiled Astronomy Engine run is committed as an implementation oracle for all 302 events from 1950 through 2100. Every event matches, with a worst timing difference of 1.525 seconds and a distance difference below a millimeter, against tolerances of 2 seconds and 1 meter. This verifies the translation; it makes no separate physical-accuracy claim. Cross-port parity checks the new events in all three ports, and the release workflow verifies all three suites, Kotlin coverage and source consumption, and independent SwiftPM and packed npm consumers before publishing with provenance.

npm install @openwaters/almanac@0.11.0

import { earthApsides } from '@openwaters/almanac';
for (const { kind, time, distanceKm } of earthApsides(start, end)) console.log(kind, time.toISOString(), distanceKm);

.package(url: "https://github.com/openwatersio/almanac.git", exact: "0.11.0")

Kotlin consumers can pin the v0.11.0 source checkout using the installation guide. No Maven artifact is published.

Earth apsides: #82. CI Node versions from mise: #80. Release preparation: #83.

Full changelog.

Depth bands and isobaths from zoom 4 (Seascape style 0.4.0)

Fri, 16 Oct 2026 13:28:24 GMT

The style for the v2026.10.16 tiles.

Bands mode and isobaths start at z4 instead of z6 (#214).
The coarse depth ladders carry the 10 and 20 m contours, so shallow seas split into bands at low zoom (#214).
BANDS_MIN_ZOOM is exported for apps that switch between Bands and Relief.

Shallow seas split into depth bands at low zoom (Seascape 2026.10.16)

Fri, 16 Oct 2026 13:06:27 GMT

Shallow seas no longer turn into one solid blue band at low zoom, and Bands mode is a compiled chart partition from z4 up.

Chart fixes

Shallow seas split at 10, 20 and 50 m at low zoom (#214). The coarse tiers carried no isobath shallower than 50 m (z7 to 8) or 200 m (z6), so a shallow sea like the Kattegat or the North Sea painted one band in the darkest tint. Each tier now follows NOAA's ENC Design Handbook contour set for its scale, plus the 10 and 20 m contours wherever that set lacks them.
Bands mode and isobaths start at z4 (#214). A new z4 tier with the Overview contour set replaces the raster handoff at z5, so the shelf no longer changes tint between z5 and z6.
Isobaths follow the seabed at z7 to z10 (#214). Each tier is cut one zoom finer than before and keeps a vertex per pixel at the last zoom it serves. At z8 over the Kuril arc the median segment went from 6.4 to 3.9 px.
Depth bands below 4,000 m and in the deepest trenches (#214). Water deeper than a tier's deepest contour got no band at all: the deep ocean at z4 to z6, and trenches past 10,000 m or 5,000 fathoms at every zoom. A floor below the deepest ocean closes it.
Shoal soundings show with their ring (#214). A least depth inside a 10 to 100 m contour now shows from the zoom that contour draws at.

Pipeline

Coarse tiers reuse the native tier's tidal-water union, the cost that dominated the slowest stems: the Arctic stem 4-3-3-8 went from 316 to 101 minutes (#214).
The low-zoom vector bundle writes below its top zoom at detail 11, so the Philippines z4 tile fits under tippecanoe's size ceiling (#215).
Every commit that touches the style or viewer gets a viewer preview, and the style package now releases from style-v* tags once the live tiles carry its pipeline (#213).

Seascape is not an official Electronic Navigational Chart and is never a replacement for one. Not for navigational use.

Soundings placed at the transducer, none lost or sent twice; requires Node 24 (Crowd depth 1.3.0)

Thu, 15 Oct 2026 19:55:06 GMT

More accurate soundings, and none lost or sent twice.

Requires Node 24. Signal K servers running an older Node need to upgrade before installing this version (#115).

Positions at the transducer: each sounding's position is moved from the GPS antenna to the transducer using your heading, or your course over ground while you are moving faster than about 1 knot. A sounding that can't be placed this way is no longer uploaded with the antenna's position (#134)
Correct depth reference: reports say what depths are measured from: the waterline, the transducer, or unknown. Depths read through the History API now get the same transducer depth or draft correction as live data, and the transducer depth below the waterline is optional (#128)
Sensor offsets in the standard frame: report metadata gives sensor positions from the transducer, as forward, starboard and down (#129)
Late history providers: after a restart, the plugin waits up to 10 minutes for a history provider such as signalk-to-influxdb2 to come up, recording meanwhile, before it settles on its own storage (#132)
No lost or duplicate soundings: each report stops 5 minutes short of the current time, so soundings a history provider is still writing go out in the next report instead of being skipped. A sounding stamped exactly on a report boundary is sent once, not twice. BATHY_REPORT_DELAY changes the delay (#136)
End-to-end tests: CI now uploads soundings through a real Signal K server and checks them against the CSB schema, and runs on pull requests from forks (#131)
Dependency updates (#114)

Thanks to @dirkwa for most of this release.

Depth areas, isobaths, and soundings compiled per zoom level (Seascape 2026.10.15)

Thu, 15 Oct 2026 18:01:52 GMT

Depth areas and isobaths are now compiled per zoom tier, the way an ENC is compiled per usage band, and the soundings follow chart practice for selection and rounding.

Chart fixes

Depth areas and isobaths compiled per zoom (#195). Each zoom tier (z6, z7 to 8, z9 to 10, z11 to 12, z13 and up) is its own complete partition, cut from the bathymetry at that tier's resolution with the isobath ladder a chart draws at that scale. Zooming out can only shoal, never deepen, and bands too small to read at a tier's scale merge into their shallower neighbour. A coarse source viewed closely shows its own content rather than 2 m bands interpolated from kilometre cells. The emphasized safety contour follows the ladder drawn at each zoom.
Low-zoom isobaths keep their shape (#210). At z6 to z9 the lines had been thinned to long straight segments across shelves and island arcs; they now keep a vertex per pixel and draw with round joins.
No more false shallow water along ditches and small canals (#196). Under coarse sources, polder ditches and canals narrower than the source's own cell had read as 0 to 2 m depth bands with soundings on them (the Haarlemmermeer). Water narrower than the source cell now stays land in that source and shows as unknown depth.
Exact datum is unknown water, never foreshore (#195). A depth of exactly 0 is the land sentinel and the fill for water a source holds no depth for; it no longer draws as drying.
Unknown-depth water fills no longer compound (#195). Abutting water polygons inside a lake had overlapped into a dark lattice along every outline; the fills now dissolve per tile.
Soundings in line with chart standards (#180). The selection keeps the least depths a chart ranks first (the 1 m floor that discarded real shoals is gone), rounds toward the shoal side, and thins by the chart's spacing rules.
No more horizontal stripes across the map at fixed latitudes (#192). Unknown-water rows on the easternmost tiles had wrapped around the antimeridian.

Pipeline

Depth-area tier files declare their full read sets, so a bbox smoke and a planet build heal the same stems (#195); the vector archive's census measures each feature at its own tier's zoom (#195); a bundle whose tiles overflowed fails instead of merging bands (#210).
Depth-area contouring uses upstream GDAL's fast polygon mode (#193); the planet build aborts early when the box's disk can't hold the run (#178) and stops a doomed build sooner (#194); a GEOS overlay failure on one stem no longer stops the planet (#208).

Seascape is not an official Electronic Navigational Chart and is never a replacement for one. Not for navigational use.

Is available on the App Store (Slackwater for iOS 1.14.0)

Wed, 14 Oct 2026 19:48:18 GMT

Welcome to the first release of Slackwater, the tides & currents app that works offline where you need it — on the water, at the beach, in the anchorage. View past, present, and future predictions at thousands of stations worldwide, already on your phone.

Tide and current predictions on a timeline you can scrub, with sun, Moon, and eclipse events alongside.
A station map and search, and nearby tide and current stations on every station page.
Canadian tides and currents from CHS, downloaded for offline use.
Home-screen widgets for the next event and today's tide curve.
An Apple Watch app with tide and current complications, scrubbed with the Digital Crown.
Calendar and notification alerts for slack windows, tides, and eclipses.
Ask Siri for the next high tide, low tide, or slack window.
Available in 14 languages.
Slackwater Premium is an optional purchase; the offline core is free and stays free.

Slackwater on the App Store

Requires Swift 6 (Almanac 0.10.0)

Tue, 13 Oct 2026 08:34:39 GMT

Almanac 0.10.0 uses Swift 6 language mode and requires a Swift 6 or newer toolchain.

Swift's compiler checks the package and its tests under Swift 6 concurrency rules. Immutable event specifications have a checked Sendable conformance.
The public astronomy API and calculations are unchanged. TypeScript and Kotlin consumers use the same API as 0.9.0.
Slackwater's iOS consumer validation passed Debug and unsigned Release builds for the phone, watch, and both widget extensions, including watch hardware's arm64_32 architecture. All 170 selected sun, moon, eclipse, alert, and timeline integration tests passed.

npm install @openwaters/almanac@0.10.0

.package(url: "https://github.com/openwatersio/almanac.git", exact: "0.10.0")

Kotlin consumers can pin the v0.10.0 source checkout using the installation guide. No Maven artifact is published.

Swift 6 migration: #78. Release preparation: #79.

Full changelog.

Check whether the Sun is up (Almanac 0.9.0)

Mon, 12 Oct 2026 21:45:17 GMT

Almanac 0.9.0 provides an instantaneous sunrise-based day/night decision in TypeScript, Swift, and Kotlin.

sunIsUp(time, observer, heightAboveGroundM = 0) returns whether the Sun’s upper limb clears the modeled horizon. It uses the same changing solar radius, standard refraction convention, topocentric geometry, and optional horizon dip as sunEvents sunrise and sunset.
Polar day and night work without an event search or a calendar-day choice. The helper preserves the existing date, observer, and eye-height validation. Exact equality with the horizon target returns false.
The cookbook shows display-mode recipes in all three languages, explains eye height versus elevation, and leaves refresh timing and missing-position handling to the application. The astronomical model does not account for terrain, clouds, or eclipses.

Tests cover independent USNO sunrise/set evidence, midnight sun, polar night, raised horizons, and a grazing polar sunrise where a fixed threshold on refracted altitude reports night. Cross-port parity checks the boolean exactly. The release workflow verifies all three suites, Kotlin coverage and source consumption, and independent SwiftPM and packed npm consumers before publishing with provenance.

npm install @openwaters/almanac@0.9.0

import { sunIsUp } from '@openwaters/almanac';
const mode = sunIsUp(new Date(), observer) ? 'day' : 'night';

.package(url: "https://github.com/openwatersio/almanac.git", exact: "0.9.0")

Kotlin consumers can pin the v0.9.0 source checkout using the installation guide. No Maven artifact is published.

Day/night helper and cookbook: #75. Release preparation: #76.

Full changelog.

Kotlin port, angle helpers, and tested migration guides (Almanac 0.8.1)

Mon, 12 Oct 2026 14:51:19 GMT

Almanac 0.8.1 provides shared angle conversion helpers and tested migration guides, with the public astronomy API available in TypeScript, Swift, and Kotlin.

degreesToRadians and radiansToDegrees preserve signed angles and full turns without wrapping. Non-finite inputs and conversion overflow raise validation errors.
The SunCalc guide and Astronomy Engine guide cover event windows, polar crossings, refraction, phase conventions, and supported-range boundaries, with tested examples.
The native Kotlin/JVM port shares the public contract and fixture corpus with TypeScript and Swift. It supports Java 8 bytecode and Android API 26+, and is consumed through a pinned source checkout; no Maven artifact is published.
Equinox and solstice searches, lunar perigee and apogee searches, and the equation of time are available in all three ports. The accuracy contract records their evidence and limits: measured worst errors are 79 seconds for seasons through 2050, 14.8 minutes and 54 kilometers for lunar apsides, and 1.0 second for the equation of time.
The packed npm package is checked with static ESM imports, dynamic imports, and synchronous CommonJS loading on Node 22.12 and 24.

Local validation for the conversion helpers and guides passed 245 TypeScript tests, 204 Swift release tests, and 79 Kotlin tests, with 100% handwritten Kotlin line coverage. The release workflow runs all three suites, fixture checks, and independent npm and SwiftPM consumers before publishing.

npm install @openwaters/almanac@0.8.1

.package(url: "https://github.com/openwatersio/almanac.git", exact: "0.8.1")

Angle helpers and migration guides: #73. Kotlin port: #70. Seasons, apsides, and equation of time: #68. Benchmarks: #69. Release preparation: #74.

Full changelog.

Uranus and Neptune, plus guides for moving from SunCalc and Solar (Almanac 0.8.0)

Sun, 11 Oct 2026 03:43:06 GMT

Almanac 0.8.0 adds Uranus and Neptune, the Sun and Moon events apps need to move off SunCalc, and migration guides for SunCalc and Solar, in TypeScript and Swift.

sunAltitudeEvents(startUtc, endUtc, observer, altitudeDeg) finds the Sun crossing any altitude, rising and falling: golden hour at +6°, blue hour, or SunCalc's addTime angles, which mean the same thing here. At −6° it returns the same instants as civil twilight.
sunTransits and moonTransits find upper and lower transits, so solar midnight and the Moon's highest and lowest points are available alongside rise and set.
moonOrientation(time, observer) gives the position angle of the Moon's bright limb and its parallactic angle; subtracting one from the other gives the bright limb's angle from the zenith, which is what drawing the Moon as it looks needs.
Uranus and Neptune support every planetary API: Sun-centered vectors, apparent positions, altitude and azimuth, illumination, approximate magnitude, solar elongation, and rise and set.
Migrating from SunCalc and Migrating from Solar map every export of those libraries to an Almanac call and give drop-in adapters; both test suites run the guides' code verbatim against output recorded from SunCalc 2.1.1 and Solar 4.0.1. How Almanac compares sets it beside SunCalc, Astronomy Engine, astronomia, Solar, SwiftAA, and EDSunriseSet, including where they are the better choice.

Existing functions return the same results, and no existing enum gains a case.

New quantity	Evidence	Worst	Limit
Sun altitude crossings at +6°, −0.3°, −4°, −8°	124 crossings on Horizons one-minute grids, 20°N to 70.5°N	5.6 s	60 s
Upper and lower transits, Sun and Moon	Horizons hour-angle grids	1.1 s	60 s
Moon upper transit, Sun and Moon lower transit	54 USNO rows	27.5 s	60 s
Parallactic angle	Horizons azimuth, elevation, and declination	0.18′	1′
Bright limb, elongation 20°–160°	Meeus 48.5 on Horizons apparent positions	0.42′	1′
Uranus, Neptune Sun-centered position	Horizons, 1950–2100	0.00035 AU	0.001 AU

Against SunCalc 2.1.1 the migration adapters agree within 7 seconds on Sun times and 4 seconds on moonrise and moonset. Against Solar 4.0.1 they agree within 59 seconds from 34°S to 49°N; at 78°N, where the Sun grazes the twilight altitudes, the worst is 449 seconds.

Validation includes 216 TypeScript tests, 178 Swift release tests, offline fixture regeneration, cross-port parity, and Apple Watch compilation. Every existing benchmark workload stays inside the 20% regression limit. A year of Sun altitude events takes about 21 ms in TypeScript and 12 ms in Swift, and a year of Sun or Moon transits about 7 ms and 4 ms; timings vary by machine.

Fixture metadata records each Horizons request's own retrieval date, checked against the raw response headers.

npm install @openwaters/almanac@0.8.0

.package(url: "https://github.com/openwatersio/almanac.git", exact: "0.8.0")

Uranus and Neptune: #59. SunCalc parity and migration guide: #62. Solar migration guide: #65. Library comparison: #64. CI lockfile checks: #60, #66. Release preparation: #67.

Full changelog.

App Store screenshots in Navionics and Aqua Map (Signal K AIS plugin 0.6.3)

Fri, 09 Oct 2026 19:38:47 GMT

The plugin's App Store page has screenshots of aiscast traffic in Navionics and Aqua Map, which receive it from the Signal K server as NMEA 0183 over Wi-Fi.

Accurate course, heading, and turn rate from NMEA 2000 receivers (Signal K AIS plugin 0.6.2)

Fri, 09 Oct 2026 12:56:55 GMT

Traffic your NMEA 2000 AIS receiver hears reaches Open Waters AIS more faithfully. A vessel steering just west of north no longer has its course and heading sent as not available, a turn's rate is no longer rounded down, and a position report that leaves out the navigation status or rate of turn now says so, where it used to claim the vessel was under way using its engine and not turning.

Renamed to Open Waters AIS (Signal K AIS plugin 0.6.1)

Fri, 09 Oct 2026 11:40:56 GMT

The plugin is now called Open Waters AIS, in Plugin Config and in the App Store, where it was AIScast. It is the same plugin: the package is still signalk-aiscast, your settings and station carry over, and nothing about how it shares or receives traffic has changed.
The plugin has an icon in the App Store, and its page there suggests signalk-buddylist-plugin, which lets you follow buddy boats on Open Waters AIS far beyond VHF range.

Horizon dip and planetary motion (Almanac 0.7.0)

Tue, 06 Oct 2026 17:57:02 GMT

Almanac 0.7.0 provides apparent horizon dip and native planetary motion in TypeScript and Swift, with Earth included for solar-system views.

horizonDip(observer, heightAboveGroundM) gives the apparent altitude of an unobstructed horizon, accounting for Earth shape and terrestrial refraction. Eye height above the surface is separate from elevation above sea level; body altitudes remain relative to the horizontal plane.
Sun and Moon rise/set, local solar eclipse searches, and lunar eclipse visibility accept optional eye height. The default of zero preserves existing calls and results. Twilight and transit retain their definitions.
Mercury, Venus, Mars, Jupiter, and Saturn have apparent positions, refracted altitude/azimuth, point-center rise/set, illumination, approximate airless visual magnitude, and solar elongation through planetPosition, planetAltAz, planetEvents, and planetIllumination. Viewing windows combine these quantities with the consumer's twilight and observing policy.
planetHeliocentricPosition accepts those five planets and Earth. It returns geometric Sun-centered xAu, yAu, and zAu in fixed J2000 equatorial coordinates. Earth-based planetary queries reject Earth.

Planetary geometry is checked against JPL Horizons across 1950 through 2100, including both supported boundaries, conjunctions, near-zenith tracks, and polar grazing rise/set pairs. Angular limits remain one arcminute, physical range and heliocentric vector limits are 0.001 AU, and event limits are 60 seconds. Magnitudes are approximate: the pinned model differs from Horizons by up to 0.75 magnitudes for extreme Venus crescents in the retained evidence. Saturn's magnitude includes its rings.

Validation includes 193 TypeScript tests, 155 Swift release tests, offline fixture regeneration, cross-port reproduction within 5 scaled units / 100 ms, and Apple Watch hardware and simulator compilation. All 30 benchmark workloads pass the 20% regression limit in both ports. On the local machine, the five-planet 228-hour sky track takes about 17.2 ms in TypeScript and 6.5 ms in Swift; timings vary by machine.

The library retains zero runtime dependencies and zero runtime data files. Plans and specs live in #51; the repository contains the maintained API contract and scope.

npm install @openwaters/almanac@0.7.0

.package(url: "https://github.com/openwatersio/almanac.git", exact: "0.7.0")

Documentation scope: #50. Apparent horizon: #52. Planetary motion: #53. Release preparation: #55.

Full changelog.

Tide widget for chart plotters (Signal K tides plugin 2.2.0)

Fri, 02 Oct 2026 17:34:17 GMT

New Features

feat: offer a tide widget to chart plotters (#139)

Maintenance

Group vitest and @vitest/* Dependabot updates (#137)

Tiles at half the size, with land areas (Maritime zones 0.2.0)

Thu, 01 Oct 2026 20:11:45 GMT

Maritime zone tiles for @openwaters/maritime-zones 0.2.0. The package downloads the tiles it needs from this release and checks each against the sha256 in tiles.json.

636 seekable zstd tiles (256 KiB frames, level 19), 142 MB in total. Sizes and SHA-256 cover the compressed downloads.

Zone and boundary features: Marine Regions Maritime Boundaries Geodatabase (Flanders Marine Institute), CC-BY 4.0. Land features: Flanders Marine Institute (2020). World Countries Geodatabase, CC-BY 4.0, adapted from ESRI World Countries 2014 with DeLorme (2014) source data. Country polygon rings come from MarineRegions:worldcountries_esri_2014 and include inland borders and holes. The source hashes are recorded in upstream.lock.json. Marine Regions land_v9 is not used.

VLIZ has approved derived-tile redistribution and the monthly upstream-check load. Maintainers monitor Marine Regions updates to avoid distributing deprecated versions. World Countries supplies a proxy for normal baselines, not a complete legal-baseline model. The v0.1.0 release uses OpenStreetMap coastlines and retains its own NOTICE and ODbL 1.0 terms. npm publication is authorized and follows the matching tile release; see CONTRIBUTING.md for publishing instructions.

Internal Waters (v4, world, 2023): 113 features
Archipelagic Waters (v4, world, 2023): 23 features
Territorial Seas (12 NM) (v4, world, 2023): 230 features
Contiguous Zones (24 NM) (v4, world, 2023): 220 features
Exclusive Economic Zones (200 NM) (v12, world, 2023): 285 features
High Seas (v2, world, 2024): 1 feature
World countries (ESRI, 2014): 294 features

Not for navigation. Marine Regions data "is not meant to be used for legal, economical … or navigational purposes" and "has no legal value whatsoever". See the attached NOTICE for the citation and licence of each layer.

Stations named after your boat, and signed token requests (Signal K AIS plugin 0.6.0)

Thu, 01 Oct 2026 14:00:50 GMT

Your station on aiscast takes your boat's name, the vessel name set in Signal K, while Share my own ship is on. Turning that switch off removes the name, so the station never says where the boat is. There is nothing to set up.
The plugin signs its token requests with the boat's key, so nobody else can get a token for your station. After the upgrade it requests a new token once.
Plugin Config shows the address of this boat's station page on openwaters.io under Advanced → Access token, to copy into a browser, so you can see what your receiver is contributing.
A pasted token that aiscast refuses now says how to fix it: clear Advanced → Access token and the plugin goes back to its own token. Tokens from openwaters.io/ais/token that are bound to a network address stop working when that address changes, as it does on Starlink and cellular. The plugin's own token works from any address.

First maritime zone tiles (Maritime zones 0.1.0)

Thu, 01 Oct 2026 02:59:09 GMT

Maritime zone tiles for @openwaters/maritime-zones 0.1.0. The package downloads the tiles it needs from this release and checks each against the sha256 in tiles.json.

586 seekable zstd tiles (256 KiB frames, level 19), 282 MB in total. Sizes and SHA-256 cover the compressed downloads.

Zone and boundary features: Marine Regions Maritime Boundaries Geodatabase (Flanders Marine Institute), CC-BY 4.0. Coastline features: © OpenStreetMap contributors, ODbL 1.0. The source archive is recorded in upstream.lock.json. Marine Regions land_v9 is not used.

This is an experimental release while VLIZ's confirmation of derived-tile redistribution is pending. The release and Pages mirror may be removed. The package remains private and is not published to npm.

Internal Waters (v4, world, 2023): 113 features
Archipelagic Waters (v4, world, 2023): 23 features
Territorial Seas (12 NM) (v4, world, 2023): 230 features
Contiguous Zones (24 NM) (v4, world, 2023): 220 features
Exclusive Economic Zones (200 NM) (v12, world, 2023): 285 features
High Seas (v2, world, 2024): 1 feature
OpenStreetMap coastlines (WGS84), ODbL 1.0: 879204 features

Where each solar eclipse is greatest (Almanac 0.6.0)

Sun, 27 Sep 2026 22:12:39 GMT

Almanac 0.6.0 reports where greatest eclipse falls for every solar eclipse on Earth, including partial eclipses, in TypeScript and Swift.

GlobalSolarEclipse gains greatestLatitudeDeg, greatestLongitudeDeg, and greatestObscuration, present for every eclipse. For a total or annular eclipse they equal the ground point. When the Moon's shadow axis misses the Earth, as it does for every partial eclipse and a few non-central annular and total ones, they give the point on the Earth's limb nearest the axis, where the Sun's center is on the geometric horizon, and the fraction of the Sun covered there. latitudeDeg, longitudeDeg, and obscuration keep their meaning and are still null for a partial eclipse.
Swift's GlobalSolarEclipse public initializer takes the three new values as required arguments, so code that constructs the struct by hand needs updating.

The point is checked against the Espenak Five Millennium Catalog for all 122 eclipses from 1950 through 2100 whose axis misses the Earth, 115 partial and 7 non-central:

Quantity	Worst residual	Tolerance
Point against the catalog's whole-degree coordinates	0.63°	1°
Geometric Sun altitude there	0.0011°	0.01°
Local search placed there: peak against greatest eclipse	0.95 s	2 s
Local search placed there: obscuration	about 1e-9	1e-6

The local search placed at the point also reports the catalog's kind for all 122. The performance comparison showed no regression in either port. Validation includes 178 TypeScript tests, 137 Swift release tests, and the shared fixture and parity checks.

npm install @openwaters/almanac@0.6.0

.package(url: "https://github.com/openwatersio/almanac.git", exact: "0.6.0")

Greatest eclipse for partial solar eclipses: #43, #44, #45.

Full changelog.

Solar eclipses anywhere on Earth, with central lines (Almanac 0.5.0)

Sun, 27 Sep 2026 18:21:24 GMT

Almanac 0.5.0 adds solar eclipses anywhere on Earth, and the central line of each total or annular eclipse, in TypeScript and Swift.

nextGlobalSolarEclipse(after:) / nextGlobalSolarEclipse(after), previousGlobalSolarEclipse(before:) / previousGlobalSolarEclipse(before), and globalSolarEclipses(from:to:) / globalSolarEclipses(from, to) find solar eclipses with no observer. Each result carries the time of greatest eclipse, the shadow axis's distance from the Earth's center, and where the axis meets the ground, with the kind (partial, annular, or total) and obscuration seen from there. When the axis misses the Earth, the eclipse is partial, with no ground point.
solarEclipseAxisPoint(at:) / solarEclipseAxisPoint(time) gives where the shadow axis meets the ground at any instant, or nothing when it misses.
solarEclipseCentralLine(peak:stepSeconds:) / solarEclipseCentralLine(peak, stepSeconds) traces the central line from where the axis first touches the Earth to where it leaves. Interior points fall on whole multiples of the step since the Unix epoch, which defaults to 60 seconds, so a line at a step that is a whole multiple of another samples a subset of its instants.
The shared performance harness gains five global workloads. benchmarks/run.mjs --skip '^global/' leaves them out when the comparison base predates 0.5.0.

The global search finds all 337 solar eclipses from 1950 through 2100 in the Espenak Five Millennium Catalog, with no extras, and every kind matches. The central line is checked against NASA's path tables for six central eclipses, at the same dynamical time:

Quantity	Worst residual	Tolerance
Greatest eclipse, 337 eclipses	8.2 s	60 s
Axis distance against catalog gamma	4.1 km	5 km
Ground point, 202 eclipses with the axis under 6,100 km	0.66°	1°
Central line against NASA path tables	3.1 km, 4.9 s	5 km, 60 s
Central line of the grazing 2044-08-23 eclipse	9.4 km, 8.1 s	15 km, 60 s
Annular obscuration against the diameter ratio squared	0.0010	0.002
Local search at 953 central-line points: peak	0.40 s	2 s

The hosted CI comparison measured these median query times, in milliseconds:

Workload	TypeScript	Swift
Next global solar eclipse	0.22	0.16
Previous global solar eclipse	0.18	0.12
Global solar eclipses / 228 hours, no new moon	0.006	0.005
Global solar eclipses / 1950–2100	149	111
Central line of 2024-04-08, 60 s step	1.3	1.0

Both revisions used the same harness and toolchain within each port, with seven interleaved process pairs and 300 ms warmup. No existing workload moved by more than 2.6% in either port. Validation includes 174 TypeScript tests, 133 Swift release tests, and the shared fixture and parity checks.

npm install @openwaters/almanac@0.5.0

.package(url: "https://github.com/openwatersio/almanac.git", exact: "0.5.0")

Global solar eclipses: #39, #40, #42. Development and toolchain: #36. Dependency updates: #37.

Full changelog.

Works with the new contributor station names (Signal K AIS plugin 0.5.2)

Sat, 26 Sep 2026 14:36:00 GMT

Works with aiscast's new names for contributing stations. aiscast now files every contribution as station:<key>, which 0.5.1 does not recognize, so it took its own reports coming back from the server for traffic from another station. The loop guard then held back the boat's receiver when it heard an identical report again, such as a nearby vessel's unchanged static data, and that report never reached aiscast. The plugin recognizes its own reports under the old and new names, and with an operator-issued token as well as one it minted itself.

Permanent station slugs, Alaska panhandle gauges, and Dutch tide fits (Slackwater database 0.10.20260924)

Thu, 24 Sep 2026 15:48:44 GMT

Publish the Alaska panhandle's NOAA gauges in Alaska (#177)
Re-import NOAA stations after the state fix (#178)
Exit non-zero when the NOAA importer or LAT/HAT scripts crash (#180)
Fit Rijkswaterstaat tide heights with harmonics (#182)
Remove numeric subdivision codes from station locations (#183)
Distinguish nearby stations that share a name (#186)
Keep a published slug for good, record every move as a redirect, and merge the ten BC pairs (#189)
Keep a published bare slug through a name collision (#190)
Publish the database rewrite as 0.10 (#193)

Swift package by URL and cleaner station names (Slackwater database 0.9.20260923)

Wed, 23 Sep 2026 05:25:54 GMT

Let Swift apps depend on the tide database by URL (#162)
Evaluate Kartverket tide-height coverage for Norway (#163)
Refresh UHSLC research-quality datums from live RQD (#140)
Stop station name cleanup damaging brackets, possessives and Mc names (#166)
Read a subordinate station's tidal range without resolving its reference yourself (#169)
Fix capitalized station names and repeated state codes (#171)
Label cross-border gauges by location instead of publisher (#173)
Prototype Rijkswaterstaat tide prediction data (#172)
Move NOAA current ingestion into the tide database (#175)

Water body names and boat rentals (Seamap 0.3.1)

Tue, 22 Sep 2026 23:05:08 GMT

Name islands, bays, straits, and other water bodies (#71)
Quieter restricted-area fills and paper-style boundaries (#70)
Show boat rentals on the chart (#75)
Serve label glyphs from the Open Waters font stack (#77)
Fix seamarks not showing on the chart (#85)

One-file database with a Swift reader and current stations (Slackwater database 0.9.20260921)

Mon, 21 Sep 2026 18:35:48 GMT

Stop loading baltic-sea.geo.json as a phantom station (#128)
Package the database as a single FlatBuffers file (#123)
Fix mise npm version for installs (#137)
Reorganize the repo into workspace packages (#130)
Swift package for reading the database (#129)
Unify tide and current station metadata (#131)
Include current stations in the XTide tide database (#143)
Place stations by the bay or strait they sit in (#145)
Credit TICON-4's authors and state what we change (#158)
Document Rijkswaterstaat tide coverage and offline format (#156)
Give every station a ready-to-display attribution (#159)
Ship a single tide file instead of separate metric and imperial ones (#147)

Names, call signs, and dimensions on chartplotters (Signal K AIS plugin 0.5.1)

Mon, 21 Sep 2026 16:53:13 GMT

Chartplotters now show names, call signs, and dimensions for aiscast targets. aiscast sends a vessel's static data only when it changes, so for most aggregated targets the only copy arrives in the snapshot on connect, which the NMEA 0183 relay held back. The plugin now keeps the latest static data for each target, sends it right after the target's first live position, and repeats it with a position every 6 minutes while the target stays live.

Open Waters AIS traffic on NMEA 0183 chartplotters (Signal K AIS plugin 0.5.0)

Mon, 21 Sep 2026 13:25:27 GMT

New Receive setting, on by default: Send aiscast traffic to NMEA 0183 output. Targets injected from aiscast are re-emitted as !AIVDM on the nmea0183out event, so chartplotters and tablet apps reading the server's NMEA 0183 connections see over-the-horizon traffic, not only the Signal K apps. Only aiscast-sourced targets are relayed, and in Always mode a target the local receiver already covers is left out, so nothing is duplicated. Turn it off if signalk-vessels-to-ais is doing the same conversion.
Position events older than 2 minutes are discarded before they reach Signal K or NMEA 0183. Static data is always injected into Signal K, but reaches NMEA 0183 only after that vessel has sent a live position, keeping the snapshot replay burst off slow serial connections. Remote !AIVDO is converted to !AIVDM before relay so it cannot replace the chartplotter's own-ship state.

Faster sunrise, sunset, and twilight searches (Almanac 0.4.2)

Sun, 20 Sep 2026 04:53:21 GMT

Almanac 0.4.2 speeds up Sun and Moon rise, set, and twilight searches in TypeScript and Swift, and the Sun's position in TypeScript. The public API is unchanged.

Event searches find altitude extrema with Brent's method instead of a fixed 22-sample golden section, and find altitude crossings with a cosine-seeded secant solver. Every crossing is still proven inside a half-second bracket, and anything that stalls or leaves the segment falls back to the bracketed search. Sampler calls for a year at Victoria drop from 40,681 to 15,400 for Sun events and from 24,437 to 10,173 for Moon events.
The TypeScript Sun series evaluates its 51 VSOP87 terms as straight-line arithmetic rather than iterating the coefficient table, for bit-for-bit identical results. Swift already evaluated the series efficiently and mirrors the structure for the twin-port contract.

The focused year benchmark returns the same 3,255 Sun events:

Port	v0.4.1	v0.4.2	Change
TypeScript	136.267 ms	36.268 ms	73.4% faster
Swift	56.322 ms	20.963 ms	62.8% faster

Moon events over the same year are 57.6% faster in TypeScript and 57.4% faster in Swift. Sun positions, the sky track, Moon phases, and every lunar and solar eclipse workload are 21% to 36% faster in TypeScript; Swift's remaining workloads are within 2%.

Each search now reports the root inside its verified bracket rather than the bracket's midpoint, so event times move by at most a third of a second. Across 1950 through 2100 at Victoria, 60°N, the equator, and 70.5°S, every event count, kind, and order is identical, and the parity corpus still holds 9,449 Sun events and 2,115 Moon events.

npm install @openwaters/almanac@0.4.2

.package(url: "https://github.com/openwatersio/almanac.git", exact: "0.4.2")

Sun series: #32. Event searches: #34.

Full changelog.

Fewer SD card writes while offline (Signal K AIS plugin 0.4.0)

Thu, 17 Sep 2026 13:54:00 GMT

The offline queue writes far less to the SD card. Each queue file used to be rewritten from scratch every fifteen seconds as sentences were added to it, so a boat at anchor hearing a slow trickle of traffic wrote the same data to the card a dozen times over. Sentences are now appended to the end of a file and nothing is rewritten, which on a quiet anchorage cuts the writing to a fraction of what it was.
A replay the server only partly accepts no longer rewrites anything on disk, and a queue file damaged by a power cut costs one sentence instead of the five hundred it was sharing a file with.
The queue keeps working when the plugin cannot delete a file, as happens when an SD card turns read-only. A queue file that could neither be read nor removed used to stop the replay where it stood until the next reconnect, and files the server had already taken could be left behind in a way that made the 100 MB cap discard data that had not been sent yet. Files that will not delete are now set aside, retried in the background, and never replayed.

Offline backlog uploads in full after reconnecting (Signal K AIS plugin 0.3.1)

Thu, 17 Sep 2026 11:45:58 GMT

Fixes a queue that never emptied. While the plugin was replaying a backlog to aiscast it wrote every sentence its receiver heard to a new queue file, so it traded one file for another and the replay never reached the end. On a boat that had been offline a while, the queue directory stayed at tens of thousands of files no matter how long the connection was up. A replay now carries up to a thousand sentences from as many files in one frame, and sentences heard mid-replay go out from memory.
The queue keeps far fewer files. Time offline used to leave one behind every fifteen seconds; the plugin now fills each file to 500 sentences before starting another, so the count follows how much is owed rather than how long the boat was out of range.
Sentences past the server's publish limit are no longer lost. aiscast accepts 6000 sentences a minute and quietly drops the rest, so a large replay used to arrive mostly empty while the plugin counted it as delivered. The plugin now paces a replay under the limit and keeps anything the server did not take. A boat with a big backlog takes about a minute for every 5400 sentences owed to catch up, with live sending held back until it is done.

Faster Moon positions and Moon events (Almanac 0.4.1)

Tue, 15 Sep 2026 15:01:51 GMT

Almanac 0.4.1 speeds up Moon positions and the searches built on them in TypeScript and Swift. The public API is unchanged.

The focused year benchmark returns the same 705 Moon events:

Port	v0.4.0	v0.4.1	Change
TypeScript	127.918 ms	53.918 ms	57.8% faster
Swift	127.762 ms	42.581 ms	66.7% faster

Representative Moon-dependent workloads are 35% to 62% faster in TypeScript and 51% to 69% faster in Swift.

This release also makes the tag workflow create a GitHub release for every published version.

npm install @openwaters/almanac@0.4.1

.package(url: "https://github.com/openwatersio/almanac.git", exact: "0.4.1")

Moon performance: #29. Release automation: #28.

Full changelog.

Positions of fixed stars (Almanac 0.3.0)

Tue, 15 Sep 2026 14:58:48 GMT

Almanac 0.3.0 adds the altitude and azimuth of any fixed star in TypeScript and Swift.

starAltAz(raDeg:decDeg:at:observer:) / starAltAz(raDeg, decDeg, time, observer) takes a star's J2000 catalog right ascension and declination and returns its refracted topocentric altitude and azimuth. It precesses and nutates the position to date and uses the same sidereal time and refraction as sunAltAz and moonAltAz.
Annual aberration, proper motion, and stellar parallax are not applied. Aberration is at most 20.5″, and all but a few fast-moving stars shift by only arcseconds per decade.
An out-of-range right ascension or declination is a validation error, like an invalid observer.
The library ships no star catalog; callers pass the coordinates they already carry.

The star positions are checked against the USNO celestial-navigation almanac for the navigational stars at Victoria and at 35°S, on the 2026 equinoxes and solstices, 1999-01-17, and 2050-06-21, with J2000 positions from SIMBAD. The tests compare every star above 10° altitude and leave out the twelve stars whose proper motion would exceed the tolerance by 2050.

Positions checked	Worst altitude error	Worst azimuth error	Tolerance
197	0.45′	0.51′	1′

Validation includes 88 TypeScript tests, 93 Swift release tests, and the shared fixture and parity checks.

npm install @openwaters/almanac@0.3.0

.package(url: "https://github.com/openwatersio/almanac.git", exact: "0.3.0")

Requested in #12. Changes: #13, #14.

Full changelog.

Offline Sun and Moon astronomy for TypeScript and Swift (Almanac 0.1.0)

Tue, 15 Sep 2026 14:58:40 GMT

Almanac 0.1.0 is the first release: offline Sun and Moon astronomy for TypeScript and Swift, with one behavior in both ports and no network access or runtime data files.

sunPosition and moonPosition give geocentric apparent right ascension, declination, and distance. sunAltAz and moonAltAz give refracted topocentric altitude and azimuth.
sunEvents finds sunrise, sunset, civil, nautical, and astronomical twilight, and transit within a window. moonEvents finds moonrise and moonset from the Moon's upper limb.
moonIllumination reports the illuminated fraction, phase angle, phase, and waxing state, and searchMoonPhases finds new, first-quarter, full, and last-quarter moons.
nextLunarEclipse returns the kind, peak, magnitudes, and contact times of the next lunar eclipse, and lunarEclipseVisibility reports which contacts an observer can see.
Every function covers 1950 through 2100 and raises a typed out-of-range error outside that interval. The functions share names across both ports, with Swift argument labels. The algorithms are translated from Astronomy Engine by Don Cross.

Both ports are tested against the same external fixtures and a cross-port parity corpus, with these tolerances:

Quantity	Tolerance	Evidence
Sun and Moon position	1′	JPL Horizons, 1,839 samples each across 1950–2100
Sun distance	1e-4 AU	JPL Horizons
Moon distance	70 km	JPL Horizons
Rise, set, twilight, and phase times	60 s	USNO rise and set grid, 693 USNO moon phases
Lunar eclipse peaks and magnitudes	60 s, 0.03	All 344 eclipses in the Espenak catalog, 1950–2100
Lunar eclipse contacts	60 s	NASA contact tables for four eclipses

Event searches scale with window length: a full 151-year window takes about 68 s in TypeScript and 44 s in a Swift release build, so run long searches off the main thread. Validation includes 80 TypeScript tests, 84 Swift release tests, and the shared fixture and parity checks.

npm install @openwaters/almanac@0.1.0

.package(url: "https://github.com/openwatersio/almanac.git", exact: "0.1.0")

Changes: #1.

Full history.

Solar eclipses visible from a location (Almanac 0.4.0)

Mon, 14 Sep 2026 18:39:11 GMT

Almanac 0.4.0 adds solar eclipses for an observer in TypeScript and Swift.

nextSolarEclipse(after:observer:) / nextSolarEclipse(after, observer), previousSolarEclipse(before:observer:) / previousSolarEclipse(before, observer), and solarEclipses(from:to:observer:) / solarEclipses(from, to, observer) find the solar eclipses a place can see. Each result carries the kind (partial, annular, or total), the obscuration at peak, contacts C1 through C4, and the Sun's altitude at each contact. C2 and C3 are present only for annular and total eclipses.
An eclipse whose Sun is below the horizon at C1, the peak, and C4 is not returned. Next and previous searches walk to the edge of the supported interval, because a place can go years without a visible solar eclipse.
solarObscuration(at:observer:) / solarObscuration(time, observer) gives the fraction of the Sun's disc the Moon covers at any instant, for drawing an eclipse as it happens.
The shared performance harness gains seven solar workloads. benchmarks/run.mjs --skip <regex> leaves them out when the comparison base predates 0.4.0.
Swift CI runs on Linux with Swift 6.3.3, and the TypeScript package builds with TypeScript 7.

The searches are checked against USNO local circumstances for eight places and against all 337 solar eclipses from 1950 through 2100 in the Espenak Five Millennium Catalog. The worst residuals sit well inside the contract's tolerances:

Quantity	Worst residual	Tolerance
USNO contacts C1 through C4	7.2 s	60 s
USNO peak	7.0 s	300 s
Catalog peak, 215 central eclipses	123 s	300 s
USNO obscuration	0.001	0.01
USNO Sun altitude at a contact	0.06°	0.5°

The hosted CI comparison measured these median query times, in milliseconds:

Workload	TypeScript	Swift
Next solar eclipse	8.1	6.0
Previous solar eclipse	6.9	5.1
Solar eclipses / 228 hours, one visible	0.72	0.51
Solar eclipses / 228 hours, new moon not visible	0.48	0.35
Solar eclipses / 228 hours, no new moon	0.012	0.009
Solar eclipses / 1950–2100	391	295
Obscuration / 228 hours	2.8	2.0

Both revisions used the same harness and toolchain within each port, with seven interleaved process pairs and 300 ms warmup. No existing workload moved by more than 2.1% in either port. Validation includes 127 TypeScript tests, 109 Swift release tests, and the shared fixture and parity checks.

npm install @openwaters/almanac@0.4.0

.package(url: "https://github.com/openwatersio/almanac.git", exact: "0.4.0")

Solar eclipses: #24, #27. Development and toolchain: #15, #22, #23, #25, #26. Dependency updates: #16, #17, #18, #19, #20, #21.

Full changelog.

Nearby stations on every station page, and how the Moon shapes tides (Slackwater for iOS 1.13.0)

Mon, 14 Sep 2026 04:06:28 GMT

Find nearby places from any detail page, and see how the Moon can shape the tides.

Each station page now lists nearby tide and current stations with a map, so you can move between places without returning to search.
The Moon sheet explains spring and neap tides and how the Moon's distance can affect tidal range. Phase shortcuts take you to the relevant night sky.
Search shows where same-name stations are and remembers the place you selected. Results use more space on iPad.
First launch offers ready Chesapeake Bay stations and a clearer location choice.
Canadian tide and current downloads recover better from slow or interrupted connections, and downloaded currents appear in widgets.
The Now button returns the schedule to the current week. Current pages show station details consistently.

Nearest tide and current stations, an endless timeline, and sharing (Slackwater for iOS 1.12.0)

Sat, 12 Sep 2026 04:11:00 GMT

Finding the right station, a timeline that doesn't end, and sharing the moment you're looking at.

My Location shows two cards — the nearest tide station and the nearest current station — and Near Me and search share All/Tides/Currents filter chips. Every tide detail links to the nearest current station and back again, with the distance in the label.
The detail timeline scrolls without end in both directions. Tapping anywhere on it brings that moment to the centerline; a sunrise or sunset scrubs to itself, and the date opens the week picker.
A share button sits beside the star on every detail page. It sends a slackwater.xyz link, carrying the instant you scrubbed to rather than making the receiver find it again.
The commentary pill names sunrise or sunset whenever it comes before the next high, low or slack — and taps through to it like any other stop.
The Moon sheet is drawn instead of tabulated: rise and set on a horizon, next full and next new as the discs they name, the orbit under the distance readout, and each eclipse row drawing its own eclipse.
Shape-only gates such as Malibu Rapids now use the same curve language as measured currents without implying a speed, slack windows read cleanly against the curve, and the card and widget direction arrows match the detail page.
The schedule collapses to one day at a time, Recents use the same cards as the rest of the list, day labels sit at the middle of daylight rather than clock noon, and the lead readout carries the date while you scrub through the night.
The station list renders before the catalogs finish decoding, so the first frame arrives sooner.
Fixes: a My Location card opens the station you tapped, not its neighbour; the location refreshes when the app comes back from the background instead of only on a cold launch.

LAT and HAT for NOAA stations that don't publish them (Slackwater database 0.9.20260907)

Mon, 07 Sep 2026 23:07:51 GMT

Synthesize LAT and HAT where NOAA publishes neither (#126)

Faster Moon, Sun, and eclipse calculations (Almanac 0.2.1)

Mon, 07 Sep 2026 12:36:42 GMT

Almanac 0.2.1 reduces repeated astronomy work in TypeScript and Swift, with the same public API and fixture tolerances.

Reuse Moon geometry for illumination and flatten the Moon model's scratch arrays.
Share solar crossing probes, skip crossings before the requested window, and accelerate altitude refinement with a verified bracket and bisection fallback.
Reuse peak shadow geometry when calculating eclipse contacts.
Expand the shared performance harness to 15 workloads, including an empty eclipse window that exercises latitude pruning, and document how to reproduce comparisons in the README.

The hosted CI comparison measured these reductions in median query time versus the 0.2.0 astronomy code:

Workload	TypeScript	Swift
Sky track / 228 hours	40.0%	42.4%
Sun events / 228 hours	39.3%	40.2%
Moon events / 228 hours	39.1%	35.1%
Previous lunar eclipse	26.0%	36.6%
Lunar eclipses / 1950–2100	26.4%	23.4%

Both revisions used the same harness and toolchain within each port, with seven interleaved process pairs and 300 ms warmup. Build/startup time is excluded; timings vary by machine. All 15 workloads pass the 20% regression gate in both ports.

Refined rise/set and twilight times can shift by up to 600 ms after quantization; event counts and kinds are unchanged, and existing accuracy and parity tolerances are preserved. Validation includes 86 TypeScript tests, 91 Swift release tests, and the shared fixture checks.

npm install @openwaters/almanac@0.2.1

.package(url: "https://github.com/openwatersio/almanac.git", exact: "0.2.1")

Performance changes: #10.

Full changelog.

Search past lunar eclipses and date ranges (Almanac 0.2.0)

Mon, 07 Sep 2026 11:22:10 GMT

Almanac 0.2.0 adds backward and range lunar eclipse searches in TypeScript and Swift.

previousLunarEclipse(before:) / previousLunarEclipse(before) finds the previous eclipse directly, retaining the 100 ms same-eclipse band used by next searches.
lunarEclipses(from:to:) / lunarEclipses(from, to) returns eclipse peaks in a sorted, half-open [from, to) window. Visibility remains a separate observer query.
Stable peak calculations and Swift date normalization allow adjacent windows to split at a returned peak. The root solver also rejects narrow intervals without a crossing.
A shared performance harness compares both ports against the base revision in CI, with macOS benchmarks gated on the cheaper TypeScript job.

Compared with the previous consumer loops, CI measured previous searches about 86% faster and 228-hour range searches 65–99% faster. Stable boundary handling adds about 0.1 ms to next searches (8–11%); all workloads pass the 20% regression gate.

Validated against all 344 catalog eclipses, with 86 TypeScript tests, 91 Swift tests, and unchanged fixture/parity tolerances.

npm install @openwaters/almanac@0.2.0

.package(url: "https://github.com/openwatersio/almanac.git", exact: "0.2.0")

Changes: #7, #8.

Full changelog.

CHS constituents 0.3.1

Sun, 06 Sep 2026 15:03:41 GMT

No behavior change.

0.3.0 was published by hand to bootstrap @openwaters/chs-constituents, since npm cannot configure a trusted publisher for a package that does not exist yet. This release is the first to go out through publish.yml over OIDC, with provenance attached.

The package moved from @sailingnaturali/chs-constituents in #13, along with its shared registry dependency, now @openwaters/station-metadata.

Follow buddy boats beyond VHF range (Signal K AIS plugin 0.3.0)

Tue, 01 Sep 2026 19:29:23 GMT

Buddy boats: vessels on signalk-buddylist-plugin's list are followed on aiscast wherever they are, far beyond VHF range, in every receive mode. The buddylist plugin keeps raising its buddy flag and proximity alerts, so Freeboard-SK's buddy icon and phone notifications work at any distance. The status line shows how many buddies have been heard from.
Subscriptions request a snapshot, so targets appear from the server's cache at connect instead of one by one as they next transmit.
Own-ship reports from NMEA 2000 are recognized by the boat's MMSI, not only by the transceiver-information field, so transmitting transponders like the B&G V60-B publish as !AIVDO and pause self-reported position synthesis.

Slackwater database 0.9.20260901

Tue, 01 Sep 2026 11:22:06 GMT

Chores:

ci: cache GeoNames data to avoid re-downloading in tests (#117)

New icon and App Store listing (Crowd depth 1.2.6)

Mon, 31 Aug 2026 14:07:27 GMT

Polish for the Signal K AppStore listing — no behavior changes.

New icon: sonar pings from a sailboat down to the seabed, in the Open Waters palette (#113)
AppStore metadata: display name "Crowd Depth", a fuller description, and expanded keywords (#113)
MIT license, now bundled with the npm package (#113)
README rewrite: leads with why crowdsourced bathymetry matters and how reports flow through Open Waters as an IHO trusted node to the IHO DCDB (#113)
New CONTRIBUTING.md: repo layout, dev/test workflows, and the release process (#112)

Readable device names in the source menus (Crowd depth 1.2.5)

Mon, 31 Aug 2026 01:24:36 GMT

Fixed friendly device names in the Position/Depth source dropdowns (#111, first half of #93). The config UI now shows e.g. "Furuno SCX-20 (IPG100.c0788c00e7e04312)" instead of the raw sourceRef, including for canName-form refs (useCanName).

CHS constituents 0.2.2

Sat, 29 Aug 2026 03:26:58 GMT

Move repository ownership to Open Waters while retaining the @sailingnaturali/chs-constituents package identity. Add automated checks that keep CHS-derived output and provider station IDs out of Git and npm packages.

Share your position from GPS when there's no AIS transponder (Signal K AIS plugin 0.2.0)

Mon, 24 Aug 2026 16:41:07 GMT

New Share setting: Fallback to self-reported AIS position. When an AIS transponder is not available, the plugin builds class B position and static reports from Signal K (like @signalk/aisreporter) and publishes them as !AIVDO tagged s:self, so a boat with only a GPS shows up on aiscast as self-reported. Synthesis pauses while a real !AIVDO is heard. Checked by default when the config form is saved; configs saved before this setting existed stay off until re-saved. The checkbox is disabled until an MMSI is set in Vessel settings.
Each Share setting explains itself below its label, and Receive mode renders as radio buttons instead of a dropdown.

Tokens no longer expire (Signal K AIS plugin 0.1.4)

Fri, 21 Aug 2026 22:15:46 GMT

Personal tokens minted by aiscast no longer expire; the plugin keeps a cached token with no expiry instead of minting a new one every start.
The npm package includes a CHANGELOG.md.

Connects over Starlink, satellite, and slow cellular links (Signal K AIS plugin 0.1.3)

Fri, 21 Aug 2026 11:22:13 GMT

Fixes the plugin never connecting on high-latency links (Starlink in remote regions, satellite, some cellular): the status line stuck on reconnecting while curl to the server worked. Node gave up on the IPv4 connection after 250 ms and fell back to an unroutable IPv6 address; the plugin now allows 3 s per attempt.

The debug log now shows the real reason a socket failed (for example socket error: ETIMEDOUT (connect ETIMEDOUT 2.29.0.215:443; …)) instead of an empty socket error: line.

Dashboard clears the "No token" error once connected (Signal K AIS plugin 0.1.2)

Fri, 21 Aug 2026 02:17:31 GMT

Clears the red 'No token' line on the Dashboard once the token is obtained (the server keeps a plugin's last error until the status entry is reset).

Starts sharing once the network comes up (Signal K AIS plugin 0.1.1)

Fri, 21 Aug 2026 02:09:51 GMT

Retries token minting with backoff (1 to 30 min) instead of waiting six hours after a failed start, so a Pi that boots before its network is up starts sharing as soon as it can. Token errors now include the underlying cause (DNS, TLS, connection refused).