Short Citation:
Office of National Marine Sanctuaries, 2021: Olympic Coast National Marine Sanctuary Boundary (polygon), https://www.fisheries.noaa.gov/inport/item/40109.

Item Identification

Title: Olympic Coast National Marine Sanctuary Boundary (polygon)
Short Name: ocnms_py
Status: Completed
Publication Date: 2004-12
Abstract:

The Office of National Marine Sanctuaries manages a system of sanctuaries and other managed areas around the country. The legal boundaries of These sanctuaries are defined within the Code of Federal Regulations, at 15 C.F.R. Part 922 and thesubparts for each national marine sanctuary. The GIS compatible digital boundary files for each national marine sanctuary are representations of those legal boundaries and are based on the best available data. These files are availablefor public use at locations defined in this metadata record.

Purpose:

These GIS compatible digital files are provided to promote an understanding of the boundaries of each national marine sanctuary. They are based on the legal definition of each sanctuary as defined in the Code of Federal Regulations, at 15C.F.R. Part 922 and the subparts for each national marine sanctuary. These digital files are not intended and should not be relied upon for use in navigation or legal purposes. For legal questions relating to the digital files, please contact the ONMS at the information provided in this metadata record.

Notes:

1360

Other Citation Details:

none

Keywords

Theme Keywords

Thesaurus Keyword
ISO 19115 Topic Category boundaries
NOS Data Explorer Topic Category Marine Boundaries
NOS Data Explorer Topic Category Nautical Charting
None CFR
None Code of Federal Regulations
None marine protected area
None MPA
None National Marine Sanctuary
None NMS
None ONMS

Spatial Keywords

Thesaurus Keyword
None Marine
None National Marine Sanctuary
None NMS
None Olympic
None Pacific Ocean
None Washington

Physical Location

Organization: Office of National Marine Sanctuaries
City: Silver Spring
State/Province: MD

Data Set Information

Data Set Scope Code: Data Set
Maintenance Note:

Continually on varying schedule

Data Presentation Form: vector digital data
Distribution Liability:

Users must assume responisibility to determine the appropriate use of These data. These boundaries are not to be used as LEGAL definitions. The boundaries are created with the most recent and accurate boundary information available, but the edges and/or borders of the boundaries may change due to the natural land changes, site boundary modification or higher resolution maps. Therefore, the currency or accuracy of These boundaries cannot be guaranteed.

Support Roles

Data Steward

CC ID: 500573
Date Effective From: 2004-12
Date Effective To:
Contact (Position): GIS Coordinator
Address: 1305 East-West Highway, 11th Floor
Silver Spring, MD 20910
Email Address: sanctuaries@noaa.gov
Phone: (301) 713-3125
Fax: (301) 713-0404

Distributor

CC ID: 500575
Date Effective From: 2004-12
Date Effective To:
Contact (Position): GIS Coordinator
Address: 1305 East-West Highway, 11th Floor
Silver Spring, MD 20910
Email Address: sanctuaries@noaa.gov
Phone: (301) 713-3125
Fax: (301) 713-0404

Metadata Contact

CC ID: 500576
Date Effective From: 2004-12
Date Effective To:
Contact (Position): GIS Coordinator
Address: 1305 East-West Highway, 11th Floor
Silver Spring, MD 20910
Email Address: sanctuaries@noaa.gov
Phone: (301) 713-3125
Fax: (301) 713-0404

Point of Contact

CC ID: 500574
Date Effective From: 2004-12
Date Effective To:
Contact (Position): GIS Coordinator
Address: 1305 East-West Highway, 11th Floor
Silver Spring, MD 20910
Email Address: sanctuaries@noaa.gov
Phone: (301) 713-3125
Fax: (301) 713-0404

Extents

Currentness Reference: 200412

Extent Group 1

Extent Group 1 / Geographic Area 1

CC ID: 500579
W° Bound: -125.681664
E° Bound: -124.183899
N° Bound: 48.50589
S° Bound: 47.129166

Extent Group 1 / Time Frame 1

CC ID: 500578
Time Frame Type: Discrete
Start: 2004-12

Spatial Information

Spatial Representation

Representations Used

Vector: Yes

Vector Representation 1

CC ID: 587707
Complex Object Present?: Yes
Complex Object Count: 1

Access Information

Security Class: Unclassified
Data Access Procedure:

Olympic Coast National Marine Sanctuary Digital Boundary File (ocnms_py.shp) Digital boundry files are available for public consumption from the Office of National Marine Sanctuaries through their internet site. Because URL addresses and pages change, the actual data URL is not listed here, but will be searchable within the site (http://sanctuaries.noaa.gov/) Requests may also be made through the ONMS Boundary Coordinator. See Distributor Contact Information for contact details.;

Data Access Constraints:

None

Data Use Constraints:

NOT FOR LEGAL USE

URLs

URL 1

CC ID: 500571
URL: http://sanctuaries.noaa.gov/library/imast_gis.html
URL Type:
Online Resource

Activity Log

Activity Log 1

CC ID: 500597
Activity Date/Time: 2010-10-18
Description:

Date that the source FGDC record was last modified.

Activity Log 2

CC ID: 500596
Activity Date/Time: 2017-04-05
Description:

Converted from FGDC Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details.

Activity Log 3

CC ID: 577380
Activity Date/Time: 2017-08-14
Description:

Partial upload of Maintenance Note field only.

Activity Log 4

CC ID: 587705
Activity Date/Time: 2017-09-13
Description:

Partial upload of Spatial Info section only.

Activity Log 5

CC ID: 602033
Activity Date/Time: 2017-11-01
Description:

Replaced entire Lineage section to populate new Source Contribution field.

Activity Log 6

CC ID: 718924
Activity Date/Time: 2018-02-08
Description:

Partial upload of Positional Accuracy fields only.

Technical Environment

Description:

Microsoft Windows 2000 Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 8.3.0.800

Data Quality

Accuracy:

Attributes were standardized by feature type (point, line, and polygon)across all sanctuary boundaries. The values recorded for each attributewere quality assured and believed to be accurate.

Horizontal Positional Accuracy:

Positional accuracy will vary depending on source

Vertical Positional Accuracy:

Positional accuracy will vary

Completeness Report:

Where possible, the entire boundary for the sanctuary is represented by this digital file.

Conceptual Consistency:

The data were topologically cleaned.

Lineage

Sources

Code of Federal Regulations, Title 15, Volume 3

CC ID: 602035
Contact Name: US Federal GovernmentUS Department of CommerceNational Oceanic and Atmospheric Administration
Publish Date: 2003-01-01
Extent Type: Range
Extent Start Date/Time: 1996
Extent End Date/Time: 2003
Source Contribution:

The depicted shoreline of the sanctuary boundary wasderived in part from information contained within the CFR. | Type of Source Media: online

Raster Coastal Map Series Showing Hydrography and Topography Found on NOAA's Charted Nautical Charts for All Near-Shore Geographic Areas of the U.S.

CC ID: 602034
Contact Name: NOAA Office of Coast Survey (OCS)
Publish Date: 2001-01-10
Extent Type: Continuing
Extent Start Date/Time: 1995-01-01
Citation URL: http://nauticalcharts.noaa.gov/csdl/ctp/cm_vs.htm
Source Contribution:

All information in Coastal Maps is derived from the Source Nautical Chart. | Source Geospatial Form: raster digital data | Type of Source Media: Raster Images

Process Steps

Process Step 1

CC ID: 602036
Description:

The geographic boundary coordinates listed within the United StatesCode of Federal Regulations (CFR) were converted to decimal degreesand a text file was created. A point coverage was then generatedusing ArcInfo GIS. The coverage was projected into the GeographicCoordinate System and overlaid on large scale nautical charts andanalyzed with additional data such as adjacent sanctuaries andshorelines. Specific attention was given to analysis ofinconsistencies between textual descriptions and listedcoordinates. The polyline files were created using a combination of thecoordinate list from the CFR and applicable shoreline vector files. Forpoint files, two methods were used. If the sanctuary had a shorelinecomponent, a polyline to point script was used to create a point foreach vertice. If a shoreline component was not present, then theoriginal coordinates from the CFR were used to create a point shapefile.Polygon files were created by converting polylines to polygons. Formore detailed process description, please use contact information below.

Process Date/Time: 2004-12-01 00:00:00

Child Items

Rubric scores updated every 15m

Rubric Score Type Title
Entity (ENT) cbnms_py

Catalog Details

Catalog Item ID: 40109
Metadata Record Created By: Tyler Christensen
Metadata Record Created: 2017-04-05 14:27+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2019-06-04 13:14+0000
Metadata Record Published: 2018-02-08
Owner Org: ONMS
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Next Review Date: 2019-02-09