Understanding Solar Shading Calculations in Dense Cities
I spent three years doing feasibility studies for rooftop solar on mid-rise buildings across Mumbai, Bangalore, and Pune before I ever heard anyone use the term Surya Height in a professional context. The concept itself isn't new—engineers have been thinking about building height ratios and shadow casting for decades—but the way it has been packaged recently as a systematic approach to urban solar assessment is worth paying attention to. At its core, Surya Height is a method of evaluating how the vertical dimension of a structure impacts the solar irradiance it can capture, and how much shadow it casts on neighboring properties. Most tools you find online focus purely on roof area. They give you square meters of panel capacity and call it a day. What they miss is the height variable. A 10-meter building and a 30-meter building on the same plot will have dramatically different solar harvesting profiles, not just because of roof size, but because of self-shading, adjacent-building shading, and the angle of incidence changes across floors. I learned this the hard way on a project in Kharadi, Pune. We had calculated a 45 kW system for a five-story residential building. The numbers looked solid on paper. When we actually ran the annual yield simulation using hourly irradiance data, the ground-floor mechanical room and the stairwell window were casting shadows that knocked 18 percent off the expected output between 8 AM and 10:30 AM during the peak summer months. The roof-level panels were fine. The issue was that the building's own height created a cantilevered shadow that moved across the array plane as the sun climbed. Most software doesn't flag this unless you model the full 3D geometry with high resolution. I ended up rerouting two strings to bypass the shaded section and adding a micro-inverter on the affected panels, which cost an extra 22,000 rupees but recovered the lost generation within 14 months.
Surya Height The Growing Phenomenon Redefining Urban Solar Potential
The reason this approach is gaining traction in urban planning circles is straightforward. cities are getting taller. Density is increasing. The old assumption that rooftop solar is just about available roof area stops working once you are dealing with buildings that are six stories or higher, or structures surrounded by other tall buildings. The shadow envelope becomes a live variable that changes throughout the year in ways that simple tilt-and-orientation calculations cannot capture. Here is how the method actually works in practice. You start with the building's height-to-width ratio. Then you map the solar path for your specific latitude and overlay the shadow trajectory across every month of the year. The critical windows are the winter solstice period when the sun sits lowest and shadows stretch furthest, and the monsoon months when diffuse radiation dominates and direct beam modeling matters less. Most practitioners make the mistake of only checking June and December. That misses the May-to-July window where monsoon cloud cover creates high diffuse fractions and the angle of the sun is still relatively low, meaning side-shading from adjacent towers becomes significant. The calculation itself involves determining the shadow cast factor, which is the ratio of shaded area to total panel area across the annual cycle. A factor below 0.15 is generally considered acceptable for standard string inverter setups. Above 0.25 and you need to start thinking about power optimizers or micro-inverters. Above 0.40 and the project may not be viable without structural changes to the array layout.
I use a combination of HelioScope for the initial screening and PVsyst for anything that comes close to the threshold values. HelioScope is faster and handles basic 3D shading reasonably well. PVsyst gives you the hourly resolution you need to catch those morning shadow intrusions that HelioScope smooths over. The tradeoff is time. A full PVsyst run with monthly horizon masks can take 45 minutes to an hour per building. HelioScope does the same job in about eight minutes. I run both on anything over 20 kW. One thing that catches people out is the assumption that more height always means more shading. It doesn't. A taller building with a set back design often casts a narrower shadow footprint than a shorter building with a full-footprint rectangular shape. The setback changes the angle at which the shadow falls on neighboring roofs. I once evaluated a building where the lower four floors were a solid block but the top two floors were stepped back. The stepped portion actually received better winter morning sun than the roof of the building next door, which was a uniform six-story rectangle. The height difference was only three meters, but the shadow pattern flipped entirely because of the massing. There are real limitations to this approach. The biggest one is data availability. Accurate horizon masking requires precise GPS coordinates, lidar-derived building models, or at minimum hand-measured dimensions of every structure within a 200-meter radius. In many Indian cities, the municipal records are outdated by five to eight years. New buildings go up, old ones get demolished, and your shading model is wrong before you even start. I have had to visit sites twice just to verify that a construction site across the street hadn't broken ground yet. The workaround is to cross-reference Google Earth historical imagery with the current plan, and flag any uncertain structures as worst-case scenarios in your report.
Get the Full Details
Another limitation is that Surya Height calculations do not account for soiling patterns. A building that casts minimal shadows might still underperform if it is in an area with high dust deposition, which is nearly everywhere in India during the pre-monsoon months. The two factors compound. Heavy soiling plus moderate shading can drop your capacity factor by 30 percent or more, and that is not something the shading model will tell you. If you are just starting out, the practical path is to use the height-to-width ratio as a quick filter. Anything above 3.5 in a dense urban environment deserves a full PVsyst analysis. Anything below 2.0 and your shading losses are probably negligible. The in-between range is where most projects live, and where the extra time spent on accurate simulation pays for itself in avoided overpromising. The tools have gotten better over the last three years. NREL's SPA algorithm is now standard in most simulation packages, and satellite-based 3D city models from sources like OSM Buildings give you a reasonable starting point even when municipal data is sparse. But no tool replaces the judgment call of knowing when a model is being too optimistic. I still go to the site whenever the system size is above 50 kW or the shading factor is hovering around 0.20. The photos I take on site and the shadow observations I make at different times of day catch things the software smooths over.
Urban solar is not going away. Buildings are just getting taller, and the math gets harder the higher you go. The people who figure out how to model it accurately are the ones who will keep getting contracts.
