Schema documentation for

Showing:

Annotations

Attributes

Diagrams

Facets

Instances

Properties

Source

Used by

Main schema DelineationObjectMK_V1p0.xsd

Namespace

urn:metsateho:delineationobject

Properties

attribute form default:	unqualified
element form default:	qualified
version:	draft_1.0

Element DelineationObjectMK

Namespace

urn:metsateho:delineationobject

Diagram

Type

DelineationObjectMKType

Properties

content:

complex

Model

Header , DelineationObjectDefinition , Extension{0,1}

Children

DelineationObjectDefinition, Extension, Header

Instance

<DelineationObjectMK version="" versionDate="">
  <Header>{1,1}</Header>
  <DelineationObjectDefinition>{1,1}</DelineationObjectDefinition>
  <Extension extensionAction="">{0,1}</Extension>
</DelineationObjectMK>

Attributes

QName	Type	Fixed	Default	Use	Annotation
version	StanForD2010VersionType			required	1.0 version number The version number of the message in format: "major"."minor", where "major" is a sequential number of the major version (start from 1) and "minor" is a sequential number of the minor version.>
versionDate	xsd:date			required	1.0 yyyy-mm-dd Date of version

Source

<xsd:element name="DelineationObjectMK" type="DelineationObjectMKType"/>

Element DelineationObjectMKType / Header

Namespace

urn:metsateho:delineationobject

Diagram

Type

HeaderType

Properties

content:

complex

Model

MessageID , MessageCreationTime

Children

MessageCreationTime, MessageID

Instance

<Header>
  <MessageID>{1,1}</MessageID>
  <MessageCreationTime>{1,1}</MessageCreationTime>
</Header>

Source

<xsd:element name="Header" type="HeaderType"/>

Element HeaderType / MessageID

Namespace

urn:metsateho:delineationobject

Annotations

free text Unique identity of message. This identifier is send back to sender in acknowledgement message

Diagram

Type

xsd:string

Properties

content:

simple

Source

<xsd:element name="MessageID" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>
      <doc:Unit>free text</doc:Unit>
      <doc:Description>Unique identity of message. This identifier is send back to sender in acknowledgement message</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>

Element HeaderType / MessageCreationTime

Namespace

urn:metsateho:delineationobject

Annotations

yyyy-mm-ddThh:mm:ss[+|-]hh:mm Transmission time and date of message. Time stamp must have the following times registered: local time ±offset from UTC.

Diagram

Type

StanForD2010DateTimeType

Properties

content:

simple

Facets

pattern

.+T.+[+-].+

Source

<xsd:element name="MessageCreationTime" type="StanForD2010DateTimeType">
  <xsd:annotation>
    <xsd:documentation>
      <doc:Unit>yyyy-mm-ddThh:mm:ss[+|-]hh:mm</doc:Unit>
      <doc:Description>Transmission time and date of message.  Time stamp must have the following times registered: local time ±offset from UTC.</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>

Element DelineationObjectMKType / DelineationObjectDefinition

Namespace

urn:metsateho:delineationobject

Diagram

Type

DelineationObjectDefinitionType

Properties

content:

complex

Model

ContractNumber , ObjectUserID , StartDate , EndDate{0,1} , HarvestingSitePlanningObject+ , NumberOfStems{0,1} , NumberOfStemsWithCoordinates{0,1} , Stem* , Extension{0,1}

Children

ContractNumber, EndDate, Extension, HarvestingSitePlanningObject, NumberOfStems, NumberOfStemsWithCoordinates, ObjectUserID, StartDate, Stem

Instance

<DelineationObjectDefinition>
  <ContractNumber>{1,1}</ContractNumber>
  <ObjectUserID>{1,1}</ObjectUserID>
  <StartDate>{1,1}</StartDate>
  <EndDate>{0,1}</EndDate>
  <HarvestingSitePlanningObject>{1,unbounded}</HarvestingSitePlanningObject>
  <NumberOfStems>{0,1}</NumberOfStems>
  <NumberOfStemsWithCoordinates>{0,1}</NumberOfStemsWithCoordinates>
  <Stem>{0,unbounded}</Stem>
  <Extension extensionAction="">{0,1}</Extension>
</DelineationObjectDefinition>

Source

<xsd:element name="DelineationObjectDefinition" type="DelineationObjectDefinitionType"/>

Element DelineationObjectDefinitionType / ContractNumber

Namespace

urn:metsateho:delineationobject

Annotations

free text Harvesting object contract number/identity

Diagram

Type

xsd:string

Properties

content:

simple

Source

<xsd:element name="ContractNumber" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>
      <doc:Unit>free text</doc:Unit>
      <doc:Description>Harvesting object contract number/identity</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>

Element DelineationObjectDefinitionType / ObjectUserID

Namespace

urn:metsateho:delineationobject

Annotations

free text Identity per harvesting object defined by user of data, normally logging organisation.

Diagram

Type

xsd:string

Properties

content:

simple

Source

<xsd:element name="ObjectUserID" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>
      <doc:Unit>free text</doc:Unit>
      <doc:Description>Identity per harvesting object defined by user of data, normally logging organisation.</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>

Element DelineationObjectDefinitionType / StartDate

Namespace

urn:metsateho:delineationobject

Annotations

yyyy-mm-ddThh:mm:ss[+|-]hh:mm Time and date for starting production at a site for the first time. Time stamp must have the following times registered: local time ±offset from UTC.

Diagram

Type

StanForD2010DateTimeType

Properties

content:

simple

Facets

pattern

.+T.+[+-].+

Source

<xsd:element name="StartDate" type="StanForD2010DateTimeType">
  <xsd:annotation>
    <xsd:documentation>
      <doc:Unit>yyyy-mm-ddThh:mm:ss[+|-]hh:mm</doc:Unit>
      <doc:Description>Time and date for starting production at a site for the first time. Time stamp must have the following times registered: local time ±offset from UTC.</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>

Element DelineationObjectDefinitionType / EndDate

Namespace

urn:metsateho:delineationobject

Annotations

yyyy-mm-ddThh:mm:ss[+|-]hh:mm Time and date for ending a site. Mandatory when object is finished. Time stamp must have the following times registered: local time ±offset from UTC.

Diagram

Type

StanForD2010DateTimeType

Properties

content:	simple
minOccurs:	0

Facets

pattern

.+T.+[+-].+

Source

<xsd:element name="EndDate" type="StanForD2010DateTimeType" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>
      <doc:Unit>yyyy-mm-ddThh:mm:ss[+|-]hh:mm</doc:Unit>
      <doc:Description>Time and date for ending a site. Mandatory when object is finished. Time stamp must have the following times registered: local time ±offset from UTC.</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>

Element DelineationObjectDefinitionType / HarvestingSitePlanningObject

Namespace

urn:metsateho:delineationobject

Diagram

Type

HarvestingSitePlanningObjectType

Properties

content:	complex
maxOccurs:	unbounded

Model

LoggingFormCode , PolygonGeometry

Children

LoggingFormCode, PolygonGeometry

Instance

<HarvestingSitePlanningObject>
  <LoggingFormCode>{1,1}</LoggingFormCode>
  <PolygonGeometry>{1,1}</PolygonGeometry>
</HarvestingSitePlanningObject>

Source

<xsd:element name="HarvestingSitePlanningObject" type="HarvestingSitePlanningObjectType" maxOccurs="unbounded"/>

Element HarvestingSitePlanningObjectType / LoggingFormCode

Namespace

urn:metsateho:delineationobject

Annotations

1.0 code Code for logging form. Allowed values can be found from MTS: CuttingTypeType/Toimenpiteen hakkuutapa

Diagram

Type

CuttingTypeType

Properties

content:

simple

Facets

enumeration	0	Määräaikainen lepo
enumeration	1	Ylispuiden poisto
enumeration	2	Ensiharvennus
enumeration	3	Harvennus
enumeration	4	Kaistalehakkuu
enumeration	5	Avohakkuu
enumeration	6	Verhopuuhakkuu
enumeration	7	Suojuspuuhakkuu
enumeration	8	Siemenpuuhakkuu
enumeration	9	Erikoishakkuu
enumeration	11	Yläharvennus
enumeration	12	Väljennyshakkuu
enumeration	13	Kunnostushakkuu
enumeration	14	Poimintahakkuu
enumeration	15	Pienaukkohakkuu
enumeration	20	Energiapuuharvennus
enumeration	90	Maankäyttömuodon muutokseen johtava erityishakkuu. Metsänkäyttöilmoituksella esiintyvä hakkuutapa.
enumeration	91	Erityishakkuu (Metsälain 6§:n mukainen hakkuu). Metsänkäyttöilmoituksella esiintyvä hakkuutapa.
enumeration	92	Muu hakkuu tai toimenpide. Metsänkäyttöilmoituksella esiintyvä hakkuutapa.
enumeration	93	Uudistushakkuu metsätuhoalueella.
enumeration	94	Kasvatushakkuu metsätuhoalueella.

Source

<xsd:element name="LoggingFormCode" type="fdc:CuttingTypeType">
  <xsd:annotation>
    <xsd:documentation>
      <doc:VersionCreated>1.0</doc:VersionCreated>
      <doc:Unit>code</doc:Unit>
      <doc:Description>Code for logging form. Allowed values can be found from MTS: CuttingTypeType/Toimenpiteen hakkuutapa</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>

Element HarvestingSitePlanningObjectType / PolygonGeometry

Namespace

urn:metsateho:delineationobject

Diagram

Type

PolygonType

Properties

content:

simple

Source

<xsd:element name="PolygonGeometry" type="gml:PolygonType"/>

Element DelineationObjectDefinitionType / NumberOfStems

Namespace

urn:metsateho:delineationobject

Annotations

Number of stems in delineation object.

Diagram

Type

xsd:nonNegativeInteger

Properties

content:	simple
minOccurs:	0

Source

<xsd:element name="NumberOfStems" type="xsd:nonNegativeInteger" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>
      <doc:Description>Number of stems in delineation object.</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>

Element DelineationObjectDefinitionType / NumberOfStemsWithCoordinates

Namespace

urn:metsateho:delineationobject

Annotations

Number of stems in delineation object that have coordinates.

Diagram

Type

xsd:nonNegativeInteger

Properties

content:	simple
minOccurs:	0

Source

<xsd:element name="NumberOfStemsWithCoordinates" type="xsd:nonNegativeInteger" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>
      <doc:Description>Number of stems in delineation object that have coordinates.</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>

Element DelineationObjectDefinitionType / Stem

Namespace

urn:metsateho:delineationobject

Diagram

Type

StemType

Properties

content:	complex
minOccurs:	0
maxOccurs:	unbounded

Model

StemID , StemNumber , StemCoordinates , Extension{0,1}

Children

Extension, StemCoordinates, StemID, StemNumber

Instance

<Stem>
  <StemID>{1,1}</StemID>
  <StemNumber>{1,1}</StemNumber>
  <StemCoordinates coordinateReferenceSystem="" receiverPosition="">{1,1}</StemCoordinates>
  <Extension extensionAction="">{0,1}</Extension>
</Stem>

Source

<xsd:element name="Stem" type="StemType" minOccurs="0" maxOccurs="unbounded"/>

Element StemType / StemID

Namespace

urn:metsateho:delineationobject

Annotations

1.0 sequential no Stem number. A unique running / sequential number that is generated during extraction process of hpr- or stm-file(s). Using this number instead the number of file, we are certain that every stem has unique number in bucking object

Diagram

Type

xsd:positiveInteger

Properties

content:

simple

Source

<xsd:element name="StemID" type="xsd:positiveInteger">
  <xsd:annotation>
    <xsd:documentation>
      <doc:VersionCreated>1.0</doc:VersionCreated>
      <doc:Unit>sequential no</doc:Unit>
      <doc:Description>Stem number. A unique running / sequential number that is generated during extraction process of hpr- or stm-file(s). Using this number instead the number of file, we are certain that every stem has unique number in bucking object</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>

Element StemType / StemNumber

Namespace

urn:metsateho:delineationobject

Annotations

1.0 V270 sequential no Stem number. A running / sequential number only to be reset when starting on a new harvesting object. (Old stem code 500 in v266)

Diagram

Type

xsd:positiveInteger

Properties

content:

simple

Source

<xsd:element name="StemNumber" type="xsd:positiveInteger">
  <xsd:annotation>
    <xsd:documentation>
      <doc:VersionCreated>1.0</doc:VersionCreated>
      <doc:VarNumber>V270</doc:VarNumber>
      <doc:Unit>sequential no</doc:Unit>
      <doc:Description>Stem number. A running / sequential number only to be reset when starting on a new harvesting object. (Old stem code 500 in v266)</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>

Element StemType / StemCoordinates

Namespace

urn:metsateho:delineationobject

Annotations

1.0 2.0 Stem coordinates, describes the location of the standing tree.

Diagram

Type

CoordinatesType

Properties

content:

complex

Model

Latitude , Longitude , Altitude , CoordinateDate{0,1} , Extension{0,1}

Children

Altitude, CoordinateDate, Extension, Latitude, Longitude

Instance

<StemCoordinates coordinateReferenceSystem="" receiverPosition="">
  <Latitude latitudeCategory="">{1,1}</Latitude>
  <Longitude longitudeCategory="">{1,1}</Longitude>
  <Altitude>{1,1}</Altitude>
  <CoordinateDate>{0,1}</CoordinateDate>
  <Extension extensionAction="">{0,1}</Extension>
</StemCoordinates>

Attributes

QName	Type	Fixed	Default	Use	Annotation
coordinateReferenceSystem	CoordinateReferenceSystemType			required	1.0 list Coordinate system used in StanForD file: WGS84
receiverPosition	ReceiverPositionType			required	1.0 list Position of coordinate registration in file: "Base machine position", "Crane tip position when felling the tree. Observe that only "Base machine position“ is relevant for all types of coordinates. Other enumerations valid only in some specific situations."

Source

<xsd:element name="StemCoordinates" type="CoordinatesType">
  <xsd:annotation>
    <xsd:documentation>
      <doc:VersionCreated>1.0</doc:VersionCreated>
      <doc:VersionModified>2.0</doc:VersionModified>
      <doc:Description>Stem coordinates, describes the location of the standing tree.</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>

Element StemType / Extension

Namespace

urn:metsateho:delineationobject

Annotations

1.0 Extension element can include whatever data the users want. The only requirement is that it is well-formed XML i.e. it is tagged

Diagram

Type

ExtensionType

Properties

content:	complex
minOccurs:	0

Model

ANY element from ANY namespace

Attributes

QName	Type	Fixed	Default	Use	Annotation
extensionAction	ExtensionActionType			optional	1.0 list Enumeration list. Allowed values are: "Copy" and "Ignore". The purpose of this attribute is to inform the receiver of the message that sender want to get back the copy of the content of the extension structure. For example if we have product specifiic information in extension structure send in pin-message we might want that back in hpr-message.

Source

<xsd:element name="Extension" type="ExtensionType" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>
      <doc:VersionCreated>1.0</doc:VersionCreated>
      <doc:Description>Extension element can include whatever data the users want. The only requirement is that it is well-formed XML i.e. it is tagged</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>

Element DelineationObjectDefinitionType / Extension

Namespace

urn:metsateho:delineationobject

Annotations

1.0 Extension element can include whatever data the users want. The only requirement is that it is well-formed XML i.e. it is tagged

Diagram

Type

ExtensionType

Properties

content:	complex
minOccurs:	0

Model

ANY element from ANY namespace

Attributes

QName	Type	Fixed	Default	Use	Annotation
extensionAction	ExtensionActionType			optional	1.0 list Enumeration list. Allowed values are: "Copy" and "Ignore". The purpose of this attribute is to inform the receiver of the message that sender want to get back the copy of the content of the extension structure. For example if we have product specifiic information in extension structure send in pin-message we might want that back in hpr-message.

Source

<xsd:element name="Extension" type="ExtensionType" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>
      <doc:VersionCreated>1.0</doc:VersionCreated>
      <doc:Description>Extension element can include whatever data the users want. The only requirement is that it is well-formed XML i.e. it is tagged</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>

Element DelineationObjectMKType / Extension

Namespace

urn:metsateho:delineationobject

Annotations

1.0 Extension element can include whatever data the users want. The only requirement is that it is well-formed XML i.e. it is tagged

Diagram

Type

ExtensionType

Properties

content:	complex
minOccurs:	0

Model

ANY element from ANY namespace

Attributes

QName	Type	Fixed	Default	Use	Annotation
extensionAction	ExtensionActionType			optional	1.0 list Enumeration list. Allowed values are: "Copy" and "Ignore". The purpose of this attribute is to inform the receiver of the message that sender want to get back the copy of the content of the extension structure. For example if we have product specifiic information in extension structure send in pin-message we might want that back in hpr-message.

Source

<xsd:element name="Extension" type="ExtensionType" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>
      <doc:VersionCreated>1.0</doc:VersionCreated>
      <doc:Description>Extension element can include whatever data the users want. The only requirement is that it is well-formed XML i.e. it is tagged</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>

Complex Type DelineationObjectMKType

Namespace

urn:metsateho:delineationobject

Diagram

Used by

Element

DelineationObjectMK

Model

Header , DelineationObjectDefinition , Extension{0,1}

Children

DelineationObjectDefinition, Extension, Header

Attributes

QName	Type	Fixed	Default	Use	Annotation
version	StanForD2010VersionType			required	1.0 version number The version number of the message in format: "major"."minor", where "major" is a sequential number of the major version (start from 1) and "minor" is a sequential number of the minor version.>
versionDate	xsd:date			required	1.0 yyyy-mm-dd Date of version

Source

<xsd:complexType name="DelineationObjectMKType">
  <xsd:sequence>
    <xsd:element name="Header" type="HeaderType"/>
    <xsd:element name="DelineationObjectDefinition" type="DelineationObjectDefinitionType"/>
    <xsd:element name="Extension" type="ExtensionType" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation>
          <doc:VersionCreated>1.0</doc:VersionCreated>
          <doc:Description>Extension element can include whatever data the users want. The only requirement is that it is well-formed XML i.e. it is tagged</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
  </xsd:sequence>
  <xsd:attributeGroup ref="MessageAttributeGroup"/>
</xsd:complexType>

Complex Type HeaderType

Namespace

urn:metsateho:delineationobject

Diagram

Used by

Element

DelineationObjectMKType/Header

Model

MessageID , MessageCreationTime

Children

MessageCreationTime, MessageID

Source

<xsd:complexType name="HeaderType">
  <xsd:sequence>
    <xsd:element name="MessageID" type="xsd:string">
      <xsd:annotation>
        <xsd:documentation>
          <doc:Unit>free text</doc:Unit>
          <doc:Description>Unique identity of message. This identifier is send back to sender in acknowledgement message</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element name="MessageCreationTime" type="StanForD2010DateTimeType">
      <xsd:annotation>
        <xsd:documentation>
          <doc:Unit>yyyy-mm-ddThh:mm:ss[+|-]hh:mm</doc:Unit>
          <doc:Description>Transmission time and date of message.  Time stamp must have the following times registered: local time ±offset from UTC.</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
  </xsd:sequence>
</xsd:complexType>

Complex Type DelineationObjectDefinitionType

Namespace

urn:metsateho:delineationobject

Diagram

Used by

Element

DelineationObjectMKType/DelineationObjectDefinition

Model

Children

ContractNumber, EndDate, Extension, HarvestingSitePlanningObject, NumberOfStems, NumberOfStemsWithCoordinates, ObjectUserID, StartDate, Stem

Source

<xsd:complexType name="DelineationObjectDefinitionType">
  <xsd:sequence>
    <xsd:element name="ContractNumber" type="xsd:string">
      <xsd:annotation>
        <xsd:documentation>
          <doc:Unit>free text</doc:Unit>
          <doc:Description>Harvesting object contract number/identity</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element name="ObjectUserID" type="xsd:string">
      <xsd:annotation>
        <xsd:documentation>
          <doc:Unit>free text</doc:Unit>
          <doc:Description>Identity per harvesting object defined by user of data, normally logging organisation.</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element name="StartDate" type="StanForD2010DateTimeType">
      <xsd:annotation>
        <xsd:documentation>
          <doc:Unit>yyyy-mm-ddThh:mm:ss[+|-]hh:mm</doc:Unit>
          <doc:Description>Time and date for starting production at a site for the first time. Time stamp must have the following times registered: local time ±offset from UTC.</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element name="EndDate" type="StanForD2010DateTimeType" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation>
          <doc:Unit>yyyy-mm-ddThh:mm:ss[+|-]hh:mm</doc:Unit>
          <doc:Description>Time and date for ending a site. Mandatory when object is finished. Time stamp must have the following times registered: local time ±offset from UTC.</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element name="HarvestingSitePlanningObject" type="HarvestingSitePlanningObjectType" maxOccurs="unbounded"/>
    <xsd:element name="NumberOfStems" type="xsd:nonNegativeInteger" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation>
          <doc:Description>Number of stems in delineation object.</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element name="NumberOfStemsWithCoordinates" type="xsd:nonNegativeInteger" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation>
          <doc:Description>Number of stems in delineation object that have coordinates.</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element name="Stem" type="StemType" minOccurs="0" maxOccurs="unbounded"/>
    <xsd:element name="Extension" type="ExtensionType" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation>
          <doc:VersionCreated>1.0</doc:VersionCreated>
          <doc:Description>Extension element can include whatever data the users want. The only requirement is that it is well-formed XML i.e. it is tagged</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
  </xsd:sequence>
</xsd:complexType>

Complex Type HarvestingSitePlanningObjectType

Namespace

urn:metsateho:delineationobject

Diagram

Used by

Element

DelineationObjectDefinitionType/HarvestingSitePlanningObject

Model

LoggingFormCode , PolygonGeometry

Children

LoggingFormCode, PolygonGeometry

Source

<xsd:complexType name="HarvestingSitePlanningObjectType">
  <xsd:sequence>
    <xsd:element name="LoggingFormCode" type="fdc:CuttingTypeType">
      <xsd:annotation>
        <xsd:documentation>
          <doc:VersionCreated>1.0</doc:VersionCreated>
          <doc:Unit>code</doc:Unit>
          <doc:Description>Code for logging form. Allowed values can be found from MTS: CuttingTypeType/Toimenpiteen hakkuutapa</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element name="PolygonGeometry" type="gml:PolygonType"/>
  </xsd:sequence>
</xsd:complexType>

Complex Type StemType

Namespace

urn:metsateho:delineationobject

Diagram

Used by

Element

DelineationObjectDefinitionType/Stem

Model

StemID , StemNumber , StemCoordinates , Extension{0,1}

Children

Extension, StemCoordinates, StemID, StemNumber

Source

<xsd:complexType name="StemType">
  <xsd:sequence>
    <xsd:element name="StemID" type="xsd:positiveInteger">
      <xsd:annotation>
        <xsd:documentation>
          <doc:VersionCreated>1.0</doc:VersionCreated>
          <doc:Unit>sequential no</doc:Unit>
          <doc:Description>Stem number. A unique running / sequential number that is generated during extraction process of hpr- or stm-file(s). Using this number instead the number of file, we are certain that every stem has unique number in bucking object</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element name="StemNumber" type="xsd:positiveInteger">
      <xsd:annotation>
        <xsd:documentation>
          <doc:VersionCreated>1.0</doc:VersionCreated>
          <doc:VarNumber>V270</doc:VarNumber>
          <doc:Unit>sequential no</doc:Unit>
          <doc:Description>Stem number. A running / sequential number only to be reset when starting on a new harvesting object. (Old stem code 500 in v266)</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element name="StemCoordinates" type="CoordinatesType">
      <xsd:annotation>
        <xsd:documentation>
          <doc:VersionCreated>1.0</doc:VersionCreated>
          <doc:VersionModified>2.0</doc:VersionModified>
          <doc:Description>Stem coordinates, describes the location of the standing tree.</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element name="Extension" type="ExtensionType" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation>
          <doc:VersionCreated>1.0</doc:VersionCreated>
          <doc:Description>Extension element can include whatever data the users want. The only requirement is that it is well-formed XML i.e. it is tagged</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
  </xsd:sequence>
</xsd:complexType>