I am using the current developer version of pgRouting (2.0.0-dev) on Windows
8, 64Bit with PostgreSQL 9.2 and PostGIS 2.0. When I am running the
pgr_dijkstra(...) procedure the edge id column contains only zeros while the
nodes are perfectly fine. That happens with my own dataset as well as with
the pgRouting sample dataset (have a look at the screenshot). The
pgr_ksp(...) procedure does currently crash the PostgreSQL Server everytime
it is run.
If you have any hint on how the get the edge IDs that would be most
appreciated.
I am using the current developer version of pgRouting (2.0.0-dev) on Windows
8, 64Bit with PostgreSQL 9.2 and PostGIS 2.0. When I am running the
pgr_dijkstra(…) procedure the edge id column contains only zeros while the
nodes are perfectly fine. That happens with my own dataset as well as with
the pgRouting sample dataset (have a look at the screenshot). The
pgr_ksp(…) procedure does currently crash the PostgreSQL Server everytime
it is run.
If you have any hint on how the get the edge IDs that would be most
appreciated.
I am using the current developer version of pgRouting (2.0.0-dev)
on Windows
8, 64Bit with PostgreSQL 9.2 and PostGIS 2.0. When I am running the
pgr_dijkstra(...) procedure the edge id column contains only zeros
while the
nodes are perfectly fine. That happens with my own dataset as well
as with
the pgRouting sample dataset (have a look at the screenshot). The
pgr_ksp(...) procedure does currently crash the PostgreSQL Server
everytime
it is run.
If you have any hint on how the get the edge IDs that would be most
appreciated.
I am using the current developer version of pgRouting (2.0.0-dev) on Windows
8, 64Bit with PostgreSQL 9.2 and PostGIS 2.0. When I am running the
pgr_dijkstra(…) procedure the edge id column contains only zeros while the
nodes are perfectly fine. That happens with my own dataset as well as with
the pgRouting sample dataset (have a look at the screenshot). The
pgr_ksp(…) procedure does currently crash the PostgreSQL Server everytime
it is run.
If you have any hint on how the get the edge IDs that would be most
appreciated.
The cause of this issue may be memory related one,
and we will try to fix this issue as soon as possible.
Regards,
2013/6/28 mw_boness <[hidden email]>
Dear pgRouting Team,
I am using the current developer version of pgRouting (2.0.0-dev) on Windows
8, 64Bit with PostgreSQL 9.2 and PostGIS 2.0. When I am running the
pgr_dijkstra(…) procedure the edge id column contains only zeros while the
nodes are perfectly fine. That happens with my own dataset as well as with
the pgRouting sample dataset (have a look at the screenshot). The
pgr_ksp(…) procedure does currently crash the PostgreSQL Server everytime
it is run.
If you have any hint on how the get the edge IDs that would be most
appreciated.