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
In order to determine which values for the thresholds would be most realistic for precipitation and wind speed, histograms were made of the API data for the seven year period that has been used as the MESA output. The histograms for precipitation and wind speed can be seen below.
Precipitation
Wind Speed
As can be seen, there is a nice distribution of values for the wind speed histogram, indicating that it is a good metric and that the API data being returned is most likely representative of reality. In order to cut about 50% of data, a windspeed threshold of 10 km/hr would suffice. The same cannot be said for precipitation however, as it seems that the majority of values are clustered at 0.0 mm of precipitation. This is most likely due to the API call not having enough data for the time period, and instead of just putting null where they did not have data, they put 0 instead. This issue can be fixed by finding a better source of data and just switching where the API call is made to.
The text was updated successfully, but these errors were encountered:
In order to determine which values for the thresholds would be most realistic for precipitation and wind speed, histograms were made of the API data for the seven year period that has been used as the MESA output. The histograms for precipitation and wind speed can be seen below.
Precipitation
Wind Speed
As can be seen, there is a nice distribution of values for the wind speed histogram, indicating that it is a good metric and that the API data being returned is most likely representative of reality. In order to cut about 50% of data, a windspeed threshold of 10 km/hr would suffice. The same cannot be said for precipitation however, as it seems that the majority of values are clustered at 0.0 mm of precipitation. This is most likely due to the API call not having enough data for the time period, and instead of just putting null where they did not have data, they put 0 instead. This issue can be fixed by finding a better source of data and just switching where the API call is made to.
The text was updated successfully, but these errors were encountered: