Closed veenstrajelmer closed 3 months ago
It seems that storm-induced extremes strongly affect the mean values in case of monthly maxima (tidalindicators), while for havengetallen we purely look at the culmnation hour (a proxy for spring/neap tide or anything in between). When we plot the high waters from culmination hour 0/6/all (spring/neap/mean tide), we clearly see that springtide (culmination hour 0) does not include the most extreme maxima. These are included in the yearly means derived within the tidalindicators module. This could explain these different values.
# plot spring/mean/neap values based on culmination hours, this clearly shows that not all highest extremes are in the spring-tide class, so might explain why these methods return different results.
fig,ax = plt.subplots()
data_pd_HW_mean["values"].plot(ax=ax, linewidth=1)
data_pd_HW_spring["values"].plot(ax=ax)
data_pd_HW_neap["values"].plot(ax=ax)
ax.set_xlim(pd.Timestamp("2010"), pd.Timestamp("2011"))
ax.set_ylim(0.2,2.2)
Gives
Since this is now explained, this issue will be closed.
The spring/mean/neap values from havengetallen should in theory compare well to the spring/mean/neap values from tidalindicators. This seems not to be the case.
the different methods in havengetallen/tidalindicators result in significant (~40 cm) differences in mean high water values for spring and neap tide: