St. Johns River Water Management District 19900101 vector digital data Palatka, Florida St. Johns River Water Management District St. Johns River Water Management District: Alachua County (Partial Coverage), Baker County (Partial Coverage), Bradford County (Partial Coverage), Brevard County, Clay County, Columbia County (Partial Coverage), 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://www.sjrwmd.com/disk6a/lcover_luse/luse1990/ This dataset contains 1990 Land Use Land Cover data for the St. Johns River Water Management District (SJRWMD) Region. Land use and land cover in the SJRWMD Region is based on 1986-1989 black and white aerial photography (1:24,000). 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 Land Acquisition, Land Management, Water Supply Planning, Floodplain Management, and Surface and Ground Water Quality Monitoring. Most of the data was photo-interpreted from 1:24,000 scale black and white aerial photography captured between 1986 and 1989. Lake County was interpreted from 1:24,000 color infrared photography. The photography dates vary by county, see below. Calendar date: 1988 - Alachua County Calendar date: 1989 - Baker County Calendar date: 1987 - Bradford County Calendar date: 1989 - Brevard County Calendar date: 1987 - Clay County Calendar date: 1988 - Indian River County Calendar date: 1987 - Lake County Calendar date: 1989 - Marion County Calendar date: 1989 - Nassau County Calendar date: 1986 - Okeechobee County Calendar date: 1989 - Putnam County Calendar date: 1989 - Seminole County Calendar date: 1988 - St. Johns County Calendar date: 1988 - Volusia County 19860101 19890101 ground condition Complete None planned -82.502935 -80.206957 30.836789 27.453837 None Land Use Land Cover ISO 19115 Topic Category imageryBaseMapsEarthCover None St. Lucie County Bradford County Orange County Okeechobee County Alachua County Putnam County Lake County Duval County Indian River County Levy County Florida Seminole County Polk County Union County Nassau County Brevard County Volusia County Osceola County Baker County Marion County Flagler County St. Johns County Sumter County Clay County None 1989 - Putnam County 1986 - Okeechobee County 1987 - Bradford County 1989 - Brevard County 1989 - Seminole County 1988 - Indian River County 1989 - Marion County 1987 - Lake County 1988 - Alachua County 1988 - Volusia County 1988 - St. Johns County 1987 - Clay County 1989 - Baker County 1989 - Nassau County 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 32178-1429 US (386) 329-4500 gis_support@sjrwmd.com 0800 - 1700 EST St. Johns River Water Management District Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595 St. Johns River Water Management District http://www.sjrwmd.com/ GeoPlan relied on the integrity of the attribute information within the original data. This data is provided 'as is'. GeoPlan relied on the integrity of the original data layer's topology This data is provided 'as is' by GeoPlan and is complete to our knowledge. SJRWMD: The minimum mapping units are 0.5 acres for wetland categories and 2.0 acres for all other categories. District coverage is nearly complete: After this data layer was developed, a more accurate District boundary data layer was created. The 1990 land use data does not extend fully to the new boundary layer in some areas. However, the data has been interpreted and exists in analog (hard copy) format in the Division of GIS. Original quad units in the southwest corner of Lake County have land use past the District boundary to the county boundary. These are available from archives and are named LULAKE<###>, where ### is the old, 3-digit SJRWMD quad naming convention. This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlan SJRWMD: A specific accuracy report is not available; however, comparison of this data with subsequent DOQQs illustrates that this layer has greater horizontal positional inaccuracy than land use / land cover layers generated from the DOQQs. This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan Most of the data was photo-interpreted from 1:24,000 scale black and white aerial photography captured between 1986 and 1989. Lake County was interpreted from 1:24,000 color infrared photography. Photo-interpretation occurred in the following manner: The source photography was examined using stereoscopes. Zoom transfer scopes were used to delineate polygons and transfer linework to mylars. The mylars were then digitized. 24 onLine SJRWMD Spatial and Attribute Information Revisions completed by Division of GIS staff: - Staff updated this metadata file by adding previously unlisted FLUCCS codes that are found in the data layer. - In the original coverage, when dual LUCODE / LUCODE2 coding was employed, the land use (e.g. military or recreation) was listed in LUCODE and the land cover (e.g. wetland or forest) was listed in LUCODE2. However, the majority of users are more interested in land cover than land use. Therefore, where both codes were nonzero, GIS staff switched LUCODE and LUCODE2 for the following LUCODE values: 1700, 1720, 1730, 1750, 1800, 1850, 1900, 1920, and 8320. SJRWMD Feature attributes were verified by the Division of Environmental Sciences. Check plots were generated from the digital data and compared against the original aerial photos. Topological verification and error correction tasks were undertaken by the Division of GIS. The Indian River Lagoon (IRL) data were more intensively field checked than the rest of the District. SJRWMD This dataset was projected from State Plane, East Zone, NAD 1927 to UTM, Zone 17, NAD 1983, 1990 Correction. This dataset was copied to double precision. SJRWMD This data layer was developed under two contracts. The bulk of the Indian River Lagoon (IRL) basin, from just north of Cape Canaveral to the Indian River County / St. Lucie County line, was developed under contract #90G185. The rest of the District was developed under contract #90B182. See the browse graphic luse1990+fit.gif for an illustration of the spatial extent of the IRL contract. Some of the 7.5 minute quad units which intersect the IRL basin boundary were partially interpreted by both contractors. These quads have been merged, and because of the differences in photo-interpretation, the polygons along the IRL basin boundary may not match well. SJRWMD Division of GIS staff revised LUCODE values for 1.2% of the total polygons, representing 0.5% of the total area: 1. Added an item REV to the attribute table identifying polygons that were revised. A value of A indicates an attribute change only (LUCODE or LUCODE2); no arcs were revised. 2. Submerged aquatic vegetation: Moved submerged aquatic vegetation codes (6450) to LUCODE2 and populated LUCODE with the appropriate water body code. 3. Commercial and Services: Collapsed all 1400 level 3 codes other than 1460 and 1480 into 1400. 4. Institutional: Collapsed all 1700 level 3 codes other than 1730 and 1750 into 1700. 5. Extractive: Revised codes 1650-1670 to be consistent with FLUCCS and the rest of the state. 6. Fixed miscellaneous erroneously coded polygons. A complete and detailed listing of the changes is available upon request, as well as summary files listing the frequency and total area of each land use class before and after the revisions. SJRWMD Data inserted into SDE SJRWMD 20020219 The GeoPlan Center downloaded the original St. Johns River Water Management District 1990 Land use and land cover datasets (see below) via FTP (see below) on June 3rd, 2011. ftp://www.sjrwmd.com/disk6a/lcover_luse/luse1990/ lulc1990_alachua.zip lulc1990_baker.zip lulc1990_bradford.zip lulc1990_brevard.zip lulc1990_clay.zip lulc1990_columbia.zip lulc1990_duval.zip lulc1990_flagler.zip lulc1990_indian_river.zip lulc1990_lake.zip lulc1990_levy.zip lulc1990_marion.zip lulc1990_nassau.zip lulc1990_okeechobee.zip lulc1990_orange.zip lulc1990_osceola.zip lulc1990_polk.zip lulc1990_putnam.zip lulc1990_seminole.zip lulc1990_st_johns.zip lulc1990_st_lucie.zip lulc1990_sumter.zip lulc1990_union.zip lulc1990_volusia.zip Each county was downloaded and unzipped. The datasets were originally in the following projection. NAD_1983_HARN_UTM_Zone_17N GeoPlan reprojected the datasets to the FGDL Albers projection. Next GeoPlan Merged all the datasets together to create one district-wide layer. Below is the original district-wide SJRWMD file structure: ITEM NAME Shape LUCODEDESC LUCODE LUCODE2 REV SQ_METER OBJECTID SHAPE_AREA SHAPE_LEN Below is the crosswalk table between the original file structure and the new file structure: ORIGINAL NAME NEW NAME Shape Same LUCODEDESC Same LUCODE FLUCCS LUCODE2 OTHER REV Same SQ_METER ACRES OBJECTID Deleted SHAPE_AREA Deleted SHAPE_LEN Deleted Additionally GeoPlan added and populated the following fields: SOURCE SOURCE2 LEVEL1 LEVEL2 LEVEL3 FLUCCSCOMP ACRES DESCRIPT FGDLAQDATE Next GeoPlan renamed the dataset to LU_SJRWMD_1990 in order to match the LU naming schema used in FGDL. Next GeoPlan ran the Integrate GeoProcessing Tool at a tolerance of 1m, in order to remove any sliver polygons. Next GeoPlan ran the Repair Geometry GeoProcessing Tool 3x, in order to repair any geometry issues cause by the Integrate process. For LUCODE numbers that did not have a LUCODEDESC, the GeoPlan Center converted the original FLUCCS level three code to a FLUCCS level two code. Example: A code with a value of 9990 was converted to 9900. These alter attributes can be found by searching for the value 1 in the FLUCCSCOMP field. Finally the records in the attribute table were UPPERCASED. GeoPlan 20110603 Vector GT-polygon composed of chains 284584 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_1990 LU_SJRWMD_1990.DBF GeoPlan 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, LUCODE. GeoPlan OTHER The following represents the original LUCODE2 field from the source Water Management District Layer. GeoPlan LUCODEDESC Character description of the LUCODE, Land use / land cover description. GeoPlan REV Revision code SJRWMD SOURCE Water Management District of Coverage/Origin. GeoPlan SOURCE2 Other contributing source. 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. 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. 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 field LUCODEDESC. 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). All Indian River Lagoon basin data are classified to Florida Land Use Cover Classification Scheme (FLUCCS) level three. The rest of the data layer is classified using a mixture of modified FLUCCS level two, three, and four codes. The INFO item definitions are identical, but there are differences in the land use coding. The following table represents all codes that may be present for LUCODE or LUCODE2. If an LUCODE is not present in the list below, it may be an erroneous code. Special notes regarding the LUCODE list below: * - denotes LUCODEs that were not in the original SJRWMD-modified FLUCCS code list. Originally, SJRWMD staff concluded that these land uses could not be reliably identified on black and white aerial photography, and therefore did not include them in the contract specifications. However, they are legitimate FLUCCS codes and the contractors chose to use them in their land use interpretation. Users of this data may wish to instead use the next general level of coding (e.g. 1100 instead of 1110) if accuracy is critical, especially outside the Indian River Lagoon basin, where ancillary data and field checking were not as widely used. # - denotes LUCODEs that were either created or modified by the contractor for the IRL basin. These codes are only found in the IRL basin. ST. JOHNS RIVER WATER MANAGEMENT DISTRICT MODIFIED FLUCCS CLASSIFICATION SYSTEM - 1990 1000 URBAN AND BUILT-UP 1100 Residential, Low Density - Less than two dwelling units per acre. * 1110 - fixed single family units * 1120 - mobile home units * 1130 - mixed units (fixed and mobile home units) * 1190 - low density under construction 1200 Residential, Med. Density - Two to five dwelling units per acre. * 1210 - fixed single family units * 1220 - mobile home units * 1230 - mixed units (fixed and mobile home units) * 1290 - medium density under construction 1300 Residential, High Density * 1310 - fixed single family units (six or more dwelling units per acre) * 1320 - mobile home units (six or more dwelling units per acre) * 1330 - multiple dwelling units, low rise (two stories or less) * 1340 - multiple dwelling units, high rise (three stories or more) * 1350 - mixed units (fixed and mobile home units) * 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 1500 Industrial 1510 - food processing 1520 - timber processing (sawmills, plywood and veneer mills, pole peeler and treatment plants, wood distillation, log home pre-fabrication, and wood yards) 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 (includes 1564, cement plants) 1563 - metal fabrication plants * 1564 - cement 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 * 1631 - limerock 1632 - limerock or dolomite 1633 - phosphates 1634 - heavy minerals 1640 - oil and gas fields 1650 - reclaimed lands 1660 - holding ponds 1670 - abandoned lands 1700 Institutional 1730 - military 1750 - governmental: use the level II classification code (Institutional) for city halls, court-houses, police stations, office buildings, and post offices. 1800 Recreational 1810 - swimming beach 1820 - golf course 1830 - race tracks 1840 - marinas and fish camps (IRL basin: independent boat ramps also) 1850 - parks and zoos * 1860 - community recreational facilities 1870 - stadiums (those facilities not associated with high schools, colleges, or universities) * 1880 - historical sites * 1890 - other recreational (riding stables, go-cart tracks, etc.) 1900 Open Land * 1910 - undeveloped land within urban areas 1920 - inactive land with street pattern but without structures * 1930 - urban land in transition without positive indicators of intended activity * 1940 - other open land 2000 AGRICULTURE 2100 - Cropland and Pastureland 2110 - improved pastures 2120 - unimproved pastures 2130 - woodland pastures 2140 - row crops 2141 - potatoes and cabbage 2150 - field crops 2160 - mixed crops: used if crop type cannot be determined 2200 - Tree Crops 2210 - citrus groves * 2220 - fruit orchards * 2230 - other groves (pecan, avocado, mango, etc.) # 2240 - abandoned tree crops 2300 - Feeding Operations 2310 - cattle feeding operations 2320 - poultry feeding operations * 2330 - swine feeding operations 2400 - Nurseries and Vineyards 2410 - tree nurseries * 2420 - sod farms 2430 - ornamentals 2431 - shade ferns 2432 - hammock ferns * 2440 - vineyards 2450 - floriculture * 2460 - timber nursery 2500 - Specialty Farms 2510 - horse farms 2520 - dairies * 2530 - kennels 2540 - aquaculture * 2590 - other 2600 - Other Open Lands - Rural 2610 - fallow cropland 3000 RANGELAND 3100 - Herbaceous 3200 - Shrub and Brushland * 3210 - palmetto prairies * 3220 - coastal scrub * 3290 - other shrubs and brush (IRL basin: generally used in disturbed habitats) 3300 - Mixed Rangeland 4000 UPLAND FORESTS 4100 - Upland Coniferous Forests 4110 - pine flatwoods 4120 - longleaf pine - xeric oak 4130 - sand pine * 4140 - pine - mesic oak * 4190 - other pines 4200 - Upland Hardwood Forest (4200 - 4399) * 4210 - xeric oak * 4220 - brazilian pepper * 4230 - oak - pine - hickory * 4240 - melaleuca # 4250 - temperate/tropical hardwood * 4260 - tropical hardwood * 4270 - live oak * 4280 - cabbage palm * 4290 - wax myrtle - willow 4300 - Upland Hardwood Forest continued 4310 - beech - magnolia * 4320 - sand live oak * 4330 - western everglades hardwood 4340 - upland mixed coniferous/hardwood * 4350 - dead trees 4370 - australian pine * 4380 - mixed hardwoods * 4390 - other hardwoods 4400 - Tree Plantations 4410 - coniferous pine * 4420 - hardwood plantations 4430 - forest regeneration * 4440 - experimental tree plots * 4450 - seed plantations 5000 WATER 5100 - streams and waterways 5200 - lakes * 5240 - lakes less than 10 acres (4 hectares) which are dominant features # 5250 - open water within a freshwater marsh 5300 - reservoirs 5340 - reservoirs less than 10 acres (4 hectares) which are dominant features 5400 - bays and estuaries * 5410 - embayments (opening directly into the Gulf of Mexico or Atlantic Ocean) * 5420 - embayments (not opening directly into the Gulf of Mexico or Atl. Ocean) # 5430 - enclosed salt water ponds within a salt marsh 5500 - major springs 5600 - slough waters 6000 WETLANDS 6100 - wetland hardwood forests 6110 - bay swamps * 6120 - mangrove swamps * 6130 - gum swamps * 6140 - titi swamps 6150 - river/lake swamp (bottomland) * 6160 - inland ponds and sloughs * 6170 - mixed wetland hardwoods # 6180 - cabbage palm savannah 6200 - wetland coniferous forest 6210 - cypress * 6220 - pond pine # 6230 - southern red cedar * 6240 - cypress - pine - cabbage palm 6300 - wetland forested mixed 6400 - vegetated non-forested wetlands 6410 - freshwater marshes 6420 - saltwater marshes 6430 - wet prairies 6440 - emergent aquatic vegetation 6450 - submergent aquatic vegetation 6460 - mixed scrub-shrub wetland (predominately willow and wax myrtle) 6500 - non-vegetated wetland * 6510 - tidal flats * 6520 - shorelines (zone between low tide mark and the farthest point inland to which wave action transports beach materials; beaches are not included here) * 6530 - intermittent ponds * 6540 - oyster bars 7000 BARREN LAND 7100 - beaches other than swimming beaches 7200 - sand other than beaches 7300 - exposed rocks 7400 - disturbed land: use level II classification code for rural land in transition, fill areas (highways and railways), burned areas 7410 - rural land in transition without positive indicators of intended activity 7420 - borrow areas 7430 - spoil areas * 7440 - fill areas (highways, railways; IRL basin: barren areas along causeways) 8000 TRANSPORTATION, COMMUNICATION AND UTILITIES 8100 - Transportation 8110 - airports 8120 - railroads 8130 - bus and truck terminals 8140 - roads and highways: only four lane divided highways with medians 8150 - port facilities: use level III classification code for passenger terminals, ship chandlers, port administration and port services as well as facilities under construction * 8152 - piers * 8153 - terminals (cargo) * 8155 - relair facilities * 8156 - shipyards 8160 - canals and locks * 8170 - oil, water, or gas long distance transmission lines 8180 - auto parking facilities (when not directly related to other land uses) 8190 - transportation facilities under construction 8191 - highways 8192 - railroads 8193 - airports 8194 - port facilities * 8195 - pipelines 8200 - Communications * 8210 - transmission towers (microwave towers) * 8220 - communication facilities * 8290 - communication facilities 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 - treatment ponds (non-sewage) 8390 - utilities under construction Florida Geographic Data Library (FGDL) mailing

431 Architecture PO Box 115706

Gainesville Florida 32611-5706 US For FGDL Software: http://www.fgdl.org/software.html Technical Support: http://www.fgdl.org/fgdlfeed.html FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html Web site: http://www.fgdl.org Mailing list for FGDL: http://www.fgdl.org/fgdl-l.html 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 20200303 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