Building Blocks specified in OGC API - Moving Features - Part 1: Core (0.1.0)

Download OpenAPI specification:Download

Taehoon Kim: kim.taehoon@aist.go.jp License: OGC License

This is the OpenAPI definition of Moving Features API specification that conforms to the OGC Moving Features Encoding Extension - JSON.

Capabilities

Essential characteristics of the information available from the API.

Landing page

The landing page provides links to the API definition, the conformance statements and to the feature collections in this dataset.

Responses

Response samples

Content type
application/json
{
  • "title": "Moving features data server",
  • "description": "Access to data about moving features",
  • "links": []
}

Information about specifications that this API conforms to

A list of all conformance classes specified in a standard that the server conforms to.

Responses

API definition

A list of all API definition

Responses

Response samples

Content type
application/json
{
  • "openapi": "3.0.3",
  • "info": {},
  • "tags": [
    ],
  • "paths": {
    },
  • "components": {
    }
}

Retrieve catalogs of moving features collection

A user can retrieve catalogs to access collections by simple filtering and a limit.

Responses

Response samples

Content type
application/json
{}

MovingFeatureCollection

Collections of moving features to be logically managed by a user.

Register metadata about a collection of moving features

A user SHOULD register metadata about a collection of moving features into the system.

Request Body schema: application/json
title
string

human readable title of the collection

updateFrequency
number

a time interval of sampling location. The unit is millisecond.

description
string

any description

itemType
required
string
Default: "movingfeature"

indicator about the type of the items in the moving features collection (the default value is 'movingfeature').

Responses

Request samples

Content type
application/json
{
  • "title": "moving_feature_collection_sample",
  • "updateFrequency": 1000,
  • "description": "example"
}

Response samples

Content type
application/json
{
  • "id": "mfc-1"
}

Access metadata about the collection

A user can access metadata with id collectionId.

path Parameters
collectionId
required
string

local identifier of a collection

Responses

Response samples

Content type
application/json
{}

Delete the collection

The collection catalog with id collectionId and including metadata and moving features SHOULD be deleted.

path Parameters
collectionId
required
string

local identifier of a collection

Responses

Response samples

Content type
application/json
{
  • "code": "500",
  • "description": "Server Internal Error"
}

Replace metadata about the collection

A user SHOULD replace metadata with id collectionId.

The request body schema is the same the POST's one.

However, updateFrequency property is NOT updated.

path Parameters
collectionId
required
string

local identifier of a collection

Request Body schema: application/json
title
string

human readable title of the collection

updateFrequency
number

a time interval of sampling location. The unit is millisecond.

description
string

any description

itemType
required
string
Default: "movingfeature"

indicator about the type of the items in the moving features collection (the default value is 'movingfeature').

Responses

Request samples

Content type
application/json
{
  • "title": "moving_feature_collection_sample",
  • "updateFrequency": 1000,
  • "description": "example"
}

Response samples

Content type
application/json
{
  • "code": "500",
  • "description": "Server Internal Error"
}

MovingFeatures

Moving feature data, including the temporal geometry, temporal properties, etc.

Retrieve moving feature collection

A user can retrieve moving feature collection to access the static information of the moving feature by simple filtering and a limit.

Specifically, if the subTrajectory parameter is "true", it will return the temporal geometry within the time interval specified by datetime parameter.

path Parameters
collectionId
required
string

local identifier of a collection

query Parameters
Array of numbers or Array of numbers

Only features that have a geometry that intersects the bounding box are selected. The bounding box is provided as four or six numbers, depending on whether the coordinate reference system includes a vertical axis (height or depth):

  • Lower left corner, coordinate axis 1
  • Lower left corner, coordinate axis 2
  • Minimum value, coordinate axis 3 (optional)
  • Upper right corner, coordinate axis 1
  • Upper right corner, coordinate axis 2
  • Maximum value, coordinate axis 3 (optional)

