I am downloading waveform data with RoutingClient. I want to save the individual files in mseed format. I simply use tr.write(filename, fomrat=‘MSEED’).
in this way, a single channel, one day data after downloading is around 100mb (200hz). This is not normal size, should it not be around 15mb per day?
what should I change, if there is something to change?
/Users/bvicic/anaconda3/envs/qtt/lib/python3.7/site-packages/obspy/io/mseed/core.py:790: UserWarning: The encoding specified in trace.stats.mseed.encoding does not match the dtype of the data.
Is the record very noisy? I think that would justify why the file would be heavier than normal. Still you suggest that you write individual traces separately, I guess that you checked if HHE is heavier than the others. I would then try to slice the in several pieces and write them in separate files to understand if there any problematic time period …
as soon as you do any (pre-)processing you are not looking at integer values anymore but floating point numbers. MiniSEED has good compression for the original raw, integer data but floating point data is basically written without compression (this is also why this warning message shows up, since data was read from an integer encoding and has to be saved in a different encoding – for floats). This is causing the higher file size. I would recommend to just save and keep the raw data (see above) and do those pre-processing steps you do ad-hoc in your processing workflows.
I changed the code to use classic Client, and used orfeus data provider (before I used eida-routing). The problem is now solved! indeed the size of mseed files is now around 17mb!
Thank you for your help. Maybe this could be added in the documentation. I didnt know this works like that.