15.02.2024 | Frederik Ramm
Our project-internal download server, which provides OSM data with full metadata, has been upgraded to use OAuth2 in preparation for the upcoming shutdown of OSMF’s support for OAuth1.0a.
(For those who are not aware – the public “no login required” download server does not publish the author and timestamp of modifications in order to comply with data protection; the project-internal server requires an OSM login, ensuring that users have consented to OSM’s policies, including a data protection clause.)
In fact, we had been using OAuth1.0, not 1.0a, until now, which was discontinued last weekend, causing a service interruption on the internal download server for a few days.
However, this issue has been resolved, and those who use automated downloads with a cookie will need to update their oauth_cookie_client.py and obtain a new cookie as explained on the GitHub page.