Class <<FeatureType>> Fault (extends ShearDisplacementStructure)

A discrete surface, or zone of discrete surfaces, with some thickness, separating two rock masses across which one mass has slid past the other and characterized by brittle deformation. Fault is a map-scale feature. When observed in outcrop, some faults are just big breccia/gouge zones with no discrete surfaces, sometimes they are breccia/gouge zones bounded by discrete fault surfaces, sometimes a discrete surface in relatively unbroken rock (at the scale of description).

Local Subclasses: (none)

Attributes

Name Type Bounds From Class Notes
observationMethod CGI_TermValue 1..* GeologicFeature Term(s) that specify the method by which the values for the GeologicFeature were obtained (e.g. point count, brunton compass on site, air photo interpretation, field observation, hand specimen, laboratory, aerial photography, creative imagination...). This corresponds (loosely) to ISO19115 Lineage.

Statement specifies the method that was used to identify the MappedFeature. Examples: .
Attribute tagged values
Tag Value
sequenceNumber 2
purpose DescriptionPurpose 1..1 GeologicFeature Specification of the intended purpose/level of abstraction for a given feature or object instance. Scoped name because intention is asserted by author of the data instance. Values: Instance, TypicalNorm, IdentifyingNorm.
Attribute tagged values
Tag Value
sequenceNumber 3
planeOrientation CGI_PlanarOrientation 0..1 ShearDisplacementStructure allows capturing the orientation of the plane of the structure
Attribute tagged values
Tag Value
sequenceNumber 2
 

Outbound Associations

Name Type Multiplicity From Class Notes
occurrence MappedFeature 0..* GeologicFeature Points to any number of mapped features which are occurrences of the geologic feature. Mapped features may all be from a single map or from several maps.
Association tagged values
Tag Value
sequenceNumber 4
preferredAge GeologicEvent 0..1 GeologicFeature Specifies the geologic event that the data supplier considers the 'preferred' event age and event process for that feature.
This is the age and process of the feature that would be commonly shown on a geologic map (eg deposition age, peak temperature age, intrusion age).
Normative geologic unit descriptions are expected to include an age specification whenever the age is constrained--even if the range is very large (e.g. Phanerozoic....).
Association tagged values
Tag Value
sequenceNumber 5
geologicHistory GeologicEvent 0..* GeologicFeature A sequence of GeologicEvents with role geologicHistory allow describing the Genesis of the GeologicFeature. In future versions of GeoSciML this sequence should be ordered.
Association tagged values
Tag Value
sequenceNumber 6
targetLink GeologicFeatureRelation 0..* GeologicFeature Specifies the GeologicFeatureRelation that links the 'source' GeologicFeature to the 'target' GeologicFeature.
Association tagged values
Tag Value
sequenceNumber 8
metadata MD_Metadata 0..1 GeologicFeature feature level metadata associated with the GeologicFeature
Association tagged values
Tag Value
inlineOrByReference byReference
sequenceNumber 10
physicalProperty PhysicalDescription 0..* ShearDisplacementStructure The PhysicalDescription of the ShearDisplacementStructure
Association tagged values
Tag Value
sequenceNumber 3
totalDisplacement DisplacementValue 0..1 ShearDisplacementStructure Describes the total displacement DisplacementValues
Association tagged values
Tag Value
sequenceNumber 4
segment Fault 0..* Fault In some use cases, eg., active seismology and fluid flow modelling, it is important to be able to segment the ShearDisplacementStructures where there is a change in orientation and/or dip and/or nature of the character of the fault. This segmentation can be scale dependent.
"segment" is the name of the role that a subsidiary Fault plays with respect to a Fault that it is part of. They are both Faults, and "segment" is the label on the composition. The distinction between Fault and FaultSystem is a question of the scale of description and the perspective of the observer; a Fault is composed of segments that are individually identified, but all considered part of a single Fault. Fault segments are usually collinear on the map, and generally do not overlap significantly along strike. A Fault may have 0..* segment parts (a part of/composition relationship.
Association tagged values
Tag Value
sequenceNumber 3
 

Constraints

Constraint Type Status Weight
 

Tagged values

Tag Value Notes
byValuePropertyType false Values: true,false
Default: false
Description: enforce the 'by value' property pattern without xl
hasXmlLang false Values: true | false
Default: false
Description: axml attribute xml:lang shall be generated for the type representing the class
isCollection false Values: true,false
Default: false
Description: attribute group gml:AggregationAttributeGroup is a
noPropertyType false Values: true,false
Default: false
Description: suppress automatic creation of *PropertyType compl
 

GML-conformant XML Implementation Details

<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="Fault" substitutionGroup="gsml:ShearDisplacementStructure" type="gsml:FaultType">
    <xs:annotation>
        <xs:documentation>A discrete surface, or zone of discrete surfaces, with some thickness, separating two rock masses across which one mass has slid past the other and characterized by brittle deformation. Fault is a map-scale feature. When observed in outcrop, some faults are just big breccia/gouge zones with no discrete surfaces, sometimes they are breccia/gouge zones bounded by discrete fault surfaces, sometimes a discrete surface in relatively unbroken rock (at the scale of description).</xs:documentation>
    </xs:annotation>
</xs:element>
<xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="FaultType">
    <xs:complexContent>
        <xs:extension base="gsml:ShearDisplacementStructureType">
            <xs:sequence>
                <xs:element maxOccurs="unbounded" minOccurs="0" name="segment" type="gsml:FaultPropertyType">
                    <xs:annotation>
                        <xs:documentation>In some use cases, eg., active seismology and fluid flow modelling, it is important to be able to segment the ShearDisplacementStructures where there is a change in orientation and/or dip and/or nature of the character of the fault. This segmentation can be scale dependent.
"segment" is the name of the role that a subsidiary Fault plays with respect to a Fault that it is part of. They are both Faults, and "segment" is the label on the composition. The distinction between Fault and FaultSystem is a question of the scale of description and the perspective of the observer; a Fault is composed of segments that are individually identified, but all considered part of a single Fault. Fault segments are usually collinear on the map, and generally do not overlap significantly along strike. A Fault may have 0..* segment parts (a part of/composition relationship.</xs:documentation>
                    </xs:annotation>
                </xs:element>
            </xs:sequence>
        </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="FaultPropertyType">
    <xs:sequence minOccurs="0">
        <xs:element ref="gsml:Fault"/>
    </xs:sequence>
    <xs:attributeGroup ref="gml:AssociationAttributeGroup"/>
</xs:complexType>