You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 3, 2024. It is now read-only.
Within the last year or so, PO.DAAC have updated their Webservice documentation which improves the developer-facing documentation but which I think also introduces a major regression. The regression being that it now now longer lists datasets... meaning that this information would need to be acquired from elsewhere and a data triage task take place if Podaacpy were to provide the PodaacUtils().list_all_available_extract_granule_dataset_ids() utility functionality.
The email I got from a Podaacpy user was as follows
I am Argha from Bangladesh. We are trying to predict Oyster Diseases in our lab. For doing this task we need the Salinity and Temperature data. We are trying to access this dataset “Multi-Mission Optimally Interpolated Sea Surface Salinity Global Dataset V1”.
We will be giving Date, Longitude, Latitude as our inputs and want the salinity output from the dataset. For this purpose I have followed your podaacpy_getting_started_tutorial.ipynb . But the problem I am facing:
I have not found any Persistent ID for the above mentioned dataset
I am getting an error for some specific lines of code but not all. For example:
print(u.list_all_available_extract_granule_dataset_ids()) line gives an error like:
AttributeError: 'NoneType' object has no attribute 'find_all'
But at the same time print(u.list_all_available_granule_search_dataset_ids()) is running perfectly
I have opened a thread at the PO.DAAC Forum to discuss this... more to come.
The text was updated successfully, but these errors were encountered:
Within the last year or so, PO.DAAC have updated their Webservice documentation which improves the developer-facing documentation but which I think also introduces a major regression. The regression being that it now now longer lists datasets... meaning that this information would need to be acquired from elsewhere and a data triage task take place if Podaacpy were to provide the
PodaacUtils().list_all_available_extract_granule_dataset_ids()
utility functionality.The email I got from a Podaacpy user was as follows
I have opened a thread at the PO.DAAC Forum to discuss this... more to come.
The text was updated successfully, but these errors were encountered: