7.3.2.1.  Retrieve

The retrieve operation is defined in the Collections requirements class of OGC API — Common. No modifications are needed to support MovingFeature resources.

Support for the HTTP GET method on the {root}/collections path is specified as a requirement in OGC API — Common.

7.3.2.2.  Create

The create operation is defined in the CREATE section of the “Create/Replace/Delete” requirements class of OGC API — Features. This operation targets the Collection resource.

Support for the HTTP POST method is specified as a requirement in OGC API — Features.

type: object
required:
  - itemType
properties:
  title:
    description: human readable title of the collection
    type: string
  updateFrequency:
    description: a time interval of sampling location. The unit is millisecond.
    type: number
  description:
    description: any description
    type: string
  itemType:
    description: indicator about the type of the items in the moving features collection (the default value is 'movingfeature').
    type: string
    default: "movingfeature"

Listing 1 — Collection Request Body Schema:

The following example adds a new feature (collection information object) to the feature collections. The feature is encoded as JSON. A pseudo-sequence diagram notation is used, below, to illustrate the details of the HTTP communication between the client and the server.

Client                                                           Server
 |                                                                   |
 | POST /collections   HTTP/1.1                                      |
 | Content-Type: application/json                                    |
 |                                                                   |
 | {                                                                 |
 |   "title": "MovingFeatureCollection_1",                           |
 |   "updateFrequency": 1000,                                        |
 |   "description": "a collection of moving features to manage data  |
 |                   in a distinct (physical or logical) space",     |
 |   "itemType": "movingfeature"                                     |
 | }                                                                 |
 |------------------------------------------------------------------>|
 |                                                                   |
 | HTTP/1.1 201 Created                                              |
 | Location: /collections/mfc_1                                      |
 |<------------------------------------------------------------------|

Listing 2 — An Example of Creating a New Collection:

7.3.3.1.  Retrieve

A successful response to the Collections GET operation is a document that contains summary metadata for each collection accessible through an instance of an API implementation. In a typical deployment of the OGC API — Moving Features Standard, the Collections GET response will list collections of all offered resource types. The collections where the value of the itemType property is movingfeature are collections of moving features.

type: object
required:
  - collections
  - links
properties:
  collections:
    type: array
    items:
      $ref: 'collection.yaml'
  links:
    type: array
    items:
      $ref: 'https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/link.yaml'

Listing 3 — Collections GET Response Schema (collections.yaml):

The following JSON payload is an example of a response to an OGC API — Moving Features Collections GET operation.

{
  "collections": [
    {
      "id": "mfc-1",
      "title": "MovingFeatureCollection_1",
      "description": "a collection of moving features to manage data in a distinct (physical or logical) space",
      "itemType": "movingfeature",
      "updateFrequency": 1000,
      "extent": {
        "spatial": {
          "bbox": [
            -180, -90, 190, 90
          ],
          "crs": "http://www.opengis.net/def/crs/OGC/1.3/CRS84"
        },
        "temporal": {
          "interval": [
            "2011-11-11T12:22:11Z","2012-11-24T12:32:43Z"
          ],
          "trs": "http://www.opengis.net/def/uom/ISO-8601/0/Gregorian"
        }
      },
      "links": [
        {
          "href": "https://data.example.org/collections/mfc-1",
          "rel": "self",
          "type": "application/json"
        }
      ]
    }
  ],
  "links": [
    {
      "href": "https://data.example.org/collections",
      "rel": "self",
      "type": "application/json"
    }
  ]
}

Listing 4 — An Example of a Collections JSON Payload:

7.3.3.2.  Create

A successful response to the Collections POST operation is an HTTP status code.

7.4.2.1.  Retrieve

The retrieve operation is defined in the Collection section of the Collections requirements class of OGC API — Common. No modifications are required to support MovingFeature resources.

The {collectionId} path parameter is the unique identifier for a single collection offered by an API implementation instance. The list of valid values for {collectionId} is provided in the /collections response.

Support for the {root}/collections/{collectionId} path is required by OGC API — Common.

7.4.2.2.  Replace

The replace operation is defined in the REPLACE section of the “Create/Replace/Delete” requirements class of OGC API — Features. This operation targets the Collection resource.

Support for the HTTP PUT method is specified as a requirement in OGC API — Features.

The following example replaces the feature created by the Create Example with a new feature (collection metadata without an update frequency). Once again, the replacement feature is represented as a JSON payload. A pseudo-sequence diagram notation is used to illustrate the details of the HTTP communication between the client and the server.

Client                                                           Server
 |                                                                   |
 | PUT /collections/mfc_1   HTTP/1.1                                 |
 | Content-Type: application/json                                    |
 |                                                                   |
 | {                                                                 |
 |   "title": "MovingFeatureCollection_2",                           |
 |   "description": "Title is changed"                               |
 | }                                                                 |
 |------------------------------------------------------------------>|
 |                                                                   |
 | HTTP/1.1 204 OK                                                   |
 |<------------------------------------------------------------------|

Listing 5 — An Example of Replacing an Existing Collection:

7.4.2.3.  Delete

The delete operation is defined in the DELETE section of the “Create/Replace/Delete” requirements class of OGC API — Features.

Support for the HTTP DELETE method is specified as a requirement in OGC API — Features.

The following example deletes the feature created by the Create Example and replaced with a new feature in the Replace Example. A pseudo-sequence diagram notation is used to illustrate the details of the HTTP communication between the client and the server.

Client                                                           Server
 |                                                                   |
 | DELETE /collections/mfc_1   HTTP/1.1                              |
 |------------------------------------------------------------------>|
 |                                                                   |
 | HTTP/1.1 204 OK                                                   |
 |<------------------------------------------------------------------|

Listing 6 — An Example of Deleting an Existing Collection:

7.4.3.1.  Retrieve

A successful response to the Collection GET operation is a set of metadata that describes the collection identified by the {collectionId} parameter.

type: object
required:
  - id
  - links
  - itemType
properties:
  id:
    description: identifier of the collection used, for example, in URIs
    type: string
    example: 'address'
  title:
    description: human readable title of the collection
    type: string
    example: 'address'
  description:
    description: a description of the features in the collection
    type: string
    example: 'An address.'
  links:
    type: array
    items:
      $ref: 'https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/link.yaml'
    example:
      - href: https://data.example.com/buildings
        rel: item
      - href: https://example.com/concepts/buildings.html
        rel: describedby
        type: text/html
  extent:
    $ref: 'https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/extent.yaml'
  itemType:
    description: indicator about the type of the items in the collection
    type: string
    default: 'movingfeature'
  crs:
    description: the list of coordinate reference systems supported by the service
    type: array
    items:
      type: string
    default:
      - 'https://www.opengis.net/def/crs/OGC/1.3/CRS84'
    example:
      - 'https://www.opengis.net/def/crs/OGC/1.3/CRS84'
      - 'https://www.opengis.net/def/crs/EPSG/0/4326'
  updateFrequency:
    description: a time interval of sampling location. The unit is millisecond.
    type: number

Listing 7 — Collection GET Response Schema (collection.yaml)

The following JSON payload is an example of a response to an OGC API — Moving Features Collection GET operation.

{
  "id": "mfc-1",
  "title": "moving_feature_collection_sample",
  "itemType": "movingfeature",
  "updateFrequency": 1000,
  "extent": {
    "spatial": {
      "bbox": [
        -180, -90, 190, 90
      ],
      "crs": [
        "http://www.opengis.net/def/crs/OGC/1.3/CRS84"
      ]
    },
    "temporal": {
      "interval": [
        "2011-11-11T12:22:11Z","2012-11-24T12:32:43Z"
      ],
      "trs": [
        "http://www.opengis.net/def/uom/ISO-8601/0/Gregorian"
      ]
    }
  },
  "links": [
    {
      "href": "https://data.example.org/collections/mfc-1",
      "rel": "self",
      "type": "application/json"
    }
  ]
}

Listing 8 — An Example of Collection GET Operation:

7.4.3.2.  Replace

A successful response to the Collection PUT operation is an HTTP status code.

7.4.3.3.  Delete

A successful response to the Collection DELETE operation is an HTTP status code.

8.3.2.1.  Parameter subTrajectory

The subTrajectory query parameter is defined as follows:

name: subTrajectory
in: query
required: false
schema:
  type: boolean
style: form
explode: false

The subTrajectory query parameter is used to select a subset of a TemporalGeometrySequence for the specified time interval. Each MovingFeature in the MovingFeatures has a TemporalGeometrySequence. The subTrajectory parameter is used to implement the subTrajectory operation, which is defined in the OGC Moving Feature Access Standard. This operation requires two timestamps ( newStartTime and newEndTime) to represent a specified time interval. The time interval for the subTrajectory operation is taken from the datetime parameter.

If the subTrajectory parameter is provided by the client, the endpoint SHALL return only a subset of the trajectory derived from the temporal primitive geometry by the operation at time (newStartTime and newEndTime) included in the subTrajectory parameter, using interpolated trajectory according to the interpolation property in the TemporalPrimitiveGeometry. The interpolation property in the response shall be the same as the original temporal primitive geometry.

Figure 2 — Example of a response result with a subTrajectory parameter

8.3.3.1.  Retrieve

The retrieve operation is defined in the Features section of the ‘Core’ requirements class of OGC API — Features. Additional support for the subTrajectory query parameter is needed to support the MovingFeatures resource.

Support for GET on the {root}/collections/{collectionID}/items path is required by OGC API — Features.

8.3.3.2.  Create

The create operation is defined in the CREATE section of the “Create/Replace/Delete” requirements class of OGC API — Features. This operation targets a single or collection of MovingFeature resources.

Support for the HTTP POST method is specified as a requirement in OGC API — Features.

The following example adds a new feature (MovingFeature object in MF-JSON) to the specific Collection. The feature is represented as a MovingFeature object (or MovingFeatureCollection object) in MF-JSON. A pseudo-sequence diagram notation is used, below, to illustrate the details of the HTTP communication between the client and the server.

