You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From a Slack thread between Stacie and Rob Griffin:
SW: wind_energy_points.shp is based on the Wind Data Points input, and each point seems to have output data for fields Dens_W/m2 and Harv_MWhr, even though density_W_per_m2.tif and harvested_energy_MWhr_per_yr.tif have values of NoData at these locations. Why is this?
RG: It is ok that Dens_W/m2 returns values even for locations that are masked out based on depth/distance constraints, as this is a metric that is based on wind resource independent of any interaction with turbines. Returning values for harvested energy (or any valuation outputs) for those same locations does not make sense though. I suspect this would be straightforward to fix for the software team using distance/depth indicators.
Also, this point needs clarification in the User Guide, so it's easier to understand the relationship between the rasters and wind input, and where the wind point output gets its fields from. In case it's useful later, when I asked for clarification on the first point, Rob said this:
RG: The depth and distance constraints in the input fields control which areas are viable for placing turbines. All modeled results (points and rasters) should only be given for these areas, with the possible exception of Dens_W/m2 as this is a metric that is based on wind resource independent of any interaction with turbines. It should probably be an intermediate output (as a raster), as it is really just restating in different terms the wind resource input file.
Rob says that he has a lot of UG updated queued up, so let's make sure this is one of them.
The text was updated successfully, but these errors were encountered:
From a Slack thread between Stacie and Rob Griffin:
Also, this point needs clarification in the User Guide, so it's easier to understand the relationship between the rasters and wind input, and where the wind point output gets its fields from. In case it's useful later, when I asked for clarification on the first point, Rob said this:
Rob says that he has a lot of UG updated queued up, so let's make sure this is one of them.
The text was updated successfully, but these errors were encountered: