Feature Collections - Schema
specdraftimplcandidatePublish a logical schema of the feature properties, described in JSON Schema.
Scope
The schema is automatically derived from the type definitions in the feature provider. Currently, schemas are created according to JSON Schema 2020-12.
Conformance Classes
Feature Collections - Schema is based on the OGC API - Features - Part 5: Schemas.
Operations
| Resource | Path | Methods | Media Types | Description |
|---|---|---|---|---|
Feature Schema | collections/{collectionId}/schema | GET | JSON Schema of the features of the collection collectionId. |
Path Parameters
| Name | Resources | Description |
|---|---|---|
collectionId | Feature Schema | The identifier of the feature collection. |
Query Parameters
| Name | Resources | Description |
|---|---|---|
f | Feature Schema | Select the output format of the response. If no value is provided, the standard HTTP rules apply, i.e., the "Accept" header will be used to determine the format. |
Configuration
Options
| Name | Default | Description | Type | Since |
|---|---|---|---|---|
buildingBlock | Always SCHEMA. | string | v3.1 | |
enabled | false | Enable the building block? | boolean | v3.1 |
caching | {} | Sets fixed values for HTTP Caching Headers for the resources. | object | v3.1 |
defaultProfiles | {"codelist": "codelists-ref"} | Change the default value of the profile parameter for schema resources. The value is an object where the key is the id of a profile set, such as codelist, and the value is the default profile for the profile set, e.g., codelists-inline. In addition, format-specific default profiles can be specified in the building block of each schema format. Those defaults have a higher priority. | object | v4.5 |
Examples
- buildingBlock: SCHEMA
enabled: true