Felix Gündling

- [ ] include RabbitMQ - [ ] batching of RI Basis messages

This seems to help. Better: the routing response contains two flags "end reached" (earlier / later). ``` diff --git a/base/core/src/access/time_access.cc b/base/core/src/access/time_access.cc index 9c61cea..73409b3 100644 --- a/base/core/src/access/time_access.cc +++ b/base/core/src/access/time_access.cc @@ -26,10...

modules/path/src/prepare/schedule/stations.cc

Currently, GTFS-RT in MOTIS requires external scripts for download and updates. This can be automated in MOTIS.

Parse `wheelchair_accessible` and `bikes_allowed` attributes from GTFS and make them enforcable in the search API / UI. - [ ] Parse `wheelchair_accessible` and `bikes_allowed` as attributes - [ ] Add...

 from: `52.42865;10.786206` to: `52.535542;13.198407999999999` DELFI GTFS dataset from 2020-05-15

Transfers in `transfers.txt` from X to X (reflexive) should be considered the transfer time of this stop.

The attribute `platform_code` in `stops.txt` needs to be translated into platform rules in MOTIS' schedule.raw file.

Currently, MOTIS does not consider `frequencies.txt`: https://developers.google.com/transit/gtfs/reference#frequenciestxt However, nearly no timetable seems to have this file.

## Cover letter Describe in plain language the motivation (bug, feature, etc.) behind the change in this PR and how the included commits address it. Fixes #ISSUE-NUMBER, Fixes #ISSUE-NUMBER, ......