PCIO VIS Boat

Adds a Boat Register to PCIO VIS Member Event for sailing clubs and other
boat-oriented organisations.

Features

• Register boats with: home harbour, name, type, model, build year, sail
  number and MMSI number.
• A boat belongs to a membership number. Everyone who shares that membership
  number is crew on the boat, so the crew group and the subscription follow the
  same number — there is no separate crew table to keep in sync.
• The home harbour is picked from the shared harbour list and stored by id, so
  the same harbour name cannot drift across boats.
• Members can maintain their own boat and crew from the core member profile —
  no administrator needed.
• When a core member is deleted their boat is removed only if they were the
  last member on that membership number; otherwise the boat stays with the
  remaining crew.
• Boat Register admin page at /vis/boats, access-controlled by the
  vis_boat_manage capability (granted to Editor and Administrator on
  activation).
• Harbours management page at /vis/harbours — list, create, edit, and delete
  harbours on a map, with duplicate-name protection and delete-guard against
  harbours still in use.
• Boat name appears in the core member list; clicking it opens a read-only
  popup with the full boat details and the crew group.

This plugin stores all its data locally in two custom database tables. It does not
communicate with any external service, apart from the harbour map tiles listed
under External services below.

Uninstall

Deleting the plugin from Plugins removes its pcio_me_boat_db_version option, so a reinstall rebuilds the tables from scratch.

The database tables are deliberately kept, because they hold your club’s boat register and harbour list. These tables survive:

• {prefix}me_boat_boats
• {prefix}me_boat_harbours

If you want a full wipe, drop both tables manually from phpMyAdmin or a SQL client. Also delete the leftover {prefix}me_boat_crew table if your site was created before 1.1 — it is no longer used and is dropped automatically on the 1.1 upgrade.

External services

The plugin itself makes no outbound requests: all boat, harbour and member data stays in your local database, no analytics or tracking is included, and no account with any third party is required.

The one exception is the harbour map on /vis/boats and /vis/harbours, which displays map tiles in your browser:

• OpenStreetMap — https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png. Your browser’s IP address is visible to OpenStreetMap, along with the map area you pan to. No boat or member data is sent. Their tile usage policy applies.
• OpenSeaMap — https://tiles.openseamap.org/seamark/{z}/{x}/{y}.png, a transparent overlay of seamarks. Same conditions as above; see the OpenSeaMap site.

The map is only used in wp-admin and requires the vis_boat_manage capability. You can replace both tile URLs in assets/harbour-map.js and assets/harbours-admin.js with your own tile server or a local tile set if you would rather not contact them at all.