Open 3mily8rown opened 9 months ago
@joelll-u could you work on this because I think Emily is right, I think storing the wind/tide information as a magnitude and direction would make more sense as we end up having to resolve it everywhere we use it anyway
I've been unsure what is best now because I think we use both the components and the resultant in the backend so maybe we just need a utility function on either end that resolves a generic 2d force? But I guess it would still be useful, if the front end only wants the magnitude and the direction
In WindFiltering, the front-end visualisations, and the route planning all separately are resolving wind data from the wind service - so we maybe we should do it just in the wind service to reduce duplication?