Skip to main content

Changes in metadata files


LIDS 9.23

ComponentVersion
Metadata:131
AS:9.23
  • model.xml
    • Added optional boolean attribute 'dropTmpTables' to the 'arealTopologyAssoc' element. If set to true, the session TMP tables are dropped before each topology generation of the current user session (except the first time the topology generation is run).

LIDS 9.8

ComponentVersion
Metadata:130
AS:9.8
  • model.xml

    • Added optional boolean attribute 'preserveMasterFeature' into the master role of 'featureRefRelationAssocType' element. If set to true, all feature types in the masterRole must be versioned for history.
  • map-service.xml

    • New optional element 'backgroundColor' under element 'wms'. Moved from browser.xml, which is now deleted.

LIDS 8.25

Build 8.25.23, 2024-05-xx

ComponentVersion
Metadata:129
AS:8.25-195023
  • model.xml
    • Extended geometryFunction with 'minZ', 'maxZ' and 'length2D'.

Build 8.25.15, 2024-01-xx

ComponentVersion
Metadata:128
AS:8.25-195015
  • model.xml
    • Extended cross section query: can now contain includedGraphicTypeComponentArray containing array of includedGraphicTypeComponent.

Build 8.25.11, 2023-12-xx

ComponentVersion
Metadata:127
AS:8.25-195011
  • model.xml
    • Extended attribute rules: can now contain multiple conditions.

Build 8.25.9, 2023-10-xx

ComponentVersion
Metadata:126
AS:8.25-195009
  • model.xml

    • Added optional attribute 'unique' for codelist columns.
  • presentation.xml

    • Introduced dwg line weight mapping:
<ber:dwgLineWeights>
<ber:dwgLineWeight display="0" dwg="0.5"/>
...
<ber:dwgLineWeight display="6" dwg="5"/>
</ber:dwgLineWeights>
  • cross-section.xml
    • Introduced new cableToVirtualCable element within relationAssocArray.

Build 8.25.5, 2023-08-xx

ComponentVersion
Metadata:125
AS:8.25-195xxx
  • model.xml
    • Introduced new uniqueRule element within attributeRuleArray. This rule contains a constraint with one or more attributes defining unique combination of allowed values. The constraint can contain the optional 'ignoreNullValues' attribute to control how NULL values are handled during validation.
<ber:uniqueRule id="uc_sketch_type_identification" name="Unique sketch type and identification">
<ber:description>Unique constraint of sketch type and identification for Sketch</ber:description>
<ber:constraint ignoreNullValues="true">{at_5080001},{at_5080002}</ber:constraint>
</ber:uniqueRule>

Build 8.25.3, 2023-06-xx

ComponentVersion
Metadata:124
AS:8.25-195xxx
  • tool.xml
    • Extended initialize element of construction tool: added optional element attachment with optional attribute 'source' and optional subtag attachmentType.
<ber:initialize autoDAConstruction="true">
<ber:attachment source="camera/file">
<ber:attachmentType xlink:href="model.xml#att_1"/>
</ber:attachment>
</ber:initialize>

Build 8.23, 2023-05-xx

ComponentVersion
Metadata:124
AS:8.23-193xxx
  • tool.xml
    • Extended ribbonPageGroup element: added optional attributes 'collapsed' and 'maxRows' and optional elements description and icon.
    • Added boolean attributes 'copyRelations' and 'copyAttachments' within splitLine element of pointConstruction, e.g.:
<ber:pointConstruction>
<ber:symbolOnLine>
<ber:splitLine copyRelations="true" copyAttachments="true"/>
</ber:symbolOnLine>
</ber:pointConstruction>

LIDS 8.21

Build 8.21, 2023-02-xx

ComponentVersion
Metadata:123
AS:8.21-191xxx
  • bulk-update.xml
    • Added support for text type geometry, e.g.:
<ber:bulkUpdateDefinition nullValue="" dataFileEncoding="windows-1250" shortDateFormat="yyyyMMdd" dateFormat="" taskType="insert" decimalSeparator="," xmlns:ber="http://www.berit.com/ber">
...
<ber:geometry type="text">
<ber:x>
<ber:position>4</ber:position>
</ber:x>
<ber:y>
<ber:position>5</ber:position>
</ber:y>
<ber:text>
<ber:position>6</ber:position>
</ber:text>
</ber:geometry>
</ber:bulkUpdateDefinition>
  • cross-section.xml
    • Added new relation type cableToJoint in relationAssocArray, e.g.:
<ber:cableToJoint xlink:href="model.xml#r_cable_cabjoint"/>
  • model.xml
    • Added new optional element coordinatesScale in spatialInfo
    • It describes number of decimal places to which coordinates are rounded.
<ber:spatialInfo baseUnit="m" srs="EPSG:31467">
...
<ber:coordinatesScale>2</ber:coordinatesScale>
</ber:spatialInfo>

LIDS 8.17

Build 8.17, 2022-07-xx

ComponentVersion
Metadata:123
AS:8.17-187xxx
  • model.xml
    • Added optional attribute 'unique' for feature attribute and redefined feature attribute. If a feature attribute is set to unique="true", then a unique constraint will be created in the database. However, this value must not be redefined within one container!

LIDS 8.16

Build 8.16, 2022-07-xx

ComponentVersion
Metadata:122
AS:8.16-186xxx
  • tool.xml
    • Allowed to place separator in subToolArray element.

LIDS 8.15

Build 8.15, 2022-05-xx

ComponentVersion
Metadata:122
AS:8.15-185xxx
  • model.xml

    • Extended outputFormat element, except ":F/:f" also ":N/:n" or ":D/:d" conversion specifiers are allowed for decimal attribute.
    • Extended rule element by cascadeRollback attribute to disable feature creating with spatial relation in the case of corrupted relation rule.
  • telco.xml

    • Added new port element, new cassetteToPort and portToContact relations.

LIDS 8.13

Build 8.13, 2022-04-xx

ComponentVersion
Metadata:121
AS:8.13-183xxx
  • model.xml
    • Added optional roleFilter element to boundary and centroid role of areal topology association type. It can specify one or more featureTypes and OGC filter. The boundary or centroid role can use more roleFilter elements.
<ber:arealLayer id="lay_1" name="Area">
<ber:boundaryRole>
<ber:featureType refId="ft_5100000"/>
<ber:roleFilter><!--[0..unbounded]-->
<!--ber:featureType refId="ft_5100000"/--><!--[0..unbounded]-->
<ogc:Filter>
<ogc:PropertyIsGreaterThan>
<ogc:PropertyName>at_5100001</ogc:PropertyName>
<ogc:Literal>0</ogc:Literal>
</ogc:PropertyIsGreaterThan>
</ogc:Filter>
</ber:roleFilter>
</ber:boundaryRole>
<ber:centroidRole>
<ber:centroidItem>
<ber:featureType refId="ft_5111100"/>
<ber:faceFeatureType refId="ft_5111200"/>
</ber:centroidItem>
<ber:centroidItem>
<ber:featureType refId="ft_5112100"/>
<ber:faceFeatureType refId="ft_5112200"/>
</ber:centroidItem>
<ber:roleFilter><!--[0..unbounded]-->
<ber:featureType refId="ft_5111100"/><!--[0..unbounded]-->
<ogc:Filter>
<ogc:PropertyIsGreaterThan>
<ogc:PropertyName>at_5110004</ogc:PropertyName>
<ogc:Literal>0</ogc:Literal>
</ogc:PropertyIsGreaterThan>
</ogc:Filter>
</ber:roleFilter>
</ber:centroidRole>
...
</ber:arealLayer>

LIDS 8.11

Build 8.11, 2022-01-xx

ComponentVersion
Metadata:120
AS:8.11-181xxx
  • model.xml
    • Added optional attribute 'fallbackValue' to the relationQuery element. This value is used if the relation query returns no row (there is no related feature).
    • Added optional attributes 'subtype' and 'durationUnit' to the decimalDataType element. Subtype can be number (default) or duration. Duration unit is used for duration subtype.

LIDS 8.2

Build 8.2, 2021-03-xx

ComponentVersion
Metadata:119
AS:8.2-172xxx
  • model.xml
    • Added boolean attribute 'default' into attribute reference of the featureRef attribute definition, relevant for featureRef attributes with multiple master attributes.
    • Added optional attribute 'id' into field and caption elements of form definition, suitable for multilingual support.
    • Added optional attribute 'attributePath' into form field element that can be used to specify the path of a nested related attribute.

LIDS 8.0

Build 7.7.5, 2020-11-xx

ComponentVersion
Metadata:118
AS:7.7.5-165xxx
  • model.xml
    • changed sharedSemantics attribute of featureType element from boolean to enumeration with allowed values: false, true, single. New value single restricts a feature with shared semantics to only one instance.

LIDS 7.7.3

Build 7.7.3, 2020-09-xx

ComponentVersion
Metadata:117
AS:7.7.3-163xxx
  • model.xml
    • project may optionally define language settings for multilingual projects.
  • extdimension.xml
    • added textComponentDecimalSeparator attribute to dimensionArray element.

LIDS 7.7.1

Build 7.7.1, 2020-04-xx

ComponentVersion
Metadata:116
AS:7.7.1-161xxx
  • option.xml

    • added optional attribute legibility into daAutoConstruction element.
    • diameter element - the optional side attribute added for line border generation.
    • The line borders output extended. It can be also represented by a separate feature connected to the axis using a relation. Define it by specifying both featureType and optional relationAssoc inside the border definition.
    • The elements borderLine and closingLine can be empty for output as feature (see below).
    • If featureType and optional relationAssoc elements are defined the user can use for given featureType optional default feature attributes specified in defaultAttValueArray element.
    <ber:outputLineBorder>
    <ber:diameter side="left">
    <ogc:PropertyName>at_e5121006/ca_31903</ogc:PropertyName>
    </ber:diameter>
    <ber:featureType xlink:href="model.xml#ft_B"/>
    <ber:relationAssoc xlink:href="model.xml#rel_Y"/>
    <ber:defaultAttValueArray>
    <ber:defaultAttValue>
    <ber:attribute xlink:href="model.xml#at_5010004"/>
    <ber:currentDate/>
    </ber:defaultAttValue>
    <ber:defaultAttValue>
    <ber:attribute xlink:href="model.xml#at_5010005"/>
    <ber:value>145</ber:value>
    </ber:defaultAttValue>
    </ber:defaultAttValueArray>
    <ber:borderLine quadrantSegmentsCount="8"/>
    <!-- Optional element-->
    <ber:closingLine/>
    </ber:outputLineBorder>
  • bulkupdate.xml

    • new task deleteTask for deleting data according to a definition and data file.
  • crosssection.xml

    • Relation element ductInsideDuct supports m:n relation types and requires specification of an outer duct role.
    <ber:ductInsideDuct xlink:href="model.xml#r\_duct\_duct">
    <ber:outerRole xlink:href="model.xml#rt\_duct\_out"/>
    </ber:ductInsideDuct>

