Geodataset Name:       NAVTEQ_STREETS_ALT_APR09
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Polyline
Feature Count:         1235176

DATA SOURCE(S):                    NAVTEQ
SCALE OF ORIGINAL SOURCE MAPS:     Unknown
GEODATASET EXTENT:                 State of Florida

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

FEATURE ATTRIBUTE TABLES:

Datafile Name: NAVTEQ_STREETS_ALT_APR09.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
OBJECTID	Internal feature number.
Shape	Feature geometry.
LINK_ID	The unique number used to identify each link (road segment) in the NAVTEQ database. For POIs and other related layers, the unique number used to identify an associated link. This set of unique integer identifiers provides primary keys and is consistent between dataset versions. LINK_ID values are never reused. If a feature is changed, split, or removed, new LINK_ID values are assigned and old ones retired.
ST_NAME	The NAVTEQ attributes Feature Base Name, Street Type, Prefix, and Suffix are combined to form the full Street Name. For a POI, this name is the street name associated with the road segment referenced by the POI's LINK_ID.
FEAT_ID	The unique number to identify the set of connected links with the same street name.
ST_LANGCD	A code to indicate what language to use when displaying the Street Name. ENG = English
ST_NM_PREF	A directional identifier that precedes the base name of a road. N = North NE = Northeast E = East SE = Southeast S = South SW = Southwest W = West NW = Northwest
ST_TYP_BEF	The local municipality designator of each road, such as "street", "road", "strasse", "straat", "via", "rue dela", etc. preceeds the base name. Y = Street Type appears before Street Name N = Street Type does not appear before Street Name
ST_NM_BASE	Base Name part of the Street.
ST_NM_SUFF	A suffix is a directional identifier that follows, but is not included in, the base name of a road. N = North NE = Northeast E = East SE = Southeast S = South SW = Southwest W = West NW = Northwest
ST_TYP_AFT	The local municipality designator of each road, such as "street", "road", "strasse", "straat", "via", "rue dela", etc. follows the base name. Y = Street Type appears after Street Name N = Street Type does not appear after Street Name
ST_TYP_ATT	Specifies whether the street type is separated from the street base name by a space. Y = The street type is attached to the street base name. N = The street type is separated from the street base name.
ADDR_TYPE	Identifies the type of address range that applies to address. Only one type of address can be associated with a range. A = Actual B = Base C = City D = County H = Alternate Base O = Old T = Commercial
L_REFADDR	The left side reference address. Each NAVTEQ link has a reference node at one end and a non-reference node at the other end. The reference node is the node with the lowest latitude. If latitude values are equal, the reference node is the one with the lowest longitude.
L_NREFADDR	The left side non-reference address. Each NAVTEQ link has a reference node at one end and a non-reference node at the other end. The reference node is the node with the lowest latitude. If latitude values are equal, the reference node is the one with the lowest longitude.
L_ADDRSCH	Address Scheme Identifies the numbering scheme for the addresses assigned to the left and right sides of a link. blank = Undefined address range. E = Even address range. M = Mixed address range. O = Odd address range.
L_ADDRFORM	Identifies the address format used on the left and right sides of a link. Helps with addresses that have alpha characters or hyphens so that special geocoding rules can be applied. blank = UNADDRESSED 1 = ALPHAHYPHENATED-5 3 = ALPHANUMERIC-3 4 = NUMERICALPHA A = ALPHANUMERIC-N B = BLOCK C = ALPHANUMERIC-1 D = SLASH E = ALPHANUMERIC-E H = HYPHENATED I = ALPHANUMERIC-NW J = ALPHANUMERIC-NE K = ALPHANUMERIC-SW L = ALPHANUMERIC-SE N = NUMERIC O = ALPHANUMERIC-ES P = ALPHANUMERIC-EN Q = ALPHANUMERIC-WS R = ALPHANUMERIC-WN S = ALPHANUMERIC-S W = ALPHANUMERIC-W X = ALPHANUMERIC-SLASH Z = LEADING ZERO
R_REFADDR	The right side reference address. Each NAVTEQ street segment has a reference node at one end and a non-reference node at the other end. The reference node is the node with the lowest latitude. If latitude values are equal, the reference node is the one with the lowest longitude.
R_NREFADDR	The right side non-reference address. Each NAVTEQ link has a reference node at one end and a non-reference node at the other end. The reference node is the node with the lowest latitude. If latitude values are equal, the reference node is the one with the lowest longitude.
R_ADDRSCH	The Address Scheme identifies the numbering scheme for the addresses assigned on the left and right sides of a link. See the Left Address Scheme attribute (L_ADDRSCH) for a list of valid values.
R_ADDRFORM	Identifies the address format used on the left and right sides of a link. Helps with addresses that have alpha characters or hyphens so that special geocoding rules can be applied. See the Left Address Format attribute (L_ADDRFORM) for a list of valid values.
NUM_AD_RNG	Counter for the number of address ranges associated with the link. This value includes the Base address range. The Streets Layer entries having NUM_STNMES > 1 or NUM_AD_RNG > 1 will have a corresponding entry in the Alternate Streets layer.
ROUTE_TYPE	A route type value indicates that the road's name is actually a route number and in many countries is displayed in a shield symbol (i.e. Interstate and State routes in the U.S.). This numeric code can be used to determine the level of road/route type, by country, from tables in the NAVSTREETS Reference Manual. 1 = U.S. Interstate or European Level 1 Road 2 = U.S. Federal or European Level 2 Road 3 = U.S. State or European Level 3 Road 4 = U.S. County or European Level 4 Road 5 = European Level 5 Road 6 = European Level 6 Road blank = Not Applicable
DIRONSIGN	Indicates the official directional identifiers assigned to highways, typically either North/South or East/West. Blank = Not Applicable N = North, Norte, Nord S = South, Sud, Sur E = East, Est, Este W = West O = Oeste, Ouest
EXPLICATBL	A road name is identified as explicatable when it is a legal name or a valid name for a road. Y = The name is a legal or valid name for the road. N = The name is not explicatable.
NAMEONRDSN	Indicates that this name entry is the name assigned to a road by the official organisation responsible for the existence and maintenance of the road. If Yes, this name is generally the name posted on the street signs. A link may have more than one name with Name on Road Sign = Y. There is no distinction in this case to which name is more important than the other name. Y = The road sign name is the official name. N = The road sign name is not the official name.
POSTALNAME	Indicates the presence of additional names that are added to a link to match a postal service file. Y = The name matches a Postal Service file name. N = A Postal Service file name is not present.
STALENAME	Indicates if the street name is stale, e.g., old or obsolete, but still in use. Y = The name is a Stale Name. N = There is not an applicable Stale Name.
VANITYNAME	A Vanity Name identifies an alternative name (specific to a business, settlement, location, etc.) other than the official street name. The Vanity Name may only apply to one building along the street (e.g. IBM Plaza). Vanity Names are included in the database to assist in address identification and may be used for route guidance. Y = The name is a Vanity Name N = The name is not a Vanity Name
JUNCTIONNM	Identifies a ramp system that comprises a named Junction between two or more motorways or a named motorway exit/entrance. Y = The name is a Junction Name. N = The name is not a Junction Name.
EXITNAME	Applied to name on the ramp link associated with a posted Exit Number sign.
SCENIC_NM	Indicates if the name is a scenic route name. Scenic Route Names can be used for destination selection and map display. Y = The name is a Scenic Route Name. N = The name is not a Scenic Route Name.
DESCRIPT	GeoPlan added field based on ST_NAME
FGDLAQDATE	Date GeoPlan acquired data from source.
AUTOID	Unique ID added by GeoPlan
SHAPE.LEN	Length in meters

USER NOTES:

NAVTEQ data contains the most navigable attributes available in a database. Utilizing the data to its fullest allows the user to access Layers such as expressway ramps, complete and correct connectivity of all roadways, one-way streets, physical, logical, and legal turn restrictions, construction projects, as well as physical and painted lane dividers. In addition to these navigable attributes, NAVTEQ data provides address ranges down to the level of the correct side of the street.

NAVTEQ provides 4 levels of street map coverage: Detailed City, Inter-Town, In-Process Data and Connector areas. Detailed City is NAVTEQ's highest level of coverage. This coverage level has the most detail and enables door-to-door routing functionality. Inter-Town coverage includes the main highway network and all the necessary attributes required to allow routing from city to city. Inter-Town links are coded with attributes Detailed City Inclusion = N and In-Process Data = N. For Inter-town links, the Full Geometry attribute flag may be set to either yes or no depending on the presence or lack of surrounding In-Process Data Coverage. In many countries, NAVTEQ has used a commercial source to add local roads to the Inter-Town network. The inclusion of this geometry allows improved map display and guidance. This coverage level is called Full Coverage in the U.S. and Road Network Coverage in Europe. The Connector Specification enables NAVTEQ to maintain minimum coverage in areas prior to completing (full) Detailed City (DC), Inter Town (IT), or In-Process areas. For defining a hierarchical network used to determine a logical and efficient route for a traveler, each NAVTEQ street segment is tagged with a 5 level Functional Class (FC) attribute explained as follows. FC 1: Very long distance routes between major cities - The "highest level" network comprises the FC 1 arterials, which are primarily controlled access highways designed for very-long-distance travel linking major metropolitan areas and cities, FC 2: Primary routes between major and smaller cities and through metro areas, FC 3: Major routes between minor cities or towns, and through city districts, FC 4: Routes connecting minor towns or villages and collecting the local traffic in the city districts, and FC 5: Roads that are not efficient through routes - The "lowest level" and final category is FC 5, which comprises roads not considered to be arterials or transportation corridors.

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

