Liner Polygon Events

The Polygon Event API enables historical and real-time tracking of containers and passenger vessels as they enter or exit defined maritime zones, such as ports, canals, anchorages, terminals, shipyards. By leveraging over 12 years of AXSMarine’s proprietary AIS data, this API provides structured insights into vessel movements across 60,000+ AXSMarine proprietary polygons.

A Polygon Event represents a vessel’s movement through a strategically defined maritime zone, triggered when the vessel enters and exits the area. Each event is captured through two key AIS signals: entry (the first AIS signal detected within the polygon) and out (the last AIS signal before the vessel leaves the polygon), as reflected in the API response.

Key Features

🚢 Vessel Activity Insights – Identify when a vessel enters and exits a geofenced area using the first and last AIS signals within the polygon. Each “Polygon Event” captures both entry and exit parameters, providing a detailed snapshot of the event.

📍 Geofenced Tracking – Track vessel movements through custom-defined zones including anchorages, canals, terminals, and more using polygon-based detection.

📌 Service Identification – Each event includes vessel_service_name and vessel_service_id, representing the service the vessel is part of. This enables deeper segmentation of vessel activity based on service context.

⏱ Event Duration – Calculate time spent within the polygon to support congestion analysis or loading duration metrics.

📊 Time Series Ready – Use historical event data to generate time series charts of port activity, vessel counts, and duration.

🚨 Activity Alerts – Monitor live “open” events to trigger alerts when vessels enter specific zones or are still present within them.

🎯 Flexible Filtering – Apply filters by:

• Vessel IMO, DWT, or other specifications
• Polygon ID, name, or type (e.g., anchorage, canal)
• Entry or exit timestamps and AIS attributes
• Filtering with is_open_event = true is recommended for tracking real-time vessel activity.

📚 Data Depth – Access a comprehensive archive of over 12 years of containers and passenger vessel tracking data, suitable for trend analysis and predictive modeling.

📦 Efficient Pagination – Manage large datasets using link-based pagination via the "links" object (e.g., { "next": "" }). Results are limited to 10,000 events per page. For handling large datasets, refer to the pagination section.

🧾 Flat Response Format – Structured output designed for easy integration and visualization, compatible with spreadsheets, BI tools, and time series databases.

Filter by ancestors

The ancestor_polygons parameter is a new filter introduced in the v6 API. It allows you to target events based on the parent (or “ancestor”) of the polygons that contain the event, something that wasn’t possible with the existing parameters in v5.

What it does exactly

• Filters events whose polygon lies inside a parent polygon (e.g., a port, zone).
• Considers the parent polygon’s type via the polygon_types option. In other words, you must first specify the type of polygon you’re looking for (port, berth, etc.) and then provide the corresponding parent identifiers.

Accepted value formats

You can provide these values in two ways:

1. Comma‑separated list ancestor_polygons=NL,NLRTM
2. Repeated parameter ancestor_polygons=NL&ancestor_polygons=NLRTM

Example request

https://apihub.axsmarine.com/liner/ais/event/polygon/v6?polygon_types=zone&ancestor_polygons=NLRTM&page_size=50

In this example, the call will return events located in zone polygons that are contained within the parent polygons identified by the LOCODE NLRTM.

Why it’s useful

• Hierarchical geographic search – you can filter events not only by the polygon of interest but also by the larger geographic area that surrounds it.
• Noise reduction – by combining polygon_types and ancestor_polygons, you limit results to relevant child polygons of a given geographic structure.

In summary, ancestor_polygons adds a layer of hierarchical filtering to requests, improving the accuracy and relevance of results obtained via the v6 API.