Update features

Update features. This is a replace operation, i.e., all feature properties have to be sent in the request body even if their values do not change.

Securityoidc-token or oauth2-client-credentials or oauth2-open-industrial-data or oauth2-auth-code
Request
path Parameters
featureTypeExternalId
required
string <= 32 characters ^[A-Za-z][A-Za-z0-9_]{0,31}$

External Id of the feature type provided by client. Must be unique among all feature type external ids within a CDF project.

Example: ocean_measures
Request Body schema: application/json
required

List of features to update.

allowCrsTransformation
boolean (GeospatialAllowCrsTransformation)

Optional parameter indicating if input geometry properties should be transformed into the respective Coordinate Reference Systems defined in the feature type specification. If the parameter is true, then input geometries will be transformed when the input and output Coordinate Reference Systems differ. When it is false, then requests with geometries in Coordinate Reference System different from the ones defined in the feature type will result in bad request response code. Transformations apply to property geometries in case of create and update feature, as well as to geometries in spatial filters in search endpoints.

required
Array of objects (GeospatialFeatureSpec) [ 1 .. 1000 ] items
Responses
200

Feature list response.

400

Failed request reponse.

post/geospatial/featuretypes/{featureTypeExternalId}/features/update
Request samples
application/json
{
  • "items": [
    • {
      },
    • {
      }
    ]
}
Response samples
application/json
{
  • "items": [
    • {
      },
    • {
      }
    ]
}
➔ Next to Seismic