FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION
VERSION 2007

TITLE: OUTSTANDING FLORIDA WATERS

Geodataset Name:       OFW_OTHER_JUL08
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Polygon
Feature Count:         3735
GENERAL DESCRIPTION:
Outstanding Florida Waters, (OFW), are waters designated worthy of special protection because of their natural attributes. This special designation is applied to certain waters, and is intended to protect and maintain existing acceptable quality standards. The OFW layer is a GIS spatial dataset that represents the OFW boundaries throughout the state of Florida. This project involves adding new data to and modifying existing data within the OFW data layer for better accuracy and representation. Boundaries for Outstanding Florida Waters (OFWs) as described in Section 62-302.700, F.A.C. This layer includes all three types of OFWs: OFW Aquatic Preserves, Special OFWs, and Other OFWs.
DATA SOURCE(S):                    Florida Department of Environmental Protection
SCALE OF ORIGINAL SOURCE MAPS:     24000
DATE OF AUTOMATION OF SOURCE:      19960101
GEODATASET EXTENT:                 State of Florida

FEATURE ATTRIBUTE TABLES:

Datafile Name: OFW_OTHER_JUL08.DBF
ITEM NAME WIDTH TYPE
OBJECTID
4 OID
TYPE
16 String
NAME
60 String
ALT_NAME
60 String
RULE_ID
16 String
GIS_ID
11 Number
NOTES
254 String
DESCRIPT
60 String
FGDLAQDATE
8 Date
SHAPE
4 Geometry
AUTOID
4 Integer
SHAPE.AREA
0 Double
SHAPE.LEN
0 Double

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item
Item Description
OBJECTID Internal feature number.

TYPE Type designation of waterway

NAME Name of waterway

ALT_NAME Alternative name of waterway

RULE_ID Undefined by source

GIS_ID Undefined by source

NOTES Notes on waterway

DESCRIPT FGDL added field based on NAME

FGDLAQDATE FGDL added field based on date downloaded from source

SHAPE Feature geometry.

AUTOID Unique ID added by GeoPlan

SHAPE.AREA Area in meters

SHAPE.LEN Perimeter in meters

STANDARD COGO PROCEDURES used in creating original source information
 
REVISED 5/1/95 
 
1 NEW DRAWING 
 
	1.1  Start a new AutoCad/COGO drawing using the CGPROTO.DWG prototype 
drawing found in 
		           F:\GROUPS\PARKS\CGPARCEL 
	1.2  File the new drawing under the park ID number plus "CG" 
		1.2.1 Example: SOOOO1CG.dwg for Addison Blockhouse S.H.S. 
		1.2.2  All park drawings shall be filed in 
		           F:\GROUPS\PARKS\CGPARCEL	 
	1.3  Attach, as an Xref, the USGS quad(s), if available. 
		1.3.1  All USGS quads may be found in 
		           F:\GROUPS\PARKS\QUADS 
		1.3.2  The USGS quads are for reference only and shall not be 
modified. 
 
2 SOURCES FOR BOUNDARY DEVELOPMENT 
	2.1     Electronic survey file:  Parcel deeds from 1991 to present may 
have an electronic survey file.  Research should be done to locate any 
electronic files from Survey and.  Mapping.  The electronic survey files need 
to be verified per our deeds to be certain all out easements and out parcels 
are represented.  Also, one survey may encompass several deeds and will need to 
be broken out deed per deed. 
	2.2    Deed descriptions :  The parcel boundaries will be generated 
from the legal descriptions on the deeds. 
	2.3    USGS 1-24,000 electronic quads:  Certain information on the 
electronic quads (section lines, water meander lines and roadways) may be used  
if and only if better information, such as bearing and distance calls and 
electronic survey information, is not available  
	2.4    USGS 1-24,000 paper quads:  Hardcopies of USGS quadrangle maps 
compliment the electronic quads and provide a good visual reference.  In 
addition, if the electronic quad is not available, section lines, water meander 
lines and  roadways may be digitized from the paper quads as a last resort. 
	2.5    TRW/REDI  tax maps:  Tax maps are available for some counties 
and provide information on tax parcels, government lots and roadways. 
	2.6    Additional sources: 
		2.6.1  Government survey plats show government lot boundaries. 
		2.6.2  Water line surveys are available for some coastal water 
lines and river meander lines. 
		2.6.3  Base maps for the parks may help to clarify confusing 
boundaries but are to be used for visual reference only 
 
3 OBTAINING SOURCE INFORMATION 
	3.1  Electronic quads :  If the quad(s) you need is/are not on the QUAD 
directory, notify Kelley in writing requesting the specific quad(s) by quad 
number. 
		3.1.1 The quad number (s) for each park may be determined as 
follows: 
		1)  find the general park location using THE FLORIDA STATE PARK 
SYSTEM map, 
			2)  from the GMDNCC FLORIDA BASEMAP, select the USGS 
Quadrangle(s) corresponding to the paper quadrangle(s) in the COGO folder for 
that park, 
			3)  each quad has a four (4) digit number followed by 
the letter "N", "W",  or "E" associated with north, west and east zones, 
respectfully -- choose the zone which applies to all or most of the previously 
selected quad(s), 
			4) record the quad number (s) on parks COGO folder and 
COGO Boundary Development Sheet. 
		3.1.2  Record the request in your COGO notebook 
	3.2  Electronic survey:  If you need an electronic survey file, notify 
Kayle in writing.  Include the park name, county, Section, Township and Range, 
deed date, grantor and any other information you feel may be helpful. 
		3.2.1  Record the request in your COGO notebook.   
	3.3  TRW/REED tax maps:  Copies of tax maps may be obtained by 
notifying Todd in writing.  Include the county, Section, Township and Range 
with your request. 
		3.3.1 Record the request in your COGO notebook. 
	3.4  Deeds and official records:  For deeds and other count records, 
notify Todd in writing.  Include the county, O.R. book and page numbers and any 
other information you feel may be helpful. Make absolutely certain that the 
parcel  boundaries cannot be completed without this information before you 
request it. 
		3.4.1 Record the request in your COGO notebook.	 
	3.5  Additional information:  Should you require any other resources 
such as government survey plats or water line surveys, notify Todd in writing.  
Include the park name, county, Section, Township and Range and any other 
information you feel may be helpful. 
		3.5.1  Record the request in your COGO notebook. 
 
4  PARCEL BOUNDARY DEVELOPMENT For our purposes a parcel is defined as all that 
area,  upland or submerged, as described by a single deed. 
	4.1  From electronic survey:  If an electronic survey is used, the 
parcel boundary shall be WBLOCKed and INSERTed on the park drawing.  For an 
insertion point, use the POINT OF BEGINNING as specified on the electronic 
survey. 
	4.2  From legal descriptions:  Most parcel boundaries will be created 
from the legal deed descriptions.  These descriptions may provide bearing and 
distance calls or refer to quadrangle sections, manmade or natural features, 
government lots, tax parcels, or a combination thereof. 
		4.2.1 Bearing and distance calls are the most accurate of all 
the deed information and shall be used whenever available, even for water 
lines, section lines and roadways. 
		NOTE:   If a bearing and a distance are provided but the 
description also refers to a specific location (section line, roadway, water 
line, etc.)  and the location can be positively determined, follow the bearing 
to the specified location regardless of the distance. 
		4.2.2  When it is necessary to use information from an 
electronic quad,  verify the entities needed for your parcel boundary then 
duplicate them on your drawing file. 
		4.2.3. If REDI tax maps are used, dimensions may be scaled but 
verify that the scale you are using is correct and that  you can accurately 
locate the parcel boundaries on the electronic quad(s).  Also, parcel 
information may be digitized as a last resort. 
	4.3.  From other sources:  Only as a last resort and in the absence of 
more accurate information, other sources may be used to complete parcel 
boundaries.  However, the use of any sources not specified in this section 
requires Todd's approval. 
		4.3.1.  Also, record your request and Todd's decision in your 
COGO notebook. 
		4.3.2.  Todd will notify Kelley when other information is used. 
 
5 DRAWING REQUIREMENTS 
	5.1  Parcel boundaries:  The boundaries of each parcel shall meet the 
following requirements. 
		5.1.1  All parcel boundaries shall be on the B-PARCEL layer. 
		5.1.2. Individual parcel boundaries should close but do not 
need to be polylines. 
		5.1.3 All temporary lines used to create parcel boundaries 
should be removed. 
		5.1.4. Parcels should not overlap. Notify Todd if this occurs. 
		5.1.5.  When two parcels touch along one or more sides, only 
one (1) dividing line is necessary.  Double lines should be avoided.  
	5.2  Parcel numbers:  Each parcel shall be given a nine (9) digit 
identification number (####-#####) as follows. 
		5.2.1  The first four (4) digits correspond to the Unit I.D. 
Number for the park being developed. 
		5.2.2  The last five (5) digits are used to sequentially number 
the parcels in chronological order according to deed date where "-00001" refers 
to the oldest deed.  NOTE:  If a parcel is added later, chose the next 
available number regardless of deed date and do not renumber the parcels. 
		5.2.3  Clearly label each parcel on the drawing with its 
complete parcel number. 
		5.2.4  All parcel number labels and associated leader lines 
shall be on the B-PARTXT layer. 
		5.2.5 	Record each parcel number, grantor and deed date on the 
park's PARCEL IDENTIFICATION SHEET. 
		5.2.6	If a lease exists without a deed, use the lessor and 
lease date in place of the grantor and deed date and note it on the park's 
PARCEL IDENTIFICATION SHEET. 
		5.2.7	Example:  "0001-00001" would represent the parcel 
described in the oldest deed for Addison Blockhouse S.H.S. 
	5.3	Out parcels:  Out parcels are areas removed from a parcel 
according to the legal description and should have their own respective 
boundaries. 
		5.3.1   All out parcel boundaries shall be on the B-OUTL layer. 
		5.3.2	In addition to its own boundary, each out parcel shall 
have a parcel boundary on the B-PARCEL layer and a park boundary on the B-BNDL  
layer.  
		5.3.3	Clearly label all out parcels with the word "OUT".    
		5.3.4	All "OUT" labels and associated leader lines shall be 
on the B-OUTTXT  layer/  
		5.3.5	Out parcels will not be recorded on the PARCEL 
IDENTIFICATION SHEET. 
	5.4  Park boundary:  After all the parcel boundaries have been 
completed, create a separate polyline boundary for the entire park. 
	         5.4.1  If the park consists of several  non-adjoining pieces, 
each piece should have its own separate polyline boundary. 
	         5.4.2  All boundary lines shall be on the B-BNDL layer.
USER NOTES:
This data is provided 'as is'. GeoPlan relied on the integrity
of the original data layer's topology
This data is provided 'as is' by GeoPlan and is complete to our
knowledge.
GeoPlan relied on the integrity of the attribute information within
the original data.

The legislature of the  State of  Florida established a category of  
surface water features called "Outstanding Florida Waters" that are to be 
protected from  any degradation from their current water quality 
classification.  A description of the water features eligible for inclusion as 
an OFW and a list of  currently established OFWs is contained in Section 
62-302.700, F.A.C., (Attachment 4).  Additionally, "Waters" are defined in 
Section 403.031, F.S., as  "... rivers, lakes, streams, springs, impoundments, 
and wetlands ... including fresh, brackish, saline, tidal, surface, and 
underground waters."  Chapter 62-340, F.A.C.,  "Delineation of  the Landward  
Extent of Wetlands and Surface Waters" details the plants and soil types that 
indicate the existence of wetland or surface water, under authority granted in 
Section 373.421, F.S. 
 
Most of the OFWs are contained within the boundaries of publicly-owned 
lands managed for conservation and/or recreation so that the extent of the 
water features that are protected can be defined by the legal boundary of the 
park, recreation area, preserve, or other publicly-owned property.  Three 
categories of OFWs do not have boundaries so described:  1) the three river 
segments designated as wild and scenic under the Florida Scenic and Wild Rivers 
Program, federal Wild and Scenic Rivers Act and the Myakka River Wild and 
Scenic Designation and Preservation Act; 2) the 16 streams or lakes in the 
National  Forests, and 3) the 56 streams and lakes defined as Special Waters.  
 
As a portion of an Environmental Protection Agency Wetland Protection 
grant, a separate project to reduce the boundaries of the OFWs to a digital 
format was undertaken by the FDEP.  Some digital data existed and was compiled 
from many different source formats and scales.  These data were incorporated 
into a statewide coverage but because of the lack of documentation and concerns 
about accuracy, other approaches were investigated to improve portions of the 
data. 
 
Other divisions within the FDEP have felt the need to develop digital 
coverages for the State-owned or managed properties they oversee and are in the 
process of reducing the legal descriptions on deeds into a digital form by 
interpreting and transferring the legal description to a quad sheet or using  
one or another of the COGO (COordinate GeOmetry) systems.  These lands include 
the Aquatic Preserves and the State Park boundaries.  Where possible, to 
minimize duplication of effort, the Division of Environmental Permitting either 
acquired the boundaries already created for the Aquatic Preserves, or entered 
into a joint venture to create boundaries for the 145 lands managed by the 
Division of Parks and Recreation.

This data is provided 'as is' and its horizontal positional accuracy
has not been verified by GeoPlan

This data is provided 'as is' and its vertical positional accuracy
has not been verified by GeoPlan

THE DATA INCLUDED IN FGDL ARE 'AS IS' AND SHOULD NOT BE CONSTRUED
AS LEGALLY BINDING. 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.

A note about data scale: 

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

1:24000 scale datasets 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 datasets are recommended for projects that are at the
multi-county or regional level.
1:125000 scale datasets 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 analysis. 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 webpage at:
http://geoplan.ufl.edu/education.html

REFERENCES:


DATA LINEAGE SUMMARY:
OFW Aquatic Preserves Category:

Aquatic Preserve boundaries were created by the Florida Marine Research 
Institute (FMRI)/CAMRA.  We are using these boundaries to represent the OFWs 
that are also designated Aquatic Preserves 

Special OFW Category :

The streams and lakes that do not have defined legal boundaries were 
automated using methods other than transferring legal descriptions into a 
digital format.  Because of the interpretive nature of the boundaries for the 
Special Waters Category, we have avoided making any implication that this line 
represents the ordinary high water line that separates the State-owned lands 
from privately-owned lands by referring to this line as a fuzzy boundary or 
trip wire.  Final determinations of these boundaries will require on-site 
inspections or aerial photo-interpretations coupled with field verifications 
and will not be carried out for any of the streams and lakes designated as 
OFWs, in the short term.  These interpretive boundaries were designed to alert 
persons making land use decisions that on-site inspections or further 
investigations by qualified soils scientists or botanists may be necessary.  
These interpretive boundaries are necessary because if a proposed activity 
falls within or near an OFW boundary, different, more stringent permitting 
review standards are imposed on the permittee's application.   
 
The OFW Special Water boundary is based on the contour lines from the 
U.S. Geological  Survey 1:24000-scale quadrangle maps.  This boundary is 
labeled with the elevation of those contours that are most likely to meet the 
criteria of supporting obligate and facultative plants and hydric soils.  These 
elevations are 5 or 10 feet apart vertically, so that other information was 
used to modify the line.  Currently, the best additional information is a set 
of EOSAT satellite images from 1992.  The 1994 EOSAT imagery was also 
available, but because 1994 was an extremely wet year, the spectral reflectance 
values were judged less reliable. 
 
However, other indications that the area inside the Special Waters 
delineation line is likely to meet the rule's criteria are the swamp symbols on 
the quadrangle, the change in slope that is indicative of  the seepage line, or 
springs that indicate that the groundwater is near the surface at  that 
elevation.  Cultural features can also be helpful.  Roads often stop at wetted 
areas and buildings are usually (but not always) built above the elevation of 
the water feature's most frequent floods.  Similarly, railroads are usually 
built up high enough to stay dry.  This information is generally discernible on 
USGS 7.5 minute quadrangles. 

Other OFW Categories :

All other categories are taken from the Lands managed for Conservation 
created and compiled by GEOPLAN or have been created by us using descriptions 
from the Outstanding Florida Waters documentation.  Those boundaries created 
internally were scanned from published materials, registered and rectified with 
1:24,000 USGS Public Land Survey section corners.  Data was then extracted from 
USGS 1:24,000 hydrology layer and attributed.  For boundaries not completely 
represented by USGS 1:24,000 hydrology layer, arcs were digitized directly from 
the scanned material to complete the boundary. 
State Parks and Recreational Areas Category 

The COGO method has several advantages and disadvantages for use in 
producing a database for the OFWs.  It uses primary source material - the legal 
description on the deed.  Data created using this method should have validity 
within the legal system because it is from a source familiar to the courts.  
Other agencies are using the COGO system so it is a familiar process and 
product.  COGO methodology is appropriate in that it weds the new system for 
describing land ownership to the existing system.  Additionally, each parcel 
boundary will be maintained in a digital form and can be extracted from the 
official boundary as a parcel's status changes.  This data layer will also be 
maintained and updated by the stewards of all the state park boundaries data, 
so as the parcel boundaries change, the OFW boundaries will automatically be 
updated.  The downside is that COGO (or the survey data it automates) is labor 
intensive and requires extensive training and expertise to use.  Each legal 
description references source materials that may only be available locally or 
from the county appraiser's office, at a cost of travel and materials.  Each  
park boundary may have numerous parcels transferred to the state at different 
times and some parcel boundaries overlap. 
 
Legal descriptions were transferred to digital form using the COGO 
modules in  ESRI's ARC/INFO software on a UNIX platform DEC Alpha 3000 
workstation and Softdesk's ADDCAD Civil/Survey software on 486/90 DELL personal 
computers configured with 1 gigabyte storage memory, 32 megabytes of RAM, 17" 
VGA monitors and running DOS.  Both platforms are connected to HP-650C 
plotters.  See Standard COGO Procedures developed by the Division of Parks and 
Recreation.
Process Date: 1996

