NAVTEQ 2010 Q2 Travel Destination Points for the United States, including Puerto Rico and the US Virgin Islands, Canada and Mexico in SDC Format, Released Quarterly.
Metadata also available as
Metadata:
- Identification_Information:
-
- Citation:
-
- Citation_Information:
-
- Originator: NAVTEQ
- Publication_Date: 20100401
- Title:
-
NAVTEQ 2010 Q2 Travel Destination Points for the United States, including Puerto Rico and the US Virgin Islands, Canada and Mexico 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 TRAVDEST layer contains all hotels, motels, significant tourist attractions, and tourist information locations. This layer is used for destination selection, geocoding, and map visualisation. Note that a travel destination is represented by multiple point objects when it has names in multiple languages. 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: -166.553060
- East_Bounding_Coordinate: -52.624729
- North_Bounding_Coordinate: 71.290191
- South_Bounding_Coordinate: 14.654700
- Keywords:
-
- Theme:
-
- Theme_Keyword_Thesaurus: ISO 19115 Topic Category
- Theme_Keyword: location
- Theme_Keyword: economy
- Theme_Keyword: society
- Theme_Keyword: structure
- 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: convention centres
- Theme_Keyword: guest houses
- Theme_Keyword: historical monuments
- Theme_Keyword: hotels
- Theme_Keyword: motels
- Theme_Keyword: rental cars
- Theme_Keyword: rest areas
- Theme_Keyword: ski resorts
- Theme_Keyword: tourist attractions
- Theme_Keyword: tourist information
- Theme_Keyword: wineries
- Place:
-
- Place_Keyword_Thesaurus: None
- Place_Keyword:
-
the United States, including Puerto Rico and the US Virgin Islands, Canada and Mexico
- 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:
-
The position of POI data is determined through a geocoding process, using linear interpolation along a street segment. Positions are therefore relatively accurate along the segment, but may not necessarily fall on the exact physical location of the POI.
- 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:
-
Individual POI files are extracted from a single central master POI database containing all POI data. NAVTEQ POI data points are generated from a geocoding process whereby textual address information is used to locate a point along a NAVTEQ street segment, using linear interpolation against left and right low and high address ranges.
- 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\travdest.sdc.xml
- Process_Date: 20101015
- Process_Time: 08433000
- Process_Step:
-
- Process_Description: Metadata imported.
- Source_Used_Citation_Abbreviation: C:\temp\travdest.xml
- Process_Date: 20120313
- Process_Time: 15260200
- 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: TRAVDEST
- Entity_Type_Definition:
-
Travel Destinations - The TRAVDEST layer contains all hotels, motels, significant tourist attractions, and tourist information locations. This layer is used for destination selection, geocoding, and map visualisation. Note that a travel destination is represented by multiple point 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: LINK_ID
- Attribute_Definition:
-
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.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Unrepresentable_Domain: The set of all LINK_ID values
- Attribute:
-
- Attribute_Label: POI_ID
- Attribute_Definition:
-
POI ID - Unique number used to identify each POI (Point of Interest) in the NAVTEQ database. This set of unique integer identifiers provides primary keys and is consistent between dataset versions.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Unrepresentable_Domain: The set of all POI_ID values
- Attribute:
-
- Attribute_Label: SEQ_NUM
- Attribute_Definition:
-
Sequence Number - Each POI is duplicated when it has multiple names. The Sequence Number is necessary in order to distinctly associate a POI Transliteration to its correct POI Name.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Unrepresentable_Domain: The set of all SEQ_NUM values
- Attribute:
-
- Attribute_Label: FAC_TYPE
- Attribute_Definition:
-
Facility Type - The 4-digit code that identifies the POI Facility Type.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: 2084
- Enumerated_Domain_Value_Definition: Winery
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: 5999
- Enumerated_Domain_Value_Definition: Historical Monument
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: 7011
- Enumerated_Domain_Value_Definition: Hotel
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: 7012
- Enumerated_Domain_Value_Definition: Ski Resort
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: 7389
- Enumerated_Domain_Value_Definition: Tourist Information
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: 7510
- Enumerated_Domain_Value_Definition: Rental Car Agency
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: 7897
- Enumerated_Domain_Value_Definition: Rest Area
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: 7990
- Enumerated_Domain_Value_Definition: Convention/Exhibition Centre
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: 7999
- Enumerated_Domain_Value_Definition: Tourist Attraction
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute:
-
- Attribute_Label: POI_NAME
- Attribute_Definition: POI Name - The name by which the POI is known.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Unrepresentable_Domain: The set of all POI_NAME values
- Attribute:
-
- Attribute_Label: POI_LANGCD
- Attribute_Definition:
-
POI Language Code - A code to indicate the language used for the POI name.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: ENG
- Enumerated_Domain_Value_Definition: ENGLISH
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: FRE
- Enumerated_Domain_Value_Definition: FRENCH
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: SPA
- Enumerated_Domain_Value_Definition: SPANISH
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute:
-
- Attribute_Label: POI_NMTYPE
- Attribute_Definition:
-
POI Name Type - The word type for the POI name. All POI Name Types (Base, Exonyms, Synonyms, and Unnamed) can be used for destination selection and map display for languages supported by NAVTEQ.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: B
- Enumerated_Domain_Value_Definition:
-
Base name. If multiple names exist for a particular POI, the base name represents the POI name in the country's official language.
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: E
- Enumerated_Domain_Value_Definition:
-
Exonym. An exonym is a name that is different in another language than it is in the National Language. Exonyms may also be translations of the official name. In Canada, if settlements in French speaking provinces have names in two different languages, the
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: S
- Enumerated_Domain_Value_Definition:
-
Synonym. A synonym is a name in the National Language which is different than the official name.
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: U
- Enumerated_Domain_Value_Definition: Unnamed
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute:
-
- Attribute_Label: POI_ST_NUM
- Attribute_Definition: POI Street Number - The POI's actual street number.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Unrepresentable_Domain: The set of all POI_ST_NUM values
- Attribute:
-
- Attribute_Label: ST_NUM_FUL
- Attribute_Definition: Full POI Street Number - Full POI Street Number.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Unrepresentable_Domain: The set of all ST_NUM_FUL values
- Attribute:
-
- Attribute_Label: ST_NFUL_LC
- Attribute_Definition:
-
Full POI Street Number Language Code - Full POI Street Number Language Code.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Unrepresentable_Domain: The set of all ST_NFUL_LC values
- Attribute:
-
- Attribute_Label: ST_NAME
- Attribute_Definition:
-
Street 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.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Unrepresentable_Domain: The set of all ST_NAME values
- Attribute:
-
- Attribute_Label: ST_LANGCD
- Attribute_Definition:
-
Street Name Language Code - A code to indicate what language to use when displaying the Street Name.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: ENG
- Enumerated_Domain_Value_Definition: ENGLISH
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: FRE
- Enumerated_Domain_Value_Definition: FRENCH
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: SPA
- Enumerated_Domain_Value_Definition: SPANISH
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute:
-
- Attribute_Label: POI_ST_SD
- Attribute_Definition:
-
POI Street Side - Identifies the side of the street on which the POI is located in situations where the link is valid unaddressed, contains mixed addresses, or the POI is unaddressed.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: L
- Enumerated_Domain_Value_Definition: Left
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: R
- Enumerated_Domain_Value_Definition: Right
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: N
- Enumerated_Domain_Value_Definition: Not Applicable
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute:
-
- Attribute_Label: ACC_TYPE
- Attribute_Definition: Access Type - This field is no longer in use.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Unrepresentable_Domain: The set of all ACC_TYPE values
- Attribute:
-
- Attribute_Label: PH_NUMBER
- Attribute_Definition: Phone Number - The phone number for the POI.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Unrepresentable_Domain: The set of all PH_NUMBER values
- Attribute:
-
- Attribute_Label: CHAIN_ID
- Attribute_Definition:
-
Chain ID - The code that identifies the commercial chain associated with the POI.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Unrepresentable_Domain: The set of all CHAIN_ID values
- Attribute:
-
- Attribute_Label: NAT_IMPORT
- Attribute_Definition:
-
Nationally Important - Indicates if the POI name is recognizable without a city name. For example, The Empire State Building is recognizable without the city name of New York.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: Y
- Enumerated_Domain_Value_Definition: Is recognizable without a city name.
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: N
- Enumerated_Domain_Value_Definition: Is not recognizable without a city name.
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute:
-
- Attribute_Label: PRIVATE
- Attribute_Definition:
-
Private - For a street, indicates if the street is private. For a POI, indicates if POI normally requires membership for admission.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: Y
- Enumerated_Domain_Value_Definition: Private
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: N
- Enumerated_Domain_Value_Definition: Not Private
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute:
-
- Attribute_Label: IN_VICIN
- Attribute_Definition:
-
In Vicinity - Indicates whether a POI is located directly on the road with which it is associated.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: Y
- Enumerated_Domain_Value_Definition:
-
POI is located directly on the road with which it is associated.
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: N
- Enumerated_Domain_Value_Definition:
-
POI is not located directly on the road with which it is associated.
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute:
-
- Attribute_Label: NUM_PARENT
- Attribute_Definition:
-
Number of Parents - The number of POI parents that exist in the POI Association layer.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Range_Domain:
-
- Range_Domain_Minimum: 0
- Range_Domain_Maximum: 10
- Attribute:
-
- Attribute_Label: NUM_CHILD
- Attribute_Definition:
-
Number of Children - The number of POI children that exist in the POI Association layer.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Range_Domain:
-
- Range_Domain_Minimum: 0
- Range_Domain_Maximum: 100
- Attribute:
-
- Attribute_Label: PERCFRREF
- Attribute_Definition:
-
Percent From Reference Node - Indicates the location of the Point of Interest (POI) on the link in terms of percent from the reference node. Percent from Reference Node can be used to determine icon placement and timing of guidance information. This is particularly useful when POIs do not have an address, the road does not carry addresses, or when the POI is located on a very long link.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Unrepresentable_Domain: The set of all PERCFRREF values
- Attribute:
-
- Attribute_Label: VAN_CITY
- Attribute_Definition:
-
Vanity City - Identifies a city that is different from the city where the POI is physically located. For example, Charles-de-Gaulle airport is located in Roissy-en-France, not in Paris. It is common, however, for people to think the airport is in Paris.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Unrepresentable_Domain: The set of all VAN_CITY values
- Attribute:
-
- Attribute_Label: ACT_ADDR
- Attribute_Definition:
-
Actual Address - The Actual Address is an address that is different from the street address where the entrance of the POI is physically located.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Unrepresentable_Domain: The set of all ACT_ADDR values
- Attribute:
-
- Attribute_Label: ACT_LANGCD
- Attribute_Definition:
-
Actual Address Language Code - A code to indicate what language to use when displaying the Actual Address. See the Name Language Code attribute (NM_LANGCD) for a list of valid values.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Unrepresentable_Domain: The set of all ACT_LANGCD values
- Attribute:
-
- Attribute_Label: ACT_ST_NAM
- Attribute_Definition: Actual Street Name - The parsed Actual Street Name for the POI.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Unrepresentable_Domain: The set of all ACT_ST_NAM values
- Attribute:
-
- Attribute_Label: ACT_ST_NUM
- Attribute_Definition:
-
Actual Street Number - The parsed Actual Street Number of the POI.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Unrepresentable_Domain: The set of all ACT_ST_NUM values
- Attribute:
-
- Attribute_Label: ACT_ADMIN
- Attribute_Definition:
-
Actual Administrative Area - The parsed Actual Admin name of the POI. Up to two admin names can be published separated by a comma.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Unrepresentable_Domain: The set of all ACT_ADMIN values
- Attribute:
-
- Attribute_Label: ACT_POSTAL
- Attribute_Definition: Actual Postal Code - The parsed Actual Postal Code of the POI.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Unrepresentable_Domain: The set of all ACT_POSTAL values
- Attribute:
-
- Attribute_Label: ENTR_TYPE
- Attribute_Definition:
-
Entrance Type - Entrance Type identifies whether or not the entrance is the preferred entrance to a facility. Entrance Type can be used for destination selection and map display to identify preferred entrances to a POI.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: Y
- Enumerated_Domain_Value_Definition: Preferred Entrance
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: N
- Enumerated_Domain_Value_Definition: Not Preferred Entrance
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute:
-
- Attribute_Label: REST_TYPE
- Attribute_Definition:
-
Rest Area Type - A code indicating the type of services available at a rest area.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: 1
- Enumerated_Domain_Value_Definition:
-
Complete Rest Area - applied to rest areas which include all facilities like Petrol Station, Restaurant, Parking etc.
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: 2
- Enumerated_Domain_Value_Definition:
-
Parking and Rest Room - applied to rest areas that provide both parking and a rest room.
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: 3
- Enumerated_Domain_Value_Definition:
-
Parking Only - applied to rest areas that provide parking, but not a rest room.
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: 4
- Enumerated_Domain_Value_Definition:
-
Motorway Service Area - applied to areas that provide service to the motorway, but require the driver to exit the motorway for access.
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute:
-
- Attribute_Label: STATE_NM
- Attribute_Definition: State Name - The name of the state or province.
- Attribute_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: ALABAMA
- Enumerated_Domain_Value_Definition: The US State of ALABAMA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: ALASKA
- Enumerated_Domain_Value_Definition: The US State of ALASKA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: ARIZONA
- Enumerated_Domain_Value_Definition: The US State of ARIZONA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: ARKANSAS
- Enumerated_Domain_Value_Definition: The US State of ARKANSAS
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: CALIFORNIA
- Enumerated_Domain_Value_Definition: The US State of CALIFORNIA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: COLORADO
- Enumerated_Domain_Value_Definition: The US State of COLORADO
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: CONNECTICUT
- Enumerated_Domain_Value_Definition: The US State of CONNECTICUT
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: DELAWARE
- Enumerated_Domain_Value_Definition: The US State of DELAWARE
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: FLORIDA
- Enumerated_Domain_Value_Definition: The US State of FLORIDA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: GEORGIA
- Enumerated_Domain_Value_Definition: The US State of GEORGIA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: HAWAII
- Enumerated_Domain_Value_Definition: The US State of HAWAII
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: IDAHO
- Enumerated_Domain_Value_Definition: The US State of IDAHO
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: ILLINOIS
- Enumerated_Domain_Value_Definition: The US State of ILLINOIS
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: INDIANA
- Enumerated_Domain_Value_Definition: The US State of INDIANA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: IOWA
- Enumerated_Domain_Value_Definition: The US State of IOWA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: KANSAS
- Enumerated_Domain_Value_Definition: The US State of KANSAS
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: KENTUCKY
- Enumerated_Domain_Value_Definition: The US State of KENTUCKY
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: LOUISIANA
- Enumerated_Domain_Value_Definition: The US State of LOUISIANA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: MAINE
- Enumerated_Domain_Value_Definition: The US State of MAINE
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: MARYLAND
- Enumerated_Domain_Value_Definition: The US State of MARYLAND
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: MASSACHUSETTS
- Enumerated_Domain_Value_Definition: The US State of MASSACHUSETTS
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: MICHIGAN
- Enumerated_Domain_Value_Definition: The US State of MICHIGAN
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: MONTANA
- Enumerated_Domain_Value_Definition: The US State of MONTANA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: NEBRASKA
- Enumerated_Domain_Value_Definition: The US State of NEBRASKA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: NEVADA
- Enumerated_Domain_Value_Definition: The US State of NEVADA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: NEW HAMPSHIRE
- Enumerated_Domain_Value_Definition: The US State of NEW HAMPSHIRE
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: NEW JERSEY
- Enumerated_Domain_Value_Definition: The US State of NEW JERSEY
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: NEW MEXICO
- Enumerated_Domain_Value_Definition: The US State of NEW MEXICO
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: NEW YORK
- Enumerated_Domain_Value_Definition: The US State of NEW YORK
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: NORTH CAROLINA
- Enumerated_Domain_Value_Definition: The US State of NORTH CAROLINA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: MINNESOTA
- Enumerated_Domain_Value_Definition: The US State of MINNESOTA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: NORTH DAKOTA
- Enumerated_Domain_Value_Definition: The US State of NORTH DAKOTA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: MISSISSIPPI
- Enumerated_Domain_Value_Definition: The US State of MISSISSIPPI
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: MISSOURI
- Enumerated_Domain_Value_Definition: The US State of MISSOURI
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: OHIO
- Enumerated_Domain_Value_Definition: The US State of OHIO
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: OKLAHOMA
- Enumerated_Domain_Value_Definition: The US State of OKLAHOMA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: OREGON
- Enumerated_Domain_Value_Definition: The US State of OREGON
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: PENNSYLVANIA
- Enumerated_Domain_Value_Definition: The US State of PENNSYLVANIA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: RHODE ISLAND
- Enumerated_Domain_Value_Definition: The US State of RHODE ISLAND
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: SOUTH CAROLINA
- Enumerated_Domain_Value_Definition: The US State of SOUTH CAROLINA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: SOUTH DAKOTA
- Enumerated_Domain_Value_Definition: The US State of SOUTH DAKOTA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: TENNESSEE
- Enumerated_Domain_Value_Definition: The US State of TENNESSEE
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: TEXAS
- Enumerated_Domain_Value_Definition: The US State of TEXAS
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: UTAH
- Enumerated_Domain_Value_Definition: The US State of UTAH
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: VERMONT
- Enumerated_Domain_Value_Definition: The US State of VERMONT
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: VIRGINIA
- Enumerated_Domain_Value_Definition: The US State of VIRGINIA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: WASHINGTON
- Enumerated_Domain_Value_Definition: The US State of WASHINGTON
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: WASHINGTON, D.C.
- Enumerated_Domain_Value_Definition: The US District of WASHINGTON, D.C.
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: WEST VIRGINIA
- Enumerated_Domain_Value_Definition: The US State of WEST VIRGINIA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: WISCONSIN
- Enumerated_Domain_Value_Definition: The US State of WISCONSIN
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: WYOMING
- Enumerated_Domain_Value_Definition: The US State of WYOMING
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: PUERTO RICO
- Enumerated_Domain_Value_Definition: The US Territory of PUERTO RICO
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: US VIRGIN ISLANDS
- Enumerated_Domain_Value_Definition: The US Territory of the VIRGIN ISLANDS
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: ALBERTA
- Enumerated_Domain_Value_Definition: The Canadian Province of ALBERTA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: BRITISH COLUMBIA
- Enumerated_Domain_Value_Definition: The Canadian Province of BRITISH COLUMBIA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: MANITOBA
- Enumerated_Domain_Value_Definition: The Canadian Province of MANITOBA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: NEW BRUNSWICK
- Enumerated_Domain_Value_Definition: The Canadian Province of NEW BRUNSWICK
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: NEWFOUNDLAND AND LABRADOR
- Enumerated_Domain_Value_Definition: The Canadian Province of NEWFOUNDLAND AND LABRADOR
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: NORTHWEST TERRITORIES
- Enumerated_Domain_Value_Definition: The Canadian Province of NORTHWEST TERRITORIES
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: NOVA SCOTIA
- Enumerated_Domain_Value_Definition: The Canadian Province of NOVA SCOTIA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: NUNAVUT
- Enumerated_Domain_Value_Definition: The Canadian Province of NUNAVUT
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: ONTARIO
- Enumerated_Domain_Value_Definition: The Canadian Province of ONTARIO
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: PRINCE EDWARD ISLAND
- Enumerated_Domain_Value_Definition: The Canadian Province of PRINCE EDWARD ISLAND
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: QUEBEC
- Enumerated_Domain_Value_Definition: The Canadian Province of QUEBEC
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: SASKATCHEWAN
- Enumerated_Domain_Value_Definition: The Canadian Province of SASKATCHEWAN
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: YUKON
- Enumerated_Domain_Value_Definition: The Canadian Province of YUKON
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: AGUASCALIENTES
- Enumerated_Domain_Value_Definition: The Mexican State of AGUASCALIENTES
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: BAJA CALIFORNIA
- Enumerated_Domain_Value_Definition: The Mexican State of BAJA CALIFORNIA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: BAJA CALIFORNIA SUR
- Enumerated_Domain_Value_Definition: The Mexican State of BAJA CALIFORNIA SUR
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: CAMPECHE
- Enumerated_Domain_Value_Definition: The Mexican State of CAMPECHE
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: CHIAPAS
- Enumerated_Domain_Value_Definition: The Mexican State of CHIAPAS
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: CHIHUAHUA
- Enumerated_Domain_Value_Definition: The Mexican State of CHIHUAHUA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: COAHUILA
- Enumerated_Domain_Value_Definition: The Mexican State of COAHUILA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: COLIMA
- Enumerated_Domain_Value_Definition: The Mexican State of COLIMA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: DISTRITO FEDERAL
- Enumerated_Domain_Value_Definition: The Mexican District of DISTRITO FEDERAL
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: DURANGO
- Enumerated_Domain_Value_Definition: The Mexican State of DURANGO
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: GUANAJUATO
- Enumerated_Domain_Value_Definition: The Mexican State of GUANAJUATO
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: GUERRERO
- Enumerated_Domain_Value_Definition: The Mexican State of GUERRERO
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: HIDALGO
- Enumerated_Domain_Value_Definition: The Mexican State of HIDALGO
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: JALISCO
- Enumerated_Domain_Value_Definition: The Mexican State of JALISCO
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: MEXICO
- Enumerated_Domain_Value_Definition: The Mexican State of MEXICO
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: MICHOACÃN
- Enumerated_Domain_Value_Definition: The Mexican State of MICHOACÃN
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: MORELOS
- Enumerated_Domain_Value_Definition: The Mexican State of MORELOS
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: NAYARIT
- Enumerated_Domain_Value_Definition: The Mexican State of NAYARIT
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: NUEVO LEÓN
- Enumerated_Domain_Value_Definition: The Mexican State of NUEVO LEÓN
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: OAXACA
- Enumerated_Domain_Value_Definition: The Mexican State of OAXACA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: PUEBLA
- Enumerated_Domain_Value_Definition: The Mexican State of PUEBLA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: QUERÉTARO
- Enumerated_Domain_Value_Definition: The Mexican State of QUERÉTARO
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: QUINTANA ROO
- Enumerated_Domain_Value_Definition: The Mexican State of QUINTANA ROO
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: SAN LUIS POTOS
- Enumerated_Domain_Value_Definition: The Mexican State of SAN LUIS POTOS
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: SINALOA
- Enumerated_Domain_Value_Definition: The Mexican State of SINALOA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: SONORA
- Enumerated_Domain_Value_Definition: The Mexican State of SONORA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: TABASCO
- Enumerated_Domain_Value_Definition: The Mexican State of TABASCO
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: TAMAULIPAS
- Enumerated_Domain_Value_Definition: The Mexican State of TAMAULIPAS
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: TLAXCALA
- Enumerated_Domain_Value_Definition: The Mexican State of TLAXCALA
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: VERACRUZ
- Enumerated_Domain_Value_Definition: The Mexican State of VERACRUZ
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: YUCATÃN
- Enumerated_Domain_Value_Definition: The Mexican State of YUCATÃN
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- Attribute_Domain_Values:
-
- Enumerated_Domain:
-
- Enumerated_Domain_Value: ZACATECAS
- Enumerated_Domain_Value_Definition: The Mexican State of ZACATECAS
- Enumerated_Domain_Value_Definition_Source: NAVTEQ
- 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, Canada and Mexico 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:26 2015