1. GeoSciML Implementation by Agnès Tellez-Arenas

2. GeoSciML implementation 1. First step: data mapping preparation of the services WMS,WFS Data Specification (the attributes delivered). Vocabularies (content of the attributes) 2. Second step: schema transformation GML => GeoSciML: WMS.getFeatureInfo, WFS.getFeature GeoSciML => GML: WMS.getMap using GeoSciML expressed SLD WFS.getFeature using queries How implement GeoSciML by a Web Service? For client applications, what utilisation of GeoSciML?

3. GeoSciML implementation What a GeoSciML Web Map/Feature Service is? > It is a service delivering features > The features are expressed in several formats: In Image (getMap request) In text or HTML (getFeatureInfo) In XML (getFeatureInfo, getFeature). In that case, the XML delivered is GeoSciML (instead of usual GML).

4. GeoSciML implementation What a GeoSciML Web Map/Feature Service is? > It is a service delivering features > The Data Model of these features is a schema (a structure) who respects GeoSciML: Content of the data (numerical, free text, of urn referencing GeoSciML concepts) Organization of the data (names of the fields and structure).

5. GeoSciML implementation Example of key attribute/value expressed in GeoSciML > For example, “lithology” is a field named (i.e. the path): “ gsml:composition/gsml:CompositionPart/gsml:lithology@xlink:href ” Which the GeoSciML value is urn:cgi:classifier:CGI:SimpleLithology:2008:sand > Instead of the GML name: “ brgm_litho_multiple ” Which the value is “ sable d’Orléans ” The GML name (and value) is specific to a dataset. The GeoSciML name (and value) is “generic”, harmonized, standard.

6. GeoSciML implementation What are the steps for implementing a GeoSciML service? First Step: Data Mapping 1. Create a new dataset, copying the “starting from” dataset A new table in a database, or a new shapefile a) Add one column by GeoSciML attribute Depending on the Data Model b) From columns of the “starting from” dataset, deduce the textual (or numerical) values of the GeoSciML attributes. This step should require the participation of an IT person and a data content expert (geoscientist).

7. GeoSciML implementation What are the steps for implementing GeoSciML service? First Step: Data Mapping c) Some attributes (depend on the Data Model) must have values took inside a GeoSciML vocabulary. These values are Controlled Concepts identified by URN (Unified Resource Name). A GeoScientist expert must decide, for each possible value (textual value in the “starting from” column), which GeoSciML Controlled Concept corresponds. The GeoSciML Controlled Concepts are organized in trees (hierarchy), therefore the GeoScientist can simplify the “local data” if it doesn’t exist in the GeoSciML vocabulary. The aim is to provide a WMS / WFS delivering usual GML with attributes and values following the Data Specification.

8. GeoSciML implementation What are the steps for implementing GeoSciML service? First Step: Data Mapping Example 1. In a GeoSciML Data Model, we decide to store the lithology as up to five fields (to express multiple lithology). 2. The objective is to produce a dataset with the following attributes: > urn_litho_1, urn_litho_2, urn_litho_3, urn_litho_4, urn_litho_5 > Which each value is took from the official the GeoSciML vocabulary urn:cgi:classifierScheme:CGI:SimpleLithology:200811.xml 3. In the “starting from” national dataset, lithology is stored inside a unique field named “brgm_litho_multiple”, which values are free texts: > sables, argiles, graviers, galets

9. GeoSciML implementation What are the steps for implementing GeoSciML service? First Step: Data Mapping Example 4. Starting from a unique field which value is “sables, argiles, graviers”; the Objective is to obtain: urn_litho_1=urn:cgi:classifierScheme:CGI:SimpleLithology:200811:sand urn_litho_2=urn:cgi:classifier:CGI:SimpleLithology:2008:non_clastic_siliceous_sedimentary_rock urn_litho_3= urn:cgi:classifierScheme:CGI:SimpleLithology:200811:rock urn_litho_4= urn_litho_5= 5. The GeoSciML path of each lithology field is: > gsml:composition/gsml:CompositionPart/gsml:lithology@xlink:href The GeoSciML vocabularies are available here: http://appgeosciml.brgm.fr/GeoSciMLWeb/middleware.jsp Some GeoSciML vocabularies used for the OneGeology-Europe project: http://appgeosciml.brgm.fr/Voca/www/vocabularyLitho.jsp

10. GeoSciML implementation What are the steps for implementing GeoSciML service? First Step: Data Mapping Example http://onegeology-europe.brgm.fr/demoServices/index.jsp

11. GeoSciML implementation Second Step: Implement the GeoSciML schema Starting from the Data Specification implemented in step 1: 22763.700000,1602697.400000 1215763.800000,2682702.500000 17722 urn:cgi:classifier:ICS:StratChart:2008:Holocene Lithologie: sables, argiles, graviers, galets urn:cgi:classifier:CGI:SimpleLithology:2008:sand urn:cgi:classifier:CGI:SimpleLithology:2008:non_clastic_siliceous_sedimentary_rock

12. GeoSciML implementation Second Step: Implement the GeoSciML schema The objective is to generate the GeoSciML schema:

13. GeoSciML implementation Second Step: Implement the GeoSciML schema Example http://onegeology-europe.brgm.fr/demoServices/index.jsp There does not exist any WMS or WFS software implementing GeoSciML. It is necessary to add a component front of the WMS/WFS to handle/generate GeoSciML.

14. GeoSciML implementation What a GeoSciML Web Map/Feature Service is? > WMS (View service) Metadata (GetCapabilities): Usual WMS GetCapabilities View (GetMap): – If using external SLD, for example user-defined SLD for “query and view” applications, or using harmonized external SLD: SLD is expressed with GeoSciML path (instead of GML path). Get the Data (GetFeatureInfo): if requested in XML, should be delivered in GeoSciML. > WFS (Query and use/download service) Metadata (GetCapabilities): Usual WFS GetCapabilities Get the Data (GetFeature): if requested in XML, should be delivered in GeoSciML. – If using query (filter), the query is expressed with GeoSciML path (instead of GML path).

15. GeoSciML implementation What are the steps for implementing GeoSciML service? Second Step: Implement the GeoSciML schema > WMS (View service) Metadata (GetCapabilities): Usual WMS GetCapabilities In the GetCapabilities, the outputFormat for the GetFeatureInfo must include “text/xml”. Nothing else.

16. GeoSciML implementation What are the steps for implementing GeoSciML service? Second Step: Implement the GeoSciML schema > WMS (View service) View (GetMap): If using external SLD, for example user-defined SLD for “query and view” applications, or using harmonized external SLD: SLD is expressed with GeoSciML path (instead of GML path). Example: http://onegeology-europe.brgm.fr/demoServices/index.jsp http://onegeology-europe.brgm.fr/demoServices/index.jsp The GeoSciML Component must: > Handle an external SLD > Transform the SLD with GeoSciML path into a SLD expressed using local paths

17. GeoSciML implementation GeoSciML SLD Example GML OGC filter used in the SLD to query and view the dataset urn_litho_1 urn:cgi:classifier:CGI:SimpleLithology:2008:sand The same OGC filter expressed in GeoSciML gsml:composition/gsml:CompositionPart/gsml:lithology@xlink:href urn:cgi:classifier:CGI:SimpleLithology:2008:sand

18. GeoSciML implementation What are the steps for implementing GeoSciML service? Second Step: Implement the GeoSciML schema > WMS (View service) Get the Data (GetFeatureInfo): if requested in XML, should be delivered in GeoSciML. Example: http://onegeology-europe.brgm.fr/demoServices/index.jsp http://onegeology-europe.brgm.fr/demoServices/index.jsp The GeoSciML Component must: > Read the GML generated by the OGC WMS server > Transform it into GeoSciML

19. GeoSciML implementation What are the steps for implementing GeoSciML service? Second Step: Implement the GeoSciML schema > WFS (Query and use/download service) Metadata (GetCapabilities): Usual WFS GetCapabilities In the GetCapabilities, the outputFormat for the GetFeature must include “text/xml; subtype=geosciml/2.0”. Nothing else.

20. GeoSciML implementation What are the steps for implementing GeoSciML service? Second Step: Implement the GeoSciML schema > WFS (Query and use/download service) Get the Data (GetFeature): if requested in XML, should be delivered in GeoSciML. If using query (filter), the query is expressed with GeoSciML path (instead of GML path). The GeoSciML Component must: > Handle the query expressed in GeoSciML > Transform it (replacing GeoSciML path by local path) > Transfert the query to the OGC WFS server, then read the GML generated > Transform it into GeoSciML

21. GeoSciML implementation For client applications, what utilisation of GeoSciML? > Example of OneGeology-Europe project

22. GeoSciML implementation For client applications, what utilisation of GeoSciML? Interesting functionalities on such harmonized datasets: > Query and view: Using external SLD and getMap requests to query datasets > Query and print / download: Using query and WFS to query then print or download the features > Multilingualism: Data content: the getFeatureInfo or GetFeature response is expressed in GeoSciML. Using GeoSciML vocabularies (where each Concept is translated), the terms used can be translated by the client application. Legend: in the case of a legend based on a SLD known by the client application, this application is able to display a legend translated (same process as translation of GetFeatureInfo or GetFeature).

23. GeoSciML implementation Conclusion > GeoSciML WFS, with some filters allowed in the query: Already implemented in GeoSciML testbed > GeoSciML WFS, already implemented by several OneGeology Global WFS To be implemented and used into OneGeology Europe project