crs-l1-london-laea-areas
Analyst notes
Description
Tests whether the agent recognizes that computing area on WGS84 (degree) geometries is meaningless, and reprojects to an equal-area CRS before measuring. The prompt deliberately omits any CRS hint, so the agent has to spot the problem from the input metadata.
Approach
- Read `london_admin.geojson` and inspect its CRS metadata.
- Recognize the geometries are in WGS84, so area measured directly would come out in degrees² and be meaningless.
- Pick an equal-area projection appropriate for Europe. LAEA Europe (EPSG:3035) is the canonical choice.
- Reproject the polygons and compute their area in square metres.
- Convert to square kilometres and write a CSV with columns id, name, area_km2.
Pitfalls
- Calling `.area` directly on WGS84 geometries gives a result in degrees², not metres².
- Picking a single-zone projection (like a UTM zone) for a region that spans several zones throws the totals off.
- Forgetting the m² → km² conversion leaves the numbers off by a factor of a million.
- Filtering to just the 33 borough-level `county` features and dropping the `locality` rows cuts the output to 33 of 232 rows, which a real run did before the prompt spelled out both subtypes.
- Dropping or renaming the id and name columns breaks the join back to the original admin units.
Recent runs task v5
| adapter | started | score | steps | duration | cost | status |
|---|---|---|---|---|---|---|
| openrouter-gemma4-26b-basic | 2026-06-18T07:32:32Z | 1.00 | 4 | 1:07 | 0.14¢ | done |
| openrouter-deepseek-v4-flash-basic | 2026-06-18T03:08:04Z | ERR | 1 | 2:42 | 0.01¢ | failed |
| openrouter-deepseek-v4-flash-detailed | 2026-06-17T22:01:33Z | 0.00 | 5 | 1:52 | 5.76¢ | done |
| openrouter-gemma4-26b-detailed | 2026-06-17T19:47:47Z | 1.00 | 9 | 0:55 | 0.19¢ | done |
| openrouter-deepseek-v4-flash-basic | 2026-06-16T21:43:55Z | 1.00 | 5 | 0:39 | 0.58¢ | done |