selfserviceimport

This configuration is optional when using the plugin Self_Service_Import.

  • Documentation

  • YAML Format

  • XML Format

Fill relevant inputs (blue boxes) and click the blue bars on the left to copy XML configuration snippets.
<selfServiceImport
<fileInterpretation
<csv
<charsets
<charset
>
requiredmax. unbounded
string
</charset>
>
optional

Charsets for CSV file import the user can select. If this is not configured a default list of charsets will be offered. For details see https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/nio/charset/Charset.html

</charsets>
>
required

Configuration options for CSV file interpretation.

</csv>
>
optional

Configuration options for the file interpretation within the import wizard.

</fileInterpretation>
<objecttype
<srs
>
optional
string

Automatically transform all spatial data into this spatial reference system during import. If this is not set, all imports and operations use their specific SRSs, e.g. EPSG:4326 for KML or the map SRS for grid square layer.

</srs>
<onDelete
xsd:string
deleteData

Delete the data table to free memory and mark the data as deleted in the metadata.

keepData

Do not really delete the data, as usual it would only be marked as deleted in the metadata.

>
optional
</onDelete>
>
optional

DEPRECATED: A configuration on how to treat the objecttype that is being or was created by selfservice import.

</objecttype>
<dataPreparation
<trimWhitespace
>
optional
boolean

"true" to activate trimming. Trimming removes a continuous sequence of leading and trailing whitespace characters as defined by https://docs.oracle.com/en/java/javase/21/docs/api/java.base/java/lang/Character.html#isWhitespace(int) from all input values that the input format and Cadenza consider to be string typed. This happens before the value is used to generate additional columns. "false" to deactivate trimming.

Default: true

</trimWhitespace>
>
optional

Configuration of the data preparation before the data will be imported.

</dataPreparation>
<temporalReference
<attributePatterns
<dateTimePattern
xsd:string
>
optionalmax. unbounded
</dateTimePattern>
<datePattern
xsd:string
>
optionalmax. unbounded
</datePattern>
<timePattern
xsd:string
>
optionalmax. unbounded
</timePattern>
>
optional

Patterns for parsing values from one or multiple attributes in order to create a temporal reference. Possible case-sensitive tokens are HH (hour-of-day, 0-23), mm (minute-of-hour), ss (second-of-minute), SSS (fraction-of-second), X (timezone-offset, accepts Z for zero), yyyy (year), MM (month-of-year), dd (day-of-month). Use single quotes ('') for matching arbitrary text. If some kinds of patterns (dateTime, date, time) are not specified here, Cadenza defined default patterns will be used. In any way the user will have a possibility to enter a custom pattern, so these patterns are not required to be exhaustive but should cover the main use cases.

</attributePatterns>
<attributeMappings
>
optional

Potential columns with a time reference in the import file and their assignment to the input fields for the time reference in the import wizard.

<dateTime
<name
>
requiredmax. unbounded
string
</name>
>
optional
</dateTime>
<date
<name
>
requiredmax. unbounded
string
</name>
>
optional
</date>
<time
<name
>
requiredmax. unbounded
string
</name>
>
optional
</time>
</attributeMappings>
>
optional

In case the data includes temporal information the user can optionally create a date. This configuration allows tuning the choices, e.g. by offering patterns for parsing date and time values.

</temporalReference>
<spatialReference
<attributeMappings
>
optional

Potential columns with a spatial reference in the import file and their assignment to the input fields for the spatial reference in the import wizard.

<coordinates
>
optional

Column mapping for the fields of projected coordinates. There are predefined elements xValue and yValue for this.

<xValue
<name
>
requiredmax. unbounded
string
</name>
>
optional
</xValue>
<yValue
<name
>
requiredmax. unbounded
string
</name>
>
optional
</yValue>
</coordinates>
<geographicCoordinates
>
optional

Column mapping for the fields of geographic coordinates. There are predefined elements longitude and latitude for this.

<longitude
<name
>
requiredmax. unbounded
string
</name>
>
optional
</longitude>
<latitude
<name
>
requiredmax. unbounded
string
</name>
>
optional
</latitude>
</geographicCoordinates>
<geographicCoordinatesNmea
>
optional

Column mapping for the fields of NMEA-0183 coordinates. There are predefined elements longitude and latitude as well as longitudeHemisphere and latitudeHemisphere for this.

<longitude
<name
>
requiredmax. unbounded
string
</name>
>
optional
</longitude>
<latitude
<name
>
requiredmax. unbounded
string
</name>
>
optional
</latitude>
<longitudeHemisphere
<name
>
requiredmax. unbounded
string
</name>
>
optional
</longitudeHemisphere>
<latitudeHemisphere
<name
>
requiredmax. unbounded
string
</name>
>
optional
</latitudeHemisphere>
</geographicCoordinatesNmea>
</attributeMappings>
>
optional

In case the data includes spatial information the user can optionally create a geometry. This configuration allows tuning the choices or preselection of attributes for certain ways of creating a spatial reference.

</spatialReference>
>
required

Basic Configuration for selfservice, independent of specific data types like qml, excel, etc.

</selfServiceImport>
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:
    selfserviceimport:
      fileInterpretation:
        csv:
          charsets:
          - "text"
          - "text"
      objecttype:
        srs: "text"
        onDelete: "deleteData"
      dataPreparation:
        trimWhitespace: true
      temporalReference:
        attributePatterns:
          dateTimePattern:
          - "text"
          - "text"
          datePattern:
          - "text"
          - "text"
          timePattern:
          - "text"
          - "text"
        attributeMappings:
          dateTime:
          - "text"
          - "text"
          date:
          - "text"
          - "text"
          time:
          - "text"
          - "text"
      spatialReference:
        attributeMappings:
          coordinates:
            xValue:
            - "text"
            - "text"
            yValue:
            - "text"
            - "text"
          geographicCoordinates:
            longitude:
            - "text"
            - "text"
            latitude:
            - "text"
            - "text"
          geographicCoordinatesNmea:
            longitude:
            - "text"
            - "text"
            latitude:
            - "text"
            - "text"
            longitudeHemisphere:
            - "text"
            - "text"
            latitudeHemisphere:
            - "text"
            - "text"

Filename: selfserviceimport-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"?>
<selfServiceImport>
  <fileInterpretation>
    <csv>
      <charsets>
        <charset>text</charset>
        <charset>text</charset>
      </charsets>
    </csv>
  </fileInterpretation>
  <objecttype>
    <srs>text</srs>
    <onDelete>deleteData</onDelete>
  </objecttype>
  <dataPreparation>
    <trimWhitespace>true</trimWhitespace>
  </dataPreparation>
  <temporalReference>
    <attributePatterns>
      <dateTimePattern>text</dateTimePattern>
      <dateTimePattern>text</dateTimePattern>
      <datePattern>text</datePattern>
      <datePattern>text</datePattern>
      <timePattern>text</timePattern>
      <timePattern>text</timePattern>
    </attributePatterns>
    <attributeMappings>
      <dateTime>
        <name>text</name>
        <name>text</name>
      </dateTime>
      <date>
        <name>text</name>
        <name>text</name>
      </date>
      <time>
        <name>text</name>
        <name>text</name>
      </time>
    </attributeMappings>
  </temporalReference>
  <spatialReference>
    <attributeMappings>
      <coordinates>
        <xValue>
          <name>text</name>
          <name>text</name>
        </xValue>
        <yValue>
          <name>text</name>
          <name>text</name>
        </yValue>
      </coordinates>
      <geographicCoordinates>
        <longitude>
          <name>text</name>
          <name>text</name>
        </longitude>
        <latitude>
          <name>text</name>
          <name>text</name>
        </latitude>
      </geographicCoordinates>
      <geographicCoordinatesNmea>
        <longitude>
          <name>text</name>
          <name>text</name>
        </longitude>
        <latitude>
          <name>text</name>
          <name>text</name>
        </latitude>
        <longitudeHemisphere>
          <name>text</name>
          <name>text</name>
        </longitudeHemisphere>
        <latitudeHemisphere>
          <name>text</name>
          <name>text</name>
        </latitudeHemisphere>
      </geographicCoordinatesNmea>
    </attributeMappings>
  </spatialReference>
</selfServiceImport>