Added gamekey data to the schedule so that we can tie in with nflvid.
Some data updates. Fix the ATL/SF playoff game so that it is identified
as being finished.
Make game over checking a bit more flexible.

Also add a method to games that returns the season it belongs too.
Add schedule info to each game for convenience.
pep8 updates
Version bump to 1.1.9.
Make the FieldPosition type more useful.
Make the game string a bit nicer.
Change the quarter correction logic to be a bit smarter.

Before it was just using the quarter of the last play in the drive
according to the JSON. But this isn't always correct. Instead, use
the maximum quarter number of all the plays in the drive. If that
doesn't work out, use a heuristic to increase the quarter number by
one when the drive start time is greater than the drive end time
(and only in quarters 1 and 3, of course).
Change the play duplication logic and move it to _json_plays.

Previously, we were throwing out any drive that contained a duplicate
play. Not only does this sometimes throw out too much data, but it
doesn't detect all duplicate plays. Namely, sometimes a duplicate play
has a different play id, which was escaping our detection. Therefore,
detect duplicate plays by also looking at local data: the quarter, time
and description string.
Correct some *seriously* corrupt data that is beyond heuristic
correction. In this particular game, I had to remove dozens of
duplicate plays.
Apparently this data was updated on NFL's web site. So refresh it.
Version bump to 1.1.10 and updated player meta data.
Add yahoo team abbreviations.
A property on player objects to guess the position of the player
based on aggregate statistics when meta data isn't available.
Progress on a test for nflgame, to compare with Yahoo stats for 2012.
The results of the first nflgame test.
I guess punting_blk does not include a count.
Test results for different ways of stat gathering.

This seems to affirm that the "max" between plays and games is a decent
approach, and at the very least, almost always better than either
constituent on its own.

The only other method I can think of is to assume that game statistics,
when present, are always correct.
Player json data update.