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

Enhancement: Support for ISD Compression #604

Closed
jlaura opened this issue May 21, 2024 · 1 comment · Fixed by #606
Closed

Enhancement: Support for ISD Compression #604

jlaura opened this issue May 21, 2024 · 1 comment · Fixed by #606
Assignees

Comments

@jlaura
Copy link
Collaborator

jlaura commented May 21, 2024

When working with a large number of ISDs, the total data volume can start to become an issue. To combat this, some sort of compression for ISDs would be terrific. Right now, this is living in user land where one can compression/uncompress. This is to request a potential enhancement in ALE to standardize on one compression method. The idea being that down stream ISD consumers could choose to support compressed ISDs because they know what the compression is.

This review of JSON suggests that simple brotli compression is both fast and efficient. It also seems that brotli is well supported.

@thareUSGS
Copy link
Contributor

thareUSGS commented May 21, 2024

I like that brotli was designed for http streaming and there is a C++ header-only option (https://github.com/NewYaroslav/brotli-hpp). Perhaps the "usgs_csm_test" helper app could include a built-in compress/decompress method so that it can be made human-readable. Well, that app would need to support decompression since there is a method to inject a camera state into a GXP "sup" supplemental file. The sup file would require the ASCII version.

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

Successfully merging a pull request may close this issue.

3 participants