Hallo!

Thanks for your answer.

No problem. I was able to mix a possible helpful answer with some advertising ;-)

The route calculation is already done, I have an ordered list of nodes, relations and links ("extracts" of a way) describing the path to follow.
I am looking for specifications describing a route. Ad example:
<route>
   <node ... />
   <link ... />
   <node ... />
   <link ... />
   <relation ... />
   <link ... />
   <node ... />
   ...
</route>

In my system a route internal consists of a list of node ids (you can also resolve ways and relations to list of ways so our result are similar). The mentioned GPX and KML formats however work on geo coordinates and thus may not suitable.

I would also prefer to separate route calculation from route description. Because the result of the routing process is not directly a driving description. To get a good driving description one needs to postprocess the result of the routing algortihm. Because of that I had separated routing calculation (which should be exchangeable) and postprocessing (in the beginnings).

In such circumstances a standard OSM route description may be useful.

I have tried to find something like that on google, but unsuccessfully. Maybe I have missed a point...

See above. I could also envision some need for this. Imn my case the format is defined by C++ classes.

Since my current routing alorithm is slow (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) I'm always interested in other people (in this case you - without knowing your concrete algorithm) integration their algorithm into my library.

Advantages:
* You get map drawing for free
* You can street and poi name lookup for free
* You get all that *.osm preprocessing for free (at least you get a simpler API) * You get/can share the route postprocessing for free (there is not yet that much to share)

My problem is lack of time and I assume to geta state of the art routing agortihm also take much time. SHaring code is a way to geerate win-win situation and relax or solve time constraints :-)

--
Gruß...
   Tim



_______________________________________________
Routing mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/routing

Reply via email to