Skip to main content

LIDS Edit / Explorer

explorer.xml​

explorer.xml is optional extension file, which enables further configuration specific for thick clients. It's common for LIDS Edit and LIDS Explorer.

Example: Structure of explorer.xml.

<?xml version="1.0" encoding="UTF-8"?>
<ber:modelExplorer xmlns:ber="http://www.berit.com/ber"
                   xmlns:xlink="http://www.w3.org/1999/xlink">
  <ber:version>
    <ber:metadata>1</ber:metadata>
    <ber:minClient>7676</ber:minClient>
    <ber:minAS>171001</ber:minAS>
  </ber:version>
  <ber:groupArray>
    <group key="businessMetaGroup" value="explorerBusiness,requests"/>
    <group key="searchMetaGroup" value="explorerSearch,territory"/>
    <group key="relationTreeMetaGroups" value="territory,water,roads"/>
    <group key="snapMetaGroups" value="Water_network,inspections"/>
  </ber:groupArray>
  <businessAssignmentArray>
    <businessAssignment assetAssignFillAttributes="true" boAssignFillAttributes="true" copyAfterAssetSplit="true">
      <ber:featureType xlink:href="model.xml#ft_bo_assign"/>
      <ber:relationAssoc xlink:href="model.xml#as_bo_assign"/>
      <ber:assetRelationAssocArray>
        <ber:relationAssoc xlink:href="model.xml#as_bo_asset_1"/>
        <ber:relationAssoc xlink:href="model.xml#as_bo_asset_2"/>
        <ber:relationAssoc xlink:href="model.xml#as_bo_asset_3"/>
      </ber:assetRelationAssocArray>
    </businessAssignment>
  </businessAssignmentArray>
  <ber:dynamicDAArray>
    <ber:graphicTagType xlink:href="model.xml#ft_street_da_name"/>
  </ber:dynamicDAArray>
  <ber:parameterArray>
    <ber:parameter name="as_timeout" value="666666"/>
    <ber:parameter name="automatic_download_relations" value="true"/>
    <ber:parameter name="explorer_detail_max_scale" value="35"/>
    <ber:parameter name="uStn_respect_backdrop_GO" value="true"/>
    <ber:parameter name="uStn_master_units" value="m"/>
  </ber:parameterArray>
  <ber:unavailableFunctions>
    <ber:module name="Module1">
      <ber:function name="Function1"/>
      <ber:function name="Function2"/>
    </ber:module>
    <ber:module name="Module2">
      <ber:function name="Function3"/>
    </ber:module>
  </ber:unavailableFunctions>
  <ber:dependentFormArray>
    <ber:dependentForm>
      <ber:featureType xlink:href="model.xml#ft_A"/>
      <ber:attribute xlink:href="model.xml#at_01/ca_01"/>
    </ber:dependentForm>
  </ber:dependentFormArray>
  <ber:onDemandDownloadRelationTypeArray>
    <ber:relationAssoc xlink:href="model.xml#as_1">
      <ber:relationRole xlink:href="model.xml#rt_2"/>
    </ber:relationAssoc>
  </ber:onDemandDownloadRelationTypeArray>
</ber:modelExplorer>

  • businessMetaGroup – comma separated names of metadata groups. Forms of feature types from these groups only will include possibility to call SAMO business actions. If value “business” is used, forms of all feature types which have a SAMO business action defined will be expanded by the appropriate functions. The group business is a system group, it doesn’t have to be defined in model.xml. If businessMetaGroup definition is missing, no SAMO business actions are available in LIDS Edit / Explorer

  • searchMetaGroup – comma separated names of metadata groups. If defined, only feature types from these groups will be queried by the function Search out. If not defined, all feature types defined in Search extension are queried

  • relationTreeMetaGroups – comma separated names of metadata groups. If defined, only these groups will be offered for the filter in Subordinate Features Tree dialog. If not defined, all groups containing at least one relationship type will be offered

  • snapMetaGroups– comma separated names of metadata groups. If defined, these groups will be offered for exclusive snapping in LIDS Explorer graphic view

  • forbiddenFTChangeMetaGroups – comma separated names of metadata groups. If defined, feature types from these groups can’t be selected as source or destination for the feature type change function. In case of shared semantics, any feature type included in this group causes a semantic parent and all graphical children to be excluded

  • moveWithContextMetaGroups – comma separated names of metadata groups. If defined, the groups can be selected in the Move with context window. Only features of the selected types will be moved using this function

    • businessAssignmentArray – section for defining the SAMO assignment

      • assetAssignFillAttributes – true / false attribute defines, whether the form for filling the assignment attributes is opened, when the assigning of asset is started from business object form

      • boAssignFillAttributes – true / false attribute defines, whether the form for filling the assignment attributes is opened, when the assigning of business object is started from asset form

      • copyAfterAssetSplit – true / false attribute defines behavior of split line function. If set to true, the assignment feature is copyied and related to the newly created line segment

      • featureType – assignemnt feature type used to bind SAMO business object and assets

      • relationAssoc – relation between the assignment feature type and SAMO business object

      • assetRelationAssocArray – list of relations between the assignment feature type and assets

    • dynamicDAArray – list of displayable attribute types, which will be moved automatically to fit into map frame

    • parameterArray – various parameters described in the separate chapter

    • unavailableFunctions – optional definition of client functions, which should be hidden on the project, for all users

    • dependentForm – defines feature type attribute, typically codelist attribute, including form id. The form with corresponding id will be used for displaying feature attributes in the form window. This way it’s possible to control the used form by attribute value

    • onDemandDownloadRelationType – defines list of relations + roles, whose content will not be downloaded automatically when activating particular relation type in the related features component. It’s useful for relations with big amount of related features

Parameters​

The following parameters were included in config.xml and were editable by LIDS Application Server console using the Client properties section up to version 7.7. Starting with version 8.0, the parameters are part of standard project metadata.

General parameters​

  • as_timeout (integer, default = 60) Time limit (sec) for receiving a response to a request passed on to the application server. After a timeout, the original request is canceled on the client side.

  • automatic_project_logoff_timeout (integer) Time limit (sec) for inactivity of LIDS Explorer / LIDS Edit clients. If no communication between the client application and the server occurs within the defined interval, a dialog box is displayed to the user with a 30-second countdown. Once this has expired, the client application will be terminated. The minimum allowed value is 30 s.

    • automatic_project_logoff_pending_changes_policy (keep / commit / rollback, default = keep) Defines the behavior of the automatic_project_logoff_timeout parameter when some operations in operation history have not been committed
      • keep – keep pending changes uncommitted; don't log off
      • commit – commit pending changes and log off
      • rollback – roll back pending changes and log off.

  • automatic_download_relations (true/false, default = false) Manages automatic downloading of relations at the moment when the feature form is displayed.

  • feature_page_size (number >= 1) Number of records on one page when downloading data to browse and form.

  • feature_page_size_till_end (number >= 1) Number of records on one page when downloading all remaining data in browse and form.

  • autocommit (true/false) Switches on/off option Automatic committing of operations after logging in to the project.

  • backdropCache_dir (directory path) Name of directory for temporary saving of backdrop map files.

  • backdropCache_exclusive (true/false) Suppression of downloading backdrop map files from the AS – requested files are only searched for in the local cache.

  • backdropCache_update (true/false) Suppression of downloading backdrop map files from the local cache – requested files are always downloaded from the AS.

  • bulk_operation_question_limit (number) If the parameter exists and user modifies more features than specified, confirmation window is displayed. Following functions consider this parameter:

    • Bulk editing of attributes in browse
    • Move features - selection set / fence

  • offline_download_all_codelists (true/false) Manages downloading of codelists on transfer to off-line mode (all codelists / only codelists defined for feature types selected for off-line mode).

  • explorer_max_scale (number >= 0.1) Maximum allowed scale for Graphic View window in LIDS Explorer.

  • explorer_detail_max_scale (number >= 1) Maximum allowed scale for window displaying a detail.

  • uStn_master_units (km/m/cm/mm/um) Master units of created DGN files. Used for exported DGN and for system DGN in LIDS Edit.

  • uStn_sub_units (km/m/cm/mm/um) Subunits of created DGN files. Used for exported DGN and for system DGN in LIDS Edit.

  • uStn_working_per_master (integer) Ratio of master units and subunits for LIDS Edit with MicroStation.

  • uStn_3d_seed_file (true/false, default = false) Manages use of 2D/3D seed file for LIDS Edit with MicroStation.

  • uStn_local_seed_only (true/false) Flag defining priority use of the seed file installed on the local computer over the seed file registered on the application server.

  • uStn_respect_backdrop_GO (true/false, default = false) Flag defining if global origin of DGN files is considered when attaching backdrop maps. Default is false.

  • dgn_export_model_name (text) Defines the name of the model for the output dgn file for the Save into dgn file function.

  • maxRequestImportItems (number >= 1) Defines the maximum number of imported features which will be sent in one request when using the Import file function.

  • exp_XML_max_levels Defines the maximum allowed value for Related non-graphic features - To level in the function Export to XML.

  • project_info The parameter contains URL of the Web page that appears after the user logs on to the project.

  • project_info_time The parameter specifies the timestamp for the webpage defined in the project_info parameter. It has the following format: YYYY-MM-DD HH:MM:SS.

  • infra3d_url The parameter contains URL of the infra3d server application.

  • system_settings_folderId (setting id in the format „id_1234567890“) The parameter contains id of folder in store, where the „system“ settings should be stored. The setting types include e.g. useroptions, projectoptions,keyboardshortcuts, guicustomized etc. The folder has to be created manually and the existing settings should be moved there. The folder should be writable so that users can insert new items

  • coordinatesScale (whole number >= 0) Defines the number of fraction digits for displaying coordinates in some windows. In LIDS 8.22 limited to the window Change Coordinates - Table

  • gridShift (pair of coordinates separated by semicolon, example: "2.8;-3.25") Defines the shift of coordinates grid in x and y axis. Doesn’t have any impact on the data or coordinates, only shifts the display of grid in graphical vew.

  • delete_orphan_ducts (true/false, default = false) When deleting a route, system offers to delete ducts from this route, which are not related to any other route

  • split_route_split_all_ducts (true/false, default = false) When splitting a route, all related ducts are automatically split as well. If related cables exist, the window Split Line - Cables is opened.

Parameters for projects with configuration with SIAS​

  • dynamic_vector_download (true/false) Manages availability of control icons for downloading of vector data.

  • detail_raster_format (jpg, png) Format of files displaying a detail.

  • allow_plain_scale_lock (true/false) Manages availability of function to lock scale for backdrop maps download.

Parameters for projects with configuration with TOMS​

  • toms_use_sid (true/false) Manages use of SID or FID identifiers for requests sent from TOMS to LIDS AS.

  • toms_max_objects (number 1 to 1000000) Maximum allowed number for tab page TOMS.

  • tdm_timeout (number) Time interval (sec) for checking the ECHO signal from TOMS Desktop Manager.

  • toms_startup_raster (number >= 0) Defines which raster will be displayed when GIS Explorer is launched from the TOMS module. The value determines the position of the given type of backdrop map in backdropTypeArray in model.xml.

  • toms_encoding (default for TOMS = UTF-8, default for GIS Explorer tools = windows-1250) Encoding used for communication between TOMS modules and GIS Explorer.

warning

This toms_encoding parameter is used also by other interfaces based on GIS Explorer tools, e.g. IMS or TIS.

  • redline_featuretype Identification of feature type used for redline. Supported up to TOMS version 3.2.

Project Options settings​

LIDS Edit / Explorer applications can be configured also interactively using the options available in the Settings dialog box. There are a lot of options to configure this way. Though every user can tune the options individually, it’s useful to preconfigure some options on the project level, for all users.

The client application includes functions for managing two types of option settings:

  • The Project Settings dialog box allows a user with the appropriate rights to manage the project options setting.

  • The Settings dialog box allows a user to manage its user options setting

Both, the project options setting and user options settings are stored in database in the LIDS_SETTINGS table. There can be up to one project options setting for whole project and one user options setting for every user.

The client application always generates complete user options setting including all possible parameters when connecting to the project. It reads both the project options setting and the saved version of the user options setting:

  • If some parameter doesn't exist in the user options, the value from project options is copied to user options with the flag changed="False"

  • If some parameter exists in the user options with the flag changed="False", the value is updated according to the project options and the flag changed="False" is preserved

  • If some parameter exists in the user options with the flag changed="True", the value from user options wins and the value from project options is ignored

tip

Following possibilities exist to make particular entry from project options to appear in the user options:

  • Delete user options setting completely. It will be regenerated according to the project options during the next logging into the client
  • Delete particular entry from the user options setting. It will be regenerated according to the project options during the next logging into the client
  • Set the value of particular entry in the user options to changed="False". It will be updated according to the project options during the next logging into the client
  • It’s always possible to update the particular entry directly in user options and set the flag changed="True". That’s exactly what the interactive manipulation in the Settings dialog box does

LIDS Edit on Bentley platform​

system.dgn generating​

The procedure of creating system.dgn follows:

  1. Seed file is copied and opened

    a. If seedDgn resource is registered in project, the seed file is used from project resources

    b. If seedDgn resource is not registered in project, seed.dgn from client installation is used

  2. It is converted to 3D if project is 3D or uStn_3d_seed_file property is set to true

  3. Colors for background, selection set and highlight are set according to project / user Options

  4. Units are set according to client properties (uStn_master_units, uStn_sub_units and uStn_working_per_master)

  5. Project RSC and LIN line style are imported into the file

  6. Project fonts are initialized in the file

  7. Library of symbol hatching styles is generated and attached to the file

  8. Project coordinate system is assigned to the file according to EPSG

  9. File Views are set according to default situation

Copy features configuration​

The function for copying features can operate in two modes. The new features either take over the type of the source feature or they can be assigned another type on the basis of rules saved in metadata.

The rules are defined in option.xml in featureCopyArray. Every rule can define following properties:

  • parameters – preconfigured geometry operations rotation, scaleFactor, horizontalFlip, verticalFlip

  • copyFTArray – pairs of source feature type - inputFT and target feature type – outputFT

  • sharedSemantic – optional attribute, default value is false. If sharedSemantic =“true“, the source and target features are assigned to a common group sharing the semantics.

  • copyAttributeArray – optional definition of the way how the attributes of the target features (outputAttribute) are filled. Possible definitions:

    • inputAttribute – attribute value taken from input feature attribute

    • defaultValue – attribute value defined as constant value

Example: featureCopy definitions in option.xml

<ber:featureCopyArray>
    <ber:featureCopy id="fc_1" name="Map A converted to map B and transformed">
      <ber:parameters rotation="180" scaleFactor="1.5" horizontalFlip="true" verticalFlip="true"/>
      <ber:copyFTArray>
        <ber:copyFT sharedSemantic="false">
          <ber:inputFT xlink:href="model.xml#ft_A1"/>
          <ber:outputFT xlink:href="model.xml#ft_B1"/>
        </ber:copyFT>
        <ber:copyFT sharedSemantic="true">
          <ber:inputFT xlink:href="model.xml#ft_A2"/>
          <ber:outputFT xlink:href="model.xml#ft_B2"/>
        </ber:copyFT>
        <ber:copyFT sharedSemantic="true">
          <ber:inputFT xlink:href="model.xml#ft_A3"/>
          <ber:outputFT xlink:href="model.xml#ft_A3"/>
        </ber:copyFT>
      </ber:copyFTArray>
    </ber:featureCopy>
    <ber:featureCopy id="fc_2" name="...">
      <ber:parameters rotation="0" scaleFactor="1.0" horizontalFlip="false" verticalFlip="false"/>
      <ber:copyFTArray>
        <ber:copyFT sharedSemantic="true">
          <ber:inputFT xlink:href="model.xml#ft_1"/>
          <ber:outputFT xlink:href="model.xml#ft_1"/>
        </ber:copyFT>
        <ber:copyFT sharedSemantic="false">
          <ber:inputFT xlink:href="model.xml#ft_2"/>
          <ber:outputFT xlink:href="model.xml#ft_3"/>
          <ber:copyAttributeArray>
            <ber:copyAttribute>
              <ber:inputAttribute xlink:href="model.xml#at_1"/>
              <ber:outputAttribute xlink:href="model.xml#at_2"/>
            </ber:copyAttribute>
            <ber:copyAttribute>
              <ber:inputAttribute xlink:href="model.xml#at_3"/>
              <ber:outputAttribute xlink:href="model.xml#at_4"/>
            </ber:copyAttribute>
            <ber:copyAttribute>
              <ber:defaultValue>abc</ber:defaultValue>
              <ber:outputAttribute xlink:href="model.xml#at_5"/>
            </ber:copyAttribute>
          </ber:copyAttributeArray>
        </ber:copyFT>
      </ber:copyFTArray>
    </ber:featureCopy>
  </ber:featureCopyArray>