On Fri, 28 Jan 2011, Ethan Furman wrote:
:'JCM-10B':'JCM-10B':'JCM-10B':'JCM-10B':'JCM-10B':'JCM-10B':'JCM-10B':
:2004-08-16:2005-06-07:2005-08-31:2006-06-12:2006-09-21:2007-06-21:2007-12-11:
'Depth to Water':76.75:77.51:82.15:73.17:72.66:84.44:96.41:
'HeightToSky':8917.72:7812.28:9153.72:8411.91:8837.51:8784.22:9244.76:
'SomethingElse':182.98:817.82:352.99:721.57:292.38:379.28:447.92:
Ethan,
That's close enough. The spreadsheet was created with, in this case two
locations (JCM-10B and JCM-20B) as the top row. The second row contains
dates, and succeeding rows each contain a water quality paramter and the
value measured for that parameter at that location on that date.
I'm having a hard time understanding your description of what the second,
third, etc, lines should look like... if I carry out your table further,
is it correct?
::'JCM-10B':'2004-08-16':'Depth to water':76.75::
::'JCM-10B':'2004-08-16':'HeightToSky':8917.72::
::'JCM-10B':'2004-08-16':'SomethingElse':182.89::
If that's correct, what happens to the remaining values on lines 3, 4, etc?
Yes, this is correct. Instead of the organization above, I want each row
to be a complete record of location, date, parameter and value. Somewhat
analogous to transposing rows and columns in the spreadsheet, but that's not
a solution.
In the re-written file, there will be one row for each unique set of
location, date, parameter, and value. For this file, there are 2 locations,
22 dates, and 32 parameters (each with 1 value for that parameter on that
date at that location) or 1408 distinct rows.
Does this make it clearer?
Unfortunately, no one now or before at the client's site knows anything
about databases or data storage so the spreadsheets are a horrible mess in
terms of extracting the data.
Rich
_______________________________________________
Portland mailing list
[email protected]
http://mail.python.org/mailman/listinfo/portland
