Backlog

Next up

In Progress

Done

Main Roadmap

It would be convenient if there were ways to convert the degrees from DD to DDM or DMS. DDM and DMS are consistently used by external official bodies for NAVAREA warnings or Singapore Strait boardings. The MOOs primarily use DMS.

In Review

Coordinates

An Anonymous User

The ability to draw a polygon on the map would be beneficial for mapping out areas such as for military exercises.

Polygon Tool

It would be very useful to have the ability to It would be very useful to have the ability to download all vessels currently visible in the map view For example, if I zoom into an anchorage area, it would be helpful to have a UI function that allows me to export the details of all vessels displayed on screen, including vessel name, flag, IMO number and other key fields.This would support analytical workflows by allowing users to quickly capture a defined vessel set based on a specific area of interest, rather than having to manually extract each vessel individually.

Ability to download all vessels currently visible in the map view

Tomas Alexa

The measuring line goes under vessel tracks making it difficult to see.

Measuring Line

Could we please add a feature to colourise vessel tracks based on speed, similar to the functionality available in Marine Traffic?When a vessel is selected, its historical track would be displayed in different colours corresponding to speed ranges. This would make it significantly easier to identify areas where the vessel may have been conducting manoeuvres such as Search and Rescue (SAR) operations, loitering, or experiencing disruptions.This enhancement would provide a much clearer visual representation of vessel behaviour and greatly improve the efficiency of track analysis.

Track Colourisation

It would be very useful to introduce search and rescue zones as a dedicated map layer within Fathom2.While SAR regions often broadly follow EEZ boundaries, this is not always the case. Having a visible SAR-zone layer would help analysts quickly identify which national authority or MRCC has responsibility for a given incident or area of activity.

Search and rescue zones as a dedicated map layer

It would be very useful to introduce a vessel icon colour scheme based on vessel type.For example, tankers, bulk carriers, general cargo vessels, container vessels, tugs, passenger vessels, fishing vessels, offshore vessels and small craft could each be displayed in different colours. This would allow analysts to quickly identify vessel types within a congested port, anchorage or area of interest without needing to click on each individual vessel.

Colour scheme based on vessel type

It would be very useful to introduce a FlightRadar24, ADS-B Exchange, or similar aviation-tracking API as an optional overlay within the platform.This would significantly support GEOINT workflows by allowing users to correlate vessel activity with aircraft movements in the same area of interest. For example, it would help identify maritime patrol aircraft, UAVs, search-and-rescue aircraft, helicopters, surveillance flights, or other aerial assets operating near a vessel, port, anchorage or incident location

Introduction of a  FlightRadar24,  or similar aviation-tracking API

I have noticed that vessels displayed in purple, which I assume are Class B AIS targets, do not currently show vessel names or key details in the pop-up table.We do occasionally use these smaller vessels as part of our monitoring. In some cases, they may be smaller NGO vessels, local law enforcement craft, patrol boats, fishing vessels, or other small craft relevant to an incident or area of interest.It would therefore be very useful if the pop-up table could display available details for these vessels, including vessel name, MMSI, flag, type, dimensions and. Even where the data is limited, displaying the available identifiers would support monitoring, verification and incident analysis.

Purple vessel do not currently show vessel names or key details in the pop-up table.

<h3>Summary</h3>Add selectable basemap modes including Dark, Light, ENC/Nautical Charts and Satellite imagery.<h3>Problem</h3>Users cannot currently adapt the basemap to different operational or analytical workflows.<h3>Proposed Solution</h3>Provide multiple basemap options:<ul><li>Dark mode</li><li>Light mode</li><li>ENC / nautical charts</li><li>Satellite imagery</li></ul><h3>User Value</h3>Different workflows require different visualisation styles. ENC and simplified charts improve navigational awareness and reduce visual fatigue.

Map Visualisation & Basemap

Nick

Feature RequestShow AIS destination and port call context in Fathom vessel details, including destination, port of origin, previous port, and next port where available, so users can assess voyage intent without leaving Fathom.User StoryAs a Maritime Operations Officer or analyst, I want to see a vessel’s AIS destination and port call context in Fathom, so that I can quickly understand voyage intent, detect destination or route changes, and assess whether the vessel’s movement is consistent with expected operational behaviour.Acceptance Criteria:<ul><li>Vessel details show AIS destination where available.</li><li>Vessel details show port of origin, previous port, and next port where available.</li><li>Port and destination fields are visible in the primary vessel details workflow without requiring external lookup.</li><li>Missing or unavailable values are clearly marked rather than hidden or ambiguous.</li><li>Destination and port call context supports anomaly review, including cases where a vessel changes destination, deviates from expected routing, or may be involved in an incident such as Search and Rescue.</li><li>Port/voyage fields use clear labels so users can distinguish AIS-declared destination from enriched previous/next port data.</li></ul>

Planned

High Priority

AIS Destination and Port Call Context

Feature Request Add Exclusive Economic Zone boundaries to Fathom as a named operational map layer and vessel filter, including validated operational coverage for priority regions such as West Africa. User Story As a Maritime Operations Officer or analyst, I want to view and filter vessels by country EEZ in Fathom, so that I can quickly understand jurisdictional context, identify vessels operating in relevant national zones, and prepare operational briefings without switching to ArcGIS, GeoStore, or external map tools. Acceptance Criteria <ul><li>EEZ boundaries are available as a toggleable layer in the Fathom layers panel.</li><li>EEZs are named by country/authority and are searchable/selectable.</li><li>Users can filter vessels by one or more selected EEZs.</li><li>The EEZ filter works with vessel type, flag, tags, lists, selected vessels, and other existing Fathom filters.</li><li>EEZ boundaries render clearly without obscuring AIS tracks, vessel icons, or operational overlays.</li><li>Boundary source and update cadence are documented internally.</li><li>Initial rollout includes validated West Africa coverage, including Nigerian Navy-recognised EEZ boundaries where they differ from generic EEZ datasets, or clearly records any source/data limitation.</li></ul>

Country EEZ Layer and Vessel Filter

Feature Request:Enable selected vessel tracks to load reliably across historical windows and at low zoom levels, so analysts can follow one vessel or a small selected cohort over longer time periods without needing to zoom in past 6.0.User Story:As a Maritime Operations Officer or analyst, I want to view selected vessel tracks over historical periods, including up to one month, at low zoom levels, so that I can reconstruct vessel movements, identify port calls, and understand behaviour without losing the track when zooming out.Acceptance Criteria:<ul><li>Users can select one vessel or a small MMSI-only cohort and view its historical track below 6.0 zoom.</li><li>Selected vessel tracks remain visible globally/across zoom levels where the user is focused on that selected cohort.</li><li>Users can load historical selected-vessel tracks over longer windows, including up to one month where data is available.</li><li>Track loading provides clear progress/status feedback and does not require repeated map zooming to reveal the selected track.</li><li>Behaviour works in both live and historical workflows where selected-vessel history is available.</li></ul>

Selected Vessel Historical Tracks Across Zoom Levels

<h3>Summary</h3>Allow radius and line tools to anchor to specific coordinates.<h3>Problem</h3>Users cannot link analytical tools directly to coordinates.<h3>Proposed Solution</h3>Allow drawing tools and radius overlays to attach to fixed coordinates.<h3>User Value</h3>Improves operational planning and investigation workflows.

Ambrey AI

Main Roadmap