[pgrouting-users] TRSP error - Invalid result geometry node_id:-1edge_id:0

Wed Aug 19 06:49:04 PDT 2015

Ross,

Thanks for the catch about 2.0.  I forgot to flip the labeling and that's
pointing at develop which has since been flipped to 2.1 branch.  I'll fix
that.

Regarding RCs.  Yes will be packaging those later this week so should be
available Monday.  But sounds like you already have it

Unfortunately I won't be packaging 2.1 for PostgreSQL 9.2 as installer, but
the binaries will be available at release time.  

Only reason for that is that the pgRouting 2.1.0 will be available with
PostGIS 2.2 installers, and I'm planning to drop 9.2 for PostGIS 2.2.

Thanks,

Regina

From: pgrouting-users-bounces at lists.osgeo.org
[mailto:pgrouting-users-bounces at lists.osgeo.org] On Behalf Of McDonaldR
Sent: Wednesday, August 19, 2015 9:37 AM
To: 'pgRouting users mailing list' <pgrouting-users at lists.osgeo.org>
Subject: Re: [pgrouting-users] TRSP error - Invalid result geometry
node_id:-1edge_id:0

OK, testing on Windows 7 64bit with the following setups confirms your fix:

Testing with PostGIS 2.1.8 and pgRouting 2.0.0

==============================================

"PostgreSQL 9.4.4, compiled by Visual C++ build 1800, 64-bit"

"POSTGIS="2.1.8 r13780" GEOS="3.4.2-CAPI-1.8.2 r3924" PROJ="Rel. 4.8.0, 6
March 2012" GDAL="GDAL 1.11.1, released 2014/09/24 GDAL_DATA not found"
LIBXML="2.7.8" LIBJSON="UNKNOWN" TOPOLOGY RASTER"

"2.0.0";"pgrouting-2.0.0";"0";"f26831f";"master";"1.53.0"

TRSP returns route not found

----------------------------------------------------------------------------
-----

"PostgreSQL 9.3.9, compiled by Visual C++ build 1600, 64-bit"

"POSTGIS="2.1.8 r13780" GEOS="3.4.2-CAPI-1.8.2 r3924" PROJ="Rel. 4.8.0, 6
March 2012" GDAL="GDAL 1.11.1, released 2014/09/24 GDAL_DATA not found"
LIBXML="2.7.8" LIBJSON="UNKNOWN" TOPOLOGY RASTER"

"2.0.0";"pgrouting-2.0.0";"0";"d6ed2cb";"master";"1.53.0"

TRSP returns route not found

----------------------------------------------------------------------------
-----

"PostgreSQL 9.2.13, compiled by Visual C++ build 1600, 64-bit"

"POSTGIS="2.1.8 r13780" GEOS="3.4.2-CAPI-1.8.2 r3924" PROJ="Rel. 4.8.0, 6
March 2012" GDAL="GDAL 1.11.1, released 2014/09/24 GDAL_DATA not found"
LIBXML="2.7.8" LIBJSON="UNKNOWN" TOPOLOGY RASTER"

"2.0.0";"pgrouting-2.0.0";"0";"f26831f";"master";"1.53.0"

TRSP returns route not found

----------------------------------------------------------------------------
-----

Testing with PostGIS 2.2.0dev and pgRouting 2.1.0alpha and rc1

==============================================================

"PostgreSQL 9.4.4, compiled by Visual C++ build 1800, 64-bit"

"POSTGIS="2.2.0dev r13937" GEOS="3.5.0-CAPI-1.9.0 r4088" PROJ="Rel. 4.9.1,
04 March 2015" GDAL="GDAL 2.0.0, released 2015/06/14 GDAL_DATA not found"
LIBXML="2.7.8" LIBJSON="0.12" TOPOLOGY RASTER"

"(2.1.0,pgrouting-2.1.0-rc1,81,5fa89b2,develop_2_1_0,1.58.0)"

TRSP returns a valid route

----------------------------------------------------------------------------
-----

"PostgreSQL 9.3.9, compiled by Visual C++ build 1600, 64-bit"

"POSTGIS="2.2.0dev r13937" GEOS="3.5.0-CAPI-1.9.0 r4088" PROJ="Rel. 4.9.1,
04 March 2015" GDAL="GDAL 2.0.0, released 2015/06/14 GDAL_DATA not found"
LIBXML="2.7.8" LIBJSON="0.12" TOPOLOGY RASTER"

"(2.1.0,pgrouting-2.1.0-rc1,81,5fa89b2,develop_2_1_0,1.58.0)"

TRSP returns a valid route

----------------------------------------------------------------------------
-----

"PostgreSQL 9.2.13, compiled by Visual C++ build 1600, 64-bit"

"POSTGIS="2.2.0dev r13937" GEOS="3.5.0-CAPI-1.9.0 r4088" PROJ="Rel. 4.9.1,
04 March 2015" GDAL="GDAL 2.0.0, released 2015/06/14 GDAL_DATA not found"
LIBXML="2.7.8" LIBJSON="0.12" TOPOLOGY RASTER"

"(2.1.0,pgrouting-2.1.0-alpha1,81,5fa89b2,develop_2_1_0,1.58.0)"

TRSP returns a valid route

----------------------------------------------------------------------------
-----

Is there a RC1 for PG9.2.x?

I also noticed the  zipped binaries at
http://winnie.postgis.net/download/windows/pg94/buildbot/pgrouting-pg94-bina
ries-2.0w64gcc48.zip  are labelled as 2.0 but is actually the 2.1.0 RC1

Thanks

Ross

From: pgrouting-users-bounces at lists.osgeo.org
<mailto:pgrouting-users-bounces at lists.osgeo.org>
[mailto:pgrouting-users-bounces at lists.osgeo.org] On Behalf Of Paragon
Corporation
Sent: 18 August 2015 19:11
To: 'pgRouting users mailing list'
Subject: Re: [pgrouting-users] TRSP error - Invalid result geometry
node_id:-1edge_id:0

Ross,

The true test would be testing on 64-bit Windows.

As I recall when I was doing the debugging of this problem, the issue did
not happen under windows 32-bit.  It only happened under windows 64-bit.

As KoNagase  mentioned we made changes to make it work in pgRouting 2.1.0,
but the underlying issue is not fixed. Which is what is meant by "fixed
temporary"

As a general precaution - in windows 64-bit - it only works if you have
NOTICE enabled either for logging or client messages - which is the default,
so should work for most folks.

We will investigate the issue more for the 2.0.1 and 2.1.1 releases.

Thanks,

Regina 

From: pgrouting-users-bounces at lists.osgeo.org
<mailto:pgrouting-users-bounces at lists.osgeo.org>
[mailto:pgrouting-users-bounces at lists.osgeo.org] On Behalf Of McDonaldR
Sent: Tuesday, August 18, 2015 11:28 AM
To: 'pgRouting users mailing list' <pgrouting-users at lists.osgeo.org
<mailto:pgrouting-users at lists.osgeo.org> >
Subject: Re: [pgrouting-users] TRSP error - Invalid result geometry
node_id:-1edge_id:0

Regina,

Using the 2.1.0 version
["2.1.0";"pgrouting-2.1.0-alpha1";"81";"5fa89b2";"develop_2_1_0";"1.58.0"]
on my Windows 7 32bit PC the problem is indeed fixed. 

TRSP works with and without reverse costs, with and without turn
restrictions and with both vertices and edges.

Huge thanks to you, Steve, Ko and Vicky (and others) for all the work that
goes into making pgRouting better and better.  It is much appreciated.  I am
going to be running a couple of short training sessions using pgRouting
shortly after showing a couple of live examples at our internal GIS user
group that piqued interest.

Ross

From: pgrouting-users-bounces at lists.osgeo.org
<mailto:pgrouting-users-bounces at lists.osgeo.org>
[mailto:pgrouting-users-bounces at lists.osgeo.org] On Behalf Of Paragon
Corporation
Sent: 18 August 2015 14:29
To: 'pgRouting users mailing list'
Subject: Re: [pgrouting-users] TRSP error - Invalid result geometry
node_id:-1edge_id:0

Ross,

Were you able to try the 2.1.0 beta binaries?  

This issue should be fixed on those.

Thanks,

Regina

From: pgrouting-users-bounces at lists.osgeo.org
<mailto:pgrouting-users-bounces at lists.osgeo.org>
[mailto:pgrouting-users-bounces at lists.osgeo.org] On Behalf Of McDonaldR
Sent: Tuesday, August 18, 2015 8:53 AM
To: pgrouting-users at lists.osgeo.org <mailto:pgrouting-users at lists.osgeo.org>

Subject: [pgrouting-users] TRSP error - Invalid result geometry
node_id:-1edge_id:0

Hello list

I am getting an error using the pgr_trsp function with vertices.

[Invalid result geometry node_id:-1 edge_id:0] using the pgRouting Layer
plugin in QGIS

The query is:

SELECT *

FROM pgr_trsp('SELECT gid as id, source::integer, target::integer,
cost_len::float AS cost

FROM itn_network', 

 30,

60, 

 false, 

 false

);

Result

0;-1;0;0 using PgAdmin

If I use the function with edges then it works as expected

SELECT *

FROM pgr_trsp('SELECT gid as id, source::integer, target::integer,
cost_len::float AS cost

FROM itn_network', 

 2958, 0.5,

1194, 0.5, 

 false, 

 false

);

Result

0;-1;2958;302.909919799321

1;21;12;3289.06571781744

2;22;2534;0

3;1841;1484;0

4;1063;669;657.261388446325

5;1062;671;306.606908032689

6;1064;2381;0

7;428;241;0

8;427;69391;0

9;1504;1104;0

10;1069;675;0

11;1066;672;0

12;430;242;0

13;429;1763;0

14;506;290;814.718952140309

15;507;1157;206.661904345321

16;505;69401;394.173213311315

17;2093;69400;1152.8033703581

18;24;1156;0

19;1109;712;911.407628015424

20;1110;69367;82.6836380428031

21;2275;2954;55.7924940561552

22;2818;69406;10.2909471381108

23;2262;2171;93.7878062207647

24;1548;1148;0

25;1547;1543;0

26;1901;2178;0

27;1546;2172;0

28;1897;1540;0

29;1542;1968;22.2622766251952

30;495;284;0

31;494;2612;0

32;499;286;0

33;498;69364;0

34;1557;1155;0

35;1556;1154;0

36;1555;2603;0

37;146;79;0

38;145;1981;35.7573399535413

39;148;80;0

40;147;2994;0

41;2842;2996;0

42;26;14;0

43;25;1170;0

44;1572;2993;0

45;1133;736;0

46;1132;737;0

47;1134;1173;0

48;1136;739;0

49;150;82;1139.31607861894

50;151;1175;267.426016400421

51;1197;794;0

52;604;349;0

53;603;2077;0

54;1941;1589;0

55;1604;1206;0

56;1196;793;0

57;1195;1207;0

58;1189;788;491.087128220612

59;1190;789;300.17025240827

60;1191;1586;122.598743787454

61;167;1840;0

62;171;92;0

63;170;1579;0

64;1593;1199;0

65;1592;68167;0

66;1183;1828;0

67;1933;1578;0

68;1932;1985;0

69;1595;1200;0

70;1594;1984;26.9342460479565

71;1931;1577;67.4166151627323

72;1181;782;312.414537400116

73;1179;781;0

74;1180;68143;0

75;591;341;0

76;590;772;0

77;1167;68151;0

78;1170;773;0

79;1169;774;0

80;1171;1194;0

Any suggestions on how to debug this?  Using the same two vertices with the
Djikstra functions works fine.

I am running it on Postgresql 9.2.13 64bit with PostGIS 2.1.7 and pgRouting
2.0.0

"POSTGIS="2.1.7 r13414" GEOS="3.4.2-CAPI-1.8.2 r3924" PROJ="Rel. 4.8.0, 6
March 2012" GDAL="GDAL 1.11.1, released 2014/09/24" LIBXML="2.7.8"
LIBJSON="UNKNOWN" TOPOLOGY RASTER"

"2.0.0";"pgrouting-2.0.0";"0";"f26831f";"master";"1.53.0"

Thanks

Ross

Ross McDonald | GIS Data Coordinator | Resources Department, IT Division |
Angus Council, Angus House, Orchardbank Business Park, Forfar, DD8 1AT

T: 01307 476419 | F: 01307 476401 | E:  <mailto:mcdonaldr at angus.gov.uk>
mcdonaldr at angus.gov.uk 

This message is strictly confidential. If you have received this in error,
please inform the sender and remove it from your system. If received in
error you may not copy, print, forward or use it or any attachment in any
way. This message is not capable of creating a legal contract or a binding
representation and does not represent the views of Angus Council. Emails may
be monitored for security and network management reasons. Messages
containing inappropriate content may be intercepted. Angus Council does not
accept any liability for any harm that may be caused to the recipient system
or data on it by this message or any attachment. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pgrouting-users/attachments/20150819/7c6f2a8e/attachment-0001.html>