Geodataset Name:       TIGER_ROADS_2008
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Polyline
Feature Count:         1747524

DATA SOURCE(S):                    U.S. Department of Commerce, U.S. Census Bureau, Geography Division
SCALE OF ORIGINAL SOURCE MAPS:     Various
GEODATASET EXTENT:                 State of Florida

PUBLICATION DATE:                  2008
TIME PERIOD OF CONTENT:            Begin Date: 200801    End Date: 200807
DOWNLOAD LINK:                     http://www.fgdl.org/metadataexplorer/explorer.jsp

FEATURE ATTRIBUTE TABLES:

Datafile Name: TIGER_ROADS_2008.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
OBJECTID	Internal feature number.
Shape	Feature geometry.
COUNTYFP	Current county Federal Information Processing Standards (FIPS) code
TLID	Permanent edge ID
MTFCC	MAF/TIGER feature class code of the primary feature for the edge S1100 = Primary Road S1200 = Secondary Road S1400 = Local Neighborhood Road, Rural Road, City Street S1500 = Vehicular Trail (4WD) S1630 = Ramp S1640 = Service Drive usually along a limited access highway S1710 = Walkway/Pedestrian Trail S1720 = Stairway S1730 = Alley S1740 = Private Road for service vehicles (logging, oil, fields, ranches, etc.) S1750 = Private Driveway S1780 = Parking Lot Road S1820 = Bike Path or Trail S1830 = Bridle Path
FULLNAME	Concatenation of expanded text for prefix qualifier, prefix direction, prefix type, base name, suffix type, suffix direction, and suffix qualifier (as available) with a space between each expanded text field
LFROMADD	From house number associated with the most inclusive address range on the left side of the edge
LTOADD	To house number associated with the most inclusive address range on the left side of the edge
RFROMADD	From house number associated with the most inclusive address range on the right side of the edge
RTOADD	To house number associated with the most inclusive address range on the right side of the edge
ZIPL	ZIP code associated with the most inclusive address range on the left side
ZIPR	ZIP code associated with the most inclusive address range on the right side
PASSFLG	Special passage flag B = Bridge F = Ford T = Tunnel
DIVROAD	Divided road flag N = Not separated Y = Separated
DECKEDROAD	Decked road indicator A = Rail above B = Rail below H = Road above a different road (allow MTFCCs to vary) N = Not Decked R = One road split between several different levels (MTFCC cannot vary)
TYPE	MTFCC field Description.
PRE_DIR	Roadway directional prefix. (N, S, E, W, NE, NW, SE, SW)
PRE_TYPE	Road name prefix type. Used for county, state and interstate road names, etc.
NM_BASE	Road Name Base (as in 'Smith' in 'N Smith Street').
ST_TYPE	Type of road, i.e. St, Ave, Rd, Ln, etc.
SUFF_DIR	Roadway directional suffix. (N, S, E, W, NE, NW, SE, SW)
ZIPCODE	Zipcode of line segment's centroid.
DESCRIPT	Based on the field FULLNAME.
FGDLAQDATE	The date FGDL acquired the data from the Source.
AUTOID	Unique ID added by GeoPlan
SHAPE.LEN	Length in meters

USER NOTES:

There may be some inconsistencies in feature names along features. An anomaly exists with the sporadic occurrence of road segments comprising a complete chain with different MAF/TIGER Feature Census Class Code (MTFCC) values assigned. This problem could affect applications that use the MTFCC values for network analysis, routing, or for assigning symbology to a feature when creating a map. The Census Bureau performed automated tests to ensure logical consistency and limits of shapefiles. Node/geometry and topology relationships are collected or generated to satisfy topological edit requirements. These requirements include: (1) Complete chains must begin and end at nodes. (2) Complete chains must connect to each other at nodes. (3) Complete chains do not extend through nodes. (4) Left and right polygons are defined for each complete chain element and are consistent throughout the extract process. (5) The chains representing the limits of the files are free of gaps.

Data completeness of the TIGER/Line Shapefiles reflects the contents of the Census MAF/TIGER database at the time the TIGER/Line Shapefiles were created.

GeoPlan relied on the integrity of the attribute information within the original data.

Please Note: This roads data layer is Not used in the FDOT ETDM project.

The data was created to serve as base information for use in GIS systems for a variety of planning and analytical purposes. In order for others to use the information in the Census MAF/TIGER database in a geographic information system (GIS) or for other geographic applications, the Census Bureau releases to the public extracts of the database in the form of TIGER/Line Shapefiles.

