inp_project
This file defines the inputs on a line by line basis.
It is parsed one single time, when the configure step begins.
For each line, values are separated by whitespaces.
Tip
Lines beginning with a # character are not processed (and won't raise error).
The first value indicates what type of data is being defined on this line.
The type of data should be either one of:
- georef
- terrain
- roughness
- terrain_uniform
-
roughness_uniform
-
mast
- wt
- point
- meso
- wrg
- interest
Various templates of "inp_project" files can be found in src/templates/cases/* folders.
georef
Allows defining the project inputs georeference.
If no reference is specified, default georeference will defined as "Fictive". This equates to a georef Fictive entry in the file.
The use of a "Fictive" georeference implies that:
- Each data entry is to be specified in a cartesian system
- Some features are disactivated, including:
- Reference wind data generation with ZephyWDG
- Map and satellite views
- Kmz exports
To define the project's georeference, a valid EPSG number integer entry can be used. For instance, georef 32643 entry would define the "WGS84|UTM Z43N" georeference.
Georeference codename can also be preferred: georef WGS84|UTM Z43N entry can also be used instead.
The list of valid EPSG numbers and its corresponding codenames can be found in file: georef.
Eventually, a last possible couple of entries are "4326" and "WGS84|Geographic". Both allows to use inputs defined with decimal latitudes and longitudes.
When the use of geographical data is activated, a cartesian georeference is automatically evaluated and all the project's data and results are using this latest.
To be noticed
Once project's center coordinates are evaluated, the data are transferred into the project virtual reference, which origin is defined at the project's center.
terrain
Allows defining some user-defined orography data for the project.
The path (relative from project's folder) to the file should be specified (and the file should of course exist).
Allowed file formats are:
- .map (Wasp map format)
- .xyz (text file providing the list of orography data points)
- .npz (numpy binary providing the list of orography data points)
For instance, if "orodata.map" is directly included in the project's folder, terrain orodata.map entry should be used.
To be noticed
Defining a terrain is not mandatory. When default value is found (which equates to a terrain none entry in the file), either one of the ZephyData database can be used (when the option available and activated), or the default terrain will be considered as a 100m elevation flat terrain.
It is not possible to define more than one user-defined terrain data input (and these should be merged externally).
terrain_uniform
A terrain_uniform entry would force a 100m flat terrain, whatever the possible activation of the use of ZephyData.
roughness
Allows defining some user-defined roughness data for the project.
The path (relative from project's folder) to the file should be specified (and the file should of course exist).
Allowed file formats are:
- .map (Wasp map format)
- .xyr (text file providing the list of roughness length data points)
- .npz (numpy binary providing the list of roughness length data points)
For instance, if "roughdata.map" is directly included in the project's folder, roughness roughdata.map entry should be used.
To be noticed
Defining a roughness is not mandatory. When default value is found (which equates to a roughness none entry in the file), either one of the ZephyData database can be used (when the option available and activated), or the default roughness will be considered as a 0.03m homogenous roughness length.
It is not possible to define more than one user-defined roughness data input (and these should be merged externally).
roughness_uniform
A roughness_uniform 0.05 entry would force an homogeneous roughness length of 0.05m for the terrain, whatever the possible activation of the use of ZephyData.
To be noticed
No roughness length filtering process to detect non-valid roughness length data (yet): negative and 0 values will lead to crashes.
Keep valid roughness data: 0.00001 m < roughness < 2.5 m
mast
Met masts can be defined using:
(Xmast, Ymast) coordinates should be specified in the project's input georeference.
Each mast label is optional, a default one being generated when no last entry is found in the line.
wt
Wind Turbines can be defined using:
(Xwt, Ywt) coordinates should be specified in the project's input georeference.
Each wind turbine label is optional, a default one being generated when no penultimate entry is found in the line.
Each wind turbine group is optional, a default one being generated when no last entry is found in the line.
The use of groups can facilitate the wind farm turbine definition when multiple turbine models are to be used.
Also, the use of groups can be usefull to reduce the size of a single wind resource grid that would cover the whole farm.
To be noticed
mast and wt entities are generating a row of 191 points for each meter, from 10 to 200 meters, to be able to extract and show the wind profile results at each location.
point
Result Points can be defined using:
(Xpoint, Ypoint) coordinates should be specified in the project's input georeference.
Hpoint defines the point's height in meters.
The use of points can facilitate the definition of reference, and also allow the use of references defined at intermediate heights (and not for each meter as for the masts).
Validity condition for Hpoint: 10 m < Hpoint
meso
Mesoscale Points can be defined using:
(Xmeso, Ymeso) coordinates should be specified in the project's input georeference.
Hmeso defines the mesoscale point's height in meters.
Validity condition for Hmeso: 50. ≤ Hmeso ≤ 2000.
For these mesoscale points, the results are evaluated by averaging the results over a circular area centered on the point.
The circular area diameter is defined by the MesoReso entry, in meters.
Validity condition for Hmeso: 1000. ≤ MesoReso ≤ 10000.
The resolution of the result points used to average the results is given by the PointReso entry, in meters.
Validity condition for Hmeso: 25. ≤ PointReso ≤ 250.
wrg
Wind Resource Grids can be defined using:
(X1, X2, Y1, Y2) coordinates, defining the wind resource grid corners, should be specified in the project's input georeference.
Hwrg defines the wind resource grid's height in meters.
Validity condition for Hwrg: 10. ≤ Hwrg ≤ 200.
RESOwrg defines the wind resource grid's resolution in meters.
Validity condition for RESOwrg: 5. ≤ RESOwrg ≤ 500.
interest
Allows defining some user-defined interest area for the project, for which "unstructured wind resource grid" will be produced.
The path (relative from project's folder) to the file should be specified (and the file should of course exist).
Allowed file formats are:
- .geojson
- .shp
For instance, if "area.geojson" is directly included in the project's folder, interest area.geojson entry should be used.