Don't omit falsy values from csv export

Any falsy value (False, '', 0, etc.) was being omitted from species CSV exports. Change to only exclude actual None values.
Merge pull request #166 from steventlamb/bug/show_falsy_csv_values

Don't omit falsy values from csv export
Upgrade to latest stable version of openlayers

fixes iOS zoom bug
Merge pull request #167 from steventlamb/bug/fix_map_iOS

Upgrade to latest stable version of openlayers
Remove incomplete species name from CSV export

fixes the following reported issue:
"it looks like the scientific name column is just using data from the genus and species fields rather than genus, species, cultivar, and other part of scientific name. All four of those fields should contribute to the scientific name field. If that's not possible, then we need to remove the scientific name field from the export."
Merge pull request #168 from steventlamb/bug/hide_incomplete_species_name

Remove incomplete species name from CSV export
Better species admin
Clear cached model info when reloading panels
Don't commit un-merged rows
Fix waiting info
JS fixup on importer commit was being killed too early
Use 'bytes io' with a latin1 input
Spelling
Fix lint
Disable zoomMethod and transitionEffect

This regression was introduced by c589fea69d8e57bd87e61fe762223a4251f8bff1, upgrading to version 2.13 of OpenLayers, in order to fix broken zoom on mobile devices.

Dots from pervious zoom levels were lingering after zooming, which was determined to be caused by the way OpenLayers was replacing old tiles with new ones in conjunction with slowdowns in geoserver and/or lag in getting tiles from the google maps api.

This fix disables the zoomMethod and transitionEffect, both of with work together to control the animation of how layers change. They perform much faster now.

The only wrinkle here, is that transitionEffect is not documented for the version of OpenLayers we're using (2.13), it's from the 2.6 docs. It's default for 2.6 is listed as null, the same value assignment that fixed this bug. This points to the fact that there's some underdocumented new feature addition or old feature deprecation. It's something to watch out for if this breaks again.
Merge pull request #172 from steventlamb/bug/animation_lag

Bug/animation lag