It’s been a long time coming, but it’s really and truly here.
First, we have to reiterate that Season 7 would never have been possible without your help. Last summer, our long-term National Science Foundation funding ran out and we were facing a gap in funding that could have closed down the camera survey forever. We launched the Save Snapshot Serengeti campaign to make sure that Season 7 happened — and because of your support, it did. Thank you, again, for making this project possible in so many ways.
And now! The hard won photos of Season 7 are here.
Season 7 is a big one, running from May 2013 all the way through to the end of November. That’s 7 months! In that time, the long rains faded and the roads became dusty. Stan, whose face you’ve seen so many times checking cams
began a master’s program in Dar es Salaam, and Norbert took over checking the cameras in his place.
Back in Minnesota, Margaret defended her dissertation and began a new post doc at Harvard working with the Phenocam project. I’ve been frantically analyzing data from Seasons 1-6 to finish my dissertation. And Meredith became the newest member of the Snapshot Serengeti team.
So, stop whatever you’re doing for a few minutes and go check out Season 7. Because really, whose day *isn’t* brightened by photos like this?
Yippee! More waving grass! 😉
Congratulations to Stan for continuing that valuable education and hello to Norbert whose smiling face will be welcome, and welcome to Meredith who is so lucky as to have joined you, Ali. And thanks for all your hard work to make it possible for us to see these beautiful animals in their natural habitat. Now I know what I’ll be doing with my evenings for quite awhile.
I’m already checking some photos. Looks like there are fewer wildebeest here. I also noticed that fires have been taken place.
mm, seems to a problem with Chromium on Ubuntu; nothing much except the nice hardwood background and the words “Just a moment, please…” appears
Gimme some wildebeests – can’t wait…
Oy! We’ll look into that issue as soon as we can.
Our web guys think you might have your Java Script disabled — can you try their suggestion below and let me know if it works?
So if they go to the Chrome Menu -> Settings -> Click Advanced settings at the bottom -> click “Content Settings” then uncheck “Block third-party cookies and site data” that should resolve this issue.
Yes, that worked (the cookie and site data thing); thanks!
Is that a costumary thing to require from your users?
I’m not sure what the technical reasons are behind it, but I imagine those settings are needed so the website can communicate properly with the underlying database…