Seismic data is used to visualize the Earth's sub surface. This is achieved by measuring travel times of reflections from pressure waves propagating through the ground. Seismic data and interpretations of seismic data will therefore often have z values in travel time, not depth. In order to get a depth value for a travel time value, we need to do a depth conversion. A depth conversion combines the velocity of the pressure wave with the travel time to get a depth value.
Data sets may be depth converted in Geocap using the command "Velocity Model Depth Convert". This command uses a "Velocity Model" as input in order to determine the velocity of a the pressure wave.
...
A velocity model is stored as an item in your Projectproject. It represents the seismic velocities in an area , and is used as input to the "Velocity Model Depth Convert" command.
To create a new velocity model
...
In the Layer Velocity model , you may use seismic horizons as interval velocity boundaries. The horizons may be interpreted lines from 2D seismic (IHorizon or PolyData) or grids (StructuredPoints). You may set the interval velocity of each interval using a table. In the table you also need to set the top horizon of each interval. In addition you need to set the water velocity as input.
When going from top to bottom , the layer velocity model will initially use the water velocity as interval velocity until it meets the top horizon. From the top horizon , it will use the top horizon velocity as interval velocity until it meets the next horizon, and so on. continuing this pairwise matching of successive horizons for the rest of the seismic data.
During depth conversion , the interval velocities are used to calculate an average velocity.
...
In order to generate an average velocity, the velocity model will run Dix formula on the RMS velocity to generate interval velocities. An average velocity is computed from the interval velocities.
Note that the Search search radius should be big large enough so that all points where you need a velocity will have RMS points within the search radius. However if the search radius is set too big, the velocity computation for a point will include too many RMS points, and the calculation may be slow. The recommended radius will depend on the density of the RMS velocity dataset.
...