Changed water_levels catalog to jive with new data storage structure from GLOS.py scraper.

[DanielJMaher]

Changed water_levels catalog to jive with new data storage structure from GLOS.py scraper.

[kknee]

does this change how charlton should be accessing the data? Not showing up in http://72.44.60.22/glos/ now.

[DanielJMaher]

To be in proper CF compliance I needed to swap the dimensions of the dataset (from [Time, Stations] to [Stations, Time]. I didn’t think it would cause an issue, but I guess I was wrong. It should be fairly easy to swap how they’re read to be put into the data portal. If it proves to be too difficult I could change it myself easily.

I’m sorry I didn’t highlight this change on Friday.

From: Kelly Knee [mailto:notifications@github.com]
Sent: Saturday, May 17, 2014 11:05 AM
To: glos/glos_catalog
Cc: Daniel Maher
Subject: Re: [glos_catalog] Changed water_levels catalog to jive with new data storage structure from GLOS.py scraper. (#30)

does this change how charlton should be accessing the data? Not showing up in http://72.44.60.22/glos/ now.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/30#issuecomment-43409268.