RasUtil methods don't handle result of metadata queries

[Dirk Daems]

The method executeWcpsQuery of the RasUtil class fails when executing a WCPS query which only retrieves metadata. E.g. in case of query:

for c in (Biopar_Africa_LAI) return crsSet(c)

It will try to execute RASQL query

t:CRS:1, x:http://www.opengis.net/def/crs/EPSG/0/4326 CRS:1, y:http://www.opengis.net/def/crs/EPSG/0/4326 CRS:1

which of course fails.

The PetascopeInterface.handleProcessCoverages(..) method handles this, and this handling should be factored into RasUtil.

[Dimitar Misev]

Perhaps it has something to do with the fact that your data is 3D? Here it executes fine

for c in (mean_summer_airtemp) return crsSet(c)

and I get result

x:http://www.opengis.net/def/crs/EPSG/0/4326 CRS:1, y:http://www.opengis.net/def/crs/EPSG/0/4326 CRS:1

[Dirk Daems]

I tried a 2D coverage, but the error remains. Did you also try using the RasUtil executeWcpsQuery method? When I execute it using the Petascope servlets, the queries also run fine.

[Dimitar Misev]

Ah ok, I didn't notice it's specific to RasUtil. I'm just guessing you didn't initialize something, can you post your code?

[Dimitar Misev]

Did you initialize ConfigManager with

ConfigManager.getInstance(String confDir)

where confDir is absolute path to the dir containing petascope.properties and log4j.properties?

[Dirk Daems]

Yes, the ConfigManager is initialized. See attached file. The query which is commented executes normally.

[Dimitar Misev]

Have a look at PetascopeInterface.handleProcessCoverages the handling is somewhat more involved in order to take care of metadata results. Let me know if this fixes your problem.

[Dirk Daems]

Indeed, the implementation of the PetascopeInterface.handleProcessCoverages takes care of WCPS queries which don't actually end up in a RASQL query. However, a working utility method / API to execute WCPS queries would be useful.

[Dimitar Misev]

Yes definitely, I'll change the ticket subject to match this.