diff --git a/.gitignore b/.gitignore index 2b26358..4b07b16 100644 --- a/.gitignore +++ b/.gitignore @@ -6,3 +6,4 @@ __pycache__/ *.pyc *.pyo *.pyd +solar_database/__pycache__/settings.cpython-312.pyc diff --git a/database/plotly_dash.py b/database/plotly_dash.py index 07be0fd..648a9ff 100644 --- a/database/plotly_dash.py +++ b/database/plotly_dash.py @@ -81,7 +81,7 @@ #set up the data for the permit status map with the time slider mapDataClean = mapData[(mapData.local_permit_status != 'NA') & (mapData.final_action_year.isna()==False)] mapDataClean['final_action_year']=mapDataClean.final_action_year.replace('PENDING',2026) -mapDataClean['final_action_year']=mapDataClean.final_action_year.replace('PENDING ',2026).astype("int") +mapDataClean['final_action_year']=mapDataClean.final_action_year.replace('PENDING ',2026).astype("int64") years = mapDataClean['final_action_year'].unique() years.sort() @@ -293,7 +293,7 @@ yaxis=dict(title="Percent of Projects",tickformat='.0%'), xaxis=dict(type='category', tickmode='array', - tickvals=[2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024,2025], + tickvals=[2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024,2025, 2026], categoryorder='category ascending', title='')) @@ -346,7 +346,7 @@ yaxis=dict(title="Percent of Projects",tickformat='.0%'), xaxis=dict(type='category', tickmode='array', - tickvals=[2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024,2025], + tickvals=[2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024,2025, 2026], categoryorder='category ascending', title='')) @@ -398,7 +398,7 @@ type='category', categoryorder='category ascending', tickmode='array', - tickvals=[2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024, 2025]), + tickvals=[2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024, 2025, 2026]), yaxis=dict(tickformat=",.0f", title="Megawatts")) @@ -447,7 +447,7 @@ title=''), xaxis=dict(title='', tickmode='array', - tickvals=[2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024, 2025], + tickvals=[2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024, 2025, 2026], type='category', categoryorder='category ascending'), yaxis=dict(tickformat=",.0f", @@ -643,7 +643,7 @@ html.Br(), html.Br(), html.H1("Virginia Solar Dashboard"), - html.P("Visualizations reflect all projects in the database as of December 31, 2025. Explore different data highlights with the buttons, and download a graph with the camera icon in the upper right corner of each graph. Project Size map includes all projects regardless of local permit status. Hovertext labels on all maps and graphs provide supplemental information."), + html.P("Visualizations reflect all projects in the database as of March 31, 2026. Explore different data highlights with the buttons, and download a graph with the camera icon in the upper right corner of each graph. Project Size map includes all projects regardless of local permit status. Hovertext labels on all maps and graphs provide supplemental information."), html.Div( #dashboard [ diff --git a/database/plotly_dash_bat.py b/database/plotly_dash_bat.py index 6409d33..720e3bf 100644 --- a/database/plotly_dash_bat.py +++ b/database/plotly_dash_bat.py @@ -289,7 +289,7 @@ yaxis=dict(title="Percent of Projects",tickformat='.0%'), xaxis=dict(type='category', tickmode='array', - tickvals=[2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024,2025], + tickvals=[2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024,2025,2026], categoryorder='category ascending', title='')) @@ -342,7 +342,7 @@ yaxis=dict(title="Percent of Projects",tickformat='.0%'), xaxis=dict(type='category', tickmode='array', - tickvals=[2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024,2025], + tickvals=[2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024,2025,2026], categoryorder='category ascending', title='')) @@ -395,7 +395,7 @@ type='category', categoryorder='category ascending', tickmode='array', - tickvals=[2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024, 2025]), + tickvals=[2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024, 2025, 2026]), yaxis=dict(tickformat=",.0f", title="Megawatts")) mwhAnnualLine = px.line(annualData, @@ -446,7 +446,7 @@ type='category', categoryorder='category ascending', tickmode='array', - tickvals=[2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024, 2025]), + tickvals=[2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024, 2025, 2026]), yaxis=dict(tickformat=",.0f", title="Megawatts")) @@ -495,7 +495,7 @@ title=''), xaxis=dict(title='', tickmode='array', - tickvals=[2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024, 2025], + tickvals=[2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024, 2025,2026], type='category', categoryorder='category ascending'), yaxis=dict(tickformat=",.0f", @@ -646,7 +646,7 @@ html.Br(), html.Br(), html.H1("Virginia BESS Dashboard"), - html.P("Visualizations reflect all projects in the database as of December 31, 2025. Explore different data highlights with the buttons, and download a graph with the camera icon in the upper right corner of each graph. Hovertext labels on all maps and graphs provide supplemental information."), + html.P("Visualizations reflect all projects in the database as of March 31, 2026. Explore different data highlights with the buttons, and download a graph with the camera icon in the upper right corner of each graph. Hovertext labels on all maps and graphs provide supplemental information."), html.Br(), html.P("For the purposes of this dashboard, Known Megawatt Hours (MWh) is limited to the projects where the megawatt hour value can be confirmed. The number of projects that apply to this measure of MWh has been specified in the graph titles. This number will be updated as new projects are added and missing MWh values are able to be confirmed. Megawatt values are available for all projects."), html.Div( diff --git a/database/static/About_DB_Jan_2026.pdf b/database/static/About_DB_April 2026.pdf similarity index 67% rename from database/static/About_DB_Jan_2026.pdf rename to database/static/About_DB_April 2026.pdf index 7d72a58..4e41b4a 100644 Binary files a/database/static/About_DB_Jan_2026.pdf and b/database/static/About_DB_April 2026.pdf differ diff --git a/database/static/Data_Dictionary_Definitions.csv b/database/static/Data_Dictionary_Definitions.csv index 496d5f4..ce1b590 100644 --- a/database/static/Data_Dictionary_Definitions.csv +++ b/database/static/Data_Dictionary_Definitions.csv @@ -1,41 +1,42 @@ Datapoint Term,CSV Term,Working Definition,Source(s) Of Data -Data ID,data_id,Unique alphanumeric identifier assigned to each project by UVA. Projects that span multiple localities will be assigned a unique Data ID for each locality that reviewed the project. Solar + storage projects will appear in both databases and will share a Data ID. ,Weldon Cooper Center at UVA -Locality,locality,"Jurisdiction having authority (AHJ) over local land use permitting; in other words, the name of the town, city, county where the project is proposed. Only one locality per project record; if more than one locality is permitting a project, the additional localities will each be given a project record and a unique Data ID. The additional localities will be listed under ""Additional Localities"". If the AHJ is a town, the county the town is located within will be listed as Additional Locality, but a separate Data ID will only be given if that County took action on the project. ","Local permit documents, DEQ, SCC" -Virginia Region,region,"Regions are defined using the Weldon Cooper Center Demographics Research Group’s eight regions for the Commonwealth of Virginia (linked in Sources). These regions have been developed based on communities’ shared demographic, social, economic and geographic characteristics. These were the defined regions used to evaluate results of the Virginia Solar Survey.",Weldon Cooper Center at UVA: https://www.coopercenter.org/virginias-demographic-regions -Additional Localities,additional_localities,"Name of additional localities if project required land use permitting from multiple localities. If the authority having jurisdiction (AHJ) is a town, the county the town is located within will be listed as Additional Locality, but a separate Data ID will only be given if that County took action on the project. ","Local permit documents, media, other reliable sources" -Project Name,project_name,"Project name at the time of local permitting, as it appears in local records. If the project was by-right, the name is as it appears in state permitting records.","Local permit documents, EIA, DEQ, SCC" -Alternative Project Names ,alt_names,Other names the project has been/is known by. Associated storage project will be listed here if it has a different name.,"Local permit documents, EIA, SCC, DEQ, PJM, media, other reliable sources" -Project Phases,project_phase,For solar only: Project name of phase(s) associated with the parent project.,"Local permit documents, DEQ" -Data ID for Parent/Child Project,parent_or_child_project_id,"For solar only: Data ID of projects affiliated with the project. A parent project is a large project that encompasses smaller, independently recorded or permitted projects (child project), such as when a project has several phases. ","Local permit documents, DEQ, SCC, EIA, UVA" +Data ID,data_id,Unique alphanumeric identifier assigned to each project by UVA. Projects that span multiple localities will be assigned a unique Data ID for each locality that reviewed the project. Solar + storage projects will appear in both databases and will share a Data ID.,Weldon Cooper Center at UVA +Locality,locality,"Jurisdiction having authority (AHJ) over local land use permitting; in other words, the name of the town, city, county where the project is proposed. Only one locality per project record; if more than one locality is permitting a project, the additional localities will each be given a project record and a unique Data ID. The additional localities will be listed under ""Additional Localities"". If the AHJ is a town, the county the town is located within will be listed as Additional Locality, but a separate Data ID will only be given if that County took action on the project.","Local permit documents, DEQ, SCC" +Virginia Region,region,"Regions are defined using the Weldon Cooper Center Demographics Research Group§s eight regions for the Commonwealth of Virginia (linked in Sources). These regions have been developed based on communities§ shared demographic, social, economic and geographic characteristics. These were the defined regions used to evaluate results of the Virginia Solar Survey.",Weldon Cooper Center at UVA: https://www.coopercenter.org/virginias-demographic-regions +Additional Localities,additional_localities,"Name of additional localities if project required land use permitting from multiple localities. If the authority having jurisdiction (AHJ) is a town, the county the town is located within will be listed as Additional Locality, but a separate Data ID will only be given if that County took action on the project.","Local permit documents, media, other reliable sources" +Project Name,project_name,"Project name at the time of local permitting, as it appears in local records. If the project was by-right, the name is as it appears in state permitting records. Sometimes a locality will refer to a project by multiple names; when this happens the most common name, or name the owner/developer uses today, will be chosen as Project Name.","Local permit documents, EIA, DEQ, SCC, project website" +Alternative Project Names,alt_names,Other names the project has been/is known by. Associated battery energy storage project will be listed here if it has a different name.,"Local permit documents, EIA, SCC, DEQ, PJM, project website, media, other reliable sources" +Project Phases,project_phase,For solar only: Project name of phase(s) associated with the parent project.,"Local permit documents, DEQ, EIA" +Data ID for Parent/Child Project,parent_or_child_project_id,"For solar only: Data ID of projects affiliated with the project. A parent project is a large project that encompasses smaller, independently recorded or permitted projects (child project), such as when a project has several phases.","Local permit documents, DEQ, SCC, EIA, UVA" Data ID for Previous Project,prev_project_id,"For solar only: Data ID that links a project to a previous iteration of the same project. Projects generally share location, relative size and attributes, but may not share the same project name or developer. Previous projects were typically denied or withdrawn; otherwise it may be considered an amendment to a previously approved project.",Weldon Cooper Center at UVA -Owner/Developer at Local Action,local_action_project_owner,"Name of the project developer/owner at the time of local action. This is not the property owner unless the developer, applicant, and property owner are the same entity. If the project was by-right, this is the developer at the time the project appears in offical records. ","Local permit documents, media " -Latest Nameplate Capacity per Local Action (MWac),project_mw,"For solar projects, latest permitted maximum nameplate electrical generation by megawatts (MW) in AC, per local application and/or permit amendment.","Local permit documents, media, other reliable sources" -BESS project MW ,project_bess_mw,"For BESS projects, latest permitted maximum power capacity in megawatts (MW) as reported in locality records or other verified source.","Local permit documents, media, other reliable sources" -BESS Project Energy Capacity (MWh),project_bess_capacity,"For BESS projects, latest permitted maximum energy capacity in megawatt hours (MWh), as reported in locality records or other verified source.", -BESS Project Duration- Short or Long,bess_duration_short_long,"For BESS projects, short duration is defined as delivering less than 10 hours of generation and long duration is defined as 10 or more hours. ", -Phase Capacity (MWac),phase_mw,"For solar only: Megawatts (MW) associated with that particular phase of a project, reported in AC. At this time, this datapoint is for solar only.","Local permit documents, DEQ, SCC, EIA " -Local Permit Status,local_permit_status,"Description of the status of the local zoning permit or land use application that would enable the project (e.g., Rezoning, 15.2-2232 review, Siting Agreement, Conditional or Special Use Permit, or Special Exception). ""By-right"" is applied when the project didn't require local zoning action; however, the project may still have a siting agreement with local approval. ""Pending"" is applied when there is a valid zoning or enabling application on file; a public hearing may have been scheduled, but the AHJ has not completed action on it. ""Withdrawn"" is when the applicant withdrew their application prior to final local action. For solar projects, ""Approved/Amended"" is applied when a project was approved, but was supplanted by a new project application (as opposed to an amendment of the existing permit). For solar projects, ""NA"" is applied when the project is a child/phase of a parent project and permitting history is applied to the parent project. For solar projects, ""NA"" could also be applied to a parent project if the child/phases applied individually for local permitting.","Local permit documents, DEQ, media, other reliable sources" -Best Available Project Acreage,public_project_acres,"Acreage assigned by UVA based on best available information provided in local permit documents, or other verified sources. Preference is to record ""project acreage"" as reported by locality. There is no single or universal definiton of ""project acreage."" For solar projects, if ""project acreage"" is not reported, ""best available acreage"" will be determined based on a triage of the following: ""in-fence"", then ""lease"", then ""under panel"", then ""parcel"" acreages. For BESS, ""project acreage"" will be reported if the acreage is verifiable by the locality records, DEQ, SCC, or other reliable source. Because BESS project footprint and acreage can vary so much based on technology and duration, best available acreage will not be estimated if it is not provided in permitting records.","Weldon Cooper Center at UVA; local permit documents, DEQ, SCC, other reliable source (project developer, utility)." -Location Description,location_description,"Exact address if available, and/or description of the location with respect to towns, roads, and other features. ","Local application documents (public hearing notice), media" -Date- Final Action,final_action_date,"This is the date the locality took final action on a project application. It may be the date of planning commission action only (ex: in the event 15.2-2232 is the only required approval), Board/Council action (SUP, CUP, special exception, siting agreement, appeal, public property lease agreement), or applicant action (withdrawn). This date does not reflect any subsequent amendments to the primary application. For projects approved as solar+storage, permitting data (including date of final action) reside in the solar database.",Local application documents (meeting minutes) -Date(s)- Local Permit Amendment,local_permit_amend_date,"For solar projects: Date(s) of amendment(s) to an approved local permit. If an amendment requires an entire new SUP application, for example, or the project changed substantially, it would be recorded in this database as a subsequent project to a previous project. ",Local application documents -Local Permit Amendment Description,local_permit_amend_desc,For solar projects: A brief description of the nature of the amendment.,Local application documents -Siting Agreement Executed?,siting_agreement_exists,"""Yes"" indicates an executed siting agreement (per state code 15.2-2316.7) has been verified. This does NOT include or reflect any executed proffer agreements, conditions, or community benefit agreements (CBAs). For siting agreements that were presented but denied or not approved, the response is ""No"". Projects that were enabled before siting agreement legislation effective date of 2020 were not required to have a siting agreement NOI or negotiations. ","Local application documents, Virginia Energy" +Owner/Developer at Local Action,local_action_project_owner,"Name of the project developer/owner at the time of local action. This is not the property owner unless the developer, applicant, and property owner are the same entity. If the project was by-right, this is the developer at the time the project appears in offical records.","Local permit documents, media" +Latest Nameplate Capacity per Local Action (MWac),project_mw,"For solar projects, latest permitted maximum nameplate electrical generation by megawatts (MW) in AC, per local application and/or permit amendment. If MW is not provided in local permit documents, state and/or interconnection records will be used to verify nameplate capacity.","Local permit documents, media, other reliable sources" +BESS project MW,project_bess_mw,"For BESS projects, latest permitted maximum power capacity in megawatts (MW) as reported in locality records or other verified source.","Local permit documents, media, other reliable sources" +BESS Project Energy Capacity (MWh),project_bess_capacity,"For BESS projects, latest permitted maximum energy capacity in megawatt hours (MWh), as reported in locality records or other verified source.","Local permit documents, DEQ, SCC, media, other reliable sources" +BESS Project Duration- Short or Long,bess_duration_short_long,"For BESS projects, short duration is defined as delivering less than 10 hours of generation and long duration is defined as 10 or more hours. 10 hour threshold was determined based on definitions proposed at the time of this release, HB 895: https://lis.virginia.gov/bill-details/20261/HB895 , and with stakeholder consent.","Local permit documents, media, other reliable sources" +Phase Capacity (MWac),phase_mw,"For solar only: Megawatts (MW) associated with that particular phase of a project, reported in AC. At this time, this datapoint is for solar only.","Local permit documents, DEQ, SCC, EIA" +Local Permit Status,local_permit_status,"Description of the status of the local zoning or land use application that would enable the project (e.g., Rezoning, 15.2-2232 review, Siting Agreement, Conditional or Special Use Permit, or Special Exception). ""By-right"" is applied when the project didn't require local zoning action; however, the project may still have a siting agreement with local approval. ""Pending"" is applied when there is a valid zoning or enabling application on file; a public hearing may have been scheduled, but the AHJ has not completed action on it. ""Withdrawn"" is when the applicant withdrew their application prior to final local action. For solar projects, ""Approved/Amended"" is applied when a project was approved, but was supplanted by a new project application (as opposed to an amendment of the existing permit). For solar projects, ""NA"" is applied when the project is a child/phase of a parent project and permitting history is applied to the parent project. For solar projects, ""NA"" could also be applied to a parent project if the child/phases applied individually for local permitting.","Local permit documents, DEQ, media, other reliable sources" +Best Available Project Acreage,public_project_acres,"Acreage assigned by UVA based on best available information provided in local permit documents or other verified sources. Preference is to record ""project acreage"" as reported by locality. There is no single or universal definiton of ""project acreage."" For solar projects, if ""project acreage"" is not reported, ""best available acreage"" will be determined based on a triage of the following: ""in-fence"", then ""lease"", then ""under panel"", then ""parcel"" acreages. For BESS, ""project acreage"" will be reported if the acreage is verifiable by the locality records, DEQ, SCC, or other reliable source. Because BESS project footprint and acreage can vary so much based on technology and duration, best available acreage will not be estimated if it is not provided in permitting records.","Weldon Cooper Center at UVA; local permit documents, DEQ, SCC, other reliable source (project developer, utility)." +Location Description,location_description,"Exact address if available, and/or description of the location with respect to towns, roads, and other features.","Local application documents (public hearing notice), media" +Date- Final Action,final_action_date,"The date the locality took final action on a project application. It may be the date of planning commission action only (ex: in the event 15.2-2232 is the only required approval), Board/Council action (SUP, CUP, special exception, siting agreement, appeal, public property lease agreement, appeal), or applicant action (withdrawn). This date does not reflect any subsequent amendments to the primary application. For projects approved as solar+storage, permitting data (including date of final action) reside in the solar database.",Local application documents (meeting minutes) +Date(s)- Local Permit Amendment,local_permit_amend_date,"For solar projects: Date(s) of amendment(s) to an approved local permit. If an amendment requires a new SUP application, for example, or the project changed substantially, it would be recorded in this database as a subsequent project to a previous project.",Local application documents +Local Permit Amendment Description,local_permit_amend_desc,For solar projects: A brief description of the nature of the amendment request.,Local application documents +Siting Agreement Executed?,siting_agreement_exists,"""Yes"" indicates an executed siting agreement (per state code 15.2-2316.7) has been verified. This does NOT include or reflect any executed proffer agreements, conditions, or community benefit agreements (CBAs). For siting agreements that were presented but denied or not approved, the response is ""No"". Projects that were enabled before siting agreement legislation effective date of 2020 were not required to have a siting agreement NOI or negotiations.","Local application documents, Virginia Energy" Date- Siting Agreement Action,siting_agreement_date,"Date the siting agreement was authorized to be executed, or executed by the local authority, date it was denied, or date the locality failed to take action at an advertised siting agreement hearing.","Local application documents, Virginia Energy" Siting Agreement Link,siting_agreement_link,"Link to executed version of siting agreement (if not signed, this is the version approved by the local authority in the public hearing.)","Local application documents, Virginia Energy" Shared Solar Program - Enrolled (Dominion or Appalachian Power),shared_solar_enrolled,"For solar only, this datatpoint captures whether the project is officially enrolled in a Dominion or Appalachian Power shared solar program (MW have been allotted to subscriber organization.)",Dominion and Appalachian Power Shared Solar Programs Shared Solar Program - Enrolled Date,shared_solar_enrolled_date,"For solar only, the date project was enrolled in its utility's shared solar program, as reported by the utility.",Dominion and Appalachian Power Shared Solar Programs -Mined Land?,mined_land,"For solar only, this datapoint reports whether the project is located on Abandoned Mined Land (AML) or a released permitted surface mine site. These locations have been identified as AML sites or permitted by the Virginia Dept. of Energy or predecessor agency. ",Virginia Department of Energy (thru 9/30/24) -Pollinator-Smart Certified? ,dcr_pollinator_certified,"For solar projects: A ""yes"" or ""no"" response, based on Va Department of Conservation and Recreation records. ""Yes"" indicates the project has been certified as Pollinator-Smart by the Pollinator Smart Committee at any point during its lifetime. ""No"" indicates the project has not been certified as Pollinator-Smart by the Pollinator Smart Committee; ""no"" does not differentiate between projects that are in review for certification versus projects that are not seeking certification.","DCR records provided to UVA, eff 12/31/25. Additional definitions and program information can be found at: Pollinator-Smart Comprehensive Manual https://www.dcr.virginia.gov/natural-heritage/document/solar-site-comprehensive-manual.pdf. For more information about native vegetation requirements, see the Virginia Localities Solar Ordinances and Native Vegetation report from DCR https://www.dcr.virginia.gov/natural-heritage/document/va-solarordin-natveg.pdf" -Pollinator-Smart Stage of Development,dcr_pollinator_status,"For solar projects: For Pollinator Smart certified projects, ""stage of development"" describes the milestone of development certified, based on program defintions and DCR records. Certification for each milestone is a separate and unique achievement. There are six milestone certifications: ""Design""- the project is either pre-construction or less than 2 years old, the Pollinator-Smart Committee has concurred that the design meets the criteria for Pollinator-Smart. The site plan design including the planting plan (vegetation management plan) meets Pollinator Smart Certification per the proposed or retrofit solar sites scorecard version 2.0a (the blue form). ""Monitoring Year 2, Monitoring Year 4, Monitoring Year 6, or Monitoring Year 8""- The year indicates how many years since vegetation has been established. The project has been monitored and assessed with the Monitoring Scorecard version 2.0b (the green form). The Pollinator-Smart Committee concurs that the vegetation on the ground meets the requirement for Pollinator Smart based on review of the scorecard and Monitoring Report. ""Lifetime""- The site has been certified at all past milestones and has developed a long term mangement plan. The plan, Year 10 monitoring , and scorecard have been reviewed by the Pollinator Smart committee and they concur with the assessment. ",DCR: Pollinator-Smart Comprehensive Manual https://www.dcr.virginia.gov/natural-heritage/document/solar-site-comprehensive-manual.pdf ; Pollinator-Smart Monitoring Plan https://www.dcr.virginia.gov/natural-heritage/document/solar-site-monitoring.pdf ; Proposed or Retrofit Solar Sites Scorecard (blue) https://www.dcr.virginia.gov/natural-heritage/document/solar-site-pollinator-bird-habitat-scorecard-a-new.pdf ; Established Site Scorecard (green) https://www.dcr.virginia.gov/natural-heritage/document/solar-site-pollinator-bird-habitat-scorecard-b-established.pdf. -Pollinator-Smart Scorecard (link),dcr_pollinator_scorecard,"For solar only. This datapoint provides a link to the Pollinator-Smart Scorecard on file with DCR. For projects that achieved some level of Pollinator-Smart certification, the linked scorecard shows what level of certification was achieved. ""Certified"" is a project that has earned 80-99 points based on the Pollinator Smart scorecard self-assessment of the site and was reviewed for concurrance from the Pollinator Smart Committee. ""Gold"" is a project that has earned 100+ points based on the scorecard self-assessment and was reviewed for concurrance from the Pollinator-Smart Committee.",DCR Pollinator Smart Scorecard (linked). Additional definitions and program information can be found at: Pollinator-Smart Comprehensive Manual https://www.dcr.virginia.gov/natural-heritage/document/solar-site-comprehensive-manual.pdf. -Pollinator-Smart Scorecard Name,dcr_pollinator_scorecard_name,"For solar projects: This datapoint indicates for projects that achieved some level of Pollinator-Smart certification, what the level of certification is. ""Certified"" is a project that has earned 80-99 points based on the Pollinator Smart scorecard self-assessment of the site and was reviewed for concurrance from the Pollinator Smart Committee. ""Gold"" is a project that has earned 100+ points based on the scorecard self-assessment and was reviewed for concurrance from the Pollinator-Smart Committee.",DCR records provided to UVA eff 12/31/25. Additional definitions and program information can be found at: Pollinator-Smart Comprehensive Manual https://www.dcr.virginia.gov/natural-heritage/document/solar-site-comprehensive-manual.pdf. +Mined Land?,mined_land,"For solar only, this datapoint reports whether the project is located on Abandoned Mined Land (AML) or a released permitted surface mine site. These locations have been identified as AML sites or permitted by the Virginia Dept. of Energy or predecessor agency.",Virginia Department of Energy (thru 3/31/26) +Brownfield?,,"For solar only, this datapoint report whether the project site is identified as a brownfield or previously distrubed or repurposed area by Virginia Department of Environmental Quality. Per 9VAC15-60-10: ""Brownfield"" means real property , the expansion, redevelopment, or reuse of which may be complicated by the presence or potential presence of a hazardous substance, pollutant, or contaminant as defined in § 10.1-1230 of the Code of Virginia. ""Previously disturbed or repurposed areas"" means the land area within the property boundary of industrial or commercial properties, including brownfields or previously mined areas. It does not include active or fallow agricultural land or silvicultural land use.","Virginia Department of Environmental Quality, Small Renewable Energy PBR Status Report" +Pollinator-Smart Certified?,dcr_pollinator_certified,"For solar projects: A ""yes"" or ""no"" response, based on Va Department of Conservation and Recreation records. ""Yes"" indicates the project has been certified as Pollinator-Smart by the Pollinator Smart Committee at any point during its lifetime. ""No"" indicates the project has not been certified as Pollinator-Smart by the Pollinator Smart Committee; ""no"" does not differentiate between projects that are in review for certification versus projects that are not seeking certification.","DCR records provided to UVA, eff 3/31/26. Additional definitions and program information can be found at: Pollinator-Smart Comprehensive Manual https://www.dcr.virginia.gov/natural-heritage/document/solar-site-comprehensive-manual.pdf. For more information about native vegetation requirements, see the Virginia Localities Solar Ordinances and Native Vegetation report from DCR https://www.dcr.virginia.gov/natural-heritage/document/va-solarordin-natveg.pdf. For county by county defintions, guidance, and requirements, see DCR's 2025 Virginia Localities' Solar Guidance and Associated Vegetation Requirements Report: https://www.dcr.virginia.gov/natural-heritage/document/va-solarordin-natveg.pdf" +Pollinator-Smart Stage of Development,dcr_pollinator_status,"For solar projects: For Pollinator Smart certified projects, ""stage of development"" describes the milestone of development certified, based on program defintions and DCR records. Certification for each milestone is a separate and unique achievement. There are six milestone certifications: ""Design""- the project is either pre-construction or less than 2 years old, the Pollinator-Smart Committee has concurred that the design meets the criteria for Pollinator-Smart. The site plan design including the planting plan (vegetation management plan) meets Pollinator Smart Certification per the proposed or retrofit solar sites scorecard version 2.0a (the blue form). ""Monitoring Year 2, Monitoring Year 4, Monitoring Year 6, or Monitoring Year 8""- The year indicates how many years since vegetation has been established. The project has been monitored and assessed with the Monitoring Scorecard version 2.0b (the green form). The Pollinator-Smart Committee concurs that the vegetation on the ground meets the requirement for Pollinator Smart based on review of the scorecard and Monitoring Report. ""Lifetime""- The site has been certified at all past milestones and has developed a long term mangement plan. The plan, Year 10 monitoring , and scorecard have been reviewed by the Pollinator Smart committee and they concur with the assessment.",DCR: Pollinator-Smart Comprehensive Manual https://www.dcr.virginia.gov/natural-heritage/document/solar-site-comprehensive-manual.pdf ; Pollinator-Smart Monitoring Plan https://www.dcr.virginia.gov/natural-heritage/document/solar-site-monitoring.pdf ; Proposed or Retrofit Solar Sites Scorecard (blue) https://www.dcr.virginia.gov/natural-heritage/document/solar-site-pollinator-bird-habitat-scorecard-a-new.pdf ; Established Site Scorecard (green) https://www.dcr.virginia.gov/natural-heritage/document/solar-site-pollinator-bird-habitat-scorecard-b-established.pdf. +Pollinator-Smart Scorecard (link),dcr_pollinator_scorecard,"For solar only. This datapoint provides a link to the Pollinator-Smart Scorecard on file with DCR. For projects that achieved some level of Pollinator-Smart certification, the linked scorecard shows what level of certification was achieved. ""Certified"" is a project that has earned 80-99 points based on the Pollinator Smart scorecard self-assessment of the site and was reviewed for concurrance from the Pollinator Smart Committee. ""Gold"" is a project that has earned 100+ points based on the scorecard self-assessment and was reviewed for concurrance from the Pollinator-Smart Committee.",DCR Pollinator Smart Scorecard (linked). Additional definitions and program information can be found at: Pollinator-Smart Comprehensive Manual https://www.dcr.virginia.gov/natural-heritage/document/solar-site-comprehensive-manual.pdf. +Pollinator-Smart Scorecard Name,dcr_pollinator_scorecard_name,"For solar projects: This datapoint indicates for projects that achieved some level of Pollinator-Smart certification, what the level of certification is. ""Certified"" is a project that has earned 80-99 points based on the Pollinator Smart scorecard self-assessment of the site and was reviewed for concurrance from the Pollinator Smart Committee. ""Gold"" is a project that has earned 100+ points based on the scorecard self-assessment and was reviewed for concurrance from the Pollinator-Smart Committee.",DCR records provided to UVA eff 3/31/26. Additional definitions and program information can be found at: Pollinator-Smart Comprehensive Manual https://www.dcr.virginia.gov/natural-heritage/document/solar-site-comprehensive-manual.pdf. Energy Storage Onsite?,energy_storage_onsite,For solar projects: Answers whether the solar facility is proposed to be colocated with an on-site battery energy storage facility.,"PJM, DEQ, local permit application" -Energy Storage Capacity (MW),energy_storage_mw,"For solar projects: If battery energy storage is proposed onsite, the total capacity in MW of the BESS.","Local permit application, PJM, DEQ, media and other reliable sources" -Current Virginia Senate District,va_state_senate_district,"As defined by the applicable Virginia Supreme Court map (linked in Sources), this datapoint provides the current Virginia Senate district in which the project lies. Note: Project location was defined using latitude and longitude coordinates. Preference was to obtain lat/long coordinates from local permitting records or EIA; if lat/longs were not provided by a reliable source, UVA assigned a lat/long based on project address or best available location information. For this reason, the congressional/sentate/house district assigned is that which applies to the lat/long and it is possible additional districts may apply to other areas of the project.",Virginia Supreme Court -Current Virginia House of Delegates District,va_house_of_delegates,"As defined by the applicable Virginia Supreme Court map (linked in Sources), this datapoint provides the current Virginia House of Delegates district in which the project lies. Note: Project location was defined using latitude and longitude coordinates. Preference was to obtain lat/long coordinates from local permitting records or EIA; if lat/longs were not provided by a reliable source, UVA assigned a lat/long based on project address or best available location information. For this reason, the congressional/sentate/house district assigned is that which applies to the lat/long and it is possible additional districts may apply to other areas of the project.",Virginia Supreme Court -Current Federal Congressional District,va_federal_congressional_district,"As reported by the applicable Virginia Supreme Court map (linked in Sources), this datapoint provides the current US Congressional district in which the project lies. Note: Project location was defined using latitude and longitude coordinates. Preference was to obtain lat/long coordinates from local permitting records or EIA; if lat/longs were not provided by a reliable source, UVA assigned a lat/long based on project address or best available location information. For this reason, the congressional/sentate/house district assigned is that which applies to the lat/long and it is possible additional districts may apply to other areas of the project.",Virginia Supreme Court +Energy Storage Capacity (MW),energy_storage_mw,"For solar projects: If battery energy storage is proposed onsite, the total capacity in MW of the BESS, if known.","Local permit application, PJM, DEQ, media and other reliable sources" +Current Virginia Senate District,va_state_senate_district,"As defined by the applicable Virginia Supreme Court map (linked in Sources), this datapoint provides the current Virginia Senate district in which the project lies. Note: Project location was defined using latitude and longitude coordinates. Preference was to obtain lat/long coordinates from local permitting records or EIA; if lat/longs were not provided by a reliable source, UVA estimated a lat/long based on project address or best available location information. For this reason, the congressional/sentate/house district assigned is that which applies to the lat/long and it is possible additional districts may apply to other areas of the project.",Virginia Supreme Court +Current Virginia House of Delegates District,va_house_of_delegates,"As defined by the applicable Virginia Supreme Court map (linked in Sources), this datapoint provides the current Virginia House of Delegates district in which the project lies. Note: Project location was defined using latitude and longitude coordinates. Preference was to obtain lat/long coordinates from local permitting records or EIA; if lat/longs were not provided by a reliable source, UVA estimated a lat/long based on project address or best available location information. For this reason, the congressional/sentate/house district assigned is that which applies to the lat/long and it is possible additional districts may apply to other areas of the project.",Virginia Supreme Court +Current Federal Congressional District,va_federal_congressional_district,"As reported by the applicable Virginia Supreme Court map (linked in Sources), this datapoint provides the current US Congressional district in which the project lies. Note: Project location was defined using latitude and longitude coordinates. Preference was to obtain lat/long coordinates from local permitting records or EIA; if lat/longs were not provided by a reliable source, UVA estimated a lat/long based on project address or best available location information. For this reason, the congressional/sentate/house district assigned is that which applies to the lat/long and it is possible additional districts may apply to other areas of the project.",Virginia Supreme Court Solar+ Storage or Co-located with Solar?,solar_storage,"This datapoint reports projects that were initially permitted as a solar + storage project (=Yes) and projects where BESS was added to an existing solar project later (= Co-located). If the project was originally permitted as solar + storage, permitting data will be found in the solar database, with storage-specific datapoints in the BESS database. Projects can be matched between the solar and storage databases using their shared Data ID. For solar projects that had BESS permitted and added later, the storage and solar projects will have unique Data IDs, storage permitting data will reside in the storage database, and the related solar/storage project will be referenced under ""Alternative Project Names"". Note- When solar and storage-specific acreages are not provided in local records, total project acreages will remain in the solar database and no acreages will be parsed out for storage in the storage database.","Local permit documents, DEQ, SCC, media, other reliable sources" BESS Technology Type,storage_tech,"The general battery technology being proposed for a BESS. Examples include: Lithium-Ion, Non Lithium-Ion. This data is not always available.","Local permit documents, DEQ, SCC, EIA, media, other reliable sources" BESS Technology Chemistry,storage_chemistry,"The specific battery technology or chemistry being proposed for a BESS. Examples include: Lithium Nickel Manganese Cobalt, Lithium Iron Phosphate, Iron Air, Zinc Hyrbid. This data is not always available.","Local permit documents, DEQ, SCC, EIA, media, other reliable sources" -Notes on Co-location/ Use ,colocation_info,"BESS are often co-located with, or located adjacent to a primary use such as an electric generation facility or substation. This datapoint documents co-location information as it was reported in local permitting documents or other reliable sources. ","Local permit documents, media, SCC, other reliable sources" \ No newline at end of file +Notes on Co-location/ Use,colocation_info,"BESS are often co-located with, or located adjacent to a primary use such as an electric generation facility or substation. This datapoint documents co-location information as it was reported in local permitting documents or other reliable sources.","Local permit documents, media, SCC, other reliable sources" \ No newline at end of file diff --git a/database/templates/database/about.html b/database/templates/database/about.html index 89125e4..facf3aa 100644 --- a/database/templates/database/about.html +++ b/database/templates/database/about.html @@ -10,7 +10,7 @@

