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
use case: long-term observation dataset was archived as two packages, in the latest update the author wants most tables in one package and get rid of others. And updated tables have slightly different structures.
The text was updated successfully, but these errors were encountered:
Good idea. Another use case I've been thinking about at MCM: we currently archive monthly and/or daily summaries of our met and hydro data as separate packages from the high-frequency data. So this means for each met station or stream gage, we have 2-3 packages per station. It's a ton of extra work on my part, and creates confusion to our researchers (they often download the wrong package). I would like to consider consolidating into a single package per station, but I also wonder how others are tackling? If we consolidate, then we'll have to depreciate some packages...
use case: long-term observation dataset was archived as two packages, in the latest update the author wants most tables in one package and get rid of others. And updated tables have slightly different structures.
The text was updated successfully, but these errors were encountered: