To set the departure time for a weather-route forecast, you must enter the time in hours, minutes and seconds. See the screenshot:
I don't imagine that the departure time is necessarily so precise. I suggest that the timetable be given in hours and minutes. And this, even for short distance coastal navigations.
In the same way, the difference in duration between two isochrones, visible on the right in the image, is currently in hours, minutes and seconds. This level of precision seems unnecessary to me.
I propose to limit this data to hours and minutes.
For very long distance navigations, for example a transatlantic crossing, being satisfied with a duration of one hour between two isochrones would be good.
On the other hand, on short navigations, the possibility of choosing a gap of less than an hour is perfectly suited. I tried it and it is useful.
To set the departure time for a weather-route forecast, you must enter the time in hours, minutes and seconds. See the screenshot:
I don't imagine that the departure time is necessarily so precise. I suggest that the timetable be given in hours and minutes. And this, even for short distance coastal navigations.
In the same way, the difference in duration between two isochrones, visible on the right in the image, is currently in hours, minutes and seconds. This level of precision seems unnecessary to me. I propose to limit this data to hours and minutes.