A contractor delivered the five-minute-walk coverage map for the cycle-hire scheme. It was built in a web-mapping tool, entirely in Web Mercator, and its coverage figure for Inner London is about a fifth lower than the one produced in British National Grid. Both teams insist they buffered by 400 metres. You have to explain, with numbers, why they are both telling the truth and only one of them is right.
Web Mercator (EPSG:3857) is conformal: shapes are right locally, but its metre is not a ground metre. At latitude φ the map is stretched by a scale factor
k = 1 / cos(φ)so a distance of 400 "metres" in EPSG:3857 is only 400 / k metres on the ground.
Compute and report, using the docking-station snapshot:
scale_factor — k at the mean latitude of the stations, to 4 decimalsground_radius_m — the ground distance a 400 m EPSG:3857 buffer really has at that latitude, to the nearest metrecovered_km2_mercator — the Inner London coverage you get if you buffer every station by ground_radius_m (dissolved, clipped to the 13 Inner London boroughs), km²lost_pct — how much smaller that is than the correct 400 m coverage, as a percentage of the correct figureThe correct coverage is the same computation with a true 400 m buffer in EPSG:27700 (or a geodesic buffer); do both and compare.
These are where the teaching is. Read them twice.
Buffers and distances computed in EPSG:3857 are the single most common silent error in web-built spatial analysis, and the size of the error grows with latitude.
Work the problem in whatever tool you like, then enter the answers here.
scale_factorground_radius_mcovered_km2_mercatorlost_pct4 scored, 0 informational
Web Mercator scale factor at the stations' mean latitude
20%Ground radius of a 400 m Mercator buffer
20%Inner London coverage with the shrunken buffer
30%Share of the true coverage lost
30%