Thanks, you were right on both counts.
1. Code change in nitfimage.c fixed the ERDAS/Global Mapper error.
2. To get the improved accuracy I did have to specify the GEOPSB TRE as
well.
To make this work in mapserver I'll need to do something like the following,
but that means the OUTPUTFORMAT will
> EXAMPLE:
>
> If I don't create the GEOLOB, then IGEOLO is written as follows.
> IGEOLO 258041N0665839E250841N0665915E250807N0665915E250807N0665839E
>
> If I create a GEOLOB, then IGEOLO is written as follows.
> IGEOLO+25.145+066.977+25.145+066.987+25.135+066.987+25.135+066.977
>
Curr
Even thanks for all your help. With the correct syntax the NITF generation
does complete without error. But it seems that writing GEOLOB also changes
the way IGEOLO is written.
EXAMPLE:
If I don't create the GEOLOB, then IGEOLO is written as follows.
IGEOLO 258041N0665839E250841N0665915E250807
On 09/24/2010 03:48 PM, Oyvind Idland wrote:
Hi,
i am fiddling around a bit with GDAL. I can successfully load GeoTIFF
files etc, but when trying with the WMS
driver, something strange happens:
Opening the example frmt_wms_onearth_global_mosaic.xml works fine. I
query for bands, and get 3.
W
