Web Mercator projection
Web Mercator, Google Web Mercator, Spherical Mercator, WGS 84 Web Mercator or WGS 84/Pseudo-Mercator is a variant of the Mercator projection and is the de facto standard for Web mapping applications. It rose to prominence when Google Maps adopted it in 2005. It is used by virtually all major online map providers, including Google Maps, Mapbox, Bing Maps, OpenStreetMap, Mapquest, Esri, and many others. Its official EPSG identifier is EPSG:3857, although others have been used historically.
Web Mercator is a slight variant of the Mercator projection, one used primarily in Web-based mapping programs. It uses the same formulas as the standard Mercator as used for small-scale maps. However, the Web Mercator uses the spherical formulas at all scales whereas large-scale Mercator maps normally use the ellipsoidal form of the projection. The discrepancy is imperceptible at the global scale but causes maps of local areas to deviate slightly from true ellipsoidal Mercator maps at the same scale. This deviation becomes more pronounced further from the equator, and can reach as much as 40 km on the ground.
While the Web Mercator's formulas are for the spherical form of the Mercator, geographical coordinates are required to be in the WGS 84 ellipsoidal datum. This discrepancy causes the projection to be slightly non-conformal. General lack of understanding that the Web Mercator differs from standard Mercator usage has caused considerable confusion and misuse.:87 For all these reasons, the United States Department of Defense through the National Geospatial-Intelligence Agency has declared this map projection to be unacceptable for any official use.
Formulas for the Web Mercator are fundamentally the same as for the standard spherical Mercator, but before applying zoom, the "world coordinates" are adjusted such that the upper left corner is (0, 0) and the lower right corner is (256, 256):
Because the Mercator projects the poles at infinity, a map using the Web Mercator projection cannot show the poles. Services such as Google Maps cut off coverage at 85.051129° north and south. This is not a limitation for street maps, which is the primary purpose for such services. The value 85.051129° is the latitude at which the full projected map becomes a square, and is computed as φ given y = 0:
Spherical and ellipsoidal mix
The projection is neither strictly ellipsoidal nor strictly spherical. EPSG's definition says the projection "uses spherical development of ellipsoidal coordinates". The underlying geographic coordinates are defined using the WGS84 ellipsoidal model of the Earth's surface, but are projected as if defined on a sphere. This practice is uncontroversial for small-scale maps (such as of the entire world), but has little precedent in large-scale maps (such as of a city or province).
Advantages and disadvantages
Web Mercator is a spherical Mercator projection, and so it has the same properties as a spherical Mercator: north is up everywhere, meridians are equally spaced vertical lines, angles are locally correct (assuming spherical coordinates), and areas inflate with distance from the equator such that the polar regions are grossly exaggerated. The ellipsoidal Mercator has these same properties, but models the earth as an ellipsoid.
Unlike the ellipsoidal Mercator, however, the Web Mercator is not quite conformal. This means that angles between lines on the surface will not be drawn to the same angles in the map, although they will not deviate enough to be noticeable by eye. Lines deviate because Web Mercator specifies that coordinates be given as surveyed on the WGS 84 ellipsoidal model. By projecting coordinates surveyed against the ellipsoid as if they were surveyed on a sphere, angular relationships change slightly. This is standard practice on the standard spherical Mercator projection, but unlike Web Mercator, the spherical Mercator is not normally used for maps of local areas, such as street maps, and so the accuracy of positions needed for plotting is typically less than the angular deviation caused by using spherical formulas. The benefit the Web Mercator gains is that the spherical form is much simpler to calculate than the ellipsoidal form, and so requires only a fraction of the computing resources.
The projected coordinate reference system originally lacked an official spatial reference identifier (SRID), and the Geodesy subcommittee of the OGP's Geomatics committee (also known as EPSG) refused to provide it with one, declaring "We have reviewed the coordinate reference system used by Microsoft, Google, etc. and believe that it is technically flawed. We will not devalue the EPSG dataset by including such inappropriate geodesy and cartography." The unofficial code "EPSG:900913" (GOOGLE transliterated to numbers) came to be used. It was originally defined by Christopher Schmidt in his Technical Ramblings blog and became codified in OpenLayers 2, which, technically, would make OpenLayers the SRID authority.
In 2008, EPSG provided the official identifier EPSG:3785 with the official name "Popular Visualisation CRS / Mercator", but noted "It is not an official geodetic system". This definition used a spherical (rather than ellipsoidal) model of the Earth.
Later that year, EPSG provided an updated identifier, EPSG:3857 with the official name "WGS 84 / Pseudo-Mercator". The definition switched to using the WGS84 ellipsoid (EPSG:4326), rather than the sphere.
Although the projection is closely associated with Google, Microsoft is listed as the "information source" in EPSG's standards.
ESRI:102113 corresponds to EPSG:3785 while ESRI:102100 corresponds to EPSG:3857.
The projection covers the Earth from −180° to 180° longitude, and 85.05° north and south. Using well-known text representation of coordinate reference systems (WKT), EPSG:3857 is defined as follows:
PROJCS["WGS 84 / Pseudo-Mercator", GEOGCS["WGS 84", DATUM["WGS_1984", SPHEROID["WGS 84",6378137,298.257223563, AUTHORITY["EPSG","7030"]], AUTHORITY["EPSG","6326"]], PRIMEM["Greenwich",0, AUTHORITY["EPSG","8901"]], UNIT["degree",0.0174532925199433, AUTHORITY["EPSG","9122"]], AUTHORITY["EPSG","4326"]], PROJECTION["Mercator_1SP"], PARAMETER["central_meridian",0], PARAMETER["scale_factor",1], PARAMETER["false_easting",0], PARAMETER["false_northing",0], UNIT["metre",1, AUTHORITY["EPSG","9001"]], AXIS["X",EAST], AXIS["Y",NORTH], EXTENSION["PROJ4","+proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0 +x_0=0.0 +y_0=0 +k=1.0 +units=m +nadgrids=@null +wktext +no_defs"], AUTHORITY["EPSG","3857"]]
- "WGS 84 and the Web Mercator Projection NGA Office of Geomatics" (PDF). National Geospatial Intelligence Agency. 2014-05-16. Retrieved 2014-08-06.
- "Google Maps & Earth Help Forum". Retrieved 29 August 2017.
- "Our Map Data". MapBox. Retrieved June 20, 2018.
Mapbox supports the popular Web Mercator projection, and currently does not support any other projections for display.
- Battersby, Sarah E.; Finn, Michael P.; Usery, E. Lynn; Yamamoto, Kristina H. (2014). "Implications of Web Mercator and Its Use in Online Mapping" (PDF). Cartographica. 49 (2): 92. doi:10.3138/carto.49.2.2313.
- "NGA: (U) NGA Advisory Notice on "Web Mercator" (UNCLASSIFIED)". earth-info.nga.mil. Retrieved 2018-06-07.
- "The Google Maps / Bing Maps Spherical Mercator Projection". Alastair Aitchison. Retrieved 4 October 2014.
- "NGA: (U) NGA Advisory Notice on "Web Mercator" (UNCLASSIFIED)". Retrieved 4 October 2014.
- "OpenStreetMap Slippy map tilenames". openstreetmap.org. Retrieved 2018-11-14.
- Strebe, Daniel "daan" (2019). "A bevy of area-preserving transforms for map projection designers". Cartography and Geographic Information Science. 46 (3). doi:10.1080/15230406.2018.1452632.
- "The Earth is Not Round! Utah, NAD83 and WebMercator Projections". Utah GIS Portal. Retrieved 2020-06-20.
- "dotMorten | Spherical/Web Mercator: EPSG code 3785". www.sharpgis.net.
- "Google Projection: 900913". August 7, 2007.
- "Spherical Mercator — OpenLayers". docs.openlayers.org.
- GmbH (https://www.klokantech.com/), Klokan Technologies. "WGS 84 / Pseudo-Mercator - Spherical Mercator, Google Maps, OpenStreetMap, Bing, ArcGIS, ESRI - EPSG:3857". epsg.io.
- "102100 vs. 102113 is mixed up?". GeoNet, The Esri Community. October 3, 2012.