Wrong edge costs after collapsing edges?

[aheld84]

Dear pfaedle developers,

Could it be the case that edge costs are calculated from beeline distances (start node to end node distance) instead of the real line string length here

pfaedle/src/pfaedle/osm/OsmBuilder.cpp

Line 1122 in 6467076

e->pl().setCost(costToInt(dist(e->getFrom(), e->getTo()) /

after collapsing the edges?

Or did I misunderstand the concept of the edge cost? My understanding is that the edge cost should be proportional to the travel time, so the real length should be used .

All the best
Alex

[patrickbr]

Indeed - this seems to have been introduced last year. Previously, the logic here was to first compute the costs on the uncollapsed edges, and adding them up during the subsequent collapsing.

This explains some strange results I noticed during the last months. Thanks for pointing that out!

Fixed in 5c1ad45