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
We're considering xcube for several use-cases here, and find it very promising.
One of the case is displaying precipitation nowcasts (from radar data).
What I envisage is to build cubes where the time axis would be the forecast time (from t0 to t0+h).
Since it's nowcasting, it's frequently updated, and every x minutes we receive a full new forecast, so at t1 we'd have a full new cube t1..t1+h
I'd like to publish that and have the server discover the new cube automatically, without a server/container restart (that would be too frequent), and expose it at a new url (for http caching purpose): /nowcast_t0, /nowcast_t1, etc
What would be the proper way to do this?
The text was updated successfully, but these errors were encountered:
We're considering xcube for several use-cases here, and find it very promising.
One of the case is displaying precipitation nowcasts (from radar data).
What I envisage is to build cubes where the time axis would be the forecast time (from t0 to t0+h).
Since it's nowcasting, it's frequently updated, and every x minutes we receive a full new forecast, so at t1 we'd have a full new cube t1..t1+h
I'd like to publish that and have the server discover the new cube automatically, without a server/container restart (that would be too frequent), and expose it at a new url (for http caching purpose): /nowcast_t0, /nowcast_t1, etc
What would be the proper way to do this?
The text was updated successfully, but these errors were encountered: