pixel cutouts (instead of world coordinates) on all axes are missing

[Bonnarel]

Considered for version 1.0 but delayed to stay simple (due to syntax problems)
Asked by CASDA , others
Ranges can be given by SODA service descriptor or computed from ObsCore 

Which syntax ?

[gpdf]

Existing (non-SODA) image services at IRSA are able to return cutouts with sizes defined in pixels as well as in angular units:
https://irsa.ipac.caltech.edu/ibe/cutouts.html

The prototype Rubin Observatory/LSST image cutout services also provide an option of performing cutouts by pixel, through a non-standard parameter to SODA. I would very much like to have that be a standards-based operation. We would welcome discussing this in DAL between now and the next InterOp.

Additionally, cutout services (on spectral cubes) will be of substantial interest to SPHEREx (at IRSA) in the 2023+ era, and that project would also welcome the opportunity to look for standards-based interfaces.

[pdowler]

CADC also supports FITS extension and sub-array extraction (pixel cutout) using an API derived from cfitsio syntax. I think a standard could be pulled out, but I am less certain that different formats (eg FITS vs HDF5) could easily/simply be addressed with the same request input.

[Bonnarel]

CADC also supports FITS extension and sub-array extraction (pixel cutout) using an API derived from cfitsio syntax. I think a standard could be pulled out, but I am less certain that different formats (eg FITS vs HDF5) could easily/simply be addressed with the same request input.

Images all have pixels ranges. Why should HDF5 not fot with a cfitsio syntax ? Can you explain ?

[Bonnarel]

Within the scope of the SRCnet project our INAF colleagues are planning to implement special cutouts extracting one pixel among n in their soda service. I modify PR#16 accordingly