St. Johns River Water Management District 20020701 Land Cover / Land Use - 2000 - SJRWMD vector digital data Palatka, Florida St. Johns River Water Management District 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), Levy 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), Sumter County (Partial Coverage), Union County (Partial Coverage), and Volusia County. ftp://secure.sjrwmd.com/disk6b/lcover_luse/luse2000/ This dataset contains land cover and land use in the St. Johns River Water Management District based on 1999 and 2000 color infrared aerial 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 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. The photography for the DOQs upon which this layer is based was flown by the National Aerial Photography Program (NAPP) primarily from Jan 1999 through Dec 1999. See the item DOQ00_INFO in the attribute table of gislib.img_idx_doqs for specific photo dates. January 1999 February 1999 March 1999 November 1999 December 1999 19990101 19991201 publication date Complete As needed -82.603103 -80.195687 30.837854 27.362658 ISO 19115 Topic Category imageryBaseMapsLandCover planningCadastre None Land Use vegetation urban agriculture Land Cover wetland FLUCCS residential SJRWMD-GIS Metadata Thesaurus Clay County Osceola County Duval County Nassau County Florida Orange County Bradford County Sumter County Okeechobee County Putnam County Volusia County Polk County Levy County Lake County Alachua County Seminole County Marion County Flagler County Baker County Indian River County St. Johns County St. Johns River Water Management District Brevard County Year 1999 None 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. St. Johns River Water Management District GIS Data Manager, Information Resources Department mailing

P.O Box 1429

