County Boundaries (Administrative Area Boundary 3)

FGDC Metadata:

Identification Information:

Citation:

Citation Information:

Originator: 

Publication Date: 20240101

Title: County Boundaries (Administrative Area Boundary 3)

Geospatial Data Presentation Form: vector digital data

Online Linkage: http://NAVTEQ.com

Larger Work Citation:

Citation Information:

Originator: 

Publication Date: 20150401

Title: NAVTEQ NAVSTREETS, available for 77 countries on 6 continents, is organized into 4 categories of geospatial data layers and related tabular datasets including 1) Road Features and Associated Navigation Information, 2) Points of Interest (POIs), 3) Administrative Areas and Other Cartography, and 4) Metadata. These datasets include Streets, Major Highways, Secondary Highways, Signs, Driving Conditions, Traffic, Travel Destinations, Parking, Named Places, Auto Maintenance, Service, and Petrol, Hospitals, Restaurants, Shopping, Business Facilities, Entertainment, Financial Institutions, Educational Institutions, Transportation Hubs, Border Crossings, Parks and Recreation, Community Service Centres, Country, State, and other Administrative Areas, Buildings, Landmarks, Railroads, Land Use, Waterways, Islands, and Oceans, and other related information. NAVTEQ global map data includes approximately 19 million roadway miles (over 30.5 million kilometers) and over 40 million POIs in approximately 50 categories.

Geospatial Data Presentation Form: Vector digital data

Online Linkage: http://NAVTEQ.com

Description:

Abstract: County boundaries.NAVTEQ's Administrative Area Boundaries. There are five Administrative Area Boundaries layers (1, 2, 3, 4, 5). These layers contain the boundaries that divide countries into administrative areas such as country, state, county, city, or settlement. These designations vary on a country by country basis. (In the US for example, the AdminBndy2 layer contains State boundaries, the AdminBndy3 layer contains County boundaries, and the AdminBndy4 layer contains City boundaries.) See Administrative Level Coding and Boundary Features in the NAVSTREETS manual for a list of the administrative area types by country. This layer is used for map visualisation. Note that an Administrative Area Boundary is represented by multiple region objects when it has names in multiple languages. This NAVTEQ dataset is released on a Quarterly basis. This dataset is a subset of the full NAVTEQ NAVSTREETS database.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.

Purpose: County Boundaries - NAVTEQ's Administrative Area Boundary 3. This dataset is a subset of the full NAVTEQ NAVSTREETS database.

Supplemental Information: 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.

Time Period of Content:

Time Period Information:

Single Date/Time:

Calendar Date: 20240101

Currentness Reference: Publication date

Status:

Progress: Complete

Maintenance and Update Frequency: Quarterly

Spatial Domain:

Bounding Coordinates:

West Bounding Coordinate: -87.643690

East Bounding Coordinate: -79.988951

North Bounding Coordinate: 31.166715

South Bounding Coordinate: 24.376387

Keywords:

Theme:

Theme Keyword Thesaurus: None

Theme Keyword: geocoding

Theme Keyword: boundaries

Theme Keyword: political boundaries

Theme Keyword: countries

Theme Keyword: location

Theme Keyword: cities

Theme Keyword: roadmap

Theme Keyword: settlements

Theme Keyword: NAVTEQ

Theme Keyword: states

Theme Keyword: routing

Theme Keyword: towns

Theme Keyword: nations

Theme Keyword: counties

Theme Keyword: provinces

Theme Keyword: navigation

Theme:

Theme Keyword Thesaurus: None

Theme Keyword: towns

Theme Keyword: counties

Theme Keyword: roadmap

Theme Keyword: provinces

Theme Keyword: geocoding

Theme Keyword: cities

Theme Keyword: settlements

Theme Keyword: political boundaries

Theme Keyword: states

Theme Keyword: routing

Theme Keyword: NAVTEQ

Theme Keyword: navigation

Theme Keyword: nations

Theme Keyword: countries

Theme:

Theme Keyword Thesaurus: ISO 19115 Topic Categories

Theme Keyword: location

Theme Keyword: boundaries

Place:

Place Keyword Thesaurus: None

Place Keyword: Detailed Coverage Area 9: Alabama, Florida, Georgia, South Carolina, and Parts of North Carolina

Access Constraints: Access to this data is allowed only to NAVTEQ customers, as detailed specifically in NAVTEQ licensing terms and agreements.

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

Point of Contact:

Contact Information:

Contact Organization Primary:

Contact Organization: NAVTEQ Technical Customer Support

Contact Address:

Address Type: mailing and physical

Address: 425 W Randolph Street

City: Chicago

State or Province: IL

Postal Code: 60606

Contact Voice Telephone: 312-894-7000

