Open aakashysharma opened 7 years ago
The data is not an error, as you can see in the osm:maxspeed Currently osm2pgrouting handles the numeric case. for the other cases, currently, it assigns the default value given in the configuration file.
A Q to myself: how to handle the rest of the cases of the maxspeed variable in the configuration file?
Maybe it's data error, however while importing Australia's map file from 2014 I get a lot of such warnings. Source file: http://download.geofabrik.de/australia-oceania/australia-140101.osm.pbf
unknown maxspeed3 value: 100; 60; 100
Maybe such weird issues could be handled.