Changes between Version 9 and Version 10 of PetascopeSubsets


Ignore:
Timestamp:
Mar 13, 2014, 2:31:57 PM (10 years ago)
Author:
Piero Campalani
Comment:

update wiki after 700-of-death ticket

Legend:

Unmodified
Added
Removed
Modified

  • PetascopeSubsets

    v9 v10  
    2020
    2121In the image, it is assumed that the first grid axis (`+1`) is the horizontal axis, while the second (`+2`) is the vertical axis; the grid starting point is the full diamond.
    22 Sticking to the linear sequence rule was the best choice for `rasdaman` since that is the same rule which `rasdaman` itself uses to print the values of cells in an collection/marray.
     22`rasdaman` uses its own grid function when listing cell values, ''linearly'' spanning the ''outer'' dimensions first, then proceeding to the innermost ones. To make it clearer, this means ''column-major'' listing order in the 2D case.
     23
     24In order to have a coeherent GML output, a mapping coverage function is then declared. This (see #700) can look like this in a 3D hypothetical response:
     25
     26{{{
     27<gml:coverageFunction>
     28  <gml:GridFunction>
     29    <gml:sequenceRule axisOrder="+3 +2 +1">Linear</gml:sequenceRule>
     30    <gml:startPoint>0 0 0</gml:startPoint>
     31  </gml:GridFunction>
     32</gml:coverageFunction>
     33}}}
    2334
    2435Coming back to the origin question on where to put the origin of our grid coverages, we have to make it coincide to what the starting value represents in `rasdaman`, the marray origin.