Closed macintoshpie closed 2 years ago
@nllong does that column name seem ok to you?
@macintoshpie -- @nllong should weigh in but your name seems good.
And then the user would fill in that value in their imported file, right?
Where do the values for the different regions come from? Do we have a definition / resource that I can include in the writeup about this?
The reason this came up was that I was trying to document all the analyses capabilities and so testing the CO2 option
@RDmitchell
And then the user would fill in that value in their imported file, right?
Yes that's right, they can map to the new column
Where do the values for the different regions come from? Do we have a definition / resource that I can include in the writeup about this?
Here's the "official" website, and here's a quick summary of the codes from BEDES.
(edit) Also this might be the most convenient way to look up a code for a particular zip code. There's a spreadsheet somewhere that does the same thing
So in the eGrid Region field users would enter the 4 letter code shown in the BEDES definition?
And then I guess behind the scenes the program figures out what factors should be used based on that region for the calculation?
Yes, it would be great if SEED could automatically determine the egrid region based on zip code if it's available -- maybe that should be a separate issue for a future refinement.
@nllong / @macintoshpie -- maybe SEED figuring out the eGrid region from zip code could be part of the GIS functionality ? In the same way that SEED determines the Lat/Long from address / zip now.
And then I guess behind the scenes the program figures out what factors should be used based on that region for the calculation?
Yes that's how it works
Yes, it would be great if SEED could automatically determine the egrid region based on zip code if it's available -- maybe that should be a separate issue for a future refinement.
I agree, that would be really useful to users, but probably a separate ticket.
I think I'm going to reopen this ticket because SEED needs this column anyways due to decarbonization efforts, we want this in SEED right @nllong ? If not feel free to close
Though this does remind me of the discussion we had for BuildingSync (here) -- some properties might have multiple eGRID Subregion Codes... not sure how we want to handle that, or maybe we don't in SEED (for now...)
We decided to do a single "blessed" eGRID Subregion Code column for now (worry about everything else later)
Instance: dev1 SHA: 9e0821f4d
I added the CAMX (West coast region) eGRID code to the JCC anonymized test dataset, imported the file, and did an Annual Average CO2 analysis. SEED picked up the region code and did the calculations. and there were no error messages
context
SEED created an analysis for calculating co2 emissions which uses egrid subregion. Currently the analysis looks for
egrid_subregion
in extra_data. This isn't easily accessible to users who use the mapping frontend (instead of API)task
Create a new "blessed" PropertyState column,
eGRID Subregion Code
. Use this column in the co2 analysis