dd-l1-vienna-gpkg-manifest

Analyst notes

Description

Tests whether the agent treats a GeoPackage as a multi-layer container rather than a single-layer file. The prompt deliberately does not say how many layers are in there, so an agent that opens the default first layer (or hand-rolls a manifest from the persona's hints) produces a partial answer. The other hidden gotcha is the bbox: it must be reported in each layer's own CRS, not reprojected to WGS84 for friendliness.

Approach

  1. Open the GPKG with a tool that exposes its schema (pyogrio, fiona, ogrinfo, or DuckDB-spatial) and list every layer it declares.
  2. For each layer, read the declared CRS as an EPSG string, the declared geometry type, the feature count, and the native bounding box. Do not reproject.
  3. Assemble one JSON object per layer with the five required keys in the exact names and types the prompt asks for.
  4. Write the result as a top-level JSON list to manifest.json.

Pitfalls

Inputs

nameformatcrsgeometryfeatures
vienna_planning gpkg EPSG:31287 Polygon 22

Expected outputs

nameformatcrsgeometryfeatures
manifest.json json EPSG:31287 mixed

Map

Recent runs task v1

adapterstartedscorestepsdurationcoststatus
openrouter-gemma4-26b-basic 2026-06-18T07:32:32Z pending pending
openrouter-deepseek-v4-flash-basic 2026-06-18T03:08:04Z 1.00 6 0:26 0.17¢ done
openrouter-deepseek-v4-flash-detailed 2026-06-17T22:01:33Z 1.00 5 0:42 0.13¢ done
openrouter-gemma4-26b-detailed 2026-06-17T19:47:47Z 1.00 7 2:20 0.26¢ done
openrouter-deepseek-v4-flash-basic 2026-06-16T21:43:55Z 1.00 4 0:40 0.08¢ done