[pgrouting-users] Nasty crash from pgRouting

[Richard Marsden]

Anton & Daniel,

Thanks.

I saw some references to problems with negative reverse_cost. I've checked
the data and I don't have any negative cost or reverse_cost values. Plenty
of zeroes though.

Highest node value is 49,608,314 - so I don't think it is the integer
overflow problem I'm seeing discussed.

I also tried Iran (northern hemisphere, not too big, imperfect road data in
osm) and it also crashes. The common thread seems to be that countries where
I can't match all (geonames-derived) cities with osm nodes, crash using
valid nodes. This isn't a simple "route cannot be found" as my UK Belfast
example demonstrates (no routes possible from Belfast to the England - no
crash occurs)

One problem is that all I'm getting is a big crash - nothing indicates what
the problem actually is.

My laptop can boot into Ubuntu but the partition will be too small and the
cpu too slow.

The machine I'm using is my main batch processing /testing machine. It
currently doesn't have space for a Unix/Linux partition, but has enough
spare disk bays.  I was already thinking of buying a large (1TB+) hard disk
for this project. Although I've managed to squeak by with what I have, and
PostGres's requirements aren't too big, manipulating planet.osm files does
take some disk space!

Perhaps this is the way forward then: New disk and try building an Ubuntu
partition with postgres/etc. Assuming I don't have to rerun osm2po, it
should take me a couple of days to rebuild everything.
Most of my 'stack' should run fine on Ubuntu - Postgres, PostGis, Python.
Windows is being used partly for historical reasons (earlier versions of my
Python scripts used Windows for a good reason which no longer applies), but
also I'm using Excel for my output. Perhaps there's a cross-platform Python
library I can use. If not, I could create CSV files and "tie them together"
with a Windows-based script (they're simple data sheets but I am relying on
some formatting to make the data easier to use).

re. building: I actually do most of my dev in Windows but using Visual
Studio. I've seen the pgRouting Windows build instructions and they don't
look very Windows friendly! Believe it or not I would be happier doing such
builds in a Unix/Linux type of environment...     (I've built my own UMN
Mapserver with FreeBSD in the past).

The project can't go forward if these crashes continue. So a little bit of a
gamble that a new disk (or two if I decide on RAID) and Ubuntu will fix
it...


Richard




On Sun, Jan 30, 2011 at 9:51 PM, Daniel Kastl <daniel at georepublic.de> wrote:

> Hi Richard,
>
> You could try OSGeo Live DVD with already installed pgRouting in Virtualbox
> for example just to see if a newer version of would solve your issue:
> http://live.osgeo.org/
>  <http://live.osgeo.org/>As Anton mentioned, there seem to be not many
> developers out there, who are willing (or have the knowledge) to contribute
> Windows binaries.
> My feeling is that most pgRouting installations are running on Linux
> servers, while most users, who just want to try out pgRouting, prefer to do
> this on Windows.
>
> Daniel
>
> 2011/1/31 Anton Patrushev <anton.patrushev at georepublic.de>
>
> Hi Richard,
>>
>> Unfortunately Win binaries are quite old because nobody is willing to
>> make new ones.
>> There can be few different reasons why it crushes (data problem for
>> example). Do you have any Linux box around to test your data with
>> newer version of pgRouting?
>>
>> Anton.
>> _______________________________________________
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/pgrouting-users/attachments/20110131/53283b81/attachment-0001.html