Page History

...

The configuration of the BroGldAdditionServer import module is shown in the following example. It retrieves the data from the BRO GLD REST API. For documentation see: URL's publieke REST services (bro-productomgeving.nl). To switch to different BRO environment, replace the front part of the URL with https://int-publiek for demo and https://acc-publiek for acceptance.

For each imported XML file a BRO ID is required. This can either be the same as the interal locationId or (preferably) should be configured as a location attribute. The location attribute that holds the BRO ID should be mapped, using a location id function. For example:

...

The BroGldAdditionServer can import multiple XML files by specifying time series sets and a relativeViewPeriod. However, the BRO GLD doesn't have multiple parameters (in the FEWS sense) so the external BRO parameter will always be mapped to the specified only the heads in reference to NAP (for details see Basisregistratie Ondergrond Catalogus Grondwaterstandonderzoek (geostandaarden.nl)), so the external BRO parameter will always be mapped to the specified internal parameterId. This also means that the timeSeriesSets should only hold 1 parameterId.

<?xml version="1.0" encoding="UTF-8"?>
<timeSeriesImportRun xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/timeSeriesImportRun.xsd">
	<import>
		<general>
			<importType>BroGldAdditionServer</importType>
			<serverUrl>https://int-publiek.broservices.nl/gm/gld-/v1.0</</serverUrl>
			<relativeViewPeriod unit="day" start="-365" end="0"></relativeViewPeriod>
			<idMapId>IdImportBro</idMapId>
			<flagConversionsId>FlagConversionBro</flagConversionsId>
            <dataFeedId>BRO.GLD.Addition.server</dataFeedId>
			<expiryTime unit="day" multiplier="356"/>
		</general>
		<timeSeriesSet>
			<moduleInstanceId>ImportBROServer</moduleInstanceId>	
			        <properties>
            <string key="flag" value="StatusQualityControl" />
        </properties>
        <timeSeriesSet>
			<moduleInstanceId>ImportBROServer</moduleInstanceId>	
			<valueType>scalar</valueType>
			<parameterId>GW.m</parameterId>
			<locationSetId>Peilbuizen_BRO</locationSetId>
			<timeSeriesType>external historical</timeSeriesType>
			<timeStep unit="nonequidistant"/>
			<readWriteMode>read complete forecast</readWriteMode>
		</timeSeriesSet>
		<externUnit parameterId="GW.m" unit="cm+NAP"/>
	</import>
</timeSeriesImportRun>  

The above example includes the optional property "flag", which triggers a flag conversion from attributes found in the XML, supported values are:

statusQualityControl : Qualifier for individual measurements, "afgekeurd", "goedgekeurd", "nogNietBeoordeeld", "onbeslist", "onbekend"
observationType : Qualifier for a series of measurements, "reguliereMeting", "controleMeting"
statusCode : Qualifier for a series of measurements, "reguliereMeting", "controleMeting"

A simple flag conversion configuration for the statusQualityControl qualifier can be configured as follows:

<?xml version="1.0" encoding="UTF-8"?>
<flagConversions xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/flagConversions.xsd">
	<flagConversion>
		<inputFlag>
			<value>goedgekeurd</value>
		</inputFlag>
		<outputFlag>
			<name>Original/Reliable</name>
			<value>0</value>
		</outputFlag>
	</flagConversion>
	<defaultOuputFlag>
		<name>Original/Doubtful</name>
		<value>3</value>
	</defaultOuputFlag>
	<missingValueFlag>
		<name>Original/Missing</name>
		<value>9</value>
	</missingValueFlag>
</flagConversions>

The following code shows a sample BRO Gld_Addition document that can be imported:

...