Opened 13 years ago
Closed 5 years ago
#3855 closed defect (wontfix)
The FITS driver sees some 2D files as being 0D.
| Reported by: | ericdavies2 | Owned by: | warmerdam |
|---|---|---|---|
| Priority: | normal | Milestone: | closed_because_of_github_migration |
| Component: | Algorithms | Version: | 1.7.2 |
| Severity: | normal | Keywords: | FITS zero-dimensional |
| Cc: |
Description
Change History (3)
comment:1 by , 13 years ago
comment:3 by , 5 years ago
| Milestone: | → closed_because_of_github_migration |
|---|---|
| Resolution: | → wontfix |
| Status: | new → closed |
This ticket has been automatically closed because Trac is no longer used for GDAL bug tracking, since the project has migrated to GitHub. If you believe this ticket is still valid, you may file it to https://github.com/OSGeo/gdal/issues if it is not already reported there.
Note:
See TracTickets
for help on using tickets.
A FITS file consists of one or more Header + Data Units (HDUs), where the first HDU is called the
Primary HDU', orPrimary Array'. In some FITS file, the primary HDU is zero dimensional, while the subsequent HDU's have valid dimensions. FITS file viewers such as fv and SAOImage D9 seem to be fine with these files. GDAL on the other hand, sees the 0D primary array and generates an error message that the file is not 2D or 3D.I can supply an example FITS file, however, it is rather large (134MB) and I don't know of any way to crop it to a smaller size.