Schema documentation for component diggs:extent

The area over which this group acts, or within which its members lie. An extent, not a reference point: a treated area, a monitoring network or a paired investigation has no single meaningful position. Optional, because a group need not be spatially delimited; a borehole/CPT pair, for example, is defined by the proximity of its two members. Two-dimensional; elevation is not meaningful for a group extent. Where a concrete group also carries a scalar area, the geometry prevails. May be given inline or by reference (xlink:href). A group extent and a member's featureExtent are not the same thing by default: a group's members often lie outside the area the group is about, for example exploratory boreholes drilled beyond a treated footprint. Where the two genuinely coincide, give the polygon once and reference it from the other rather than writing the same coordinates twice. See diggs:featureExtent.

<diggs:extent owns="false" xlink:href="" nilReason="" xmlns:diggs="http://diggsml.org/schemas/3"> <diggs:AbstractSurface axisLabels="" gml:id="" srsDimension="" srsName="" uomLabels="">{1,1}</diggs:AbstractSurface> <diggs:MultiSurface aggregationType="" axisLabels="" gml:id="" srsDimension="" srsName="" uomLabels="">{1,1}</diggs:MultiSurface> </diggs:extent>

QName

Type

Default

Use

nilReason

gml:NilReasonType

optional

owns

boolean

false

optional

xlink:href

anyURI

optional

<element minOccurs="0" name="extent" type="diggs:SurfacePropertyType"> <annotation> <documentation>The area over which this group acts, or within which its members lie. An extent, not a reference point: a treated area, a monitoring network or a paired investigation has no single meaningful position. Optional, because a group need not be spatially delimited; a borehole/CPT pair, for example, is defined by the proximity of its two members. Two-dimensional; elevation is not meaningful for a group extent. Where a concrete group also carries a scalar area, the geometry prevails. May be given inline or by reference (xlink:href). A group extent and a member's featureExtent are not the same thing by default: a group's members often lie outside the area the group is about, for example exploratory boreholes drilled beyond a treated footprint. Where the two genuinely coincide, give the polygon once and reference it from the other rather than writing the same coordinates twice. See diggs:featureExtent.</documentation> </annotation> </element>

Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods. This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.

<complexType name="AbstractSamplingFeatureGroupType" abstract="true">
  <annotation>
    <documentation>Abstract base type for groups of sampling features. Adds the spatial extent of the group.</documentation>
  </annotation>
  <complexContent>
    <extension base="diggs:AbstractProjectScopedGroupType">
      <sequence>
        <element minOccurs="0" name="extent" type="diggs:SurfacePropertyType">
          <annotation>
            <documentation>The area over which this group acts, or within which its members lie. An extent, not a reference point: a treated area, a monitoring network or a paired investigation has no single meaningful position. Optional, because a group need not be spatially delimited; a borehole/CPT pair, for example, is defined by the proximity of its two members. Two-dimensional; elevation is not meaningful for a group extent. Where a concrete group also carries a scalar area, the geometry prevails. May be given inline or by reference (xlink:href). A group extent and a member's featureExtent are not the same thing by default: a group's members often lie outside the area the group is about, for example exploratory boreholes drilled beyond a treated footprint. Where the two genuinely coincide, give the polygon once and reference it from the other rather than writing the same coordinates twice. See diggs:featureExtent.</documentation>
          </annotation>
        </element>
      </sequence>
    </extension>
  </complexContent>
</complexType>

Showing: