smoningi / sf-environment-benchmark Goto Github PK

• figure out why histogram for metrics other than energystar aren't working properly
• update gh-pages branch
• send link to Seung-hee

I was wondering if we could add a getting started section to the README.md? Something like

step 1. clone repo
step 2. start server
step 3. profit!

since we are using mapbox map tiles, the attribution should be at the bottom of the map.

• transition on exit() and enter()
• add axis labels
• pretty-format y-axis
• highlight a particular building
• flip order of colors (blue = lower EUI)

who wrote the modeling code? we should credit him in the README

• highlight bar should fade slowly if moused over nothing?
• transition bars on exit() and enter()
• add y-axis
• add axis labels

choose to display 'GHG emissions' or 'SITE/Source EUI' on map instead of 'Energy Star Score'
When the user clicks on a selected metric:

• the map should update with the new data
• the legend colors should update
• the scorebox displayed value should update
• the histogram should update

for instance, College/University

This may be better as for the entire working group, but it's like this:

The brigadeHub folks are doing some good stuff in regards to having a contributing.md doc. Check this out:

https://github.com/sfbrigade/brigadehub/wiki/Contributing

https://github.com/sfbrigade/brigadehub/blob/develop/.github/CONTRIBUTING.md

when switching metrics, something's not refreshing:
in maps, try switching metics to site eui, select "all" explicitly and the histogram distribution changes.

@geoffnet, since you want to get more familiar with D3 this is a good place to implement a common D3 pattern and clean up the code a little.

In main.js there is a switch statement to decide the background color of the switchbox element, but we should be able to use the color variable, which is a d3 quantize scale.

I believe it would be a matter of changing the switch to something like scorebox.style.backgroundColor = color(escore) with an if to set the text color accordingly

using newly released landuse dataset we should be able to grab geojson for individual properties using soda api:

https://data.sfgov.org/resource/a2rp-pwkh.json?block_num=0871&lot_num=016
or
https://data.sfgov.org/resource/a2rp-pwkh.json?blklot=0871016

with the release of new data, we should grab a new geojson file that contains only the parcels that are present.
this should be in the form of a script that makes a SodaQL query to data.sfgov.org