Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#341 closed defect (fixed)

Petascope return wrong domainSet

Reported by: barboni@… Owned by: pcampalani
Priority: critical Milestone: 8.4.1
Component: petascope Version: 8.4
Keywords: Cc: mantovani@…
Complexity: Easy


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

The collection sdom:

A wcs2 query with subset T larger than raster sdom:

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


<Envelope srsName="" axisLabels="x y t" uomLabels="" srsDimension="3">

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



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


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



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


<axisLabels>x y t</axisLabels>


<gml:Point gml:id="MACC_OMAOD550_4326_1125-origin" srsName="">

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


<gml:offsetVector srsName="">1.125 0 0</gml:offsetVector>
<gml:offsetVector srsName="">0 1.125 0</gml:offsetVector>
<gml:offsetVector srsName="">0 0 1.0</gml:offsetVector>


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.



# rpm -qa | grep rasdaman

Change History (7)

comment:1 Changed 4 years ago by abeccati

  • Complexity changed from Medium to Easy
  • Milestone set to 8.4.1
  • Owner changed from abeccati to pcampalani
  • Priority changed from major to critical
  • Status changed from new to assigned

Thanks for reporting Damiano, indeed it looks like a wrong domainset bounds.

comment:2 Changed 4 years ago by pcampalani

Hi there,
a patch is submitted for this error:

Name	Piero Campalani <>
Subject	[PATCH] Fix wrong grid envelope when axis is subset via grid coordinates (ticket #341).
Date	Mon, 8 Apr 2013 18:54:06 +0200

I would leave this ticket open anyway, because there is still an issue (which I believe is there from year 0) when subsetting via CRS:1 (grid) coordinates: the grid coordinates are not back-transformed to domain coordinates so the the domainSet is ok while the boundedBy gets broken.




    <Envelope (...)>
      <lowerCorner>0.0 25.0 **10.0**</lowerCorner> WRONG Y BOUND
      <upperCorner>5.0 75.0 **15.0**</upperCorner> WRONG Y BOUND

    <RectifiedGrid (...)>
          <low>0 0 10</low>
          <high>5 100 15</high>

comment:3 Changed 4 years ago by pcampalani

  • Summary changed from Petascope return wrong domainSet to Petascope returns wrong bounds with CRS:1 subsets

comment:4 Changed 4 years ago by abeccati

I think if this other aspect does not get fixed in the patch its probably better to factor it out to a separated ticket, unless we can have also the second patch in short time. So we can release the patch version 8.4.1 solving the specific user need (and closing this ticket accordingly), while deferring the other issue.


comment:5 Changed 4 years ago by pcampalani

  • Summary changed from Petascope returns wrong bounds with CRS:1 subsets to Petascope return wrong domainSet

comment:6 Changed 4 years ago by abeccati

  • Resolution set to fixed
  • Status changed from assigned to closed

Fixed by Piero, giving now the expected output for the t axis of [1200919:1202376]

comment:7 Changed 4 years ago by pcampalani

Fixed in changeset:eff4fa8.

Note: See TracTickets for help on using tickets.