Automation index
How much of a Cartographer’s job can AI already do?
OSM and a generalisation come earlier. A map that reads, and does not lie, do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Cartographer
31%
AI can already do 31% of this job.
#31 / 763
View rankingCartographer
Where the time goes
Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.
The time saving for each task is estimated separately.
| Task | Share | AI | Points |
|---|---|---|---|
Sources, OSM, satellite and generalisation.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Symbology, type and visual hierarchy.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 48% | +7.7 |
Projections, scales and getting the heights right.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Review with the client, the field and the lie in the data.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Print maps, web maps and updates.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Credit, metadata and owning the map.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 31% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- make maps
- generalise cartography
- symbology
- choose projection
- visual hierarchy
- update OSM
- web maps
- maps that do not lie
Sources for this job· O*NET 17-1021.00· ESCO/ISCO 2165
IS WORK OVER?
Backend developer
27%
#151 / 763
View rankingBackend developer
Where the time goes
Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.
The time saving for each task is estimated separately.
| Task | Share | AI | Points |
|---|---|---|---|
Endpoint, the contract and the test.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Spike, the queue and the one that drops.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Key, the secret and not leaving it in the repo.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Migration, the rollback and not improvising in prod.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the deadline and not cutting the one that matters.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it takes the spike, and not leaving the key.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 27% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- endpoints
- API contracts
- queues
- secrets
- migrations
- rollback
- backend tests
- write server code
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2512