Client                                                                  Server
 |                                                                          |
 | POST /collections/mfc_1/items   HTTP/1.1                                 |
 | Content-Type: application/geo+json                                       |
 |                                                                          |
 | {                                                                        |
 |   "type": "Feature",                                                     |
 |   "id": "mf_1",                                                          |
 |   "properties": {                                                        |
 |      "name": "car1",                                                     |
 |      "state": "test1",                                                   |
 |      "video": "http://.../example/video.mpeg"                            |
 |   },                                                                     |
 |   "crs": {                                                               |
 |      "type": "Name",                                                     |
 |      "properties": {                                                     |
 |         "name": "urn:ogc:def:crs:OGC:1.3:CRS84"                          |
 |      }                                                                   |
 |   },                                                                     |
 |   "trs": {                                                               |
 |      "type": "Link",                                                     |
 |      "properties": {                                                     |
 |         "type": "ogcdef",                                                |
 |         "href": "http://www.opengis.net/def/uom/ISO-8601/0/Gregorian"    |
 |      }                                                                   |
 |   },                                                                     |
 |   "temporalGeometry": {                                                  |
 |      "type": "MovingPoint",                                              |
 |      "datetimes": [                                                      |
 |         "2011-07-14T22:01:01.000Z",                                      |
 |         "2011-07-14T22:01:02.000Z",                                      |
 |         "2011-07-14T22:01:03.000Z",                                      |
 |         "2011-07-14T22:01:04.000Z",                                      |
 |         "2011-07-14T22:01:05.000Z"                                       |
 |      ],                                                                  |
 |      "coordinates": [                                                    |
 |         [139.757083,35.627701,0.5],                                      |
 |         [139.757399,35.627701,2.0],                                      |
 |         [139.757555,35.627688,4.0],                                      |
 |         [139.757651,35.627596,4.0],                                      |
 |         [139.757716,35.627483,4.0]                                       |
 |      ],                                                                  |
 |      "interpolation": "Linear",                                          |
 |      "base": {                                                           |
 |         "type": "glTF",                                                  |
 |         "href": "http://.../example/car3dmodel.gltf"                     |
 |      },                                                                  |
 |      "orientations": [                                                   |
 |          {"scales": [1,1,1],"angles": [0,0,0]},                          |
 |          {"scales": [1,1,1],"angles": [0,355,0]},                        |
 |          {"scales": [1,1,1],"angles": [0,0,330]},                        |
 |          {"scales": [1,1,1],"angles": [0,0,300]},                        |
 |          {"scales": [1,1,1],"angles": [0,0,270]},                        |
 |      ]                                                                   |
 |   },                                                                     |
 |   "temporalProperties": [                                                |
 |      {                                                                   |
 |         "datetimes": [                                                   |
 |            "2011-07-14T22:01:01.450Z",                                   |
 |            "2011-07-14T23:01:01.450Z",                                   |
 |            "2011-07-15T00:01:01.450Z"                                    |
 |            ],                                                            |
 |         "length": {                                                      |
 |            "type": "Measure",                                            |
 |            "form": "http://qudt.org/vocab/quantitykind/Length",          |
 |            "values": [1,2.4,1],                                          |
 |            "interpolation": "Linear",                                    |
 |            "description": "description1"                                 |
 |         },                                                               |
 |         "discharge": {                                                   |
 |            "type": "Measure",                                            |
 |            "form": "MQS",                                                |
 |            "values": [3,4,5],                                            |
 |            "interpolation": "Step"                                       |
 |         }                                                                |
 |      },                                                                  |
 |      {                                                                   |
 |         "datetimes": [                                                   |
 |            "2011-07-15T23:01:01.450Z",                                   |
 |            "2011-07-16T00:01:01.450Z"                                    |
 |         ],                                                               |
 |         "camera": {                                                      |
 |            "type": "Image",                                              |
 |            "values": [                                                   |
 |               "http://.../example/image1",                               |
 |               "VBORw0KGgoAAAANSUhEU......"                               |
 |            ],                                                            |
 |            "interpolation": "Discrete"                                   |
 |         },                                                               |
 |         "labels": {                                                      |
 |            "type": "Text",                                               |
 |            "values": ["car","human"],                                    |
 |            "interpolation": "Discrete"                                   |
 |         }                                                                |
 |      }                                                                   |
 |   ]                                                                      |
 | }                                                                        |
 |------------------------------------------------------------------------->|
 |                                                                          |
 | HTTP/1.1 201 Created                                                     |
 | Location: /collections/mfc_1/items/mf_1                                  |
 |<-------------------------------------------------------------------------|

Listing 10 — An Example of Creating a New MovingFeature Object:

8.3.4.1.  Retrieve

A successful response to the MovingFeatures GET operation is a document that contains the static data for a set of moving features.

If the value of the subTrajectory query parameter is provided, the value of the corresponding temporalGeometry property of each moving feature is calculated using the subTrajectory parameter value and included in the result, i.e., a MovingFeatureCollection object of MF-JSON.

In a typical deployment of the OGC API — Moving Features, the MovingFeatures GET response will list the MovingFeature resources.

type: object
required:
  - type
  - features
