Energy Pack for Developers
Siting constraints, conflict density, and renewable-zone classification in one call.
Energy developers and siting analysts piece together solar zones, sage-grouse PHMA, and existing well density from three different downloads and a manually-joined GIS layer. The Energy Pack returns siting constraints, conflict density, and renewable-zone classification from a single PLSS section or TXSS abstract.
How the workflow changes.
- Download BLM Western Solar Plan zones, project into local CRS
- Pull sage-grouse PHMA tiers from a separate state-FWS dataset
- Cross-reference existing well density from a state regulator export
- Manually join three layers in QGIS for every candidate site
- /api/energy/renewable-siting returns Western Solar Plan zone + USGS wind turbine proximity
- /api/energy/sage-grouse returns BLM HMA tier intersection
- /api/energy/wells returns operational well counts within a buffer
- /api/energy/orphaned-wells flags legacy liability for site selection
Recommended layers
- Renewable siting
- Sage-Grouse habitat
- O&G wells
- Orphaned-well liability
Recommended endpoints
/api/energy/renewable-siting/api/energy/sage-grouse/api/energy/wells/api/energy/orphaned-wells
Coverage states most relevant to Developers
Common questions from Developers.
Which renewable-siting datasets are included?
BLM Western Solar Plan zones (variance / exclusion / utility-scale) plus the USGS Wind Turbine Database (commercial wind turbines, ~70K records nationally). Together they're enough to screen siting conflicts on most BLM-administered candidate sites.
Can I screen sites without specifying a PLSS section?
Yes — every /api/energy/* endpoint also accepts lat/lon coordinates. The resolver wraps the coordinate in a 1-mile buffer by default and returns the intersection. Pre-computing a section reference is recommended for SEO-stable URLs, but it's not a hard requirement.
Other federal-land personas
Not an energy persona? See workflow guides across every Township America vertical.
All persona guides