Especially as I haven't seen a descriptive document for them yet. ________________________________ From: Brad Hards <br...@frogmouth.net> Sent: Thursday, April 2, 2020 12:00 PM To: Edson, Adam Robert <are...@psu.edu>; gdal-dev@lists.osgeo.org <gdal-dev@lists.osgeo.org> Subject: RE: [gdal-dev] Accessing DES in NITF through GDAL
I think there could be value in adding CSSHPB with new code inside GDAL NITF. See https://github.com/OSGeo/gdal/blob/master/gdal/frmts/nitf/nitfdes.c#L209<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOSGeo%2Fgdal%2Fblob%2Fmaster%2Fgdal%2Ffrmts%2Fnitf%2Fnitfdes.c%23L209&data=02%7C01%7Care131%40psu.edu%7Cdb0f54a867014bd9d01c08d7d71f0225%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C1%7C637214400509897086&sdata=fjKo%2BPoB13uLWVme017unoi7Vtej4UKCJ%2Bc3%2FoJthbU%3D&reserved=0> Do GLAS/GFM later. Brad From: gdal-dev <gdal-dev-boun...@lists.osgeo.org> On Behalf Of Edson, Adam Robert Sent: Friday, 3 April 2020 2:53 AM To: Even Rouault <even.roua...@spatialys.com>; gdal-dev@lists.osgeo.org Subject: Re: [gdal-dev] Accessing DES in NITF through GDAL 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<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcalval.cr.usgs.gov%2Fapps%2Fsites%2Fdefault%2Ffiles%2Fjacie%2FBarbaraEckstein.pdf&data=02%7C01%7Care131%40psu.edu%7Cdb0f54a867014bd9d01c08d7d71f0225%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C1%7C637214400509907083&sdata=FsHOy6MExgDO2PwRfumpRdCNiPUEnf1GWLL5Nk%2FB6Zo%3D&reserved=0>) 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://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcalval.cr.usgs.gov%2Fapps%2Fsites%2Fdefault%2Ffiles%2Fjacie%2FBarbaraEckstein.pdf&data=02%7C01%7Care131%40psu.edu%7Cdb0f54a867014bd9d01c08d7d71f0225%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C1%7C637214400509907083&sdata=FsHOy6MExgDO2PwRfumpRdCNiPUEnf1GWLL5Nk%2FB6Zo%3D&reserved=0> 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.roua...@spatialys.com<mailto:even.roua...@spatialys.com>> Sent: Thursday, April 2, 2020 11:03 AM To: gdal-dev@lists.osgeo.org<mailto:gdal-dev@lists.osgeo.org> <gdal-dev@lists.osgeo.org<mailto:gdal-dev@lists.osgeo.org>> Cc: Edson, Adam Robert <are...@psu.edu<mailto:are...@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<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.spatialys.com%2F&data=02%7C01%7Care131%40psu.edu%7Cdb0f54a867014bd9d01c08d7d71f0225%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C1%7C637214400509917076&sdata=t%2FN3ibH8aUsEDcre1Qr9PdSiNr%2Fae1Nnjedd%2BKVhazc%3D&reserved=0>
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
