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>
The locations of archaeological sites, historic structures, unmarked human burials, cemeteries, and other cultural features contained in this (and other) Florida Master Site File data layers are for resource management, law enforcement, and research purposes only.
The original location information is based on field reports and address data which have been submitted to the Florida Master Site File by many and varied individuals, groups, institutions, and cultural resource firms. Submissions to the Site File are sometimes accepted from amateurs as well as professionals. The accuracy of submitted information cannot always be verified.
The address matching was carried out using the geocoding function of ArcView 3.0a. Addresses were matched against the ESRI U.S. Street Database(1997). The line data for the ESRI database (based on Tiger line data) was digitized at a 1:100,000 scale. Due to the small scale and numerous attribute errors in the reference street data, the geocoding process resulted in typical positional errors (as spot-checked against surveyor provided maps) of 20 to 100 meters with occasional larger errors possible. In some cases this results in a structure location point appearing on the wrong side of the street or in the wrong block when displayed against a scanned 1:24,000 USGS quadrangle. It is recommended that the data user compare the locations of the address matched structures to the ESRI U.S. Street Database and other background layers(such as scanned quads) to most accurately interpret locational information.
Not all structures and addresses adequately matched the ESRI U.S. Street Database. Structures which did not address match were on-screen digitized in ArcView 3.0a, 3.1 and 3.2 using scanned, georeferenced (geographic coordinates, NAD27) USGS 1:24,000 quadrangles as a background. Location information for these structures was culled from a variety of sources, including: surveyor-provided maps (the vast majority fall into this category), verbal location descriptions included on the site form, commercially available street atlases, county road maps, county property appraiser databases, city directories, and direct telephone contact with surveyors or property owners. The accuracy of the digitized locations is, in general, somewhat better than that of the address matched structures. However the overall coverage should be considered a 1:100,000 scale data layer.
A small number of structure locations in this data set were automated by an outside entity. In general, these locations are deemed by the Site File to be of better quality/accuracy than those address matched by DHR.