Palatka FL 32177-1429 US (386) 329-4500 gis_support@sjrwmd.com 0800 - 1700 EST http://intraweb/gisdoc/cf/smms0/gifimages/ JPEG Avineon, Inc. (formerly Agra-Baymont, Inc.) This data set was compiled with input from SJRWMD project staff. Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595 SJRWMD GIS data download table: http://www.sjrwmd.com/gisdevelopment/docs/themes.html 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 2000 Photo interpretation Key. GeoPlan relied on the integrity of the attribute information within the original data. The dataset was developed with the following contract specifications; the contractor ran a QA aml on all data to check these specs. · All files must import from ArcInfo export files correctly. · No edit masks shall be present. · Coverages shall exist in DOUBLE precision. · Arc and Polygon topology (NET topology) shall be present. · During the entire development process, the ArcInfo CLEAN command shall not be performed, directly or indirectly, more than once on each coverage. · All coverages shall be flawlessly coordinate edge matched to adjacent coverages. Since product delivery will be in partial sets of coverages, each subsequent delivery shall be flawlessly coordinate edge matched to all previous deliveries. · Identically coded polygons shall not be adjacent to each other within a coverage. · All features shall exist wholly within the registration coverage tile bounding arcs. · No superfluous pseudo nodes shall exist. · No superfluous tics shall exist. · There shall be no duplicate features. · No sliver polygons shall exist. · No label errors shall exist. · No dangles shall exist. · No intersection errors shall exist. · The universe polygon shall not possess a label. 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. SJRWMD: This layer is based upon 1999/2000 digital orthophoto quarter quads. 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 This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan The 2000 layer is based on the 1995 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 1999 DOQQs. onLine SJRWMD 1995 Land Use / Land Cover Spatial and Attribute Information 40000 onLine 19990101 ground condition SJRWMD Spatial and Attribute Information The following steps were followed by the contractor, Avineon Inc. (formerly Agra-Baymont, Inc.), to create the 2000 layer. See contract specifications (District contract #SD418RA) for further details. 1. For each DOQQ, the photo interpreters will create a 2000 layer by modifying a copy of the 1995 layer according to: a) thematic changes dictated by updates to the PI Key and classification system, and b) thematic and boundary changes indicated by the 1999 DOQQs. 2. All mapping shall be from screen digitizing color-infrared (CIR) 3.75' Digital Orthophoto Quarter Quadrangles (DOQQ), in ArcInfo 8.1, with an adjacent stereoscope for inspecting the photography. 3. All mapping shall be conducted while consulting the ancillary data, primarily accessed through a separate ArcView interface. 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 photo interpreters have questions regarding appropriate classification, the primary photo interpreter shall contact the District project manager for further discussion of the problem. 5. The 2000 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 Attachment A, and are also incorporated in the PI Key. The contract was initiated Sept. 2000, work began October 2000, and work was completed June 2003. Photo interpretation Key revisions at the beginning and significant scope changes slowed the project down in its early phases. SJRWMD Data in this layer has been accepted as complete from the contractor, but is being reviewed by appropriate SJRWMD project staff as a substitute for field verification. Follow-up note: no significant revisions were required. SJRWMD 20030601 All deliverables were QA'ed by the SJRWMD photo interpretation specialist. Comments were sent to the contractor, who then revised the data accordingly. Also, the contractor made further edge matching changes and code checks before final submittal. SJRWMD 20030601 July 1, 2003 - Made available to all users via the custom ArcMap / ArcView SJR button. SJRWMD 20030701 In 2004, the SDE layer was modified in the following ways: 1. The original deliverables used the code 5340 (reservoirs less than 10 acres). All features with this code were changed to 5300 (reservoirs). 2. The code 1750 (Kennedy Space Center) was used erroneously throughout the District. Occurrences of 1750, except on Kennedy Space Center, were replaced with 1700. 3. Features were checked against our internal photo interpretation specialist's QA points; see v:\gis2\projects\lu\sd418\datareview\qapts.shp, still in that location as of 6/09/06. In cases where the deliverable did not match the QA points, the feature code was changed to match the QA point value. SJRWMD 20040101 SJRWMD GIS Data Manager (386)329-4500 gis_support@sjrwmd.com In March, 2006, it was discovered that between their existence as ArcInfo coverages and their conversion to ArcSDE features, 74 features that should have been classified as land cover/land use 6170, were inadvertently classified as land cover/land use 6300. These have been changed back. SJRWMD 20060321 The GeoPlan Center downloaded the original St. John River Water Management District datasets (see below) from the following FTP site on July 5th, 2013. ftp://secure.sjrwmd.com/disk6b/lcover_luse/luse2000/ lulc2000_alachua.zip lulc2000_baker.zip lulc2000_bradford.zip lulc2000_brevard.zip lulc2000_clay.zip lulc2000_columbia.zip lulc2000_desc.dbf lulc2000_duval.zip lulc2000_flagler.zip lulc2000_indian_river.zip lulc2000_lake.zip lulc2000_levy.zip lulc2000_marion.zip lulc2000_nassau.zip lulc2000_okeechobee.zip lulc2000_orange.zip lulc2000_osceola.zip lulc2000_polk.zip lulc2000_putnam.zip lulc2000_seminole.zip lulc2000_st_johns.zip lulc2000_st_lucie.zip lulc2000_sumter.zip lulc2000_union.zip lulc2000_volusia.zip Each county was downloaded and unzipped. Next the counties were merged to create one district wide layer. 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 lulc2000_desc.dbf and the district-wide layer based on the CODE field in the lulc2000_desc.dbf, and the LUCODE field in the shapefile. Once joined the layer was exported. in order to permanently append the lulc2000_desc.dbf table information. 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 N1* 4 Number 1000:__URB 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 N1* Deleted 1000:__URB LUCOD_DESC Additionally GeoPlan added and populated the following fields: LCCOD_DESC SOURCE SOURCE2 FLUCCS_L1 LEVEL1 FLUCCS_L2 LEVEL2 FLUCCS_L3 LEVEL3 FLUCCSCOMP ACRES DESCRIPT FGDLAQDATE AUTOID Next the records in the attribute table were UPPERCASED. - GeoPlan ran the Integrate Command at 1m, the Repair Geometry Command was then run to fix any geometry issues resulting from the Integrate procedure. - GeoPlan has removed the crocodile bracket symbols [ < and > ] from the LEVEL2, LEVEL3 and DESCRIPT fields, these symbols have been replaced by common round bracket symbols [ ( and ) ]. GeoPlan 20130705 Vector GT-polygon composed of chains 320224 NAD 1983 HARN Florida GDL Albers 24.0 31.5 -84.0 24.0 400000.0 0.0 coordinate pair 0.0001 0.0001 meter D North American 1983 HARN GRS 1980 6378137.0 298.257222101 LU_SJRWMD_2000 LU_SJRWMD_2000.DBF SJRWMD OBJECTID Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. Shape Feature geometry. ESRI Coordinates defining the features. 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.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 2000 Photointerpretation Key for more information. SJRWMD OTHER The following represents the original field from the source Water Management District Layer.SJRWMD = LCCODE - Land cover code. See SJRWMD 2000 Photointerpretation Key for more information. SJRWMD NOTES Descriptive comments. SJRWMD LUCOD_DESC SJRWMD land use classification FLUCCS code number and FLUCCS code description. SJRWMD LCCOD_DESC SJRWMD land cover classification FLUCCS code number and FLUCCS code description. SJRWMD SOURCE Water Management District of Coverage/Origin. GEOPLAN SOURCE2 Other contributing source; Avineon Inc. GEOPLAN FLUCCS_L1 The highest level (level 1) designation in a hierarchical coding scheme containing 4 levels. GEOPLAN LEVEL1 Level 1 land use description, based on the FDOT classification schema. GEOPLAN FLUCCS_L2 The second highest level (level 2) designation in a hierarchical coding scheme containing 4 levels. GEOPLAN LEVEL2 Level 2 land use description, based on the FDOT classification schema. GEOPLAN FLUCCS_L3 The third highest level (level 3) designation in a hierarchical coding scheme containing 4 levels. GEOPLAN LEVEL3 Level 3 land use description, based on the FDOT classification schema. GEOPLAN FLUCCSCOMP 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. GEOPLAN ACRES Number of Acres. GEOPLAN DESCRIPT Based on the field LUCOD_DESC, however, the classification numbers were removed from the front of each record. GEOPLAN FGDLAQDATE The date FGDL acquired the data from the Source. GEOPLAN AUTOID Unique ID added by GeoPlan GeoPlan SHAPE.AREA Area in meters GeoPlan SHAPE.LEN Perimeter in meters GeoPlan 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 Photo interpretation Key. The PI Key lists each class used in the 2000 land use / land cover layer, along with a detailed description, keys to photo interpretation, 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 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 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 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) 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 photo interpreter 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 The SJRWMD 2000 Land Cover / Land Use Photo interpretation Key See also: Florida Department of Transportation. 1999. Florida Land Use, Cover and Forms Classification System. Surveying and Mapping, Thematic Mapping Section, Tallahassee Florida. Florida Geographic Data Library (FGDL) mailing

431 Architecture PO Box 115706

Gainesville Florida 32611-5706 US Technical Support: http://www.fgdl.org/fgdlfeed.html For FGDL Software: http://www.fgdl.org/software.html Mailing list for FGDL: http://www.fgdl.org/fgdl-l.html FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html Web site: http://www.fgdl.org DOWNLOADABLE DATA 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 ARCE v8.2 ARC/INFO Export Format - UNIX Compression Winzip http://www.sjrwmd.com CD-ROM $40 per CD There is no charge for downloading data from the DISTRICT web site at http://www.sjrwmd.com. Data can be ordered on CD-ROM as instructed on the web site. 10 working days This data is intended for use with a Geographic Information Systems or Remote Sensing software package. 20200302 St. Johns River Water Management District GIS Data Manager, Information Resources Department mailing

P.O. Box 1429

Palatka FL 32178-1429 US (386)329-4500 gis_support@sjrwmd.com 0800-1700 EST FGDC Content Standard for Digital Geospatial Metadata FGDC-STD-001-1998 local time