Solargis API type

Availability of PV, solar and meteorological data

Technical features

Data Delivery Web Service

YES

YES

YES

YES

NO

synchronous over HTTPS

XML

XML

LTA Web Service (LTA API)

NO

NO

NO

NO

YES

synchronous over HTTPS

XML

XML

historical

satellite model

• Start: the beginning of the archive

• End: the last completed calendar month (MONTH-1)

Data for any location enters this stage upon completion of the calendar month. The reanalysis of the previous month takes effect on the 3rd day of each calendar month. Historical data can be regarded as final or of archive quality. The oldest solar data stored by Solargis dates back to 1994.

operational

satellite model

• Start: the beginning of the current calendar month

• End: the last completed calendar day (DAY-1)

Operational stage of the solar data is created as soon as the calendar day is completed at the location.

real-time

satellite model

• Start: the beginning of the current calendar day (DAY+0)

• End: the current time

The real-time data stage is actually ending shortly before the current time due to processing delays of the satellite model.

nowcasting

satellite model

• Start: the current time

• End: 4 hours after the current time

The beginning of this stage at the current time is approximate. The nowcasting data is generated from the series of satellite scenes. Solargis predicts solar data parameters by utilizing CMVs (Cloud Motion Vectors). After approximately 3-4 hours, the satellite nowcasting model output begins to blend with the numerical weather prediction data.

numerical weather prediction (NWP)

post-processed outputs of NWP models

• Start: 4 hours after the current time

• End: DAY+14 (15 days in a row including the current day)

The NWP based solar data is asembled from multiple NWP data sources: IFS forecast model (ECMWF), ICON forecast model (DWD), GFS forecast model (NOAA), HRRR model (NOAA). Find more information about the forecasting here.

satellite data region

historical data start

description of satellites

when the local DAY-1 is available

real-time and nowcasting availability

GOES WEST

1999-01-01

2019+: GOES-S, 10-minute time step

2018 - 1999:  GOES-W, 30-minute time step

09:00 UTC

Satellite data availability delay is 2-12 minutes and

it increases from south to north.

Processing frequency is every 10 minutes and it takes another 5-15 minutes.

GOES EAST

1999-01-01

2019+: GOES-R, 10-minute time step

2018+: GOES-R, 15-minute time step

2017 - 1999:  GOES-E, 30-minute time step

05:00 UTC

same as the GOES WEST region

GOES EAST PATAGONIA

2018-01-01

2019+: GOES-R, 10-minute time step

2018+: GOES-R, 15-minute time step

05:00 UTC

same as the GOES WEST region

METEOSAT PRIME SCANDINAVIA between

60°and 65° latitude

2005-01-01

2005+: MSG 15-minute time step

00:30 UTC

not yet

METEOSAT PRIME

1994-01-01

2005+: MSG 15-minute time step

2004 - 1994:  MFG, 30-minute time step

00:30 UTC

Satellite data availability delay is 2-16 minutes and

it increases from north to south.

Processing frequency is every 15 minutes and it takes another 5-15 minutes.

METEOSAT IODC

1999-01-01

2017+: MSG 15-minute time step

2016 - 1999:  MFG, 30-minute time step

19:

00 UTC 

same as

the METEOSAT PRIME region

IODC-HIMAWARI

1999-01-01

2017+: HIMAWARI 10-minute time step

2016 - 1999:  MFG, 30-minute time step

16:

00 UTC

same as

the HIMAWARI region

HIMAWARI

2006-07-01

2016+: HIMAWARI 10-minute time step

2015 - 2006:  MTSAT, 30-minute time step

16:00 UTC

Satellite data availability delay is 5-15 minutes and

it increases from south to north.

Processing frequency is every 10 minutes and it takes another 5-15 minutes.

ERA5 reanalysis of the global climate (ECMWF)

• Start: the beginning of the archive

• End: DAY-11

The TEMP data parameter is extracted from the ERA5-Land reanalysis dataset (ECMWF). Important note: ECMWF provider can have delays which can affect the availability of the ERA5-Land dataset.

IFS forecast model (ECMWF)

• Start: DAY-10

• End: DAY+3

GFS forecast model (NOAA)

• Start: DAY+4

• End: DAY+14

dataDeliveryRequest

http://solargis.info/schema/ws-data.xsd

The root element of the XML request is the <dataDeliveryRequest> with required attributes 'dateFrom' and 'dateTo' for setting desired data period in the response. Accepted is a date string in the form of  ''YYYY-mm-dd" e.g., "2017-09-30". It is assumed UTC (GMT+00) time zone for both dates unless otherwise specified by the <timeZone> element of the <processing>.

required one <site> , required one <processing>

start of the data period, ''YYYY-mm-dd"

end of the data period, ''YYYY-mm-dd"

processing

http://solargis.info/schema/data-request.xsd

Complex element with instructions about how response should be generated.

optional one <timeZone>, optional one <timestampType>

required, time frequency in the response. One of

MONTHLY, DAILY, HOURLY, MIN_30, MIN_15, MIN_10, MIN_5

required, text value, output data parameters separated by white space. Example: key="GHI GTI TEMP WS PVOUT". See below table for all supported parameters.

optional, boolean, if 'true', the distant horizon taken from SRTM data is considered, default is 'false' (no horizon obstructions at all), Note: a user can also apply custom horizon data by providing <horizon> element within the <site> element

GHI

Global Horizontal Irradiation [kWh/m2, Wh/m2, W/m2]. Regarding units see below note.

GHI_C

Clear-sky Global Horizontal Irradiation [kWh/m2, Wh/m2, W/m2]

GHI_UNC_HIGH

GHI high estimate (10 %

probability of exceedance) [kWh/m2, Wh/m2, W/m2]

GHI_UNC_LOW

GHI low estimate (90 %

probability of exceedance) [kWh/m2, Wh/m2, W/m2]

DNI

Direct Normal Irradiation [kWh/m2, Wh/m2, W/m2]

DNI_C

Clear-sky Direct Normal Irradiation [kWh/m2, Wh/m2, W/m2]

DIF

Diffuse Horizontal Irradiation [kWh/m2, Wh/m2, W/m2]

GTI

Global Tilted Irradiation [kWh/m2, Wh/m2, W/m2]

GTI_UNC_HIGH

GTI high estimate (10 %

probability of exceedance) [kWh/m2, Wh/m2, W/m2]

GTI_UNC_LOW

GTI low estimate (90 %

probability of exceedance) [kWh/m2, Wh/m2, W/m2]

GTI_C

Global tilted clear-sky irradiance [W/m2]

CI_FLAG

Cloud identification quality flag [categories], this parameter is

represented as 'flagR' in the response

FLAG_R

alias for CI_FLAG

KTM

Deprecated alias of KC. Can be discontinued in future versions.

KC

Clear-sky index [unitless]

KT

clearness index, values range (0, 1.1), during the night -9

PAR

Photo-synthetically Active Irradiation [kWh/m2, Wh/m2, W/m2]

SE

Sun Altitude (Elevation) Angle [deg.]

SA

Sun Azimuth Angle [deg.]

TEMP

Air Temperature at 2m [deg. C]

TD

Dew Point Temperature [deg. C]

WBT

Wet Bulb Temperature [deg. C]

AP

Atmospheric Pressure [hPa]

RH

Relative Humidity [%]

WS

Wind Speed [m/s]

WD

Wind Direction [deg.]

PREC

Precipitation Rate [kg/m2]

PWAT

Precipitable Water [kg/m2]

PVOUT

Photovoltaic Output [kW, kWh]. Regarding units see below note.

PVOUT_UNC_HIGH

PVOUT high estimate (10 %

probability of exceedance) [kW, kWh]

PVOUT_UNC_LOW

PVOUT low estimate (90 %

probability of exceedance) [kW, kWh]

SDWE

Water equivalent of accumulated snow depth [kg/m2]

SWE

Deprecated alias of SDWE. Can be discontinued in future versions. SDWE will be returned in a response.

TMOD

Module temperature [deg. C]. This parameter needs a PV system defined in the request

, at least in a mimimal setup like:
<pv:system installedPower="1"><pv:module type="CSI"/><pv:inverter/><pv:losses/></pv:system>

WG

Wind Gust [m/s]

WS100

Wind speed at 100 m [m/s]

WD100

Wind direction at 100 m [deg.]

SFWE

Water equivalent of fresh snowfall rate [kg/m2/hour] - source ERA5 , the latest data available is approx. one month backward (no data for very recent or forecast period)

INC

Incidence angle of direct irradiance [deg.], this parameter needs GTI or PVOUT in the request

TILT

Tilt of inclined surface [deg.], this parameter needs GTI or PVOUT in the request

ASPECT

Aspect of inclined surface [deg.], this parameter needs GTI or PVOUT in the request

timeZone

http://solargis.info/schema/data-request.xsd

The element controls the time zone in the response (how all timestamps should be shifted from the UTC). Hourly and half-hourly precision is supported.

required, string value in the pattern "GMT[+-][ zero-padded hours ][:30]", default value is GMT+00 (UTC), Examples: GMT-04, GMT+05:30, GMT-02:30

Full request example for the GHI parameter in the India Standard Time (IST) zone:

<ws:dataDeliveryRequest dateFrom='2024-04-19' dateTo='2024-04-19' xmlns='http://geomodel.eu/schema/data/request' xmlns:ws='http://geomodel.eu/schema/ws/data' xmlns:geo='http://geomodel.eu/schema/common/geo' xmlns:pv='http://geomodel.eu/schema/common/pv' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
    <site id='Delhi' lat='28.758009' lng='77.296243' name='Delhi' />
    <processing summarization='HOURLY' key='GHI' terrainShading='true'>
        <timeZone>GMT+05:30</timeZone>
        </processing>
</ws:dataDeliveryRequest>

timestampType

http://solargis.info/schema/data-request.xsd

Simple element provides how aggregated time intervals in the response should be labeled.

Valid for [sub]hourly summarization. Intervals can be time-stamped at the center (default) or at start or at end. In other words, users can choose the left (START) or the right (END) edge of the time interval for its label (besides the center).

required, one of START, CENTER, END

site

http://solargis.info/schema/data-request.xsd

Complex element representing site location, optionally with a PV technology installed

optional one <geometry>, optional one <system>, optional one <terrain>, optional one <horizon>

required, site identification, cannot start with number, cannot have white space. It is recommended to use different site id for unique combinations of latitude and longitude. Referring to the specific site id facilitates the troubleshooting of issues in the API. Do not reuse the same site id for multiple locations.

required, site latitude in decimal degrees e.g, 48.61259

required, site longitude in decimal degrees e.g, 20.827079

optional, more descriptive name of the site (e.g., address), default is empty string

terrain

http://solargis.info/schema/common-geo.xsd

Ground terrain characterized by elevation, terrain slope and terrain azimuth. Terrain properties affect the self shading of a fixed angle PV array (note, that 'tilt' and 'row spacing' attributes of PV modules on the pictures below are identical - what is changing is the terrain slope and how it affects the self shading).

none

optional, meters above the mean see level. If missing, the value will be taken from SRTM terrain database

optional, orientation of tilted terrain in degrees, 0 for North, 180 for South, clockwise, default is 180, has no effect for the flat terrain (tilt=0)

optional, slope tilt of the terrain in degrees, 0 for flat ground, 90 for vertical surface, default is 0 (flat)

horizon

http://solargis.info/schema/common-geo.xsd

User can provide custom skyline for expressing distant or close obstruction features (hills, trees, buildings, poles, etc.)

String of this form: space-delimited list of float number pairs [azimuth in degrees:0-360]:[horizon height in degrees:0-90], Example: "<geo:horizon>0:3.6 123:5.6 359:6</geo:horizon>"

geometry

http://solargis.info/schema/common-pv.xsd

Parametrization of PV system mounting type used for calculating GTI and PVOUT. If this element is missing and GTI/PVOUT is requested, flat-lying PV panels are considered (GTI=GHI). Examples:

<pv:geometry xsi:type="pv:GeometryFixedOneAngle" azimuth="180" tilt="25"/>

<pv:geometry xsi:type="pv:GeometryOneAxisHorizontalNS" rotationLimitEast="-90" rotationLimitWest="90" backTracking="true" azimuth="180"/>

<pv:geometry xsi:type="pv:GeometryOneAxisInclinedNS" axisTilt="30" rotationLimitEast="-90" rotationLimitWest="90" backTracking="true" azimuth="180"/>

<pv:geometry xsi:type="pv:GeometryOneAxisVertical" tilt="25" rotationLimitEast="-180" rotationLimitWest="180" backTracking="true"/>

<pv:geometry xsi:type="pv:GeometryTwoAxisAstronomical" rotationLimitEast="-180" rotationLimitWest="180" tiltLimitMin="10" tiltLimitMax="60" backTracking="true"/>

none

required, type of the mounting geometry. Use one from GeometryFixedOneAngle, GeometryOneAxisHorizontalNS, GeometryOneAxisInclinedNS, GeometryOneAxisVertical, GeometryTwoAxisAstronomical, see table below for pictures.

the value in degrees of a true geographical azimuth (0: north, 90: east, 180: south, 270: west, 360: north --> a compass value) . In the case of 'GeometryFixedOneAngle' the azimuth attribute is required.

In the case of two tracker types (GeometryOneAxisHorizontalNS, GeometryOneAxisInclinedNS) the value is the compass value at which the southern end of the tracker axis is oriented. Regardless of the Earth's hemisphere. With trackers, the value is limited to the range from 135 deg. to 225 deg. inclusive, so the deviation from the north-south line is not bigger than 45 degrees. With trackers, the attribute is optional and it defaults to 180 deg. (which means the southern end of the axis faces to geographical south, so the tracker field is aligned with the north-south line which is the optimal solution for most cases).

tilt of panel surface in degrees range (0, 90), 0=horizontal, 90=vertical surface, required for 'GeometryFixedOneAngle' and 'GeometryOneAxisVertical' types

optional, default is 30 deg., allowed range is (0, 90). Tilt of rotating inclined axis in degrees, 0 = horizontal, 90 = vertical axis, only applicable for 'GeometryOneAxisInclinedNS',

WARNING: if this attribute is missing, the value defaults to 30 degree.

optional, for trackers only

default values / allowed ranges:

• default is -180 deg, allowed range: -180, 180. Applies for vertical axis of GeometryTwoAxisAstronomical and

• GeometryOneAxisVertical trackers.  Rotation limits are in this case defined relative to 0 deg. (initial tracker position regardless of the hemisphere), default range from -180 to 180 deg (e.g., -90 deg. for east and +90 deg. for west)

• default is -90, allowed range: -90, 90, Applies for the GeometryOneAxisHorizontalNS and GeometryOneAxisInclinedNS. Rotation limits are in this case defined as tilt of tracker table relative to its central position, both limits are typically symmetric e.g., rotationLimitEast=-50, rotationLimitWest=50

The general rule is: negative values are used for the east side, positive for the west side, the same rule applies for both Earth hemispheres).

The value of rotationLimitEast must be smaller or equal than

the rotationLimitWest.

optional, for trackers only

default values / allowed ranges:

• default is 180 deg, allowed range: -180, 180. Applies for vertical axis of GeometryTwoAxisAstronomical and

• GeometryOneAxisVertical trackers.  Rotation limits are in this case defined relative to 0 deg. (initial tracker position regardless of the hemisphere), default range from -180 to 180 deg (e.g., -90 deg. for east and +90 deg. for west)

• default is 90, allowed range: -90, 90, Applies for the GeometryOneAxisHorizontalNS and GeometryOneAxisInclinedNS. Rotation limits are in this case defined as tilt of tracker table relative to its central position, both limits are typically symmetric e.g., rotationLimitEast=-50, rotationLimitWest=50

The general rule is: negative values are used for the east side, positive for the west side, the same rule applies for both Earth hemispheres).

The value of rotationLimitEast must be smaller or equal than

the rotationLimitWest.

optional, for trackers only

Default is 0 deg, allowed range: 0, 90. Used with the horizontal axis of

GeometryTwoAxisAstronomical tracker. Limit is defined relative to the horizontal position of the tracking surface (0 deg.). Example: if set as tiltLimitMin="0"  and tiltLimitMax="60" - the tracker follows the sun elevation in the range from horizontal position to 60 degree of tilt.

The value of tiltLimitMin must be smaller or equal than the tiltLimitMax.

optional, for trackers only

Default is 90 deg, allowed range: 0, 90. Used with the horizontal axis of

GeometryTwoAxisAstronomical tracker. Limit is defined relative to the horizontal position of the tracking surface (0 deg.). Example: if set as tiltLimitMin="0"  and tiltLimitMax="60" - the tracker follows the sun elevation in the range from horizontal position to 60 degree of tilt.

The value of tiltLimitMin must be smaller or equal than the tiltLimitMax.

optional boolean value, default is 'false' - tracker moves freely regardless of the neighbors, value is 'true' - tracker moves in the way that it avoids shading from neighboring tracker constructions.

• fixed surface described by azimuth and tilt

• self-shading simulation supported

• single vertical tracker axis

• tilted fixed surface

• rotation limits

• back-tracking

• relative column spacing

• self-shading simulation not implemented

• single inclined tracker axis

• tilted surface

• rotation limits

• azimuth of the axis

• back-tracking

• relative column spacing

• self-shading simulation supported

• single horizontal tracker axis

• rotation limits

• azimuth of the axis

• back-tracking

• relative column spacing

• self-shading simulation supported
  
  

• two tracker axes

• rotation limits for both axes

• back-tracking

• relative column spacing

• self-shading simulation not implemented

system

http://solargis.info/schema/common-pv.xsd

Parametrization of the PV system. Required for simulating PVOUT parameter.

required one <module> element, required one <inverter> element, required one <losses> element, optional one <topology> element,

required float value (greater than zero). Total installed DC power of the PV system in kilowatts-peak (kWp). The total PV system rating consists of a summation of the panel ratings measured in STC.

optional, use one from FREE_STANDING (default), ROOF_MOUNTED, BUILDING_INTEGRATED. This property of the PV system helps to estimate how modules are cooled by air. For sloped roof with PV modules on rails tilted at the same angle as the roof choose 'ROOF_MOUNTED' value. For PV modules incorporated into building facade choose 'BUILDING_INTEGRATED' value. This option is considered as the worst ventilated. As the best ventilated option is considered 'FREE_STANDING' installation. This typically means stand-alone installation on tilted racks anchored into the ground. Also choose this option if a PV system is installed on a flat roof.

optional string formatted as "yyyy-mm-dd" (example 2015-01-01). Start-up date of the PV system (unpacking of modules). This parameter is used for calculation of degradation of modules caused by aging. If omitted, the degradation is not taken into account.

optional, default is 'false'. The parameter affects PV power calculation for 'GeometryFixedOneAngle' geometry, then 'GeometryOneAxisInclinedNS' and 'GeometryOneAxisHorizontalNS' trackers if backTracking="false". When 'selfShading' is switched on, the simulated PV power is typically lower comparing to standalone PV construction not affected by shading from its neighbors. With trackers, always switch off 'backTracking' attribute, because the back tracking avoids self-shading.

module

http://solargis.info/schema/common-pv.xsd

