for the Vocabulary to describe Spatial Geological Data in Europe at a 1 : 1 Million Scale - for the econtentplus project OneGeology-Europe

Transcription

1 Explanatory Notes for the Vocabulary to describe Spatial Geological Data in Europe at a 1 : 1 Million Scale - for the econtentplus project OneGeology-Europe Updating and amending the OneGeology-Europe Scientific/Semantic Data Specification and Dictionaries (ECP GEO ) Objective of this document This document provides explanatory notes designed to show how the scientific vocabulary developed by OneGeology-Europe Work Package 3 will populate the data model, developed by Work Package 5. It is designed to be read by those responsible for encoding geological map data in the national geological survey partner organisations of OneGeology-Europe. The document provides guidance on the agreed vocabulary, the terms, their definitions and their relations, which must be used by all OneGeology-Europe participants. This vocabulary is the core of the OneGeology-Europe data specification. It is attached as separate Excel files. An introductory explanation of the relevant parts of the GeoSciML data model along with guidance on the usage of GeoSciML are also included to provide initial context. This version has been updated for use in the OneGeology-Europe Plus project. Authors: Asch, K., Laxton, J.L., Bavec, M., Bergman, S., Perez Cerdan, F., Declercq, P.Y., Janjou, D., Kacer, S., Klicker, M. Nironen, M., Pantaloni, M., Schubert, C. dated May 2013

2 Contents A short introduction to OneGeology-Europe 4 1. Explanatory Notes and vocabulary 4 2. Introduction to the GeoSciML model and its use within 1G-E MappedFeature and GeologicFeature Ages and events Lithology Metamorphism 9 3. GeoSciML properties and how to encode them for 1G-E MappedFeature Properties Observation Method Positional Accuracy Shape Sampling Frame GeologicUnit properties ID Name Description GeologicUnit Type Observation Method Purpose Geologic Events Preferred Age Geologic History Composition Part Lithology Role Proportion Metamorphic Description Metamorphic Facies Metamorphic Grade Protolith Lithology Dykes/Dikes GeologicStructure properties ID Name Observation Method Purpose Geologic Events Preferred Age Event Age Event Process Event Environment Fault Type Contact Type Complex Rock Descriptions Flysch Molasse Olistostrome Turbidite 27 Version 1.0 2

3 4.5 Ophiolitic mélange Tectonic mélange Ophiolite complex Acknowledgements Bibliography 29 *Note that the vocabulary has been produced and supplied as separate Excel files. Version 1.0 3

4 A short introduction to OneGeology-Europe One of the major deliverables of the OneGeology-Europe (1G-E) project is the creation of a web accessible, semantically and technically interoperable geological dataset, for Europe at a 1 : 1 million scale (1:1 M). This is based on the geological data held by each geological survey. However, the survey datasets differ considerably with respect to their contents, description and geometry. To make these data interoperable is a considerable challenge and it is the task of 1G-E Work Package 3 (WP3) to deliver the essential basis for the interoperable dataset. The 1G-E Geology vocabulary describes the lithology, age and genesis of the rocks and the tectonic structures. The vocabulary provides both the definition of terms and the relationship between terms. The 1G-E project is using a distributed digital model that leaves the data with the responsible geological survey organisation. Each survey provides access to its data via the internet and the 1G-E portal will harvest that data. Thus, each geological survey implements and hosts an interoperable web service, delivering their national geological data in a semantically harmonized form. This vocabulary is the way geological surveys participating in 1G-E will describe the geology of their country within the project and how they deliver that data in accordance with the agreed 1G-E data model and overarching data specification. It is important to note that the original national databases, internal classifications and the vocabulary will remain unchanged. Once the national datasets have been provided to the project in accordance with this vocabulary, the WP3 team and surveys will then review these datasets, note issues and rework them with partners to make progress towards a geometric harmonisation a further crucial step towards INSPIRE goals. The vocabulary and framework developed here is intended to be subsequently up-scaled to more detailed levels and progressively deployed for higher resolution geological data. (However, this is not part of the 1G-E project) 1. Explanatory Notes and vocabulary Geology does not recognise political boundaries, however, from one country to another the properties of the same rock formations will, with a high probability, be described differently; whether this be their lithology (i.e. the rock material), the age, or the genesis. Furthermore, the rock formations will be portrayed with different colours and symbols. The European Commission and many other users require consistent data about the geology of each country; data which does not change its attributes or portrayal as it crosses political boundaries. The EC INSPIRE Directive (2007) is addressing these issues, along with the EC Water and Soil Directives. An internationally agreed generic definition and description of the data both technically and geoscientifically - a data specification - is thus essential. This document provides an explanation and background to the Europe-wide data specification and in particular, the vocabulary, for the 1G-E project. Applying this vocabulary across Europe will allow the national geological units to be described in a semantically harmonised way. The vocabulary encompasses terms, definitions, a hierarchical order, a reference and a Uniform Resource name (URN). The topics included in this vocabulary are: 1. lithology, 2. age (geochronology), 3. genesis, 4. structures and faults Version 1.0 4

5 These themes are described in the tables (Excel spread sheets), an overview of which is provided in Table 1. Genesis was included during the course of the work although it is not listed in the project s original work description. WP3 decided to include a vocabulary for Genesis, because describing the genesis of the rock units is deemed essential to describing the Quaternary, which covers large areas of Europe, it is also important for other rock units. Table 1: Files specifying the 1G-E vocabulary Excel spread sheet describing the concepts and terms File showing the concept hierarchy Property the concepts describe 1GE_Lithology.xls 1GE_Lithology_entire_A1.pdf *, 1GE_Lithology_sedimentary_material.pdf *, 1GE_Lithology_igneous_material.pdf *, 1GE_Lithology_composite_genesis_mater ial.pdf lithology 1GE_Ages.xls 1GE_Ages.pdf eventage (for preferredage) 1GE_Orogenic_Events.xls 1GE_Orogenic_Events.pdf name (of GeologicEvent) Description of the property mandatory / optional** mandatory mandatory optional 1GE_EventEnvironment.xls 1GE_EventEnvironment.pdf eventenvironment optional 1GE_EventProcess.xls 1GE_EventProcess.pdf eventprocess mandatory 1GE_MetamorphicGrade.xls 1GE_MetamorphicGrade.pdf metamorphicgrade optional 1GE_MetamorphicFacies.xls 1GE_MetamorphicFacies.pdf metamorphicfacies optional 1GE_GeologicUnitMorphology.xls Not necessary bodymorphology optional (mandatory for dykes) 1GE_FaultType.xls 1GE_FaultType.pdf faulttype mandatory (for faults) 1GE_ContactType.xls 1GE_ContactType.pdf contacttype mandatory (for contacts) 1GE_ProportionTerm.xls 1GE_ProportionTerm.pdf proportion mandatory 1GE_GeologicUnitPartRole.xls 1GE_GeologicUnitPartRole.pdf role mandatory 1GE_GeologicUnitType.xls No concept hierarchy file necessary geologicunittype mandatory 1GE_MappedFeatureObservationMet No concept hierarchy file necessary observationmethod mandatory hod.xls (for MappedFeature) 1GE_FeatureObservationMethod.xls No concept hierarchy file necessary observationmethod (for GeologicFeature) mandatory * Note: These files explain the hierarchies; please either view and zoom into them on screen or print them out in A1 (as the file name indicates) or A3 ** Certain properties are mandatory and some are optional, however, if an optional property is populated then the terms within the 1G-E Vocabulary must be used to describe it. In producing the vocabulary element of the data specification WP3 has worked in close collaboration with WP5 and WP6. These notes are designed to explain how the scientific vocabulary developed by WP3 will populate the 1G-E data model developed by WP5. The basis for the 1G-E vocabulary (and data specification) is the GeoSciML data model and the CGI/GeoSciML vocabulary, both developed by the IUGS Commission for the Management and Application of Geoscience Information (CGI) Interoperability Working Group (IWG) and Concept Definitions Task Group (CDTG). Version 1.0 5

6 The CGI Simple Lithology vocabulary uses multiple, overlapping hierarchies and offers numerous detailed ways how to classify and identify a rock unit. For 1G-E, which addresses spatial data at a target scale of 1 : 1 Million this proved to be too complex and would make harmonisation significantly more difficult. WP3 selected an adequate subset of the CGI vocabulary, and submitted more than120 new terms and concepts and several definitions to the CGI vocabulary in order to meet European requirements. The process of delivering an agreed set of terms involved many discussions and iterations between CGI experts and WP3. The aim was that to build one set of terms for 1G-E that would be a part of the global vocabulary. The dialogue was successful with compromises necessary on both sides. There are only two additional elements in the 1G-E vocabulary that are not globally applicable and will be a part of a specific European, rather than a global vocabulary: European terms for Orogenic events and additional sub-divisions of the Pre- Cambrian at epoch level. An initial first version of the vocabulary was developed by nine geological survey partners within the WP3 core team. It then underwent a thorough review process by the 20 project member surveys and eight partners, including two NGOs outside the project (the Commission of the Geological Map of The World and the IUGS Concept Definition Task Group). The return rate on review comment was substantial: 532 comments were received. This demonstrates the sometimes passionate European interest in geological specifications, and accordingly that any pan-european specification will be highly contentious. The vocabulary deals with an extremely sensitive issue as each European nation has a long held tradition of describing geoscience data in accordance with its own national conventions. Thus, the vocabulary produced by WP3 represents a compromise between national schemes; a pan-european cross-boundary approach for geological map data at 1:1 M scale; and consistency with a global vocabulary. Version 1.0 6

7 2. Introduction to the GeoSciML model and its use within 1G-E This section is designed to provide an introduction to that part of the GeoSciML data model that is used by 1G-E. It is not intended to be a full explanation of the GeoSciML data model, but provides initial context and background so that partners may understand how the vocabulary relates to it. 1G-E used GeoSciML v2.1 and it has been decided for simplicity and to achieve harmonisation that 1G-E+ should also use this version. All references to GeoSciML in this document therefore refer to GeoSciML v2.1. Note however that GeoSciML v3.1 is the currently released version and that there are some significant differences between this version and GeoSciML v2.1. Full documentation is available at and an encoding cookbook, covering the main features of the model, is available at _V2.1_1.0.pdf. Specific and detailed GeoSciML technical information will be provided as a 1G-E online resource by Work Packages 4, 5 and 6. GeoSciML follows the encoding rules from ISO Annex E for GML and is therefore a profile of GML. This means that it inherits some properties (attributes), in particular for the specification of geometry, from GML Explanation of terms 'Concepts', 'terms', 'properties', features and 'vocabulary' The relationship between 'concepts', 'terms', 'properties', and 'vocabularies' can be confusing and merits explanation. 'Concept' is a term that comes from philosophy and can be defined as 'a general idea or notion that corresponds to some class of entities and that consists of the characteristic or essential features of the class'. For example in geology 'fault', 'lithology', 'Mercia Mudstone Group', and 'sandstone' are all concepts. A concept is given a label that is used to identify it and a definition that provides the 'characteristic or essential features of the class' described by the concept. These labels are commonly referred to as 'terms', so that 'sandstone' can be referred to as a 'term' but it is really a label for the concept 'sandstone'. A data model identifies the 'real world' objects in the field of interest and their characteristics. The objects are modelled as 'features' and the characteristics as 'properties' of those features. So for example in the GeoSciML data model we have a 'GeologicUnit' feature with properties such as 'geologicunittype' and 'unitthickness'. These properties will have particular values in particular instances, for example the geologicunittype might be 'Lithostratigraphic'. Geologic Unit, Geologic Unit Type and Lithostratigraphic are all concepts, but it is useful to group together those concepts that are used to provide the values for a particular property. This is done by grouping these concepts in a vocabulary which contains the concept label and the concept definition. For example, all concepts that can be used to populate the geologicunittype property are grouped together in the GeologicUnitType vocabulary (Table 1GE_GeologicUnitType). Version 1.0 7

8 2.1 MappedFeature and GeologicFeature Central to GeoSciML are two features, MappedFeature and GeologicFeature, which require explanation. GeologicFeature is used to describe real-world geological features the full geometric extent of which is unknown. A MappedFeature can be seen as a view of a GeologicFeature and any GeologicFeature can have several such MappedFeature views. On published geological maps different polygons depicting the same rock unit are generally depicted with the same symbolisation and have a single description in the map key. In GeoSciML each such polygon is a distinct MappedFeature all of which are a view of the same GeologicUnit. Other MappedFeature views of the GeologicUnit might occur on geological maps of different scales or as volumes in a 3D model for example. A MappedFeature is therefore mainly a holder of geometry whereas a GeologicFeature is a holder of descriptive properties. In the present implementation of GeoSciML there are two types of GeologicFeature GeologicUnit (for bodies of rock) and GeologicStructure (for geologic structures). Most of the information we are encoding for 1G-E will be for GeologicUnits, although we will use GeologicStructure for faults, calderas, impact structures and glacial stationary lines. 2.2 Ages and events In GeoSciML ages and events are bound together in the feature GeologicEvent. Any age must be the age of some event happening, for example the age during which deposition of a sedimentary rock took place; the age of intrusion of an igneous rock; the age of crystallisation of an igneous rock; the age of a particular period of folding; the protolith age of a metamorphic rock; the age of the final phase of metamorphism. In GeoSciML an age can be recorded as a numeric value or as a geochronologic term, and both numeric and term ages can be given as single values or as a range. Note this age range is to record a time period and is distinct from an error range on a numeric age which can also be recorded. GeoSciML allows the recoding of both a preferredage and a geologichistory for any GeologicFeature. The preferredage property allows a single age, which can be a range, to be given to a GeologicFeature. The geologichistory property allows a series of GeologicEvents to be recorded that led to the formation of the unit, for example in the case of a metamorphic rock there might be a primary deposition event followed by several metamorphic events. 2.3 Lithology In GeoSciML a GeologicUnit can be composed of one or more CompositionParts, each of which is a discrete lithology which together form the GeologicUnit. In 1G-E the use of lithology terms, drawn from the 1G-E-enriched CGI Simple Lithology vocabulary will be implemented. Version 1.0 8

9 2.4 Metamorphism For large scale maps GeoSciML offers packages of descriptive properties to allow a very detailed description of particular aspects of a GeologicUnit, such as bedding, weathering, physical properties, and metamorphism. Because 1G-E is addressing small-scale overview maps of a scale around 1: 1 Million most of these will not be a part of the 1G-E vocabulary and model. An exception is the MetamorphicDescription package which will be described in section GeoSciML properties and how to encode them for 1G-E This chapter will describe those GeoSciML properties that are used in 1G-E and the values to use to encode them in other words: how to map from terms in your database to GeoSciML. Please note that this chapter discusses the semantic requirements for encoding 1G-E and it is recommended that you read it in conjunction with Section 4 of the GeoSciML cookbook ( How to Map Data to GeoSciML Version 2 ) which gives more detail on the XML encoding. The terms that are used to populate properties in 1G-E should be uniquely identified and reference a concept and its definition. These concept definitions are generally held in a vocabulary. The WP3 team ensured that legitimate requirements identified by project members, (the core team or feedback within the review process) were considered and included if possible in the CGI vocabulary. Thus, the CGI vocabulary was modified to ensure it met European requirements. For the unique and unambiguous identification of concepts and terms, URNs are being used within 1G-E, following the conventions used by the CGI and OGC. Subsequent to the 1G-E project the use of has become preferred to URNs, and these are used in current versions of the CGI vocabularies. However for reasons of simplicity and harmonisation it has been decided to continue the use of URNs in 1G-E+. The URNs relating to specific concepts and terms are given in the 1G-E vocabulary, these URNs must be used to populate properties in 1G-E. More information on the structure of CGI URNs is given at Examples of GeoSciML code are provided as figures within the text. Please note: Unless it is specifically stated that they are optional all the properties described in the following sections are mandatory to use for 1G-E (see also table 1). 3.1 MappedFeature Properties Observation Method The observationmethod property of MappedFeature enables the distinct methodologies for observing the geometry to be recorded. Note that this is distinct from the observationmethod property of GeologicFeature which enables the distinct methodologies for observing the GeologicFeature properties to be recorded. For 1G-E the MappedFeature observationmethod property should be set for all MappedFeatures to urn:cgi:classifier:cgi:mappedfeatureobservationmethod:201001:compilation (see example in Figure 1) Version 1.0 9

10 3.1.2 Positional Accuracy This property is designed to provide an indication of spatial resolution. For 1G-E it should be provided as a numeric value in metres to indicate the distance from the given geometric position that a feature could be. The value is centred on the geometric position so that a positionalaccuracy value of 500m means +/- 500m about the geometry. It is recommended that the same, approximate, value be given for all MappedFeatures and will generally be around 250m for a 1:1 M scale map Shape This property holds the geometry of the feature as a series of co-ordinate pairs. The geometry can be of any appropriate GML geometric type, but for a GeologicUnit will typically be a Polygon with LinearRing structures defining the outerboundary and innerboundary (for holes ), and for a GeologicStructure will typically be a LineString (see figure 2) Sampling Frame This property indicates the spatial reference frame within which the features have been observed. For 1G-E this should be set to urn:cgi:feature:cgi:earthnaturalsurface for the surface map and urn:cgi:feature:cgi:bedrocksurface for the bedrock map (see Figure 1). Figure 1: Example of the coding of MappedFeature properties. Figure 2: Example of the coding of shape (geometry). Version

11 3.2 GeologicUnit properties ID Each GeologicUnit should be given a unique identifier. This is for use within application processing rather than for information exchange, so the ID value can be anything as long as it is unique Name Normally a GeologicUnit on a map would have a name, typically recorded in a stratigraphic lexicon. In 1G-E there has been no attempt to harmonize lithostratigraphy and create a single integrated stratigraphic lexicon for Europe. GeologicUnits will be portrayed in 1G-E web services on the basis of their age or lithology rather than lithostratigraphy. There is therefore no requirement to name GeologicUnits and use of the Name property is optional. However you may wish to use the Name property of GeologicUnit to record the name of the unit used in your own stratigraphic lexicon which would therefore provide a link to the full original description of the unit. No retrieval or symbolisation based on this name will be implemented in 1G-E but such a link could be implemented in the future if required. If you wish to give a name to the GeologicUnit from your own stratigraphic lexicon you should give it an URN following the CGI pattern described at An example of this is (from the BGS Stratigraphic lexicon): urn:cgi:classifier:bgs:stratigraphiclexicon:mmg where: BGS = Registered CGI Party responsible for the resource. (A full list of registered CGI parties, who are able to register resources, is available at If your organisation is not on this list you can apply to have it added following the instructions on this web page. You can then register your resources (eg a classification scheme) in the CGI Authority Register following the procedures given here: StratigraphicLexicon = the name of the vocabulary within which the concept being referenced is held. MMG = the identifier for a specific concept, in this case the MERCIA MUDSTONE GROUP. Note that the resource referenced does not need to be available in digital form; the URN is simply providing an identifier not an address. You can give multiple names to a GeologicUnit. The example shown in Figure 3 demonstrates that the name can also be presented in natural language in addition to the name giving the URN. Version

12 3.2.3 Description You can use this property to provide a free-text description of the GeologicUnit. Use of the Description property is optional and will not be used for retrieval. It could be used to provide useful information about the GeologicUnit that is not provided elsewhere in the 1G-E specification GeologicUnit Type Each GeologicUnit must be given a geologicunittype value drawn from the GeologicUnitType vocabulary (Table 1GE_GeologicUnitType.xls, see Vocabulary). The GeologicUnitType refers to how the GeologicUnit was defined/delimited, not how it will be portrayed in 1G-E. Most maps contributing to 1G-E are likely to have a combination of Lithostratigraphic Units and Lithodemic Units. If these can t be practically separated for encoding, they could all be grouped as Lithologic Units Observation Method The observationmethod property of GeologicUnit enables the distinct methodologies for observing the GeologicFeature properties to be recorded. Note that this is distinct from the observationmethod property of MappedFeature which enables the distinct methodologies for observing the geometry to be recorded. For 1G-E the GeologicUnit observationmethod property should be set to either urn:cgi:classifier:cgi:featureobservationmethod:201001:data_from_single_publishe d_description where the property values are derived from a single source document, or urn:cgi:classifier:cgi:featureobservationmethod:201001:synthesis_of_multiple_publi shed_descriptions where they are derived from multiple source documents (see Figure 3) Purpose This property is used to state if the GeologicUnit description is of an instance, as would be the case for a field map for example, or a type of normative description such as might occur in a Stratigraphic Lexicon. On published maps the descriptions are generally normative and given in the map key and possibly in a related Stratigraphic Lexicon. For 1G-E the Purpose property should be set to typical_norm, as shown in Figure 3: Figure 3: Example of the coding of a Geologic Unit Name, Description, Observation Method and Purpose. Version

13 3.2.7 Geologic Events Preferred Age In 1G-E it is mandatory to provide a preferredage for all Geologic Units and the GeologicEvent properties for preferredage should be encoded as described in this section and shown in Figure 7. For 1G-E the preferredage is the age of formation, i.e. of the genesis of the GeologicUnit Name The Name property of GeologicEvent is only used for orogenic events and if populated should provide the URN of one of the orogenic events shown in Figure 4 and listed in 1GE_OrogenicEvents.xls (see Vocabulary). These were defined and agreed by the 1G-E WP3 team and are Europe specific and will not form a part of the global CGI vocabulary. For preferredage a name should only be given where the GeologicUnit was formed by the orogenic event Event Age The eventage field should be populated as a term range giving the lower age and the upper age. For the Phanerozoic the terms used should be the URNs of the ICS geochronologic units listed in Table 1GE_Ages.xls and Figure 1GE_Ages.pdf (see Vocabulary). For the Pre- Cambrian the ICS geochronologic units should be used down to system period level, but for epoch level the proposed new geochronologic units (marked with an asterisk) listed in Table 1GE_Ages.xls (see Vocabulary) should be used if required. You should aim to record ages to the highest temporal resolution possible. Where both the upper and lower age fall within the same geochronologic unit, then upper and lower age should be populated with the same term. The description of the orogenic events in Table 1GE_OrogenicEvents.xls (see Vocabulary) includes an age range and the eventage should be consistent with this. The age range given in eventage can be the same as the age range of the orogenic event, or it can be contained with it, indicating the GeologicUnit was formed during part of the orogenic event. The concept hierarchy of the 1G-E OrogenicEvents is shown in Figure 4. Version

14 1GE_Orogenic_Events coe.1 Alpine ( ) coe.1.1 Late Alpine ( ) coe.1.2 Middle Alpine (63-19) coe.1.3 Early Alpine (221-63) coe.2 Variscan (373 ±5-262 ±2) coe.2.1 Late Variscan ( ) coe.2.2 Middle Variscan ( ) coe.2.3 Early Variscan (373 ±5-360) coe.3 Caledonian ( ± 3) coe.4 Cadomian (752 ±8-502 ±3) coe.5 Sveconorwegian ( ) coe.6 Hallandian ( ) coe.7 Gothian ( ) coe.8 Svecokarelian ( ) coe.9 Archean ( ) Figure 4: Presentation of the concept hierarchy of the 1G-E OrogenicEvents Event Process The age given in eventage is the age of formation of the GeologicUnit and eventprocess records the process that formed the GeologicUnit. For example for a sedimentary rock the process is deposition and the eventage is the period over which that deposition process acted. Other relevant processes include intrusion and crystallisation. For rocks that were formed by different processes over a period of time, such as metamorphic rocks, the eventprocess should be that which is reflected in the eventage. In geologichistory (see section ) it is possible to provide ages to several events that led to the formation of the GeologicUnit. The eventprocess property should be populated with the URN of one of the concepts given in Table 1GE_EventProcess.xls and Figure 1GE_EventProcess.pdf (see Vocabulary). The concept hierarchy of the 1G-E EventProcess is shown in Figure 5 below. Version

15 Figure 5: Presentation of the concept hierarchy of the 1G-E_EventProcess If the GeologicEvent is a named orogenic event, then the eventprocess should be consistent with formation by an orogenic event e.g. tectonic process Event Environment This property is optional but can be used to describe the environment in which the GeologicUnit was formed. The eventenvironment property should be populated with the URN of one of the concepts presented in Table 1GE_EventEnvironment.xls and Figure 1GE_EventEnvironment.pdf (see Vocabulary). The concept hierarchy of the 1G-E EventEnvironment is presented in Figure 6. Version

16 Figure 6: Presentation of the concept hierarchy of the 1G-E_EventEnvironment Version

17 Figure 7: Example of the coding of Preferred Age Geologic History It is not mandatory to provide a geologichistory for the GeologicUnit. The geologichistory property is designed for recording a series of GeologicEvents that led to the formation of the GeologicUnit, which is likely to be particularly useful for metamorphic rocks. For each GeologicEvent in the geologichistory an eventage and eventprocess must be provided, and an eventenvironment can optionally be provided. In 1G-E geologichistory can also be used to provide a numeric age to refine the geochronologic unit based age given in preferredage, in which case the geologichistory might contain only one GeologicEvent Name The Name property of GeologicEvent is used for orogenic events and if populated should provide the URN of one of the orogenic events listed in Table 1GE_OrogenicEvents.xls (see Vocabulary). For geologichistory there might be several GeologicEvents referencing the same orogenic event, for example different periods of folding that occurred within the orogeny Event Age The eventage field can be populated either with geochronologic terms or numeric values (see Figures 8 and 9). These can be either single values or a range. If using geochronologic terms then these should be drawn from the list of ICS geochronologic units given in Table 1GE_Ages.xls and Figure 1GE_Ages.pdf or the Pre-Cambrian epochs given in Table 1GE_Ages.xls (marked by asterisk, see Vocabulary). Please note that to record a numeric age of 250 Million years, the units of measure property (uom) should be set to Ma and the age recorded as a negative number (e.g. -250). Version

18 Event Process The eventprocess property should be populated with the URN of one of the concepts given in table 1G-E_EventProcess.xls and figure 1G-E_EventProcess.pdf (see Vocabulary). If the GeologicEvent is a named orogenic event, then the eventprocess should be consistent with its formation during an orogenic event e.g. tectonic process Event Environment This property is optional but can be used to describe the environment in which the GeologicEvent took place (see figures 8 and 9). The eventenvironment property should be populated with the URN of one of the concepts listed in Table 1GE_EventEnvironment.xls (see Vocabulary). Figure 8: Example of the coding of Geologic History to provide a numeric age. The coding of the Geologic Unit Type property is also shown. Version

19 Figure 9: Example of the coding of Geologic History with two Geologic Events, one a named orogeny: Svekokarelian Composition Part The lithology of GeologicUnits is described in GeoSciML using CompositionParts. Some GeologicUnits will have a single CompositionPart, but others may have multiple CompositionParts, such as interbedded layers, each of which can be described with a distinct CompositionPart. Each CompositionPart has three properties the lithology; the role of the CompositionPart in the GeologicUnit as a whole; and the proportion of the CompositionPart in the GeologicUnit as a whole Lithology In 1G-E lithology is described using a subset of concepts drawn from the CGI SimpleLithology vocabulary in a straightforward hierarchical order. This will increase the level of harmonisation and make the portrayal easier. The complete CGI SimpleLithology vocabulary incorporates multiple hierarchies to incorporate the different classification systems in use. You will need to map your lithology concepts to the ones given in Table 1GE_Lithology.xls (see Vocabulary). This should be done at the highest semantic resolution possible, but it is recognised that this mapping may lead to a loss of semantic resolution in some cases. When determining the correct lithology concept to use it is the concept definition rather than the concept term which should be the primary consideration. Note that in addition to CompositionPart, information about metamorphism can be provided using Version

20 MetamorphicDescription (see section 3.2.9) and information about genesis (e.g. intrusion ) can be provided using GeologicEvent (see section 3.2.7). For each lithology concept Table 1GE_Lithology.xls gives the URN which has to be used to populate the lithology property. Some concepts commonly used as lithologies, such as ophiolite, are in fact a combination of lithology, genesis and other concepts. Section 4 describes how to encode some such complex rocks that have been identified as being required in 1G-E Role The CompositionPart role property describes the role of the CompositionPart in the GeologicUnit as a whole, for example a lithosome or cycling bedding or only part. For 1G- E, due both to the scale of the maps being used and in order to enable harmonisation, the role property should be restricted to the two values of only part and unspecified_part_role in most cases. Thus, where the CompositionPart is the only one in the GeologicUnit the role property should be set to urn:cgi:classifier:cgi:geologicunitpartrole:200811:only_part Where the CompositionPart is one of several in the GeologicUnit the role property should be set to urn:cgi:classifier:cgi:geologicunitpartrole:200811:unspecified_part_role. The additional values such as inclusion, lithosome, blocks etc. should be only used for the description of complex rocks (see chapter 4) Proportion The Proportion property provides an indication of the proportion of the CompositionPart in the GeologicUnit as a whole. In GeoSciML this can be described numerically or using term values. For 1G-E it has been decided to use term values. Where there is only one CompositionPart in the GeologicUnit the Proportion property should be set to urn:cgi:classifier:cgi:proportionterm:201001:all. Where there are multiple CompositionParts in the GeologicUnit the CompositionPart that comprises the single largest proportion of the GeologicUnit should be given a Proportion value of urn:cgi:classifier:cgi:proportionterm:201001:predominant. All other CompositionParts should be given a Proportion value of urn:cgi:classifier:cgi:proportionterm:201001:subordinate. Note that where there are multiple CompositionParts in the GeologicUnit one must be given a value of urn:cgi:classifier:cgi:proportionterm:201001:predominant and this will be the one used for portrayal of the lithology of the GeologicUnit (see figure 10). Version

21 Figure 10: Example of the coding of Composition with two Composition Parts Metamorphic Description The GeoSciML MetamorphicDescription package has five properties for describing the metamorphism of a GeologicUnit, three of which are available for use in 1G-E. The use of MetamorphicDescription in 1G-E is optional Metamorphic Facies If used, the metamorphicfacies property should be populated with the URN of one of the metamorphic facies concepts given in Table 1GE_MetamorphicFacies.xls and Figure 1GE_MetamorphicFacies.pdf (see Vocabulary), as demonstrated in the encoding example in Figure 13. The concept hierarchy of the 1G-E Metamorphic Facies is illustrated by Figure 11. Version

22 Figure 11: Presentation of the concept hierarchy of of the 1GE_MetamorphicFacies Metamorphic Grade If used, the metamorphicgrade property should be populated with the URN of one of the metamorphic grade concepts given in Table 1GE_MetamorphicGrade.xls and Figure 1GE_MetamorphicGrade.pdf (see Vocabulary), as demonstrated in the encoding example in Figure 13. The concept hierarchy of the 1G-E Metamorphic Grade is shown in Figure 12. Figure 12: Presentation of the concept hierarchy of the 1G-E_MetamorphicGrade Version

23 Protolith Lithology GeoSciML allows one or more protolith lithologies for a GeologicUnit to be described using the detailed lithological description properties available in the GeoSciML EarthMaterial package. For 1G-E, which deals with 1:1 Million scale data, this level of detail is not required and only the concepts from the 1G-E subset of CGI Simple Lithology concepts (Table 1GE_Lithology.xls, see Vocabulary) should be used to describe protolith lithology, rather than full EarthMaterial descriptions. Nevertheless, due to the structure of the GeoSciML model, these need to be given in the context of an EarthMaterial description, which makes the encoding a bit more complex and requires values for the EarthMaterial purpose and consolidationdegree properties to be provided, as shown in the encoding example in Figure 13. The EarthMaterial purpose property should always be set to typicalnorm and the consolidationdegree property (which has no meaning in the context of a protolith lithology) should always be set to urn:cgi:classifier:cgi:consolidationdegree:200811:consolidation_not_specified. The RockMaterial lithology property should be populated with the URN of a concept from the 1G-E subset of the CGI Simple Lithology vocabulary (Table 1GE_Lithology.xls, see Vocabulary). Figure 13: Example of the coding of a Metamorphic Description Dykes/Dikes In order to describe a GeologicUnit as a dyke it is necessary, in addition to its genesis (see section 3.2.7) and its lithology (see section 3.2.8), to describe the morphology of the unit. For dykes the GeologicUnit bodymorphology property should always be set to urn:cgi:classifier:cgi:geologicunitmorphology:201001:dike. 3.3 GeologicStructure properties In 1G-E the only types of structure that are being used are Faults and Contacts. Contacts are only being used to describe Calderas, Impact Craters and Glacial Stationary Lines. Version

24 3.3.1 ID Each geologic structure should be given a unique identifier. This is for use within application processing rather than for information exchange, so the ID value can be anything as long as it is unique Name A name can be given to a GeologicStructure if required but this is optional in 1G-E. However, you may wish to use the Name property of GeologicStructure to record the name of the unit used in your own vocabulary which would therefore provide a link to the full original description of the structure. No retrieval or symbolisation based on this name will be implemented in 1G-E, but such a link could be implemented in the future if required. If you wish to give a name to the GeologicStructure you should give it an URN following the pattern described in section Observation Method The observationmethod property of GeologicStructure enables the distinct methodologies for observing the GeologicStructure properties to be recorded. Note that this is distinct from the observationmethod property of MappedFeature which enables the distinct methodologies for observing the geometry to be recorded. For 1G-E the GeologicStructure observationmethod property should be set to either urn:cgi:classifier:cgi:featureobservationmethod:201001:data_from_single_published_ description, where the property values are derived from a single source document, or urn:cgi:classifier:cgi:featureobservationmethod:201001:synthesis_of_multiple_publis hed_descriptions where they are derived from multiple source documents Purpose This property is used to state if the GeologicStructure description is of an instance, as would be the case for a field map for example, or a type of normative description such as might occur in a Stratigraphic Lexicon. On published maps the descriptions are generally normative and given in the map key. For 1G-E the Purpose property should be set to typical_norm Geologic Events Preferred Age You can optionally provide an age as preferredage for glacial stationary lines for 1G-E. This section describes how this can be done. Version

25 Event Age The eventage field should be populated as a numeric range or as a single numeric value. An appropriate unit of measure property (uom) should be chosen, e.g. Ma, ka and the age recorded as a negative number (e.g. -250) Event Process The age given in eventage is the age of formation of the GeologicStructure and eventprocess records the process that formed the GeologicStructure. The eventprocess property should be populated with the URN of one of the concepts given in Table 1GE_EventProcess.xls and Figure 1GE_EventProcess.pdf (see Vocabulary). This property is mandatory if a Preferred Age is being recorded Event Environment This property is optional but can be used to describe the environment in which the GeologicStructure was formed. The eventenvironment property should be populated with the URN of one of the concepts listed in Table 1GE_EventEnvironment.xls and Figure 1GE_EventEnvironment.pdf (see Vocabulary) Fault Type In GeoSciML Faults are a type of ShearDisplacementStructure which in turn are a type of GeologicStructure. For all Faults the ShearDisplacementStructure property faulttype must be populated with the URN of one of the concepts described in Table 1_GE_FaultType, xls and Figure 1_GE_FaultType.pdf (see Vocabulary). The encoding is shown in Figure 14. Figure 14: Example of the coding of a Shear Displacement Structure Contact Type In 1G-E Contacts are only being used to describe the linear features delimiting impact craters, calderas and glacial stationary lines. Impact craters and calderas are not defined as polygons and the material within these structures should be described using GeologicUnit. For impact craters the Contact contacttype property should be set to urn:cgi:classifier:cgi:contacttype:201001:impact_structure_boundary. For calderas the Contact contacttype property should be set to urn:cgi:classifier:cgi:contacttype:201001:volcanic_subsidence_zone_boundary (see example in Figure 15). Version

26 For glacial stationary lines the Contact contacttype property should be set to urn:cgi:classifier:cgi:contacttype:201001:glacial_stationary_line. You may also wish to give the glacial stationary line a name (see section 3.3.2). Figure 15: Example of the encoding of a Caldera. 4. Complex Rock Descriptions Some GeologicUnits that are required for 1G-E are a composite of lithology, genesis and other concepts. This section provides guidelines on how to describe these in GeoSciML. 4.1 Flysch Flysch consists of repeated sedimentary cycles with upwards fining of the sediments. At the bottom of each cycle are sometimes coarse conglomerates or breccias, which gradually evolve upwards into sandstone and shale/claystone. Flysch is formed under deep marine circumstances, in a quiet and low-energy depositional environment. One CompositionPart (see section 3.2.8) should be encoded for each of the lithologies present. This may vary between different flysch occurrences. The CompositionPart role property (see section ) for all CompositionParts should be set to urn:cgi:classifier:cgi:geologicunitpartrole:200811:cyclic_bedding_package The eventenvironment property of GeologicEvent (see section ) should be set to one of the marine setting environments listed in Table 1GE_EventEnvironment.xls (see Vocabulary), e.g. urn:cgi:classifier:cgi:eventenvironment:201001:bathyal. 4.2 Molasse Similar to Flysch but with different lithologies (sandstone, conglomerate, shale and marls) and a paralic (partly marine, partly continental or deltaic sedimentary facies). Molasse is more clastic and less rhythmic then the preceding Flysch facies. The eventenvironment property of GeologicEvent (see section ) should be set to one of the marine setting environments listed in Table 1GE_EventEnvironment.xls e.g. urn:cgi:classifier:cgi:eventenvironment:201001:epicontinental_marine_setting or urn:cgi:classifier:cgi:eventenvironment:201001:piedmont_slope_system_setting Version

27 or urn:cgi:classifier:cgi:eventenvironment:201001:deltaic_system_setting. The role of each CompositionPart is probably urn:cgi:classifier:cgi:geologicunitpartrole:200811:cyclic_bedding_package. 4.3 Olistostrome A debris-flow deposit consisting of a chaotic mass of intimately mixed heterogeneous materials (such as blocks and muds) that accumulated by submarine gravity sliding or slumping of unconsolidated sediments. It can best be described as a diamictite from the Lithology vocabulary. The EventProcess property of GeologicEvent should be set to urn:cgi:classifier:cgi:eventprocess:201001:debris_flow The eventenvironment property of GeologicEvent (see section ) should be set to subaqueous setting: urn:cgi:classifier:cgi:eventenvironment:201001:subaqueous_setting. 4.4 Turbidite The characteristic feature here is that it is deposited by turbidity currents in an ocean environment. Turbidites can be consolidated or unconsolidated and can show graded bedding and often moderate sorting. The EventProcess property of GeologicEvent should be set to urn:cgi:classifier:cgi:eventprocess:201001:turbidity_current_deposition The eventenvironment property of GeologicEvent (see section ) should be set to one of the marine setting environments listed in Table 1GE_EventEnvironment.xls e.g. urn:cgi:classifier:cgi:eventenvironment:201001:bathyal The CompositionPart role property (see section ) should be set to urn:cgi:classifier:cgi:geologicunitpartrole:200811:cyclic_bedding_package for all CompositionParts 4.5 Ophiolitic mélange Characteristic for this kind of diamictite are ophiolitic rock fragments (Serpentinite, peridotite) in a pelitic to psammitic groundmass. The role of each CompositionPart is for groundmass urn:cgi:classifier:cgi:geologicunitpartrole:200811:geologic_unit_matrix and for the rock fragments urn:cgi:classifier:cgi:geologicunitpartrole:200811:blocks. Version

28 4.6 Tectonic mélange This is much the same as ophiolitic mélange apart from ophiolithic rock fragments. The EventProcess property of GeologicEvent should be set to urn:cgi:classifier:cgi:eventprocess:201001:tectonic_process The CompositionPart role property (see section ) should be set to urn:cgi:classifier:cgi:geiologicunitpartrole:200811:blocks The metamorphism can be described with one term of the MetamorphicFacies and one term of the MetamorphicGrade and additionally by one of the terms from the eventenvironment: Low pressure high temperature setting; High pressure low temperature Earth interior setting or Ultra high pressure crustal setting, if required. The MetamorphicFacies property should be set to one of the metamorphic facies e.g. urn:cgi:classifier:cgi:metamorphicfacies:201001:greenschist_metamorphic_facies The MetamorphicGrade property should be set to one of the metamorphic grades e.g. urn:cgi:classifier:cgi:metamorphicgrade:201001:low_metamorphic_grade The EventEnvironment property (see section ) should be set to one of the URNs below: or or urn:cgi:classifier:cgi:eventenvironment:201001:low_pressure_high_temperature_setti ng urn:cgi:classifier:cgi:eventenvironment:201001:high _pressure_ low_temperature_earth_interior_setting urn:cgi:classifier:cgi:eventenvironment:201001:ultra_high _pressure_ low _temperature_crustal_setting 4.7 Ophiolite complex This is an assemblage of distinct lithologies formed by particular tectonic processes. It can be built up as a set of CompositionParts, one for each of the lithologies along with an appropriate role (e.g. urn:cgi:classifier:cgi:geologicunitpartrole:200811:layer_lithosome). The EventProcess property of GeologicEvent should be set to urn:cgi:classifier:cgi:eventprocess:201001:tectonic_process The EventEnvironment should be set to urn:cgi:classifier:cgi:eventenvironment:201001:tectonic_setting The metamorphism can be described using one of the MetamorphicFacies, MetamorphicGrade and by an eventenvironment of Low pressure high temperature setting; High pressure low temperature Earth interior setting or Ultra high pressure crustal setting if required. The MetamorphicFacies property should be set to one of the metamorphic facies e.g. urn:cgi:classifier:cgi:metamorphicfacies:201001:greenschist_metamorphic_facies Version