<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI Light";
panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='mso-fareast-language:EN-US'>I think there could be value in adding CSSHPB with new code inside GDAL NITF. See <a href="https://github.com/OSGeo/gdal/blob/master/gdal/frmts/nitf/nitfdes.c#L209">https://github.com/OSGeo/gdal/blob/master/gdal/frmts/nitf/nitfdes.c#L209</a><o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Do GLAS/GFM later.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Brad<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> gdal-dev <gdal-dev-bounces@lists.osgeo.org> <b>On Behalf Of </b>Edson, Adam Robert<br><b>Sent:</b> Friday, 3 April 2020 2:53 AM<br><b>To:</b> Even Rouault <even.rouault@spatialys.com>; gdal-dev@lists.osgeo.org<br><b>Subject:</b> Re: [gdal-dev] Accessing DES in NITF through GDAL<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal style='background:white'><span style='font-size:12.0pt;color:black'>I have been tasked with making GDAL capable of dealing with a new NITF type (<a href="https://calval.cr.usgs.gov/apps/sites/default/files/jacie/BarbaraEckstein.pdf">https://calval.cr.usgs.gov/apps/sites/default/files/jacie/BarbaraEckstein.pdf</a>) 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.<o:p></o:p></span></p></div><div style='margin-top:12.0pt;margin-bottom:12.0pt;min-width: 424px' id="LPBorder_GTaHR0cHM6Ly9jYWx2YWwuY3IudXNncy5nb3YvYXBwcy9zaXRlcy9kZWZhdWx0L2ZpbGVzL2phY2llL0JhcmJhcmFFY2tzdGVpbi5wZGY."><table class=MsoNormalTable border=1 cellspacing=5 cellpadding=0 width="100%" style='width:100.0%;border:solid #C8C8C8 1.0pt'><tr><td width="100%" valign=top style='width:100.0%;border:none;padding:9.0pt 27.0pt 9.0pt 9.0pt'><div style='margin-right:6.0pt;margin-bottom:9.0pt' id=LPTitle548487><p class=MsoNormal><span style='font-size:16.0pt;font-family:"Segoe UI Light",sans-serif'><a href="https://calval.cr.usgs.gov/apps/sites/default/files/jacie/BarbaraEckstein.pdf" target="_blank"><span style='text-decoration:none'>The Spectral NITF Implementation Profile (SNIP): A New Standard for Multispectral and Hyperspectral Imagery Datasets</span></a><o:p></o:p></span></p></div><div style='margin-right:6.0pt;margin-bottom:9.0pt;max-height: 100px;overflow:hidden' id=LPDescription548487><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Segoe UI",sans-serif;color:#666666'>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<o:p></o:p></span></p></div><div id=LPMetadata548487><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Segoe UI",sans-serif;color:#A6A6A6'>calval.cr.usgs.gov<o:p></o:p></span></p></div></td></tr></table></div><p class=MsoNormal><o:p> </o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="98%" align=center></div><div id=divRplyFwdMsg><p class=MsoNormal><b><span style='color:black'>From:</span></b><span style='color:black'> Even Rouault <<a href="mailto:even.rouault@spatialys.com">even.rouault@spatialys.com</a>><br><b>Sent:</b> Thursday, April 2, 2020 11:03 AM<br><b>To:</b> <a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a> <<a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a>><br><b>Cc:</b> Edson, Adam Robert <<a href="mailto:are131@psu.edu">are131@psu.edu</a>><br><b>Subject:</b> Re: [gdal-dev] Accessing DES in NITF through GDAL</span> <o:p></o:p></p><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><p><span style='font-size:9.0pt;font-family:"Courier New"'>Adam,<o:p></o:p></span></p><p><span style='font-size:9.0pt;font-family:"Courier New"'> <o:p></o:p></span></p><p><span style='font-size:9.0pt;font-family:"Courier New"'>> I am working with NITF data. How are Data Extension Segments (DES) accessed<o:p></o:p></span></p><p><span style='font-size:9.0pt;font-family:"Courier New"'>> through GDAL?<o:p></o:p></span></p><p><span style='font-size:9.0pt;font-family:"Courier New"'> <o:p></o:p></span></p><p><span style='font-size:9.0pt;font-family:"Courier New"'>Complicated topic.<o:p></o:p></span></p><p><span style='font-size:9.0pt;font-family:"Courier New"'> <o:p></o:p></span></p><p><span style='font-size:9.0pt;font-family:"Courier New"'>TRE stored in DES are reported in the TRE and xml:TRE metadata domains.<o:p></o:p></span></p><p><span style='font-size:9.0pt;font-family:"Courier New"'> <o:p></o:p></span></p><p><span style='font-size:9.0pt;font-family:"Courier New"'>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.<o:p></o:p></span></p><p><span style='font-size:9.0pt;font-family:"Courier New"'> <o:p></o:p></span></p><p><span style='font-size:9.0pt;font-family:"Courier New"'>Even<o:p></o:p></span></p><p><span style='font-size:9.0pt;font-family:"Courier New"'> <o:p></o:p></span></p><p><span style='font-size:9.0pt;font-family:"Courier New"'>-- <o:p></o:p></span></p><p><span style='font-size:9.0pt;font-family:"Courier New"'>Spatialys - Geospatial professional services<o:p></o:p></span></p><p><span style='font-size:9.0pt;font-family:"Courier New"'><a href="http://www.spatialys.com">http://www.spatialys.com</a><o:p></o:p></span></p></div></div></body></html>