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
Currently, most of the data in Pangeo's catalog is in the same cloud region. I expect that, in the future, we'll move to a more distributed storage system where we may want to point to data on multiple clouds/regions. For this reason, it will be convenient to subset data by cloud vendor and region. Perhaps something like this would work:
Another option would be to rework the catalog nesting to represent this level of per-cloud structure.
On the flask-app side, I think it would be useful to understand what is possible in terms of subsetting and how we can leverage intake search capabilities to make this possible.
The text was updated successfully, but these errors were encountered:
I'll check out if the app (from gcloud's side) is able to discern what region a user is accessing from - if the intention is to provide a user data from the appropriate region, then reworking the catalogs to use region as a top-level filter could let us provide them regional cloud catalogs.
Currently, most of the data in Pangeo's catalog is in the same cloud region. I expect that, in the future, we'll move to a more distributed storage system where we may want to point to data on multiple clouds/regions. For this reason, it will be convenient to subset data by cloud vendor and region. Perhaps something like this would work:
Another option would be to rework the catalog nesting to represent this level of per-cloud structure.
On the flask-app side, I think it would be useful to understand what is possible in terms of subsetting and how we can leverage intake search capabilities to make this possible.
The text was updated successfully, but these errors were encountered: