PORT DATA FOR YACHT DESIGN

Understand what a design choice means at the harbour edge

LOA, beam, draft, air draft and utility decisions shape the set of harbours a yacht can plausibly use. MaritimIQ gives designers and technical teams a structured way to explore those consequences across real harbour evidence—without treating incomplete global data as a design rule or safe-navigation assessment.

Explore the portal See API access

Explore how dimensional scenarios change recorded harbour compatibility.

Identify which constraints are authoritative, contextual, conflicting or not yet evidenced.

Give owners a clearer explanation of operational trade-offs during design and refit decisions.

WHY THIS ROLE NEEDS IT

Replace fragmented research with a governed record.

Describe, compare and plan the physical and service environment that yachts depend on.

Small dimensional changes can matter

Draft, beam, air draft or LOA changes may alter access to a preferred cruising programme or home-port infrastructure.

Port data has different authority levels

Contextual bathymetry, directory values and official controlling depths cannot be treated as interchangeable.

Global completeness is uneven

A missing restriction does not prove unrestricted access; it may only reveal a coverage gap requiring specialist verification.

Yacht design scenario evaluated against Port Hercule dimensions — Vessel-to-harbour feasibility
Change the yacht envelope and inspect why the harbour result changes—or why evidence is insufficient.
Open in portal

ROLE-SPECIFIC FEATURES

The product capabilities that matter to builders & naval architects.

Parametric compatibility

Test design scenarios against supported LOA, beam, draft, air-draft and infrastructure constraints.

Datum-aware hydrography

Keep depth type, vertical datum, observation and source class attached to every relevant value.

Approach geometry

Inspect recorded entrances, channels, locks, bridges and breakwater context without generating a route-to-go.

Utility requirements

Compare shore-power and water specifications with the yacht's intended systems and operating profile.

Explainable design trade-offs

Show owners which preferred destinations are supported, constrained or simply insufficiently evidenced for the scenario.

USE CASES

Where the database earns its place.

Concept-envelope study

Compare several LOA or draft scenarios against a selected set of owner-priority ports.

Refit impact review

Evaluate whether a modification to draft, appendages or power requirements changes recorded compatibility.

Delivery planning context

Prepare a candidate port list for detailed route, chart, pilotage and operator review before handover.

COMMERCIAL API ACCESS

Use the same intelligence in your own systems.

Use the API in design studies, digital twins or owner portals to run repeatable compatibility scenarios. Responses retain evidence quality so models can separate a known limit from an absent fact.

Developer documentation API reference

Useful endpoints for Builders & naval architects

POST/v1/compatibility

Evaluate dimensional design scenarios against harbour evidence.

GET/v1/harbors/:id/hydrography

Retrieve typed depths, datums and supporting observations.

GET/v1/harbors/:id/approaches

Inspect recorded approach-channel and restriction context.

GET/v1/harbors/:id/utilities

Compare shore-side utility specifications.

Bearer keys, plan-aware limits and explicit scopes apply. API output is decision support—not a navigational chart, safety approval or live berth reservation.

Port Hercule dimensions and operational evidence for naval architects — Port Hercule intelligence dossier
The harbour dossier keeps reported dimensions, confidence and live context visibly separate.
Open in portal

A PRACTICAL WORKFLOW

Evidence in. Clear next step out.

Model

Define the yacht scenario and the ports important to the owner profile.

Stress-test

Run the same scenario across evidence-backed harbour constraints and review gaps.

Validate

Move material assumptions into formal naval, class, hydrographic and operator diligence.

TRUST MODEL

Honest about the limits of maritime data.

Provenance visible

Decision-critical facts keep their source, observed date, confidence and conflict state.

UNKNOWN stays UNKNOWN

Missing evidence is never quietly translated into no, zero, available or safe.

Licensing-aware

Accessible source material and permitted redistribution remain separate decisions.

QUESTIONS

Frequently asked.

Is MaritimIQ suitable for design approval?

No. It is an early-stage intelligence input. Class, flag, yard engineering, official hydrography and competent authorities control design and operational approval.

Does the API calculate a safe route?

No. It exposes harbour and approach evidence for decision support and does not generate an official route, chart or safety clearance.

How are missing port dimensions treated?

They remain UNKNOWN or produce INSUFFICIENT_DATA. The platform does not infer unrestricted access from an empty field.