Identification

Title

Anonymised AIS Derived Track Lines 2013

Alternative title(s)

AIS_Tracks_2013_MMO

Anonymised_AIS_Derived_Track_Lines_2013.shp

Abstract

This dataset contains the anonymised transit line data used to create the UK shipping density grid.

Resource type

dataset

Resource locator

http://s3-eu-west-1.amazonaws.com/mmo-data/MMO_Data/datagovuk/Anonymised_AIS_Derived_Track_Lines_2013.zip

description: A link to the web service or dataset

Unique resource identifier

code

MMO1600154

codeSpace

Dataset language

eng

Spatial reference system

code identifying the spatial reference system

urn:ogc:def:crs:EPSG::0

Classification of spatial data and services

Topic category

transportation

Keywords

Keyword set

keyword value

Keyword set

keyword value

originating controlled vocabulary

title

reference date

date type

revision

effective date

2008-01-06

Keyword set

keyword value

originating controlled vocabulary

title

reference date

date type

revision

effective date

2009-11-16

Geographic location

West bounding longitude

-10.0000

East bounding longitude

9.9384

North bounding latitude

64.6625

South bounding latitude

47.0000

Temporal reference

Temporal extent

Begin position

2016-06-03

End position

2016-08-26

Dataset reference date

date type

publication

effective date

2016-06-03

date type

creation

effective date

2016-06-03

date type

revision

effective date

2016-08-23

Frequency of update

notPlanned

Quality and validity

Lineage

The MCA supplied type A and type B AIS data on behalf of the MMO. AIS-A is carried by international voyaging ships with gross tonnage (GT) of 300 or more tonnes, and all passenger ships regardless of size. The data contained message types 1, 2, 3 and 5. AIS-B is carried by smaller vessels and is aimed at the leisure and fishing sector. This data contained message types 18, 19 and 24. The AIS data was decoded and simplified to identify track lines which were then plotted using GIS. For full methodology including processing techniques and data outputs please see the MMO1066 report Mapping UK Shipping Density and Routes technical annex. An overview of the process can be found in Figure 3, pg 12. The Ship Type Group vessel codes are as follows: 0 - Unknown Vessels 1 - Non-Port service craft 2 - Port service craft 3 - Vessels engaged in dredging or underwater operations 4 - High Speed Craft 5 - Military or Law enforcement 6 - Passenger 7 - Cargo 8 - Tankers 9 - Fishing vessels 10 - Recreational vessels Weekly AIS Transit Line data for 2013 attribution as follows: Fields from Transit table data from Stage 2 of AIS Data Processing: ShipTypeGr - Ship Type Group, ShipLength - Ship Length, ShipWidth - Ship Width, Draughtx10 - Ship Draught x10, VoyageData - Voyage Data Source, TransLen - Transit Length, PosDen - PositionDensity, TransEndRe, - Transit End Reason, AISType - AIS Type Fields from VTC classification Stage 3 of AIS Data Processing SZone, SRegion, EZone, ERegion, VTC_Zone (VTC per Transit) Fields from Stage 4 of AIS Data Processing (following Lloyds List Validation) LloydsVess - Lloyds Vessel Type, VTC Group_Corr - Group Correction, CorrectedG - Corrected Group, Draught_Cor - Draught Correction, CorrectedD - Corrected Draught, Size Caveats: Lloyds List categorises “Roll On Roll Off” (RORO) vessel types as Cargo vessels. As part of the process to create AIS tracks, verification against Lloyds List has meant that some passenger ferry vessels classified as RORO, have been categorised as Cargo. The MMO corrected these attributes after identification of vessels and cross referencing of vessel types. For more information on Lloyds List types and categories, please see https://help.marinetraffic.com/hc/en-us/articles/205579997-What-is-the-significance-of-the-AIS-SHIPTYPE-number-

Conformity

Data format

name of format

version of format

Constraints related to access and use

Constraint set

Use constraints

Open Government Licence reproduced with permission of the Marine Management Organisation.

Constraint set

Limitations on public access

No limitations on access, however copyright should be used at all times.

Responsible organisations

Responsible party

contact position

Data/GIS Officer

organisation name

Marine Management Organisation

email address

dkm@marinemanagement.org.uk

responsible party role

originator

Responsible party

contact position

Data/GIS Officer

organisation name

Marine Management Organisation

email address

dkm@marinemanagement.org.uk

responsible party role

custodian

Metadata on metadata

Metadata point of contact

contact position

Data/GIS Officer

organisation name

Marine Management Organisation

email address

dkm@marinemanagement.org.uk

responsible party role

pointOfContact

Metadata date

2016-08-26

Metadata language