The Census Bureau uses Global Positioning System (GPS) coordinates at road centerline intersections to evaluate the horizontal spatial accuracy of source files that may be used to realign road features in the MAF/TIGER database and test the horizontal spatial accuracy of the road features in the TIGER/Line Shapefiles. The test compares a survey-grade GPS coordinate to its associated road centerline intersection in the TIGER/Line Shapefiles. The test is based on an independent collection of GPS coordinates for a random sample of road intersections from a centerline file that meet certain criteria. The points are referred to as the sample points and are gathered through a private contractor working for the Census Bureau. Since the collection method uses survey-quality GPS-based field techniques, the resulting control points are considered 'ground truth' against which the TIGER road centerline intersection coordinates are compared. The distances between the coordinates are calculated and the Census Bureau determines the Circular Error 95% (CE95). That is, the accuracy of the file in meters with 95% confidence. The CE95 can be calculated from the mean and standard deviation by using the formula: mean of differences plus (2.65 times the standard deviation). CE95 results reported for each file tested are determined using a spreadsheet with embedded statistical formula. The use and applicability of the spreadsheet and its embedded formula have been verified by Census Bureau statisticians. The basis of the calculation is the use of the root mean square error (RSME). This is the method as stated in the U.S. Government's Federal Geographic Data Committee Standard FGDC-STD-007.3-1998, Geospatial Positioning Accuracy Standards. Part 3: National Standard for Spatial Data Accuracy. The results of using this measure of accuracy are in compliance with Federal Spatial Data requirements. In terms of the Census Bureau application, the dataset coordinate values are those taken from the centerline file and the coordinate values from an independent source of higher accuracy are those acquired through the Census Bureau's contractor. Please note that the horizontal spatial accuracy, where reported, refers only to the realigned road features identified as matched to the positionally accurate source file with that accuracy. It is not the spatial accuracy of the TIGER/Line Shapefile as a whole.

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

The TIGER/Line Shapefile products are not copyrighted however TIGER/Line and Census TIGER are registered trademarks of the U.S. Census Bureau. These products are free to use in a product or publication, however acknowledgement must be given to the U.S. Census Bureau as the source. The horizontal spatial accuracy information present in these files is provided for the purposes of statistical analysis and census operations only. No warranty, expressed or implied is made with regard to the accuracy of the spatial accuracy, and no liability is assumed by the U.S. Government in general or the U.S. Census Bureau, specifically as to the spatial or attribute accuracy of the data. The TIGER/Line Shapefiles may not be suitable for high-precision measurement applications such as engineering problems, property transfers, or other uses that might require highly accurate measurements of the earth's surface. Coordinates in the TIGER/Line shapefiles have six implied decimal places, but the positional accuracy of these coordinates is not as great as the six decimal places suggest.

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:

2008 TIGER/Line Shapefiles http://www.census.gov/geo/www/tiger/tgrshp2008/tgrshp2008.html Download TIGER/Line Shapefiles and Relationship Files Download multiple 2008 TIGER/Line Shapefiles at a time via our FTP site ftp://ftp2.census.gov/geo/tiger/TIGER2008/ Please direct any questions or comments to geo.tiger@census.gov Geocoding Standards PDF http://gis.tn.gov/geocoding_standards.pdf

DATA LINEAGE SUMMARY:

TIGER/Line Shapefiles are extracted from the Census MAF/TIGER database by nation, state, county, and entity. Census MAF/TIGER data for the nation, state, county, and entity are then distributed among 58 shapefiles each containing attributes for line, polygon, or landmark geographic data. Process Date: 2008 GeoPlan Center Process Steps: GeoPlan downloaded the 2008 Census Bureau's TIGER/Line data for the State of Florida on September 16th, 2009 from the following FTP site. ftp://ftp2.census.gov/geo/tiger/TIGER2008/ The Florida Tiger/Line data was downloaded for each of the 67 counties as zipfiles. The following represents the original naming structure of the data: tl_2008_12001_edges.shp (Alachua County). The 67 counties were combined into one statewide layer. The data was originally in the following projection: North American Datum of 1983, GRS80, Decimal Degrees. The Statewide layer was reprojected to the FGDL NAD83 HARN Albers projection. Next a selection was performed on the statewide layer where the field [ROADFLG] = 'Y' The roadway features were then extracted to create a new statewide roads layer. Next the following fields were deleted to remove unused fields and decrease the size of the dataset. STATEFP, TFIDL, TFIDR, SMID, FEATCAT, HYDROFLG, RAILFLG, ROADFLG, OLFFLG, EXTTYP, TTYP, ARTPATH, PERSIST, GCSEFLG, OFFSETL, OFFSETR, TNIDF, and TNIDT. Next the following fields were added and populated to help standardize the dataset for use as a reference layer in geocoding. TYPE, PRE_DIR, PRE_TYPE, NM_BASE, ST_TYPE, SUFF_DIR, and ZIPCODE. Please Note: This roads data layer is Not used in the FDOT ETDM project. Process Date: 20090916 Data imported to ArcSDE and exported as a shapefile. Process Date: 20100625

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:

U.S. Department of Commerce, U.S. Census Bureau, Geography Division, Geographic Products Branch
MAF/TIGER
4600 Silver Hill Road, Stop 7400
Washington, DC
20233-7400
301-763-1128


http://www.census.gov/geo/www/tiger
tiger@census.gov

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