<div dir="ltr">Hi Eyad,<div><br></div><div>Looking at just a few of your network images, the network is definitely broken afterwards. So it's not the fault of the shortest path algorithm.</div><div><br></div><div>Without access to the data I can only guess, but often CAD data may contain geomtries, that don't work well for GIS.</div><div><br></div><div>When I look at some screenshots and which parts have been removed, could it be, that your data contains circles or self-intersecting linestrings for example?</div><div><br></div><div>Daniel</div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 19, 2014 at 4:16 PM, AUS - Eyad <span dir="ltr"><<a href="mailto:b00038807@aus.edu" target="_blank">b00038807@aus.edu</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks Steve..<br>
<br>
It seems that I may need to re-install the pgRouting to update the<br>
"ST_DumpPoints()"?<br>
<br>
Can I split the lines on CAD instead? Then pgr_nodeNetwork() adds nodes<br>
correctly? Or I may get to same situation if the bug is in the nodding, not<br>
in splitting lines?<br>
<br>
I have done a cross-check for the pgr_kdijkstraCost and pgr_kdijkstraPath<br>
results. The cost results are exactly the same. But I'm still not sure if<br>
the calculated cost is done based on the real shortest_path because I can't<br>
see the outcome on the map<br>
<br>
If you think that the bug of nodding is only impacting the reflective Path<br>
outcome? but the Cost outcome is fine? I would rather to complete my<br>
exercise for now as I'm running out of time.. I can fix this later<br>
<br>
Looking forward to hear your 'practical' expert advice, as I'm still<br>
beginner<br>
<br>
Thanks again<br>
<span class=""><br>
Eyad<br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:pgrouting-users-bounces@lists.osgeo.org">pgrouting-users-bounces@lists.osgeo.org</a><br>
[mailto:<a href="mailto:pgrouting-users-bounces@lists.osgeo.org">pgrouting-users-bounces@lists.osgeo.org</a>] On Behalf Of Stephen<br>
Woodbridge<br>
</span><div><div class="h5">Sent: Friday, December 19, 2014 2:36 AM<br>
To: <a href="mailto:pgrouting-users@lists.osgeo.org">pgrouting-users@lists.osgeo.org</a><br>
Subject: Re: [pgrouting-users] Wierd results using pgr_kdijkstraPath<br>
<br>
On 12/18/2014 1:51 PM, AUS - Eyad wrote:<br>
> Also pgr_analyzeGraph function returned in the Messages Tab:<br>
><br>
> NOTICE: ANALYSIS RESULTS FOR SELECTED EDGES:<br>
> NOTICE: Isolated segments: 7<br>
> NOTICE: Dead ends: 351<br>
> NOTICE: Potential gaps found near dead ends: 1<br>
> NOTICE: Intersections detected: 62<br>
> NOTICE: Ring geometries: 0<br>
><br>
> I don't know if this is positive or negative, but would like to know your<br>
> feedback<br>
><br>
> Maybe the isolated segments are lines which are not connected to the<br>
> network? Is there a way to visualize each group of the above lines?<br>
<br>
So this command adds columns "cnt" amd "chk" to the vertices_tmp table.<br>
<br>
Isolated segments are identified by the fact that both the start and end<br>
points are dead-ends:<br>
<br>
select *<br>
from edges a, vertices_tmp b, vertices_tmp c<br>
where a.source=<a href="http://b.id" target="_blank">b.id</a> and a.target=<a href="http://c.id" target="_blank">c.id</a> and b.cnt=1 and c.cnt=1;<br>
<br>
or maybe:<br>
<br>
select *<br>
from vertices_tmp a, edges b<br>
where a.chk>0 and st_dwithin(a.geom, b.geom, <distance>);<br>
<br>
Intersections detected indicates you have lines that cross but are not<br>
noded where they cross. You have to split all lines if they cross and<br>
make sure there is node at the intersection.<br>
<br>
There is a tool pgr_nodeNetwork() that can help, but there has recently<br>
been a big found in it and a patch posted with the ticket for the bug.<br>
<a href="https://github.com/pgRouting/pgrouting/issues/280" target="_blank">https://github.com/pgRouting/pgrouting/issues/280</a><br>
<br>
-Steve<br>
<br>
> Eyad<br>
><br>
><br>
> -----Original Message-----<br>
> From: AUS - Eyad [mailto:<a href="mailto:b00038807@aus.edu">b00038807@aus.edu</a>]<br>
> Sent: Thursday, December 18, 2014 9:54 PM<br>
> To: 'pgRouting users mailing list'<br>
> Subject: RE: [pgrouting-users] Wierd results using pgr_kdijkstraPath<br>
><br>
> The function<br>
><br>
> SELECT pgr_analyzeGraph('schema.network_noded',50,'geom');<br>
><br>
> Returned "OK"<br>
><br>
> Feel free to ask for any other details. I know it's not easy to get things<br>
> done remotely.<br>
><br>
> Eyad<br>
><br>
><br>
> -----Original Message-----<br>
> From: <a href="mailto:pgrouting-users-bounces@lists.osgeo.org">pgrouting-users-bounces@lists.osgeo.org</a><br>
> [mailto:<a href="mailto:pgrouting-users-bounces@lists.osgeo.org">pgrouting-users-bounces@lists.osgeo.org</a>] On Behalf Of Stephen<br>
> Woodbridge<br>
> Sent: Thursday, December 18, 2014 8:25 PM<br>
> To: <a href="mailto:pgrouting-users@lists.osgeo.org">pgrouting-users@lists.osgeo.org</a><br>
> Subject: Re: [pgrouting-users] Wierd results using pgr_kdijkstraPath<br>
><br>
> Ok this sounds reasonable.<br>
><br>
> Give this a try:<br>
> <a href="http://docs.pgrouting.org/dev/src/common/doc/functions/analyze_graph.html" target="_blank">http://docs.pgrouting.org/dev/src/common/doc/functions/analyze_graph.html</a><br>
><br>
> It is hard to diagnose problems remotely via the list.<br>
><br>
> -Steve<br>
><br>
> On 12/18/2014 10:48 AM, AUS - Eyad wrote:<br>
>> Here is st_astext(geom) function result (below table).<br>
>><br>
>> For both createTopology and nodeNetwork functions, I used "50" as<br>
>> tolerance because my data unit is in millimeter. However, the network is<br>
>> done on CAD and fairly not poor in resolution.<br>
>><br>
>> Is this what you wanted, or you need another layout/map? I attached many<br>
>> layouts/maps already in the previous 3 emails.. let me know if you were<br>
>> not able to visualize<br>
>><br>
>> Eyad<br>
>><br>
>> -----Original Message-----<br>
>> From: <a href="mailto:pgrouting-users-bounces@lists.osgeo.org">pgrouting-users-bounces@lists.osgeo.org</a><br>
>> [mailto:<a href="mailto:pgrouting-users-bounces@lists.osgeo.org">pgrouting-users-bounces@lists.osgeo.org</a>] On Behalf Of Stephen<br>
>> Woodbridge<br>
>> Sent: Thursday, December 18, 2014 7:26 PM<br>
>> To: <a href="mailto:pgrouting-users@lists.osgeo.org">pgrouting-users@lists.osgeo.org</a><br>
>> Subject: Re: [pgrouting-users] Wierd results using pgr_kdijkstraPath<br>
>><br>
>> Eyad,<br>
>><br>
>> What does you geomerty look like?<br>
>><br>
>> Select st_astext(geom) from edges limit 10;<br>
>><br>
>> What value did you use for tolerance when creating your topology?<br>
>><br>
>> What value did you use for tolerance when you noded your network?<br>
>><br>
>> -Steve<br>
>><br>
>> On 12/18/2014 10:17 AM, AUS - Eyad wrote:<br>
>><br>
>> > And here I enclose below the resulted travel_costs' table of<br>
>><br>
>> > pgr_dijkstra function:<br>
>><br>
>> ><br>
>><br>
>> > Note that Shortest path cost on original network (between the 2 lines<br>
> of<br>
>><br>
>> > the resulted vector feature) is around 250m (below - by converting<br>
from<br>
>><br>
>> > millimeter to meter) whereas the sum of costs in the above table is<br>
>><br>
>> > around 45m only<br>
>><br>
>> ><br>
>><br>
>> > Thanks..<br>
>><br>
>> ><br>
>><br>
>> > Eyad<br>
>><br>
>> ><br>
>><br>
>> > *From:*AUS - Eyad [mailto:<a href="mailto:b00038807@aus.edu">b00038807@aus.edu</a>]<br>
>><br>
>> > *Sent:* Thursday, December 18, 2014 7:02 PM<br>
>><br>
>> > *To:* 'pgRouting users mailing list'<br>
>><br>
>> > *Subject:* RE: [pgrouting-users] Wierd results using<br>
pgr_kdijkstraPath<br>
>><br>
>> ><br>
>><br>
>> > Here is a prt_sc after trying pgr_dijkstra as follows:<br>
>><br>
>> ><br>
>><br>
>> > SELECT seq, id1 as path, (b.geom) as geom, cost FROM pgr_dijkstra(<br>
>><br>
>> ><br>
>><br>
>> > 'SELECT id, source, target, (st_length(geom) * 0.001) as cost<br>
FROM<br>
>><br>
>> > schema.network_noded',<br>
>><br>
>> ><br>
>><br>
>> > 336, (SELECT MAX(id) FROM schema.l1_pv1), false, false<br>
>><br>
>> ><br>
>><br>
>> > ) a, schema.network_noded b<br>
>><br>
>> ><br>
>><br>
>> > WHERE a.id1=<a href="http://b.id" target="_blank">b.id</a><br>
>><br>
>> ><br>
>><br>
>> > As you may see, there is only too little parts of the network's lines<br>
>><br>
>> > left (on the sides of the layout)! No route is visible<br>
>><br>
>> ><br>
>><br>
>> > Hope this clarifies..<br>
>><br>
>> ><br>
>><br>
>> > Eyad<br>
>><br>
>> ><br>
>><br>
>> > *From:*AUS - Eyad [mailto:<a href="mailto:b00038807@aus.edu">b00038807@aus.edu</a>]<br>
>><br>
>> > *Sent:* Thursday, December 18, 2014 6:29 PM<br>
>><br>
>> > *To:* 'pgRouting users mailing list'<br>
>><br>
>> > *Subject:* RE: [pgrouting-users] Wierd results using<br>
pgr_kdijkstraPath<br>
>><br>
>> ><br>
>><br>
>> > Hi Daniel,<br>
>><br>
>> ><br>
>><br>
>> > Enclosed are 3 maps (1^st prt_sc with the original network, 2^nd &<br>
3^rd<br>
>><br>
>> > prt_sc with the resulted network)<br>
>><br>
>> ><br>
>><br>
>> > Clearly, the majority of the network has faded away<br>
>><br>
>> ><br>
>><br>
>> > Awaiting your feedback, I would work on 2^nd suggestion<br>
>><br>
>> ><br>
>><br>
>> > Regards,<br>
>><br>
>> ><br>
>><br>
>> > Eyad<br>
>><br>
>> ><br>
>><br>
>> > *From:*<a href="mailto:pgrouting-users-bounces@lists.osgeo.org">pgrouting-users-bounces@lists.osgeo.org</a><br>
>><br>
>> > [mailto:<a href="mailto:pgrouting-users-bounces@lists.osgeo.org">pgrouting-users-bounces@lists.osgeo.org</a>] *On Behalf Of<br>
>> *Daniel Kastl<br>
>><br>
>> > *Sent:* Thursday, December 18, 2014 6:28 AM<br>
>><br>
>> > *To:* pgRouting users mailing list<br>
>><br>
>> > *Subject:* Re: [pgrouting-users] Wierd results using<br>
pgr_kdijkstraPath<br>
>><br>
>> ><br>
>><br>
>> > Hi Eyad,<br>
>><br>
>> ><br>
>><br>
>> > It's difficult to give an answer based on your query and problem<br>
>><br>
>> > description only. I guess, that (still) your network topology is not<br>
>><br>
>> > correct. It looks like a data problem.<br>
>><br>
>> ><br>
>><br>
>> > There are 2 things you could do for now:<br>
>><br>
>> ><br>
>><br>
>> > (1) Show us some image of your "weird de-attached "little" pieces"<br>
>><br>
>> ><br>
>><br>
>> > (2) Try a simple shortest path query with one start and one end point<br>
>><br>
>> > and see if it works with pgr_dijkstra function for example.<br>
>><br>
>> ><br>
>><br>
>> > Daniel<br>
>><br>
>> ><br>
>><br>
>> > On Thu, Dec 18, 2014 at 7:37 AM, AUS - Eyad <<a href="mailto:b00038807@aus.edu">b00038807@aus.edu</a><br>
>><br>
>> > <mailto:<a href="mailto:b00038807@aus.edu">b00038807@aus.edu</a>>> wrote:<br>
>><br>
>> ><br>
>><br>
>> > Hello pgr_Experts,<br>
>><br>
>> ><br>
>><br>
>> > I'm trying to get all the routes from a source point (i.e. 336) to a<br>
>><br>
>> > group of target/destination points (located at different edges/ends<br>
of<br>
>><br>
>> > linestrings' network) using the below code:<br>
>><br>
>> ><br>
>><br>
>> > SELECT seq, id1 as path, id2 as node, id3 as edge, (b.geom) as geom,<br>
>><br>
>> > cost FROM pgr_kdijkstraPath(<br>
>><br>
>> ><br>
>><br>
>> > 'SELECT id, source, target, (st_length(geom) * 0.001) as cost FROM<br>
>><br>
>> > schema.network_noded',<br>
>><br>
>> ><br>
>><br>
>> > 336, (SELECT array_agg(id) FROM schema.l1_pv1), false, false<br>
>><br>
>> ><br>
>><br>
>> > ) a, schema.network_noded b<br>
>><br>
>> ><br>
>><br>
>> > WHERE a.id1=<a href="http://b.id" target="_blank">b.id</a> <<a href="http://b.id" target="_blank">http://b.id</a>><br>
>><br>
>> ><br>
>><br>
>> > It's resulting a weird de-attached "little" pieces of my original<br>
>><br>
>> > nodded_network! However, the number of resulted paths is equal to the<br>
>><br>
>> > target/destination points. Please advise:<br>
>><br>
>> ><br>
>><br>
>> > 1)What potential mistake I may have committed?<br>
>><br>
>> ><br>
>><br>
>> > 2)Does it mean that all the calculated travel_cost(s) are wrong (as<br>
> they<br>
>><br>
>> > are reflected/represented by wrong linestrings)?<br>
>><br>
>> ><br>
>><br>
>> > I'm using QGIS 2.4.0 and pgRouting pg93-binaries-2.4.0<br>
>><br>
>> ><br>
>><br>
>> > I found similar question on this list of pgRouting users, asked by<br>
>><br>
>> > Antonio last October<br>
>><br>
>> ><br>
>><br>
(<a href="http://lists.osgeo.org/pipermail/pgrouting-users/2014-October/001992.html" target="_blank">http://lists.osgeo.org/pipermail/pgrouting-users/2014-October/001992.html</a><br>
>><br>
>> > ), but obviously the question is not answered yet?<br>
>><br>
>> ><br>
>><br>
>> > Regards..<br>
>><br>
>> ><br>
>><br>
>> > Eyad<br>
>><br>
>> ><br>
>><br>
>> ><br>
>><br>
>> > _______________________________________________<br>
>><br>
>> > Pgrouting-users mailing list<br>
>><br>
>> > <a href="mailto:Pgrouting-users@lists.osgeo.org">Pgrouting-users@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:Pgrouting-users@lists.osgeo.org">Pgrouting-users@lists.osgeo.org</a>><br>
>><br>
>> > <a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/pgrouting-users</a><br>
>><br>
>> ><br>
>><br>
>> ><br>
>><br>
>> > --<br>
>><br>
>> ><br>
>><br>
>> > Georepublic UG & Georepublic Japan<br>
>><br>
>> > eMail: <a href="mailto:daniel.kastl@georepublic.de">daniel.kastl@georepublic.de</a><br>
<mailto:<a href="mailto:daniel.kastl@georepublic.de">daniel.kastl@georepublic.de</a>><br>
>><br>
>> > Web: <a href="http://georepublic.info" target="_blank">http://georepublic.info</a><br>
>><br>
>> ><br>
>><br>
>> ><br>
> ------------------------------------------------------------------------<br>
>><br>
>> ><br>
>><br>
>> > No virus found in this message.<br>
>><br>
>> > Checked by AVG - <a href="http://www.avg.com" target="_blank">www.avg.com</a> <<a href="http://www.avg.com" target="_blank">http://www.avg.com</a>><br>
>><br>
>> > Version: 2015.0.5577 / Virus Database: 4253/8755 - Release Date:<br>
> 12/17/14<br>
>><br>
>> ><br>
>><br>
>> ><br>
>><br>
>> ><br>
>><br>
>> > _______________________________________________<br>
>><br>
>> > Pgrouting-users mailing list<br>
>><br>
>> > <a href="mailto:Pgrouting-users@lists.osgeo.org">Pgrouting-users@lists.osgeo.org</a><br>
>><br>
>> > <a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/pgrouting-users</a><br>
>><br>
>> ><br>
>><br>
>> _______________________________________________<br>
>><br>
>> Pgrouting-users mailing list<br>
>><br>
>> <a href="mailto:Pgrouting-users@lists.osgeo.org">Pgrouting-users@lists.osgeo.org</a><br>
>><br>
>> <a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/pgrouting-users</a><br>
>><br>
>> -----<br>
>><br>
>> No virus found in this message.<br>
>><br>
>> Checked by AVG - <a href="http://www.avg.com" target="_blank">www.avg.com</a><br>
>><br>
>> Version: 2015.0.5577 / Virus Database: 4253/8755 - Release Date: 12/17/14<br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Pgrouting-users mailing list<br>
>> <a href="mailto:Pgrouting-users@lists.osgeo.org">Pgrouting-users@lists.osgeo.org</a><br>
>> <a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/pgrouting-users</a><br>
>><br>
><br>
> _______________________________________________<br>
> Pgrouting-users mailing list<br>
> <a href="mailto:Pgrouting-users@lists.osgeo.org">Pgrouting-users@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/pgrouting-users</a><br>
> -----<br>
> No virus found in this message.<br>
> Checked by AVG - <a href="http://www.avg.com" target="_blank">www.avg.com</a><br>
> Version: 2015.0.5577 / Virus Database: 4253/8755 - Release Date: 12/17/14<br>
><br>
> _______________________________________________<br>
> Pgrouting-users mailing list<br>
> <a href="mailto:Pgrouting-users@lists.osgeo.org">Pgrouting-users@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/pgrouting-users</a><br>
><br>
<br>
_______________________________________________<br>
Pgrouting-users mailing list<br>
<a href="mailto:Pgrouting-users@lists.osgeo.org">Pgrouting-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/pgrouting-users</a><br>
-----<br>
No virus found in this message.<br>
Checked by AVG - <a href="http://www.avg.com" target="_blank">www.avg.com</a><br>
</div></div>Version: 2015.0.5577 / Virus Database: 4253/8761 - Release Date: 12/18/14<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Pgrouting-users mailing list<br>
<a href="mailto:Pgrouting-users@lists.osgeo.org">Pgrouting-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/pgrouting-users</a><br>
</div></div></blockquote></div><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><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.info" style="color:rgb(66,99,171)" target="_blank">http://georepublic.info</a></span><div><br></div><div><br></div><div><br></div></div></div>
</div>