Librarian coverage transformed from NAD27 to HPGN using PROJECT command. Process Date: Spring 1997
Shapefile of this dataset was inserted into Spatial Database Engine. Process Date: Spring 1999
35 NULL and 305 'OUT PARCEL' records were removed at the request of Richard Butgereit and Kathleen Swanson of ERP. Process Date: October 2000
Layer recreated as one OFW layer from three separate OFW designation layers. Process Date: 12/18/02
OFW Edits Added Bear Creek State Recreation Area (Other OFW). Rule_ID 9c5 Added Passage Key (Special OFW). Rule_ID 9b22 Edited Myakka River State Park (Other OFW). Rule_ID 9c57 Edited Big Bend Seagrasses Aquatic Preserve (Aquatic Preserve) by removing the Keaton Beach exceptions. May need more editing. Made the following edits as well: 9)(h) Aquatic Preserves 18. Indian River Malabar to Vero Beach (additions) - except those portions of Sebastian Creek and Turkey Creek upstream of U.S. Highway 1. 42. Wekiva River Addition, except that portion of the St. Johns River between Interstate Highway 4 and the Wekiva River confluence. December 19, 2003 Rule ID 9i38 (GIS_ID 530): Weekiwachee Riverine System. Effective as of December 11, 2003. Added on 20031219 by RH for Janet Klemm. {Special OFW.} Rule ID 9i17 (GIS_ID 540): Lake Disston. Added on 20031219 by RH. {Special OFW.} Rule ID 9i14c (GIS_ID 500): Hillsborough River. Two wetland areas removed at request of Janet Klemm on 20031219. RH. Wetlands were removed from T26S, R19E, section 26 and 27 respectively. {Special OFW.} January 29, 2004 Rule ID 9b8 (GIS_ID 12): Egmont Key NWR. Changed "Name" field from Egmont Key (designation undetermined) to Egmont Key NWR for Janet Klemm. RH 20040129. {Other OFW} Rule ID 9b22 (GIS_ID 520): Passage Key. Changed "Type" from "Special" OFW to "Other" OFW for Janet. RH 20040129. {Other OFW}. April 8, 2004 Rule ID 9f43 (GIS_ID 550): Placid Lakes Highlands. Acquired boundary from FWCC Management Areas shapefile. Added 20040408. by RH for Janet Klemm. (Other OFW). April 28, 2004 Rule ID 9i40 (GIS_ID 560): Wiggins Pass Estuarine Area and the Cocohatchee River System. Added on 20040428 by RH as special request by Kim Jackson. She needed it for Janet Klemm's "OFW Economics" pilot project. Re-edited on April 29, 2004 using a map from Janet Klemm and 24K DRG's USGS Quad Maps. May 4, 2004 Rule ID 9f60 (GIS_ID 570): Three Lakes/Prairie Lakes. Added on 20040504 by RH. To create this shape, I used major river boundaries, state lands boundaries, PLS Boundaries, Cad Files from TLSDSL6 and hand digitizing. Rule ID 9f49 (GIS_ID 580): Saddle Blanket Lakes Scrub. Added on 20040504 by RH. Used State Lands and PLS Boundaries to make this. Only State Owned Property is included for the time being. March 30, 2005 Rule ID 9e58 (GIS_ID 590): Stoney-Lane (10-4-90). Added on 20050330 by RH. (Other OFW). April 19, 2005. Rule_ID 9e9 (GIS_ID 600): Nassau Valley State Reserve (12-1-82). Added on 20050419 by RH. Not all areas within boundary are OFW. Hand created by using ArcView 3.2 while using 1987 OFW Atlas page 182 and 24k DRG as guide. Confidence Level: Low. Strictly meant for representation. Not for legal purposes. (Other OFW). May 11, 2005. Rule_ID 9f31 (GIS_ID 610): Indian River North Beach (5-14-86). Added on 20050511 by RH. Indian River North Beach Complex and County Property in northern portion. Number 11 Corp and Sirk Tract in southern portion. Based on State Lands Records from DataMiner. Confidence level Medium. OFW Atlas 1987, page 214. (Other OFW). May 13, 2005. Rule_ID 9f41 (GIS_ID 620): North Beach (5-14-86). Also known as North Beach Additions. Added on 20050513 by RH. Edits based on State Lands Records from DataMiner, 24K DRG, 1999 DOQQ and OFW Atlas 1987, page 219. Confidence level Medium to Low. Boundaries directly on either side of Sheridan St. were hand created. (Other OFW). May 25, 2005. Rule_ID 9h19 (GIS_ID 231): Indian River - Vero Beach to Ft. Pierce Aquatic Preserve. Edited on 20050525 by RH at request of Janet Klemm. Added the portion of the Harbor Beach Channel waterward (eastward) of preconstruction mean high water line. Confidence Level Medium. Corresponded with Earl Pearson from the Office of Coastal and Aquatic Managed Areas. He edits the Aquatic Preserves layer. We need to have both OFW and Aquatic Preserves boundaries coincide so I sent him a jpeg and the shapefile that I edited. He said that my edits look the same as he planned to do, but that it will take some time to get his edit approved. Janet already approved mine, so I went ahead and updated the boundary and asked Earl to let me know when he gets his edits approved. (Aquatic Preserve OFW). June 20, 2005. Rule_ID 9i13 (GIS_ID 630): Florida Keys. Added on 20050620 by RH. Hand digitized. Used 24k DRG for Dade-Monroe boundary reference. Used Everglades National Park Other OFW as boundary reference. Also used John Pennekamp Other OFW and State Land Records parcels to create boundary. Confidence Level: Low. Stock Island and artificial water bodies were not removed at this time. (Special OFW). June 21, 2005. Rule_ID 9i29 (GIS_ID 282): Sarasota Bay Estuarine System. Edited on 20050621 by RH at request of Janet Klemm. Used 24K DRG as guide to include Blind Pass and the water just below Blind Pass and above Midnight Pass. (Special OFW). June 21, 2005. OFW was submitted to BIS/GIS for SDE Layer update. Added to SDE Layer on 20050624. Inserted updated dataset acquired from Ron Hughes (WRM) and inserted in ArcSDE. This updated dataset has 3747 records. Process Date: 6/23/2005
November 29, 2005. Rule_ID 9b7 (GIS_ID 640): Added Crystal River National Wildlife Refuge. 17 individual records were dissolved into one thereby reducing record count. (Other OFW). November 29, 2005. Rule_ID 9b7 (GIS_ID 640): Created Crystal River National Wildlife Refuge. Edits based on State Lands layer from FDEP DataMiner library. (Other OFW). November 29, 2005. Rule_ID 9b12 (GIS_ID 650): Created Island Bay National Wildlife Refuge. Edits based on Florida Managed Areas layer from FDEP DataMiner library. (Other OFW). November 30, 2005. Rule_ID 9b17 (GIS_ID 660): Created Loxahatchee National Wildlife Refuge. (Other OFW). December 1, 2005. Rule_ID 9e11 (GIS_ID 670): Created Prairie Lakes State Preserve. (Other OFW). December 13, 2005. Rule_ID 9e19 (GIS_ID 680): Created Weedon Island State Preserve. Edits based on Florida Managed Areas and State Lands FDEP layer. (Other OFW). February 22, 2006. Rule_ID 9h4 (GIS_ID 216): Big Bend Seagrasses Aquatic Preserve. Edited on 20060222 by RH. Corrected Southeast corner in Levy County near mouth of Withlachoochee River. Aquatic Preserve. March 24, 2006. Rule_ID 9f16 (GIS_ID 690): Created Deering Hammock/Estate. November 29, 2005. Rule_ID 9b12 (GIS_ID 650): Added Island Bay National Wildlife Refuge. (Other OFW). Inserted updated dataset acquired from Ron Hughes (WRM) and inserted in ArcSDE. This updated dataset has 3755 records. Process Date: 3/28/2006
July 10, 2006. Rule_ID 9h31 (GIS_ID 243): Data edited on Pine Island Sound Aquatic Preserve. Josslyn Island added on 20060710 at request of Janet Klemm. Submitted on July 10, 2006 for DataMiner update. Inserted updated dataset acquired from Ron Hughes (WRM) and inserted in ArcSDE. This updated dataset has 3756 records. Josslyn Island polygon was to the Pine Island Sound Aquatic Preserve. Process Date: 7/10/2006
August 31, 2006. Rule_ID 9e6 (GIS_ID 128): Fakahatchee Strand State Preserve. Edited on 20063108 by RH. Edits based on 1987 OFW Atlas, existing OFWs and State Lands layer (like CUL040029390) from FDEP DataMiner library. Confidence level Medium. (Other OFW). October 3, 2006. Rule_ID 9f66 (GIS_ID 700): West Lake. Added on 20063108 by RH. Edits based on 1987 OFW Atlas and State Lands layer from FDEP DataMiner library. Confidence level Medium. (Other OFW). Process Date: 10/3/2006
December 4, 2006 Rule ID 9i8 (GIS_ID 263): Edited Clermont Chain of Lakes. (Special OFW). December 8, 2006 Rule ID 9i4 (GIS_ID 259): Edited Butler Chain of Lakes. (Special OFW). December 15, 2006 Rule ID 9c67 (GIS_ID 710): Created Rose Sink (addition to Ichetucknee Springs State Park) (1-9-06). (Other OFW). Five sliver parcels were removed which reduced the record count. Process Date: December 20, 2006
Inserted updated dataset acquired from WRM and inserted in ArcSDE. This updated dataset has 3754 records. Five sliver parcels were removed which reduced the record count. Process Date:
February 28, 2007: Edited Myakka Florida Wild and Scenic River Segment (5-14-86). May 22, 2007: Multiple edits to Lower Econlockhatchee. June 11, 2007: Multiple edits to Savannas State Reserve. June 13, 2007: Multiple edits to Lake Woodruff NWR. June 15, 2007: Created Hillsborough River State Park. June 21, 2007: Created ITT Hammock Snapper Creek. Process Date:
Inserted updated dataset acquired from WRM and inserted in ArcSDE. This updated dataset has 3763 records. Process Date: 7/5/2007
September 7, 2007: Edited Gulf Islands National Seashore. Boundaries were completely redone. September 14, 2007: Created Carlton Half-Moon Ranch OFW. Submitted for SDE Update. Process Date: 20071024
Inserted updated dataset acquired from WRM and inserted in ArcSDE. Metadata updated Process Date: 20071029
December 14, 2007: Edits to Indian River - Malabar to Vero Beach Aquatic Preserve in the Mullet Creek and Sebastian River areas. December 19, 2007: Major edits to Mosquito Lagoon Aquatic Preserve were finally completed. Submitted for SDE update. Process Date: 20071221
Inserted updated dataset acquired from WRM and inserted in ArcSDE. Metadata updated. Process Date: 20080104
April 1, 2008: Created Bower Tract. June 25, 2008: Created Stark Tract OFW. June 25, 2008: Created Upper Black Creek OFW at Janet Klemm's request. June 27, 2008: Created a new boundary for Canaveral National Seashore OFW. July 1, 2008: Edited Spruce Creek Special OFW. Added tributary (see OFW Rule ID 9i33a). Submitted for SDE layer update. Process Date: 20080701
Inserted updated dataset acquired from WRM and inserted in ArcSDE. Metadata updated Process Date: 20080707
This dataset was downloaded by the GeoPlan Center from the FDEP website (http://www.dep.state.fl.us/gis/datadir.asp) on 07/23/2008. When received the data set was in the following projection: Albers NAD 83 HARN. - Added the field DESCRIPT based on NAME. - Added the field FGDLAQDATE based on date downloaded from source. - Upcased all text in the attribute table. - Data set was renamed ofw_other_jan08 from OUTSTANDING_FLORIDA_WATERS Process Date: 20080723
Data imported to ArcSDE and exported as a shapefile. Process Date: 20080725
MAP PROJECTION PARAMETERS:

Projection                          ALBERS
Datum                               HPGN
Units                               METERS
Spheroid                            GRS1980
1st Standard Parallel               24  0  0.000
2nd Standard Parallel               31 30  0.000
Central Meridian                   -84 00  0.000
Latitude of Projection's Origin     24  0  0.000
False Easting (meters)              400000.00000
False Northing (meters)             0.00000

DATA SOURCE CONTACT (S):

Name:
Abbr. Name:
Address:


Phone:

Web site:
E-mail:
Contact Person:
         Phone:
        E-mail:
Florida Department of Environmental Protection (FDEP) OTIS/GIS Section
FDEP
2600 Blair Stone Rd Twin Towers MS 6520
Tallahassee, FL
32399-2400


http://www.dep.state.fl.us/gis/datadir.htm GIS.Librarian@dep.state.fl.us

FGDL CONTACT:
Name:                   FLORIDA GEOGRAPHIC DATA LIBRARY
Abbr. Name:             FGDL
Address:                Florida Geographic Data Library
                        431 Architecture Building
                        PO Box 115706
                        Gainesville, FL  32611-5706
Web site:               http://www.fgdl.org

Contact FGDL: 

      Technical Support:	        http://www.fgdl.org/fgdlfeed.html
      FGDL Frequently Asked Questions:  http://www.fgdl.org/fgdlfaq.html
      FGDL Mailing Lists:		http://www.fgdl.org/fgdl-l.html
      For FGDL Software:                http://www.fgdl.org/software.html