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
The combination of ringserver with portable-fdsnws-dataselect and mseedindex makes a nice combination for ingesting data and making it available. But having to run an separate program periodically to index miniseed files seems inefficient. Could the miniseed archiving portion of ringserver directly update the mseedindex time series database as it writes records to file? That would also keep the database up to date regardless of when the data arrived.
The text was updated successfully, but these errors were encountered:
Could the miniseed archiving portion of ringserver directly update the mseedindex time series database as it writes records to file?
Sure, after all it's just software!
But on a serious note: it's complicated and would be difficult to update an index in near real-time. The index is most useful and efficient when it can present a coherent picture of contiguous time series. mseedindex is designed for mostly static data sets; sure it can update when files change, but the operation is pretty heavy for applying every record written. Instead new logic would likely be better to "extend" index entries efficiently, creating when needed, and that's non-trivial.
I think the concept is a great idea, so this should be left here.
The combination of ringserver with portable-fdsnws-dataselect and mseedindex makes a nice combination for ingesting data and making it available. But having to run an separate program periodically to index miniseed files seems inefficient. Could the miniseed archiving portion of ringserver directly update the mseedindex time series database as it writes records to file? That would also keep the database up to date regardless of when the data arrived.
The text was updated successfully, but these errors were encountered: