Since we are talking about easier ways to edit data, I might as well make a pitch for the potential future of Weathercat.
When it comes to editing data, flat files are very hard to edit especially if there is no delimiter in the file.
Which is why it may be wise to phase Weathercat 2.0 onto a database instead of a flatfile.
Editing data on a database using a query is quite simple and it can be simple in a programming prospective too.
Databases dont necessarily need to have a server installed onto the machine, SQLite is an example that comes to mind.
The reason why I am pitching for the cat to be phased onto a database is a more unified data structure which is easy to import data into it and export out.
This unifies what other meteorological companies do with meteorological data which makes it easy to compare data simply.
Remember, this is not intended to be a proposed Weathecat 1.0 feature, perhaps a version 2.0 instead.
I use databases for my weatherdata (they power the backend of this:
http://matangiweather.org/lookback.php )