(Created page with "Category:Shipping =General Information= {{Infobox | title = {{PAGENAME}} | image = 200px | headerstyle = background:#595958; color:#f9f9f9; | header1 = Layer Info | label2 = Category | data2 = Activities | label3 = Sub-category | data3 = Shipping | label4 = Editable | Yes | }} ==Description== Routes designated and recognised by the International Maritime Organization ==MSP Challenge== This puts no pressure on t...")
 
No edit summary
 
(12 intermediate revisions by 3 users not shown)
Line 14: Line 14:
==Description==
==Description==


Routes designated and recognised by the International Maritime Organization
Shipping routes designated and recognised by the [https://www.imo.org/en/ International Maritime Organization].


==MSP Challenge==
==MSP Challenge==


This puts no pressure on the ecosystem.
IMO routes do not contribute to pressures on the ecosystem, but will influence the shipping intensity calculated by the shipping simulation. The total shipping intensity calculated contributes to [[surface disturbance]] and [[noise]] pressures.
 
Return to [[Categories and Layers#tab=Shipping|shipping]].


=North Sea=
=North Sea=
The North Sea is very busy in terms of shipping, especially in the area of the Strait of Dover, to avoid incidents, IMO shipping routes are defined in the region.
 
==Types==
==Types==
* Ferry
* Ferry
* Passenger
* [[Passenger]]
* Tanker
* Tanker
* Cargo
* Cargo
Line 32: Line 34:
==Metadata==
==Metadata==
===Data Source===
===Data Source===
Enter data source for North Sea here.
NorthSEE partner World Maritime University.


===Original Title===
===Original Title===
Enter name of the layer at the North Sea source.
Not available.


===Description===
===Description===
Enter the description of the North Sea dataset here.
Not available.


===Creation Date===
===Creation Date===
yyyy-mm-dd North Sea
Not available. Data integrated on 2018/05.


===Methodology===
===Methodology===
Enter here how the layer was prepared to be integrated into the MSP Challenge North Sea Edition.
Data layer implemented as provided by project partners, assuming the routes are applicable to all types of vessels considered.
 
== North Sea Digitwin Edition ==
In the North Sea Digitwin edition the data is from [https://www.nationaalgeoregister.nl/geonetwork/srv/dut/catalog.search#/metadata/5996e444-f7f3-40d2-b485-8b9af6e8aa89 Rijkswaterstaat] and was retrieved on 2019-10.


=Baltic Sea=
=Baltic Sea=
"There are about 2000 ships in the Baltic marine area at any given moment and about 3500–5500 ships navigate through the Baltic Sea per month (Stankiewicz et al. 2010, Madjidian et al. 2013). More than 50% of the ships are general cargo ships. Approximately 20% of the ships in the Baltic Sea are tankers carrying over 200 million tons of oil, about 11% are passenger ships operating about 50 million passengers (Stankiewicz et al. 2010, Meski and Kaitaranta 2014, Parsmo et al. 2016)." ''In'' Baltic LINes (2016): Shipping in the Baltic Sea – Past, present and future developments relevant for Maritime Spatial Planning. Project Report I. 35 p.


==Types==
==Types==
Baltic Sea types here
* Cargo
* Passenger
* Maintenance
* Tanker
* Automated Vessels


==Metadata==
==Metadata==
===Data Source===
===Data Source===
Enter data source for Baltic Sea here.
 
'''[https://maps.helcom.fi/website/mapservice/ HELCOM]'''


===Original Title===
===Original Title===
Enter name of the layer at the Baltic Sea source.
 
IMO ships routeing guide


===Description===
===Description===
Enter the description of the Baltic Sea dataset here.


===Creation Date===
"This dataset includes digitized deep-water route, traffic separation schemes, precautionary areas and inshore traffic zones in the Baltic Sea as defined in the 9th edition of the Ships Routing Guide (2008) of the International Maritime Organization.
yyyy-mm-dd Baltic Sea
 
It was updated in 2017.
 
The update includes information about new traffic separation schemes and deep-water routes, amendments to the existing traffic separation schemes and establishment of new two-way routes which are not included in the original 2008 routeing guide, but were adopted by the 54th, 55th, 57th, and 58th session of the Sub-Committee on the Safety of Navigation of the IMO, and 3rd session of IMO's Sub-Committee Meeting on the Navigation, Communications, Search and Rescue."


===Methodology===
Description retrieved from HELCOM's metadata page for this resource (2021-07-15).
Enter here how the layer was prepared to be integrated into the MSP Challenge Baltic Sea Edition.


=Clyde Marine Region=
===Creation Date===


==Types==
Not available. Revision date: 2017-01-01
Clyde Marine Region types here


==Metadata==
===Methodology===
===Data Source===
Enter data source for Clyde Marine Region here.


===Original Title===
The routeing guide's features where classified in their different zone types; only the features corresponding to "deep-water route", "recommend route", and "traffic lane' where considered as IMO shipping lanes. For those zone types the middle lines were taken into account and implemented in the platform with their average width.  
Enter name of the layer at the Clyde Marine Region source.


===Description===
== Western Baltic Sea ==
Enter the description of the Clyde Marine Region dataset here.
The IMO Routes layer in the Western Baltic Sea Edition remains consistent with  that featured in the Baltic Sea edition.


===Creation Date===
=Clyde Marine Region=
yyyy-mm-dd Clyde Marine Region  
Not applicable.


===Methodology===
This layer is not available in the Clyde Marine Region Edition.
Enter here how the layer was prepared to be integrated into the MSP Challenge Clyde Marine Region Edition.


=Adriatic Sea=
=Adriatic Sea=
For the shipping routes, the following types of vessels are considered:


==Types==
==Types==
Adriatic Sea types here
* Passenger
* Tanker
* Cargo
* Others


==Metadata==
==Metadata==
===Data Source===
===Data Source===
Enter data source for Adriatic Sea here.
Provided by the project partner [http://www.ismar.cnr.it/ CNR-ISMAR] based on data from [https://www.portodimare.eu/layers_ext/geonode:imo_traffic_regulation_z_ncfos portodimare].


===Original Title===
===Original Title===
Enter name of the layer at the Adriatic Sea source.


IMO - Traffic regulation zones: traffic lane
===Description===
===Description===
Enter the description of the Adriatic Sea dataset here.
"Ships' routeing systems and traffic separation schemes that have been approved by International Maritime Organization (IMO). The traffic-lanes (or clearways) indicate the general direction of the ships in that zone; ships navigating within a Traffic Separation Scheme or TSS all sail in the same direction or they cross the lane in an angle as close to 90 degrees as possible." Retrieved from [https://www.portodimare.eu/layers_ext/geonode:imo_traffic_regulation_z_ncfos portodimare] on 2022-04-25.


===Creation Date===
===Creation Date===
yyyy-mm-dd Adriatic Sea
2012/03/30


===Methodology===
===Methodology===
Enter here how the layer was prepared to be integrated into the MSP Challenge Adriatic Sea Edition.


<headertabs/>
The layer was implemented in the MSP Challenge as provided by the project partner (CNR-ISMAR), assuming that the routes apply to all vessel types.
 
 
=Eastern Mediterranean Sea=
In the Eastern Mediterranean Sea Edition the IMO Routes layer is an empty plannable layer. There is currently limited data available considering the Shipping Lanes and Traffic Separations Schemes in the Mediterranean.
 
==Types==
* Ferry
* Passenger
* Tanker
* Cargo
* Maintenance
 
==Metadata==
Not Applicable. <headertabs/>

Latest revision as of 12:28, 6 November 2024

IMO Routes
Layer IMO Routes.png
Layer Info
Category Activities
Sub-category Shipping

Description

Shipping routes designated and recognised by the International Maritime Organization.

MSP Challenge

IMO routes do not contribute to pressures on the ecosystem, but will influence the shipping intensity calculated by the shipping simulation. The total shipping intensity calculated contributes to surface disturbance and noise pressures.

Return to shipping.

The North Sea is very busy in terms of shipping, especially in the area of the Strait of Dover, to avoid incidents, IMO shipping routes are defined in the region.

Types

Metadata

Data Source

NorthSEE partner World Maritime University.

Original Title

Not available.

Description

Not available.

Creation Date

Not available. Data integrated on 2018/05.

Methodology

Data layer implemented as provided by project partners, assuming the routes are applicable to all types of vessels considered.

North Sea Digitwin Edition

In the North Sea Digitwin edition the data is from Rijkswaterstaat and was retrieved on 2019-10.

"There are about 2000 ships in the Baltic marine area at any given moment and about 3500–5500 ships navigate through the Baltic Sea per month (Stankiewicz et al. 2010, Madjidian et al. 2013). More than 50% of the ships are general cargo ships. Approximately 20% of the ships in the Baltic Sea are tankers carrying over 200 million tons of oil, about 11% are passenger ships operating about 50 million passengers (Stankiewicz et al. 2010, Meski and Kaitaranta 2014, Parsmo et al. 2016)." In Baltic LINes (2016): Shipping in the Baltic Sea – Past, present and future developments relevant for Maritime Spatial Planning. Project Report I. 35 p.

Types

  • Cargo
  • Passenger
  • Maintenance
  • Tanker
  • Automated Vessels

Metadata

Data Source

HELCOM

Original Title

IMO ships routeing guide

Description

"This dataset includes digitized deep-water route, traffic separation schemes, precautionary areas and inshore traffic zones in the Baltic Sea as defined in the 9th edition of the Ships Routing Guide (2008) of the International Maritime Organization.

It was updated in 2017.

The update includes information about new traffic separation schemes and deep-water routes, amendments to the existing traffic separation schemes and establishment of new two-way routes which are not included in the original 2008 routeing guide, but were adopted by the 54th, 55th, 57th, and 58th session of the Sub-Committee on the Safety of Navigation of the IMO, and 3rd session of IMO's Sub-Committee Meeting on the Navigation, Communications, Search and Rescue."

Description retrieved from HELCOM's metadata page for this resource (2021-07-15).

Creation Date

Not available. Revision date: 2017-01-01

Methodology

The routeing guide's features where classified in their different zone types; only the features corresponding to "deep-water route", "recommend route", and "traffic lane' where considered as IMO shipping lanes. For those zone types the middle lines were taken into account and implemented in the platform with their average width.

Western Baltic Sea

The IMO Routes layer in the Western Baltic Sea Edition remains consistent with that featured in the Baltic Sea edition.

Not applicable.

This layer is not available in the Clyde Marine Region Edition.

For the shipping routes, the following types of vessels are considered:

Types

  • Passenger
  • Tanker
  • Cargo
  • Others

Metadata

Data Source

Provided by the project partner CNR-ISMAR based on data from portodimare.

Original Title

IMO - Traffic regulation zones: traffic lane

Description

"Ships' routeing systems and traffic separation schemes that have been approved by International Maritime Organization (IMO). The traffic-lanes (or clearways) indicate the general direction of the ships in that zone; ships navigating within a Traffic Separation Scheme or TSS all sail in the same direction or they cross the lane in an angle as close to 90 degrees as possible." Retrieved from portodimare on 2022-04-25.

Creation Date

2012/03/30

Methodology

The layer was implemented in the MSP Challenge as provided by the project partner (CNR-ISMAR), assuming that the routes apply to all vessel types.


In the Eastern Mediterranean Sea Edition the IMO Routes layer is an empty plannable layer. There is currently limited data available considering the Shipping Lanes and Traffic Separations Schemes in the Mediterranean.

Types

  • Ferry
  • Passenger
  • Tanker
  • Cargo
  • Maintenance

Metadata

Not Applicable.

This page was last edited on 6 November 2024, at 12:28. Content is available under GPLv3 unless otherwise noted.