You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we are only feeding the "latest year" (the last year of data that we have, not necessarily the current year) to the frontend of the website. We should track the below fields over time so that we can build further data visualizations (e.g. issue #4).
Fields to track over time:
Submission Status (so we know if they skipped a year?)
Square Footage
TotalGHGEmissions
GHGIntensity
SiteEUI
SourceEUI
ENERGYSTARScore
ElectricityUse
NaturalGasUse
DistrictSteamUse
DistrictChilledWaterUse
The main script for this change should be src/data/scripts/clean_and_pare_down_data_current_year.py. The current thinking is we either modify that component to do what we want or, more ideally, we create a new script that outputs to a different file to maintain the stability of current processes.
This should output to a separate CSV file in the dist (e.g. buildings_across_years.csv) so that building list pages and search pages don't need to do a bunch of complex filtering. Also the current ranking UI might break. We'd basically have a latest data set (what we have right now) and the historical data we can query building by building.
The text was updated successfully, but these errors were encountered:
Depends on #89.
Currently we are only feeding the "latest year" (the last year of data that we have, not necessarily the current year) to the frontend of the website. We should track the below fields over time so that we can build further data visualizations (e.g. issue #4).
Fields to track over time:
The main script for this change should be
src/data/scripts/clean_and_pare_down_data_current_year.py
. The current thinking is we either modify that component to do what we want or, more ideally, we create a new script that outputs to a different file to maintain the stability of current processes.This should output to a separate CSV file in the dist (e.g.
buildings_across_years.csv
) so that building list pages and search pages don't need to do a bunch of complex filtering. Also the current ranking UI might break. We'd basically have a latest data set (what we have right now) and the historical data we can query building by building.The text was updated successfully, but these errors were encountered: