Failure on corrupted data

I found that my migration failed and tracked it to corrupted data. My CCK table had a few values in it like this:

GEOMETRYCOLLECTION(POINT())

and with no lat or lon, the migration died. Once I found this, I could delete these records from the table and the migration worked. Seems that it could catch this and bypass them. The table had over 50,000 rows and has been accumulating for years, so there is no way to track how the corruption got in there. They were older records.

I called this a bug report, though I suppose it could be considered a feature request since the module works for properly formed data.