2009/6/6 Frank Glück <[email protected]> > Hi Daniel, > > >OpenLayers is for sure a good choice to display your route. > > > >The advantage of pgRouting is that you are free in defining what you > >take as "cost". > > As "cost"? What do you mean by this?
He is saying that pgRouting has an interface (API) for changing the speed associated with any particular segment, when calculating the fastest route and / or the length of any individual segment. > > > >And you can do shortest path search in combination with > >other database queries. > > Indeed this is a very important feature for me! Be advised that nothing prevents you from using one piece of software for routing with its own data and then have a separate database for the other queries. > >Other routing approaches often have preprocessed binary formats, which > >makes them usually faster but less flexible. > > Could you please explain that a little bit more? Are the geo-data itselves > in a preprocessed binary format or only the functions? The geodata. 256MB > > Boost Let me just point out that Boost does come with utilities for importing OSM data. Writing it is non-trivial. I have put in a lot of effort into Gosmore to structure the data so that it does not need a lot of RAM and disk seeks (which are slow) are kept to a minimum. >>http://wiki.openstreetmap.org/wiki/YOURS#Route_calculation_API The YOURS source code has been checked into svn.openstreetmap.org, so you can download it and set up your own private server. Then you don't need to use the API because you can directly modify the source code.
_______________________________________________ Routing mailing list [email protected] http://lists.openstreetmap.org/listinfo/routing
