[engolling]

@engolling, We both know that this question about wrong or invalid records was started with a problem caused by the use of AVR boards manager 1.6.22 and 1.6.23 which messes the system clock which by turn causes that records on the data logger have a wrong timestamp.

Considering that there are hundreds of bug reports related to avr 1.6.22 I'm not concerned it it. Recommendation on Arduino.cc is: if a software not works with 1.6.22 or 1.6.23 revert back to 1.6.21

So, why are we complicating or creating the idea that WeatherDuino stores invalid records on the logger?

Due to the bug i had the 35th of Oktober written on the Display for example. I don't know which timestamp is saved here, but it can not be good  .
Moreover I'm thinking of the possibility to specify a time range where the data should be kept and the other stuff should be deleted.

For those that are not inside the matter we are talking about, I think its important to say that this strange date (35th of Oktober) referred by engolling, which was also stored on the logger, is a consequence of compiling the weatherduino code using avr boards manager 1.6.22 or 1.6.23, otherwise it would never have happened. At least I never saw it happen before.

Just to clarify:
Of course we know that this was (and still is) a result of a bug in the Arduino AVR board library. It took us a whole evening to find out what happened.  
In my opinion there was never a bug in the WeatherDuino source code causing a data problem and also not in the WeatherDuino logger. This was all a result of the faulty Arduino.

Like I said before, I will have a closer look at all the code especially how the logger works and more important what WeeWx does with the loaded data and then I will decide.

Have a nice day,
engolling