properties:
  type:
    type: string
    enum:
      - 'FeatureCollection'
  features:
    type: array
    nullable: true
    items:
      $ref: 'movingFeature.yaml'
  crs:
    $ref: "https://schemas.opengis.net/movingfeatures/1.0/MF-JSON_Prism.schema.json#/definitions/crs"
  trs:
    $ref: "https://schemas.opengis.net/movingfeatures/1.0/MF-JSON_Prism.schema.json#/definitions/trs"
  bbox:
    $ref: "https://schemas.opengis.net/movingfeatures/1.0/MF-JSON_Prism.schema.json#/definitions/bbox"
  time:
    $ref: "https://schemas.opengis.net/movingfeatures/1.0/MF-JSON_Prism.schema.json#/definitions/time"
  links:
    type: array
    items:
      $ref: 'https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/link.yaml'
  timeStamp:
    type: string
    format: date-time
  numberMatched:
    type: integer
    minimum: 0
  numberReturned:
    type: integer
    minimum: 0

Listing 11 — MovingFeatures GET Response Schema (movingFeatureCollection.yaml):

The following JSON payload is an example of a response to an OGC API — Moving Features MovingFeatures GET operation.

{
  "type": "FeatureCollection",
  "features":[
    {
      "id": "mf-1",
      "type": "Feature",
      "geometry":{
        "type": "LineString",
        "coordinates": [
          [139.757083, 35.627701, 0.5],
          [139.757399, 35.627701, 2.0],
          [139.757555, 35.627688, 4.0],
          [139.757651, 35.627596, 4.0],
          [139.757716, 35.627483, 4.0]
        ]
      },
      "properties":{
        "label": "car",
        "state": "test1",
        "video": "http://www.opengis.net/spec/movingfeatures/json/1.0/prism/example/video.mpeg"
      },
      "bbox":[
        139.757083, 35.627483, 0.0,
        139.757716, 35.627701, 4.5
      ],
      "time":[
        "2011-07-14T22:01:01Z",
        "2011-07-15T01:11:22Z"
      ],
      "crs": {
        "type": "Name",
        "properties": "urn:ogc:def:crs:OGC:1.3:CRS84"
      },
      "trs": {
        "type": "Name",
        "properties": "urn:ogc:data:time:iso8601"
      }
    }
  ],
  "crs": {
    "type": "Name",
    "properties": "urn:ogc:def:crs:OGC:1.3:CRS84"
  },
  "trs": {
    "type": "Name",
    "properties": "urn:ogc:data:time:iso8601"
  },
  "links":[
    {
      "href": "https://data.example.org/collections/mfc-1/items",
      "rel": "self",
      "type": "application/geo+json"
    },
    {
      "href": "https://data.example.org/collections/mfc-1/items&offset=1&limit=1",
      "rel": "next",
      "type": "application/geo+json"
    }
  ],
  "timeStamp": "2020-01-01T12:00:00Z",
  "numberMatched": 100,
  "numberReturned": 1
}

Listing 12 — An Example of a MovingFeatures GET Operation:

8.3.4.2.  Create

A successful response to the MovingFeatures POST operation is an HTTP status code.

A MovingFeatureCollection object of MF-JSON is a collection of MovingFeature objects. Posting a collection of resources is the same as posting a single resource consecutively. However, because the result must be returned in a single response, the Locations header includes a list of the URIs of the newly added resources.

8.4.2.1.  Retrieve

The retrieve operation is defined in the Feature section of the “Core” requirements class of OGC API — Features. No modifications are needed to support MovingFeature resources.

The {mFeatureId} path parameter is the unique identifier for a single moving feature offered by the API. The list of valid values for {mFeatureId} is provided in the {root}/collections/{collectionId}/items GET response.

Support for GET on the {root}/collections/{collectionID}/items/{mFeatureId} path is required by OGC API — Features.

8.4.2.2.  Delete

The delete operation is defined in the DELETE section of the “Create/Replace/Delete” requirements class of OGC API — Features.

Support for the HTTP DELETE method is required by OGC API — Features.

8.4.3.1.  Retrieve

A successful response to the MovingFeature GET operation is a set of metadata that describes the moving feature identified by the {mFeatureId} parameter. This response does not include a set of temporal object information. The temporal object information may be accessed using TemporalGeometry and TemporalProperties operations.

type: object
required:
  - id
  - type
properties:
  type:
    type: string
    enum:
      - 'Feature'
  temporalGeometry:
    $ref: "https://schemas.opengis.net/movingfeatures/1.0/MF-JSON_Prism.schema.json#/definitions/temporalGeometry"
  temporalProperties:
    $ref: "https://schemas.opengis.net/movingfeatures/1.0/MF-JSON_Prism.schema.json#/definitions/temporalProperties"
  crs:
    $ref: "https://schemas.opengis.net/movingfeatures/1.0/MF-JSON_Prism.schema.json#/definitions/crs"
  trs:
    $ref: "https://schemas.opengis.net/movingfeatures/1.0/MF-JSON_Prism.schema.json#/definitions/trs"
  bbox:
    $ref: "https://schemas.opengis.net/movingfeatures/1.0/MF-JSON_Prism.schema.json#/definitions/bbox"
  time:
    $ref: "https://schemas.opengis.net/movingfeatures/1.0/MF-JSON_Prism.schema.json#/definitions/time"
  geometry:
    $ref: 'https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/geometryGeoJSON.yaml'
  properties:
    type: object
    nullable: true
  id:
    description: 'An identifier for the feature'
    oneOf:
      - type: string
      - type: integer
  links:
    type: array
    items:
      $ref: 'https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/link.yaml'

Listing 13 — MovingFeature GET Response Schema (movingFeature.yaml):

The time property of the MovingFeature response represents a particular period of moving feature existence.

The following JSON payload is an example of a response to an OGC API — Moving Features MovingFeature operation.

{
  "id": "mf-1",
  "type": "Feature",
  "geometry":{
    "type": "LineString",
    "coordinates": [
      [139.757083, 35.627701, 0.5],
      [139.757399, 35.627701, 2.0],
      [139.757555, 35.627688, 4.0],
      [139.757651, 35.627596, 4.0],
      [139.757716, 35.627483, 4.0]
    ]
  },
  "properties":{
    "name": "car1",
    "state": "test1",
    "video": "http://www.opengis.net/spec/movingfeatures/json/1.0/prism/example/video.mpeg"
  },
  "bbox":[
    139.757083, 35.627483, 0.0,
    139.757716, 35.627701, 4.5
  ],
  "time":[
    "2011-07-14T22:01:01Z",
    "2011-07-15T01:11:22Z"
  ],
  "crs": {
    "type": "Name",
    "properties": "urn:ogc:def:crs:OGC:1.3:CRS84"
  },
  "trs": {
    "type": "Name",
    "properties": "urn:ogc:data:time:iso8601"
  }
}

Listing 14 — An Example of a MovingFeature JSON Payload:

8.4.3.2.  Delete

A successful response to the Collection DELETE operation is an HTTP status code.

8.5.2.1.  Parameter leaf

The leaf query parameter is defined as follows:

name: leaf
in: query
required: false
schema:
  type: array
  uniqueItems: true
  minItems: 1
  items:
    type: string
    format: date-time
style: form
explode: false

The leaf parameter is a sequence of monotonic increasing instants represented by date-time strings (ex. “2018-02-12T23:20:50Z”) whose structure adheres to IETF RFC3339. The leaf parameter consists of a list of the date-time format strings, different from datetime parameter. The list does not allow the same element value. Listing 16 shows valid expression examples of the leaf parameter.

(O) "2018-02-12T23:20:50Z"

(O) "2018-02-12T23:20:50Z","2018-02-12T23:30:50Z"

(O) "2018-02-12T23:20:50Z","2018-02-12T23:30:50Z","2018-02-12T23:40:50Z"

(X) "2018-02-12T23:20:50Z","2018-02-12T23:20:50Z"

(X) "2018-02-12T23:20:50Z","2018-02-12T22:40:50Z"

Listing 16 — leaf parameter valid (and invalid) Examples

If the leaf parameter is provided by the client, the endpoint returns only temporal geometry coordinate (or temporal property value) with the leaf query at each time included in the leaf parameter, similar to pointAtTime operation in the OGC Moving Feature Access Standard. The interpolation property in the response shall be “Discrete”.

Figure 3 — Example of a response result with leaf parameter

8.5.3.1.  Retrieve

8.5.3.2.  Create

The create operation is defined in the CREATE section of the “Create/Replace/Delete” requirements class of OGC API — Features. This operation targets the TemporalPrimitiveGeometry resource.

Support for the HTTP POST method is specified as a requirement in OGC API — Features.

The following example adds a new feature (TemporalPrimitiveGeometry object in MF-JSON) to the feature created by the Creation a MovingFeature Example. The feature is represented as a TemporalPrimitiveGeometry object in MF-JSON, which is an extension of the JSON. A pseudo-sequence diagram notation is used, below, to illustrate the details of the HTTP communication between the client and the server.

Client                                                                  Server
 |                                                                          |
 | POST /collections/mfc_1/items/mf_1/tgsequence  HTTP/1.1                  |
 | Content-Type: application/json                                           |
 |                                                                          |
 | {                                                                        |
 |    "id": "tg_1",                                                         |
 |    "type": "MovingPoint",                                                |
 |    "datetimes": [                                                        |
 |       "2011-07-14T22:01:06.000Z",                                        |
 |       "2011-07-14T22:01:07.000Z",                                        |
 |       "2011-07-14T22:01:08.000Z"                                         |
 |    ],                                                                    |
 |    "coordinates": [                                                      |
 |       [139.757716,35.627483,4.0],                                        |
 |       [139.757782,35.627483,4.0],                                        |
 |       [139.757843,35.627483,4.0]                                         |
 |    ],                                                                    |
 |    "interpolation": "Linear",                                            |
 |    "base": {                                                             |
 |       "type": "glTF",                                                    |
 |       "href": "http://.../example/car3dmodel.gltf"                       |
 |    },                                                                    |
 |    "orientations": [                                                     |
 |        {"scales": [1,1,1],"angles": [0,0,270]},                          |
 |        {"scales": [1,1,1],"angles": [0,0,270]},                          |
 |        {"scales": [1,1,1],"angles": [0,0,270]}                           |
 |    ]                                                                     |
 | }                                                                        |
 |------------------------------------------------------------------------->|
 |                                                                          |
 | HTTP/1.1 201 Created                                                     |
 | Location: /collections/mfc_1/items/mf_1/tgsequence/tg_1                  |
 |<-------------------------------------------------------------------------|

