NAVTEQ 2010 Q2 ZIP Code 5-Digit Area Points for the United States, including Puerto Rico and the US Virgin Islands in SDC Format, Released Quarterly.

Metadata also available as

Metadata:

Identification_Information:
Citation:
Citation_Information:
Originator: NAVTEQ
Publication_Date: 20100401
Title:
NAVTEQ 2010 Q2 ZIP Code 5-Digit Area Points for the United States, including Puerto Rico and the US Virgin Islands in SDC Format, Released Quarterly.
Geospatial_Data_Presentation_Form: Vector digital data
Online_Linkage: <http://NAVTEQ.com>
Larger_Work_Citation:
Citation_Information:
Originator: NAVTEQ
Publication_Date: 20100401
Title:
NAVTEQ data, available for 81 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 69 categories.
Online_Linkage: <http://NAVTEQ.com>
Description:
Abstract:
The USA_ZIP5_PNTS layer contains 5 digit ZIP code points. Each feature in the USA_ZIP5_POLYS layer encloses an associated USA_ZIP5_PNTS feature. This NAVTEQ dataset is released on a Quarterly basis.
Purpose:
NAVTEQ SDC data layers provide high performance display and rapid attribute retrieval for use in both desktop and web based applications including ArcGIS, ArcGIS Street Map, ArcIMS Route Server, Network Analyst, and ArcLogistics. 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 NAVTEQ data. 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.
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 81 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: 20100401
Currentness_Reference: Publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: Quarterly
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -174.663400
East_Bounding_Coordinate: 172.937031
North_Bounding_Coordinate: 70.986861
South_Bounding_Coordinate: -0.000000
Keywords:
Theme:
Theme_Keyword_Thesaurus: ISO 19115 Topic Category
Theme_Keyword: location
Theme:
Theme_Keyword_Thesaurus: None
Theme_Keyword: roadmap
Theme_Keyword: navigation
Theme_Keyword: routing
Theme_Keyword: geocoding
Theme_Keyword: reverse geocoding
Theme_Keyword: NAVTEQ
Theme_Keyword: postal codes
Theme_Keyword: zip codes
Place:
Place_Keyword_Thesaurus: None
Place_Keyword:
the United States, including Puerto Rico and the US Virgin Islands
Access_Constraints:
Access to this data is allowed only to NAVTEQ customers, as detailed specifically in NAVTEQ licensing terms and agreements.
Use_Constraints:
For data terms and conditions, go to <http://dc.gov/page/terms-and-conditions-use-district-data>
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: NAVTEQ Technical 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:
ESRI ArcGIS versions 9.x; Platform: PC-Intel; Operating System: Windows 2000 or Windows XP (Home Edition and Professional); Memory: 512 MB RAM; Processor: 1 GHz;
Cross_Reference:
Citation_Information:
Originator: NAVTEQ
Publication_Date: 20100401
Title:
NAVTEQ data, available for 81 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 69 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, and then drives them over again to confirm the accuracy of all information contained in the database. 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 feature, 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 core 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 features 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: Prime/Detailed City, Network/Inter-Town, Road Network/Complete and Major Road Network/City to City. Prime/Detailed City is NAVTEQ's highest level of coverage. This coverage level has the most detail and enables door-to-door routing functionality. Network/Inter-Town coverage includes the main highway network and all the necessary attributes required to allow routing from city to city. Network/Inter-Town links are coded with attributes Detailed City Inclusion = N and In-Process Data = N. For Network/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 Complete 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) Prime/Detailed City (DC), Network/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.
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 SDC data layers are generated through the use of an external 3rd party application, which converts and merges multiple NAVSTREETS ShapeFiles and tabular navigation data tables for North America into single SDC layers and supporting file sets.
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. Source 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, and then drives them over again to confirm the accuracy of all information contained in the database. Photographs are also taken of all overhead signage to ensure that the data accurately reflects the real world.
Process_Date: Unknown
Process_Step:
Process_Description:
NAVTEQ digital map data is built on the roads of the world. Over one thousand NAVTEQ field researchers from approximately 203 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:
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 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:
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, no-turns, postal codes, and other details to every location on the map.
Process_Date: Unknown
Process_Step:
Process_Description:
Field data collection: Using proprietary tools and processes, NAVTEQ collects everything from road geometry to road attributes, 260 in all, on roads, streets, and highways throughout the world. Proprietary software is used to add navigable information, addresses, and points of interest. All overhead signage is collected 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. All 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:
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:
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
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: Metadata imported.
Source_Used_Citation_Abbreviation:
C:\GIS_Information\Commercial_Aquisitons\Navteq\Updates_for_Gold2011\FGDC Metadata SDC NA 2010 Q2\usa_zip5_pnts.sdc.xml
Process_Date: 20101015
Process_Time: 08443200
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\temp\usa_zip5_pnts.xml
Process_Date: 20120313
Process_Time: 15264300
Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: Entity Point
Point_and_Vector_Object_Count: 0
Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Geographic:
Latitude_Resolution: 0.00001
Longitude_Resolution: 0.00001
Geographic_Coordinate_Units: Decimal degrees
Geodetic_Model:
Horizontal_Datum_Name: D_WGS_1984
Ellipsoid_Name: WGS_1984
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257224
Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: USA_ZIP5_PNTS
Entity_Type_Definition:
USA ZIP5 Points - The USA_ZIP5_PNTS layer contains 5 digit ZIP code points. Each feature in the USA_ZIP5_POLYS layer encloses an associated USA_ZIP5_PNTS feature.
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: POSTALCODE
Attribute_Definition:
5 digit postal code reference - The 5 digit Zone Improvement Plan (ZIP) postal code.
Attribute_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Unrepresentable_Domain: The set of all POSTALCODE values
Attribute:
Attribute_Label: STATE
Attribute_Definition:
State abbreviation for the state within which the applicable postal code falls - State abbreviation for the applicable postal code area.
Attribute_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: AL
Enumerated_Domain_Value_Definition: ALABAMA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: AK
Enumerated_Domain_Value_Definition: ALASKA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: AZ
Enumerated_Domain_Value_Definition: ARIZONA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: AR
Enumerated_Domain_Value_Definition: ARKANSAS
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: CA
Enumerated_Domain_Value_Definition: CALIFORNIA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: CO
Enumerated_Domain_Value_Definition: COLORADO
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: CT
Enumerated_Domain_Value_Definition: CONNECTICUT
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: DE
Enumerated_Domain_Value_Definition: DELAWARE
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: FL
Enumerated_Domain_Value_Definition: FLORIDA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: GA
Enumerated_Domain_Value_Definition: GEORGIA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: HI
Enumerated_Domain_Value_Definition: HAWAII
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: ID
Enumerated_Domain_Value_Definition: IDAHO
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: IL
Enumerated_Domain_Value_Definition: ILLINOIS
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: IN
Enumerated_Domain_Value_Definition: INDIANA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: IA
Enumerated_Domain_Value_Definition: IOWA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: KS
Enumerated_Domain_Value_Definition: KANSAS
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: KY
Enumerated_Domain_Value_Definition: KENTUCKY
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: LA
Enumerated_Domain_Value_Definition: LOUISIANA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: ME
Enumerated_Domain_Value_Definition: MAINE
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: MD
Enumerated_Domain_Value_Definition: MARYLAND
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: MA
Enumerated_Domain_Value_Definition: MASSACHUSETTS
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: MI
Enumerated_Domain_Value_Definition: MICHIGAN
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: MT
Enumerated_Domain_Value_Definition: MONTANA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: NE
Enumerated_Domain_Value_Definition: NEBRASKA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: NV
Enumerated_Domain_Value_Definition: NEVADA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: NH
Enumerated_Domain_Value_Definition: NEW HAMPSHIRE
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: NJ
Enumerated_Domain_Value_Definition: NEW JERSEY
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: NM
Enumerated_Domain_Value_Definition: NEW MEXICO
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: NY
Enumerated_Domain_Value_Definition: NEW YORK
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: NC
Enumerated_Domain_Value_Definition: NORTH CAROLINA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: MN
Enumerated_Domain_Value_Definition: MINNESOTA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: ND
Enumerated_Domain_Value_Definition: NORTH DAKOTA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: MS
Enumerated_Domain_Value_Definition: MISSISSIPPI
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: MO
Enumerated_Domain_Value_Definition: MISSOURI
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: OH
Enumerated_Domain_Value_Definition: OHIO
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: OK
Enumerated_Domain_Value_Definition: OKLAHOMA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: OR
Enumerated_Domain_Value_Definition: OREGON
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: PA
Enumerated_Domain_Value_Definition: PENNSYLVANIA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: PR
Enumerated_Domain_Value_Definition: PUERTO RICO
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: RI
Enumerated_Domain_Value_Definition: RHODE ISLAND
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: SC
Enumerated_Domain_Value_Definition: SOUTH CAROLINA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: SD
Enumerated_Domain_Value_Definition: SOUTH DAKOTA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: TN
Enumerated_Domain_Value_Definition: TENNESSEE
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: TX
Enumerated_Domain_Value_Definition: TEXAS
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: UT
Enumerated_Domain_Value_Definition: UTAH
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: VT
Enumerated_Domain_Value_Definition: VERMONT
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: VA
Enumerated_Domain_Value_Definition: VIRGINIA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: WA
Enumerated_Domain_Value_Definition: WASHINGTON
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: WV
Enumerated_Domain_Value_Definition: WEST VIRGINIA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: WI
Enumerated_Domain_Value_Definition: WISCONSIN
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: WY
Enumerated_Domain_Value_Definition: WYOMING
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute:
Attribute_Label: STFIPS
Attribute_Definition:
State FIPS code - The state Federal Information Processing Standards (FIPS) code.
Attribute_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 01
Enumerated_Domain_Value_Definition: ALABAMA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 02
Enumerated_Domain_Value_Definition: ALASKA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 04
Enumerated_Domain_Value_Definition: ARIZONA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 05
Enumerated_Domain_Value_Definition: ARKANSAS
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 06
Enumerated_Domain_Value_Definition: CALIFORNIA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 08
Enumerated_Domain_Value_Definition: COLORADO
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 09
Enumerated_Domain_Value_Definition: CONNECTICUT
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 10
Enumerated_Domain_Value_Definition: DELAWARE
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 11
Enumerated_Domain_Value_Definition: DISTRICT OF COLUMBIA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 12
Enumerated_Domain_Value_Definition: FLORIDA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 13
Enumerated_Domain_Value_Definition: GEORGIA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 15
Enumerated_Domain_Value_Definition: HAWAII
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 16
Enumerated_Domain_Value_Definition: IDAHO
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 17
Enumerated_Domain_Value_Definition: ILLINOIS
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 18
Enumerated_Domain_Value_Definition: INDIANA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 19
Enumerated_Domain_Value_Definition: IOWA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 20
Enumerated_Domain_Value_Definition: KANSAS
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 21
Enumerated_Domain_Value_Definition: KENTUCKY
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 22
Enumerated_Domain_Value_Definition: LOUISIANA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 23
Enumerated_Domain_Value_Definition: MAINE
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 24
Enumerated_Domain_Value_Definition: MARYLAND
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 25
Enumerated_Domain_Value_Definition: MASSACHUSETTS
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 26
Enumerated_Domain_Value_Definition: MICHIGAN
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 27
Enumerated_Domain_Value_Definition: MINNESOTA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 28
Enumerated_Domain_Value_Definition: MISSISSIPPI
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 29
Enumerated_Domain_Value_Definition: MISSOURI
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 30
Enumerated_Domain_Value_Definition: MONTANA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 31
Enumerated_Domain_Value_Definition: NEBRASKA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 32
Enumerated_Domain_Value_Definition: NEVADA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 33
Enumerated_Domain_Value_Definition: NEW HAMPSHIRE
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 34
Enumerated_Domain_Value_Definition: NEW JERSEY
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 35
Enumerated_Domain_Value_Definition: NEW MEXICO
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 36
Enumerated_Domain_Value_Definition: NEW YORK
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 37
Enumerated_Domain_Value_Definition: NORTH CAROLINA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 38
Enumerated_Domain_Value_Definition: NORTH DAKOTA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 39
Enumerated_Domain_Value_Definition: OHIO
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 40
Enumerated_Domain_Value_Definition: OKLAHOMA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 41
Enumerated_Domain_Value_Definition: OREGON
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 42
Enumerated_Domain_Value_Definition: PENNSYLVANIA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 44
Enumerated_Domain_Value_Definition: RHODE ISLAND
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 45
Enumerated_Domain_Value_Definition: SOUTH CAROLINA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 46
Enumerated_Domain_Value_Definition: SOUTH DAKOTA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 47
Enumerated_Domain_Value_Definition: TENNESSEE
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 48
Enumerated_Domain_Value_Definition: TEXAS
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 49
Enumerated_Domain_Value_Definition: UTAH
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 50
Enumerated_Domain_Value_Definition: VERMONT
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 51
Enumerated_Domain_Value_Definition: VIRGINIA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 53
Enumerated_Domain_Value_Definition: WASHINGTON
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 54
Enumerated_Domain_Value_Definition: WEST VIRGINIA
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 55
Enumerated_Domain_Value_Definition: WISCONSIN
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 56
Enumerated_Domain_Value_Definition: WYOMING
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 72
Enumerated_Domain_Value_Definition: PUERTO RICO
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 78
Enumerated_Domain_Value_Definition: US VIRGIN ISLANDS
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute:
Attribute_Label: PC_NAME
Attribute_Definition:
Postal Code Name - Name of postal (ZIP) code - for non-unique and PO box postal codes this represents the post office name and for unique.
Attribute_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Unrepresentable_Domain: The set of all PC_NAME values
Attribute:
Attribute_Label: PC_TYPE
Attribute_Definition:
Postal Code Classification - Postal code classification for each postal code reference. Postal code types are as follows: NON UNIQUE = General delivery postal code, UNIQUE ORGANIZATION = Unique postal code records for companies receiving large quantities of mail, PO BOX = Post Office box postal codes, and Military = Military Base postal codes.
Attribute_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Military
Enumerated_Domain_Value_Definition: Military
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Non Unique
Enumerated_Domain_Value_Definition: General delivery postal code
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Po Box
Enumerated_Domain_Value_Definition: Post Office Box
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Unique Organization
Enumerated_Domain_Value_Definition:
Unique postal code records for companies receiving large quantities of mail
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute:
Attribute_Label: PA_NAME
Attribute_Definition:
Postal area USPS name - Postal area name (Last line city name from United States Postal Service (USPS) sources).
Attribute_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Unrepresentable_Domain: The set of all PA_NAME values
Attribute:
Attribute_Label: PA_FIPS
Attribute_Definition:
Postal Area FIPS code - Postal Area (Last Line City) Federal Information Processing Standards (FIPS) code.
Attribute_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Unrepresentable_Domain: The set of all PA_FIPS values
Attribute:
Attribute_Label: COUNTY
Attribute_Definition:
County Name - County name within which the applicable postal code falls.
Attribute_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Unrepresentable_Domain: The set of all COUNTY values
Attribute:
Attribute_Label: CTYFIPS
Attribute_Definition:
County FIPS code - County Federal Information Processing Standards (FIPS) code.
Attribute_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Unrepresentable_Domain: The set of all CTYFIPS values
Attribute:
Attribute_Label: ACCURACY
Attribute_Definition:
Accuracy - The positional accuracy of each postal code point location.
Attribute_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: CS
Enumerated_Domain_Value_Definition: County, state centroid accuracy
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: PC
Enumerated_Domain_Value_Definition: Polygon centroid accuracy from Postal Code boundaries
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: S
Enumerated_Domain_Value_Definition: Street level accuracy
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: T
Enumerated_Domain_Value_Definition: Town, county centroid accuracy
Enumerated_Domain_Value_Definition_Source: NAVTEQ
Attribute:
Attribute_Label: NTLINK_ID
Attribute_Definition: Nearest Link Id - Nearest NAVTEQ NAVSTREETS street Link_Id.
Attribute_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Unrepresentable_Domain: The set of all NTLINK_ID values
Attribute:
Attribute_Label: ENC_PC
Attribute_Definition:
Enclosing FSA boundary - Enclosing Canadian Postal FSA (Forward Sortation Area) boundary.
Attribute_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Unrepresentable_Domain: The set of all ENC_PC values
Attribute:
Attribute_Label: SHAPE
Attribute_Definition:
Shape Points - Sets of binary spatial coordinate values representing ESRI geometry objects as Points, Polylines, or Polygons.
Attribute_Definition_Source: NAVTEQ
Attribute_Domain_Values:
Unrepresentable_Domain: The set of all geometry object values.
Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: NAVTEQ
Contact_Address:
Address_Type: Mailing and Physical
Address: 200 I Street SE, 5th Floor
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:
Filename NAAM10200NNA000DBE00.tar NAVTEQ SDC data for the United States, including Puerto Rico and the US Virgin Islands in ESRI's Smart Data Compression (SDC) format. ESRI SDC data is packaged as sets of interdependent files consisting of .sdc geometry and attribute files, .sdi spatial index files, .prj layer projection files, and .edk layer license files. Each layer file set must have the same root name and be located in the same folder. In addition a number of other configuration and indexing files are used to support rapid display and attribute retrieval as well as routing and geocoding. NAVTEQ SDC product data folders contain .mxd and .axl files to support both ArcGIS desktop applications and web based ArcIMS 9 Route Server. SDC product folders also contain a number of .loc locator files for geocoding, reverse geocoding, and routing applications as well as a number of other file types including .prj projection files, SDC Network Datasets, and various supporting XML files. All SDC attributes are stored using the Latin 1 character set. Some layer name and data content differences exist between the SDC and NAVSTREETS products. The standard NAVTEQ product file folder name will comprise up to 23 capitalized alphanumeric characters in the following format: RRCCYYQVVAAADDDBBBBB.ZZZ where RR = Sub Region Code, CC = Clipping/Merge Code, YY = Year Code, Q = Year Quarter, VV = version, AAADDD = Region Identification Code, BBBBB = Product Type Code, and ZZZ = compression method. For a full description of all SDC file types and functions see the latest ESRI SM_Data_Specs_NAVTEQ_NA_QQYY_Desktop.pdf and SDC_NA_QQYY_Release_Notes.pdf files where QQYY indicates the current calendar quarter and year.
Distribution_Liability:
For data terms and conditions, go to <http://dc.gov/page/terms-and-conditions-use-district-data>
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Format_Name: ESRI Smart Data Compression (SDC)
Format_Version_Number: 2.0
Transfer_Size: 3.9 GB
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: All data is available at <http://opendata.dc.gov>
Metadata_Reference_Information:
Metadata_Date: 20100401
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: NAVTEQ Technical Customer Support
Contact_Address:
Address_Type: Mailing and Physical
Address: 200 I Street SE, 5th Floor
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 Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
Generated by mp version 2.9.12 on Thu Jun 25 15:19:27 2015