CBSEG_104

ESRI ArcCatalog 9.2.2.1350 Cbseg2003_st uses state and district boundary data to subdivide the Chesapeake Bay Program monitoring segments that encompass multiple jurisdictions into separate polygons and to assign a state code to all segments and subdivided segments . The 2003 Chesapeake Bay Program Segmentation Scheme (cbseg2003) was a revision of the 2000 version that incorporates four changes: the addition of a new segment (ANATF) that separates the Anacostia River from the rest of the Potomac Tidal Fresh (POTTF) segment, the merger of two Elizabeth River segments (ELIMH and ELIPH into ELIPH) and the small segment boundary location changes between Mattaponi River segments MPNTF and MPNOH and between Choptank River segments CHOTF and CHOOH. The Chesapeake Bay Program Segmentation Scheme is used as a way to organize the collection, analysis and presentation of environmental data within the Chesapeake Bay and its tidal tributaries. Originally, the impetus to divide certain Chesapeake Bay Program segments came from the desire of Maryland, Virginia and the District of Columbia to be able to meet SAV restoration and water clarity goals for the Potomac River. Bay Program segments were allocated goals, but the jurisdictions wanted to know what portions of those segments were their responsibility. To allocate the area of Bay Program segments shared by two or more jurisdictions to the appropriate jurisdiction it became necessary to get state and District boundary data to be able to subdivide those segments. However, there were no legally recognized boundary data for the Potomac River or even one common dataset that all of the jurisdictions were using. An attempt was made to create a jurisdictional boundary file for the tidal Potomac River that Maryland, Virginia and the District of Columbia could agree upon. Chesapeake Bay Program 20050902 CBSEG_104 vector digital data withheld publication date 20050902 Complete None planned -77.516902 -75.383457 39.613910 36.696728 segmentation scheme monitoring segments MD DC VA DE U.S. Postal Abbreviations Chesapeake Bay None None Howard Weinberg Chesapeake Bay Program GIS Analyst 410-267-5735 410-267-5777 hweinber@chesapeakebay.net mailing and physical address

410 Severn Ave

