FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION
VERSION 2006

TITLE: STATEWIDE WATER MANAGEMENT DISTRICT LAND USE 2004

Geodataset Name:       LU04
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Polygon
Feature Count:         613349
GENERAL DESCRIPTION:
This dataset contains 2004 land use/cover features categorized according to the Florida Land Use and Cover Classification System (FLUCCS). The features were photointerpreted from 1:12,000 UGSG color infrared (CIR) digital orthophoto quarter quadrangles (DOQQs).
DATA SOURCE(S):                    St. John's Water Management District,South West Florida Water Management District,
SCALE OF ORIGINAL SOURCE MAPS:     12,000
DATE OF AUTOMATION OF SOURCE:      20060907
GEODATASET EXTENT:                 SJRWMD, SWFWMD

FEATURE ATTRIBUTE TABLES:

Datafile Name: LU04.DBF
ITEM NAME WIDTH TYPE N. DECIMAL DEGREES
OBJECTID
4 OID ---
FLUCCS
4 Number ---
SOURCE
6 String ---
SOURCE2
13 String ---
OTHER
6 String ---
ACRES
19 Number 11
LEVEL1
50 String ---
LEVEL2
75 String ---
DESCRIPT
125 String ---
FGDLAQDATE
8 Date ---
AUTOID
9 Number ---
SHAPE
4 Geometry ---
SHAPE.AREA
0 Double ---
SHAPE.LEN
0 Double ---

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item
Item Description
OBJECTID Internal feature number.

FLUCCS The land use and land cover classification code as defined in the Florida DOT's FLUCCS classification system. The following represents the original field from the source Water Management District layer
SWFWMD = FLUCCSCODE

SFWMD = LUCODE

SJRWMD = LUCODE


SOURCE Water Management District of Origin

SOURCE2 Portions of SWFWMD and SFWMD overlap. If data from SWFWMD existed then it was used even though it was outside the SWFWMD district. Polygons that orginated from SWFWMD and reside in SFWMD will have a value of SWFWMD_SOUTH in this field.

OTHER The following represents the original field from the source Water Management District: layer:
SWFWMD = LCCODE

SFWMD = OTHER

SJRWMD = LCCODE


ACRES The area in acres of the land use polygon.

LEVEL1 Level 1 land use description.

LEVEL2 Level 2 land use description.

DESCRIPT FGDL item based on level 3 land use from the Florida DOT's FLUCCS classification system.

FGDLAQDATE The Date FGDL acquired the date from the Source(s).

AUTOID GeoPlan Center feature identification number.

SHAPE Feature geometry.

SHAPE.AREA Area in meters

SHAPE.LEN Perimeter in meters

1000    Urban and Built-up
1100    Residential, low density
1120    Mobile home units, low density
1200    Residential, medium density
1220    Mobile home units, medium density
1300    Residential, high density
1320    Mobile home units, high density
1400    Commercial and services
1420    Junk Yards
1440    Cultural and entertainment
1460    Tourist services
1480    Cemeteries
1500    Industrial
1560    Other Heavy Industrial
1600    Extractive
1610    Strip Mines
1620    Sand and gravel pits
1630    Rock quarries
1640    Oil and gas fields
1660    Holding ponds
1700    Institutional
1710    Educational facilities
1720    Religious
1730    Military
1740    Medical and Health care
1750    Governmental
1760    Correctional
1790    Institutional under construction
1800    Recreational
1810    Swimming beach
1820    Golf Courses
1830    Race Tracks
1840    marinas and fish camps
1850    Parks and zoos
1860    Community recreational facilities
1870    Stadiums
1880    Historic sites
1890    Other recreational
1900    Open land (Urban)
2000    Agriculture
2100    Cropland and pastureland
2200    Tree crops
2300    Feeding operations
2400    Nurseries and vineyards
2500    Specialty farms
2540    Aquaculture
2600    Other open land (Rural)
3000    Rangeland
3200    Shrub and brushland
3220    Coastal scrub
3300    Mixed rangeland
4000    Upland Forests
4100    Upland coniferous forests
4130    Sand pines
4200    Upland hardwood forests
4340    Mixed coniferous/hardwood
4350    Dead trees
4400    Tree plantations
4410    Coniferous plantations
4430    Forest regeneration areas
5000    Water
5100    Streams and waterways
5200    Lakes
5300    Reservoirs
5400    Bays and estuaries
5410    Embayments opening directly into the Gulf
5420    Embayments not opening directly into the Gulf
5600    Slough waters
5700    Oceans, Seas, and Gulf's
6000    Wetlands
6100    Wetland hardwood forests
6110    Bay swamps
6120    Mangrove swamps
6130    Gum swamps
6150    Stream and lake swamps
6160    Inland ponds and sloughs
6200    Wetland coniferous forests
6210    Cypress
6230    Atlantic cedar
6300    Wetland forestedmixed
6400    Vegetated non-forested wetlands
6410    Freshwater marshes
6420    Saltwater marshes
6440    Emergent aquatic vegetation
6500    Non-vegetated
6510    Tidal flats
6530    Intermittent ponds
6900    Wetland shrub
7000    Barren land
7100    Beaches
7200    Sand other than beaches
7300    Exposed rocks
7400    Disturbed land
7420    Borrow areas
7450    Burned areas
7500    Riverine sandbars
8000    Transportation, communications, and utilities
8100    Transportation
8110    Airports
8120    Railroads
8140    Roads and highways
8150    Port facilities
8160    Canals and docks
8170    Oil, water, or gas transmission lines
8180    Auto parking facilities
8200    Communications
8210    Transmissions towers
8220    Communication facilities
8300    Utilities
8310    Electrical power facilities
8320    Electrical power transmission lines
8330    Water supply plants
8340    Sewage treatment
8350    Solid waste disposal

*** SJRWMD - LUCODE VS. LCCODE ***
Each feature is required to have two attributes, one emphasizing land 
cover (LCCODE) and the second land use (LUCODE).  In most cases, these two 
values are the same.  They differ in a minority of cases where separate cover and 
use values are required in order to adequately describe the mapping unit. The 
result is a map with dual codes. The LCCODE attribute can be used (mapped, 
queried, etc.) alone for a land cover emphasis; LUCODE can be used alone for a 
land use emphasis; or both can be used together.  

Any polygon described by the following LUCODE values must be assigned a 
different LCCODE value:
       1180 - Rural residential (2-5 acres per dwelling unit)
       1650 - Reclaimed mining lands
       1670 - Abandoned mining lands
       1900 - Open land (urban) 
       1920 - Inactive land with street pattern but no structures (urban)
       2600 - Other open lands (rural)

Any polygon described by the following LCCODE values must be assigned a 
different LUCODE value:
       8340  - Wastewater treatment	
       8360 - Other treatment ponds (non-sewage). 
                   In this case, the LUCODE must be populated with the 
                   associated land use or purpose of the ponds, e.g. 
                   dairy (2520) or cattle feeding operation (2310). 

Polygons described by the following LUCODEs may at the discretion of the 
photointerpreter have differing values for LUCODE and LCCODE:
       1700 - Institutional
       1730 - Military
       1750 - Governmental (Kennedy Space Center only)
       1800 - Recreational
       1850 - Parks and zoos
       2240 - Abandoned tree crops
       2310 - Cattle feeding operations
       2320 - Poultry feeding operations
       2500 - Specialty farms
       2510 - Horse farms
       2520 - Dairies
       8350 - Solid waste disposal
USER NOTES:
This data is provided 'as is'. GeoPlan relied on the integrity of the original data layer's topology.

SJRWMD Logical Consistency Report:

Primary ancillary layers
2004 DOQQs
SSURGO soils
County parcels
SJRWMD wetlands

Other ancillary layers
1999 DOQQs
1994 DOQQs
1984 digital photography

Mapping procedure
Copy of 1999 layer is the input
District divided into 10 mapping phases 
Progress monitored / measured by quarterquad (SDE status layer)
Photointerpreters (PIs) work on independent quarterquads that are 
adjacent to encourage consistency
Onscreen, ArcGIS editing
Geodatabase:
SDE layer
SDE Versions created for each of the two editors 
Editor versions reconciled daily against default 
Attribute domains for LUCODE and LCCODE
Includes fields for editor and edit date; scripts populate these 
fields automatically 
 
Editing process: 
map topology, not geodatabase topology. A cluster tolerance of 0.05 
meters to be used
emphasis on accuracy at 1:12,000 scale, even though the data look 
good enough to focus on larger scale
No sliver polygons shall exist
No overlapping polygons
No gaps
No label errors shall exist.
No dangles shall exist.
No intersection errors shall exist.
This data is provided 'as is' by GeoPlan and is complete to our knowledge.

SJRWMD Completeness Report:

Minimum Mapping Units (see also the PI Key for additional guidelines)
1.  Upland Classes (FLUCCS Codes of 1000, 2000, 3000, 4000, 7000, 8000) - 2 acres
2.  Water and Wetland Classes (FLUCCS Codes of 5000 and 6000) - 0.5 acres
3.  Special Cases
a.  Rivers - Rivers and canals shall be delineated where they are 
approximately 10 meters or greater in width and can be mapped as 
continuous features.
b.  Roads and Railroads - All major transportation corridors shall be 
mapped. Major transportation corridors shall include all US and State 
Routes identified on United States Geological Survey (USGS) 7.5 minute 
topographic quadrangle maps and all other roadways with at least four 
lanes and a substantial median.
c. Utility Corridors - Utility corridors shall be delineated where they are 
approximately 30 meters or greater in width.
GeoPlan relied on the integrity of the attribute information within
the original data.
In the past, FGDL distributed land use by County by Water Management District.
For the 2006 version of FGDL, the two districts that have 2004 land use data 
have been merged together. These two districts (SWFWMD,  
SJRWMD) make up the layer LU04. This layer has been broken up by county for 
easy distribution via ftp or cd-rom.

Because there is no data from SFWMD, SRWMD or NWFWMD, there are several counties
in the panhandle that don't have data for this layer. In these cases you will need
to get LU00 and/or LU95. In addition, because WMD boundaries do not follow county
boundaries, there are some counties in the north eastern part of the state that
have partial data.

No data available:
Dixie, Gilchrist, Suwannee, Hamilton, Lafayatte, Taylor, Madison, Jefferson,
Wakulla, Leon, Franklin, Liberty, Gadsden, Gulf, Calhoun, Jackson, Bay,
Washington, Homes, Walton, Okaloosa, Santa Rosa, Escambia,
Martin, Palm Beach, Broward, Miami-Dade, Monroe, Collier, Lee, 
Hendry, Glades.

Partial Coverage:
Levy, Alachua, Bradford, Union, Columbia, Orange, Osceola, Polk, 
Highlands, Charlotte, Okeechobee, St Lucie

The data was created to serve as base information for use in GIS 
systems for a variety of planning and analytical purposes.

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:
Water Management Districts:

SWFWMD: www.swfwmd.state.fl.us 

SJRWMD: http://sjr.state.fl.us/index.html

DATA LINEAGE SUMMARY:
Process Steps:  SWFWMD

Each 1:24,000 quarter quadrangle, within the District, was 
plotted out two times; once with the existing 1999 land use/cover 
linework, attribute and the 1999 doqq and a second with the 1999 
land use/cover, attribute and the 2004 1M digital aerial photography.  
The plots were plotted out at a scale of 1:8000.  

Changes that occurred with the land use or cover between the 1999 
and 2004 study were documented on the 1:8000 plot using a green 
marker.  Linework or labels that were to be removed were indicated by 
placing a series of "x" over the linework to be deleted.  New linework 
and labels were delineated as a solid line.  Only areas of change between 
1999 and 2004 were delineated.  The 1999 land use/cover was assumed 
to be corrected.  

The 2004 land use/cover map standards remained the same as the 1999 
land use: must fit feature boundaries at a scale of 1:12,000, minimum 
mapping unit of .5 acres for wetlands and 5 acres for uplands.  The FDOT's 
Florida Land Use, Cover and Forms Classification System (FLUCCS) was 
used to classify all features.

Ancillary data sources were used to the fullest extent to ensure proper 
delineation of land use/cover features.  
These data sources included: 1984, 1990, 1994/1995 color infrared 
aerial photography; 1990 and 1995 land use/cover, 
National Wetlands Inventory 1:24,000 maps, 
NRCS county soil surveys and SWFWMD aerial mapping sheets.  
Any features that could not be reliably interpreted were field reviewed.

Versioning and disconnected editing functions were implemented for the 
digital update process.  From the default SDE version of the 2004 land use 
data, a QC1 version was created.  QC2 was then created from the QC1 
version. From the QC2 version, disconnected edit versions were created 
by each editor.  Edits are performed on the editor versions and when 
finished are checked back in to the QC2 version.  Any conflicts between 
QC2 and editors' versions are resolved by accepting the edit changes, or 
keeping the original linework in QC2.  QC2 is subsequently reconciled to QC1.  
QC1 subsequently reconciled to Default. Any conflicts are resolved. All child 
versions are deleted and the database is compressed. QC1 and QC2 are 
re-created and the process is kept going.

Land use and land cover features were delineated, on screen, using 
the 2004 1M digital aerial photographs as a back drop.  Edits were 
made, using heads-up digitizing in ArcMap, on the feature class in the 
personal geodatabase created with the disconnected edit function. 
Linework and labels were added, deleted or reshaped according to the 
corrections delineated on the interpreted image plots. Topology Rules, 
no overlaps and no gaps, were created and verified on the personal 
geodatabase.
Process Date: 20060907

Process Steps: SJRWMD The following steps were conducted onsite by staff of Kyra InfoTech, Inc, to create the 2004 layer. See Statement of work and purchase order specifications (District Purchase order # PO038177) for further details. 1. For each DOQQ, the photointerpreters will create a 2004 layer by modifying a copy of the 2000 layer according to thematic and boundary changes indicated by the 2004 DOQQs. 2. All mapping shall be from screen digitizing color-infrared (CIR) 3.75' Digital Orthophoto Quarter Quadrangles (DOQQ), in ArcGIS 9, with an adjacent digital stereo capable imagery and software for inspecting the digital imagery. 3. All mapping shall be conducted while consulting the ancillary data. 4. All classification will be in keeping with specifications listed in the PI Key. If the PI Key is unclear or incorrect, or if the photointerpreters have questions regarding appropriate classification, the internal District photointerpreter will make the decision. 5. The 2004 layer will have two land use classification items: LCCODE and LUCODE. LCCODE will be used for land cover, while LUCODE will be used for land use; item values will differ only when land use and land cover for any given polygon differ. Detailed guidelines for application of this dual coding scheme are discussed in the PI Key. The contract was initiated Sept. 2004, work began November 2004, and work Sept 2006. Adapting the use of Geodatabase for update and editing of data as well as technical issues with software and hardware slowed the project down in its early phases. All phases were QA'ed by the SJRWMD photointerpretation specialist. Comments were sent to the photointerpreter(s) who then revised the data accordingly. Spatial data was checked for topology errors against the following rules: No gaps between polygons No overlapping polygons A cluster tolerance of 0.05 meters was used. Where substantial overlaps or gaps existed, an SJRWMD photointerpretation specialist was consulted and the errors corrected. The Land Use/Land Cover code combinations were checked for all features against the modified FLUCCS code. Illegal code combinations were corrected. The landuse/land cover data in quarter quad areas around the periphery of the SJRWMD boundary were checked for completeness. If changes to the LULC data for the quarter quad were a result of changes to features shared by complete, neighboring quarter quad data, the features for the quarter quad in question were clipped and deleted. Process Date: 20061101
In 2007 GeoPlan downloaded this dataset from 2 of the 5 Water Management District websites: SJRWMD (http://sjr.state.fl.us/index.html) SWFWMD (http://www.swfwmd.state.fl.us) The data was downloaded in shapefile format. Data from SJRWMD was in Universal Transverse Mercator (UTM), Zone 17, NAD83-90 (HPGN), meters. Data from SWFWMD was in Universal Transverse Mercator (UTM), Zone 17, NAD83-90, meters. Each dataset was then projected to FGDL Albers HPGN. The shapefiles were then appended into a statewide layer using ArcGIS 9.1. There was some overlap in the land use layers before merging them together. Any place there was overlap the following hierarchy was used in this order: SWFWMD, SJRWMD, SFWMD. The layer was then loaded to SDE exported to shapefile and clipped to county boundaries. In some cases there were counties that had very small amounts of data and also fell outside either SJRWMD or SWFWMD. In these cases the data was not included. The following counties fell into this category: St Lucie, Union, Lee, Glades, Columbia, Bradford Process Date: 20070215
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:
SJRWMD
WMD
4049 Reid Street
Palatka, FL
32177
(386) 329-4500

http://sjr.state.fl.us/index.html gis_support@sjrwmd.com

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