Versions Compared

Old Version 14

changes.mady.by.user Boyan Domhof

Saved on

compared with

New Version 15

changes.mady.by.user Bart Adriaanse

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The export can be used to automatically upload GLD_Addition documents at: https://basisregistratieondergrond.nl/werken-bro/producten-diensten/bronhouderportaal/

Getting BRO GLD IDs

To get the BRO GLD IDs, you need to start the registration in the BRO for a groundwater filter. To achieve this you need to upload a BRO GLD Start Registration xml file to the bronhouder portal. The bronhouder portal will give you (if the BRO GLD Start Registration xml is valid) back to GLD ID.

To make the BRO GLD Start Registration xml files, the attached tool can be used. Note: the tool itself doesn't fall under support of Deltares and it is the responsibility of the configurator to use it correctly!

maak_gld_start_registraties.zip

BRO_GLD_Addition_Server Export Configuration

...

  • chamberOfCommerceNumber: will be used to set the value of the brocom:chamberOfCommerceNumber element.
  • qualityRegime: will be used to set the brocom:qualityRegime value. Can be either IMBRO or IMBRO/A

Optional properties that can be configured:

  • skipBroValidation: default false. Before uploading the GLD_Addition document to the BRO, the XML document will be validated using the validation API of the BRO. This is an optional feature and can make the export take a lot of time. The uploaded document will also be validated again after upload by the BRO. To disable validation, set the skipBroValidation property to true.
  • splitFiles: default false. If set to true, timeseries that have 10000 or more time steps, will be splitted in files with 9999 timesteps. The BRO Portal currently doesn't support more than 9999 time steps.
  • unitOfMeasurement: optional property to set the unit of measurement. Default value is 'm'.
  • statusQualityControl: default '"goedgekeurd" allowed values are:
    "afgekeurd", "goedgekeurd", "nogNietBeoordeeld", "onbeslist", "onbekend"
  • observationType: default "reguliereMeting" allowed values are:
    "reguliereMeting", "controleMeting"
  • statusCode: default "voorlopig" allowed values are:
    "volledigBeoordeeld", "voorlopig", "onbekend"
  • processReference: default "NEN_EN_ISO22475v2006_C11v2010" allowed values are:
    "NEN5120v1991", "NEN_EN_ISO22475v2006_C11v2010", "NEN_ISO21413v2005", "NPR_ISO.TR23211v2009", "RWSgwmon", "STOWAgwst", "onbekend"
  • measurementInstrumentType: default "druksensor" allowed values are:
    "akoestischeSensor", "akoestischHandapparaat", "analoogPeilklokje", "druksensor", "elektronischPeilklokje", "opzetStuk", "radarsensor", "stereoDruksensor", "onbekend", "onbekendPeilklokje"
  • processType: default "" allowed values are:
    "Algorithm", "Manual Method", "Sensor", "Simulation", "Unknown"
  • evaluationProcedure: default "oordeelDeskundige" allowed values are:
    "brabantWater2013", "eijkelkampDataValidatiev0.0.9", "oordeelDeskundige", "PMBProtocolDatakwaliteitscontroleQC2018v2.0", "RWSAATGrondwaterv1.0", "warecoWaterDataValidatieProtocolv20200219", "onbekend"
  • airPressureCompensationType: default "monitoringnetmeting" allowed values are:
    "capillair", "gecorrigeerdLokaleMeting", "KNMImeting", "monitoringnetmeting", "putlocatiemeting", "onbekend"

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

...