You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Gilletarom
changed the title
RFE : Pourquoi heures, minutes et secondes. Heures et minutes suffisent.
RFE : Why hours, minutes and seconds. Hours and minutes are enough.
Nov 10, 2023
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.
The text was updated successfully, but these errors were encountered: