I'm not sure what your use case is.
We use the Stata implementation from S.Huber and C. Rust to do static routing.
That is, we have a static list of starting points and ending points that we
route in batch. You do have to build your routing maps first, and this takes a
lot of memory, although
My experience is probably with a slightly older version of OSRM, but I found
that you have to have actual physical RAM (like 64G) to do the map extract.
Creating a big swap space isn't sufficient. Some people advise doing the
extract on an AWS cloud computer.
Bryan Sayer
4 GB or RAM.
Is there anyway way to successfully prepare the files ? Perhaps by downloading
them ready yet ?
Thanks for your answer.
Didier
Le jeu.09/08/18 à 18:15, Sayer, Bryan a écrit :
When I had that problem it was due to lack of memory. For the United States, I
had to have 64 GB
When I had that problem it was due to lack of memory. For the United States, I
had to have 64 GB of memory prepare, though I was doing it through a Stata
interface, not directly.
From: Didier Doumerc
Sent: Thursday, August 9, 2018 11:53:39 AM
To:
18, 2018 12:25 PM
To: Sayer, Bryan <bsa...@s-3.com>
Cc: Mailing list to discuss Project OSRM <osrm-talk@openstreetmap.org>
Subject: Re: [OSRM-talk] calculation of jump distances
Hi Bryan,
OSRM uses an R-Tree (https://en.wikipedia.org/wiki/R-tree) to do a nearest
neighbour s
Hi,
We are calculating distances between an U.S. census tract centroid and
hospitals. A tract averages about 4,000 people, but can vary in area.
Obviously, the centroid is likely to not be on a street, and thus a jump
distance has to be calculated to get to a street.
Our question is what is
Just as a point of reference, you mention that avoiding swapping and just using
RAM will be much faster. If the swap space is an SSD drive, how much does using
only RAM speed up contract? That is, what is the difference between using say a
7200 rpm SATA drive versus an SSD drive make?
7 matches
Mail list logo
