Geodataset Name:       AQUAP_JUN06
Geodataset Type:       SHAPEFILE
Geodataset Feature:    POLYGON
Feature Count:         2904

DATA SOURCE(S):                    Florida Department of Environmental Protection
SCALE OF ORIGINAL SOURCE MAPS:     24,000
DATE OF AUTOMATION OF SOURCE:      1997
GEODATASET EXTENT:                 State of Florida

FEATURE ATTRIBUTE TABLES:

Datafile Name: AQUAP_JUN06.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
FID	Internal feature number.
Shape	Feature geometry.
LANDTYPE	Whether the polygon represents "WATER" or "LAND."
NAME	Aquatic Preserve name from the original FWRI Aquatic Preserve data
SECONDARY	Alternate name from the original FWRI Aquatic Preserve data
PROJ_LINK	Address for the mitigation project listings
AREA	Area of the polygon (meters).
DESCRIPT	FGDL added field based on NAME
FGDLAQDATE	FGDL added field based on date downloaded from source

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. Description of DOUBLE precision coverage of waqprs FEATURE CLASSES Number of Attribute Spatial Feature Class Subclass Features data (bytes) Index? Topology? ------------- -------- --------- ------------ ------- --------- ARCS 6231 124 POLYGONS 4699 174 Yes NODES 5773 ANNOTATIONS (blank) 69 SECONDARY FEATURES Tics 390 Arc Segments 482440 Polygon Labels 4698 TOLERANCES Fuzzy = 73.706 V Dangle = 0.000 N COVERAGE BOUNDARY Xmin = 73799.446 Xmax = 790295.300 Ymin = 70578.796 Ymax = 748942.526 STATUS The coverage has not been Edited since the last BUILD or CLEAN. COORDINATE SYSTEM DESCRIPTION Projection ALBERS Datum HPGN Units METERS Spheroid GRS1980 Parameters: 1st standard parallel 24 0 0.000 2nd standard parallel 31 30 0.000 central meridian -84 0 0.000 latitude of projection's origin 24 0 0.000 false easting (meters) 400000.00000 false northing (meters) STANDARD COGO PROCEDURES 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. 6 PROJECT DOCUMENTATION 6.1 COGO notebooks: Your personal COGO notebook is a record of the methods which you used to complete your COGO assignments. It should contain at least, but not limited to the following information. 1) any questions you have asked and answers you have received as well as who gave the answer, 2) any request for additional information, 6.2 Information requests: All requests for information shall be written and directed to the appropriate person(see sec. 3). Be sure to include all necessary information. 6.3 Information sources: All sources used to generate parcel boundaries for a park (electronic quad, tax maps, etc.) shall be recorded on the COGO BOUNDARY DEVELOPMENT SHEET for that park. 6.4 Parcel numbers: Record all parcel numbers (see sec. 5.2) along with the grantors and deed dates on the PARCEL IDENTIFICATION SHEET for each park. 6.5 Plots: A color plot of the completed park showing parcel boundaries, parcel text and the associated electronic quad map information should be included in the COGO folder for that park. Set pen size for pen number 7 (black lines) to 0.030. 6.6 Time sheets: Individually record the time spent (number of hours) working on each park, on your DAILY TIME SHEET and briefly describe the work you did. List meetings and other work related activities as separate projects. 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 A note concerning data scale: Scale is an important factor in data usage. Certain scale datasetsare 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:250000 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 analyses. Every effort has been made to supply the user with data documentation. For additional information, see the References sectionand 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

REFERENCES:

Florida Department of Environmental protection: http://www.dep.state.fl.us/gis/datadir.asp

DATA LINEAGE SUMMARY:

Aquatic Preserve boundaries were originally created by the Florida Marine Research Institute (FMRI)/CAMRA using COGO (COordinate GeOmetry) methods. Process Date: 1996 Librarian coverage was transformed from NAD27 to HPGN using PROJECT command. Process Date: Spring 1997 Shapefile of this dataset was inserted into Spatial Database Engine (SDE 3.0.2). Process Date: Spring 1999 Four Lake Weir polygons were removed to reflect Lake Weir having been delisted. Also, 1,812 unnecessary polygons with NAME = 'NOT PRESERVE' were removed. Finally, the field LINK was added which contains URLs to internet information for each of the preserves. All of this work was done at the request of Richard Butgereit and Kathleen Swanson of ERP. Process Date: October 2000 Boundaries for BIG BEND SEAGRASSES AQUATIC PRESERVE, OKLAWAHA RIVER AQUATIC PRESERVE, and PINELLAS COUNTY AQUATIC PRESERVE were replaced by updated boundaries reworked by Earl Pearson of the Office of Coastal and Aquatic Managed Areas and approved by Kathleen Swanson of ERP. Process Date: November 2000 Column PROJ_LINK was added which contains URLs to internet information listing the public interest projects for each Preserve. Process Date: December 2000 Links in the columns LINK and PROJ_LINK were updated to reflect new page locations required by myflorida.com. Process Date: January 2001 Layer name changed to reflect separate nature of CAMA and OFW Aquatic Preserve boundaries. Process Date: 12/18/02 This data was downloaded by GeoPlan from the FDEP website (http://www.dep.state.fl.us/gis/datadir.asp) on June 22, 2006. The file was in the projection NAD 83 HARN. The file was dissolved on the fields LANDTYPE and NAME. - Renamed shapefile from aquatic_preserves_areas to AQUAP_JUN06 - Added a DESCRIPT field to attribute table based on NAME - Added a FGDLAQDATE based on date downloaded from source - Deleted field OBJECTID, OFW_ID - Deleted field LINK as it contained the same information as PROJ_LINK - Upcased all fields - Updated area field using X-tools Process Date: 20060622

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
2600 Blair Stone Rd. Twin Towers MS 6520
Tallahassee, FL
32399-2400
(850) 245-8238


http://www.dep.state.fl.us/gis/datadir.asp

GIS Section

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