[pgrouting-users] pgRounting with PostGIS 2.0

Dear all,

Out of the box, pgRounting doesn’t work with PostGIS 2.0. All PostGIS functions now have the st_ prefix to their name, hence most (all?) of the pgRouting scripts don’t run. I see there is a pull request opened for some time to solve this issue:

https://github.com/pgRouting/pgrouting/pull/72

Is this pull being considered? Or will pgRouting remain attached to PostGIS 1.5? Would it be possible to create a PostGIS 2.0 compatible branch?

Thank you,

Luís

This pledge was met, so I am hoping/expecting that we may see it
distributed as part of the extensions list soon:

http://www.pledgebank.com/pgRoutingWindows

James

On 9 April 2013 11:21, Luís de Sousa <luis.a.de.sousa@gmail.com> wrote:

Dear all,

Out of the box, pgRounting doesn't work with PostGIS 2.0. All PostGIS
functions now have the st_ prefix to their name, hence most (all?) of the
pgRouting scripts don't run. I see there is a pull request opened for some
time to solve this issue:

https://github.com/pgRouting/pgrouting/pull/72

Is this pull being considered? Or will pgRouting remain attached to PostGIS
1.5? Would it be possible to create a PostGIS 2.0 compatible branch?

Thank you,

Luís

_______________________________________________
Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users

Thank you for the tip James.

I don’t use Winblows, nor it will ever be the base of our servers. I’d also prefer to keep these changes within the present repo and not splinter the project.

Regards,

Luís

···

On 9 April 2013 12:25, James David Smith <james.david.smith@gmail.com> wrote:

This pledge was met, so I am hoping/expecting that we may see it
distributed as part of the extensions list soon:

http://www.pledgebank.com/pgRoutingWindows

James

On 9 April 2013 11:21, Luís de Sousa <luis.a.de.sousa@gmail.com> wrote:

Dear all,

Out of the box, pgRounting doesn’t work with PostGIS 2.0. All PostGIS
functions now have the st_ prefix to their name, hence most (all?) of the
pgRouting scripts don’t run. I see there is a pull request opened for some
time to solve this issue:

https://github.com/pgRouting/pgrouting/pull/72

Is this pull being considered? Or will pgRouting remain attached to PostGIS
1.5? Would it be possible to create a PostGIS 2.0 compatible branch?

Thank you,

Luís


Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users


Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users

On 9 April 2013 12:25, James David Smith <james.david.smith@gmail.com>wrote:

This pledge was met, so I am hoping/expecting that we may see it
distributed as part of the extensions list soon:

http://www.pledgebank.com/pgRoutingWindows

James

On 9 April 2013 11:21, Luís de Sousa <luis.a.de.sousa@gmail.com> wrote:
> Dear all,
>
> Out of the box, pgRounting doesn't work with PostGIS 2.0. All PostGIS
> functions now have the st_ prefix to their name, hence most (all?) of
the
> pgRouting scripts don't run. I see there is a pull request opened for
some
> time to solve this issue:
>
> https://github.com/pgRouting/pgrouting/pull/72
>
> Is this pull being considered? Or will pgRouting remain attached to
PostGIS
> 1.5? Would it be possible to create a PostGIS 2.0 compatible branch?
>
> Thank you,
>

A new release is currently worked on.
There is lots of discussion on the developer list and if you want to try
out, you could checkout from Github repository and compile using the
following branch:
https://github.com/pgrouting/pgrouting/tree/sew-devel-2_0

There are also experimental automated Windows builds since a few hours ago:
http://www.bostongis.com/blog/index.php?/archives/215-pgRouting-1.07dev-windows-binaries-available-for-PostgreSQL-9.2-32-bit-and-64-bit.html

Daniel

--
Georepublic UG & Georepublic Japan
eMail: daniel.kastl@georepublic.de
Web: http://georepublic.de

Hi Luis,

I'm using postgis 2.0 with pgrouting.
I have to change some code of pgrouting (because the 'st_') but works.
But i'm using only two functions:

shortest_path
assign_vertex_id

SO: Ubuntu Server

Pedro

Em 09-04-2013 11:33, Luís de Sousa escreveu:

Thank you for the tip James.

I don't use Winblows, nor it will ever be the base of our servers. I'd also prefer to keep these changes within the present repo and not splinter the project.

Regards,

Luís

On 9 April 2013 12:25, James David Smith <james.david.smith@gmail.com <mailto:james.david.smith@gmail.com>> wrote:

    This pledge was met, so I am hoping/expecting that we may see it
    distributed as part of the extensions list soon:

    http://www.pledgebank.com/pgRoutingWindows

    James

    On 9 April 2013 11:21, Luís de Sousa <luis.a.de.sousa@gmail.com
    <mailto:luis.a.de.sousa@gmail.com>> wrote:
    > Dear all,
    >
    > Out of the box, pgRounting doesn't work with PostGIS 2.0. All
    PostGIS
    > functions now have the st_ prefix to their name, hence most
    (all?) of the
    > pgRouting scripts don't run. I see there is a pull request
    opened for some
    > time to solve this issue:
    >
    > https://github.com/pgRouting/pgrouting/pull/72
    >
    > Is this pull being considered? Or will pgRouting remain attached
    to PostGIS
    > 1.5? Would it be possible to create a PostGIS 2.0 compatible branch?
    >
    > Thank you,
    >
    > Luís
    >
    > _______________________________________________
    > Pgrouting-users mailing list
    > Pgrouting-users@lists.osgeo.org
    <mailto:Pgrouting-users@lists.osgeo.org>
    > http://lists.osgeo.org/mailman/listinfo/pgrouting-users
    >
    _______________________________________________
    Pgrouting-users mailing list
    Pgrouting-users@lists.osgeo.org
    <mailto:Pgrouting-users@lists.osgeo.org>
    http://lists.osgeo.org/mailman/listinfo/pgrouting-users

_______________________________________________
Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users

Hi Daniel, thanks for the update.

I know this is a tricky question, but is there any expected date for this new release?

Thank you,

Luís

···

On 9 April 2013 13:05, Daniel Kastl <daniel@georepublic.de> wrote:

A new release is currently worked on.
There is lots of discussion on the developer list and if you want to try out, you could checkout from Github repository and compile using the following branch:
https://github.com/pgrouting/pgrouting/tree/sew-devel-2_0

On Tue, Apr 9, 2013 at 10:22 PM, Luís de Sousa <luis.a.de.sousa@gmail.com>wrote:

Hi Daniel, thanks for the update.

I know this is a tricky question, but is there any expected date for this
new release?

Yes, tricky and easy at the same time.
As more time we can spend on development as earlier it will be ready :wink:

Thanks to some funding we're able to work on the new release right now.
If someone has an interest in getting this done faster, we're happy for any
support: whether it is financial contribution or help with development.

Here is a rough list of what we have in mind:
https://github.com/pgRouting/pgrouting/wiki/2.0-Development-Plan
Lots of "Milestones 1" has been done already. But there is still a lot to
do and time and funds are limited.

Daniel

Thank you,

Luís

On 9 April 2013 13:05, Daniel Kastl <daniel@georepublic.de> wrote:

A new release is currently worked on.
There is lots of discussion on the developer list and if you want to try
out, you could checkout from Github repository and compile using the
following branch:
https://github.com/pgrouting/pgrouting/tree/sew-devel-2_0

_______________________________________________
Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users

--
Georepublic UG & Georepublic Japan
eMail: daniel.kastl@georepublic.de
Web: http://georepublic.de

Hi All,

The sew-devel-2_0 branch is what I'm currently working on. I do not have a release date because it depends on how much we decide to integrate into this branch and how much funding we can raise to support this effort.

My general development goals is to try an make sure that at the end of each day (UTC-0500) that the branch is stable and compiles and builds on Linux and Windows.

Currently it:
* works with PostGIS 2.0
* has had the source tree restructured to better support multiple devs
* has TRSP merged into the tree
* has had TSP solver replaced to remove GAUL dependency
* has a new doc system integrated into the source tree
* has a new test infrastructure integrated into the source tree
* has some tests have been added to the source tree
* has some bugs fixed
* has some new graph analytic tools for detecting graph connectivity issues
* installs as a postgresql extension on PG9.1+
* has probably a few other things that I'm not remembering.

Things that will change over time in this branch:

* all functions will get a pgr_ prefix
* all functions will get reviewed and probably restructured to be more consistent and allow users to easily switch between function
* more algorithms from pull requests and GSoC projects will get pulled into the main respository
* rewrite driving distance to drop CGAL and use postgis functions

Look at this to get an idea:
https://github.com/pgRouting/pgrouting/wiki/2.0-Development-Plan

You can see a lot has been done and there is a lot more to do. A lot of the infrastructure work has been tackled and some of the low hanging fruit has been picked. Any offers for funding would be greatly appreciated and could help accelerate and/or prioritize features.

This is currently stable and fairly close to the 1.0.5 functionality so if you are inclined to give it a try we would love to here about on what works and doesn't, etc.

Thanks,
   -Steve

On 4/9/2013 9:22 AM, Luís de Sousa wrote:

Hi Daniel, thanks for the update.

I know this is a tricky question, but is there any expected date for
this new release?

Thank you,

Luís

On 9 April 2013 13:05, Daniel Kastl <daniel@georepublic.de
<mailto:daniel@georepublic.de>> wrote:

    A new release is currently worked on.
    There is lots of discussion on the developer list and if you want to
    try out, you could checkout from Github repository and compile using
    the following branch:
    https://github.com/pgrouting/pgrouting/tree/sew-devel-2_0

_______________________________________________
Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users

Hi Stephen and Daniel,

I’d be glad to contribute, I believe I can invest a few hours per week. Besides that I’m working on a project where K-Shortest will be used, I can try to source some funding around it.

Regards,

Luís

···

On 9 April 2013 15:56, Stephen Woodbridge <woodbri@swoodbridge.com> wrote:

Hi All,

The sew-devel-2_0 branch is what I’m currently working on. I do not have a release date because it depends on how much we decide to integrate into this branch and how much funding we can raise to support this effort.

My general development goals is to try an make sure that at the end of each day (UTC-0500) that the branch is stable and compiles and builds on Linux and Windows.

Currently it:

  • works with PostGIS 2.0
  • has had the source tree restructured to better support multiple devs
  • has TRSP merged into the tree
  • has had TSP solver replaced to remove GAUL dependency
  • has a new doc system integrated into the source tree
  • has a new test infrastructure integrated into the source tree
  • has some tests have been added to the source tree
  • has some bugs fixed
  • has some new graph analytic tools for detecting graph connectivity issues
  • installs as a postgresql extension on PG9.1+
  • has probably a few other things that I’m not remembering.

Things that will change over time in this branch:

  • all functions will get a pgr_ prefix
  • all functions will get reviewed and probably restructured to be more consistent and allow users to easily switch between function
  • more algorithms from pull requests and GSoC projects will get pulled into the main respository
  • rewrite driving distance to drop CGAL and use postgis functions

Look at this to get an idea:
https://github.com/pgRouting/pgrouting/wiki/2.0-Development-Plan

You can see a lot has been done and there is a lot more to do. A lot of the infrastructure work has been tackled and some of the low hanging fruit has been picked. Any offers for funding would be greatly appreciated and could help accelerate and/or prioritize features.

This is currently stable and fairly close to the 1.0.5 functionality so if you are inclined to give it a try we would love to here about on what works and doesn’t, etc.

Thanks,
-Steve

On 4/9/2013 9:22 AM, Luís de Sousa wrote:

Hi Daniel, thanks for the update.

I know this is a tricky question, but is there any expected date for
this new release?

Thank you,

Luís

On 9 April 2013 13:05, Daniel Kastl <daniel@georepublic.de

mailto:[daniel@georepublic.de](mailto:daniel@georepublic.de)> wrote:

A new release is currently worked on.
There is lots of discussion on the developer list and if you want to
try out, you could checkout from Github repository and compile using
the following branch:
https://github.com/pgrouting/pgrouting/tree/sew-devel-2_0


Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users


Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users

On 4/10/2013 8:48 AM, Luís de Sousa wrote:

Hi Stephen and Daniel,

I'd be glad to contribute, I believe I can invest a few hours per week.
Besides that I'm working on a project where K-Shortest will be used, I
can try to source some funding around it.

Luis,

Funding would be great if you can arrange it, K-Shorest path is one of the algorithms that we would like to add to 2.0 so we might be able to accelerate getting that moved into sew-devel-2_0 branch.

Regarding contributing, do you have any area(s) that you would like to work on. We can use effort in all areas. I do not where your skills are on the spectrum from developer <----> user, but there is no shortage of tasks across the board.

Regards,
   -Steve

Regards,

Luís

On 9 April 2013 15:56, Stephen Woodbridge <woodbri@swoodbridge.com
<mailto:woodbri@swoodbridge.com>> wrote:

    Hi All,

    The sew-devel-2_0 branch is what I'm currently working on. I do not
    have a release date because it depends on how much we decide to
    integrate into this branch and how much funding we can raise to
    support this effort.

    My general development goals is to try an make sure that at the end
    of each day (UTC-0500) that the branch is stable and compiles and
    builds on Linux and Windows.

    Currently it:
    * works with PostGIS 2.0
    * has had the source tree restructured to better support multiple devs
    * has TRSP merged into the tree
    * has had TSP solver replaced to remove GAUL dependency
    * has a new doc system integrated into the source tree
    * has a new test infrastructure integrated into the source tree
    * has some tests have been added to the source tree
    * has some bugs fixed
    * has some new graph analytic tools for detecting graph connectivity
    issues
    * installs as a postgresql extension on PG9.1+
    * has probably a few other things that I'm not remembering.

    Things that will change over time in this branch:

    * all functions will get a pgr_ prefix
    * all functions will get reviewed and probably restructured to be
    more consistent and allow users to easily switch between function
    * more algorithms from pull requests and GSoC projects will get
    pulled into the main respository
    * rewrite driving distance to drop CGAL and use postgis functions

    Look at this to get an idea:
    https://github.com/pgRouting/__pgrouting/wiki/2.0-__Development-Plan
    <https://github.com/pgRouting/pgrouting/wiki/2.0-Development-Plan&gt;

    You can see a lot has been done and there is a lot more to do. A lot
    of the infrastructure work has been tackled and some of the low
    hanging fruit has been picked. Any offers for funding would be
    greatly appreciated and could help accelerate and/or prioritize
    features.

    This is currently stable and fairly close to the 1.0.5 functionality
    so if you are inclined to give it a try we would love to here about
    on what works and doesn't, etc.

    Thanks,
       -Steve

    On 4/9/2013 9:22 AM, Luís de Sousa wrote:

        Hi Daniel, thanks for the update.

        I know this is a tricky question, but is there any expected date for
        this new release?

        Thank you,

        Luís

        On 9 April 2013 13:05, Daniel Kastl <daniel@georepublic.de
        <mailto:daniel@georepublic.de>
        <mailto:daniel@georepublic.de>__>
        wrote:

             A new release is currently worked on.
             There is lots of discussion on the developer list and if
        you want to
             try out, you could checkout from Github repository and
        compile using
             the following branch:
        https://github.com/pgrouting/__pgrouting/tree/sew-devel-2_0
        <https://github.com/pgrouting/pgrouting/tree/sew-devel-2_0&gt;

        _________________________________________________
        Pgrouting-users mailing list
        Pgrouting-users@lists.osgeo.__org
        <mailto:Pgrouting-users@lists.osgeo.org>
        http://lists.osgeo.org/__mailman/listinfo/pgrouting-__users
        <http://lists.osgeo.org/mailman/listinfo/pgrouting-users&gt;

    _________________________________________________
    Pgrouting-users mailing list
    Pgrouting-users@lists.osgeo.__org
    <mailto:Pgrouting-users@lists.osgeo.org>
    http://lists.osgeo.org/__mailman/listinfo/pgrouting-__users
    <http://lists.osgeo.org/mailman/listinfo/pgrouting-users&gt;

