[gdal-dev] Accessing DES in NITF through GDAL

[Edson, Adam Robert]

I have been tasked with making GDAL capable of dealing with a new NITF type (https://calval.cr.usgs.gov/apps/sites/default/files/jacie/BarbaraEckstein.pdf) that has major buy-in from data providers. Due to the ubiquity of GDAL, making the change at this level will give the most people access.
The Spectral NITF Implementation Profile (SNIP): A New Standard for Multispectral and Hyperspectral Imagery Datasets<https://calval.cr.usgs.gov/apps/sites/default/files/jacie/BarbaraEckstein.pdf>
The NITF Standard (NITFS) consists of a file header and different “segment” types Some segments may include “tagged record extensions” (TREs), i.e., metadata headers
calval.cr.usgs.gov

________________________________
From: Even Rouault <even.rouault at spatialys.com>
Sent: Thursday, April 2, 2020 11:03 AM
To: gdal-dev at lists.osgeo.org <gdal-dev at lists.osgeo.org>
Cc: Edson, Adam Robert <are131 at psu.edu>
Subject: Re: [gdal-dev] Accessing DES in NITF through GDAL


Adam,



> I am working with NITF data. How are Data Extension Segments (DES) accessed

> through GDAL?



Complicated topic.



TRE stored in DES are reported in the TRE and xml:TRE metadata domains.



For generic DES extraction, you need to build GDAL with the ESRI_BUILD macro enabled, and then they should be reported as Base64 encoded content in the NITF_DES metadata domain, but I haven't tried such builds recently.



Even



--

Spatialys - Geospatial professional services

http://www.spatialys.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20200402/5813b94d/attachment.html>