BRENNEN

Industries / Technology

Mapping and geospatial

The mapping and geospatial industry measures the Earth's surface from satellites, aircraft, drones and the ground, turns the measurements into maps and location data, and builds the software (GIS, geographic information systems) that stores, analyzes and shows them.

1962

Roger Tomlinson of Spartan Air Services, an aerial survey firm in Ottawa, presented a paper in November 1962 proposing that computers store, overlay and measure the maps of the new Canada Land Inventory; the work became the Canada Geographic Information System, which an IEEE Milestone dedicated in 2023 names the first geographic information system, developed from 1962 to 1968.,_1962-1968).

esri.comethw.org

41

Milestones achieved across 6 domains.

7

To watch for: announced, not yet confirmed outside.

12

Open deliverables. Nobody has shipped them.

In one minute

Where it started

People have drawn maps for thousands of years, and in 1569 Gerardus Mercator published the projection that web maps still use in a simplified form. The industry in its present form began in 1962, when Roger Tomlinson proposed that computers store and overlay the maps of the Canada Land Inventory, work that became the Canada Geographic Information System. Pictures from orbit (Landsat from 1972, SPOT from 1986), the US Census Bureau's TIGER road database of 1990 and Esri's ARC/INFO, sold from 1981, turned maps into data that could be bought, measured and combined.

Where it stands

Much of the raw material is now free: Landsat and Sentinel-2 pictures, the Copernicus DEM elevation model, England's lidar, and OpenStreetMap, a world map drawn by volunteers that counted 10 million registered users in January 2023. Free software such as QGIS, GDAL and MapLibre reads it, and newer file formats let a program fetch only the part of a file it needs. Companies sell satellite pictures with pixels of about 30 cm and keep the road maps that cars navigate by, and AI already traces roads, reads house numbers and strips trees from elevation models.

What is open

Many of the numbers the industry relies on come only from the people who make the data: how accurate a navigation map's speed limits are, how fast new roads appear in it, how tall the world's buildings are, and how well global elevation models do under tropical forest. Most open deliverables here are outside tests with public answer keys, for maps, elevation models and coordinate software. Two are archives left half done: the spy-satellite photographs of the 1960s and Landsat's first twenty years of pictures, neither yet corrected into map-ready form at scale.

Domains

AchievedWatch forOpen

Advances to build with

1 research note

Open in mapping and geospatial

3 of 12 open deliverables

Open · Satellite imagery

A 1960s base map

An open mosaic of 1960s CORONA KH-4B photographs for one large region outside the Middle East, orthorectified (corrected for camera angle and terrain so that each pixel sits where it belongs on a map), with every frame's position error measured at checkpoints against today's Sentinel-2 pictures, and the processing scripts published so the next region costs less.

Built with what exists

KH-4B scans from USGS EarthExplorer; the Ames Stereo Pipeline's optical bar (panoramic) camera model; LightGlue, an open learned feature matcher from ETH Zurich (2023), to find the same points in an old photo and a Sentinel-2 picture; the Copernicus DEM for terrain; GDAL, the standard open library for raster maps.

Credit · unclaimed

Open · Aerial photos and elevation

Terrain maps tested in tropics

A DEMIX-style ranking of the global terrain models (Copernicus DEM, FABDEM, FathomDEM, GEDTM30, AW3D30) in tropical forest, scored against ground models from open airborne lidar, with the reference grids and code published.

Built with what exists

NASA's archive of airborne lidar surveys over forest sites in Brazil, 2008 to 2018, 3,154 files with terrain models, shared without restriction; ICESat-2 ground heights as spot checks; the global models above; GDAL and Python.

Credit · unclaimed

Open · Street maps

Speed limits against the signs

A public, repeatable test of the speed limits that map providers give for roads, checked against the limits posted on the signs. For a random sample of road segments in several cities, the posted limit is read from a dated photo of the sign and compared with the limit in each map.

Built with what exists

Mapillary street-level photos, which are open under the CC-BY-SA licence, and Panoramax, an open French alternative, both of which record when each photo was taken; the tester's own photos of signs, taken from the pavement and framed on the sign, not on passers-by; speed limits from TomTom's Snap to Roads API, the Mapbox Directions API's maxspeed annotation (in beta), OpenStreetMap's maxspeed tags and Overture's transportation data; QGIS and Python. Google's speed-limit service is open only to holders of its Asset Tracking licence. Read each provider's terms on publishing comparisons before starting.

Credit · unclaimed