How do osm2po and osm2pgrouting differ in their algorithms for creating their
ways table ? I've seen significant differences between their processing of the same osm extract.
Processing the same file (us-midwest-latest.osm) from geofabrik using both
osm2pgrouting (and using config for cars only with both) resulted in nearly 400K more entries in the
ways table from
osm2pgrouting than in the corresponding
Does osm2pgrouting just create more nodes/vertices?