Listing 17 — An Example of Creating a New TemporalPrimitiveGeometry Object:

8.5.4.1.  Retrieve

A successful response to the TemporalGeometrySequence GET operation is a document that contains the set of temporal geometry of the moving feature identified by the {mFeatureId} parameter.

type: object
required:
  - type
  - geometrySequence
properties:
  type:
    type: string
    enum:
      - "TemporalGeometrySequence"
  geometrySequence:
    type: array
    items:
      $ref: 'https://schemas.opengis.net/movingfeatures/1.0/MF-JSON_Prism.schema.json#/definitions/temporalPrimitiveGeometry'
  links:
    type: array
    items:
      $ref: 'https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/link.yaml'
  timeStamp:
    type: string
    format: date-time
  numberMatched:
    type: integer
    minimum: 0
  numberReturned:
    type: integer
    minimum: 0

Listing 18 — TemporalGeometrySequence GET Response Schema (temporalGeometrySequence.yaml):

The following JSON payload is an example of a response to an OGC API — Moving Features TemporalGeometrySequence GET operation.

{
  "type": "TemporalGeometrySequence",
  "geometrySequence": [
    {
      "id": "tg-1",
      "type": "MovingPoint",
      "datetimes": [
        "2011-07-14T22:01:02Z",
        "2011-07-14T22:01:03Z",
        "2011-07-14T22:01:04Z"
      ],
      "coordinates": [
        [139.757399, 35.627701, 2.0],
        [139.757555, 35.627688, 4.0],
        [139.757651, 35.627596, 4.0]
      ],
      "interpolation": "Linear",
      "base": {
        "type": "glTF",
        "href": "https://www.opengis.net/spec/movingfeatures/json/1.0/prism/example/car3dmodel.gltf"
      },
      "orientations":[
        {
          "scales": [1,1,1],
          "angles": [0,355,0]
        },
        {
          "scales": [1,1,1],
          "angles": [0,0,330]
        },
        {
          "scales": [1,1,1],
          "angles": [0,0,300]
        }
      ],
      "crs": {
        "type": "Name",
        "properties": "urn:ogc:def:crs:OGC:1.3:CRS84"
      },
      "trs": {
        "type": "Name",
        "properties": "urn:ogc:data:time:iso8601"
      }
    }
  ],
  "links": [
    {
      "href": "https://data.example.org/collections/mfc-1/items/mf-1/tgsequence",
      "rel": "self",
      "type": "application/json"
    },
    {
      "href": "https://data.example.org/collections/mfc-1/items/mf-1/tgsequence&offset=10&limit=1",
      "rel": "next",
      "type": "application/json"
    }
  ],
  "timeStamp": "2021-09-01T12:00:00Z",
  "numberMatched": 100,
  "numberReturned": 1
}

Listing 19 — An Example of a TemporalGeometrySequence GET operation:

8.5.4.2.  Create

A successful response to the TemporalGeometrySequence POST operation is an HTTP status code.

8.6.2.1.  Delete

The delete operation is defined in the DELETE conformance class of API — Features.

The {tGeometryId} parameter is the unique identifier for a single temporal primitive geometry object offered by the API. The list of valid values for {tGeometryId} is provided in the {root}/collections/{collectionId}/items/{mFeatureId}/tgsequence GET response.

Support for the HTTP DELETE method is specified as a requirement in OGC API — Features.

8.6.3.1.  Delete

A successful response to the TemporalPrimitiveGeometry DELETE operation is an HTTP status code.

8.8.2.1.  Parameter subTemporalValue

The subTemporalValue query parameter is defined as follows:

name: subTemporalValue
in: query
required: false
schema:
  type: boolean
style: form
explode: false

The subTemporalValue query parameter is used to select a subset of TemporalProperty for the specified time interval. Each TemporalProperty in the TemporalProperties has a sequence of TemporalPrimitiveValue objects. The subTemporalValue parameter behaves functionally the same as the subTrajectory parameter. The difference is that subTrajectory is associated with temporal geometry, while subTemporalValue is associated with temporal properties.

8.8.3.1.  Retrieve

8.8.3.2.  Create

The create operation is defined in the CREATE conformance class in the OGC API — Features Standard. This operation targets a single or a collection of TemporalProperty resources.

Support for the HTTP POST method is specified as a requirement in OGC API — Features.

type: object
required:
  - name
  - type
properties:
  name:
    type: string
  type:
    type: string
    enum:
      - 'TBoolean'
      - 'TText'
      - 'TInteger'
      - 'TReal'
      - 'TImage'
  form:
    oneOf:
      - type: string
        format: uri
      - type: string
        minLength: 3
        maxLength: 3
  valueSequence:
    type: array
    uniqueItems: true
    items:
      $ref: 'temporalPrimitiveValue.yaml'
  description:
    type: string
  links:
    type: array
    items:
      $ref: 'https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/link.yaml'

Listing 21 — TemporalProperties Request Body Schema (temporalProperty.yaml):

The following example adds a new feature (TemporalProperty Object and ParametricValues Object in MF-JSON) to the feature created by the Creation of a MovingFeature Example. The feature is represented as a JSON payload. A pseudo-sequence diagram notation is used, below, to illustrate the details of the HTTP communication between the client and the server.

Client                                                                  Server
 |                                                                          |
 | POST /collections/mfc_1/items/mf_1/tproperties   HTTP/1.1                |
 | Content-Type: application/json                                           |
 |                                                                          |
 | {                                                                        |
 |    "name": "speed",                                                      |
 |    "type": "TReal",                                                      |
 |    "form": "KMH"                                                         |
 | }                                                                        |
 |------------------------------------------------------------------------->|
 |                                                                          |
 | HTTP/1.1 201 Created                                                     |
 | Location: /collections/mfc_1/items/mf_1/tproperties/speed                |
 |<-------------------------------------------------------------------------|

Listing 22 — An Example of Creating a New TemporalProperty Object:

 Client                                                                  Server
 |                                                                          |
 | POST /collections/mfc_1/items/mf_1/tproperties   HTTP/1.1                |
 | Content-Type: application/json                                           |
 |                                                                          |
 | {                                                                        |
 |    "datetimes": [                                                        |
 |       "2011-07-14T22:01:06.000Z",                                        |
 |       "2011-07-14T22:01:07.000Z",                                        |
 |       "2011-07-14T22:01:08.000Z",                                        |
 |    ],                                                                    |
 |    "speed": {                                                            |
 |       "type": "Measure",                                                 |
 |       "form": "KMH",                                                     |
 |       "values": [65.0, 70.0, 80.0],                                      |
 |       "interpolation": "Linear"                                          |
 |    }                                                                     |
 | }                                                                        |
 |------------------------------------------------------------------------->|
 |                                                                          |
 | HTTP/1.1 201 Created                                                     |
 | Location: /collections/mfc_1/items/mf_1/tproperties/speed                |
 |<-------------------------------------------------------------------------|

Listing 23 — An Example of Creating a New TemporalProperty Object with ParametricValues as a MF-JSON encoding:

8.8.4.1.  Retrieve

A successful response to the TemporalProperties GET operation is a document that contains the set of metadata (and static data) of TemporalProperty in the moving feature identified by the {mFeatureId} parameter. The response result does not include dynamic (and temporal information).

If the value of the subTemporalValue query parameter is provided, the temporal value of the corresponding temporalProperties property of the moving feature is calculated using the subTemporalValue parameter value and included in the result.

type: object
required:
  - temporalProperties
properties:
  temporalProperties:
    oneOf:
      - $ref: "https://schemas.opengis.net/movingfeatures/1.0/MF-JSON_Prism.schema.json#/definitions/temporalProperties"
      - type: array
        items:
          $ref: "temporalProperty.yaml"
  links:
    type: array
    items:
      $ref: 'https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/link.yaml'
  timeStamp:
    type: string
    format: date-time
  numberMatched:
    type: integer
    minimum: 0
  numberReturned:
    type: integer
    minimum: 0

Listing 24 — TemporalProperties GET Response Schema (TemporalProperties.yaml):

The following JSON payload is an example of a response to an OGC API — Moving Features TemporalProperties GET operation.

{
  "temporalProperties": [
    {
      "name": "length",
      "type": "TReal",
      "form": "http://qudt.org/vocab/quantitykind/Length"
    },
    {
      "name": "speed",
      "type": "TReal",
      "form": "KMH"
    }
  ],
  "links": [
    {
      "href": "https://data.example.org/collections/mfc-1/items/mf-1/tproperties",
      "rel": "self",
      "type": "application/json"
    },
    {
      "href": "https://data.example.org/collections/mfc-1/items/mf-1/tproperties&offset=2&limit=2",
      "rel": "next",
      "type": "application/json"
    }
  ],
  "timeStamp": "2021-09-01T12:00:00Z",
  "numberMatched": 10,
  "numberReturned": 2
}

Listing 25 — An Example of a TemporalProperties GET Operation:

The following JSON payload is an example of a response to an OGC API — Moving Features TemporalProperties GET operation with query parameter subTemporalValue.

{
  "temporalProperties": [
    {
      "datetimes": ["2011-07-14T22:01:06.000Z", "2011-07-14T22:01:07.000Z", "2011-07-14T22:01:08.000Z"],
      "length": {
        "type": "Measure",
        "form": "http://qudt.org/vocab/quantitykind/Length",
        "values": [1.0, 2.4, 1.0],
        "interpolation": "Linear"
      },
      "speed" : {
        "type" : "Measure",
        "form" : "KMH",
        "values" : [65.0, 70.0, 80.0],
        "interpolation": "Linear"
      }
    }
  ],
  "links": [
    {
      "href": "https://data.example.org/collections/mfc-1/items/mf-1/tproperties",
      "rel": "self",
      "type": "application/json"
    },
    {
      "href": "https://data.example.org/collections/mfc-1/items/mf-1/tproperties&offset=2&limit=2",
      "rel": "next",
      "type": "application/json"
    }
  ],
  "timeStamp": "2021-09-01T12:00:00Z",
  "numberMatched": 10,
  "numberReturned": 2
}

Listing 26 — An Example of a TemporalProperties GET Operation with subTemporalValue:

8.8.4.2.  Create

A successful response to the TemporalProperties POST operation is an HTTP status code.

A ParametricValues Object in MF-JSON can be a collection of TemporalProperty objects. Posting a collection of resources is the same as posting a single resource consecutively. However, because the result must be returned in a single response, the Locations header includes a list of the URIs of the newly added resources.

8.9.3.1.  Retrieve

The {tPropertyName} parameter is the unique identifier for a single temporal property value offered by an implementation instance (endpoint) of the OGC API — Moving Features. The list of valid values for {tPropertyName} is provided in the {root}/collections/{collectionId}/items/{mFeatureId}/tproperties GET response.

8.9.3.2.  Create

The create operation is defined in the CREATE conformance class in the OGC API — Features Standard. This operation targets the new TemporalPrimitiveValue object.

Support for the HTTP POST method is specified as a requirement in OGC API — Features.

type: object
required:
  - datetimes
  - values
  - interpolation
properties:
  datetimes:
    type: array
    uniqueItems: true
    minItems: 2
    items:
      type: string
      format: date-time
  values:
    oneOf:
      - type: number
      - type: string
      - type: boolean
  interpolation:
    type: string
    enum:
      - 'Discrete'
      - 'Step'
      - 'Linear'
      - 'Regression'

Listing 27 — TemporalProperty Request Body Schema (TemporalPrimitiveValue.yaml):

The following example adds a new feature (TemporalPrimitiveValue resource) to the feature created by Creating a New TemporalProperty Object Example. The feature is represented as a JSON payload. A pseudo-sequence diagram notation is used, below, to illustrate the details of the HTTP communication between the client and the server.

Client                                                                  Server
 |                                                                          |
 | POST /collections/mfc_1/items/mf_1/tproperties/speed   HTTP/1.1          |
 | Content-Type: application/json                                           |
 |                                                                          |
 | {                                                                        |
 |    "datetimes": [                                                        |
 |       "2011-07-14T22:01:09.000Z",                                        |
 |       "2011-07-14T22:01:010.000Z",                                       |
 |    ],                                                                    |
 |    "values": [                                                           |
 |       90.0,                                                              |
 |       95.0,                                                              |
 |    ],                                                                    |
 |    "interpolation": "Linear"                                             |
 | }                                                                        |
 |------------------------------------------------------------------------->|
 |                                                                          |
 | HTTP/1.1 201 Created                                                     |
 | Location: /collections/mfc_1/items/mf_1/tproperties/speed                |
 |<-------------------------------------------------------------------------|

Listing 28 — An Example of Creating a New TemporalPrimitiveValue Object:

8.9.3.3.  Delete

The delete operation is defined in the DELETE section of the “Create/Replace/Delete” requirements class of OGC API — Features.

Support for the HTTP DELETE method is specified as a requirement in OGC API — Features.

8.9.4.1.  Retrieve

A successful response to the TemporalProperty GET operation is a temporal property identified by the {tPropertyName} parameter.

The following JSON payload is an example of a response to an OGC API — Moving Features TemporalProperty GET operation.

{
  "temporalProperties": [
    {
      "datetimes":[
        "2011-07-14T22:01:02Z",
        "2011-07-14T22:01:03Z",
        "2011-07-14T22:01:04Z"
      ],
      "values":[
        65.0,
        70.0,
        80.0
      ],
      "interpolation": "Linear"
    },
    {
      "datetimes":[
        "2011-07-15T08:00:00Z",
        "2011-07-15T08:00:01Z",
        "2011-07-15T08:00:02Z"
      ],
      "values":[
        0.0,
        20.0,
        50.0
      ],
      "interpolation": "Linear"
    }
  ],
  "links": [
    {
      "href": "https://data.example.org/collections/mfc-1/items/mf-1/tproperties/speed",
      "rel": "self",
      "type": "application/json"
    }
  ]
}

Listing 29 — An Example of TemporalProperty GET Operation:

8.9.4.2.  Create

A successful response to the TemporalProperty POST operation is an HTTP status code.

8.9.4.3.  Delete

A successful response to the TemporalProperty DELETE operation is an HTTP status code.

8.10.2.1.  Delete

The delete operation is defined in the DELETE section of the “Create/Replace/Delete” requirements class of OGC API — Features.

The {tValueId} parameter is the unique identifier for a single temporal primitive value object offered by the API. The list of valid values for {tValueId} is provided in the {root}/collections/{collectionId}/items/{mFeatureId}/tproperties/{tPropertyName} GET response.

Support for the HTTP DELETE method is specified as a requirement in OGC API — Features.

8.10.3.1.  Delete

A successful response to the TemporalPrimitiveValue DELETE operation is an HTTP status code.