An integrated seismic microzoning (SM) and …...2013/06/26 · Inspire Conference 2013 Florence, June 26 th An integrated seismic microzoning (SM) and geological model toward Inspire

Inspire Conference 2013 Florence, June 26th

An integrated seismic microzoning (SM) and geological model toward

Inspire

P.L. Fantozzi(1), M. Corongiu (2), S.Romanelli (2), M. Baglione (3) 1)Department of Physic, Earth Sciences and Environmental Sciences,

University of Siena, Siena, Italy (2)LAMMA Consortium, Sesto Fiorentino, Italy

(3) Tuscany Regional Government, Florence, Italy


The geological information base

Lithotechnical

map

Geological map

Landslide DB

the geological

information base

Planning

Since the end of eighties the Italian Geological Survey started the geological mapping of Italian territory at the scale 1:50.000 (National CARG Project).This project required the survey at the scale 1:25.000 and the realization of a spatial data base. This project is still under completion because since the mid nineties many regional administration started the geological mapping of region territory at the scale 1:10.000 (Regional CARG Project) .

NATIONAL PROJECT (scale 1:50.000 CARG)

REGIONAL PROJECT (Scale 1:10.000 es.

TUSCANY)

Relating to the geological matters there are many other actors that play an important role from general (country level) es. INGV to local (regional, provincial and municipal) level

After the seismic events of L’ Aquila in 2009 The Italian Department of Civil Protection and the Regional Administrations, defined the criteria of Seismic Microzoning.

In the current guidelines for SM, the model was determined by the creation of a synthetic map of geological, geomorphological, and geotechnical data including the subsurface geological and a extensive geophysical characterization of the explored area.

All project described were realized with the scientific contribution of the universities and research institutions (CNR, LAMMA, etc). As consequence of the mandatory action of INSPIRE , is necessary for the all exiting data base an action of comparison and compliance analysis to the application schemas belonging to INSPIRE GE. For this raison we tested the impact of GE and other connected themes in the sector of seismic risk protection, i.e. the SM. The target of our work consists on the verification of the adaptability of the available geological dataset to the GE schemas of INSPIRE. We remark that our contribution is only a scientifically and methodologically test, because the institutional obligations envisaged by INSPIRE directive, establish responsability and competencies thath are assumed by the specific public bodies


Tests and Surveys

Engineering Geological Map National Specs on

Seismic Microzoning

Seismic Microzoning

class GeologyCore

«type»Geometry root::GM_Object

{root}

SF_SamplingFeature

«FeatureType»spatialSamplingFeature::

SF_SpatialSamplingFeature

«FeatureType»GeologicFeature::MappedFeature

+ observationMethod: CGI_Term [1..*]+ positionalAccuracy: Quantity+ resolutionScale: MD_RepresentativeFraction

«FeatureType»GeologicFeature::GeologicFeature

+ observationMethod: CGI_Term [1..*]+ purpose: DescriptionPurpose = instance

SF_SamplingCurve

«FeatureType»Borehole::Borehole

«FeatureType»Borehole::BoreholeCollar

+ location: GM_Point+ elevation: DirectPosition

«FeatureType»GeologicStructure::GeologicStructure

«FeatureType»GeologicStructure::ShearDisplacementStructure

+ faultType: FaultTypeTerm+ deformationStyle: DeformationStyleTerm

«estimatedProperty»+ planeOrientation: CGI_PlanarOrientation

«featureType»GeomorphologicFeature

«CodeList»GeologicStructure::

FaultTypeTerm

«FeatureType»GeologicUnit::GeologicUnit

+ geologicUnitType: GeologicUnitTypeTerm+ rank: RankTerm

«estimatedProperty»+ bodyMorphology: CGI_Term [1..*]+ unitComposition: CGI_Term [1..*]+ exposureColor: CGI_Term [1..*]+ outcropCharacter: CGI_Term [1..*]+ unitThickness: CGI_NumericRange

«DataType»GeologicUnit::CompositionPart

+ role: CompositionPartRoleTerm

«estimatedProperty»+ material: CompoundMaterial+ proportion: CGI_NumericRange

«CodeList»GeologicUnit::

CompositionPartRoleTerm

«CodeList»GeologicUnit::GeologicUnitTypeTerm

+ AllostratigraphicUnit+ AlterationUnit+ ArtificialGround+ BiostratigraphicUnit+ ChronostratigraphicUnit+ DeformationUnit+ ExcavationUnit+ GeomorphologicUnit+ GeophysicalUnit+ LithodemicUnit+ LithogeneticUnit+ LithologicUnit+ LithostratigraphicUnit+ LithotectonicUnit+ MagnetostratigraphicUnit+ MassMovementUnit+ Pedoderm+ PedostratigraphicUnit+ PolarityChronostratigraphicUnit+ GeologicUnit

«CodeList»GeologicUnit::RankTerm

«Type»EarthMaterial::CompoundMaterial

+ compositionCategory: CGI_Term [1..*]+ geneticCategory: CGI_Term [1..*]

«Type»EarthMaterial::RockMaterial

+ consolidationDegree: CGI_Term+ lithology: LithologyTerm [1..*]

«CodeList»CGI_Value::

DescriptionPurpose

+ definingNorm+ instance+ typicalNorm


DeformationStyleTerm

«CodeList»EarthMaterial::LithologyTerm

«Type»EarthMaterial::EarthMaterial

+ purpose: DescriptionPurpose = instance

«estimatedProperty»+ color: CGI_Term [1..*]

Definition

«Type»Vocabulary::ControlledConcept

+ name: LocalizedGenericName [1..*]

constraints{metadata.hierarchyLevel=(feature or dataset or series)}{prototype.purpose="definingNorm"}

0..*

+samplingFrame

+specification 1

Description

+occurrence 0..*

+collarLocation 1

+borehole 1..*

+definedUnit

+definingStructure

1..*

+relatedUnit

0..1

+composition 1..*

+classifier

0..1GE AS Geology

class Measurement

«featureType»AbstractGeophStation

+ shape: GM_Point

«voidable»+ stationRank: StationRankValue [1..*]+ relatedNetwork: NetworkNameValue [0..*]

«featureType»AbstractGeophProfile

+ shape: GM_Curve

«featureType»AbstractGeoph3DMeasurement

+ shape: GM_Object

«codeList»StationRankValue

+ observatory+ secularStation+ 1stOrderBase+ 2ndOrderBase+ normal

«codeList»PlatformTypeValue

+ ground+ fixWingedAirplane+ helycopter+ researchVessel+ satell ite

«codeList»NetworkNameValue

+ UEGN+ WDC+ IMS

«codeList»ProjectedGeometryTypeValue

+ point+ trace+ footPrint

«featureType»GeophStation

+ stationType: StationTypeValue

constraints{stationRankIsNotNormal}

«featureType»GeophProfile

+ profileType: ProfileTypeValue

constraints{shape.length>=1000}

«featureType»Geoph3DMeasurement

+ measurementType: 3DMeasurementTypeValue

constraints{shape.area>=1000000}

«codeList»3DMeasurementTypeValue

+ 3DSeismics«codeList»StationTypeValue

+ gravityStation+ magneticStation+ seismologicalStation

«codeList»ProfileTypeValue

+ seismicLine+ boreholeLogging

«featureType»GeophMeasurement

+ inspireId: Identifier+ citation: CI_Citation+ resolutionScale: MD_RepresentativeFraction+ projectedGeometry: ProjectedGeometry [1..*]+ platformType: PlatformTypeValue

«voidable»+ measurementStart: TM_Position+ measurementEnd: TM_Position+ verticalExtent: EX_VerticalExtent+ distributionInfo: MD_Distribution+ largerWork: MD_Identifier [1..*]+ relatedModel: MD_Identifier [1..*]+ dataOwner: CI_ResponsibleParty

«dataType»ProjectedGeometry

+ geometry: GM_Primitive+ projectedGeometryType: ProjectedGeometryTypeValue

constraints{geometryIsConformantWithType}

GE AS Geophysics

class ef_diagram

Additional classes

EF-Level

ISO FDIS 19156:2011 Observations and Measurements

«featureType»AbstractMonitoringFeature

«voidable»+ reportedTo: ReportToLegalAct [0..*]

constraints{Observation and ObservingCapability}{ObservationRequired}

«featureType»Env ironmentalMonitoringProgram

«featureType»Env ironmentalMonitoringNetwork

«voidable»+ onlineResource: URI [0..*]+ organisationalLevel: LegislationLevelValue

Env ironmentalMonitoringActiv ity

«voidable»+ activityTime: TM_Object+ activityConditions: CharacterString

«featureType»Observ ingCapability

«voidable»+ observingTime: TM_Object+ processType: ProcessTypeValue+ reportedTo: ReportToLegalAct [0..*]+ resultNature: ResultNatureValue

«featureType»AbstractMonitoringObject

+ inspireId: Identifier+ name: CharacterString [0..*]+ additionalDescription: CharacterString [0..1]+ geometry: GM_Object [0..1]

«voidable»+ legalBackground: LegislationReference [0..*]+ responsibleParty: CI_ResponsibleParty [0..*]+ beginLifespan: DateTime+ endLifespan: DateTime [0..1]

«featureType»Env ironmentalMonitoringFacility

+ mediaMonitored: MediaValue [1..*]

«voidable»+ representativePoint: GM_Point [0..1]+ measurementRegime: MeasurementRegimeValue+ mobile: MobileValue+ resultAcquisitionSource: ResultAcquisitionSourceValue [0..1]

«FeatureType»observ ation::OM_Observ ation

+ phenomenonTime: TM_Object+ resultTime: TM_Instant+ validTime: TM_Period [0..1]+ resultQuality: DQ_Element [0..*]+ parameter: NamedValue [0..*]

«FeatureType»observation::OM_Process

«FeatureType»General Feature Instance::GFI_Feature

«featureType»INSPIRE_OM_Process

+ inspireId: Identifier+ name: CharacterString [0..1]+ onlineResource: URI [0..1]+ processParameter: ProcessParameter [0..*]+ responsibleParty: CI_ResponsibleParty [1..*]

«featureType»OperationalActiv ityPeriod

+ activityTime: TM_Object

«featureType»INSPIRE_GF_PropertyType

+ inspireId: Identifier+ name: CharacterString [0..1]+ onlineResource: URI [0..1]

«featureType»ClassificationUnit

+ inspireId: Identifier+ name: CharacterString [0..1]

«featureType»ClassificationSchema


Observation and ObservingCapability/* If you attache Observation(s) to an Abstract Monitoring Feature this must have an Observing Capability attached to it. The Observing Capability must reference the same Domain, Phenomenon and Process as the Observation. */inv: hasObseration->notEmpty() -> observingCapability->notEmpty()

ObservationRequired/* If an Observation is required the Abstract Monitoring Feature should be linked to an OM_Observation */inv: reportedTo.observationRequired=yes -> hasObservation->notEmpty()

NetworkFacility

«voidable»+ linkingTime: TM_Object

«metaclass»General Feature Model::GF_PropertyType

{root}

+ memberName: LocalName+ definition: CharacterString

Hierarchy


AnyThematicLink

«voidable»+ comment: CharacterString

«type»Records and Class

Metadata::Any{root}

observ ation::Observ ationContext

+ role: GenericName

The INSPIRE_GF_PropertyType represents a model for specifying the observed property of an observation.

0..* +relatedObservation0..*

Phenomenon

+observedProperty 1

Phenomenon

+observedProperty

1

+unit

0..*

+schema

1..*

+referringFrom0..* anyRelation

+referringTo0..*


+referringTo0..*

+classificationUnit 0..*

+baseProperty 0..*

+property 0..*

+procedure 0..*

+referringFrom0..*

anyRelation

+referringTo0..*

+propertyValueProvider

0..* Domain

+featureOfInterest

1

Domain

+featureOfInterest0..1

ProcessUsed

+procedure 1

+broader0..1

hierarchy+narrower0..*

+hasObservation0..*

+operationalActivityPeriod«voidable» 1..*

+belongsTo 0..*

+contains 0..*

+supersede0..*

genealogy

+supersedeBy0..*

+relatedTo0..*

+reportedTo

0..*

+observingCapability0..*

+generatedObservation

0..* ProcessUsed

+procedure

1

EF

class 1_Core Model

«featureType»HazardArea

+ geometry: RiskHazardGeometry+ inspireId: Identifier+ typeOfHazard: NaturalRiskOrHazardClassification

«voidable, l ifeCycleInfo»+ beginLifespanVersion: DateTime+ endLifespanVersion: DateTime [0..1]

«voidable»+ levelOfHazard: LevelOfHazard+ likelihoodOfOccurence: LikelihoodOfOccurence

tagsbyValuePropertyType = falsebyValuePropertyType = falseisCollection = falsenoPropertyType = falsexsdEncodingRule = iso19136_2007_INSPIRE_Extensions

«featureType»RiskZone

+ geometry: RiskHazardGeometry+ inspireId: Identifier+ typeOfRisk: NaturalRiskOrHazardClassification

«voidable, l ifeCycleInfo»+ beginLifespanVersion: DateTime+ endLifespanVersion: DateTime [0..1]+ validFrom: DateTime+ validTo: DateTime [0..1]

«voidable»+ determinationMethod: DeterminationMethodValue+ legalBasis: LegislationReference [0..*]+ legallyBindingZone: Boolean+ levelOfRisk: LevelOfRisk

constraints{A riskzone must be linked to 1 (or more) exposed elements}{legallyBindingZone - legalBasis}

tagsbyValuePropertyType = falseisCollection = falsenoPropertyType = falsexsdEncodingRule = iso19136_2007_INSPIRE_Extensions

«featureType»ExposedElements

+ geometry: GM_Object+ inspireId: Identifier+ typeOfElement: TypeOfExposedElementValue



VulnerabilityOfElement

«voidable»+ qualitativeVulnerabil ity: CharacterString+ qualitativeVulnerabil ityAssessmentMethod: DocumentReference+ quantitativeVulnerabil ity: Number+ quantitativeVulnerabil ityAssessmentMethod: DocumentReference

constraints{either the quantitative vulnerabil ity or the quantitative vulnerabil ity must be completed.}{If the qualitative vulnerabil ity iscompleted, then the qualitative vulnerabil ity assessment method must be completed.}{If the quantitative vulnerabil ity is completed, then the quantitative vulnerabil ity assessment method must be completed.}

«featureType»Observ edHazard

«voidable»+ nameOfEvent: CharacterString

«voidable, l ifeCycleInfo»+ validFrom: DateTime+ validTo: DateTime [0..1]

constraints{The likelihood of occurence is mandatory}


«featureType»ModelledOrDeterminedHazard

«voidable»+ determinationMethod: DeterminationMethodValue


NOTE : An exposed element is typically any spatial object representing a real-world object or administrative/statistical unit, management are.

Therefore, it is impossible to explicitly define which INSPIRE spatial objects should be encoded as a Exposed Element.

This feature class therefore aims at including any spatial data which is considered as an exposed element, and for which a link to a risk zone is made, and vulnerabil ity is calculated.

+sourceHazard«voidable» 0..*

affects

+resultHazard«voidable»0..*

+result«voidable»

0..*

+source«voidable»

1

+observedHazard«voidable»

0..*+exposedElement«voidable»

0..*

+riskZone«voidable»

0..*

isExposedTo

+exposedElement«voidable»

1..*

NR


Seismic Microzoning as GE Use Case

The test of compliance has been carried out using the following procedure: •The MS data and requirement are formalized in a data model using the UML •Compilation of a matching table that compare and correlates the different geological information used in the base maps to the thematic requirements of SM. The MS thematic requirements are then compared and correlated to the INSPIRE themes •The analysis of the SM requirements fit quite well as a Use Case of INSPIRE and particularly with the GE themes with many levels of broadening. Other relevant relationships and dependencies by MS were been identified to other INSPIRE themes such as the themes NR natural risk zones and EF environmental monitoring facilities



Example of matching table GEOLOGY SM INSP

Derivation from geological Data to SM data Model may be:

• direct derivable

• derivable by processing and analysis of existing data

• not derivable

Mapping toward Inspire Data Models may be:

• direct mappable

• mappable by analysis and processing

• not mappable

Landslides No stability area GE geomorphology

NR instance1

ULF Bedrock Stability area GE AS core geological unit

NR instance 2

ULF Quaternary

Possible instability due local seis. waves amplification

GE AS core geological unit

NR instance 3

ULF sands*(water sature)+ analysis and processing

Possible instability due liquefaction phoenomena

GE AS core geological unit (only as class)

NR instance1

no Geophysical survey

GE AS geophysics

EF

NR = Natural Risk Zones EF = Environmental Monitoring Facilities

GEOLOGY SM INSP


ArcGIS Workspace

«ObjectClass»LegendaFoglio

«Field»+ ID_LEGFOG :Integer+ sigla_carta :String+ appartenenza :Integer+ num_foglio :DmNumFoglio+ nome_ULF :String+ descrizione_ULF :String+ lito_assortimento :DmLitoAssortimento+ tipo_ULF :DmTipoUlf+ cartografata :DmBool+ formale :DmBool+ colore :String+ ID_LEGFOG_TABETA :Integer

«ObjectClass»ElementoTerritoriale

«Field»+ ElementoTerritorialeID :String+ nome_topografico :String+ conforme_CTR :DmBool

«ObjectClass»Cav aMiniera

«Field»+ CavaMinieraID :String+ tipo_cm :DmCavaMiniera+ mineralizzazione :String+ materiale_estratto :String+ tipo_materiale :DmTipoMateriale

«ObjectClass»SezioneProspezione

«Field»+ SezioneProspezioneID :String+ tipo_sp :DmSezioneProspezione

«ObjectClass»ElementoFranoso

«Field»+ ElementoFranosoID :String+ stato_attivita :DmStatoAttivita+ direzio :Dm0_360

«ObjectClass»Frana

«Field»+ FranaID :String+ movimento_frana :DmTipoMovimento

«ObjectClass»Affiorante

«Field»+ AffioranteID :String+ tipo_a :DmAffiorante

«ObjectClass»LegendaFoglio1

«Field»+ ID_LEGFOG1 :Integer+ sigla_carta :String+ appartenenza :Integer+ num_foglio :DmNumFoglio+ nome_ULF :String+ descrizione_ULF :String+ lito_assortimento :DmLitoAssortimento+ tipo_ULF :DmTipoUlf+ cartografata :DmBool+ formale :DmBool+ colore :String+ ID_LEGFOG_TABETA :Integer

«ObjectClass»SigleCipe

«Field»+ Sigla :String+ Età :String+ CodiceColore :Integer+ Sigla250k :String+ Sigla100k :String+ Nome10k :String+ Posizione :String+ descrizione_ULF :String+ tipo_ULF :DmTipoUlf_1+ cartografata :DmBool+ eta_sup :DmEta_1+ eta_inf :DmEta_1+ sig_etas :DmSigEta+ sig_etai :DmSigEta+ posizione2 :String

«ObjectClass»LitologiaSTab

«Field»+ ID_TABLITO :Integer+ sigla_carta :String+ litologia :DmLitologia+ ruolo :DmRuolo+ alternanza :DmAlternanza+ comp_mineralogica :DmCompMineralogica+ struttura :DmStruttura+ ID_TABLITO_LEGFOG :Integer

«ObjectClass»GranulometriaQTab

«Field»+ ID_TABGRANU :Integer+ sigla_carta :String+ appartenenza :Integer+ granulometria :DmGranulometriaQ+ litologia :DmLitologia+ percentuale :DmPercentuale+ struttura :DmStruttura+ tipo_cemento :DmTipoCemento+ grado_cemento :DmGradoCemento+ tipo_matrice :DmMatrice+ localmente :DmBool+ ID_TABGRANU_LEGFOG :Integer

«ObjectClass»ULF

«Field»+ sigla_carta :String+ ID_ULF :String+ ID_ULF_LEGFOG :Integer

«ObjectClass»TabEta

«Field»+ ID_TABETA :Integer+ sigla_carta :String+ eta_sup :DmEta+ eta_inf :DmEta+ sig_etai :DmSigEta+ sig_etas :DmSigEta

«ObjectClass»ElementoGeologico

«Field»+ ElementoGeologicoID :String

«ObjectClass»ElementoGeomorfologico

«Field»+ ElementoGeomorfologicoID :String

«ObjectClass»Forma

«Field»+ FormaID :String+ tipo_f :DmForma+ genesi :DmGenesi+ stato :DmStato

+Affiorante 1

REL_TabELGEOMORF_TabAFFIORANTE

«RelationshipClass»

+ElementoGeomorfologico 1

+Forma 1

REL_TabELGEOMOR_TabFORMA


+ElementoGeomorfologico 1

+ULF 1

REL_TabELGEOLOGICO_TabULF


+ElementoGeologico 1

+LegendaFoglio

1

REL_LEGFOG_ULF


+ULF 0..*

+LegendaFoglio

1

REL_LEGFOG_GRANU


+GranulometriaQTab 0..*

+LegendaFoglio 1

REL_LEGFOG_LITO


+LitologiaSTab 0..*

+PADRE 1

REL_LEGFOG1«RelationshipClass»

+FIGLI 0..*

+TabEta

1

REL_TABETA_LEGFOG


+LegendaFoglio

0..*

+PADRE 1

REL_LEGFOG


+FIGLI 0..*

+Frana 1

REL_ELEMENTOFRANOSO_FRANA


+ElementoFranoso 1

+CavaMiniera 1

REL_TABELTERRI_TABCM


+ElementoTerritoriale 1

+SezioneProspezione 1

REL_TABELTERRI_TABSP


+ElementoTerritoriale 1

PostGIS

SM as GE Use case

dependencies

dependencies

PostGIS

Physical implementation

Geological Base information

class 1_Core Model

«featureType»HazardArea

+ geometry: RiskHazardGeometry+ inspireId: Identifier+ typeOfHazard: NaturalRiskOrHazardClassification

«voidable, l ifeCycleInfo»+ beginLifespanVersion: DateTime+ endLifespanVersion: DateTime [0..1]

«voidable»+ levelOfHazard: LevelOfHazard+ likelihoodOfOccurence: LikelihoodOfOccurence

tagsbyValuePropertyType = falsebyValuePropertyType = falseisCollection = falsenoPropertyType = falsexsdEncodingRule = iso19136_2007_INSPIRE_Extensions

«featureType»RiskZone

+ geometry: RiskHazardGeometry+ inspireId: Identifier+ typeOfRisk: NaturalRiskOrHazardClassification


«voidable»+ determinationMethod: DeterminationMethodValue+ legalBasis: LegislationReference [0..*]+ legallyBindingZone: Boolean+ levelOfRisk: LevelOfRisk

constraints{A riskzone must be linked to 1 (or more) exposed elements}{legallyBindingZone - legalBasis}


«featureType»ExposedElements

+ geometry: GM_Object+ inspireId: Identifier+ typeOfElement: TypeOfExposedElementValue



VulnerabilityOfElement

«voidable»+ qualitativeVulnerabil ity: CharacterString+ qualitativeVulnerabil ityAssessmentMethod: DocumentReference+ quantitativeVulnerabil ity: Number+ quantitativeVulnerabil ityAssessmentMethod: DocumentReference

constraints{either the quantitative vulnerabil ity or the quantitative vulnerabil ity must be completed.}{If the qualitative vulnerabil ity iscompleted, then the qualitative vulnerabil ity assessment method must be completed.}{If the quantitative vulnerabil ity is completed, then the quantitative vulnerabil ity assessment method must be completed.}

«featureType»Observ edHazard

«voidable»+ nameOfEvent: CharacterString

«voidable, l ifeCycleInfo»+ validFrom: DateTime+ validTo: DateTime [0..1]

constraints{The likelihood of occurence is mandatory}


«featureType»ModelledOrDeterminedHazard

«voidable»+ determinationMethod: DeterminationMethodValue


NOTE : An exposed element is typically any spatial object representing a real-world object or administrative/statistical unit, management are.

Therefore, it is impossible to explicitly define which INSPIRE spatial objects should be encoded as a Exposed Element.

This feature class therefore aims at including any spatial data which is considered as an exposed element, and for which a link to a risk zone is made, and vulnerabil ity is calculated.

+sourceHazard«voidable» 0..*

affects

+resultHazard«voidable»0..*

+result«voidable»

0..*

+source«voidable»

1

+observedHazard«voidable»

0..*+exposedElement«voidable»

0..*

+riskZone«voidable»

0..*

isExposedTo

+exposedElement«voidable»

1..*NR

class GeologyCore

«type»Geometry root::GM_Object

{root}

SF_SamplingFeature

«FeatureType»spatialSamplingFeature::

SF_SpatialSamplingFeature

«FeatureType»GeologicFeature::MappedFeature

+ observationMethod: CGI_Term [1..*]+ positionalAccuracy: Quantity+ resolutionScale: MD_RepresentativeFraction

«FeatureType»GeologicFeature::GeologicFeature

+ observationMethod: CGI_Term [1..*]+ purpose: DescriptionPurpose = instance

SF_SamplingCurve

«FeatureType»Borehole::Borehole

«FeatureType»Borehole::BoreholeCollar

+ location: GM_Point+ elevation: DirectPosition

«FeatureType»GeologicStructure::GeologicStructure

«FeatureType»GeologicStructure::ShearDisplacementStructure

+ faultType: FaultTypeTerm+ deformationStyle: DeformationStyleTerm

«estimatedProperty»+ planeOrientation: CGI_PlanarOrientation

«featureType»GeomorphologicFeature


FaultTypeTerm

«FeatureType»GeologicUnit::GeologicUnit

+ geologicUnitType: GeologicUnitTypeTerm+ rank: RankTerm

«estimatedProperty»+ bodyMorphology: CGI_Term [1..*]+ unitComposition: CGI_Term [1..*]+ exposureColor: CGI_Term [1..*]+ outcropCharacter: CGI_Term [1..*]+ unitThickness: CGI_NumericRange

«DataType»GeologicUnit::CompositionPart

+ role: CompositionPartRoleTerm

«estimatedProperty»+ material: CompoundMaterial+ proportion: CGI_NumericRange

«CodeList»GeologicUnit::

CompositionPartRoleTerm

«CodeList»GeologicUnit::GeologicUnitTypeTerm

+ AllostratigraphicUnit+ AlterationUnit+ ArtificialGround+ BiostratigraphicUnit+ ChronostratigraphicUnit+ DeformationUnit+ ExcavationUnit+ GeomorphologicUnit+ GeophysicalUnit+ LithodemicUnit+ LithogeneticUnit+ LithologicUnit+ LithostratigraphicUnit+ LithotectonicUnit+ MagnetostratigraphicUnit+ MassMovementUnit+ Pedoderm+ PedostratigraphicUnit+ PolarityChronostratigraphicUnit+ GeologicUnit

«CodeList»GeologicUnit::RankTerm

«Type»EarthMaterial::CompoundMaterial

+ compositionCategory: CGI_Term [1..*]+ geneticCategory: CGI_Term [1..*]

«Type»EarthMaterial::RockMaterial

+ consolidationDegree: CGI_Term+ lithology: LithologyTerm [1..*]

«CodeList»CGI_Value::

DescriptionPurpose

+ definingNorm+ instance+ typicalNorm


DeformationStyleTerm

«CodeList»EarthMaterial::LithologyTerm

«Type»EarthMaterial::EarthMaterial

+ purpose: DescriptionPurpose = instance

«estimatedProperty»+ color: CGI_Term [1..*]

Definition

«Type»Vocabulary::ControlledConcept

+ name: LocalizedGenericName [1..*]

constraints{metadata.hierarchyLevel=(feature or dataset or series)}{prototype.purpose="definingNorm"}

0..*

+samplingFrame

+specification 1

Description

+occurrence 0..*

+collarLocation 1

+borehole 1..*

+definedUnit

+definingStructure

1..*

+relatedUnit

0..1

+composition 1..*

+classifier

0..1

GE

class ef_diagram

Additional classes

EF-Level

ISO FDIS 19156:2011 Observations and Measurements

«featureType»AbstractMonitoringFeature

«voidable»+ reportedTo: ReportToLegalAct [0..*]

constraints{Observation and ObservingCapability}{ObservationRequired}

«featureType»Env ironmentalMonitoringProgram

«featureType»Env ironmentalMonitoringNetwork

«voidable»+ onlineResource: URI [0..*]+ organisationalLevel: LegislationLevelValue

Env ironmentalMonitoringActiv ity

«voidable»+ activityTime: TM_Object+ activityConditions: CharacterString

«featureType»Observ ingCapability

«voidable»+ observingTime: TM_Object+ processType: ProcessTypeValue+ reportedTo: ReportToLegalAct [0..*]+ resultNature: ResultNatureValue

«featureType»AbstractMonitoringObject

