[gdal-dev] GDAL: How to create one NITF image from CIB CD

Rydzak, Carol-P28503 Carol.Rydzak at gdc4s.com
Thu Sep 3 22:25:59 EDT 2009


Hi.  
Thank you for getting back to me on this!
Yes, I am using the 1.6.0 version of GDAL.  

I did what you suggested and it gives me a bus error when I run the
gdalinfo command on the a.toc file.  Do you recall what the problems
were with the CIB data that you heard about?  I have a 1 meter, 5 meter
and 10 meter data sets that I tried and I got a bus error on all of
them.  Any other ideas?

Thanks,

Carol
-----Original Message-----
From: Even Rouault [mailto:even.rouault at mines-paris.org] 
Sent: Thursday, September 03, 2009 12:50 PM
To: Rydzak, Carol-P28503
Cc: gdal-dev at lists.osgeo.org
Subject: Re: [gdal-dev] GDAL: How to create one NITF image from CIB CD

Selon "Rydzak, Carol-P28503" <Carol.Rydzak at gdc4s.com>:

I assume you are using a recent enough GDAL version (>= 1.5.0) that has
the RPFTOC driver. If so, gdalinfo on the a.toc should return a list of
subdatasets (at least one). You can then select one and translate it to
a GeoTIFF. It will mosaic all the underlying NITF tiles. See
http://gdal.org/frmt_various.html#RPFTOC for more info.

Someone recently reported problems with CIB but I've not heard any news
since then. The driver was tested against CADRG datasets but should
theoritically work with CIB too.

> I am trying to use GDAL utilities (on a Solaris 10 system) against CIB

> files (from a CD) to convert them to a single NITF image.
>
> When I run gdal_translate, it doesn't seem to accept the a.toc, but it

> does create a one-to-one nitf image for each CIB file the command is 
> run against.
>
> Is there a GDAL command that takes the table of contents file and 
> processes all the CIB frames into one NITF image?  Or takes all the 
> .ntf files that get created and stitches them together into one .ntf
image?
>
>
> Thank you,
>
> Carol Rydzak
> General Dynamics C4 Systems
> Phone: (480) 441-7405
> Email: Carol.Rydzak at gdc4s.com
> This email message is for the sole use of the intended recipient(s) 
> and may contain GDC4S confidential or privileged information. Any 
> unauthorized review, use, disclosure or distribution is prohibited. If

> you are not an intended recipient, please contact the sender by reply 
> email and destroy all copies of the original message.
>
>
>




More information about the gdal-dev mailing list