ÿþ<HTML> <HEAD> <SCRIPT><!-- function fix(e) { var par = e.parentNode; e.id = ""; e.style.marginLeft = "0.42in"; var pos = e.innerText.indexOf("\n"); if (pos > 0) { while (pos > 0) { var t = e.childNodes(0); var n = document.createElement("PRE"); var s = t.splitText(pos); e.insertAdjacentElement("afterEnd", n); n.appendChild(s); n.style.marginLeft = "0.42in"; e = n; pos = e.innerText.indexOf("\n"); } var count = (par.children.length); for (var i = 0; i < count; i++) { e = par.children(i); if (e.tagName == "PRE") { pos = e.innerText.indexOf(">"); if (pos != 0) { n = document.createElement("DD"); e.insertAdjacentElement("afterEnd", n); n.innerText = e.innerText; e.removeNode(true); } } } if (par.children.tags("PRE").length > 0) { count = (par.children.length); for (i = 0; i < count; i++) { e = par.children(i); if (e.tagName == "PRE") { e.id = ""; if (i < (count-1)) { var e2 = par.children(i + 1); if (e2.tagName == "PRE") { e.insertAdjacentText("beforeEnd", e2.innerText+"\n"); e2.removeNode(true); count = count-1; i = i-1; } } } } } } else { n = document.createElement("DD"); par.appendChild(n); n.innerText = e.innerText; e.removeNode(true); } } --></SCRIPT> </HEAD> <BODY oncontextmenu="return true"> <A name="Top" /> <H1>Waterbody_SJRWMD24k</H1> <H2>Metadata:</H2> <UL> <LI><A HREF="#Identification_Information">Identification_Information</A></LI> <LI><A HREF="#Data_Quality_Information">Data_Quality_Information</A></LI> <LI><A HREF="#Spatial_Data_Organization_Information">Spatial_Data_Organization_Information</A></LI> <LI><A HREF="#Spatial_Reference_Information">Spatial_Reference_Information</A></LI> <LI><A HREF="#Entity_and_Attribute_Information">Entity_and_Attribute_Information</A></LI> <LI> <A HREF="#461862208"> Distribution_Information </A> </LI> <LI><A HREF="#Metadata_Reference_Information">Metadata_Reference_Information</A></LI> </UL> <A name="Identification_Information"><HR /></A> <DL> <DT><I>Identification_Information:</I></DT> <DD> <DL> <DT><I>Citation:</I></DT> <DD> <DL> <DT><I>Citation_Information:</I></DT> <DD> <DL> <DT><I>Originator:</I> St. Johns River Water Management District.</DT> <DT><I>Publication_Date:</I> August 2011</DT> <DT><I>Title:</I></DT> <DD>Waterbody_SJRWMD24k</DD> <DT><I>Geospatial_Data_Presentation_Form:</I> vector digital data</DT> <DT><I>Publication_Information:</I></DT> <DD> <DL> <DT><I>Publication_Place:</I> Palatka, Florida</DT> <DT><I>Publisher:</I> St. Johns River Water Management District</DT> </DL> </DD> <DT><I>Online_Linkage:</I> <A TARGET="viewer" HREF="#"> \\DELL19735\C$\TempEllen\Waterbody_SJRWMD24k.shp</A> </DT> </DL> </DD> </DL> </DD> <DT><I>Description:</I></DT> <DD> <DL> <DIV> <DT><I>Abstract:</I></DT> <PRE ID="original">Waterbody is a polygon feature class delineating waterbodies such as lakes, rivers, estuaries, and wetlands. Waterbody was originally populated using the high resolution National Hydrography Dataset (NHD), but has subsequently been extensively updated by SJRWMD staff. * This layer is part of the SJRWMD Water Resources Geodatabase (WRGDB), which is based on the ArcHydro data model. When used in combination with other WRGDB layers, it participates in a geometric flow network and relationship classes. However, it can also be used independently as a simple 1:24,000 waterbody dataset. The field NHDFType identifies the feature type, e.g. LakePond or SwampMarsh. * The Waterbody layer also contains unique IDs for each feature. HydroCode is the SJRWMD waterbody ID. NHDComID is the original ID from the NHD, however, as features are edited, the integrity of NHDComID may be compromised, and we do not guarantee that the value is correct. * Date of last update: August 2011.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DIV> <DT><I>Purpose:</I></DT> <PRE ID="original">The Water Resources Geodatabase (WRGDB) was created to integrate water-related spatial information on a 1:24,000 scale, in a relational manner that supports hydrologic analysis and modeling efforts. The District uses this information for general mapping and cartographic purposes, and for small and medium scale hydrologic and assessment applications.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DIV> <DT><I>Supplemental_Information:</I></DT> <PRE ID="original">Additional information on the primary source of the Waterbody layer, the National Hydrography Dataset, can be found at http://nhd.usgs.gov/. Waterbodies were derived from two NHD layers: all features from the NHDWaterbody feature class, plus Stream-River and Canal-Ditch features from the NHDArea feature class. See the Positional Accuracy (Horizontal) section for information on topology / positional errors that have not yet been repaired in this data layer.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> <DT><I>Time_Period_of_Content:</I></DT> <DD> <DL> <DT><I>Time_Period_Information:</I></DT> <DD> <DL> <DT><I>Single_Date/Time:</I></DT> <DD> <DL> <DT><I>Calendar_Date:</I> REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.</DT> </DL> </DD> </DL> </DD> <DIV> <DT><I>Currentness_Reference:</I></DT> <PRE ID="original">publication date</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> <DT><I>Status:</I></DT> <DD> <DL> <DT><I>Progress:</I> Complete</DT> <DT><I>Maintenance_and_Update_Frequency:</I> Irregular</DT> </DL> </DD> <DT><I>Spatial_Domain:</I></DT> <DD> <DL> <DT><I>Bounding_Coordinates:</I></DT> <DD> <DL> <DT><I>West_Bounding_Coordinate:</I> -82.607490</DT> <DT><I>East_Bounding_Coordinate:</I> -80.110277</DT> <DT><I>North_Bounding_Coordinate:</I> 31.035362</DT> <DT><I>South_Bounding_Coordinate:</I> 27.119083</DT> </DL> </DD> </DL> </DD> <DT><I>Keywords:</I></DT> <DD> <DL> <DT><I>Theme:</I></DT> <DD> <DL> <DT><I>Theme_Keyword_Thesaurus:</I> SJRWMD-GIS Metadata Thesaurus</DT> <DT><I>Theme_Keyword:</I> Arc Hydro</DT> <DT><I>Theme_Keyword:</I> Water</DT> <DT><I>Theme_Keyword:</I> Waterbody</DT> <DT><I>Theme_Keyword:</I> Area</DT> <DT><I>Theme_Keyword:</I> Hydrography</DT> <DT><I>Theme_Keyword:</I> inland Waters</DT> <DT><I>Theme_Keyword:</I> Waterbodies</DT> <DT><I>Theme_Keyword:</I> Rivers</DT> </DL> </DD> <DT><I>Place:</I></DT> <DD> <DL> <DT><I>Place_Keyword_Thesaurus:</I> SJRWMD-GIS Metadata Thesaurus</DT> <DT><I>Place_Keyword:</I> Florida</DT> <DT><I>Place_Keyword:</I> St. Johns River Water Management District</DT> <DT><I>Place_Keyword:</I> Alachua County</DT> <DT><I>Place_Keyword:</I> Baker County</DT> <DT><I>Place_Keyword:</I> Bradford County</DT> <DT><I>Place_Keyword:</I> Brevard County</DT> <DT><I>Place_Keyword:</I> Clay County</DT> <DT><I>Place_Keyword:</I> Duval County</DT> <DT><I>Place_Keyword:</I> Flagler County</DT> <DT><I>Place_Keyword:</I> Indian River County</DT> <DT><I>Place_Keyword:</I> Lake County</DT> <DT><I>Place_Keyword:</I> Marion County</DT> <DT><I>Place_Keyword:</I> Nassau County</DT> <DT><I>Place_Keyword:</I> Okeechobee County</DT> <DT><I>Place_Keyword:</I> Orange County</DT> <DT><I>Place_Keyword:</I> Osceola County</DT> <DT><I>Place_Keyword:</I> Polk County</DT> <DT><I>Place_Keyword:</I> Putnam County</DT> <DT><I>Place_Keyword:</I> Seminole County</DT> <DT><I>Place_Keyword:</I> St. Johns County</DT> <DT><I>Place_Keyword:</I> Volusia County</DT> </DL> </DD> </DL> </DD> <DT><I>Access_Constraints:</I> None</DT> <DIV> <DT><I>Use_Constraints:</I></DT> <PRE ID="original">The St. Johns River Water Management District prepares and uses information for its own purposes and this information may not be suitable for other purposes. This information is provided "as is". Further documentation of this data can be obtained by contacting: St. Johns River Water Management District, Division of Integrated Application Systems, Post Office Box 1429, Palatka, Florida, 32178-1429, (386) 329-4500.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DT><I>Point_of_Contact:</I></DT> <DD> <DL> <DT><I>Contact_Information:</I></DT> <DD> <DL> <DT><I>Contact_Organization_Primary:</I></DT> <DD> <DL> <DT><I>Contact_Organization:</I> St. Johns River Water Management District</DT> </DL> </DD> <DT><I>Contact_Position:</I> GIS Data Manager, Information Resources Department</DT> <DT><I>Contact_Voice_Telephone:</I> 386-329-4145</DT> <DT><I>Contact_Electronic_Mail_Address:</I> gis_support@sjrwmd.com</DT> <DT><I>Hours_of_Service:</I> 0800 - 1700 ET</DT> </DL> </DD> </DL> </DD> <DT><I>Browse_Graphic:</I></DT> <DD> <DL> <DT><I>Browse_Graphic_File_Name:</I> <A TARGET="viewer" HREF="#"> X:\IR\GISProjects\WR_GDB\WorkDir\Doug\Artwork mxd\Waterbody Data Dictionary Illustration.jpg</A> </DT> <DT><I>Browse_Graphic_File_Type:</I> JPEG</DT> </DL> </DD> <DIV> <DT><I>Data_Set_Credit:</I></DT> <PRE ID="original">This data set was compiled from a combination of USGS data sets, internal SJRWMD data sets, and SJRWMD staff knowledge.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DT><I>Native_Data_Set_Environment:</I></DT> <DD>Microsoft Windows Vista Version 6.0 (Build 6001) Service Pack 1; ESRI ArcCatalog 9.3.1.1850</DD> </DL> </DD> </DL> <A HREF="#Top">Back to Top</A> <A name="Data_Quality_Information"><HR /></A> <DL> <DT><I>Data_Quality_Information:</I></DT> <DD> <DL> <DT><I>Positional_Accuracy:</I></DT> <DD> <DL> <DT><I>Horizontal_Positional_Accuracy:</I></DT> <DD> <DL> <DIV> <DT><I>Horizontal_Positional_Accuracy_Report:</I></DT> <PRE ID="original">This layer has some positional errors: features that came from the NHD Waterbody feature class are offset by up to 0.5 meter. The source of this offset is an error in the spatial reference of the input NHD datasets. The datasets were identified as using the 1983 HARN horizontal datum. However, they were actually in 1983, not HARN. This error was not discovered until after we loaded the NHDWaterbody features into the WRGDB Waterbody feature class. The datum error WAS corrected for NHDArea features before loading them into the WRGDB Waterbody feature class. As a result of this difference in how the two input sources were handled, there is frequent although very small overlap between features that came from the different NHD layers. For example, in places where a Swamp/Marsh (from NHDWaterbody) is adjacent to a Stream/River (from NHDArea), there is polygon overlap of up to 0.5 meter. The Waterbody outlet layer, the source of HydroJunctions for Waterbody, was developed with this overlap in place. Therefore some of the Junctions may not be exactly on the boundary of the related Waterbody. We hope to address this problem in the future. However, the geometric network and relationships that relate waterbodies to the network are still functional, even with these errors.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> </DL> </DD> <DT><I>Lineage:</I></DT> <DD> <DL> <DT><I>Process_Step:</I></DT> <DD> <DL> <DIV> <DT><I>Process_Description:</I></DT> <PRE ID="original">Created feature class from source NHD datasets (insert list here)</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DT><I>Process_Date:</I> September 2007</DT> <DT><I>Process_Contact:</I></DT> <DD> <DL> <DT><I>Contact_Information:</I></DT> <DD> <DL> <DT><I>Contact_Person_Primary:</I></DT> <DD> <DL> <DT><I>Contact_Person:</I> GIS Data Manager</DT> <DT><I>Contact_Organization:</I> SJRWMD</DT> </DL> </DD> </DL> </DD> </DL> </DD> </DL> </DD> <DT><I>Process_Step:</I></DT> <DD> <DL> <DIV> <DT><I>Process_Description:</I></DT> <PRE ID="original">Linked waterbodies to the HydroEdge network by assigning the HydroID of the appropriate HydroJunction to the JunctionID field of the waterbody. The process took a couple months to complete. Automatic generation of HydroJunctions resulted in many duplicate points for each waterbody; extra points had to be deleted and IDs transferred.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DT><I>Process_Date:</I> January 2008</DT> <DT><I>Process_Contact:</I></DT> <DD> <DL> <DT><I>Contact_Information:</I></DT> <DD> <DL> <DT><I>Contact_Person_Primary:</I></DT> <DD> <DL> <DT><I>Contact_Person:</I> GIS Data Manager</DT> <DT><I>Contact_Organization:</I> SJRWMD</DT> </DL> </DD> </DL> </DD> </DL> </DD> </DL> </DD> <DT><I>Process_Step:</I></DT> <DD> <DL> <DIV> <DT><I>Process_Description:</I></DT> <PRE ID="original">Reviewed connectivity to the network: select all features that intersect HydroEdge; from these, select features with null JunctionID (487 features); review to ensure that null JunctionID is valid.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DT><I>Process_Date:</I> July 2008</DT> <DT><I>Process_Contact:</I></DT> <DD> <DL> <DT><I>Contact_Information:</I></DT> <DD> <DL> <DT><I>Contact_Person_Primary:</I></DT> <DD> <DL> <DT><I>Contact_Person:</I> GIS Data Manager</DT> <DT><I>Contact_Organization:</I> SJRWMD</DT> </DL> </DD> </DL> </DD> </DL> </DD> </DL> </DD> <DT><I>Process_Step:</I></DT> <DD> <DL> <DIV> <DT><I>Process_Description:</I></DT> <PRE ID="original">Connected additional SwampMarsh features to the network. These were the features that do not intersect a HydroEdge and were therefore left out of the initial waterbody network connection. Rules: 1. Generally, the HydroJunction was placed at the downstream-most point of the HydroEdge that was nearest the SwampMarsh. 2. When a wetland was represented by multiple small SwampMarsh features, all features were assigned to the same single HydroJunction. This is common in the complex intertidal wetlands of Nassau and St. Marys Rivers Basins. 3. For SwampMarsh features contained within a larger LakePond waterbody, the junction was placed within the LakePond, at the downstream edge of the HydroEdge. 4. If a SwampMarsh feature no longer exists and will be deleted in future edits to the Waterbody layer, we did not connect it to the network. In estuarine areas, where features were often bordered by more than one HydroEdge and flow direction is not clear, we used best judgement to apply the above rules.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DT><I>Process_Date:</I> January 2009</DT> </DL> </DD> <DT><I>Process_Step:</I></DT> <DD> <DL> <DIV> <DT><I>Process_Description:</I></DT> <PRE ID="original">Systematic feature update: Edits were made on Waterbody, QuadBasin, HydroEdge, and HydroJunction at the same time, one Planning Unit at a time, in the Ocklawaha River and Florida Ridge Major Basins. Reference imagery: 2008 county true color imagery Wetland existence and boundaries source: 2004 SJRWMD land cover</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DT><I>Process_Date:</I> February-June 2009</DT> </DL> </DD> <DT><I>Process_Step:</I></DT> <DD> <DL> <DIV> <DT><I>Process_Description:</I></DT> <PRE ID="original">Systematic feature update: Edits were made on Waterbody, QuadBasin, HydroEdge, and HydroJunction at the same time, one Planning Unit at a time, in the Lower St. Johns River, Lake George, Middle St. Johns River, and Upper St. Johns River Major Basins. Reference imagery: 2008 county true color imagery Wetland existence and boundaries source: 2004 SJRWMD land cover</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DT><I>Process_Date:</I> July 2009 - January 2010</DT> </DL> </DD> <DT><I>Process_Step:</I></DT> <DD> <DL> <DIV> <DT><I>Process_Description:</I></DT> <PRE ID="original">Systematic feature update: Edits were made on Waterbody, QuadBasin, HydroEdge, and HydroJunction at the same time, one Planning Unit at a time, in the Northern Coastal and Indian River Lagoon Major Basins. Reference imagery: 2008 county true color imagery Wetland existence and boundaries source: 2004 SJRWMD land cover.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DT><I>Process_Date:</I> February, 2010 - April, 2010</DT> </DL> </DD> <DT><I>Process_Step:</I></DT> <DD> <DL> <DIV> <DT><I>Process_Description:</I></DT> <PRE ID="original">Systematic feature update: Edits were made on Waterbody, QuadBasin, HydroEdge, and HydroJunction at the same time, one Planning Unit at a time, in the St Mary's and Nassau River Major Basins. Also included were small southern sections of Charlton and Camden Counties Georgia. Reference imagery: 2008 county true color imagery Wetland existence and boundaries source: 2004 SJRWMD land cover.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DT><I>Process_Date:</I> April, 2010 - May, 2010</DT> </DL> </DD> <DT><I>Process_Step:</I></DT> <DD> <DL> <DIV> <DT><I>Process_Description:</I></DT> <PRE ID="original">Removed "NHDFLAG" field - were either not using or not using consistently. Are instead relying on the "EDIT_DATE" field to determine if a Waterbody feature has been modified. (edean 8/4/2010)</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> <DT><I>Process_Step:</I></DT> <DD> <DL> <DIV> <DT><I>Process_Description:</I></DT> <PRE ID="original">Extensive restoration efforts within the Upper St. Johns River Basin Project required additional revisions in the following areas: Banjo Groves, Ft. Drum Creek, Jane Green Creek, and Wolf Creek. These include removal of levees and the classification of many canals \ ditches to 'derelict' with the goal of returning natural flow characteristics. Collaborated with project expert: Ken Snyder. Project specific information can found at : X:\ES\USJRB\Library\Data\restoration</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DT><I>Process_Date:</I> August 2010</DT> </DL> </DD> <DT><I>Process_Step:</I></DT> <DD> <DL> <DIV> <DT><I>Process_Description:</I></DT> <PRE ID="original">1. Revised Waterbody features to split the surface area of the St. Johns River from that of its tributaries. In many areas, this was a straightforward task, and the location of the split was determined by QuadBasin boundaries. In some areas, the split was determined by accepted waterbody names, such as Mill Cove in Jacksonville. However, in areas where the St. Johns River is very complex, such as throughout the Middle and Upper Basins, the decisions had to be made under the guidance of subject matter experts. Primary subject matter experts included David Clapp and Joe Stewart from the Engineering Division. However, the results were also reviewed by additional staff. HydroEdge features were also edited so that they did not cross Waterbody boundaries, and HydroJunctions were edited as needed. The editing goal was that Waterbody, HydroEdge, and QuadBasin boundaries should all match. In some places, we were unable to trim small waterbody areas from the SJR waterbody due to the absence of HydroEdges in small canals or tributaries. 2. Added the field AlternateName to accomodate waterbodies that are considered part of the St. Johns River (primary name) but also have a different name referring to just that part; e.g. Mill Cove or Murphy Creek.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DT><I>Process_Date:</I> October 2010</DT> </DL> </DD> <DT><I>Process_Step:</I></DT> <DD> <DL> <DIV> <DT><I>Process_Description:</I></DT> <PRE ID="original">Over a period of several months, revisions focused on the coastal basins, primary subject matter expert: Whitney Green, Env. Sciences Division.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DT><I>Process_Date:</I> January 2011</DT> </DL> </DD> <DT><I>Process_Step:</I></DT> <DD> <DL> <DIV> <DT><I>Process_Description:</I></DT> <PRE ID="original">Final Intracoastal Waterway naming. To maintain consistency with USGS, all open bodies use USGS naming conventions complimented by a seperate 'alternate name' field. The 'alternate name' field is populated primarily by "Intracoastal Waterway" unless otherwise noted. Subject expert for the Northern Coastal Basin: Chrystal Yates.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DT><I>Process_Date:</I> March - 2011</DT> </DL> </DD> <DT><I>Process_Step:</I></DT> <DD> <DL> <DIV> <DT><I>Process_Description:</I></DT> <PRE ID="original">Miscellaneous updates (March through August 2011)</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DT><I>Process_Date:</I> August 2011</DT> </DL> </DD> </DL> </DD> </DL> </DD> </DL> <A HREF="#Top">Back to Top</A> <A name="Spatial_Data_Organization_Information"><HR /></A> <DL> <DT><I>Spatial_Data_Organization_Information:</I></DT> <DD> <DL> <DT><I>Direct_Spatial_Reference_Method:</I> Vector</DT> <DT><I>Point_and_Vector_Object_Information:</I></DT> <DD> <DL> <DT><I>SDTS_Terms_Description:</I></DT> <DD> <DL> <DT><I>SDTS_Point_and_Vector_Object_Type:</I> G-polygon</DT> <DT><I>Point_and_Vector_Object_Count:</I> 109307</DT> </DL> </DD> </DL> </DD> </DL> </DD> </DL> <A HREF="#Top">Back to Top</A> <A name="Spatial_Reference_Information"><HR /></A> <DL> <DT><I>Spatial_Reference_Information:</I></DT> <DD> <DL> <DT><I>Horizontal_Coordinate_System_Definition:</I></DT> <DD> <DL> <DT><I>Planar:</I></DT> <DD> <DL> <DT><I>Map_Projection:</I></DT> <DD> <DL> <DT><I>Map_Projection_Name:</I> Transverse Mercator</DT> <DT><I>Transverse_Mercator:</I></DT> <DD> <DL> <DT><I>Scale_Factor_at_Central_Meridian:</I> 0.999600</DT> <DT><I>Longitude_of_Central_Meridian:</I> -81.000000</DT> <DT><I>Latitude_of_Projection_Origin:</I> 0.000000</DT> <DT><I>False_Easting:</I> 500000.000000</DT> <DT><I>False_Northing:</I> 0.000000</DT> </DL> </DD> </DL> </DD> <DT><I>Planar_Coordinate_Information:</I></DT> <DD> <DL> <DT><I>Planar_Coordinate_Encoding_Method:</I> coordinate pair</DT> <DT><I>Coordinate_Representation:</I></DT> <DD> <DL> <DT><I>Abscissa_Resolution:</I> 0.000000</DT> <DT><I>Ordinate_Resolution:</I> 0.000000</DT> </DL> </DD> <DT><I>Planar_Distance_Units:</I> meters</DT> </DL> </DD> </DL> </DD> <DT><I>Geodetic_Model:</I></DT> <DD> <DL> <DT><I>Horizontal_Datum_Name:</I> D_North_American_1983_HARN</DT> <DT><I>Ellipsoid_Name:</I> Geodetic Reference System 80</DT> <DT><I>Semi-major_Axis:</I> 6378137.000000</DT> <DT><I>Denominator_of_Flattening_Ratio:</I> 298.257222</DT> </DL> </DD> </DL> </DD> <DT><I>Vertical_Coordinate_System_Definition:</I></DT> <DD> <DL> <DT><I>Altitude_System_Definition:</I></DT> <DD> <DL> <DT><I>Altitude_Resolution:</I> 1.000000</DT> <DT><I>Altitude_Encoding_Method:</I> Explicit elevation coordinate included with horizontal coordinates</DT> </DL> </DD> </DL> </DD> </DL> </DD> </DL> <A HREF="#Top">Back to Top</A> <A name="Entity_and_Attribute_Information"><HR /></A> <DL> <DT><I>Entity_and_Attribute_Information:</I></DT> <DD> <DL> <DT><I>Detailed_Description:</I></DT> <DD> <DL> <DT><I>Entity_Type:</I></DT> <DD> <DL> <DT><I>Entity_Type_Label:</I> Waterbody_SJRWMD24k</DT> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> <DT><I>Attribute_Label:</I> COMMENTS</DT> <DIV> <DT><I>Attribute_Definition:</I></DT> <PRE ID="original">Comments.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> <DT><I>Attribute_Label:</I> FID</DT> <DIV> <DT><I>Attribute_Definition:</I></DT> <PRE ID="original">Internal feature number.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DIV> <DT><I>Attribute_Definition_Source:</I></DT> <PRE ID="original">ESRI</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DT><I>Attribute_Domain_Values:</I></DT> <DD> <DL> <DT><I>Unrepresentable_Domain:</I></DT> <DD>Sequential unique whole numbers that are automatically generated.</DD> </DL> </DD> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> <DT><I>Attribute_Label:</I> SHAPE</DT> <DIV> <DT><I>Attribute_Definition:</I></DT> <PRE ID="original">Feature geometry.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DIV> <DT><I>Attribute_Definition_Source:</I></DT> <PRE ID="original">ESRI</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DT><I>Attribute_Domain_Values:</I></DT> <DD> <DL> <DT><I>Unrepresentable_Domain:</I></DT> <DD>Coordinates defining the features.</DD> </DL> </DD> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> <DT><I>Attribute_Label:</I> NAME</DT> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> <DT><I>Attribute_Label:</I> HYDROID</DT> <DIV> <DT><I>Attribute_Definition:</I></DT> <PRE ID="original">A unique feature identifier in the Water Resources Geodatabase</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> <DT><I>Attribute_Label:</I> HYDROCODE</DT> <DIV> <DT><I>Attribute_Definition:</I></DT> <PRE ID="original">A permanent public identifier of the feature in the Water Resources Geodatabase; it is used to acquire information about the feature from information systems external to the geodatabase. It is equivalent to HydroID + 2 million.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> <DT><I>Attribute_Label:</I> ALTERNATE_</DT> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> <DT><I>Attribute_Label:</I> AREASQKM</DT> <DIV> <DT><I>Attribute_Definition:</I></DT> <PRE ID="original">Waterbody area in square kilometers.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DIV> <DT><I>Attribute_Definition_Source:</I></DT> <PRE ID="original">A trigger based on the SHAPE.AREA field is used to update this field automatically any time a WaterBody polygon is modified. This trigger is setup on the "adds" table of the feature class. create or replace trigger giswrgdb_stage.a8491_t1 before insert on a8491 for each row begin :new.areasqkm := :new.shape.area/1000000; end; /</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> <DT><I>Attribute_Label:</I> NHDREACHCO</DT> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> <DT><I>Attribute_Label:</I> JUNCTIONID</DT> <DIV> <DT><I>Attribute_Definition:</I></DT> <PRE ID="original">HydroID of the related HydroJunction representing the Waterbody centroid.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> <DT><I>Attribute_Label:</I> NHDELEVATI</DT> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> <DT><I>Attribute_Label:</I> NHDCOMID</DT> <DIV> <DT><I>Attribute_Definition:</I></DT> <PRE ID="original">NHDComID of the Waterbody.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> <DT><I>Attribute_Label:</I> NHDFTYPE</DT> <DIV> <DT><I>Attribute_Definition:</I></DT> <PRE ID="original">A numeric value that encodes the type for the feature. It is a three-digit code. See Entity and Attribute Overview for a list.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DT><I>Attribute_Domain_Values:</I></DT> <DD> <DL> <DT><I>Enumerated_Domain:</I></DT> <DD> <DL> <DT><I>Enumerated_Domain_Value:</I> 334</DT> <DIV> <DT><I>Enumerated_Domain_Value_Definition:</I></DT> <PRE ID="original">Connector</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> <DT><I>Enumerated_Domain:</I></DT> <DD> <DL> <DT><I>Enumerated_Domain_Value:</I> 336</DT> <DIV> <DT><I>Enumerated_Domain_Value_Definition:</I></DT> <PRE ID="original">CanalDitch</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> <DT><I>Enumerated_Domain:</I></DT> <DD> <DL> <DT><I>Enumerated_Domain_Value:</I> 390</DT> <DIV> <DT><I>Enumerated_Domain_Value_Definition:</I></DT> <PRE ID="original">LakePond</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> <DT><I>Enumerated_Domain:</I></DT> <DD> <DL> <DT><I>Enumerated_Domain_Value:</I> 428</DT> <DIV> <DT><I>Enumerated_Domain_Value_Definition:</I></DT> <PRE ID="original">Pipeline</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> <DT><I>Enumerated_Domain:</I></DT> <DD> <DL> <DT><I>Enumerated_Domain_Value:</I> 436</DT> <DIV> <DT><I>Enumerated_Domain_Value_Definition:</I></DT> <PRE ID="original">Reservoir</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> <DT><I>Enumerated_Domain:</I></DT> <DD> <DL> <DT><I>Enumerated_Domain_Value:</I> 460</DT> <DIV> <DT><I>Enumerated_Domain_Value_Definition:</I></DT> <PRE ID="original">StreamRiver</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> <DT><I>Enumerated_Domain:</I></DT> <DD> <DL> <DT><I>Enumerated_Domain_Value:</I> 466</DT> <DIV> <DT><I>Enumerated_Domain_Value_Definition:</I></DT> <PRE ID="original">SwampMarsh</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> <DT><I>Enumerated_Domain:</I></DT> <DD> <DL> <DT><I>Enumerated_Domain_Value:</I> 493</DT> <DIV> <DT><I>Enumerated_Domain_Value_Definition:</I></DT> <PRE ID="original">Estuary</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> <DT><I>Enumerated_Domain:</I></DT> <DD> <DL> <DT><I>Enumerated_Domain_Value:</I> 558</DT> <DIV> <DT><I>Enumerated_Domain_Value_Definition:</I></DT> <PRE ID="original">Artificial Path</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> <DT><I>Enumerated_Domain:</I></DT> <DD> <DL> <DT><I>Enumerated_Domain_Value:</I> 566</DT> <DIV> <DT><I>Enumerated_Domain_Value_Definition:</I></DT> <PRE ID="original">Coastline</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> </DL> </DD> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> <DT><I>Attribute_Label:</I> EDIT_DATE</DT> <DIV> <DT><I>Attribute_Definition:</I></DT> <PRE ID="original">Date the feature was revised, whether spatially or attributes. Automatically populated using an Oracle trigger.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DIV> <DT><I>Attribute_Definition_Source:</I></DT> <PRE ID="original">A trigger is used to update this field automatically with the current system time any time a Waterbody polygon is modified. This trigger is setup on the "adds" table of the feature class. create or replace trigger giswrgdb_stage.a8491_t2 before insert on a8491 for each row begin select sysdate into :new.edit_date from dual; end; /</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> <DT><I>Attribute_Label:</I> SHAPE_AREA</DT> <DIV> <DT><I>Attribute_Definition:</I></DT> <PRE ID="original">Area of feature in internal units squared.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DIV> <DT><I>Attribute_Definition_Source:</I></DT> <PRE ID="original">ESRI</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DT><I>Attribute_Domain_Values:</I></DT> <DD> <DL> <DT><I>Unrepresentable_Domain:</I></DT> <DD>Positive real numbers that are automatically generated.</DD> </DL> </DD> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> <DT><I>Attribute_Label:</I> SHAPE_LEN</DT> </DL> </DD> </DL> </DD> <DT><I>Detailed_Description:</I></DT> <DD> <DL> <DT><I>Entity_Type:</I></DT> <DD> <DL> <DT><I>Entity_Type_Label:</I> GISWRGDB_STAGE.HydroJunctionHasWaterbody</DT> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> </DL> </DD> <DT><I>Attribute:</I></DT> <DD> <DL> </DL> </DD> </DL> </DD> <DT><I>Overview_Description:</I></DT> <DD> <DL> <DIV> <DT><I>Entity_and_Attribute_Overview:</I></DT> <PRE ID="original">NHDFType (Domain)- A numeric value that encodes the type for the feature. Values are: 334 Connector 336 CanalDitch 361 Playa 378 Ice Mass 390 LakePond 428 Pipeline 436 Reservoir 460 StreamRiver 466 SwampMarsh 493 Estuary 558 Artificial Path 566 Coastline</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> </DL> </DD> </DL> </DD> </DL> <A HREF="#Top">Back to Top</A> <A NAME="461862208"> <HR /> </A> <DL> <DT><I>Distribution_Information:</I> </DT> <DD> <DL> <DT><I>Resource_Description:</I> Downloadable Data</DT> <DIV> <DT><I>Distribution_Liability:</I></DT> <PRE ID="original">The St. Johns River Water Management District prepares and uses information for its own purposes and this information may not be suitable for other purposes. This information is provided "as is". Further documentation of this data can be obtained by contacting: St. Johns River Water Management District, Division of Integrated Application Systems, Post Office Box 1429, Palatka, Florida, 32178-1429, (386) 329-4500.</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DT><I>Standard_Order_Process:</I></DT> <DD> <DL> <DT><I>Digital_Form:</I></DT> <DD> <DL> <DT><I>Digital_Transfer_Information:</I></DT> <DD> <DL> <DIV> <DT><I>Format_Specification:</I></DT> <PRE ID="original">ESRI personal geodatabase</PRE> <SCRIPT>fix(original)</SCRIPT> </DIV> <DT><I>Transfer_Size:</I> 81.959</DT> </DL> </DD> <DT><I>Digital_Transfer_Option:</I></DT> <DD> <DL> <DT><I>Online_Option:</I></DT> <DD> <DL> <DT><I>Computer_Contact_Information:</I></DT> <DD> <DL> <DT><I>Network_Address:</I></DT> <DD> <DL> <DT><I>Network_Resource_Name:</I> <A TARGET="viewer" HREF="http://floridaswater.com"> floridaswater.com</A> </DT> </DL> </DD> </DL> </DD> <DT><I>Access_Instructions:</I></DT> <DD>search for GIS Data Download page</DD> </DL> </DD> </DL> </DD> </DL> </DD> <DT><I>Fees:</I> None</DT> </DL> </DD> </DL> </DD> </DL> <A HREF="#Top">Back to Top</A> <A name="Metadata_Reference_Information"><HR /></A> <DL> <DT><I>Metadata_Reference_Information:</I></DT> <DD> <DL> <DT><I>Metadata_Date:</I> 20110826</DT> <DT><I>Metadata_Contact:</I></DT> <DD> <DL> <DT><I>Contact_Information:</I></DT> <DD> <DL> <DT><I>Contact_Organization_Primary:</I></DT> <DD> <DL> <DT><I>Contact_Organization:</I> REQUIRED: The organization responsible for the metadata information.</DT> <DT><I>Contact_Person:</I> REQUIRED: The person responsible for the metadata information.</DT> </DL> </DD> <DT><I>Contact_Address:</I></DT> <DD> <DL> <DT><I>Address_Type:</I> REQUIRED: The mailing and/or physical address for the organization or individual.</DT> <DT><I>City:</I> REQUIRED: The city of the address.</DT> <DT><I>State_or_Province:</I> REQUIRED: The state or province of the address.</DT> <DT><I>Postal_Code:</I> REQUIRED: The ZIP or other postal code of the address.</DT> </DL> </DD> <DT><I>Contact_Voice_Telephone:</I> REQUIRED: The telephone number by which individuals can speak to the organization or individual.</DT> </DL> </DD> </DL> </DD> <DT><I>Metadata_Standard_Name:</I> FGDC Content Standards for Digital Geospatial Metadata</DT> <DT><I>Metadata_Standard_Version:</I> FGDC-STD-001-1998</DT> <DT><I>Metadata_Time_Convention:</I> local time</DT> <DT><I>Metadata_Extensions:</I></DT> <DD> <DL> <DT><I>Online_Linkage:</I> <A TARGET="viewer" HREF="http://www.esri.com/metadata/esriprof80.html"> http://www.esri.com/metadata/esriprof80.html</A> </DT> <DT><I>Profile_Name:</I> ESRI Metadata Profile</DT> </DL> </DD> </DL> </DD> </DL> <A HREF="#Top">Back to Top</A> </BODY> </HTML>