Evaluate a ruleset against a geometry
Runs every check in the ruleset against the submitted geometry and returns a verdict with per-check evidence plus reproducibility metadata. Pass either ruleset_id (catalog reference) or ruleset (inline body).
Response content is negotiated via the Accept header:
application/json(default) —StandardResponse[VerdictResponse].application/geo+json— a GeoJSONFeatureCollectionwith one feature per evidence hit; each feature’spropertiescarry the check metadata (check_id,severity,triggered,color) and evidence metrics (overlap_area_m2,distance_m, etc.).
Pass ?explain=true to return cardinality estimates per set without evaluating user terminals.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Query Parameters
When true, returns cardinality estimates per set without evaluating user terminals.
When true, includes ruleset-linter findings in meta.lint alongside the verdict.
Body
- EvaluateRequest
- EvaluateRequest
User-supplied data for the request — geometry, identifier bag, and an optional source CRS. At least one of input.geometry or input.subjects MUST be present (enforced inside the input model).
Catalog ruleset reference. Accepts name@version for a pinned version or just name for the latest. Mutually exclusive with ruleset.
256Inline ruleset document (same shape as the DSL). Mutually exclusive with ruleset_id.
Point-in-time read for the ruleset. Only takes effect when ruleset_id is passed without @version — resolves to the highest version whose created_at <= ruleset_as_of. Ignored when ruleset_id pins a version explicitly or when ruleset (inline) is used.
Response
Evaluation result.
The response is of type FeatureCollection · object.