In hatyan there is a X-factor of 0.53 for the M2 component (and other values for several other components), to account for damping of the nodal cycle by the shallow shelf. This is applied for stations along the Dutch coast. Research shows that this X-factor is actually spatially varying:
It could be considered to apply a spatially varying X-factor instead. This should already be possible with hatyan, so it is possible to investigate the impact of this improvement. However, it will be cumbersome and prone to errors to save this metadata in component files and therefore it might be inconvenient to apply it in the tidal prediction practice.
Original slides by FZ:
LowFrequencyTidalModulations_20240415.pdf
FZ: Voor het testen van afwijkende M2 Xfactoren zijn de volgende locaties interessant:
- M2 Xfactor hoger dan 0.53:
- Cadzand
- Vlakte van de Raan
- Vlissingen
- M2 Xfactor lager dan 0.53:
- Harlingen
- Hoek van Holland
- IJmuiden
- Ook Platform K13 kan interessant zijn. Daar wordt dacht ik geen M2 Xfactor toegepast, terwijl daar wel enige demping van de knoopcyclus plaatsvindt.
- Voor andere getijcomponenten zijn andere locaties geschikt.
Also:
- The S2 component is an exception since it is linked to the M2 component
In hatyan there is a X-factor of 0.53 for the M2 component (and other values for several other components), to account for damping of the nodal cycle by the shallow shelf. This is applied for stations along the Dutch coast. Research shows that this X-factor is actually spatially varying:
It could be considered to apply a spatially varying X-factor instead. This should already be possible with hatyan, so it is possible to investigate the impact of this improvement. However, it will be cumbersome and prone to errors to save this metadata in component files and therefore it might be inconvenient to apply it in the tidal prediction practice.
Original slides by FZ:
LowFrequencyTidalModulations_20240415.pdf
FZ: Voor het testen van afwijkende M2 Xfactoren zijn de volgende locaties interessant:
Also: