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

Connecting VNP14IMG Swath Data with VNP03IMG Geolocation Data #2945

Open
jiyeon-kim20 opened this issue Oct 21, 2024 · 1 comment
Open

Connecting VNP14IMG Swath Data with VNP03IMG Geolocation Data #2945

jiyeon-kim20 opened this issue Oct 21, 2024 · 1 comment

Comments

@jiyeon-kim20
Copy link

Hello,

I am working with VIIRS satellite data and currently have two files:

  1. VNP14IMG - Swath data without geolocation.
  2. VNP03IMG - Geolocation data.

Each file uses a different reader:

viirs_l1b for VNP03IMG
viirs_edr_active_fires for VNP14IMG (for which I have already made a custom reader in the YAML file).

scn = Scene(filenames={
    'viirs_l1b': ['/content/VNP03IMG.A2023221.1124.002.2023221175939.nc'],
    'viirs_edr_active_fires': ['/content/VNP14IMG.A2023221.1124.002.2024080020549.nc']
                       })

Given these differences,
how can I connect or merge the geolocation data from VNP03IMG with the swath data from VNP14IMG?

Thank you!

@djhoese
Copy link
Member

djhoese commented Oct 21, 2024

Thanks for filing this question. There are two paths to a solution, but I need more information about these files. Mainly, are these new official fires products from NASA? Are these imagery versions of the fire detection (isn't that a waste of space?)?

To get something working I would either edit the viirs_edr_active_fires as it sounds like you've already started or update the viirs_edr reader. If this is some kind of official EDR product it might be nice to update viirs_edr to handle it if the loading resembles/matches the existing files handled by that reader.

For the viirs_edr_active_fires case, I would copy the geolocation file type definition and lon/lat definitions from viirs_l1b and place them into viirs_edr_active_fires.yaml. Or make a whole new YAML file for a new reader if you run into issues. The viirs_edr_active_fires.yaml file would point to the python code for viirs l1b and for the viirs active fires. That's fine.

Bottom line: the "connecting" of these two file types happens via duplication in the reader YAML rather than anything fancy on the Scene-level.

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

No branches or pull requests

2 participants