Open Source Routing Machine - C++ backend
Go to file
2010-07-23 13:00:16 +00:00
Contractor kdtree usage simplified and dropped intermediate data structures 2010-07-14 16:29:18 +00:00
DataStructures Make SConscript work with eclipse plugin 2010-07-21 15:29:41 +00:00
Docs Additional road network extractor that works in external memory. 2010-07-15 14:45:43 +00:00
HttpServer Lat/Lon mixed up in output of locate command. Thanks to Ted Rosenbaum. 2010-07-23 13:00:16 +00:00
AUTHORS.TXT Initial Import. 2010-07-09 09:05:40 +00:00
createHierarchy.cpp Initial Import. 2010-07-09 09:05:40 +00:00
extractLargeNetwork.cpp Replacing many includes by a single one 2010-07-20 13:16:36 +00:00
extractNetwork.cpp Removed redundant code for extractors 2010-07-20 09:46:52 +00:00
LICENCE.TXT Initial Import. 2010-07-09 09:05:40 +00:00
README.TXT changing build management to scons 2010-07-20 13:33:06 +00:00
routed.cpp kdtree usage simplified and dropped intermediate data structures 2010-07-14 16:29:18 +00:00
SConstruct Minor fixes in Scons script 2010-07-23 12:34:15 +00:00
typedefs.h Initial Import. 2010-07-09 09:05:40 +00:00

Compilation
---

Compiling the source code is easy. If you are running a decent linux 
installing dependencies and running make should suffic. Make sure the following
dependencies are installed:

 - Boost		1.37+
 - kdtree++	    0.7+ (0.62 does not work with g++ 4.0+)
 - sparsehash   1.4+
 - g++			4.4+
 - libxml2
 - scons 		1.20
 - stxxl		1.2.1+

Building the binaries is done by using scons. It should check for required
libraries and header files and report missing ones.

Once the dependencies are properly installed running 'scons' should build the 
binaries. The Sconstruct has been built for Ubuntu 10.04, but it should work 
under any recent Linux. 

Running the Server
---
Running the server requires preprocessing data from Openstreetmap. To do so you
you need to acquire an .osm file. Beware of the world file, because you need
serious computing power to preprocess it. Start with a smaller country. The
preprocessing runs in three steps, all done by seperate programs.

'extractNetwork file.osm' extracts the road network of an osm file. This is
necessary, because the osm data is not made to support fast routing out of the
box. The output of the step is a file called 'file.osrm'

'createHierarchy file.osmr' preprocesses the road network and computes additional
information that is exploited later to speed up the path computation. The output
of this step consists of two file 'file.osrm.hsgr' and 'file.osrm.nodes'. The first
file is the so-called hierarchy that speeds up the path computation while the
latter one carries (among other things) geographical information.

'routed file.osmr.hsgr file.osm.hsgr' starts the server on TCP Port 5000. The
server communicates over http and can be queried by any browser or http-capable
command line tool. The server responds with KML-formatted output.Assume the 
server is installed on machine localhost and a map containing the Netherlands 
has been installed. Computing a route from Amsterdam to Den Haag can be done by
calling 
        http://localhost:5000/route&52.370197&4.890444&52.048167&4.3175
which gives a shortest (fastest) route between the two points. To locate a
point in the map that is nearest to a given coordinate use the following call
        http://localhost:5000/locate&52.048167&4.3175