Expedition Captain Lite — Proprietary · Browser-based

This guide describes Expedition Captain Lite 9.0.6. The About tab shows the version installed for your current session.

Expedition Captain Lite is a browser-based application for expedition and shipboard route work: import routes and tracks, preview them on a map, edit waypoints, simplify large tracks where appropriate, and export to common marine and GIS formats. Design emphasis is practical file interchange—fast conversion, inspection, light editing, and reliable hand-off to ECDIS and other systems—without claiming to be a certified chart display or mandatory passage-planning system.

Processing runs locally in the browser on the files you load. Route and track data are not uploaded to an Expedition Captain application server for conversion (map tiles and static assets load from the network as in any web app). The About tab summarises privacy and local processing; this guide is available from Operator guide there.

Capabilities (summary)

Supported formats

Imports (indicative)

GPX; .rtz and .rtzp (RTZ route XML and RTZP zip container with embedded RTZ); .rt3 (Transas TSH RtServer v3); KML/KMZ; GeoJSON/JSON; CSV; NACOS XML (.xml with detected content); Olex text (.txt) and gzip (.gz); Sperry legacy .route.

PC Maritime route revision filenames: PC Maritime route revision files may be stored as .rtz.1, .rtz.2, .rtz.5, and similar .rtz.<integer> names alongside plain .rtz. These are standard RTZ 1.0 XML and import the same way. Verified with supplied PC Maritime routes. Drag-and-drop is the recommended import path for revision filenames; the file picker filters to common extensions such as .rtz and may not list every revision suffix on all platforms (choose All files if needed).

Exports

GPX; RT3 (Transas / Navi-Sailor); RTZ 1.0; RTZ 1.0 (Sperry ECDIS); RTZ 1.2; KML; GeoJSON.

Always verify exports on the target ECDIS or planner before operational use.

Quick start

1. Open the Expedition Captain operational platform at https://expeditioncaptain.app. Documentation and ecosystem information are published at https://expeditioncaptain.com.
2. Upload a route or track file.
3. Set output format and filename on the Route tab.
4. Preview & edit — review the map and table; edit as required.
5. For large tracks, adjust simplification if offered.
6. Convert & download — exports reflect the current route on screen and the export rules above.

Clear unloads the session; it may prompt if there are unsaved edits since import or last successful export.

Replacing the working route: uploading a new file while the route has unsaved edits (changed since import or last successful export) opens a confirmation dialog before the file picker. Confirming replaces the working route and discards session edits; the map and table refresh from the new file. The same guard applies when Preview & Edit would reload or replace the current route.

Route vs track

Tracks (e.g. time-stamped GPX tracks, or data parsed as a track) expose simplification controls and related behaviour. Routes (waypoint-style data) are fully editable and exportable but do not use track-only simplification UI. Classification follows the source format and content (for example GPX track segments versus route waypoints).

Map preview: routes

On waypoint routes, the map draws a preview line so bends read clearly at harbour and coastal scales. Where a waypoint has a valid turn radius (NM), the preview shows a rounded turn that follows your imported or edited radius. This is a review aid only—not ECDIS execution and not a substitute for validating the route on your equipment.

Waypoint positions in the table and in export files are the authoritative route. The preview line is for visual review and for choosing where to insert waypoints on open leg segments; it does not change stored coordinates or interchange files.

If a corner cannot be drawn as a full arc (for example a very shallow bend, a tight leg, or a very large route), the preview may use a simpler bend so the route remains readable. In those cases, rely on the table and on export verification rather than the preview alone.

Tracks do not use this route preview refinement; very large tracks may use lightweight polyline rendering without per-vertex markers (see Large tracks).

Navigation HUD and chart orientation

Screen-fixed navigation chrome sits above the map and stays readable when the chart is rotated:

• Scale bar — shows current chart scale with operator-friendly graduations; updates as you pan and zoom.
• Orientation control — compass rose with current bearing readout; click to return to North Up with a smooth animated reset.

The HUD does not rotate with the chart. Route geometry, corridors, and tactical overlays remain on the map layer beneath it.

Right-click drag (or equivalent rotation gesture) can rotate the chart. Use the orientation control when you need to recover North Up.

Chart waypoint labels (routes)

After Preview & Edit, use the Labels control on the chart toolbar to cycle:

Labels favour waypoints inside the current map view, then fill remaining slots up to an internal cap. In Labels and Names modes, overlapping chart labels are suppressed (same screen-bounds check) so text stays readable on dense routes.