_______________________________________________
Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users

Dear Steve,

I work regularly with pgpsql and PostGIS 2.0, and did a good deal of C coding back in the 1990s.

I’d rather start with simpler tasks and then build from there if I find the resources.

Regards,

Luís

···

On 10 April 2013 15:33, Stephen Woodbridge <woodbri@swoodbridge.com> wrote

Luis,

Funding would be great if you can arrange it, K-Shorest path is one of the algorithms that we would like to add to 2.0 so we might be able to accelerate getting that moved into sew-devel-2_0 branch.

Regarding contributing, do you have any area(s) that you would like to work on. We can use effort in all areas. I do not where your skills are on the spectrum from developer <----> user, but there is no shortage of tasks across the board.

Regards,
-Steve

Hi
I added some code for doing k shortest routes, see

https://github.com/pgRouting/pgrouting/pull/75

The code that does the ksp part is taken from an another open source project, I just added the interface layer to postgres.

If there is a 'better/faster' way of doing the same thing ......

Dave.

On 10/04/13 16:24, Luís de Sousa wrote:

Dear Steve,

I work regularly with pgpsql and PostGIS 2.0, and did a good deal of C coding back in the 1990s.

I'd rather start with simpler tasks and then build from there if I find the resources.

Regards,

Luís

On 10 April 2013 15:33, Stephen Woodbridge <woodbri@swoodbridge.com <mailto:woodbri@swoodbridge.com>> wrote

    Luis,

    Funding would be great if you can arrange it, K-Shorest path is
    one of the algorithms that we would like to add to 2.0 so we might
    be able to accelerate getting that moved into sew-devel-2_0 branch.

    Regarding contributing, do you have any area(s) that you would
    like to work on. We can use effort in all areas. I do not where
    your skills are on the spectrum from developer <----> user, but
    there is no shortage of tasks across the board.

    Regards,
      -Steve

_______________________________________________
Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users

Dave, Luis,

I am merging Dave's ksp branch into sew-devel-2_0 branch. Once I have all the files merged into my tree and integrated with my cmake, I may need some help testing it out and/or debugging it.

I should have something commited and pushed later today.

Thanks,
   -Steve

On 4/14/2013 1:04 AM, Dave Potts wrote:

Hi
I added some code for doing k shortest routes, see

https://github.com/pgRouting/pgrouting/pull/75

The code that does the ksp part is taken from an another open source
project, I just added the interface layer to postgres.

If there is a 'better/faster' way of doing the same thing ......

Dave.

On 10/04/13 16:24, Luís de Sousa wrote:

Dear Steve,

I work regularly with pgpsql and PostGIS 2.0, and did a good deal of C
coding back in the 1990s.

I'd rather start with simpler tasks and then build from there if I
find the resources.

Regards,

Luís

On 10 April 2013 15:33, Stephen Woodbridge <woodbri@swoodbridge.com
<mailto:woodbri@swoodbridge.com>> wrote

    Luis,

    Funding would be great if you can arrange it, K-Shorest path is
    one of the algorithms that we would like to add to 2.0 so we might
    be able to accelerate getting that moved into sew-devel-2_0 branch.

    Regarding contributing, do you have any area(s) that you would
    like to work on. We can use effort in all areas. I do not where
    your skills are on the spectrum from developer <----> user, but
    there is no shortage of tasks across the board.

    Regards,
      -Steve

_______________________________________________
Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users

_______________________________________________
Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users

I could help testing it. I’ll set up an environment and let you know.

Best,

Luís

···

On 14 April 2013 17:07, Stephen Woodbridge <woodbri@swoodbridge.com> wrote:

Dave, Luis,

I am merging Dave’s ksp branch into sew-devel-2_0 branch. Once I have all the files merged into my tree and integrated with my cmake, I may need some help testing it out and/or debugging it.

I should have something commited and pushed later today.

Thanks,
-Steve

On 4/14/2013 1:04 AM, Dave Potts wrote:

Hi
I added some code for doing k shortest routes, see

https://github.com/pgRouting/pgrouting/pull/75

The code that does the ksp part is taken from an another open source
project, I just added the interface layer to postgres.

If there is a ‘better/faster’ way of doing the same thing …

Dave.

On 10/04/13 16:24, Luís de Sousa wrote:

Dear Steve,

I work regularly with pgpsql and PostGIS 2.0, and did a good deal of C
coding back in the 1990s.

I’d rather start with simpler tasks and then build from there if I
find the resources.

Regards,

Luís

On 10 April 2013 15:33, Stephen Woodbridge <woodbri@swoodbridge.com

mailto:[woodbri@swoodbridge.com](mailto:woodbri@swoodbridge.com)> wrote

Luis,

Funding would be great if you can arrange it, K-Shorest path is
one of the algorithms that we would like to add to 2.0 so we might
be able to accelerate getting that moved into sew-devel-2_0 branch.

Regarding contributing, do you have any area(s) that you would
like to work on. We can use effort in all areas. I do not where
your skills are on the spectrum from developer <----> user, but
there is no shortage of tasks across the board.

Regards,
-Steve


Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users


Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users


Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users

Hi Guys,

Sorry, I gotten distracted with other project work and tomorrow is a travel day so this has been put on the back seat for a few days. I will get back to it and get it merged. Please be patient.

Thanks,
   -Steve

On 4/14/2013 11:07 AM, Stephen Woodbridge wrote:

Dave, Luis,

I am merging Dave's ksp branch into sew-devel-2_0 branch. Once I have
all the files merged into my tree and integrated with my cmake, I may
need some help testing it out and/or debugging it.

I should have something commited and pushed later today.

Thanks,
   -Steve

On 4/14/2013 1:04 AM, Dave Potts wrote:

Hi
I added some code for doing k shortest routes, see

https://github.com/pgRouting/pgrouting/pull/75

The code that does the ksp part is taken from an another open source
project, I just added the interface layer to postgres.

If there is a 'better/faster' way of doing the same thing ......

Dave.

On 10/04/13 16:24, Luís de Sousa wrote:

Dear Steve,

I work regularly with pgpsql and PostGIS 2.0, and did a good deal of C
coding back in the 1990s.

I'd rather start with simpler tasks and then build from there if I
find the resources.

Regards,

Luís

On 10 April 2013 15:33, Stephen Woodbridge <woodbri@swoodbridge.com
<mailto:woodbri@swoodbridge.com>> wrote

    Luis,

    Funding would be great if you can arrange it, K-Shorest path is
    one of the algorithms that we would like to add to 2.0 so we might
    be able to accelerate getting that moved into sew-devel-2_0 branch.

    Regarding contributing, do you have any area(s) that you would
    like to work on. We can use effort in all areas. I do not where
    your skills are on the spectrum from developer <----> user, but
    there is no shortage of tasks across the board.

    Regards,
      -Steve

_______________________________________________
Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users

_______________________________________________
Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users

_______________________________________________
Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users