Hexagon Geospatial
MENU

ERDAS APOLLO & ECW/JP2

Wondering how others have configured their ERDAS APOLLO server or what data they are crawling? The ERDAS APOLLO Discussion board is a place to find information, share ideas and more. Join the community, connect, contribute and share.
Showing results for 
Search instead for 
Do you mean 
Reply
Contributor
Posts: 38
Registered: ‎12-03-2015

Data Manager (2015) - CADRG (.tl3 files) support

Hi All,

Does DM support CADRG in .TL3 files extentions?

I tried to crawl these type of files and DM couldn't add it to the catalog.

 

According to this document http://www.hexagongeospatial.com/technical-documents/erdas-apollo-2015-product-description 

CADRG format is supported.

 

Thanks.

Pkrok

 

Highlighted
Technical Evangelist
Posts: 828
Registered: ‎07-30-2015

Re: Data Manager (2015) - CADRG (.tl3 files) support

Hi Prrok,

Can you use IMAGINE to export img/tif to this .tl3?
When I use IMAIGNE 2016 CADRG (Compressed ADRG) exporter, I could not find .tl3 from output folder.
output folder
|_RPF\
     |_A.TOC
     |_CADRGTC\
            |_ZONE2\
                  |_00AEL011.TC2
                  |_...
                  |_0099Z011.TC2

best
haiyan

Staff inactive
Posts: 57
Registered: ‎10-12-2015

Re: Data Manager (2015) - CADRG (.tl3 files) support

Pkrok

 

CADRG uses an A.TOC file which points to the frame files in the subfolders (CTLC in my case). ERDAS APOLLO recognizes the A.TOC and catalogs it successfully. The separate *.tl3 frames files are not recognized as raster files. The frame files are NITF format, the file extension is a combination of the product type (TL= topographic line map, and 3 is the ARC Zone 3 (the coordinate system)). Most image file formats have a “magic number” in the first word, so software such as ERDAS IMAGINE can identify the file format without depending on the file extension.  ERDAS APOLLO does not support this 'magic number' at this time and just uses the decoder.txt and the decoder.ymal files to associate a file extension with the actual file type and the raster library to use to read it.

 

A user can edit the decoder.txt and decoder.ymal files and map .tl3 as a NITF file format. The problem is that if they have any files in other ARC zones (there are 18 zones) they would have map each zone extension. This would also be true for any other CADRG product.

 

I hope this helps to a degree...

Do you need immediate support?
If you encounter a critical issue and need immediate assistance please submit a Service Request through our Support Portal.