AIS_Route_Density_2020 (MapServer)

View In: ArcGIS JavaScript ArcGIS Online Map Viewer ArcGIS Earth ArcGIS Pro

Service Description: <DIV STYLE="text-align:Left;"><DIV>The Route Density Maps are produced and provided to EMODnet by the European Maritime Safety Agency (EMSA).The method selected by EMSA and agreed by the Member States is the ship routes restoring method. This method rebuilds the track of each distinct ship from the recorded positions and counts how many routes are crossing each cell of a grid during a given period of time. This method can be implemented in all regions (coastal and open sea), using all the available ships position data and allows connecting ship routes even within areas with a low coverage. The grids used as reference to build the route density maps are constructed to cover all the target areas and have a definition of 1x1 km. The grids are based on the EMODnet constructed grids. In order to build a density map, the first step is to collect ship positions data from EMSA’s ship position database. Terrestrial AIS (T-AIS) and satellite AIS (S-AIS) data are collected by using an SQL query (filtering). Each ship position is collected with the indication of the ship’s type. The position data is collected and aggregated per period of time and target area (e.g. North Sea-Atlantic, Atlantic, Baltic Sea, Mediterranean Sea, Black Sea and All Europe). Positions are checked to remove improbable situations, e.g. erroneous positions or duplicated positions. Position data with a high frequency acquisition (e.g. T-AIS data) is down-sampled (e.g. one position per 6 minutes). S-AIS data normally is not down-sampled. The down sampling rate is configurable. The routes are recreated by connecting the position reports into polylines using the acquisition time stamp to order the points in a chronological order (per MMSI and a period). The polylines are then tagged per AIS ship types ranges: Passenger (includes AIS ship type codes 60 to 69); Cargo (includes AIS ship type codes 70 to 79); Tanker (includes AIS ship type codes 80 to 89); Fishing (includes AIS ship type code 30); All Other (includes all other ship types), and All Traffic (includes all ships monitored). The polyline segments which are obviously improbable are removed, such as: segments joining two consecutive positions of the same vessel (MMSI) too distant in time from each other; too long segments joining two consecutive positions of the same vessel (e.g. more than 100 NM); too short segments joining two consecutive positions of the same vessel (e.g. less than 10m.); segments overlapping land area (either by checking if the polyline goes beyond existing grid cells or it crosses a land polygon), etc. The filtering settings are configurable. The traffic density map is created by counting the number of routes (polylines) crossing each grid cell and applying a colour code corresponding to the number of crossings. The system counts the number of polylines crossing boundary of each cell. The output of this process is a grid data file containing the number of vessel route crossings per cell. The data files are created for all combinations of the predefined criteria (i.e. area, ship type range and time period). The traffic density (the number of polylines crossing each cell) is presented by using a colour code per the range of values. A corresponding colour code is given to each cell. The output of this process is a georeferenced image file showing a density map with a predefined code by cell. The files are created for all combinations of the predefined criteria (i.e. area, ship type range and time period). The final route density maps are produced by aggregating (stacking and summing) the intermediate files generated according to the configured time criteria (i.e. monthly, seasonal and annual maps) and ship type ranges (i.e. Cargo, Fishing, Passenger, Tanker, All Other and All traffic) and finally clipping according to the preconfigured geographic area (e.g. All Europe). </DIV></DIV>

Map Name: EMSA AIS Route Density Map 2020 all vessels

Legend

All Layers and Tables

Dynamic Legend

Dynamic All Layers

Layers:

AIS all vessel route density 2020 (0)

Description: <DIV STYLE="text-align:Left;"><DIV>The Route Density Maps are produced and provided to EMODnet by the European Maritime Safety Agency (EMSA).The method selected by EMSA and agreed by the Member States is the ship routes restoring method. This method rebuilds the track of each distinct ship from the recorded positions and counts how many routes are crossing each cell of a grid during a given period of time. This method can be implemented in all regions (coastal and open sea), using all the available ships position data and allows connecting ship routes even within areas with a low coverage. The grids used as reference to build the route density maps are constructed to cover all the target areas and have a definition of 1x1 km. The grids are based on the EMODnet constructed grids. In order to build a density map, the first step is to collect ship positions data from EMSA’s ship position database. Terrestrial AIS (T-AIS) and satellite AIS (S-AIS) data are collected by using an SQL query (filtering). Each ship position is collected with the indication of the ship’s type. The position data is collected and aggregated per period of time and target area (e.g. North Sea-Atlantic, Atlantic, Baltic Sea, Mediterranean Sea, Black Sea and All Europe). Positions are checked to remove improbable situations, e.g. erroneous positions or duplicated positions. Position data with a high frequency acquisition (e.g. T-AIS data) is down-sampled (e.g. one position per 6 minutes). S-AIS data normally is not down-sampled. The down sampling rate is configurable. The routes are recreated by connecting the position reports into polylines using the acquisition time stamp to order the points in a chronological order (per MMSI and a period). The polylines are then tagged per AIS ship types ranges: Passenger (includes AIS ship type codes 60 to 69); Cargo (includes AIS ship type codes 70 to 79); Tanker (includes AIS ship type codes 80 to 89); Fishing (includes AIS ship type code 30); All Other (includes all other ship types), and All Traffic (includes all ships monitored). The polyline segments which are obviously improbable are removed, such as: segments joining two consecutive positions of the same vessel (MMSI) too distant in time from each other; too long segments joining two consecutive positions of the same vessel (e.g. more than 100 NM); too short segments joining two consecutive positions of the same vessel (e.g. less than 10m.); segments overlapping land area (either by checking if the polyline goes beyond existing grid cells or it crosses a land polygon), etc. The filtering settings are configurable. The traffic density map is created by counting the number of routes (polylines) crossing each grid cell and applying a colour code corresponding to the number of crossings. The system counts the number of polylines crossing boundary of each cell. The output of this process is a grid data file containing the number of vessel route crossings per cell. The data files are created for all combinations of the predefined criteria (i.e. area, ship type range and time period). The traffic density (the number of polylines crossing each cell) is presented by using a colour code per the range of values. A corresponding colour code is given to each cell. The output of this process is a georeferenced image file showing a density map with a predefined code by cell. The files are created for all combinations of the predefined criteria (i.e. area, ship type range and time period). The final route density maps are produced by aggregating (stacking and summing) the intermediate files generated according to the configured time criteria (i.e. monthly, seasonal and annual maps) and ship type ranges (i.e. Cargo, Fishing, Passenger, Tanker, All Other and All traffic) and finally clipping according to the preconfigured geographic area (e.g. All Europe). </DIV></DIV>

Service Item Id: 63acc425ed734fa5a8c5ef70a1570348

Copyright Text: EMSA

Spatial Reference: 25833 (25833) LatestVCSWkid(0)

Single Fused Map Cache: false

Initial Extent:

Full Extent:

Units: esriMeters

Supported Image Format Types: PNG32,PNG24,PNG,JPG,DIB,TIFF,EMF,PS,PDF,GIF,SVG,SVGZ,BMP

Document Info:

Supports Dynamic Layers: true

MaxRecordCount: 2000

MaxImageHeight: 4096

MaxImageWidth: 4096

Supported Query Formats: JSON, geoJSON, PBF

Supports Query Data Elements: true

Min Scale: 0

Max Scale: 0

Supports Datum Transformation: true

Child Resources: Info Dynamic Layer

Supported Operations: Export Map Identify QueryLegends QueryDomains Find Return Updates