Custom Query (2765 matches)

Currently, it failed with unknown error

insert into nil_value (reason, value, nil_value_id) values (?, ?, ?) [42122-200]

with these settings in petascope.properties

spring.datasource.url=jdbc:h2:file:///home/rasdaman/petascopedb.db
spring.datasource.username=petauser
spring.datasource.password=petapasswd
spring.datasource.jdbc_jar_path=/home/rasdaman/h2-1.4.200.jar

Petascope should still start even if a coverage's set type doesn't exist in rasdaman. It should not show this coverage in GetCapabilities and should log in petascope.log, for example:

Set type 'test_mr_TO_BE_DELETED_Set' does not exist in rasdaman, but is required for coverage 'test_mr_TO_BE_DELETED'. Hint: create the missing set type, or delete the coverage in petascope with a DeleteCoverage request.

Currently, when creating / adding new pyramid member, it is always pushed to the top of the pyramid list.

It is fine as this is the common way to build pyramid from high → low resolutions. (e.g. Sentinel 2: 10m, 20m, then 60m)

However, if one wants to add a pyramid member in the middle of the pyramid, this is not correct (e.g. Sentinel 2: 10m, 60m, then 20m).