Data Content for Marine Boundaries:

1
Data Content for Marine Boundaries A case
study using the cadastral data content
standard for the Olympic Coast National Marine
Sanctuary David Stein, TPMC/CSC Mitchell Tartt,
NMSP
2
Presentation Outline

• 1) Existing Standards
• Cadastral Data Content Standard
• Application of Cadastral Standard
• Olympic Coast National Marine Sanctuary
• Metadata and documentation
• Next steps
• Discussion

3
Existing standards

• Cadastral Data Content Standard Cadastral
  Subcommittee
• Provides common definitions and attributes for
  cadastral and marine cadastral information found
  in public records which will faciliate use and
  understanding of land and submerged land records.
• Governmental Unit Boundary Data Exchange Standard
  FGDC Subcommittee for Cultural and Demographic
  Data
• Establishes the content requirement for the
  collection and interchange of governmental unit
  and other legal entity boundary data.
• IHO Transfer Standard for Digital Hydrographic
  Data S-57
• To be used as the exchange and content standard
  for digital hydrographic data.

4
Cadastral Data Content Standard

• Pros
• Endorsed by the FGDC in 1996
• Nationally recognized
• Contains most of the elements that are needed to
  create offshore boundary data
• Flexible in interpretation
• Cons
• To be determined

5
Olympic Coast National Marine Sanctuary
6
OCNMS Boundary I

• Designation Process - Environmental Impact
  statement
• Boundary alternatives and preferred alternative
• Terms of designation - Boundary definition
• Code of Federal Regulations
• The Sanctuary boundary extends from Koliath
  Point due north to the United States/Canada
  international boundary. The Sanctuary boundary
  then follows the U.S./Canada boundary seaward to
  the 100 fathom isobath. The seaward boundary of
  the Sanctuary approximates the 100 fathom isobath
  in a southerly direction from the U.S. Canada
  international boundary to a point due west of the
  mouth of the Copalis River cutting across the
  heads of Nitnat, Juan de Fuca and Quinault
  Canyons.

7
OCNMS Boundary II

• Outer boundary
• US Territorial limit / Canadian Border
• 100 fathom isobath
• Inner boundary
• Mean Higher High Water
• Mean Lower Low Water
• Federally managed lands
• Indian reservations
• State and county managed lands
• La Push Harbor

8
Data Needed to Construct Boundary
9
OCNMS Seaward BoundaryCoordinates



The Sanctuary boundary extends from Koliath Point
due north to the United States/Canada
international boundary. The Sanctuary boundary
then follows the U.S./Canada boundary seaward to
the 100 fathom isobath. The seaward boundary of
the Sanctuary approximates the 100 fathom
isobath in a southerly direction from the U.S.
Canada international boundary to a point due west
of the mouth of the Copalis River cutting across
the heads of Nitnat, Juan de Fuca and Quinault
Canyons. Source U.S. Code of Federal
Regulations
10
OCNMS Coastal Boundary IMHHW and MLLW
The coastal boundary of the Sanctuary is the
mean higher high water line when adjacent to
Federally managed lands cutting across the
mouths of all rivers and streams, except where
adjacent to Indian reservations, State and
County owned lands in such case, the coastal
boundary is the mean lower low water line. Data
Sources NOAA OCS Coastal Map/Extracted Vector
Shoreline Washington State Department of Ecology
Indian Reservation data Scale 1180K 1100K
11
OCNMS Coastal Boundary IIIndian Reservations
The coastal boundary of the Sanctuary is the
mean higher high water line when adjacent to
Federally managed lands cutting across the
mouths of all rivers and streams, except where
adjacent to Indian reservations, State and
County owned lands in such case, the coastal
boundary is the mean lower low water line. Data
Sources Washington State Department of Ecology
Indian Reservation data Scale 1100K
12
OCNMS Coastal Boundary IIILa Push Harbor
(Colreg Line)
La Push harbor is excluded from the Sanctuary
shoreward of the International Collision at Sea
Regulation (Colreg.) demarcation lines. Data
Sources NOAA Chart 18480_2 Scale 110K
13
(No Transcript)
14
Cadastral Data Content StandardDatabase
Construction

• Data content sources Cadastral Data Content
  Standard NMS Boundary Project
• Data format ArcView Shapefile
• Entity National Marine Sanctuary Boundary
  (OCNMS)
• Feature Types Polyline, Polygon
• Attributes included from the Cadastral Data
  Content Standard
• record bounds legal status map unit source
  type source agent source comment distance
  unit distance type measurement method
  others?
• Attributes created for the NMSP Boundary
  Project
• scale datum feature notes length area
  start end

15
Metadata

• FGDC compliant
• Methodology captured in Process Description
• Process_Description
• The geographic boundary coordinates
  listed within the United States Code of Federal
  Regulations (CFR) were converted to decimal
  degrees in NAD83 and a text file was created. A
  line coverage was then generated using ArcINfo
  GIS. The coverage was projected into the
  Geographic Coordinate System and overlaid on
  large-scale nautical charts to check for
  accuracy. To create the coastal boundary of the
  OCNMS, the following processing steps were used
• 1) Obtained vector shorelines from the NOAA
  Office of Coast Survey for largest scale charts.
  The following charts were used Cape Flattery
  (140000), Columibia River to Destruction Island
  (1180000), and Destruction Island to Amphitate
  Point (1176000).
• 2) Obtained Indian Reservation data
  from the Washington State Department of Ecology
  at a scale of 1100000.
• 3) The data were converted to decimal
  degrees, NAD83 and added to an ArcView project.
• 4) Straight line segments were
  digitized between the MHW (vector shoreline) and
  the MLW (Indian Reservations) to connect the
  shorelines.
• 5) Straight lines were digitized to
  close rivers and streams along the coastal
  boundary of the OCNMS.
• 6) The COLREG line was digitized from
  the 110000 scale Quillayate River Entrance Chart
  as described in the CFR.
• 7) The resulting data set was manually
  QA/QC'd to remove overshoots and undershoots,
  then cleaned and built for topology.
• 8) The line segments of the polyline
  file were then attributed using standard field
  names and domains.
• Attributes fully described in Entity and
  Attribute Information section

16
Next Steps

• Finalize remainder of NMS digital boundaries.
• Work with MBWG and Cadastral Subcommittee to
  refine/customize data content for marine
  boundaries.
• Develop data model, implementation guidelines for
  marine boundaries
• Best Practices Handbook

17
Questions

• Is there anything missing from this customized
  application of the Cadastral Data Content
  Standard?
• Should anything be formally added to the CS to
  address data content for marine boundaries?
• Does this type of methodology and documentation
  bring us closer to having compatible and user
  friendly boundary files?

18

• For Additional Information
• David Stein
• NOAA Coastal Services Center
• Dave.Stein_at_noaa.gov
• Mitchell Tartt
• National Marine Sanctuary Program
• Mitchell.Tartt_at_noaa.gov

19
Discussion...