<br><br><div class="gmail_quote">On Mon, Dec 5, 2011 at 12:28 AM, Stephen Woodbridge <span dir="ltr"><<a href="mailto:woodbri@swoodbridge.com">woodbri@swoodbridge.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Daniel,<br>
<br>
Who wrote the routing_core_smart.sql functions?<br></blockquote><div><br></div><div>Anton</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Is there any documentation of them? It would be nice if we had:<br></blockquote><div><br></div><div>Right ... would be nice to have ;-) </div><div>I actually just decided to publish the wrapper, because there were several questions in the past how the pgRouting demo could start the route from/to the point you clicked. </div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
1. description of the major public entry points and what the arguments should be.<br></blockquote><div><br></div><div><div>It even needs an extra table "network_statistics" to work.</div><div>But on the other hand it was supposed to be an example of writing a more complex wrapper function. It's not really a generic function and may not work with any type of data. </div>
<div>There are probably several possibilities to improve the functions. </div><div><br></div><div>Daniel</div><div><br></div></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
2. comments in the code that explain what the overview strategy is and/or a high level pseudocode of how it executes<br>
<br>
Thanks,<br>
-Steve<div class="im"><br>
<br>
On 12/2/2011 9:57 PM, Daniel Kastl wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
Hi Lutz,<br>
<br>
Thank you very much for sharing this information!<br>
I have also created this ticket:<br>
<a href="https://github.com/pgRouting/pgrouting-contrib/issues/3" target="_blank">https://github.com/pgRouting/<u></u>pgrouting-contrib/issues/3</a><br>
<br>
So you're talking about the following two lines?<br>
<br></div>
* Line 191<br>
<a href="https://github.com/pgRouting/pgrouting-contrib/blob/master/wrapper/routing_core_smart.sql#L191" target="_blank">https://github.com/pgRouting/<u></u>pgrouting-contrib/blob/master/<u></u>wrapper/routing_core_smart.<u></u>sql#L191</a><br>
* Line 205<div class="im"><br>
<a href="https://github.com/pgRouting/pgrouting-contrib/blob/master/wrapper/routing_core_smart.sql#L205" target="_blank">https://github.com/pgRouting/<u></u>pgrouting-contrib/blob/master/<u></u>wrapper/routing_core_smart.<u></u>sql#L205</a><br>
<br>
Best regards,<br>
Daniel<br>
<br>
<br>
On Sat, Dec 3, 2011 at 4:26 AM, Worth Lutz <<a href="mailto:wal3@mindspring.com" target="_blank">wal3@mindspring.com</a><br></div><div class="im">
<mailto:<a href="mailto:wal3@mindspring.com" target="_blank">wal3@mindspring.com</a>>> wrote:<br>
<br>
Hi all,<br>
<br>
I have found what appears to be a problem in one of the<br>
routing_core_smart functions.<br>
<br>
In the function locate_point_as_geometry there are two lines which<br>
call the function geometryfromtext.<br>
<br>
These functions are called when line_substring returns a point.<br>
<br>
In the geometryfromtext function calls, there is no second argument<br>
for the srid. This produces a geometry with a “-1” for the srid.<br>
<br>
When I use shootingstar_smart in my script, MapServer fails on<br>
trying to work with two geometries with different srids.<br>
<br>
Adding the second argument to the geometryfromtext function fixed<br>
this problem. The only geometry with the “-1” srid was the one<br>
created by these function calls.<br>
<br>
I hope this helps someone.<br>
<br>
Worth Lutz<br>
<br>
<br>
______________________________<u></u>_________________<br>
Pgrouting-users mailing list<br></div>
<a href="mailto:Pgrouting-users@lists.osgeo.org" target="_blank">Pgrouting-users@lists.osgeo.<u></u>org</a> <mailto:<a href="mailto:Pgrouting-users@lists.osgeo.org" target="_blank">Pgrouting-users@lists.<u></u>osgeo.org</a>><div class="im">
<br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-<u></u>users</a><br>
<br>
<br>
<br>
<br>
--<br>
Georepublic UG & Georepublic Japan<br></div>
eMail: <a href="mailto:daniel.kastl@georepublic.de" target="_blank">daniel.kastl@georepublic.de</a> <mailto:<a href="mailto:daniel.kastl@georepublic.de" target="_blank">daniel.kastl@<u></u>georepublic.de</a>><br>
Web: <a href="http://georepublic.de" target="_blank">http://georepublic.de</a> <<a href="http://georepublic.de/" target="_blank">http://georepublic.de/</a>><div class="im"><br>
<br>
<br>
______________________________<u></u>_________________<br>
Pgrouting-users mailing list<br>
<a href="mailto:Pgrouting-users@lists.osgeo.org" target="_blank">Pgrouting-users@lists.osgeo.<u></u>org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-<u></u>users</a><br>
</div></blockquote><div class="HOEnZb"><div class="h5">
<br>
______________________________<u></u>_________________<br>
Pgrouting-users mailing list<br>
<a href="mailto:Pgrouting-users@lists.osgeo.org" target="_blank">Pgrouting-users@lists.osgeo.<u></u>org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-<u></u>users</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 href="mailto:daniel.kastl@georepublic.de" style="color:rgb(66, 99, 171)" target="_blank">daniel.kastl@georepublic.de</a><br>
Web: <a href="http://georepublic.de/" style="color:rgb(66, 99, 171)" target="_blank">http://georepublic.de</a></span><br>