Renaming a waypoint in the table updates chart labels immediately when Names is active.

Waypoint radius units by format (all normalised to NM internally):

Editing turn radius on the map

On routes, at close zoom (approximately level 13 and above), a handle appears on each accepted fillet arc. The handle sits just inside the turn angle on purpose: it keeps the waypoint easy to drag while still giving a precise radius control.

Drag the handle to change that waypoint’s turn radius (NM); hold Shift for finer steps. The preview updates immediately; waypoint positions and exports use the updated radius value, not moved vertices.

On hover or drag of a radius handle (zoom 13+), a map tooltip shows the waypoint (number and name), turn radius (NM), and drag hints. When local geometry limits the achievable arc, the tooltip shows the effective radius and your stored radius separately. The tooltip hides when the pointer leaves the handle or the map, and at the end of a drag until you hover again. Zoom out to review the whole route without accidental radius edits.

Operational route table

Below the map, the route table separates waypoint (turn) data from leg data:

• Waypoint rows — number, name, position, turn radius, turn Port and turn Stbd XTD, turn speed, distance run, and distance remaining to the route end.
• Leg rows (for example 3 → 4) — bearing, leg distance, and the same Port XTD, Stbd XTD, and Speed columns (leg domain for that segment). Use the + on a leg row to insert at the leg midpoint when geometry allows.

Waypoint number, name, and the Actions column stay visible when you scroll sideways. When the table is wider than the window, drag horizontally on the table to pan; a brief cue may appear until you have panned once.

Operational columns (shared headers; meaning depends on row type):

Display and edit units (Radius and XTD): Click the Radius header or either Port/Stbd XTD header to toggle the global table display between nautical miles and metres. Port and Stbd XTD always share one mode; Radius has its own independent mode. Cell values show a unit suffix (for example 0.250' in NM mode, 463m in metre mode, 12kn for speed, 245° for bearing, 5.4' for leg/distance-run/distance-remaining columns). When editing, enter the numeric value only (for example 0.25, 250, or 12); the value is converted to nautical miles or knots before storage. Apply menus, cell hints, and brief status messages use the active display unit. Import, export, RTZ, GPX, and corridor calculations are unchanged — values are still stored in nautical miles and knots.

Edits use compact inline fields. Values match import and export where the format supports them.

Corridor (XTD) semantics: leg and turn corridor widths are stored on each waypoint in the route table. Turn XTD values are separate from leg-domain values on dual-domain routes. Values you set in the table or import from a file are exported as-is; empty cells are not filled with manufactured defaults on export.

Copying turn radius, XTD, or speed to other rows

When you apply a value to other rows, Expedition Captain Lite uses the first cell you selected as the source—not necessarily the cell you right-click. If you are not using a multi-row selection, the right-clicked cell is the source. On waypoint rows, Port/Stbd XTD and speed apply in the turn domain; on leg rows, in the leg domain.

1. Right-click a cell that already has a value. Choose Apply this … to route start or Apply this … to route end to copy that cell's value along the route (upstream or downstream from the clicked waypoint or leg).
2. Drag-select along waypoint or leg rows in the radius, Port/Stbd XTD, or speed columns. Related columns stay grouped: corridor (Port/Stbd XTD), radius, speed. With two or more rows selected, right-click the source cell and choose Apply … to selection (menus show the value in the active display unit, for example Apply 12kn to selection or Apply 250m to selection). Route-start and route-end entries are omitted when you operate inside an active selection. Shift+↑/↓ extends the selection vertically within the same column family; Shift+←/→ on Port or Stbd XTD expands or contracts the corridor selection horizontally (waypoint range unchanged).

XTD menus on dual-domain routes: inside an active Port or Stbd selection, choose Turn widths, Leg widths, or Corridor widths to apply turn widths, leg widths, or both. Labels use the source value in the active XTD display unit. On single-domain routes, a single Apply … to selection entry applies leg widths.

Speed copies to both turn and leg speed fields within the selected rows (turn speeds on selected waypoint rows; leg speeds on selected leg rows), using the first selected cell as the source.

Radius applies only to selected waypoint rows; leg rows are not radius targets.

Each apply action is one undo step (for example Undo XTD batch or Undo radius batch). Hover the undo button for the full scope.

Inserting waypoints

• Leg row + — insert at the leg midpoint when the leg is open.
• Map — click an open trim-to-trim segment on the preview line (not through consumed turn geometry).
• Reference mark — Insert waypoint here on the mark menu places a waypoint on the nearest editable leg (same trim geometry as map click; mark clears after success).
• Route start / end rows — insert before the first or after the last waypoint.

Insertion is refused on segments already consumed by turn geometry, or where the new corner cannot fit—you receive a clear message rather than a silent failure.

Waypoint names

• Click the name cell to select it; double-click, F2, or Enter (when selected) enters edit mode.
• Long names scroll inside the cell while typing (scrollbar hidden; caret stays visible).
• Escape while editing cancels and restores the prior name; the cell stays selected.
• See Waypoint table keyboard (spreadsheet-style) below for Tab, arrows, and selection behaviour.

Tracks (no leg rows): bearing, leg distance, and distance run remain on the waypoint row for the inbound leg.

Route navigation

After Preview & Edit, the bar below the chart helps you work through long routes without scrolling the full table for every check.

Selecting a waypoint centres the map on that position at close zoom so turn-radius handles stay available when you step along the chain. The route table highlights the corresponding row while you hover a waypoint on the chart.

Corridor display and review (routes with XTD)

When the route has cross-track distances, the route navigation band provides corridor controls next to the waypoint selector:

Both preferences are saved for the session. The corridor outline is display-only — it is rebuilt from waypoint XTD values and the route preview; nothing is stored as a separate corridor polygon.

Corridor display policy

Some route formats support separate corridor widths for route legs and for turns.

Expedition Captain Lite preserves the original corridor values contained in the route file and exports those values unchanged whenever the route format supports them.

Different navigation systems may present those corridor values differently on the chart. Expedition Captain Lite applies a consistent display policy when drawing turns so that corridor lines remain stable and visually unambiguous around small-radius turns and corridor-width transitions.

As a result, the corridor shown on screen may not always look identical to the presentation used by another ECDIS or route-planning system, even though the underlying route data remains the same.

This affects chart presentation only. It does not modify the route data, corridor values, or export fidelity.

When reviewing routes that contain separate leg and turn corridor widths, operators should refer to the stored corridor values if an exact interpretation of third-party corridor presentation is required.

Reverse route preserves the geographic corridor footprint: port and starboard XTD values are remapped correctly when waypoint order is reversed end-for-end.

Corridor review (advisory only) runs after you change XTD or radius, reverse the route, load a file, or undo/redo. It does not block edits or change your route. If Expedition Captain Lite finds configurations that may need a second look (for example a large width change between legs, a small turn radius with wide corridors, or strong port/starboard asymmetry), a warning message appears, for example:

Corridor review — 3 corridor items need review. Press I to show this message again.

Press I to show the last message again. You remain responsible for validating corridors on your ECDIS or passage plan before operational use.

Waypoint table keyboard (spreadsheet-style)

After commit (Enter, Tab, or click outside), the active cell stays selected so you always know where the next keypress applies. Press Escape again (without editing) to leave the table workflow. Chart interaction (clicking the map, a waypoint, the route, or starting EBL/VRM/ruler/mark tools) also clears table selection when you return to the chart.

Visual states: Selected cells show a subtle amber outline; editing cells show orange styling (numeric fields use an orange input border only, not a double border).

Keyboard and interaction shortcuts

Press F1 anywhere outside a text field to open the in-app keyboard shortcut reference. The tables below match what you see when you press F1 in the app and in the printable handbook appendix. Press Escape to close the reference modal.

The Waypoint table keyboard section above describes spreadsheet-style selection and editing workflow in more detail. Where a binding appears in both places, the F1 reference is authoritative for the key assignment.

A compact Category | Shortcut | Function printable page is included at the end of the downloadable operator handbook (operator-handbook.html).

Chart overlay declutter (H)

While Preview & Edit is active, press H (outside text fields) to cycle chart overlay declutter:

Declutter affects transient chart chrome (for example tactical hover hints), not your route geometry, corridor lines, or waypoint data.

Compatibility tab

The Compatibility tab is an indicative guide to how route and track files typically move between Expedition Captain Lite and other navigation or planning systems. It is not a certificate of how your specific ECDIS, plotter, or planner will behave on every firmware build.

How to read the table

• Expedition Captain Lite (reference) at the top shows what Expedition Captain Lite imports and exports today, including full route data retention in normal use.
• Formats with both import and export use paired In / Out columns; import-only formats (CSV, NACOS XML, Olex, Sperry .route) share one compact centred In column (width from the longest first-line label word only). Route data is a single narrow column — not a full In/Out pair.
• Other products are grouped by type (for example ECDIS, chartplotters, PC planners). Scroll down to compare.
• In and Out show whether GPX, RTZ, RT3 (Transas), KML/KMZ, GeoJSON, and other listed formats are usually accepted in each direction.
• Route data summarises whether positions, names, turn radius, port/starboard corridor widths, and leg speed typically survive a round-trip through Expedition Captain Lite — not whether the on-screen preview matches every detail on target equipment.
• Symbols: ✓ supported in typical use; △ partial or firmware-dependent; ✗ not supported or not applicable; ? not routinely verified — confirm locally. RT3 (Transas) is native on Transas/Navi-Sailor planners and supported in Expedition Captain Lite; most other systems show ✗ because RT3 is not their route interchange format (not “unknown”).
• Hover any symbol for a short operational note.

Always confirm with a sample export on the target system before operational use.

PC Maritime Navmaster ECDIS: the matrix includes a row for Navmaster ECDIS RTZ interchange. PC Maritime route revision files may be stored as .rtz.1, .rtz.2, .rtz.5, etc.; Expedition Captain Lite supports these as RTZ 1.0 XML. Use drag-and-drop for revision filenames for the most reliable import experience.

The in-app Compatibility tab shows the compatibility matrix described above.

Compatibility disclaimer

All product names, manufacturer names, software names, and file format names referenced on this page are trademarks or registered trademarks of their respective owners.

Expedition Captain is an independent product and is not affiliated with, endorsed by, sponsored by, or associated with any of the manufacturers, organisations, or companies listed.

Compatibility statements refer solely to Expedition Captain's ability to import data from, export data to, or otherwise interact with the listed file formats. Such compatibility does not imply any official relationship, approval, endorsement, certification, partnership, or commercial association with the manufacturers or developers of the hardware, software, or services that produce or consume those file formats.

Cursor telemetry (inspection mode)

Beneath the chart, the Cursor block supports coordinate inspection while route preview is active. Cursor is not a general map-click mark tool.

• Enable or disable with the Cursor checkbox. When disabled, LAT and LON show — placeholders (fields remain available for entry).
• While Cursor is on and the pointer is over the chart, LAT and LON update live in the strip. When the pointer leaves the chart, readouts return to — unless you are editing a field.
• A subtle plotting plus (+) appears on the chart during inspection. It is replaced by tactical handle cursors when you hover or drag a frozen EBL/VRM handle.
• Map click does not place, move, or freeze a position. To set the session reference mark, enter valid latitude and longitude in the strip (active format DDM, DD, or DMS via the header control) and press Enter or leave the field; the map centres on that position and the mark updates.
• Ctrl+V in either field pastes paired coordinates. Right-click a LAT or LON field for Paste coordinates. Click a field to select its contents for quick overwrite.
• Any operational chart action disengages Cursor immediately: placing or fixing EBL/VRM/ruler, dragging a frozen tactical handle, inserting or dragging a waypoint, dragging a turn-radius handle, and similar. Re-enable Cursor from the checkbox when you want inspection again.
• There is no floating cursor coordinate tooltip on the chart; the strip readouts are authoritative. Default chart hover tips for waypoints and route context are suppressed while Cursor is active where applicable.

Chart review aids (EBL / VRM and ruler)

For on-chart review only—not ECDIS execution and not written into exports:

• Up to two overlays labelled EBL / VRM 1 and EBL / VRM 2, plus one ruler.
• Right-click open chart space → Move reference mark to here, start EBL / VRM 1 or EBL / VRM 2 from here, or Ruler from here (right-click does not clear an existing ruler).
• Right-click a waypoint or the reference mark for the same starts, Paste / Copy coordinates, Insert waypoint here (mark at exact coordinates on the nearest editable leg; mark clears after successful insert), or Delete mark.

Live placement: move the pointer to set bearing and distance, then click to fix the overlay. Press Esc to cancel. Starting placement disengages the Cursor inspection tool.

Frozen overlays: after fixing, use invisible handles on the chart (semantic cursor on hover):

Short hover hints (for example Move EBL/VRM, Adjust EBL, Adjust VRM) appear at the pointer; they hide as soon as you press or drag. There are no persistent floating bearing/distance labels on the chart—use the navigation strip readouts under each active EBL / VRM toggle and the Ruler block.

Strip controls: EBL / VRM 1, EBL / VRM 2, and Ruler toggles show live / fixed / inactive state. Uncheck to remove an overlay. You may edit bearing and distance numerically in the strip; mouse wheel over a distance field steps in increments that scale with the current value (Shift for a finer step). Bearing steps use 1° ( 0.1° with Shift ).

If both EBL/VRM slots are occupied and you start another without choosing a slot, a compact menu asks which overlay to overwrite. Tactical geometry uses rhumb-consistent lines and range rings and remains usable across pan, zoom, and routes near the antimeridian.

Waypoint table height

Above the waypoint table, a slim resize handle lets you drag to increase visible table height for dense routes. Double-click the handle to toggle between default and a modest expanded height. Waypoint columns, sticky headers, horizontal pan, and apply-to-selection behaviour are unchanged.

On-screen guidance (tooltips)

Operational tips use a single restrained style: light tips on panels and controls, dark tips on the chart.

• Cursor — strip readouts only; no chart-following coordinate tooltip.
• Tactical handles — short hover hints on frozen EBL/VRM handles only; hidden during drag.
• Chart background — one brief route-context message when you enter the chart (when Cursor is off); not a persistent label.
• Message recall — press I to show the last status message again (when one exists).
• Waypoints and radius handles — coordinate and radius guidance where applicable.
• Controls — hover for guidance; tips clear when you click, focus, or start editing.

RTZ corridor and radius (operator notes)

Corridor widths in RTZ files are in nautical miles. After import, compare Port and Stbd XTD (and radius if used) against your ECDIS before operational use. RTZ export writes explicit table values only; imported defaultWaypoint metadata is preserved on re-export when present—always verify the downloaded file on target equipment.

RT3 (Transas / Navi-Sailor)

Schedule selection (speed): Expedition Captain Lite picks (1) Calculation with CalcDone="1", else (2) CalcName normalised to Schedule1 / Schedule, else (3) the schedule with the most non-zero Speed values, else the first schedule. Only speeds > 0 kts are applied. ETA/ETD/Stay and additional schedules are not imported.

Not imported: turn XTD, UKC, weather, UserXML, CustomData, LegType semantics, and proprietary voyage data blocks.

Export: Expedition Captain Lite writes RT3 (Transas) with document-order waypoints, packed DDM coordinates, Port/Stb XTE (leg domain), turn radius, and Schedule1 speeds when present. LegType is exported as 0. Not exported: turn XTD, ETA/ETD/Stay, UserXML, CustomData, UKC/weather blocks. Export uses operational values from the working route — not ECDIS Route Manager lossy defaults (fixed 0.1 NM XTE, etc.). Tracks cannot be exported as RT3.

Round-trip: Re-importing an exported RT3 preserves geometry, corridor, radius, and speeds within normal float tolerance; empty source names may appear as WP n on re-import.

Undo and redo

Undo and Redo work at operation level, not per keystroke. One drag of a radius handle, one waypoint insert, one corridor-width apply action, or one rename is one undo step.

Toolbar labels stay short (for example Undo waypoint insert, Undo XTD batch). Hover the button for a full description (which waypoint, how many downstream values changed, and so on). Keyboard: Ctrl+Z / Ctrl+Y (Cmd on macOS).

Manual Coordinate Entry

Waypoint table coordinates are displayed in DDM (degrees and decimal minutes). While editing, you may enter DDM or decimal degrees (DD); committed values are stored and shown in DDM.

Accepted latitude examples (DDM):

• 54°30.500' N
• 54 30.500 N
• 5430.500N

Accepted longitude examples (DDM):

• 003°45.250' E
• 003 45.250 E
• 00345.250E

DD examples while editing: 54.508333N, -3.754167, or six-decimal forms with hemisphere letters.

Compact numeric DDM entry uses fixed degree widths:

