<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Thanks for the hints Mario and Daniel,<br>
<br>
I'll have look and let you know as soon as I can put my hands on
it.<br>
<pre class="moz-signature" cols="72">--
Christophe</pre>
<br>
Le 02/07/2012 10:09, Daniel Kastl a écrit :<br>
</div>
<blockquote
cite="mid:CABXBSH_9BAx3hMxXfqUWiMF-2a_EeL9XADc4THwSisqiGykqSA@mail.gmail.com"
type="cite"><br>
<br>
<div class="gmail_quote">On Mon, Jul 2, 2012 at 9:41 AM,
"Christophe Damour (SIGéal)" <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:sigeal@sigeal.com"
target="_blank">sigeal@sigeal.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
I totally agree with both of you, Daniel and Mario.<br>
I too was a bit confused by existing wrappers when I began to
use pgrouting.<br>
Wrappers should add extra functionalities.<br>
<br>
A function that accept source and target x/y would indeed be
usefull, especially if it can return the first and last edge
cut at the actual projection of source and target x/y. I will
need such a function soon, so I will have to work on it...<br>
</blockquote>
<div><br>
</div>
<div>This is indeed an often requested "feature". But it can be
more tricky than it initially looks like.</div>
<div>There is some example you can start with: <a
moz-do-not-send="true"
href="https://github.com/pgRouting/pgrouting-contrib/tree/master/wrapper">https://github.com/pgRouting/pgrouting-contrib/tree/master/wrapper</a></div>
<div><br>
</div>
<div>For wrappers "shipped" we should define some criteria. As
more we have as more needs to be documented and maintained.
Instead a tutorial or a few recipes to help users to write and
modify their own custom wrappers might make more sense. </div>
<div><br>
</div>
<div>Daniel</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Any hints appreciated.<br>
<br>
--<br>
Christophe<br>
<br>
<br>
Le 02/07/2012 09:28, Mario Basa a écrit :
<div class="HOEnZb">
<div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Daniel,<br>
<br>
I agree. Right now it really is quite confusing which
function to use,<br>
and the description of each function is not also very
helpful.<br>
<br>
I am curious though why is it that there is no sp
function that<br>
accepts source_x,source_y and target_x,target_y
parameters similar to<br>
that of driving_distance. This I think, will be very
useful.<br>
<br>
Mario.<br>
<br>
<br>
On Mon, Jul 2, 2012 at 4:11 PM, Daniel Kastl <<a
moz-do-not-send="true"
href="mailto:daniel@georepublic.de" target="_blank">daniel@georepublic.de</a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Mario,<br>
<br>
In my opinion I would drop functions like the one you
mentioned and reduce<br>
the number of wrappers as much as possible.<br>
<br>
I think a good and useful wrapper function is one,
that selects a BBOX<br>
containing start and end point and returns records
with geometries.<br>
Then everyone can modify it as needed. I don't think
we should simplify<br>
those basic wrappers and make assumptions like naming
the cost column<br>
"length" or so.<br>
<br>
What do you think?<br>
<br>
Daniel<br>
<br>
<br>
<br>
<br>
On Mon, Jul 2, 2012 at 9:02 AM, Mario Basa <<a
moz-do-not-send="true"
href="mailto:mario.basa@gmail.com" target="_blank">mario.basa@gmail.com</a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
<br>
The core wrapper functions have<br>
<br>
dijkstra_sp_delta_directed<br>
astar_sp_delta_directed<br>
<br>
with "length" hard coded as cost for some reason.<br>
<br>
While astar_sp_delta_cc has a cost column parameter,
but all it does<br>
is call astar_sp_delta_cc_directed with<br>
reverse_cost=false,directed=false.<br>
<br>
There is also no dijkstra_sp_delta_cc with a cost
column parameter, so<br>
a user has to rename the column containing the cost
value to "length"<br>
to use this clipping function. Etc....<br>
<br>
Personally I am getting confused with all these
functions and would<br>
like to just trim it down to dijkstra_sp_delta and
astar_sp_delta with<br>
a cost column parameter along with reverse_cost and
directed<br>
parameters.<br>
<br>
Opinions?<br>
<br>
Mario.<br>
_______________________________________________<br>
pgrouting-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:pgrouting-dev@lists.osgeo.org"
target="_blank">pgrouting-dev@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev"
target="_blank">http://lists.osgeo.org/mailman/listinfo/pgrouting-dev</a><br>
</blockquote>
<br>
<br>
<br>
--<br>
Georepublic UG & Georepublic Japan<br>
eMail: <a moz-do-not-send="true"
href="mailto:daniel.kastl@georepublic.de"
target="_blank">daniel.kastl@georepublic.de</a><br>
Web: <a moz-do-not-send="true"
href="http://georepublic.de" target="_blank">http://georepublic.de</a><br>
<br>
_______________________________________________<br>
pgrouting-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:pgrouting-dev@lists.osgeo.org"
target="_blank">pgrouting-dev@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev"
target="_blank">http://lists.osgeo.org/mailman/listinfo/pgrouting-dev</a><br>
<br>
</blockquote>
_______________________________________________<br>
pgrouting-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:pgrouting-dev@lists.osgeo.org"
target="_blank">pgrouting-dev@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev"
target="_blank">http://lists.osgeo.org/mailman/listinfo/pgrouting-dev</a><br>
</blockquote>
<br>
_______________________________________________<br>
pgrouting-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:pgrouting-dev@lists.osgeo.org"
target="_blank">pgrouting-dev@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev"
target="_blank">http://lists.osgeo.org/mailman/listinfo/pgrouting-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<span
style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse">Georepublic
UG & Georepublic Japan<br>
eMail: <a moz-do-not-send="true"
href="mailto:daniel.kastl@georepublic.de"
style="color:rgb(66,99,171)" target="_blank">daniel.kastl@georepublic.de</a><br>
Web: <a moz-do-not-send="true" href="http://georepublic.de/"
style="color:rgb(66,99,171)" target="_blank">http://georepublic.de</a></span><br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
pgrouting-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pgrouting-dev@lists.osgeo.org">pgrouting-dev@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev">http://lists.osgeo.org/mailman/listinfo/pgrouting-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>