creating the page |
Marked this version for translation |
||
| Line 1: | Line 1: | ||
<translate> | <translate> | ||
=Orientation of FITS images= | =Orientation of FITS images= <!--T:1--> | ||
<!--T:2--> | |||
The FITS standard is a container that describes how to store image data and meta-data. Professional tools, from the early age of the FITS format, like [[ds9]] (Harvard Smithsonian Center for Astrophysics), [https://heasarc.gsfc.nasa.gov/docs/software/ftools/fv/ fv] (FITS viewer from NASA), store images '''bottom-up'''. We might be tempted to say that it does not really matter, but when demosaicing or astrometry is involved, problems arise. For example, the usual RGGB Bayer pattern becomes GBRG if the image is upside-down. | The FITS standard is a container that describes how to store image data and meta-data. Professional tools, from the early age of the FITS format, like [[ds9]] (Harvard Smithsonian Center for Astrophysics), [https://heasarc.gsfc.nasa.gov/docs/software/ftools/fv/ fv] (FITS viewer from NASA), store images '''bottom-up'''. We might be tempted to say that it does not really matter, but when demosaicing or astrometry is involved, problems arise. For example, the usual RGGB Bayer pattern becomes GBRG if the image is upside-down. | ||
<!--T:3--> | |||
Nowadays, despite this, most camera drivers are writing data in the top-down order and we have to cope with it. | Nowadays, despite this, most camera drivers are writing data in the top-down order and we have to cope with it. | ||
<!--T:4--> | |||
For these reasons, we recently have introduced, together with P. Chevalley of [https://www.ap-i.net/ccdciel/en/start CCDCiel], a '''new FITS keyword'''. We encourage all data producers, INDI and ASCOM developers, to use it in order to make things easier for everybody. | For these reasons, we recently have introduced, together with P. Chevalley of [https://www.ap-i.net/ccdciel/en/start CCDCiel], a '''new FITS keyword'''. We encourage all data producers, INDI and ASCOM developers, to use it in order to make things easier for everybody. | ||
<!--T:5--> | |||
'''This keyword is''' <tt>ROWORDER</tt> of type <tt>TSTRING</tt>. It can take two values: <tt>BOTTOM-UP</tt> and <tt>TOP-DOWN</tt>. | '''This keyword is''' <tt>ROWORDER</tt> of type <tt>TSTRING</tt>. It can take two values: <tt>BOTTOM-UP</tt> and <tt>TOP-DOWN</tt>. | ||
<!--T:6--> | |||
[[Siril]] will always read and display images in the bottom-up order, however if the top-down information is specified in the keyword, then Siril will demosaic the image with the corrected pattern. | [[Siril]] will always read and display images in the bottom-up order, however if the top-down information is specified in the keyword, then Siril will demosaic the image with the corrected pattern. | ||
<!--T:7--> | |||
Why would some programs write images bottom-up in the first place? The reason is: [https://stackoverflow.com/a/8347036 mathematics do it that way]. | Why would some programs write images bottom-up in the first place? The reason is: [https://stackoverflow.com/a/8347036 mathematics do it that way]. | ||
</translate> | </translate> | ||
Revision as of 21:02, 10 July 2020
Orientation of FITS images
The FITS standard is a container that describes how to store image data and meta-data. Professional tools, from the early age of the FITS format, like ds9 (Harvard Smithsonian Center for Astrophysics), fv (FITS viewer from NASA), store images bottom-up. We might be tempted to say that it does not really matter, but when demosaicing or astrometry is involved, problems arise. For example, the usual RGGB Bayer pattern becomes GBRG if the image is upside-down.
Nowadays, despite this, most camera drivers are writing data in the top-down order and we have to cope with it.
For these reasons, we recently have introduced, together with P. Chevalley of CCDCiel, a new FITS keyword. We encourage all data producers, INDI and ASCOM developers, to use it in order to make things easier for everybody.
This keyword is ROWORDER of type TSTRING. It can take two values: BOTTOM-UP and TOP-DOWN.
Siril will always read and display images in the bottom-up order, however if the top-down information is specified in the keyword, then Siril will demosaic the image with the corrected pattern.
Why would some programs write images bottom-up in the first place? The reason is: mathematics do it that way.