OGC and STAC test evidence
Conformance report
FailedOGC protocol suites
| Protocol / profile | Evidence | Status | Passed | Failed | Skipped | Duration |
|---|---|---|---|---|---|---|
| OGC API · Features 1.0core | Stock official | Passed | 1745 | 0 | 0 | 23s |
| OGC API · Tiles 1.0core | Stock official | Passed | 16 | 0 | 0 | 7s |
| WCS 2.0core | Stock official | Passed | 53 | 0 | 0 | 31s |
| WCS 2.0crs | Stock official | Passed | 21 | 0 | 0 | 17s |
| WCS 2.0post | Stock official | Passed | 6 | 0 | 0 | 15s |
| WCS 2.0range-subsetting | Stock official | Passed | 5 | 0 | 0 | 15s |
| WCS 2.0scaling | Stock official | Passed | 11 | 0 | 0 | 15s |
| WFS 2.0core | Stock official | Failed | 958 | 1 | 22 | 2m42s |
| WMS 1.3core | Stock official | Passed | 187 | 0 | 0 | 13s |
| WMTS 1.0core | Stock official | Passed | 51 | 0 | 0 | 31s |
| WCS 2.0interpolation | Official-derived | Passed | 10 | 0 | 0 | 26s |
| WFS 2.0core202 | Official-derived | Passed with skips | 960 | 0 | 21 | 4m18s |
Counts describe leaf assertion executions within each profile. Infrastructure outcomes, upstream totals, and skip reasons are available in the details.
STAC validation
STAC API and document validation use community tools. PySTAC checks demonstrate client interoperability. The stock OGC Features suite checks requirements inherited by STAC. These results do not constitute OGC STAC certification.
| Protocol / profile | Evidence | Status | Passed | Failed | Skipped | Duration |
|---|---|---|---|---|---|---|
| STAC API 1.0stac-api-validator | Community validatorv0.6.8 | Passed with warnings2 advisory warning occurrences | — | — | — | 9s |
| STAC 1.1 documentsstac-validator | Community validatorv4.1.2 | Passed | — | — | — | 9s |
| PySTAC client interoperabilitypystac-client | Client interoperabilityv0.9.0 | Passed | — | — | — | 9s |
| Inherited OGC Features requirementsstac | Stock official | Passed with skipsSkips reviewed by coverage policy | 82 | 0 | 43 | 2s |
Validator exit codes and advisory warnings are recorded separately from ETS assertion counts. Warnings can describe recommended metadata or a limitation in test coverage. Duplicate warning occurrences are retained. Validator durations cover the shared validation batch.