Skip to content

Releases: stadiamaps/stadiamaps-api-py

v7.0.1

13 Jun 02:15

Choose a tag to compare

Version 7.0.1 - 2025-06-12

Fixed

  • Add two missing OSRM maneuver types which were mistakenly omitted.

Full Changelog: v7.0.0...v7.0.1

v7.0.0

11 Jun 15:16

Choose a tag to compare

Added

  • Support for the v2 search (forward geocoding) endpoint! The new API includes better structure, more details, and better address formatting.
- res = api_instance.search("Telliskivi 60a/3, Tallinn, Estonia")
+ res = api_instance.search_v2("Telliskivi 60a/3, Tallinn, Estonia")

For an overview of the structural changes we've made in the V2 API,
refer to the migration guide.

Fixed

  • The maneuvers property on route responses was previously marked as required.
    However, it is possible to explicitly request routes with this field removed.
    These would fail validation and the whole request would end with an exception
    in the API client.
    This has been fixed in this version, so the property is optional.

Full Changelog: v6.3.0...v7.0.0

v6.3.0

03 Jun 08:05

Choose a tag to compare

Added

  • New fields to the time zone API responses including localized timestamps in several standard formats.

Fixed

  • Fix a bug which caused structured search bulk requests to incorrectly spell the postalcode field.

Full Changelog: v6.2.0...v6.3.0

v6.2.0

21 Apr 12:37

Choose a tag to compare

Added

  • Add documentation for the geocoding metadata query field.

Fixed

  • Removed boundary circle properties that were mistakenly added.
    They did not behave as expected, so this is a bug fix despite being a code-breaking change if you used it.
  • Added missing water layers to context.

Full Changelog: v6.1.0...v6.2.0

v6.1.0

19 Apr 02:30

Choose a tag to compare

Added

  • Support for the v2 reverse geocoding endpoint! The new API includes better structure, more details, and better address formatting.
- res = api_instance.reverse(59.444351, 24.750645)
+ res = api_instance.reverse_v2(59.444351, 24.750645)

For an overview of the structural changes we've made in the V2 API,
refer to the migration guide.

Fixed

  • Added the wheelchair property to the OSM addendum model (it was in the API response, but not explicitly modeled).
  • Fix the types of the Natural Earth and Karmashapes identifiers

Full Changelog: v6.0.0...v6.1.0

v6.0.0

07 Apr 16:10

Choose a tag to compare

Version 6.0.0 - 2025-04-07

Added

  • Support for the v2 autocomplete and place details APIs!
  • BREAKING: We have renamed the Place Details method to clarify its purpose.

If you want to keep using the v1 endpoint, you can amend your code like so:

- res = api_instance.place("Põhja pst 27")
+ res = api_instance.place_details("Põhja pst 27")

To upgrade to the v2 Place Details endpoint, which features improved address formatting,
use the new V2 method:

- res = api_instance.place("Põhja pst 27")
+ res = api_instance.place_details_v2("Põhja pst 27")

For an overview of the structural changes we've made in the V2 API,
refer to the migration guide.

Full Changelog: v5.0.0...v6.0.0

v5.0.0

20 Jan 13:15

Choose a tag to compare

Added

  • BREAKING: Renamed models containing Valhalla and Pelias in their names to be generic. These now have rout(e|ing) or geocod(e|ing) prefixes.
  • BREAKING: Added additional properties to the "main" feature properties object. This improves accessibility, but if you previously reached into additional_properties, you may need to change your code to use the new property directly.
  • Adds support for the foursquare data source.
  • Documents the elevation_interval parameter on certain routing requests.

You will now need to access the actual_instance property of API responses that return directions responses.
Aside from this, your existing code should work.

Full Changelog: v4.0.0...v5.0.0

v4.0.0

04 Sep 07:42

Choose a tag to compare

Version 4.0.0 - 2024-09-04

Added

  • Support for the OSRM format and navigation aids
  • BREAKING: To support the new format, the response type of directions APIs has changed

You will now need to access the actual_instance property of API responses that return directions responses.
Aside from this, your existing code should work.

res = api_instance.route(req).actual_instance

v3.2.1

16 Aug 09:04

Choose a tag to compare

Fixed

  • Improve modeling of bulk geocoding

v3.2.0

14 Aug 18:14

Choose a tag to compare

Added

  • Add support for bulk geocoding

Fixed

  • Isochrone request models now support all costing models