Commit: r676: Route is now active with a small test .mp file.

Version 676 was commited by steve on 2008-08-25 19:27:07 +0100 (Mon, 25 Aug 2008) Route is now active with a small test .mp file. There are numerous problems, but it is being recognised and acted upon. You get: 1. a valid route down a road 2. a ms error box 3. a route that goes the wrong way down a road and then connects to where it should be.

I realise that no one reads this list, but for anyone that reads the archives...
Route is now active with a small test .mp file.
1. The input must be in polish .mp format 2. The file must be very small, say less than 50 roads 3. Use the flags --route --tdbfile --tdb-v4 I've only tested it with a single very small file with about 3 roads, so you may not have any luck with random files. There are many limitations there but I think we know enough to create full maps and it is just a matter of coding it up with some trial and error. The rough steps that are needed are: 1. Make it work with a .osm input file. This should be a matter of looking at how the osm to .mp converters work and doing something similar. 2. The roads need to be split into smaller areas, this shouldn't be too difficult as similar things are done already inside mkgmap. You should then be able to do a full map, but each area would be an island. To get routes from area to area you need to add records the routing section that link between areas. 3. Routing between tiles in a map set. There is a section where you need to list all the nodes on the boundaries of the map. I don't know if that is all you have to do (and make sure that there are matching nodes in the adjacent map) or if there is any else involved. ..Steve
participants (2)
-
apache@lachesis.vm.bytemark.co.uk
-
Steve Ratcliffe