This dataset includes land use for only parts of the following counties: Alachua, Brevard, Charlotte, Highlands, Levy, Okeechobee, Orange, Osceola, Polk
Because there is no data from SFWMD, SRWMD or NWFWMD, there are several counties in the panhandle that don't have data for this layer. In these cases you will need to get LU00 and/or LU95. In addition, because WMD boundaries do not follow county boundaries, there are some counties in the north eastern part of the state that have partial data.
No data available: Dixie, Gilchrist, Suwannee, Hamilton, Lafayatte, Taylor, Madison, Jefferson, Wakulla, Leon, Franklin, Liberty, Gadsden, Gulf, Calhoun, Jackson, Bay, Washington, Homes, Walton, Okaloosa, Santa Rosa, Escambia, Martin, Palm Beach, Broward, Miami-Dade, Monroe, Collier, Lee, Hendry, Glades.
Partial Coverage: Levy, Alachua, Bradford, Union, Columbia, Orange, Osceola, Polk, Highlands, Charlotte, Okeechobee, St Lucie
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>
SWFWMD: www.swfwmd.state.fl.us
SJRWMD Logical Consistency Report:
Primary ancillary layers 2004 DOQQs SSURGO soils County parcels SJRWMD wetlands
Other ancillary layers 1999 DOQQs 1994 DOQQs 1984 digital photography
Mapping procedure Copy of 1999 layer is the input District divided into 10 mapping phases Progress monitored / measured by quarterquad (SDE status layer) Photointerpreters (PIs) work on independent quarterquads that are adjacent to encourage consistency Onscreen, ArcGIS editing Geodatabase: SDE layer SDE Versions created for each of the two editors Editor versions reconciled daily against default Attribute domains for LUCODE and LCCODE Includes fields for editor and edit date; scripts populate these fields automatically Editing process: map topology, not geodatabase topology. A cluster tolerance of 0.05 meters to be used emphasis on accuracy at 1:12,000 scale, even though the data look good enough to focus on larger scale No sliver polygons shall exist No overlapping polygons No gaps No label errors shall exist. No dangles shall exist. No intersection errors shall exist.
SJRWMD Completeness Report:
Minimum Mapping Units (see also the PI Key for additional guidelines) 1. Upland Classes (FLUCCS Codes of 1000, 2000, 3000, 4000, 7000, 8000) - 2 acres 2. Water and Wetland Classes (FLUCCS Codes of 5000 and 6000) - 0.5 acres 3. Special Cases a. Rivers - Rivers and canals shall be delineated where they are approximately 10 meters or greater in width and can be mapped as continuous features. b. Roads and Railroads - All major transportation corridors shall be mapped. Major transportation corridors shall include all US and State Routes identified on United States Geological Survey (USGS) 7.5 minute topographic quadrangle maps and all other roadways with at least four lanes and a substantial median. c. Utility Corridors - Utility corridors shall be delineated where they are approximately 30 meters or greater in width.
Each 1:24,000 quarter quadrangle, within the District, was plotted out two times; once with the existing 1999 land use/cover linework, attribute and the 1999 doqq and a second with the 1999 land use/cover, attribute and the 2004 1M digital aerial photography. The plots were plotted out at a scale of 1:8000.
Changes that occurred with the land use or cover between the 1999 and 2004 study were documented on the 1:8000 plot using a green marker. Linework or labels that were to be removed were indicated by placing a series of "x" over the linework to be deleted. New linework and labels were delineated as a solid line. Only areas of change between 1999 and 2004 were delineated. The 1999 land use/cover was assumed to be corrected.
The 2004 land use/cover map standards remained the same as the 1999 land use: must fit feature boundaries at a scale of 1:12,000, minimum mapping unit of .5 acres for wetlands and 5 acres for uplands. The FDOT's Florida Land Use, Cover and Forms Classification System (FLUCCS) was used to classify all features.
Ancillary data sources were used to the fullest extent to ensure proper delineation of land use/cover features. These data sources included: 1984, 1990, 1994/1995 color infrared aerial photography; 1990 and 1995 land use/cover, National Wetlands Inventory 1:24,000 maps, NRCS county soil surveys and SWFWMD aerial mapping sheets. Any features that could not be reliably interpreted were field reviewed.
Versioning and disconnected editing functions were implemented for the digital update process. From the default SDE version of the 2004 land use data, a QC1 version was created. QC2 was then created from the QC1 version. From the QC2 version, disconnected edit versions were created by each editor. Edits are performed on the editor versions and when finished are checked back in to the QC2 version. Any conflicts between QC2 and editors' versions are resolved by accepting the edit changes, or keeping the original linework in QC2. QC2 is subsequently reconciled to QC1. QC1 subsequently reconciled to Default. Any conflicts are resolved. All child versions are deleted and the database is compressed. QC1 and QC2 are re-created and the process is kept going.
Land use and land cover features were delineated, on screen, using the 2004 1M digital aerial photographs as a back drop. Edits were made, using heads-up digitizing in ArcMap, on the feature class in the personal geodatabase created with the disconnected edit function. Linework and labels were added, deleted or reshaped according to the corrections delineated on the interpreted image plots. Topology Rules, no overlaps and no gaps, were created and verified on the personal geodatabase.
The following steps were conducted onsite by staff of Kyra InfoTech, Inc, to create the 2004 layer. See Statement of work and purchase order specifications (District Purchase order # PO038177) for further details. 1. For each DOQQ, the photointerpreters will create a 2004 layer by modifying a copy of the 2000 layer according to thematic and boundary changes indicated by the 2004 DOQQs.
2. All mapping shall be from screen digitizing color-infrared (CIR) 3.75' Digital Orthophoto Quarter Quadrangles (DOQQ), in ArcGIS 9, with an adjacent digital stereo capable imagery and software for inspecting the digital imagery.
3. All mapping shall be conducted while consulting the ancillary data. 4. All classification will be in keeping with specifications listed in the PI Key. If the PI Key is unclear or incorrect, or if the photointerpreters have questions regarding appropriate classification, the internal District photointerpreter will make the decision.
5. The 2004 layer will have two land use classification items: LCCODE and LUCODE. LCCODE will be used for land cover, while LUCODE will be used for land use; item values will differ only when land use and land cover for any given polygon differ. Detailed guidelines for application of this dual coding scheme are discussed in the PI Key.
The contract was initiated Sept. 2004, work began November 2004, and work Sept 2006. Adapting the use of Geodatabase for update and editing of data as well as technical issues with software and hardware slowed the project down in its early phases.
All phases were QA'ed by the SJRWMD photointerpretation specialist. Comments were sent to the photointerpreter(s) who then revised the data accordingly.
Spatial data was checked for topology errors against the following rules:
No gaps between polygons No overlapping polygons
A cluster tolerance of 0.05 meters was used.
Where substantial overlaps or gaps existed, an SJRWMD photointerpretation specialist was consulted and the errors corrected.
The Land Use/Land Cover code combinations were checked for all features against the modified FLUCCS code. Illegal code combinations were corrected.
The landuse/land cover data in quarter quad areas around the periphery of the SJRWMD boundary were checked for completeness. If changes to the LULC data for the quarter quad were a result of changes to features shared by complete, neighboring quarter quad data, the features for the quarter quad in question were clipped and deleted.
SJRWMD (<http://sjr.state.fl.us/index.html>) SWFWMD (<http://www.swfwmd.state.fl.us>)
The data was downloaded in shapefile format. Data from SJRWMD was in Universal Transverse Mercator (UTM), Zone 17, NAD83-90 (HPGN), meters. Data from SWFWMD was in Universal Transverse Mercator (UTM), Zone 17, NAD83-90, meters.
Each dataset was then projected to FGDL Albers HPGN. The shapefiles were then appended into a statewide layer using ArcGIS 9.1.
There was some overlap in the land use layers before merging them together. Any place there was overlap the following hierarchy was used in this order: SWFWMD, SJRWMD, SFWMD.
The layer was then loaded to SDE exported to shapefile and clipped to county boundaries. In some cases there were counties that had very small amounts of data and also fell outside either SJRWMD or SWFWMD. In these cases the data was not included. The following counties fell into this category: St Lucie, Union, Lee, Glades, Columbia, Bradford
*** SJRWMD - LUCODE VS. LCCODE *** Each feature is required to have two attributes, one emphasizing land cover (LCCODE) and the second land use (LUCODE). In most cases, these two values are the same. They differ in a minority of cases where separate cover and use values are required in order to adequately describe the mapping unit. The result is a map with dual codes. The LCCODE attribute can be used (mapped, queried, etc.) alone for a land cover emphasis; LUCODE can be used alone for a land use emphasis; or both can be used together.
Any polygon described by the following LUCODE values must be assigned a different LCCODE value: 1180 - Rural residential (2-5 acres per dwelling unit) 1650 - Reclaimed mining lands 1670 - Abandoned mining lands 1900 - Open land (urban) 1920 - Inactive land with street pattern but no structures (urban) 2600 - Other open lands (rural)
Any polygon described by the following LCCODE values must be assigned a different LUCODE value: 8340 - Wastewater treatment 8360 - Other treatment ponds (non-sewage). In this case, the LUCODE must be populated with the associated land use or purpose of the ponds, e.g. dairy (2520) or cattle feeding operation (2310).
Polygons described by the following LUCODEs may at the discretion of the photointerpreter have differing values for LUCODE and LCCODE: 1700 - Institutional 1730 - Military 1750 - Governmental (Kennedy Space Center only) 1800 - Recreational 1850 - Parks and zoos 2240 - Abandoned tree crops 2310 - Cattle feeding operations 2320 - Poultry feeding operations 2500 - Specialty farms 2510 - Horse farms 2520 - Dairies 8350 - Solid waste disposal