docs: add deprecation notice

docs/autodocs.rst

@@ -1,3 +1,8 @@
+.. attention::
+
+   With the release of the ohsome API v2 the ohsome API v1 is reaching end-of-life in September 2026.
+   To migrate to ohsome API v2, refer to the `official documentation <https://docs.ohsome.org/ohsome-api/>`_.
+
 Autogenerated Documentation
 ===========================
 

docs/boundaries.rst

@@ -1,3 +1,8 @@
+.. attention::
+
+   With the release of the ohsome API v2 the ohsome API v1 is reaching end-of-life in September 2026.
+   To migrate to ohsome API v2, refer to the `official documentation <https://docs.ohsome.org/ohsome-api/>`_.
+
 Boundaries
 ==========
 

docs/endpoint-visualisation.rst

@@ -1,3 +1,8 @@
+.. attention::
+
+   With the release of the ohsome API v2 the ohsome API v1 is reaching end-of-life in September 2026.
+   To migrate to ohsome API v2, refer to the `official documentation <https://docs.ohsome.org/ohsome-api/>`_.
+
 API Endpoints Visualisations
 ============================
 

docs/endpoints.rst

@@ -1,3 +1,8 @@
+.. attention::
+
+   With the release of the ohsome API v2 the ohsome API v1 is reaching end-of-life in September 2026.
+   To migrate to ohsome API v2, refer to the `official documentation <https://docs.ohsome.org/ohsome-api/>`_.
+
 API Endpoints
 =============
 

docs/filter.rst

@@ -1,3 +1,8 @@
+.. attention::
+
+   With the release of the ohsome API v2 the ohsome API v1 is reaching end-of-life in September 2026.
+   To migrate to ohsome API v2, refer to the `official documentation <https://docs.ohsome.org/ohsome-api/>`_.
+
 Filter
 ======
 

docs/group-by.rst

@@ -1,3 +1,8 @@
+.. attention::
+
+   With the release of the ohsome API v2 the ohsome API v1 is reaching end-of-life in September 2026.
+   To migrate to ohsome API v2, refer to the `official documentation <https://docs.ohsome.org/ohsome-api/>`_.
+
 Grouping
 ========
 The grouping end points are available for every aggregation resource (count, length, perimeter, 

docs/http-response-status.rst

@@ -1,3 +1,8 @@
+.. attention::
+
+   With the release of the ohsome API v2 the ohsome API v1 is reaching end-of-life in September 2026.
+   To migrate to ohsome API v2, refer to the `official documentation <https://docs.ohsome.org/ohsome-api/>`_.
+
 HTTP Response Status
 ====================
 

docs/index.rst

@@ -3,6 +3,11 @@
    You can adapt this file completely to your liking, but it should at least
    contain the root `toctree` directive.
 
+.. attention::
+
+   With the release of the ohsome API v2 the ohsome API v1 is reaching end-of-life in September 2026.
+   To migrate to ohsome API v2, refer to the `official documentation <https://docs.ohsome.org/ohsome-api/>`_.
+
 .. image:: https://heigit.org/wp-content/uploads/2018/08/ohsome.png
    :width: 75%
    :align: center

docs/response-parameters.rst

@@ -1,3 +1,8 @@
+.. attention::
+
+   With the release of the ohsome API v2 the ohsome API v1 is reaching end-of-life in September 2026.
+   To migrate to ohsome API v2, refer to the `official documentation <https://docs.ohsome.org/ohsome-api/>`_.
+
 Response Parameters
 ===================
 

docs/time.rst

@@ -1,3 +1,8 @@
+.. attention::
+
+   With the release of the ohsome API v2 the ohsome API v1 is reaching end-of-life in September 2026.
+   To migrate to ohsome API v2, refer to the `official documentation <https://docs.ohsome.org/ohsome-api/>`_.
+
 Time
 ====
 
@@ -31,4 +36,4 @@ detailed information on timestamp formats and how to use the earliest/latest tim
 .. note:: If you use the time interval syntax and use an end timestamp that does not perfectly align with the given start
           timestamp and period, you will get a response where the last result has as an end timestamp value which is the
           start timestamp plus a multiple of the period, and not one equal to the given end time. For example, if you
-          use ``2010-01-01/2012-02-01/P1Y``, the actually used final timestamp will be ``2012-01-01``.
+          use ``2010-01-01/2012-02-01/P1Y``, the actually used final timestamp will be ``2012-01-01``.