General import settings are available for every import type.
Setting name |
Description |
Target domain |
This is a mandatory setting. Each import session created from an import definition must target a specific domain. This domain will be used for following: •Resolve feature that are already in Redbex •Find alias schemes •Domain for newly created features |
Create new features |
If set, the import session will create new features (and if present their observations) found in the import data sources. If not set new features (and again their observations) will not be created. The import type decides what is a new feature by trying to match features found in the sources against features already existing in Redbex. The logic for this matching is different for each feature type. |
Update existing observations |
If set, data of already existing observations (observations with the same sampling time as an observation in the import source) stamp will be overwritten with the data from the import source. Note: Updating observations results in a deletion of existing observations and creation of new observations. |
Update existing features |
If set, data for already existing features (features in Redbex that could be mapped to the features found in the import source with the logic of the import type) will be updated with the data from the import source |
Create historical data |
If set, Redbex stores information about what was changed or created in a database. Advisable to turn this off when running gigantic import such as a TMO import. |
Import session name |
The identifying name that will be used for all import sessions that are created from this import definition. This setting is optional but is useful when tracking import logs etc. If no import session name is defined the Application Server will choose a default name. |
Import session description |
Description that will be added to all import sessions that are created from this import definition. This setting is optional but is useful when tracking import logs etc. |
Table 1: Settings in the General group
Time conversion
Settings in this group are used to define how the Application Server shall handle Date-Time values read from the source(s) when converting them to Date-Time-Offset.
Setting name |
Description |
Conversion type |
Defines which conversion type shall be used when converting Date-Time values. Two options are available: •Time zone: With Time Zone conversion Date-Time values are interpreted using the Time Zone defined in the Time Zone setting. •Fixed offset: With Fixed offset conversion Date-Time values are interpreted using a fixed offset. I.e. all Date-Time values in the source are assumed to have the same offset from UTC. |
Time Zone |
This setting is only effective if Conversion type (see above) is set to Time Zone. Defines the time zone used to convert Date-Time values to Date-Time Offset Values. Default: Application Server's Operating System Time zone. |
Fixed offset |
This setting is only effective if Conversion type (see above) is set to Fixed Offset. Defines a time span (in minutes) that is used to convert Date-Time values to Date-Time Offset Values. Default: Application Server's Operating System Current Time Offset.. |
Table 2: Settings in the Time conversion group
Settings in this group are used to define if features created or modified by the import shall be added as members to the specified group features.
Setting name |
Description |
Apply to |
This setting defines which features that are added or updated by the import will actually become a member of the specified group features. No feature: Disables adding features to groups New features: Only features newly created Existing features: Only modified features (i.e. features where either feature data or observations have been modified) will be added as group members New and existing features: combination of the above. |
Group feature 1 |
Feature to which all features created and/or modified by the import shall be added as group member. |
Group feature 2 |
Feature to which all features created and/or modified by the import shall be added as group member. |
Group feature 3 |
Feature to which all features created and/or modified by the import shall be added as group member. |
Table 3: Settings in the Group feature membership group
Advanced settings
Settings in this group are usually only for advanced users, they allow you to fine tune your import definition.
Setting name |
Description |
Alias scheme |
This is an optional setting. Defines the alias scheme to be used for resolving feature names found in the source files. If no alias scheme is given the Application Server will resolve feature names in the source files with the real feature names stored on the Application Server |
Skip errors |
If enabled the import will skip errors if possible, if not enabled the import will break if an error is detected, e.g. when reading a malformed source file. Default: False |
Break after conversion |
If set the import definition will not actually create or modify features or observations but the import will break after the data was read from the import sources. This setting is useful when trying to read data from a new source since it will report all errors during reading from that source and will not create any features or observations. Default: False |
Edit mode setting |
Can be used to advice the importer to set the editing mode of newly created observations. Default: None |
Table 4: Settings in the Advanced settings group
