EchoProcess + Support UOMs + Support BBOX - #580
Merged
Conversation
…e of value in double_input.
…correcting bugs for EchoProcess
…a/weaver into implement-example-process
fmigneault
force-pushed
the
echo-process+support-uom
branch
from
November 21, 2023 03:09
db0fdbd to
a304816
Compare
…y#43) and pyramid_celery==5.0.0a (sontek/pyramid_celery#102)
fmigneault
force-pushed
the
echo-process+support-uom
branch
from
December 13, 2023 01:49
43a5a95 to
60d1c08
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
weaver.formats.ContentEncodingwith handlers for common encoding manipulation from input values.weaver.processes.builtindefinitions with itsCWLrepresentation andcomplementary
OGC API - Processesreference implementation details. ThisProcesswill be automatically deployedat
APIstartup, and is employed to validate multiple parsing combinations of execution I/O values and encodings(fixes Implement example process #379).
OGCBoundingBoxdefinition (bboxandcrsfields) asProcessexecution input valuewith appropriate schema validation (fixes Support of BoundingBox I/O #51).
Unit of Measure(UoM) definition (measurementanduomfields) asProcessexecutioninput value with appropriate schema validation (fixes`Support I/O literal with unit of measure #430).
create_metalinkutility function to facilitate generation of a.meta4or.metalinkfile definitionfrom a list of file link references (relates to How to handle "multiple output" #25).
Fixes
weaver.wps_restapi.swagger_definitions.ExecuteInputValuesdeserialization that sometimes silently droppedinvalid
JSON-formatted inputs that did not fulfill schema validation. This was caused by a side effect regardinghow
weaver.wps_restapi.colander_extras.VariableSchemaNodehandled "unknown"JSONpropertiesfrom submittedcontent. In cases where required
Processinputs were causing the invalid schema,Jobexecution would be abortedand the error would be reported due to "missing" inputs. However, if the
JSONfailing schema validation happened tobe nested under an optional input definition, the
Jobexecution could have resumed silently by omitting thisinput's value propagation to the downstream
CWL,WPSorOGC API - Processesimplementation, which could makeit use an alternative default value than the real input that was submitted for the
Job.colander.Invaliderror when a schema validation failed, inorder to better represent deeply nested schema using multiple
oneOf,anyOf,allOfschema nodes.Using
colander.Invalid.asdict, each dictionary key now properly indicates the specific path of sub-nodes withtheir relevant schema validation error.
variableschema node names to provide a{SchemaName}<{VariableName}>representation, such that it can bemore easily identified. Schema nodes with a
variable(i.e.: schema underadditionalProperties) previously onlyindicated
{VariableName}, which made it complicated to follow reference schema classes that formed the error path.Each of the evaluated fields against each possible
variableschema will now report their corresponding nestedschema validation error as
{SchemaName}<{VariableName}>({field})such that results can be understood.href) dropping aschemaURL reference if provided explicitly.This parameter now remains within the produced content passed to the
Job, and forwarded to a remoteProcessifapplicable, but no further schema validation is accomplished with the value in
schemafor the moment.ContentType.IMAGE_OGC_GEOTIFFusing invalid media-type name (missingiinimage).Jobinput validation stripping additional parameters from provided Media-Type, potentially causing mismatchingContent-Type validation against the corresponding
Processdescription inputs. Types should now match exactly theoriginal
Processdefinition, including any additional parameters and sub-types.anyOfschema raisingcolander.Invalideven when the property was marked as optionalusing
missing=colander.drop.$schemaofOGCnameReferenceTypebeing reported under everydataTypeofliteralDataDomainsforliteral
I/OofProcessdescriptions. The reference is not only included in theOpenAPIdefinition as intended.References
pywps==4.6.0)owslib==0.30.0)pywpsandowslibupdates.EchoProcessfrom OGC API Processes in CWL #541To Do