Geodataset Name:       LU_SR_INDUSTRIAL_11
Geodataset Type:       SDE Feature Class
Geodataset Feature:    Polygon
Feature Count:         145

DATA SOURCE(S):                    Florida Department of Environmental Protection's Bureau of Watershed Restoration
SCALE OF ORIGINAL SOURCE MAPS:     12,000
GEODATASET EXTENT:                 Alachua County (Partial Coverage), Baker County (Partial Coverage), 
Bradford County, Columbia County, Dixie County, Gilchrist County, Hamilton County, 
Jefferson County (Partial Coverage), Lafayette County, Levy County (Partial Coverage), Madison County, 
Suwannee County, Taylor County, and Union County.

PUBLICATION DATE:                  20121217
TIME PERIOD OF CONTENT:            Begin Date: 20100101    End Date: 20110301
DOWNLOAD LINK:                     http://www.fgdl.org/metadataexplorer/explorer.jsp

FEATURE ATTRIBUTE TABLES:

Datafile Name: LU_SR_INDUSTRIAL_11.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
OBJECTID	Internal feature number.
Shape	Feature geometry.
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. SRWMD = LANDUSE_CODE - The primary classification type assignment. This may be either a land use classification or a land cover classification in the case that keys to identification indicate a physiographic feature. SRWMD uses an adopted classification scheme, for more information on the adopted classification scheme please the Attribute Overview Description Section.
OTHER	The following represents the original field from the source Water Management District Layer. SRWMD = SECONDARY_CODE - A secondary classification assigned to account for the fact that any given polygon may have more than one use or a use and a physiographic cover.
LANDUSE_DE	A brief definition of the class code: description of the primary land use or land cover.
SECONDARY2	A brief definition of the class code: description of the secondary land use or land cover.
SOURCE	Water Management District of Coverage/Origin.
SOURCE2	Agency of Origin: Florida Department of Environmental Protection's Bureau of Watershed Restoration.
FLUCCS_L1	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
LEVEL1	Level 1 land use description, based on the FDOT classification schema.
FLUCCS_L2	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
LEVEL2	Level 2 land use description, based on the FDOT classification schema.
FLUCCS_L3	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
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.
FLUCCSCOMP	A value of 1 in this field indicates a difference when comparing the FLUCCS code description to the FDOT FLUCCS code description.
ACRES	Number of Acres.
DESCRIPT	Based on the field LANDUSE_DE, however the classification numbers were removed from the front of each record.
FGDLAQDATE	The date FGDL acquired the data from the Source.
AUTOID	Unique ID added by GeoPlan
SHAPE.AREA	Area in meters
SHAPE.LEN	Perimeter in meters

The adopted classification scheme has resulted from the following process: 1. Potential classification types originally taken from Florida Department of Transportations "Florida Land use, cover and forms classification system" 2. Conformity with SJRWMD's classification system was sought whenever possible out of an interest in creating a data layer that would result in a product that was seamless in terms of its geometry and attribution with this contingent area. 3. Bureau of Watershed Restoration, Watershed Assessment Section (WAS) Managers reviewed a preliminary list for the purpose of identifying classification types that contributed to sources of pollution and those that allowed them to identify natural conditions that may have an effect on water quality impairment. This led to the removal of some classification types from the preliminary list to form a WAS wants list. 4. Photo interpreters reviewed the available photography for the purpose of determining which of the WAS wants list could and could not be classified. For example, the resolution of the imagery allowed a photointerpreter to confidently assign the level 3 class code of 2140: Row Crops to a polygon but not of any of the Level 4 codes (see next item). 5. The FLUCC's system is hierarchical; it includes four levels that build in terms of specificity: A Level 1 classification is the most general it is a four digit code in which the first integer in the code is assigned one of eight numbers; 1000 = Urban and Built up class, 2000 = Agricultural, 3000 = Rangeland, 4000 = Upland Forests, 5000 = Water, 6000 = Wetlands, 7000 = Barren Land and 8000 = Transportation, Communications, Utilities. The second integer (and each successive integer) provides a subclassification of a higher specificity. For example 2100 (Level II) Class is Crop and pasture land a subtype of the 2000 Agricultural class, 2150 (Level III) : Field Crops is a specific subtype of the 2100 Crop and pasture land subtype. Further, 2153 (Level iV) is a specific subtype of the 2150 class. Very few level 4 classifications have been chosen. This is so because discernment of the keys to classification for these classes typically require imagery of a higher resolution than our source imagery. The Level 4 designation is indicated in either the Land Use Code or Secondary Code Fields of the attribute table. 6. A few classification types were added to accommodate needs that were specific to the Water Management districts. Land Use Descriptions: 1110: MDC - LOW DENSITY, FIXED SINGLE FAMILY UNITS 1120: MDC - LOW DENSITY, MOBILE HOME UNITS 1130: MDC - LOW DENSITY, MIXED UNITS (FIXED AND MOBILE HOME UNITS) 1190: MDC - LOW DENSITY UNDER CONSTRUCTION 1210: MEDIUM DENSITY, FIXED SINGLE FAMILY UNITS 1220: MEDIUM DENSITY, MOBILE HOME UNITS 1230: MEDIUM DENSITY, MIXED UNITS 1290: MEDIUM DENSITY, UNDER CONSTRUCTION 1310: HIGH DENSITY, FIXED SINGLE FAMILY UNITS (> 6 DU/ACRE) 1320: HIGH DENSITY, MOBILE HOME UNITS 1330: HIGH DENSITY, MULTIPLE DWELLING UNITS, LOW RISE (THREE STORIES OR LESS) 1340: HIGH DENSITY, MULTIPLE DWELLING UNITS, HIGH RISE (FOUR STORIES OR MORE) 1350: HIGH DENSITY, MIXED UNITS (FIXED AND MOBILE HOME) 1390: HIGH DENSITY, UNDER CONSTRUCTION 1400: COMMERCIAL AND SERVICES 1423: JUNK YARDS 1454: CAMPGROUNDS 1460: OIL AND GAS STORAGE (EXCEPT ASSOCIATED WITH INDUSTRIAL USE OR MANUFACTURING) 1480: CEMETERIES 1490: COMMERCIAL AND SERVICES UNDER CONSTRUCTION 1510: FOOD PROCESSING 1520: TIMBER PROCESSING 1523: PULP AND PAPER MILLS 1530: MINERAL PROCESSING 1532: PHOSPHATE 1533: LIMEROCK 1540: OIL AND GAS PROCESSING 1550: OTHER LIGHT INDUSTRIAL 1551: BOAT BUILDING AND REPAIR 1552: ELECTRONICS 1560: OTHER HEAVY INDUSTRIAL (SHIP REPAIR, SHIP BUILDING, LARGE LUMBER MILLS) 1562: PRE-STRESSED CONCRETE PLANTS 1564: CEMENT PLANTS 1600: EXTRACTIVE 1613: STRIP MINES - HEAVY MINERALS 1620: SAND AND GRAVEL PITS 1631: LIMEROCK 1632: DOLOMITE 1633: PHOSPHATE 1650: MDC - RECLAIMED LANDS 1660: HOLDING PONDS 1700: ODC - INSTITUTIONAL ( EDUCATION, RELIGIOUS, HEALTH, MILITARY) 1730: MDC - MILITARY 1750: ODC - GOVERNMENTAL 1810: SWIMMING BEACH 1820: GOLF COURSES 1830: RACE TRACKS 1831: AUTOMOBILE TRACKS 1832: HORSE TRACKS 1840: MARINA'S AND FISH CAMPS 1850: ODC - PARKS AND ZOOS 1860: COMMUNITY RECREATIONAL FACILITIES 1890: OTHER RECREATIONAL (RIDING STABLES, GO CART TRACKS, SKEET RANGES) 1900: MDC - OPEN LAND 1910: UNDEVELOPED LAND WITHIN URBAN AREAS 1920: MDC - INACTIVE LAND WITH STREET PATTERNS BUT WITHOUT STRUCTURES 2110: IMPROVED PASTURES 2120: UNIMPROVED PASTURES 2130: WOODLAND PASTURES 2140: ROW CROPS 2150: FIELD CROPS 2153: HAY FIELDS 2210: CITRUS GROVES 2220: FRUIT ORCHARDS 2230: OTHER GROVES (PECAN, AVOCADO, COCONUT, MANGO ETC) 2300: RU - FEEDING OPERATIONS 2310: ODC - CATTLE FEEDING OPERATIONS 2320: ODC - POULTRY FEEDING OPERATIONS 2400: NURSERIES AND VINEYARDS 2410: TREE NURSERIES 2420: SOD FARMS 2430: ORNAMENTALS 2500: RU - SPECIALTY FARMS 2510: ODC - HORSE FARMS 2520: MDC - DAIRIES 2540: AQUACULTURE 2600: MDC - OTHER OPEN LANDS (RURAL) 2610: FALLOW CROP LAND 3100: RANGE LAND, HERBACEOUS (DRY PRAIRIE) 3200: SHRUB AND BRUSHLAND 3210: PALMETTO PRAIRIES 3220: COASTAL SCRUB 3300: MIXED RANGELAND 4100: UPLAND CONIFEROUS FORESTS 4110: PINE FLATWOODS 4120: LONGLEAF PINE - XERIC OAK 4130: SAND PINE 4140: PINE-MESIC OAK 4200: UPLAND HARDWOOD FORESTS 4210: XERIC OAK 4270: LIVE OAK 4280: CABBAGE PALM 4340: HARDWOOD CONIFEROUS - MIXED 4400: RU - TREE PLANTATIONS 4410: CONIFEROUS PLANTATIONS 4430: FOREST REGENERATION AREAS 5100: STREAMS AND WATERWAYS 5200: LAKES 5300: RESERVOIRS 5410: EMBAYMENTS OPENING DIRECTLY INTO THE GULF OF MEXICO OR THE ATLANTIC 5500: MAJOR SPRINGS 5600: RU - SLOUGH WATERS (CHANNELS OF SLOW MOVING WATER) 5720: GULF OF MEXICO 6100: WETLAND HARDWOOD FORESTS 6110: BAY SWAMPS 6120: MANGROVE SWAMPS 6130: GUM SWAMPS 6140: TITI SWAMPS 6150: STREAM AND LAKE SWAMPS (BOTTOMLAND) 6170: MIXED WETLAND HARDWOODS 6180: CABBAGE PALMS 6210: CYPRESS 6220: POND PINE 6250: HYDRIC PINE FLATWOODS 6300: WETLAND FORESTED MIXED 6410: FRESHWATER MARSHES 6420: SALTWATER MARSHES 6430: WET PRAIRIES 6440: EMERGENT AQUATIC VEGETATION 6460: MIXED SCRUB-SHRUB WETLAND 6500: NON-VEGETATED WETLANDS 6510: TIDAL FLATS 6540: OYSTER BARS 7100: BEACHES OTHER THAN SWIMMING BEACHES 7200: SAND OTHER THAN BEACHES 7400: RU - DISTURBED LANDS 7410: RURAL LAND IN TRANSITION WITHOUT POSITIVE INDICATORS OF INTENDED ACTIVITY 7420: BORROW AREAS 7430: SPOIL AREAS 7450: BURNED AREAS 8110: AIRPORTS 8120: RAILROADS 8130: BUS AND TRUCK TERMINALS 8140: ROADS AND HIGHWAYS 8160: CANALS AND LOCKS 8170: OIL, WATER OR GAS LONG DISTANCE TRANSMISSION LINES 8180: AUTO PARKING FACILITIES (WHEN NOT DIRECTLY RELATED TO OTHER LAND USE) 8200: COMMUNICATIONS 8310: ELECTRIC POWER FACILITIES 8320: ELECTRICAL POWER TRANSMISSION LINES 8330: WATER SUPPLY PLANTS (INCLUDING PUMPING STATIONS) 8340: MDC - SEWAGE TREATMENT 8350: ODC - SOLID WASTE DISPOSAL 8370: SURFACE WATER COLLECTION FEATURES 8390: UTILITIES UNDER CONSTRUCTION

USER NOTES:

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.

GeoPlan relied on the integrity of the attribute information within the original data. FDEP Accuracy Report: The creation of this layer involves photo interpretation; for this data layer the classification of the land surface into one or two of 170 types. It is the nature of interpretation that it involves the assessment of multiple sources of information, primarily the color, shape, pattern, horizontal size, vertical height, texture and context of features in a photograph and secondarily, information provided in ancillary data layers to arrive at a conclusive attribute assignment. Conclusion is a product of a weights-of-evidence analysis and as compared to direct measurement is subject to larger variability. Several staff were involved in the creation of this layer and an individual's skill at photo interpretation is a known variable among several affecting accuracy. In an effort to improve accuracy and limit variation between photo interpreters skills, the following methods were employed: 1. Sought photo interpreters who had several years of experience. 2. Provided like-training when at all possible 3. Held monthly field trips to "calibrate" photo features with real world features. 4. Assessed each photo interpreters work weekly to assure compliance with methodological rules 5. Randomly selected classified polygons and made field trips monthly to verify classifications, results were provided to Photo interpreters Largest variation occurred between 6170: Mixed Wetland Hardwoods and 6300: Wetland Forested Mixed classifications. It is difficult in some instances to distinguish between coniferous signatures and colors reflected from hardwoods that keep their leaves throughout the winter when photographs were flown. It too is labor intensive to accurately determine the proportion of hardwood versus coniferous trees in these mixed classifications when polygons can be quite large and access constraints because of private property postings are numerous so field verifications of these classifications yield information of limited value.

