<p align="center">
<img src="https://bedrock.engineer/public/Bedrock_TextRight.png" alt="Bedrock logo" width="75%"/>
</p>
<h3 align="center">Bedrock, the Open Source Foundation for Ground Investigation Data</h3>
---
📃 **Documentation:** <https://bedrock.engineer/docs>
🖥️ **Source Code:** <https://github.com/bedrock-gi/bedrock-gi>
🐍 **`bedrock-gi` on PyPI:** <https://pypi.org/project/bedrock-gi/>
🌐 **Website:** <https://bedrock.engineer/>
🔗 **LinkedIn:** <https://www.linkedin.com/company/bedrock-gi>
---
## 🌟 Highlights
### 📖 Read / write Ground Investigation (GI) data in different formats
| Data Format | Read | Write |
|-------------|------|-------|
| AGS 3 | ✅ | ❌ |
| AGS 4 | Soon | [python-ags4](https://pypi.org/project/python-AGS4/) |
| Excel | ✅ | ✅ |
| CSV | ✅ | ✅ |
| JSON | ✅ | ✅ |
| GeoJSON | ✅ | ✅ |
What do you need? [DIGGS](https://diggsml.org/)? [NADAG](https://www.ngu.no/geologisk-kartlegging/om-nadag-nasjonal-database-grunnundersokelser)? [GEF](https://publicwiki.deltares.nl/display/STREAM/Dutch+National+GEF+Standards)? Something else?
Let us know by creating an [issue](https://github.com/bedrock-gi/bedrock-gi/issues) or starting a [discussion](https://github.com/orgs/bedrock-gi/discussions) 💭
Also, if you have a project with publicly available GI data, please share that in a [discussion](https://github.com/orgs/bedrock-gi/discussions), such that we can create a tutorial from it 🤩
### ✅ Validate your GI data
`bedrock-gi` comes with data validation to make sure that you can combine Ground Investigation data from multiple files into a single GIS database with consistent relationships between GI locations, samples, in-situ measurements and lab tests.
This data validation mechanism (based on [`pandera`](https://pandera.readthedocs.io/en/stable/)) is easily extensible, giving you the power to add your own data validation criteria 💪
### 🗺️ Put your GI data from multiple files into a single 3D GIS database
For example, you can take GI data from 100 AGS files and combine them into a single a [GeoPackage](https://en.wikipedia.org/wiki/GeoPackage) ([like a Shapefile, but then waaay better](http://switchfromshapefile.org/)). Such a GeoPackage can then be loaded into ArcGIS, such that you can visualize your GI data in 3D:
<p align="center">
<img src="https://bedrock.engineer/public/images/KaiTak_BrGI_ArcGIS.gif" alt="GI data visualization .gif in 3D in ArcGIS" width="90%"/>
</p>
### 🟦 Put your GI data into Speckle
Once you have your GI data inside [Speckle](https://speckle.systems/), it's super easy to visualize GI data together with civil engineering designs:
<p align="center">
<img src="https://bedrock.engineer/public/images/KaiTak_BrGI_Speckle.png" alt="Kai Tak, Hong Kong, data from many sources." width="56%" />
<img src="https://bedrock.engineer/public/images/BPFoundation.png" alt="Bored Pile foundation design." width="40%" />
<a href="https://app.speckle.systems/projects/013aaf06e7/models/0fa0287ba8@dfbec71408,1cbe68ed69@d3c4a34cff,44c8d1ecae@b962e2f29d,7f9d99cae2@bbed7cf165,9535541c2b@fafe06f9c0,a739490298@e858cc8cb3,ff81bfa02b@dda7c2f981" target="_blank">Click here to go to the Kai Tak Speckle project from the left image</a>
</p>
Moreover, your GI data becomes available in all the software that [Speckle has connectors for](https://app.speckle.systems/downloads).
### 🔓 Free and Open Source Software
Free and Open Source Software (FOSS) gives you full access to the code, which means you can customize `bedrock-gi` to integrate with other tools and fit your workflows & project needs.
As the name implies, FOSS is free to use, so you're not tied to expensive software licenses or locked into a specific software vendor ⛓️💥
You can give [feedback](#-feedback) and [contribute](#-contributing), such that together we together can build the tools we've always wanted and needed 🤝
## ℹ️ Overview
> **Definition of Bedrock**
>
> In an abstract sense, the main principles on which something is based. [1]
>
> In the real world, the bedrock is the hard area of rock in the ground that holds up the loose soil above. [1]
>
> In many civil engineering projects, the identification of the bedrock through digging, drilling or geophysical methods is an important task, which greatly influences (foundation) design. [2]
>
> Sources: [[1] Bedrock | Cambridge Dictionary](https://dictionary.cambridge.org/us/dictionary/english/bedrock), [[2] Bedrock | Wikipedia](https://en.wikipedia.org/wiki/Bedrock)
Bedrock, this open source software project, forms the foundation for for ground investigation data, subsurface modelling and Geo-BIM.
With Bedrock you can get your data from any Ground Investigation data format into a GIS database 🗺️, from a GIS database into Speckle 🟦, and from Speckle into all the software we work with in the AEC industry 🏗️.
The purpose of Bedrock is NOT to become THE standard for geotechnical data, because we don't need 15 instead of 14 competing standards:
<p align="center">
<img src="https://bedrock.engineer/public/images/14Become15Standards.png" alt="14 competing standards become 15 competing standards | xkcd.com/927" width="60%"/>
<br>
Source: <a href="https://xkcd.com/927/" target="_blank">https://xkcd.com/927</a>
</p>
For example, us geotechnical engineers who are used to working with AGS data know that the "ISPT group" is a table that describes an In-Situ Standard Penetration Test and we know what headings, i.e. columns that AGS group, i.e. table has. Therefore, Bedrock doesn't change that the naming of those columns. Bedrock just makes sure that the data is structured in a sensible way, such that Ground Investigation data from multiple sources can be converted into a GIS database.
A GIS database with Ground Investigation data contains tables that describe the Ground Investigation `'Project'`, the `'Location'`s where GI data was collected, the `'Sample'`s and `'InSitu'` measurements taken at these `'Location'`s, and the `'Lab'` tests that were performed on the collected `'Sample'`s.
The `'Project'`, `'Location'`, `'Sample'`, `'InSitu'` measurement and `'Lab'` test tables are related to each other: each lab test belongs to a sample, which belongs to a GI location, which belongs to a project. These relationships can be visualized in a hierarchy like this:
```bash
'Project'
└───'Location'
├───'InSitu'
└───'Sample'
└───'Lab'
```
These relationships are represented in the database tables with so-called "foreign keys". For example, the results of an Atterberg Limits Lab test, i.e. Liquid Limit and Plastic Limit tests, that originated from an AGS file would be in stored in the `'Lab_LLPL'` table. Each row in this table represents the Atterberg Limit test results performed on a specific sample. Each row knows to which project, GI location and sample it belongs through its `project_uid`, `location_uid` and `sample_uid` respectively.
This relational database ([linked tables](https://en.wikipedia.org/wiki/Relational_database)) with Ground Investigation data becomes a GIS database by assigning a (3D) GIS geometry to each of the rows in each of the database tables (except for the `'Project'` table).
## ⬇️ Installation
In case you're using `uv`, you can add `bedrock-gi` to your Python project and install it in your project's virtual environment by running:
```bash
uv add bedrock-gi
```
I would highly recommend anyone to start using [`uv`](https://docs.astral.sh/uv/) (Unified Virtual Environment Manager) if you're not already doing so. Some of the advantages (Source: [`uv`](https://docs.astral.sh/uv/)):
- 🖥️ `uv` Python projects will work on Windows, macOS and Linux.
- 🐍 `uv` [installs and manages](https://docs.astral.sh/uv/#python-management) Python versions.
- 🗂️ `uv` provides [comprehensive project management](https://docs.astral.sh/uv/#project-management), with a [universal lockfile](https://docs.astral.sh/uv/concepts/projects/#project-lockfile). This means no more headaches about virtual environments (or having to explain what on earth a virtual env is), or people running different versions of Python or Python packages on the same project, causing errors and other problems.
- In short, 🚀 `uv` is a single tool to replace `pip`, `pip-tools`, `pipx`, `poetry`, `pyenv`, `virtualenv`, `conda` and more...
It's of course also possible to install `bedrock-gi` from [PyPI](https://pypi.org/project/bedrock-gi/) (Python Packaging Index) using `pip`:
```bash
pip install bedrock-gi
```
## 💭 Feedback
Got some feedback, a great idea, running into problems when working with Bedrock or just want to ask some questions?
Please feel free to:
1. open an issue for feature requests or bug reports: [`bedrock-gi` issues](https://github.com/bedrock-gi/bedrock-gi/issues),
2. start a discussion in this GitHub repo: [Bedrock discussions](https://github.com/orgs/bedrock-gi/discussions),
3. or start a discussion on the Speckle community forum if that's more appropriate: [Speckle community forum](https://speckle.community/)
All feedback and engagement with the Bedrock community is welcome 🤗
## 👷 Contributing
🛑 Wait, please read this too!
Contributing isn't scary 😄
Contributing isn't just about writing code:
- Use Bedrock and provide [feedback](#-feedback) 🪲
- Share how you use Bedrock 🏗️
- Help each other out, e.g. by replying to questions in the [discussions](https://github.com/orgs/bedrock-gi/discussions) or [`bedrock-gi` issues](https://github.com/bedrock-gi/bedrock-gi/issues) 🤝
- Spread the word about Bedrock 🤩
- Documentation and tutorials 📃
- Most pages on the [bedrock.engineer](https://bedrock.engineer/) website can be edited, so if you see a spelling mistake or have a suggestion on how to explain something better, please smash that button! 🖱️💥
<p align="center">
<img src="https://bedrock.engineer/public/images/EditThisPage.png" alt="Edit this page on GitHub button on bedrock.engineer" width="20%"/>
</p>
- If you would like to contribute code, AWESOME! 💖
Please create an issue for what you'd like to contribute. If you don't know how to get started, please indicate this in your issue, and we'll help you out.
## 🤔 Things to Consider
### GIS Data, Projected vs Geodetic CRS's and Heights / Elevations
Ground investigation data is initially measured in Easting, Northing, z-coordinate, i.e. in a projected Coordinate Reference System (CRS).
If you want your ground investigation data to go into a GIS database, all GIS geometry needs to use the same CRS.
Therefore, if you are dealing with GI data collected using different projected CRS's, you'll have to convert the Easting, Northing, z-coordinates to global longitude, latitude, ellipsoidal height coordinates in a geodetic CRS. ([Further reading](https://clover-animantarx-a3a.notion.site/Geomatics-36dfece2dece4358b44c44d08c9cded6))
Please start a [discussion](https://github.com/orgs/bedrock-gi/discussions) or create an issue if want to be able to put data that were collected in different projected CRS's into a single GIS database. This is pretty easy with [`geopandas`](https://geopandas.org/en/stable/) / [`pyproj`](https://pyproj4.github.io/pyproj/stable/) transformations, but hasn't been necessary yet.
## ✍️ Author
Hi, I'm Joost Gevaert 👋
I studied geotechnical engineering and applied geophysics and then worked for [Arup](https://www.arup.com/) for 4 as a geotechnical engineer an computational designer.
During my time at Arup I worked a lot on bringing computational design into the world of geotechnical engineering, and on [bridging the gaps between geotechnical engineering and structural engineering](https://www.linkedin.com/posts/joost-gevaert_lightbim-lightbim-lightbim-activity-7234726439835549697-3xdO).
Bedrock is the Free and Open Source Software (FOSS) that I wish existed when I worked as a geotechnical engineer at Arup.
> Computational design is a field that involves the use of computer algorithms, simulations, and data analysis to support and enhance the design process. It enables designers to explore vast design spaces, to find solutions to complex design problems, and to make informed decisions based on data-driven insights.
> Source: [Computational design | Arup](https://www.arup.com/services/computational-and-parametric-design/)
Raw data
{
"_id": null,
"home_page": null,
"name": "bedrock-gi",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.9",
"maintainer_email": null,
"keywords": "aec, ags, bedrock, bim, engineering geology, geo-bim, geotech, geotechnical data, geotechnical engineering, gi data, gis, ground engineering, ground investigation, ground investigation data",
"author": null,
"author_email": "Bedrock <info@bedrock.engineer>",
"download_url": "https://files.pythonhosted.org/packages/60/d6/44817a51c21331ae348ffaae1449f7ca57ee65978e8f4e14ada229b315ff/bedrock_gi-0.1.2.tar.gz",
"platform": null,
"description": "<p align=\"center\">\n <img src=\"https://bedrock.engineer/public/Bedrock_TextRight.png\" alt=\"Bedrock logo\" width=\"75%\"/>\n</p>\n\n<h3 align=\"center\">Bedrock, the Open Source Foundation for Ground Investigation Data</h3>\n\n---\n\n\ud83d\udcc3 **Documentation:** <https://bedrock.engineer/docs>\n\n\ud83d\udda5\ufe0f **Source Code:** <https://github.com/bedrock-gi/bedrock-gi>\n\n\ud83d\udc0d **`bedrock-gi` on PyPI:** <https://pypi.org/project/bedrock-gi/>\n\n\ud83c\udf10 **Website:** <https://bedrock.engineer/>\n\n\ud83d\udd17 **LinkedIn:** <https://www.linkedin.com/company/bedrock-gi>\n\n---\n\n## \ud83c\udf1f Highlights\n\n### \ud83d\udcd6 Read / write Ground Investigation (GI) data in different formats\n\n| Data Format | Read | Write |\n|-------------|------|-------|\n| AGS 3 | \u2705 | \u274c |\n| AGS 4 | Soon | [python-ags4](https://pypi.org/project/python-AGS4/) |\n| Excel | \u2705 | \u2705 |\n| CSV | \u2705 | \u2705 |\n| JSON | \u2705 | \u2705 |\n| GeoJSON | \u2705 | \u2705 |\n\nWhat do you need? [DIGGS](https://diggsml.org/)? [NADAG](https://www.ngu.no/geologisk-kartlegging/om-nadag-nasjonal-database-grunnundersokelser)? [GEF](https://publicwiki.deltares.nl/display/STREAM/Dutch+National+GEF+Standards)? Something else? \nLet us know by creating an [issue](https://github.com/bedrock-gi/bedrock-gi/issues) or starting a [discussion](https://github.com/orgs/bedrock-gi/discussions) \ud83d\udcad\n\nAlso, if you have a project with publicly available GI data, please share that in a [discussion](https://github.com/orgs/bedrock-gi/discussions), such that we can create a tutorial from it \ud83e\udd29\n\n### \u2705 Validate your GI data\n\n`bedrock-gi` comes with data validation to make sure that you can combine Ground Investigation data from multiple files into a single GIS database with consistent relationships between GI locations, samples, in-situ measurements and lab tests.\n\nThis data validation mechanism (based on [`pandera`](https://pandera.readthedocs.io/en/stable/)) is easily extensible, giving you the power to add your own data validation criteria \ud83d\udcaa\n\n### \ud83d\uddfa\ufe0f Put your GI data from multiple files into a single 3D GIS database\n\nFor example, you can take GI data from 100 AGS files and combine them into a single a [GeoPackage](https://en.wikipedia.org/wiki/GeoPackage) ([like a Shapefile, but then waaay better](http://switchfromshapefile.org/)). Such a GeoPackage can then be loaded into ArcGIS, such that you can visualize your GI data in 3D:\n\n<p align=\"center\">\n <img src=\"https://bedrock.engineer/public/images/KaiTak_BrGI_ArcGIS.gif\" alt=\"GI data visualization .gif in 3D in ArcGIS\" width=\"90%\"/>\n</p>\n\n### \ud83d\udfe6 Put your GI data into Speckle\n\nOnce you have your GI data inside [Speckle](https://speckle.systems/), it's super easy to visualize GI data together with civil engineering designs:\n\n<p align=\"center\">\n <img src=\"https://bedrock.engineer/public/images/KaiTak_BrGI_Speckle.png\" alt=\"Kai Tak, Hong Kong, data from many sources.\" width=\"56%\" />\n <img src=\"https://bedrock.engineer/public/images/BPFoundation.png\" alt=\"Bored Pile foundation design.\" width=\"40%\" />\n <a href=\"https://app.speckle.systems/projects/013aaf06e7/models/0fa0287ba8@dfbec71408,1cbe68ed69@d3c4a34cff,44c8d1ecae@b962e2f29d,7f9d99cae2@bbed7cf165,9535541c2b@fafe06f9c0,a739490298@e858cc8cb3,ff81bfa02b@dda7c2f981\" target=\"_blank\">Click here to go to the Kai Tak Speckle project from the left image</a>\n</p>\n\nMoreover, your GI data becomes available in all the software that [Speckle has connectors for](https://app.speckle.systems/downloads).\n\n### \ud83d\udd13 Free and Open Source Software\n\nFree and Open Source Software (FOSS) gives you full access to the code, which means you can customize `bedrock-gi` to integrate with other tools and fit your workflows & project needs.\n\nAs the name implies, FOSS is free to use, so you're not tied to expensive software licenses or locked into a specific software vendor \u26d3\ufe0f\u200d\ud83d\udca5\n\nYou can give [feedback](#-feedback) and [contribute](#-contributing), such that together we together can build the tools we've always wanted and needed \ud83e\udd1d\n\n## \u2139\ufe0f Overview\n\n> **Definition of Bedrock**\n>\n> In an abstract sense, the main principles on which something is based. [1]\n>\n> In the real world, the bedrock is the hard area of rock in the ground that holds up the loose soil above. [1]\n>\n> In many civil engineering projects, the identification of the bedrock through digging, drilling or geophysical methods is an important task, which greatly influences (foundation) design. [2] \n>\n> Sources: [[1] Bedrock | Cambridge Dictionary](https://dictionary.cambridge.org/us/dictionary/english/bedrock), [[2] Bedrock | Wikipedia](https://en.wikipedia.org/wiki/Bedrock)\n\nBedrock, this open source software project, forms the foundation for for ground investigation data, subsurface modelling and Geo-BIM.\n\nWith Bedrock you can get your data from any Ground Investigation data format into a GIS database \ud83d\uddfa\ufe0f, from a GIS database into Speckle \ud83d\udfe6, and from Speckle into all the software we work with in the AEC industry \ud83c\udfd7\ufe0f.\n\nThe purpose of Bedrock is NOT to become THE standard for geotechnical data, because we don't need 15 instead of 14 competing standards:\n\n<p align=\"center\">\n <img src=\"https://bedrock.engineer/public/images/14Become15Standards.png\" alt=\"14 competing standards become 15 competing standards | xkcd.com/927\" width=\"60%\"/>\n <br>\n Source: <a href=\"https://xkcd.com/927/\" target=\"_blank\">https://xkcd.com/927</a>\n</p> \n\nFor example, us geotechnical engineers who are used to working with AGS data know that the \"ISPT group\" is a table that describes an In-Situ Standard Penetration Test and we know what headings, i.e. columns that AGS group, i.e. table has. Therefore, Bedrock doesn't change that the naming of those columns. Bedrock just makes sure that the data is structured in a sensible way, such that Ground Investigation data from multiple sources can be converted into a GIS database.\n\nA GIS database with Ground Investigation data contains tables that describe the Ground Investigation `'Project'`, the `'Location'`s where GI data was collected, the `'Sample'`s and `'InSitu'` measurements taken at these `'Location'`s, and the `'Lab'` tests that were performed on the collected `'Sample'`s.\n\nThe `'Project'`, `'Location'`, `'Sample'`, `'InSitu'` measurement and `'Lab'` test tables are related to each other: each lab test belongs to a sample, which belongs to a GI location, which belongs to a project. These relationships can be visualized in a hierarchy like this:\n\n```bash\n'Project'\n \u2514\u2500\u2500\u2500'Location'\n \u251c\u2500\u2500\u2500'InSitu'\n \u2514\u2500\u2500\u2500'Sample'\n \u2514\u2500\u2500\u2500'Lab'\n```\n\nThese relationships are represented in the database tables with so-called \"foreign keys\". For example, the results of an Atterberg Limits Lab test, i.e. Liquid Limit and Plastic Limit tests, that originated from an AGS file would be in stored in the `'Lab_LLPL'` table. Each row in this table represents the Atterberg Limit test results performed on a specific sample. Each row knows to which project, GI location and sample it belongs through its `project_uid`, `location_uid` and `sample_uid` respectively.\n\nThis relational database ([linked tables](https://en.wikipedia.org/wiki/Relational_database)) with Ground Investigation data becomes a GIS database by assigning a (3D) GIS geometry to each of the rows in each of the database tables (except for the `'Project'` table).\n\n## \u2b07\ufe0f Installation\n\nIn case you're using `uv`, you can add `bedrock-gi` to your Python project and install it in your project's virtual environment by running:\n\n```bash\nuv add bedrock-gi\n```\n\nI would highly recommend anyone to start using [`uv`](https://docs.astral.sh/uv/) (Unified Virtual Environment Manager) if you're not already doing so. Some of the advantages (Source: [`uv`](https://docs.astral.sh/uv/)):\n\n- \ud83d\udda5\ufe0f `uv` Python projects will work on Windows, macOS and Linux.\n- \ud83d\udc0d `uv` [installs and manages](https://docs.astral.sh/uv/#python-management) Python versions.\n- \ud83d\uddc2\ufe0f `uv` provides [comprehensive project management](https://docs.astral.sh/uv/#project-management), with a [universal lockfile](https://docs.astral.sh/uv/concepts/projects/#project-lockfile). This means no more headaches about virtual environments (or having to explain what on earth a virtual env is), or people running different versions of Python or Python packages on the same project, causing errors and other problems.\n- In short, \ud83d\ude80 `uv` is a single tool to replace `pip`, `pip-tools`, `pipx`, `poetry`, `pyenv`, `virtualenv`, `conda` and more...\n\nIt's of course also possible to install `bedrock-gi` from [PyPI](https://pypi.org/project/bedrock-gi/) (Python Packaging Index) using `pip`:\n\n```bash\npip install bedrock-gi\n```\n\n## \ud83d\udcad Feedback\n\nGot some feedback, a great idea, running into problems when working with Bedrock or just want to ask some questions?\n\nPlease feel free to:\n\n1. open an issue for feature requests or bug reports: [`bedrock-gi` issues](https://github.com/bedrock-gi/bedrock-gi/issues),\n2. start a discussion in this GitHub repo: [Bedrock discussions](https://github.com/orgs/bedrock-gi/discussions),\n3. or start a discussion on the Speckle community forum if that's more appropriate: [Speckle community forum](https://speckle.community/)\n\nAll feedback and engagement with the Bedrock community is welcome \ud83e\udd17\n\n## \ud83d\udc77 Contributing\n\n\ud83d\uded1 Wait, please read this too!\n\nContributing isn't scary \ud83d\ude04\n\nContributing isn't just about writing code:\n\n- Use Bedrock and provide [feedback](#-feedback) \ud83e\udeb2\n- Share how you use Bedrock \ud83c\udfd7\ufe0f\n- Help each other out, e.g. by replying to questions in the [discussions](https://github.com/orgs/bedrock-gi/discussions) or [`bedrock-gi` issues](https://github.com/bedrock-gi/bedrock-gi/issues) \ud83e\udd1d\n- Spread the word about Bedrock \ud83e\udd29\n- Documentation and tutorials \ud83d\udcc3\n- Most pages on the [bedrock.engineer](https://bedrock.engineer/) website can be edited, so if you see a spelling mistake or have a suggestion on how to explain something better, please smash that button! \ud83d\uddb1\ufe0f\ud83d\udca5\n \n<p align=\"center\">\n <img src=\"https://bedrock.engineer/public/images/EditThisPage.png\" alt=\"Edit this page on GitHub button on bedrock.engineer\" width=\"20%\"/>\n</p>\n\n- If you would like to contribute code, AWESOME! \ud83d\udc96 \n Please create an issue for what you'd like to contribute. If you don't know how to get started, please indicate this in your issue, and we'll help you out.\n\n## \ud83e\udd14 Things to Consider\n\n### GIS Data, Projected vs Geodetic CRS's and Heights / Elevations\n\nGround investigation data is initially measured in Easting, Northing, z-coordinate, i.e. in a projected Coordinate Reference System (CRS).\n\nIf you want your ground investigation data to go into a GIS database, all GIS geometry needs to use the same CRS.\n\nTherefore, if you are dealing with GI data collected using different projected CRS's, you'll have to convert the Easting, Northing, z-coordinates to global longitude, latitude, ellipsoidal height coordinates in a geodetic CRS. ([Further reading](https://clover-animantarx-a3a.notion.site/Geomatics-36dfece2dece4358b44c44d08c9cded6))\n\nPlease start a [discussion](https://github.com/orgs/bedrock-gi/discussions) or create an issue if want to be able to put data that were collected in different projected CRS's into a single GIS database. This is pretty easy with [`geopandas`](https://geopandas.org/en/stable/) / [`pyproj`](https://pyproj4.github.io/pyproj/stable/) transformations, but hasn't been necessary yet.\n\n## \u270d\ufe0f Author\n\nHi, I'm Joost Gevaert \ud83d\udc4b\n\nI studied geotechnical engineering and applied geophysics and then worked for [Arup](https://www.arup.com/) for 4 as a geotechnical engineer an computational designer.\n\nDuring my time at Arup I worked a lot on bringing computational design into the world of geotechnical engineering, and on [bridging the gaps between geotechnical engineering and structural engineering](https://www.linkedin.com/posts/joost-gevaert_lightbim-lightbim-lightbim-activity-7234726439835549697-3xdO).\n\nBedrock is the Free and Open Source Software (FOSS) that I wish existed when I worked as a geotechnical engineer at Arup.\n\n> Computational design is a field that involves the use of computer algorithms, simulations, and data analysis to support and enhance the design process. It enables designers to explore vast design spaces, to find solutions to complex design problems, and to make informed decisions based on data-driven insights. \n> Source: [Computational design | Arup](https://www.arup.com/services/computational-and-parametric-design/)\n",
"bugtrack_url": null,
"license": "Apache Software License (Apache 2.0)",
"summary": "Bedrock, the Open Source Foundation for Ground Investigation Data",
"version": "0.1.2",
"project_urls": {
"Documentation": "https://bedrock.engineer/docs/",
"Homepage": "https://bedrock.engineer/",
"Source": "https://github.com/bedrock-gi/bedrock-gi",
"Tracker": "https://github.com/bedrock-gi/bedrock-gi/issues"
},
"split_keywords": [
"aec",
" ags",
" bedrock",
" bim",
" engineering geology",
" geo-bim",
" geotech",
" geotechnical data",
" geotechnical engineering",
" gi data",
" gis",
" ground engineering",
" ground investigation",
" ground investigation data"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "f9eac2d5bf69651e154adeb2e94ab77bee3b5bdc8cc01a282e3d3175963dc24d",
"md5": "124f528612424bd8bc74456be068a7f1",
"sha256": "f65403d1ce1f2446a87d4203463826221218569332b125731a0601dfb7420d75"
},
"downloads": -1,
"filename": "bedrock_gi-0.1.2-py3-none-any.whl",
"has_sig": false,
"md5_digest": "124f528612424bd8bc74456be068a7f1",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.9",
"size": 93444,
"upload_time": "2024-10-31T09:35:43",
"upload_time_iso_8601": "2024-10-31T09:35:43.600364Z",
"url": "https://files.pythonhosted.org/packages/f9/ea/c2d5bf69651e154adeb2e94ab77bee3b5bdc8cc01a282e3d3175963dc24d/bedrock_gi-0.1.2-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "60d644817a51c21331ae348ffaae1449f7ca57ee65978e8f4e14ada229b315ff",
"md5": "18e2a2e7623a4804812294bcb7d4346d",
"sha256": "1e9f66386901c4f0a5214c439224711d74bcdcadd5c62790b803db2441c9152d"
},
"downloads": -1,
"filename": "bedrock_gi-0.1.2.tar.gz",
"has_sig": false,
"md5_digest": "18e2a2e7623a4804812294bcb7d4346d",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.9",
"size": 24624182,
"upload_time": "2024-10-31T09:35:49",
"upload_time_iso_8601": "2024-10-31T09:35:49.786346Z",
"url": "https://files.pythonhosted.org/packages/60/d6/44817a51c21331ae348ffaae1449f7ca57ee65978e8f4e14ada229b315ff/bedrock_gi-0.1.2.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-10-31 09:35:49",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "bedrock-gi",
"github_project": "bedrock-gi",
"travis_ci": false,
"coveralls": false,
"github_actions": false,
"lcname": "bedrock-gi"
}
JSON
