Better error handling in geojson conversion

[mgrauer]

@jeffbaumes noticed this today with some dirty data. Add some exception handling in the object conversion code, log any exceptions, and proceed past the bad row.

Either that, or get cleaner data. 🚿

[aashish24]

@mgrauer I already have created a issue for it #252

[aashish24]

Its not the problem that we are getting bad data

[mgrauer]

This was a separate issue to #252, there was data that didn't have the mapped "latitude" and "longitude" fields on certain rows, and would cause the entire dataset conversion to fail. Instead, those rows should be skipped during conversion. I think there was an issue of some incorrect formats of lat/long values also for certain rows.

[aashish24]

his was a separate issue to #252, there was data that didn't have the mapped "latitude" and "longitude" fields on certain rows, and would cause the entire dataset conversion to fail. Instead, those rows should be skipped during conversion. I think there was an issue of some incorrect formats of lat/long values also for certain rows.

Ah okay, sorry for the noise then.