maritimIQ

Finish marina truth first.

maritimIQ will become the most comprehensive trustworthy marina intelligence platform — navigational, operational, guest, shore-access, superyacht, mapping, connectivity, capacity and historical — in one provenance-aware, temporally correct, licensing-safe ledger. Nothing in 2.0 or 3.0 delays closing 1.0.

1.0 · Shipping now

Trusted marina truth

What is objectively known about this harbour, where did it come from, and can we trust or use it?

  • Marina identity, UN/LOCODE, operator, authority, VHF
  • Vessel envelope: LOA, beam, draft, air draft, displacement
  • Hydrography, tide, surge, siltation
  • Stable basin / pier / berth-class identities
  • Restrictions, notices to mariners, conflicts
  • Customs and immigration, after-hours medical clearance
  • Fuel, water, shore power, waste, security
  • Fees as labelled estimates
  • Role-based contacts with verification dates
  • Provenance, confidence, temporal validity

2.0 · Foundations only

Harbor experience & connectivity

How does a guest, owner or captain actually use this harbour — on shore, in the basin, and to the next cruising ground?

  • Shore-access nodes with IATA/GTFS external refs (not copied GTFS)
  • Guest informational maps vs captain briefings
  • Cruising connectivity and next-harbour steaming times
  • Crew logistics, provisioning, concierge
  • Business-yacht / VIP services
  • Explainable busy-time climatology
  • Accessibility as a first-class domain
  • Refit ecosystem and yard identities
  • Minimum realistic transfer times to airports and cities

3.0 · Extension points only

Live operations, capacity & prediction

What is the harbour doing right now, what is allocated, and what is likely in the next hours?

  • Typed observation / time-series foundation
  • Vessel-call identity and alongside milestones
  • Declared capacity kept separate from reservations
  • VTS / port traffic windows never stored as berth slots
  • Lock bookings and bridge openings as their own kinds
  • Occupancy forecasts with drivers, not a mystery score
  • Hurricane / cyclone protocol as operational truth

Six extension points already in 1.0

  1. 01

    Stable basin / pier / berth identities

    Never store a quay later as a string. Every 1.0 harbour already has typed Basin, Pier and BerthClass IDs.

  2. 02

    Typed observation foundation

    Occupancy, wind, tide and movement series share one observation model with an estimate-label rule.

  3. 03

    Vessel-call identity + milestones

    Arrivals, alongside, bunkering and departure will share one call object so history and live ops do not fork.

  4. 04

    Shore-access nodes

    External IATA and GTFS identifiers live on the node. Transit tables are not copied into marina rows.

  5. 05

    Capacity and allocation as separate concepts

    BERTH_RESERVATION, DECLARED_CAPACITY, VTS_TRAFFIC_WINDOW, LOCK_BOOKING and BRIDGE_OPENING never share one Slot table.

  6. 06

    Geospatial layers with audience and licence

    GUEST_INFORMATIONAL, CAPTAIN_INFORMATIONAL and OFFICIAL_NAVIGATIONAL_DOCUMENT can coexist without contamination.