Opened 17 years ago
Closed 17 years ago
#1754 closed defect (fixed)
[PATCH] Fixes display of rpf/cjga/cjgaz01/0105f033.ja1 CADRG product
| Reported by: | Even Rouault | Owned by: | Even Rouault |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.5.0 |
| Component: | GDAL_Raster | Version: | 1.4.2 |
| Severity: | normal | Keywords: | CADRG |
| Cc: | warmerdam |
Description
This is a fix for a problem with rpf/cjga/cjgaz01/0105f033.ja1 and rpf/cjga/cjgaz03/0034t0b3.ja3 CADRG products (sorry. I can't attach them). These products have the strange particularity that their block start table begins one byte after its theoretical beginning, for an unknown reason. We detect this situation when the block start offset is not a multiple of 6144 Hopefully there's something in the NITF/CADRG standard that could account for it, but I've not found it.
Attachments (1)
Change History (4)
by , 17 years ago
| Attachment: | gdal_svn_cadrg_bug1754.patch added |
|---|
comment:1 by , 17 years ago
| Component: | default → GDAL_Raster |
|---|---|
| Keywords: | CADRG added |
| Version: | unspecified → 1.4.2 |
comment:2 by , 17 years ago
| Cc: | added |
|---|---|
| Milestone: | → 1.5.0 |
| Owner: | changed from to |
Note:
See TracTickets
for help on using tickets.
Even,
I must admit this scares me a bit, but go ahead and commit in trunk. I appreciate the excellent internal documentation about the issue and the user warning. The NITF driver can easily become fragile as patchs for broken products are layered in it, but appropriate internal docs and user warnings help to keep things managable.