52 Things You Should Know About Geocomputing
This is a second attempt at collecting 52 essays about geocomputing. Here's the original call for papers, from a little over 2 years ago. This time we can do it!
Authors, please see Submitting an essay.
Reviewers, please see Reviewing submissions.
| Thing | Author | Working title | Reviewed by |
|---|---|---|---|
| 1 | Martin Bentley | In praise of small tools | |
| 2 | Martin Bentley | Best Practices are not the best... | |
| 3 | Austin Bingham | Domain-driven design in geocomputing | |
| 4 | Ben Bougher | Am = d: a linear algebra approach... | |
| 5 | Bert Bril | Putting colours on data | |
| 6 | Jesper Dramsch | General purpose GPU programming | |
| 7 | Chris Ennen | Software, software everywhere | |
| 8 | Sergey Fomel | Reproducible research | |
| 9 | GRAM | Seismic data encryption | |
| 10 | Dave Hale | My favourite 10 line program | |
| 11 | John Leeman | Hardware is hard: teaching geotech | |
| 12 | Bill Menger | The steady advance of Linux | |
| 13 | Bill Menger | Software challenges in oil & gas | |
| 14 | Matteo Niccoli | A fault colourmap prototype | |
| 15 | Steve Purves | Learn JavaScript! | |
| 16 | Alan Richardson | Use standard file & problem formats | |
| 17 | Alberto Rusic | I hate computers 1 | |
| 18 | Alberto Rusic | I hate computers 2 | |
| 19 | Hassan Sabirin | Quality checking spatial data | |
| 20 | James Selvage | Serverless computing | |
| 21 | Andrew D. Steen | Teaching geoscientists to code | |
| 22 | Martin Storey | De profundis: of well depth | |
| 23 | John Thurmond | The tyranny of formats | |
| 24 | Florian Wellmann | A Geological Model is a Hypothesis |
If you have a topic you wish someone would write about, please add it here:
- Three ways to get started in geocomputing.
- Drop everything and learn X (Julia? Clojure?).
- Getting started in HPC in 3 easy steps.
- Only a quantum computer can do geology.
- Geocomputing at enterprise scale.
- Open sourcing a corporate software project.
- Data standards, lol.
- Geocomputing in the year 2028.
- Teaching geoscientists to code: Everything Drew Steen said is wrong
- Thank you for the state-of-the-art processing, I will now proceed to interpret it incorrectly.
- Units -sigh- let's start using pint (like metpy), astropy, or something.
- How tech ubiquity is changing geoscientific observation.
- 5 libraries for geophysicists: obspy, madagascar, simpeg, vispy, etc.
- 5 libraries for geologists: pynoddy, qgis, pygmt, pandas/welly/striplog, etc.
- 5 libraries for geobiologists: dplyr, magrittr (maybe), tidyr, vegan, ggplot2
If you want to tell others what you're writing on, or find a co-author!, please add your topic here:
| Author | Topic or working title |
|---|---|
| Matt Hall | Hackathons and similar events |
| Matt Hall | What's so special about geoscience? |
| Evan Bianco | Something something |
| Justin Gosses | Standing on the shoulders of the guy in the UK office |
| Paige Bailey | Machine learning opportunities in the geosciences |