[pgrouting-users] routing_core_smart problem
wal3 at mindspring.com
Sat Dec 3 08:55:49 EST 2011
Yes, those lines are correct.
Without the second argument to the function call you get an unknown (-1)
This route segment is then returned in the routing result along with the
others with the correct srid.
From: pgrouting-users-bounces at lists.osgeo.org
[mailto:pgrouting-users-bounces at lists.osgeo.org] On Behalf Of Daniel Kastl
Sent: Friday, December 02, 2011 9:58 PM
To: pgRouting users mailing list
Subject: Re: [pgrouting-users] routing_core_smart problem
Thank you very much for sharing this information!
I have also created this ticket:
So you're talking about the following two lines?
* Line 191
* Line 205
On Sat, Dec 3, 2011 at 4:26 AM, Worth Lutz <wal3 at mindspring.com> wrote:
I have found what appears to be a problem in one of the routing_core_smart
In the function locate_point_as_geometry there are two lines which call the
These functions are called when line_substring returns a point.
In the geometryfromtext function calls, there is no second argument for the
srid. This produces a geometry with a "-1" for the srid.
When I use shootingstar_smart in my script, MapServer fails on trying to
work with two geometries with different srids.
Adding the second argument to the geometryfromtext function fixed this
problem. The only geometry with the "-1" srid was the one created by these
I hope this helps someone.
Pgrouting-users mailing list
Pgrouting-users at lists.osgeo.org
Georepublic UG & Georepublic Japan
eMail: <mailto:daniel.kastl at georepublic.de> daniel.kastl at georepublic.de
Web: <http://georepublic.de/> http://georepublic.de
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.1873 / Virus Database: 2102/4652 - Release Date: 12/02/11
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pgrouting-users