FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION
VERSION 2007

TITLE: NORTH FLORIDA FUTURE LAND USE

Geodataset Name:       FTRLUN
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Polygon
Feature Count:         21538
GENERAL DESCRIPTION:
This dataset contains the future land use as developed by the Regional Planning Councils of the State of Florida.
DATA SOURCE(S):                    Southwest Florida Regional Planning Council
SCALE OF ORIGINAL SOURCE MAPS:     126720
DATE OF AUTOMATION OF SOURCE:      19940413
GEODATASET EXTENT:                 North Florida

FEATURE ATTRIBUTE TABLES:

Datafile Name: FTRLUN.DBF
ITEM NAME WIDTH TYPE
COUNTY
40 Text
ACRES
21 Double
DESCRIPT
50 Text
OBJECTID
4 OID
AUTOID
4 Integer
SHAPE
4 Geometry
SHAPE.AREA
0 Double
SHAPE.LEN
0 Double

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item
Item Description
COUNTY The county of Florida in which the polygon lies

ACRES Number of acres in each land-use polygon; calculated by dividing AREA by 43560 (original dataset had units in feet)

DESCRIPT Based on USE item

OBJECTID Internal feature number.

AUTOID No description

SHAPE Feature geometry.

SHAPE.AREA No description

SHAPE.LEN No description


USER NOTES:
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."
GeoPlan relied on the integrity of the attribute information within the original data.

This dataset is the result of a compilation of many datasets that
did not use the same land use categories. The result is that many different
land use types were consolidated into generic categories.

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:
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) Reprojected data to FGDL HPGN
(2) Set Precision to DOUBLE
(3) Set Tolerances to FGDL Standards
(4) Added DESCRIPT item based on USE item
Process Date: 2000

Metadata imported. Process Date:
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:
SWFRPC
Southwest Florida Regional Planning Council
4890 Bayline Drive, 4th Floor, PO Box 3455
N. Fort Myers, FL
33918-3455
(941) 656-7720

http://www.swfrpc.org/

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