Hi Tim and Jaak, Thanks for your answers.
>The mentioned GPX and KML formats however work on geo coordinates and thus may >not suitable. I have decided to output GPX format after route calculation. This is a standard format for exchanging GPS data, and it can be easily converted. Not fully suitable, but I can manage, hopping for >(A* but most of the performance gos into disk access because mobile devices >are target and I do not want to load the whole datafiles into memory) Why don't externalize route calculation on remote server and send back data to the device? >I'm always interested in other people (in this case you - without knowing your >concrete algorithm) integration their algorithm into my library. I am using Dijkstra algorithm, downloaded somewhere and modified for my needs [1] Route calculation is processed on a remote server because I use a remote repository. >I would also prefer to separate route calculation from route description. Moreover, data structure isn't the same. I convert OSM data into edges and vertex, then I run Dijkstra and convert resulting route in GPX. >Only standard for routing results (and also requests) what I've found is >OpenLS routing XML. I have seen this website while I was looking for a standard. Good starting point :) Audrey [1] http://files.codes-sources.com/fichier.aspx?id=30362 _______________________________________________ Routing mailing list [email protected] http://lists.openstreetmap.org/listinfo/routing
