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

extrapolation of satellite relative azimuiths? #3015

Open
kameshvinjamuri opened this issue Dec 13, 2024 · 3 comments · May be fixed by #3017
Open

extrapolation of satellite relative azimuiths? #3015

kameshvinjamuri opened this issue Dec 13, 2024 · 3 comments · May be fixed by #3017

Comments

@kameshvinjamuri
Copy link

kameshvinjamuri commented Dec 13, 2024

Describe the bug
The SLSTR L1B RBT product geometry files (viewing angles) are in tie point grids. When reading from satpy (which should ideally give interpolated values for an asked grid), the values seem to be getting extrapolated (values more than 360 degrees).

scn = Scene(filenames=glob(os.path.join(swath_dir, "*.nc")), reader="slstr_l1b")    
dq = DataQuery(name='satellite_azimuth_angle', stripe='a', view='nadir', resolution=500)
var_ret = load_data(dq, scn)
np.nanmax(var_ret.data)

Expected behavior
values should always in between 0 to 360 degrees for sun-earth geometry

Actual results
out: 428.0610558123558

Screenshots

Environment Info:

  • OS: [ Linux]
  • Satpy Version: Version: 0.53.0
  • PyResample Version: Version: 1.31.0
  • Readers and writers dependencies (when relevant): [run from satpy.utils import check_satpy; check_satpy()]

Additional context

@simonrp84
Copy link
Member

Could you please provide the granule name for the scene where you noticed this? I'd like to download the entire granule rather than just the geometry_tn.nc file...

@kameshvinjamuri
Copy link
Author

S3A_SL_1_RBT____20200408T055716_20200408T060016_20200409T121711_0180_057_034_1620_LN2_O_NT_004.SEN3

@simonrp84 simonrp84 linked a pull request Dec 13, 2024 that will close this issue
2 tasks
@simonrp84
Copy link
Member

I just made a PR that should fix this :)

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.

2 participants