expand_households fails if zone IDs are floats about populationsim HOT 7 OPEN

How did this csv file end up with floats in it - was it created by populationsim? (If so, then we should fix that bug?)

Or was it user pilot error? (In which case, there are probably lots of places that could happen and we should talk about whether this is an eventuality that we should allow generally - because it doesn't make sense to just fix it in one place and not otehrs...)

from populationsim.

This is a user created input file. I think we should check for this issue at the beginning when we read in inputs.

from populationsim.

For every field in every file that ought to have integers? Do we check to make sure it was a float int and not a float that will be rounded/truncated (in which case maybe it is an error?)

Just wondering why we are fixing this particular random bad input?

from populationsim.

We don't have to fix bad data, but I think we should catch bad data / do more error checking / add more informative error messages / etc. It took me quite some time to figure this out and I'm pretty familiar with PopulationSim.

from populationsim.

Might as well address it opportunistically then - but we should throw an error if the values change when coerced to ints.

from populationsim.

sounds good

from populationsim.

This is also true for the geo crosswalk file as well - the data needs to be ints. We should fix this.

from populationsim.