尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Parse Energy Performance Certificates and Display Energy Certificates for the UK
翻譯準備中
取自儲存庫 README
正在載入完整 README。 以下為已儲存的摘錄。
Parse Energy Performance Certificates and Display Energy Certificates for the UK
In the UK, domestic and non-domestic buildings are required to have an Energy Performance Certificate (EPC) when they are sold or rented. Certificates are valid for 10 years, and they are the only dataset in the UK where somebody has visited the building and taken measurements and observations.
Publicly accessible buildings are required to have an annual Display Energy Certificate (DEC).檢視完整 README ↗In the UK, domestic and non-domestic buildings are required to have an Energy Performance Certificate (EPC) when they are sold or rented. Certificates are valid for 10 years, and they are the only dataset in the UK where somebody has visited the building and taken measurements and observations.
Publicly accessible buildings are required to have an annual Display Energy Certificate (DEC).
While there has been a lot of criticism in the UK of EPCs, in particular, they are not very good at predicting actual energy use. They are an invaluable source of data about much of the building stock.
Data for England and Wales is published as Open Data at https://epc.opendatacommunities.org/
Data for Scotland is published at https://www.scottishepcregister.org.uk/
This repo provides much of the pre-processing of the EPC data that is available on the www.carbon.place website. Specifically, it has 3 functions.
The scripts in R/ are run in this order:
import_epc.R, import_nondom_epc.R, import_dec.R (England & Wales) and
import_epc_scotland.R, import_nondom_epc_scotland.R (Scotland).../inputdata/epc/:
clean_epc.R, clean_nondom_epc.R, clean_decs.R,
clean_epc_scot.R, clean_nondom_epc_scot.R.merge_epcs.R combines the cleaned England & Wales and
Scotland data into single Great Britain datasets
(GB_domestic_epc.Rds, GB_nondomestic_epc.Rds).Two further analysis scripts use the raw/cleaned data:
uprn_classifications.R classifies UPRNs by building type and tenure using
the most recent certificate of any kind lodged against each UPRN.epc_over_time.R produces plots and maps of EPC ratings over time by area
classification.Most of the free-text cleaning is done in clean_epc.R and
clean_epc_scot.R, based on functions defined in functions.R and
translate_welsh.R.
Important cleaning functions include:
fix_wm2k, which converts the many versions of watts per square metre kelvin (a unit of heat loss) into a standard format.standardclean, which removes common errors or inconsistencies (e.g. & vs and)yn2logical, which converts yes/no text variables to logical TRUE/FALSEsplitwelsh; in some EPCs, the text is provided in both English and Welsh, separated by |; this function splits and removes the Welsh version.translatewelsh is used when only the Welsh text is available and translates common Welsh phrases to their English equivalents. E.g. "briciau solet" to "solid brick". I used Google Translate for these, and feedback from Welsh speakers is welcome. Oddly, EPCs in Welsh don't only occur in Wales.validate, which checks that a cleaned column only contains values from a
controlled vocabulary (defined in the clean scripts) and converts it to a
factor, stopping with a report of any unexpected values.While the cleaning is not perfect, it does significantly reduce variation between EPCs, which is useful for analysis. For example, instead of thousands of different Main Fuel Types in the raw data, there are about 40 distinct types in the cleaned data.
merge_epcs.R resolves differences between the Scotland and England/Wales datasets. Specifically, the different age bands used by Scotland are mapped to the English/Welsh version. This can result in minor errors, e.g. "1992-1998" becomes "1991-1995"
Note that these scripts read the whole EPC dataset into memory and so require a PC with a large amount of RAM (e.g. 256 GB).
This repo also works on the assumption that the build and inputdata repos are available on the same drive to provide inputs (the downloaded zip files and UPRN locations) and as a place for exports.
See the website for public downloads.