Six perspectives for accounting for distant terrain in the PVSyst manual

Table of Contents

• Basics to grasp before considering distant terrain

• Perspective 1: Determine when distant terrain influences power generation.

• Viewpoint 2: Consider separating near shadows and distant terrain

• Perspective 3: Confirm the accuracy and granularity of horizon data

• Perspective 4: Prevent Misreading of Azimuth and Elevation Angle

• Perspective 5: Check seasonal and time-of-day effects in the results

• Perspective 6: Convert into decision-making materials that can be used for design changes

• Common points of confusion when reading the PVSyst manual

• Practical workflow for handling distant terrain

• Considerations when explaining results to stakeholders

• The importance of linking on-site surveys and simulations

• Summary

Basics to Understand Before Considering Distant Terrain

In simulations of solar power generation, many configuration items are handled, such as panel performance, PCS capacity, orientation and tilt, meteorological data, and loss conditions. Among these, one that is easily overlooked is solar shading caused by distant terrain. When there are buildings or trees immediately adjacent to the site, the presence of shadows is easy to notice, but cases where slightly more distant terrain—such as mountain ranges, hills, slopes, forest belts, or surrounding high ground—blocks morning and evening sunlight can be difficult to assess by simply walking the site.

The purpose of reading the PVSyst manual is not simply to learn how to use the interface. It is important to understand which settings affect energy production and how precisely each condition needs to be entered. When accounting for distant terrain, you assemble the simulation conditions while checking how finely to reproduce the terrain’s shape, which directions have obstructions, and how much they will affect performance at the low sun angles in winter.

Distant terrain is often treated less as something that intricately covers parts of panels like near-field shading and more as an element that blocks sunlight itself during periods when the sun is near the horizon. Therefore, rather than drawing the exact shape of shadows in detail, it is important to adopt the mindset of understanding at which azimuths and up to what elevation angles the sky is obscured. In other words, it is an approach that organizes the surrounding horizon as seen from the power plant in terms of combinations of azimuth and elevation.

For example, at a site with mountains to the east, direct solar radiation in the morning may be delayed. At a site with a ridge to the west, power generation in the evening may fall off earlier. If there is a high ridge to the south, it can have a larger impact in winter when the solar elevation is low. For photovoltaic systems in the Northern Hemisphere, southern shading tends to be particularly important, so when checking distant terrain you need to carefully examine the horizon from southeast to southwest.

However, setting far-field terrain in excessive detail does not necessarily increase accuracy. If you reproduce fine terrain detail while the input data remain of low accuracy, you may end up with a simulation that is even less well founded. When checking the setup method in the PVSyst manual, it is important to consider not only the on‑screen procedures but also how reliable the terrain data you input are and whether they are at a level suitable for use in design decisions.

Perspective 1: Identify situations where distant terrain affects power output

Whether distant terrain should be taken into account varies greatly depending on site conditions. In flat coastal areas or industrial parks with open surroundings, shading from distant terrain may be minimal. On the other hand, in mountainous areas, hilly terrain, developed land, valley terrain, basins, former quarry sites, or sites surrounded by slopes, the terrain can significantly limit morning and evening sunlight.

What you should pay particular attention to is that the on-site visual impression does not necessarily match the impact on power generation. To the human eye, distant mountains may not look very high, but they can still block sunlight during periods when the solar altitude is low. Conversely, even if mountains appear large, their effect on power generation can be limited if they lie outside the sun’s path. What matters is not the dramatic appearance of the terrain but whether it coincides with the sun’s trajectory.

The effects of distant terrain are not uniform throughout the year. In summer, solar altitude is high and the morning and evening periods are longer, so the impact of terrain can appear limited. However, in winter the solar altitude is low, and ridgelines and hills on the southern side can shorten power generation hours. Even if the difference looks small when considering only annual generation, it can be non-negligible for projects that prioritize winter generation.

Also, from the perspective of power sales plans and self-consumption plans, the impact of distant terrain varies. When prioritizing annual generation under an all-output power sales model versus expecting generation to match a factory’s or facility’s morning demand, the same shading is evaluated differently. On sites where mountains to the east delay the start of morning generation, the effect on morning self-consumption may decrease. On sites where mountains to the west cause generation to fall early in the evening, the contribution to evening demand may be reduced.

