Nicolas wrote:
Can anyone with some experience in these matters, and especially of
alternative formats, e.g. netCDF, comment on this and recommend a
standard well-supported solution?
I do not think scientific data should be stored with protocol-buffers.
I would suggest, since netCDF-4 now
Even if the message contains only one, non-repeated field, ParseFrom*() will
keep reading until EOF or an error.
At Google, we have lots of various container formats, for streaming,
record-based files, database tables, etc., where each record is a protocol
buffer. All of these formats store the
