wcst_import - check if pyramid_bases in the ingredients file caught the error in petascope when base and pyramid member coverages have different band name

[Bang Pham Huu]

For example:

• S1_GRDH_IW_DV_VH has band Grey
• S1_GRDH_IW_DV_VH_8 has band Gray

in the ingredients file for importing S1_GRDH_IW_DV_VH_8, it has

        "tiling": "ALIGNED [0, 0:999, 0:1999]",
        "pyramid_bases": ["S1_GRDH_IW_DV_VH"]

This error should show in wcst_import:

 <ows:ExceptionText>Pyramid member coverage 'S1_GRDH_IW_DV_VH_8' does not contain band 'Grey' as in base coverage 'S1_GRDH_IW_DV_VH'.</ows:ExceptionText>

[Bang Pham Huu]

And check if databound (it should be dataBound) is invalid by json schema in wcst_import.

[Dimitar Misev]

Not particularly this case, but that in general that typos cause an error instead of being ignored.

[Bang Pham Huu]

The error from petascope is caught in wcst_import as below:

wcst_import.sh ingest.json
....

Progress: [------------------------------] 0/1 0.00% 
[2022-01-12 09:28:07] coverage 'test_pyramid' - 1/1 - file 'mean_summer_airtemp.tif' - grid domains [0:70,0:88] of size 0.01 MB; Total time to ingest file 0.11 s @ 0.09 MB/s.
Progress: [------------------------------] 0/1 0.00% Service Call: http://localhost:8080/rasdaman/admin/coverage/pyramid/add?&COVERAGEID=test_base&MEMBERS=test_pyramid&HARVESTING=False
Error Code: 404
Error Text: Failed reading response from WCS service. Detailed error: Runtime error: Failed opening connection to 'http://localhost:8080/rasdaman/admin/coverage/pyramid/add'. 

Reason: Pyramid member coverage 'test_pyramid' does not contain band 'Gray' 
as in base coverage 'test_base'.