Binnacle Chartplotter

A WebGL chartplotter for Signal K.

It has not been field-tested at any scale. It has been developed and verified against a single Signal K server, never across a fleet or a range of real-world boats, hardware, and conditions. It is also not certified for safety-of-life navigation. Always carry redundant means of navigation, cross-check against your primary instruments, and treat every display as advisory.

What's new in 0.22.0

• Helm controls: an optional Autopilot panel, off-course alarms, alarm self-test and volume, and a screen lock that leaves emergency controls available.
• Passage context: forecast wind and after-dark arrivals in route plans, measured barometer tendency, multi-day weather, and provider or NOAA weather warnings even when Weather is closed.
• Keyboard and touch workflows: coordinate entry for routes, measurements, and anchor corrections, tap-based reordering, and controls that remain reachable with enlarged text.
• Recovery without lost work: retained logbook and handoff drafts, retryable radar-area edits, explicit refresh actions, and offline coverage tied to the route and saved charts actually checked.
• Data confidence: press-time MOB marks remain unchanged across stations and reconnects; stale telemetry, tide datums, unknown hazard assessments, and unconfirmed actions stay explicit.
• Watchkeeping tools: optional ship's logbook and AI advisor integrations, display dimming, automatic themes, and per-category Signal K unit preferences.

See the 0.22.0 changelog for the full list.

What it does

Signal K is an open marine data standard that streams a boat's navigation, environment, and AIS data over a single API. Binnacle displays that data: a GPU-rendered, offline-capable chartplotter that runs in a browser and is served by the boat's Signal K server.

It is built for low-bandwidth, offline use on modest hardware. It has night-readable themes, computes collision and course data on the client when no server provider supplies them, and caches viewed areas so they keep rendering without a connection. It runs on the same Raspberry Pi that hosts the Signal K server.

Features

Binnacle ships its full feature set as a Signal K webapp:

• Charts and layers: a GPU vector base map, server charts, five streaming bathymetry and ENC sources (NOAA ENC, BlueTopo, EMODnet, GEBCO, and Seascape), your own PMTiles charts added by URL or from the server's charts folder, and a 24 hour track history layer under the live track. An ambient badge grades the current view honestly and never calls the reference base map a chart.
• Offline charts: with the optional Chart Locker plugin, draw and save the chart area needed for a passage, keep an automatic cache around the moving boat, and manage installed charts and storage from one landing page. Check any saved route from its passage plan without activating navigation. The advisory result reports Complete, Partial, or Unknown for the assessed corridor and detail; without Chart Locker, the landing page remains available with setup guidance.
• Overlays: free, key-free OpenSeaMap seamarks, marine protected areas, maritime boundaries, and NASA GIBS ocean conditions (sea-surface temperature and sea ice), each with its source attribution.
• Marine radar: an optional live radar picture from the Signal K Radar API, rendered over the chart with range rings, a heading line, strict night-red colors, confirmed transmit, and the tuning and zone controls the radar reports. Provider, stream, stale-data, access, and renderer failures stay distinct, so an old picture is never presented as live.
• Routing: draw or enter coordinates and save routes as Signal K resources, tap Go to here to navigate straight to a point, and follow a route with a nav strip (cross-track, distance, bearing, velocity made good, and time to go) over the v2 Course API. A plan speed and departure time turn the route into a passage plan with a local-clock arrival, forecast wind, and after-dark cues at every point. Edit or reorder points without dragging, snap chart edits to saved waypoints, and import or export GPX.
• Autopilot: detect a Signal K v2 Autopilot API provider, show its state, mode, and target, and offer only its supported controls. Engagement and maneuvers require deliberate confirmation; missing, unknown, stale, and unreachable states never appear as confirmed standby.
• Profiles: keep named helm setups containing the theme, chart and weather layers, chart orientation, collision thresholds, track and planning settings, unit fallback, toolbar pins, instrument and Data trends selections, display settings, and preferred anchor radius. Changes to the active profile save automatically and sync through Signal K when you are logged in, while each browser keeps its own active choice.
• Instruments: a gauge dock (SOG, heading, depth, apparent wind, and more from a curated catalog you pick and reorder) that takes the full screen on a phone. Values color by your server's configured alarm zones, staleness honors the server's own declarations, and every tile's detail names its live source and calls out a quiet failover.
• Playback: review 1 hour, 6 hours, 24 hours, or 7 days from a registered Signal K history provider, scrubbing or replaying the synchronized recorded track, vessel position, depth, apparent wind, barometer, and speed over ground.
• Weather: a zoom-capped mini-map with animated WebGL wind, pressure isobars, waves, precipitation, cloud, and radar, plus time-aware point readouts, marine forecasts, and official warnings from a Signal K weather provider or the NOAA point-alert fallback. Observed conditions stay distinct from forecast estimates. Open-Meteo provides the key-free forecast fallback, and cached forecasts remain available offline with explicit stale labeling.
• Tides: independent tide-height and tidal-current station selection with automatic nearest choices, exact manual NOAA CO-OPS choices, a 48-hour tide curve, and the next high, low, flood, ebb, or slack. Heights retain the provider's datum or explicitly say it is unspecified; times include their date and local-time basis. Currents remain available without tide heights. Automatic tide height prefers the signalk-tides plugin when the server runs it.
• Lookout: a collision watch with CPA and TCPA, chart-highlight rings, an audible alarm, and a published Signal K notification, plus a searchable AIS target list and an Alarms panel that collects every active alert on the boat. One audio authority coordinates audible alarms. Supported Silence and Acknowledge actions propagate through Signal K; acknowledgment means seen, not resolved. Device-local mute remains distinct and available after a boat-wide action fails.
• Anchor watch: drop the anchor at the boat, set the swing radius, and get a drag alarm that latches until acknowledged. It drives the signalk-anchoralarm-plugin when installed, so the alarm keeps running with the browser closed, and falls back to a fully in-browser watch when it is not.
• Man overboard: an always-visible MOB button with a confirm pop-out that marks the spot, publishes the boat-wide Signal K alarm, and raises a recovery strip with live bearing, range, and elapsed time. The position and time are captured on the initial press and preserved through confirmation and reconnects. An MOB raised by another station shows here too. Without a fresh fix, the alarm still raises but does not invent a position.
• Watch handoff: a timestamped review-status snapshot for the change of watch: fix, course, alarms, the top contact, depth watch, radar health, weather and tide ages, and route coverage, plus a short operator note. Snapshots share between stations through Signal K and always state whether they synced; the surface reviews status and never declares it safe to take watch.
• Measure: tap points on the chart or enter coordinates for rhumb-line leg range, true bearing, and a running total, with movable points, Undo, and a confirmed Clear.
• Tracks: record, pause, save, show, and export segmented voyage tracks as GeoJSON, and GPS gaps never become invented route legs. Save the latest continuous segment as a reusable route, or confirm a retrace to navigate home along it.
• Waypoints: drop one from a long press, then search, sort, locate, navigate to, rename, or delete it from the Waypoints panel. Marks live in the server's waypoint resources, so they interoperate with other Signal K clients.
• Data trends: choose and reorder up to eight navigation, weather, electrical, propulsion, tank, or cabin readings per profile, each drawn as a themed 24-hour chart from the Signal K History API, with bounded live-session samples on a stock server. Every chart states its data coverage and is marked Partial or Stale when warranted.
• Find places and points of interest: search the notes in the current chart view, preview a result on the chart, and open its structured detail, with custom symbols through the signalk-symbol-manager plugin. Add personal notes from a chart press, then edit, move, or delete only the notes Binnacle owns.
• Chart orientation: north-up by default, with course-up and heading-up as explicit profile-owned choices that fall back to north the moment their reference goes stale.
• Help: a first-run orientation banner and a permanent Help panel with safe-use framing, Signal K access and alarm-sound setup, a marine glossary, and operating-context checklists.
• Logbook: read recent entries and compose notes through the optional signalk-logbook plugin. Navigation, anchor, and handoff events can offer factual drafts, but never save an entry without your action.
• AI advisor: read reports and request analyzer runs through optional signalk-openrouter-companion. Reports are advisory and show their age. Run now discloses the telemetry and paid-credit implications, tracks server status with a bounded wait, and shows completion, refusal, or an unconfirmed outcome alongside the plugin's run and budget responses.
• Your units: supported readouts and editable limits follow the server's per-category unit preferences, with the profile's preference as fallback. Navigation-specific fields such as track distance and route plan speed retain their labeled nautical-mile and knot conventions. Stored values remain SI.
• Display: day, dusk, and night-red themes, a dimmer, a bright-sun chart palette, automatic theme switching, and interface text sizing. Night-red stays red on black for a dark-adapted watch.

