Repository navigation
Home
Submission Date: 2023-12-22
Approval Date: YYYY-MM-DD
Publication Date: YYYY-MM-DD
External identifier of this OGC® document: http://www.opengis.net/doc/per/XXX
Internal reference number of this OGC® document: YY-XXX
Category: OGC® Engineering Report
Editors: Mickael Beaufils
Copyright notice
Copyright © 2023 Open Geospatial Consortium To obtain additional rights of use, visit http://www.opengeospatial.org/legal/.
Warning
LICENSE AGREEMENT
Use of this document is subject to the license agreement at https://www.ogc.org/license
Suggested additions, changes and comments on this document are welcome and encouraged. Such suggestions may be submitted using the online change request form on OGC web site: http://ogc.standardstracker.org/
This wiki provides an overview of the vision that is built in this Interoperability Experiment.
Please notice this is a work in progress and adjustments are very prone to happen.
Most pages of this wiki are associated to a GitHub issue that you can use for providing feedback.
For more information about the initiative, please see : https://www.ogc.org/projects/initiatives/geotechie --->
BIM, GIS & Digital Twins introduce or emphasize several requirements regarding the data. This mostly concern the built environment but also orientate the way the geoscience data are expected to be delivered.
The main concern is about semantics. As also identified as the main criteria of interoperability in the FAIR principles, data shall be described in a non-ambiguous way. Those definitions shall be shared by the community independently from the standard that is used. For that purpose, a federation of model is needed. Then OGC and bSI will derive logical models for OGC based and bSI based (IFC) standards.
This effort would fit into the ongoing collaboration between OGC initiatives and bSI projects on georeferencing, infrastructures alignments, procedural geometries, voxels, etc...
Richard Petrie (bSI), Scott Simmons (OGC)
Although, this project is the opportunity to align with other standards. A non-exhaustive list of them include AGS/AGSi, DIGGS, Geo3DML, GeoValML, BoreholeML, ResqML...
On the OGC side, this project is identified as the main contributor to leverage the OGC based standards. For the moment, the IFC schema extension for Geotechnics is mainly supported by the GeoSubgroup of the IFC Tunnel but it aims to serve all the IFC infrastructure projects.

- Conceptual model (Work in Progress): https://github.com/opengeospatial/Geotech/wiki/1-Conceptual-model
- Guidance for the use of OGC APIs (Work in Progress): https://github.com/opengeospatial/Geotech/wiki/OGC-APIs
- Guidance for the display of geotech information in software (TBD)
Want to have an overview of all the things you can find in this wiki?
Follow us: https://github.com/opengeospatial/Geotech/wiki/Summary
- About the Borehole IE and Sampling Boreholes
- Geometry considerations
- Features properties vs observations
- A brief introduction to ISO 19148 and ISO 19156
- Enabling linear referencing based observations
- Conceptual Borehole Model
- A brief introduction to GeoSciML
- Extending gsml:GeologicUnit
- Extending gsml:ShearStructureDisplacement
- Extending gsml:Fold
- Extending gsml:Contact
- Adding gsml:GeotechUnit
- Extending gsml:Joint
- A brief introduction to GroundWaterML2
- Extending gwml2:HydroGeoUnit
- Extending gwml2:FluidBody
- Extending gwml2:FluidBodySurface
- Extending gwml2:HydroGeoVoid
- A brief introduction to LandInfra and InfraGML
- Reusing InfraGML:Alignment
- Extending InfraGML:Facility and FacilityPart