Retrieves the supported mathematical operations
get
/spatialviewer/api/v1/raster/rasterOperations
Request
Query Parameters
-
complex: string
Filter the operations that are complex. Only works if the passed value is true. It is false by default.
-
dataTypes: string
Filter the operations that supports the passed data types. Supports multiple values separated by commas.
-
processTypes: string
Filter the operations that supports the passed process types. Supports multiple values separated by commas.
-
sort: string
Sort the operations by name if the passed value is descendant. It is ascendant by default.
Response
Supported Media Types
- application/json
200 Response
successful request
Root Schema : RasterProcessOperationsSuccessResponse
Type:
Show Source
object
-
o:successCode(optional):
string
Success code.Example:
SVR-00203
-
response(optional):
object response
Response details
-
status(optional):
string
success or errorExample:
success
-
title(optional):
string
Response descriptionExample:
Raster process configuration loaded correctly.
Nested Schema : response
Type:
object
Response details
Show Source
-
operation(optional):
object operation
Additional Properties Allowed: additionalPropertiesIndividual operation details
Nested Schema : operation
Type:
object
Additional Properties Allowed
Show Source
Individual operation details
Show Source
-
complex:
boolean
Specifies whether the operation is a complex operationExample:
true
-
enabled:
boolean
Specifies whether the operation is activeExample:
true
-
name:
string
Operation NameExample:
Local Divition
Nested Schema : additionalProperties
Type:
Show Source
object
-
config(optional):
array config
Operation configuration details
-
operators(optional):
array operators
-
params(optional):
array params
Parameters details array
-
supportedDataTypes(optional):
array supportedDataTypes
Specifies the data types of rasters in which this operation can be applied
-
supportedProcessTypes(optional):
array supportedProcessTypes
Specifies the types of process in which this operation can be applied
Nested Schema : operators
Type:
Show Source
array
-
Array of:
string
Example:
[ ">", "<", "<=", ">=", "!=", "=" ]
Nested Schema : supportedDataTypes
Type:
array
Specifies the data types of rasters in which this operation can be applied
Show Source
-
Array of:
number
Example:
[ 2, 3, 4, 5, 6, 7 ]
Nested Schema : supportedProcessTypes
Type:
array
Specifies the types of process in which this operation can be applied
Show Source
-
Array of:
number
Example:
[ 1, 2 ]
Nested Schema : items
Type:
Show Source
object
-
defaultValue(optional):
string
Default value for the parameter.Example:
0
-
index:
string
Index of the configuration details from the source array in which the details of this parameter are set. Wilcards like * can be read here, that indicates that the parameter is a selector.Example:
*
-
source:
string
Indicates the source property (an array) in which the details of the parameter are set. This property is an attribute of the operation.Example:
operators
Nested Schema : items
Type:
Show Source
object
-
id:
string
Unique identifier for the parameter.Example:
operand
-
name:
string
Informative name of the parameter.Example:
Operator
-
required:
boolean
Identify the parameter as required or optional.Example:
true
-
type:
string
Type of the parameter. Util for validation.Example:
int
404 Response
raster operations details not found in server
Root Schema : RasterProcessOperationsNotFoundResponse
Type:
Show Source
object
-
detail(optional):
string
Response details informationExample:
Raster operations configuration could not be located in server
-
o:errorCode(optional):
string
Success code.Example:
SVR-E0008
-
status(optional):
string
success or errorExample:
error
-
title(optional):
string
Response descriptionExample:
Raster operations configuration could not be located in server.
406 Response
provided parameters are not correct
Root Schema : RasterProcessOperationsInvalidParametersResponse
Type:
Show Source
object
-
detail(optional):
string
Response details information like valid formatsExample:
Invalid parameters. Supported options for raster bits types: 1: Byte, 2: Unsigned int 16 bits, 3: Int 16 bits, 4: Unsigned int 32 bits, 5: Int 32 bits, 6: Float 32 bits, 7: Float 64 bits
-
o:errorCode(optional):
string
Success code.Example:
SVR-E0010
-
status(optional):
string
success or errorExample:
error
-
title(optional):
string
Response descriptionExample:
Invalid parameters.
417 Response
raster operations details are corrupt in server
Root Schema : RasterProcessOperationsCorruptFileResponse
Type:
Show Source
object
-
detail(optional):
string
Response details informationExample:
Raster operations configuration can not be parsed
-
o:errorCode(optional):
string
Success code.Example:
SVR-E0009
-
status(optional):
string
success or errorExample:
error
-
title(optional):
string
Response descriptionExample:
Raster operations configuration can not be parsed
500 Response
unknow error
Root Schema : RasterErrorGenericResponse
Type:
Show Source
object
-
detail(optional):
string
Response details informationExample:
Unknow error
-
o:errorCode(optional):
string
Success code.Example:
SVR-E0001
-
status(optional):
string
success or errorExample:
error
-
title(optional):
string
Response descriptionExample:
Error while processing REST request.
Examples
Retrieves the supported mathematical operations that can be applied to a raster process.
The following example shows how to get some of the mathematical operations details by submitting a GET request on the REST resource using cURL with some parameter values to filter and sort the operations.
curl -X GET "http://localhost:8045/spatialviewer/api/v1/raster/rasterOperations?dataTypes=1&complex=false&sort=descendant" -H "accept: application/json"
Example of Response Header
Example of Response Header
HTTP/1.1 200 OK Date: Wed, 22 Aug 2018 21:41:26 GMT Content-Type: application/json Access-Control-Allow-Origin: * Access-Control-Allow-Credentials: true Access-Control-Allow-Methods: GET, POST, DELETE, PUT Access-Control-Allow-Headers: Content-Type, Accept Transfer-Encoding: chunked
Example of the Response Body
The following example shows the contents of the response body in JSON format
{ "status" : "success", "title" : "Raster process configuration loaded correctly.", "o:successCode" : "SVR-00203", "response" : { "localnot" : { "name" : "Local Not", "enabled" : true, "complex" : false, "supportedDataTypes" : [ 1, 2, 3, 4, 5 ] } } }