Better check for data internal consistency than via unit-testing

[AlexLipp]

Some WaterCompanies use the StatusStart field on the API instead of the LatestEventEnd field. However, sometimes these don't always accord, and so they fail the unit-tests. This seems slightly harsh on the software given bad input datasets. However, we would like to be able to test this sensibly. So, perhaps a warning during object initiation rather than failing the unit-test?

Similarly, unit-tests are being failed by false time-stamps and incorrect coordinates. Should these be unit-tests or errors with the data?