Concept
Alternate Profiles
Different views and formats:
Alternate Profiles ?Profiles (alternative information views) encoded in various Media Types (HTML, text, RDF, JSON etc.) are available for this resource.
- Preferred Labelskos:prefLabel
None
- URI
- https://opengeospatial.github.io/ogc.geo.common.data_types.bounding_box ↗Go to the persistent identifier link
- Within Vocab
- Building Blocks - OGC Main
| Definitionskos:definition | None | ||||
|---|---|---|---|---|---|
| Object Typetype | Dataset | ||||
| https://www.opengis.net/def/bblocks/Schema | |||||
| http://purl.org/dc/terms/createdcreated | 2022-05-24T13:51:38+00:00 | ||||
| Date Modifiedmodified | 2023-03-09 | ||||
| http://purl.org/dc/terms/hasVersionhasVersion | 1.0.1 | ||||
| Descriptiondescription |
b0
|
||||
b1
|
|||||
b2
|
|||||
| Sourcesource | OGC API - Features, Part 1, 7.13.2: Feature Collections Response | ||||
| Abstractabstract | The bounding box JSON object describes a simple spatial extent of a resource. For OGC API’s this could be a feature, a feature collection or a dataset, but it can be used in any JSON resource that wants to communicate its rough location. The extent is simple in that the bounding box does not describe the precise location and shape of the resource, but provides an axis-aligned approximation of the spatial extent that can be used as an initial test whether two resources are potentially intersecting each other. | ||||
| https://www.opengis.net/def/bblocks/hasSchemahasSchema | https://opengeospatial.github.io/bblocks/annotated-schemas/geo/common/data_types/bounding_box/schema.json | ||||
| https://opengeospatial.github.io/bblocks/annotated-schemas/geo/common/data_types/bounding_box/schema.yaml | |||||
| https://www.opengis.net/def/bblocks/scopescope | http://www.opengis.net/def/bblocks/scope/geo | ||||
| https://www.opengis.net/def/bblocks/statusstatus | stable |