If the value consists of four numbers, the coordinate reference system is WGS 84 longitude/latitude (http://www.opengis.net/def/crs/OGC/1.3/CRS84) unless a different coordinate reference system is specified in the parameter bbox-crs.

If the value consists of six numbers, the coordinate reference system is WGS 84 longitude/latitude/ellipsoidal height (http://www.opengis.net/def/crs/OGC/0/CRS84h) unless a different coordinate reference system is specified in the parameter bbox-crs.

The query parameter bbox-crs is specified in OGC API - Features - Part 2: Coordinate Reference Systems by Reference.

For WGS 84 longitude/latitude the values are in most cases the sequence of minimum longitude, minimum latitude, maximum longitude and maximum latitude. However, in cases where the box spans the antimeridian the first value (west-most box edge) is larger than the third value (east-most box edge).

If the vertical axis is included, the third and the sixth number are the bottom and the top of the 3-dimensional bounding box.

If a feature has multiple spatial geometry properties, it is the decision of the server whether only a single spatial geometry property is used to determine the extent or all relevant geometries.

datetime
required
string

Either a date-time or an interval. Date and time expressions adhere to RFC 3339. Intervals may be bounded or half-bounded (double-dots at start or end).

Examples:

  • A date-time: "2018-02-12T23:20:50Z"
  • A bounded interval: "2018-02-12T00:00:00Z/2018-03-18T12:31:12Z"
  • Half-bounded intervals: "2018-02-12T00:00:00Z/.." or "../2018-03-18T12:31:12Z"

Only features that have temporal information that intersects the value of datetime are selected.

If a feature has multiple temporal properties, it is the decision of the server whether only a single temporal property is used to determine the extent or all relevant temporal properties.

limit
integer [ 1 .. 10000 ]
Default: 10

The optional limit parameter limits the number of items that are presented in the response document.

Only items are counted that are on the first level of the collection in the response document. Nested objects contained within the explicitly requested items shall not be counted.

Minimum = 1. Maximum = 10000. Default = 10.

subTrajectory
boolean

The subTrajectory parameter is a boolean value used with the datetime parameter. If the subTrajectory is "true",

  • the datetime must be a bounded interval, not half-bounded intervals or a date-time.
  • the datetime represents a specified time interval (new start time and new end time)
  • only features with a temporal geometry intersecting the given time interval will return.

The subTrajectory query implements subTrajectory operation, which is defined in the OGC Moving Feature Access. This operation returns only a subsequence of temporal geometry within a time interval contained in the datetime parameter, using interpolated trajectory according to the interpolation property.

If the subTrajectory parameter is provided with a bbox parameter, it will only apply to resources that intersect with a bbox parameter.

The subTrajectory parameter must not be used with the leaf parameter. Only one of these parameters can be used in the HTTP GET operation.

Responses

Response samples

Content type
application/json
{
  • "type": "FeatureCollection",
  • "features": [
    ],
  • "crs": {
    },
  • "trs": {
    },
  • "links": [],
  • "timeStamp": "2020-01-01T12:00:00Z",
  • "numberMatched": 100,
  • "numberReturned": 1
}

Insert moving features

A user SHOULD insert a set of moving features or a moving feature into a collection with id collectionId.

The request body schema SHALL follows the MovingFeature object or MovingFeatureCollection object in the OGC MF-JSON.

path Parameters
collectionId
required
string

local identifier of a collection

Request Body schema: application/json
One of
type
required
string
Value: "Feature"
required
MF-JSON TemporalPrimitiveGeometry (object) or MF-JSON TemporalComplexGeometry (object) (MF-JSON TemporalGeometry)

MF-JSON Prism encoding TemporalGeometry Object

Array of objects or null (MF-JSON TemporalProperties)

MF-JSON Prism encoding TemporalProperties Object

(MF-JSON NamedCRS (object or null)) or (MF-JSON LinkedCRS (object or null)) (MF-JSON CRS)

MF-JSON Prism encoding CoordinateReferenceSystem Object

(MF-JSON LinkedCRS (object or null)) or (MF-JSON TRS (object or null)) (MF-JSON TRS)

The "trs" member in MovingFeature object

bbox
Array of numbers or null (MF-JSON BoundingBox) >= 4 items

MF-JSON Prism encoding BoundingBox Object

time
Array of strings or null (MF-JSON LifeSpan) = 2 items unique

MF-JSON Prism encoding LifeSpan Object

pointGeoJSON (object) or multipointGeoJSON (object) or linestringGeoJSON (object) or multilinestringGeoJSON (object) or polygonGeoJSON (object) or multipolygonGeoJSON (object) or geometrycollectionGeoJSON (object) (geometryGeoJSON)
properties
object or null
string or integer

An identifier for the feature

Responses

Request samples

Content type
application/json
{
  • "type": "Feature",
  • "crs": {
    },
  • "trs": {},
  • "temporalGeometry": {
    },
  • "temporalProperties": [
    ],
  • "geometry": {
    },
  • "properties": {},
  • "bbox": [
    ],
  • "time": [
    ],
  • "id": "mf-1"
}

Response samples

Content type
application/json
{
  • "code": "500",
  • "description": "Server Internal Error"
}

Access the static data of the moving feature

A user can access a static data of a moving feature with id mFeatureId.

The static data of a moving feature is not included temporal geometries and temporal properties.

path Parameters
collectionId
required
string

local identifier of a collection

mFeatureId
required
string

local identifier of a moving feature

Responses

Response samples

Content type
application/geo+json
{
  • "id": "mf-1",
  • "type": "Feature",
  • "geometry": {
    },
  • "properties": {},
  • "bbox": [
    ],
  • "time": [
    ],
  • "crs": {
    },
  • "trs": {
    }
}

Delete a single moving feature

The moving feature with id mFeatureId and including temporal geometries and properties SHOULD be deleted.

path Parameters
collectionId
required
string

local identifier of a collection

mFeatureId
required
string

local identifier of a moving feature

Responses

Response samples

Content type
application/json
{
  • "code": "500",
  • "description": "Server Internal Error"
}

TemporalGeometry

The spatial change over time (temporal geometry), representing the movement of the rigid or nonrigid body of a feature.

Retrieve the movement data of the single moving feature

A user can retrieve only the movement data of a moving feature with id mFeatureId by simple filtering and a limit.

path Parameters
collectionId
required
string

local identifier of a collection

mFeatureId
required
string

local identifier of a moving feature

query Parameters
Array of numbers or Array of numbers

Only features that have a geometry that intersects the bounding box are selected. The bounding box is provided as four or six numbers, depending on whether the coordinate reference system includes a vertical axis (height or depth):

  • Lower left corner, coordinate axis 1
  • Lower left corner, coordinate axis 2
  • Minimum value, coordinate axis 3 (optional)
  • Upper right corner, coordinate axis 1
  • Upper right corner, coordinate axis 2
  • Maximum value, coordinate axis 3 (optional)

If the value consists of four numbers, the coordinate reference system is WGS 84 longitude/latitude (http://www.opengis.net/def/crs/OGC/1.3/CRS84) unless a different coordinate reference system is specified in the parameter bbox-crs.

If the value consists of six numbers, the coordinate reference system is WGS 84 longitude/latitude/ellipsoidal height (http://www.opengis.net/def/crs/OGC/0/CRS84h) unless a different coordinate reference system is specified in the parameter bbox-crs.

The query parameter bbox-crs is specified in OGC API - Features - Part 2: Coordinate Reference Systems by Reference.

For WGS 84 longitude/latitude the values are in most cases the sequence of minimum longitude, minimum latitude, maximum longitude and maximum latitude. However, in cases where the box spans the antimeridian the first value (west-most box edge) is larger than the third value (east-most box edge).

If the vertical axis is included, the third and the sixth number are the bottom and the top of the 3-dimensional bounding box.

If a feature has multiple spatial geometry properties, it is the decision of the server whether only a single spatial geometry property is used to determine the extent or all relevant geometries.

datetime
required
string

Either a date-time or an interval. Date and time expressions adhere to RFC 3339. Intervals may be bounded or half-bounded (double-dots at start or end).

Examples:

  • A date-time: "2018-02-12T23:20:50Z"
  • A bounded interval: "2018-02-12T00:00:00Z/2018-03-18T12:31:12Z"
  • Half-bounded intervals: "2018-02-12T00:00:00Z/.." or "../2018-03-18T12:31:12Z"

Only features that have temporal information that intersects the value of datetime are selected.

If a feature has multiple temporal properties, it is the decision of the server whether only a single temporal property is used to determine the extent or all relevant temporal properties.

limit
integer [ 1 .. 10000 ]
Default: 10

The optional limit parameter limits the number of items that are presented in the response document.

Only items are counted that are on the first level of the collection in the response document. Nested objects contained within the explicitly requested items shall not be counted.

Minimum = 1. Maximum = 10000. Default = 10.

leaf
Array of strings <date-time> non-empty unique [ items <date-time > ]

The leaf is provided as a sequence of monotonic increasing instants with date-time strings. Only features that have a temporal geometry and property that intersects the given date-time are selected.

The leaf operation implements pointAtTime operation which defined in the OGC Moving Feature Access. This operation returns only temporal geometry coordinates (or temporal property values) at each date-time included in the leaf parameter, using interpolated trajectory according to the interpolation property.

If the leaf parameter is provided with a bbox or (and) a datetime parameter, it will only apply to resources that intersect with a bbox or (and) a datetime parameter.

The leaf parameter shall not be used with the subTrajectory and subTemporalValue parameter. Only one of those parameters can be used in the HTTP GET operation.

subTrajectory
boolean

The subTrajectory parameter is a boolean value used with the datetime parameter. If the subTrajectory is "true",

  • the datetime must be a bounded interval, not half-bounded intervals or a date-time.
  • the datetime represents a specified time interval (new start time and new end time)
  • only features with a temporal geometry intersecting the given time interval will return.

The subTrajectory query implements subTrajectory operation, which is defined in the OGC Moving Feature Access. This operation returns only a subsequence of temporal geometry within a time interval contained in the datetime parameter, using interpolated trajectory according to the interpolation property.

If the subTrajectory parameter is provided with a bbox parameter, it will only apply to resources that intersect with a bbox parameter.

The subTrajectory parameter must not be used with the leaf parameter. Only one of these parameters can be used in the HTTP GET operation.

Responses

Response samples

Content type
application/json
{}

Add movement data into the moving feature

A user SHOULD add more movement data into a moving feature with id mFeatureId.

The request body schema SHALL follows the TemporalPrimitiveGeometry object in the OGC MF-JSON.

path Parameters
collectionId
required
string

local identifier of a collection

mFeatureId
required
string

local identifier of a moving feature

Request Body schema: application/json
type
required
string
Enum: "MovingPoint" "MovingLineString" "MovingPolygon" "MovingPointCloud"
required
Array of Array of pointGeoJSON coordinates (numbers) or Array of linestringGeoJSON coordinates (numbers) or Array of polygonGeoJSON coordinates (numbers) or Array of multipointGeoJSON coordinates (numbers) >= 2 items
datetimes
required
Array of strings >= 2 items unique
MF-JSON MotionCurve (string) or MF-JSON MotionCurve (string) (MF-JSON MotionCurve)

MF-JSON Prism encoding MotionCurve Object

object or null
Array of objects or null
(MF-JSON NamedCRS (object or null)) or (MF-JSON LinkedCRS (object or null)) (MF-JSON CRS)

MF-JSON Prism encoding CoordinateReferenceSystem Object

(MF-JSON LinkedCRS (object or null)) or (MF-JSON TRS (object or null)) (MF-JSON TRS)

The "trs" member in MovingFeature object

Responses

Request samples

Content type
application/json
{
  • "type": "MovingPoint",
  • "datetimes": [
    ],
  • "coordinates": [
    ],
  • "interpolation": "Linear",
  • "orientations": [
    ]
}

Response samples

Content type
application/json
{
  • "code": "500",
  • "description": "Server Internal Error"
}

Delete a singe temporal primitive geometry

The temporal primitive geometry with id tGeometryId SHOULD be deleted.

path Parameters
collectionId
required
string

local identifier of a collection

mFeatureId
required
string

local identifier of a moving feature

tGeometryId
required
string

local identifier of a temporal primitive geometry

Responses

Response samples

Content type
application/json
{
  • "code": "500",
  • "description": "Server Internal Error"
}

TemporalGeometryQuery

Queryable resources for the temporal primitive geometry.

Get a time-to-distance curve of a temporal primitive geometry

A user can get time-to-distance curve of a temporal primitive geometry with id tGeometryId.

When date-time query parameter is provided, this operation will return a single distance value according to the specified date and time in the data-time parameter.

path Parameters
collectionId
required
string

local identifier of a collection

mFeatureId
required
string

local identifier of a moving feature

tGeometryId
required
string

local identifier of a temporal primitive geometry

query Parameters
date-time
string <date-time>

A date-time. Date and time expressions adhere to RFC 3339.

Examples:

  • A date-time: "2018-02-12T23:20:50Z"

The date-time parameter defines the specified date and time to return the temporal value from the time-to-distance (or time-to-velocity or time-to-acceleration) curve.

Responses

Response samples

Content type
application/json
{
  • "name": "distance",
  • "type": "TReal",
  • "form": "MTR",
  • "valueSequence": [
    ]
}

Get a time-to-velocity curve of a temporal primitive geometry

A user can get time-to-velocity curve of a temporal primitive geometry with id tGeometryId.

When date-time query parameter is provided, this operation will return a single velocity value according to the specified date and time in the data-time parameter.

path Parameters
collectionId
required
string

local identifier of a collection

mFeatureId
required
string

local identifier of a moving feature

tGeometryId
required
string

local identifier of a temporal primitive geometry

query Parameters
date-time
string <date-time>

A date-time. Date and time expressions adhere to RFC 3339.

Examples:

  • A date-time: "2018-02-12T23:20:50Z"

The date-time parameter defines the specified date and time to return the temporal value from the time-to-distance (or time-to-velocity or time-to-acceleration) curve.

Responses

Response samples

Content type
application/json
{
  • "name": "velocity",
  • "type": "TReal",
  • "form": "KMH",
  • "valueSequence": [
    ]
}

Get a time-to-acceleration curve of a temporal primitive geometry

A user can get time-to-acceleration curve of a temporal primitive geometry with id tGeometryId.

When date-time query parameter is provided, this operation will return a single acceleration value according to the specified date and time in the data-time parameter.

path Parameters
collectionId
required
string

local identifier of a collection

mFeatureId
required
string

local identifier of a moving feature

tGeometryId
required
string

local identifier of a temporal primitive geometry

query Parameters
date-time
string <date-time>

A date-time. Date and time expressions adhere to RFC 3339.

Examples:

  • A date-time: "2018-02-12T23:20:50Z"

The date-time parameter defines the specified date and time to return the temporal value from the time-to-distance (or time-to-velocity or time-to-acceleration) curve.

Responses

Response samples

Content type
application/json
{
  • "name": "acceleration",
  • "type": "TReal",
  • "form": "KMH",
  • "valueSequence": [
    ]
}

TemporalProperty

The thematic change over time (temporal property), representing the variation of the value of any descriptive characteristic of a feature.

Retrieve a set of the temporal property data

A user can retrieve the static information of the temporal property data that included a single moving feature with id mFeatureId.

The static data of a temporal property is not included temporal values (property valueSequence).

Also a user can retrieve the sub sequence of the temporal information of the temporal property data for the specified time interval with subTemporalValue query parameter. In this case, temporalProperties property schema SHALL follows the TemporalProperties object in the OGC MF-JSON.

path Parameters
collectionId
required
string

local identifier of a collection

mFeatureId
required
string

local identifier of a moving feature

query Parameters
datetime
required
string

Either a date-time or an interval. Date and time expressions adhere to RFC 3339. Intervals may be bounded or half-bounded (double-dots at start or end).

Examples:

  • A date-time: "2018-02-12T23:20:50Z"
  • A bounded interval: "2018-02-12T00:00:00Z/2018-03-18T12:31:12Z"
  • Half-bounded intervals: "2018-02-12T00:00:00Z/.." or "../2018-03-18T12:31:12Z"

Only features that have temporal information that intersects the value of datetime are selected.

If a feature has multiple temporal properties, it is the decision of the server whether only a single temporal property is used to determine the extent or all relevant temporal properties.

limit
integer [ 1 .. 10000 ]
Default: 10

The optional limit parameter limits the number of items that are presented in the response document.

Only items are counted that are on the first level of the collection in the response document. Nested objects contained within the explicitly requested items shall not be counted.

Minimum = 1. Maximum = 10000. Default = 10.

subTemporalValue
boolean

The subTemporalValue parameter is a boolean value used with the datetime parameter. If the subTemporalValue is "true",

  • the datetime must be a bounded interval, not half-bounded intervals or a date-time.
  • the datetime represents a specified time interval (new start time and new end time)
  • only features with a temporal property intersecting the given time interval will return.
  • it returns only the subsequence of temporal property value within a time interval contained in the subTemporalValue parameter, using an interpolated time-to-value curve of temporal property according to the interpolation property.

The subTemporalValue parameter must not be used with the leaf parameter. Only one of these parameters can be used in the HTTP GET operation.

Responses

Response samples

Content type
application/json
{}

Add temporal property data

A user SHOULD add new temporal property data into a moving feature with id mFeatureId.

The request body schema SHALL follows the TemporalProperties object in the OGC MF-JSON.

path Parameters
collectionId
required
string

local identifier of a collection

mFeatureId
required
string

local identifier of a moving feature

Request Body schema: application/json
Array
datetimes
required
Array of strings <date-time> >= 2 items unique [ items <date-time > ]
pattern property
object or object or object

Responses

Request samples

Content type
application/json
[
  • {
    },
  • {}
]

Response samples

Content type
application/json
{
  • "code": "500",
  • "description": "Server Internal Error"
}

Retrieve a temporal property

A user can retrieve only the temporal values with a specified name tPropertyName of temporal property.

path Parameters
collectionId
required
string

local identifier of a collection

mFeatureId
required
string

local identifier of a moving feature

tPropertyName
required
string

local identifier of a temporal property

query Parameters
datetime
required
string

Either a date-time or an interval. Date and time expressions adhere to RFC 3339. Intervals may be bounded or half-bounded (double-dots at start or end).

Examples:

  • A date-time: "2018-02-12T23:20:50Z"
  • A bounded interval: "2018-02-12T00:00:00Z/2018-03-18T12:31:12Z"
  • Half-bounded intervals: "2018-02-12T00:00:00Z/.." or "../2018-03-18T12:31:12Z"

Only features that have temporal information that intersects the value of datetime are selected.

If a feature has multiple temporal properties, it is the decision of the server whether only a single temporal property is used to determine the extent or all relevant temporal properties.

leaf
Array of strings <date-time> non-empty unique [ items <date-time > ]

The leaf is provided as a sequence of monotonic increasing instants with date-time strings. Only features that have a temporal geometry and property that intersects the given date-time are selected.

The leaf operation implements pointAtTime operation which defined in the OGC Moving Feature Access. This operation returns only temporal geometry coordinates (or temporal property values) at each date-time included in the leaf parameter, using interpolated trajectory according to the interpolation property.

If the leaf parameter is provided with a bbox or (and) a datetime parameter, it will only apply to resources that intersect with a bbox or (and) a datetime parameter.

The leaf parameter shall not be used with the subTrajectory and subTemporalValue parameter. Only one of those parameters can be used in the HTTP GET operation.

subTemporalValue
boolean

The subTemporalValue parameter is a boolean value used with the datetime parameter. If the subTemporalValue is "true",

  • the datetime must be a bounded interval, not half-bounded intervals or a date-time.
  • the datetime represents a specified time interval (new start time and new end time)
  • only features with a temporal property intersecting the given time interval will return.
  • it returns only the subsequence of temporal property value within a time interval contained in the subTemporalValue parameter, using an interpolated time-to-value curve of temporal property according to the interpolation property.

The subTemporalValue parameter must not be used with the leaf parameter. Only one of these parameters can be used in the HTTP GET operation.

Responses

Response samples

Content type
application/json
{
  • "name": "speed",
  • "type": "TReal",
  • "form": "KMH",
  • "valueSequence": [
    ]
}

Add temporal primitive value data

A user SHOULD add more temporal primitive value data into a temporal property with id tPropertyName.

path Parameters
collectionId
required
string

local identifier of a collection

mFeatureId
required
string

local identifier of a moving feature

tPropertyName
required
string

local identifier of a temporal property

Request Body schema: application/json
datetimes
required
Array of strings <date-time> >= 2 items unique [ items <date-time > ]
required
number or string or boolean
interpolation
required
string
Enum: "Discrete" "Step" "Linear" "Regression"

Responses

Request samples

Content type
application/json
{
  • "datetimes": [
    ],
  • "values": [
    ],
  • "interpolation": "Linear"
}

Response samples

Content type
application/json
{
  • "code": "500",
  • "description": "Server Internal Error"
}

Delete a specified temporal property

The temporal property with id tPropertyName SHOULD be deleted.

path Parameters
collectionId
required
string

local identifier of a collection

mFeatureId
required
string

local identifier of a moving feature

tPropertyName
required
string

local identifier of a temporal property

Responses

Response samples

Content type
application/json
{
  • "code": "500",
  • "description": "Server Internal Error"
}