|
| 1 | +--- |
| 2 | +layout: post |
| 3 | +title: "MOTIS v0.12: triptix GmbH + NRW Mobidrom" |
| 4 | +date: 2024-06-16 21:30:00 +0200 |
| 5 | +categories: release |
| 6 | +author: felixguendling |
| 7 | +version: 0.12.7 |
| 8 | +--- |
| 9 | + |
| 10 | +It's been a while since the last update. MOTIS has seen countless improvements and new features since then. This news will give a short overview. But before we go into the details, I am thrilled to announce a freshly formed collaboration between the newly founded [triptix GmbH](https://triptix.tech) which offers professional services around MOTIS and [NRW Mobidrom GmbH](https://www.mobidrom.nrw) in Düsseldorf, Germany. Mobidrom will offer data and routing services for the German state North Rhine-Westphalia. MOTIS is going to be one of the core building blocks of NRW Mobidrom's routing services. With this collaboration, we will jointly bring MOTIS to the next level by implementing some of the most important items from the [MOTIS potential GitHub issue](https://github.com/motis-project/motis/issues/452). |
| 11 | + |
| 12 | +The following two features from the [NRW.Mobidrom](https://www.mobidrom.nrw) + [triptix GmbH](https://triptix.tech) colaboration are already available with this release: |
| 13 | + |
| 14 | +- routing with a filter for bike carriage |
| 15 | +- limiting the number of transfers |
| 16 | + |
| 17 | +The collaboration roadmap contains further improvements in all areas: |
| 18 | + |
| 19 | +- via routing (routing via an ordered list of given stops) |
| 20 | +- configuring a minimal transfer time and transfer time factors to allow for faster or transfers with an extra buffer based on the user's preference |
| 21 | +- a more convenient configuration format (upgrading from INI to JSON/Yaml) |
| 22 | +- implementing real-time monitoring (e.g. with Grafana as destination) |
| 23 | +- Improving cloud readiness through different measures such as allowing MOTIS to start with just the pre-processed data without having to access the `input` folder |
| 24 | +- Improved support for GBFS such as respecting zones where the vehicle should not be parked |
| 25 | + |
| 26 | +<p align="center" style="margin: 50px 0px"> |
| 27 | + <a href="https://www.initse.com"> |
| 28 | + <img src="/assets/mobidrom_logo.png" alt="NRW Mobidrom Logo" style="width: 200px" /> |
| 29 | + </a> |
| 30 | +</p> |
| 31 | + |
| 32 | +## New Stree Routing `osr` |
| 33 | + |
| 34 | +In the past releases, MOTIS has also taken a big leap forward to become more scalable. With [`osr`](https://github.com/motis-project/osr), we have now the most memory-efficient street routing. It supports wheelchair routing, pedestrian routing, bike routing and car routing. We are fully committed to this routing now and will existing use cases such as park and ride or sharing mobility (`gbfs` module) to `osr`. This will enable us to provide better routing results and with less preprocessing time and a **10x reduced memory** usage. |
| 35 | + |
| 36 | + |
| 37 | +## New GeoCoding / Address Auto Complete `adr` |
| 38 | + |
| 39 | +The new `adr` module by [triptix GmbH](https://triptix.tech) (licensed under the AGPL v3 license) provides planet wide address autocomplete and geo coding in under 8 GB of RAM with fast response times, fuzzy string matching, as well as house number granularity. |
| 40 | + |
| 41 | +<p align="center" style="margin-bottom: 30px"> |
| 42 | + <a href="https://www.initse.com"> |
| 43 | + <img src="/assets/triptix_logo.svg" alt="triptix GmbH Logo" style="width: 140px" /><br> |
| 44 | + triptix GmbH |
| 45 | + </a> |
| 46 | +</p> |
| 47 | + |
| 48 | + |
| 49 | +## New Routing Core |
| 50 | + |
| 51 | +The new routing core is now the default and the old routing core has been removed. We recommend to upgrade to the lastest release to make full use of the speed gains we have achieved in the past releases. MOTIS now allows to filter the modes of transportation for each routing query. |
0 commit comments