Geodataset Name:       SHPO_STRUCTURES_JUL06
Geodataset Type:       SHAPEFILE
Geodataset Feature:    POINT
Feature Count:         128365

DATA SOURCE(S):                    Bureau of Archaeological Research
SCALE OF ORIGINAL SOURCE MAPS:     1:100,000
DATE OF AUTOMATION OF SOURCE:      20060701
GEODATASET EXTENT:                 State of Florida

FEATURE ATTRIBUTE TABLES:

Datafile Name: SHPO_STRUCTURES_JUL06.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
SITEID	This is the official state site number assigned by the Florida Master Site File. The state site number is an eight character string containing a two character county code, a five character numeric code, and an optional single letter character suffix (suffix letter is generally used to indicate sites that are functionally or spatially related).
SITENAME	The site name as recorded at the Florida Master Site File. Usually the principal or best known name for a cultural resource. A site name of "NN" indicates no name has been designated for the site.
ADDRESS	The street address of the site, including the number, prefix direction if relevant, and street name.
DESTROYED	No description
SURVEYNUM	The serial number assigned by the Site File to the manuscript produced by the project which identified or reexamined the cultural resource. Not all sites have an associated report or manuscript.
ARCHITECT	The name of the architect, designer, builder, landscape architect, or artist responsible for the actual DESIGN of the building, structure, or object being documented. A blank value for this field indicates that this information is not known or is not recorded in the Florida Master Site File database.
YEARBUILT	The year of actual construction, as documented or estimated. A "C" (circa) indicates the year given is only roughly known or estimated. A "+" indicates the year given is the earliest possible year of construction. A "-" indicates that the year given is the latest possible year of construction. A blank value for this field indicates that this information is not known or is not recorded in the Florida Master Site File database.
STYLE	The architectural style or period which best describes the site.
EXTPLAN	General exterior plan of the structure
STRUCSYS1	Major structural system(s) employed in the structure. Values in this field are limited to a discrete list of possibilities used in the Site File database lookup table. Contact the Site File for more information. A blank value for this field indicates that this information is not known or is not recorded in the Florida Master Site File database.
STRUCSYS2	Major structural system(s) employed in the structure.
STRUCSYS3	Major structural system(s) employed in the structure.
EXTFABRIC1	Major exterior fabric(s) used on the structure. Values in this field are limited to a discrete list of possibilities used in the Site File database lookup table. Contact the Site File for more information. A blank value for this field indicates that this information is not known or is not recorded in the Florida Master Site File database.
EXTFABRIC2	Major exterior fabric(s) used on the structure.
EXTFABRIC3	Major exterior fabric(s) used on the structure.
EXTFABRIC4	Major exterior fabric(s) used on the structure.
STRUCUSE1	Use or function of the structure. Values in this field are limited to a discrete list of possibilities used in the Site File database lookup table. Contact the Site File for more information. A blank value for this field indicates that this information is not known or is not recorded in the Florida Master Site File database.
STRUCUSE2	Additional use or function of the structure.
STRUCUSE3	Additional use or function of the structure.
SURVEVAL	Surveyor's evaluation of the cultural resource's eligibility for the National Registerwhen the resource is considered as an independent entity - not as a component or "contributing property" to a potential district.
SURVDIST	Surveyor's evaluation of cultural resource's eligibility for the National Register as part of a district or thematic group.
SURVLOCAL	Surveyor's evaluation of a cultural resource's eligibility for listing on a local government's register of important sites.
SHPOEVAL	Evaluation of Florida's State Historic Preservation Officer (SHPO) concerning the eligibility of the resource for listing on the National Register of Historic Places. In Florida, the SHPO is the Director of the Division of Historical Resources, acting through staff in the Bureau of Historic Preservation (BHP). Generally the Site File database only contains evaluations made by the Compliance Review staff of BHP. Some properties may be listed on the NRHP without having been reviewed by Compliance Review staff. Therefore, an NR list date (indicating a property is NR listed) takes priority over a 'Not Evaluated by SHPO' value in this field. Values in this field are limited to a discrete list of possibilities used in the Site File database lookup table. Contact the Site File for more information.
D_NRLISTED	Date that the property was officially listed on the National Register of Historic Places (NRHP). The field is blank if the FMSF database does not indicate the property is National Register listed.
PLOTMTHD	Indicates whether the structure was address Matched(M) by DHR, on-screen Digitized(D) by DHR, or automated by an external individual or organization(X). Refer to the discussion of data derivation methods for more details.
DESCRIPT	Based on STRUCUSE1
FGDLAQDATE	Date FGDL obtained data from source.

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. 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.

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

A note concerning data scale: Scale is an important factor in data usage. Certain scale datasetsare 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:250000 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 analyses. Every effort has been made to supply the user with data documentation. For additional information, see the References sectionand the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our web pages at: http://www.geoplan.ufl.edu/education.html

REFERENCES:

Bureau of Archaeological Research

DATA LINEAGE SUMMARY:

Source data were created by the Division of Historical Resources. Structure locations in this data layer were automated using one of three methods; address matching by DHR, on-screen digitizing by DHR, or automated by an external party. The PLOT_MTHD field indicates whether a structure was address matched(M) by the FMSF, digitized(D) by the FMSF, or automated externally(X). Roughly 60% of the structure locations (statewide) were generated by address matching. 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. Process Date: Unknown After the data layers had been completed they were converted from ArcView shapefiles to ArcInfo coverages using the SHAPEARC command in ArcInfo 8.2. In September 2003, the base coverages were converted to an ESRI GeoDatabase format and are currently maintained in GeoDatabase format. Process Date: Unknown When received, the data was in the following projection: Geographic, Datum: NAD27, Spheroid: Clarke 1866, Units: Decimal Degrees. The shapefile was projected to FGDL Albers HPGN (See "Map Projection Parameters" below) in ArcToolBox using the Florida Harn Transformation. -Reprojected to FGDL Albers HPGN -Added DESCRIPT field based on STRUC_USE1 to attribute table -upcased all items in the attribute table -Changed file name to shpo_structures from FloridaStructures -Added FGDLAQDATE field based on date GeoPlan received the data Process Date: 20060817

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:

Bureau of Archaeological Research

R. A. Gray Building, 500 South Bronough St.
Tallahassee, FL
32399-0250
(850) 245-6440



fmsfile@dos.state.fl.us
Vincent Birdsong or Dr. Marion Smith

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