Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFE : Why hours, minutes and seconds. Hours and minutes are enough. #159

Open
Gilletarom opened this issue Nov 10, 2023 · 0 comments
Open

Comments

@Gilletarom
Copy link

Gilletarom commented 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:

2023-11-10 16_31_55-OpenCPN 5 8 4-0

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.
@Gilletarom 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant