afischerdev

@devemux86 Yes, that is the plan. Because it is also needed for roundtrip #759 to avoid ambiguity. But there should be a little time for testing.

@devemux86 This variable is still in use. As before the beelinie is added when the distance is more then `waypointCatchingRange` E.g. [this](https://brouter.de/brouter-test/#map=17/37.70738/-25.50812/standard&lonlats=-25.517515,37.721379;-25.506798,37.706501) against [this](https://brouter.de/brouter-test/#map=17/37.70738/-25.50812/standard&lonlats=-25.517515,37.721379;-25.506615,37.706242). both are with `assign add_beeline true...

@alex-the-new-guy Thanks for your idea. Do you have also some code for us and some sample to check that?

@all And a question to everyone: should this move to the ongoing version 1.7.5 or is more time needed for testing?

@alex-the-new-guy Thanks for the data. I played around a bit with it, but I could not generate a similar route. I used the start and end point from the csv...

@quaelnix good point. I made some test with both logics using an old track as sample (green line, the track has some stop points, routes don't have):  You find...

BRouter uses only parts of the OSM tags. It is defined in [lookups.dat](https://github.com/abrensch/brouter/blob/master/misc/profiles2/lookups.dat) Add funicular for next generation lookups in #416

@flecken66 After a quick search in Germany, I only found Wuppertal and possibly Frankfurt Airport. There may be more that are connected to public transportation and have transitions to other...

@flecken66 > I believe users who write their own custom profiles should at least have the option to allow routing over these systems Yes, that sounds good. But it's not...

@flecken66 Ok, the size argument is gone. You are right and I could live with the 'monorails only' solution. Please give me some time, I like to test what happens...