About the Virginia Solar and Storage Database


- More About VSSD + More About VSSD

@@ -40,7 +40,7 @@

Data

Data is sourced from primary sources such as local government archives (meeting minutes, agendas, video recordings, resolutions, land use applications, staff reports, conditions, etc.), Virginia Department of Environmental Quality (DEQ) permit records, Virginia Department of Conservation and Recreation (DCR) Pollinator Smart Certification records, Virginia Department of Energy records, Virginia State Corporation Commission (SCC) dockets and final orders, Energy Information Administration (EIA) data, PJM Interconnection Request data, and various press, utility, industry/developer, and stakeholder media.

-

NOTE: Solar and BESS data can be dowloaded together in a tabbed Excel file from either the Solar or the BESS data pages. When projects were permitted as solar+storage projects, the project’s main permitting data lives in the solar database while storage-specific datapoints such as MWh and battery technology details are provided in the storage database. The project’s Data ID can be used to link the projects.

+

NOTE: When projects were permitted as solar+storage projects, the project’s main permitting data lives in the solar database while storage-specific datapoints such as MWh and battery technology details are provided in the storage database. The project’s Data ID can be used to link the projects.

See the Data Dictionary for a complete list of datapoints, their associated definitions, and sources for the data.

Acknowledgements

@@ -56,6 +56,7 @@

Acknowledgements

New +

Current as of March 31, 2025 (Updated Quarterly)

January 14, 2026
Added BESS Data and updated usability across site

November 5, 2025 diff --git a/database/templates/database/battery_storage.html b/database/templates/database/battery_storage.html index 8057562..b2eeccf 100644 --- a/database/templates/database/battery_storage.html +++ b/database/templates/database/battery_storage.html @@ -25,7 +25,7 @@

BESS Data

Browse and Download Battery Energy Storage Data

-

Current as of December 31, 2025 (Will be updated quarterly)

+

Current as of March 31, 2026 (Will be updated quarterly)


Export All to Excel @@ -193,7 +193,8 @@

Explore Battery Storage Projects

in Virginia var mapBase = L.tileLayer('https://tile.openstreetmap.org/{z}/{x}/{y}.png', { maxZoom: 20, - attribution: '© OpenStreetMap' + attribution: '© OpenStreetMap', + referrerPolicy: 'strict-origin-when-cross-origin' }) var projectMarkers = L.layerGroup(); diff --git a/database/templates/database/dictionary.html b/database/templates/database/dictionary.html index 2839e5d..bd8e815 100644 --- a/database/templates/database/dictionary.html +++ b/database/templates/database/dictionary.html @@ -15,7 +15,7 @@

Dictionary

Browse and Download the Solar and Storage Dictionary

-

Current as of December 31, 2025

+

Current as of March 31, 2026


Export Dictionary to CSV diff --git a/database/templates/database/home.html b/database/templates/database/home.html index d4e9f7a..c3d2548 100644 --- a/database/templates/database/home.html +++ b/database/templates/database/home.html @@ -26,12 +26,12 @@

Virginia Solar and Storage Database

- Data is current through December 31, 2025 + Data is current through March 31, 2026

To cite our data: - Weldon Cooper Center for Public Service at the University of Virginia. December 31, 2025. + Weldon Cooper Center for Public Service at the University of Virginia. March 31, 2026. “Virginia Solar Database.” https://solardatabase.coopercenter.org/.

diff --git a/database/templates/database/solar.html b/database/templates/database/solar.html index 1e59845..54b6260 100644 --- a/database/templates/database/solar.html +++ b/database/templates/database/solar.html @@ -25,7 +25,7 @@

Solar Data

Browse and Download Solar Data

-

Current as of December 31, 2025 (Will be updated quarterly)

+

Current as of March 31, 2026 (Data updated quarterly)


Export All to Excel @@ -241,7 +241,8 @@

Explore Solar Projects

in Virginia var mapBase = L.tileLayer('https://tile.openstreetmap.org/{z}/{x}/{y}.png', { maxZoom: 20, - attribution: '© OpenStreetMap' + attribution: '© OpenStreetMap', + referrerPolicy: 'strict-origin-when-cross-origin' }) var projectMarkers = L.layerGroup(); diff --git a/solar_database/__pycache__/settings.cpython-310.pyc b/solar_database/__pycache__/settings.cpython-310.pyc index 4a5c9f5..10e8fd4 100644 Binary files a/solar_database/__pycache__/settings.cpython-310.pyc and b/solar_database/__pycache__/settings.cpython-310.pyc differ diff --git a/solar_database/__pycache__/settings.cpython-312.pyc b/solar_database/__pycache__/settings.cpython-312.pyc index a223c5d..746aade 100644 Binary files a/solar_database/__pycache__/settings.cpython-312.pyc and b/solar_database/__pycache__/settings.cpython-312.pyc differ diff --git a/solar_database/settings.py b/solar_database/settings.py index 04a66f1..40aeb03 100644 --- a/solar_database/settings.py +++ b/solar_database/settings.py @@ -27,10 +27,11 @@ if os.path.exists('hidden'): DEBUG = True + # ALLOWED_HOSTS = ['127.0.0.1'] else: DEBUG = True -ALLOWED_HOSTS = ['va-solar-db.azurewebsites.net','va-solar-db-dev.azurewebsites.net', '127.0.0.1', 'solardatabase.coopercenter.org'] +ALLOWED_HOSTS = ['va-solar-db.azureawebsites.net','va-solar-db-dev.azurewebsites.net', '127.0.0.1', 'solardatabase.coopercenter.org'] # Application definition @@ -74,7 +75,7 @@ CHANNEL_LAYERS = { 'default': { 'BACKEND': 'channels_redis.core.RedisChannelLayer', 'CONFIG': { - 'hosts': [('va-solar-db.azurewebsites.net','va-solar-db-dev.azurewebsites.net','127.0.0.1', 6379, 'solardatabase.coopercenter.org'),], + 'hosts': [('127.0.0.1', 6379)] } } }