St. Johns River Water Management District Waterbody

Metadata also available as

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator: St. Johns River Water Management District.
Publication_Date: August 2012
Title: St. Johns River Water Management District Waterbody
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Palatka, Florida
Publisher: St. Johns River Water Management District
Online_Linkage: <http://floridaswater.com/gisdevelopment/docs/themes.html>
Description:
Abstract:
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 2012.
Purpose:
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.
Supplemental_Information:
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.
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date:
REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.
Currentness_Reference: Publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: Irregular
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -82.607490
East_Bounding_Coordinate: -80.110277
North_Bounding_Coordinate: 31.035362
South_Bounding_Coordinate: 27.119083
Keywords:
Theme:
Theme_Keyword_Thesaurus: SJRWMD-GIS Metadata Thesaurus
Theme_Keyword: Arc Hydro
Theme_Keyword: Water
Theme_Keyword: Waterbody
Theme_Keyword: Area
Theme_Keyword: Hydrography
Theme_Keyword: inland Waters
Theme_Keyword: Waterbodies
Theme_Keyword: Rivers
Place:
Place_Keyword_Thesaurus: SJRWMD-GIS Metadata Thesaurus
Place_Keyword: Florida
Place_Keyword: St. Johns River Water Management District
Place_Keyword: Alachua County
Place_Keyword: Baker County
Place_Keyword: Bradford County
Place_Keyword: Brevard County
Place_Keyword: Clay County
Place_Keyword: Duval County
Place_Keyword: Flagler County
Place_Keyword: Indian River County
Place_Keyword: Lake County
Place_Keyword: Marion County
Place_Keyword: Nassau County
Place_Keyword: Okeechobee County
Place_Keyword: Orange County
Place_Keyword: Osceola County
Place_Keyword: Polk County
Place_Keyword: Putnam County
Place_Keyword: Seminole County
Place_Keyword: St. Johns County
Place_Keyword: Volusia County
Access_Constraints: None
Use_Constraints:
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.
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: St. Johns River Water Management District
Contact_Position: GIS Data Manager, Information Resources Department
Contact_Voice_Telephone: 386-329-4145
Contact_Electronic_Mail_Address: gis_support@sjrwmd.com
Browse_Graphic:
Browse_Graphic_File_Name:
X:\IR\GISProjects\WR_GDB\WorkDir\Doug\Artwork mxd\Waterbody Data Dictionary Illustration.jpg
Browse_Graphic_File_Type: JPEG
Data_Set_Credit:
This data set was compiled from a combination of USGS data sets, internal SJRWMD data sets, and SJRWMD staff knowledge.
Native_Data_Set_Environment:
Microsoft Windows 2000 Version 5.2 (Build 3790) Service Pack 2; ESRI ArcCatalog 9.3.1.1850

