BoatKit can publish timestamped position fixes directly to noforeignland’s supported inbound tracking API. It samples a current BoatKit GPS source, retains meaningful movement, filters implausible jumps, and sends a daily stationary keepalive. No separate Signal K server or plugin is required.
The per-boat API key is a credential. BoatKit stores it as a write-only device secret, never returns it to Viewer clients, and excludes it from portable backups. noforeignland also assigns each publishing product its own provider identifier. The integration is implemented, but official production publishing remains unavailable until noforeignland issues BoatKit its own provider key; self-hosted builds can supply a BoatKit-specific key at runtime.
Local-first delivery
When the Internet is unavailable, BoatKit continues to queue eligible track points locally while its vessel runtime and GPS source remain active. It retries those points oldest-first after connectivity returns. A dedicated BoatKit device is the best fit for continuous tracking; an app-hosted vessel can collect only while the mobile runtime remains active.
The integration is deliberately one-way. It updates your own noforeignland journey but does not import the service’s places, reviews, boats, posts, routes, or journeys into BoatKit. Avoid enabling multiple publishers for the same boat because conflicting tracking sources can create journey errors.
For the API-key path, sampling behavior, offline recovery, and troubleshooting, see the BoatKit noforeignland setup guide.
noforeignland is a third-party service. This integration does not include a noforeignland account or control its service availability and data policies.