Thank you, I was already wondering about the 'foot' routes of https://router.project-osrm.org/route/v1/foot/ ;-)
Thank you, tried this and OSRM Foot works now :) Yes, routing support seems to be a bit neglected in Viking. It would be helpful if this could be improved or if someone knows a way to use brouter (or other routing engines). Beyond that, Viking is a very powerful an useful tool.
Installed Viking 1.9 and copied default routing.xml to my user config file location. Routing preferences shows the list of engines listed in routing.xml (brouter, brouter Car, OSRM Bicycle, OSRM Driving, OSRM Foot, Yours: Car, Yours: Bicycle/Foot). OSRM Bicycle and OSRM Driving are working, all the others don't. Using brouter for example, shows message 'Error getting route from brouter' in status bar Is there something wrong with the config file or any idea how to get them all running (e.g. brouter)?...
Installed Viking 1.9 and copied default routing.xml to my user config file location. Routing preferences shows the list of engines listed in routing.xml (brouter, brouter Car, OSRM Bicycle, OSRM Driving, OSRM Foot, Yours: Car, Yours: Bicycle/Foot). OSRM Bicycle and OSRM Driving are working, all the others don't. Is there something wrong with the config file or any idea how to get them all running (e.g. brouter)? Thx
So far your fix seems to solve the problem. Comparing the binaries there is still a small difference between the the file created by csmatio and the one created by Matlab. But regardless, reading works from both sides, so no problem. We spent a lot of time converting handling a large data structure from MathWorks.MATLAB.NET.Arrays to csmatio and got this problem just at the end of it. Your help was therefore really appreciated. Thank you!
Hi Tobias I made some debugging and found a fix which seems to be suitable so far. In the constructor of the 'OSArrayTag' class, the '_compressed' flag is set to 'true' for the three character field name. This seems to result in a misalignment of the data. Setting '_compressed' to 'false' solved the problem for our needs so far. I'm not sure if there are any side effects and so far I didn't find an explanation in the Mat file format spec, but the Matlab 'load' method seems to be able to handle this...
Hi Tobias Thank you for fast reply. Yes, I am and I already did. But I wasn't able to locate the problem so far. I'm not familiar with the MAT file format, and also it's not obviously for me if the bug is in MatFileWriter or MatFileReader. Currently I would tend to MatFileWriter, because it can be read after it has be loaded and saved in Matlab. MatFileReader constructor fails in MatFileInputStream.ReadInt() method. Value of '_type' is 8 (MatDataTypes.miSIZE_DOUBLE or MatDataTypes.miSIZE_INT64) which...
Hi Tobias Thank you for fast reply. Yes, I am and I already did. But I wasn't able to locate the problem so far. I'm not familiar with the MAT file format, and also it's not obviously for me if the bug is in MatFileWriter or MatFileReader. Currently I would tend to MatFileWriter, because it can be read after it has be loaded and saved in Matlab. MatFileReader constructor fails in MatFileInputStream.ReadInt() method. Value '_type' is 8 (MatDataTypes.miSIZE_DOUBLE or MatDataTypes.miSIZE_INT64) which...