hi, thanks Anton for your answer at pgrouting forum. i'm goingo to reply here i hope it's ok.
Hi Fernando, I think I answered you already in the PostGIS mailing list. Anyway, it is worth to repeat. You can block edges by assigning high value to cost field. Or, if you wish, you can add one more field, let's say, of boolean type and name it is_blocked, and then use core routing function (not wrapper), where you can limit your search area with non-blocked edges only - "SELECT ... WHERE NOT is_blocked". So i the input sql statement at shortest path function can include where filters? sounds nice. i'm going to try it later (00:16 here lol) thanks a lot Anton A. Patrushev wrote: > > Hi, > > Of course you can. You can put any float value as a cost. And if a > cost of an edge is high enough comparing to other costs, algorithm > will prefer not to pass through that edge. > > Anton. > > On 9/24/08, Nandorov <[EMAIL PROTECTED]> wrote: >> >> can i block some segments? for example cad gives the posibility to put a >> max >> resistance value, let's say it's 100. So if the resistance of your >> segment >> is 100 that segment is blocked and you cannot go thorught this way. if >> this >> possible with pgrouting? >> >> thanks! >> >> >> >> Stephen Woodbridge wrote: >> > >> > Nandorov wrote: >> >> hi, >> >> i've tried pgrouting algorithms and works pretty well. However, i >> dont >> >> know >> >> exactly the way they applied "the resistance" of a way (represented >> by a >> >> multilinestring). has someone worked with pgrouting before? and know >> if >> >> i >> >> can modify their algorithms to adapt them to my requirements? >> >> >> >> thanks >> > >> > "the resistance" is applied as a "cost" to traverse the segment. All >> > cost must be positive. You can use length of the segment as cost for >> > shortest distance. or you can compute and assign a cost value based on >> > other attributes. >> > >> > -Steve >> > _______________________________________________ >> > postgis-users mailing list >> > [email protected] >> > http://postgis.refractions.net/mailman/listinfo/postgis-users >> > >> > >> >> >> -- >> View this message in context: >> http://www.nabble.com/PgRouting-in-PostGIS-tp19638201p19638473.html >> >> Sent from the PostGIS - User mailing list archive at Nabble.com. >> >> _______________________________________________ >> >> postgis-users mailing list >> [email protected] >> http://postgis.refractions.net/mailman/listinfo/postgis-users >> > _______________________________________________ > postgis-users mailing list > [email protected] > http://postgis.refractions.net/mailman/listinfo/postgis-users > > -- View this message in context: http://www.nabble.com/PgRouting-in-PostGIS-tp19638201p19642156.html Sent from the PostGIS - User mailing list archive at Nabble.com. _______________________________________________ postgis-users mailing list [email protected] http://postgis.refractions.net/mailman/listinfo/postgis-users
