omf-python icon indicating copy to clipboard operation
omf-python copied to clipboard

What about time-series data?

Open banesullivan opened this issue 6 years ago • 0 comments

OMF is a great format for spatially referenced information, especially static/dynamic models but I'm having difficulty conceptualizing how to store observed/collected data in the OMF format. Time series models are fairly straightforward to store as you could add a new data array on the cells/nodes for each time step, but time series data is a bit more complicated.

Take some formats of geophysical field data for example: seismic or EM methods where we have a source location, a receiver location, and a time series of data "amplitudes".

In many cases, for each time window, we will have one source location and many receiver locations for a window of a time series. How should I approach storing such a data type in the OMF format?

Motivation

Ideally, I'd like to use OMF to manage all data and models for a given project. Having the ability to store my spatially referenced observed data alongside my processing/inversion results (the models) in a single OMF project file would be of high significance. This way I could share a single OMF project file and a processing script in Python with others to easily reproduce the work in an accessible way.

banesullivan avatar Feb 28 '19 18:02 banesullivan