...
- 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:
- unitOfMeasurement: optional property to set the unit of measurement. Default value is 'm'.
- 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.
- 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. For each exported XML file a BRO ID is required. This can either be the same as the interal internal 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:
...