[pgrouting-users] New Windows 32bit/64bit binary for PostgreSQL9.1

pgRouting pgrouting-users
1

Hi list,

I had build pgRouting git version for Windows PostgreSQL9.1(x86_32/x86_64).

https://github.com/sanak/pgrouting/downloads
± pgRouting-git-sanak-mingw64_20120703_pg-9.1(x86_64).zip => 64bit version
± pgRouting-git-sanak-mingw32_20120703_pg-9.1(x86_32).zip => 32bit version

  • Both include David Techer’s roads.sql (for postgis1.x/2.x). (See http://www.davidgis.fr/documentation/pgrouting-1.02/)
  • If you use roads_postgis2.x.sql on PostGIS 2.0, in addition to “postgis.sql” and “spatial_ref_sys.sql”, “legacy.sql” is necessary.
  • Shooting Star reverse cost issue still remain. (I will check Steve Horn’s fixes(https://github.com/stevehorn/pgrouting/commits/) till next week)
  • This archive is not ver.1.05, because many other fixes includes after 1.05 release.

Build instruction is here.
https://github.com/sanak/pgrouting/blob/mingw/BUILD.mingw
https://github.com/sanak/pgrouting/blob/mingw/BUILD.mingw64

And I will create github “Pull Request”(sanak:mingw) to pgrouting:master soon.

Regards,

2

Very cool!

Thanks for this!

On Tue, Jul 3, 2012 at 9:41 AM, Sanak <geosanak@gmail.com> wrote:

Hi list,

I had build pgRouting git version for Windows PostgreSQL9.1(x86_32/x86_64).

https://github.com/sanak/pgrouting/downloads
± pgRouting-git-sanak-mingw64_20120703_pg-9.1(x86_64).zip => 64bit version
± pgRouting-git-sanak-mingw32_20120703_pg-9.1(x86_32).zip => 32bit version

  • Both include David Techer’s roads.sql (for postgis1.x/2.x). (See http://www.davidgis.fr/documentation/pgrouting-1.02/)
  • If you use roads_postgis2.x.sql on PostGIS 2.0, in addition to “postgis.sql” and “spatial_ref_sys.sql”, “legacy.sql” is necessary.
  • Shooting Star reverse cost issue still remain. (I will check Steve Horn’s fixes(https://github.com/stevehorn/pgrouting/commits/) till next week)
  • This archive is not ver.1.05, because many other fixes includes after 1.05 release.

Build instruction is here.
https://github.com/sanak/pgrouting/blob/mingw/BUILD.mingw
https://github.com/sanak/pgrouting/blob/mingw/BUILD.mingw64

And I will create github “Pull Request”(sanak:mingw) to pgrouting:master soon.

Regards,

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

–
George R. C. Silva

Desenvolvimento em GIS
http://geoprocessamento.net
http://blog.geoprocessamento.net

3

Great JOB !!

I will try it soon ,

thanks !

2012/7/3 George Silva <georger.silva@gmail.com>:

Very cool!

Thanks for this!

On Tue, Jul 3, 2012 at 9:41 AM, Sanak <geosanak@gmail.com> wrote:

Hi list,

I had build pgRouting git version for Windows
PostgreSQL9.1(x86_32/x86_64).

https://github.com/sanak/pgrouting/downloads
+- pgRouting-git-sanak-mingw64_20120703_pg-9.1(x86_64).zip => 64bit
version
+- pgRouting-git-sanak-mingw32_20120703_pg-9.1(x86_32).zip => 32bit
version

* Both include David Techer's roads.sql (for postgis1.x/2.x). (See
http://www.davidgis.fr/documentation/pgrouting-1.02/)
* If you use roads_postgis2.x.sql on PostGIS 2.0, in addition to
"postgis.sql" and "spatial_ref_sys.sql", "legacy.sql" is necessary.
* Shooting Star reverse cost issue still remain. (I will check Steve
Horn's fixes(https://github.com/stevehorn/pgrouting/commits/) till next
week)
* This archive is not ver.1.05, because many other fixes includes after
1.05 release.

Build instruction is here.
https://github.com/sanak/pgrouting/blob/mingw/BUILD.mingw
https://github.com/sanak/pgrouting/blob/mingw/BUILD.mingw64

* Thanks PostGIS team for readable documents and ming64.zip archive.
(http://trac.osgeo.org/postgis/wiki/DevWikiWinMingW64)

And I will create github "Pull Request"(sanak:mingw) to pgrouting:master
soon.

Regards,

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

--
George R. C. Silva

Desenvolvimento em GIS
http://geoprocessamento.net
http://blog.geoprocessamento.net

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

4

Hi Sanak,

Thank you for all your effort to get this working and for documenting it. We really appreciate your effort and support of the pgRouting community.

Many thanks again.

-Steve

On 7/3/2012 8:41 AM, Sanak wrote:

Hi list,

I had build pgRouting git version for Windows PostgreSQL9.1(x86_32/x86_64).

https://github.com/sanak/pgrouting/downloads
  +- pgRouting-git-sanak-mingw64_20120703_pg-9.1(x86_64).zip => 64bit
version
  +- pgRouting-git-sanak-mingw32_20120703_pg-9.1(x86_32).zip => 32bit
version

* Both include David Techer's roads.sql (for postgis1.x/2.x). (See
http://www.davidgis.fr/documentation/pgrouting-1.02/)
* If you use roads_postgis2.x.sql on PostGIS 2.0, in addition to
"postgis.sql" and "spatial_ref_sys.sql", "legacy.sql" is necessary.
* Shooting Star reverse cost issue still remain. (I will check Steve
Horn's fixes(https://github.com/stevehorn/pgrouting/commits/) till next
week)
* This archive is not ver.1.05, because many other fixes includes after
1.05 release.

Build instruction is here.
https://github.com/sanak/pgrouting/blob/mingw/BUILD.mingw
https://github.com/sanak/pgrouting/blob/mingw/BUILD.mingw64

* Thanks PostGIS team for readable documents and ming64.zip archive.
(http://trac.osgeo.org/postgis/wiki/DevWikiWinMingW64)

And I will create github "Pull Request"(sanak:mingw) to pgrouting:master
soon.

Regards,

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

5

Hi guys,

Thanks for response :slight_smile:

I had added the each build environments to skydrive,
so if someone who want to make custom build on Windows exists,
use these one.

http://sdrv.ms/NFCgr2
± Build.zip … for 32bit work folder. (extract to "C:")
± MinGW.zip … for 32bit build environment. (extract to "C:" and run “C:\MinGW\msys\1.0\msys.bat”)
± Build64.zip … for 64bit work folder. (extract to "C:")
± ming64.zip … for 64bit build environment. (based on PostGIS one. extract to "C:" and run “C:\ming64\msys\msys.bat”)

Regards,

2012/7/3 Sanak <geosanak@gmail.com>

Hi list,

I had build pgRouting git version for Windows PostgreSQL9.1(x86_32/x86_64).

https://github.com/sanak/pgrouting/downloads
± pgRouting-git-sanak-mingw64_20120703_pg-9.1(x86_64).zip => 64bit version
± pgRouting-git-sanak-mingw32_20120703_pg-9.1(x86_32).zip => 32bit version

  • Both include David Techer’s roads.sql (for postgis1.x/2.x). (See http://www.davidgis.fr/documentation/pgrouting-1.02/)
  • If you use roads_postgis2.x.sql on PostGIS 2.0, in addition to “postgis.sql” and “spatial_ref_sys.sql”, “legacy.sql” is necessary.
  • Shooting Star reverse cost issue still remain. (I will check Steve Horn’s fixes(https://github.com/stevehorn/pgrouting/commits/) till next week)
  • This archive is not ver.1.05, because many other fixes includes after 1.05 release.

Build instruction is here.
https://github.com/sanak/pgrouting/blob/mingw/BUILD.mingw
https://github.com/sanak/pgrouting/blob/mingw/BUILD.mingw64

And I will create github “Pull Request”(sanak:mingw) to pgrouting:master soon.

Regards,

6

Dear pg_routers,

I added a page describing my first (very minor) contribution to the wiki:
https://github.com/pgRouting/pgrouting/wiki/One_to_many-Dijkstra---To-review

I don't know how to make it accessible (and at first if the function really is relevant, I believe that many of you coded a similar function...).
As soon as it does not really modify the method (boost_dijkstra), I think the Algorithms section is not appropriate.

Should I
- remove the whole stuff?
- add a new section to https://github.com/pgRouting/pgrouting/wiki (i.e. "Optional wrappers" or "Contrib. / betas")?

Please feedback if you have the time to try it;

Regards,
HSylvio.

7

This is a great contribution, and something I have been working on lately (a distance matrix).

A question: does your algorithm build the graph one time (therefore only calling into the postgres data once), and re-use the graph for each target ID?

Thanks.
-Steve

On Fri, Jul 6, 2012 at 10:00 AM, Sylvain Housseman <hsylvio@gmail.com> wrote:

Dear pg_routers,

I added a page describing my first (very minor) contribution to the wiki:
https://github.com/pgRouting/pgrouting/wiki/One_to_many-Dijkstra—To-review

I don’t know how to make it accessible (and at first if the function really is relevant, I believe that many of you coded a similar function…).
As soon as it does not really modify the method (boost_dijkstra), I think the Algorithms section is not appropriate.

Should I

Please feedback if you have the time to try it;

Regards,
HSylvio.

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

–
Steve Horn

8

Yes, as soon as did not change the way the graph is built nor the calling of dijkstra_shortest_paths(graph, _source, predecessor_map(…)). After this call, a loop on nb_targets re-uses the “graph” (in fact the predecessors) for each target ID. Have you tried it already? If so, I forgot to remove a cout or two, which may pollute your .log… I’ll remove these ASAP!

···

Le 06/07/2012 17:38, Steve Horn a écrit :

This is a great contribution, and something I have been working on lately (a distance matrix).

A question: does your algorithm build the graph one time (therefore only calling into the postgres data once), and re-use the graph for each target ID?

Thanks.
-Steve

On Fri, Jul 6, 2012 at 10:00 AM, Sylvain Housseman <hsylvio@gmail.com> wrote:

Dear pg_routers,

I added a page describing my first (very minor) contribution to the wiki:
https://github.com/pgRouting/pgrouting/wiki/One_to_many-Dijkstra—To-review

I don’t know how to make it accessible (and at first if the function really is relevant, I believe that many of you coded a similar function…).
As soon as it does not really modify the method (boost_dijkstra), I think the Algorithms section is not appropriate.

Should I

Please feedback if you have the time to try it;

Regards,
HSylvio.

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

–
Steve Horn

_______________________________________________
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)
9

This looks great. I wish this had been around six months ago...

-Elijah

----- Original Message -----
From: "Sylvain Housseman" <hsylvio@gmail.com>
To: pgrouting-users@lists.osgeo.org
Sent: Friday, July 6, 2012 7:00:51 AM
Subject: [pgrouting-users] One_To_Many dijkstra

Dear pg_routers,

I added a page describing my first (very minor) contribution to the wiki:
https://github.com/pgRouting/pgrouting/wiki/One_to_many-Dijkstra---To-review

I don't know how to make it accessible (and at first if the function
really is relevant, I believe that many of you coded a similar function...).
As soon as it does not really modify the method (boost_dijkstra), I
think the Algorithms section is not appropriate.

Should I
- remove the whole stuff?
- add a new section to https://github.com/pgRouting/pgrouting/wiki (i.e.
"Optional wrappers" or "Contrib. / betas")?

Please feedback if you have the time to try it;

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

10

On 7/6/2012 10:00 AM, Sylvain Housseman wrote:

Dear pg_routers,

I added a page describing my first (very minor) contribution to the wiki:
https://github.com/pgRouting/pgrouting/wiki/One_to_many-Dijkstra---To-review

I don't know how to make it accessible (and at first if the function
really is relevant, I believe that many of you coded a similar
function...).
As soon as it does not really modify the method (boost_dijkstra), I
think the Algorithms section is not appropriate.

Should I
- remove the whole stuff?
- add a new section to https://github.com/pgRouting/pgrouting/wiki (i.e.
"Optional wrappers" or "Contrib. / betas")?

Please feedback if you have the time to try it;

Hi Sylvain,

Thank you for your contribution. It is very much appreciated.

I have a question, if I have 10 destination nodes, how many times to you solve the graph after it is built?

The Dijkstra algorithm converts a graph into a tree. If you search the tree for the destination nodes, you should be able to extract the path as the reverse of the nodes from the destination up to the root (aka: the source node). So for a single solution, can can extract any of the path from any destination node in the tree.

Is this how your algorithm works?

Thanks,
   -Steve W

11

Only once… I wouldn’t have explained it better! To detail the code modifications, I just replaced “vertex_descriptor _target;” by an array of the same type, initialized as “_target[i] = vertex(end_vertices[i], graph);” and after the resolution, I loop on nb_targets to build the paths as on the tree (_target[i] = predecessors[_target[i]]:wink: while _target[i] != _source. Thanks to you for the feedbacks!

···

On 7/6/2012 6:52 PM, Stephen Woodbridge wrote:

On 7/6/2012 10:00 AM, Sylvain Housseman wrote:

Dear pg_routers,

I added a page describing my first (very minor) contribution to the wiki:
https://github.com/pgRouting/pgrouting/wiki/One_to_many-Dijkstra—To-review

I don’t know how to make it accessible (and at first if the function
really is relevant, I believe that many of you coded a similar
function…).
As soon as it does not really modify the method (boost_dijkstra), I
think the Algorithms section is not appropriate.

Should I

Please feedback if you have the time to try it;

Hi Sylvain,

Thank you for your contribution. It is very much appreciated.

I have a question, if I have 10 destination nodes, how many times to you solve the graph after it is built?

The Dijkstra algorithm converts a graph into a tree. If you search the tree for the destination nodes, you should be able to extract the path as the reverse of the nodes from the destination up to the root (aka: the source node). So for a single solution, can can extract any of the path from any destination node in the tree.

Is this how your algorithm works?

rewinding

Thanks,
-Steve W

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

12

Hi Sanak

What is the Shooting Star reverse cost issue which still remain for the pg9.1 win build ?

Regards,

Ricardo

2012/7/6 Sanak <geosanak@gmail.com>

Hi guys,

Thanks for response :slight_smile:

I had added the each build environments to skydrive,
so if someone who want to make custom build on Windows exists,
use these one.

http://sdrv.ms/NFCgr2
± Build.zip … for 32bit work folder. (extract to "C:")
± MinGW.zip … for 32bit build environment. (extract to "C:" and run “C:\MinGW\msys\1.0\msys.bat”)
± Build64.zip … for 64bit work folder. (extract to "C:")
± ming64.zip … for 64bit build environment. (based on PostGIS one. extract to "C:" and run “C:\ming64\msys\msys.bat”)

Regards,

2012/7/3 Sanak <geosanak@gmail.com>

Hi list,

I had build pgRouting git version for Windows PostgreSQL9.1(x86_32/x86_64).

https://github.com/sanak/pgrouting/downloads
± pgRouting-git-sanak-mingw64_20120703_pg-9.1(x86_64).zip => 64bit version
± pgRouting-git-sanak-mingw32_20120703_pg-9.1(x86_32).zip => 32bit version

  • Both include David Techer’s roads.sql (for postgis1.x/2.x). (See http://www.davidgis.fr/documentation/pgrouting-1.02/)
  • If you use roads_postgis2.x.sql on PostGIS 2.0, in addition to “postgis.sql” and “spatial_ref_sys.sql”, “legacy.sql” is necessary.
  • Shooting Star reverse cost issue still remain. (I will check Steve Horn’s fixes(https://github.com/stevehorn/pgrouting/commits/) till next week)
  • This archive is not ver.1.05, because many other fixes includes after 1.05 release.

Build instruction is here.
https://github.com/sanak/pgrouting/blob/mingw/BUILD.mingw
https://github.com/sanak/pgrouting/blob/mingw/BUILD.mingw64

And I will create github “Pull Request”(sanak:mingw) to pgrouting:master soon.

Regards,

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

13

Hi Guys,

I strongly recommend that you use the turn restrict shortest path (TRSP) algorithm and not Shooting star.

TRSP is significantly faster. It handles all the cases that Shooting Star is supposed to handle and it handles cases that are not supported by shooting star.

My mind is getting a little fuzzy at this point but if I recall the problems with shooting star.

1. v1.02 or 1.03 was the last working version and it had bugs
2. you can not say where on an edge you want to start like you can with TRSP
3. if the start or end edge is one-way then I think the one-wayness is ignored.
4. in the results the real cost to traverse the edge is not reported correctly, I think it always reports the "cost" attribute not the one it used in solving the graph.
5. it is like 2-5 times slower than TRSP, this might be because of bugs introduced in the later version changes

I think it would be a better use of time and effort to just create a wrapper to TRSP the is identical to Shooting star so you can call shooting star and have it executed by TRSP. Then we only have one algorithm to maintain and bug fix.

I believe TRSP is getting moved into the main release as part of the pgRouting 2.0 release, but I don't know when that might be.

Thanks,
   -Steve

On 8/4/2012 10:32 AM, Ricardo Bayley wrote:

Hi Sanak

What is the Shooting Star reverse cost issue which still remain for the
pg9.1 win build ?

Regards,

Ricardo

2012/7/6 Sanak <geosanak@gmail.com <mailto:geosanak@gmail.com>>

    Hi guys,

    Thanks for response :slight_smile:

    I had added the each build environments to skydrive,
    so if someone who want to make custom build on Windows exists,
    use these one.

    http://sdrv.ms/NFCgr2
      +- Build.zip ... for 32bit work folder. (extract to "C:\")
      +- MinGW.zip ... for 32bit build environment. (extract to "C:\"
    and run "C:\MinGW\msys\1.0\msys.bat")
      +- Build64.zip ... for 64bit work folder. (extract to "C:\")
      +- ming64.zip ... for 64bit build environment. (based on PostGIS
    one. extract to "C:\" and run "C:\ming64\msys\msys.bat")

    Regards,

    2012/7/3 Sanak <geosanak@gmail.com <mailto:geosanak@gmail.com>>

        Hi list,

        I had build pgRouting git version for Windows
        PostgreSQL9.1(x86_32/x86_64).

        https://github.com/sanak/pgrouting/downloads
          +- pgRouting-git-sanak-mingw64_20120703_pg-9.1(x86_64).zip =>
        64bit version
          +- pgRouting-git-sanak-mingw32_20120703_pg-9.1(x86_32).zip =>
        32bit version

        * Both include David Techer's roads.sql (for postgis1.x/2.x).
        (See http://www.davidgis.fr/documentation/pgrouting-1.02/)
        * If you use roads_postgis2.x.sql on PostGIS 2.0, in addition to
        "postgis.sql" and "spatial_ref_sys.sql", "legacy.sql" is necessary.
        * Shooting Star reverse cost issue still remain. (I will check
        Steve Horn's
        fixes(https://github.com/stevehorn/pgrouting/commits/) till next
        week)
        * This archive is not ver.1.05, because many other fixes
        includes after 1.05 release.

        Build instruction is here.
        https://github.com/sanak/pgrouting/blob/mingw/BUILD.mingw
        https://github.com/sanak/pgrouting/blob/mingw/BUILD.mingw64

        * Thanks PostGIS team for readable documents and ming64.zip archive.
        (http://trac.osgeo.org/postgis/wiki/DevWikiWinMingW64)

        And I will create github "Pull Request"(sanak:mingw) to
        pgrouting:master soon.

        Regards,

    _______________________________________________
    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

14

Hi Recardo,

Shooting Star reverse cost issue is confirmable by David Techer’s road sample.
(Try http://www.davidgis.fr/documentation/pgrouting-1.02/ - 6. Shortest Path Shooting Star : shortest_path_shooting_star() section).
I had wanted to fix this issue before my busy season(July - November), but time was up.
If you want to use Shooting Star at hurry, I will try it again at my short summer vacation(8/11 - 8/19).
But I want to rest this summer.

Hi Stepen,

I think that current project status is too bad,
because 1.0x is broken and 2.0 is incomplete.
So I think that following interim release (like 1.5x) is necessary.

  • include TRSP module at “extra” folder. (almost same as current ‘trsp’ branch)
  • fix packaging issue. (Windows/Mac, Boost/CGAL)
  • include GSoc member’s regression test system. (like PostGIS)

I think that above code change is not hard work than 2.0,
and packager(xnix/mac/win) will be able to provide TRSP module officially.

Regards,

2012/8/4 Stephen Woodbridge <woodbri@swoodbridge.com>

Hi Guys,

I strongly recommend that you use the turn restrict shortest path (TRSP) algorithm and not Shooting star.

TRSP is significantly faster. It handles all the cases that Shooting Star is supposed to handle and it handles cases that are not supported by shooting star.

My mind is getting a little fuzzy at this point but if I recall the problems with shooting star.

  1. v1.02 or 1.03 was the last working version and it had bugs
  2. you can not say where on an edge you want to start like you can with TRSP
  3. if the start or end edge is one-way then I think the one-wayness is ignored.
  4. in the results the real cost to traverse the edge is not reported correctly, I think it always reports the “cost” attribute not the one it used in solving the graph.
  5. it is like 2-5 times slower than TRSP, this might be because of bugs introduced in the later version changes

I think it would be a better use of time and effort to just create a wrapper to TRSP the is identical to Shooting star so you can call shooting star and have it executed by TRSP. Then we only have one algorithm to maintain and bug fix.

I believe TRSP is getting moved into the main release as part of the pgRouting 2.0 release, but I don’t know when that might be.

Thanks,
-Steve

On 8/4/2012 10:32 AM, Ricardo Bayley wrote:

Hi Sanak

What is the Shooting Star reverse cost issue which still remain for the
pg9.1 win build ?

Regards,

Ricardo

2012/7/6 Sanak <geosanak@gmail.com mailto:[geosanak@gmail.com](mailto:geosanak@gmail.com)>

Hi guys,

Thanks for response :slight_smile:

I had added the each build environments to skydrive,
so if someone who want to make custom build on Windows exists,
use these one.

http://sdrv.ms/NFCgr2
± Build.zip … for 32bit work folder. (extract to "C:")
± MinGW.zip … for 32bit build environment. (extract to "C:"
and run “C:\MinGW\msys\1.0\msys.bat”)
± Build64.zip … for 64bit work folder. (extract to "C:")
± ming64.zip … for 64bit build environment. (based on PostGIS
one. extract to "C:" and run “C:\ming64\msys\msys.bat”)

Regards,

2012/7/3 Sanak <geosanak@gmail.com mailto:[geosanak@gmail.com](mailto:geosanak@gmail.com)>

Hi list,

I had build pgRouting git version for Windows
PostgreSQL9.1(x86_32/x86_64).

https://github.com/sanak/pgrouting/downloads
± pgRouting-git-sanak-mingw64_20120703_pg-9.1(x86_64).zip =>
64bit version
± pgRouting-git-sanak-mingw32_20120703_pg-9.1(x86_32).zip =>
32bit version

  • Both include David Techer’s roads.sql (for postgis1.x/2.x).
    (See http://www.davidgis.fr/documentation/pgrouting-1.02/)
  • If you use roads_postgis2.x.sql on PostGIS 2.0, in addition to
    “postgis.sql” and “spatial_ref_sys.sql”, “legacy.sql” is necessary.
  • Shooting Star reverse cost issue still remain. (I will check
    Steve Horn’s
    fixes(https://github.com/stevehorn/pgrouting/commits/) till next
    week)
  • This archive is not ver.1.05, because many other fixes
    includes after 1.05 release.

Build instruction is here.
https://github.com/sanak/pgrouting/blob/mingw/BUILD.mingw
https://github.com/sanak/pgrouting/blob/mingw/BUILD.mingw64

And I will create github “Pull Request”(sanak:mingw) to
pgrouting:master soon.

Regards,

Pgrouting-users mailing list

Pgrouting-users@lists.osgeo.org mailto:[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

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