ALURMaritime Route Intelligence
OPEN NETWORK · ESTIMATE
Vessel feasibility ↓
Choose a routeGlobal maritime network
Sea River Estuary estimate Inferred approach
READY WHEN YOU ARE

A distance you can inspect.

Search ports and Indonesian facilities, or use coordinates for your terminal. The route connects covered rivers and sea corridors automatically, with estimated estuary links clearly marked. C is optional.

VESSEL & ACCESS LIMITS

Can this vessel fit?

Preliminary screening

Check your ship or tug-and-barge combination against controlling depths and approved dimensional limits. Unknown data stays unknown.

Select and calculate a route first.
Operating allowances — use your operator / harbour requirements

Use the deepest loaded draft of each hull, including trim and freshwater effects. Squat is a supplied allowance, not an automatic hydrodynamic model. This configuration does not model side-by-side barges, pushing, swept bends or towing capability.

Controlling reaches & terminal limits

Add the river mouth, shallow stretches, bridges and berths that govern this voyage. Blank values are not treated as zero.

CSV template

Inputs are session-only. Export your assessment to keep it. No complete route survey or live water-level feed is connected.

How this route is calculated

Enter From A and To B. C is hidden until Add stop is selected. With C, your voyage is A → B → C in that order. River, estuary and sea sections remain one continuous route.

Geography first, assessment separately

The engine resolves maritime access separately from the selected display location, considers several network connections and compares complete route distances. Mapped-area and sourced river-centreline candidates are land-checked before restriction assessment. Canal alternatives use sourced geometry, and ordinary routes exclude polar corridors unless explicitly enabled. User passage exclusions are separate from system restrictions. A bounded local water search can find an approach around a pier or headland. Every returned segment is checked against the source-aware land mask; there is no unrestricted straight-line fallback.

Missing river-area polygons are not evidence that a mapped river is dry land. Where only an OSM river line exists, a narrow numerical envelope accommodates the source’s approximately 10 m simplification. It is not a channel width. Such sections are marked low confidence. Coastline conflicts and mapped river islands remain blocked. Inferred approaches, river-mouth links and incomplete local data require review.

Restrictions

HARD_BLOCK requires a specific passage, confirmed reliable evidence, a supported rule and an applicable vessel condition. Missing vessel information returns an incomplete assessment. Free-text voyage notes cannot block. Explicit user exclusions are separate route preferences. The engine tries an alternative corridor where possible. CONDITIONAL and WARNING return the route with the concern; INFORMATIONAL adds context. Unknown data and unconfirmed hard-block notices do not automatically reject a geographic route. No live regulatory restriction feed is connected.

Distance and endpoints

Distance is measured along the returned geometry using the existing spherical calculation and exactly 1,852 metres per nautical mile. Leg totals reconcile before rounding. A port’s display coordinate is not assumed to be a berth. The resolver uses supplied access coordinates or searches adjacent water, retaining a separate display location. Port / terminal searches extend to 3 NM, jetties to 0.6 NM, coastal localities to 1 NM and manual points to 0.25 NM. It rejects disconnected access and water–land–water jumps. A source-coordinate adjustment is not sailed, added to mileage or drawn across land. Resolved access is an estimate, not a verified berth. River candidates are considered within 1.5 NM, and sea candidates within 80 NM. These are search limits, not navigability guarantees.

Long approaches and major detours must be inspected. Use Add waypoint, pick water on the map or edit coordinates. Markers can be dragged and vias removed. Removing C also removes corrections belonging to its B → C leg. Export the route to Google Earth or download routing diagnostics.

Location quality

The source directory is preserved. Aliases improve discovery without establishing an official berth identity. Suralaya currently resolves to a nearby mapped jetty with unverified terminal identity; Taboneo and Muara Berau are approximate or historical reference positions, not assigned anchorages. Empty draft, beam, LOA, operator and cargo fields remain unknown.

Vessel and bathymetry limits

The separate vessel screen uses the entered limits, sources, dates and datums. Missing vessel information does not prevent a geographic route. GEBCO remains regional imagery only; its depths are not sampled for route clearance. No tides, weather, live closures, traffic schemes or operational channel surveys are connected.

Detailed coastline covers western Indonesia, the additional Makassar area and the local Suez / Panama gateways and Alghero / Aberdeen endpoint patches. Sourced canal centrelines restore geographic connectivity; transit permission and operating conditions are unverified. Other areas use Natural Earth at 1:10 million scale, which can omit small islands. A source-aware mask pass is a map-geometry result, not a navigation clearance. Confirm the actual berth and local conditions before commercial reliance.

Land-data manifest · Edge audit · Licenses and sources

Indonesia coverage

Add your own jetties

Import name, latitude and longitude from a CSV. Imported records stay in this session; original source files are not uploaded.

CSV template