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

Metadata also available as

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator: St. Johns River Water Management District
Publication_Date: 20040301
Title:
ST. JOHNS RIVER WATER MANAGEMENT DISTRICT LAND USE AND COVER 2004
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://www.sjrwmd.com/disk6b/lcover_luse/luse2004/>
Description:
Abstract:
This dataset contains 2004 land use/cover features categorized according to the Florida Land Use and Cover Classification System (FLUCCS). Land cover and land use features in the St. Johns River Water Management District (SJRWMD) were photo interpreted from aerial photography consisting of 2004 natural color and color infrared (CIR) 1:12,000 digital orthophoto quarter quadrangles (DOQQs). 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.
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:
The source imagery was obtained from December 2003 to March 2004 and used to produce orthophotos with a one meter ground resolution. Imagery was acquired at 0.62 meter ground sample distance (GSD) resolution. Flight height maintained during mission was 20,000 feet AGL. The imagery was captured at 12-bit radiometric resolution and converted to 8-bit radiometric resolution during post processing. The imagery was captured with 20% sidelap between all adjacent flight lines. The SJRWMD project area was divided into 5 flight blocks due to necessary base station and flight line length requirements. The imagery was obtained and processed by all digital means beginning with data acquisition using a Leica ADS40 Digital Airborne Sensor. The orthophotos are available in GeoTIFF form. The projected coordinate system is UTM zone 17 N, NAD 83 HARN, GRS 80, Units Meters.

Differences between the District FLUCCS and the statewide FDOT FLUCCS.

Every effort is made to keep the District's classification system consistent with the statewide system and those of adjacent districts (SF, SWF, and SR). The classes in the District system use the same names, code numbers and descriptions as the FDOT FLUCCS, in almost all cases. Definitions have been modified or expanded to meet the District's requirements, or to provide necessary clarification to PI's and users. Significant departures from the FDOT FLUCCS are noted in the PI Key pages and in the attached table fluccs_all_layers.

One significant difference between the District and Statewide FLUCCS is with the 3000 category - formerly Rangeland. This level 1 class has been re-named to Upland Non-forested, to better conform to actual mapping practices and landscape conditions. The District realized that many of the herbaceous and shrub areas mapped as 3000s do not meet the FDOT definition of rangeland - they tend rather to be open non-forested areas in urban or rural contexts other than range. A detailed explanation of this change is found at the 3000 PI Key page.

A minor change was made to the 4300 class, changing from 'Upland Hardwood Forests, Continued' to 'Upland Mixed Forest'. However none of the active codes used in these categories are changed from the FDOT version. This change creates a more logical system for the District's purposes.

Users should also note that the definition of 'Forested' vs. 'Non-forested' has been changed. The District system requires 25% rather than 10% canopy closure to be considered Forested.

Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 20031201
Ending_Date: 20040301
Currentness_Reference: ground condition
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:
Theme_Keyword_Thesaurus: ISO 19115 Topic Category
Theme_Keyword: imageryBaseMapsEarthCover
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
Access_Constraints: NONE
Use_Constraints:
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>

SJRWMD 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
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 XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.1.0.722
Cross_Reference:
Citation_Information:
Other_Citation_Details:
St. Johns River Water Management District GIS data download table <http://www.sjrwmd.com/gisdevelopment/docs/themes.html>

Guide to the Photointerpretation Key for the SJRWMD Land Cover Land Use 2000 Layer. <ftp://www.sjrwmd.com/disk6b/lcover_luse/luse2004/PI_Key_lulc2004/guide.html>


Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
GeoPlan relied on the integrity of the attribute information within the original data.

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 2004 Photointerpretation Key.

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.

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 2004 digital orthophoto quarterquads. Digital orthophoto quadrangles and quarter-quadrangles must meet horizontal National Map Accuracy Standards (NMAS) at 1:24,000 scale and 1:12,000 scale, respectively. The NMAS specify that 90 percent of the well-defined points tested must fall within 40 feet (1/50 inch) at 1:24,000 scale and 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.

This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlan

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:
Originator: St. Johns River Water Management District
Publication_Date: 20040301
Title: 2004 Digital Orthophoto Quarterquads
Geospatial_Data_Presentation_Form: remote-sensing image
Publication_Information:
Publication_Place: Palatka, FL
Publisher: St. Johns River Water Management District
Source_Scale_Denominator: 40000
Type_of_Source_Media: online
Source_Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 20031201
Ending_Date: 20040301
Source_Currentness_Reference: ground condition
Source_Citation_Abbreviation: SJRWMD
Source_Contribution: Spatial and Attribute Information
Source_Information:
Source_Citation:
Citation_Information:
Originator: St. Johns River Water Management District
Publication_Date: 20061101
Title: SJRWMD 2000 Land Use / Land Cover
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Palatka, FL
Publisher: St. Johns River Water Management District
Other_Citation_Details:
The 2004 layer is based on the 2000 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 2004 DOQQs.
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 20061101
Source_Currentness_Reference: publication date
Source_Citation_Abbreviation: SJRWMD 2000 Land Use / Land Cover
Source_Contribution: Spatial and Attribute Information
Process_Step:
Process_Description:
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.

Source_Used_Citation_Abbreviation: SJRWMD
Process_Date: September 30, 2006
Process_Step:
Process_Description:
All phases were QA'ed by the SJRWMD photointerpretation specialist. Comments were sent to the photointerpreter(s) who then revised the data accordingly.
Source_Used_Citation_Abbreviation: SJRWMD
Process_Date: September 30, 2006
Process_Step:
Process_Description:
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.

Source_Used_Citation_Abbreviation: SJRWMD
Process_Date: October 2006
Process_Step:
Process_Description:
The Land Use/Land Cover code combinations were checked for all features against the modified FLUCCS code. Illegal code combinations were corrected.
Source_Used_Citation_Abbreviation: SJRWMD
Process_Date: October 2006
Process_Step:
Process_Description:
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.
Source_Used_Citation_Abbreviation: SJRWMD
Process_Date: October 2006
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 May 21st, 2008. <ftp://www.sjrwmd.com/disk6b/lcover_luse/luse2004/>

lulc2004_alachua.zip lulc2004_baker.zip lulc2004_bradford.zip lulc2004_brevard.zip lulc2004_clay.zip lulc2004_columbia.zip lulc2004_desc.dbf lulc2004_duval.zip lulc2004_flagler.zip lulc2004_indian_river.zip lulc2004_lake.zip lulc2004_marion.zip lulc2004_nassau.zip lulc2004_okeechobee.zip lulc2004_orange.zip lulc2004_osceola.zip lulc2004_polk.zip lulc2004_putnam.zip lulc2004_seminole.zip lulc2004_st_johns.zip lulc2004_st_lucie.zip lulc2004_union.zip lulc2004_volusia.zip

Each county was downloaded and unzipped. Next the counties were merged to create one district wide layer.

Next the district wide layer was dissolved (single part) on both the LUCODE and LCCODE, to remove the feature lines created at the county boundaries, this was done to create a more uniform district wide layer. The district wide feature count went from 354563 to 333954 features upon completion of the dissolve.

PLEASE NOTE: A few of the polygons found on the interior of the counties were dissolved into adjoining polygons with the same LUCODE and LCCODEs.

The newly created district-wide dataset was originally in NAD_1983_HARN_UTM_Zone_17N projection The district-wide layer was reprojected to the FGDL Albers projection.

Next a table join was performed between the lulc2004_desc.dbf and the district-wide layer based on the CODE field in the lulc2004_desc.dbf, and the LUCODE field in the shapefile. Once joined the layer was exported. in order to permanently append the lulc2004_desc.dbf table information.

Next the records in the attribute table were UPPERCASED.

Below is the original SJRWMD file structure:

ITEM NAME WIDTH TYPE OBJECTID 10 Number LCCODE 4 Number LUCODE 4 Number SHAPE_AREA 19 Number SHAPE_LEN 19 Number CODE 4 Number DESCRPT 150 String

Below is the crosswalk table between the original file structure and the new file structure:

ORIGINAL NAME NEW NAME OBJECTID Deleted LCCODE OTHER LUCODE FLUCCS SHAPE_AREA Deleted SHAPE_LEN Deleted CODE Deleted DESCRPT 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

Source_Used_Citation_Abbreviation: GeoPlan
Process_Date: 20080521
Process_Step:
Process_Description:
A problem was found with 14,477 records that affected the attribute values only (not spatial values) for the fields FLUCCS_L1, FLUCCS_L2, FLUCCS_L3. This field should be based on the FLUCCS field and for these records it was based on the OTHER field. The problem has now been corrected. This problem will be found if you downloaded this layer from FGDL anywhere between: 5/15/08 to 10/15/08.

Data imported to ArcSDE and exported as a shapefile.

Source_Used_Citation_Abbreviation: GeoPlan
Process_Date: 20081008

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: 333954
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: G-polygon
Point_and_Vector_Object_Count: 352299

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_2004
Entity_Type_Definition: LU_SJRWMD_2004.DBF
Entity_Type_Definition_Source: GeoPlan
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: 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. SJRWMD uses an adopted classification scheme, for more information on the adopted classification scheme please the Attribute Overview Description Section. See SJRWMD 2004 Photointerpretation Key for more information.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: OTHER
Attribute_Definition:
The following represents the original field from the source Water Management District Layer.SJRWMD = LCCODE - Land cover code. See SJRWMD 2004 Photointerpretation Key for more information.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: DESCRPT
Attribute_Definition:
SJRWMD land use classification FLUCCS code number and FLUCCS code description, based on the lulc2004_desc.dbf.
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; Kyra InfoTech.
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. The following represents the original field from the source Water Management District Layer.SRWMD = LEVEL_1_LANDUSE
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. The following represents the original field from the source Water Management District Layer.SRWMD = LEVEL_2_LANDUSE
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. The following represents the original field from the source Water Management District Layer.SRWMD = LEVEL_3_LANDUSE
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 comparision 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 DESCRPT, 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: GeoPlan Center feature identification number.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: SHAPE
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
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:
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 Limerock 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 Brushland 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

8200 Communications 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 basins

9000 Special Classifications - Direction requested

Entity_and_Attribute_Detail_Citation:
The SJRWMD 2004 Land Cover / Land Use Photointerpretation Key

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 FGDL DATA AS PROVIDED BY CONTRIBUTING ORGANIZATIONS AND ANY PROGRAMMING SOFTWARE CREATED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER (COLLECTIVELY THE 'MATERIALS') ARE COPYRIGHTED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER FOR THE FGDL CONTRIBUTING AGENCIES AND ORGANIZATIONS (THE 'DATA PROVIDERS'). DO NOT REPRODUCE, REDISTRIBUTE OR RESELL THE MATERIALS, OR PROVIDE THE MATERIALS FOR FREE TO CUSTOMERS OR CLIENTS, OR PLACE THE MATERIALS FOR DOWNLOAD ON A WEBSITE. ADDITIONALLY, WHEN USING FGDL DATA OR SOFTWARE IN PROJECTS, MAPS, ETC.; YOU AGREE TO ACKNOWLEDGE THE FGDL AS A DATA SOURCE. THE MATERIALS ARE PROVIDED 'AS IS'. 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 MAKES NO WARRANTIES, GUARANTIES OR REPRESENTATIONS AS TO THE TRUTH, ACCURACY OR COMPLETENESS OF THE DATA PROVIDED BY THE FGDL CONTRIBUTING ORGANIZATIONS. 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.
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Format_Name: SHP
Format_Version_Number: v9.0
File_Decompression_Technique: Winzip
Transfer_Size: 318.326
Digital_Transfer_Option:
Online_Option:
Computer_Contact_Information:
Network_Address:
Network_Resource_Name: <http://www.sjrwmd.com>
Offline_Option:
Technical_Prerequisites:
This data is intended for use with a Geographic Information Systems or Remote Sensing software package.

Metadata_Reference_Information:
Metadata_Date: 20080521
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
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.8.6 on Wed Oct 15 13:10:18 2008