Small improvements for #46 (Type definitions for custom backend respo…

…nse types).
Open-EO · Jun 1, 2018 · 9fe688b · 9fe688b
1 parent 72f70b7
commit 9fe688b
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 2 deletions.
diff --git a/docs/docs/errors.md b/docs/docs/errors.md
@@ -127,6 +127,7 @@ None yet.
 | 3001              |                                      | Output format not supported.                                 | 400              |
 | 3002              |                                      | Output format argument **X** is not supported.               | 400              |
 | 3003              |                                      | Invalid value **Y** for the output format argument **X** specified. | 400              |
+| 3004              |                                      | Data can't be transformed into the requested output format.  | 400              |
 
 ### Authorization, user content and billing (401-403, 4xxx)
 

diff --git a/openapi.json b/openapi.json
@@ -215,7 +215,7 @@
     "/output_formats": {
       "get": {
         "summary": "Returns output formats supported by the back-end.",
-        "description": "The request will ask the back-end for supported output formats, e.g. PNG, GTiff and time series, and its default output format. The response is an object of the default and all available output formats and their options. This does not include the supported web services.\n**Note**: Whenever available, the output format names and options should be fully aligned with the GDAL codes, see http://www.gdal.org/formats_list.html. Some file formats not available through GDAL might be defined centrally for openEO in the documentation. Custom output formats or options can be defined wherever needed. Not all output format options supported by GDAL need to be supported.",
+        "description": "The request will ask the back-end for supported output formats, e.g.\nPNG, GTiff and JSON, and its default output format. The response\nis an object of the default and all available output formats and their\noptions. This does not include the supported web services.\n\n**Note**: Output format names and options SHOULD be fully aligned with the GDAL codes if available, see\n[GDAL Raster Formats](http://www.gdal.org/formats_list.html) and [OGR Vector Formats](http://www.gdal.org/ogr_formats.html). It is OPTIONAL to support all output format options supported by GDAL. Some file formats not available through GDAL could be defined centrally for openEO. Custom output formats or options MAY be defined, but it is recommended to stick to GDAL to increase interoperability.\n  A `JSON` file format MAY be supported by back-ends to allow outputting data that doesn't fit into raster or vector file formats. ",
         "tags": [
           "Capabilities",
           "Job Management"
@@ -261,7 +261,8 @@
                         },
                         "PNG": {
                           "worldfile": "Force the generation of an associated ESRI world file."
-                        }
+                        },
+                        "JSON": {}
                       }
                     }
                   }