LIDS 7.6.9

Build 7.6.9, 2020-01-xx

ComponentVersion
Metadata:115
AS:7.6.9-155xxx
  • option.xml

    • CompoundDA - simple or geometry query can be defined together with a header component, e.g.:
    <ber:daQuery>
    <ber:simpleQuery>
    <ber:attributeArray>
    <ber:attribute xpath="at_e5121006/ca_31902"/>
    </ber:attributeArray>
    <ber:format>Diameter: {0} [cm]</ber:format>
    </ber:simpleQuery>
    <ber:headerComponent lineHeight="1.0">
    <ber:graphicTypeComponent xlink:href="model.xml#gtcda_01_route"/>
    </ber:headerComponent>
    <ber:compoundQuery>
    <!-- original compound query definition -->
    </ber:compoundQuery>
    ...
    </ber:daQuery>

LIDS 7.6.7

Build 7.6.7, 2019-11-xx

ComponentVersion
Metadata:114
AS:7.6.7-153xxx
  • model.xml

    • changed the syntax of the relation rule, now it looks like:
    <ber:rule id="" name="">
    <ber:condition r1.roleId="rt_point" r1.ftids="ft_P1 ft_P2">{r1.at_material} = 'GOLD'</ber:condition>
    <ber:constraint r1.roleId="rt_line" r1.ftids="ft_L1 ft_L2">{r1.at_color} = 'YELLOW'</ber:constraint>
    </ber:rule>

LIDS 7.6.6

Build 7.6.6, 2019-xx-xx

ComponentVersion
Metadata:113
AS:7.6.6-152xxx
  • model.xml
    • added new optional attribute measure into the element container and groupContainer.
    • versioned attribute of element container and groupContainer can now contain values false, history and longTransaction. Value true can still be used because of backwards compatibility and has same meaning as value history.

LIDS 7.6.5

Build 7.6.5, 2019-xx-xx

ComponentVersion
Metadata:112
AS:7.6.5-151xxx
  • model.xml
    • added new role interfaceRole that supports a relation role with feature types from different containers. In fact, it refers the interface from which all feature types implementing this interface are detected and added to this role.

LIDS 7.6.4

Build 7.6.4, 2019-09-xx

ComponentVersion
Metadata:111
AS:7.6.4-150003
  • presentation.xml
    • Element defaultValue for date type can be set to currentDate.
    • Added new optional element groupsArray in reports for classification.

LIDS 7.6.2

Build 7.6.2, 2019-06-xx

ComponentVersion
Metadata:110
AS:7.6.2.148001
  • model.xml
    • added new optional attribute preventRegeneration into the element attributeQuery of the derived or security derived attribute.

LIDS 7.6.0

Build 7.6.0, 2019-05-xx

ComponentVersion
Metadata:109
AS:7.6.0.146007
  • model.xml

    • added new relation rules for relation associations. These rules can define conditions and constraints for creating relations, e.g.:
    <ber:featureRefRelationAssoc id="r_pipe_inspection" name="Main pipeline segment --> Inspection">
    <ber:groupsArray>
    <ber:group id="inspections"/>
    </ber:groupsArray>
    <ber:masterRole refId="rt_5012100_s"/>
    <ber:childRole refId="rt_inspection_d" deleteWithMasterFeature="true"/>
    <ber:relationRuleArray>
    <ber:rule id="rc_pipe_inspection" name="Damage or pig inspection ~R~ pipe with diameter != -1">
    <ber:description>Damage or pig inspection cannot be related to pipe with Unknown diameter</ber:description>
    <ber:condition roleId="rt_inspection\_d" ftids="ft_damage ft_pig_inspection"/>
    <ber:constraint roleId="rt_5012100\_s">{at\_5012000\_diameter} != -1</ber:constraint>
    </ber:rule>
    </ber:relationRuleArray>
    </ber:featureRefRelationAssoc>
      • added new dynamic default value to feature attributes including redefined variants, e.g.:
    <ber:attribute id="at_nextCheckDate" name="Next check date" dbName="NEXT_CHECK_DATE">
    <ber:dataType>
    <ber:date/>
    </ber:dataType>
    <!-- choice of defaultValue or dynamicDeafultValue -->
    <ber:dynamicDefaultValue> <!-- default value for next check is after one week -->
    <ber:simpleQuery>
    <ber:attributeArray>
    <ber:attribute xpath="at_checkDate"/>
    </ber:attributeArray>
    <!-- choice of format or expression -->
    <ber:expression>{0} + 7</ber:expression>
    </ber:simpleQuery>
    </ber:dynamicDefaultValue>
    </ber:attribute>
    • added optional attribute readOnly into the attribute rule's constraint. A rule can look like this:

      <ber:attributeRuleArray>
      <ber:rule id="rule1" name="Reset check interval">
      <description>If Material = 10, then CHECK_INTERVAL = 0</description
      <ber:condition>{at_5012115} = 10</ber:condition>
      <ber:constraint readOnly="true" force="true">{at_5012121} = 0</ber:constraint>
      </ber:rule>
      <ber:attributeRuleArray>
  • tool.xml

    • added mandatory attribute 'id' into ribbon page and ribbon page group.
  • presentation.xml

    • new data type codeListRefExt for external references codeList and displayColumn using xlink, e.g.:
    <ber:codeListRefExt>
    <ber:codeList xlink:href="model.xml#cl_204"/>
    <ber:displayColumn xlink:href="model.xml#ca_20402"/>
    </ber:codeListRefExt>
  • browser.xml

    • new collection selectByPolygonLayers

LIDS 7.5.6

Build 7.5.6, 2019-02-xx

ComponentVersion
Metadata:108
AS:7.5.6.143003
  • option.xml
    • added new optional collection of compound displayable attributes.
  • resource.xml
    • added json format for the line style.

LIDS 7.5.4

Build 7.5.4, 2018-11-xx

ComponentVersion
Metadata:107
AS:7.5.4.141003
  • model.xml

    • added new data type binary for codelist column.
    • added optional element attributeRuleArray into feature type that contains one or more attribute rules.
  • tool.xml

    • added new optional element shapePolar to the surface construction.

LIDS 7.5.1

Build 7.5.1, 2018-07-xx

ComponentVersion
Metadata:106
AS:7.5.1.138001
  • model.xml

    • added new optional element groupsArray that contains 1 or more group elements, each group is identified by attribute id. This collection can be used within featureType, codelist or association for meta-item grouping.
    • added new optional element orderBy within relation roles that can define attributes for ordering features, e.g.:
    <ber:featureRefRelationAssoc id="r_5040000_5012100" name="Mains --> Main pipeline segment">
    <ber:masterRole refId="rt_5040000_s">
    <ber:orderBy>
    <ber:attribute refId="at_5040007" direction="ascending" position="0"/>
    </ber:orderBy>
    </ber:masterRole>
    <ber:childRole refId="rt_5012100_d"/>
    </ber:featureRefRelationAssoc>
  • tool.xml

    • added a collection of ribbon pages.

LIDS 7.5.0

Build 7.5.0, 2018-05-xx

ComponentVersion
Metadata:105
AS:7.5.0.137001
  • telco.xml
    • allowed to add a secondary color in colorSchema element.

LIDS 7.4.5

Build 7.4.5, 2018-05-xx

ComponentVersion
Metadata:105
AS:7.4.5.136001
  • model.xml

    • Added optional attribute contentType to string data type.
    • Redesigned assignedForms element - new attribute usage specifying type of assigned form.
  • tool.xml

    • Added new construction mode 'vertexMode' to the curveConstruction.

LIDS 7.4.1

Build 7.4.1 SP2 HF5, 2018-04-19

ComponentVersion
Metadata:104
AS:7.4.1.132037
  • model.xml
    • Spatial relation: added new spatial condition 'overlaps' for faceToFace interaction.

Build 7.4.1 SP2, 2017-12-20

ComponentVersion
Metadata:104
AS:7.4.1.132030
  • model.xml

    • Instead of referencing standard SRS in the model, it's possible to use a derived SRS like in the multi-crs.xml extension metadata. This means the data are stored in such derived system instead of a standard one. If used, the standard srs parameter must not be provided.
    <ber:project name="LIDSdemo" version="7.4.1">
    <ber:spatialInfo baseUnit="m"> <!- NO srs ATTRIBUTE -->
    <ber:derivedCRS id="EPSG_31467_translated" name="Gauss-Krueger zone 3 - translated">
    <ber:baseCRS refId="EPSG:31467"/>
    <ber:transform>
    <ber:translate offsetX="30" offsetY="0"/>
    <ber:rotation anchorX="3456926" anchorY="5481071">0</ber:rotation>
    <ber:scale>1</ber:scale>
    </ber:transform>
    </ber:derivedCRS>
    ...
    </ber:spatialInfo>
    </ber:project>

Build 7.4.1 SP1, 2017-07-xx

ComponentVersion
Metadata:103
AS:7.4.1.132015
Client:7.4.1.xxxx
  • model.xml

    • Added new optional element complexQuery to the attributeQuery element that is used by a derived or redefined derived attribute. It can contain a combination of simple, geometry and relation query. Because of just one derived value is expected, the format or expression must be given for the concatenation of individual results, e.g.:
    <ber:derivedAttribute id="at_complex_info" name="Complex info" dbName="COMPLEX_AT_INFO">
    <ber:dataType>
    <ber:string maxLength="120"/>
    </ber:dataType>
    <ber:attributeQuery>
    <ber:complexQuery>
    <ber:queryArray>
    <ber:simpleQuery>
    <ber:attributeArray>
    <ber:attribute xpath="at_5012104"/>
    <ber:attribute xpath="at_5012105"/>
    </ber:attributeArray>
    <ber:expression>{1} - {0}</ber:expression>
    </ber:simpleQuery>
    <ber:geometryQuery>
    <ber:geometryFunction name="length"/>
    <ber:expression>nvl({0}, 0)</ber:expression>
    </ber:geometryQuery>
    <ber:relationQuery>
    <ber:attributeArray>
    <ber:attribute xpath="at_5040007"/>
    </ber:attributeArray>
    <ber:relationAssoc refId="r_5040000_5012100"/>
    </ber:relationQuery>
    </ber:queryArray>
    <!--ber:format>Gradient: {0}, Length: {1}, Main Id: {2}</ber:format-->
    <ber:expression>'Gradient: ' || nvl2({0},'{0}','') || ', Length: {1}, Main Id: {2}'</ber:expression>
    </ber:complexQuery>
    </ber:attributeQuery>
    </ber:derivedAttribute>
  • lrs.xml

    • Added new optional elements to refer attributes derived feature types and their derived attributes in the line or surface events.
  • tool.xml

    • Added new construction mode 'parallelCurve' to the curveConstruction.

