ST. JOHN'S SPRINGS LOCATIONS

Metadata:

• Identification_Information
• Data_Quality_Information
• Spatial_Reference_Information
• Entity_and_Attribute_Information
• Distribution_Information
• Metadata_Reference_Information

Identification_Information:

Citation:

Citation_Information:

Originator: St. John's River Water Management District

Publication_Date: 19990300

Title: ST. JOHN'S SPRINGS LOCATIONS

Edition: 20010000

Geospatial_Data_Presentation_Form: SHAPE

Online_Linkage: <http://sjr.state.fl.us/index.html>

Description:

Abstract:

This dataset contains the locations of various springs occuring in the St. John's River Water Management District.

Purpose:

The mission of the St. Johns River Water Management District is to manage water resources to ensure their continued availability while maximizing both environmental and economic benefits.

Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: 19990300

Currentness_Reference: Ground Condition

Status:

Progress: Complete

Maintenance_and_Update_Frequency: Irregular

Spatial_Domain:

Bounding_Coordinates:

West_Bounding_Coordinate: -87.429040

East_Bounding_Coordinate: -79.872251

North_Bounding_Coordinate: 30.983191

South_Bounding_Coordinate: 24.492815

Keywords:

Theme:

Theme_Keyword_Thesaurus: NONE

Theme_Keyword: St. John's River Water Management District

Theme_Keyword: Springs

Theme_Keyword: Planning

Place:

Place_Keyword_Thesaurus: NONE

Place_Keyword: Florida

Place_Keyword: St. John's River

Place_Keyword: Spring locations

Temporal:

Temporal_Keyword_Thesaurus: NONE

Temporal_Keyword: 1990's

Access_Constraints: NONE

Use_Constraints:

The St. John's River Water Management District is the extent of this data set.

There are 51 springs in this coverage, all within the SJRWMD. The USGS Geographic Names Information System only lists 27 springs within the SJRWMD.

This data layer was originally created in 1993 by Division of Groundwater Programs staff. It is a static springs location data layer for general mapping purposes. September, 1996: This dataset was projected from Stateplane, East Zone, NAD 1927 to UTM, Zone 17, NAD 1983, 1990 Adjustment. March, 1999: This dataset was copied to double precision, and its processing tolerances were set to District standard values.

THE DATA INCLUDED IN THIS APPLICATION ARE BASED ON INTERPRETATION OF AVAILABLE INFORMATION AND SHOULD NOT BE CONSTRUED AS LEGALLY BINDING.

Scale is an important factor in data usage. Certain scale data sets are not suitable for some projects, analysis, or modeling purposes. Please be sure you are using the best available data.

1:24000 scale data sets are recommended for projects that are at the county level. 1:24000 data should NOT be used for high accuracy base mapping such as property parcel boundaries.

1:100000 scale data sets are recommended for projects that are at the multi-county or regional level. 1:250000 scale data sets are recommended for projects that are at the regional or state level or larger.

Vector datasets with no defined scale or accuracy should be considered suspect. Make sure you are familiar with your data before using it for projects or analyses. Every effort has been made to supply the user with data documentation. For additional information, see the References section and the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our web pages at: <http://www.geoplan.ufl.edu/education.html>

Native_Data_Set_Environment: For more information, visit: <http://sjr.state.fl.us/index.html>

Cross_Reference:

Citation_Information:

Originator: St. John's River Water Management District

Publication_Date: 19990300

Title: Unavailable

Geospatial_Data_Presentation_Form: Map

Data_Quality_Information:

Attribute_Accuracy:

Attribute_Accuracy_Report:

Relied on the integrity of the attribute information within the original data layer.

Logical_Consistency_Report:

Certain node/geometry and topology (GT)-polygon/chain relationships are collected or generated to satisfy topological requirements. Some of these requirements include: chains must begin and end at nodes, chains must connect to each other at nodes, chains do not extend through nodes, left and right GT-polygons are defined for each chain element and are consistent throughout the transfer, and the chains representing the limits of the file (neatline) are free of gaps. The neatline is generated by connecting the four corners of the digital file, as established during initialization of the digital file. All data outside the enclosed region are ignored and all data crossing these geographically straight lines are clipped at the neatline. (Exception: During the QA/QC process all data is examined and if errors are found and corrections are possible, then data is corrected accordingly. This process is documented in the Process_Step.) Data within a specified tolerance of the neatline are snapped to the neatline. Neatline straightening aligns the digitized edges of the digital data with the generated neatline, that is, with the longitude/latitude lines in geographic coordinates. All internal polygons are tested for closure. Certain attributes and/or entities, e.g. closure line, convey data quality information. When information to be encoded in the subfield is known to be not applicable (undefined, not relevant), then the subfield is valued by a string of "9s"; and when the information to be encoded is relevant but unknown (or missing), then the subfield is valued by a string of "9s."

Completeness_Report:

Certain node/geometry and topology (GT)-polygon/chain relationships are collected or generated to satisfy topological requirements. Some of these requirements include: chains must begin and end at nodes, chains must connect to each other at nodes, chains do not extend through nodes, left and right GT-polygons are defined for each chain element and are consistent throughout the transfer, and the chains representing the limits of the file (neatline) are free of gaps. The neatline is generated by connecting the four corners of the digital file, as established during initialization of the digital file. All data outside the enclosed region are ignored and all data crossing these geographically straight lines are clipped at the neatline. (Exception: During the QA/QC process all data is examined and if errors are found and corrections are possible, then data is corrected accordingly. This process is documented in the Process_Step.) Data within a specified tolerance of the neatline are snapped to the neatline. Neatline straightening aligns the digitized edges of the digital data with the generated neatline, that is, with the longitude/latitude lines in geographic coordinates. All internal polygons are tested for closure. Certain attributes and/or entities, e.g. closure line, convey data quality information. When information to be encoded in the subfield is known to be not applicable (undefined, not relevant), then the subfield is valued by a string of "9s"; and when the information to be encoded is relevant but unknown (or missing), then the subfield is valued by a string of "9s."

Lineage:

Source_Information:

Source_Citation:

Citation_Information:

Originator: St. John's River Water Management District

Publication_Date: 19990300

Title: Unavailable

Geospatial_Data_Presentation_Form: Map

Source_Scale_Denominator: 24,000

Type_of_Source_Media: Map

Source_Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: 19990300

Source_Currentness_Reference: Ground Condition

Source_Citation_Abbreviation: SJRWMD

Source_Contribution:

Data representing springs within the St. John's River Water Management District

Process_Step:

Process_Description:

The process step describes, in general, the process used in the production of data sets. The originating agencies created the original spatial coverage. GeoPlan, during the QA/QC process included the following aspects: (1) Reprojection into FGDL format (2) Tolerance set to FGDL standards (3) Added NOTECODE and DESCRIPT items

Process_Date: 20000000

Spatial_Reference_Information:

Horizontal_Coordinate_System_Definition:

Planar:

Map_Projection:

Map_Projection_Name: Albers Conical Equal Area

Albers_Conical_Equal_Area:

Standard_Parallel: 24.000000

Standard_Parallel: 31.500000

Longitude_of_Central_Meridian: -84.000000

Latitude_of_Projection_Origin: 24.000000

False_Easting: 400000.00000

False_Northing: 0.00000

Planar_Coordinate_Information:

Planar_Coordinate_Encoding_Method: Coordinate Pair

Coordinate_Representation:

Abscissa_Resolution: 0.000512

Ordinate_Resolution: 0.000512

Planar_Distance_Units: METERS

Geodetic_Model:

Horizontal_Datum_Name: D_North_American_1983_HARN

Ellipsoid_Name: GRS1980

Semi-major_Axis: 6378137.000000

Denominator_of_Flattening_Ratio: 298.257222

Entity_and_Attribute_Information:

Detailed_Description:

Entity_Type:

Entity_Type_Label: SJSPGS.DBF

Entity_Type_Definition: Database File

Entity_Type_Definition_Source: None

Attribute:

Attribute_Label: GIS-ID

Attribute_Definition: Numeric ID

Attribute_Definition_Source: SJRWMD record

Attribute_Domain_Values:

Unrepresentable_Domain: Unknown

Attribute:

Attribute_Label: NAME

Attribute_Definition: Spring name

Attribute_Definition_Source: Same

Attribute_Domain_Values:

Unrepresentable_Domain: Unknown

Attribute:

Attribute_Label: FIPS

Attribute_Definition: FIPS County code

Attribute_Definition_Source: Same

Attribute_Domain_Values:

Unrepresentable_Domain: Unknown

Attribute:

Attribute_Label: CFS

Attribute_Definition: Average spring discharge in cubic feet per second

Attribute_Definition_Source: FDEP record

Attribute_Domain_Values:

Unrepresentable_Domain: Unknown

Attribute:

Attribute_Label: PU

Attribute_Definition: Planning Unit

Attribute_Definition_Source: Same

Attribute_Domain_Values:

Unrepresentable_Domain: Unknown

Attribute:

Attribute_Label: COUNTY

Attribute_Definition: County in which the spring is located

Attribute_Definition_Source: Same

Attribute_Domain_Values:

Unrepresentable_Domain: Unknown

Attribute:

Attribute_Label: MGD

Attribute_Definition:

Million of Gallons Per Day - flow rate (see NOTES for variation)

Attribute_Definition_Source: FDEP record

Attribute_Domain_Values:

Unrepresentable_Domain: Unknown

Attribute:

Attribute_Label: LATITUDE

Attribute_Definition: Latitude location of spring

Attribute_Definition_Source: Same

Attribute_Domain_Values:

Unrepresentable_Domain: Unknown

Attribute:

Attribute_Label: LONGITUDE

Attribute_Definition: Longitude location of spring

Attribute_Definition_Source: Same

Attribute_Domain_Values:

Unrepresentable_Domain: Unknown

Attribute:

Attribute_Label: PLAN_UNIT

Attribute_Definition: Planning Unit

Attribute_Definition_Source: Same

Attribute_Domain_Values:

Unrepresentable_Domain: Unknown

Attribute:

Attribute_Label: PU-ID

Attribute_Definition: Planning Unit basin ID

Attribute_Definition_Source: FDEP record

Attribute_Domain_Values:

Unrepresentable_Domain: Unknown

Attribute:

Attribute_Label: NOTES

Attribute_Definition: Notes

Attribute_Definition_Source: Same

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: B

Enumerated_Domain_Value_Definition: MGD value in Units of Gallons per minute

Enumerated_Domain_Value_Definition_Source: Same

Enumerated_Domain:

Enumerated_Domain_Value: C

Enumerated_Domain_Value_Definition:

Springs cited in Tibbals, C.H. 1990 Hydrology of the Floridan Aquifer System in East-Central Florida; discharge averaged from Tibbals and USGS

Enumerated_Domain_Value_Definition_Source: Same

Enumerated_Domain:

Enumerated_Domain_Value: D

Enumerated_Domain_Value_Definition: Springs identified solely from quad sheets

Enumerated_Domain_Value_Definition_Source: Same

Enumerated_Domain:

Enumerated_Domain_Value: E

Enumerated_Domain_Value_Definition:

Discharge and lat-long information came from the SJRWMD, TDS Average Spring Discharge Measurments USGS vs SJRWMD. The discharge is the average value of the USGS and SJRWMD data as of 10/14/91.

Enumerated_Domain_Value_Definition_Source: Same

Enumerated_Domain:

Enumerated_Domain_Value: F

Enumerated_Domain_Value_Definition: Data from the USGS

Enumerated_Domain_Value_Definition_Source: Same

Enumerated_Domain:

Enumerated_Domain_Value: G

Enumerated_Domain_Value_Definition:

Lat and long data from GeoTrans Inc., Wekiva River Basin Modeling Study, May 1991

Enumerated_Domain_Value_Definition_Source: Same

Enumerated_Domain:

Enumerated_Domain_Value: H

Enumerated_Domain_Value_Definition: Lat and long from the USGS

Enumerated_Domain_Value_Definition_Source: Same

Enumerated_Domain:

Enumerated_Domain_Value: I

Enumerated_Domain_Value_Definition: Lat and long digitized from quad

Enumerated_Domain_Value_Definition_Source: Same

Enumerated_Domain:

Enumerated_Domain_Value: J

Enumerated_Domain_Value_Definition:

USGS Altamonte has a discharge reading of 10.6 CFS in 1935 - it is also noted with this data the spring backs up when the river gets high and the flow has been known to reverse.

Enumerated_Domain_Value_Definition_Source: Same

Enumerated_Domain:

Enumerated_Domain_Value: K

Enumerated_Domain_Value_Definition: probably less than a few CFS - Rick Speckler, USGS

Enumerated_Domain_Value_Definition_Source: Same

Enumerated_Domain:

Enumerated_Domain_Value: L

Enumerated_Domain_Value_Definition: rock aquifer or Upper Floridan mixing w/surficial

Enumerated_Domain_Value_Definition_Source: Same

Enumerated_Domain:

Enumerated_Domain_Value: M

Enumerated_Domain_Value_Definition: surficial

Enumerated_Domain_Value_Definition_Source: Same

Enumerated_Domain:

Enumerated_Domain_Value: N

Enumerated_Domain_Value_Definition: pseudospring

Enumerated_Domain_Value_Definition_Source: Same

Unrepresentable_Domain: Unknown

Attribute:

Attribute_Label: DESCRIPT

Attribute_Definition: Based on NAME item

Attribute_Definition_Source: Same

Attribute_Domain_Values:

Unrepresentable_Domain: Unknown

Distribution_Information:

Distributor:

Contact_Information:

Contact_Person_Primary:

Contact_Person: Operator

Contact_Organization: FLORIDA GEOGRAPHIC DATA LIBRARY

Contact_Address:

Address_Type: Physical

Address:

431 Architecture Building PO Box 115706

City: Gainesville

State_or_Province: Florida

Postal_Code: 32611-5706

Contact_Voice_Telephone: (352) 3920997, Operator

Contact_Electronic_Mail_Address: <http://www.fgdl.org/fgdldocs/document/techsupp.htm>

Hours_of_Service: 24 Hours / Day

Contact_Instructions:

Please visit the web site, <http://www.fgdl.org>, for all questions or concerns.

Distribution_Liability:

Florida Geographic Data Library is a product of the University of Florida GeoPlan Center with support from the Florida Department of Transportation and the Florida Department of Environmental Protection. THE FGDL DATA AS PROVIDED BY CONTRIBUTING ORGANIZATIONS AND ANY PROGRAMMING SOFTWARE CREATED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER (COLLECTIVELY THE "MATERIALS") ARE COPYRIGHTED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER FOR THE FGDL CONTRIBUTING AGENCIES AND ORGANIZATIONS (THE "DATA PROVIDERS"). DO NOT REPRODUCE, REDISTRIBUTE OR RESELL THE MATERIALS, OR PROVIDE THE MATERIALS FOR FREE TO CUSTOMERS OR CLIENTS, OR PLACE THE MATERIALS FOR DOWNLOAD ON A WEBSITE. ADDITIONALLY, WHEN USING FGDL DATA OR SOFTWARE IN PROJECTS, MAPS, ETC.; YOU AGREE TO ACKNOWLEDGE THE FGDL AS A DATA SOURCE. THE MATERIALS ARE PROVIDED "AS IS". THE UNIVERSITY OF FLORIDA GEOPLAN CENTER MAKES NO REPRESENTATIONS OR WARRANTIES ABOUT THE QUALITY OR SUITABILITY OF THE MATERIALS, EITHER EXPRESSLY OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THE UNIVERSITY OF FLORIDA GEOPLAN CENTER MAKES NO WARRANTIES, GUARANTIES OR REPRESENTATIONS AS TO THE TRUTH, ACCURACY OR COMPLETENESS OF THE DATA PROVIDED BY THE FGDL CONTRIBUTING ORGANIZATIONS. THE UNIVERSITY OF FLORIDA GEOPLAN CENTER SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED AS A RESULT OF USING, MODIFYING, CONTRIBUTING OR DISTRIBUTING THE MATERIALS.

Metadata_Reference_Information:

Metadata_Date: 2001

Metadata_Contact:

Contact_Information:

Contact_Person_Primary:

Contact_Person: Operator

Contact_Address:

Address_Type: Physical

Address: P.O. Box 1429

City: Palatka

State_or_Province: FL

Postal_Code: 32178-1429

Contact_Voice_Telephone: (904) 329-4500

Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata

Metadata_Standard_Version: FGDC-STD-001-1998