I'm currently testing pgRouting using OpenStreempMap XML dataset loaded via Osm2PgRouting. My goal is to solve shortest path problems using time driven costs instead of path length.
I noticed that since V 2.1 osm2pgrouting include two nice columns namely cost_s and reverse_cost_s. They aim to express cost in seconds. Theses columns are computed using maxspeed_forward maxspeed_backward properties.
When the OSM dataset include maxspeed attribute you can expect reasonable results. However when theses tags are not filled a default value is applied (controlled by the config.xml file).
This lead to very high maxspeed values in residential area when the road type is set to primary/secondary/tertiary. But 90Km/H inside a town really doesn't sound realistic.
Has anybody already have a fix for that kind of behavior?
I was thinking about setting a lower maxspeed for road that intersect landuse=residential in OSM. Am I reinventing the wheel or is it something to look at?