[pgrouting-users] removal of the find nearest node/link/etc from 2.0

[Stephen V. Mather]

Hmm, poking under the hood, most of the logic Greg built is in PHP not as a plpgsql anyway.  But, the question remains for the other functions  :)

Best,
Steve


[http://sig.cmparks.net/cmp-ms-90x122.png] Stephen V. Mather
GIS Manager
(216) 635-3243 (Work)
clevelandmetroparks.com<http://www.clemetparks.com>



________________________________
From: pgrouting-users-bounces at lists.osgeo.org [pgrouting-users-bounces at lists.osgeo.org] on behalf of Stephen V. Mather [svm at clevelandmetroparks.com]
Sent: Thursday, May 16, 2013 10:09 AM
To: pgRouting users mailing list
Subject: [pgrouting-users] removal of the find nearest node/link/etc from 2.0

Hi All,

What is the rationale/thought behind removing the find nearest node/link/etc from the 2.0 version of pgRouting?

Greg Allensworth wrote some code for us which extends that problem to search for nearest node within a distance, respecting polygon barriers, to avoid, for example, finding the nearest node Y from point X to start routing when there's a cliff or steep slop preventing a walker from getting to a network node to start the routing.  I was just about to e-mail him to suggest maybe we could contribute it, when I saw that that family of functions is going away... .

Top of hill
X______
       \
        \
         \
          \____Y   Bottom of hill

Best,
Steve

[http://sig.cmparks.net/cmp-ms-90x122.png] Stephen V. Mather
GIS Manager
(216) 635-3243 (Work)
clevelandmetroparks.com<http://www.clemetparks.com>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pgrouting-users/attachments/20130516/358d5c11/attachment.html>