BCMCA_HU_Shippingtrans_VesselDensity_2007_Marxan_data

Metadata also available as

Metadata:

Identification_Information:
Citation:
Citation_Information:
Originator:
The British Columbia Marine Conservation Analysis (BCMCA), a Tides Canada Initiatives Project
Publication_Date: May 2010
Title: BCMCA_HU_Shippingtrans_VesselDensity_2007_Marxan_data
Geospatial_Data_Presentation_Form: vector digital data
Series_Information:
Series_Name: Human Use Data, Marine Atlas of Pacific Canada
Publication_Information:
Publisher: British Columbia Marine Conservation Analysis
Online_Linkage:
\\data-server\gis\BCMCA\HumanUse\Repository\shipping\data\BCMCA_hu_ShippingTrans_VesselDensity_2007_marxan_data.shp
Larger_Work_Citation:
Citation_Information:
Originator:
The British Columbia Marine Conservation Analysis (BCMCA), a Tides Canada Initiatives Project
Publication_Date: May 2011
Title: Marine Atlas of Pacific Canada
Online_Linkage: www.bcmca.ca/atlas
Description:
Abstract:
This dataset illustrates the density of marine vessel traffic within each BCMCA Marxan Planning Unit (2km x 2km grid cell). There are 10 features included in this dataset. Traffic is broken down into the following categories: Carrier, Cruise, Fishing, Tanker and Tug by summer (May-September) and winter months (January-April and October-December) for 2007.
Purpose:
The source for this dataset was initially developed to support research on a model of the risk of encountering oil spills for seabirds considered vulnerable to oil pollution. Shipping densities were used as a proxy for the risk of oil spills.
For the BCMCA, the dataset's purpose is represent ten shipping and transportation features in a Marxan analysis. The features are summer and winter vessel density for Carrier, Cruise, Fishing, Tanker and Tug Vessels.
The British Columbia Marine Conservation Analysis (BCMCA) is a collaborative project assembling and analyzing spatial information about Canada's Pacific Ocean. The overall goal of the BCMCA is to identify marine areas of high conservation value and marine areas important to human use. Results of the project are intended to inform and help advance marine planning initiatives in BC by providing collaborative, peer-reviewed scientific analyses based on the best ecological and human use spatial data at scales relevant to a BC coast-wide analysis.
Supplemental_Information:
This dataset is based on ship monitoring data from the Canadian Coast Guard's Marine Communications and Traffic Services (MCTS) system. All ships operating in Canadian waters must obtain Vessel Traffic Services (VTS) clearance before beginning a voyage from a Canadian location or before entering Canadian waters. The Coast Guard monitors ship traffic using radio communication, radar detection and an Automatic Identification System. The Coast Guard documents ship position approximately every 4 minutes with ship-identification (Lloyd's Register name and number), flag-state (country of registry), ship-type and size.
See data quality for more supplemental information.
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 2007
Currentness_Reference: ground condition
Status:
Progress: Complete
Maintenance_and_Update_Frequency: None planned
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -139.382424
East_Bounding_Coordinate: -121.180445
North_Bounding_Coordinate: 56.051980
South_Bounding_Coordinate: 45.979698
Keywords:
Theme:
Theme_Keyword: vessel traffic
Theme_Keyword: vessel movement
Theme_Keyword: vessel density
Theme_Keyword: carrier
Theme_Keyword: cruise
Theme_Keyword: fishing
Theme_Keyword: tanker
Theme_Keyword: tug
Theme_Keyword: winter
Theme_Keyword: summer
Theme_Keyword: Marxan
Place:
Place_Keyword: British Columbia
Place_Keyword: BC
Place_Keyword: Pacific Ocean
Access_Constraints:
Not to be reproduced or distributed without permission from the data custodian
Use_Constraints:
Not to be reproduced or distributed without permission from the data custodian
Point_of_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Patrick O'Hara
Contact_Organization: Canadian Wildlife Service, Environment Canada
Contact_Position: Research Biologist
Contact_Address:
Address_Type: mailing and physical address
Address: 9860 West Saanich Road, P.O. Box 6000
City: Sidney
State_or_Province: British Columbia
Postal_Code: V8L 4B2
Country: Canada
Contact_Voice_Telephone: 250 363-6545
Contact_Electronic_Mail_Address: paddio@uvic.ca
Contact_Instructions:
Patrick is the point of contact for the source data. Contact info@BCMCA.ca for information regarding processing into Marxan Planning Units.
Data_Set_Credit:
Data courtesy of the Canadian Coast Guard, Marine Communications and Traffic Services. Dataset developed by Patrick O'Hara, Canadian Wildlife Service.
Native_Data_Set_Environment:
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.3.1.3500
Data_Quality_Information:
Logical_Consistency_Report:
NOTE: grid cells in the source data labelled 130_224, 131_223, 131_224, 132_224 (around Sointula) were updated to replace the values in the WINTER ferry field with those in the WINTER cruise ship field and vice versa. NOTE: Process steps 5-7 were done within a geodatabase so that the Shape_Area field updated automatically, if trying this method using shapefiles the Shape_Area field must be created and calculated manually.
Completeness_Report:
Included in this database are ships over 20m in length, and ships engaged in towing or pushing any vessel or object more than 20m in length (other than fishing gear) that had a combined length of more than 45 m. The database does not include vessels towing or pushing inside a log booming ground, pleasure yachts less than 30 m, or fishing vessels less than 24 m and 150 tons gross, which are not required to report their position to the VTS.
There is radar coverage of most of Georgia Strait and a radar station with 90 nautical mile range in the vicinity of Tofino. The radar coverage extends from Juan de Fuca in the south to an area just north of Kyuquot Sound on the west coast of Vancouver Island. All the other areas are tracked by vessels using the established call-in points indicated on the charts. This means that all of the northern area off Vancouver Island, both coasts of Haida Gwaii and the North Coast mainland is without radar coverage.
The information used to create this map does not include vessels transiting the portion of the Juan de Fuca Strait, which is the responsibility of the US Coast Guard.
The map provides minimum estimates of vessel traffic densities for the various traffic types included here and likely underestimates vessel traffic, particularly west of Haida Gwaii. Reasons for this include: 1) limited extents of Coast Guard radar coverage; 2) many of the vessels transiting the area west of Haida Gwaii are not bound for Canadian destinations and therefore not required to report to the Coast Guard; and 3) the Automatic Identification System is still in process of being brought in by VST.
There is no data available from west of the 136 degree longitude to the 200 mile territorial limit.
This dataset does not include data from 2003, which was also produced by the Canadian Coast Guard.
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Title: BCMCA_HU_Shippingtrans_VesselDensity_summer2007_data
Source_Contribution:
Canadian Coast Guard Marine Communications and Traffic Services vessel tracking database. <http://www.ccg-gcc.gc.ca/e0003910#VTS>
Source_Information:
Source_Citation:
Citation_Information:
Title: BCMCA_HU_Shippingtrans_VesselDensity_winter2007_data
Source_Contribution:
Canadian Coast Guard Marine Communications and Traffic Services vessel tracking database. <http://www.ccg-gcc.gc.ca/e0003910#VTS>
Process_Step:
Process_Description:
Vessel observations were reduced to one uniquely identifiable vessel observation per 5*5 km cell in a GIS grid per hour. For each 5*5km grid cell, data were summarised by calculating total number of uniquely identifiable ship observations per hour that either moved into or out of the focal cell (i.e., ensuring ships were moving). This ensured every vessel observation was tied to a vessel movement.
Process_Step:
Process_Description:
Vessel observations were assigned 5*5 km grid cell labels by spatially joining grid cells with each observation (ESRI: ArcGIS v9.x). Using data-step functions (for e.g., 'proc sort', 'first.obs', and 'lag[]') in the statistics program SAS, the data set was reduced to one uniquely identifiable vessel observation, per cell per hour, and lines were removed when vessel movement between cells was not indicated. 'Proc Tabulate" (SAS v9.x) was used to sum the number of observations per cell (i.e., a spatial grid of values), which we used as an index of relative vessel intensity throughout the British Columbian Exclusive Economic Zone.
Process_Step:
Process_Description:
5x5km cells located outside of Canadian waters were removed from the dataset.
Process_Date: May 3, 2010
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Lindsay McBlane
Contact_Organization: Parks Canada, Western and Northern Service Centre (for BCMCA)
Contact_Position: Resource Conservation Technician
Process_Step:
Process_Description:
****This step was necessitated because some cells from the original data were split to eliminate land but maintained the original value for number of vessels. This necessitated corrections so that the number of vessels of each category within individual polygon/record is proportional by area to the original grid cell amount, which then allows steps 6 and 7 to be taken. The following steps calculate the correct summer vessel traffic density for each polygon in the original data layer due to the separation of many grid cells into multiple parts following the erasing of land features****
- Make copy of original data, call summer_VTD - Determine Frequency (Toolbox>Analysis>Stats>Frequency) where the input is summer_VTD, the frequency field is Cell_Label and the summary field is Shape_Area (Output table is: Summer_VTD_Freq) - Add table to ArcMap and join to summer_VTD on common field Cell_Label, then export joined file as new feature called summer_VTD_freq_join - Add 6 new fields to summer_VTD_freq_join (FISH_X, CARR_X, FERR_X, TUG_X, OIL_X and CRUI_X) all doubles - Calculate all the new fields: FISH_X = FISH * Shape_Area / Shape_Area_1, CARR_X = CARR * Shape_Area / Shape_Area_1, etc... ^where "Shape_Area is the new area of the polygon and Shape_Area_1 is the original marine area of the grid cell prior to the land being erased (obtained from the frequency calculation table) - result is the correct proportional amount of the vessel traffic for each polygon
Process_Date: September 2010
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Chris McDougall
Contact_Organization: Contractor
Process_Step:
Process_Description:
****the following steps union the updated vessel traffic layer (summer_VTD_freq_join) with the BCMCA planning unit layer and calculate the correct vessel traffic density for each polygon in the unioned layer****
- Ensure projection is NAD 83, BC Environment Albers for all data - Union clean planning unit layer (PU) with updated traffic layer created above (summer_VTD_freq_join) and name resulting file summer_VTD_PU_Union - Select and delete records where Unit_ID = 0 (these are polygons outside the study area) - Determine Frequency (Toolbox>Analysis>Stats>Frequency) where the input is summer_VTD_PU_Union, the frequency file is FID_summer_VTD_freq_join and the summary field is Shape_Area (Output table is: Summer_VTD_PU_freq) - Add table to ArcMap and join to summer_VTD_PU_Union on common field FID_summer_VTD_freq_join, then export joined file as new feature called summer_VTD_PU_freq_join - Add 6 new fields to summer_VTD_freq_join (FISH_Z, CARR_Z, FERR_Z, TUG_Z, OIL_Z and CRUI_Z) all doubles - Calculate all the new fields: FISH_Z = FISH_X * Shape_Area / Shape_Area_12, CARR_Z = CARR_X * Shape_Area / Shape_Area_12, etc... ^where "Shape_Area is the new area of the polygon and Shape_Area_12 is the original area of the VTD polygons prior to the union with the PU layer (obtained from the frequency calculation table) - result is the correct proportional amount of the vessel traffic for each polygon
Process_Date: September 2010
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Chris McDougall
Contact_Organization: contractor
Process_Step:
Process_Description:
****the following steps calculate the total VTD for each vessel category within each PU and creates the marxan input for this feature****
- Export the .dbf for summer_VTD_PU_freq and call it summer_VTD_final - Open the summer_VTD_final.dbf in excel - Insert Pivot Table and select/drag Unit_ID to be the Row Label and FISH_Z, CARR_Z, FERR_Z, TUG_Z, OIL_Z and CRUI_Z as the SUM Values - Select all resulting values, copy and paste special (values) into a new excel book called Summary_summer_VTD_final - Code the heading to match the BCMCA codes [1201 to 1210 - see entity attribute for definitions] - delete FERR_Z column - save as comma delimited excel file
Process_Date: September 2010
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Chris McDougall
Contact_Organization: Contractor
Process_Step:
Process_Description: Repeat Steps 5-7 for Winter Density Data
Process_Date: September 2010
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Chris McDougall
Contact_Organization: Contractor
Process_Step:
Process_Description:
Summer and Winter were appended together to create the final Marxan input shapefile.
Process_Date: September 2010
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Chris McDougall
Contact_Organization: Contractor
Process_Step:
Process_Description:
31 Marxan planning units that overlapped the 4 shipping polygons where ferry density data incorrectly was included in the cruise ship field were manually adjusted to correctly account for the accurate cruise ship density (number of movements). Marxan planning units were assigned either 0 or 0.125 shipping movements. This adjustment was initially made directly to the Marxan input file abundance.dat and later added to the Marxan spatial data. The data in the original source files were separately updated in November 2010 as follows: grid cells labelled 130_224, 131_223, 131_224, 132_224 were updated to replace the WINTER values in the ferry field with those in the cruise ship field and vice versa.
Process_Date: December 14, 2010
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Dave Nicolson
Contact_Organization: BCMCA
Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: G-polygon
Point_and_Vector_Object_Count: 120499
Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Map_Projection:
Map_Projection_Name: Albers Conical Equal Area
Albers_Conical_Equal_Area:
Standard_Parallel: 50.000000
Standard_Parallel: 58.500000
Longitude_of_Central_Meridian: -126.000000
Latitude_of_Projection_Origin: 45.000000
False_Easting: 1000000.000000
False_Northing: 0.000000
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.000000
Ordinate_Resolution: 0.000000
Planar_Distance_Units: meters
Geodetic_Model:
Horizontal_Datum_Name: North American Datum of 1983
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222
Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: Vessel traffic density 2007 Marxan
Attribute:
Attribute_Label: FID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: Shape
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: UNIT_ID
Attribute_Definition: Planning unit ID - unique identifier
Attribute:
Attribute_Label: AREA
Attribute_Definition: size of Planning Unit (m2)
Attribute:
Attribute_Label: COST
Attribute_Definition: Planning Unit Cost (same as size for HU Data)
Attribute:
Attribute_Label: STATUS
Attribute_Definition:
indicates whether Planning Unit is available to be selected in the Marxan analysis, locked in or locked out.
Attribute:
Attribute_Label: 1201
Attribute_Definition: Summer Carrier Vessel Density for Planning Unit.
Attribute_Definition_Source: Bulk cargo and container vessels.
Attribute:
Attribute_Label: 1202
Attribute_Definition: Summer Cruise Vessel Density for Planning Unit.
Attribute_Definition_Source:
Vessels which transport passengers only on multi-day journeys to multiple ports.
Attribute:
Attribute_Label: 1203
Attribute_Definition: Summer Fishing Vessel Density for Planning Unit.
Attribute_Definition_Source: Vessels used to catch, process or transport fish.
Attribute:
Attribute_Label: 1204
Attribute_Definition: Summer Tanker Vessel Density for Planning Unit.
Attribute_Definition_Source:
Vessels which transport oil and liquid chemicals, including petroleum and natural gas.
Attribute:
Attribute_Label: 1205
Attribute_Definition: Summer Tug Vessel Density for Planning Unit.
Attribute_Definition_Source: Vessels which tow or propel barges.
Attribute:
Attribute_Label: 1206
Attribute_Definition: Winter Carrier Vessel Density for Planning Unit.
Attribute_Definition_Source: Bulk cargo and container vessels.
Attribute:
Attribute_Label: 1207
Attribute_Definition: Winter Cruise Vessel Density for Planning Unit.
Attribute_Definition_Source:
Vessels which transport passengers only on multi-day journeys to multiple ports.
Attribute:
Attribute_Label: 1208
Attribute_Definition: Winter Fishing Vessel Density for Planning Unit.
Attribute_Definition_Source: Vessels used to catch, process or transport fish.
Attribute:
Attribute_Label: 1209
Attribute_Definition: Winter Tanker Vessel Density for Planning Unit.
Attribute_Definition_Source:
Vessels which transport oil and liquid chemicals, including petroleum and natural gas.
Attribute:
Attribute_Label: 1210
Attribute_Definition: Winter Tug Vessel Density for Planning Unit.
Attribute_Definition_Source: Vessels which tow or propel barges.
Distribution_Information:
Distributor:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Ian Wade
Contact_Organization: Canadian Coast Guard
Resource_Description:
Data cannot be distributed without permission of custodian and distributor.
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Transfer_Size: 15.629
Metadata_Reference_Information:
Metadata_Date: 20120103
Metadata_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Dave Nicolson
Contact_Organization: British Columbia Marine Conservation Analysis
Contact_Position: Project Manager
Contact_Address:
Contact_Electronic_Mail_Address: info@bcmca.ca
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
Generated by mp version 2.9.6 on Tue Jan 03 15:59:51 2012