Online we were able to find this extremely detailed infographic of tide prediction tides.
Using the analogue model again this builds data from the centre out. One common thing I have found is the inclusion of the moon and its stages. Though this is the prominent factor affecting the tide, I don’t feel it’s necessary to include. Depending on the stage of the cycle the tide will be unusually higher or lower. I feel the data that should be included in such interface is the resulting effect on the tide, rather than the factor causing the effect. Like a navigation interface does not need to inform the user the cause of an accident, it just needs to route them around it.
This similar one I find to be much easier. They both are in static infographic form, thus face the challenge of using visual hierarchy to make it readable. I felt that even in a dynamic interface we still include a large quantity of data, however, Emma believed that we cannot leave the control of reading the data up to the user. We need to tell them what they need to know, and allow them to reveal more data when they prompt to with progressive disclosure.
Willyweather uses a clock model as a countdown to the next high and low tide. This highlights one problem I knew I was going to have with project. This is a single dial with one specific piece of data being represented, adding to a series of dials and the interface will begin to feel like a dashboard and very confusing for its intended purpose.
The give some of the more important data about the tide predications, their accuracy. The predictions are almost never absolutely accurate to the observed results, as a result of the many natural and man-made factors. However, it’s possible to indicate this in the interface. It may not be possible to take weather data for example and more predictably predict the tide, however, we could give a visual(icon)indication that the tide could be higher than predicted to unusually heavy rainfall for instance.
Looking at this interface logging terrorist attacks gave me an idea for the high and low tides.
It maps the location, number of deaths and organisation responsible. Rather than terrorist data we could map where high and low tide is. High and low tide is only ever at one place;, it moves along the river like a wave. We could represent on a map using size and colour where high and low currently is. Then allow the user to manipulate the data to view how long till the next high tide and see predictions for the future for the location they want.
This graphic from he rowing code shows a similar idea, the point of high tide could be mapped to the darker point of the blue gradient and vice versa. The gradient, like the size of the circle would indicate how long till the next high or low tide and thus the speed of the flow too, as it slows down towards the beginning and end of rising and falling.