Classifications for the following Counties were based on imagery "flown" on the listed dates: (Alachua 4/3/2011), (Baker 1/2011), (Bradford 1/2011), (Columbia 2/4/2010), (Dixie 12/19-21/2010), (Gilchrist 12/19-21/2010), (Hamilton 4/1/2010), (Jefferson 1/4/2010), (Lafayette 12/19-21/2010), (Levy December 2010 ? January 2011), (Madison 4/1/2010), (Suwannee 3/30/2010), (Taylor 3/23/2010), (Union 1/2011)

Analyses of Land Use - Land Cover GIS information provide environmental scientists an understanding of the relationships between human activities, land surface physiography and water resources. Florida's landscape is quickly changing and as a result, at the time prior to this layer's creation, existing land use - land cover GIS layers for the Suwannee River area were out-of-date. A more current layer was needed to improve the accuracy of these analyses.

This data is provided 'as is' and its horizontal accuracy has not been verified by GeoPlan. FDEP Accuracy Report: Reported Horizontal accuracy is not better than the source imagery upon which this dataset has been developed. Source imagery is Florida's Ortho program imagery for a product developed at a 1 foot resolution; that meets or exceeds a verified horizontal accuracy of 7.6 feet at the 95% confidence interval (4.4 feet RMSE) as specified in the FGDC Geospatial Positioning Accuracy Standards, Part 3: National Standard for Spatial Data Accuracy (NSSDA).

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

Florida Department of Environmental Protection (FDEP) Projection Information and Data Disclaimer: FDEP GIS data is provided as a public service. FDEP makes every effort to provide accurate and complete data. Metadata is provided for all datasets and no data should be used without first reading and understanding the limitations of the data. The Florida Department of Environmental Protection (FDEP) provides NO WARRANTY as to the accuracy of this data or any corresponding attributes or metadata. Data is provided in an 'as is' condition, without warranty of any kind, either expressed or implied, including any assurance that the data is fit for a particular purpose. FDEP shall have no liability, in any case, to the use of provided data (including redistribution and reproduction). Full liability, responsibility and consequence relating to the use of provided data rest with the user. This data is intended to be used for general informational and planning purposes, and is not appropriate for legal and/or cadastral purposes.

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

REFERENCES:

Florida Department of Environmental Protection: Watershed Management http://www.dep.state.fl.us/water/watersheds/ Suwannee River Water Management District (SRWMD) http://www.srwmd.state.fl.us/

DATA LINEAGE SUMMARY:

1. The seed dataset was created by exporting all features of FDEP's SRWMD 2004 Land Use Land Cover SDE layer to a feature class Process Date: March 2009 2. Geodatabase schema was created allowing for the creation of a polygon edit feature class that contained coded domains for Landuse and Secondary code attributes and a new domain coded field that allowed for a photo interpreter to specify whether an individual polygon had been reviewed by them or not, whether the previously delineated polygon contained an error in the 2004 version or had a change as a result of some anthropogenic or natural activity, a point feature class that captured errors detected by the project's QA manager with coded domains defined for fields that allowed for communication between the QA manager and photo interpreters and a gridded polygon feature class that allowed the project team to track progress. Process Date: March 2009 3. All features created in step 1 were imported into the geodatabase created in step 2. Process Date: March 2009 4. The Geodatabase resulting from step 3 was copied into a predefined Geodatabase Schema, this was provided to OTIS/GIS and copied into a versioned enterprise Geodatabase (SDE Version 9.1, Oracle 9.2) Process Date: March 2009 5. Photo interpreters were assigned areas that they had created in the 2004 version and began the process of reviewing each individual polygon. In cases where no change was apparent in the newer imagery they updated the Status attribute field with a "yes" entry indicating that it had been reviewed. In cases where there was some change apparent, the geometry and attributes of the initial polygon were changed and the Status field attributed with a "change" entry. An "error" entry was indicated in those cases. Process Date: March through December 2009 6. Each Photo interpreters work was assessed by a Quality Assurance Manager weekly for adherence to minimum mapping unit and other feature capture and attribution guidelines. A point feature class within the database was populated with locations of these violations. Photo interpreters corrected errors and communicated this information back to the QA manager who in turn verified the repairs. Process Date: March through December 2009 7. A random sample was drawn from the population of polygons that had been delineated that month for field verification. The random sample of polygons were referred to as anchor polygons. A field verification team composed of two photo interpreters and the project manager navigated as closely as possible to each anchor polygon and then noted on paper maps of the area the appropriate code that matched field conditions, took photos of each polygon and GPS'ed a point representing the location of each polygon. An arc map project was created for each field trip that joined GPS coordinate, field verified code and hyperlinked photo. This information was compared to the photo interpreters office classification and feedback was provided to them in the form of a shapefile. Photo interpreters adjusted initial classifications appropriately and reviewed adjacent classifications to assure that like errors were corrected. Process Date: March through December 2009 8. Individual "framework" polygons that existed between each photointerpreters work were inspected for errors and repaired. Process Date: December 2009 9. All photointerpreter versions were reconciled and posted to a parent version. A new Geodatabase and feature dataset within were created using FDEP's standard datum and projection. A polygon feature class was created within the new feature dataset by importing all features from the parent version mentioned above. Process Date: December 2009 10. Topology checks (no Gaps or overlaps) were performed on the entire dataset. No violations found. Process Date: December 2009 11. Level 1, 2 and 3 fields were added to the dataset. Process Date: December 2009 12. Symbology was created by loading the 2004 SDE layer into an ArcMap document and then using symbology in this layer to define symbology in the new layer. Layer file exported. Process Date: December 2009 Added new layer in ArcSDE and published in DataCatalog/DataMiner and MapDirect Process Date: 20100105 Layer has been reviewed for classification errors and updated for improved accuracy. August 2011. Process Date: 20110829 Dataset revision completed using the 2010 and 2011 aerial photography. Process Date: Obtained SRWMD Land Use 2010-2011 data from Ron Hughes and inserted in ArcSDE/DataMiner and MapDirect. Process Date: 20121217 The GeoPlan Center received the original dataset SRWMD_LANDUSE_2010_2011.shp from the Florida Department of Environmental Protection's Bureau of Watershed Restoration via FTP on March 6th, 2013. The dataset was originally in the FDEP Albers projection which matched the FGDL Albers projection so the FDEP .prj file was swapped out for the FGDL .prj file. Next the records in the attribute table were UPPERCASED. Below is the original FDEP SRWMD file structure: ITEM NAME WIDTH TYPE Shape 0 Geometry OID_ 4 Integer LANDUSE_CODE 4 Integer SECONDARY_CODE 4 Integer LANDUSE_DESCRIPTION 85 String SECONDARY_DESCRIPTION 85 String LEVEL_1_LANDUSE 4 String LEVEL_2_LANDUSE 4 String LEVEL_3_LANDUSE 4 String OBJECTID 4 OID Below is the crosswalk table between the original file structure and the new file structure: ORIGINAL NAME NEW NAME Shape Same OID_ Deleted LANDUSE_CODE FLUCCS SECONDARY_CODE OTHER LANDUSE_DESCRIPTION LANDUSE_DE SECONDARY_DESCRIPTION SECONDARY2 LEVEL_1_LANDUSE FLUCCS_L1 LEVEL_2_LANDUSE FLUCCS_L2 LEVEL_3_LANDUSE FLUCCS_L3 OBJECTID Deleted Additionally GeoPlan added and populated the following fields: SOURCE SOURCE2 LEVEL1 LEVEL2 LEVEL3 FLUCCSCOMP ACRES DESCRIPT FGDLAQDATE Process Date: 20130306 Dataset copied. Process Date: 20130314 The following SDE spatial view command was run: sdetable -o create_view -T LU_SR_INDUSTRIAL_11 -t "LU_WMDWMD_2011" -c "*" -w "FLUCCS >= 1500 and FLUCCS < 1600" Process Date: 20130314

