Custom Query (2764 matches)

• WCS GetCapabilites should support optional sections parameter which allows to get the list of requested sections from GetCapabilities result. The valid values are (choose one or multiple values):

  sections=ServiceMetadata,ServiceIdentification,ServiceProvider,OperationsMetadata,Contents,Languages
  

If sections=All it is equivalent to sections parameter is not specified.

• Currently, petascope requires that XY axes label for subsettingCRS must match with the ones specified in the requesting coverage.

e.g. this coverage has EPSG:3857 as nativeCRS and the axis labels are X and Y, then this request below returns error, because Lat and Long don't exist in test_wms_3857.

http://localhost:8080/rasdaman/ows?service=WCS&version=2.0.1&request=GetCoverage&coverageid=test_wms_3857&subset=Lat(-35,-25)&subset=Long(120,135)&format=image/png&subsettingCRs=http://www.opengis.net/def/crs/EPSG/0/4326

If Lat and Long are replaced by the existing axis labels X and Y in coverage test_wms_3857 then it will work, but this is not correct because X and Y have uom meters, while Lat and Long have uom degrees.

Hence, petascope needs to support the correct spatial axis labels specified in the geo CRS besides the existing coverage's spatial axis labels for backwards compatibility.

I suggest to add an --analyze option, which will not run any import but do the following:

• same as "mock": true, it will print mock requests
• calculate optimal tiling and print it

• in future: print hints about compression, data preprocessing for pyramids, etc.

for example:

              "axes": {
                        "time": {
                            "min": "2015",
                            "irregular": true,
                            "dataBound": false,
                            "areasOfValidity": [
                                {
                                    "start": "2015",
                                    "end": "2025"
                                }
                            ]
                        },

here time is AnsiDate axis and "min": "2015", should be converted to "2015-01-01" implicitly instead of 2015 seconds and set the min value to time("1970-01-01T00:33:35 00:00").

Currently, one has to do that manually in the ingredients file with:

                       "time": {
                            "statements": "from datetime import datetime",                        
                            "min": "datetime.strptime('2015', '%Y').isoformat()",