Contact Electronic Mail Address: tcs@navteq.com

Data Set Credit: NAVTEQ incorporates and enhances data from a number of local governments, utility companies, other public agencies, and commercial mapping agencies in building its final products.

Native Data Set Environment:  Version 6.2 (Build 9200) ; Esri ArcGIS 10.8.1.14362

Cross Reference:

Citation Information:

Originator: 

Publication Date: 20150401

Title: NAVTEQ NAVSTREETS, available for 77 countries on 6 continents, is organized into 4 categories of geospatial data layers and related tabular datasets including 1) Road Features and Associated Navigation Information, 2) Points of Interest (POIs), 3) Administrative Areas and Other Cartography, and 4) Metadata. These datasets include Streets, Major Highways, Secondary Highways, Signs, Driving Conditions, Traffic, Travel Destinations, Parking, Named Places, Auto Maintenance, Service, and Petrol, Hospitals, Restaurants, Shopping, Business Facilities, Entertainment, Financial Institutions, Educational Institutions, Transportation Hubs, Border Crossings, Parks and Recreation, Community Service Centres, Country, State, and other Administrative Areas, Buildings, Landmarks, Railroads, Land Use, Waterways, Islands, and Oceans, and other related information. NAVTEQ global map data includes approximately 19 million roadway miles (over 30.5 million kilometers) and over 40 million POIs in approximately 50 categories.

Geospatial Data Presentation Form: Vector digital data

Online Linkage: http://NAVTEQ.com

Data Quality Information:

Attribute Accuracy:

Attribute Accuracy Report: NAVTEQ field office staff drives the roads and streets to collect and verify new data. In addition, internal test applications are regularly run on attributes to assist in verification and correction. NAVTEQ also publishes Technical Notification Memorandums (TNM) for customers on a quarterly basis. These TNMs include information pertaining to product updates, format changes, new attributes, detailed attribute specifications and representations, and new country coverage announcements. If NAVTEQ plans to add, remove, or change an attribute or product Layer, an announcement is made to customers a minimum of 6 months in advance. This allows customers to prepare and make necessary modifications to their applications before a new attribute is released in the product.

Logical Consistency Report: 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.

Completeness Report: 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 traveller, 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.

Positional Accuracy:

Horizontal Positional Accuracy:

Horizontal Positional Accuracy Report: Boundaries for cartographic features may be generalized. Generalisation refers to the process of reusing existing links when cartography and administrative boundaries are created. If existing geometry is within the generalization guidelines below, then the feature is added to the existing links instead of creating additional geometry. Roads and ferries cannot share geometry with railways, runways, country boundaries, or any water links. Additionally, Building/Landmark polygons which require sufficient detail to make the building recognisable, can never share geometry with navigable links. All other cartography may share geometry based on the generalisation rules. For example, a road link or railroad link may also have a feature of state park or hospital. Cartography and administrative boundary features in Detailed City areas can be generalised up to 25 metres/82 feet (except built-up areas) and 100 metres/328 feet for built-up areas Cartography and administrative boundary features in Inter-Town areas can be eneralised up to 250 metres/820 feet (except built-up areas) 100 metres/328 feet for built-up areas.

Lineage:

Process Step:

Process Description: 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

Process Step:

Process Description: 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

Process Step:

Process Description: 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

Process Step:

Process Description: Source normalization: Source maps are carefully reviewed and digitized. The data are normalized and entered into the NAVTEQ database.

Process Date: unknown

Process Step:

Process Description: 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

Process Step:

Process Description: 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

Process Step:

Process Description: 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

Process Step:

Process Description: 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

Process Step:

Process Description: 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

Process Step:

Process Description: 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

Process Step:

Process Description: 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

Spatial Data Organization Information:

Direct Spatial Reference Method: Vector

Point and Vector Object Information:

SDTS Terms Description:

SDTS Point and Vector Object Type: GT-polygon composed of chains

Point and Vector Object Count: 105

Entity and Attribute Information:

Detailed Description:

Entity Type:

Entity Type Label: Administrative Area Boundaries 3 - County Boundaries

Entity Type Definition: There are five Administrative Area Boundaries layers (1, 2, 3, 4, 5). These layers contain the boundaries that divide countries into administrative areas such as country, state, county, city, or settlement. These designations vary on a country by country basis. (In the US for example, the AdminBndy2 layer contains State boundaries, the AdminBndy3 layer contains County boundaries, and the AdminBndy4 layer contains City boundaries.) See Administrative Level Coding and Boundary Features in the NAVSTREETS manual for a list of the administrative area types by country. This layer is used for map visualisation. Note that an Administrative Area Boundary is represented by multiple region objects when it has names in multiple languages.

Entity Type Definition Source: NAVTEQ

Attribute:

Attribute Label: OBJECTID

Attribute Definition: Internal feature number.

Attribute Definition Source: Esri

Attribute Domain Values:

Unrepresentable Domain: Sequential unique whole numbers that are automatically generated.

Attribute:

Attribute Label: POLYGON_ID

Attribute Definition: Unique identifier for polygon features. This set of unique integer identifiers provides primary keys and is consistent between dataset versions.

Attribute Definition Source: NAVTEQ

Attribute:

Attribute Label: AREA_ID

Attribute Definition: Identifies the unique ID for the area. This set of unique integer identifiers provides primary keys and is consistent between dataset versions. The Area IDs are unique within North America and within Europe/South Africa. However, Area IDs may be duplicated between North America and Europe/South Africa.

Attribute Definition Source: NAVTEQ

Attribute:

Attribute Label: NM_AREA_ID

Attribute Definition: The Number of Area Ids associated to this Administrative Area. If the number > 1, the additional area ids can be found in the AdminArea table.

Attribute Definition Source: NAVTEQ

Attribute:

Attribute Label: POLYGON_NM

Attribute Definition: The Feature Name (Polygon Name) identifies the name of the Administrative Area.

Attribute Definition Source: NAVTEQ

Attribute:

Attribute Label: NM_LANGCD

Attribute Definition: A code to indicate the language used for the feature name. ENG = ENGLISH

Attribute Definition Source: NAVTEQ

Attribute:

Attribute Label: POLY_NM_TR

Attribute Definition: A Transliteration is a Latin-1 representation of a non-Latin-1 name.

Attribute Definition Source: NAVTEQ

Attribute:

Attribute Label: TRANS_TYPE

Attribute Definition: A Transliteration Type defines the method used to transliterate a non-Latin-1 name into Latin-1.

Attribute Definition Source: NAVTEQ

Attribute:

Attribute Label: FEAT_TYPE

Attribute Definition: The Feature Type is the textual description of the feature associated with the Feature Code identifier. A list of NAVTEQ Feature Codes and corresponding Feature Types can be found in the Feature Code attribute metadata.

Attribute Definition Source: NAVTEQ

Attribute:

Attribute Label: DETAIL_CTY

Attribute Definition: Indicates whether the feature is in an area of Detailed City coverage. The Detailed City specification represents the most comprehensive coverage of an area. The Detail_Cty attribute allows systems to adapt to different levels of attributing. List of values  Value Y Description The feature is within detailed city coverage. Value N Description The feature is not within detailed city coverage. Value P Description Part of the feature is within Detailed City Coverage Area, part is not Detailed City Coverage Area.

Attribute Definition Source: NAVTEQ

Attribute:

Attribute Label: FEAT_COD

Attribute Definition: Every spatial feature (excluding POI's) within the NAVSTREETS data has a Feature Code, whether it is a street network feature (e.g. an interstate or highway), or a cartographic feature (e.g. a beach, island, woodland, landmark). Value 900170 Description Country

Attribute Definition Source: NAVTEQ

Attribute:

Attribute Label: COVERIND

Attribute Definition: Coverage Indicator is an attribute to a navigable link that indicates a product level that corresponds to the inclusion of database features. It also indicates verification and completeness for a particular feature in the database. Value N0 Description DETAILED CITY

Attribute Definition Source: NAVSTREETS Street Data Reference Manual v5.6

Attribute:

Attribute Label: CLAIMED_BY

Attribute Definition: Claimed By indicates which country claims an administrative area boundary in a disputed territory.

Attribute Definition Source: NAVTEQ

Attribute:

Attribute Label: CONTROL_BY

Attribute Definition: The Controlled By attribute is used to indicate (for cartographic features in disputed areas) which country is in control of the area according to international agreements. Controlled By identifies cartographic features located in a Disputed Area and not claimed by another country.

Attribute Definition Source: NAVTEQ

Attribute:

Attribute Label: SHAPE

Attribute Definition: Shape Points - Sets of binary spatial coordinate values representing ESRI geometry objects.

Attribute Definition Source: Esri

Attribute Domain Values:

Unrepresentable Domain: The set of all geometry object values.

Attribute:

Attribute Label: Shape.STArea()

Attribute:

Attribute Label: Shape.STLength()

Distribution Information:

Distributor:

Contact Information:

Contact Organization Primary:

Contact Organization: NAVTEQ

Contact Address:

Address Type: mailing and physical

Address: 425 W Randolph Street

City: Chicago

State or Province: IL

Postal Code: 60606

Country: US

Contact Voice Telephone: 312-894-7000

Contact Electronic Mail Address: DataRequestNA@navteq.com

Resource Description: NAVTEQ Adminbndy4, in ESRI Shape File format. NAVTEQ data folders are organized using a 4-5 level hierarchy. The 1st level consists of 3 global areas including 1) The Americas, 2) Asia-Pacific (APAC) and 3) Europe, The Middle East, and Africa (EMEA). These 3 global areas are then divided into approximately 60 2nd level areas as countries, e.g., Argentina, regions within a country, e.g., North America DCA7, or several countries together, e.g., Spain and Portugal. The 3rd level folders correspond to a specific year and quarter release date, e.g., 2009Q4. The 4th and 5th level folders use NAVTEQ's standard product file naming. The standard product file folder name will comprise up to 17 capitalized alphanumeric characters in the following format: RRCCYYQVVAAABBB.ZZ where RR = Sub Region Code, CC = Clipping/Merge Code, YY = Year Code, Q = Year Quarter, VV = version, AAA = Region Identification, BBB = Product Identification Code, and ZZ = compression method. In some cases, the data files for a NAVTEQ coverage area will be packaged in a single country folder, e.g., Thailand, in other cases, multiple sets of data files for a country will be packaged as multiple sub region folders under a single top level grouping folder, e.g., France. NAVTEQ NAVSTREETS is comprised of approximately 40 GIS layers and 30 related dbf tabular datasets. Prior to Q4 2009, the related tabular datasets were packaged as empty shapefiles with only the dbf files containing data. As of Q4, 2009, these related tabular datasets are no longer packaged as empty shapefiles and are now delivered as single dbf files. For fully describing the entity and attribute information contained in these dbf only tabular datasets, NAVTEQ does provide FGDC metadata files, and describes them using an FGDC Vector Type of Point. For areas of the world using non Latin-1 (ISO-8859-1) character sets for local language representation, NAVTEQ provides supplemental matching Unicode (UTF-8) based or "look-aside" files for many dataset attributes. When Unicode based data is available for a NAVTEQ coverage area, it will be packaged into a separate and complete NAVTEQ coverage area folder using a different Product Identification Code. This folder will contain both the main Latin-1 based and the supplemental Unicode files. The Unicode based data files will be found in the LAT subfolder, and named with .uni file extension. Empty Layers Note: Layers such as WaterWys, Adminbndy3, Adminbndy4, and MajHwys, MajHwyShield, various POI layers, etc., could potentially be empty, depending on the coverage and regional inclusion of the data. In addition, depending upon the situation, the layersAdminBndy1 and AdminBndy2 can be empty as a result of cases where regional divisions of NAVTEQ products do not align with real-world geo-political boundaries. To help users get started with viewing and using layers and data tables, as of Q4, 2009, NAVTEQ also provides an ArcGIS/ArcMap.mxd, and an MXD_Readme.txt file, located in the Region folder containing the ESRI Shapefiles. NAVTEQ data can also be used with other GIS software including MapInfo and is available in a variety of other formats including RDF (Relational Data Format), GDF (Geographic Data Format), SIF+ (Standard Interchange Format), POI XML, and ODF (Oracle Delivery Format).

Distribution Liability: This data can only be distributed to NAVTEQ customers, as detailed specifically in NAVTEQ licensing terms and agreements.

Standard Order Process:

Digital Form:

Digital Transfer Information:

Format name: ESRI Shape File and supplemental documentation packaged as sets of .tar and .tar.gz compressed coverage area folders. For data packaging and delivery, these NAVTEQ coverage areas are organized using 3 world areas including: Americas, Asia Pacific (APAC), and Europe, Middle East, Africa (EMEA).

Format Version Number: ArcGIS 9.x

Digital Transfer Option:

Online Option:

Computer Contact Information:

Network Address:

Network Resource name: https://navteq.subscribenet.com requiring username and password as issued to customer by NAVTEQ. Immediate, easy, and secure download access for data and documentation through NAVTEQ's B2B website is the preferred data delivery method. NAVTEQ customers also receive email notification when new releases or updates become available for data and documentation.

Fees: Contact NAVTEQ Sales for most current pricing information.

Ordering Instructions: Call 312-894-7000

Metadata Reference Information:

Metadata Date: 20240807

Metadata Contact:

Contact Information:

Contact Organization Primary:

Contact Organization: NAVTEQ Technical Customer Support

Contact Address:

Address Type: mailing and physical

Address: 425 W Randolph Street

City: Chicago

State or Province: IL

Postal Code: 60606

Contact Voice Telephone: 312-894-7000

Contact Electronic Mail Address: tcs@navteq.com

Metadata Standard name: FGDC Content Standard for Digital Geospatial Metadata

Metadata Standard Version: FGDC-STD-001-1998

Metadata Time Convention: local time