GBA Data viewer
- 1. DataViewer Martin Schiegl Geoinformation Section Geological Survey of Austria 2015 an application to analyze geological units
- 2. Thesaurus project » started in 2011 as LinkedOpenData project » a knowledge representation for geosciences » compensate the temporary discontinuation of the Austrian Stratigraphic Commission » using semantic web capabilities (RDF/SKOS, URI‘s) http://resource.geolba.ac.at » provide codes for attributing data (e.g. for missing INSPIRE codelists) Wien, 2015
- 3. DataViewer module » A modul/extension of GBA Thesaurus » Live access to harmonized data sets » One query for all geological datasets at all scales » To improve the quality and process of harmonizing datasets » live feedback on impacts of modelling the vocabularies and applying » The ”practical definition” of lithostratigraphic units, to look for lithological information Wien, 2015
- 5. Data model for Geology Wien, 2015 features in red are used for navigating the DataViewer
- 6. Coding with URI’s from.. (unique resource identifier web address)≅ » GBA Thesaurus data linked to INSPIRE and GeoSciML − 250 lithological concepts − 3 different time scales (ICS2013, ice ages, Paratethys) − 800 geologic Units (e.g. geol. formations) − 300 tectonic units (e.g. Austro alpine nappes) » GeoSciML vocabulary (Event process, environment) » INSPIRE codelists mapped to GBA Thesaurus Wien, 2015
- 7. Data Sets - 2015 Wien, 2015 Geological maps 1:50.000 1GE-surface geol. 1:500.000
- 8. Data Sets - 2016 Wien, 2015 Geological maps 1:50.000 Geofast 1:50.000 1GE-surface geol. 1:500.000
- 9. Data Sets - 2018 Wien, 2015 Geological maps 1:50.000 Geofast 1:50.000 Geological maps 1:200.000 1GE-surface geol. 1:500.000 Rocky Austria 1:1Mio
- 10. Technical overview Wien, 2015 HTML-Web page •Javascript, CSS 3 •jQuery . Ajax •Leaflet •RequireJS, AMD Module Map display •ArcGIS-REST-Service •JSON-Queries (points) •PNG-Export (polygons) •Base map WMTS •ArcGIS-Imageservices Facetted filter •MS-SQL-Server •ASP.NET ASHX Handler •Entity Framework 6.1 •MVVM Concept (Knockout) Thesaurus data •SESAME triplestore SKOS/RDF JSON •PoolParty 5.0 Server, Tomcat webserver (Apache), Ubuntu •Sparql-Endpoints MapMap geodatageodata SelectionSelection graph datagraph data FilterFilter SQL dataSQL data
- 12. Wien, 2015 thank you for your attention questions? mailto: Martin Schiegl – coordinator, design Arno Kaimbacher - programmer Christine Hörfarter – geologist, editor Miroslav Janata – programmer, prototype
Editor's Notes
- #3: a controlled vocabulary of geoscientific concepts, on six different domains like Lithology or timescale. The concepts are modelled as a Thesaurus which defined by polyhierarchies as broader, narrower, and related concepts, designed as a knowledge representation of our geological survey, e.g. contrary to international standards like INSPIRE codelists, or other dictionaries Published bilingual in German and English. As used in our own text publications and geological maps .. and the it has semantic web capabilities (RDF/SKOS, URI‘s) formatted as so called SKOS concepts (terms, including synonyms), Each concept has its own web address the so called URI. Unique resource identifier. These web addresses we use for encoding geological data. The process of data harmonization. On the other side our thesaurus is connected to other resources published in the web, that is what we call the LinkedData part. Actually our Thesaurus refers to 4 LinkedData resources DBpedia-> Wikipedia, INSPIRE, GeoSciML and BGS rock classification system it is machine-readable published using web services ( Sparql endpoints) according to the standards of W3C
- #4: Then the DataViewer should improve the quality and process of harmonizing datasets Give a live feedback whether modelling of hierarchies and relationships in Thesaurus are right or wrong It is a tool to identify errors in map data. Maybe useful for a compilation all over the country (And it is also a tool to verify the structure of thesaurus, whether the construction of hierarchies and relationships are reliable)
- #6: The data model which runs behind this application is derived from INSPIRE geology core model
- #7: All geological data to be analyzed is coded with so called URI‘s. An acronym for „Unique resource identifier“. Actually it is a web address of the code or concept.