How do I set up site screening software for GIS-based buildability checks on candidate renewable sites?

To set up site screening software for GIS-based buildability checks on candidate renewable energy sites, you want a workflow that turns raw geospatial data into a repeatable screening + scoring + constraint mapping process.

Here’s a practical setup approach.

---

1) Define the buildability questions first

Before choosing software, decide what “buildable” means for your project type.

Typical questions:

• Is the site physically suitable for development?
• Are there hard exclusions?
• What are the slope, land cover, flood, setback, and access constraints?
• What is the approximate developable area?
• How much of the site is usable after buffers and exclusions?
• How does the site score against alternatives?

For renewable sites, the criteria differ by technology:

Solar

• Slope
• Aspect / shading
• Land cover / vegetation
• Floodplain
• Proximity to roads and substations
• Parcel size and shape
• Setbacks from water, roads, property lines, protected areas

Wind

• Terrain / elevation / slope
• Turbulence / roughness proxies
• Setbacks from homes and aviation constraints
• Environmental exclusions
• Grid access and transport route feasibility

BESS / substation / other infrastructure

• Parcel size
• Access to road network
• Flood risk
• Zoning / land use
• Utility interconnection proximity
• Environmental and permitting constraints

---

2) Choose the software stack

You generally need three layers:

A. GIS engine

Used for spatial analysis and overlays. Common options:

• ArcGIS Pro / ArcGIS Enterprise
• QGIS
• PostGIS for database-backed spatial processing
• GeoPandas / rasterio / shapely for Python workflows

B. Screening application layer

Used to provide the user interface and workflow. Options:

• Commercial site screening platforms
• Custom web app with map interface
• ArcGIS Experience Builder / Dash / Streamlit / Leaflet-based app
• QGIS plugins or model-driven desktop workflows

C. Data management layer

Used to store candidate sites, constraint layers, and results. Options:

• PostgreSQL/PostGIS
• ArcGIS Enterprise geodatabase
• Cloud object storage plus catalog/index layer

If you want repeatable enterprise screening, a common setup is:

• PostGIS + Python + QGIS/ArcGIS
• or ArcGIS Enterprise + custom geoprocessing tools

---

3) Assemble the base spatial data

You need consistent, up-to-date geospatial layers.

Typical layers:

• Parcel boundaries / cadastral data
• DEM / DSM / slope raster
• Land cover / land use
• Hydrology: rivers, wetlands, floodplains
• Protected areas / conservation lands
• Roads, rail, transmission lines, substations
• Buildings / residences
• Zoning / planning overlays
• Environmental constraints: habitat, species, wetlands, cultural sites
• Aviation / radar / military constraints if relevant
• Administrative boundaries

Make sure all layers are:

• In the same projection or a well-managed coordinate system
• Cleaned for topology errors
• Tagged with source, date, and confidence
• Versioned so you can reproduce results

---

4) Standardize screening rules

Create a rules library that defines each constraint.

Examples:

• Hard exclusion: site intersects protected habitat → exclude
• Setback: 100 m buffer from streams
• Threshold: average slope must be < 10%
• Scoring factor: site within 5 km of substation gets higher score
• Area rule: usable contiguous area must exceed minimum project size

Represent rules in a structured format:

• JSON / YAML
• Database tables
• Configuration files
• Model builder workflows

This makes the screening process auditable and easy to update.

---

5) Build the GIS workflow

A typical GIS-based screening pipeline looks like this:

Step 1: Ingest candidate sites

• Upload polygons, parcels, or centroid points
• Validate geometry
• Attach project metadata

Step 2: Apply hard exclusions

• Intersect candidate site with exclusion layers
• Remove or flag sites that overlap forbidden areas

Step 3: Apply buffers/setbacks

• Buffer roads, water bodies, homes, protected areas, etc.
• Subtract buffered areas from site polygons

Step 4: Compute physical suitability metrics

• Slope statistics from DEM
• Terrain ruggedness
• Contiguous developable area
• Cut/fill proxies if needed
• Aspect/shading if solar

Step 5: Compute access and infrastructure metrics

• Distance to roads
• Distance to transmission or substation
• Access route complexity
• Distance to ports/rail for large components if relevant

Step 6: Score and rank

• Weighted scoring system
• Multi-criteria decision analysis
• Normalize metrics so sites are comparable

Step 7: Generate outputs

• Screening report
• Map layers
• Scorecards
• Boolean pass/fail flags
• Constraint summary tables

---

6) Decide on the analysis method

There are three common methods.

A. Rule-based screening

Best for pass/fail feasibility.

• Simple
• Transparent
• Easy to defend

Example:

• If slope > 15% → reject
• If overlap with wetlands > 0 → reject
• If usable area < 20 ha → reject

B. Weighted scoring

Best for ranking candidates.

• More nuanced
• Helps compare sites
• Needs careful weight design

Example weights:

• Grid proximity: 30%
• Slope: 20%
• Environmental constraints: 25%
• Access: 15%
• Parcel size: 10%

C. Hybrid

Most useful in practice.

• First apply hard exclusions
• Then score surviving sites

This is usually the best setup for renewable site screening.

---

7) Set up the geoprocessing logic

In software terms, your screening engine should support:

• Overlay: intersect, union, erase, clip
• Buffering: setbacks around features
• Raster analysis: slope, reclassification, cost surfaces
• Nearest neighbor / distance calculations
• Area calculations for usable land
• Topology checks for invalid geometries
• Batch processing for many candidate sites

If using Python, the workflow often looks like:

• Load candidate site polygons
• Load constraint layers
• Reproject all data
• Run intersection/buffer operations
• Calculate summary statistics
• Write results back to database and exports

---

8) Design the data model

A clean data model makes the system scalable.

Minimum tables:

• candidate_sites
• constraint_layers
• screening_rules
• screening_results
• site_scores
• audit_log

Useful fields:

• Site ID
• Geometry
• Project type
• Constraint flags
• Usable area
• Slope stats
• Distance to grid
• Final score
• Screening version
• Date screened

---

9) Add map-based user interaction

A good screening tool usually includes:

• Draw or upload site polygons
• Toggle constraint layers
• Show pass/fail indicators
• Display metrics in a dashboard
• Click a site to see rule-by-rule reasons
• Export reports and maps

This is important because stakeholders often need to understand why a site was screened out.

---

10) Build reporting and auditability

Each screening result should be reproducible.

Include:

• Data sources used
• Rule set version
• Analysis date
• Coordinate system
• Threshold values
• Summary of exclusions and buffers
• Map snapshot or export
• Notes on limitations

This is especially important for permitting, land acquisition, and investment decisions.

---

11) Validate with known sites

Test the software against:

• Known good sites
• Known rejected sites
• Edge cases
• Sites with partial overlaps
• Small/irregular parcels
• Sites with incomplete data

Check:

• Whether the results match expert judgment
• Whether the buffers are being applied correctly
• Whether raster and vector data align
• Whether output areas are realistic

---

12) Automate updates

Renewable screening depends on current data.

Set up:

• Scheduled refresh of roads, parcels, flood maps, protected areas
• Version control for rules
• Automated reruns when base data changes
• Logging for every screening batch

---

Example architecture

A practical implementation might be:

• Database: PostgreSQL/PostGIS
• Processing: Python (GeoPandas, rasterio, shapely)
• Desktop QA: QGIS
• Web UI: Leaflet or Mapbox-based app
• Reporting: PDF/HTML generated from templates
• Deployment: Docker on cloud VM or internal server

---

Recommended implementation sequence

If you’re starting from scratch:

1. Define technology-specific screening criteria
2. Collect and clean core GIS layers
3. Build rule table for exclusions and scoring
4. Prototype in QGIS or Python
5. Validate against sample sites
6. Automate in a repeatable pipeline
7. Add UI and reporting
8. Deploy for batch screening

---

Common pitfalls

• Mixing coordinate systems
• Using outdated constraint layers
• Applying arbitrary weights without validation
• Ignoring parcel shape and access
• Not distinguishing hard exclusions from soft constraints
• Failing to document rule versions
• Treating raster resolution as more precise than it is

---

If you want a fast starter configuration

For a lean but powerful setup:

• QGIS for interactive review
• PostGIS for data storage
• Python for automated screening
• JSON/YAML for rules
• PDF/HTML reports for outputs

---

If you want, I can also give you:

1. a sample screening rule set for solar or wind,
2. a database schema, or
3. a Python/QGIS workflow example.