St. John's River Water Management District unknown 20010000 SHAPE St. John's River Water Management District http://sjr.state.fl.us/index.html This dataset contains the locations of various springs occuring in the St. John's River Water Management District. 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. unknown ground condition Complete Irregular -82.363786 -81.082887 30.443728 28.556818 None geology ISO 19115 Topic Category inlandWaters geoscientificInformation None St. John's River Florida Spring locations None 1990's None 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 Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595 St. John's River Water Management District unknown Map Relied on the integrity of the attribute information within the original data layer. 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." 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." St. John's River Water Management District unknown Map 24 None unknown ground condition SJRWMD Data representing springs within the St. John's River Water Management District 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 unknown Vector Entity point 51 NAD 1983 HARN Florida GDL Albers 24.0 31.5 -84.0 24.0 400000.0 0.0 coordinate pair 0.0001 0.0001 meter D North American 1983 HARN GRS 1980 6378137.0 298.257222101 DATABASE FILE Database File None OBJECTID Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. ETAT_SJSPGS_AREA PERIMETER SJSPGS_ SJSPGS_ID GIS_ID NAME Spring name Same Unknown FIPS FIPS County code Same Unknown CFS Average spring discharge in cubic feet per second FDEP record Unknown PU Planning Unit Same Unknown COUNTY County in which the spring is located Same Unknown MGD Million of Gallons Per Day - flow rate (see NOTES for variation) FDEP record Unknown LATITUDE Latitude location of spring Same Unknown LONGITUDE Longitude location of spring Same Unknown PLAN_UNIT Planning Unit Same Unknown PU_ID NOTES Notes Same B MGD value in Units of Gallons per minute Same C Springs cited in Tibbals, C.H. 1990 Hydrology of the Floridan Aquifer System in East-Central Florida; discharge averaged from Tibbals and USGS Same D Springs identified solely from quad sheets Same E 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. Same F Data from the USGS Same G Lat and long data from GeoTrans Inc., Wekiva River Basin Modeling Study, May 1991 Same H Lat and long from the USGS Same I Lat and long digitized from quad Same J 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. Same K probably less than a few CFS - Rick Speckler, USGS Same L rock aquifer or Upper Floridan mixing w/surficial Same M surficial Same N pseudospring Same Unknown DESCRIPT Based on NAME item Same Unknown AUTOID SHAPE Feature geometry. ESRI Coordinates defining the features. FLORIDA GEOGRAPHIC DATA LIBRARY Operator physical

431 Architecture Building PO Box 115706

Gainesville Florida 32611-5706 (352) 3920997, Operator http://www.fgdl.org/fgdldocs/document/techsupp.htm 24 Hours / Day Please visit the web site, http://www.fgdl.org, for all questions or concerns. 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. 20200303 Operator physical

P.O. Box 1429

Palatka FL 32178-1429 (904) 329-4500 FGDC Content Standard for Digital Geospatial Metadata FGDC-STD-001-1998 local time