DEP.AQUATIC_PRESERVES_AREAS

Data format: SDE Feature Class

File or table name: DEP.AQUATIC_PRESERVES_AREAS

Coordinate system: Albers Conical Equal Area

Theme keywords: Aquatic Preserve

Abstract: Aquatic Preserves in the State of Florida maintained by CAMA.

FGDC and ESRI Metadata:

Metadata elements shown with blue text are defined in the Federal Geographic Data Committee's (FGDC) Content Standard for Digital Geospatial Metadata (CSDGM). Elements shown with green text are defined in the ESRI Profile of the CSDGM. Elements shown with a green asterisk (*) will be automatically updated by ArcCatalog. ArcCatalog adds hints indicating which FGDC elements are mandatory; these are shown with gray text.

Identification Information:


Citation:
Citation information:
Originators: FMRI


*Title:
DEP.AQUATIC_PRESERVES_AREAS
*File or table name: DEP.AQUATIC_PRESERVES_AREAS


Publication date: 1997
*Geospatial data presentation form: vector digital data


*Online linkage: Server=arcsde; Service=sde1; User=dep; Version=SDE.DEFAULT


Description:
Abstract:
Aquatic Preserves in the State of Florida maintained by CAMA.

Purpose:
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 Department
acquired the boundaries already created for the Aquatic Preserves.

*Language of dataset: en


Time period of content:
Time period information:
Single date/time:
Calendar date: 1997

Currentness reference:
ground condition

Status:
Progress: Complete
Maintenance and update frequency: As needed

Spatial domain:
Bounding coordinates:
*West bounding coordinate: -87.408479
*East bounding coordinate: -79.922243
*North bounding coordinate: 30.748418
*South bounding coordinate: 24.581931

Local bounding coordinates:
*Left bounding coordinate: 73799.357000
*Right bounding coordinate: 790295.300000
*Top bounding coordinate: 748942.526500
*Bottom bounding coordinate: 70578.795500

Keywords:
Theme:
Theme keywords: Aquatic Preserve
Theme keyword thesaurus: none

Place:
Place keywords: Florida

Access constraints: none
Use constraints:
Aquatic Preserve information is availiable in two different versions.  This version contains AP 
information maintained by CAMA.  Aquatic Preserve information is also available in the 
Outstanding Florida Waters layer.

Currently, all aquatic preserves are also Outstanding Florida Waters (OFWs).  This was not the case
in the past and may change again in the future, but an Aquatic Preserve was dropped.  It's important
to note that there are three aquatic preserves whose OFW boundaries differ from the aquatic preserve
boundary. These are described more specifically in the OFW rule 62-302.700:  Indian River Malabar
to Vero expansion - does not include portions of Sebastian and Turkey Creeks; Wekiva River - does
not include portions of the St. Johns River; and Big Bend - the OFW rule specifies certain
"incorporated and unincorporated areas that are excluded."

Browse graphic:
Browse graphic file name: \\bis-4cgxh11\metadata\thumbnails\dep.aquatic_preserves_areas.gif
Browse graphic file type: GIF

*Native dataset format: SDE Feature Class
*Native data set environment:
Microsoft Windows 2000 Version 5.0 (Build 2195) Service Pack 2; ESRI ArcCatalog 8.1.2.671


Back to Top
Data Quality Information:


Lineage:
Source information:
Source citation:
Citation information:
Source scale denominator: 24,000

Process step:
Process description:
Aquatic Preserve boundaries were originally created by the Florida Marine Research 
Institute (FMRI)/CAMRA using COGO (COordinate GeOmetry) methods.

Process software and version: ARC/INFO
Process date: 1996


Process contact:
Contact information:
Contact organization primary:
Contact person: Earl Pearson
Contact organization: Florida Department of Environmental Protection/Coastal & Aquatic Managed Areas
Contact position: OPS GIS Technician


Contact address:
Address type: mailing and physical address
Address:
432I  Douglas Bldg.
City: Tallahassee
State or province: FL
Postal code: 32399-2400

Contact voice telephone: 850/245-2094


Process step:
Process description:
Librarian coverage was transformed from NAD27 to HPGN using PROJECT command.

Process software and version: ARC/INFO 7.0.4
Process date: Spring 1997


Process step:
Process description:
Shapefile of this dataset was inserted into Spatial Database Engine (SDE 3.0.2).

Process software and version: SDE 3.0.2
Process date: Spring 1999


Process step:
Process description:
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 software and version: SDE 3.0.2
Process date: October 2000


Process step:
Process description:
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 software and version: SDE 3.0.2
Process date: November 2000


Process step:
Process description:
Column PROJ_LINK was added which contains URLs to internet information
listing the public interest projects for each Preserve.

Process software and version: SDE 3.0.2
Process date: December 2000


Process step:
Process description:
Links in the columns LINK and PROJ_LINK were updated to reflect new page
locations required by myflorida.com.

Process software and version: SDE 3.0.2
Process date: January 2001


