JBBI tried re-enabling Sacramento (that was temporarily disabled in https://github.com/public-transport/transitous/commit/ad3f92bea2fbb2e28c440179781f5338e7757b41), it looks like using the proxy works for it (at least the test import works). I support for proxying was added after that first attempt?)

This release and roadmap (had not seen this section yet !) is very cool !

Question : the statement about osr looks way more confident than osr's readme. Is it production ready yet ? What about speed : is it on par with osrm speed :) ?

In the past releases, MOTIS has also taken a big leap forward to become more scalable. With 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.

This release and roadmap (had not seen this section yet !) article is very cool !

Question : the statement about osr looks way more confident than osr's readme. Is it production ready yet ? What about speed : is it on par with osrm speed :) ?

In the past releases, MOTIS has also taken a big leap forward to become more scalable. With 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.

Yes, osr made a lot of progress since the last README update. For our specific use cases, speed is a bit slower than OSRM but still very good (given you use a SSD, if not => use OSRM for now). We even have our first combined mode in osr (park & ride, but not yet supported in MOTIS). We plan to replace OSRM completely with osr as with osr we have the option for combined multi-modal street routing which is great for GBFS bike/car/scooter/etc sharing. We can also deeply integrate it into MOTIS to support access areas in GBFS and other features - where OSRM would always stay a black-box. Currently, I am working on time-dependent routing for planned elevator maintenance windows, etc which also requires a deep integration (to recalculate nigiris transfers with osrtriggered by an elevator real-time update). So if all goes as planned, we will eliminate the need for other routers and enable use cases that require deeper integration by usingosr`. That doesn't mean that other routers cannot be supported - but probably only for use cases where black-box routing is sufficient.

In the end, nobody is perfect.. so if you find bugs in osr - please report 🙂

Yes, osr made a lot of progress since the last README update. For our specific use cases, speed is a bit slower than OSRM but still very good (given you use a SSD, if not => use OSRM for now). We even have our first combined mode in osr (park & ride, but not yet supported in MOTIS). We plan to replace OSRM completely with osr as with osr we have the option for combined multi-modal street routing which is great for GBFS bike/car/scooter/etc sharing. We can also deeply integrate it into MOTIS to support access areas in GBFS and other features - where OSRM would always stay a black-box. Currently, I am working on time-dependent routing for planned elevator maintenance windows, etc which also requires a deep integration (to recalculate nigiri's transfers with osrtriggered by an elevator real-time update). So if all goes as planned, we will eliminate the need for other routers and enable use cases that require deeper integration by usingosr\. That doesn't mean that other routers cannot be supported - but probably only for use cases where black-box routing is sufficient.

In the end, nobody is perfect.. so if you find bugs in osr - please report 🙂

Yes, osr made a lot of progress since the last README update. For our specific use cases, speed is a bit slower than OSRM but still very good (given you use a SSD, if not => use OSRM for now). We even have our first combined mode in osr (park & ride, but not yet supported in MOTIS). We plan to replace OSRM completely with osr as with osr we have the option for combined multi-modal street routing which is great for GBFS bike/car/scooter/etc sharing. We can also deeply integrate it into MOTIS to support access areas in GBFS and other features - where OSRM would always stay a black-box. Currently, I am working on time-dependent routing for planned elevator maintenance windows, etc which also requires a deep integration (to recalculate nigiri's transfers with osrtriggered by an elevator real-time update). So if all goes as planned, we will eliminate the need for other routers and enable use cases that require deeper integration by usingosr. That doesn't mean that other routers cannot be supported - but probably only for use cases where black-box routing is sufficient.

In the end, nobody is perfect.. so if you find bugs in osr - please report 🙂

Yes, osr made a lot of progress since the last README update. For our specific use cases, speed is a bit slower than OSRM but still very good (given you use a SSD, if not => use OSRM for now). We even have our first combined mode in osr (park & ride, but not yet supported in MOTIS). We plan to replace OSRM completely with osr as with osr we have the option for combined multi-modal street routing which is great for GBFS bike/car/scooter/etc sharing. We can also deeply integrate it into MOTIS to support access areas in GBFS and other features - where OSRM would always stay a black-box. Currently, I am working on time-dependent routing for planned elevator maintenance windows, etc which also requires a deep integration (to recalculate nigiri's transfers with osrtriggered by an elevator real-time update). So if all goes as planned, we will eliminate the need for other routers and enable use cases that require deeper integration by using osr. That doesn't mean that other routers cannot be supported - but probably only for use cases where black-box routing is sufficient.

In the end, nobody is perfect.. so if you find bugs in osr - please report 🙂