+ inspireId: Identifier+ name: CharacterString [0..*]+ additionalDescription: CharacterString [0..1]+ geometry: GM_Object [0..1]

«voidable»+ legalBackground: LegislationReference [0..*]+ responsibleParty: CI_ResponsibleParty [0..*]+ beginLifespan: DateTime+ endLifespan: DateTime [0..1]

«featureType»Env ironmentalMonitoringFacility

+ mediaMonitored: MediaValue [1..*]

«voidable»+ representativePoint: GM_Point [0..1]+ measurementRegime: MeasurementRegimeValue+ mobile: MobileValue+ resultAcquisitionSource: ResultAcquisitionSourceValue [0..1]

«FeatureType»observ ation::OM_Observ ation

+ phenomenonTime: TM_Object+ resultTime: TM_Instant+ validTime: TM_Period [0..1]+ resultQuality: DQ_Element [0..*]+ parameter: NamedValue [0..*]

«FeatureType»observation::OM_Process

«FeatureType»General Feature Instance::GFI_Feature

«featureType»INSPIRE_OM_Process

+ inspireId: Identifier+ name: CharacterString [0..1]+ onlineResource: URI [0..1]+ processParameter: ProcessParameter [0..*]+ responsibleParty: CI_ResponsibleParty [1..*]

«featureType»OperationalActiv ityPeriod

+ activityTime: TM_Object

«featureType»INSPIRE_GF_PropertyType


«featureType»ClassificationUnit

+ inspireId: Identifier+ name: CharacterString [0..1]

«featureType»ClassificationSchema


Observation and ObservingCapability/* If you attache Observation(s) to an Abstract Monitoring Feature this must have an Observing Capability attached to it. The Observing Capability must reference the same Domain, Phenomenon and Process as the Observation. */inv: hasObseration->notEmpty() -> observingCapability->notEmpty()

ObservationRequired/* If an Observation is required the Abstract Monitoring Feature should be linked to an OM_Observation */inv: reportedTo.observationRequired=yes -> hasObservation->notEmpty()

NetworkFacility


«metaclass»General Feature Model::GF_PropertyType

{root}

+ memberName: LocalName+ definition: CharacterString

Hierarchy


AnyThematicLink

«voidable»+ comment: CharacterString

«type»Records and Class

Metadata::Any{root}

observ ation::Observ ationContext

+ role: GenericName

The INSPIRE_GF_PropertyType represents a model for specifying the observed property of an observation.

0..* +relatedObservation0..*

Phenomenon

+observedProperty 1

Phenomenon

+observedProperty

1

+unit

0..*

+schema

1..*


+referringTo0..*


+referringTo0..*

+classificationUnit 0..*

+baseProperty 0..*

+property 0..*

+procedure 0..*

+referringFrom0..*

anyRelation

+referringTo0..*

+propertyValueProvider

0..* Domain

+featureOfInterest

1

Domain

+featureOfInterest0..1

ProcessUsed

+procedure 1

+broader0..1

hierarchy+narrower0..*

+hasObservation0..*

+operationalActivityPeriod«voidable» 1..*

+belongsTo 0..*

+contains 0..*

+supersede0..*

genealogy

+supersedeBy0..*

+relatedTo0..*

+reportedTo

0..*

+observingCapability0..*

+generatedObservation

0..* ProcessUsed

+procedure

1

EF

SM zones

Engineering geological

Test and survey


Conclusion: Our test of compliance to INSPIRE for the SM indicates: •The SM requirements and details are very specific respect to a general purpose geological data •The mandatory characteristics of INSPIRE applied to SM enhances the importance of standardized base knowledge • Is checked that in case of applying a specific application schema, would be possible use a neutral informative structure (i.e. a simple spatial data base) which allows to define a continuity character between the base information and their elaboration or derivation •Is checked the correspondence between national specifics and thematic standard (i.e. is checked particularly the correspondence between a geological application (as the SM) with INSPIRE) We also remarks that the INSPIRE specifications are a very good reference point not only for the definition of basic information themes but also as a guide to connect a specific application to their reference informative base

Documents

An integrated seismic microzoning (SM) and …...2013/06/26 · Inspire Conference 2013 Florence, June 26 th An integrated seismic microzoning (SM) and geological model toward Inspire