Add Belgium flanders

[thiagovmdon]

Summary

Related to issue #93

This PR adds support for Belgium-Flanders to RivRetrieve via the HIC KiWIS service.

Implemented:

• new fetcher: rivretrieve/belgium_flanders.py
• package export in rivretrieve/__init__.py
• fetcher docs page: docs/fetchers/belgium_flanders.rst
• API docs integration in docs/api.rst
• cached metadata: rivretrieve/cached_site_data/belgium_flanders_sites.csv
• example usage script
• unit tests and Belgium-specific fixtures

Implementation details

Supported RivRetrieve variables:

• constants.DISCHARGE_DAILY_MEAN
• constants.STAGE_DAILY_MEAN
• constants.WATER_TEMPERATURE_DAILY_MEAN

Key behaviors:

• station metadata is fetched from the HIC KiWIS getStationList endpoint
• station names are split into station and river where the upstream format is Station/River
• virtual stations from group 260592 are excluded
• time series are discovered via KiWIS getTimeseriesList
• time series values are fetched via getTimeseriesValues
• output is standardized to RivRetrieve daily-mean DataFrames

Notes:

• area is parsed when available, but upstream HIC metadata often contains placeholder values such as 1,00 km², which are treated as missing
• docs metadata sections were added so the fetcher page includes source, API/manual, and terms-of-use information

[olivierbonte]

Hi,

Very nice to see that Flanders is being added to the list of providers!
I see that the focus now is on data from HIC, which provides data over navigable rivers. For non-navigable rivers, data is provided by the Flemish Environment Agency (VMM). They provide their data via another API endpoint (although they also use KIWIS).

For access to HIC and VMM data there is already a Python package to access these APIs called pywaterinfo, maybe the docs of this package can be of help for this implementation? I am by no means an expert on this API, but maybe @stijnvanhoey can help you out if you have any questions.

Best,
Olivier

[thiagovmdon]

Hi,

Very nice to see that Flanders is being added to the list of providers! I see that the focus now is on data from HIC, which provides data over navigable rivers. For non-navigable rivers, data is provided by the Flemish Environment Agency (VMM). They provide their data via another API endpoint (although they also use KIWIS).

For access to HIC and VMM data there is already a Python package to access these APIs called pywaterinfo, maybe the docs of this package can be of help for this implementation? I am by no means an expert on this API, but maybe @stijnvanhoey can help you out if you have any questions.

Best, Olivier

Hi @olivierbonte . It is great to hear your feedback. Our intention is to put together all those APIs to facilitate global hydrology studies (or even more local ones). I was not aware of this detail about Flanders. This is extremely handy and ww will take the documentation you send into consideration! It would be great to have both endpoints indeed!

Cheers,
Thiago

[thiagovmdon]

Hi,

Very nice to see that Flanders is being added to the list of providers! I see that the focus now is on data from HIC, which provides data over navigable rivers. For non-navigable rivers, data is provided by the Flemish Environment Agency (VMM). They provide their data via another API endpoint (although they also use KIWIS).

For access to HIC and VMM data there is already a Python package to access these APIs called pywaterinfo, maybe the docs of this package can be of help for this implementation? I am by no means an expert on this API, but maybe @stijnvanhoey can help you out if you have any questions.

Best, Olivier

[stijnvanhoey]

@olivierbonte thanks for the headsup; @thiagovmdon, nice initiative. I see in the PR you already found the documentation of VMM/HIC and the supported Timeseriesgroup_id they provide in the documentation, nice work!

[thiagovmdon]

@olivierbonte thanks for the headsup; @thiagovmdon, nice initiative. I see in the PR you already found the documentation of VMM/HIC and the supported Timeseriesgroup_id they provide in the documentation, nice work!

Thanks, @olivierbonte . Yes, we managed to implement it smoothly thanks to the documentation provided which was very detailed!