{"id":20219942,"url":"https://github.com/cgre-aachen/remote-geomod","last_synced_at":"2025-10-13T11:16:04.938Z","repository":{"id":79190829,"uuid":"114757716","full_name":"cgre-aachen/remote-geomod","owner":"cgre-aachen","description":"Coupling remote geological mapping in Google Earth with direct 3D geological modeling in GemPy.","archived":false,"fork":false,"pushed_at":"2018-06-28T17:03:49.000Z","size":44571,"stargazers_count":21,"open_issues_count":10,"forks_count":7,"subscribers_count":6,"default_branch":"master","last_synced_at":"2025-10-13T11:16:00.834Z","etag":null,"topics":["3d-modelling","geology","google-earth","mapping"],"latest_commit_sha":null,"homepage":"","language":"Jupyter Notebook","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/cgre-aachen.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE.txt","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2017-12-19T11:34:01.000Z","updated_at":"2025-03-16T20:54:51.000Z","dependencies_parsed_at":"2023-02-28T13:30:59.485Z","dependency_job_id":null,"html_url":"https://github.com/cgre-aachen/remote-geomod","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/cgre-aachen/remote-geomod","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cgre-aachen%2Fremote-geomod","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cgre-aachen%2Fremote-geomod/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cgre-aachen%2Fremote-geomod/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cgre-aachen%2Fremote-geomod/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/cgre-aachen","download_url":"https://codeload.github.com/cgre-aachen/remote-geomod/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cgre-aachen%2Fremote-geomod/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":279014760,"owners_count":26085593,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-10-13T02:00:06.723Z","response_time":61,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["3d-modelling","geology","google-earth","mapping"],"created_at":"2024-11-14T06:44:21.204Z","updated_at":"2025-10-13T11:16:04.910Z","avatar_url":"https://github.com/cgre-aachen.png","language":"Jupyter Notebook","funding_links":[],"categories":[],"sub_categories":[],"readme":"# remote-geomod\n\n![Python 3](https://img.shields.io/badge/Python-3-blue.svg)\n[![License: LGPL v3](https://img.shields.io/badge/License-LGPL%20v3-blue.svg)](https://www.gnu.org/licenses/lgpl-3.0)\n\n\u003e Coupling remote geological mapping in Google Earth with direct 3D geological modeling \nin GemPy.\n\n## Introduction\n\n## Example\n\nThe best way to get started is actually to go through the example in the book chapter - this is currently in review and more information will (hopefully) be provided here, soon!\n\n## Installation\n\nNext to remote-geomod, you will require two additional major software components: (1) \n[Google Earth Pro](https://www.google.com/earth/desktop/) for remote mapping and (2) a Python \ndistribution with specific software libraries. The software libraries remote-geomod relies on can be difficult to\ninstall on certain systems. Because of this we provide you with two possible installation paths that will take care\nof installing the dependecies:\n\n * Using the open-source **Anaconda** Python distribution which allows convenient, automated installation of the \n dependencies. \n * A local installation inside of a **Docker** environment, for wich we can directly ship all dependencies insode\n of a Docker image. We recommend this installation path for users familiar with using Dokcer of if the above one fails.\n\n### Installation using Anaconda\n\nAs a first step you need to download the Anaconda Python Distribution on your system. Make sure to select the correct \nPython 3.6 version for your operating system and install it (a comprehensive user guide with installation \ninstructions can be found on the [Conda Documentation website](https://conda.io/docs/user-guide/install/)).\n \nThe next step is to either download and unpack the remote-geomod repository, or to directly clone it using your \ncommand-line tool of choice:\n \n    git clone https://github.com/cgre-aachen/remote-geomod.git\n\nOnce you have a local copy of the repository on your computer, you have to create a new Conda environment. You can \neither do this using your command-line tool (1) or the Anaconda Navigator (2): \n\n1. Open your command-line tool in the downloaded or cloned remote-geomod folder and run \n``conda env create -n rgeomod -f environment.yml``. Afterwards you can activate the environment with the command \n``activate rgeomod`` (Windows) or ``source activate rgeomod`` (macOS, Linux) or in your Anaconda Navigator.\n2. For the latter option start the Anaconda Navigator, select ``Environments`` in the navigation bar on the left-hand \nside, then click ``Import`` at the bottom of the window and browse for the ``environment.yml`` file located in the \nremote-geomod folder and give the environment the same name. This will create a separate Conda environment and install \nall necessary dependencies automatically. Once the installation finished, make sure you have selected the newly \ncreated environment.\n\n### Dependencies\n\nremote-geomod uses Python 3 and has several dependencies for numerical operations, geographical data operations, \ngeological modeling and visualization. All dependencies can be found in the  `environment.yml` file:\n\n````\ndependencies:\n  - python=3.6\n  - numpy\n  - conda-forge::gdal\n  - clinicalgraphics::vtk\n  - theano=1.0.1\n  - jupyter\n  - nb_conda\n  - matplotlib\n  - pandas\n  - seaborn\n  - scikit-image\n  - tqdm\n  - pip:\n    - mplstereonet\n    - gempy\n````\n\nWe also provide precompiled Docker images hosted on Docker Hub with all necessary dependencies to get remote-geomod up\nand running. \n\n### Installation using Docker\n\nDocker is an operating-system-level-visualization software,\nmeaning that we can package a tiny operating system with pre-installed\nsoftware into a Docker image. This Docker image can then be shared\nwith and run by others, enabling them to use intricate dependencies\nwith just a few commands. For this to work the user needs to have a\nworking [Docker](https://www.docker.com/) installation.\n\n#### (a) Pull Docker image from DockerHub\n\nThe easiest way to get remote-geomod running is by running the pre-compiled Docker image (containing everything you\nneed) directly from the cloud service Docker Hub to get a locally running Docker container. Make sure to set your \nDocker daemon to Linux containers in Docker's context menu.\n\n    docker run -it -p 8888:8888 cgreaachen/rgeomod_complete\n    \nThis will automatically pull the Docker image from Docker Hub and run it, opening a command line shell inside of the\nrunning Docker container. There you have access to the file system inside of the container. Note that this pre-compiled\nDocker image already contains the rgeomod repository. As rgeomod is undergoing active development, we can not \nguarantee that this Docker image always contains the latest release version.\n\nIf you just want the dependencies:\n\n    docker run -it -p 8888:8888 cgreaachen/rgeomod_dependencies\n\nAlternatively, you can also build the Docker image yourself from the Dockerfile provided with the repository by running\n``docker build . -t \u003cimage-tag\u003e`` in its root directory. Once the Docker image is built you can look up it's image-id \nusing ``docker images``. Then, instead of using the DockerHub repository name, you can run the Docker image by using\nits id: ``docker run -it -p 888:8888 \u003cimage-id\u003e``.\n\n## Getting started\n\nA good way to get started is to follow the steps in the publication (see below) and to run the jupyter notebooks, supplied with this package.\n\n## References\n\nWellmann, F., A. Schaaf and C. von Hagke: \"From GoogleEarth to 3-D Geology Problem 2: Seeing below the surface of the Digital Earth\". Submitted as book chapter for \"Structural Geology and Tectonics: Problems and Solutions\".\n\n## Contact\n\nThis library is developed by LuFG Computational Geoscience and Reservoir Engineering (CGRE) at RWTH Aachen University, Germany.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcgre-aachen%2Fremote-geomod","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fcgre-aachen%2Fremote-geomod","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcgre-aachen%2Fremote-geomod/lists"}