locationfinderweb

This configuration is optional when using the plugin Location_Finder.

  • Documentation

  • YAML Format

  • XML Format

Fill relevant inputs (blue boxes) and click the blue bars on the left to copy XML configuration snippets.
<locationFinderConfiguration
<coordinateProviderConfigurations
>
optional
<coordinateProviderConfiguration
id
required
=
string

The identifier for this coordinate provider. Should be unique. Necessary for referencing/using this coordinate provider by data provider definitions of the location finder.

<coordinateResolver
<srs
<authority
>
requiredmax. 1
string
</authority>
<code
>
requiredmax. 1
int
</code>
>
required

Any SRS Cadenza is configured to know.

</srs>
<areaOfUse
<minX
>
required
double
</minX>
<minY
>
required
double
</minY>
<maxX
>
required
double
</maxX>
<maxY
>
required
double
</maxY>
>
required

Interpreted in WGS 84. Matched coordinates will be transformed to WGS 84 and checked for being inside this bounding box.

</areaOfUse>
<inputFormat
formatType
optional
=
xsd:string
decimal
sexagesimal

decimal or sexagesimal

<pattern
>
requiredmax. unbounded
string

Patterns for parsing the entered coordinate strings. E.g.: Pseudo Mercator X Y with German separators: \s*(?<x>-?[12]?\d?\.?\d?\d?\d?\.?\d?\d?\d?(,\d+)?)\s*[\s/;]\s*(?<y>-?[12]?\d?\.?\d?\d?\d?\.?\d?\d?\d?(,\d+)?).* Pseudo Mercator X Y with US separators: \s*(?<x>-?[12]?\d?,?\d?\d?\d?,?\d?\d?\d?(\.\d+)?)\s*[\s/;]\s*(?<y>-?[12]?\d?,?\d?\d?\d?,?\d?\d?\d?(\.\d+)?).*

</pattern>
>
required

Configuration for how the input for the search will be structured. See documentation in InputFormatType for more details.

</inputFormat>
<result
<listItemFormat
>
required
string

Regular expression with placeholders for attributes (coordinates) that defines which elements appear in which order and with what formatting in the result list entries.

For inputFormat.formatType = decimal: Valid placeholders are x and y. E.g. {x,number,#.#######} {y,number,#.#######} .

For inputFormat.formatType = sexagesimal: Valid placeholders are x, y, xd, xm, xs, ew, yd, ym, ys and ns. E.g. {yd,number,00}°{ym,number,00}′{ys,number,00.###}″{ns} {xd,number,00}°{xm,number,00}′{xs,number,00.###}″{ew}.

</listItemFormat>
<listItemDescription
>
optional
string

Header over the results of that coordinate parser. If two parsers have the same listItemDescription, their results get grouped under the same header. Default: coordinateProviderConfiguration.id

</listItemDescription>
<maxCount
>
optional
int
</maxCount>
>
required

Configuration for how the result of the search will be displayed. See documentation in ResultType for more details.

</result>
>
requiredmax. unbounded
</coordinateResolver>
>
optionalmax. unbounded

A single provider for coordinate search. Can contain 1 to many configurations for different coordinate parsers. If the user should be able to choose from different coordinate searches it can make sense to put available coordinate parser definitions into different coordinateProviderConfiguration elements.

</coordinateProviderConfiguration>
</coordinateProviderConfigurations>
>
required

Configuration for the location finder in maps.

</locationFinderConfiguration>
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:
    locationfinderweb:
      coordinateProviderConfigurations:
      - id: "text"
        coordinateResolver:
        - srs:
            authority: "text"
            code: 15
          areaOfUse:
            minX: 133.7
            minY: 133.7
            maxX: 133.7
            maxY: 133.7
          inputFormat:
            formatType: "decimal"
            pattern:
            - "text"
            - "text"
          result:
            listItemFormat: "text"
            listItemDescription: "text"
            maxCount: 15
        - srs:
            authority: "text"
            code: 15
          areaOfUse:
            minX: 133.7
            minY: 133.7
            maxX: 133.7
            maxY: 133.7
          inputFormat:
            formatType: "decimal"
            pattern:
            - "text"
            - "text"
          result:
            listItemFormat: "text"
            listItemDescription: "text"
            maxCount: 15
      - id: "text"
        coordinateResolver:
        - srs:
            authority: "text"
            code: 15
          areaOfUse:
            minX: 133.7
            minY: 133.7
            maxX: 133.7
            maxY: 133.7
          inputFormat:
            formatType: "decimal"
            pattern:
            - "text"
            - "text"
          result:
            listItemFormat: "text"
            listItemDescription: "text"
            maxCount: 15
        - srs:
            authority: "text"
            code: 15
          areaOfUse:
            minX: 133.7
            minY: 133.7
            maxX: 133.7
            maxY: 133.7
          inputFormat:
            formatType: "decimal"
            pattern:
            - "text"
            - "text"
          result:
            listItemFormat: "text"
            listItemDescription: "text"
            maxCount: 15

Filename: locationfinderweb-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"?>
<locationFinderConfiguration>
  <coordinateProviderConfigurations>
    <coordinateProviderConfiguration id="text">
      <coordinateResolver>
        <srs>
          <authority>text</authority>
          <code>15</code>
        </srs>
        <areaOfUse>
          <minX>133.7</minX>
          <minY>133.7</minY>
          <maxX>133.7</maxX>
          <maxY>133.7</maxY>
        </areaOfUse>
        <inputFormat formatType="decimal">
          <pattern>text</pattern>
          <pattern>text</pattern>
        </inputFormat>
        <result>
          <listItemFormat>text</listItemFormat>
          <listItemDescription>text</listItemDescription>
          <maxCount>15</maxCount>
        </result>
      </coordinateResolver>
      <coordinateResolver>
        <srs>
          <authority>text</authority>
          <code>15</code>
        </srs>
        <areaOfUse>
          <minX>133.7</minX>
          <minY>133.7</minY>
          <maxX>133.7</maxX>
          <maxY>133.7</maxY>
        </areaOfUse>
        <inputFormat formatType="decimal">
          <pattern>text</pattern>
          <pattern>text</pattern>
        </inputFormat>
        <result>
          <listItemFormat>text</listItemFormat>
          <listItemDescription>text</listItemDescription>
          <maxCount>15</maxCount>
        </result>
      </coordinateResolver>
    </coordinateProviderConfiguration>
    <coordinateProviderConfiguration id="text">
      <coordinateResolver>
        <srs>
          <authority>text</authority>
          <code>15</code>
        </srs>
        <areaOfUse>
          <minX>133.7</minX>
          <minY>133.7</minY>
          <maxX>133.7</maxX>
          <maxY>133.7</maxY>
        </areaOfUse>
        <inputFormat formatType="decimal">
          <pattern>text</pattern>
          <pattern>text</pattern>
        </inputFormat>
        <result>
          <listItemFormat>text</listItemFormat>
          <listItemDescription>text</listItemDescription>
          <maxCount>15</maxCount>
        </result>
      </coordinateResolver>
      <coordinateResolver>
        <srs>
          <authority>text</authority>
          <code>15</code>
        </srs>
        <areaOfUse>
          <minX>133.7</minX>
          <minY>133.7</minY>
          <maxX>133.7</maxX>
          <maxY>133.7</maxY>
        </areaOfUse>
        <inputFormat formatType="decimal">
          <pattern>text</pattern>
          <pattern>text</pattern>
        </inputFormat>
        <result>
          <listItemFormat>text</listItemFormat>
          <listItemDescription>text</listItemDescription>
          <maxCount>15</maxCount>
        </result>
      </coordinateResolver>
    </coordinateProviderConfiguration>
  </coordinateProviderConfigurations>
</locationFinderConfiguration>