Data_Quality_Information:
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
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.
Lineage:
Process_Step:
Process_Description:
Created feature class from source NHD datasets (insert list here)
Process_Date: 200709
Process_Step:
Process_Description:
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.
Process_Date: 200801
Process_Step:
Process_Description:
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.
Process_Date: 200807
Process_Step:
Process_Description:
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.
Process_Date: 200901
Process_Step:
Process_Description:
Systematic feature update, Feb - Jun 2009: 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
Process_Date: 200906
Process_Step:
Process_Description:
Systematic feature update, Jul 2009 - Jan 2010: 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
Process_Date: 201001
Process_Step:
Process_Description:
Systematic feature update, Feb - Apr 2010: 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.
Process_Date: 201004
Process_Step:
Process_Description:
Systematic feature update, Apr - May 2010: 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.
Process_Date: 201005
Process_Step:
Process_Description:
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)
Process_Date: 20100804
Process_Step:
Process_Description:
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
Process_Date: 201008
Process_Step:
Process_Description:
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.
Process_Date: 201010
Process_Step:
Process_Description:
Over a period of several months, revisions focused on the coastal basins, primary subject matter expert: Whitney Green, Env. Sciences Division.
Process_Date: 201101
Process_Step:
Process_Description:
Final Intracoastal Waterway naming. To maintain consistency with USGS, all open waterbodies use USGS naming conventions complimented by a separate '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.
Process_Date: 201103
Process_Step:
Process_Description: Miscellaneous updates (March through August 2011)
Process_Date: 201108
Process_Step:
Process_Description:
Multiple edits working with Dave Clapp; focused in the Fellesmere WMA
Process_Date: August 2012

Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:

Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.000125
Ordinate_Resolution: 0.000125
Planar_Distance_Units: meters
Geodetic_Model:
Horizontal_Datum_Name: D_North_American_1983_HARN
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222
Vertical_Coordinate_System_Definition:
Altitude_System_Definition:
Altitude_Resolution: 1.000000
Altitude_Encoding_Method:
Explicit elevation coordinate included with horizontal coordinates

Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: GISWRGDB_STAGE.Waterbody
Attribute:
Attribute_Label: COMMENTS
Attribute_Definition: Comments.
Attribute:
Attribute_Label: SHAPE
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: SHAPE.AREA
Attribute:
Attribute_Label: SHAPE.LEN
Attribute:
Attribute_Label: NAME
Attribute:
Attribute_Label: ALTERNATE_NAME
Attribute:
Attribute_Label: OBJECTID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: HYDROID
Attribute_Definition: A unique feature identifier in the Water Resources Geodatabase
Attribute:
Attribute_Label: HYDROCODE
Attribute_Definition:
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.
Attribute:
Attribute_Label: AREASQKM
Attribute_Definition: Waterbody area in square kilometers.
Attribute_Definition_Source:
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; /
Attribute:
Attribute_Label: JUNCTIONID
Attribute_Definition:
HydroID of the related HydroJunction representing the Waterbody centroid.
Attribute:
Attribute_Label: NHDCOMID
Attribute_Definition: NHDComID of the Waterbody.
Attribute:
Attribute_Label: NHDREACHCODE
Attribute_Definition:
A numeric code that uniquely identifies a reach. This 14-digit code has 2 parts: the first 8 digits are the hydrologic unit code for the subbasin in which the reach is located; the last 6 digits are a sequentially ordered, arbitrarily assigned number.
Attribute:
Attribute_Label: NHDFTYPE
Attribute_Definition:
A numeric value that encodes the type for the feature. It is a three-digit code. See Entity and Attribute Overview for a list.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 334
Enumerated_Domain_Value_Definition: Connector
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 336
Enumerated_Domain_Value_Definition: CanalDitch
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 390
Enumerated_Domain_Value_Definition: LakePond
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 428
Enumerated_Domain_Value_Definition: Pipeline
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 436
Enumerated_Domain_Value_Definition: Reservoir
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 460
Enumerated_Domain_Value_Definition: StreamRiver
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 466
Enumerated_Domain_Value_Definition: SwampMarsh
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 493
Enumerated_Domain_Value_Definition: Estuary
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 558
Enumerated_Domain_Value_Definition: Artificial Path
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 566
Enumerated_Domain_Value_Definition: Coastline
Attribute:
Attribute_Label: EDIT_DATE
Attribute_Definition:
Date the feature was revised, whether spatially or attributes. Automatically populated using an Oracle trigger.
Attribute_Definition_Source:
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; /
Attribute:
Attribute_Label: NHDELEVATION
Attribute_Definition:
Elevation of the waterbody, in meters above the vertical datum. In the initial release of the NHD, only CanalDitch, LakePond, Reservoir, and StreamRiver in the waterbody theme can have elevations. Most of these features do not have a value for elevation, so -9998 (unspecified) is the most common value. For all other NHD feature types, the value for elevation is -9999 (not applicable).
Detailed_Description:
Entity_Type:
Entity_Type_Label: GISWRGDB_STAGE.HydroJunctionHasWaterbody
Overview_Description:
Entity_and_Attribute_Overview:
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

Distribution_Information:
Resource_Description: Downloadable Data
Distribution_Liability:
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.
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Format_Specification: ESRI personal geodatabase
Digital_Transfer_Option:
Online_Option:
Computer_Contact_Information:
Network_Address:
Network_Resource_Name: <http://floridaswater.com/gisdevelopment/docs/themes.html>
Fees: None

Metadata_Reference_Information:
Metadata_Date: 20110824
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:
REQUIRED: The organization responsible for the metadata information.
Contact_Person: REQUIRED: The person responsible for the metadata information.
Contact_Address:
Address_Type:
REQUIRED: The mailing and/or physical address for the organization or individual.
City: REQUIRED: The city of the address.
State_or_Province: REQUIRED: The state or province of the address.
Postal_Code: REQUIRED: The ZIP or other postal code of the address.
Contact_Voice_Telephone:
REQUIRED: The telephone number by which individuals can speak to the organization or individual.
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time

Generated by mp version 2.9.6 on Mon Aug 27 16:27:33 2012