LoD2 buildings of Amsterdam from 3DBAG. The 3D preview shows roofs, courtyards and shadows for the selected day and time; no modules are placed in this view yet.Click to enlarge
In my thesis I study urban photovoltaics, with particular attention to bifacial modules and Nordic climates. Nearby buildings can shade the sky or reflect light towards the panels; snow changes the reflectance of surfaces over time. OmniPV brings geometry, weather, optics and electrical design together in one environment for configuring and analysing these effects.
- Goal
- How do irradiance and yield of a rooftop system change once urban geometry, reflections and snow are taken into account? The work compares the contribution of each process, with validation cases and sensitivity analysis.
- Method
- The pipeline ingests LoD2 buildings and materials, attaches weather data and builds an optical scene. Radiance computes the irradiance on the modules; the dynamic snow model updates the state and albedo of the surfaces. The electrical part connects modules, strings and inverters to the yield estimate. The viewer's interactive shadows serve as a visual preview; the scientific calculation runs in the backend.
- Development and features
- I developed four scientific packages — urban3ddata, urbanpvfactors, snowpvsim and snow_urban_orch — and the FastAPI/React demonstrator with a Three.js viewer. The GUI lets you pick the site, load the geometry, place modules and define inverters, strings and MPPT inputs. The electrical design can precede placement, or the wiring can be derived after the simulation from irradiance and module proximity. Weather, geometry and simulation options stay visible in the workflow, together with parameter checks and calculation progress.
Screens and results
Interface and method
From data availability to electrical design. The scene, map and component screens were supplied by the author; placement and simulation illustrate a different configuration example in Amsterdam.
01
Site and LoD2 data coverage
Green areas show the coverage of the available urban datasets. Selecting a site checks the availability of the geometry before opening the 3D model. The scene supplied by the author is in Amsterdam, with 3DBAG data and a 70 m search radius.
02
Modules, inverters and strings
System Design collects the nameplate parameters of modules and inverters, the DC/AC power ratio and the configuration of the MPPT inputs. In Pre-wired mode the strings are planned before placing the panels; in Auto-stringer the wiring is derived after the irradiance calculation.
03
PV layout
The layout is built on the 3D model. The GUI lets you choose module, orientation, distance from the surface and mounting type; you can place a single panel or fill a roof plane with a grid.
04
Filling a roof plane
Newly added modules stay in preview until confirmed. In this second example the fill function arranged 55 panels on a roof plane. The scene also keeps the material class and reflectance of the surrounding surfaces, used in the optical problem.
05
Simulation setup
The page links the weather period, the scene, the layout and the Radiance solver options. The snow model is optional. Before launching, a checklist verifies that the required elements are available; the solver settings let you gauge the cost of the calculation.
06
Pipeline architecture
The sequence follows the project presentation: urban3ddata ingests geometry and materials, urbanpvfactors builds and solves the optical scene, snowpvsim evolves snow and albedo, snow_urban_orch coordinates the simulations. The GUI is one way of using this same pipeline.