question-mark
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.

NSIDC not implemented error with readable_granule_name

See original GitHub issue

An extension of #274, the ability to order granules by readable_granule_name is not working. Specifically,

request_params= {'short_name': 'ATL06',
 'version': '005',
 'options[readable_granule_name][pattern]': 'true',
 'options[spatial][or]': 'true',
 'readable_granule_name[]': ['ATL06_??????????????_084903??_*',
  'ATL06_??????????????_090203??_*',
  'ATL06_??????????????_084904??_*',
  'ATL06_??????????????_090204??_*',
  'ATL06_??????????????_084905??_*',
  'ATL06_??????????????_090205??_*',
  'ATL06_??????????????_084906??_*',
  'ATL06_??????????????_090206??_*',
  'ATL06_??????????????_084907??_*',
  'ATL06_??????????????_090207??_*'],
 'polygon': '-55.0,68.0,-48.0,68.0,-48.0,71.0,-55.0,71.0,-55.0,68.0',
 'page_size': 2000,
 'page_num': 1,
 'request_mode': 'async',
 'include_meta': 'Y',
 'client_string': 'icepyx'}

session.get("https://n5eil02u.ecs.nsidc.org/egi/request", params=request_params) 

returns: HTTPError: 501 Server Error: Not Implemented for url: https://n5eil02u.ecs.nsidc.org/egi/request?short_name=ATL06&version=005&options%5Breadable_granule_name%5D%5Bpattern%5D=true&options%5Bspatial%5D%5Bor%5D=true&readable_granule_name%5B%5D=ATL06_%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F_084903%3F%3F_%2A&readable_granule_name%5B%5D=ATL06_%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F_090203%3F%3F_%2A&readable_granule_name%5B%5D=ATL06_%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F_084904%3F%3F_%2A&readable_granule_name%5B%5D=ATL06_%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F_090204%3F%3F_%2A&readable_granule_name%5B%5D=ATL06_%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F_084905%3F%3F_%2A&readable_granule_name%5B%5D=ATL06_%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F_090205%3F%3F_%2A&readable_granule_name%5B%5D=ATL06_%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F_084906%3F%3F_%2A&readable_granule_name%5B%5D=ATL06_%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F_090206%3F%3F_%2A&readable_granule_name%5B%5D=ATL06_%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F_084907%3F%3F_%2A&readable_granule_name%5B%5D=ATL06_%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F_090207%3F%3F_%2A&polygon=-55.0%2C68.0%2C-48.0%2C68.0%2C-48.0%2C71.0%2C-55.0%2C71.0%2C-55.0%2C68.0&page_size=2000&page_num=1&request_mode=async&include_meta=Y&client_string=icepyx&Boundingshape=%7B%22type%22%3A%22FeatureCollection%22%2C%22features%22%3A%5B%7B%22id%22%3A%220%22%2C%22type%22%3A%22Feature%22%2C%22properties%22%3A%7B%7D%2C%22geometry%22%3A%7B%22type%22%3A%22Polygon%22%2C%22coordinates%22%3A%5B%5B%5B-55.0%2C68.0%5D%2C%5B-48.0%2C68.0%5D%2C%5B-48.0%2C71.0%5D%2C%5B-55.0%2C71.0%5D%2C%5B-55.0%2C68.0%5D%5D%5D%7D%2C%22bbox%22%3A%5B-55.0%2C68.0%2C-48.0%2C71.0%5D%7D%5D%2C%22bbox%22%3A%5B-55.0%2C68.0%2C-48.0%2C71.0%5D%7D (as originally cited by @nitin-ravinder in #274).

@betolink @andypbarrett @tsutterley Anything jump out immediately as causing the issue? Given these examples worked previously, I’m wondering if there was a CMR change that we need to update for?

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:11 (11 by maintainers)

github_iconTop GitHub Comments

1reaction
JessicaS11commented, Apr 29, 2022

See the updated comment in #292. After further digging, it looks like we found an edge case in the subsetter versus CMR API implementations of readable_granule_name. The former can only handle one string, while the latter will search for a list of strings. Namely:

request_params= {'short_name': 'ATL06',
 'version': '005',
 'options[readable_granule_name][pattern]': 'true',
 'options[spatial][or]': 'true',
 'readable_granule_name[]': ['ATL06_??????????????_084903??_*'],
 'polygon': '-55.0,68.0,-48.0,68.0,-48.0,71.0,-55.0,71.0,-55.0,68.0',
 'page_size': 2000,
 'page_num': 1,
 'request_mode': 'async',
 'include_meta': 'Y',
 'client_string': 'icepyx'}

worked, but:

request_params= {'short_name': 'ATL06',
 'version': '005',
 'options[readable_granule_name][pattern]': 'true',
 'options[spatial][or]': 'true',
 'readable_granule_name[]': ['ATL06_??????????????_084903??_*',
  'ATL06_??????????????_090203??_*',
  'ATL06_??????????????_084904??_*',
  'ATL06_??????????????_090204??_*',
  'ATL06_??????????????_084905??_*',
  'ATL06_??????????????_090205??_*',
  'ATL06_??????????????_084906??_*',
  'ATL06_??????????????_090206??_*',
  'ATL06_??????????????_084907??_*',
  'ATL06_??????????????_090207??_*'],
 'polygon': '-55.0,68.0,-48.0,68.0,-48.0,71.0,-55.0,71.0,-55.0,68.0',
 'page_size': 2000,
 'page_num': 1,
 'request_mode': 'async',
 'include_meta': 'Y',
 'client_string': 'icepyx'}

doesn’t when submitting an order.

@nitin-ravinder, could you check that your use case works with the updates? Would you be able/willing to review the PR?

1reaction
JessicaS11commented, Feb 21, 2022

Repeating you to make sure I have it right: readable granule names are valid for CMR queries, but not for the order request itself (which would match with the error message)? Here reqparams is actually “required parameters” that MUST be supplied to submit a request (with the specific parameters depending on whether it’s a CMR query or order to the NSIDC API). So it sounds like they are getting carried through to the order placing but shouldn’t be… I’ll see if I can figure out what may have changed on the icepyx end to trigger this, unless we hear from NSIDC that something changed on their end.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Help Center - National Snow and Ice Data Center
NSIDC currently archives passive microwave sea ice concentration products based on two algorithms: the NASA Team algorithm and the ...
Read more >
Programmatic Data Access Guide
Programmatic Data Access Guide. All data from the NASA National Snow and Ice Data Center Distributed Active Archive Center (NSIDC DAAC) can be...
Read more >
Get Started with NSIDC Data
The National Snow and Ice Data Center (NSIDC) data management programs focus on preserving, documenting and providing access to over 1400 data sets...
Read more >
Frequently Asked Questions on Arctic sea ice
What is the error range for your images? NSIDC does not have error bars on the time series plot shown in the “Daily...
Read more >
MEaSUREs Arctic Sea Ice Characterization Daily 25km EASE ...
Programmatically request selected data products through NSIDC's API. Bulk download using spatial and temporal filters, or incorporate data access commands into ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found