Thx to Martin and Even for the useful information.<br><br>Best Regards,<br>Daniele Romagnoli<br><br><br><div class="gmail_quote">On Tue, Mar 11, 2008 at 7:57 PM, Even Rouault <<a href="mailto:even.rouault@mines-paris.org">even.rouault@mines-paris.org</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Daniele,<br>
<br>
>From GDAL 1.5.0, there is a RPFTOC driver that can read the A.TOC file and<br>
reports a list of subdatasets. These subdatasets can then be opened with GDAL<br>
and they'll provide the list of frame files in metadata. See<br>
<a href="http://www.gdal.org/frmt_various.html#RPFTOC" target="_blank">http://www.gdal.org/frmt_various.html#RPFTOC</a>.<br>
<br>
To answer exactly to your question, you can have a look at the<br>
frmts/nitf/nitffile.c file in the GDAL source tree, in particularly the<br>
array 'nitfSeries' at the end of the file. The first column gives the first 2<br>
letters of the possible extensions. If you add as the third character the<br>
figures from 1 to 9 (corresponding to the 9 ARC zones), you'll have all the<br>
possible extensions. So you have .gn1 to .gn9, .on1 to .on9, .jn1<br>
to .jn9, .tp1 to .tp9, .jg1 to .jg9, .ja1 to .ja9, .tl1 to .tl9, etc... (from<br>
my experience, these are the extensions that'll cover 90% of the typical<br>
available CADRG products)<br>
<br>
<br>
Le Tuesday 11 March 2008 17:10:39 Martin Chapman, vous avez écrit :<br>
<div><div></div><div class="Wj3C7c">> Daniele,<br>
><br>
><br>
><br>
> The RPF specification is MILSTD-2411 which has a couple of addendums and<br>
> all can be found at <a href="http://earth-info.nga.mil/publications/specs/" target="_blank">http://earth-info.nga.mil/publications/specs/</a> . The<br>
> basic structure of an RPF file is a root directory named RPF which contains<br>
> a file named a.toc which means "Table of Contents". That file is a<br>
> database of boundaries and frames files that make up the various images<br>
> within the RPF file. The boundaries constitute a group of adjacent frame<br>
> files that together make a scene or image. Each frame file is 1536 x 1536<br>
> pixels and is formatted as an NITF file. The frame files live within or<br>
> below the RPF directory in other directories and the file name is a key<br>
> that denotes the series, scale, zone and other information. If you cannot<br>
> open the frame files because your viewer wants an .ntf extension, just<br>
> change the extension to .ntf and it will open in your viewer. Then RPF is<br>
> split into two types, Compressed Arc Digital Raster Graphics (CADRG) and<br>
> Controlled Image Base (CIB). The first is a vector map that has one band<br>
> and a color table where the second is a one band gray scale image. The<br>
> main file you should be opening is always a.toc and then you should use the<br>
> toc to retrieve whatever boundary and frame info you want. The toc has the<br>
> file paths for each of the frames files for a given boundary.<br>
><br>
><br>
><br>
> Hope this helps!<br>
><br>
><br>
><br>
> Best regards,<br>
><br>
> Martin Chapman<br>
><br>
><br>
><br>
> From: <a href="mailto:gdal-dev-bounces@lists.osgeo.org">gdal-dev-bounces@lists.osgeo.org</a><br>
> [mailto:<a href="mailto:gdal-dev-bounces@lists.osgeo.org">gdal-dev-bounces@lists.osgeo.org</a>] On Behalf Of Daniele Romagnoli<br>
> Sent: Tuesday, March 11, 2008 8:55 AM<br>
> To: <a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br>
> Subject: [gdal-dev] Question about NITF CADRG data file extensions.<br>
><br>
><br>
><br>
> Hi list,<br>
> I have a trivial question about the supported/existing Nitf CADRG data file<br>
> extensions.<br>
><br>
> In the ImageIO-Ext project, I'm setting up a NITF plugin (leveraging on<br>
> GDAL).<br>
> The ImageReaderSpi of each ImageIO reader could specify the suffixes which<br>
> the format specific plugin is able to support.<br>
> Actually, I'm interested in CADRG format extensions. Thus, my silly<br>
> question is:<br>
> Which file extensions exist for the NITF CADRG format?<br>
><br>
> After a "quick and random" search, I have found some ".on1", ".on2", ".on5"<br>
> file extensions for Operational Navigation Chart and ".tp4" file extension<br>
> for Tactical Pilotage Chart.<br>
> I'm pretty sure there are ".onX" and ".tpX" (where X is a number) file<br>
> extensions. Can someone give me some advice on this?<br>
><br>
> Thank you very much.<br>
><br>
> Best regards,<br>
> Daniele<br>
<br>
<br>
</div></div>_______________________________________________<br>
gdal-dev mailing list<br>
<div class="Ih2E3d"><a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br>
</div><a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>-------------------------------------------------------<br>Eng. Daniele Romagnoli <br>Software Engineer<br><br>GeoSolutions S.A.S.<br>Via Carignoni 51<br>55041 Camaiore (LU)<br>
Italy<br><br>phone: +39 0584983027<br>fax: +39 0584983027<br>mob: +39 328 0559267<br><br><br><a href="http://www.geo-solutions.it">http://www.geo-solutions.it</a><br><br>-------------------------------------------------------<br>