[pgrouting-users] [Fwd: [mapserver-users] Re: OpenStreetMap + osm2pgsql = pgRouting]

[Stephen Woodbridge]

This is probably because the OSM data is not properly noded at all 
intersections. For example, this is bad for routing:

         C
         |
A------------------B
         |
         D

In the example above lines AB and CD cross.

         C
         |E
A-------+----------B
         |
         D

For routing you need a node E at the intersection with segments:

AE, EB, CE, DE

This has bee discussed on the list, you might also check the archives 
for the postGIS list or post a message there on how to fix your data.

-Steve
  http://imaptools.com/

-------- Original Message --------
Subject: [mapserver-users] Re: OpenStreetMap + osm2pgsql = pgRouting
Date: Mon, 17 May 2010 15:00:46 -0700 (PDT)
From: roshni.spain <roshni.aruna at gmail.com>
To: mapserver-users at lists.osgeo.org
References: <1274130822829-5067095.post at n2.nabble.com>


Looking further into the matter,
i have noticed that the only cases where i have managed to get some result
with the shortest_path function is when there is a straight line between A
and B, but if i need to do A and C, and there is no straight line between
them (suppose something like A => B => C), then no result will be returned
:(

The same applies for other routing algorithms ... and still no clue
-- 
View this message in context: 
http://osgeo-org.1803224.n2.nabble.com/OpenStreetMap-osm2pgsql-pgRouting-tp5067095p5067309.html
Sent from the Mapserver - User mailing list archive at Nabble.com.
_______________________________________________
mapserver-users mailing list
mapserver-users at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users