ST. JOHNS RIVER WATER MANAGEMENT DISTRICT LAND USE AND COVER 2009

Metadata also available as

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator: St. Johns River Water Management District
Publication_Date: 20111101
Title:
ST. JOHNS RIVER WATER MANAGEMENT DISTRICT LAND USE AND COVER 2009
Edition: LCLU2009_SJRWMD
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Palatka, Florida
Publisher: St. Johns River Water Management District
Other_Citation_Details:
St. Johns River Water Management District consisting of; Alachua County (Partial Coverage), Baker County, Bradford County (Partial Coverage), Brevard County, Columbia County (Partial Coverage), Clay County, Duval County, Flagler County, Indian River County, Lake County (Partial Coverage), Marion County (Partial Coverage), Nassau County, Okeechobee County (Partial Coverage), Orange County (Partial Coverage), Osceola County (Partial Coverage), Polk County (Partial Coverage), Putnam County, Seminole County, St. Johns County, St. Lucie County (Partial Coverage), Union County (Partial Coverage), and Volusia County.
Online_Linkage: <ftp://secure.sjrwmd.com/disk6b/lcover_luse/lcover2009/>
Online_Linkage:
Server=wopr.fla-etat.org; Service=5151; User=etat; Version=SDE.DEFAULT
Description:
Abstract:
Land cover and land use in the St. Johns River Water Management District based on 2009 color infrared aerial photography. This layer is a copy of the 2004 lulc dataset, with updates based on conditions in the 2009 photography. Please note: The field names in the original attribute table from SJRWMD were renamed by the GeoPlan Center. The original field names from SJRWMD are listed in the Process Steps (Data Quality Section) and in the Attribute Definitions (Entity and Attribute Information section). All Water Management District land use datasets distributed via FGDL will contain these standardized field names, for ease of using land use data at the statewide extent. This is an update to the FGDL LU_SJRWMD_2004.shp data layer.
Purpose:
This data layer was developed to support many of the District's critical projects or programs, including Pollution Load Reduction Goal Development, Land Acquisition, Land Management, Water Supply Planning, Floodplain Management, and Surface and Ground Water Quality Monitoring.
Wetlands identified in this layer should only be used for general reference, not for legal purposes or detailed analysis. Local determinations always require field inspection.
Supplemental_Information:
A detailed Photointerpretation Key is available at X:\IR\Documentation\LULC\lu2009_PI_Key\keylist.html
The source imagery was primarily flown from December 2008 to March 2009. There are exceptions: see the metadata for the 2009 orthophotos for more details. (to be filled in here later ...)
Important note about wetlands: The primary reference wetland occurrence is the SJRWMD Wetland Vegetation layer, which is based on photography from the late 1980s. In editing the 2009 land use / land cover layer, the assumption is that if a feature was identified as a wetland in the Wetland Vegetation layer, it is still considered a wetland, even if the vegetation has been disturbed. Exceptions in developed areas can occur, where the wetland feature has been eradicated or drained, or if prolonged dry conditions appear to have irreversibly impacted the wetland.
Changes to 2009 compared to previous layers:
1. In 2009, the use of the 3000 classes (Upland nonforested) is restricted to natural areas, and no longer applies to grassy or herbaceous areas in an urban context.
2. Changes to Rural Residential features (LUCODE = 1180) - In 2004, rural residential classes (LUCODE = 1180) were required to have a different land cover code. In 2009, this rule was changed to require dual coding only if the cover type is forested (4000s), shrub and brush land (3200), or mixed upland nonforested (3300). - If the land use is pasture (LUCODE = 2110 or 2120), then both the LUCODE and LCCODE values should be classed as pasture, not 1180, even if a home is present. - If it appears that the majority of the feature is actively mowed, then both the LUCODE and LCCODE values should be 1180.
3. Changes to Improved Pasture (2110) - In 2009, improved pastures (LUCODE = 2110) may have a different land cover code where wetlands occur within the pasture. In these cases, the LCCODE is usually Wet Prairie (6430).
4. Changes to Unimproved Pasture (2120) - In 2009, unimproved pastures (LUCODE = 2120) must have a different land cover code such as 3100, 3200, 3300 or a wetland class. This change was made based on user feedback.
5. Changes to residential under construction (LUCODE = 1190, 1290, and 1390) - The percent cutoff was changed to 50%, meaning that if the feature is more than 50% complete, it should be classed as the regular residential type, not "under construction". In previous years, the cutoff was 67%. This change was made based on user feedback. - We also allow for "under construction" codes to be used for even very low percentages of completion, at the discretion of the PI. These cases are relatively few, and used where property data shows parcel lots already laid out, and residential use appears very likely, even with no visible construction activity.
6. Surface water collection basins (8370) can be used as both a land use and land cover code. To maintain the new convention that Herbaceous upland nonforested (3100) be used in natural or non-urban settings, 3100 can no longer be used as a cover type in conjunction with 8370.
Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 20081201
Ending_Date: 20090301
Currentness_Reference: publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: As needed
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -87.429040
East_Bounding_Coordinate: -79.872251
North_Bounding_Coordinate: 30.983191
South_Bounding_Coordinate: 24.492815
Keywords:
Theme:
Theme_Keyword_Thesaurus: NONE
Theme_Keyword: land cover
Theme_Keyword: land use
Theme_Keyword: FLUCCS
Theme_Keyword: 2009 Land Use/Cover Classifications
Theme:
Theme_Keyword_Thesaurus: ISO 19115 Topic Category
Theme_Keyword: imageryBaseMapsEarthCover
Theme_Keyword: planningCadastre
Place:
Place_Keyword_Thesaurus: SJRWMD-GIS Metadata Thesaurus
Place_Keyword: Florida
Place_Keyword: St. Johns River Water Management District
Place_Keyword: Alachua County
Place_Keyword: Baker County
Place_Keyword: Bradford County
Place_Keyword: Brevard County
Place_Keyword: Clay County
Place_Keyword: Duval County
Place_Keyword: Flagler County
Place_Keyword: Indian River County
Place_Keyword: Lake County
Place_Keyword: Marion County
Place_Keyword: Nassau County
Place_Keyword: Okeechobee County
Place_Keyword: Orange County
Place_Keyword: Osceola County
Place_Keyword: Polk County
Place_Keyword: Putnam County
Place_Keyword: Seminole County
Place_Keyword: St. Johns County
Place_Keyword: Volusia County
Place_Keyword: SJRWMD
Temporal:
Temporal_Keyword: 2009
Access_Constraints: None
Use_Constraints:
The St. Johns River Water Management District prepares and uses information for its own purposes and this information may not be suitable for other purposes. This information is provided "as is". Further documentation of this data can be obtained by contacting: St. Johns River Water Management District, Division of Integrated Application Systems, Post Office Box 1429, Palatka, Florida, 32178-1429, (386) 329-4500.
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: St. Johns River Water Management District
Contact_Position: GIS Data Manager, Information Resources Department
Contact_Address:
Address_Type: mailing address
Address: P.O. Box 1429
City: Palatka
State_or_Province: FL
Postal_Code: 32177-1429
Country: USA
Contact_Voice_Telephone: (386) 329-4500
Contact_Electronic_Mail_Address: gis_support@sjrwmd.com
Hours_of_Service: 0800 - 1700 ET
Data_Set_Credit:
This data set was compiled with input from SJRWMD project staff.
Native_Data_Set_Environment:
Microsoft Windows Vista Version 6.1 (Build 7601) Service Pack 1; ESRI ArcCatalog 9.3.1.4000
Cross_Reference:
Citation_Information:
Other_Citation_Details:
St. Johns River Water Management District <http://www.sjrwmd.com>
St. Johns River Water Management District - GIS Data Download Table <http://www.sjrwmd.com/gisdevelopment/docs/themes.html>

Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
SJRWMD: LCCODE and LUCODE values were screened to ensure that they belonged to the set of legal FLUCCS values for this data layer, as defined in the SJRWMD 2009 Photointerpretation Key.
GeoPlan relied on the integrity of the attribute information within the original data.
Logical_Consistency_Report:
Primary ancillary layers 2009 color infrared orthophotography SSURGO soils County parcels SJRWMD wetlands
Other ancillary layers 2004 DOQQs 1999 DOQQs 1994 DOQQs 1984 digital photography
Mapping procedure Copy of 2004 layer is the input District divided into mapping phases Progress monitored / measured by quarter quad (SDE LULC2009_Completion_status layer) Photointerpreters (PIs) work on independent quarter quads within the same phase 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 - topology checked periodically to ensure no gaps or overlaps
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.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
This layer is based upon 2009 digital orthophotos. Digital orthophotos must meet horizontal National Map Accuracy Standards (NMAS) at 1:12,000 scale. The NMAS specify that 90 percent of the well-defined points tested must fall within 33.3 feet (1/30 inch) at 1:12,000 scale.
To create the data, the orthorectified images were displayed on a computer screen at varying scales of about 1:12,000 or less.
Vertical_Positional_Accuracy:
Vertical_Positional_Accuracy_Report:
This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Title: 2009 SJRWMD Digital Orthophotos
Source_Scale_Denominator: 12,000
Type_of_Source_Media: Online
Source_Citation_Abbreviation: SJRWMD
Source_Contribution: Spatial and Attribute Information
Source_Information:
Source_Citation:
Citation_Information:
Title: SJRWMD 2004 Land Use / Land Cover
Geospatial_Data_Presentation_Form: vector digital data
Other_Citation_Details:
The 2009 layer is based on the 2004 land use / land cover layer, with revisions made to accommodate: a) thematic changes dictated by updates to the PI Key and classification system, and b) thematic and boundary changes indicated by the 2009 orthophotos.
Type_of_Source_Media: online
Source_Citation_Abbreviation: SJRWMD 2004 Land Use / Land Cover
Source_Contribution: Spatial and Attribute Information
Process_Step:
Process_Description:
The following steps were conducted onsite by contingent staff to create the 2009 layer. 1. The photointerpreters will create a 2009 layer by modifying a copy of the 2004 layer according to thematic and boundary changes indicated by the 2009 orthophotography. 2. All mapping shall be from screen digitizing color-infrared digital orthophotos in ArcGIS 9.3. 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 2009 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. Work began October 2009, and is ongoing as of 5/11/2010.
Source_Used_Citation_Abbreviation: SJRWMD
Process_Date: Not complete
Process_Step:
Process_Description:
All phases are QA'ed by the SJRWMD photointerpretation specialist. Comments are discussed with the photointerpreter(s) who then revise the data accordingly.
Source_Used_Citation_Abbreviation: SJRWMD
Process_Date: Not complete
Process_Step:
Process_Description:
At the completion of each phase, spatial data is checked for topology errors against the following rules:
No gaps between polygons No overlapping polygons
A cluster tolerance of 0.05 meters is used.
Where substantial overlaps or gaps exist, the photointerpreters correct the errors.
Source_Used_Citation_Abbreviation: SJRWMD
Process_Date: Not complete
Process_Step:
Process_Description:
At the completion of each phase, all Land Use/Land Cover code combinations are checked. Illegal code combinations are corrected.
Source_Used_Citation_Abbreviation: SJRWMD
Process_Date: Not complete
Process_Step:
Process_Description:
Over 300 multipart features were discovered and exploded using ArcMap 9.3.
Source_Used_Citation_Abbreviation: SJRWMD
Process_Date: 20100416
Process_Step:
Process_Description:
Final QC steps - Specific check#1: Removed the "STATUS" and "CHECK_PREVIOUS_YEARS" fields. Only 26580 records (out of 332619 total) had a value of "1" for the "STATUS" field - the rest of the records were NULL. This field was probably used by Dawn for her own checking purposes.
Only 14 records (out of 332619 total) had the "CHECK_PREVIOUS_YEARS" field populated. Again, this was probably used at one time by Dawn or Marty for their own checking purposes.
Source_Used_Citation_Abbreviation: SJRWMD
Process_Date: October 6, 2011
Process_Step:
Process_Description:
Specific check #3: Dissolved on the fields: LCCODE, LUCODE, EDITOR, EDIT_DATE.
Added Acres field and recalculated.
Source_Used_Citation_Abbreviation: SJRWMD
Process_Date: October 6, 2011
Process_Step:
Process_Description:
Specific check #4: Manually reviewed all polygons with ACRES value < 0.09. Total=900 polygons. Merged as appropriate after visual inspection.
Acres field was recalculated.
Source_Used_Citation_Abbreviation: SJRWMD
Process_Date: October 19,2011
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Ellen Dean
Contact_Organization: St. Johns River Water Management District
Contact_Position: GIS Analyst
Contact_Voice_Telephone: (386) 227-0351
Process_Step:
Process_Description:
Specific check #5: Built topology. Checked for Gaps and Overlaps. Fixed all. In some gaps, copied polygons from LULC_2004_UPDATE feature class, as it looked as if these polygons in the 2009 feature class had been accidentally deleted.
Acres field was recalculated.
Source_Used_Citation_Abbreviation: SJRWMD
Process_Date: October 20, 2011
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Ellen Dean
Contact_Organization: St. Johns River Water Management District
Contact_Position: GIS Analyst
Contact_Voice_Telephone: (386) 227-0351
Process_Step:
Process_Description:
Reviewed all combinations of LCCODE / LUCODE, and edited to correct errors.
Source_Used_Citation_Abbreviation: SJRWMD
Process_Date: November 2011
Process_Step:
Process_Description:
The GeoPlan Center downloaded the original St. John River Water Management District datasets (see below) from the following FTP site on January 27th, 2012. <ftp://secure.sjrwmd.com/disk6b/lcover_luse/lcover2009/LCLU2009_SJRWMD.zip>
The district-wide dataset LCLU2009_SJRWMD.shp was originally in NAD_1983_HARN_UTM_Zone_17N projection The district-wide layer was reprojected to the FGDL Albers projection.
Next the dataset was renamed from LCLU2009_SJRWMD.shp to LU_SJRWMD_2009.shp
Next the records in the attribute table were UPPERCASED.
Below is the original SJRWMD file structure:
ITEM NAME LCCODE LUCODE EDIT_DATE EDITOR COMMENTS LCCOD_DESC LUCOD_DESC
Below is the crosswalk table between the original file structure and the new file structure:
ORIGINAL NAME NEW NAME LCCODE OTHER LUCODE FLUCCS EDIT_DATE Deleted EDITOR Deleted COMMENTS Deleted LCCOD_DESC Same LUCOD_DESC Same
Additionally GeoPlan added and populated the following fields:
SOURCE SOURCE2 FLUCCS_L1 LEVEL1 FLUCCS_L2 LEVEL2 FLUCCS_L3 LEVEL3 FLUCCSCOMP ACRES DESCRIPT FGDLAQDATE AUTOID
Next GeoPlan ran the Repair Geometry Command 3x.
Next GeoPlan ran the Eliminate Polygon Command on ten features whose area was less than 0.001 Acres.
Next GeoPlan ran the Repair Geometry Command 1x.
Next GeoPlan reviewed the Data layer and cleaned up some issues within the table in order to make sure that the Land cover code (OTHER) and the Land use code (FLUCCS) had the correct matching Land cover code descriptions (LCCOD_DESC) as well as Land use code descriptions (LUCOD_DESC).
Next GeoPlan filled in any missing LCCOD_DESC or LUCOD_DESC attributes with the information found within the SJRWMD 2009 Photointerpretation Key. <ftp://secure.sjrwmd.com/disk6b/lcover_luse/lcover2009/lu2009_PI_Key/>
Source_Used_Citation_Abbreviation: GeoPlan
Process_Date: 20120208
Process_Step:
Process_Description: Dataset copied.
Source_Used_Citation_Abbreviation:
Server=delphi.geoplan.ufl.edu; Service=5151; User=etat; Version=SDE.DEFAULT
Process_Date: 20120214
Process_Time: 22413600

Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: G-polygon
Point_and_Vector_Object_Count: 329927

Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
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.002048
Ordinate_Resolution: 0.002048
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

Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: LU_SJRWMD_2009
Entity_Type_Definition: LU_SJRWMD_2009.DBF
Entity_Type_Definition_Source: SJRWMD
Attribute:
Attribute_Label: OBJECTID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: Shape
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: FLUCCS
Attribute_Definition:
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. SJRWMD = LUCODE - Land use code. The Land Use/Land Cover classification code as defined in the Florida Department of Transportations (DOT) Florida Land Use and Land Cover Classification System (FLUCCS). This is also considered Level 4, SJRWMD uses an adopted classification scheme, for more information on the adopted classification scheme please the Attribute Overview Description Section.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: OTHER
Attribute_Definition:
The following represents the original field, LCCODE (Land cover code), from the St. Johns River Water Management District Layer.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: LUCOD_DESC
Attribute_Definition:
Land use code description from the SJRWMD 2009 Photointerpretation Key.
Attribute_Definition_Source: SJRWMD
Attribute:
Attribute_Label: LCCOD_DESC
Attribute_Definition:
Land cover code description from the SJRWMD 2009 Photointerpretation Key.
Attribute_Definition_Source: SJRWMD
Attribute:
Attribute_Label: SOURCE
Attribute_Definition: Water Management District of Coverage/Origin.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: SOURCE2
Attribute_Definition: Other contributing source.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: FLUCCS_L1
Attribute_Definition:
The highest level (level 1) designation in a hierarchical coding scheme containing 4 levels.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: LEVEL1
Attribute_Definition:
Level 1 land use description, based on the FDOT classification schema.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: FLUCCS_L2
Attribute_Definition:
The second highest level (level 2) designation in a hierarchical coding scheme containing 4 levels.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: LEVEL2
Attribute_Definition:
Level 2 land use description, based on the FDOT classification schema.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: FLUCCS_L3
Attribute_Definition:
The third highest level (level 3) designation in a hierarchical coding scheme containing 4 levels.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: LEVEL3
Attribute_Definition:
Level 3 land use description, based on the FDOT classification schema. There is a possibility that the FDOT Level 3 description does not match that of the Water Management District, for those occurrences this discrepancy has been identified in the FLUCCSCOMP field.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: FLUCCSCOMP
Attribute_Definition:
This field represents a comparison between the dataset's FLUCCS code description and the FDOT FLUCCS code description. Where these two descriptions differed a number one was inserted.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: ACRES
Attribute_Definition: Number of Acres.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: DESCRIPT
Attribute_Definition:
Based on the field LUCOD_DESC, however the classification numbers were removed from the front of each record.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: FGDLAQDATE
Attribute_Definition: The date FGDL acquired the data from the Source.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: AUTOID
Attribute_Definition: Unique ID added by GeoPlan
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: SHAPE.AREA
Attribute_Definition: Area in meters
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: SHAPE.LEN
Attribute_Definition: Perimeter in meters
Attribute_Definition_Source: GeoPlan
Overview_Description:
Entity_and_Attribute_Overview:
The coding scheme is a modified Florida Land Use/Land Cover and Forms Classification System (FLUCCS). A detailed discussion of the coding scheme can be found in the SJRWMD 2000 Photointerpretation Key. The PI Key lists each class used in the 2004 land use / land cover layer, along with a detailed description, keys to photointerpretation, a list of similar classes, special mapping conventions if they exist, a sample DOQ image, and a field picture. SJRWMD staff may access the PI Key through GISDOC (Data, Data Users Guides).
See below for a discussion of the use of LUCODE vs. LCCODE.
Following is a list of valid LCCODE and LUCODE values. * Codes marked with an asterisk are not used for classification and are listed only for clarification.
1000* URBAN AND BUILT UP 1100 Residential, Low Density - Less than 2 dwelling units per acre 1180 Residential, Rural - Less than or equal to 0.5 dwelling units per acre (one unit on 2 or more acres) 1190 Low density under construction 1200 Residential, Med. Density - Two to five dwelling units per acre 1290 Medium density under construction 1300 Residential, High Density 1390 High density under construction 1400 Commercial and Services 1460 Oil and gas storage: except those areas associated with industrial use or manufacturing 1480 Cemeteries 1490 Commercial and services under construction 1500* Industrial 1510 Food processing 1520 Timber processing 1523 Pulp and paper mills 1530 Mineral processing 1540 Oil and gas processing 1550 Other light industry 1560 Other heavy industrial 1561 Ship building and repair 1562 Prestressed concrete plants 1563 Metal fabrication plants 1590 Industrial under construction 1600 Extractive 1610 Strip mines 1611 Clays 1612 Peat 1613 Heavy metals 1620 Sand and gravel pits 1630 Rock quarries 1632 Lime rock or dolomite 1633 Phosphates 1640 Oil and gas fields 1650 Reclaimed lands 1660 Holding ponds 1670 Abandoned mining lands 1700 Institutional 1730 Military 1750 Governmental (to be used for KSC only) 1800 Recreational 1810 Swimming beach 1820 Golf course 1830 Race tracks 1840 Marinas and fish camps 1850 Parks and zoos 1860 Community recreational facilities 1870 Stadiums: Those facilities not associated with High Schools, Colleges, or Universities 1890 Other recreational 1900 Open Land 1920 Inactive land with street pattern but without structures
2000* AGRICULTURE 2100* Cropland and Pastureland 2110 Improved pastures 2120 Unimproved pastures 2130 Woodland pastures 2140 Row crops 2143 Potatoes and cabbage 2150 Field crops 2160 Mixed crops 2200 Tree Crops 2210 Citrus groves 2240 Abandoned tree crops 2300* Feeding Operations 2310 Cattle feeding operations 2320 Poultry feeding operations 2400 Nurseries and Vineyards 2410 Tree nurseries 2420 Sod farms 2430 Ornamentals 2431 Shade ferns 2432 Hammock ferns 2450 Floriculture 2500 Specialty Farms 2510 Horse farms 2520 Dairies 2540 Aquaculture 2600 Other Open Lands - Rural 2610 Fallow cropland
3000* UPLAND NONFORESTED 3100 Herbaceous Upland Nonforested 3200 Shrub and Brush land 3300 Mixed Upland Nonforested
4000* UPLAND FORESTS 4100* Upland Coniferous Forests 4110 Pine flatwoods 4120 Longleaf pine - xeric oak 4130 Sand pine 4200 Upland Hardwood Forest 4210 Xeric oak 4280 Cabbage palm 4300* Upland Mixed Forest 4340 Upland mixed coniferous/hardwood 4370 Australian pine 4400 Tree Plantations 4410 Coniferous pine 4430 Forest regeneration
5000* WATER 5100 Streams and waterways 5200 Lakes 5250 Marshy Lakes 5300 Reservoirs 5400 Bays and estuaries 5430 Enclosed saltwater ponds within a salt marsh 5500 Major springs 5600 Slough waters
6000* WETLANDS 6100* Wetland Hardwood Forests 6110 Bay swamps 6120 Mangrove swamp 6170 Mixed wetland hardwoods 6180 * Cabbage palm wetland 6181 Cabbage palm hammock 6182 Cabbage palm savannah 6200 * Wetland Coniferous Forest 6210 Cypress 6220 Pond pine 6250 Hydric pine flatwoods 6300 Wetland Forested Mixed 6400* Vegetated Non-Forested Wetlands 6410 Freshwater marshes 6420 Saltwater marshes 6430 Wet prairies 6440 Emergent aquatic vegetation 6460 Mixed scrub-shrub wetland 6500 Non-vegetated Wetland
7000* BARREN LAND 7100 Beaches other than swimming beaches 7200 Sand other than beaches 7400 Disturbed land 7410 Rural land in transition without positive indicators of intended activity 7420 Borrow areas 7430 Spoil areas
8000* TRANSPORTATION, COMMUNICATION AND UTILITIES 8100* Transportation 8110 Airports 8120 Railroads 8130 Bus and truck terminals 8140 Roads and highways 8150 Port facilities 8160 Canals and locks 8180 Auto parking facilities - when not directly related to other land uses 8190 Transportation under construction 8200 Communications 8290 Communications under construction 8300* Utilities 8310 Electrical power facilities 8320 Electrical power transmission lines 8330 Water supply plants 8340 Sewage treatment plants 8350 Solid waste disposal 8360 Other treatment ponds 8370 Surface Water Collection Basin 8390 Utilities under construction
*** 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) 2120 - Unimproved pasture 2600 - Other open lands (rural)
Any polygon described by the following LCCODE values must be assigned a different LUCODE value: 8340 - Wastewater treatment - but only for those areas associated with the facility other than the buildings / facility itself 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
Entity_and_Attribute_Detail_Citation: The SJRWMD 2009 Land Cover / Land Use Photointerpretation Key
Entity_and_Attribute_Detail_Citation:
See also: Florida Department of Transportation. 1999. Florida Land Use, Cover and Forms Classification System. Surveying and Mapping, Thematic Mapping Section, Tallahassee Florida.

Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Florida Geographic Data Library (FGDL)
Contact_Person:
Contact_Position:
Contact_Address:
Address_Type: mailing address
Address: 431 Architecture PO Box 115706
City: Gainesville
State_or_Province: Florida
Postal_Code: 32611-5706
Country: United States
Contact_Voice_Telephone:
Contact_TDD/TTY_Telephone:
Contact_Facsimile_Telephone:
Contact_Electronic_Mail_Address: Web site: <http://www.fgdl.org>
Contact_Electronic_Mail_Address: Technical Support: <http://www.fgdl.org/fgdlfeed.html>
Contact_Electronic_Mail_Address: For FGDL Software: <http://www.fgdl.org/software.html>
Contact_Electronic_Mail_Address:
FGDL Frequently Asked Questions: <http://www.fgdl.org/fgdlfaq.html>
Contact_Electronic_Mail_Address: Mailing list for FGDL: <http://www.fgdl.org/fgdl-l.html>
Hours_of_Service:
Contact_Instructions:
Resource_Description: DOWNLOADABLE DATA
Distribution_Liability:
The Florida Geographic Data Library is a collection of Geospatial Data compiled by the University of Florida GeoPlan Center with support from the Florida Department of Transportation. GIS data available in FGDL is collected from various state, federal, and other agencies (data sources) who are data stewards, producers, or publishers. The data available in FGDL may not be the most current version of the data offered by the data source. University of Florida GeoPlan Center makes no guarantees about the currentness of the data and suggests that data users check with the data source to see if more recent versions of the data exist.
Furthermore, the GIS data available in the FGDL are provided 'as is'. The University of Florida GeoPlan Center makes no warranties, guaranties or representations as to the truth, accuracy or completeness of the data provided by the data sources. The University of Florida GeoPlan Center makes no representations or warranties about the quality or suitability of the materials, either expressly or implied, including but not limited to any implied warranties of merchantability, fitness for a particular purpose, or non-infringement. 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>
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Transfer_Size: 326.008
Technical_Prerequisites:
This data is intended for use with a Geographic Information Systems or Remote Sensing software package.

Metadata_Reference_Information:
Metadata_Date: 20120215
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: St. Johns River Water Management District
Contact_Position: GIS Data Manager, Information Resources Department
Contact_Address:
Address_Type: mailing address
Address: P.O. Box 1429
City: Palatka
State_or_Province: FL
Postal_Code: 32178-1429
Country: USA
Contact_Voice_Telephone: (386)329-4500
Contact_Electronic_Mail_Address: gis_support@sjrwmd.com
Hours_of_Service: 0800-1700 ET
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Access_Constraints: None
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile

Generated by mp version 2.9.6 on Wed Feb 15 21:39:55 2012