Search for a command to run...
In the last years, several methods to establish surface flow velocities and river flow from camera videos have been developed and codified into software. Together with a hardware setup, these may be used to establish near real-time observations of river flow. The hardware setup used and associated quality of the camera, methods to pre-process, process and post-process the videos may all result in errors, and uncertainties. In this contribution we assess what the main sources of uncertainty are, and under what conditions these may appear, focusing on both hardware and processing methods. We do this by co-locating two different camera setups, and using two different software processing methods. For camera setups we use a very simple and low cost FOSCAM FI9900EP running at its maximum of 4Mbps and a much better quality Vivotek IB9367-EHT running at 20Mbps. As systems we use the DischargeKeeper and pyOpenRiverCam.The cameras were co-located over a significantly long period at a site in Limburg in The Netherlands, and footage analyzed with 15-minute intervals. Videos were treated with as much as possible the same settings, reprojection resolution and window. Results were compared in terms of the ability to resolve velocities (amount and quality) and the impact of post-processing. Integrated flow over a cross-section is also compared. We assess under what conditions flow and velocity estimates are robust and similar and under what conditions these diverge focusing on the platform used, light conditions, and flow conditions.Keywords: River flow monitoring, stage-discharge relationships, OpenRiverCam, DischargeKeeper, computer visionThe work leading to these results has received funding from the German Federal Ministry of Education and Research (BMBF) and the CLIENT II program (Drought-ADAPT, FKZ: 01LZ2002B) and the European Horizon Europe Programme (2021-2027) under grant agreement no. 101086209 (TEMBO Africa). The opinions expressed in the document are of the authors only and no way reflect the European Commission’s opinions. The European Union is not liable for any use that may be made of the information.