• latitude uses 2-digit degrees (5430.500N -> 54°30.500' N)
• longitude uses 3-digit degrees (00345.250E -> 003°45.250' E)

If no hemisphere is entered during editing, the existing waypoint hemisphere/sign is retained.

Click a LAT or LON cell to select that waypoint’s coordinate pair (both LAT and LON highlight). Double-click or F2 enters edit mode. Ctrl+V pastes paired coordinates into the selected row when the clipboard holds a lat/lon pair. Right-click a LAT or LON cell for Paste coordinates (menu, not automatic paste). Pasted DDM values retain degrees and decimal minutes (for example 48° 12.345' N is not reduced to degrees only). Enter commits; Escape cancels and restores the prior value (all editable columns including name); a second Escape clears selection when not editing; Tab / Shift+Tab move between editable cells.

Context menus (coordinates and chart)

• Waypoint table — right-click a LAT or LON cell for Paste coordinates when a lat/lon pair is on the clipboard.
• Cursor strip — right-click the readout or a LAT / LON field for the same action.
• Map — waypoint, tactical, and reference-mark menus open from the chart; they stay inside the map viewport (not over side panels or external chrome).
• Table and strip menus — clamp to the browser window when the map does not fill the screen.
• Placement is above and to the right of the pointer where possible; at edges menus flip left or slide downward so every item remains visible without scrolling the page.

Large tracks

Very large tracks may use lightweight map rendering (polyline plus sparse labels; no per-vertex markers on very dense tracks) to keep the UI responsive. You can still edit via the table and relevant map actions; Focus Route fits the view to the current working route. Warnings may appear when simplifying or exporting very large tracks.

Safety and responsibility

Expedition Captain Lite assists with conversion, inspection, editing, and export. It is not a certified ECDIS, ENC display, or mandatory voyage planning system. The master and bridge team remain responsible for validating routes, complying with regulations, and safe navigation. Simplified or converted data must be checked on the intended equipment before operational use.

Installability and browsers

You can add the app to your home screen, use an install or create shortcut option where your browser offers it, or keep using it in a normal tab. What you see depends on your browser and device: Chrome and Microsoft Edge usually give the most reliable install, taskbar, and “app-like” full-screen launch. Other browsers may only save a shortcut that opens like an ordinary website. The name and icon on your home screen or taskbar are chosen by the browser or operating system, not only by the app itself.

On Firefox for iOS, the experience often stays closer to a regular browser tab than to a separate app icon—this is normal for that environment, not a fault in Expedition Captain Lite.

For the most predictable behaviour when pinning or installing, use https://expeditioncaptain.app as your entry address.

The marketing site and Expedition Captain Lite on expeditioncaptain.app share the same restrained nautical chart atmosphere on a common schedule (the same background artwork during each UTC day). This is visual consistency only — it does not change your route data or exports.

Technical notes

• Online use: Map tiles and other assets load over the network when you are connected. The app does not run as a full offline program—use it like any other website that needs connectivity for maps and updates.
• Privacy: Core parsing and export run in your browser; the usual workflow does not upload your voyage files to an Expedition Captain server for conversion.
• Export filenames: the suggested save name may replace spaces with underscores (especially helpful on some phones and Firefox on iOS). That affects only the suggested download name, not the data inside GPX, RTZ, or other exports.
• Guide export: About → Operator guide → Download guide saves a single HTML file with the same operational text as this guide, suitable for offline reading or printing from your browser’s Print dialog.
• Version display: The About tab and Download guide title show the version you are running. If About shows a different version from this guide’s opening line after an update, refresh the page or reopen from the operational URL.
• Guide viewing / printing: The exported guide is meant for normal browser viewing and native print (including Save as PDF where the browser offers it). Save as PDF / print-to-PDF workflows are typically most consistent in Chromium-based browsers (Chrome, Edge, and similar). Print layout may vary slightly between browser engines and with different printers or PDF drivers—check a quick preview before relying on a specific pagination for operational circulation.

Operational feedback

Operational feedback, compatibility reports, and format edge cases are welcome. This is optional guidance for anyone choosing to report an issue—there is no automatic collection and no obligation to supply more than you are comfortable sharing.

When reporting import/export problems or route-format anomalies, it is particularly useful to include, where you can:

• the original route or track file (or a minimal redacted sample that still reproduces the behaviour);
• browser name and version;
• the make, model, and software/firmware version of the originating or target ECDIS or routing/planning package, if known.

That context materially speeds investigation of RTZ behaviour, schedule or extension variants, and manufacturer-specific differences. If a file cannot be shared, a short written description of the workflow (create → export → re-import on which system) still helps.

Feedback channels are listed under Contact and in the About tab/footer links.

Licence

Expedition Captain Lite is proprietary software supplied as a hosted web application. Use is governed by the licence terms available via Licence in About. You must not modify the software, create derivative works, redistribute it, or use it outside the permitted scope except as expressly agreed in writing with the copyright holder. This is not a permissive or public licence.

Contact

Product feedback may be directed via the About tab and footer Support link. For operational or import/export issues, reports are most useful when they include steps to reproduce, browser and version, approximate file type/size where relevant, and—if available—the original file plus ECDIS or routing software make/model/version (see Operational feedback above).