US EPA National Geospatial Support (NGS) Team
U.S. Environmental Protection Agency, Research Triangle Park
OEI RTP NCC GIS
919-767-7493
USEPA Mailroom N127-02
Research Triangle Park
NC
27711
geoservices@epa.gov
http://intranet.epa.gov/rtpgis
20130928
ArcGIS Metadata
1.0
US EPA National Geospatial Support (NGS) Team
U.S. Environmental Protection Agency, Research Triangle Park
OEI RTP NCC GIS
919-767-7493
USEPA Mailroom N127-02
Research Triangle Park
NC
27711
geoservices@epa.gov
http://intranet.epa.gov/rtpgis
Contact NAVTEQ Sales for most current pricing information.
Call 312-894-7000
ESRI Shape File and supplemental documentation packaged as sets of .tar and .tar.gz compressed coverage area folders. For data packaging and delivery, these NAVTEQ coverage areas are organized using 3 world areas including: Americas, Asia Pacific (APAC), and Europe, Middle East, Africa (EMEA).
ArcGIS 9.x
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.
NAVTEQ Product Folder: americas\usa_dca1\2011q2\D1AM09202ND1ADX, File: Streets, in ESRI Shape File format. NAVTEQ data folders are organized using a 4-5 level hierarchy. The 1st level consists of 3 global areas including 1) The Americas, 2) Asia-Pacific (APAC) and 3) Europe, The Middle East, and Africa (EMEA). These 3 global areas are then divided into approximately 60 2nd level areas as countries, e.g., Argentina, regions within a country, e.g., North America DCA7, or several countries together, e.g., Spain and Portugal. The 3rd level folders correspond to a specific year and quarter release date, e.g., 2011q2. The 4th and 5th level folders use NAVTEQ's standard product file naming. The standard product file folder name will comprise up to 17 capitalized alphanumeric characters in the following format: RRCCYYQVVAAABBB.ZZ where RR = Sub Region Code, CC = Clipping/Merge Code, YY = Year Code, Q = Year Quarter, VV = version, AAA = Region Identification, BBB = Product Identification Code, and ZZ = compression method. In some cases, the data files for a NAVTEQ coverage area will be packaged in a single country folder, e.g., Thailand, in other cases, multiple sets of data files for a country will be packaged as multiple sub region folders under a single top level grouping folder, e.g., France. NAVTEQ NAVSTREETS is comprised of approximately 40 GIS layers and 30 related dbf tabular datasets. Prior to Q2 2011, the related tabular datasets were packaged as empty shapefiles with only the dbf files containing data. As of Q2, 2011, these related tabular datasets are no longer packaged as empty shapefiles and are now delivered as single dbf files. For fully describing the entity and attribute information contained in these dbf only tabular datasets, NAVTEQ does provide FGDC metadata files, and describes them using an FGDC Vector Type of Point. For areas of the world using non Latin-1 (ISO-8859-1) character sets for local language representation, NAVTEQ provides supplemental matching Unicode (UTF-8) based or "look-aside" files for many dataset attributes. When Unicode based data is available for a NAVTEQ coverage area, it will be packaged into a separate and complete NAVTEQ coverage area folder using a different Product Identification Code. This folder will contain both the main Latin-1 based and the supplemental Unicode files. The Unicode based data files will be found in the LAT subfolder, and named with .uni file extension. Empty Layers Note: Layers such as WaterWys, Adminbndy3, Adminbndy4, and MajHwys, MajHwyShield, various POI layers, etc., could potentially be empty, depending on the coverage and regional inclusion of the data. In addition, depending upon the situation, the layersAdminBndy1 and AdminBndy2 can be empty as a result of cases where regional divisions of NAVTEQ products do not align with real-world geo-political boundaries. To help users get started with viewing and using layers and data tables, as of Q2, 2011, NAVTEQ also provides an ArcGIS/ArcMap.mxd, and an MXD_Readme.txt file, located in the Region folder containing the ESRI Shapefiles. NAVTEQ data can also be used with other GIS software including MapInfo and is available in a variety of other formats including RDF (Relational Data Format), GDF (Geographic Data Format), SIF+ (Standard Interchange Format), POI XML, and ODF (Oracle Delivery Format).
http://NAVTEQ.com
File Geodatabase Feature Class
NAVTEQ Streets for the United States.
2013-09-28
NAVTEQ
Chicago, IL
NAVTEQ
Vector digital data
NAVTEQ NAVSTREETS, available for 77 countries on 6 continents, is organized into 4 categories of geospatial data layers and related tabular datasets including 1) Road Features and Associated Navigation Information, 2) Points of Interest (POIs), 3) Administrative Areas and Other Cartography, and 4) Metadata. These datasets include Streets, Major Highways, Secondary Highways, Signs, Driving Conditions, Traffic, Travel Destinations, Parking, Named Places, Auto Maintenance, Service, and Petrol, Hospitals, Restaurants, Shopping, Business Facilities, Entertainment, Financial Institutions, Educational Institutions, Transportation Hubs, Border Crossings, Parks and Recreation, Community Service Centres, Country, State, and other Administrative Areas, Buildings, Landmarks, Railroads, Land Use, Waterways, Islands, and Oceans, and other related information. NAVTEQ global map data includes approximately 19 million roadway miles (over 30.5 million kilometers) and over 40 million POIs in approximately 50 categories.
NAVTEQ Streets for the United States. The Streets layer contains all roads plus all Road Network attributes such as direction of travel, lanes, dividers, speed category, and access restrictions. This layer is suitable for routing applications, as it represents the complete navigable road network. For intersection-driven routing applications, the Z Levels layer can also be used to establish roadway connectivity. This layer contains address ranges for all addressable lines and polylines and is also used for geocoding. NAVSTREETS provides Addresses for each end of a line or polyline. "From" addresses correspond to the "Reference" end of the line or polyline, and "To" addresses correspond to the "Non-Reference" end of the line or polyline. This dataset is a subset of the full NAVTEQ NAVSTREETS database.
With the most accurate geometry, the highest number of attributes, and the most complete detailed coverage, NAVTEQ data is the ideal resource for Fleet applications that offer route planning and optimization, and GIS geocoding and other applications that require superior accuracy, and location-enabled services, from Personal Navigation Devices (PNDs) and mobile social networking, to location-enabled entertainment, leisure, and business applications. Products, applications, and services that rely on digital mapping data can ensure superior performance and accuracy by using NAVSTREETS. NAVTEQ data drives most in-vehicle navigation systems around the world, the top routing Web sites, and the leading brands of wireless devices. Designed for rapid display and retrieval of attributes for routing, NAVTEQ data additionally provides support for express mail services, emergency and government routing plans, efficient field service management, wireless Location Based Services (LBS), and delivery of real-time traffic information.
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.
US EPA National Geospatial Support (NGS) Team
U.S. Environmental Protection Agency, Research Triangle Park
OEI RTP NCC GIS
919-767-7493
USEPA Mailroom N127-02
Research Triangle Park
NC
27711
geoservices@epa.gov
http://intranet.epa.gov/rtpgis
United States
geocoding
routing
NAVTEQ
navigation
roadmap
street
transportation
location
ISO 19115 Topic Category
geocoding
routing
transportation
NAVTEQ
navigation
United States
roadmap
location
street
This data can only be distributed to NAVTEQ customers, as detailed specifically in NAVTEQ licensing terms and agreements.
Access to this data is allowed only to NAVTEQ customers, as detailed specifically in NAVTEQ licensing terms and agreements.
FIPS Pub 199
Standard Technical Controls
This data can only be used by NAVTEQ customers, as detailed specifically in NAVTEQ licensing terms and agreements.
NAVTEQ NAVSTREETS, available for 77 countries on 6 continents, is organized into 4 categories of geospatial data layers and related tabular datasets including 1) Road Features and Associated Navigation Information, 2) Points of Interest (POIs), 3) Administrative Areas and Other Cartography, and 4) Metadata. These datasets include Streets, Major Highways, Secondary Highways, Signs, Driving Conditions, Traffic, Travel Destinations, Parking, Named Places, Auto Maintenance, Service, and Petrol, Hospitals, Restaurants, Shopping, Business Facilities, Entertainment, Financial Institutions, Educational Institutions, Transportation Hubs, Border Crossings, Parks and Recreation, Community Service Centres, Country, State, and other Administrative Areas, Buildings, Landmarks, Railroads, Land Use, Waterways, Islands, and Oceans, and other related information. NAVTEQ global map data includes approximately 19 million roadway miles (over 30.5 million kilometers) and over 40 million POIs in approximately 50 categories.
2013-09-28
NAVTEQ
Vector digital data
http://NAVTEQ.com
NAVTEQ NAVSTREETS, available for 77 countries on 6 continents, is organized into 4 categories of geospatial data layers and related tabular datasets including 1) Road Features and Associated Navigation Information, 2) Points of Interest (POIs), 3) Administrative Areas and Other Cartography, and 4) Metadata. These datasets include Streets, Major Highways, Secondary Highways, Signs, Driving Conditions, Traffic, Travel Destinations, Parking, Named Places, Auto Maintenance, Service, and Petrol, Hospitals, Restaurants, Shopping, Business Facilities, Entertainment, Financial Institutions, Educational Institutions, Transportation Hubs, Border Crossings, Parks and Recreation, Community Service Centres, Country, State, and other Administrative Areas, Buildings, Landmarks, Railroads, Land Use, Waterways, Islands, and Oceans, and other related information. NAVTEQ global map data includes approximately 19 million roadway miles (over 30.5 million kilometers) and over 40 million POIs in approximately 50 categories.
2013-09-28
NAVTEQ
Vector digital data
http://NAVTEQ.com
Platform: PC-Intel; Operating System: Windows 2000 or Windows XP (Home Edition and Professional); Memory: 512 MB RAM; Processor: 1 GHz;
-124.40962
-114.03937
32.53429
42.00946
Publication date
2013-09-28
NAVTEQ maps provide a highly accurate representation of the detailed road network including hundreds of attributes such as turn restrictions, physical barriers and gates, one-way streets, restricted access and relative road heights. NAVTEQ digital map data offers accuracy, detail, reliability, and flexibility. Continuously updated to maintain its freshness and precision, NAVTEQ digital map data not only enables door-to-door routing it contains millions of Points of Interest (POIs), making it easy to locate everything from restaurants to hospitals and gas stations. NAVTEQ data are found onboard most navigation-enabled vehicles produced around the world and on all the top Internet navigation sites. It is the unseen force behind the leading express mail services, emergency and government routing plans, efficient field service management, as well as numerous fleet operations, worldwide. Plus, it is the foundation for a growing category of wireless, Location Based Services (LBS). NAVTEQ offers digital map coverage in 77 countries on 6 continents. In addition to widely used GIS formats, including ESRI and MapInfo, data are also available in a number of other formats including RDF (Relational Data Format), GDF (Geographic Data Format), SIF+ (Standard Interchange Format), POI XML, and ODF (Oracle Delivery Format). An in-depth description of NAVTEQ datasets, data processing methodology, geometry, attributes, and metadata is provided to NAVTEQ customers through the NAVSTREETS Reference Manual and a number of other supplemental documents. NAVTEQ documentation uses standardized British spelling.
20161231
NAVTEQ data contains the most navigable attributes available in a database. Utilizing the data to its fullest allows the user to access Layers such as expressway ramps, complete and correct connectivity of all roadways, one-way streets, physical, logical, and legal turn restrictions, construction projects, as well as physical and painted lane dividers. In addition to these navigable attributes, NAVTEQ data provides address ranges down to the level of the correct side of the street.
NAVTEQ provides 4 levels of street map coverage: Detailed City, Inter-Town, In-Process Data and Connector areas. Detailed City is NAVTEQ's highest level of coverage. This coverage level has the most detail and enables door-to-door routing functionality. Inter-Town coverage includes the main highway network and all the necessary attributes required to allow routing from city to city. Inter-Town links are coded with attributes Detailed City Inclusion = N and In-Process Data = N. For Inter-town links, the Full Geometry attribute flag may be set to either yes or no depending on the presence or lack of surrounding In-Process Data Coverage. In many countries, NAVTEQ has used a commercial source to add local roads to the Inter-Town network. The inclusion of this geometry allows improved map display and guidance. This coverage level is called Full Coverage in the U.S. and Road Network Coverage in Europe. The Connector Specification enables NAVTEQ to maintain minimum coverage in areas prior to completing (full) Detailed City (DC), Inter Town (IT), or In-Process areas. For defining a hierarchical network used to determine a logical and efficient route for a traveller, each NAVTEQ street segment is tagged with a 5 level Functional Class (FC) attribute explained as follows. FC 1: Very long distance routes between major cities - The "highest level" network comprises the FC 1 arterials, which are primarily controlled access highways designed for very-long-distance travel linking major metropolitan areas and cities, FC 2: Primary routes between major and smaller cities and through metro areas, FC 3: Major routes between minor cities or towns, and through city districts, FC 4: Routes connecting minor towns or villages and collecting the local traffic in the city districts, and FC 5: Roads that are not efficient through routes - The "lowest level" and final category is FC 5, which comprises roads not considered to be arterials or transportation corridors.
NAVTEQ field office staff drives the roads and streets to collect and verify new data. In addition, internal test applications are regularly run on attributes to assist in verification and correction. NAVTEQ also publishes Technical Notification Memorandums (TNM) for customers on a quarterly basis. These TNMs include information pertaining to product updates, format changes, new attributes, detailed attribute specifications and representations, and new country coverage announcements. If NAVTEQ plans to add, remove, or change an attribute or product Layer, an announcement is made to customers a minimum of 6 months in advance. This allows customers to prepare and make necessary modifications to their applications before a new attribute is released in the product.
The positional accuracy of a given NAVTEQ street segment depends on the value of the Enhanced Geometry (ENH_GEOM) attribute. Links with Enhanced Geometry = Y conform to accuracy requirements of +/-5 metres for absolute position and +/- 1 metre for relative position. The minimum length of any street segment, independent of generalization, is 2 meters/7 feet.
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.
NAVTEQ's comprehensive data build process ensures the highest quality data available for routing and mapping applications. The process begins with establishing a field office in the new build area. Sources or Base Maps are acquired from a variety of sources including local governments, utility companies, other public agencies, and commercial mapping agencies. These maps are then carefully reviewed and digitized. All base map data is further enhanced with aerial photos and differential GPS to accurately position roads and represent lakes, rivers, railroads, etc., and proprietary software is then used to add navigable information, addresses, and points of interest. NAVTEQ additionally road tests the data to further add to the quality of the database. Field office staff drives the roads and streets to collect and verify new data. Photographs are also taken of overhead signage to ensure that the data accurately reflects the real world.
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.
Geometry development: NAVTEQ verifies (and if needed, corrects) the data by bringing together the source material, field data gathered through driving the road network, and additional digital imagery. Base map data is further enhanced with aerial photos and differential GPS to accurately position roads and represent lakes, rivers, railroads, etc.
Source normalization: Source maps are carefully reviewed and digitized. The data are normalized and entered into the NAVTEQ database.
Geocoding: The field and production teams code the one-ways, turn restrictions, postal codes, and other details to every location on the map.
Field data collection: Using proprietary tools and processes, NAVTEQ collects everything from road geometry to road attributes, 300 in all, on roads, streets, and highways throughout the world. Proprietary software is used to add navigable information, addresses, and points of interest. Photographs are also taken of overhead signage to ensure that the data accurately reflects the real world.
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.
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.
NAVTEQ digital map data is built on the roads of the world. Over seven hundred NAVTEQ field researchers from approximately 168 offices drive millions of kilometers of the road network each year. To provide uniformity and maximize precision each team works to a single global specification. And each team has state-of-the-art equipment, including our proprietary GPS-based collection technology and software.
NAVSTREETS is a NAVTEQ extraction format. The NAVTEQ data production environment, while not designed to be adopted directly by customers, is designed to insulate customers from data structure changes, additions, and deletions. NAVTEQ uses data extraction formats to "publish" NAVTEQ data externally to its customers, enabling them to process map data into their own production environment. These extraction formats generally have a design that is independent from the NAVTEQ internal production environment, and are not impacted when NAVTEQ modifies parts of the production environment. Extraction formats generally publish the same content, with differences only in the representation of the data.
0
Streets - Streets
The Streets layer contains all roads plus all Road Network attributes such as direction of travel, lanes, dividers, speed category, and access restrictions. This layer is suitable for routing applications, as it represents the complete navigable road network. For intersection-driven routing applications, the Z Levels layer can also be used to establish roadway connectivity. This layer contains address ranges for all addressable lines and polylines and is also used for geocoding. NAVSTREETS provides Addresses for each end of a line or polyline. "From" addresses correspond to the "Reference" end of the line or polyline, and "To" addresses correspond to the "Non-Reference" end of the line or polyline.
NAVTEQ
Feature Class
0
OBJECTID
OBJECTID
OID
4
0
0
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
SHAPE
Shape Points - Sets of binary spatial coordinate values representing ESRI geometry objects.
NAVTEQ
The set of all geometry object values.
Shape
Geometry
0
0
0
LINK_ID
LINK_ID
Double
8
0
0
ST_NAME
ST_NAME
String
240
0
0
FEAT_ID
FEAT_ID
Double
8
0
0
ST_LANGCD
ST_LANGCD
String
3
0
0
NUM_STNMES
NUM_STNMES
SmallInteger
2
0
0
ST_NM_PREF
ST_NM_PREF
String
6
0
0
ST_TYP_BEF
ST_TYP_BEF
String
90
0
0
ST_NM_BASE
ST_NM_BASE
String
105
0
0
ST_NM_SUFF
ST_NM_SUFF
String
6
0
0
ST_TYP_AFT
ST_TYP_AFT
String
90
0
0
ST_TYP_ATT
ST_TYP_ATT
String
1
0
0
ADDR_TYPE
ADDR_TYPE
String
1
0
0
L_REFADDR
L_REFADDR
String
10
0
0
L_NREFADDR
L_NREFADDR
String
10
0
0
L_ADDRSCH
L_ADDRSCH
String
1
0
0
L_ADDRFORM
L_ADDRFORM
String
2
0
0
R_REFADDR
R_REFADDR
String
10
0
0
R_NREFADDR
R_NREFADDR
String
10
0
0
R_ADDRSCH
R_ADDRSCH
String
1
0
0
R_ADDRFORM
R_ADDRFORM
String
2
0
0
REF_IN_ID
REF_IN_ID
Double
8
0
0
NREF_IN_ID
NREF_IN_ID
Double
8
0
0
N_SHAPEPNT
N_SHAPEPNT
Integer
4
0
0
FUNC_CLASS
FUNC_CLASS
String
1
0
0
SPEED_CAT
SPEED_CAT
String
1
0
0
FR_SPD_LIM
FR_SPD_LIM
Integer
4
0
0
TO_SPD_LIM
TO_SPD_LIM
Integer
4
0
0
TO_LANES
TO_LANES
SmallInteger
2
0
0
FROM_LANES
FROM_LANES
SmallInteger
2
0
0
ENH_GEOM
ENH_GEOM
String
1
0
0
LANE_CAT
LANE_CAT
String
1
0
0
DIVIDER
DIVIDER
String
1
0
0
DIR_TRAVEL
DIR_TRAVEL
String
1
0
0
L_AREA_ID
L_AREA_ID
Double
8
0
0
R_AREA_ID
R_AREA_ID
Double
8
0
0
L_POSTCODE
L_POSTCODE
String
11
0
0
R_POSTCODE
R_POSTCODE
String
11
0
0
L_NUMZONES
L_NUMZONES
SmallInteger
2
0
0
R_NUMZONES
R_NUMZONES
SmallInteger
2
0
0
NUM_AD_RNG
NUM_AD_RNG
SmallInteger
2
0
0
AR_AUTO
AR_AUTO
String
1
0
0
AR_BUS
AR_BUS
String
1
0
0
AR_TAXIS
AR_TAXIS
String
1
0
0
AR_CARPOOL
AR_CARPOOL
String
1
0
0
AR_PEDEST
AR_PEDEST
String
1
0
0
AR_TRUCKS
AR_TRUCKS
String
1
0
0
AR_TRAFF
AR_TRAFF
String
1
0
0
AR_DELIV
AR_DELIV
String
1
0
0
AR_EMERVEH
AR_EMERVEH
String
1
0
0
AR_MOTOR
AR_MOTOR
String
1
0
0
PAVED
PAVED
String
1
0
0
PRIVATE
PRIVATE
String
1
0
0
FRONTAGE
FRONTAGE
String
1
0
0
BRIDGE
BRIDGE
String
1
0
0
TUNNEL
TUNNEL
String
1
0
0
RAMP
RAMP
String
1
0
0
TOLLWAY
TOLLWAY
String
1
0
0
POIACCESS
POIACCESS
String
1
0
0
CONTRACC
CONTRACC
String
1
0
0
ROUNDABOUT
ROUNDABOUT
String
1
0
0
INTERINTER
INTERINTER
String
1
0
0
UNDEFTRAFF
UNDEFTRAFF
String
1
0
0
FERRY_TYPE
FERRY_TYPE
String
1
0
0
MULTIDIGIT
MULTIDIGIT
String
1
0
0
MAXATTR
MAXATTR
String
1
0
0
SPECTRFIG
SPECTRFIG
String
1
0
0
INDESCRIB
INDESCRIB
String
1
0
0
MANOEUVRE
MANOEUVRE
String
1
0
0
DIVIDERLEG
DIVIDERLEG
String
1
0
0
INPROCDATA
INPROCDATA
String
1
0
0
FULL_GEOM
FULL_GEOM
String
1
0
0
URBAN
URBAN
String
1
0
0
ROUTE_TYPE
ROUTE_TYPE
String
1
0
0
DIRONSIGN
DIRONSIGN
String
1
0
0
EXPLICATBL
EXPLICATBL
String
1
0
0
NAMEONRDSN
NAMEONRDSN
String
1
0
0
POSTALNAME
POSTALNAME
String
1
0
0
STALENAME
STALENAME
String
1
0
0
VANITYNAME
VANITYNAME
String
1
0
0
JUNCTIONNM
JUNCTIONNM
String
1
0
0
EXITNAME
EXITNAME
String
1
0
0
SCENIC_RT
SCENIC_RT
String
1
0
0
SCENIC_NM
SCENIC_NM
String
1
0
0
TO_X_LANES
TO_X_LANES
Double
8
0
0
FR_X_LANES
FR_X_LANES
Double
8
0
0
FOURWHLDR
FOURWHLDR
String
1
0
0
COVERIND
COVERIND
String
2
0
0
PLOT_ROAD
PLOT_ROAD
String
1
0
0
REVERSIBLE
REVERSIBLE
String
1
0
0
EXPR_LANE
EXPR_LANE
String
1
0
0
CARPOOLRD
CARPOOLRD
String
1
0
0
PHYS_LANES
PHYS_LANES
SmallInteger
2
0
0
VER_TRANS
VER_TRANS
String
1
0
0
PUB_ACCESS
PUB_ACCESS
String
1
0
0
LOW_MBLTY
LOW_MBLTY
String
1
0
0
PARK_AVAIL
PARK_AVAIL
SmallInteger
2
0
0
PRIORITYRD
PRIORITYRD
String
1
0
0
SPD_LM_SRC
SPD_LM_SRC
String
2
0
0
EXPAND_INC
EXPAND_INC
String
1
0
0
TRANS_AREA
TRANS_AREA
String
1
0
0
Shape_Length
Shape_Length
Double
8
0
0
Length of feature in internal units.
Esri
Positive real numbers that are automatically generated.
WA_Streets_WM
002
Projected
GCS_WGS_1984
Linear Unit: Meter (1.000000)
WGS_1984_Web_Mercator_Auxiliary_Sphere
<ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/2.7.0'><WKT>PROJCS["WGS_1984_Web_Mercator_Auxiliary_Sphere",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Mercator_Auxiliary_Sphere"],PARAMETER["False_Easting",0.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",0.0],PARAMETER["Standard_Parallel_1",0.0],PARAMETER["Auxiliary_Sphere_Type",0.0],UNIT["Meter",1.0],AUTHORITY["EPSG",3857]]</WKT><XOrigin>-20037700</XOrigin><YOrigin>-30241100</YOrigin><XYScale>10000</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.001</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>102100</WKID><LatestWKID>3857</LatestWKID></ProjectedCoordinateSystem>
20210317
09060100
20210317
09060100
20210317
06523900
1.0
FALSE
dataset
EPSG
6.18.3(9.3.1.2)
Simple
FALSE
0
TRUE
FALSE