Investing the bug here: cds-astro/aladin-lite#120 I tested exporting the current view of aladin lite in FITS using hips2fits and setting the CTYPE1 to AIR. Then by loading that FITS file again in aladin lite I see the view does not match with the file plotted. See below:
When I do that process for other CTYPE1 (SIN, AIT, ZEA, CAR, ... as checked by @ManonMarchand in cds-astro/aladin-lite#120) the survey plotted matches (by eye, it does not mean it matches pixel perfect) with the fits file. So this lead me to open an issue here for the AIRY projection.
Is there a difference of impl between mapproj and wcslib (used by hips2fits) for the airy projection ? Here is the code of the projection, they seem to operate on sky coo instead of cartesian coo: https://github.com/astropy/astropy/blob/main/cextern/wcslib/C/prj.c#L3076
Thanks
Investing the bug here: cds-astro/aladin-lite#120 I tested exporting the current view of aladin lite in FITS using hips2fits and setting the CTYPE1 to AIR. Then by loading that FITS file again in aladin lite I see the view does not match with the file plotted. See below:
When I do that process for other CTYPE1 (SIN, AIT, ZEA, CAR, ... as checked by @ManonMarchand in cds-astro/aladin-lite#120) the survey plotted matches (by eye, it does not mean it matches pixel perfect) with the fits file. So this lead me to open an issue here for the AIRY projection.
Is there a difference of impl between mapproj and wcslib (used by hips2fits) for the airy projection ? Here is the code of the projection, they seem to operate on sky coo instead of cartesian coo: https://github.com/astropy/astropy/blob/main/cextern/wcslib/C/prj.c#L3076
Thanks