Build 7.4.1 FINAL, 2017-06-28

ComponentVersion
Metadata:102
AS:7.4.1.132013
Client:7.4.1.xxxx
  • model.xml

    • Added new system attribute featureInfo to the root feature type.
    • Added new optional element featureInfo with refId attribute to the feature type. RefId cannot be virtual attribute or feature ref attribute.
    • Added 2 new assignedForms for LIDS Mobile (mobileSimple and mobileFull).
  • crosssection.xml

    • Added the possibility to define the folder structure with components, there is new optional element <ber:componentFolderArray>
    • Added new optional element <ber:ductInDuctAssignArray> with one or more feature types containing the attribute for the automatic assigning of ducts.
  • presentation.xml

    • Added new optional attribute secured to element <ber:jasperReport> and <ber:dynamicJasperReport>.

LIDS 7.4.0

Build 7.4.0 SP2, 2016-12-20

ComponentVersion
Metadata:101
AS:7.4.0.131051
Client:7.4.0.xxxx
  • model.xml
    • Backdrop layer has an optional attribute colorModelType="rgb/rgba/greyscale/palette". If specified, only rasters having this color model may be inserted into the layer.
  • dbhint.xml
    • Extended DB hinting. A regular expression may be defined which, if present in the executed SQL query, will change the hint to the specified value.

Build 7.4.0, 2016-07-29

ComponentVersion
Metadata:101
AS:7.4.0.131017
Client:7.4.0.xxxx
  • model.xml

    • Added new optional attribute ordered to codeListBinding.
    • Added new optional attribute readOnly to codelist.
    • Added new optional attribute georeferenced to the attachment type.
    • Added new optional element <ber:featureType> with attribute refId to set a related feature type for the attachment type.
    • Added attribute 'versioned' to container, relation association and backdrop type.
    • Added new system attributes validFrom and validTo to the root feature type.
    • Added new optional element <ber:featureType> with attribute refId to set a related feature type for a backdrop type.
    • History support for backdrop hierarchies
      • Multiple hierarchical layers can be defined for the main tiled layer.
      • Each one has a date attribute representing the age of the raster data.
      • Optionally there can be one layer without the date attribute representing the hierarchy for current data.
  • presentation.xml

    • Added new optional element over1000Rows to dynamicJasperReport.
    • Added mandatory patternFill properties to default surface symbolizer.
    <ber:polygonSymbolizer>
    <ber:fill>
    <se:SvgParameter name="fill">#00FF00</se:SvgParameter>
    <se:SvgParameter name="fill-opacity">1.0</se:SvgParameter>
    <ber:fillStyle>solid</ber:fillStyle>
    </ber:fill>
    <ber:patternFill>
    <se:GraphicFill>
    <se:Graphic>
    <se:ExternalGraphic>
    <se:OnlineResource xlink:href="system.fill#none"/>
    <se:Format/>
    </se:ExternalGraphic>
    </se:Graphic>
    </se:GraphicFill>
    <se:SvgParameter name="fill">#000000</se:SvgParameter>
    <se:SvgParameter name="fill-opacity">1.0</se:SvgParameter>
    </ber:patternFill>
    ...
    </ber:polygonSymbolizer>
  • tool.xml

    • Added new optional element displayMeasure to surface and curve construction.
  • telco.xml

    • Name-value parameters added.
  • mapService.xml

    • Added optional element <ber:referenceTimeMapping> to <ber:wms> element for mapping of referenceTime attributes to feature types.

LIDS 7.3.6

Build 7.3.6 SP5, 2016-03-17

ComponentVersion
Metadata:100
AS:7.3.6-12852
Client:7.3.6.xxxx
  • telco.xml
    • Added new relation types assignmentToStartJoint and assignmentToEndJoint.

Build 7.3.6 SP1, 2015-07-31

ComponentVersion
Metadata:100
AS:7.3.6.12840
Client:7.3.6.xxxx
  • model.xml

    • Added optional element maxParallelRequests to plainLayer of backdrop type.
  • browser.xml

    • Element <ber:paintingPanel> and its children elements <ber:paintingPanelItem> with attribute id to set function in drawing window.
    <ber:paintingPanel>
    <ber:paintingPanelItem id="insert"/>
    <ber:paintingPanelItem id="modify"/>
    <ber:paintingPanelItem id="cutHole"/>
    <ber:paintingPanelItem id="deleteHole"/>
    <ber:paintingPanelItem id="delete"/>
    <ber:paintingPanelItem id="deleteSingle"/>
    </ber:paintingPanel>

Build 7.3.6 FINAL, 2015-06-11

ComponentVersion
Metadata:100
AS:7.3.6.12835
Client:7.3.6.xxxx
  • browser.xml
    • Added attribute usageLinkUrl into <ber:usageLink> element. It define reference to extern URL after click on usageLink.
    • Added Attribute opacity into <ber:layer> element.
    • Option to define units for area measurement.
    • New element mapContextCache with boolean value to configure browser map context cache.
    • New element embedit with boolean value for Browser in embedded mode.

Build 7.3.6 BETA3, 2015-05-03

ComponentVersion
Metadata:100
AS:7.3.6.12829
Client:7.3.6.xxxx
  • model.xml
    • Added the possibility to define construction parameters within the feature type definition.
  • tool.xml
    • Added new curve construction parameters.
    • Added new point construction parameter lineDistance within parameter symbolOnLine.
    • Surface construction parameter was renamed from ortogonal to orthogonal.
    • Surface construction parameter circleRadius can contain a value (type of double).
  • options.xml
    • Added optional attribute constructionDeactivated to element displayableAttribute.

LIDS 7.3.5

Build 7.3.5 SP3, 2014-04-27

ComponentVersion
Metadata:99
AS:7.3.5.12722
  • telco.xml
    • Added service assignments.

Build 7.3.5 SP2, 2015-02-20

ComponentVersion
Metadata:99
AS:7.3.5.12719
  • telco.xml
    • Some attributes can have additional attributes hideOnFrontSide and hideOnBackSide.
    • Added definition of attenuation.
    • Added definition of nodes and new relation type nodeToJoint.
    • Added services, subinterfaces and logical interfaces.

Build 7.3.5 FINAL, 2014-11-03

ComponentVersion
Metadata:99
AS:7.3.5.12710
Client:7.3.5.xxxx
  • telco.xml
    • Changed modelling of telco connection. New connection features were defined between fibres and contacts or complex splicepoints. Removed planned relations.
  • browser.xml
    • Buttons in header toolbars could be managed.

LIDS 7.3.4

Build 7.3.4 SP4, 2015-05-14

ComponentVersion
Metadata:99
AS:7.3.4.12725
Client:7.3.4.xxxx
  • browser.xml
    • New element attachments with attribute maxScaleDenominator to configure visibility of attachment data.

Build 7.3.4 SP1, 2014-06-20

ComponentVersion
Metadata:99
AS:7.3.4.12611
Client:7.3.4.xxxx
  • option.xml
    • Area borders support different types of joins and end caps.

Build 7.3.4 FINAL, 2014-05-05

ComponentVersion
Metadata:98
AS:7.3.4.12610
Client:7.3.4.xxxx
  • model.xml
    • Spatial relations support a new relation type lastToFirstVertex.
  • option.xml
    • Area borders can be represented by a separate feature connected to the axis using a relation. Define it by specifying both featureType and relationAssoc inside the border definition.
  • mapService.xml
    • You can define WMS contexts independent on LIDS Browser definition. The contexts have their own layer list and URL.

LIDS 7.3.3

Build 7.3.3 SP2, 2014-01-31

ComponentVersion
Metadata:97
AS:7.3.3.12522
Client:7.3.3.xxxx
  • option.xml
    • ignoreMasterRotation attribute of <ber:position> element in <ber:daAutoConstruction> added. It optionally defines whether X, Y DA offsets respect master feature rotation (default) or whether the master feature rotation is ignored.
  • tool.xml
    • autoDAConstruction attribute of <ber:initialize> element in <ber:stdConstructionTool> added. It optionally initializes automatic construction of displayable attributes. If not set, initialized to false.
  • mapService.xml
    • TMS levels can be defined by a list of scale denominators using element <ber:fixedScaleDenominators>.
  • crosssection.xml
    • Each type of cross-section relation has a different element name now: <ber:cableInsideRoute>, <ber:ductInsideRoute>, <ber:cableInsideDuct> and <ber:ductInsideDuct>
    • New relation type is supported: <ber:ductToDuct>
  • browser.xml
    • New boolean attribute disableOpenAll of <ber:includedLayers> element. If set to true, it isn't possible to turn on visibility of included layers with folder checkbox.

Build 7.3.3 FINAL, 2013-10-13

ComponentVersion
Metadata:96
AS:7.3.3.12508
Client:7.3.3.xxxx
  • model.xml
    • <ber:z> element in a spatial info is now used to determine if the container is 2D or 3D. For 2D containers the element must not be present.
    • <ber:backdropCategory> can be used to create backdrop type hierarchy.
  • browser.xml
    • <ber:scales> element can optionally define set of available Browser scales. If set, others scales are not available for Browser graphic display.
    • queryable attribute of <ber:layer> element disables semantic data querying for the layer.

LIDS 7.3.2

Build 7.3.2 SP4, 2013-10-03

ComponentVersion
Metadata:95
AS:7.3.2.12410
Client:7.3.2.xxxx
  • browser.xml
    • <ber:disableLayersAccessRightsChecking> boolean value of element sets if layer list is filtered with user rights on Lids Browser start.

Build 7.3.2 FINAL, 2013-05-20

ComponentVersion
Metadata:95
AS:7.3.2.12410
Client:7.3.2.xxxx
  • model.xml
    • In <relationQuery> inside element <relationAssoc> it's possible to optionally define <inputRoleId> defining the input role for relations that contain the same feature type in both roles and therefore it's not possible to determine the input role automatically. This attribute is mandatory for those "self-reference" relations and forbidden for others.
  • presentation.xml
    • New report types: jasperReport and dynamicJasperReport.
    • In <generalProperties> there is a new optional element <defaultDisplayOverlap width="xxx"> which specifies the default width of the range extent for TMS and WMS services. This value is used for all feature types unless the value is explicitly overridden for that feature type. This can be accomplished by using <displayOverlap width="xxx"> inside <ftPresentation> element. The width value is a non-negative integer chosen from a fixed set of values.
  • browser.xml
    • <ber:folder> element has mandatory id and name attributes now.
    • <ber:layer> elements were changed from <ber:layer xlink:href="model.xml#cat_1234"/> format to <ber:layer refId="cat_1234"/>. Format for setting layers changed from <ber:layer xlink:href="setting#id_1234"/> to <ber:layer refId="setdefinition_1234"/>
  • mapService.xml
    • New metadata extension.
  • siasMetadata.xml
    • Inside backdrop element there is a new optional element <maxSize width="123" height="123/>.

LIDS 7.3.1

Build 7.3.1 FINAL, 2012-10-29

ComponentVersion
Metadata:94
AS:7.3.1.12309
Client:7.3.1.xxxx
  • model.xml
    • New optional element <filterRelated> within <relationQuery> element. It's able to define an OGC filter on semantics of the related features.
    • New optional element <convertSrs> can be coupled with an existing <format> element inside geometry query or simple query. It's used to convert SRS of input coordinate parameters (either attributes or geometry functions) before the formatter processed them.

Build 7.3.1 BETA6, 2012-10-09

ComponentVersion
Metadata:94
AS:7.3.1.12305
Client:7.3.1.xxxx
  • model.xml
    • The element <form> within <formArray> element is optional. It allows to use just <assignedForms> element without needing to define <form> element.

Build 7.3.1 BETA5, 2012-09-26

ComponentVersion
Metadata:93
AS:7.3.1.12304
Client:7.3.1.xxxx
  • presentation.xml
    • Added the optional element <dynamicMasterDetailReport>. It is a new type of report.
  • browser.xml
    • Added new attributes minScaleDenominator and maxScaleDenominator to <layer> element.

LIDS 7.3.0

Build 7.3.0 SP3, 2012-07-27

ComponentVersion
Metadata:92
AS:7.3.0.12217
Client:7.3.0.xxxx
  • option.xml
    • Added graphic tag type mapping used by the ChangeFeatureType operation.
  • bulkupdate.xml
    • Added new attribute decimalSeparator.

Build 7.3.0 SP2, 2012-06-26

ComponentVersion
Metadata:91
AS:7.3.0.12214
Client:7.3.0.xxxx
  • model.xml
    • The data type featureRef can be used for the interface attribute.

Build 7.3.0 SP1, 2012-05-15

ComponentVersion
Metadata:90
AS:7.3.0.12208
Client:7.3.0.xxxx
  • model.xml

    • Added the optional element <roleFilter> to the spatial interaction. It allows to choose only required feature types (especially shared semantics graphic child) to be related automatically.
    <ber:spatialRelationAssoc id="sr_5060000\5010100" name="Service organization unit --> Pumping station" dbName="SR_5060000_5010100">
    <ber:srcRole refId="rt_5060000_s" cardinality="1"/>
    <ber:destRole refId="rt_5010100_d"/>
    <ber:interactionType>
    <ber:faceToPoint spatialCondition="intersects"/>
    <ber:roleFilter refId="rt_5060000_s">
    <ber:featureType refId="ft_5060000"/>
    </ber:roleFilter>
    </ber:interactionType>
    </ber:spatialRelationAssoc>

Build 7.3.0 SP1 BETA3, 2012-04-25

ComponentVersion
Metadata:89
AS:7.3.0.12205
Client:7.3.0.xxxx
  • model.xml

    • New security derived attribute! In metadata, new type of feature attribute can be defined for deriving a security code list value.
    <ber:securityDerivedAttribute id="at_5120006_s" name="Operation status">
    <ber:dataType>
    <ber:codeListRef refId="cl_018" displayColumn="ca\_01802"/>
    </ber:dataType>
    <ber:defaultValue>
    <ber:value>1</ber:value>
    </ber:defaultValue>
    <ber:attributeQuery>
    <ber:relationQuery>
    <ber:attributeArray>
    <ber:attribute xpath="at_5120005_s"/>
    </ber:attributeArray>
    <ber:expression>min({0})</ber:expression>
    <ber:relationAssoc refId="r_route_duct"/>
    </ber:relationQuery>
    </ber:attributeQuery>
    </ber:securityDerivedAttribute>

Of course the security attribute can be also redefined.

<ber:redefinedSecurityDerivedAttribute refId="at_5120006_s">
<ber:defaultValue>
<ber:value>0</ber:value>
</ber:defaultValue>
<ber:attributeQuery>
<ber:relationQuery>
<ber:attributeArray>
<ber:attribute xpath="at_5120006_s"/>
</ber:attributeArray>
<ber:expression>min({0})</ber:expression>
<ber:relationAssoc refId="r_route_duct"/>
</ber:relationQuery>
</ber:attributeQuery>
</ber:redefinedSecurityDerivedAttribute>

Build 7.3.0 RC1, 2012-03-27

ComponentVersion
Metadata:88
AS:7.3.0.12202
Client:7.3.0.xxxx
  • model.xml

    • Cardinality definition simplified. For all associations minCardinality is removed as useless. Consequently, maxCardinality is renamed to cardinality with possible values revised to 1 and unbounded.

    • Featureref relations introduced! Since now featureref atributes are physically stored in semantic table instead of associative table. In metadata, new type of relation featureRefRelationAssoc must be defined for each featureref attribute. It has master role and child role. Master role does not define cardinality, it must be 1 in every case.

      Note: Featureref relation dbName is optional. It is defined only for former relation upgrade. It is useless for newly created featureref relations.

    <ber:featureRefRelationAssoc id="r_5012000_5011000" name="MPS - Service Pipe" dbname="MPS_SRVPIPE">
    <ber:masterRole refId="r_mps"/>
    <ber:childRole refId="r_servicepipe" cardinality="unbounded"/>
    </ber:featureRefRelationAssoc>
    <ber:featureRefAttribute id="at_5012112" name="MPS identification" dbName="MPS\_ID">
    <ber:dataType>
    <ber:featureRef>
    <ber:attribute refId="at_5040007"/>
    <ber:featureRefRelationAssoc refId="r_5012000_5011000"/>
    </ber:featureRef>
    </ber:dataType>
    </ber:featureRefAttribute>

Build 7.3.0 BETA3, 2012-03-21

ComponentVersion
Metadata:86
AS:7.3.0.12201
Client:7.3.0.xxxx
  • crosssection.xml

    • The default delegate style for a cross section template can be optionally specified.
    <ber:routeType id="route_1" name="Route 1">
    <ber:description>Complex route type</ber:description>
    <ber:graphicType xlink:href="model.xml#gtcs_0002"/>
    <ber:templateDelegateStyleArray>
    <!-- default style for delegate component: gtcs_0002_01 -->
    <ber:delegateStyle xlink:href="thematization.xml#st_gtcs_0002_01_02"/>
    </ber:templateDelegateStyleArray>
    </ber:routeType>

LIDS 7.2.3

Build 7.2.3 SP3 BETA3, 2012-02-02

ComponentVersion
Metadata:86
AS:7.2.3.12116
Client:7.2.3.xxxx
  • model.xml

    • Optional maximum pixel size <maxSize> of returned image added to plain backdrops.
  • neplan.xml

    • Mapping of NEPLAN TYPE to LIDS semantic attribute added.

Build 7.2.3 SP2, 2012-01-12

ComponentVersion
Metadata:85
AS:7.2.3.12114
Client:7.2.3.xxxx
  • siasMetadata.xml
    • Added the optional element <excludeYesNoCodelist> containing a list of codelists that do not refer yes/no codelists.

Build 7.2.3 FINAL, 2011-10-18

ComponentVersion
Metadata:85
AS:7.2.3.12103
Client:7.2.3.xxxx
  • option.xml
    • Added the optional element <suppressedOutputStates> to tracing task. It can define a list of feature states to be suppressed in the output.

LIDS 7.2.2

Build 7.2.2 SP4 BETA2, 2011-08-23

ComponentVersion
Metadata:84
AS:7.2.2.12015
Client:7.2.2.xxxx
  • model.xml, thematization.xml
    • Added the attribute hidden to the derivedSymbolizer.

Build 7.2.2 SP2 BETA2, 2011-06-15

ComponentVersion
Metadata:83
AS:7.2.2.12010
Client:7.2.2.xxxx
  • resource.xml
    • A collection of user-defined resources specified by the element <customResourceArray> may be defined more times for various types.

Build 7.2.2 SP1 RC, 2011-05-25

ComponentVersion
Metadata:82
AS:7.2.2.12008
Client:7.2.2.xxxx
  • model.xml
    • Added restriction for virtual and featureRef attributes - attribute identifier may be at most 30 characters long.

Build 7.2.2 Beta1, 2011-03-14

ComponentVersion
Metadata:81
AS:7.2.2.12001
Client:7.2.2.xxxx
  • model.xml, option.xml

    • Added new geometry functions rotation, rotationRad and rotationGrad that can be used by derived, virtual or displayable attributes.
    <ber:virtualAttribute id="at_5010105" name="Rotation (degrees)">
    <ber:dataType>
    <ber:decimal precision="3"/>
    </ber:dataType>
    <ber:attributeQuery>
    <ber:geometryQuery>
    <ber:geometryFunction name="rotation"/>
    <ber:format>{0:F0}</ber:format>
    </ber:geometryQuery>
    </ber:attributeQuery>
    </ber:virtualAttribute>
  • model.xml, thematization.xml

    • The element <mask> of text symbolizer has been changed
  • presentation.xml

    • Added new mask properties to default text symbolizer

LIDS 7.2.1

Build 7.2.1 RC1, 2010-10-26

ComponentVersion
Metadata:79
AS:7.2.1.11909
Client:7.2.1.xxxx
  • model.xml

    • Elements defining relation role <srcRole> and <destRole> have been replaced by the element <relationRole>. The <relationRole> element can be reused more times in relation associations regardless of whether it represents source or destination role.
      There are some restrictions in relation association concerning to this change:
      - relation association must not refer the same relation roles (with the same identifier).
      - relation association must not contain relation roles with the same database name.
    • Added new metadata for generating unique values for feature attributes. There are two new metadata objects:
      - numberGenerator defines properties for the sequence numbering.
      - generatedAttribute defines a feature attribute referencing the number generator.
    <ber:model>
    ...
    <ber:system>
    ...
    </ber:system>
    <ber:numberGeneratorArray>
    <ber:numberGenerator id="seq_sernum" name="Serial number" dbName="SEQ_SER_NUMBER" startValue="1" step="1">
    <ber:description>Optional description</ber:description>
    </ber:numberGenerator>
    </ber:numberGeneratorArray>
    ...
    <ber:featureType>
    ...
    <ber:featureAttributeArray>

    <ber:generatedAttribute id="at_5011005" name="Serial number" dbName="SERIAL_NUM">
    <ber:dataType>
    <ber:string maxLength="40"/>
    </ber:dataType>
    <ber:attributeQuery>
    <ber:numberGeneratorQuery>
    <ber:numberGenerator refId="seq_sernum"/>
    <ber:format>SN_{0}</ber:format>
    </ber:numberGeneratorQuery>
    </ber:attributeQuery>
    </ber:generatedAttribute>
    ...
    </ber:featureAttributeArray>
    ...
    </ber:featureType>
    ...
    </ber:model>

Build 7.2.1 Beta5, 2010-08-31

ComponentVersion
Metadata:78
AS:7.2.1.11905
Client:7.2.1.xxxx
  • thematization.xml
    • Added new optional attribute utilizedForWMS to <theme> element. This attribute indicates whether or not the theme is utilized for WMS.

Build 7.2.1 Beta4, 2010-08-17

ComponentVersion
Metadata:77
AS:7.2.1.11904
Client:7.2.1.xxxx
  • model.xml

    • The horizontal delimiters can be added to a form using <fieldGroup> element. It can start with <separator> or <caption> element with optional attributes label and collapsible. Allowed values for collapsible attribute are: expanded|collapsed|false. Default is false.
    <ber:form id="fmd_50400" name="Water mains - default">
    <ber:fieldGroup>
    <ber:field refId="at_5040001" label="Function" readOnly="false" length="80"/>
    </ber:fieldGroup>
    <ber:fieldGroup>
    <ber:separator/>
    <ber:field refId="at_5040007" label="Identification" readOnly="false" length="40"/>
    <ber:field refId="at_5040008" label="Water variety" readOnly="false" length="80"/>
    </ber:fieldGroup>
    <ber:fieldGroup>
    <ber:caption label="Segments" collapsible="expanded"/>
    <ber:field refId="at_5040002" label="Count" readOnly="true" length="40"/>
    <ber:field refId="at_5040003" label="Total length [m]" readOnly="true" length="40"/>
    </ber:fieldGroup>
    </ber:form>

Build 7.2.1 Beta2, 2010-07-15

ComponentVersion
Metadata:76
AS:7.2.1.11902
Client:7.2.1.xxxx
  • model.xml

    • Checkboxed codelists can be defined. Attributes of this codelist type are represented as checkboxes. The codelist must contain exactly two values - refered by pkOn and pkOff parameters.
      • Security codelists can be defined as checkboxed as well.
      • Checkboxed codelists can be used as data types of codelists columns as well.
    <ber:codeList id="cl_006" name="Status" dbName="C_G_STATUS" size="small">
    <ber:description>Status</ber:description>
    <ber:checkboxed pkOn="1" pkOff="2"/>
    <ber:columnArray>
    ...
    </ber:columnArray>
    </ber:codeList>
  • bulkupdate.xml

    • SRS code of the input data can be optionally specified by the sourceSRS attribute.
    <ber:bulkUpdateDefinition xmlns:ber="http://www.berit.com/ber"
    nullValue="null" taskType="insert" sourceSRS="EPSG:4326">

Build 7.2.1 Beta1, 2010-06-30

ComponentVersion
Metadata:75
AS:7.2.1.11901
Client:7.2.1.xxxx
  • resource.xml

    • It's possible to define custom resources with the specified type.
    <ber:customResourceArray type="dimStyle">
    <ber:customResource id="ds_1" name="ft_5031000">
    <ber:formatArray>
    <ber:format name="dgn" file="dimStyles.dgn" extResId="template_5031000"/>
    </ber:formatArray>
    </ber:customResource>
    </ber:customResourceArray>
  • browser.xml (2)

    • Layer list can contain the sublayers.
    <ber:includedLayers>
    <ber:layer xlink:href="setting#id_82" visible="true"/>
    <ber:layer xlink:href="setting#id_1258"/>
    <ber:layer xlink:href="model.xml#cat_redlining_sketch">
    <ber:layer xlink:href="model.xml#cat_5070000"/>
    <ber:layer xlink:href="model.xml#cat_5080000"/>
    </ber:layer>
    <ber:layer xlink:href="model.xml#cat_5010000"/>
    <ber:layer xlink:href="model.xml#cat_5040000"/>
    <ber:layer xlink:href="model.xml#bd_02" visible="true"/>
    <ber:layer xlink:href="model.xml#bd_03"/>
    </ber:includedLayers>

LIDS 7.2.0

Build 7.2.0 SP2 RC, 2010-05-27

ComponentVersion
Metadata:74
AS:7.2.0.11813
Client:7.2.0.xxxx
  • option.xml

    • Displayable attribute - the multi line query can specify more relation associations. This also applies to displayable attributes defined in the crosssection.xml.
    <ber:multiLineQuery>
    <ber:attributeArray>
    <ber:attribute xpath="at_5010007"/>
    <ber:attribute xpath="at_5011001/ca_10502"/>
    <ber:attribute xpath="at_5011003/ca_10402"/>
    </ber:attributeArray>
    <ber:format>{0}: [{1}, {2}]</ber:format>
    <ber:relationAssoc xlink:href="model.xml#sr_5012100_5011100"/>
    <ber:relationAssoc xlink:href="model.xml#sr_5012100"/>
    <ber:lineFormat maxChars="50" maxLines="3">{0}, {1}, \\r\\n</ber:lineFormat>
    </ber:multiLineQuery>
  • crosssection.xml

    • The default cable positions can be optionally specified.

Build 7.2.0 RC2, 2010-04-12

ComponentVersion
Metadata:73
AS:7.2.0.11808
Client:7.2.0.xxxx
  • model.xml
    • Linear topology associations - added optional name and description to node type, edge type and constraint elements.
    • Removed storage type link from attachment type.

Build 7.2.0 Beta6, 2010-03-29

ComponentVersion
Metadata:72
AS:7.2.0.11806
Client:7.2.0.xxxx
  • model.xml
    • Attribute snapRadius of lineToLine spatial relation has been removed.

Build 7.2.0 Beta5, 2010-03-16

ComponentVersion
Metadata:71
AS:7.2.0.11805
Client:7.2.0.xxxx
  • model.xml

    • Added a new interaction type pointToPoint for the spatial relation.
    • Added the optional attribute outputFormat to a code list column, feature attribute, interface attribute and form field (e.g. outputFormat=":f4").
    • Removed the unused <format> element containing an input and output mask.
    • The crossSectionFunction has been extended. Now it can also contain csName or csDescription function to derive name or description of assigned cross section to a route type's attribute.
  • option.xml, presentation.xml

    • The <plotting> element has been moved from option.xml to presentation.xml.
    • Added new <lineWeights> element to the <plotting> element. It represents a collection to define the weight of printed lines:
    <ber:modelPresentation>
    ...
    <ber:plotting>
    <ber:defaultNortharrow>
    ...
    </ber:defaultNortharrow>
    <ber:lineWeights>
    <ber:lineWeight display="0" print="2" />
    <ber:lineWeight display="1" print="2.5" />
    </ber:lineWeights>
    </ber:plotting>
    </ber:modelPresentation>

Build 7.2.0 Beta3, 2010-02-16

ComponentVersion
Metadata:70
AS:7.2.0.11803
Client:7.2.0.xxxx
  • tool.xml
    • The optional parameter dynamicAnchorPoint has been moved to DAConstrTool definition.

Build 7.2.0 Beta2, 2010-02-02

ComponentVersion
Metadata:69
AS:7.2.0.11802
Client:7.2.0.xxxx
  • model.xml
    • Removed the directedLinearTopologyAssoc definition. All funtionality is covered by the linearTopologyAssoc.
    • dynamicAnchorPoint parameter can be used in the definition of text components of displayable attributes.
    • Added a new <crossSectionQuery> element for a derived attribute. It is intended for a cross section feature type and computes cable positions. The cross section query can contain one of these cross section functions:
      • freePositionsCount
      • maxPositionsCount
      • assignedPositionsCount

For example:

<ber:derivedAttribute id="at_5123406" name="Max positions" dbName="MAX_POS">
<ber:dataType>
<ber:decimal precision="5" scale="0"/>
</ber:dataType>
<ber:attributeQuery>
<ber:crossSectionQuery>
<ber:crossSectionFunction name="maxPositionsCount"/>
</ber:crossSectionQuery>
</ber:attributeQuery>
</ber:derivedAttribute>

Build 7.2.0 Beta1, 2010-01-19

ComponentVersion
Metadata:68
AS:7.2.0.11801
Client:7.2.0.xxxx
  • model.xml
    • Removed attribute secId from feature type.

LIDS 7.1.6

Build 7.1.6 SP4, 2010-02-10

ComponentVersion
Metadata:67
AS:7.1.6.11724
Client:7.1.6.xxxx
  • option.xml
    • Added login and password for connection to external server.
  • tool.xml
    • The element symbolOnLine inside pointConstruction parameters can be empty.

Build 7.1.6 SP1, 2009-10-30

ComponentVersion
Metadata:66
AS:7.1.6.11712
Client:7.1.6.xxxx
  • tool.xml
    • New optional element initialize, inside stdConstrTool, extConstrTool elements. It can define an initial state of the construction tool dialog.

Build 7.1.6 RC2, 2009-09-23

ComponentVersion
Metadata:65
AS:7.1.6.11706
Client:7.1.6.xxxx
  • presentation.xml
    • New optional element generalProperties, that can contain emptyTextLabel element, which defines the text string in case that text geometry is empty.
    • In linear topology definition the element edgeType supports attribute value systemNode="inner".

Build 7.1.6 RC1, 2009-09-16

ComponentVersion
Metadata:64
AS:7.1.6.11705
Client:7.1.6.xxxx
  • model.xml

    • Added new spatial conditions for lineToLine relation. In addition, it can contain intersects or commonVertex value.
  • model.xml, thematization.xml

    • Vector rules <ber:vectorRule> can be defined as part of <ber:vectorBackdropStyle>. They are the heart of vector backdrop dynamic symbology.
    • <ber:simpleVectorSymbolizer> can optionally define color. When used in static symbology (model.xml), it is the color common to the whole backdrop type. In dynamic symbology (thematization.xml), it behaves as a header for particular elements symbolizers.

Build 7.1.6 Beta4, 2009-09-09

ComponentVersion
Metadata:63
AS:7.1.6.11704
Client:7.1.6.xxxx
  • model.xml, thematization.xml

    • Polygon symbolizer: Changed <se:Fill> element to <ber:fill>. Added <ber:patternFill> element for fill style definition.
  • resource.xml

    • Pattern fill styles (hatch, cross-hatch and symbol patterns) can be registered as project resources in <ber:fillStyleArray>.

Build 7.1.6 Beta3, 2009-08-31

ComponentVersion
Metadata:62
AS:7.1.6.11703
Client:7.1.6.xxxx
  • thematization.xml
    • The file may contain new element <ber:delegateStyleArray> that is used to define thematization styles for graphic tag component delegates.
    • The feature style may contain <ber:delegateStyle> element containing a reference to the corresponding component delegate style.

Build 7.1.6 Beta2, 2009-08-19

ComponentVersion
Metadata:61
AS:7.1.6.11702
Client:7.1.6.xxxx
  • thematization.xml
    • Elements <se:Recode>, <se:MapItem> and <se:Data> have been replaced by elements <ber:recode>, <ber:mapItem> and <ber:data>. This new definition allows to define a condition with a string value for the combined classification.

Build 7.1.6 Beta1, 2009-08-11

ComponentVersion
Metadata:60
AS:7.1.6.11701
Client:7.1.6.xxxx
  • model.xml
    • the attribute spatialCondition of a lineToPoint relation has been extended. In addition, it can contain firstVertex or lastVertex value.
    • outputAreaBorder in areaBorder element can contain graphicTagType reference instead of featureType reference.
    • Changed meaning of excludeFeatures filter in border definition. Features accepted by the filter are now completely ignored by border generator. Features that must not have any borders are defined by deleteBorderForFeatures filter now. If they have any, it is removed by border generator.


LIDS 7.1.5

Build 7.1.5 SP4 Beta2, 2009-06-02

ComponentVersion
Metadata:59
AS:7.1.5.11621
Client:7.1.5.xxxx
  • option.xml

    • added new optional element <orderBy> for multi line query of displayable attribute. It gives possibility to specify ordering for multi line query data, e.g.:
    <ber:multiLineQuery>
    <ber:attributeArray>
    <ber:attribute xpath="at_5010007"/>
    <ber:attribute xpath="at_5011101/ca_10602"/>
    </ber:attributeArray>
    <ber:format>{0} - {1}</ber:format>
    <ber:relationAssoc xlink:href="model.xml#sr_5012100_5011100"/>
    <ber:orderBy>
    <ber:attribute xpath="at_5011101/ca_10602" direction="ascending"/>
    </ber:orderBy>
    <ber:lineFormat maxChars="50" maxLines="3">{0}, {1},</ber:lineFormat>
    </ber:multiLineQuery>

Build 7.1.5 SP3, 2009-04-16

ComponentVersion
Metadata:58
AS:7.1.5.11616
Client:7.1.5.xxxx
  • model.xml
    • added new backdrop formats: bmp, gif and shp.

Build 7.1.5 SP2, 2009-04-01

ComponentVersion
Metadata:57
AS:7.1.5.11615
Client:7.1.5.xxxx
  • option.xml
    • only one of limits (maxLength, maxSteps) is allowed for stopping of tracing task.

Build 7.1.5 SP1, 2009-03-10

ComponentVersion
Metadata:56
AS:7.1.5.11612
Client:7.1.5.xxxx
  • option.xml

    • end of line (endPoint) added as a possible lengthwise line master point for automatic DA construction.
  • tool.xml

    • DA construction tool parameter 'DistanceLock' was changed to xsd:double.

Build 7.1.5 Final, 2009-02-16

ComponentVersion
Metadata:54
AS:7.1.5.11611
Client:7.1.5.xxxx
  • option.xml
    • for tracing task has been added optional element <maxLength> representing maximal length of tracing path.

Build 7.1.5 RC3, 2009-02-09

ComponentVersion
Metadata:53
AS:7.1.5.11610
Client:7.1.5.xxxx
  • model.xml

    • value of attribute dbName is restricted to pattern [A-Z0-9_\-]+
  • thematization.xml

    • filter definition of interval classification has been changed. The first interval must be defined with OGC comparison operator PropertyIsLessThanOrEqualTo and last interval with PropertyIsGreaterThan.

Build 7.1.5 RC1, 2009-01-26

ComponentVersion
Metadata:52
AS:7.1.5.11608
Client:7.1.5.xxxx
  • option.xml
    • element <autoDAConstruction> was renamed to <daAutoConstruction>.
    • added new optional output feature type filter <outputFeatureTypeFilter> for topology tracing task.

Build 7.1.5 Beta5, 2009-01-08

ComponentVersion
Metadata:51
AS:7.1.5.11605
Client:7.1.5.xxxx
  • presentation.xml

    • elements <symbolFontClipping> and <clipSymbol> were renamed to <symbolMasking> and <mask>.
  • option.xml

    • element <defaultPosition> was definitely removed.
  • thematization.xml

    • new element <directLookup> can be defined within a combined rule. It allows to take a symbology property value direct from the given feature attribute.
  • model.xml, thematization.xml

    • added possibility to define symbol/text masking for point/text symbolizers.

Build 7.1.5 Beta4, 2008-12-16

ComponentVersion
Metadata:50
AS:7.1.5.11604
Client:7.1.5.xxxx
  • presentation.xml

    • added new optional collection symbolFontClipping. It contains one or more symbol fonts with clip symbols.
  • option.xml

    • added new element <autoDAConstruction>. It replaces element <defaultPosition>.

Build 7.1.5 Beta2, 2008-11-18

ComponentVersion
Metadata:49
AS:7.1.5.11602
Client:7.1.5.xxxx
  • option.xml

    • added new part for plotting definitions: plotting. Currently contains only default northarrow symbolizer: defaultNortharrow.
  • thematization.xml

    • added new backdrop styles: vectorBackdropStyle, rasterBackdropStyle and binaryRasterBackdropStyle. These backdrop styles can specify one or more scale only rules defining visible or invisible scale range and they can also contain corresponding symbolizer.

Build 7.1.5 Beta1, 2008-11-03

ComponentVersion
Metadata:48
AS:7.1.5.11601
Client:7.1.5.xxxx
  • model.xml, presentation.xml
    • added new symbolizers: rasterSymbolizer and simpleVectorSymbolizer. They are also defined as default symbolizers in the presentation.xml.


LIDS 7.1.4

Build 7.1.4 Final, 2008-09-22

ComponentVersion
Metadata:47
AS:7.1.4.11513
Client:7.1.4.xxxx
  • model.xml
    • decimal data type: maximum precision (total number of digits) is 28.

Build 7.1.4 RC4, 2008-09-17

ComponentVersion
Metadata:46
AS:7.1.4.11512
Client:7.1.4.xxxx
  • model.xml

    • the element <defaultProperties> within textGraphicType has been renamed to <defaultTextProperties>. It can contain a rotation and anchorPoint definition.
    • new element <defaultPointProperties> with a rotation can be defined for pointGraphicType.
  • tool.xml

    • particular graphicParams elements within <stdConstrTool> element have been replaced by construction and defaultProperties elements.

E.g. for a point construction tool:

<ber:stdConstrTool id="ti\_5020000p" name="Free text 2 (ft\_5020000)">
<ber:description>Left-bottom + angle 90</ber:description>
<ber:icon xlink:href="resource.xml#ic_5020000p"/>
<ber:featureType xlink:href="model.xml#ft_5020000"/>
<ber:defaultAttValueArray>
<ber:defaultAttValue>
<ber:attribute xlink:href="model.xml#at_5033"/>
<ber:value>22</ber:value>
</ber:defaultAttValue>
</ber:defaultAttValueArray>
<ber:defaultTextProperties>
<ber:rotation>90</ber:rotation>
<ber:anchorPoint>left-bottom</ber:anchorPoint>
</ber:defaultTextProperties>
<ber:textConstruction>
<ber:adjustAngle/>
<ber:storeAngle/>
</ber:textConstruction>
</ber:stdConstrTool>

Build 7.1.4 Beta6, 2008-08-22

ComponentVersion
Metadata:45
AS:7.1.4.11508
Client:7.1.4.xxxx
  • model.xml
    • a new optional attribute drawPriority can be specified within <graphicTagType> element. It determines drawing order of graphic elements. A graphic tag with negative draw priority will be rendered before a master graphics.

Build 7.1.4 Beta5, 2008-08-11

ComponentVersion
Metadata:44
AS:7.1.4.11507
Client:7.1.4.xxxx
  • model.xml

    • added new binary raster backdrop type which can use a symbology.
    • added new feature attribute featureRefAttribute with the data type featureRef representing a relationship to a master feature (formerly known as feature code list - like reference).
  • model.xml, presentation.xml, thematization.xml

    • added new symbolizer binaryRasterSymbolizer. It must be also defined as default symbolizer in the presentation.xml.

Build 7.1.4 Beta4, 2008-07-25

ComponentVersion
Metadata:43
AS:7.1.4.11506
Client:7.1.4.xxxx
  • model.xml, presentation.xml, thematization.xml

    • textSymbolizer: added new parameter lineSpacing.
  • model.xml

    • added new form type plotReport that can be used within <assignedForms> element.

Build 7.1.4 Beta3, 2008-07-14

ComponentVersion
Metadata:42
AS:7.1.4.11505
Client:7.1.4.xxxx
  • model.xml, presentation.xml, thematization.xml
    • se:LineSymbolizer has been replaced by ber:lineSymbolizer.
    • se:PolygonSymbolizer has been replaced by ber:polygonSymbolizer.
    • optional attribute "hidden" was added to all symbolizers.

Build 7.1.4 Beta2, 2008-06-30

ComponentVersion
Metadata:41
AS:7.1.4.11503
Client:7.1.4.xxxx
  • model.xml, presentation.xml, thematization.xml

    • textSymbolizer: the justification (anchorPoint) defined within <LabelPlacement> element has been removed with no replacement.
    • pointSymbolizer: the justification (anchorPoint) defined within <PointPlacement> element has been removed. Now it can be defined as part of <OnlineResource> element with text value, e.g.: .
  • model.xml

    • textGraphicType, derivedTextGraphicType: added optional default justification.
  • tool.xml

    • a text justification parameter (anchorPoint) can be specified within the construction tool.

Build 7.1.4 Beta1, 2008-06-17

ComponentVersion
Metadata:40
AS:7.1.4.11502
Client:7.1.4.xxxx
  • model.xml

    • the <defaultAttValueArray> element has been removed. The default value of a feature attribute can be defined within the feature attribute or redefined attribute definition.
    • the redefined attribute definition has been extended. Now it can contain either standard or derived redefining attribute. The following attribute properties can be redefined:
      • nillable value
      • default value
      • forbidden operations
      • code list data type
      • derived attribute query
    • the <backdropType> element has been redesigned. The actual <backdropType> element is replaced either <rasterBackdropType> or <vectorBackdropType> element with one or more <layer> elements. E.g.:
    <ber:rasterBackdropType id="bd_02" name="Orthophoto">
    <ber:description>Hierarchical raster</ber:description>
    <ber:layerArray>
    <ber:mainTiledLayer id="lay_bd_02_tiff" name="TIFF orthophoto layer" format="tiff">
    <ber:hierachicalLayer id="lay_bd_02_jpeg" name="Hierarchy JPEG orthophoto layer" format="jpeg">
    <ber:hierarchy decreaseRatio="3" tileWidth="1000" tileHeight="1000" />
    </ber:hierarchicalLayer>
    </ber:mainTiledLayer>
    <ber:tiledLayer id="lay_bd_02_cit" name="CIT orthophoto layer" format="cit" />
    <ber:tiledLayer id="lay_bd_02_cot" name="COT orthophoto layer" format="cot" />
    </ber:layerArray>
    </ber:rasterBackdropType>

LIDS 7.1.3

Build 7.1.3 RC1, 2008-05-14