Process step:
Process description:
Layer name changed to reflect separate nature of CAMA and OFW
Aquatic Preserve boundaries.

Process software and version: ArcSDE 8.1.2; ArcCatalog
Process date: 12/18/02


Back to Top
Spatial Data Organization Information:


*Direct spatial Rreference method: Vector


Point and vector object information:
SDTS terms description:
*Name: DEP.AQUATIC_PRESERVES_AREAS
*SDTS point and vector object type: G-polygon
*Point and vector object count: 2904

ESRI terms description:
*Name: DEP.AQUATIC_PRESERVES_AREAS
*ESRI feature type: Simple
*ESRI feature geometry: Polygon
*ESRI topology: FALSE
*ESRI feature count: 2904
*Spatial index: TRUE
*Linear referencing: FALSE


Back to Top
Spatial Reference Information:


Horizontal coordinate system definition:
Coordinate system name:
*Projected coordinate system name: Custom
*Geographic coordinate system name: GCS_North_American_1983_HARN

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.000000
*False northing: 0.000000

Planar coordinate information:
*Planar coordinate encoding method: coordinate pair
Coordinate representation:
*Abscissa resolution: 0.000500
*Ordinate resolution: 0.000500
*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

Back to Top
Entity and Attribute Information:


Detailed description:
*Name: DEP.AQUATIC_PRESERVES_AREAS


Entity type:
*Entity type label: DEP.AQUATIC_PRESERVES_AREAS
*Entity type type: Feature Class
*Entity type count: 2904

Attribute:
Attribute label: AREA
*Attribute alias: DEP.AQUATIC_PRESERVES_AREAS.AREA


*Attribute type: Double
*Attribute width: 8
*Attribute precision: 28
*Attribute scale: 9


Attribute:
*Attribute label: NAME
*Attribute alias: NAME


*Attribute type: String
*Attribute width: 70
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: SECONDARY
*Attribute alias: SECONDARY


*Attribute type: String
*Attribute width: 70
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: LANDTYPE
*Attribute alias: LANDTYPE


*Attribute type: String
*Attribute width: 5
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: OFW_ID
*Attribute alias: OFW_ID


*Attribute type: String
*Attribute width: 5
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: LINK
*Attribute alias: LINK


*Attribute type: String
*Attribute width: 128
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: PROJ_LINK
*Attribute alias: PROJ_LINK


*Attribute type: String
*Attribute width: 100
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: OBJECTID
*Attribute alias: OBJECTID
*Attribute definition:
Feature geometry.
*Attribute definition source:
ESRI

*Attribute type: OID
*Attribute width: 4
*Attribute precision: 10
*Attribute scale: 0


Attribute domain values:
*Unrepresentable domain:
Coordinates defining the features.


Attribute:
*Attribute label: SHAPE
*Attribute alias: SHAPE
*Attribute definition:
Feature geometry.
*Attribute definition source:
ESRI

*Attribute type: Geometry
*Attribute width: 4
*Attribute precision: 0
*Attribute scale: 0


Attribute domain values:
*Unrepresentable domain:
Coordinates defining the features.


Attribute:
*Attribute label: SHAPE.AREA
*Attribute alias: SHAPE.AREA


*Attribute type: Double
*Attribute width: 0
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: SHAPE.LEN
*Attribute alias: SHAPE.LEN


*Attribute type: Double
*Attribute width: 0
*Attribute precision: 0
*Attribute scale: 0


Overview description:
Entity and attribute overview:
Attribute Description 
 
OFWAQPRS 

PAT: 
NAME          Aquatic Preserve name from the original FMRI Aquatic Preserve data 
SECONDARY     Alternate name from the original FMRI Aquatic Preserve data 
LANDTYPE      'WATER' or 'LAND' 
OFW_ID        Unique DEP OFW identifier 
LINK          WEB address for general information about the Aquatic Preserve
PROJ_LINK     WEB address for the mitigation project listings

 
 
 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.

Back to Top
Distribution Information:


Resource description: Aquatic Preserves (areas)


Back to Top
Metadata Reference Information:


*Metadata date: 20030528


*Language of metadata: en


Metadata contact:
Contact information:
Contact organization primary:
Contact person: GIS Section
Contact organization: Florida Department of Environmental Protection

Contact address:
Address type: mailing and physical address
Address:
2600 Blair Stone Rd
Twin Towers MS 6520
City: Tallahassee
State or province: FL
Postal code: 32399-2400

Contact voice telephone: 850/245-8238


*Metadata standard name: FGDC Content Standards for Digital Geospatial Metadata
*Metadata standard version: FGDC-STD-001-1998
*Metadata time convention: local time


Metadata extensions:
*Online linkage: http://www.esri.com/metadata/esriprof80.html
*Profile name: ESRI Metadata Profile

Back to Top
Binary Enclosures:


Enclosure:
Enclosure type: Base64
Original file name: dep.ofw_aquatic_preserves_areas.wri
Description of enclosure:

Back to Top