Spencer Gardner

Same problem here on the latest release built from source on Ubuntu 16.04. No idea what the cause is.

osm2pgrouting --version This is osm2pgrouting Version 2.1

Here's the file I'm getting errors with: [brookings.osm.gz](https://github.com/pgRouting/osm2pgrouting/files/512075/brookings.osm.gz)

@cvvergara it seems strange that the file would have errors. It's from Mapzen's custom extract tool which should be pulling straight from planet.osm. Are errors like this common in the...

That approach makes sense to me. I think @woodbri is right, a typical user isn't going to care about the broken ways at the edge of the extract.

Another example osm_id: 302156855 This one doesn't have any relations defined so might be easier to troubleshoot.

Also, please disregard the version change. I was playing around with things on my local copy and forgot to revert that line.

The only columns that could be overlooked are optional columns according to the spec, right? In other words, if our model defines a column as nullable, it might be left...

I'm OK with outputting empty columns. As for the field validation, what are the challenges? I don't imagine the mechanics of converting between, for example, binary and 0/1 is too...