ComponentVersion
Metadata:39
AS:7.1.3.11403
Client:7.1.3.xxxx
  • model.xml

    • nodeRole, edgeRole of linearTopologyAssoc and directedLinearTopologyAssoc now must contain id, name XML attributes
    • edgeRole linearTopologyAssoc and directedLinearTopologyAssoc now can contain se:LineSymbolizer
    • nodeRole linearTopologyAssoc and directedLinearTopologyAssoc now can contain ber:pointSymbolizer
    • linearTopoConnection now can contain se:LineSymbolizer
  • option.xml

    • Structure of the ber:lineBorder element was redesigned.
    • Value of quadrantSegmentsCount attribute may be 0. This means the border will have pointed ("mitre") bends.


Build 7.1.3 Beta3, 2008-04-30

ComponentVersion
Metadata:38
AS:7.1.3.11402
Client:7.1.3.xxxx
  • model.xml
    • Support for feature type delegate.

Build 7.1.3 Beta2, 2008-04-17

ComponentVersion
Metadata:37
AS:7.1.3.11401
Client:7.1.3.xxxx
  • model.xml
    • The definition of the <query> element within derived and virtual attributes was redesigned. The query definition refers some properties (feature attributes or geometry functions) and can contain format mask (for simple formatting) or expression (specifies SQL group function or arithmetic expression for additional calculation). The virtual or derived attribute can contain one of following query definition:
      • simple (refers one or more feature attributes)
      • geometry (refers one or more geometry functions)
      • relation (refers either one or more feature attributes or an expression with a group function and specifies the relation association)

Examples:

<!-- Geometry query with two geometry function and format mask -->
<ber:geometryQuery>
<ber:geometryFunction name="firstVertexX"/>
<ber:geometryFunction name="firstVertexY"/>
<ber:format>X: {0:F2}, Y: {1:F2}</ber:format>
</ber:geometryQuery>

<!-- Simple semantic query with subtract function -->
<ber:simpleQuery>
<ber:attributeArray>
<ber:attribute xpath="at_start_z"/> <!-- First line vertex Z value -->
<ber:attribute xpath="at_end_z"/> <!-- Last line vertex Z value -->
</ber:attributeArray>
<!-- Using SQL Expression -->
<ber:expression>{1} – {0}</ber:expression>
</ber:simpleQuery>

<!-- Relation query with group function -->
<ber:relationQuery>
<ber:expression>count(*)</ber:expression>
<ber:relationAssoc refId="as_1"/>
</ber:relationQuery>

<!-- Relation query with three attributes and format mask -->
<ber:relationQuery>
<ber:attributeArray>
<ber:attribute xpath="at_1/ca_2"/>
<ber:attribute xpath="at_2"/>
<ber:attribute xpath="at_3/ca_4"/>
</ber:attributeArray>
<ber:format>{0}mm {1:F2}m {2}</ber:format>
<ber:relationAssoc refId="as_1"/>
</ber:relationQuery>
    • Support feature types with derived text graphics - there is new graphic type derivedTextGraphicType. It contains <deriveQuery> element which specifies simple or geometry query.
  • option.xml

    • The definition of a <query> element for displayable attributes was redesigned. It can contains simple or geometry query and it can also contain multiline query, e.g.:
    <ber:daQuery>
    <ber:simpleQuery>
    <ber:attributeArray>
    <ber:attribute xpath="at_11" />
    </ber:attributeArray>
    <ber:format>{0}: </ber:format>
    </ber:simpleQuery>
    <ber:multiLineQuery>
    <ber:attributeArray>
    <ber:attribute xpath="at_21" />
    <ber:attribute xpath="at_22/ca_2" />
    </ber:attributeArray>
    <ber:format>{0} - {1}</ber:format>
    <ber:relationAssoc xlink:href="model.xml#as_123"/>
    <ber:lineFormat maxChars="50" maxLines="3">{0}, {1}, \r\n</ber:lineFormat>
    </ber:multiLineQuery>
    </ber:daQuery>

Build 7.1.3 Beta1, 2008-04-02

ComponentVersion
Metadata:36
AS:7.1.2.11400
Client:7.1.2.xxxx
  • model.xml
    • new interaction types (faceToPoint, faceToLine and faceToFace) can be defined for <spatialRelationAssoc> element. The interaction has to contain attribute "spatialCondition" defining a spatial relationship (e.g. intersects, touches, contains).
    • current interaction types have been consolidated:
      • linePointToPoint, lineEndPointToPoint and lineInnerPointToPoint to lineToPoint interaction, it has to also contain spatialCondition attribute with one of values: allVertices|endVertices|innerVertices.
      • parallelLines, partialParallelLines and fullParallelLines to lineToLine interaction with spatialCondition: parallel|partialParallel|fullParallel.

LIDS 7.1.2

There is a transformation tool available for upgrading 7.1.1 metadata to version 7.1.2. See the readme for more information.

Build 7.1.2 SP5, 2008-03-05

ComponentVersion
Metadata:35
AS:7.1.2.11313
Client:7.1.2.2962
  • thematization.xml
    • the element <value> has new optional attribute name. It can define human readable name for condition in combined classification.

Build 7.1.2 SP3, 2008-02-08

ComponentVersion
Metadata:34
AS:7.1.2.11311
Client:7.1.2.2962
  • model.xml
    • the element <srcRole> within <relationAssoc> element can contain boolean attribute deleteWithDestFeature.
    • the element <destRole> within <relationAssoc> element can contain boolean attribute deleteWithSrcFeature.

These attributes identify whether or not the related feature(s) in source/destination role will be deleted during destination/source feature deletion.


Build 7.1.2 Final, 2008-01-15

ComponentVersion
Metadata:33
AS:7.1.2.11309
Client:7.1.2.2937
  • model.xml

    • graphic tag definition (<graphicType> element) can also define symbology with derivedSymbolizer.
    • the <featureType> element can contain one or more <redefinedDerivedAttribute> elements. This element allows to redefine a feature attribute of a parent feature type.
    • the new <sharedSemanticsGeometryFunction> element can be defined for a derived or virtual feature attribute. It allows to define the geometry function for a semantic parent of feature type with the shared semantics. The subelement <graphicChild> refers child feature type containing graphics.
  • option.xml

    • the new optional attribute quadrantSegmentsCount of <bufferZone> element specifies number of quadrant segments used to approximate quarter-circle, default value = 1.

Build 7.1.2 RC3.5, 2008-01-09

ComponentVersion
Metadata:32
AS:7.1.2.11308
Client:7.1.2.2930 RC3.5
  • A specification replacement

the specification StyledLayerDescriptor has been replaced by SymbologyEncoding specification. It caused these changes in metadata files (model.xml, thematization.xml and presentation.xml):

    • namespace declaration xmlns:sld="http://www.opengis.net/sld" has been replaced by xmlns:se="http://www.opengis.net/se".
      • namespace prefix <sld:xxx> has been replaced by <se:xxx>.
      • <CssParameter> element has been changed to <SvgParameter>.
      • <ogc:FeatureId> element has been replaced by <ber:featureId> element (presentation.xml).

Build 7.1.2 RC1, 2007-12-07

ComponentVersion
Metadata:31
AS:7.1.2.11304
Client:XXXX
  • model.xml

    • the <rootFeatureType> element has a new system attribute with id symbologyTokens.
    • the <graphicTypeClass> with id DA has been added.
    • the displayable attributes are defined in a new project file option.xml.
    • new data type <ber:shortDate /> was introduced. This data type defines only date without hour, minute and second part.
  • thematization.xml

    • new element <combinedRule> can be used to define combined semantic classification
    • the <daDerivedSymbolizer> element has been renamed to <derivedSymbolizer> and its sld:Geometry/ogc:PropertyName subelement contains a reference to the graphic tag.
    • the <daSymbolizer> element has been renamed to <textSymbolizer> and its sld:Geometry/ogc:PropertyName subelement contains a reference to the graphic tag.
    • the <ftStyleRefs> subelement of the <theme> element has been renamed to <featureTypeStyleArray> which contains <featureTypeStyle> elements instead of <ftStyle>.
    • the <ftStyleArray> element has been renamed to <featureTypeStyleArray>.
    • the <featureTypeStyle>, <staticRule>, <scaleOnlyRule>, <intervalRule>, <discreteRule> and <theme> elements have new attributes id (required), name (optional) and subelement <description> (optional) instead of elements <sld:Name>, <sld:Title> and <sld:Abstract>. These elements have been removed.
    • the attribute id of the rule elements must be unique within the whole thematization.xml metadata file.
  • tool.xml

    • the <daAssoc> element has been renamed to <displayableAttribute> and its attribute xlink:href contains a reference to the displayable attribute.
  • topology.xml (removed)

    • its content has been moved into a new project file option.xml.
  • option.xml (added)

    • The new optional project file. It may contain following elements:
      • <featureCopyArray> - the definitions for copying the features in the client application
      • <borderDeriveArray> - the definitions of the border derives
      • <displayableAttributeArray> - the definitions of the displayable attributes
      • <topoTracingArray> - moved from topology.xml file.

Build 7.1.2 Beta4, 2007-11-27

ComponentVersion
Metadata:30
AS:7.1.2.11302
Client:XXXX
  • model.xml
    • the element <graphicTagType> and its enclosed array element defining subordinate graphics (within the <model> element) has been renamed to <graphicType>.
    • the <graphicTagType> element of a feature type has been redefined.
    • the elements <daRole> and <daAssoc> have been removed. Displayable attributes are now defined in the separate file displayableAttributes.xml.

Build 7.1.2 Beta3, 2007-11-13

ComponentVersion
Metadata:29
AS:7.1.2.11301
Client:XXXX
  • model.xml

    • a new collection of <graphicTagType> elements can be defined within the <model> element before featureType collection. It represents a subordinate graphics of feature types (e.g. DA, CrossSection, ...). It contains the identifier, name, description (optionally), a reference to the graphic type class and the collectionGraphicType definition.
    • each feature type can define one or more references to graphicTagType.
    • the new mandatory attribute "folderName" in the <backdropType> element specifies the folder for storing the backdrop files. The value is a simple name (not a path!) and folder with this name will be situated directly in the root backdrop directory specified by the LIDS AS configuration.
  • thematization.xml

    • there were slight changes concerning a definition of symbolizers within <rule> element.

LIDS 7.1.1

There is a transformation tool available for upgrading 7.1.0 metadata to version 7.1.1. See the readme for more information.

Build 7.1.1 RC2, 2007-09-17

ComponentVersion
Metadata:28
AS:7.1.1.11205
Client:XXXX
  • model.xml

    • a new collection of <graphicTypeClass> elements can be defined in the <system> element. It represents identifier and name of a graphic extension (e.g. ExtDimension, DA, CrossSection, ...) and it can contain description. This information can be used by an application extension.
    • the attribute "class" in the <masterGraphics> element has been replaced by the element <class refId="ExtDimension"/>. It refers graphic type class identifier.
    • the element <topologyAssoc> has been renamed to the linearTopologyAssoc and the element <directedTopologyAssoc> has been renamed to the directedLinearTopologyAssoc, the attribute "type" has been removed.
    • a collection of <topoAnalysis> elements has been removed from linear associations. Now, it can be defined in a new topology.xml metadata file.
    • the element <computedField> within the <form> element has been temporarily removed.
  • topology.xml
    a new metadata file defines topology tracing tasks


Build 7.1.1 Beta1, 2007-08-16

ComponentVersion
Metadata:27
AS:7.1.1.11201
Client:XXXX
  • model.xml
    • the new <rootFeatureType> element has to be defined within the <featureTypeArray> element. The <rootFeatureType> has to be abstract, the attribute "secId" has to equal 5000002 and it has to contain all system attributes. It can also contain forms.
    • the <geometry> element defined within the <featureType> element has been replaced by new <masterGraphics> element and the <symbology> element has been moved to this <masterGraphics>. The <masterGraphics> element has to contain one of primitive graphic type (point, text, curve or surface) or one collection graphic type. More information is available in the analytic document AdvancedGraphics.

LIDS 7.1.0

Build 7.1.0 FCS, 2007-07-30

ComponentVersion
Metadata:26
AS:7.1.0.11103
Client:XXXX
  • model.xml
    • the <column> element used within <codeList> element can define "display" attribute. It will be used by Code list Maintenance tool.
    • the new "next" attribute within <defaultAttValue> element can define integer value which will be incremented/decremented to/from the entered value of the last inserted feature for the specified feature attribute.

LIDS 7.0.6

There is a transformation tool available for upgrading 7.0.5 metadata to version 7.0.6. See the readme for more information.

Build 7.0.6 SP1, 2007-06-07

ComponentVersion
Metadata:25
AS:7.0.6.11009
Client:XXXX
  • model.xml
    • the attribute "secId" within the <featureType> element has been restricted: the value of this attribute must be positive number in range <5001000,5999999> and must be unique.
    • the value of "secId" attribute for the root feature type has to equal 5000002.

Build 7.0.6 RC3, 2007-05-21

ComponentVersion
Metadata:24
AS:7.0.6.11006
Client:XXXX
  • model.xml
    • added unique constraint on the dbName attribute in container element.
    • added unique constraint on the dbName attribute in groupContainer element.
    • position attribute in the orderBy element of code list column is mandatory.

Build 7.0.6 RC1, 2007-04-30

ComponentVersion
Metadata:23
AS:7.0.6.11004
Client:XXXX
  • model.xml
    • interactionTypes element renamed to interactionType. It must contain exactly one element of lineEndPointToPoint, lineInnerPointToPoint, linePointToPoint, partialParallelLines, fullParallelLines, parallelLines

LIDS 7.0.5

There is a transformation tool available for upgrading 7.0.4 metadata to version 7.0.5. See the readme for more information.

Build 7.0.5 SP3, 2007-03-09

ComponentVersion
Metadata:22
AS:7.0.5.10910
Client:2621
  • model.xml
    • geometry type special has been temporarily restored, but it is deprecated and will be removed.

Build 7.0.5 SP2, 2007-03-06

ComponentVersion
Metadata:22
AS:7.0.5.10909
Client:2621
  • model.xml
    • geometryFunction element: the attribute name of element geometryFunction can contain following functions: length, area, centroidX, centroidY, firstVertexX, firstVertexY, firstVertexZ, lastVertexX, lastVertexY, lastVertexZ.
    • feature geometry type special: this type has been removed because it has been replaced by type dimension.

Build 7.0.5 RC2, 2007-02-12

ComponentVersion
Metadata:21
AS:7.0.5.10905
Client:2599
  • model.xml

    • baseUnit attribute: the value of this attribute defined within spatialInfo element is restricted to one of: 'm', 'cm' or 'mm'.
    • pointSymbolizer: the element LabelPlacement has been replaced by PointPlacement element; the new symbolHeight element must be defined to specify the height of a symbol in project units.
    • format element: a format can contain output and/or input mask. It can be used within feature attributes and form fields. A format with output mask only can be used for computed fields and for DA associations.
    • computedField element: the attribute expression has been removed; the new elements fieldQuery and format can be defined.
  • presentation.xml

    • defaultSymbology: The element defaultSymbology containing four symbolizers (line, polygon, point and text) must be defined within a root element.
    • ftPresentation: The format element with outputMask can be used within featureInfo element. Former outputMask attribute has been removed.
  • tool.xml

    • tool and toolBox: the icon element used for a tool or toolbox definition now contains an external reference to the icon defined in the resource.xml file.
    • construction tool: featureType or attribute element used in construction tool has to specify an external reference to the featureType or feature attribute defined in the model.xml file.
    • DA construction tool: the assocType element now contains an external reference to the assocType defined in the model.xml file.

Build 7.0.5 RC1, 2007-02-05

ComponentVersion
Metadata:20
AS:7.0.5.10903
Client:2592
  • model.xml
    • attachments: A new collection of attachments can be defined within model. The attachment contains id, name, storage type and secured flag. Each feature type can define one or more references to attachment. More information is available in the analytic document Attachments.
    • project element: A new project element defines project name and it contains <spatialInfo> element. In addition it can contain project version and description.
    • system element: A new system element specifies system id and contains former <version> element.
    • deprecated attributes and elements nextMetaItemId, displayOrder, rule have been removed.

Build 7.0.5 Beta3, 2007-01-29

ComponentVersion
Metadata:19
AS:7.0.4.10804
Client:2435
  • model.xml
    • attribute name for any meta item has to contain at least 1 character
    • attribute label within <computedField> element is now mandatory
    • filtered codelists: A new collection of filtered codelists can be defined. The filtered codelist contains id and name. It also specifies the Ogc filter and refers codelist to be filtered. The filtered codelist must not refer the security or another filtered codelist. More information is available in the analytic document Filtered codelists.

Build 7.0.5 Beta1, 2007-01-16

ComponentVersion
Metadata:18
AS:7.0.4.10804
Client:2435
  • model.xml
    • new optional attribute length can be defined within <computedField> element
    • attribute dbName within <interfaceAttribute> element is now optional (it is used for integration with TOMS)

In addition, only marginal changes have been done concerning setting some items as deprecated. These deprecated items are now optional and they will be removed in the next version:

    • nextMetaItemId element
      • displayOrder attribute within <backdropType> element
      • rule element within <daAssocType> element
  • resource.xml

    • extResId attribute has been added to the <format> element. It is optional attribut and it can identify an external resource

LIDS 7.0.4

Build 7.0.4 Final, 2006-12-12

ComponentVersion
Metadata:17
AS:7.0.4.10804
Client:2435

no changes


Build 7.0.4 RC2, 2006-12-05

ComponentVersion
Metadata:17
AS:7.0.4.10803
Client:2435
  • model.xml
    • dimension: The existing geometric types (point, curve, surface, text and special) have been extended to support the dimension.
    • spatial info: The <spatialInfo> element within <container> element is optional now.

Build 7.0.4 RC1, 2006-11-27

ComponentVersion
Metadata:16
AS:7.0.4.10802
Client:2435
  • model.xml

    • data types: New constraints (facets) can be defined for data types. For example: min/maxInclusive or min/MaxExclusive for decimal, min/maxLength for string and min/MaxValue for date data type. More information is available in the analytic document FeatureAttributeValidation.
  • resource.xml

    • lineStyle, symbolFont, icon: New resources can be defined in the file resource.xml. Each resource contains id, name and list of formats. See schema file modelResource.xsd for more information.

Build 7.0.4 Beta2, 2006-11-13

ComponentVersion
Metadata:15
AS:7.0.4.10801
Client:2435
  • model.xml
    • codelist bindings: A new collection of codelist bindings can be defined. The codelist binding contains a database name of binding table and 2 or more bounded codelists with a database name representing a column in the binding table. More information is available in the analytic document Bounded codelists.
    • bounded attributes: The bounded attributes can be defined inside a feature type. Each definition of bounded attributes specifies which codelist binding listed feature attributes are defined for. These bounded feature attributes are inheritable and they must not be redefined.

Build 7.0.4 Beta1, 2006-11-07

  • resource.xml

The new metadata file resource.xml can be stored on the AS. This file (same as other metadata files) is included in a response of DescribeProject service.


LIDS 7.0.3

Build 7.0.3 SP2, 2006-10-23

no changes

Build 7.0.3 SP1, 2006-10-19

no changes

Build 7.0.3 FINAL, 2006-10-11

no changes

Build 7.0.3 RC3, 2006-10-06

no changes

Build 7.0.3 RC2, 2006-10-02

no changes


Build 7.0.3 RC1, 2006-09-25

ComponentVersion
Metadata:14
AS:7.0.3.10605
Client:2435
  • model.xml

    • tolerance: A tolerance can be defined in the <spatialInfo> element. It is used to associate a level of precision with spatial data.
  • presentation.xml

    • feature type short info: The element <featureInfo> can be defined inside a <ftPresentation> element. It contains element <infoQuery> which defines expression to be evaluated for feature's short info. In addition, it can contain format mask.
  • thematization.xml The original file thema.xml is renamed to thematization.xml. For the same reason some elements are renamed too: root element <thema> to <thematization>, element <themaMapArray> to <themeArray> and element <themaMap> to <theme>.


Build 7.0.3 Beta4, 2006-09-11

ComponentVersion
Metadata:14
AS:7.0.3.10603
Client:2435
  • model.xml
    • forbidden operations: The feature types and feature attributes can define some operations that are forbidden. The possible forbidden operations for feature types are [query | update | insert | delete], for feature attributes [select | filter | update]. The forbidden operations have higher priority than access rights and they are evaluated before them. The virtual and derived attributes have operation update forbidden from their principle.

Build 7.0.3 Beta3, 2006-09-01

ComponentVersion
Metadata:14
AS:7.0.3.10602
Client:2435

There is a transformation tool available that can upgrade model.xml file to version 7.0.3. It upgrades the version number, removes sortColumn and changes the symbology to SLD form.

  • model.xml

    • metadata version: The metadata version number is incremented to 14.
    • sortColumn: The attribute data type is changed. The sortColumn is removed. Sorting of codelist can be specified in a CodeList metadata definition. See analytic document about codelists Codelists Overview.
    • symbology: Format of a symobology is changed to SLD form.
  • thema.xml

    • SLD atributes: The order of some SLD attributes is changed.
    • thema.xsd: There is a thema.xsd available for validating thema.xml files. This file is included in the LIDS AS deployment archive.

Build 7.0.3 Beta2, 2006-08-23

ComponentVersion
Metadata:13
AS:7.0.3.10601
Client:2426
  • model.xml
    • MultiLine DA Query: The <ber:select> clause in Multi-line displayable attribute is now optional.

Build 7.0.3 Beta1