-
Notifications
You must be signed in to change notification settings - Fork 23
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
Add wind power density to the OEO #1997
Comments
This looks like a good definition. |
So, we are talking about wind (i.e. moving air) and not wind power plants. Is this correct for the task definition use case @tpelser? |
In this case, yes. The theoretical wind potential can include the wind power density of an area. In the technical potential there is a similar, but different term called the "capacity density" which refers to how many megawatts of wind power are installed in a square kilometer. |
It may also be useful to provide the unit that the WPD is supposed to be in. I assume it would be W/m²? At least this is what I found searching online. The formula I used for the definition is also the generic one I searched online. But since this issue wants to use WPD as its own term I would assume we should stick to the generic use of the formula - even if in the task there may be something more specialized in use? |
Hi, yes I agree and the unit is correct (W/m^2). The formula is also correct for wind power density. Capacity density is something entirely different with a similar sounding name. |
Description of the issue
Wind power density
(WPD) is a term used in the definitions of the tasks module (see #1891). As decided in the dev meeting there should be a separate issue to discuss the definition.It was also discussed if this should be the subclass of
areal power density
.Ideas of solution
I propose this definition:
wind power density (WPD)
is a quantity vale of the power wind has in a specific area. It is calculated as 0.5 * air density * (wind speed to the power of 3)Workflow checklist
I am aware that
The text was updated successfully, but these errors were encountered: