"type" of an APEx algorithm OGC record #65
Labels
bug
Something isn't working
help wanted
Extra attention is needed
question
Further information is requested
from ESA-EarthCODE/EarthCODE#5
There is a conflict between the current constraint/convention to use "apex_algorithm" as
properties.type
in algorithm_catalog OGC records and EarthCODE expectationse.g.:
apex_algorithms/algorithm_catalog/max_ndvi_composite.json
Lines 1 to 11 in 7c32e3d
this is currently enforced in CI as well by
apex_algorithms/qa/unittests/tests/test_algorithm_catalog.py
Line 26 in 7c32e3d
However, as discussed in ESA-EarthCODE/EarthCODE#5 , the EarthCODE tooling/schemas expect an enum
['dataset', 'service', 'process', 'workflow']
instead of "apex_algorithm"Should we align here with EarthCODE? Note that it's currently not very clear why the enum constraint is in place there in the first place -> EOEPCA/metadata-profile#1
And should we use a different field (or approach) than
properties.type
to indicate that this is an APEx algorithm OGC recordThe text was updated successfully, but these errors were encountered: