Ingestion Screening Results

The checks a screening has finished so far, while the rest still run.

Use Cases

  • Show each location's results as each check lands, instead of waiting for the whole screening.

Behaviour

  • Read-only. The rows come straight from the validation service and are never stored. They are not the ingestion's results: those are written once validation completes.
  • Same shape as the stored rows. assessments is keyed by assessment type, with the fields the stored assessment rows carry. One item per uploaded feature, keyed by the feature's id.
  • Only finished types. An assessment type appears once every check it needs has finished; meta.complete_groups lists them. Values are never computed from half the checks.
  • Geometry is null unless include_geometry=true.
  • meta.state:
    • running: the items are the checks finished so far. completed_checks names them.
    • not_started: nothing to show yet. Poll again.
    • finishing: every check is done and the results are being saved. Poll again.
    • failed: the validation service's task failed. Stop polling and read the ingestion, which reports why.
    • finished: validation is over. Read links.final instead.
  • geometry_settled is false while a check that can move a point is still running, so a point read now may move.
  • Polling. Poll every 5 to 10 seconds. Repeat reads with no new check are served from a short cache.
  • Uploads over 2,000 features answer not_started.

Errors

  • 404 NOT_FOUND: unknown task id, or a task belonging to another organization.
  • 502 SCREENING_RESULTS_UNAVAILABLE: the validation service could not be reached.
  • 503 SCREENING_RESULTS_UNAVAILABLE: the validation service is busy. Retry after the Retry-After seconds.

Required scopes: ingestions:read, assessments:read