Page 1 of 1

Major regression in Webservices?

PostPosted: Fri Jul 30, 2021 9:29 am
by lmcgibbn
Hi WS Devs,

Nice work on the OAS3 WS... really nice looking and easier for developers.

I recently got a query from a Podaacpy user cf. https://github.com/nasa/podaacpy/issues/159
The issue stems from a regression which was introduced when the webservices documentation (https://podaac.jpl.nasa.gov/ws/) was updated and the dataset collections tables were removed. This means that no-one knows the dataset identifiers...???

What is the (new) best/recommended way to list the datasets for utility purposes given the above regression?
How is someone meant to know the dataset identifier? Go to Earthdata Search and get it then use it in their code? This seems a tad laborious...

Thanks for any advice.
Lewis

P.S. Now that PO.DAAC WS are based on OAS3, I had thought it might be prudent to utilize one of the OAS3 Python generators to generate a Python client and then use that within Podaacpy however Podaacpy was more feature complete than what is now offered through the updated PO.DAAC WS API... so that would also be a major regreession for the Podaacpy project.

Re: Major regression in Webservices?

PostPosted: Fri Jul 30, 2021 9:37 am
by lmcgibbn
Additionally, where did the datasetID's disappear to?
There is no dataset ID for this given dataset
https://podaac.jpl.nasa.gov/dataset/OISSS_L4_multimission_7day_v1
Thanks