referencingconfiguration

This configuration is optional when using the plugin Gis.

  • Documentation

  • YAML Format

  • XML Format

Fill relevant inputs (blue boxes) and click the blue bars on the left to copy XML configuration snippets.
<referencingConfiguration
>
required

Settings for coordinate reference systems (CRSs). In order to adapt and optimize the use of CRSs, there are the following possibilities: - definition of additionally available CRSs - pre-setting of maximum geographic extents for CRSs in order to optimize loading time - restrict the CRSs from which the user can select in the corresponding dialogs - mappings of CRSs.

<definitions
>
optionalmax. 1

Definition settings for additionally available CRSs. If the CRSs delivered with Cadenza are not sufficient to display data with spatial references, additional CRSs can be defined. These will also be available in the CRS selection dialogs. Furthermore, it is possible to override CRSs that are already supported but not accurate enough for the use case by specifying the appropriate WKT string.

<coordinateReferenceSystem
<authority
>
optionalmax. 1
string

Identifier of the CRS. Format: authority:code - authority of the CRS, code of the CRS, e.g. EPSG:31467.

</authority>
<wkt
>
requiredmax. 1
string

Well-known text (WKT) of the CRS.

</wkt>
>
requiredmax. unbounded

Definition settings of an additionally available CRS.

</coordinateReferenceSystem>
</definitions>
<maximumExtents
>
optionalmax. 1

Settings for CRSs for which a maximum geographic extent is pre-set in order to optimize loading time. Note: The default setting usually differs from the theme-specific maximum geographic extent, e.g. if data exist only for a certain federal state (Bundesland), but the default extent covers the whole of Germany. If no CRSs are configured or if no geographic extent is pre-set for the CRS of the vector theme, then the data source is queried during initial loading to calculate the maximum geographic extent - even if the geo objects are not initially visible in the map.

<maximumExtent
>
optionalmax. unbounded

Settings for a CRS for which a maximum geographic extent is pre-set.

<authority
>
required
string

Identifier of the CRS. Format: authority:code - authority of the CRS, code of the CRS, e.g. EPSG:31467. The CRS must be known to cadenza.

</authority>
<boundingBox
<xMin
>
required
double

Minimum value in x-direction.

</xMin>
<yMin
>
required
double

Minimum value in y-direction.

</yMin>
<xMax
>
required
double

Maximum value in x-direction.

</xMax>
<yMax
>
required
double

Maximum value in y-direction.

</yMax>
>
required

Settings for the extent to be considered. Note: These specifications may differ from the official definitions for the CRS. This is to ensure that geo objects lying somewhat outside of it are also considered. E.g., to cover the whole of Germany, a larger extent must be entered for the EPSG:31467 coordinate system than that officially specified (see http://epsg.io/31467).

</boundingBox>
</maximumExtent>
</maximumExtents>
<availableReferencingSystems
>
optionalmax. 1

DEPRECATED: Settings to restrict the CRSs the user can select in the corresponding dialogs. When setting a CRS, e.g. to import data with spatial reference, the CRSs available for selection can be restricted. This ensures that the user is only offered the CRSs relevant to him. If no CRSs are pre-set, a very extensive list of the supported CRSs is loaded.

<referencingSystem
>
requiredmax. unbounded

Settings for a CRS the user can select in the corresponding dialogs.

srsId
required
=
string

Identifier of the CRS. Format: authority:code - authority of the CRS, code of the CRS, e.g. EPSG:31467.

<description
>
optionalmax. 1
string

Description of the CRS.

</description>
</referencingSystem>
</availableReferencingSystems>
<mappings
>
optionalmax. 1

Settings for the mappings of CRSs. Cadenza uses CRSs from the EPSG authority. If a data source, e.g. a database, uses a a non-EPSG CRS, it can be mapped to a corresponding CRS from EPSG. If no mapping exists, the CRS of the data source will be used, if supported by Cadenza.

<mapping
>
optionalmax. unbounded

Settings for a mapping of CRSs.

<sourceSystem
Choice: Choose only ONE of the following
<authority
>
requiredmax. 1
string

Identifier of the CRS. Format: authority:code - authority of the CRS, code of the CRS, e.g. EPSG:31467.

</authority>
<wkt
>
requiredmax. 1
string

Well-known text (WKT) of the CRS. Important: DEPRECATED for targetSystem. Please do not use this element any more inside targetSystem.

</wkt>
Choice End
>
requiredmax. 1

Settings of the CRS used by the data source.

</sourceSystem>
<targetSystem
Choice: Choose only ONE of the following
<authority
>
requiredmax. 1
string

Identifier of the CRS. Format: authority:code - authority of the CRS, code of the CRS, e.g. EPSG:31467.

</authority>
<wkt
>
requiredmax. 1
string

Well-known text (WKT) of the CRS. Important: DEPRECATED for targetSystem. Please do not use this element any more inside targetSystem.

</wkt>
Choice End
>
requiredmax. 1

Settings of the CRS the data source should be mapped to in Cadenza.

</targetSystem>
</mapping>
</mappings>
</referencingConfiguration>
This is a generated sample file with fake data and all the possible options shown, refer to the Documentation tab for what combinations are valid and what is required or not. 
cadenzaconfig:
  settings:
    referencingconfiguration:
      definitions:
      - authority: "text"
        wkt: "text"
      - authority: "text"
        wkt: "text"
      maximumExtents:
      - authority: "text"
        boundingBox:
          xMin: 133.7
          yMin: 133.7
          xMax: 133.7
          yMax: 133.7
      - authority: "text"
        boundingBox:
          xMin: 133.7
          yMin: 133.7
          xMax: 133.7
          yMax: 133.7
      availableReferencingSystems:
      - srsId: "text"
        description: "text"
      - srsId: "text"
        description: "text"
      mappings:
      - sourceSystem:
          authority: "text"
          wkt: "text"
        targetSystem:
          authority: "text"
          wkt: "text"
      - sourceSystem:
          authority: "text"
          wkt: "text"
        targetSystem:
          authority: "text"
          wkt: "text"

Filename: referencingconfiguration-config.xml

This is a generated sample file with fake data and all the possible options shown, refer to the Documentation tab for what combinations are valid and what is required or not. 
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<referencingConfiguration>
  <definitions>
    <coordinateReferenceSystem>
      <authority>text</authority>
      <wkt>text</wkt>
    </coordinateReferenceSystem>
    <coordinateReferenceSystem>
      <authority>text</authority>
      <wkt>text</wkt>
    </coordinateReferenceSystem>
  </definitions>
  <maximumExtents>
    <maximumExtent>
      <authority>text</authority>
      <boundingBox>
        <xMin>133.7</xMin>
        <yMin>133.7</yMin>
        <xMax>133.7</xMax>
        <yMax>133.7</yMax>
      </boundingBox>
    </maximumExtent>
    <maximumExtent>
      <authority>text</authority>
      <boundingBox>
        <xMin>133.7</xMin>
        <yMin>133.7</yMin>
        <xMax>133.7</xMax>
        <yMax>133.7</yMax>
      </boundingBox>
    </maximumExtent>
  </maximumExtents>
  <availableReferencingSystems>
    <referencingSystem srsId="text">
      <description>text</description>
    </referencingSystem>
    <referencingSystem srsId="text">
      <description>text</description>
    </referencingSystem>
  </availableReferencingSystems>
  <mappings>
    <mapping>
      <sourceSystem>
        <authority>text</authority>
        <wkt>text</wkt>
      </sourceSystem>
      <targetSystem>
        <authority>text</authority>
        <wkt>text</wkt>
      </targetSystem>
    </mapping>
    <mapping>
      <sourceSystem>
        <authority>text</authority>
        <wkt>text</wkt>
      </sourceSystem>
      <targetSystem>
        <authority>text</authority>
        <wkt>text</wkt>
      </targetSystem>
    </mapping>
  </mappings>
</referencingConfiguration>