Kinds of problem and what you hand in
Nine ways a problem is answered, from one SQL query to a diagram you draw or a review you make, and which of them you can run.
Updated
The nine kinds
| Kind | What you hand in | Before you submit |
|---|---|---|
| SQL | One SELECT query on the PostGIS tables the brief lists, with spatial output named geom | Run shows the rows and the query plan |
| Python | A script that assigns its output to result | Run runs it in your browser |
| GeoJSON | The features you derived — pasted, or uploaded from GeoJSON, a zipped Shapefile, KML/KMZ, GPX or CSV | — |
| Values | Named answers in a form, worked out in any tool you like | — |
| Schema | PostgreSQL/PostGIS DDL | Run builds a temporary schema and shows what it holds |
| Design | One option for each decision, with a sentence on why — the choice is graded, the reasoning never is | — |
| Prepared dataset | A GeoPackage, zipped Shapefile, GeoJSON or CSV of up to 20 MB | Read shows what it was read as |
| Diagram | A system's components, an analysis workflow's steps, a deployment's machines or a geodatabase's classes, placed on a canvas and joined with arrows — see Draw a diagram | List shows the same diagram as lists you can edit by keyboard |
| Review | Every feature of a delivered dataset that breaks a rule of its specification, flagged with the rule it breaks — see Review a delivery | Your flags lists them rule by rule |
The CRS box
When a requirement checks the coordinate reference system, a Result CRS EPSG box appears beside the editor: say which system your answer is in.
Python's contract
Each dataset is at /data/<dataset id>.geojson, and what you assign to result is graded: a GeoDataFrame in any CRS (it is moved to WGS 84), a DataFrame, a dict of named values, or GeoJSON. Run executes in your browser; Submit runs the script again on the server and grades what result holds.
Related
Still stuck? Write to Support