This is an experiment in using software development processes like source control and a one step build for a seismic interpretation project.
Check out the build output for the 2D survey map.
You can run this experiment on your own machine, or a cloud development environment.
- Clone in Cloud9
- In the terminal run:
npm install
jake
You need the following tools installed:
From the command line:
git clone https://github.com/softwareunderground/TeapotDome.git
cd TeapotDome
npm install
npm run build
After cloning, observe that files that represent source field data are inside the source directory. While code and byproducts are outside of that directory.
Try changing X and Y values in /source/2D_Seismic/2DNavigationLinesA-E.txt.
Then run npm run build again (or just jake if on Cloud9). Observe that the GEOjson was regenerated. (Hint: use git diff.)
Then, run the build a second time without making changes. Observe that the build did not need to update the GEOjson file.
The idea is that dependent data can be updated in a single step when new input data is updated. (Doing this in an even more automatic fashion is called Build Automation.)
Teapot Dome data being used to demonstrate this process is courtesy of RMOTC and the U.S. Department of Energy.
This experiment was started at the 2015 Geophysics Hackathon.
Looking at .gitattributes you see that SEG-Y files are associated with git Large File Storage. This was accomplished with the following command:
git lfs track "*.sgy" "*.segy"
The 3D survey is not yet in this repo because GitHub restricts even large files to 100MB.
From 2DNavigationLinesA-E.txt we find that the XY values are in the NAD27 State Plane for Wyoming East Central.
The build generates a geoJSON file GitHub can easily display converted to WGS84 degrees.
Using EarthPoint.us we can check a conversion. We expect something like: 804635, 935826 -> 42.1527484°, -109.2056781°.