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
Use Cases and Applications of the OGC Moving Features Standard: The Requirements for a Moving Feature API
- URI
- http://www.opengis.net/def/docs/15-096 ↗Go to the persistent identifier link
- Within Vocab
- OGC Documents
Definitionskos:definition | This OGC Discussion Paper provides examples of some actual and potential geospatial applications using the OGC Moving Features encoding. These applications can be used to define the next steps in the development of the OGC Moving Features Standard: The definition of a “Moving Features API”. As a conclusion, the Moving Features SWG recommends that a new Moving Features API standard should target the following three kinds of operations: retrieval of feature information, operations between a trajectory and a geometric object, and operations between two trajectories. Additionally, the Moving Features SWG recommends establishing an abstract specification for these three kinds of operations because only a part of operations for trajectories is defined by ISO 19141:2008 - Schema for moving features. |
---|---|
Broaderbroader | Discussion Paper |
http://purl.org/dc/terms/createdcreated | 2016-01-18 |
Creatorcreator | Akinori Asahara, Hideki Hayashi, Carl Reed |
hasProfilehasProfile | http://www.opengis.net/def/docs/15-096?_profile=conceptscheme |
seeAlsoseeAlso | http://www.opengis.net/def/docs/15-096?_profile=alt |
https://portal.ogc.org/files/?artifact_id=64623 | |
Status of item in register or collectionstatus | valid |
Notationnotation | 15-096 |
Alternative LabelaltLabel | Use Cases and Applications of the OGC Moving Features Standard: The Requirements for a Moving Feature API |
15-096 | |
OGC document typedoctype | Discussion Paper |