bedrock-ge 0.2.3__py3-none-any.whl → 0.3.0__py3-none-any.whl

bedrock_ge/gi/gis_geometry.py

@@ -1,280 +0,0 @@
-from typing import Dict, Tuple, Union
-
-import geopandas as gpd
-import numpy as np
-import pandas as pd
-from pyproj import Transformer
-from pyproj.crs import CRS
-from shapely.geometry import LineString, Point
-
-# TODO: change function type hints, such that pandera checks the dataframes against the Bedrock schemas
-
-
-def calculate_gis_geometry(
-    no_gis_brgi_db: Dict[str, Union[pd.DataFrame, gpd.GeoDataFrame]],
-    verbose: bool = True,
-) -> Dict[str, gpd.GeoDataFrame]:
-    """Calculates GIS geometry for tables in a Bedrock Ground Investigation database.
-
-    This function processes a dictionary of DataFrames containing Ground Investigation (GI) data,
-    adding appropriate GIS geometry to each table. It handles both 2D and 3D geometries,
-    including vertical boreholes and sampling locations.
-
-    Args:
-        no_gis_brgi_db (Dict[str, Union[pd.DataFrame, gpd.GeoDataFrame]]): Dictionary containing
-            the Bedrock GI database tables without GIS geometry. Keys are table names,
-            values are either pandas DataFrames or GeoDataFrames.
-        verbose (bool, optional): Whether to print progress information. Defaults to True.
-
-    Returns:
-        Dict[str, gpd.GeoDataFrame]: Dictionary containing the Bedrock GI database tables
-        with added GIS geometry. All tables are converted to GeoDataFrames with
-        appropriate CRS and geometry columns.
-
-    Raises:
-        ValueError: If the projects in the database use different Coordinate Reference Systems (CRS).
-
-    Note:
-        The function performs the following operations:
-        1. Verifies all projects use the same CRS
-        2. Calculates GIS geometry for the 'Location' table
-        3. Creates a 'LonLatHeight' table for 2D visualization
-        4. Processes 'Sample' table if present
-        5. Processes all tables starting with "InSitu_"
-    """
-    # Make sure that the Bedrock database is not changed outside this function.
-    brgi_db = no_gis_brgi_db.copy()
-
-    if verbose:
-        print("Calculating GIS geometry for the Bedrock GI database tables...")
-
-    # Check if all projects have the same CRS
-    if not brgi_db["Project"]["crs_wkt"].nunique() == 1:
-        raise ValueError(
-            "All projects must have the same CRS (Coordinate Reference System).\n"
-            "Raise an issue on GitHub in case you need to be able to combine GI data that was acquired in multiple different CRS's."
-        )
-
-    crs = CRS.from_wkt(brgi_db["Project"]["crs_wkt"].iloc[0])
-
-    # Calculate GIS geometry for the 'Location' table
-    if verbose:
-        print("Calculating GIS geometry for the Bedrock GI 'Location' table...")
-    brgi_db["Location"] = calculate_location_gis_geometry(brgi_db["Location"], crs)
-
-    # Create the 'LonLatHeight' table.
-    # The 'LonLatHeight' table makes it easier to visualize the GIS geometry on 2D maps,
-    # because vertical lines are often very small or completely hidden in 2D.
-    # This table only contains the 3D of the GI locations at ground level,
-    # in WGS84 (Longitude, Latitude, Height) coordinates.
-    if verbose:
-        print(
-            "Creating 'LonLatHeight' table with GI locations in WGS84 geodetic coordinates...",
-            "    WGS84 geodetic coordinates: (Longitude, Latitude, Ground Level Ellipsoidal Height)",
-            sep="\n",
-        )
-    brgi_db["LonLatHeight"] = create_lon_lat_height_table(brgi_db["Location"], crs)
-
-    # Create GIS geometry for tables that have In-Situ GIS geometry.
-    # These are the 'Sample' table and 'InSitu_...' tables.
-    # These tables are children of the Location table,
-    # i.e. have the 'Location' table as the parent table.
-    if "Sample" in brgi_db.keys():
-        if verbose:
-            print("Calculating GIS geometry for the Bedrock GI 'Sample' table...")
-        brgi_db["Sample"] = calculate_in_situ_gis_geometry(
-            brgi_db["Sample"], brgi_db["Location"], crs
-        )
-
-    for table_name, table in brgi_db.items():
-        if table_name.startswith("InSitu_"):
-            if verbose:
-                print(
-                    f"Calculating GIS geometry for the Bedrock GI '{table_name}' table..."
-                )
-            brgi_db[table_name] = calculate_in_situ_gis_geometry(
-                table, brgi_db["Location"], crs
-            )
-
-    return brgi_db
-
-
-def calculate_location_gis_geometry(
-    brgi_location: Union[pd.DataFrame, gpd.GeoDataFrame], crs: CRS
-) -> gpd.GeoDataFrame:
-    """Calculates GIS geometry for a set of Ground Investigation locations.
-
-    Args:
-        brgi_location (Union[pd.DataFrame, gpd.GeoDataFrame]): The GI locations to calculate GIS geometry for.
-        crs (pyproj.CRS): The Coordinate Reference System (CRS) to use for the GIS geometry.
-
-    Returns:
-        gpd.GeoDataFrame: The GIS geometry for the given GI locations, with additional columns:
-            - longitude: The longitude of the location in the WGS84 CRS.
-            - latitude: The latitude of the location in the WGS84 CRS.
-            - wgs84_ground_level_height: The height of the ground level of the location in the WGS84 CRS.
-            - elevation_at_base: The elevation at the base of the location.
-            - geometry: The GIS geometry of the location.
-    """
-    # Calculate Elevation at base of GI location
-    brgi_location["elevation_at_base"] = (
-        brgi_location["ground_level_elevation"] - brgi_location["depth_to_base"]
-    )
-
-    # Make a gpd.GeoDataFrame from the pd.DataFrame by creating GIS geometry
-    brgi_location = gpd.GeoDataFrame(
-        brgi_location,
-        geometry=brgi_location.apply(
-            lambda row: LineString(
-                [
-                    (row["easting"], row["northing"], row["ground_level_elevation"]),
-                    (row["easting"], row["northing"], row["elevation_at_base"]),
-                ]
-            ),
-            axis=1,
-        ),
-        crs=crs,
-    )
-
-    # Calculate WGS84 geodetic coordinates
-    brgi_location[["longitude", "latitude", "wgs84_ground_level_height"]] = (
-        brgi_location.apply(
-            lambda row: calculate_wgs84_coordinates(
-                from_crs=crs,
-                easting=row["easting"],
-                northing=row["northing"],
-                elevation=row["ground_level_elevation"],
-            ),
-            axis=1,
-            result_type="expand",
-        )
-    )
-
-    return brgi_location
-
-
-def calculate_wgs84_coordinates(
-    from_crs: CRS, easting: float, northing: float, elevation: Union[float, None] = None
-) -> Tuple:
-    """Transforms coordinates from an arbitrary Coordinate Reference System (CRS) to the WGS84 CRS, which is the standard for geodetic coordinates.
-
-    Args:
-        from_crs (pyproj.CRS): The pyproj.CRS object of the CRS to transform from.
-        easting (float): The easting coordinate of the point to transform.
-        northing (float): The northing coordinate of the point to transform.
-        elevation (float or None, optional): The elevation of the point to
-            transform. Defaults to None.
-
-    Returns:
-        tuple: A tuple containing the longitude, latitude and WGS84 height of the
-            transformed point, in that order. The height is None if no elevation was
-            given, or if the provided CRS doesn't have a proper datum defined.
-    """
-    transformer = Transformer.from_crs(from_crs, 4326, always_xy=True)
-    if elevation:
-        lon, lat, wgs84_height = transformer.transform(easting, northing, elevation)
-    else:
-        lon, lat = transformer.transform(easting, northing)
-        wgs84_height = None
-
-    return lon, lat, wgs84_height
-
-
-def create_lon_lat_height_table(
-    brgi_location: gpd.GeoDataFrame, crs: CRS
-) -> gpd.GeoDataFrame:
-    """Creates a GeoDataFrame with GI locations in WGS84 (lon, lat, height) coordinates.
-
-    The 'LonLatHeight' table makes it easier to visualize the GIS geometry on 2D maps,
-    because vertical lines are often very small or completely hidden in 2D. This table
-    only contains the 3D point of the GI locations at ground level, in WGS84 (Longitude,
-    Latitude, Height) coordinates. Other attributes, such as the location type, sample
-    type, geology description, etc., can be attached to this table by joining, i.e.
-    merging those tables on the location_uid key.
-
-    Args:
-        brgi_location (GeoDataFrame): The GeoDataFrame with the GI locations.
-        crs (CRS): The Coordinate Reference System of the GI locations.
-
-    Returns:
-        GeoDataFrame: The 'LonLatHeight' GeoDataFrame.
-    """
-    lon_lat_height = gpd.GeoDataFrame(
-        brgi_location[
-            [
-                "project_uid",
-                "location_uid",
-            ]
-        ],
-        geometry=brgi_location.apply(
-            lambda row: Point(
-                row["longitude"], row["latitude"], row["wgs84_ground_level_height"]
-            ),
-            axis=1,
-        ),
-        crs=4326,
-    )
-    return lon_lat_height
-
-
-def calculate_in_situ_gis_geometry(
-    brgi_in_situ: Union[pd.DataFrame, gpd.GeoDataFrame],
-    brgi_location: Union[pd.DataFrame, gpd.GeoDataFrame],
-    crs: CRS,
-) -> gpd.GeoDataFrame:
-    """Calculates GIS geometry for a set of Ground Investigation in-situ data.
-
-    Args:
-        brgi_in_situ (Union[pd.DataFrame, gpd.GeoDataFrame]): The in-situ data to calculate GIS geometry for.
-        brgi_location (Union[pd.DataFrame, gpd.GeoDataFrame]): The location data to merge with the in-situ data.
-        crs (CRS): The Coordinate Reference System of the in-situ data.
-
-    Returns:
-        gpd.GeoDataFrame: The GIS geometry for the given in-situ data, with additional columns:
-        - elevation_at_top: The elevation at the top of the in-situ data.
-        - elevation_at_base: The elevation at the base of the in-situ data.
-        - geometry: The GIS geometry of the in-situ data.
-    """
-    location_child = brgi_in_situ.copy()
-
-    # Merge the location data into the in-situ data to get the location coordinates
-    location_child = pd.merge(
-        location_child,
-        brgi_location[
-            ["location_uid", "easting", "northing", "ground_level_elevation"]
-        ],
-        on="location_uid",
-        how="left",
-    )
-
-    # Calculate the elevation at the top of the Sample or in-situ test
-    location_child["elevation_at_top"] = (
-        location_child["ground_level_elevation"] - location_child["depth_to_top"]
-    )
-    brgi_in_situ["elevation_at_top"] = location_child["elevation_at_top"]
-
-    # Calculate the elevation at the base of the Sample or in-situ test
-    if "depth_to_base" in location_child.columns:
-        location_child["elevation_at_base"] = (
-            location_child["ground_level_elevation"] - location_child["depth_to_base"]
-        )
-        brgi_in_situ["elevation_at_base"] = location_child["elevation_at_base"]
-
-    # Create the in-situ data as a GeoDataFrame with LineString GIS geometry for
-    # Samples or in-situ tests that have an elevation at the base of the Sample or in-situ test.
-    brgi_in_situ = gpd.GeoDataFrame(
-        brgi_in_situ,
-        geometry=location_child.apply(
-            lambda row: LineString(
-                [
-                    (row["easting"], row["northing"], row["elevation_at_top"]),
-                    (row["easting"], row["northing"], row["elevation_at_base"]),
-                ]
-            )
-            if "elevation_at_base" in row and not np.isnan(row["elevation_at_base"])
-            else Point((row["easting"], row["northing"], row["elevation_at_top"])),
-            axis=1,
-        ),
-        crs=crs,
-    )
-    return brgi_in_situ

bedrock_ge-0.2.3.dist-info/METADATA

@@ -1,227 +0,0 @@
-Metadata-Version: 2.4
-Name: bedrock-ge
-Version: 0.2.3
-Summary: Bedrock's Python library for geotechnical engineering.
-Project-URL: Homepage, https://bedrock.engineer/
-Project-URL: Source, https://github.com/bedrock-engineer/bedrock-ge
-Project-URL: Documentation, https://bedrock.engineer/docs/
-Project-URL: Tracker, https://github.com/bedrock-engineer/bedrock-ge/issues
-Author-email: Bedrock <info@bedrock.engineer>
-License: Apache Software License (Apache 2.0)
-License-File: LICENSE
-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
-Classifier: Development Status :: 3 - Alpha
-Classifier: Intended Audience :: Education
-Classifier: Intended Audience :: Science/Research
-Classifier: License :: OSI Approved :: Apache Software License
-Classifier: Operating System :: OS Independent
-Classifier: Programming Language :: Python
-Classifier: Programming Language :: Python :: 3 :: Only
-Classifier: Programming Language :: Python :: 3.9
-Classifier: Programming Language :: Python :: 3.10
-Classifier: Programming Language :: Python :: 3.11
-Classifier: Programming Language :: Python :: 3.12
-Classifier: Programming Language :: Python :: 3.13
-Classifier: Topic :: Scientific/Engineering
-Classifier: Topic :: Scientific/Engineering :: GIS
-Requires-Python: >=3.9
-Requires-Dist: geopandas~=1.0
-Requires-Dist: openpyxl~=3.0
-Requires-Dist: pandera>=0.23.0
-Requires-Dist: python-ags4~=1.0
-Requires-Dist: sqlmodel>=0.0.22
-Description-Content-Type: text/markdown
-
-<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 Geotechnical Engineering</h3>
-
----
-
-📃 **Documentation:** <https://bedrock.engineer/docs>
-
-🖥️ **Source Code:** <https://github.com/bedrock-engineer/bedrock-ge>
-
-🐍 **`bedrock-ge` on PyPI:** <https://pypi.org/project/bedrock-ge/>
-
-🌐 **Website:** <https://bedrock.engineer/>
-
-🔗 **LinkedIn:** <https://www.linkedin.com/company/bedrock-engineer>
-
----
-
-## 🌟 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-engineer/bedrock-ge/issues) or starting a [discussion](https://github.com/orgs/bedrock-engineer/discussions) 💭
-
-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 🤩
-
-### ✅ Validate your GI data
-
-`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.
-
-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-ge` 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-ge` to your Python project and install it in your project's virtual environment by running:
-
-```bash
-uv add bedrock-ge
-```
-
-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-ge` from [PyPI](https://pypi.org/project/bedrock-ge/) (Python Packaging Index) using `pip`:
-
-```bash
-pip install bedrock-ge
-```
-
-## 💭 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-ge` issues](https://github.com/bedrock-engineer/bedrock-ge/issues),
-2. start a discussion in this GitHub repo: [Bedrock discussions](https://github.com/orgs/bedrock-engineer/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-engineer/discussions) or [`bedrock-ge` issues](https://github.com/bedrock-engineer/bedrock-ge/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-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.
-
-## ✍️ Author
-
-Hi, I'm Joost Gevaert 👋
-
-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.
-
-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/)

bedrock_ge-0.2.3.dist-info/RECORD

@@ -1,21 +0,0 @@
-bedrock_ge/__init__.py,sha256=r2ubK-fPZKVKQX5ggtX8Vx3YWk9c-bDNE1FmKYxUNCE,89
-bedrock_ge/plot.py,sha256=hUxpZXWlUmf2Ec5CKkGkOBJ_TfC1KM8yUeuMtsqk7A0,70
-bedrock_ge/gi/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
-bedrock_ge/gi/brgi-schema.json,sha256=XaumYqouiflu4Nc8ChyFSHpmpJW4YPG0hsyeSxkuIWQ,850
-bedrock_ge/gi/concatenate.py,sha256=2He9us_q5MF3DbXPIK50-VHtWqkiBNyM63e0vwId2Hc,1480
-bedrock_ge/gi/gis_geometry.py,sha256=NxJnuu9xfhlYO5pblynbZQnVYFIQoBx5xnBepQoZG3c,11570
-bedrock_ge/gi/schemas.py,sha256=ZA2wFQOevXtN57XglY-M70TzbZY2RyLHJDRUkmz47_M,2871
-bedrock_ge/gi/sqlmodels.py,sha256=_h3H9UP91I_1Ya_SZuL6gZbqL7uNCd5Y-u-yTf7CNto,2253
-bedrock_ge/gi/validate.py,sha256=0qGTtwytJQbYnRoXa2dj7clsyVPhB9AYPDHVIrK83qc,7069
-bedrock_ge/gi/write.py,sha256=3-81-CydjO0BkLNzckGKz1f4G5v9uNWFKRvjZ183PFc,4110
-bedrock_ge/gi/ags/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
-bedrock_ge/gi/ags/ags3_data_dictionary.json,sha256=Wx20_oJRdAlzEo-cKD6FgN9B9zOMDTcsp5dgc8QWofI,188588
-bedrock_ge/gi/ags/ags4_data_dictionary.json,sha256=XE5XJNo8GBPZTUPgvVr3QgO1UfEIAxzlSeXi-P1VLTs,609670
-bedrock_ge/gi/ags/read.py,sha256=zb4XHzPKEr7GQ4EeKVRPmy3-v7LVr-Cihog5HtruszE,7077
-bedrock_ge/gi/ags/schemas.py,sha256=y36n9SCKqFfoIQ_7-MTEdfArA5vAqZdRpY3wC4fdjy4,7451
-bedrock_ge/gi/ags/transform.py,sha256=BB0H_pMKiXF6Px4K6RlMwlQ0c3GXcuSBZFHjyt5QrhM,9984
-bedrock_ge/gi/ags/validate.py,sha256=ZfBS7AP_CTguLQCbGeyy4Krz32th2yCmtdG9rvX0MOU,703
-bedrock_ge-0.2.3.dist-info/METADATA,sha256=XMO0khsCbGlI1WDso2ITHsJSBgIHtHBZsHrBg-zPMvk,14376
-bedrock_ge-0.2.3.dist-info/WHEEL,sha256=qtCwoSJWgHk21S1Kb4ihdzI2rlJ1ZKaIurTj_ngOhyQ,87
-bedrock_ge-0.2.3.dist-info/licenses/LICENSE,sha256=xx0jnfkXJvxRnG63LTGOxlggYnIysveWIZ6H3PNdCrQ,11357
-bedrock_ge-0.2.3.dist-info/RECORD,,