NAVTEQ maps provide a highly accurate representation of the detailed road network including hundreds of attributes such as turn restrictions, physical barriers and gates, one-way streets, restricted access and relative road heights. NAVTEQ digital map data offers accuracy, detail, reliability, and flexibility. Continuously updated to maintain its freshness and precision, NAVTEQ digital map data not only enables door-to-door routing it contains millions of Points of Interest (POIs), making it easy to locate everything from restaurants to hospitals and gas stations. NAVTEQ data are found onboard most navigation-enabled vehicles produced around the world and on all the top Internet navigation sites. It is the unseen force behind the leading express mail services, emergency and government routing plans, efficient field service management, as well as numerous fleet operations, worldwide. Plus, it is the foundation for a growing category of wireless, Location Based Services (LBS). NAVTEQ offers digital map coverage in 77 countries on 6 continents. In addition to widely used GIS formats, including ESRI and MapInfo, data are also available in a number of other formats including RDF (Relational Data Format), GDF (Geographic Data Format), SIF+ (Standard Interchange Format), POI XML, and ODF (Oracle Delivery Format). An in-depth description of NAVTEQ datasets, data processing methodology, geometry, attributes, and metadata is provided to NAVTEQ customers through the NAVSTREETS Reference Manual and a number of other supplemental documents. NAVTEQ documentation uses standardized British spelling.

With the most accurate geometry, the highest number of attributes, and the most complete detailed coverage, NAVTEQ data is the ideal resource for Fleet applications that offer route planning and optimization, and GIS geocoding and other applications that require superior accuracy, and location-enabled services, from Personal Navigation Devices (PNDs) and mobile social networking, to location-enabled entertainment, leisure, and business applications. Products, applications, and services that rely on digital mapping data can ensure superior performance and accuracy by using NAVSTREETS. NAVTEQ data drives most in-vehicle navigation systems around the world, the top routing Web sites, and the leading brands of wireless devices. Designed for rapid display and retrieval of attributes for routing, NAVTEQ data additionally provides support for express mail services, emergency and government routing plans, efficient field service management, wireless Location Based Services (LBS), and delivery of real-time traffic information.

The positional accuracy of a given NAVTEQ street segment depends on the value of the Enhanced Geometry (ENH_GEOM) attribute. Links with Enhanced Geometry = Y conform to accuracy requirements of +/-5 meters for absolute position and +/- 1 meter for relative position. The minimum length of any street segment, independent of generalization, is 2 meters/7 feet.

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

This data can only be used by NAVTEQ customers, as detailed specifically in NAVTEQ licensing terms and agreements.

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:

