You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OSMnx v2.0.0 is targeted for release later in 2024. This major release includes some breaking changes (including removing previously deprecated functionality) that are not backwards compatible with v1. This issue provides guidance on migrating from v1 to v2. It will be updated as more details are finalized.
Migrating to v2
To ensure your code is fully compatible with OSMnx v2, install the latest v1 release (currently v1.9.2) then run your code. The latest v1 release will remain compatible with the v1 API, but any deprecated functionality you're using will issue a FutureWarning with simple guidance to make it v2 compatible.
Key changes
For now, see the changelog for details and see the v2 documentation here.
controller.py:431: FutureWarning: The `north`, `south`, `east`, and `west` parameters are deprecated and will be removed in the v2.0.0 release. Use the `bbox` parameter instead. See the OSMnx v2 migration guide: gboeing/osmnx#1123 polygon = ox.utils_geo.bbox_to_poly(north, south, east, west) controller.py:733: FutureWarning: The `north`, `south`, `east`, and `west` parameters are deprecated and will be removed in the v2.0.0 release. Use the `bbox` parameter instead. See the OSMnx v2 migration guide: gboeing/osmnx#1123 graph = ox.graph_from_bbox()
`north`, `south`, `east`, `west` parameters are deprecated use `bbox` as tuple parameter instead
Overview
OSMnx v2.0.0 is targeted for release later in 2024. This major release includes some breaking changes (including removing previously deprecated functionality) that are not backwards compatible with v1. This issue provides guidance on migrating from v1 to v2. It will be updated as more details are finalized.
Migrating to v2
To ensure your code is fully compatible with OSMnx v2, install the latest v1 release (currently
v1.9.2
) then run your code. The latest v1 release will remain compatible with the v1 API, but any deprecated functionality you're using will issue a FutureWarning with simple guidance to make it v2 compatible.Key changes
For now, see the changelog for details and see the v2 documentation here.
Work currently in progress at #1106.
The text was updated successfully, but these errors were encountered: