Data Management Plan (Deprecated)

Anchorages are well-defined navigable waters where a vessel may safely drop anchor. The size, shape, and conditions for use of these areas can vary widely. Generally, anchorages are not used for an indefinite duration, nor are they routinely used for maintenance, repair, overhaul, bunkering, or sea trials.

Process Steps:

• 2017-06-01 00:00:00 - 1. Go to http://www.gpo.gov/fdsys/pkg/CFR-2016-title33-vol1/pdf/CFR-2016-title33-vol1-chapI.pdf, http://www.gpo.gov/fdsys/pkg/CFR-2016-title33-vol2/pdf/CFR-2016-title33-vol2-chapI.pdf & http://www.gpo.gov/fdsys/pkg/CFR-2016-title33-vol3/pdf/CFR-2016-title33-vol3-chapIV.pdf and record all anchorage area info into a spreadsheet including lat/long data 2. Import sheet into ArcGIS, convert to xy coordinates, and export as a point feature class 3. Convert point feature class to polygon by connecting corner coordinates and joining attribute info NOTE: Areas from the following locations were not included, as they are all inland locations: Section 110.127 Lake Mohave and Lake Mead, NV and AZ Section 110.127a Lake Powell, UT-AZ Section 110.127b Flaming Gorge Lake, WY-UT Section 110.72c Lake Murray, SC 4. Go to https://encdirect.noaa.gov/ and download the following at full extent: Approach_Anchor_Berth_area, Approach_Anchor_Berth_point Approach_Anchorage_Area, Approach_Anchorage_Area_point Coastal_Anchorage_Area, Coastal_Anchorage_Area_point General_Anchorage_Area, General_Anchorage_Area_point Harbour_Anchor_Berth_area, Harbour_Anchor_Berth_point Harbour_Anchorage_Area, Harbour_Anchorage_Area_point Berthing_Anchorage_Area Overview_Anchorage_Area_point 5. Import all of the polygon layers into a single feature class and the point layers into a separate feature class 6. Buffer the point features to 500 feet 7. Compare between the layers, removing duplicates, and compare to NOAA_RNC continuous raster at ArcGIS on seamlessrnc.nauticalcharts.noaa.gov as a guide 8. Union the polygon and point feature classes with the CFR feature class and merge and combine features where overlap occurs, again giving the CFR features the most importance 9. Fill in any missing attributes using RNC info 10. Delete all superfluous fields 11. Check geometry and project data into WGS 1984 Auxiliary Sphere
• 2023-08-01 00:00:00 - 1. Review existing geometry to determine which features should be re-created from the CFR. 2. Within a new feature class, add existing features or create new features, in the order these are listed within section 110 of the latest available CFR. 3. In two cases (110.128, Columbia River, OR and 110.168(a)(5)(iii), Hampton Roads, VA), the RNC was used since it was the more reliable source. 4. Update or add attributes as features are created. 5. Features from the CFR that are not part of this data set include: 5a. The 14 features (for 110.127 Lake Mohave and Lake Mead, Nevada and Arizona) were not created, since there are no nautical charts or shorelines to assist with the generation of geometry. 5b. The 6 features (for 110.127a Lake Powell, Utah-Arizona) were not created, since there are no nautical charts or shorelines to assist with the generation of geometry. 5c. The 4 features (for 110.127b Flaming Gorge Lake, Wyoming-Utah) were not created, since there are no nautical charts or shorelines to assist with the generation of geometry. 6. Use the U.S. State Submerged Lands data set to create features outside CONUS (e.g. 110.129 in Hawaii). 7. It was discovered that not all new CFR features (since the last data update) were reflected by their respective currentness date in the CFR (e.g. 110.157a 19 and 20, which still showed a date of 12/12/1967, or 110.195a 34-37, which still showed a date of 10/8/1981). 8. Check Geometry for Esri and OGC validation.