https://github.com/openplannerteam/itinero-tiled-routing

A repository to focus the work on tiled-routing in Itinero.
https://github.com/openplannerteam/itinero-tiled-routing

openstreetmap routing tiles

Last synced: 5 days ago
JSON representation

A repository to focus the work on tiled-routing in Itinero.

• Host: GitHub
• URL: https://github.com/openplannerteam/itinero-tiled-routing
• Owner: openplannerteam
• License: apache-2.0
• Created: 2017-08-04T09:08:20.000Z (over 7 years ago)
• Default Branch: develop
• Last Pushed: 2022-06-22T21:07:52.000Z (over 2 years ago)
• Last Synced: 2024-06-19T11:29:24.121Z (5 months ago)
• Topics: openstreetmap, routing, tiles
• Language: C#
• Homepage:
• Size: 67.7 MB
• Stars: 2
• Watchers: 4
• Forks: 2
• Open Issues: 10
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.md
  • Roadmap: docs/ROADMAP.md

Awesome Lists containing this project

README

        
# routing2

**this is ongoing work on the next version of Itinero, if you want routing right now, please go [here](https://github.com/itinero/routing)**

[![Build status](https://build.anyways.eu/app/rest/builds/buildType:(id:anyways_Openplannerteam_ItineroTiledRouting)/statusIcon)](https://build.anyways.eu/viewType.html?buildTypeId=anyways_Openplannerteam_ItineroTiledRouting)  

A new temporary repository for v2 routing core, being tile-based.

This is part of the work done by the awesome [open planner team](https://openplanner.team/).

## Goals of this project

To consume routable tiles:

![Image of tiles for ghent](./docs/routable-tiles-ghent.png)

More detailed goals are:

- Experiment with tiled-routing.

- Build a fully functioning prototype of what Itinero 2 should be and:

  - Merge this with the current routing core when finished.

  - Or transplant the most valuable concepts over to the current routing core without breaking too much.

- Experiment to see if all the current features of the routing core can be implemented using Itinero 2's new concepts.

  - Island detections is one, how to do this when using multiple tiles?

  - Configurable profiles and changes to profiles?

  - Preprocessing & updating data.

## Requirements on top of what Itinero is now:

The main thing is to build a tile-based datastructure that replaces (or expands) the current routerdb concept. This should also enable distributed preprocessing of the data. It would be awesome to:

- Live load updates, meaning we can have immidate updates to the routing graph.

- We can add any data to the edges and make this configurable:

  - Distance.

  - Custom costs.

- We can add any data to the vertices and make this configurable:

  - Turn costs.

  - Intersection costs.

  - Meta data.

## Status

- [x] Build a basic data structures in tiled form.

  - [x] Get this done for vertices.

  - [x] Get this done for edges.

  - [ ] Add support for turn-restrictions.

  - [x] Load tiles on demand.

- [x] Experiment with routing algorithms on top of this.

- [x] Build a proper resolving algorithm and verify performance.