Publish your BoatKit track to noforeignland

Connect BoatKit to noforeignland to keep your boat's position and journey updated from the GPS data BoatKit already receives. BoatKit sends the track directly to noforeignland over the Internet. Uploads do not pass through BoatKit Cloud.

This is a one-way publishing integration. It does not bring noforeignland places, boats, posts, reviews, routes, or journeys into BoatKit.

What you need

• Administrator access to the vessel in BoatKit.
• Completed BoatKit vessel setup and registration.
• A noforeignland account with a boat configured.
• BoatKit receiving a recent, trusted GPS position.
• An outbound Internet connection for delivery. BoatKit can queue points during an outage, as described under Offline operation.

Use one tracking source

Avoid running multiple tracking sources for the same noforeignland boat. Conflicting sources can create errors in the displayed journey. Review noforeignland's tracking error guidance before switching an existing provider to BoatKit.

Connect BoatKit

1. Sign in to the noforeignland website. The Boat API Key is not available in the noforeignland app.
2. Open Account > Settings > Boat tracking > API Key and copy the key for the correct boat.
3. In BoatKit, open Settings > Integrations.
4. Select Add Integration, then Cloud Logging > noforeignland.
5. Enter the Boat API Key.
6. Enable noforeignland integration.

BoatKit begins collecting eligible position points and attempts a direct upload about every ten minutes.

noforeignland also requires every publishing product to identify itself with a separate provider API key. BoatKit supports receiving that identifier at build time, but official production publishing remains unavailable until noforeignland issues BoatKit its own key. If the panel says the build does not have provider access configured, it cannot upload. Self-hosted development builds can set GOATKIT_NOFOREIGNLAND_API_KEY with a BoatKit-specific key issued by noforeignland; this is different from your per-boat key.

Confirm it is working

In the BoatKit noforeignland panel, check the following:

• The connection message says noforeignland is receiving BoatKit track updates.
• Last attempt shows when BoatKit most recently contacted noforeignland.
• Last successful upload shows a recent acknowledged upload.
• The number of points waiting to upload falls to zero when Internet access is available.
• Last position queued advances as the vessel moves.

Then open your boat on noforeignland and confirm its position or journey. A successful BoatKit upload means noforeignland acknowledged the track; provider-side display processing can still take a little longer.

A zero queue alone does not confirm GPS collection. BoatKit does not create a point without a recent valid position, and it deliberately suppresses stationary duplicates.

What BoatKit sends

BoatKit sends only timestamped latitude and longitude points for this integration.

It checks for a recent position once a minute. After the first point, BoatKit retains another when the vessel has moved at least 80 meters. It rejects a point that would imply movement faster than 50 meters per second from the previous accepted point, which helps prevent an implausible GPS jump from appearing in the journey. While stationary, BoatKit retains one keepalive after 24 hours.

Points are sent in bounded, oldest-first batches. BoatKit does not send other sensor readings, vessel settings, account data, photos, posts, or messages through this integration.

Offline operation

An Internet outage does not stop local collection while BoatKit, its vessel runtime, and the GPS source remain active. BoatKit queues unsent points locally and retries them in order when connectivity returns.

The recovery queue is bounded to at most 366 days at the maximum one-minute collection rate. A dedicated BoatKit device can collect continuously while the device, BoatKit runtime, and GPS source remain running. An app-hosted mobile vessel collects only while the BoatKit app and its vessel runtime remain active; it is not an always-on tracking path.

Credentials and backups

BoatKit stores the Boat API Key as a write-only device secret. It is never returned to Viewer clients and is excluded from portable backups.

Replacing the Boat API Key or removing the noforeignland integration clears all queued noforeignland positions. This prevents stored locations from being delivered to another boat. The recovery queue is also excluded from portable backups.

After restoring a BoatKit portable backup, enter the Boat API Key again. If the integration was restored as enabled, it remains blocked until you re-enter the key.

Current limitations

The integration currently publishes the vessel's BoatKit track to noforeignland. It does not:

• Import noforeignland places, reviews, boats, posts, routes, or journeys
• Read or edit the noforeignland boat profile
• Publish photos, logbook text, or BoatKit sensor telemetry
• Expose noforeignland controls inside BoatKit

noforeignland is a third-party service. BoatKit does not supply the noforeignland account, privacy policy, data retention, or service availability. See noforeignland's external tracking guide and official Signal K publisher for provider-owned references. The Signal K publisher is not required for BoatKit, and its provider key must not be reused.

Troubleshooting

Symptom	What to check
noforeignland is not available under Add Integration	Confirm that you have administrator access and that BoatKit is up to date. If it is marked Added, open the existing integration instead.
Set the noforeignland Boat API Key	Copy the key from the signed-in noforeignland website under Account > Settings > Boat tracking > API Key. Do not use an account password or a key from another boat.
This BoatKit build does not have provider access configured	The build operator must configure a BoatKit-specific provider key issued by noforeignland. Do not reuse another integration's provider key.
No position is queued	Confirm that BoatKit currently shows a valid position from a trusted GPS source. A stationary boat normally queues no duplicate until the daily keepalive.
Could not reach noforeignland	Check the vessel's Internet connection. BoatKit connects directly outbound; BoatKit Cloud does not carry these uploads.
The number of waiting points keeps growing	Check the connection message and most recent attempt. Keep the Boat API Key unchanged if you want BoatKit to retain the queued positions.
noforeignland rejected the key or track	Copy the Boat API Key again from the correct boat. If the key is correct, confirm that the position and system clock are valid before retrying.
The journey has conflicting or implausible segments	Disable other trackers publishing for the same noforeignland boat, then follow noforeignland's tracking error guidance.