Custom Query (2765 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (52 - 54 of 2765)

Ticket Owner Reporter Resolution Summary
#335 Dimitar Misev ungarj fixed Coverage iterator not translated properly to rasql on WCPS trimmings
Description

Just found out that some of the WCPS queries in our WCPS Tutorial cause an error now though having worked in earlier versions.

It seems after some testing the last version the queries worked was rasdaman 8.3.1-3.

Not sure whether it's relevant but the only queries affected (just tested our example queries though) are the ones with 1D output.

catalina.out indicates the "Specified domain does not intersect with spatial domain of MDD."

Example Query:

for c in (FSC_Scandinavia)
  return
    encode(
      coverage temp
        over
        $pt t(150190:150200)
      values (count(c[t($pt)]=30)) / (count(c[t($pt)]!=0)) * 100,
      "csv"
    )

The two files attached contain the tomcat output of the same query running with rasdaman 8.3.1-3 and 8.4.0-rc2.2.

Maybe I'm missing a schema or a syntax change. Do you have any idea what could be wrong here?

Thanks, Joachim

#341 Piero Campalani barboni@… fixed Petascope return wrong domainSet
Description

In my opinion, with a wcs2 request, petascope return an invalid domainSet for the temporal axis


The collection sdom: [-159:160,-80:80,1200919:1202376]


A wcs2 query with subset T larger than raster sdom: &subsetT=t,CRS:1(1199944,1203840)


The <boundedBy> Tag in the wcs2 response(this is CORRECT !!!):

<boundedBy>

<Envelope srsName="http://www.opengis.net/def/crs/EPSG/0/4326" axisLabels="x y t" uomLabels="" srsDimension="3">

<lowerCorner>53.553381 32.217016 1200919.0</lowerCorner> <upperCorner>53.553381 32.217016 1202376.0</upperCorner>

</Envelope>

</boundedBy>


The <domainSet> Tag in the wcs2 response(for me this is WRONG):

<domainSet>

<RectifiedGrid dimension="3" gml:id="MACC_OMAOD550_4326_1125-grid">

<limits>

<GridEnvelope>

<low>47 -29 1199944</low> <high>47 -29 1203840</high>

</GridEnvelope>

</limits> <axisLabels>x y t</axisLabels>

<gml:origin>

<gml:Point gml:id="MACC_OMAOD550_4326_1125-origin" srsName="http://www.opengis.net/def/crs/EPSG/0/4326">

<gml:pos>53.553381 32.217016 1200919.0</gml:pos>

</gml:Point>

</gml:origin> <gml:offsetVector srsName="http://www.opengis.net/def/crs/EPSG/0/4326">1.125 0 0</gml:offsetVector> <gml:offsetVector srsName="http://www.opengis.net/def/crs/EPSG/0/4326">0 1.125 0</gml:offsetVector> <gml:offsetVector srsName="http://www.opengis.net/def/crs/EPSG/0/4326">0 0 1.0</gml:offsetVector> </RectifiedGrid>

</domainSet>


In my opinion, in <GridEnvelope>, the expected output for the t axis is [1200919:1202376] but petascope return [1199944:1203840] that is exactly the requested subset.

My assumption is based on the old versions of petascope that filled the <GridEnvelope> tag in this way.

Ciao

Damiano

# rpm -qa | grep rasdaman rasdaman-petascope-8.4.0-1.el6.noarch rasdaman-8.4.0-1.el6.x86_64

#343 Piero Campalani barboni@… fixed WCPS - getMetaDataExpr functions problems
Description

Functions of the getMetaDataExpr set don't work

for c in (MACC_OMAOD550_4326_1125) return imageCrsDomain©

An error has occured Error: Invalid coverage Expression, next node: imageCrsDomain


for c in (MACC_OMAOD550_4326_1125) return identifier©

An error has occured Error: Invalid coverage Expression, next node: identifier


for c in (MACC_OMAOD550_4326_1125) return crsSet©

An error has occured Error: Invalid coverage Expression, next node: crsSet


..etc…


Damiano

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.