v3.9.4 - Fixed error handling

There was an issue when reading incoming error messages from the API. Now errors are formatted properly.

Full Changelog: v3.9.3...v3.9.4

v3.9.3 - Added distance for time filter fast

Added distance for time filter fast

Full Changelog: v3.9.2...v3.9.3

v3.9.2 - Added ability to customize timeout value

Previously, if sending requests took over 5 minutes, the connection was closed. This release adds a new SDK parameter, which specifies the exact timeout value in seconds.

sdk = TravelTimeSdk("APP_ID", "API_KEY", timeout=300)

Full Changelog: v3.9.1...v3.9.2

v3.9.1 - Improved time handling for time-map requests

What's changed

Slightly improved the way time was being handled in the code.

Full Changelog: v3.9.0...v3.9.1

v3.9.0 - Updated SDK to use Pydantic V2

What's changed

Reworked SDK to use Pydantic V2. In the process dropped support for Python v3.7

Full Changelog: v3.8.1...v3.9.0

v3.8.1 - Fixed flipped arrival and departure searches in time-map endpoints

What's changed

There was an issue where time-map endpoints were returning departure searches when asked for arrival, and the other way around. Now this is fixed.

Full Changelog: v3.8.0...v3.8.1

v3.8.0 - Implemented time-map WKT response

What's changed

Now traveltimepy supports WKT format response for the time-map endpoint.

Full Changelog: v3.7.1...v3.8.0

v3.7.1 - Fixed time-map GeoJSON implementation

What's changed

The previous time-map GeoJSON implementation was a bit faulty. Now it works exactly like other endpoints.

Full Changelog: v3.7.0...v3.7.1

v3.7.0 - Added distance response for time-filter-proto

What's changed

TimeFilterFastProto now supports distances calculation, in addition to travel_times

Full Changelog: v3.6.2...v3.7.0

v3.6.2 - Add level_of_detail support for time-map

What's changed

Added the option to use level_of_detail attribute in time-map. level_of_detail is used to specify how detailed the isochrone should be.

Full Changelog: v3.6.1...v3.6.2