SICDWriter: add required "SICD:" characters to NITF FTITLE about sarpy HOT 6 CLOSED

After I wrote the ticket, I looked at the code, and I saw a place where the “SICD:” was being added to the FTITLE (_get_ftitle()), so I wasn’t sure about my observation, so I withdrew it, but it does appears that in the way I’m using SICDWriter, it is not being added. In general, if there’s a specification, I would like to see compliance with the specification. We have delivered software with customers that expect SICD specification compliance and check for that “SICD:” string in the FTITLE. The programs I am supporting now cannot influence changes to those products. If there is software in use from other vendors that are looking for that, I certainly cannot ask them to change the code. Thanks, John From: tommccullough-tenica ***@***.***> Sent: Wednesday, March 17, 2021 10:21 AM To: ngageoint/sarpy ***@***.***> Cc: Henderson, John (US) <[email protected]>; State change ***@***.***> Subject: [EXTERNAL] Re: [ngageoint/sarpy] SICDWriter: add required "SICD:" characters to NITF FTITLE (#207) No trouble. Just so you know the origins, I originally had it set to "SICD: " as suggested in the standards document. Someone gave me some specific guidance to use something else in many cases, and that's what's there now. I need to have a discussion with my POC, but I'm probably open to changing it back. I feel like this is disappointing, but I've convinced myself that the only reliable way of ensuring that the file is actually SICD file is to check: 1.) there are data extensions present - SICD files could have tre overflow data extensions or other additional data extension, but probably only have exactly one data extension. Note that SIDD files are permitted to have SIDD data extension(s) and SICD data extensions. 2.) exactly one of these data extensions contains a SICD structure - again, note that SIDD files may contain SICD data extension(s) in addition to SIDD data extension(s). 3.) the image data is complex and in keeping with the SICD structure - SICD files will contain complex data, but SIDD files will definitely not. Some other NITF files may contain complex image data, but not the SICD data extension - these will probably have meta data scattered through a variety of tres. That said, I'm trying to be completely thorough, and there's likely something less complicated that probably works in most cases. Feel free to email any correspondence at thomas dot mccullough dot ctr at nga dot mil. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub<#207 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASRBLSCQWSGGVESACHUBYPTTEC3FTANCNFSM4ZKKJBVA>. CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient and may contain material that is proprietary, confidential, privileged or otherwise legally protected or restricted under applicable government laws. Any review, disclosure, distributing or other use without expressed permission of the sender is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies without reading, printing, or saving.

Thanks for the link. Web searches keep taking me here: https://gwg.nga.mil/ntb/baseline/docs/SICD/. From: Wade Schwartzkopf ***@***.***> Sent: Wednesday, March 17, 2021 10:54 AM To: ngageoint/sarpy ***@***.***> Cc: Henderson, John (US) <[email protected]>; State change ***@***.***> Subject: [EXTERNAL] Re: [ngageoint/sarpy] SICDWriter: add required "SICD:" characters to NITF FTITLE (#207) Actually, the "SICD: " requirement no longer exist in the latest version of SICD. This means the SarPy code has to be able to handle FTITLE with or without it, in order to be completely generic. https://nsgreg.nga.mil/doc/view?i=4901 SarPy should allow writing and reading of SICDs with the "SICD: " prefix in the FTITLE, but it should not force it. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub<#207 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASRBLSDAJEL7J7N3ZLGGY3DTEC7BTANCNFSM4ZKKJBVA>. CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient and may contain material that is proprietary, confidential, privileged or otherwise legally protected or restricted under applicable government laws. Any review, disclosure, distributing or other use without expressed permission of the sender is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies without reading, printing, or saving.