Ben Abelshausen

I assumed you want to resolve only to location where a vehicle is allowed to stop but you are correct, this issue is not related. I think this route should...

The turn penalty will only work when building a CH that can handle directed queries but it should also work with uncontracted networks? I looks like one of the routes...

You mean the vertex of the edge?

This could help: https://github.com/itinero/routing/blob/develop/src/Itinero/Data/Network/RoutingNetwork.cs#L226

Probably because of the way we handle the version numbering: https://github.com/itinero/routing/blob/develop/SharedAssemblyVersion.cs#L3 We use one shared file on all the projects but it could be this isn't working properly anymore with...

If you use the nuget packages to install you shouldn't have an issue with these version #s. They have no functional value except to keep track of what code was...

There is even more to be gained by removing all edges that cannot be accessed. Now they are kept in case they get trough the initial filter. The edges can...

You would need to write a bit of custom code to check if all the profiles generate only values == 0 and remove those edges. Then compressing the database should...

I would make sense to add these attributes to the output routes by default, same as is happening with the other attributes. Also, keep in mind that an OSM way...

Keep in mind that if you do a pull request to keep focus on one feature and modify as little code as possible to implement it.