Hi wes, thanks you for the review. If I recollect correctly, the ids should refer to the OSM database, so be global ids over the whole world, rather than indices in the connectivity matrix (which is a sample of the OSM database).
Great package you have here, working perfectly for what i need! thank you for taking the time to upload.
I am having a few problems with the route planner though. when i take the node id out of the parsed osm file i get a big number such as 1151088456 but i get an eorror message saying source node index invalid. if i randomly pick one of the small numbers out of the connectivity matrix i can get it working but i have no idea how to relate to these locations to there real world position untill i run it and see where they appear.
any advice on where i'm going wrong?
thanks in advance