update to new RWS WaterWebservices

[veenstrajelmer]

• ddlpy version: 0.5.0
• Python version: 3.11
• Operating System: Windows 10

Description

The RWS WaterWebservices will be updated in 2025: https://rijkswaterstaatdata.nl/projecten/beta-waterwebservices/
ddlpy has to be updated to work with the new urls and filters:

• new url: https://waterwebservices.beta.rijkswaterstaat.nl/test/METADATASERVICES/OphalenCatalogus >> https://ddapi20-waterwebservices.rijkswaterstaat.nl/METADATASERVICES/OphalenCatalogus
• HTTPError 204 in case of no data (instead of "Geen gegevens gevonden!")
• New ProcesType for distinction between verwacht/meting/astro
• also update to ProcesType in cli testcase, example script and notebook and maybe more
• how to distinguish between extremes and timeseries? >> seems to be still via Groepering
• remove list-to-str/int conversion (Kwaliteitswaardecode is now a string instead of a list), tests are in place to make sure datatypes stay constant
• consider dropping Hoedanigheid from catalog #89 >> if no stations with NAP and MSL referenced measurements >> also in new waterwebservices, data for europlatform/k13a/lichteiland are distributed over NAP and MSL: data is distributed over NAP/MSL hoedanigheid for some stations Rijkswaterstaat/wm-ws-dl#17 (comment)
• resolve all added TODO's in branch: feedback was sent to RWS on 05-12-2025, await response before continuing. Update 08-12-2025: already quite certain: bulkwaarnemingenservice can be removed, ProjectType will probably not be split in Code/Omschrijving. Dec 2025 will be for important things on the backlog (stability etc), this feedback will be considered by the RWS/DDL developers from Jan 2026 onwards, so reach out again by then. @TvLoon-RWS recommended to wait with migration to new waterwebservices at least until Jan 2026. >> continue anyway, issues were created of all remaining TODO comments
• update all docs/examples again
• juiste foutmelding parsing bij (resp.ok=False), zonder eerst resp.json() >> voor maxaantalwaarnemingen overschreden
• consider removing check for succesvol since we now pass the complete resp.text as an error. However, update Single source of truth for succesfulness of a request Rijkswaterstaat/WaterWebservices#14 with the new ddlpy response (request to clean up resp.text)
• create waterwebservices issue for request_invalid_periode_format test
• update changelog

After release update:

• dfm_tools: update dfm_tools after ddlpy update to new waterwebservices dfm_tools#1300
• hatyan: update hatyan after ddlpy update to new waterwebservices hatyan#410
• kenmerkendewaarden: update kenmerkendewaarden after ddlpy update to new waterwebservices Deltares-research/kenmerkendewaarden#260
• check if all "DDL/waterwebservices api improvements" tasks in DDL improvements (data and waterwebservices) Deltares-research/kenmerkendewaarden#4 are ticked by new WaterWebservices
• getijverandering scripts?

[physje]

It looks like the old RWS WterWebservices has stopped working/giving outdated information.
When will the rws-ddlpy-package on pypi.org be updated to the new RWS WterWebservices?

[veenstrajelmer]

The RWS WaterWebServices is still available and this is still the most up to date source to retrieve data from. The new beta WaterWebServices is still in beta and not suitable for operational usage yet. This issue will be picked up again as soon as the new WaterWebServices is ready for production.

If you are encountering issues with ddlpy, please define the exact problem you are encountering in a dedicated issue. If you are encountering issues with the data (or data availability), please report it at the RWS Servicedesk Data and @TvLoon-RWS or a colleague will pick this up. You can also post a question about the WaterWebservices at the new discussion forum (I just noticed a link to this page in the beta-waterwebservices RWS page). I have also posted a question there: Rijkswaterstaat/WaterWebservices#4

[TBalcik-RWS]

@physje
Thank you for reaching out and letting us know. We're sorry to hear that you're experiencing issues with outdated information from our webservice.

To help us investigate this further, could you please provide the specific URL you're using, along with the body?
This will help us identify where the data may be outdated and resolve the issue as quickly as possible.

Kind regards,

Tahir Balcik

[physje]

@TBalcik-RWS the problem is solved with help of RWS.
Coordinates were changed.
Message M250920430 in RWS servicedesk.

[veenstrajelmer]

More information in Rijkswaterstaat/WaterWebservices#6

[TBalcik-RWS]

@physje
I'm glad to hear the problem has been resolved! If you have any further questions, feel free to ask them.