{"action":"created","issue":{"url":"https://api.github.com/repos/Project-OSRM/osrm-backend/issues/1624","labels_url":"https://api.github.com/repos/Project-OSRM/osrm-backend/issues/1624/labels{/name}","comments_url":"https://api.github.com/repos/Project-OSRM/osrm-backend/issues/1624/comments","events_url":"https://api.github.com/repos/Project-OSRM/osrm-backend/issues/1624/events","html_url":"https://github.com/Project-OSRM/osrm-backend/issues/1624","id":102418759,"number":1624,"title":"Release planning","user":{"login":"TheMarex","id":606968,"avatar_url":"https://avatars.githubusercontent.com/u/606968?v=3","gravatar_id":"","url":"https://api.github.com/users/TheMarex","html_url":"https://github.com/TheMarex","followers_url":"https://api.github.com/users/TheMarex/followers","following_url":"https://api.github.com/users/TheMarex/following{/other_user}","gists_url":"https://api.github.com/users/TheMarex/gists{/gist_id}","starred_url":"https://api.github.com/users/TheMarex/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/TheMarex/subscriptions","organizations_url":"https://api.github.com/users/TheMarex/orgs","repos_url":"https://api.github.com/users/TheMarex/repos","events_url":"https://api.github.com/users/TheMarex/events{/privacy}","received_events_url":"https://api.github.com/users/TheMarex/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/Project-OSRM/osrm-backend/labels/Discussion","name":"Discussion","color":"444444"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-08-21T16:45:06Z","updated_at":"2015-08-22T19:55:47Z","closed_at":null,"body":"We are planning to use OSRM as a base and implement a different pre-processing\r\nalgorithm that uses the modern three phase approach of `preparation`, `customization` and `query`. Currently customization and preparation are mixed together, which means you need to re-run the whole pre-processing for each profile update. Three phase approaches move the main work to the initial profile independent pre-processing step, while the customization should be as fast as possible.\r\n\r\nWork on this will start in a different repository in parallel to `5.0.0`. It is unclear at the moment if this can fully replace CH. As such it is yet undecided if this will replace the CH-based OSRM (e.g. `6.0.0`) or whether we can support both approaches. We will try to keep the overall tooling and API as compatible as possible.\r\n\r\n### OSRM 4.8.0\r\n\r\n- Preliminary raster data support\r\n- TSP support\r\n- Partial CH support (pre-processing + query)\r\n- Restructuring of the `osrm-prepare`:\r\n  - split out the geometry compression from EBGF\r\n  - add tests for geometry compression\r\n\r\n### OSRM 4.9.0\r\n\r\n- Traffic data integration\r\n  - fast ingestion of history and 'live' edge weights\r\n  - support in `match` plugin to establish OSM mappings\r\n- extend `segment_function` for finer grained weight data\r\n- Investigate low hanging fruit to improve bike and pedestrian routing\r\n- Further refactors and tests for pre-processing components\r\n\r\n### OSRM 5.0.0\r\n\r\nLast CH based release, probably only minor features and bug-fix releases from this point.\r\nWe can use this opportunity to break backwards compatibility since it is a major version bump.\r\n\r\n- API cleanup\r\n- Preparations for different pre-processing algorithm\r\n  - Maybe restructure pre-processing utils\r\n\r\n### OSRM 5.x.y\r\n\r\nOne of the bigger weaknesses of OSRM is the guidance. There are a few things to unlock to do good car guidance:\r\n\r\n- Support for lanes\r\n- Do more work in pre-processing to identify complex intersections and generate more\r\n  sensible turn instructions\r\n\r\nObviously bike/pedestrian guidance is a whole different beast, but we will try to keep it as\r\ngeneral as possible.\r\n\r\n/cc @lbud @daniel-j-h @chaupow @emiltin @freenerd @danpat "},"comment":{"url":"https://api.github.com/repos/Project-OSRM/osrm-backend/issues/comments/133747717","html_url":"https://github.com/Project-OSRM/osrm-backend/issues/1624#issuecomment-133747717","issue_url":"https://api.github.com/repos/Project-OSRM/osrm-backend/issues/1624","id":133747717,"user":{"login":"emiltin","id":66034,"avatar_url":"https://avatars.githubusercontent.com/u/66034?v=3","gravatar_id":"","url":"https://api.github.com/users/emiltin","html_url":"https://github.com/emiltin","followers_url":"https://api.github.com/users/emiltin/followers","following_url":"https://api.github.com/users/emiltin/following{/other_user}","gists_url":"https://api.github.com/users/emiltin/gists{/gist_id}","starred_url":"https://api.github.com/users/emiltin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/emiltin/subscriptions","organizations_url":"https://api.github.com/users/emiltin/orgs","repos_url":"https://api.github.com/users/emiltin/repos","events_url":"https://api.github.com/users/emiltin/events{/privacy}","received_events_url":"https://api.github.com/users/emiltin/received_events","type":"User","site_admin":false},"created_at":"2015-08-22T19:55:47Z","updated_at":"2015-08-22T19:55:47Z","body":"Ok, so it's correctly understood that the customization phase will allow you to change edge weights, but not the network? Meaning it can be used for fast updates based on things like live traffic data or opening hours (diffrent parks might open/close at different times..), while updates to the OSM network will require a rerun of the prepation phase as well (ie a full update)?\r\n"}}