[Babase] WeatherHawk design review

Niki Learn nlearn at princeton.edu
Mon Jul 6 15:32:07 EDT 2009


> There was no data provided for 2300 on 2005-07-02 - that row should be
> deleted.  I was not aware of duplicate date/times occurring.  A quick
> look
> at t29/05/2009 shows me identical data for the two dates.  I will
> verify
> that the others are like the same and then we can delete the extra
> rows.
> Problem solved.

Karl wrote:
Yay!   700+ rows are a lot to delete manually.  It might be
easier to delete with a sql delete statement and re-upload.

Maybe things got uploaded twice?

Niki wrote: 
Those data are in the original Excel sheet twice.  Each pair is right next
to each other too.  They must have accidentally been pasted in twice and
then at some point the whole lot sorted by date and hour to land them next
to each other like that.  I want to delete them from the Excel sheet in any
case.  But after I verify that they are all identical duplicates it may well
be easier to delete them from babase using SQL.

 
Niki further writes:
Um, well the data being there twice in Excel appears only to be true for the
first date on the duplicate list (2009-05-29).  The August 2008 dates are
not duplicated in my Excel sheet.  I do not know why there are two copies in
the whawks table on babase_copy.  

Also, while poking around for the duplicates, I noticed that there is NO
data in the whawks table for 2300 hours.  This probably explains why you
weren't getting any rain for that hour in your queries.  I don't know why
this should be.  My only theory is that you somehow deleted all 2300 data
when getting rid of the blank row for 2005-07-02?  Or maybe something with
creating the time stamp (but you knew there was a blank 2300 row...)?
Otherwise I'm stumped on that one because the data is in the file we
originally gave you.





More information about the Babase mailing list