No edit summary
No edit summary
 
(7 intermediate revisions by 3 users not shown)
Line 14: Line 14:
==Description==
==Description==


Zones were shipping activity should be avoided
No Shipping Zones portrait what IMO defines as "areas to be avoided". Areas to be avoided are defined by [https://www.imo.org/en/OurWork/Safety/Pages/ShipsRouteing.aspx IMO] (2019) as "area to be avoided: an area within defined limits in which either navigation is particularly hazardous or it is exceptionally important to avoid casualties and which should be avoided by all ships, or by certain classes of ships".
 
Source:
 
IMO, 2019. International Marine Organization. https://www.imo.org/en/OurWork/Safety/Pages/ShipsRouteing.aspx, accessed on 2022/04/26.


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


This puts no pressure on the ecosystem.
The shipping simulation in MSP Challenge takes the No Shipping Zones in consideration when calculating the Shipping Intensity.
 
This layer does not contribute to pressures on the ecosystem.
 


Return to [[Categories and Layers#tab=Shipping|shipping]].
=North Sea=
=North Sea=
   
   
Line 32: Line 39:
==Metadata==
==Metadata==
===Data Source===
===Data Source===
Enter data source for North Sea here.
Shapefiles provided by 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
2018/05


===Methodology===
===Methodology===
Enter here how the layer was prepared to be integrated into the MSP Challenge North Sea Edition.
Implemented as provided.


=Baltic Sea=
=Baltic Sea=
Line 57: Line 64:
==Metadata==
==Metadata==
===Data Source===
===Data Source===
Enter data source for Baltic Sea here.
[https://vasab.org/project/balticlines/ Baltic LINes] partners from draft plans of partners


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


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


===Creation Date===
===Creation Date===
yyyy-mm-dd Baltic Sea
Not available. Implemented on 2018/12.


===Methodology===
===Methodology===


'''Coming soon'''
Implemented as provided by partners.
 
== Western Baltic Sea ==
The No Shipping Zones layer in the Western Baltic Sea Edition remains consistent with  that featured in the Baltic Sea edition.


=Clyde Marine Region=
=Clyde Marine Region=
Line 82: Line 92:
==Metadata==
==Metadata==
===Data Source===
===Data Source===
Enter data source for Clyde Marine Region here.
Mock-up data just for the shipping simulation to be able to run.


===Original Title===
===Original Title===


Enter name of the layer at the source.
Not applicable.
 


===Description===
===Description===
Enter the description of the Clyde Marine Region dataset here.
Not applicable.


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


===Methodology===
===Methodology===


Enter here how the layer was prepared to be integrated into the MSP Challenge.
Not applicable.
 


=Adriatic Sea=
=Adriatic Sea=


==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_jaljb#/ Portodimare].


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


Areas to be avoided.
===Description===
===Description===
Enter the description of the Adriatic Sea dataset here.
Abstract provided at data source ([https://www.portodimare.eu/layers_ext/geonode:imo_traffic_regulation_z_jaljb#/ portodimare], accessed on 2022/04/26):
 
"Ships routeing systems and traffic separation schemes that have been approved by International Maritime Organization (IMO).
 
An Area to be Avoided (ATBA) is an area within defined limits that should be avoided by all ships or certain classes of ships, in which navigation is Particularly hazardous or in which it is exceptionally important to avoid casualties.
 
In general, ATBAs should be established only in places where:
 
inadequate survey or insufficient provision of aids to navigation may lead to danger of stranding; where local knowledge is considered essential for safe passage; where there is the possibility that unacceptable damage to the environment could result from a casualty; or where there might be hazard to a vital aid to navigation."


===Creation Date===
===Creation Date===
yyyy-mm-dd Adriatic Sea
2019/12/03


===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 ([http://www.ismar.cnr.it/ CNR-ISMAR]), for all vessel types.
 
 
=Eastern Mediterranean Sea=
 
== Types ==
 
* Passenger
* Tanker
* Cargo
 
== Metadata ==
Not applicable. This layer only exists in the Eastern Mediterranean Sea edition for planning purposes (the layer is empty). <headertabs/>

Latest revision as of 12:35, 12 November 2024

No shipping zones
Layer No shipping zones.png
Layer Info
Category Activities
Sub-category Shipping

Description

No Shipping Zones portrait what IMO defines as "areas to be avoided". Areas to be avoided are defined by IMO (2019) as "area to be avoided: an area within defined limits in which either navigation is particularly hazardous or it is exceptionally important to avoid casualties and which should be avoided by all ships, or by certain classes of ships".

Source:

IMO, 2019. International Marine Organization. https://www.imo.org/en/OurWork/Safety/Pages/ShipsRouteing.aspx, accessed on 2022/04/26.

MSP Challenge

The shipping simulation in MSP Challenge takes the No Shipping Zones in consideration when calculating the Shipping Intensity.

This layer does not contribute to pressures on the ecosystem.


Return to shipping.

Types

  • Ferry
  • Passenger
  • Tanker
  • Cargo
  • Maintenance

Metadata

Data Source

Shapefiles provided by NorthSEE partner World Maritime University.

Original Title

Not available.

Description

Not available.

Creation Date

2018/05

Methodology

Implemented as provided.

Types

  • Cargo
  • Passenger
  • Maintenance
  • Tanker
  • Automated Vessels

Metadata

Data Source

Baltic LINes partners from draft plans of partners

Original Title

Not available.

Description

Not available.

Creation Date

Not available. Implemented on 2018/12.

Methodology

Implemented as provided by partners.

Western Baltic Sea

The No Shipping Zones layer in the Western Baltic Sea Edition remains consistent with that featured in the Baltic Sea edition.

Types

  • Passenger
  • Tanker
  • Cargo
  • Recreational

Metadata

Data Source

Mock-up data just for the shipping simulation to be able to run.

Original Title

Not applicable.

Description

Not applicable.

Creation Date

Not applicable.

Methodology

Not applicable.

Types

  • Passenger
  • Tanker
  • Cargo
  • Others

Metadata

Data Source

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

Original Title

Areas to be avoided.

Description

Abstract provided at data source (portodimare, accessed on 2022/04/26):

"Ships routeing systems and traffic separation schemes that have been approved by International Maritime Organization (IMO).

An Area to be Avoided (ATBA) is an area within defined limits that should be avoided by all ships or certain classes of ships, in which navigation is Particularly hazardous or in which it is exceptionally important to avoid casualties.

In general, ATBAs should be established only in places where:

inadequate survey or insufficient provision of aids to navigation may lead to danger of stranding; where local knowledge is considered essential for safe passage; where there is the possibility that unacceptable damage to the environment could result from a casualty; or where there might be hazard to a vital aid to navigation."

Creation Date

2019/12/03

Methodology

The layer was implemented in the MSP Challenge as provided by the project partner (CNR-ISMAR), for all vessel types.


Types

  • Passenger
  • Tanker
  • Cargo

Metadata

Not applicable. This layer only exists in the Eastern Mediterranean Sea edition for planning purposes (the layer is empty).

Retrieved from "https://knowledge.mspchallenge.info/index.php?title=No_shipping_zones&oldid=6013"
This page was last edited on 12 November 2024, at 12:35. Content is available under GPLv3 unless otherwise noted.