Since we’re starting to support Budget Data Packages which rely on data packages I think this should be something supported by data packages which can trickle down into OpenSpending instead of we deciding our own stuff and then having something different from everyone else when (and if) data packages decide on something.
Maybe, but I think it is better to address this specific issue here:
a) Its specific (rather than the general case) - which may make it easier to address
b) It was more about immediate convenience for (power) uploaders and downloaders (specifically Holger (working on farmsubsidy) brought this up)
So: I think it is definitely worth discussing here (even if we can eventually upstream)
Doesn’t compression rob us of really amazing opportunities to do streaming stuff on CSV? I can’t imagine S3 costing so much this actually becomes a need so I would be a tentative -1 on compression as a whole
However, Holger made compelling argument in terms of upload and download that for some data (at least near-term) we may want compression because of size (e.g. farmsubsidy stuff).
I’m still not sure.
I also wonder if some compression stuff allows compression / decompression on the fly (I thought gzip supported this) in which case this might not be so bad.