Each feature's full behavior, availability, and recovery states are documented in the guides in the repository's docs directory, which also ship inside the installed package.

Architecture

Binnacle is built on a current web stack and engineered to run on modest helm hardware:

• Front end. Svelte 5 with runes, Vite, and TypeScript, linted and formatted with Biome. The code is organized as cohesive, single-responsibility slices under a strict Feature-Sliced Design, with the import boundaries enforced by the build through a dependency-cruiser gate, a modular stylesheet assembled one concern per file, and shared UI primitives and helpers, so a new feature drops in against stable interfaces rather than by surgery on the core.
• GPU rendering. MapLibre GL JS 6 draws the vector base map and chart layers through WebGL2. The own vessel and every AIS target render as GPU symbol layers, and wind draws as a WebGL particle field advected through the forecast on the graphics card.
• Off-main-thread real-time pipeline. A dedicated Web Worker hosts the Signal K WebSocket client; deltas are coalesced into frame-rate batches on a worker timer and fed into a path-keyed reactive store, so a busy AIS anchorage updates the readouts without stalling the chart render, and data and alarms keep flowing while the tab is in the background. A failed stream can recreate the worker, reconnect, and replay subscriptions without reloading the chartplotter.
• Minimal network and render work. Binnacle subscribes to exactly what it draws, keeps everything in SI internally, and converts only at the display edge.
• Offline caching. Self-hosted fonts and assets (no CDN for app code). PMTiles chart areas are cached as blocks in IndexedDB at the protocol layer, so they work offline even over plain http; tides, notes, weather, and the vessel conditions persist the same way. Over https a service worker additionally caches the base map, plugin chart tiles, supported online overlays, and predictions. With Chart Locker installed, server-side saved areas, automatic caching, shared tile storage, and installed PMTiles files add a boat-wide offline layer that is independent of one browser's cache.

Requirements

• Signal K server 2.x.
• Node.js >= 22.18 (for building from source).
• A WebGL2-capable browser that supports the shipped ES2023 bundle. Safari 16.4 or later is required.
• Optional: signalk-chart-locker for server-managed saved areas, automatic caching, shared storage, and installed PMTiles chart management.
• Optional: a Signal K Radar API provider, such as Mayara, for the marine radar overlay and controls.

Installation

Binnacle is a Signal K webapp. The production build ships inside the package, so there is nothing to build.

From the App Store (recommended). In the Signal K admin UI, open Apps and Plugins, then Store, search for Binnacle, and install. Open it from the Webapps list.

With npm. Install into the server's home directory and restart Signal K:

cd ~/.signalk
npm install signalk-binnacle

From source. See the Development section below.

Optional offline-chart management. Install Chart Locker (signalk-chart-locker) from the Signal K App Store, then start the plugin. Binnacle detects it automatically. A secured server may require you to sign in to Signal K as an administrator before downloads and chart-name edits are enabled. This is separate from approving Binnacle's ordinary read and write access request. Chart Locker management calls use the browser's Signal K administrator session, not Binnacle's device token. Binnacle checks Signal K's live login status before suggesting sign-in, so a Chart Locker permission failure does not mislabel an authenticated administrator as signed out.

Optional marine radar. Run or configure a provider that exposes the standard Signal K Radar API at /signalk/v2/api/vessels/self/radars. Mayara is the reference provider. Binnacle discovers radars, hydrates /controls, listens for radars.*.controls.* Signal K deltas, and opens the selected radar's reported spoke stream. Read access is sufficient for the picture; transmit, standby, and tuning writes require read-write approval. A provider that reports complete native zone, sector, or rectangle shapes also gets explicit Edit, Save, Cancel, and optional chart-placement controls. No-transmit sectors require an additional emission-envelope confirmation. Angles display in degrees, distances follow the server unit preference, and each write remains one SI geometry update.

First run

1. Open Binnacle. After installing, restart Signal K if the store asks, then open Binnacle from the Webapps list in the admin UI.
2. Approve its access request. On a secured server, Binnacle asks for access the first time it connects, and the request does not appear in Binnacle itself: it waits in the Signal K admin UI under Security, then Access Requests. Approve it with read and write permission (routes, waypoints, tracks, course, alarms, and profiles all write), then reload Binnacle. This is the step most first installs miss.
3. Pick your charts. Open Charts and turn on the sources for your waters; inside US waters, Binnacle offers the official NOAA ENC in one tap when no chart is on.
4. Work through Get set up. The live checklist in Help tracks what a fresh install still needs and routes to each item.

Usage

Open Binnacle from the Webapps list in the Signal K admin UI, or go straight to http://your-sk-server:3000/signalk-binnacle/. It opens on the chart, centered on your boat.

A few interactions cover most of the helm:

• Open the context menu. Long-press the chart on a touch screen, right-click with a mouse, or focus the chart and use the Context Menu key or Shift+F10. Drop a waypoint, choose Go to here to navigate straight to that point, or start a route or measurement.
• Measure a chart leg. Open Measure, tap a start and destination, then read the rhumb range, true bearing, and total. Select a point to inspect both adjacent legs, choose Move point to drag or place it again, or enter its coordinates. Use Undo to reverse an add, move, or deletion. Use Done when finished.
• Manage charts and overlays. Open Charts to select chart sources, inspect their details, repair a saved PMTiles URL, refresh its metadata, or change server sharing. Switch to Overlays to toggle overlays, change opacity, and reorder their stack by dragging or with each row's Move up and Move down actions.
• Prepare offline charts. Open Offline charts, choose Save a chart area, draw over the passage, review the included charts and detail, and start the download. Confirm the saved area's status and update date before relying on it away from coverage.
• Switch themes. Cycle the day, dusk, and night-red themes from the theme control. Night-red is pure red on true black for a dark-adapted watch.
• Mark a man overboard. Tap the always-visible MOB button in the top bar and confirm to mark the spot, raise the boat-wide alarm, and start the recovery strip.

For caching behavior, storage, and HTTPS requirements, see the Offline charts, Chart Locker, and SSL section below.

For behavior, availability, recovery states, and safety rules for every menu action, see the menu items guide in the repository's docs directory. Detailed guides there also cover tracks, waypoints, find places, measure, marine radar, and offline charts, including offline preparation and administrator-session troubleshooting. The guides ship inside the installed package as well.

When installed as a PWA on a touch device, Binnacle automatically reserves bottom clearance for Android navigation and tablet taskbars. The status strip and mobile app-menu sheet also follow reported bottom and landscape side safe areas, so their helm controls remain reachable when system chrome overlays the app window.

The Profiles panel includes Forget credentials and Erase all local data for a shared or retired display. These actions affect only Binnacle data in the current browser. They do not delete Signal K routes, waypoints, tracks, profiles, Chart Locker data, administrator sessions, or server-side device authorization. Synced profiles return after the browser signs in and syncs again. Profiles and changes that have not synced are permanently lost. Full erasure is blocked while MOB, anchor watch, navigation, route editing, measurement, or an unsaved recorded track is active.

Network privacy

Binnacle gets boat data from your Signal K server and loads its vector base map from OpenFreeMap when the chart opens. When their chart or overlay layers are visible, the browser can also request tiles from OpenSeaMap, NASA GIBS, Open Waters Seascape, GEBCO, EMODnet, and NOAA services for ENC, BlueTopo, marine protected areas, and seabed infrastructure. The maritime-jurisdiction and UNESCO site overlays request VLIZ Marine Regions.

Weather forecasts and optional layers can contact Open-Meteo and RainViewer. Opening tides can contact NOAA CO-OPS for automatic fallback, tidal-current predictions, or a manually selected station. These services can observe your public network address and the requested tile, map area, or forecast coordinates. Cached results remain usable when a provider is unavailable.

Weather warnings also run in the background whenever Binnacle has a fresh vessel position, even with the Weather panel and weather layers closed. The watch queries the detected Signal K weather provider and can fall back to NOAA's api.weather.gov point alerts. That fallback sends the vessel's latitude and longitude rounded to four decimal places, normally about every ten minutes, with additional requests after area or provider changes and retries after failures. Closing panels does not stop this check, and there is currently no in-app opt-out. Blocking external requests through your browser or network policy prevents this disclosure but also removes external warning coverage and can make other online charts, weather, and tide features unavailable.

User-added URL charts are fetched by the browser. Binnacle rejects URLs with embedded usernames or passwords, removes URL fragments, redacts every query value in displays and errors, and keeps every query-bearing URL on this device unless you explicitly choose to share the complete URL with the Signal K server. Chart detail can repair a moved or expired URL, refresh archive metadata, and change that sharing choice without losing the chart's id or layer settings. Use HTTPS for Signal K so device credentials and boat data are encrypted on the local network.

Offline charts, Chart Locker, and SSL (optional)

Chart Locker is optional, but it is the recommended way to prepare a passage rather than depending only on charts viewed previously in one browser. Install signalk-chart-locker from the Signal K App Store, then open Offline charts in Binnacle. If the plugin cannot be reached, that menu item stays available and opens a setup page explaining whether to install, start, retry, or sign in to Signal K as an administrator. When administrator access is required, the header status opens that sign-in directly. The sign-in flow stays in the PWA window and redirects back to the current Binnacle route. If Signal K already reports an administrator session but Chart Locker refuses it, Binnacle reports an access error and offers a retry instead of asking the administrator to sign in again.

The offline charts guide in the repository's docs directory covers the full setup, access, troubleshooting, download, and storage workflow.

The Offline charts landing page has four jobs:

1. Saved areas. Choose Save a chart area, draw a rectangle on the chart or enter its bounds, review the default chart selection, pick Overview, Coastal, or Harbor detail, check the estimated download and free space, name it, and start the download. On a phone, the panel collapses while drawing so the chart owns the gesture. A saved-area card is ready only when it says Saved, works offline. Accepted downloads recover by area identifier if their immediate job response is lost, and a temporary status failure offers Retry status without starting a duplicate download. If a saved definition references a removed chart source, Binnacle preserves the existing cached coverage, labels the missing source, and directs the user to adjust a copy before downloading again.
2. Automatic caching. Optionally keep selected charts cached around the moving boat. This is a rolling nearby cache, not a substitute for saving and verifying the full planned passage. Controls remain disabled until the saved server policy loads; a failed load offers Retry instead of presenting defaults as the current policy. Accepted changes report saving, saved, or failure. Settings follow Chart Locker's limits for 64 sources, zoom 0 through 24, distances up to 100 km, and update intervals from one minute through 24 hours.
3. Installed charts. Rename installed PMTiles charts, edit their descriptions, inspect bounds, zoom range, and scale, refresh the file list, and see actionable errors for invalid files. Add, replace, or remove archives in the Chart Locker chart folder on the Signal K server.
4. Storage. Review saved-area, recently viewed, and automatic-caching usage, choose when recently viewed charts clear, and clear only that expendable cache without deleting saved areas.

The header's Offline status reports the cache amount or a service problem. It does not certify that a particular passage is complete. Before leaving coverage, open Offline charts and verify the intended area's coverage, included charts, Saved, works offline status, and update date.

SSL is not required. Binnacle runs fully over plain HTTP, which is how the Signal K server serves it by default: the chart, AIS, weather, points of interest, tracks, and the Lookout alarms all work without it.

Much of the data caching works without SSL. PMTiles chart areas, the weather forecast, tides, chart notes, and the vessel conditions are cached in IndexedDB, which is not secure-context gated. Over plain HTTP, those retained records are available once the application has loaded, but a full reload still needs the Signal K server to serve the application shell. What SSL adds is the service-worker layer: browsers expose the service worker and cache-storage APIs only in a secure context (HTTPS or http://localhost), so caching the base map, plugin-served chart tiles, and the streaming overlays activates only when the server is reached over HTTPS. Over plain HTTP those degrade cleanly to online-only with no loss of live function.

Chart Locker's server-side downloads and cache work independently of the browser service worker, so they do not require HTTPS. HTTPS is still valuable because it enables Binnacle's additional browser-side service-worker cache for the base map, plugin chart tiles, and streaming overlays.

There are two good ways to add HTTPS to Signal K:

• The signalk-ssl plugin (source), which generates a local certificate authority, issues the server certificate, and distributes the root to your devices by QR code. It runs its certificate tooling on the shared signalk-container runtime. The Signal K server's built-in SSL settings (Server, then Settings, then SSL) are a bare-bones alternative.
• Tailscale, which adds remote access and publicly trusted certificates (no trust-store step at all) in one move. See Accessing Signal K remotely with Tailscale for a quick start, including a clean signalk.<tailnet>.ts.net service name.

One more step is required, and it is easy to miss: your browser has to trust that certificate, not just reach it. A self-signed certificate, including one the signalk-ssl plugin generates, is not trusted by default, and browsers refuse to register a service worker from an origin whose certificate they do not trust, even after you click through the page's certificate warning. So if you only accept the one-time warning, the page loads but offline caching never activates, and the console shows a message like "service worker registration failed: an SSL certificate error occurred." To fix it, install the certificate authority's root (the QR code or .pem the plugin gives you) into your browser or operating system trust store and mark it trusted, then reload over HTTPS. Once the certificate is trusted, the service worker registers and the base map and chart tiles cache for offline use.

Development

Development targets Node 22.18 or newer and npm 11.6 or newer. The recommended npm version is 11.19.0. .node-version and packageManager record the project defaults, while devEngines enforces the supported minimums. All tools use repository-local dependencies.

git clone https://github.com/NearlCrews/signalk-binnacle.git
cd signalk-binnacle
npm install        # install dependencies
npm run hooks      # install the git pre-commit and pre-push gates (run once)
npm run dev        # Vite dev server
npm run check      # type-check application, tooling, and browser tests
npm run lint       # code, Svelte, Markdown, and spelling checks
npm run format     # Biome format (write)
npm run ci:biome   # format, lint, and import-order verification
npm run cruise     # dependency-cruiser boundary check
npm run deadcode   # unused files, dependencies, and public exports
npm test           # Vitest unit tests
npm run test:coverage # unit tests with the enforced coverage floor
npm run build      # production build into public/
npm run size       # compressed production bundle budgets
npm run verify     # complete non-browser local and CI gate
npm run test:e2e:fast # Build, then run the Chromium browser checks only (no offline/PWA or WebKit coverage; use test:e2e:cross-browser or test:e2e:gate for the full spread)
npm run test:e2e:cross-browser # Build, then run Chromium, PWA, and WebKit checks
npm run verify:ci  # full pull request gate, including an Unreleased development version
npm run verify:release # full gate, cross-browser E2E, package checks, and both dependency audits

After npm run hooks, git runs verify:commit before each commit and verify:browser before each push. The hooks live in .githooks/ and are opt-in via core.hooksPath, never a package lifecycle script. The E2E commands build first, while the pre-push test:e2e:gate reuses the existing public/ build from verify so a push does not rebuild.

Maintainers preparing a version should follow the release checklist in docs/releasing.md. Preparation does not authorize a tag, GitHub release, or npm publication.

To run a local build inside your own Signal K server, link it into the server's module directory and add it to the server config so it loads:

ln -sfn "$(pwd)" ~/.signalk/node_modules/signalk-binnacle

{
  "dependencies": {
    "signalk-binnacle": "file:../path/to/signalk-binnacle"
  }
}

Restart Signal K, then open http://your-sk-server:3000/signalk-binnacle/ in a browser.

License

Apache-2.0. See the LICENSE file for the full text. The software is provided "AS IS", without warranty of any kind. It has not been field-tested at scale and is not certified for navigation. Treat all on-screen information as advisory, and always carry independent means of position-fixing.

Acknowledgments

Binnacle is written and maintained by Nearl Crews. It stands on open data and open source:

• Signal K Project for the open marine data standard.
• MapLibre GL JS for the GPU map renderer, and OpenFreeMap for the vector base map, built from OpenStreetMap data under the Open Database License.
• Open-Meteo for atmospheric and marine forecast grids, and RainViewer for precipitation radar.
• NOAA for the ENC chart, BlueTopo bathymetry, the MPA Inventory, and the CO-OPS tide and current predictions; EMODnet for European bathymetry, protected areas, and the seabed infrastructure layers (power cables, telecom cables, pipelines, and wind farms); GEBCO for global bathymetry; Open Waters for Seascape, merging GEBCO, EMODnet, NOAA CUDEM, and other regional sources into worldwide depth shading, hillshade, contours, and soundings; NASA EOSDIS GIBS for the ocean-conditions imagery; OpenSeaMap for the seamark overlay; and the Flanders Marine Institute (VLIZ) Marine Regions service for the maritime boundaries, the 12 nm, 24 nm, and high seas limits, the IHO sea areas, and the UNESCO marine sites.

Custom chart symbols come from signalk-symbol-manager by Joel Kozikowski, who also contributed the symbol rendering Binnacle uses in #6.

Binnacle pairs well with sibling plugins such as signalk-crows-nest, which supplies the points of interest it renders, and works with any Signal K weather provider, such as signalk-virtual-weather-sensors.

Support

Find this project useful? You can support its continued development by buying me a coffee.

• Report a bug
• Request a feature
• Security issues