Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

CMR returning duplicate results

See original GitHub issue

reg_a = ipx.Query('ATL06',[-55, 68, -48, 71],['2019-02-20','2019-02-28'])
reg_a.avail_granules()

Now returns a list of 8 granules instead of 4. However, it’s just the same list twice. It’s evident if you go directly to the cmr url as well, which has led me to conclude there’s been a change in CMR metadata returned that the previous method of results parsing doesn’t account for.

This issue aims to:

let folks know about the problem (@jpswinski @weiji14 @tsutterley), as it affects existing versions of icepyx that other tools use
provide a public forum for learning more about what changed and discussing the best approach moving forward (@betolink @asteiker @andypbarrett)

Issue Analytics

State:
Created a year ago
Comments:8 (8 by maintainers)

Top GitHub Comments

2reactions

tsutterleycommented, Oct 17, 2022

There might be a lag upon a data release getting the data to s3, but they should be parallel

1reaction

JessicaS11commented, Oct 17, 2022

the JSON return from CMR looks fine?

Apparently VSCode can’t handle multiple debugging sessions at once. So even though (as you point out) the CMR looked fine in a browser, it was not fine programmatically in that debug session. 🙄 Thanks for quickly confirming it SHOULD work.