"Do you think we should continue to only have a single file that is overwritten every time? This would be the simplest approach, and I don't foresee us running into file size issue if it is only a few dozen sensors reading daily. Just want to be explicit about this choice vs. a choice that needs more logical overhead like having each daily snowpack file written to S3 as a different CSV or something" - @christophertull (comment ported from argus pull request)
context note: updates to how the ucla parser/model writes data to s3 may have to be accounted for by means of some additional argus dev
"Do you think we should continue to only have a single file that is overwritten every time? This would be the simplest approach, and I don't foresee us running into file size issue if it is only a few dozen sensors reading daily. Just want to be explicit about this choice vs. a choice that needs more logical overhead like having each daily snowpack file written to S3 as a different CSV or something" - @christophertull (comment ported from argus pull request)
context note: updates to how the ucla parser/model writes data to s3 may have to be accounted for by means of some additional argus dev