The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="Layer" type="tps:layerType"><xs:annotation><xs:documentation>A Layer is defined by drawing parameters</xs:documentation></xs:annotation></xs:element>
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="CodeDescription" type="tps:codeDescriptionType"><xs:annotation><xs:documentation>A Code that can be used by an element to gain some properties</xs:documentation></xs:annotation></xs:element>
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="ObservationInfo" type="tps:observationInfoType"><xs:annotation><xs:documentation>An Observation info has the general information about a Measurement session</xs:documentation></xs:annotation></xs:element>
tps:Name , tps:Notes{0,1} , (ANY element from TARGET namespace 'tps' and ANY element OTHER than the defined siblings | ANY element from ANY namespace OTHER than 'tps')
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="DLRun" type="tps:dlRunType"><xs:annotation><xs:documentation>A Digital Level run contributes to create a Measurement Session</xs:documentation></xs:annotation></xs:element>
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="Device" type="tps:deviceType"><xs:annotation><xs:documentation>A Gnss device, a TS device or a DL device. It contributes to create a Measurement Session</xs:documentation></xs:annotation></xs:element>
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="Controller" type="tps:controllerType"><xs:annotation><xs:documentation>A Controller contributes to create a Measurement Session</xs:documentation></xs:annotation></xs:element>
A Coordinate system can refer to structures contained in external files, like geoids. It contains also Localization data. It contributes to create a Measurement Session
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="CoordSystemInfo" type="tps:coordinateSystemInfoType"><xs:annotation><xs:documentation>A Coordinate system can refer to structures contained in external files, like geoids. It contains also Localization data. It contributes to create a Measurement Session</xs:documentation></xs:annotation></xs:element>
tps:Manufacturer , tps:Model , tps:SerialNumber , (ANY element from TARGET namespace 'tps' and ANY element OTHER than the defined siblings | ANY element from ANY namespace OTHER than 'tps')
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="GPSAntennaSettings" type="tps:gpsAntennaSettingsType"><xs:annotation><xs:documentation>A Gnss antenna contributes to create a Measurement Session</xs:documentation></xs:annotation></xs:element>
A Block definition is defined as a collection of objects and a reference point (the real Block is an object itself, and can be included in another Block definition)
tps:Name , tps:RefPoint , tps:Objects , (ANY element from TARGET namespace 'tps' and ANY element OTHER than the defined siblings | ANY element from ANY namespace OTHER than 'tps')
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="BlockDefinition" type="tps:blockDefinitionType"><xs:annotation><xs:documentation>A Block definition is defined as a collection of objects and a reference point (the real Block is an object itself, and can be included in another Block definition)</xs:documentation></xs:annotation></xs:element>
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="ScanningSession" type="tps:scanningSessionType"><xs:annotation><xs:documentation>Definition of a Scanning session (???)</xs:documentation></xs:annotation></xs:element>
tps:Name , tps:StaEquation* , (ANY element from TARGET namespace 'tps' and ANY element OTHER than the defined siblings | ANY element from ANY namespace OTHER than 'tps')
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="StaEquationSet" type="tps:staEquationSetType"><xs:annotation><xs:documentation>A collection of Station equations</xs:documentation></xs:annotation></xs:element>
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="HorizontalAlignment" type="tps:horizontalAlignmentType"><xs:annotation><xs:documentation>A Horizontal alignment is defined by a sequence of horizontal elements. It's used by an Alignment or a Road string</xs:documentation></xs:annotation></xs:element>
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="VerticalAlignment" type="tps:verticalAlignmentType"><xs:annotation><xs:documentation>A Vertical alignment is defined by a sequence of vertical positions. It's used by an Alignment or a Road string</xs:documentation></xs:annotation></xs:element>
tps:Name , tps:Cut , tps:Fill , tps:TemplateSegment* , (ANY element from TARGET namespace 'tps' and ANY element OTHER than the defined siblings | ANY element from ANY namespace OTHER than 'tps')
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="RoadTemplate" type="tps:roadTemplateType"><xs:annotation><xs:documentation>A Road template is defined by a sequence of 2D segments. It's used by a Cross section</xs:documentation></xs:annotation></xs:element>
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="CrossSectionSet" type="tps:crossSectionSetType"><xs:annotation><xs:documentation>A sequence of Cross sections, used by an Alignment</xs:documentation></xs:annotation></xs:element>
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="RoadStringSet" type="tps:roadStringSetType"><xs:annotation><xs:documentation>A sequence of Road strings, that can be used by an Alignment instead of Cross sections</xs:documentation></xs:annotation></xs:element>
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="Alignment" type="tps:alignmentType"><xs:annotation><xs:documentation>An Alignment is defined by a Horizontal alignment, a Vertical alignment and a Cross section set (or a Road string set).</xs:documentation></xs:annotation></xs:element>
tps:Name , tps:OriSession* , tps:StereoPair* , (ANY element from TARGET namespace 'tps' and ANY element OTHER than the defined siblings | ANY element from ANY namespace OTHER than 'tps')
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="OrientationJob" type="tps:orientationJobType"><xs:annotation><xs:documentation>An Orientation job is defined as a sequence of orientation sessions and a sequence of stereo pairs (???)</xs:documentation></xs:annotation></xs:element>
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="Surface" type="tps:surfaceType"><xs:annotation><xs:documentation>A Surface is defined by a collection of triangles, which refers to a sequence of positions</xs:documentation></xs:annotation></xs:element>
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="FieldReport" type="tps:fieldReportsType"><xs:annotation><xs:documentation>A Field report is defined by its parameters (???)</xs:documentation></xs:annotation></xs:element>
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="Region" type="tps:regionType"><xs:annotation><xs:documentation>A Region describes an area with some attributes</xs:documentation></xs:annotation></xs:element>
tps:Name , tps:Object* , (ANY element from TARGET namespace 'tps' and ANY element OTHER than the defined siblings | ANY element from ANY namespace OTHER than 'tps')
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="ObjectList" type="tps:objectListType"><xs:annotation><xs:documentation>An Object List is a list of references to Objects (usually used to describe a Point List)</xs:documentation></xs:annotation></xs:element>
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="PointCustomSymbol" type="tps:pointSymbolType"><xs:annotation><xs:documentation>A customized point symbol definition</xs:documentation></xs:annotation></xs:element>
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="LineCustomStyle" type="tps:lineStyleType"><xs:annotation><xs:documentation>A customized line style definition</xs:documentation></xs:annotation></xs:element>
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
tps:Name , tps:Description{0,1} , tps:Scalable{0,1} , tps:ScaleFactor{0,1} , tps:RotationAngle{0,1} , (ANY element from TARGET namespace 'tps' and ANY element OTHER than the defined siblings | ANY element from ANY namespace OTHER than 'tps') , tps:ImageRef , (ANY element from TARGET namespace 'tps' and ANY element OTHER than the defined siblings | ANY element from ANY namespace OTHER than 'tps')
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="Location" type="tps:locationType"><xs:annotation><xs:documentation>A location is a set of informations about where a quantity is located</xs:documentation></xs:annotation></xs:element>
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="Material" type="tps:materialType"><xs:annotation><xs:documentation>A material is a type of work or material (or cost code) of the quantity</xs:documentation></xs:annotation></xs:element>
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="Quantity" type="tps:quantityType"><xs:annotation><xs:documentation>A quantity type describes the location, the material and its distribution</xs:documentation></xs:annotation></xs:element>
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="Dependency" type="tps:dependencyType"><xs:annotation><xs:documentation>A dependency type describes the relationship between two tasks: a predecessor and a successor</xs:documentation></xs:annotation></xs:element>
The id of the element. In Data structure it must be always defined and it can be referenced by an other element that uses this element. In Transaction structure it must be defined by a 'created' action (not defined in the other actions)
The reference to the id of this element. In MAXML structure is not defined. In Transaction structure it must be defined by 'modified' and 'deleted' action (not defined in 'created' action)
Source
<xs:element name="BkgImage" type="tps:imageType"><xs:annotation><xs:documentation>An image used as CAD background</xs:documentation></xs:annotation></xs:element>
<xs:group name="elementGroup"><xs:annotation><xs:documentation>A single element, of any type</xs:documentation></xs:annotation><xs:choice><xs:element name="Layer" type="tps:layerType"><xs:annotation><xs:documentation>A Layer is defined by drawing parameters</xs:documentation></xs:annotation></xs:element><xs:element name="CodeDescription" type="tps:codeDescriptionType"><xs:annotation><xs:documentation>A Code that can be used by an element to gain some properties</xs:documentation></xs:annotation></xs:element><xs:element name="ObservationInfo" type="tps:observationInfoType"><xs:annotation><xs:documentation>An Observation info has the general information about a Measurement session</xs:documentation></xs:annotation></xs:element><xs:element name="DLRun" type="tps:dlRunType"><xs:annotation><xs:documentation>A Digital Level run contributes to create a Measurement Session</xs:documentation></xs:annotation></xs:element><xs:element name="Device" type="tps:deviceType"><xs:annotation><xs:documentation>A Gnss device, a TS device or a DL device. It contributes to create a Measurement Session</xs:documentation></xs:annotation></xs:element><xs:element name="Controller" type="tps:controllerType"><xs:annotation><xs:documentation>A Controller contributes to create a Measurement Session</xs:documentation></xs:annotation></xs:element><xs:element name="CoordSystemInfo" type="tps:coordinateSystemInfoType"><xs:annotation><xs:documentation>A Coordinate system can refer to structures contained in external files, like geoids. It contains also Localization data. It contributes to create a Measurement Session</xs:documentation></xs:annotation></xs:element><xs:element name="GPSAntennaSettings" type="tps:gpsAntennaSettingsType"><xs:annotation><xs:documentation>A Gnss antenna contributes to create a Measurement Session</xs:documentation></xs:annotation></xs:element><xs:element name="BlockDefinition" type="tps:blockDefinitionType"><xs:annotation><xs:documentation>A Block definition is defined as a collection of objects and a reference point (the real Block is an object itself, and can be included in another Block definition)</xs:documentation></xs:annotation></xs:element><xs:element name="ScanningSession" type="tps:scanningSessionType"><xs:annotation><xs:documentation>Definition of a Scanning session (???)</xs:documentation></xs:annotation></xs:element><xs:element name="StaEquationSet" type="tps:staEquationSetType"><xs:annotation><xs:documentation>A collection of Station equations</xs:documentation></xs:annotation></xs:element><xs:element name="HorizontalAlignment" type="tps:horizontalAlignmentType"><xs:annotation><xs:documentation>A Horizontal alignment is defined by a sequence of horizontal elements. It's used by an Alignment or a Road string</xs:documentation></xs:annotation></xs:element><xs:element name="VerticalAlignment" type="tps:verticalAlignmentType"><xs:annotation><xs:documentation>A Vertical alignment is defined by a sequence of vertical positions. It's used by an Alignment or a Road string</xs:documentation></xs:annotation></xs:element><xs:element name="RoadTemplate" type="tps:roadTemplateType"><xs:annotation><xs:documentation>A Road template is defined by a sequence of 2D segments. It's used by a Cross section</xs:documentation></xs:annotation></xs:element><xs:element name="CrossSectionSet" type="tps:crossSectionSetType"><xs:annotation><xs:documentation>A sequence of Cross sections, used by an Alignment</xs:documentation></xs:annotation></xs:element><xs:element name="RoadStringSet" type="tps:roadStringSetType"><xs:annotation><xs:documentation>A sequence of Road strings, that can be used by an Alignment instead of Cross sections</xs:documentation></xs:annotation></xs:element><xs:element name="Alignment" type="tps:alignmentType"><xs:annotation><xs:documentation>An Alignment is defined by a Horizontal alignment, a Vertical alignment and a Cross section set (or a Road string set).</xs:documentation></xs:annotation></xs:element><xs:element name="OrientationJob" type="tps:orientationJobType"><xs:annotation><xs:documentation>An Orientation job is defined as a sequence of orientation sessions and a sequence of stereo pairs (???)</xs:documentation></xs:annotation></xs:element><xs:element name="Surface" type="tps:surfaceType"><xs:annotation><xs:documentation>A Surface is defined by a collection of triangles, which refers to a sequence of positions</xs:documentation></xs:annotation></xs:element><xs:group ref="tps:observationSessionGroup"><xs:annotation><xs:documentation>A single Raw data</xs:documentation></xs:annotation></xs:group><xs:group ref="tps:objectGroup"/><xs:element name="FieldReport" type="tps:fieldReportsType"><xs:annotation><xs:documentation>A Field report is defined by its parameters (???)</xs:documentation></xs:annotation></xs:element><xs:element name="Region" type="tps:regionType"><xs:annotation><xs:documentation>A Region describes an area with some attributes</xs:documentation></xs:annotation></xs:element><xs:element name="ObjectList" type="tps:objectListType"><xs:annotation><xs:documentation>An Object List is a list of references to Objects (usually used to describe a Point List)</xs:documentation></xs:annotation></xs:element><xs:element name="PointCustomSymbol" type="tps:pointSymbolType"><xs:annotation><xs:documentation>A customized point symbol definition</xs:documentation></xs:annotation></xs:element><xs:element name="LineCustomStyle" type="tps:lineStyleType"><xs:annotation><xs:documentation>A customized line style definition</xs:documentation></xs:annotation></xs:element><xs:element name="TextureImage" type="tps:textureImageType"><xs:annotation><xs:documentation>A texture image definition</xs:documentation></xs:annotation></xs:element><xs:element name="Texture" type="tps:textureType"><xs:annotation><xs:documentation>A texture definition</xs:documentation></xs:annotation></xs:element><xs:element name="Location" type="tps:locationType"><xs:annotation><xs:documentation>A location is a set of informations about where a quantity is located</xs:documentation></xs:annotation></xs:element><xs:element name="Material" type="tps:materialType"><xs:annotation><xs:documentation>A material is a type of work or material (or cost code) of the quantity</xs:documentation></xs:annotation></xs:element><xs:element name="Quantity" type="tps:quantityType"><xs:annotation><xs:documentation>A quantity type describes the location, the material and its distribution</xs:documentation></xs:annotation></xs:element><xs:element name="Task" type="tps:taskType"><xs:annotation><xs:documentation>A task definition</xs:documentation></xs:annotation></xs:element><xs:element name="Dependency" type="tps:dependencyType"><xs:annotation><xs:documentation>A dependency type describes the relationship between two tasks: a predecessor and a successor</xs:documentation></xs:annotation></xs:element><xs:element name="BkgImage" type="tps:imageType"><xs:annotation><xs:documentation>An image used as CAD background</xs:documentation></xs:annotation></xs:element></xs:choice></xs:group>