[pgrouting-users] weighted costs

Thank you Steve.I understand the use of costs because i learn with arcgis in university. In knows days i introduce the open source software in my business.
I am new with pg routing and i am modelling accessibility. I only like to know if exists more information or examples about costs with pg routing.
Thanks for your explanation.

Pedro Costa
Enviado do meu Android

Stephen Woodbridge

I regularly use costs for shortest time, shortest path, dynamically modify cost based traffic feeds and accident reports. Similar to accidents one could modify road outages because of mud slides, earth quakes, or flooding. We also have some users that are looking a flow analysis, so basically there are not any limitations that I can think of. We also support complex multi-edge turn restrictions using the TRSP code branch and in theory shooting star (but this is currently broken).

-Steve

On 3/17/2012 5:55 PM, pedrocostaarma@sapo.pt wrote:

Thank you Steve.I understand the use of costs because i learn with
arcgis in university. In knows days i introduce the open source software
in my business.
I am new with pg routing and i am modelling accessibility. I only like
to know if exists more information or examples about costs with pg routing.
Thanks for your explanation.

Pedro Costa
Enviado do meu Android

Stephen Woodbridge escreveu:

On 3/16/2012 8:12 AM, Pedro Costa wrote:
> Hello list,
>
> Does anybody know tutorial or more detailed information about the use of
> weighted costs?
> I only know that:
> http://workshop.pgrouting.org/chapters/advanced.html

Cost is just a positive value (negative edge cost are not allow). You
can use distance as a cost, or time as a cost, or turn angle as a cost,
or anything you want that makes sense for what you are modelling. The
issues is what are you modelling and and what do you want to take into
account and can you model that factor as a cost or a component of the cost.

For example, you could convert all costs into some increase number of
seconds to traverse from node A to node B. then you could model the
distance and average speed as time. If you had an attribute at a node
the indicated a traffic light or stop sign, you could add some
additional average wait time to the edges passing through that node. If
you had an attribute say the road had lots of potholes, you could assume
some lower average speed, etc.

You have to transform the things you are modelling into some unit or
unitless value as a cost.

-Steve W
_______________________________________________
Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users

_______________________________________________
Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users