Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for NITF MIL-STD-2500C W/CHANGE 2 (Motion Imagery, H.264) #9509

Open
sei-rsteele opened this issue Mar 19, 2024 · 2 comments
Open

Support for NITF MIL-STD-2500C W/CHANGE 2 (Motion Imagery, H.264) #9509

sei-rsteele opened this issue Mar 19, 2024 · 2 comments

Comments

@sei-rsteele
Copy link

Feature description

According to MIL-STD-2500C W/CHANGE 2 pages 36-37:

Image Compression (IC) values include motion imagery (CB, MB, C9, M9, CA, MA).

Is there any planned future support for motion imagery?

Additional context

No response

@rouault
Copy link
Member

rouault commented Mar 19, 2024

Is there any planned future support for motion imagery?

Not that I'm aware of. Unlikely to happen without funding / code contribution. Is it movies or individual frames that can be separated?

CC @bradh if he has some clues

@bradh
Copy link
Contributor

bradh commented Mar 19, 2024

There is support for a few of the TREs for the Motion Imagery Extensions for NITF. I added those because they seemed generally applicable, and the NITF Technical Board is moving those into STDI-0002.

However it's not clear how the motion imagery (time dominant) data would work in GDAL. There might be application specific subsets that could work, but a stream of frames is going to be a stretch.

I am willing to discuss further but for a new program you'd want to be using at least the Joint BIIF Profile instead of -2500C, and it might be worth getting in contact to discuss the NGIIS (ISOBMFF based) work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants