"Seegrid will be due for a migration to confluence on the 1st of August. Any update on or after the 1st of August will NOT be migrated"

Geological Boundaries


Related pages

Schema documents

A set of geological boundary features, based on surface features (see GeometryBasedFeatures), are defined in the schema document

Example Instances


Model and Document Structure

Geological Boundaries


Model from XmmlSchemaRepository:trunk/XMML/boundaries.xsd
boundary.png fault.png


Feature types for 3-D geological boundaries are provided. The basic content model used for xmml:Boundary extends xmml:SurfacedFeatureType (see GeometryBasedFeatures) with
  • a set of unitBounded properties, each pointing to a stratigraphic unit for which this feature provides part of its boundary; note that the property element carries an XML attribute orientation which records whether the oriented surface bounds the unit to the positive or negative direction.

A set of typed boundaries are based on this model:
  • xmml:Fault, xmml:IntrusiveContact, xmml:StratigraphicContact, xmml:Unconformity represent more specific geological boundary types
  • xmml:ModelDomainBoundary is used to describe the boundary of a region (typically rectangular) used for a numerical modelling instance.

Currently all of these feature types share the same content model as the generic xmml:Boundary. It is expected that the models will have additional properties added in future versions.

Note that since the shape property follows the standard GmlProperty pattern, its value can be stored remotely, perhaps as part of another feature, and used by reference as the value of the shape of the boundary feature. This capability allows the user to ensure the integrity and consistency of model topology, where several features may share the same geometry.

Issues and change requests

Readers are invited to add issues to this table - select [Edit Table] below. It is not mandatory to enter a solution, but change requests are more likely to be implemented if a concrete solution is proposed.

%EDITTABLE{ header="| # | By | Timestamp | Component(s) | Description of issue | Proposed solution | Resolution |" format="| row, -1 | text, 25, Unknown | label, 0, 19 Sep 2019 11:15 | textarea, 3x25, Component(s) | textarea, 3x25, Description | textarea, 3x25, Proposal | select, 1, Unaddressed, Progressing, Resolved |" changerows="on" }%
# By Timestamp Component(s) Description of issue Proposed solution Resolution
1 My org 14 May 2004 collar location A big whinge a proposed solution Unaddressed
Topic revision: r7 - 15 Oct 2010, UnknownUser

Current license: All material on this collaboration platform is licensed under a Creative Commons Attribution 3.0 Australia Licence (CC BY 3.0).