NAVTEQ's comprehensive data build process ensures the highest quality data available for routing and mapping applications. The process begins with establishing a field office in the new build area. Sources or Base Maps are acquired from a variety of sources including local governments, utility companies, other public agencies, and commercial mapping agencies. These maps are then carefully reviewed and digitized. All base map data is further enhanced with aerial photos and differential GPS to accurately position roads and represent lakes, rivers, railroads, etc., and proprietary software is then used to add navigable information, addresses, and points of interest. NAVTEQ additionally road tests the data to further add to the quality of the database. Field office staff drives the roads and streets to collect and verify new data. Photographs are also taken of overhead signage to ensure that the data accurately reflects the real world. Process Date: Unknown NAVTEQ digital map data is built on the roads of the world. Over seven hundred NAVTEQ field researchers from approximately 168 offices drive millions of kilometers of the road network each year. To provide uniformity and maximize precision each team works to a single global specification. And each team has state-of-the-art equipment, including our proprietary GPS-based collection technology and software. Process Date: Unknown NAVSTREETS is a NAVTEQ extraction format. The NAVTEQ data production environment, while not designed to be adopted directly by customers, is designed to insulate customers from data structure changes, additions, and deletions. NAVTEQ uses data extraction formats to "publish" NAVTEQ data externally to its customers, enabling them to process map data into their own production environment. These extraction formats generally have a design that is independent from the NAVTEQ internal production environment, and are not impacted when NAVTEQ modifies parts of the production environment. Extraction formats generally publish the same content, with differences only in the representation of the data. Process Date: Unknown NAVTEQ uses a six-step production process to build its digital road maps: source acquisition, source normalization, geometry development, field data collection, geocoding, and data validation. These steps involve compiling maps, charts and imagery, driving the road network, developing proprietary tools and processes, using hundreds of automated validation tests, and periodically re-driving the roads to ensure the data are as up-to-date as possible. Process Date: Unknown Data validation: NAVTEQ subjects the data to hundreds of automated validation tests to provide accuracy. These tests are complemented by regular reports from the field teams, who periodically re-drive the roads and streets to collect and verify new data, and confirm the accuracy of all information contained in the database. Process Date: Unknown Geocoding: The field and production teams code the one-ways, turn restrictions, postal codes, and other details to every location on the map. Process Date: Unknown Field data collection: Using proprietary tools and processes, NAVTEQ collects everything from road geometry to road attributes, 300 in all, on roads, streets, and highways throughout the world. Proprietary software is used to add navigable information, addresses, and points of interest. Photographs are also taken of overhead signage to ensure that the data accurately reflects the real world. Process Date: Unknown Geometry development: NAVTEQ verifies (and if needed, corrects) the data by bringing together the source material, field data gathered through driving the road network, and additional digital imagery. Base map data is further enhanced with aerial photos and differential GPS to accurately position roads and represent lakes, rivers, railroads, etc. Process Date: Unknown Source normalization: Source maps are carefully reviewed and digitized. The data are normalized and entered into the NAVTEQ database. Process Date: Unknown Source acquisition: The process begins with establishing a field office in the new build area. Source or Base Maps are acquired from a variety of sources including local governments, utility companies, other public agencies, and commercial mapping agencies. These sources of information, in the form of maps, charts, and imagery, provide the basic roadway detail for the new build area. Process Date: Unknown NAVTEQ Data users can help maintain and improve data accuracy by reporting suggested changes to NAVTEQ. Map updates can be submitted through the web based Map Reporter application at http://mapreporter.navteq.com/dur-web-external/. The status of updates can also be checked at this website after submittals. Process Date: Unknown GeoPlan acquired this data from the Florida Department of Transportation in June 2009. When received the data was in Geographic lat/long projection. The data was projected to Albers HPGN. -Added DESCRIPT item based on ST_NAME -Added FGDLAQDATE based on date acquired from source -Changed name from AltStreets to NAVTEQ_STREETS_ALT_APR09 Process Date: 20090907 Data imported to ArcSDE and exported as a shapefile. Process Date: 20090914

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:

NAVTEQ Technical Customer Support
NAVTEQ
425 W Randolph Street
Chicago, IL
60606
312-894-7000


http://NAVTEQ.com
tcs@navteq.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