Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wind energy returns harvested energy values for masked out points #1699

Open
newtpatrol opened this issue Nov 25, 2024 · 0 comments
Open

Wind energy returns harvested energy values for masked out points #1699

newtpatrol opened this issue Nov 25, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@newtpatrol
Copy link
Contributor

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.

@davemfish davemfish added the bug Something isn't working label Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants