AW: [pgrouting-dev] General question for understanding

[Hens,Markus M.]

Hey Daniel,

you mean its only possible for ways instead of nodes?

Markus
________________________________________
Von: pgrouting-dev-bounces at lists.osgeo.org [pgrouting-dev-bounces at lists.osgeo.org] im Auftrag von Daniel Kastl [daniel at georepublic.de]
Gesendet: Freitag, 11. Februar 2011 15:17
An: pgRouting developers mailing list
Betreff: Re: [pgrouting-dev] General question for understanding

Hi Markus.

It's only possible for nodes. But as somehow the vehicle that needs to pass this node also must pass one or more ways to this node, you could add the hight limitation as an attribute to the ways, right?
In you SQL query you could exclude all road links that contain a node that has a height limitation for example.

Daniel


2011/2/11 Hens,Markus M. <m.hens at student.fontys.nl<mailto:m.hens at student.fontys.nl>>
Hi Daniel,

thank you for the information. I understand these informations but I have one more question.

If I have a node for example a bridge with an attribute for height and my vehicle is higher I would like to set the cost very high for the node.
My question is if it is possible to set cost for nodes or only for ways.

Markus
________________________________________
Von: pgrouting-dev-bounces at lists.osgeo.org<mailto:pgrouting-dev-bounces at lists.osgeo.org> [pgrouting-dev-bounces at lists.osgeo.org<mailto:pgrouting-dev-bounces at lists.osgeo.org>] im Auftrag von Daniel Kastl [daniel at georepublic.de<mailto:daniel at georepublic.de>]
Gesendet: Freitag, 11. Februar 2011 14:47
An: pgRouting developers mailing list
Betreff: Re: [pgrouting-dev] General question for understanding

Hi Markus,

Now it worked ;-)

2011/2/11 Hens,Markus M. <m.hens at student.fontys.nl<mailto:m.hens at student.fontys.nl><mailto:m.hens at student.fontys.nl<mailto:m.hens at student.fontys.nl>>>
Hey all,

I am new to pgRouting and I have a general question.
When I have imported my osm data to pgRouting database and calculate a route via A* from x to y does the result contains any information about where it is allowed to drive?

The route shouldn't contain any roads in the result you're not allowed to drive at. It should instead return you another way instead.


For example would the result route me in an oneway street where I am not allowed to drive?

The "cost" attribute for a road link is the cost from start to end node, the "reverse_cost" attribute is the cost in the opposite direction: http://www.pgrouting.org/docs/1.x/astar.html
So a oneway street has very high cost in one of these two cost attributes. If this cost is very high it will always try to find another way ... except there is no other way. But you could easily check this if the result returns very high "cost"


Does the result really contains only the shortest path with no information about prohibitions or am I wrong?

Yes. You have to model your network that it reflects these prohibitions.

Daniel



Best regards,

Markus Hens_______________________________________________
pgrouting-dev mailing list
pgrouting-dev at lists.osgeo.org<mailto:pgrouting-dev at lists.osgeo.org><mailto:pgrouting-dev at lists.osgeo.org<mailto:pgrouting-dev at lists.osgeo.org>>
http://lists.osgeo.org/mailman/listinfo/pgrouting-dev



--
Georepublic UG & Georepublic Japan
eMail: daniel.kastl at georepublic.de<mailto:daniel.kastl at georepublic.de><mailto:daniel.kastl at georepublic.de<mailto:daniel.kastl at georepublic.de>>
Web: http://georepublic.de<http://georepublic.de/>
_______________________________________________
pgrouting-dev mailing list
pgrouting-dev at lists.osgeo.org<mailto:pgrouting-dev at lists.osgeo.org>
http://lists.osgeo.org/mailman/listinfo/pgrouting-dev



--
Georepublic UG & Georepublic Japan
eMail: daniel.kastl at georepublic.de<mailto:daniel.kastl at georepublic.de>
Web: http://georepublic.de<http://georepublic.de/>