...
In the below mentioned cases this functionality can (not) be used.
| Case | Description | Yes | No | Solution |
|---|---|---|---|---|
| 1 | A location-ID was changed by a data provider |
| X | Solve this by regular 'id-mapping' functionality for importing the data | |
| 2 | I made a typo in a location-ID, parameter-ID or qualifier-ID | X |
Create an overruling *.CSV file (for only those IDs with the typo) which is referred to in the LocationSets.xml, Parameter.xml or Qualifier.xml as in the examples below. Change the rest of your configuration referring to this obsolete IDs as well. | ||
| 3 | My location-IDs are not consistent with the IDs used by my data-provider | X |
Create an overruling *.CSV file (for only those IDs) which is referred to in the LocationSets.xml as in the examples below. Change the rest of your configuration referring to this obsolete IDs as well. | |
| 4 | A location-name is not up-to-date anymore |
| X | Solve this by editing the locations.xml or csv file and update the name attribute or field. | |
| ... | ... |
Configuration examples
XML Files
...
| Code Block | ||
|---|---|---|
| ||
<?xml version="1.0" encoding="UTF-8"?>
<locationSets xmlns="http://www.wldelft.nl/fews"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.wldelft.nl/fews httphttps://fewsfewsdocs.wldelftdeltares.nl/schemas/version1.0/locationSets.xsd" version="1.1">
<persistentIdsCsvFile>
<file>persistentLocationIds.csv</file>
<configId>%CONFIG_ID%</configId>
<persistentId>%PERSISTENT_ID%</persistentId>
</persistentIdsCsvFile>
<locationSet id="csv">
<csvFile>
<file>locations.csv</file>
<id>%ID%</id>
<x>%x%</x>
<y>%y%</y>
</csvFile>
</locationSet>
|
...
| Code Block | ||
|---|---|---|
| ||
<?xml version="1.0" encoding="UTF-8"?> <parameters xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews httphttps://fewsfewsdocs.wldelftdeltares.nl/schemas/version1.0/parameters.xsd" version="1.0"> <persistentIdsCsvFile> <file>persistentParameterIds.csv</file> <configId>%CONFIG_ID%</configId> <persistentId>%PERSISTENT_ID%</persistentId> </persistentIdsCsvFile> <parameterGroups> <displayUnitConversionsId>DisplayUnitConversions</displayUnitConversionsId> |
...
| Code Block | ||
|---|---|---|
| ||
<?xml version="1.0" encoding="UTF-8"?> <qualifiers xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews httphttps://fewsfewsdocs.wldelftdeltares.nl/schemas/version1.0/qualifiers.xsd"> <persistentIdsCsvFile> <file>persistentQualifierIds.csv</file> <configId>%CONFIG_ID%</configId> <persistentId>%PERSISTENT_ID%</persistentId> </persistentIdsCsvFile> <qualifier id="a"/> <qualifier id="b"/> </qualifiers> |
...
| Code Block | ||
|---|---|---|
| ||
<?xml version="1.0" encoding="UTF-8"?> <moduleInstanceDescriptors xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews httphttps://fewsfewsdocs.wldelftdeltares.nl/schemas/version1.0/moduleInstanceDescriptors.xsd" version="1.0"> <persistentIdsCsvFile> <file></file> <configId></configId> <persistentId></persistentId> </persistentIdsCsvFile> <!-- importing --> <moduleInstanceDescriptor id="ImportQMA"> <moduleId>TimeSeriesImportRun</moduleId> </moduleInstanceDescriptor> <moduleInstanceDescriptor id="ImportMM3PCSV"> <moduleId>TimeSeriesImportRun</moduleId> </moduleInstanceDescriptor> |
CSV file(s)
To make it still possible for Delft-FEWS to resolve the location/parameter/qualifier and module instances in the database or archive, you have to create CSV files with two columns that maps the config-id to the original persistent database/archive id. The overruling *.CSV file(s) should look like this:
...
IMPORTANT REMARK: When one of these files is used, make sure the mentioned configuration-id is used throughout the complete configuration!!