Geodataset Name:       GDT_ROADS_JAN09
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Polyline
Feature Count:         2679669

DATA SOURCE(S):                    Tele Atlas(R)
SCALE OF ORIGINAL SOURCE MAPS:     N/A
GEODATASET EXTENT:                 State of Florida

PUBLICATION DATE:                  200901
TIME PERIOD OF CONTENT:            200901
DOWNLOAD LINK:                     http://www.fgdl.org/metadataexplorer/explorer.jsp

FEATURE ATTRIBUTE TABLES:

Datafile Name: GDT_ROADS_JAN09.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
OBJECTID	Internal feature number.
DYNAMAP_ID	The unique segment identification number.
L_F_ADD	The address on the left side of a street segment at the beginning or 'from' end of the digitized segment.
L_T_ADD	The address on the left side of a street segment at the end or 'to' end of the digitized segment.
R_F_ADD	The address on the right side of a street segment at the beginning or 'from' end of the digitized segment.
R_T_ADD	The address on the right side of a street segment at the end or 'to' end of the digitized segment.
PREFIX	A 2-character field that is used to indicate a modifier to a street name occurring before the street name and usually indicating direction. Ex: 'E' Center St.
PRETYPE	This field supports new GIS geocoding technology, which allows for additional parsing of international names and highway names.
NAME	The concatenated full name of the street segment.
TYPE	The type of street. Some examples are ST, AVE, PKWY, etc.
SUFFIX	A 2-character field that is used to indicate a modifier to a street name occurring after the street name and usually indicating direction. Ex: Prospect Bay Dr 'W.'
FCC	The feature class code that the street segment is associated with. Tele Atlas(R) FCCs are similar to the Census Bureau's CFCCs used in their TIGER(R) files.
POSTAL_L	The enclosing 5-digit ZIP Code area on the left side of the street segment.
POSTAL_R	The enclosing 5-digit ZIP Code area on the right side of the street segment.
ACC	The set of Arterial Classification Codes (ACCs) is the Tele Atlas(R) system for categorizing roads according to the level of travel mobility that they provide in the road network. Mobility refers to the volume of traffic that a stretch of road carries and the length of trip that it serves. Valid entries are '1' for roads with highest mobility, through '5' for roads with least mobility.
NAME_TYPE	A 1-character field to indicate whether the street name can be used for geocoding or routing. Valid contents are: 'R'= primary routing name; 'G'= primary geocoding name; 'blank'= other.
SHIELD	The first character of the shield field indicates what shield should be used to represent each name based on its Primary Name. 'I' = Interstate, 'U' = US Hwy, 'S' = State Hwy, blank = other. The second character of the shield field indicates subclassifications of the shield type. A shield subtype should not exist if there is not a primary shield type in the first character of the field. Valid entries are 'B' for business route; 'L' for loop; 'T' for truck; 'C' for connector; 'S' for spur; 'Y' for bypass; 'A' for alternate; 'X' for extended; 'N' for scenic.
HWY_NUM	The Hwy_Num field indicates the number that appears in the shield for the highway. This will be present only for Interstates, U.S. Highways and State Highways. The HWY_NUM field will be populated only on FCC segments of A1*, A2* and A3*.
SEG_LEN	The highway segment length in miles. The distance is calculated using the arc distance with correction for the earth's curvature.
SPEED	The segment speed field contains the average speeds categorized by FCC and defined in a Tele Atlas(R) FCC-to-Speed table document. The units are in miles per hour.
ONE_WAY	The One_Way field is filled with either 'FT,' 'TF' or is blank. 'FT' indicates that the segment is one way, from the digitized From end to the digitized To end. 'TF' indicates the opposite direction of travel. A blank field indicates that travel is permitted in both directions.
F_ZLEV	This field indicates the Z-axis relative elevation of a segment in the digitized 'From-to' direction. '0' indicates ground level; '1' indicates structures elevated one level above ground; '-1' indicates structures one level below ground level, etc.
T_ZLEV	This field indicates the Z-axis relative elevation of a segment in the digitized 'To-from' direction. '0' indicates ground level; '1' indicates structures elevated one level above ground; '-1' indicates structures one level below ground level, etc.
FT_COST	The cost to travel on a segment in the digitized From-To direction. The value of the cost is based on the length of the segment and its speed value. The units of cost are minutes. In some GIS formats, a '-1' value is a code that indicates that the street contains an alternate name.
TF_COST	The cost to travel on a segment in the digitized To-From direction. The value of the cost is based on the length of the segment and its speed value. The units of cost are minutes. In some GIS formats, a '-1' value is a code that indicates that the street contains an alternate name.
FT_DIR	The FT_Dir field conveys information about the described direction of travel along highways in the digitized From-to direction. This directional is not part of the recognized postal name. Permissible values for this field are N, S, E, W, NE, SE, NW, SW.
TF_DIR	The TF_Dir field conveys information about the described direction of travel along highways in the digitized To-from direction. This directional is not part of the recognized postal name. Permissible values for this field are N, S, E, W, NE, SE, NW, SW.
NAME_FLAG	For the Street layer in this product, this field is a coded indicator of whether a street name is most appropriate for statewide or cross-country routing (field content = '1'); whether a street name is most appropriate for geocoding (field content = '2'); and whether the routing name is also appropriate for geocoding purposes (field content = '3').
STATUS	A one-character field relating to a street's category.
DESCRIPT	Description field based on PREFIX, NAME, TYPE, & SUFFIX
FGDLAQDATE	FGDL added field based on date downloaded from source
SHAPE	Feature geometry.
AUTOID	Unique ID added by GeoPlan
SHAPE.LEN	Length in meters

USER NOTES:

Tests are performed for invalid names, Feature Class Codes and characters. Tests are constantly running on the Tele Atlas(R) database to ensure segment topology meets Tele Atlas(R) specifications. The Streets layer is not generalized.

All street segments in the Tele Atlas(R) database with an FCC = A* are considered. A74 (driveways) and A75 (parking areas) are not selected. After processing, the dataset is checked for drawing display, correct number of records, record schema consistency with specifications, correct file naming, file sizes and a comparison check with the contents of the Tele Atlas(R) database at the time of creation.

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

To find out more about Dynamap(R)/Transportation and other available products, visit http://www.teleatlas.com.

The primary purpose of the Dynamap(R)/Transportation Street layer is for mapping and geocoding street addresses. When used in conjunction with other Dynamap(R)/Transportation layers, the street layer can be used for site selection, territory management, risk management/assessment, emergency response and other business and government needs.

Tele Atlas(R) street segments allow for six implied decimal places of precision. While minimum accuracy is consistent with 1990 TIGER/Line(R) files, accuracy is dependent on geographic area and sources used to update those areas. Nationwide, over 20 million street segments are horizontally accurate to 12 meters or better.

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

NONE

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: DATA LINEAGE SUMMARY:

Tele Atlas(R) extracts the dataset quarterly from the Tele Atlas(R) database using proprietary software. Data then is converted into multiple GIS formats. ISO quality standards are enforced throughout the production process. Data originally released by Tele Atlas in January 2009 on DVD. When received, data was in the following projection: Geographic Lat Long Datum D_WGS_1984, Units: Decimal Degrees. The GeoPlan QA/QC and standardization process included the following steps: 1. The data was renamed from flxxxst to gdt_roads_jan09.shp 2. The data was reprojected to FGDL Albers HPGN map projection. 3. Added DESCRIPT field based on [PREFIX] & " " & [NAME] & " " & [TYPE] & " " & [SUFFIX] 4. Added field FGDLAQDATE 5. Standardized Metadata 6. Deleted fields with empty values Process Date: 20090216 Data imported to ArcSDE and exported as a shapefile. Process Date: 20090305

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:

Tele Atlas(R)
Tele Atlas
11 Lafayette Street
Lebanon, NH
03766
(800)331-7881


www.teleatlas.com
info.NA@teleatlas.com

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