Removes CARTO and just use the Google Sheets public JSON API directly. This way, we only make one AJAX call for data, and the initial load takes about the same amount of time. The only thing we lose is the map point hover state. Closes #45
Removes the cookie-based saving feature since we haven't really talked about using it much, and it sounds like it could be more confusing than helpful for our use case. Closes #46
Misc cleanup and refactoring, removing unused libraries
Leaving this open for feedback for a bit, and to confirm that we're alright with getting rid of the saving functionality. CARTO most likely needs to go since they might be charging for API access, but there may be features of the map that we want added or changed. @kwritenow
Leaving this open for feedback for a bit, and to confirm that we're alright with getting rid of the saving functionality. CARTO most likely needs to go since they might be charging for API access, but there may be features of the map that we want added or changed. @kwritenow