Borehole Data Management System: a web interface for borehole data acquisition
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 | 295 | |
| Author | ||
| Contributors | ||
| License | CC Attribution 3.0 Germany: 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/43489 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
| |
| Keywords |
FOSS4G Bucharest 201995 / 295
15
20
28
32
37
38
39
40
41
42
43
44
46
48
52
54
57
69
72
75
83
85
87
88
101
103
105
106
108
111
114
119
122
123
126
129
130
131
132
137
139
140
141
142
143
144
147
148
149
155
157
159
163
166
170
171
179
189
191
192
193
194
195
196
197
202
207
212
213
214
215
216
231
235
251
252
263
287
00:00
Data managementPhysical systemDigital signal processingUser interfacePlastikkarteEntire functionSequenceFluid staticsCharacteristic polynomialDatabaseStandard deviationFocus (optics)Data modelOpen sourceArchitectureModul <Datentyp>Service (economics)Programmable read-only memoryScripting languageJava appletElectronic visual displayUser interfaceServer (computing)Point cloudCartesian coordinate systemTopostheorieFormal languageTheory of relativityLevel (video gaming)Harmonic analysisUser interfaceUser interfaceEndliche ModelltheorieWeb applicationComputer architectureOpen sourceCondition numberAttribute grammarExtension (kinesiology)Fisher informationLibrary (computing)SoftwareMetreImplementationWeb 2.0Web serviceStandard deviationSequenceFocus (optics)Data managementMoment (mathematics)Revision controlPhysical systemGoodness of fitACIDPosition operatorOffice suiteDatabaseData storage deviceCountingObservational studyForm (programming)Multiplication signLogicComputer animation
05:10
Service (economics)Physical systemPoint cloudArchitectureData managementUser interfaceScripting languageJava appletControl flowProcess (computing)Probability density functionText editorAsynchronous Transfer ModeShape (magazine)File viewerInteractive televisionAttribute grammarAsynchronous Transfer ModePoint cloudReading (process)File viewerText editor
05:36
Asynchronous Transfer ModeInteractive televisionAttribute grammarProbability density functionControl flowProcess (computing)Text editorFile viewerGame controllerPhysical systemSystem administratorData managementText editorFile formatAsynchronous Transfer ModeGame controllerProcess (computing)WhiteboardBoss CorporationDataflowType theory
06:21
Process (computing)Data managementPhysical systemFormal verificationControl flowSystem administratorText editorGame controllerGroup actionLocal GroupUniform boundedness principleZugriffskontrolleField (computer science)Coordinate systemDegree (graph theory)Asynchronous Transfer ModeDigital filterElectronic visual displayView (database)Probability density functionShape (magazine)Infinite conjugacy class propertyEmulatorDemo (music)GoogolDilution (equation)Overlay-NetzDrill commandsNetwork topologyFile viewerDean numberHill differential equationCloud computingCivil engineeringGamma functionExecution unitMathematicsDefault (computer science)Direction (geometry)Revision controlChainFile viewerState of matterElectronic visual displayAsynchronous Transfer ModeQuicksortDegree (graph theory)Group actionForcing (mathematics)Field (computer science)Computer fileNeuroinformatikLevel (video gaming)Fisher informationEndliche ModelltheorieFormal languageMessage passingPerformance appraisalArithmetic meanGenderGame controllerMereologyPosition operatorOnline helpUniform resource locatorWater vaporRow (database)Network topologyProcess (computing)Zoom lensRepresentation (politics)Validity (statistics)WhiteboardInsertion lossSystem administratorCoordinate systemAttribute grammarText editorDifferent (Kate Ryan album)Filter <Stochastik>Cartesian coordinate systemOverlay-NetzSelectivity (electronic)Form (programming)Demo (music)Probability density function1 (number)File formatComputer animation
14:14
Sturm's theoremRange (statistics)Graph (mathematics)Maxima and minimaWeb pageMultiplication signField (computer science)Physical systemComputer animation
14:37
Degree (graph theory)DampingRevision controlText editorPhysical systemData managementDialerProcess (computing)Validity (statistics)DataflowMereologyComputer animationMeeting/Interview
15:02
LogarithmCivil engineeringLink (knot theory)Maxima and minimaMathematicsComputer wormDean numberMIDIEstimationInclusion mapSource codeService (economics)Data managementPhysical systemAsynchronous Transfer ModeFile viewerInteractive televisionText editorInequality (mathematics)Control flowProcess (computing)Probability density functionAttribute grammarPoint cloudArchitectureScripting languageJava appletOpen sourceStandard deviationCharacteristic polynomialDatabaseFocus (optics)Data modelStandard deviationData modeloutputEmailUser interfaceVideo gameSoftware testingPrototypeLevel (video gaming)Different (Kate Ryan album)Strategy gameMereologyType theoryPattern languageOntologyGroup actionField (computer science)Validity (statistics)Computer configurationGraph coloringAsynchronous Transfer ModeProjective planeInterpreter (computing)Demo (music)Uniqueness quantificationCategory of beingFisher informationProcess (computing)Endliche ModelltheorieDrill commandsRevision controlDisk read-and-write headWave packetPresentation of a groupPhysical lawOrder (biology)Water vaporAuthorizationLine (geometry)Office suiteIncidence algebraRow (database)Phase transitionFreewareSpreadsheetComputer animation
20:14
Maxima and minimaPoint cloudCartesian coordinate systemUser interfaceUniverse (mathematics)Latent heatDataflowVirtual machineComputing platformCoordinate systemAuthorizationLevel (video gaming)Game controllerPoint (geometry)System administratorTopostheorieService (economics)File formatProjective planeProcess (computing)Software frameworkText editorSoftware testingFunctional (mathematics)Software developerCollaborationismMultiplication signFluxStandard deviationDifferent (Kate Ryan album)Open sourceObservational studyLie groupForm (programming)BitAreaRange (statistics)Stack (abstract data type)Physical systemComputer animation
Transcript: English(auto-generated)
00:07
Hello everyone. I'm Milan Antonovic. I work for the University of Applied Science and Arts of Southern Switzerland. And I'm going to present to you the Borrowed Data Management System, a web interface for Borrowed Data acquisition,
00:29
sponsored and financed by the Swiss Topological Office.
00:43
So why the first 500 meters are so important? Below the ground, the first 500 meters are the most used today.
01:00
90% of all activity are done in this portion of the underground. And the Borrowed Data reveals important information about the geological sequence of the layers. And thanks to this information, it is possible to have a very good overview of all the geological conditions of the entire country.
01:38
So what are today the common practices about producing this data?
01:45
The most used approach is producing static data. These are generated by geologists. Sometimes data are integrated into databases. And very rarely the Borrowed Data are stored using standards.
02:06
In Switzerland, the Swiss Topo produced a Federal Borrowed Data Model.
02:23
And the main focus is for the exchange of data, the usage and the quality. Having data in a standard format, we have data harmonization.
02:42
So the level of detail is well defined. The definition of the attributes are precise. And all the relations in the dependency among the data are well known. Of course, the common language between stakeholders is also important.
03:09
So last year, Swiss Topo financed to develop a first application, a web application.
03:21
Because until this moment, there was a desktop standalone application. But the users were asking to have something on the web that would be easier for sharing data with Swiss Topo.
03:43
So how is the architecture of the system? We have mainly three models. The first one is the web services. It's a Python implementation.
04:02
It relies on some well known open source softwares. And it offers a JSON API interface to interact with the data. The second layer is a JavaScript API library that exposes all the requests of the web service to the web interface.
04:38
And it's packaged in an MPM model so it can be reusable for developing a new application or extending.
04:50
And at the top we have the user interface that relies on the other two models.
05:06
And everything is now packed in a docker. So it will be easy to install and also deploy in the cloud.
05:22
So how it works? There are mainly two modes for usage. A viewer mode and an editor mode. The viewer mode is a read only access that offers access to all the published data. And offers some capability of searching, exploring with a map.
05:45
And also export selected data in various formats. Up to now PDF, CSV and shapefiles. The editor mode is used by another kind of users that have to create a new board.
06:05
And the creation process goes through a quality control flow. So this quality control process relies on four steps.
06:20
And there is also four type, four kind of roles that user can have. The first one, the editor, is who produce the data, insert new data of board and stratigraphies. And then there is a controller that check the correctness of the data.
06:43
Then there is a validator that check in a legal way the data that are inserted.
07:00
And finally the administrator that publish the data for the public. And at every step the validation can be reacted and ask for a new check. So data can have many free kind of status.
07:23
The editing is why it is in the validation and the creation process. Validated data status that is all data that have passed all the quality checks. And finally the published data that are exposed to the public.
07:48
User belong to different work groups. One user can be in more than one group. A user can have different roles in every group.
08:04
And users can only interact with data belonging to his work group. So this means that until data are published,
08:21
work groups user can only view and manipulate data belonging to this work group. In the validation process, validators and editors and controllers can exchange some messages.
08:44
So they can nominate also fields in the forms. So that it will be easier to see what is wrong and apply the modification request.
09:06
The application have a high degree of customization. So you can define which fields are visible or hidden. You can search with all the attributes.
09:23
You have six display modes. And in the map you can select different WMS overlays. Exportation in the viewer mode is quite easy.
09:42
Just select what you want to export and you can download one or more kind of export files. So in the shapefile format you just get the attributes of the borehole
10:01
without the stratigraphy and also the coordinates. In the CSV you get everything. And in the PDF you get the stratigraphy representation in a graphical format. I can show you a small demo with the help of Massimiliano.
10:45
This is the viewer mode. So on the left you can see the filters where now there are only a few ones. But you can also select more than one filter to choose.
11:02
So the viewer users can easily find the information that he is looking for.
11:25
And then there is a graphical representation of the stratigraphy. You can also zoom in, zoom out. There is no wheels here. There is a mouse behind the left.
11:43
Oh, thank you. This is because you know that generally the stratigraphy is dependent.
12:01
It can be very thin. So you can zoom in and check what is inside. And with a click you can see all the information related to the strata. And then we can go to the editor mode. We are now have login as administrator.
12:22
So we have all the roles. There is the multi-language support. So also here you have all your data in the validation process.
12:43
You can filter by the states of the data or other kind of filters. On the left we have the three levels of data insertion.
13:12
So the first is information about the location. The second one is about the borrower information.
13:23
And in the last one we can add one or more stratigraphy.
13:40
And on the right side we see the validation part. Where now we see that it has been reacted during the validation. And a technical check is needed.
14:00
So the process can go up and down until it is published. There is this lock and unlock feature. So only one user at a time can edit the data.
14:33
And with this system you can nominate some fields. That then during the next validation process are rejected.
14:51
And then they become red so the user can faster find where are the problems.
15:02
So there is this flow part in the validations. And depending on the stage you see this bar that shows and activate the mode to check or not. You can refer to different fields. And the fields get underlined in red where there is some issues related. So the data can go through this validation process until the end.
15:24
And depending on the role of the logged user you have different possibility or not to do some actions.
15:47
You can have more than one stratigraphy from one borehole. This depends on the different interpretation. So the idea is to have maybe some more geological interpretation and then geotechnical interpretation.
16:01
So that you can access directly to different information about the soil properties. Because this is not a unique interpretation of stratigraphy. And yes, I don't know if there is anything more to add.
16:23
At the stage of the process of the project now we are in the... Let's say we finished the first prototype deployment that now is in demo for testing as we stop. And then from now to the end of the project we have scheduled the competition of all the details for having the first release.
16:45
Released version.
17:08
That's it. Thank you. Any questions? Can you take the mic?
17:38
Maybe I'll take your mic. Okay.
17:41
Thanks for the presentation. I've been involved most of my professional life in capturing geological data and evaluating it. And for me the biggest problem is at the sites, at the drill rig, logging the data. And after the model garbage in, garbage out.
18:03
If you don't have data entered in a common way, all the other technologies are not so useful. How are you dealing with that? Coming up with a common vocabulary for entering data. I mean, very simply, what do the headers look like in the spreadsheets or the CSV data that are input into the system?
18:25
And further, what standards are being followed? I mean, most of the world are probably following standards like ASTM, more for soils, and ISRM, more for rock mechanics. And they have vocabularies and they have recommendations and guidelines for how one can input data or at least collect the data.
18:44
How is all this being handled? In Switzerland they have developed this Borel data model. And there is defined everything from the vocabulary to the ontologies to the patterns representing all these layers.
19:12
I can add maybe this type of standard in Switzerland is what you can reflect with INSPIRE. You know, Switzerland is not part of Europe, but anyway it's compliant with INSPIRE.
19:25
So what they implemented at national levels, a strategy and implementing different data models for different topics. And they tend to be very, very compliant with international standards and INSPIRE.
19:41
So I don't know actually which kind of standard they use for a single type. But the ontology that they use, they take from normal standards. So also the patterns for colorings and all these kinds of things, they use international standards. And in the interface, when you enter the data, you are forced to select one of the options of the vocabulary that you have.
20:06
You cannot, almost nowhere is free text to enter. And the general idea behind this interface is that when you apply for making a new Borehole in Switzerland, you need to ask for the permissions.
20:26
And the local authority gives you the permission and asks you to return back the data. And nowadays it's very difficult to check if the company then gives back the data or not.
20:42
And the idea is to have this interface so that when you give a permission, then you can also force them to give back the data in the platform. So you have the right formats and at the same time it's very easy to check who is late to give back the format and contact and why and etc.
21:01
And then this platform should also range at different levels. So cantonal levels can collect their data and then push using the standard format to the federal levels. And then they decide if they incorporate this in their portal, for example Swiss Topo or not,
21:22
because some of the points are not of interest for the federal level and these kinds of things. So this is trying to harmonize all the flux of data from the user, the producer to the publication.
21:43
Any other questions? How many resources do you have to create this project? Like people who develop the project or money and so on?
22:04
We have the collaboration of two people from Swiss Topo that coordinate the projects. And then in Subsea we are three persons, Milan, which is the main developers, then me, that's helping some of the developers and other people more for the contacts and coordination of the teams.
22:28
From a budgetary, the whole thing is about 50-60 thousand US dollars. Considering the Swiss salary standard is not much.
22:43
But of course we are a university so we have a different price respect today, but we have also different interests in exploring and testing and developing new things.
23:08
How many users do you expect to use this system? How many editors and how many just viewers? At least, I don't know.
23:34
We actually don't know how this platform goes in the future, but generally discussing with the people from Swiss Topo, we don't expect so many people using the platform.
23:46
At least from this flow control process and things like that, maybe 100 or something like this. As an editor this is different, it depends how this will be taken from local authorities, they give the permits to people to enter the data.
24:06
So if they take us and those applications to use for their day-to-day work, this can be used much better. I wouldn't expect 2000 concurrent users for this kind of application. Have you considered using functions instead of building standard stack like Lambda
24:37
or Azure functions or Google functions, doing it directly into the cloud?
24:44
Not really, because it's not just oriented for the cloud and using Amazon or specific framework. So the idea is to offer this application as a service on the cloud, but if someone,
25:08
the administration of some controls or something want to use it, can install easily on their machines. Thank you.