I'm not really sure, but as far as I remember pgRouting creates a graphedges on-the-fly each time you calculate a route. Hence a combination of FALSE TRUE does make sense because in this case pgRouting creates additional reverse edgesones. osm2po outputs undirected graphs with reverse_cost, meaning you should get correct results with regards to the one-ways. Here FALSE TRUE should be set. As a consequence TRUE TRUE is the combination which doesn't make sense. Because the reverse cost is implicitly set by the forward cost of the reverse edge. But maybe Daniel is following this thread and can give us a final best-practise.
I'm not really sure, but as far as I remember pgRouting creates a graph on-the-fly each time you calculate a route. Hence a combination of FALSE TRUE does make sense because in this case pgRouting creates additional reverse edges. osm2po outputs undirected graphs with reverse_cost, meaning you should get correct results with regards to the one-ways. Here FALSE TRUE should be set. But maybe Daniel is following this thread and can give us a final best-practise.
I'm not really sure, but as far as I remember pgRouting creates edges on-the-fly each time you calculate a route. Hence a combination of FALSE TRUE does make sense because in this case pgRouting creates additional reverse ones. osm2po outputs undirected graphs with reverse_cost, meaning you should get correct results with regards to the one-ways. Here FALSE TRUE should be set. As a consequence TRUE TRUE is the combination which doesn't make sense. Because the reverse cost is implicitly set by the forward cost of the reverse edge. But maybe Daniel is following this thread and can give us a final best-practise.
I'm not really sure, but as far as I remember pgRouting creates a graph on-the-fly each time you calculate a route. Hence a combination of FALSE TRUE does make sense because in this case pgRouting creates additional reverse edges. osm2po outputs undirected graphs with reverse_cost, meaning you should get correct results with regards to the one-ways. Here FALSE TRUE should be set. But maybe Daniel is following this thread and can give us a final best-practise.
I'm not really sure, but as far as I remember pgRouting creates a graph on-the-fly each time you calculate a route. Hence a combination of FALSE TRUE does make sense because in this case pgRouting creates additional reverse edges. osm2po outputs undirected graphs with reverse_cost.
I'm not really sure, but as far as I remember pgRouting creates a graph on-the-fly each time you calculate a route. Hence a combination of FALSE TRUE does make sense because in this case pgRouting creates additional reverse edges. osm2po outputs undirected graphs with reverse_cost, meaning you should get correct results with regards to the one-ways. Here FALSE TRUE should be set. But maybe Daniel is following this thread and can give us a final best-practise.
I'm not really sure, but as far as I remember pgRouting creates a graph on-the-fly each time you calculate a route. Hence a combination of FALSE TRUE does make sense because in this case pgRouting creates additional reverse edges. osm2po outputs undirected graphs with reverse_cost.
lang-sql