MAP PROJECTION PARAMETERS:

Projection                          ALBERS
Datum                               HPGN
Units                               METERS
Spheroid                            GRS1980
1st Standard Parallel               24  0  0.000
2nd Standard Parallel               31 30  0.000
Central Meridian                   -84 00  0.000
Latitude of Projection's Origin     24  0  0.000
False Easting (meters)              400000.00000
False Northing (meters)             0.00000

DATA SOURCE CONTACT (S):

Name:
Abbr. Name:
Address:


Phone:

Web site:
E-mail:
Contact Person:
         Phone:
        E-mail:

Florida Department of Environmental Protection (FDEP) OTIS/GIS Section
FDEP
2600 Blair Stone Rd
Tallahassee, Florida
32399-2400
(850)245-8537


http://publicfiles.dep.state.fl.us/otis/gis/data/srwmd_landuse_2010_2011.zip
Joe.North@dep.state.fl.us
Joe North

Name:                   FLORIDA GEOGRAPHIC DATA LIBRARY
Abbr. Name:             FGDL
Address:                Florida Geographic Data Library
                        431 Architecture Building
                        PO Box 115706
                        Gainesville, FL  32611-5706
Web site:               http://www.fgdl.org

Contact FGDL: 

      Technical Support:	        http://www.fgdl.org/fgdlfeed.html
      FGDL Frequently Asked Questions:  http://www.fgdl.org/fgdlfaq.html
      FGDL Mailing Lists:		http://www.fgdl.org/fgdl-l.html
      For FGDL Software:                http://www.fgdl.org/software.html