Submitted as: development and technical paper 22 Jan 2021
Submitted as: development and technical paper | 22 Jan 2021
Automated geological map deconstruction for 3D model construction
- 1Mineral Exploration Cooperative Research Centre, Centre for Exploration Targeting, School of Earth Sciences, The University of Western Australia, Perth, Australia
- 2International Centre for Radio Astronomy Research, The University of Western Australia, Perth, Australia
- 3School of Earth, Atmosphere and Environment, Monash University
- 4Computational Geoscience and Reservoir Engineering, RWTH Aachen, Germany
- 5CSIRO, Mineral Resources – Discovery, ARRC, Kensington WA, Australia
- 6ARC Centre of Excellence for all Sky Astrophysics in 3 Dimensions (ASTRO 3D)
- 1Mineral Exploration Cooperative Research Centre, Centre for Exploration Targeting, School of Earth Sciences, The University of Western Australia, Perth, Australia
- 2International Centre for Radio Astronomy Research, The University of Western Australia, Perth, Australia
- 3School of Earth, Atmosphere and Environment, Monash University
- 4Computational Geoscience and Reservoir Engineering, RWTH Aachen, Germany
- 5CSIRO, Mineral Resources – Discovery, ARRC, Kensington WA, Australia
- 6ARC Centre of Excellence for all Sky Astrophysics in 3 Dimensions (ASTRO 3D)
Abstract. We present two Python libraries (map2loop and map2model) which combine the observations available in digital geological maps with conceptual information, including assumptions regarding the subsurface extent of faults and plutons to provide sufficient constraints to build a reasonable 3D geological model. At a regional scale, the best predictor for the 3D geology of the near-subsurface is often the information contained in a geological map. This remains true even after recognising that a map is also a model, with all the potential for hidden biases that this model
status implies. One challenge we face is the difficulty in reproducibly preparing input data for 3D geological models. The information stored in a map falls into three categories of geometric data: positional data such as the position of faults, intrusive and stratigraphic contacts; gradient data, such as the dips of contacts or faults and topological data, such as the age relationships of faults and stratigraphic units, or their adjacency relationships. This work is being conducted within the Loop Consortium, in which algorithms are being developed that allow automatic deconstruction of a geological map to recover the necessary positional, gradient and topological data as inputs to different 3D geological modelling codes. This automation provides significant advantages: it reduces the time to first prototype models; it clearly separates the primary data from subsets produced from filtering via data reduction and conceptual constraints; and provides a homogenous pathway to sensitivity analysis, uncertainty quantification and Value of Information studies. We use the example of the re-folded and faulted Hamersley Basin in Western Australia to demonstrate a complete workflow from data extraction to 3D modelling using two different Open Source 3D modelling engines: GemPy and LoopStructural.
Mark Jessell et al.
Status: open (until 19 Mar 2021)
-
AC1: 'Comment on gmd-2020-400', Mark Jessell, 04 Feb 2021
reply
My Apologies, somehow Yohan de Rose was left off the author list, will be fixed in the next revision!
-
EC1: 'Reply on AC1', Thomas Poulet, 05 Feb 2021
reply
Dear authors,
Thank you for letting us know, this won't be a problem.
Best regards,
Thomas Poulet
-
EC1: 'Reply on AC1', Thomas Poulet, 05 Feb 2021
reply
-
CEC1: 'Comment on gmd-2020-400', Astrid Kerkweg, 26 Feb 2021
reply
Dear authors,
in my role as Executive editor of GMD, I would like to bring to your attention our Editorial version 1.2:
https://www.geosci-model-dev.net/12/2215/2019/
This highlights some requirements of papers published in GMD, which is
also available on the GMD website in the ‘Manuscript Types’ section:
http://www.geoscientific-model-development.net/submission/manuscript_types.html
In particular, please note that for your paper, the following requirement has not been met in the Discussions paper:
- "The main paper must give the model name and version number (or other unique identifier) in the title."
Please add the names and version numbers of the 2 python libraries to the title of you manuscript.
The code availability section would improve much, if you would find a few words of what is found in the zenodo archives.
Yours,
Astrid Kerkweg
-
AC2: 'Reply on CEC1', Mark Jessell, 03 Mar 2021
reply
Thanks, I missed that, in which case the title should be:
map2loop 1.0: Automated geological map deconstruction for 3D model construction
Mark Jessell et al.
Model code and software
map2loop code Mark Jessell and Yohan de Rose https://doi.org/10.5281/zenodo.4288476
Mark Jessell et al.
Viewed
HTML | XML | Total | BibTeX | EndNote | |
---|---|---|---|---|---|
273 | 72 | 12 | 357 | 3 | 4 |
- HTML: 273
- PDF: 72
- XML: 12
- Total: 357
- BibTeX: 3
- EndNote: 4
Viewed (geographical distribution)
Country | # | Views | % |
---|
Total: | 0 |
HTML: | 0 |
PDF: | 0 |
XML: | 0 |
- 1