Fixes issue #38
This commit is contained in:
parent
275808d0d5
commit
e8d52c0f01
11
README.TXT
11
README.TXT
@ -77,11 +77,12 @@ preprocessing runs in three steps, all done by seperate programs.
|
||||
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'
|
||||
|
||||
'osrm-prepare file.osrm' 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.
|
||||
'osrm-prepare file.osrm file.restrictions' 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.
|
||||
|
||||
'osrm-routed' starts the server on TCP Port 5000. The
|
||||
server communicates over http and can be queried by any browser or http-capable
|
||||
|
Loading…
Reference in New Issue
Block a user