Ben Abelshausen

This is definitely not intentional, routes are supposed to be identical when the same profile is used. Alternative routes are not supported by using the same profile, the only thing...

A standard .NET dictionary/array is limited in size. Replacing this by HugeDictionary could fix the issue: https://github.com/itinero/routing/blob/develop/src/Itinero/Algorithms/Contracted/Dual/FastHierarchyBuilder.cs#L19 https://github.com/itinero/routing/blob/develop/src/Itinero/Algorithms/Contracted/Dual/FastHierarchyBuilder.cs#L20 https://github.com/itinero/routing/blob/develop/src/Itinero/Algorithms/Collections/HugeDictionary.cs Will try to do this asap. It's strange however that I...

FYI, I'm testing with europe currently. The fix done does seem to solve the issue you were having but I ran into another issue:  Something is going wrong during...

Sorry I don't have time to review this in much detail. You basically need to add: - Vertices and their locations. - Edges between the vertices with a profileId -...

Cannot reproduce this in the latest version.

In the luas there is a itinero.log function, that's about it for debugging features I'm afraid. As for the instructions you should also still be able to do that in...

You should be able to use this one: https://github.com/itinero/routing/blob/develop/src/Itinero/Navigation/Instructions/UnimodalInstructionGenerator.cs But there is currently no default implement I'm afraid.

This seems to be working but in the meantime we're at .NET core 3.1 and it's the LTS version so best to support that instead.

Can you provide a sample feed or build a unittest that simulates this? Will make it a lot easier to track down this issue...

Sorry, maintaining this in my spare time so I didn't have to to check this. Are you using mono on OSX/Linux or .NET on Windows?