Annapolis MD 21403 ESRI ArcCatalog 9.2.2.1350 CBSEG_104 283857.09375 465757.0625 4384982.5 4063958.25 1 -77.516902 -75.383457 39.61391 36.696728 1 1 -77.516902 -75.383457 39.613910 36.696728 FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998 local time REQUIRED: The person responsible for the metadata information. REQUIRED: The organization responsible for the metadata information. REQUIRED: The mailing and/or physical address for the organization or individual. REQUIRED: The city of the address. REQUIRED: The state or province of the address. REQUIRED: The ZIP or other postal code of the address. REQUIRED: The telephone number by which individuals can speak to the organization or individual. 20080304 ISO 19115 Geographic Information - Metadata DIS_ESRI1.0 dataset Downloadable Data 0.000 002 withheld Local Area Network 0.000 Personal GeoDatabase Feature Class File Geodatabase Feature Class 0.000 Vector Simple FALSE 0 TRUE FALSE coordinate pair meters 0.000100 0.000100 North American Datum of 1983 Geodetic Reference System 80 6378137.000000 298.257222 NAD_1983_UTM_Zone_18N EPSG 6.11(3.0.1) 0 CBSEG_104 Feature Class 0 OBJECTID_1 FID OID 4 0 0 Internal feature number. Esri Sequential unique whole numbers that are automatically generated. Shape Feature geometry. ESRI Coordinates defining the features. Shape Geometry 0 0 0 STATE STATE String 2 0 0 CBPSEG CBPSEG String 6 0 0 OBJECTID Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. OBJECTID Integer 4 0 0 CBSEG_104 CBSEG_104 String 9 0 0 WQ_SEGS WQ_SEGS String 6 0 0 Shape_Length Shape_Length Double 8 0 0 Length of feature in internal units. Esri Positive real numbers that are automatically generated. Shape_Area Area of feature in internal units squared. ESRI Positive real numbers that are automatically generated. Shape_Area Double 8 0 0 The Segmentation Scheme polygons divide the Chesapeake bay and tidal tributaries into regions that have similar geographic (such as the upper portion of the Bay) and natural (such as salintiy regime) characteristics 20080304 After examining several different digital boundary files, it was determined that the best boundary along the Virginia shoreline was one produced by the Virginia Department of Conservation and Recreation (VA DCR). The VA DCR boundary was mostly based on the state boundaries appearing on digital 1:24000 scale quad sheets (digital raster graphics, or DRGs). The Maryland-Virginia state boundary delineated on the quad sheets appears to be based on the Mathews-Nelson Survey of 1927, which used the legally defined boundary of the low-water mark on the Virginia side of the river, except where embayments were crossed from one point on land to another point on land. However, shorelines can change in almost 80 years, either through natural or anthropogenic influences, which may partially account for discrepancies between the legal definition of the boundaries and how the data appear today. The state boundary was digitized on-screen using the DRGs as a background upon which to trace the line work. In the lower Potomac River, DCR used 1:12000 scale digital orthophoto quarter quads (DOQQs) having photo dates of 1992-1996 as the source for the boundary definition. Maps of the state boundary along the Potomac River are included in Technical Support Document for Identification of Chesapeake Bay Designated Uses and Attainability: 2004 Addendum, 2004. For the Maryland-District of Columbia boundary lines that cross the Potomac River diagonally from the Virginia shoreline, data provided by the D.C. Water Quality Control Branch were used. These and the VA DCR data were merged to create a boundary file that all three jurisdictions agreed to use in allocating restoration goals in those shared segments. Later, it was determined that all segments that crossed jurisdictional boundaries needed to be subdivided. This included the continuation of the Maryland-Virginia boundary across the Bay and partly up the Pocomoke, and the two tidal tributaries (C & D Canal and Nanticoke River) that straddled the Maryland-Delaware boundary. The Maryland-Virginia state boundary from VA DCR extended across the bay and up the Pocomoke River. This was used with slight modification of some of the vertices of the boundary in Pocomoke Sound that subdivided segments POCMH and POCOH. Maryland Department of the Environment provided coordinates of buoys that define the state boundary at those vertices. The boundary data were altered to reflect these buoy locations. The differences in distance between the buoy locations and the vertices in the DCR data were all less than 30 meters, most less than 10 meters. For the Maryland-Delaware boundary, Maptech 1:24,000 scale DRGs were used to digitize the boundary line on-screen. The GIS coverage was then edited and the two affected segments were split by the state boundary. Dataset copied. withheld 20080111 14581300 Dataset copied. withheld 20080112 22312300 Dataset copied. withheld 20080220 11114400 Dataset copied. withheld 20080220 12411000 Dataset copied. withheld 20080220 14131900 Dataset copied. withheld 20080304 10491100 Dataset copied. withheld 20080304 10571500 Dataset moved. withheld 20080304 10574400 Dataset copied. withheld 20080304 11445100 Dataset copied. withheld 20080305 13464900 Dataset copied. withheld 20081008 15135800 Dataset copied. withheld 20100308 11355600 cbsegs_104_v2_simplified50m 002 0.000 283857.093800 465757.062500 4063958.250000 4384982.500000 1 Projected GCS_North_American_1983 Linear Unit: Meter (1.000000) NAD_1983_UTM_Zone_18N <ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.0.0'><WKT>PROJCS["NAD_1983_UTM_Zone_18N",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],PARAMETER["False_Easting",500000.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-75.0],PARAMETER["Scale_Factor",0.9996],PARAMETER["Latitude_Of_Origin",0.0],UNIT["Meter",1.0],AUTHORITY["EPSG",26918]]</WKT><XOrigin>-5120900</XOrigin><YOrigin>-9998100</YOrigin><XYScale>10000</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.001</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>26918</WKID><LatestWKID>26918</LatestWKID></ProjectedCoordinateSystem> 20230707 10231100 20230707 10231100 20230707 13322000 1.0 FALSE