| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
ImportNWP 1.00 default.xml
ImportNWP | Fixed file name for the ImportNWP IdMap. |
1.00 | Version number |
default | Unit to indicate the version is the default configuration (otherwise omitted). |
Figure 155 Root element of the IdMaps configuration
...
When one to one mapping is enabled the internal ids id's are used as external ids when not mapped explicitly. When this option is not enabled the id map also acts as a filter . Everything when at least one location is mapped explicitly (using for example <location>). In that case, everything that is not mapped is not imported or exported. When not one location is mapped explicitly, enableOneToOneMapping is enabled by default but is good practice to explicitly configure the xml element. Note that the filtering option for exporting does not work in combination with the export option to write separate files per location through the data export option <useExternalLocationIdAsName>.
When FEWS imports timeseries with enableOneToOneMapping, it uses quite some flexibility for mapping. First it tries to match exactly on location, parameter, qualifiers, ensembleId, ensembleMemberId and timeStep. But if that does not result in a match it tries to match with fewer keys, by ignoring first ensembleId, then ensembleMemberId, then timeStep, and at last qualifiers. This could cause different timeseries to be imported to the same timeSeriesSet, for instance when two timeseries are imported that only differ based on a qualifier and one of the timeseries does not have an exact match on a configured timeSeries Set. A warning will then be logged: "Multiple time series sets found for XXX" and it may be in unclear from which time series the data will be imported. This can be prevented by adding a configured timeSeriesSet that does match exactly, but that is only imported as a temporary series (and thereafter ignored). This can be done by defining <timeSeriesType>temporary</timeSeriesType>, the preferred way, or setting <synchLevel>9</synchLevel>.
enableCaseInsensitivity
When case insensitivity is enabled the mapping of external to internal ID's will be case insensitive during imports.
...
Allow mapping of external id's with qualifiers to internal id's where the external qualifiers are optional. Se See the following example where the parameter P.meting is mapped to the external NEERSG parameter with some external qualifiers. When the ignoreExternalQualifiersWhenMappingToInternal the ignoreExternalQualifiersWhenMappingToInternal is used in the idMapping configuration, the external parameter NEERSG will be mapped to P.meting.
...
A typical use case is using the FEWS PI Service with the EXPORT_ID_MAP_ID configured in the FEWS Web Services configuration Configuration FewsPiService.properties (deprecated since 2022.02).