-
Notifications
You must be signed in to change notification settings - Fork 71
Roadmap
This is an overview of features that are either in development or on the roadmap:
This version has been released: https://github.com/itinero/routing/blob/master/docs/releasenotes/itinero-1.1.0.md
This contains some ideas on some non-breaking extensions on top of v1.0.
- Add a weight matrix calculation algorithm that calculates edge->edge weights excluding the source-target edge weights. DONE
- Check to see if the current edge-based matrix algorithm can be replaced by this more general case. DONE
- And several other issues and ideas: Milestone for 1.1 DONE
- Meta-data on vertices: More details here.
- A way to extract parts of the network and save them as a new routerDb.
- Use the meta-data on vertices to paste networks back together by keeping node id's.
-
Move to netstandard2.0 only.
-
Move to .NET core for the functional test project: development should be possible on any platform.
-
PLANNED: Constrained routing: Routing with constraints like weight limits or vehicle size (width and height).
-
[PLANNED] Destination-only access: Handle access constraints where there is destination only access, also when using contracted graphs.
-
Support for dynamic weights per edge, for example to handle floating car data.
-
Elevation profiles: Output height profiles of calculated routes.
-
Elevation-aware routing: Routing that takes into account elevation. Think avoiding steep hills for bicycles.
-
No-go areas or maximum speeds based on areas: https://github.com/itinero/routing/issues/19
-
Alternative routes.
-
Map matching.
-
Reevaluate lua for instruction generation of fix performance issues.
-
Remove nullable booleans to describe directional information.
A collection of general ideas that may or may not end up on the final roadmap.
Just return geojson with all details included:
- Edge with start and end vertex.
- The location on the network.
- The original location.