selfserviceImport

<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

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

keepData

We 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

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 as string typed. This happens before the value is used to generate additional columns.

Default: true

</trimWhitespace>
>
optional

Used to configure how data is prepared before being imported, e.g. the behavior for removing leading or trailing whitespace.

</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
<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
<coordinates
>
optional
<xValue
<name
>
requiredmax. unbounded
string
</name>
>
optional
</xValue>
<yValue
<name
>
requiredmax. unbounded
string
</name>
>
optional
</yValue>
</coordinates>
<geographicCoordinates
>
optional
<longitude
<name
>
requiredmax. unbounded
string
</name>
>
optional
</longitude>
<latitude
<name
>
requiredmax. unbounded
string
</name>
>
optional
</latitude>
</geographicCoordinates>
<geographicCoordinatesNmea
>
optional
<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>