Data for three PIXEL ports have been collected from the data-sharing portal AISHub: GPMB, ASPM and PPA. In the AIS notebook, work on analytics of AIS is presented: heatmaps of locations, most common navigation statuses in different areas in the ROIs, most common vessel types in different parts of the ports and neighbour areas, errors in AIS data, comparison of reported and fixed navigational statuses, voyages from entering the ROI, anchoring, mooring and leaving the region.
IMO adopted a new requirement for all ships to carry automatic identification systems (AISs) capable of providing information about the ship to other ships and to coastal authorities automatically.
The regulation requires AIS to be fitted aboard all ships of 300 gross tonnage and upwards engaged on international voyages, cargo ships of 500 gross tonnage and upwards not engaged on international voyages and all passenger ships irrespective of size. The requirement became effective for all ships by 31 December 2004.
AISHub is a FREE AIS data sharing service which provides access to real time ship positions for vessel tracking systems.
- Bordeaux - missing AIS data - antenna with bad range (on AIS HUB)
- Thessaloniki - NO AIS data (on AIS HUB)
- Monfalcone - good AIS data
- Pireas - good AIS data
Vessels heatmap
Navigational status
The AIS receiver connected to AISHUB has low range and usually doesn't get AIS messages from Bassens terminal.
ETA predictions for vessels in Gironde estuary (3-5 hours before arrival - MAE is 20 min).
ETA error corelated with distance to Bassens
Bassens distance distribution (small number of messages from vessels close to Bassens - weak AIS reciever)
It takes almost 2 days from south part of Adriatic sea to north part.
- Some vessel calls data
- Good live AIS data
Problems with AIS navigational status
Based on:
- location
- speed
- AIS speed can be inaccurate, so we have to calculate speed based on travelled distance and time passed between two AIS emssages
- "smoothen" navigational status with rolling mode (select most common navigational status from current, previous and next navigational status)
With accurate navigational status we can:
- Detect arrivals and departures from AIS data.
- Caluclate statistics of waitting (anchored) time, moored time...
- Trends and extreme outliers in waiting time, cargo processing time...
- Congestion index
- Group AIS messages in voyages
Ferry voyages in 3 months
With grouped messages in voyages, we can calculate, how much time vessel was in specific navigational status (moored, anchored, under way using engine ...). We can detect outliers and calculate trends.
MMSI | VOYAGE START | NAVSTAT | NAVSTAT START TIME | TIME IN NAVSTATE |
---|---|---|---|---|
210001000 | 2019-07-06 02:47:14 | 0 | 1561899967 | 0.250000 |
210001000 | 2019-07-06 02:47:14 | 1 | 1562382434 | 14.206944 |
210001000 | 2019-07-06 02:47:14 | 0 | 1562434335 | 2.333333 |
210001000 | 2019-07-06 02:47:14 | 5 | 1562443334 | 17.258333 |
210001000 | 2019-07-06 02:47:14 | 0 | 1562506327 | 0.415278 |
210001000 | 2019-07-13 05:26:17 | 0 | 1562506327 | 0.258333 |
210001000 | 2019-07-13 05:26:17 | 1 | 1562996808 | 31.207222 |
210001000 | 2019-07-13 05:26:17 | 0 | 1563109614 | 2.100278 |
210001000 | 2019-07-13 05:26:17 | 5 | 1563117775 | 27.563056 |
210001000 | 2019-07-13 05:26:17 | 0 | 1563217621 | 0.419444 |
210001000 | 2019-07-19 16:18:38 | 0 | 1563217621 | 0.666944 |
210001000 | 2019-07-19 16:18:38 | 1 | 1563555818 | 39.868889 |
210001000 | 2019-07-19 16:18:38 | 0 | 1563699997 | 2.352500 |
210001000 | 2019-07-19 16:18:38 | 5 | 1563709068 | 7.853889 |
210001000 | 2019-07-19 16:18:38 | 0 | 1563737996 | 0.582500 |
210001000 | 2019-07-27 04:40:59 | 0 | 1563737996 | 0.833333 |
210001000 | 2019-07-27 04:40:59 | 1 | 1564205759 | 4.929722 |
210001000 | 2019-07-27 04:40:59 | 0 | 1564224166 | 1.255278 |
210001000 | 2019-07-27 04:40:59 | 5 | 1564229303 | 23.021111 |
210001000 | 2019-07-27 04:40:59 | 0 | 1564312830 | 0.758611 |