Parametrization of the PV system modules. Required for simulating PVOUT parameter. All modules in one PV system are considered of the same type.

optional one <degradation> element, optional one

<degradationFirstYear> element, optional one <surfaceReflectance> element,

 optional one

<nominalOperatingCellTemp> element, optional one

<PmaxCoeff> element

required. Enumerated codes for materials used in PV modules. Use 'CSI' for crystalline silicon, 'ASI' for amorphous silicon, 'CDTE' for cadmium telluride, 'CIS' for copper indium selenide. For the estimate of module's surface reflectance we use an approach described here.

degradation

http://solargis.info/schema/common-pv.xsd

Estimated annual degradation [%] of rated output power of PV modules. This element is only considered if "dateStartup" attribute of PV system is present. If the element is missing, degradation defaults to 0.5%/year.

required, float number in the range (0, 100), %

degradationFirstYear

http://solargis.info/schema/common-pv.xsd

Estimated annual degradation [%] of rated output power of PV modules in the first year of operation. If the element is missing, degradation defaults to 0.8%/year.

required, float number in the range (0, 100), %

surfaceReflectance

http://solargis.info/schema/common-pv.xsd

Empirical dimensionless ratio. Typical value 0.12.

required, float number

nominalOperatingCellTemp

http://solargis.info/schema/common-pv.xsd

Normal operating cell temperature (NOCT). Float value of the temperature in degrees Celsius of a free standing PV module exposed to irradiance of 800 W/m2 in the ambient air temperature of 20°C and wind speed of 1 m/s. The value is given by manufacturer and for ventilated free-standing PV systems only. If the element is missing, the NOCT value defaults to (based on technology):

CSI=46°C
ASI=44°C
CDTE=45°C
CIS=47°C

required, float number in degrees Celsius

PmaxCoeff

http://solargis.info/schema/common-pv.xsd

Negative percent float value representing the change of PV panel output power for temperatures other than 25°C (decrease of output power with raising temperature). This property is given at the STC by manufacturer. If the element is missing, the PmaxCoeff value defaults to (based on technology):

CSI=-0.438%/°C
ASI=-0.18%/°C
CDTE=-0.297%/°C
CIS=-0.36%/°C

required, float number, percent per degree Celsius (%/°C)

inverter

http://solargis.info/schema/common-pv.xsd

Parametrization of the PV system inverter. Required for simulating PVOUT parameter. All inverters in one PV system are considered of the same type.

optional one <efficiency> element, optional one <limitationACPower> element

efficiency

http://solargis.info/schema/common-pv.xsd

Efficiency of the inverter. If the element is missing, the efficiency is given as a constant value of 97.5%.

required, concrete type of how efficiency of the inverter should be modeled. Use one from EfficiencyConstant, EfficiencyCurve

required, based on type:

EfficiencyConstant:

float number, [%]. Value of inverter's efficency known as Euro or CEC (California Energy Commission) efficiency. This value is a calculated weighted efficiency given by manufacturer. It gives a simplified picture about an inverter's, in fact non-linear, performance. Valid range of this value is typically in the range 70%-100%. For better results, it is recommended to provide inverter's efficiency curve.

EfficiencyCurve:

text value, pairs of kW:percent. Efficiency of inverter is of non-linear nature, so it can be described as simplified curve defined as list of data points. Data point on the curve is defined by coordinates, where the x coordinate is absolute float value of input power in kilowatts (kW) and y coordinate is percent float value of the corresponding inverter's efficiency (%). This parameter accepts string value of this pattern: 'x1:y1 x2:y2 x3:y3 xn:yn'. A dot should be used as decimal separator, white space as a pair delimiter and colon as x:y delimiter. We assume the last point determines the maximum input power of the inverter (with corresponding efficiency). Example of an efficiency curve with the maximum input power of 3 kW is:

<pv:efficiency xsi:type="pv:EfficiencyCurve" dataPairs="0:85.6 0.5:96.2 1:98 1.5:97 2:97 2.5:96 3.0:96"/>

It is assumed, that one efficiency curve is valid for all inverters of the PV system (their powers are summed).

limitationACPower

http://solargis.info/schema/common-pv.xsd

Maximum power accepted by the inverter as AC output. Higher power values are 'clipped'. Clipping refers to the situation where the AC power output of an inverter is limited due to the peak rating of the inverter (the parameter value in kW), even though the additional power may still be available from the solar modules. If you have power factor (PF) and AC limit in kVA available, use this formula: PF * AC_limit_kVA = kW, to obtain the value of this parameter.

No default.

required, float number, kilowatts [kW]

losses

http://solargis.info/schema/common-pv.xsd

Estimation of various PV losses.

optional one <acLosses> element, optional one <dcLosses> element

dcLosses

http://solargis.info/schema/common-pv.xsd

Estimation of power losses on the DC side. If the element is missing, the specific DC losses are estimated by default as:

snowPolution: 2.5%

cables: 2.0%

mismatch: 1.0%

none

annual value of estimated dirt and snow losses [%]

Distribution of the 'snowPollution' attribute value into 12 monthly average values. Value of the parameter must consist of 12 percent float values delimited by white space. If this parameter is present, it takes precedence over 'snowPollution' attribute. Example:

<pv:dcLosses cables="0.2" mismatch="0.3" monthlySnowPollution="5 5.2 3 1 1 1 1 1 1 1 2 4"/>

annual value of estimated DC cabling losses [%]

annual value of estimated DC mismatch losses [%]

acLosses

http://solargis.info/schema/common-pv.xsd

Estimation of power losses on the AC side. If the element is missing, the specific AC losses are estimated by default as:

transformer: 1.0%

cables: 0.5%

none

annual value of estimated transformer losses [%]

annual value of estimated AC cabling losses [%]

topology

http://solargis.info/schema/common-pv.xsd

The element is for defining PV plant layout on the ground. The reason is to provide inputs for calculation of self-shading impact on PV power (e.g., how close to each other are PV constructions).

none

XML element type, required, concrete type of how topology should be modeled. Use one from TopologyRow (applies for the 'GeometryFixedOneAngle' geometry), TopologyColumn (use for all trackers). It is assumed trackers are spaced equally in both directions (rows and columns) creating a regular grid.

required, unitless ratio. The attribute specifies the ratio of distance between the neighboring PV table legs and PV table width. Direction of the distance depends on whether topology is specified as TopologyRow or TopologyColumn. See picture below how to calculate the value.

optional. This parameter estimates a magnitude of loss of PV power when modules are shaded or semi-shaded. The effect depends on wiring interconnections within a module. Shading influence ranges from 0% (no influence) to 100% (full influence) and it is classified into following categories (based on the influence value):

PROPORTIONAL = 20% (for a-Si, CdTe and CIS where the loss of generated electricity is proportional to the size of module area in shade)
UNPROPORTIONAL1 = 40% (for c-Si with proper layout optimization if the stings are connected independently in array)
UNPROPORTIONAL2 = 60% (for c-Si modules with intermediate layout optimization if strings are interconnected within the array)
UNPROPORTIONAL3 = 80% (for c-Si, modules are portrait-oriented with poor layout optimization, bottom cells in shade will shut the whole row of modules down)

When this attribute is missing, the self-shading influence is estimated to 5%.

siteId

lat

lng

geometry

azimuth

summarization

terrainShading

processingKeys

pvModuleTechnology

pvInstallationType

pvInstalledPower

pvDateStartup

pvTrackerBackTrack

pvTrackerRotMin

active

example1

48.61259

20.827079

OneAxisHorizontalNS

180

hourly

TRUE

GHI GTI DIF TEMP

PVOUT

CSI

FREE_STANDING

40020

20150701

TRUE

-45,45

TRUE

example2

0

7

48.61259

20.827079

hourly

TRUE

GHI DNI DIF TEMP WS WD

TRUE