bedrock-ge 0.2.2__tar.gz → 0.2.3__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/PKG-INFO +17 -17
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/README.md +16 -16
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/RELEASE.md +4 -4
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/examples/README.md +6 -0
- bedrock_ge-0.2.3/examples/hk_kaitak_ags3/hk_kaitak_ags3_to_brgi_geodb.ipynb +5491 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/examples/hk_kaitak_ags3/hk_kaitak_ags3_to_brgi_geodb.py +5 -5
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/pyproject.toml +18 -1
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/src/bedrock_ge/__init__.py +1 -1
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/src/bedrock_ge/gi/ags/read.py +5 -7
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/src/bedrock_ge/gi/ags/transform.py +36 -2
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/src/bedrock_ge/gi/ags/validate.py +1 -2
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/src/bedrock_ge/gi/concatenate.py +5 -5
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/src/bedrock_ge/gi/gis_geometry.py +67 -22
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/src/bedrock_ge/gi/validate.py +82 -16
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/src/bedrock_ge/gi/write.py +19 -16
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/tests/test_gi.py +2 -4
- bedrock_ge-0.2.2/examples/hk_kaitak_ags3/hk_kaitak_ags3_to_brgi_geodb.ipynb +0 -6335
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/.gitattributes +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/.gitignore +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/.python-version +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/LICENSE +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/examples/hk_kaitak_ags3/64475_ASD012162.ags +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/examples/hk_kaitak_ags3/kaitak_ags3.zip +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/examples/hk_kaitak_ags3/kaitak_gi.gpkg +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/mypy.ini +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/ags3_to_gis.ipynb +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/bedrock_gi_to_speckle.ipynb +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/data_validation/README.md +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/data_validation/bedrock-data-package-schema.json +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/data_validation/bedrock_sql_model.ipynb +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/data_validation/frictionless-table-schema.json +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/data_validation/jsonschema_to_tableschema.py +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/data_validation/my-pandera-schema.json +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/data_validation/pandera-plus-schema.json +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/data_validation/sqlalchemy_to_json.py +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/data_validation/sqlmodel_tutorial.py +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/data_validation/try_pandera.ipynb +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/diggs/AGS Example Template.xml +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/diggs/DIGGS1-DIGGS.XML +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/diggs/DIGGS1.ags +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/hk_ags3/link_insitu_lab_gi/giu_metadata_main.csv +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/hk_ags3/link_insitu_lab_gi/giu_metadata_rel_rep.csv +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/leapfrog_weka_hills/boreholes/Geol.csv +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/leapfrog_weka_hills/boreholes/Location.csv +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/leapfrog_weka_hills/boreholes/SPT.csv +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/leapfrog_weka_hills/cpt/CPT.csv +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/leapfrog_weka_hills/cpt/Location.csv +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/sandbox/leapfrog_weka_hills/leapfrog_csv_to_gis.ipynb +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/src/bedrock_ge/gi/__init__.py +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/src/bedrock_ge/gi/ags/__init__.py +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/src/bedrock_ge/gi/ags/ags3_data_dictionary.json +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/src/bedrock_ge/gi/ags/ags4_data_dictionary.json +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/src/bedrock_ge/gi/ags/schemas.py +0 -0
- /bedrock_ge-0.2.2/src/bedrock_ge/gi/bedrock-gi-schema.json → /bedrock_ge-0.2.3/src/bedrock_ge/gi/brgi-schema.json +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/src/bedrock_ge/gi/schemas.py +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/src/bedrock_ge/gi/sqlmodels.py +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/src/bedrock_ge/plot.py +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/tests/fixtures/ags4_sample.ags +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/tests/fixtures/asg4_expected.json +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/tests/test_plot.py +0 -0
- {bedrock_ge-0.2.2 → bedrock_ge-0.2.3}/uv.lock +0 -0
@@ -1,6 +1,6 @@
|
|
1
1
|
Metadata-Version: 2.4
|
2
2
|
Name: bedrock-ge
|
3
|
-
Version: 0.2.
|
3
|
+
Version: 0.2.3
|
4
4
|
Summary: Bedrock's Python library for geotechnical engineering.
|
5
5
|
Project-URL: Homepage, https://bedrock.engineer/
|
6
6
|
Project-URL: Source, https://github.com/bedrock-engineer/bedrock-ge
|
@@ -36,19 +36,19 @@ Description-Content-Type: text/markdown
|
|
36
36
|
<img src="https://bedrock.engineer/public/Bedrock_TextRight.png" alt="Bedrock logo" width="75%"/>
|
37
37
|
</p>
|
38
38
|
|
39
|
-
<h3 align="center">Bedrock, the Open Source Foundation for
|
39
|
+
<h3 align="center">Bedrock, the Open Source Foundation for Geotechnical Engineering</h3>
|
40
40
|
|
41
41
|
---
|
42
42
|
|
43
43
|
📃 **Documentation:** <https://bedrock.engineer/docs>
|
44
44
|
|
45
|
-
🖥️ **Source Code:** <https://github.com/bedrock-
|
45
|
+
🖥️ **Source Code:** <https://github.com/bedrock-engineer/bedrock-ge>
|
46
46
|
|
47
|
-
🐍 **`bedrock-
|
47
|
+
🐍 **`bedrock-ge` on PyPI:** <https://pypi.org/project/bedrock-ge/>
|
48
48
|
|
49
49
|
🌐 **Website:** <https://bedrock.engineer/>
|
50
50
|
|
51
|
-
🔗 **LinkedIn:** <https://www.linkedin.com/company/bedrock-
|
51
|
+
🔗 **LinkedIn:** <https://www.linkedin.com/company/bedrock-engineer>
|
52
52
|
|
53
53
|
---
|
54
54
|
|
@@ -66,13 +66,13 @@ Description-Content-Type: text/markdown
|
|
66
66
|
| GeoJSON | ✅ | ✅ |
|
67
67
|
|
68
68
|
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?
|
69
|
-
Let us know by creating an [issue](https://github.com/bedrock-
|
69
|
+
Let us know by creating an [issue](https://github.com/bedrock-engineer/bedrock-ge/issues) or starting a [discussion](https://github.com/orgs/bedrock-engineer/discussions) 💭
|
70
70
|
|
71
|
-
Also, if you have a project with publicly available GI data, please share that in a [discussion](https://github.com/orgs/bedrock-
|
71
|
+
Also, if you have a project with publicly available GI data, please share that in a [discussion](https://github.com/orgs/bedrock-engineer/discussions), such that we can create a tutorial from it 🤩
|
72
72
|
|
73
73
|
### ✅ Validate your GI data
|
74
74
|
|
75
|
-
`bedrock-
|
75
|
+
`bedrock-ge` 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.
|
76
76
|
|
77
77
|
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 💪
|
78
78
|
|
@@ -98,7 +98,7 @@ Moreover, your GI data becomes available in all the software that [Speckle has c
|
|
98
98
|
|
99
99
|
### 🔓 Free and Open Source Software
|
100
100
|
|
101
|
-
Free and Open Source Software (FOSS) gives you full access to the code, which means you can customize `bedrock-
|
101
|
+
Free and Open Source Software (FOSS) gives you full access to the code, which means you can customize `bedrock-ge` to integrate with other tools and fit your workflows & project needs.
|
102
102
|
|
103
103
|
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 ⛓️💥
|
104
104
|
|
@@ -148,10 +148,10 @@ This relational database ([linked tables](https://en.wikipedia.org/wiki/Relation
|
|
148
148
|
|
149
149
|
## ⬇️ Installation
|
150
150
|
|
151
|
-
In case you're using `uv`, you can add `bedrock-
|
151
|
+
In case you're using `uv`, you can add `bedrock-ge` to your Python project and install it in your project's virtual environment by running:
|
152
152
|
|
153
153
|
```bash
|
154
|
-
uv add bedrock-
|
154
|
+
uv add bedrock-ge
|
155
155
|
```
|
156
156
|
|
157
157
|
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/)):
|
@@ -161,10 +161,10 @@ I would highly recommend anyone to start using [`uv`](https://docs.astral.sh/uv/
|
|
161
161
|
- 🗂️ `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.
|
162
162
|
- In short, 🚀 `uv` is a single tool to replace `pip`, `pip-tools`, `pipx`, `poetry`, `pyenv`, `virtualenv`, `conda` and more...
|
163
163
|
|
164
|
-
It's of course also possible to install `bedrock-
|
164
|
+
It's of course also possible to install `bedrock-ge` from [PyPI](https://pypi.org/project/bedrock-ge/) (Python Packaging Index) using `pip`:
|
165
165
|
|
166
166
|
```bash
|
167
|
-
pip install bedrock-
|
167
|
+
pip install bedrock-ge
|
168
168
|
```
|
169
169
|
|
170
170
|
## 💭 Feedback
|
@@ -173,8 +173,8 @@ Got some feedback, a great idea, running into problems when working with Bedrock
|
|
173
173
|
|
174
174
|
Please feel free to:
|
175
175
|
|
176
|
-
1. open an issue for feature requests or bug reports: [`bedrock-
|
177
|
-
2. start a discussion in this GitHub repo: [Bedrock discussions](https://github.com/orgs/bedrock-
|
176
|
+
1. open an issue for feature requests or bug reports: [`bedrock-ge` issues](https://github.com/bedrock-engineer/bedrock-ge/issues),
|
177
|
+
2. start a discussion in this GitHub repo: [Bedrock discussions](https://github.com/orgs/bedrock-engineer/discussions),
|
178
178
|
3. or start a discussion on the Speckle community forum if that's more appropriate: [Speckle community forum](https://speckle.community/)
|
179
179
|
|
180
180
|
All feedback and engagement with the Bedrock community is welcome 🤗
|
@@ -189,7 +189,7 @@ Contributing isn't just about writing code:
|
|
189
189
|
|
190
190
|
- Use Bedrock and provide [feedback](#-feedback) 🪲
|
191
191
|
- Share how you use Bedrock 🏗️
|
192
|
-
- Help each other out, e.g. by replying to questions in the [discussions](https://github.com/orgs/bedrock-
|
192
|
+
- Help each other out, e.g. by replying to questions in the [discussions](https://github.com/orgs/bedrock-engineer/discussions) or [`bedrock-ge` issues](https://github.com/bedrock-engineer/bedrock-ge/issues) 🤝
|
193
193
|
- Spread the word about Bedrock 🤩
|
194
194
|
- Documentation and tutorials 📃
|
195
195
|
- 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! 🖱️💥
|
@@ -211,7 +211,7 @@ If you want your ground investigation data to go into a GIS database, all GIS ge
|
|
211
211
|
|
212
212
|
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))
|
213
213
|
|
214
|
-
Please start a [discussion](https://github.com/orgs/bedrock-
|
214
|
+
Please start a [discussion](https://github.com/orgs/bedrock-engineer/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.
|
215
215
|
|
216
216
|
## ✍️ Author
|
217
217
|
|
@@ -2,19 +2,19 @@
|
|
2
2
|
<img src="https://bedrock.engineer/public/Bedrock_TextRight.png" alt="Bedrock logo" width="75%"/>
|
3
3
|
</p>
|
4
4
|
|
5
|
-
<h3 align="center">Bedrock, the Open Source Foundation for
|
5
|
+
<h3 align="center">Bedrock, the Open Source Foundation for Geotechnical Engineering</h3>
|
6
6
|
|
7
7
|
---
|
8
8
|
|
9
9
|
📃 **Documentation:** <https://bedrock.engineer/docs>
|
10
10
|
|
11
|
-
🖥️ **Source Code:** <https://github.com/bedrock-
|
11
|
+
🖥️ **Source Code:** <https://github.com/bedrock-engineer/bedrock-ge>
|
12
12
|
|
13
|
-
🐍 **`bedrock-
|
13
|
+
🐍 **`bedrock-ge` on PyPI:** <https://pypi.org/project/bedrock-ge/>
|
14
14
|
|
15
15
|
🌐 **Website:** <https://bedrock.engineer/>
|
16
16
|
|
17
|
-
🔗 **LinkedIn:** <https://www.linkedin.com/company/bedrock-
|
17
|
+
🔗 **LinkedIn:** <https://www.linkedin.com/company/bedrock-engineer>
|
18
18
|
|
19
19
|
---
|
20
20
|
|
@@ -32,13 +32,13 @@
|
|
32
32
|
| GeoJSON | ✅ | ✅ |
|
33
33
|
|
34
34
|
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?
|
35
|
-
Let us know by creating an [issue](https://github.com/bedrock-
|
35
|
+
Let us know by creating an [issue](https://github.com/bedrock-engineer/bedrock-ge/issues) or starting a [discussion](https://github.com/orgs/bedrock-engineer/discussions) 💭
|
36
36
|
|
37
|
-
Also, if you have a project with publicly available GI data, please share that in a [discussion](https://github.com/orgs/bedrock-
|
37
|
+
Also, if you have a project with publicly available GI data, please share that in a [discussion](https://github.com/orgs/bedrock-engineer/discussions), such that we can create a tutorial from it 🤩
|
38
38
|
|
39
39
|
### ✅ Validate your GI data
|
40
40
|
|
41
|
-
`bedrock-
|
41
|
+
`bedrock-ge` 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.
|
42
42
|
|
43
43
|
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 💪
|
44
44
|
|
@@ -64,7 +64,7 @@ Moreover, your GI data becomes available in all the software that [Speckle has c
|
|
64
64
|
|
65
65
|
### 🔓 Free and Open Source Software
|
66
66
|
|
67
|
-
Free and Open Source Software (FOSS) gives you full access to the code, which means you can customize `bedrock-
|
67
|
+
Free and Open Source Software (FOSS) gives you full access to the code, which means you can customize `bedrock-ge` to integrate with other tools and fit your workflows & project needs.
|
68
68
|
|
69
69
|
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 ⛓️💥
|
70
70
|
|
@@ -114,10 +114,10 @@ This relational database ([linked tables](https://en.wikipedia.org/wiki/Relation
|
|
114
114
|
|
115
115
|
## ⬇️ Installation
|
116
116
|
|
117
|
-
In case you're using `uv`, you can add `bedrock-
|
117
|
+
In case you're using `uv`, you can add `bedrock-ge` to your Python project and install it in your project's virtual environment by running:
|
118
118
|
|
119
119
|
```bash
|
120
|
-
uv add bedrock-
|
120
|
+
uv add bedrock-ge
|
121
121
|
```
|
122
122
|
|
123
123
|
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/)):
|
@@ -127,10 +127,10 @@ I would highly recommend anyone to start using [`uv`](https://docs.astral.sh/uv/
|
|
127
127
|
- 🗂️ `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.
|
128
128
|
- In short, 🚀 `uv` is a single tool to replace `pip`, `pip-tools`, `pipx`, `poetry`, `pyenv`, `virtualenv`, `conda` and more...
|
129
129
|
|
130
|
-
It's of course also possible to install `bedrock-
|
130
|
+
It's of course also possible to install `bedrock-ge` from [PyPI](https://pypi.org/project/bedrock-ge/) (Python Packaging Index) using `pip`:
|
131
131
|
|
132
132
|
```bash
|
133
|
-
pip install bedrock-
|
133
|
+
pip install bedrock-ge
|
134
134
|
```
|
135
135
|
|
136
136
|
## 💭 Feedback
|
@@ -139,8 +139,8 @@ Got some feedback, a great idea, running into problems when working with Bedrock
|
|
139
139
|
|
140
140
|
Please feel free to:
|
141
141
|
|
142
|
-
1. open an issue for feature requests or bug reports: [`bedrock-
|
143
|
-
2. start a discussion in this GitHub repo: [Bedrock discussions](https://github.com/orgs/bedrock-
|
142
|
+
1. open an issue for feature requests or bug reports: [`bedrock-ge` issues](https://github.com/bedrock-engineer/bedrock-ge/issues),
|
143
|
+
2. start a discussion in this GitHub repo: [Bedrock discussions](https://github.com/orgs/bedrock-engineer/discussions),
|
144
144
|
3. or start a discussion on the Speckle community forum if that's more appropriate: [Speckle community forum](https://speckle.community/)
|
145
145
|
|
146
146
|
All feedback and engagement with the Bedrock community is welcome 🤗
|
@@ -155,7 +155,7 @@ Contributing isn't just about writing code:
|
|
155
155
|
|
156
156
|
- Use Bedrock and provide [feedback](#-feedback) 🪲
|
157
157
|
- Share how you use Bedrock 🏗️
|
158
|
-
- Help each other out, e.g. by replying to questions in the [discussions](https://github.com/orgs/bedrock-
|
158
|
+
- Help each other out, e.g. by replying to questions in the [discussions](https://github.com/orgs/bedrock-engineer/discussions) or [`bedrock-ge` issues](https://github.com/bedrock-engineer/bedrock-ge/issues) 🤝
|
159
159
|
- Spread the word about Bedrock 🤩
|
160
160
|
- Documentation and tutorials 📃
|
161
161
|
- 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! 🖱️💥
|
@@ -177,7 +177,7 @@ If you want your ground investigation data to go into a GIS database, all GIS ge
|
|
177
177
|
|
178
178
|
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))
|
179
179
|
|
180
|
-
Please start a [discussion](https://github.com/orgs/bedrock-
|
180
|
+
Please start a [discussion](https://github.com/orgs/bedrock-engineer/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.
|
181
181
|
|
182
182
|
## ✍️ Author
|
183
183
|
|
@@ -1,4 +1,4 @@
|
|
1
|
-
# Releasing a new version of `bedrock-
|
1
|
+
# Releasing a new version of `bedrock-ge`
|
2
2
|
|
3
3
|
## 1. Update the Version Number
|
4
4
|
|
@@ -75,14 +75,14 @@ uv publish
|
|
75
75
|
## 10. Verify the Release
|
76
76
|
|
77
77
|
Check that the new version is available on PyPI:
|
78
|
-
<https://pypi.org/project/bedrock-
|
78
|
+
<https://pypi.org/project/bedrock-ge/>
|
79
79
|
|
80
80
|
Install the new Python package version in a clean environment to verify it works:
|
81
81
|
|
82
82
|
```bash
|
83
|
-
uv run --with bedrock-
|
83
|
+
uv run --with bedrock-ge --no-project -- python -c "import bedrock_ge; print(f'bedrock-ge version: {bedrock_ge.__version__}')"
|
84
84
|
```
|
85
85
|
|
86
86
|
## 11. Create a GitHub Release
|
87
87
|
|
88
|
-
Create a new release based on the tag: [github.com/bedrock-
|
88
|
+
Create a new release based on the tag: [github.com/bedrock-engineer/bedrock-ge/releases](https://github.com/bedrock-engineer/bedrock-ge/releases).
|
@@ -69,6 +69,12 @@ I think that if people don't know how to run a Jupyter notebook they should simp
|
|
69
69
|
marimo export ipynb --sandbox --sort top-down --include-outputs hk_kaitak_ags3_to_brgi_geodb.py -o hk_kaitak_ags3_to_brgi_geodb.ipynb
|
70
70
|
```
|
71
71
|
|
72
|
+
After or before exporting a marimo notebook to a Jupyter notebook, the cell with the import statements and the cell(s) with function definitions have to be moved to the top of the Jupyter notebook for it to work. Additionally, in order for Google Colab to be able to run the notebook, you need to install `bedrock-ge` and a few other Python libraries by adding the following cell to the very top of the Jupyter notebook:
|
73
|
+
|
74
|
+
```bash
|
75
|
+
! pip install bedrock-ge folium mapclassify marimo --quiet
|
76
|
+
```
|
77
|
+
|
72
78
|
### HTML WebAssembly (WASM)
|
73
79
|
|
74
80
|
```bash
|