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
OGC GeoPose 1.0 Data Exchange Draft Standard
- URI
- http://www.opengis.net/def/docs/21-056r10 ↗Go to the persistent identifier link
- Within Vocab
- OGC Documents
| Definitionskos:definition | GeoPose 1.0 is an OGC Implementation Standard for exchanging the location and orientation of real or virtual geometric objects (“Poses”) within reference frames anchored to the earth’s surface (“Geo”) or within other astronomical coordinate systems. The standard specifies two Basic forms with no configuration options for common use cases, an Advanced form with more flexibility for more complex applications, and five composite GeoPose structures that support time series plus chain and graph structures. These eight Standardization Targets are independent. There are no dependencies between Targets and each may be implemented as needed to support a specific use case. The Standardization Targets share an implementation-neutral Logical Model which establishes the structure and relationships between GeoPose components and also between GeoPose data objects themselves in composite structures. Not all of the classes and properties of the Logical Model are expressed in individual Standardization Targets nor in the specific concrete data objects defined by this standard. Those elements that are expressed are denoted as implementation-neutral Structural Data Units (SDUs). SDUs are aliases for elements of the Logical Model, isolated to facilitate specification of their use in encoded GeoPose data objects for a specific Standardization Target. For each Standardization Target, each implementation technology and corresponding encoding format defines the encoding or serialization specified in a manner appropriate to that technology. GeoPose 1.0 specifies a single encoding in JSON format (IETF RFC 8259). Each Standardization Target has a JSON Schema (Internet-Draft draft-handrews-json-schema-02) encoding specification. The key standardization requirements specify that concrete JSON-encoded GeoPose data objects must conform to the corresponding JSON Schema definition. The individual elements identified in the encoding specification are composed of SDUs, tying the specifications back to the Logical Model. The GeoPose 1.0 Standard makes no assumptions about the interpretation of external specifications, for example, of reference frames. Nor does it assume or constrain services or interfaces providing conversion between GeoPoses of difference types or relying on different external reference frame definitions. |
|---|---|
| Broaderbroader | Implementation Standard - Draft |
| http://purl.org/dc/terms/createdcreated | 2022-11-28 |
| Creatorcreator | Carl Stephen Smyth |
| seeAlsoseeAlso | https://docs.ogc.org/dis/21-056r10/21-056r10.html |
| Status of item in register or collectionstatus | valid |
| Notationnotation | 21-056r10 |
| Alternative LabelaltLabel | 21-056r10 |
| OGC GeoPose 1.0 Data Exchange Draft Standard | |
| OGC document typedoctype | Implementation Standard - Draft |