FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION
VERSION 2007

TITLE: FDOT OFFICE OF MAINTENANCE LOCATIONS

Geodataset Name:       FDOTOOM_JUL08
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Point
Feature Count:         62
GENERAL DESCRIPTION:
This data set contains Florida Department of Transportation Office of Maintenance locations.
DATA SOURCE(S):                    University of Florida GeoPlan Center
SCALE OF ORIGINAL SOURCE MAPS:     Unknown
DATE OF AUTOMATION OF SOURCE:      20080721
GEODATASET EXTENT:                 State of Florida

FEATURE ATTRIBUTE TABLES:

Datafile Name: FDOTOOM_JUL08.DBF
ITEM NAME WIDTH TYPE
OBJECTID
4 OID
STATUS
1 String
SCORE
2 SmallInteger
MATCH_TYPE
2 String
SIDE
1 String
MATCH_ADDR
83 String
DISTRICT
24 String
NAME
59 String
CITY
26 String
ADDRESS
56 String
ZIP
14 Number
PHONE
18 String
FAX
16 String
CNTY_SERV
150 String
DESCRIPT
59 String
FGDLAQDATE
8 Date
DETAIL_CON
100 String
SHAPE
4 Geometry
AUTOID
4 Integer

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item
Item Description
OBJECTID Internal feature number.

STATUS ESRI item which denotes the status of the geocoded address (whether it was matched or not)

SCORE ESRI item which denotes the score with which the address was matched to a feature in the reference data.

MATCH_TYPE A code showing how an adddress was matched.
A = Automatically matched or rematched.

M = Manually matched or unmatched using the Match or Unmatch button

PP = Point was placed by Pick by Point. The address was matched to the click point using the Pick Address from Map tool in the Interactive Rematch dialog box with ArcMap.

PA = Point was places by Pick by Address. The address was matched to closest address with the Pick Address from Map tool.


SIDE ESRI item which denotes the side of the street to which the address was matched (for geocoding service styles that can match an address to a particular side of a street). Records marked with an "*" have not been GeoCoded, these records have another type of spatial reference source.

MATCH_ADDR ESRI item which denotes the full street layer address to which the address was matched.

DISTRICT FDOT district where office is located

NAME Name of office

CITY City where office is located

ADDRESS Adress of office

ZIP Zip code of office

PHONE Phone number

FAX Fax number

CNTY_SERV Counties served by offices

DESCRIPT FGDL added field based on NAME

FGDLAQDATE FGDL added field based on date downloaded from source

DETAIL_CON Detailed contact. Web address to a pdf containing detailed contact information for an office.

SHAPE Feature geometry.

AUTOID Unique ID added by GeoPlan


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.
What is Geocoding?
Geocoding is term used to describe the act of address matching.  Geocoding
is the process of finding a geographic location (x, y point) for an address
(such as street number and name, city, state, and ZIP Code) on a map.
Geocoding is based off the typical address scheme for the US, in which one
side of the street contains even house numbers while the other side of the
street contains odd house numbers.

The geocoding process uses an algorithm to find the geographic location
of addresses. First, a street segment is identified using the zip code and
street name. Next, the geographic location of the address is matched using
the building number to determine how far down the street and on which side
of the street the building is located. Geocoding Accuracy

The locational accuracy of geocoded addresses may vary from urban to rural
areas due to the algorithm used to generate the geographic locations of
addresses. The algorithm assumes that the size of parcels are equivalent
along a road route. This assumption tends to be more consistent in urban
areas, where the size of parcels vary less than in rural areas.
Consequently, the results of geocoded addresses in urban areas are usually
more reliable than those in rural areas.

For example, the locational accuracy of rural addresses can be slightly
off because some parcels along a rural route may be 15 acres while others
may be 2.5 acres, but the geocoding algorithm assumes that the addresses
are distributed evenly along the route.

The data was created to serve as base information for use in GIS systems 
for a variety of planning and analytical purposes.

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

THE DATA INCLUDED IN FGDL ARE 'AS IS' AND SHOULD NOT BE CONSTRUED
AS LEGALLY BINDING. 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 Transportation
Office of Maintenance:
http://www.dot.state.fl.us/statemaintenanceoffice/district-map.htm

Original info found in: Directory Updated 2007-08-08.pdf

DATA LINEAGE SUMMARY:
GeoPlan received the source for this dataset from the Florida Department
of Transportation via email in pdf format in July of 2008. The data was converted
to an xls and then to a dbf. The dataset was then geocoded based on the 
provided addresses. Non geocodeable addresses were matched and verified
using imagery.

-All addresses were formatted so that they could be imported
 into Excel and converted to a database file format.
-The addresses were geocoded against ARC Logistics Route GDT Roads
 Shapefile created using FGDL Albers HPGN map projection
Process Date: 20080721

Data imported to ArcSDE and exported as a shapefile. Process Date: 20080722
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:
University of Florida GeoPlan Center
GeoPlan
431 Architecture, PO Box 11570
Gainesville, FL
32611-570


http://www.dot.state.fl.us/statemaintenanceoffice/district-map.htm http://www.fgdl.org/fgdlfeed.html Danny Downing

FGDL CONTACT:
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