When reviewing the PVSyst manual, you should not just read the remote terrain input screen; you need to consider it in the context of the project's objectives. The required depth of analysis varies depending on whether you want to improve the accuracy of energy yield estimates, compare design options, reduce the risk of investment decisions, or provide grounds for explanations to stakeholders.

In sites where considering distant terrain is particularly important, it is essential to confirm terrain conditions at an early stage. If the influence of distant terrain is noticed after deciding the layout design or equipment capacity, revisions to the projected power generation, design changes, and remaking of explanatory materials may occur. During the initial study stage, checking whether there are mountains or hills nearby, whether the site is valley-shaped, and whether the southern horizon is open can reduce rework in later stages.

Viewpoint 2: Consider separating near-field shadows and distant terrain

As you read through the PVSyst manual, you will find that there are multiple approaches to shading settings. One area that is easily confused is near shading versus distant terrain. Both are elements that block solar radiation, but they differ in how they are handled in the simulation and in the data that should be entered.

Close-proximity shading often refers to shadows cast on panels by objects located relatively close to the site, such as buildings on- or off-site, rows of mounting racks, fences, utility poles, trees, and equipment. With close-proximity shading, localized phenomena become problematic—shadows covering part of a panel, the shape of the shadow changing over time, and parts of a string being affected. Therefore, it is necessary to reproduce obstacles and the array layout using a 3D scene and verify shadow movement and how electrical losses are handled.

On the other hand, distant terrain is basically considered to be a situation in which part of the horizon, as seen from the power plant, is elevated. Mountains or ridges can hide the sun, causing direct solar irradiance not to reach the plant during periods when the sun would otherwise be visible. Rather than casting complex shadows on only part of the panels, distant terrain is treated as an element that blocks direct solar irradiance to the entire plant while the sun is at that azimuth and elevation.

Getting this separation wrong makes not only the data-entry work more complicated, but also the interpretation of the results more difficult. For example, attempting to model a distant mountain in detail as a 3D near-shadow obstacle can take a lot of time to reproduce its shape while being excessive for evaluating its impact on power generation. Conversely, treating buildings or trees located immediately south of the site roughly as distant terrain can lead to overlooking per-panel shadows and string-level losses.

In practice, it is easier to understand if you first organize the causes of shading by distance and by the extent of their impact. Mountain ranges and terrain ridgelines that are distant from the site are considered distant terrain. On-site equipment, neighboring buildings, nearby trees, and shadows between arrays are treated as near-field shading. When the boundary is ambiguous, judge by whether the shadow shape causes local changes on the panel surface or whether it limits the sun’s visibility for the entire power plant.

This distinction is also useful when explaining matters to stakeholders. Losses due to distant terrain arise from the site's overall geographic conditions and therefore can be difficult to eliminate by layout changes alone. On the other hand, nearby shading can be improved by reviewing array layout, separation distances, tree management, and equipment placement. If the causes of the losses are explained separately, it becomes easier to distinguish losses that can be mitigated from those that should be accepted.

When checking the shadow items in the PVSyst manual, be mindful of which screens are related to distant terrain and which are related to near shading. Rather than mechanically filling in the settings, determining which feature is most appropriate to represent the shading phenomena occurring on site is the first step to improving simulation quality.

Perspective 3: Check the accuracy and granularity of horizon data

When considering distant terrain, the accuracy of horizon data is crucial. For each azimuth as seen from the power plant, you need data that indicate how high the terrain obstructs the sky. If this is inaccurate, no matter how carefully you enter information into PVSyst, the reliability of the results will not improve.

There are several factors that affect the accuracy of horizon data. First is azimuth accuracy. If the cardinal directions are misaligned, the positions of mountains and hills will not correctly align with the solar path. If a mountain that lies to the southeast is entered as due south, the impact around solar noon in winter may be overestimated. Conversely, if a southern ridge is shifted to the southwest, the assessment of the affected time periods will change.

Next is the accuracy of the elevation angle. The elevation angle is the concept of expressing the height of the horizon, as seen from an observation point, in terms of angle. The apparent height changes not only with the mountain’s elevation but also with the distance from the power plant to the mountain. Even a tall mountain will have a small elevation angle if it is far away, and a low hill will have a large elevation angle if it is close. Therefore, instead of judging only by elevation differences on maps, it is necessary to treat the situation as the apparent horizon as seen from the power plant.

Furthermore, the granularity of the data is also important. If you divide azimuths too coarsely, you cannot represent the undulations of a mountain range. In particular, for azimuths where the ridgeline rises abruptly, or for terrain where the morning sun enters from a valley, coarse data can lead to overestimating or underestimating the effects. Conversely, making the granularity too fine is meaningless if the accuracy of the source data does not support it. Granularity should be chosen to match the scale of terrain changes at the site and the reliability of the input data.

There are several methods for creating distant terrain data: measuring the horizon on site, generating it from terrain data or map information, and using dedicated survey or analysis data. Whatever method is used, it is important that the result can ultimately be organized as the horizon elevation by azimuth as seen from the power plant. When relying solely on on-site photographs, attention must be paid to the shooting location, camera leveling, azimuth, lens distortion, and so on. Photographs are useful as explanatory material, but they may require correction and verification before they can be used directly as numerical data.

When entering data while referring to the PVSyst manual, it is also important to record the source of the horizon data. When you later review simulation results, if you don't know which data were used—whether they were on-site measurements, map-based, or approximate inputs—it becomes difficult to explain the validity of the figures. In design reviews and customer briefings, not only the power generation figures but also their underlying assumptions will be questioned.

Also, far-field terrain is not something you input once and forget. If earthworks change the site's elevation, the observation point will change and the appearance of the horizon may also change. If the panel installation height changes, the way nearby slopes or hills appear can also change slightly. On large-scale developed sites or sloping terrain, it is advisable to check multiple locations within the site—not just a representative point—to ensure horizon conditions do not change.

What's important when considering accuracy and granularity is to invest effort commensurate with the impact on power generation. There is no need to produce excessively detailed data for sites where the influence of distant terrain is small. However, in mountainous areas where winter power generation has a large effect on project viability, an approximate horizon may be insufficient. The PVSyst manual shows how to operate the software, but the required level of input accuracy must be determined based on site conditions and project objectives.

Viewpoint 4: Prevent Misreading Azimuth and Elevation Angles

A common mistake when setting up far-field terrain is misreading the azimuth and elevation angles. Even when configuring settings while referring to the PVSyst manual, misinterpreting the azimuth reference or how angles are handled can cause simulation results to diverge from actual site conditions. In particular, when combining survey data, map data, site photographs, and design drawings, you need to pay attention to differences in coordinate systems and azimuth references.

First, I want to confirm which "north" is being used as the reference. On-site orientations include true north, magnetic north, north on drawings, and north in the coordinate system. For simulations that deal with the sun's path, you need to use true north as the reference. When checking orientation on site with a smartphone or a compass, the bearing can be shifted by magnetic declination or by the influence of nearby metal objects. Even a slight deviation in orientation can change the apparent position of mountains to the southeast or southwest, which can affect the evaluation of shading times in the morning and evening.

Next, we will read the elevation angle. The elevation angle expresses the height of terrain as an angle measured from the horizon. Do not confuse this with the mountain’s elevation itself. For example, even a mountain with a high elevation will have a small elevation angle as seen from the power plant if it is far away. Conversely, low hills or slopes located very close to the site can have a large elevation angle even if the elevation difference is small. In far-field terrain settings, what matters is not the absolute height of the terrain but how it obstructs the sky as seen from the power plant.

Care is also required when entering azimuths. On drawings or in GIS, the way angles are measured can differ. Some formats use north as 0° and measure clockwise, while others treat east as the reference and measure counterclockwise, like mathematical coordinates. If you enter data without converting it, mountain positions may be mirrored or east and west may be swapped. When checking the screen descriptions in the PVSyst manual, always confirm which reference is used for the displayed angles.

Also, when the site is large, it is important to decide which location will serve as the observation point. The horizon measured at the center of the power plant and the horizon measured at the site's southern or northern edge will differ more when nearby terrain is present. If the mountain range is far away the difference may be small, but in hilly or valley terrain the portion of the sky that is visible changes depending on the position within the site. When using a representative point, you need to verify that the point can represent the entire power plant.

In practice, checking azimuth and elevation angles using multiple methods reduces mistakes. Confirm the approximate azimuth on a map, verify how the terrain looks with on-site photos and survey data, and then cross-check with the display in PVSyst. After entering the data, check the overlap with the solar path to ensure it does not clearly contradict what you observe in the field. For example, if there is a mountain on the east side in the field but the simulation shows shading on the west side, there may be a problem with azimuth conversion or the input orientation.

Mistakes in azimuth and elevation angle can be hard to notice from the results screen alone, because the difference in generated power can appear natural. Therefore, making a checklist at the input stage is effective. Confirm whether the azimuth is referenced to true north, whether the azimuth direction is correct, whether the elevation angle is measured from the horizon, whether the observation point is appropriate, and whether the source of the data is recorded before proceeding to calculations; doing so reduces rework in later stages.

Perspective 5: Verify seasonal and time-of-day effects in the results

After setting the distant terrain, it is important not to judge solely by changes in annual energy production. Because the effects of distant terrain tend to be biased by season and time of day, you need to check the results by month, by time of day, and by loss category. When reading the PVSyst manual, it is important to understand the whole process—not only how to enter inputs but also how to interpret the results.

Looking only at annual power generation, losses caused by distant terrain can appear small. However, if those losses are concentrated in winter mornings and evenings, they can be significant for project planning. Especially in regions that already receive little winter solar radiation, further reductions of morning and evening solar radiation can make the drop in monthly generation more pronounced. Even if the annual total is less than a few percent, the difference in specific months can become hard to ignore.

Checking by time of day is also important. Distant terrain on the east side tends to affect the morning power-generation start time, while distant terrain on the west side tends to affect the evening power-generation end time. If there is high terrain to the south, it can also affect daytime periods in winter. If the plant is for self-consumption, not only the simple annual generation but also how much can be generated during periods of demand is important. When it coincides with morning start-up times or evening load peaks, the impact of distant terrain should be evaluated more carefully.

When reviewing the results, it's easier to understand if you compare a case with distant terrain configured to a case without it. If you compare by changing only the horizon condition while keeping the same meteorological data, the same equipment conditions, and the same loss conditions, you can determine how much the distant terrain affects power generation. This comparison is also useful for internal reviews and for explaining to customers. However, when creating comparison cases, you need to clearly record which conditions were changed.

In the monthly results, check which seasons show differences. If the differences are large in winter, low sun angles combined with topography may be responsible. If the differences are small in summer, the higher sun angles likely allow solar radiation to clear the terrain. If east–west-oriented terrain is influencing the site, examine the generation curves by time of day as well as by season to more easily grasp changes in the morning and evening ramp-up and decline.

The numbers shown in loss diagrams and reports must also be read with an understanding of what they mean. Quoting figures alone without checking which line items include shading losses and how shielding from distant terrain is reflected can lead to misunderstandings. Consult the PVSyst manual to verify the meanings of the result items and to determine which losses represent the effects of distant terrain.

Also, results for distant terrain can be used to compare design proposals. For example, by slightly changing the array layout within the same site you can compare whether the terrain’s influence changes significantly. If changing the fill height or installation position slightly lowers the southern horizon, it may lead to improved winter power generation. However, because distant terrain is often not resolved by layout changes alone, it is important to assess the improvement together with earthworks and design costs.

What should be avoided during result checks is placing too much trust in simulation values. If remote terrain data are approximate, the results should also be treated as approximate evaluations. Inputs based on precise field surveys and detailed terrain data will produce results with greater explanatory power. Aligning input accuracy with how the results are used leads to simulations that are trusted in practice.

Perspective 6: Convert into decision-making material usable for design changes

Simply inputting distant terrain into PVSyst and checking the estimated power output does not provide sufficient practical value. What matters is translating those results into a form that can be used for design changes and business decisions. Simulation is not merely a task to calculate power output; it is a process for understanding risks, comparing options, and producing decision-making materials that stakeholders can accept.

First, clarify whether losses due to distant terrain can be avoided. Shading from distant mountain ranges often cannot be resolved by the power plant’s design alone and must be accepted as a site condition. On the other hand, it may be possible to mitigate the impact by changing the on-site layout or installation height. For example, consider moving arrays toward locations on the site where the southern horizon appears lower, adjusting site grading heights, or reconsidering the layout density in specific areas.

Next, assess how much the impact on power generation affects project viability. If the annual loss due to distant terrain is small, the cost of design changes may not be recoverable. Conversely, if winter power generation drops significantly and affects feed-in revenue or the benefits of self-consumption, it may be worth considering design changes or revising the plan. It is important not to view PVSyst results in isolation, but to evaluate them together with equipment costs, land development costs, operating conditions, and contract terms.

When using the effects of distant terrain in design decisions, comparing multiple cases is effective. By comparing a case that does not consider terrain, a case that considers simplified terrain, a case that considers detailed terrain, and cases that vary layout or height, it becomes easier to see which factors are affecting power generation. When making comparisons, it is important not to change too many conditions at once. Changing multiple conditions simultaneously makes it impossible to determine what is causing the differences in power generation.

When explaining to stakeholders, it is important not only to present losses due to far-field terrain as "adverse conditions," but to explain them as "generation forecasts that incorporate site-specific conditions." Results that reflect conditions closer to reality increase the reliability of the plan compared with optimistic simulations that do not take terrain into account. In particular, for projects in mountainous or hilly areas, the fact that far-field terrain has been considered itself serves as evidence of a thorough evaluation.

Also, when using the results for design changes, you need to translate them into words as well as numbers. In addition to expressions like "annual energy production decreases by X kWh," explanations such as "the start of generation on winter mornings is delayed," "evening generation time is shortened due to terrain on the west side," and "a southern ridge affects production when the sun is at low altitude" will make it easier for stakeholders to understand the situation. Don't just read the PVSyst manual; make sure you can explain the results in relation to the site's terrain and the movement of the sun.

Distant terrain is a factor that limits design flexibility, but if identified early it is also an element whose risks can be managed. If you assess terrain impacts in the early planning stage and incorporate them into the expected energy yield, you can reduce later occurrences of “it doesn’t generate as much as expected.” Settings in PVSyst should be positioned as a practical means to achieve that.

Common Points of Confusion When Reading the PVSyst Manual

When reading the PVSyst manual, many people’s initial confusion is over which settings correspond to far-field terrain and which correspond to near shading or 3D scenes. Because there are multiple items related to shading, trying to fill them all in the same way leads to confusion. It becomes easier to grasp the meaning of the settings if you understand far-field terrain as representing the height of the horizon as seen from the power plant.

Another common point of uncertainty is how much detail to input for distant terrain. Ridgelines can be complex when examined closely, but in simulations it is important to appropriately represent the areas that affect power generation. Trying to reproduce every bump increases the workload, and entering details for orientations that do not overlap the sun’s path has only a limited effect on generation. It is efficient to prioritize checking terrain from southeast through southwest, terrain that overlaps the sun’s altitude in winter, and terrain that affects generation during morning and evening.

The justification for input values is also an area that can be confusing. Values read from maps, estimated from on-site photographs, and derived from survey data have differing levels of reliability. Before entering data into PVSyst, clarifying the methods used to generate the data will make it easier to explain the results. In particular, the level of justification required varies depending on whether it is a preliminary assessment, detailed design, or documentation to be submitted to financial institutions or clients.

Also, when you look at PVSyst results, the loss due to distant terrain may be shown as smaller than expected. In this case, it does not necessarily mean that the inputs are incorrect. The distant terrain may not overlap much with the sun’s path, the impact may be limited to low-irradiance periods in the morning and evening, or the effect on diffuse irradiance may be limited—any of which can reduce the impact on annual energy yield. Conversely, if a larger loss than expected appears, you should check for input errors in azimuth or elevation angle, overestimation of southern terrain, or differences in the observation point settings.

When reading the manual, don't just follow the operating steps; also check what the graphs and numbers displayed on the screen mean. In particular, on screens where you can visually confirm the relationship between the horizon and the sun's path, it's important to verify that they match the local terrain. Even if the numeric input appears correct, if the graph shows an obstruction in an obviously unnatural position, there may be a problem with how azimuth or angle are being handled.

Furthermore, when creating multiple cases within a project, it is important to manage which terrain conditions were applied to each case. Leaving distinctions in case names or notes—such as with far-field terrain, without far-field terrain, simplified terrain, and detailed terrain—makes it easier to compare results later. Simulations are not one-time events; they are often updated whenever design changes or changes in conditions occur, so managing the assumptions can determine the quality of the work.

Practical workflow for handling remote terrain

The practical workflow for handling distant terrain in PVSyst begins with checking on-site conditions. First, confirm whether there are mountains, hills, slopes, forests, elevated ground, or embankments from land development around the planned power plant site. Because maps and aerial photos alone may not reveal everything, it is desirable to combine them with on-site photos and field inspections. Pay particular attention to the south, southeast, and southwest.

Next, narrow down the directions that are likely to be affected by terrain. Rather than investigating all directions with equal effort, it is more efficient to prioritize those that are most likely to coincide with the sun’s path. Terrain on the north side often has little effect on power output for typical south-facing solar power generation, but depending on site conditions, latitude, and panel azimuth it may still need to be checked. Terrain to the east and west affects generation during morning and evening hours, so pay particular attention to those when planning for self-consumption.

After that, create horizon data as seen from the power plant. Using on-site surveys, terrain data, photo analysis, map information, and so on, compile the elevation angles for each azimuth. At this time, decide where to place the observation point. For small power plants with uniform terrain conditions, a representative point may be sufficient, but for large sites or sites with undulating terrain, confirmation at multiple points may be necessary.

Once the horizon data have been organized, input them into PVSyst and check their relationship to the sun’s path. Rather than proceeding to calculations immediately after input, use the graphs and displays to confirm that the azimuth and elevation match your on-site perception. It is important to check that east and west have not been swapped, that the mountains on the south side appear at the correct azimuth, and that the elevation angles are not excessively high or low.

Next, compare the case with distant terrain and the case without it. This comparison allows you to assess how much distant terrain affects annual power generation, monthly power generation, and hourly power generation. If the differences are small, you may determine that distant terrain is not a major constraint in the design. If the differences are large, they should be reflected in design changes and in the project feasibility assessment.

Finally, reflect the results in the design documents and explanatory materials. Simply writing "distant terrain was considered" is not sufficient. Be able to explain which directions have what terrain features, which seasons and times of day are affected, and to what extent this was reflected in the expected power generation. Also organize the sources and creation methods of the input data, as this will make it easier to respond later if verification of the conditions becomes necessary.

By repeating this flow, handling remote terrain becomes not merely an input task but a process that enhances design quality. The PVSyst manual is an entry point for operation, but in practice it is important to treat on-site verification, data preparation, input, comparison, and explanation as an integrated whole.

Please translate the following input into English.

Approach to explaining results to stakeholders

Simulation results that take distant terrain into account often need to be explained not only to design engineers but also to various stakeholders such as project owners, investors, contractors, maintenance personnel, and internal approvers. What is important in such cases is not to present the technical configuration details as-is, but to clearly organize how they affect power generation.

First, briefly explain what distant terrain is. It is easier to understand if you explain that it refers to situations where surrounding mountains or hills hide the sun, making direct solar radiation unlikely to reach the site during certain times of day. Explain that, unlike shadows from nearby buildings or trees, distant terrain is a geographic condition of the entire site that affects the hours of power generation, which makes the difference from local shading clear.

Next, indicate the time periods that are affected. For example, expressions such as the morning generation start being delayed by mountains to the east, the evening generation end being brought forward by a ridge to the west, or the ridgeline to the south affecting daytime generation in winter. Stakeholders may find it difficult to visualize the situation from the annual loss rate alone. Explaining by combining time of day and season makes it easier to convey the relationship between the site’s terrain and power generation.

When showing differences in power generation, make the comparison conditions clear. Explicitly state whether you are comparing a case that does not consider distant terrain with one that does, comparing layout plan A with layout plan B, or comparing cases with different fill heights. If you present only numbers while the conditions are ambiguous, interpretations may diverge later.

Also, you need to appropriately communicate the accuracy of the results. If the horizon data are detailed and based on on-site surveys, you can explain their reliability. If the data were created from overview maps or photographs, you should state that they are an approximate assessment. Because simulation results depend on the input data, explaining the reliability of the input conditions supports the credibility of the results.

Even when losses caused by distant topography are large, this does not necessarily mean the design is poor. In mountainous or hilly areas, there can be unavoidable shading as a site condition. What matters is that those conditions are not overlooked and are reflected in the projected power generation. In fact, overly optimistic power-generation estimates that ignore terrain effects are more likely to lead to problems later on.

When explaining to stakeholders, it is constructive to also present the possible countermeasures. Organize whether improvement can be achieved by changing the layout, whether adjusting the installation height would be effective, whether it relates to the site development plan, or whether it should be accepted as a condition of the land. By separating items that can be addressed from those that cannot, discussions become less subjective and decisions become easier.

The Importance of Linking On-Site Surveys to Simulations

To handle distant terrain correctly, coordination with on-site surveys and field verification is essential, not just the settings in PVSyst. Simulations calculate based on the input conditions, but if those input conditions differ from the actual site, the results will also deviate from reality. Distant terrain in particular includes many elements that are hard to capture from drawings alone, so it is important to confirm the openness of the sky as seen from the site.

In the field, inspect the surrounding horizon from a representative point at the planned power plant site. Record what terrain is visible in the southeast, south, southwest, west, and east directions, and keep these as photographs and survey data. If possible, quantify the azimuth and elevation angles and organize them into a format that can be entered into PVSyst. On-site photographs alone are useful as explanatory material, but to use them for energy-yield calculations the angular information needs to be organized.

On a site before development, it is necessary to take into account the finished ground level and the panel installation height. This is because the horizon as seen from the current ground level can differ from the horizon as seen from the racking height after completion. Especially when slopes or embankments are nearby, slight differences in height can change the apparent horizon. During the design stage, it is important to evaluate the terrain under conditions that approximate the final viewpoint.

By using smartphones, GNSS devices, point cloud measurements, photogrammetry, and similar tools, you can record site conditions more efficiently. However, even when using equipment, it is important to organize orientation, coordinates, elevation, camera positions, and measurement reference points. If you lose track of which location the measured data corresponds to, it will be difficult to enter it into PVSyst or to use it for later verification.

Data consistency is important when linking field surveys and PVSyst. If the coordinates used for surveying, the coordinates on design drawings, and the orientations and positional relationships in the simulation are inconsistent, the terrain's orientation and elevation may be misinterpreted. Sharing reference points, orientations, elevations, and the data used among the design team, the surveying team, and the simulation team helps reduce errors.

Also, the data collected on site is useful for verification after the plant is completed. If power generation after the start of operations is lower than expected, it provides material to distinguish whether shading from distant terrain occurred as predicted, or whether other factors such as nearby shading, dirt, or equipment malfunctions are involved. If terrain conditions are recorded at an early stage, they will serve as a reference when conducting root cause analysis later.

Thus, considering distant terrain is not a task that can be completed solely within the PVSyst interface. You need to measure the site, read the terrain, convert it into azimuth and angles, reflect it in the simulation, and use the results for design decisions. When handling position and terrain information acquired on site, using an iPhone-mounted high-precision GNSS positioning device such as LRTK can make on-site verification and the organization of survey data more efficient.

Summary

When considering distant terrain in the PVSyst manual, it is important not only to memorize how to operate the settings screen but also to understand how the site’s terrain affects energy production. Distant terrain refers to elements such as mountains, hills, ridges, and slopes that can block the sun and limit direct solar irradiance during specific seasons and times of day. It can particularly affect expected energy production in mountainous areas, hilly terrain, valleys, and reclaimed or graded land.

The first thing to check is whether distant terrain actually affects the site's power output. The impact may be small on an open site, but caution is needed if there is terrain to the south or in the east–west directions. Next, separate near shadows and distant terrain. Treat shadows from nearby buildings, trees, and mounting racks as near shadows, and consider distant mountain ranges and the height of the horizon as distant terrain to make organization easier.

When entering horizon data, the accuracy of azimuth and elevation angle is important. Verify whether azimuths are referenced to true north, whether elevation angles are defined as angles above the horizon, and whether the observation point is appropriate. The granularity of terrain data should also be chosen to match site conditions and objectives. Rather than simply increasing detail, it is important to use well‑founded data that focuses on the azimuths and seasons that affect power generation.

After running the calculations, check the results not only for annual power generation but also broken down by month, by time of day, and by loss category. Because the influence of distant terrain often concentrates in winter and during mornings and evenings, looking only at the annual total can miss important changes. Comparing cases with and without distant terrain makes it easier to explain how much terrain conditions affect power generation.

Ultimately, it is important to translate the simulation results into a form that can be used for design decisions. Clarify whether improvements can be achieved by changing the layout, whether adjusting the site grading height is effective, or whether the conditions should be accepted as inherent land constraints. When explaining to stakeholders, convey not only the numbers but also, in words, which directional terrain affects outcomes in which seasons or times of day and how, as this makes the information easier to understand.

Consideration of distant terrain is an important step in improving the reliability of power generation forecasts. By using the PVSyst manual and proceeding through a continuous workflow—site verification, horizon data creation, data input, comparison, and explanation—you can achieve simulations that more closely reflect real-world conditions. At sites with complex topography, on-site surveying and the use of high-precision location information are particularly key to improving design accuracy and explanatory capability.