The as_bytes input defined in the process metadata for the hello-world processor defines its own type as 'bool', as seen at:
|
'as_bytes': { |
|
'title': 'As bytes', |
|
'description': 'Whether to force return as bytes', |
|
'schema': { |
|
'type': 'bool', |
|
'default': False |
|
}, |
|
'minOccurs': 0, |
|
'maxOccurs': 1, |
|
'keywords': ['as_bytes'] |
|
}, |
'bool' does not refer to a valid type in JSON Schema. The type should be declared as 'boolean' instead.
I'm not sure why but the published OGC API Processes standard does not refer to JSON Schema directly, but rather seems to duplicate the definitions in the standard. Regardless, it also specifies a value of 'boolean' instead of 'bool', as seen at:
https://schemas.opengis.net/ogcapi/processes/part1/1.0/openapi/schemas/schema.yaml
The
as_bytesinput defined in the process metadata for thehello-worldprocessor defines its owntypeas'bool', as seen at:pygeoapi/pygeoapi/process/hello_world.py
Lines 87 to 97 in 4794363
'bool'does not refer to a valid type in JSON Schema. The type should be declared as'boolean'instead.I'm not sure why but the published OGC API Processes standard does not refer to JSON Schema directly, but rather seems to duplicate the definitions in the standard. Regardless, it also specifies a value of
'boolean'instead of'bool', as seen at:https://schemas.opengis.net/ogcapi/processes/part1/1.0/openapi/schemas/schema.yaml