Closed JessicaS11 closed 1 year ago
:point_left: Launch a binder notebook on this branch for commit 3d48e0c8df3bdca219945b6bd98b8d5604eced64
I will automatically update this comment whenever this PR is modified
:point_left: Launch a binder notebook on this branch for commit 960d4c29b02139474a6d3d8c109bf39369f4e856
:point_left: Launch a binder notebook on this branch for commit dd0ad0ddb254b0d5decd6c4b18dd3372036a0228
:point_left: Launch a binder notebook on this branch for commit 1c39d7f50338cc8551ff100c043a56eeaa938338
:point_left: Launch a binder notebook on this branch for commit a7a3e0d43c7858f086690940026b0288fab12e4c
:point_left: Launch a binder notebook on this branch for commit bbc1ff0d13b0695ade033e2ebefdce1ef1902cd9
In some cases, if a CMR query was submitted for on-prem data (
{'provider':'NSIDC_ECS'}
), s3 urls were not available in the returned metadata. Since a separate request is submitted for downloading on-prem data (which has subsetting capabilities not available in the cloud), this PR defaults to using{'provider':'NSIDC_CPRD'}
(the cumulus production provider - data download and streaming from an s3 bucket) in all metadata requests.