8 | | - Add NITF_ICORDS to the dataset's metadata. |
9 | | - Add all ICHIPB fields to the metadata. |
10 | | - Read RPC00A exactly as RPC00B is read. (I've never been able to see any |
11 | | difference between the A and B versions. The gov't's |
12 | | STDI-0002-version-2.1-16-Nov-2000.pdf document says they differ in some |
13 | | coefficient ordering, but comparing with STDI-0002-version-1.0-25-Aug-1998.pdf, |
14 | | I see no difference at all.) |
| 6 | $ Add NITF_ICORDS to the dataset's metadata. |
| 7 | $ Add all ICHIPB fields to the metadata. |
| 8 | $ Read RPC00A exactly as RPC00B is read. (I've never been able to see any difference between the A and B versions. The gov't's |
| 9 | STDI-0002-version-2.1-16-Nov-2000.pdf document says they differ in some coefficient ordering, but comparing with STDI-0002-version-1.0-25-Aug-1998.pdf, I see no difference at all.) |
25 | | - The NITF_MIN/MAX_LAT/LONG metadata items look wrong. The RPC region usually |
26 | | straddles LAT/LONG_OFFSET by LAT/LONG_SCALE. However, the metadata items begin |
27 | | at LAT/LONG_OFFSET and extend from there by 2*LAT/LONG_OFFSET |
28 | | - The RPC projection code doesn't know about ICHIPB and so will incorrectly |
29 | | project points for a NITF file with ICHIPB. |
30 | | - The ERR_BIAS and ERR_RAND RPC00B fields aren't put in the dataset's metadata. |
| 17 | * The NITF_MIN/MAX_LAT/LONG metadata items look wrong. The RPC region usually straddles LAT/LONG_OFFSET by LAT/LONG_SCALE. However, the metadata items begin at LAT/LONG_OFFSET and extend from there by 2*LAT/LONG_OFFSET |
| 18 | * The RPC projection code doesn't know about ICHIPB and so will incorrectly project points for a NITF file with ICHIPB. |
| 19 | * The ERR_BIAS and ERR_RAND RPC00B fields aren't put in the dataset's metadata. |