GreenInfo-Network / seattle-building-dashboard

Energy benchmarking for Seattle
https://greeninfo-network.github.io/seattle-building-dashboard/
ISC License
1 stars 0 forks source link

Move content tables from CARTO to the repo as CSV data files #59

Closed tomay closed 10 months ago

tomay commented 10 months ago

CARTO now has a limit of 10 tables, we currently have 18, and in any case, we need to consider alternate approaches to using CARTO in this project.

A number of content tables are stored in CARTO, alongside the building data and building footprints. These could easily be stored as CSV files in the repository (and managed as shared files in Google Docs, if that's needed)

Citywide Scorecard

Table name: citywide_scorecard_data Last update 5 years ago, and the most recent entry is for 2016. Is this still relevant? There is an entry for this in seattle.json but I am not sure where it is used in the app

Links

Table name: links Definitely needed

FAQ

Table name: faq Definitely needed

Glossary

Table name: glossary Definitely needed

tomay commented 10 months ago

I think that the City Scorecard is no longer offered, but that is a guess at this point. I see a handful of references to a city_scorecard in the code, and city_scorecard.js in src/app/views/scorecards/charts but I don't see anything in the actual app (a button, or a link) where I can click and make a city scorecard.

tomay commented 10 months ago

Download data, then modify code to pull from CSV for the following:

City Scorecard:

tomay commented 10 months ago

Links, FAQ and Glossary are now working in the application from CSVs served from src/data/

City Scorecard is no longer used.

I've saved copies of these content tables here: https://drive.google.com/drive/folders/15x9wCxh6X4hc18GCnsu2Tw4avdTLv79H?usp=drive_link

If the client wants to edit these in Drive, then we could create Sheets from them in this same location and share. The update process would be different, we'd then have to export to CSV, save to the repo, test and commit.

tomay commented 10 months ago

Latest code is running Links, FAQ and Glossary from CSV saved in /src/data/

Once this is updated to production at the end of this phase, it will be safe to delete those tables on CARTO, but not before