[pgrouting-dev] How many people use the wrapper functions?
Stephen Woodbridge
woodbri at swoodbridge.com
Sat May 11 18:59:55 PDT 2013
Hi Worth,
Thank you for the feedback. It is really important the people speak up
on this because our current thinking is that we will probably take most
of the wrapper functions and dump them into a depreciated
pgrouting-legacy.sql file that will get copied to the server, but not
installed when you CREATE EXTENSION pgrouting;
I have talked with Daniel about improving the documentation and may be
adding a chapter that explains how to write your own wrapper function.
Our thought is that if we had fewer functions that were better
documented that it would be easier for people to make sense of how to
use from the beginning.
Regarding shooting star, you should just start using TRSP. In fact it
has the ability to specify an edge and a percentage along the edge for
the start and end locations. It also about 5 times faster than shooting
start.
With regards to the parallel edge problem. We have this in dijkstra and
astar and it is on my list of things to fix before the release. I am not
sure if trsp has this or not, but if you can make a test for it I would
be interested in the results.
Thanks,
-Steve
On 5/11/2013 7:51 PM, Worth Lutz wrote:
> Hi Steve,
>
> I used one of the wrappers, shootingstar_sp_smart I think, but had to modify
> it due to problems. I think that it is the one which uses shooting star
> which I've since heard doesn't work.
>
> I think that it works for us as all we are using is length as cost to find
> the length from a to b. No turn restrictions or anything.
>
> I chose it because the wrapper let me choose a point and it split the
> nearest edge and hooked up the point to that edge at the split.
>
> Another reason I chose it was that it worked for the following situation:
>
> ----------\
> / \
> / \
> A -----/ B
> |_____________________/
>
>
> Other algorithms would choose the upper edge because that is what was found
> first as they tried to go from A to B. I was just learning about routing and
> did not want to go figure out how to modify my network to split the long
> path where there were multiple paths between nodes.
>
> I've been following your work lately as I will be upgrading our situation to
> Postgres 9 and PostGIS 2 at some point. I was waiting for you to get things
> settled out before asking which algorithm I should look at to replace
> shootingstar.
>
> Thanks for your work on this project.
>
> Worth Lutz
>
>
> -----Original Message-----
> From: pgrouting-dev-bounces at lists.osgeo.org
> [mailto:pgrouting-dev-bounces at lists.osgeo.org] On Behalf Of Stephen
> Woodbridge
> Sent: Saturday, May 11, 2013 4:21 PM
> To: pgRouting Users List; pgRouting Dev List
> Subject: [pgrouting-dev] How many people use the wrapper functions?
>
> Hi all,
>
> Daniel and I have been wondering if people use the wrapper function
> versus the core functions directly? Or if you have written your own
> wrapper functions? etc.
>
> The core functions are the low level function that directly call the
> internal library functions.
>
> The wrapper functions are all the additional plpgsql convenience
> functions that generate more complex SQL queries and then call the core
> functions.
>
> I know that I never use the wrapper functions because I found them to
> messy and inconsistent and have hard coded values in them, etc. So I
> wrote my own high level wrapper functions that made it easy for me to
> work with the core functions.
>
> So I thought it would be wise to ask our users what they use? and how
> they use pgRouting, so we do not may a decision like "Throw out the
> wrapper functions" without some input from the user community.
>
> PLEASE TAKE ACTION and let us know!
>
> Thanks,
> -Steve
> _______________________________________________
> pgrouting-dev mailing list
> pgrouting-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/pgrouting-dev
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2013.0.3336 / Virus Database: 3162/6317 - Release Date: 05/11/13
>
> _______________________________________________
> pgrouting-dev mailing list
> pgrouting-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/pgrouting-dev
>
More information about the pgrouting-dev
mailing list