Incoherent values set for length and reverse_cost

[guibar]

The version as reported by unbuntu dpkg -s is 2.0.0-release-ppa1~trusty1

I have imported the OSM file for the city of Sao Paulo obtained from mapzen. I have used osm2pgrouting with the the mapconfig_for_cars.xml configuration file. I end up with weird values for length and reverse_cost. I imagine I am supposed to obtain the same values for both these fields.

In one case, I get an edge whose real length is 78m (as measured by Qgis) having length= 0.0776140599087553 and reverse_cost = 77614.0599087553. In another of length 34m I get length = 32645.0955223135 and reverse_cost = 0.0326450955223135. So there seems to be a factor of 1 million between the 2, sometimes length=reverse_cost/1000000 and sometimes reverse_cost=length/1000000. Is there a reason for this or is this a bug? Thanks,

[cvvergara]

@guibar Can you try the version 2.1.0-alpha