Reference · built on requestCommons signalAviation & marine

AISHub

Aggregated AIS vessel positions from AISHub's contributor network, as XML, JSON, or CSV for members who feed a receiver.

About

AISHub is a data exchange for Automatic Identification System receivers. Contributors stream raw NMEA from their own station to a UDP port AISHub assigns, and in return get an account and, when the feed meets AISHub's quality requirements, a personal API key to the aggregated feed. The web service returns each vessel's latest position and static data as XML, JSON, or CSV, filtered by bounding box, MMSI, IMO, or maximum age.

Through Fibric, an operator polls the box around your berths or anchorage once a minute and proposes arrival notices or dock changes for your approval, with the MMSI and timestamp attached.

This is a reference listing. It documents what Fibric would read from AISHub and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Vessel positions from data.aishub.net/ws.php: MMSI, TIME, LATITUDE, LONGITUDE, COG, SOG, HEADING, ROT, and NAVSTAT
  • Static and voyage data in the same record: IMO, NAME, CALLSIGN, TYPE, dimensions A, B, C, D, DRAUGHT, DEST, and ETA
  • Area filters latmin, latmax, lonmin, and lonmax, and vessel filters mmsi and imo, each accepting a list of numbers
  • An interval parameter that caps the age of returned positions in minutes
  • AIS encoding (format=0) or human-readable units (format=1), with not-available sentinels such as COG 3600 and HEADING 511
  • Your own stations' records from data.aishub.net/stations.php

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Notify a terminal before a ship arrives

    The operator watches the bounding box around your approach, reads DEST and ETA from each vessel's static data, and proposes an arrival notice and berth slot for the dock team to accept or change.

    With ETA Notice, Dock Schedule

  • Chase a shipment whose vessel has stopped

    When SOG stays at zero outside a port for longer than the window you set, the operator links the vessel to the inbound orders it carries and proposes a delay notice, with positions on the record.

    With Stalled Shipment, Inbound Delay

  • Keep your own receiver in good standing

    The operator reads stations.php for your station, compares message age against AISHub's delay requirement, and proposes a maintenance ticket when the feed drifts or drops, so your API access holds.

    With Integration Health

Requirements

  • An operational AIS station streaming at least one raw NMEA feed to the UDP port AISHub assigns; applications without one are not approved
  • A feed that meets AISHub's quality requirements for vessel coverage, uptime, downsampling rate, and message delay, averaged over the last 7 days
  • A poll cadence no faster than once per minute
  • Agreement to the AISHub Terms of Use, including public display of your station's location and coordinates
Authentication
Your AISHub username on the query string of every call. AISHub issues it after you join, and grants API access to contributors whose feed meets its quality requirements.

Limits

  • One request per minute; AISHub states the web service returns nothing if called more often
  • Synthesized NMEA, scraped data, and re-fed public AIS sources are prohibited as contributions
  • AISHub takes no responsibility for losses caused by technical failures or low-quality feeds
  • Coverage follows where contributors' receivers are; there is no guaranteed area

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request AISHub ↗

Questions and answers

Do I need to run an AIS receiver to use AISHub?
Yes. AISHub is a contributor-based network. Every contributor provides at least one raw AIS feed in NMEA format, and applications without an operational station and feed are not approved. All contributors may use the aggregated data for free.
How often can I call the API?
Not more than once per minute. AISHub states the web service returns nothing if executed more frequently. Use the interval parameter and the bounding-box or MMSI filters to keep each response to the vessels you need.
What units come back?
Two forms. format=0 keeps AIS encoding: coordinates in 1/10000 minute, COG in tenths of a degree, SOG in tenths of a knot, DRAUGHT in tenths of a metre, and TIME as a Unix timestamp. format=1 returns degrees, knots, metres, and UTC date and time.
Ask about AISHub

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.