Community validator
STAC API 1.0stac-api-validator
Passed with warningsCore, Collections, Features and Item Search, including pagination, against the workspace STAC fixture.
Download STAC validation evidence (.zip)
Recorded outcome
Advisory warnings 2 occurrences
These are upstream warnings, separate from validation errors and ETS skips. Repeated messages remain separate. Coverage limitations identify checks the validator could not complete.
Metadata recommendation
Recommended descriptive metadata, such as collection summaries and link titles. Band summaries apply when band metadata exists. These recommendations are not schema validation errors.
[Collections] : GET http://server:9000/workspaces/demo/stac/collections/conformance-scenes has these stac-check recommendations: A STAC collection should contain a summaries field,It is recommended to store information like eo:bands in summaries,,Links in catalogs and collections should always have a 'title' field,
Metadata recommendation
Recommended descriptive metadata, such as collection summaries and link titles. Band summaries apply when band metadata exists. These recommendations are not schema validation errors.
[Collections] : GET http://server:9000/workspaces/demo/stac/collections/conformance-scenes has these stac-check recommendations: A STAC collection should contain a summaries field,It is recommended to store information like eo:bands in summaries,,Links in catalogs and collections should always have a 'title' field,
Build provenance and invocation
"stac-api-validator" "--root-url" "http://server:9000/workspaces/demo/stac/" "--collection" "conformance-scenes" "--geometry" "{\"type\": \"Polygon\", \"coordinates\": [[[-10, -10], [10, -10], [10, 10], [-10, 10], [-10, -10]]]}" "--validate-pagination" "--conformance" "core" "--conformance" "collections" "--conformance" "features" "--conformance" "item-search" Original tool output
stac-api-validator.log
INFO:stac_api_validator.validations:Validating STAC API - Core conformance class. INFO:stac_api_validator.validations:Validating STAC API - Collections conformance class. INFO:stac_validator.utilities:Fetching schema: https://schemas.stacspec.org/v1.1.0/collection-spec/json-schema/collection.json INFO:stac_validator.utilities:✓ Cached schema: https://schemas.stacspec.org/v1.1.0/collection-spec/json-schema/collection.json INFO:stac_validator.utilities:Fetching schema: https://schemas.stacspec.org/v1.1.0/item-spec/json-schema/item.json INFO:stac_validator.utilities:✓ Cached schema: https://schemas.stacspec.org/v1.1.0/item-spec/json-schema/item.json INFO:stac_validator.utilities:Fetching schema: https://schemas.stacspec.org/v1.1.0/item-spec/json-schema/common.json INFO:stac_validator.utilities:✓ Cached schema: https://schemas.stacspec.org/v1.1.0/item-spec/json-schema/common.json INFO:stac_validator.utilities:Fetching schema: https://schemas.stacspec.org/v1.1.0/item-spec/json-schema/basics.json INFO:stac_validator.utilities:✓ Cached schema: https://schemas.stacspec.org/v1.1.0/item-spec/json-schema/basics.json INFO:stac_validator.utilities:Fetching schema: https://schemas.stacspec.org/v1.1.0/item-spec/json-schema/bands.json INFO:stac_validator.utilities:✓ Cached schema: https://schemas.stacspec.org/v1.1.0/item-spec/json-schema/bands.json INFO:stac_validator.utilities:Fetching schema: https://schemas.stacspec.org/v1.1.0/item-spec/json-schema/datetime.json INFO:stac_validator.utilities:✓ Cached schema: https://schemas.stacspec.org/v1.1.0/item-spec/json-schema/datetime.json INFO:stac_validator.utilities:Fetching schema: https://schemas.stacspec.org/v1.1.0/item-spec/json-schema/data-values.json INFO:stac_validator.utilities:✓ Cached schema: https://schemas.stacspec.org/v1.1.0/item-spec/json-schema/data-values.json INFO:stac_validator.utilities:Fetching schema: https://schemas.stacspec.org/v1.1.0/item-spec/json-schema/instrument.json INFO:stac_validator.utilities:✓ Cached schema: https://schemas.stacspec.org/v1.1.0/item-spec/json-schema/instrument.json INFO:stac_validator.utilities:Fetching schema: https://schemas.stacspec.org/v1.1.0/item-spec/json-schema/licensing.json INFO:stac_validator.utilities:✓ Cached schema: https://schemas.stacspec.org/v1.1.0/item-spec/json-schema/licensing.json INFO:stac_validator.utilities:Fetching schema: https://schemas.stacspec.org/v1.1.0/item-spec/json-schema/provider.json INFO:stac_validator.utilities:✓ Cached schema: https://schemas.stacspec.org/v1.1.0/item-spec/json-schema/provider.json INFO:stac_api_validator.validations:Validating STAC API - Features conformance class. INFO:stac_validator.utilities:Fetching schema: https://geojson.org/schema/Feature.json INFO:stac_validator.utilities:✓ Cached schema: https://geojson.org/schema/Feature.json INFO:stac_validator.utilities:Fetching schema: https://geojson.org/schema/Geometry.json INFO:stac_validator.utilities:✓ Cached schema: https://geojson.org/schema/Geometry.json INFO:stac_api_validator.validations:Validating STAC API - Item Search conformance class. Warnings: - [Collections] : GET http://server:9000/workspaces/demo/stac/collections/conformance-scenes has these stac-check recommendations: A STAC collection should contain a summaries field,It is recommended to store information like eo:bands in summaries,,Links in catalogs and collections should always have a 'title' field, - [Collections] : GET http://server:9000/workspaces/demo/stac/collections/conformance-scenes has these stac-check recommendations: A STAC collection should contain a summaries field,It is recommended to store information like eo:bands in summaries,,Links in catalogs and collections should always have a 'title' field, Errors: none