OpenLog - Open Source drillhole data visualization in QGIS
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Title of Series | ||
| Number of Parts | 351 | |
| Author | ||
| License | CC Attribution 3.0 Unported: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. | |
| Identifiers | 10.5446/69234 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language | ||
| Production Year | 2022 |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
| |
| Keywords |
00:00
AudiovisualisierungOpen sourceMoment (mathematics)Representation (politics)MereologyDrill commandsComputer animation
00:34
Presentation of a groupComputer fontPhysical systemTemplate (C++)DatabaseVisualization (computer graphics)Module (mathematics)File viewerPlug-in (computing)Data structurePattern languageMorley's categoricity theoremAudiovisualisierungTemporal logicComputer fileCategory of beingPoint (geometry)Type theoryEndliche ModelltheorieMereologyGeneric programmingCurveDrill commandsInformationCASE <Informatik>Representation (politics)DatabaseVertex (graph theory)Sheaf (mathematics)Open setAzimuthMultiplication signOrientation (vector space)Moment (mathematics)File viewerLoginTemplate (C++)Software developerCuboidProjective planeTouchscreenMathematicsVector spaceElectronic visual displayLevel (video gaming)Shader <Informatik>Presentation of a groupCartesian coordinate systemRepository (publishing)Revision controlVirtual machineData storage deviceRule of inferenceDemosceneBitOrder (biology)Right angleGraph (mathematics)Frame problemStructural loadRegulärer Ausdruck <Textverarbeitung>Acoustic shadowObject (grammar)Perspective (visual)Different (Kate Ryan album)Cross section (physics)Visualization (computer graphics)Graph coloringCasting (performing arts)Odds ratioSource codeTime seriesNumberComplex numberPlug-in (computing)AuthorizationFeedbackMusical ensembleForcing (mathematics)Konferenz Europäischer StatistikerElectronic mailing listOpen sourceGoodness of fitKey (cryptography)Client (computing)Shape (magazine)Water vaporIntegrated development environmentResultantAudiovisualisierungoutputProcess (computing)Shared memoryINTEGRALModule (mathematics)2 (number)Expandierender GraphLink (knot theory)AdditionGraph (mathematics)WritingReading (process)Raster graphicsUniform resource locatorOcean currentJSONXMLComputer animation
Transcript: English(auto-generated)
00:00
My name is Jean Felder. I've been working at Australia since the beginning of the year. I'm mostly working on the 3D stuff for QGIS and as part of the OpenLog project, because as has been mentioned, with our log representation, we need to deal with some 3D data.
00:21
So, in Australia we strongly believe that we have to do something about drill-all representation in QGIS, because at the moment there are not that many tools and false tools to do this.
00:40
So, in this presentation, first of all I will present what OpenLog is, what we're trying to achieve with this project about drill-all representation in QGIS. In the second part, I will explain what we have already been doing since one year, and in the last part I will try to present some future developments and some ideas where we could go next.
01:06
So, OpenLog. To give you some basic idea about OpenLog, Australia has been working with the mining industry for some time now, for a few years.
01:20
We have developed many tools and many QGIS plugins to do so, but most of the time it has been about answering to a client request and creating some workflow which are not generic. We asked ourselves last year, can we do better? Can we provide with QGIS a general workflow which would be useful for the mining industry
01:47
and not for one client specifically? So, this project has been led by Evren Pakuschari, which is our lead geologist at Auslandia. He has been talking with a lot of partners from the mining industry,
02:01
and they all answered the same thing. We really want to have in QGIS an open source drill-all visualization and addition model. So, we decided to create some consumption to do so last year, and this consumption is sponsored by a lot of key players from the mining industry.
02:26
At the moment, I think we have something like eight partners. You can get the list from the OpenLog website, as seen below, and they give some financial support, and they also make recommendations and feedback from what we've been doing.
02:46
What's important to keep in mind is that our partners, they give some ideas, but we don't really answer to one specific need. We want to provide a good workflow, a good generic workflow.
03:02
Of course, we get feedback, we get the needs we want, but we really want to have a solution which would work for anybody which is interested in drill-all representation. It's open contribution because at Auslandia, we believe in force. It's force from day one, and anyone can get right now the source code.
03:21
They can test it, they can give feedback, so you will have the link next. We really want to do it in the open, and we're really interested if people want to make contribution. For example, we have Ron El, which is the author of one courageous plugin called Geoscience,
03:42
which already does some drill-all representation. We talked to him, and we said, yes, it's a great idea. Finally, let's get all that I've been doing in OpenLog, and let's create some generic solutions. As I said, my main motivation is we believe in force.
04:02
We also have the feedback that people from the mining industry, they are really interested in using Kugis right now, but they can't because they don't have the appropriate tools, and they are really interested in financing those tools. At the moment, there are some custom solutions. Some of them are force, but if you want to do drill-all representation,
04:25
you don't really have a standard right now. We think that with OpenLog, we will be able to do so. Here is a roadmap at the moment. Let's get some overview. First of all, we want to be able to easily import data.
04:43
You have some drill-all, you have some general information, and we need to have some database which is able to load this data in a generic way to store them. This is what we have already been doing. Once you have your data which are loaded in Kugis,
05:04
you want to have some 2D representation, which is what we call analyze log and cross-section representation. Analyze log is basically if you want to have some geological information from your data. You want to see some geophysical properties.
05:20
I will explain later. Then what I've been trying to do is we also want to expand Kugis 3D viewer in order to have a good overview of the drill-all in 3D. At the moment, we have three different projects. The first one is ExploreDB. It's mostly done.
05:42
It's basically all the information to store the drill-all information in a Postgres-Pogist database. You can grab the source code right now. You can install it from PyPy. It's working. The second part of the project is the OpenLog,
06:03
which is a Kugis Python module. It's under active development. A new version was just released yesterday. We're very proud of what we can do. It has two main features at the moment. The first one is you can import any type of data.
06:22
The second one is you can have some 2D representation. The last part is directly done in Kugis upstream. It's a 3D viewer. I've been mostly working on it. It's how to improve and add some features to the 3D representation in Kugis
06:41
to have all the geological information we want to see. So, some features. This drawing represents how we can represent WildLog. On the left, you can see drill-all. Drill-all goes in the vertical section.
07:02
Along the vertical section, you have some geolical information. It's called lithology. It's basically the work properties that you find along the hall. You can display as much geophysical information as you want. For example, it's resistivity, which is displayed.
07:24
The OpenLog module at the moment is about to do so. Here are some screenshots from the current version of OpenLog. First of all, this is how you can import the data. If you want to represent data, you have three types of data you want to import.
07:42
First of all, you need to import the hall location. From each hall, you want to have some geolical information on how it behaves in the vertical section. Basically, it's some orientation information called dip and azimuth. Once this information is imported, you can check and see how the drill-all behaves as you go deeper.
08:09
The third information is for each hall, you need to have some geophysical properties or from geolical properties. OpenLog is able to load this data from the CSV file, which is very useful in the mining industry.
08:26
Then it stores them in the Postgres generic template database, which is the ExploreDB part. Once this information is stored, you can update it. The main advantage of using ExploreDB is that you have some generic ID
08:45
and you can create some custom properties. For example, in this screenshot, I have imported two properties for my hall. It's called value and value2. I just need to add the information that is some numerical values.
09:06
Then it will be able to draw some graph based on this import. Here are some graphs from OpenLog. It's a stratigraphy visualization. It's useful for geology.
09:21
It's a two-step process if you want to get this graph. First of all, you need to select which hall you want to see. In the second part, for each hall, you just need to select which property you want to display. I've selected one hall from the 2D canvas of QGIS.
09:40
Then I've selected the lithographic information and I get this result, which is also very interesting because you can easily change its symbology. You can have a very useful geological visualization right now with OpenLog,
10:05
which is also interesting. As I said, OpenLog is supposed to be very generic, so you can import data, which are some depth information, or you can also import some time representation, which value which has changed over time.
10:23
On this example, this is just a time series and the import is exactly the same. You just need to say this is a depth or this is a time series and then you can get those graphs from selecting the hall and the properties. For example, I've selected one hall and said I want to see some water information along the hall.
10:47
Of course, you can also select multiple properties and you can display them at the same time. You also have some symbology information you can change. You can change the color, you can change the shape, etc.
11:05
It's part of the last release of OpenLog. As part of the 3D visualization, at the moment 3D is really interesting because you can load right now a lot of different types of layers and features.
11:22
But it's just a generic 3D scene. You don't have some geological information, you don't really understand what you're looking at from a geographic perspective. So, we asked ourselves what should we do to solve this issue
11:41
and the first thing we did was to add a Cartesian axis, which helps to understand exactly what you're looking at and from where. We also want to be able to define a bounding box. By bounding box, I say you can select the sub-scene because you have a lot of information
12:01
and you say, yeah, I only want to be able to have the sub-part which is also very useful. Once you have a bounding box which is defined, which is just a sub-part of your data, you can also only display this part which makes the 3D viewer much faster and much more interesting.
12:25
So, this is QGIS 3D from the 3D26 version. And on the top right you can see the axis which has been done by Auslanja.
12:41
And if you try to move, to rotate this scene, you will check that it's really, really slow because there are a lot of data you need to update. Of course, QGIS 3D has some kind of load information
13:03
which means that it only loads the details you want to see and it only displays the visible scene at the moment, which means that this scene is bigger than what you can see at the moment
13:20
but the information and the data which are not visible on the screen, QGIS 3D doesn't like to load them. But it's still a little bit too slow. So, what we did is that we add this bounding box information. Basically, from the 2D canvas, you select a rubber band
13:41
so you get some X and Y information and then you just need to add some depth information. I want to see my information along this vertical axis and then you get this, which is exactly the same scene but we just have defined the bounding box.
14:04
And right now it works on my machine. It's not yet upstream. I wish I would be able to create a merge request soon on the QGIS repository, which is really interesting with this approach
14:22
is that we did this change on the shader level of the GPU, which means that it's really fast and it's basically some basic change. It just says if the data that you want to display on the screen
14:41
is not inside the bounding box, don't display it, don't do anything. Discard this information. And it works with every type of data in QGIS with vector data, with raster data. So, it's really a generic approach.
15:06
Last of all, let's talk about the future developments we want to add to QGIS and to OpenLog. As far as the OpenLog module is concerned, we want to add some section viewer to OpenLog model.
15:22
It's basically a section along a vertical axis. You have the drill all, so you can see. And it displays them along the vertical axis. It can be a depth representation and it can be a time representation. It doesn't really matter. It should be under both cases.
15:42
And, as I said before, this part has already been done in the geoscience module developed by Roland Elle. And Roland Elle is really interested to bring this type of viewer directly in OpenLog. In this way, at this point, we will have some drill all visualization
16:05
with the curves and with section viewer. We also want to add some integration for third-party database, geot database, data-share database, and acquire database.
16:22
These are some proprietary database which are used by our partner from OpenLog. We don't really want to provide full solutions. At the moment, we think that we only add some kind of read access. You load the database with OpenLog and explore the database.
16:43
You get a snapshot, a read-only snapshot, and then you can see your data which comes from your company, but we don't want to add some write access because it's really complicated, it's time-consuming,
17:00
and we don't really think it's what we should focus on at the moment. Our partners are really interested if they can directly load in QGIS, the proprietary database. As part of the 3D visualization is concerned, if you're interested in this, we created a QGIS enhancement proposal.
17:22
It's number 252. It explains our roadmap for the 3D viewer. We have already had some feedback about it. If you're interested, please go there and add your own comment. This is a representation of what we would like to achieve,
17:41
to have a good drill-all 3D representation. You can see the drill-alls, which is also interesting. This representation is that you have your properties. You can see that the colors along the drill-alls are defined by the properties.
18:01
So we want to be able to have some kind of symbology, which is able to represent the 3D drill-all with your own costs, your own geophysical or geolocal properties associated. Another interesting part we are working on right now as far as 3D is concerned
18:25
is cross-section visualization in 3D. It also requires some changes in the shader part of QGIS. It's basically a simple change.
18:41
It just says, just as for the winning box, if you're not inside the section, don't display the feature. The main problem at the moment is that there are a lot of shaders used by QGIS. So we had to make all the changes at once in all the shaders
19:02
if you want to have this representation from all types of features under bulk QGIS. And the other problem is that we have some frame graph issues. A frame graph in a 3D representation is basically you have a lot of objects. It's how you want to represent them in the same.
19:21
One should have some shader, should it be below the other one, etc. The frame graph is responsible for handling all of this. And currently the 3D frame graph is really monolithic and we're trying to make no changes but just make a more modular approach.
19:45
And once it's done, we really believe we will be able to solve a lot of issues with the frame graph and to be able to add those features in a proper manner. So thank you very much.
20:04
Thank you, Jean.