Coast Guard Sectors Southeast United States

Metadata also available as

Metadata:

Identification_Information
Data_Quality_Information
Spatial_Data_Organization_Information
Spatial_Reference_Information
Entity_and_Attribute_Information
Distribution_Information
Metadata_Reference_Information

Identification_Information:

Citation:

Citation_Information:

Originator: United States Coast Guard Districts Operations Systems Center

Publication_Date: 04/30/07

Publication_Time: Unknown

Title: Coast Guard Sectors Southeast United States

Geospatial_Data_Presentation_Form: vector digital data

Publication_Information:

Publication_Place: Kearneysville, WV
Publisher: Coast Guard Operations Systems Center

Description:

Abstract:: The Coast Guard Sectors are delineated in the description in the 33 CFR for each Sector Boundary & Area of Responsibility where latitude and longitude coordinates as well as county/state/national boundaries are included to describe the boundaries for each zone. In addition, whenever the Area of Responsibility boundary is over water the EEZ shapefile is referenced for those occurrences. This layer covers the Coast Guard Sector Boundaries for the following sectors: Boston, Long Island Sound, Delaware Bay, Baltimore, Key West, Miami, Mobile, Los Angeles-Long Beach, San Diego, Guam, Honolulu, San Juan, Buffalo, Detroit, Lake Michigan, Sault Ste. Marie, North Carolina, Honolulu, Northern New England, New York, Charleston, Portland, Seattle, Savannah, Corpus Christi, Hampton Roads, Houston-Galveston, New Orleans, Lower Mississippi River, Upper Mississippi River, Ohio Valley, Southeastern New England, San Francisco, St. Petersburg, Jacksonville, Anchorage and Juneau.
Purpose:: The purpose of this layer is to provide the United States Coast Guard with a single map layer that includes the Coast Guard Sector Boundaries and Area of Responsibility.

Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: 04/29/07

Currentness_Reference: publication date

Status:

Progress: In work
Maintenance_and_Update_Frequency: As needed

Spatial_Domain:

Bounding_Coordinates:

West_Bounding_Coordinate: -180.000000
East_Bounding_Coordinate: 180.000000
North_Bounding_Coordinate: 90.000000
South_Bounding_Coordinate: -89.972657

Keywords:

Place:

Place_Keyword: United States
Place_Keyword: Long Island Sound
Place_Keyword: Delaware Bay
Place_Keyword: Key West
Place_Keyword: Miami
Place_Keyword: Mobile
Place_Keyword: Los Angeles-Long Beach
Place_Keyword: San Diego
Place_Keyword: Guam
Place_Keyword: Honolulu
Place_Keyword: Baltimore
Place_Keyword: San Juan
Place_Keyword: Buffalo
Place_Keyword: Detroit
Place_Keyword: Lake Michigan
Place_Keyword: Sault Ste. Marie
Place_Keyword: North Carolina
Place_Keyword: Northern New England
Place_Keyword: New York
Place_Keyword: Charleston
Place_Keyword: Portland
Place_Keyword: Seattle
Place_Keyword: Corpus Christi
Place_Keyword: Hampton Roads
Place_Keyword: Houston-Galveston
Place_Keyword: New Orleans
Place_Keyword: Lower Mississippi River
Place_Keyword: Ohio Valley
Place_Keyword: Southeastern New England
Place_Keyword: San Francisco
Place_Keyword: Upper Mississippi River
Place_Keyword: St. Petersburg
Place_Keyword: Jacksonville
Place_Keyword: Boston
Place_Keyword: Anchorage
Place_Keyword: Juneau
Place_Keyword: Savannah

Access_Constraints: None

Use_Constraints:

Not recommended for navigation These unaltered data may not be redistributed without all of the elements of the metadata listed in the Supplemental_Information section of this metadata document. It is recommended that third parties wishing to use these data obtain them from the Distributor listed in this metadata document.
If these data are altered or incorporated into another dataset, they are not to be redistributed without also: altering the name of the datasetluding a Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998) compliant metadata file that describes the dataset and reflects the alteration steps that makes the new dataset different from this one, and citing this dataset in the metadata as a source for the altered dataset using the source citation specified below.
If these digital data are used in the production of a report or in the compilation of a standalone printed map, then this dataset is to be cited in the report or on the map using the source citation specified below.
The following source citation is to be used when citing this dataset: USCG - OSC Enterprise GISInventory Dataset 'Coast Guard Sectors source data, Geographic NAD83, USCG - OSC Enterprise GIS
Users hereby agree to abide by the use and reproduction conditions specified above. By using the data described in these metadata, the user acknowledges that the terms and conditions of use have been read and that the user is bound by these criteria.

Point_of_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: United States Coast Guard Operations Systems Center
Contact_Person: OSC Customer Support

Contact_Position: Customer Support

Contact_Voice_Telephone: 1-877-USCG-SYS (872-4797)

Contact_Voice_Telephone: 304-264-2500

Contact_Facsimile_Telephone: 304-262-5995

Contact_Electronic_Mail_Address: CustomerSupport@osc.uscg.mil

Hours_of_Service: 0630 EST to 1830 EST

Contact_Instructions:

The OSC's Customer Support Division is operated from 0630 EST to 1830 EST.
Support is also provided after hours Monday thru Friday from 1830 EST to 0630 EST including weekends for the following applications: AMVER/SURPIC, CASP, RAS, and MISLE.

Data_Set_Credit:

Operation Systems Center (OSC), United States Coast Guard (USCG),

Security_Information:

Security_Classification: Restricted

Native_Data_Set_Environment:

Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.1.3000

Data_Quality_Information:

Attribute_Accuracy:

Attribute_Accuracy_Report: All features are assigned attributes

Quantitative_Attribute_Accuracy_Assessment:

Attribute_Accuracy_Value: Sector
Attribute_Accuracy_Explanation:: This code equals the official name of each Marine Inspection and Captain of the Port Zone.

Logical_Consistency_Report:

This data was digitized manually from textural descriptions of (enter subject here) taken from (source document name here) The accuracy of this data depends on the clarity of the written description from (source document) and the amount and quality of collateral data that may have been used. When provided this data is accurate to the (Example here would be Degree Minute Second or Degree/Minute of Longitude/Latitude). Should any errors be found please report them to the USCG OSC Customer Support.

Completeness_Report:

Data is current as of : March 29, 2006 or date of Decision Memos on the Sectors Homepage.

Positional_Accuracy:

Horizontal_Positional_Accuracy:

Horizontal_Positional_Accuracy_Report:: When provided this data is accurate to the Degree and Minute and Second of the Longitude and latitude.
Quantitative_Horizontal_Positional_Accuracy_Assessment:

Lineage:

Source_Information:

Source_Citation:

Citation_Information:

Originator: USCG OSC
Publication_Date: Unknown
Publication_Time: Unknown
Title: Update this area if any other source data was used.
Other_Citation_Details:: enter in the CFR information here. Use the + sign to enter in individual CFR descriptions.

Type_of_Source_Media: Line file

Source_Time_Period_of_Content:

Source_Currentness_Reference: publication date

Source_Citation_Abbreviation: Database Connections\GISRead@USCG@GISDevdb01.sde\USCG.ESRI.ezz

Source_Contribution:

The USCG.ESRI.ezz linefile feature is referenced as it is used as part of a boundary for many sectors. This shapefile USCG.ESRI..ezz is located on the SDE.

Source_Information:

Type_of_Source_Media: Shapefile
Source_Citation_Abbreviation:: Database Connections\GISRead@USCG@GISDevdb01.sde\USCG.ESRI.Counties2000
Source_Contribution:: The USCG.ESRI.Counties2000 shapefile is referenced as the descriptions for many of the Sectors defined parts of the boundary on state and/or county boundaries. The USCG.ESRI. Counties2000 shapefile is located on the SDE.

Source_Information:

Type_of_Source_Media: Shapefile
Source_Citation_Abbreviation:: Database Connections\GISRead@USCG@GISDevdb01.sde\USCG.ESRI.mjwater
Source_Contribution:: The USCG.ESRI.mjwater shapefile is referenced as a few sectors descriptions mention that a interior body of water such as a lake, reservoir, or river, composes a portion of the sector boundary. The USCG.ESRI.mjwater shapefile is located on the SDE.

Source_Information:

Type_of_Source_Media: Shapefile
Source_Citation_Abbreviation:: Database Connections\GISRead@USCG@GISDevdb01.sde\USCG.ESRI.World_Counties2000
Source_Contribution:: The USCG.ESRI.World_Counties2000 shapefile is referenced as a few sectors are some U.S. territories. The USCG.ESRI.World_Counties2000 is located on the SDE.

Process_Step:

Process_Description: This Dataset was created using the GCS NAD83 projection.

Spatial_Data_Organization_Information:

Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:

Spatial_Reference_Information:

Horizontal_Coordinate_System_Definition:

Planar:

Map_Projection:

Map_Projection_Name: NAD 1983 2011 Florida GDL Albers

Albers_Conical_Equal_Area:

Standard_Parallel: 24.0
Standard_Parallel: 31.5
Longitude_of_Central_Meridian: -84.0
Latitude_of_Projection_Origin: 24.0
False_Easting: 400000.0
False_Northing: 0.0

Planar_Coordinate_Information:

Planar_Coordinate_Encoding_Method: coordinate pair

Coordinate_Representation:

Abscissa_Resolution: 0.0001
Ordinate_Resolution: 0.0001

Planar_Distance_Units: meter

Geodetic_Model:

Horizontal_Datum_Name: D NAD 1983 2011
Ellipsoid_Name: GRS 1980
Semi-major_Axis: 6378137.0
Denominator_of_Flattening_Ratio: 298.257222101

Entity_and_Attribute_Information:

Detailed_Description:

Entity_Type:

Entity_Type_Label: GIS.FWC.coast_guard_sectors

Attribute:

Attribute_Label: Shape

Attribute_Definition: Feature geometry.

Attribute_Definition_Source: ESRI