Data Type - geometry frame

Datatype: geometryFrame

Found in http://www.posc.org/schemas/dtypes_u.xsd

Download file

Description:

An element of type geometryFrame will have three subelements and an attribute:

coordinateSystem-ref. A reference to a coordinate system instance. This subelement is of type reference.

gridDescription. A gridDescription element has two subelements:

grid-ref. A reference to a grid instance. This subelement is of type reference.
descriptor. There will be one descriptor for each axis of the grid. The descriptors will be a list, corresponding to the list of axes in the grid. I.e., the first descriptor relates to the first grid axis, etc. A descriptor element has three attributes:

Attribute lowerBound. A positive integer. This is the lower bound of the data for the elements relating to the grid axis. This attribute is optional. If it is not present, it is defaulted to 1
Attribute count. The number of values to be filled on the axis. The total number of values in each leaf frame will be the product of the count attributes of all the descriptors.
Attribute storageOrder. The storage order of the data relating to the axis. The axis with storageOrder="1" will be the slowest to fill, and the axis with the highest storageOrder value will be the fastest.

vertex-ref. An optional reference to a vertex which represents the origin for the data values. This subelement is of type reference. If this element is not present, the origin of the data is the origin of the referenced coordinate system.

Attribute detailedType. The detailed type as defined in the Epicentre DAE document. Examples would be FT_LINE, FT_SURFACE, FT_CLOSED_LINE.

Proposed Usage:

This datatype was developed to support the Epicentre geometry data types (line, surface, and volume) in conjuction with one or more leaf frames. Its intended usage is shown in the PEF geometry document. It is not anticipated that it will be useful outside of the PEF application.

XML Schema:

The schema and examples do not explicitly show the lines that set the namespaces.

All schema examples will use xsd: as the namespace for the schema tags and datatypes, and null for all the locally generated namespaces.

XML Examples will exclude namespace modifiers for clarity. Actual XML will probably need namespaces.

<xsd:complexType name="geometryFrame">
  <xsd:sequence>
    <xsd:element name="coordinateSystem-ref" type="reference"/>
    <xsd:element name="gridDescription">
      <xsd:complexType>
       <xsd:sequence>
        <xsd:element name="grid-ref" type="reference"/>
        <xsd:element name="descriptor" type="descriptor" maxOccurs="unbounded"/>
       </xsd:sequence>
      </xsd:complexType>
    </xsd:element>
    <xsd:element name="vertex-ref" type="reference" minOccurs="0"/>
  </xsd:sequence>
  <xsd:attribute name="detailedType" type="xsd:string"/>
</xsd:complexType>

<xsd:complexType name="descriptor">
  <xsd:attribute name="lowerBound" type="xsd:positiveInteger" 
              use="default" value="1"/>
  <xsd:attribute name="count" type="xsd:positiveInteger" use="required"/>
  <xsd:attribute name="storageOrder" type="xsd:positiveInteger" use="required"/>
</xsd:complexType>

Sample Usage Schema:

Because of its intended usage, this datatypes usage is best shown in the PEF geometry document.

Sample XML:

Because of its intended usage, this datatypes usage is best shown in the PEF geometry document.