I agree with the needed improvements described by Stephen.
I think the memory issue is big issue too and not well addresses right now.
On the other hand, I don't think that a routing solution should really
strongly depend on a Spatial databases. Actually, the optimization is
more a network optim
Steve,
We, pgRouting developers are willing to contribute our code and know how
to "database independent" routing engine development.
Current pgRouting connects with PostgreSQL very much. But this does not
mean we have to write codes from scratch again.
Additionally, we have lessons to learn
Hi Steve,
Good points, thank you!
However some of them are up to data and application.
PgRouting is full of "hysterical raisins" and too much bounded with
PostgreSQL - there is almost no border between pgRouting as library
and wrapper functions which is application side already.
I'm still thinki
(Orkney)Toru Mori wrote:
[snip]
> p.s. Anybody want to talk about routing?
[changing subject line was: RE: [OSGeo-Discuss] Anyone interested in
geocoding and routing?]
I have started playing with pgRouting and find it to be an impressive
start. It was easy to rewrite some of the plpgsql wrapper
