-
Notifications
You must be signed in to change notification settings - Fork 82
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
Expose M1 location info #28
Comments
Great point. The first thing that comes to mind is optionally writing a separate JSON file for every image file that contains all the LRIT headers verbatim. EXIF is not an option because OpenCV doesn't support it. Also EXIF would only apply to JPEG files and not PNGs, PGMs, etc. |
a JSON file per image sounds perfect, too! |
@eminence Check out the linked commit. Make sure to set |
Following up on this after a long winter hiatus. This new feature is working great, thank you! Using the I'm curious about the |
Thanks for the feedback. Glad to hear it's working for you. Can you share a demo of where/how you're using it? The |
You can search for "image data function" in the LRIT specs (for example here) for more info. |
Thanks for the tips about the image data function info, I'll take a look
Sure! It's being used for a personal dashboard I wrote to give me a quick interface to the images produced by goesproc. https://goes.em32.net/ In the "Latest GOES-16 section" you can see that some images are labeled with some of the cites in view, and this was calculated using the ImageNavigation data from the json files |
As I understand it, the M1 payloads contain info about the area that GOES-16 is looking at. This info is how goesproc is able to correctly project the map overlay. Can this data be exposed to the user somehow? (Perhaps via exif info in the images or something). This would be useful for an end-user who wants to scan a bunch of images and find ones that are looking at particular areas of the globe.
The text was updated successfully, but these errors were encountered: