bedrock-ge 0.2.0__tar.gz → 0.2.2__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.
Files changed (63) hide show
  1. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/.gitignore +4 -5
  2. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/PKG-INFO +16 -8
  3. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/README.md +1 -1
  4. bedrock_ge-0.2.2/examples/README.md +76 -0
  5. bedrock_ge-0.2.2/examples/hk_kaitak_ags3/hk_kaitak_ags3_to_brgi_geodb.ipynb +6335 -0
  6. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/examples/hk_kaitak_ags3/hk_kaitak_ags3_to_brgi_geodb.py +489 -403
  7. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/examples/hk_kaitak_ags3/kaitak_ags3.zip +0 -0
  8. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2/examples/hk_kaitak_ags3}/kaitak_gi.gpkg +0 -0
  9. bedrock_ge-0.2.2/pyproject.toml +91 -0
  10. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/src/bedrock_ge/__init__.py +1 -1
  11. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/src/bedrock_ge/gi/ags/ags3_data_dictionary.json +7444 -7444
  12. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/src/bedrock_ge/gi/ags/ags4_data_dictionary.json +24074 -24074
  13. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/src/bedrock_ge/gi/ags/transform.py +12 -1
  14. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/uv.lock +261 -245
  15. bedrock_ge-0.2.0/examples/hk_kaitak_ags3/hk_kaitak_ags3_to_brgi_geodb.ipynb +0 -410
  16. bedrock_ge-0.2.0/kaitak_gi.xlsx +0 -0
  17. bedrock_ge-0.2.0/pyproject.toml +0 -68
  18. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/.gitattributes +0 -0
  19. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/.python-version +0 -0
  20. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/LICENSE +0 -0
  21. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/RELEASE.md +0 -0
  22. /bedrock_ge-0.2.0/examples/hk_kaitak_ags3/64475_ASD012162 AGS.ags → /bedrock_ge-0.2.2/examples/hk_kaitak_ags3/64475_ASD012162.ags +0 -0
  23. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/mypy.ini +0 -0
  24. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/ags3_to_gis.ipynb +0 -0
  25. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/bedrock_gi_to_speckle.ipynb +0 -0
  26. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/data_validation/README.md +0 -0
  27. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/data_validation/bedrock-data-package-schema.json +0 -0
  28. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/data_validation/bedrock_sql_model.ipynb +0 -0
  29. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/data_validation/frictionless-table-schema.json +0 -0
  30. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/data_validation/jsonschema_to_tableschema.py +0 -0
  31. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/data_validation/my-pandera-schema.json +0 -0
  32. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/data_validation/pandera-plus-schema.json +0 -0
  33. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/data_validation/sqlalchemy_to_json.py +0 -0
  34. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/data_validation/sqlmodel_tutorial.py +0 -0
  35. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/data_validation/try_pandera.ipynb +0 -0
  36. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/diggs/AGS Example Template.xml +0 -0
  37. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/diggs/DIGGS1-DIGGS.XML +0 -0
  38. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/diggs/DIGGS1.ags +0 -0
  39. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/hk_ags3/link_insitu_lab_gi/giu_metadata_main.csv +0 -0
  40. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/hk_ags3/link_insitu_lab_gi/giu_metadata_rel_rep.csv +0 -0
  41. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/leapfrog_weka_hills/boreholes/Geol.csv +0 -0
  42. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/leapfrog_weka_hills/boreholes/Location.csv +0 -0
  43. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/leapfrog_weka_hills/boreholes/SPT.csv +0 -0
  44. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/leapfrog_weka_hills/cpt/CPT.csv +0 -0
  45. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/leapfrog_weka_hills/cpt/Location.csv +0 -0
  46. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/sandbox/leapfrog_weka_hills/leapfrog_csv_to_gis.ipynb +0 -0
  47. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/src/bedrock_ge/gi/__init__.py +0 -0
  48. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/src/bedrock_ge/gi/ags/__init__.py +0 -0
  49. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/src/bedrock_ge/gi/ags/read.py +0 -0
  50. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/src/bedrock_ge/gi/ags/schemas.py +0 -0
  51. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/src/bedrock_ge/gi/ags/validate.py +0 -0
  52. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/src/bedrock_ge/gi/bedrock-gi-schema.json +0 -0
  53. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/src/bedrock_ge/gi/concatenate.py +0 -0
  54. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/src/bedrock_ge/gi/gis_geometry.py +0 -0
  55. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/src/bedrock_ge/gi/schemas.py +0 -0
  56. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/src/bedrock_ge/gi/sqlmodels.py +0 -0
  57. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/src/bedrock_ge/gi/validate.py +0 -0
  58. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/src/bedrock_ge/gi/write.py +0 -0
  59. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/src/bedrock_ge/plot.py +0 -0
  60. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/tests/fixtures/ags4_sample.ags +0 -0
  61. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/tests/fixtures/asg4_expected.json +0 -0
  62. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/tests/test_gi.py +0 -0
  63. {bedrock_ge-0.2.0 → bedrock_ge-0.2.2}/tests/test_plot.py +0 -0
@@ -1,8 +1,11 @@
1
1
  # marimo
2
2
  __marimo__/
3
3
 
4
- # Outputs
4
+ # Outputs, logs, tmp, etc.
5
5
  **/output
6
+ **/log
7
+ **/tmp
8
+ **/temp
6
9
 
7
10
  # SQLite Databases
8
11
  *.sqlite
@@ -91,10 +94,6 @@ ENV/
91
94
  env.bak/
92
95
  venv.bak/
93
96
 
94
- # Spyder project settings
95
- .spyderproject
96
- .spyproject
97
-
98
97
  # Rope project settings
99
98
  .ropeproject
100
99
 
@@ -1,7 +1,7 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: bedrock-ge
3
- Version: 0.2.0
4
- Summary: Bedrock, the Open Source Foundation for Ground Engineering
3
+ Version: 0.2.2
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
7
7
  Project-URL: Documentation, https://bedrock.engineer/docs/
@@ -9,18 +9,26 @@ Project-URL: Tracker, https://github.com/bedrock-engineer/bedrock-ge/issues
9
9
  Author-email: Bedrock <info@bedrock.engineer>
10
10
  License: Apache Software License (Apache 2.0)
11
11
  License-File: LICENSE
12
- Keywords: aec,ags,bedrock,bim,engineering geology,geo-bim,geotech,geotechnical data,geotechnical engineering,gi data,gis,ground engineering,ground investigation,ground investigation data
13
- Classifier: Development Status :: 2 - Pre-Alpha
12
+ Keywords: aec,aeco,ags,ags3,ags4,bedrock,bim,borehole,borehole-data,civil-engineering,engineering-geology,geo-bim,geoscience-bim,geosciences,geospatial,geospatial-data,geostatistics,geotech,geotechnical,geotechnical-data,geotechnical-engineering,geotechnics,gi-data,gis,ground-engineering,ground-investigation,ground-investigation-data,subsurface,underground
13
+ Classifier: Development Status :: 3 - Alpha
14
+ Classifier: Intended Audience :: Education
15
+ Classifier: Intended Audience :: Science/Research
14
16
  Classifier: License :: OSI Approved :: Apache Software License
15
17
  Classifier: Operating System :: OS Independent
16
- Classifier: Programming Language :: Python :: 3
18
+ Classifier: Programming Language :: Python
19
+ Classifier: Programming Language :: Python :: 3 :: Only
20
+ Classifier: Programming Language :: Python :: 3.9
21
+ Classifier: Programming Language :: Python :: 3.10
22
+ Classifier: Programming Language :: Python :: 3.11
23
+ Classifier: Programming Language :: Python :: 3.12
24
+ Classifier: Programming Language :: Python :: 3.13
25
+ Classifier: Topic :: Scientific/Engineering
26
+ Classifier: Topic :: Scientific/Engineering :: GIS
17
27
  Requires-Python: >=3.9
18
- Requires-Dist: duckdb~=1.0
19
28
  Requires-Dist: geopandas~=1.0
20
29
  Requires-Dist: openpyxl~=3.0
21
30
  Requires-Dist: pandera>=0.23.0
22
31
  Requires-Dist: python-ags4~=1.0
23
- Requires-Dist: sqlglot>=26.12.0
24
32
  Requires-Dist: sqlmodel>=0.0.22
25
33
  Description-Content-Type: text/markdown
26
34
 
@@ -209,7 +217,7 @@ Please start a [discussion](https://github.com/orgs/bedrock-gi/discussions) or c
209
217
 
210
218
  Hi, I'm Joost Gevaert 👋
211
219
 
212
- 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.
220
+ I studied geotechnical engineering and applied geophysics and then worked for [Arup](https://www.arup.com/) for 4 years as a geotechnical engineer and computational designer.
213
221
 
214
222
  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).
215
223
 
@@ -183,7 +183,7 @@ Please start a [discussion](https://github.com/orgs/bedrock-gi/discussions) or c
183
183
 
184
184
  Hi, I'm Joost Gevaert 👋
185
185
 
186
- 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.
186
+ I studied geotechnical engineering and applied geophysics and then worked for [Arup](https://www.arup.com/) for 4 years as a geotechnical engineer and computational designer.
187
187
 
188
188
  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).
189
189
 
@@ -0,0 +1,76 @@
1
+ # `bedrock-ge` examples
2
+
3
+ This folder contains example notebooks that guide you how to use Bedrock's Geotechnical Engineering Python package `bedrock-ge`.
4
+
5
+ ## How to run the example notebooks
6
+
7
+ The notebooks are available as [marimo](https://marimo.io/) (`.py` extension) as well as [Jupyter](https://jupyter.org/) notebooks (`.ipynb` extension). However, it is **STRONGLY** recommended to use the marimo notebooks, as they are more user-friendly and have [several other advantages over Jupyter notebooks](https://docs.marimo.io/#highlights).
8
+
9
+ Both the marimo notebooks as well as the Jupyter notebooks can be run online, i.e. remotely, or on your own computer, i.e. locally.
10
+
11
+ ### marimo
12
+
13
+ marimo notebooks are normal Python files, and therefore have the `.py` extension.
14
+
15
+ #### Remotely: marimo playground
16
+
17
+ marimo notebooks on GitHub can directly be run remotely in the [marimo playground](https://docs.marimo.io/guides/publishing/playground/#open-notebooks-hosted-on-github). To open the notebooks in this repository:
18
+
19
+ 1. Navigate to one of them, e.g.
20
+ The Kai Tak, Hong Kong AGS 3 example: [hk_kaitak_ags3/hk_kaitak_ags3_to_brgi_geodb.py](https://github.com/bedrock-engineer/bedrock-ge/blob/main/examples/hk_kaitak_ags3/hk_kaitak_ags3_to_brgi_geodb.py)
21
+ 2. Copy the GitHub URL of the notebook you want to try, e.g.
22
+ https://github.com/bedrock-engineer/bedrock-ge/blob/main/examples/hk_kaitak_ags3/hk_kaitak_ags3_to_brgi_geodb.py
23
+ 3. Open a new tab and go to `marimo.app/<Ctrl + V the copied GitHub URL>`, e.g.
24
+ https://marimo.app/https://github.com/bedrock-engineer/bedrock-ge/blob/dev/examples/hk_kaitak_ags3/hk_kaitak_ags3_to_brgi_geodb.py
25
+
26
+ #### Locally: on your own computer
27
+
28
+ Running the marimo notebooks in this repo locally is very easy if you're using [`uv`](https://docs.astral.sh/uv/) to manage Python. In case you're not usinng `uv` to manage Python yet, make sure to give it a try! (INCLUDE A LINK TO BEDROCK DOCS ON HOW TO INSTALL `uv`.)
29
+
30
+ Managing Python with `uv` will save you many many headaches w.r.t. managing virtual environments, Python packages, etc. etc. etc. Probably the greatest thing about `uv` is that you don't really need to understand what a virtual environment is...
31
+
32
+ To run a marimo notebook from this repo locally:
33
+
34
+ 1. Download the notebook
35
+ 2. Open the terminal
36
+ 3. Navigate to the directory where you downloaded the marimo notebook with `cd` (change directory). On Windows this could be:
37
+ ```bash
38
+ cd %USERPROFILE%\Downloads
39
+ ```
40
+ 4. Run the marimo notebook with:
41
+ ```bash
42
+ uvx marimo edit --sandbox marimo_notebook.py
43
+ ```
44
+
45
+ ### Jupyter
46
+
47
+ Jupyter notebooks have the `.ipynb` extension, which is short for Interactive Python NoteBook.
48
+
49
+ #### Remotely: Google Colab
50
+
51
+ 1. Navigate to one of them, e.g.
52
+ The Kai Tak, Hong Kong AGS 3 example: [hk_kaitak_ags3/hk_kaitak_ags3_to_brgi_geodb.ipynb](https://github.com/bedrock-engineer/bedrock-ge/blob/main/examples/hk_kaitak_ags3/hk_kaitak_ags3_to_brgi_geodb.ipynb)
53
+ 2. Copy the GitHub URL of the notebook you want to try, e.g.
54
+ https://github.com/bedrock-engineer/bedrock-ge/blob/main/examples/hk_kaitak_ags3/hk_kaitak_ags3_to_brgi_geodb.ipynb
55
+ 3. Navigate to [colab.research.google.com](https://colab.research.google.com/)
56
+ 4. Paste the GitHub URL in the GitHub > Enter a GitHub URL... field
57
+
58
+ #### Locally: on your own computer
59
+
60
+ How much do we need to go into detail on how to run a Jupyter Notebook?
61
+
62
+ I think that if people don't know how to run a Jupyter notebook they should simply use the marimo notebook. The only reason to not use marimo, is when a company uses some deployed Jupyter service like Google Colab, Jupyter Hub or something like that, in which case they should run the Jupyter notebook remotely.
63
+
64
+ ## Eporting marimo notebooks to other formats
65
+
66
+ ### Jupyter Notebook
67
+
68
+ ```bash
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
+ ```
71
+
72
+ ### HTML WebAssembly (WASM)
73
+
74
+ ```bash
75
+ marimo export html-wasm --sandbox --mode edit hk_kaitak_ags3_to_brgi_geodb.py -o output
76
+ ```