Implementing Routeplan Time & Tide in 0324 Beta

[PjotrC]

Thanks again for all flyspray comments and testing!

Attached is the corrected and enhanced version of Route Properties Dialog with extra planning capabilities.

Changes to the Forums - Post 612751">original proposal:

- correct secondary tide station support
- for active route properties, show route plan for future part of the route only, starting from current position (if "Now" given as starting time)
- "Now" is specified as ">" (greater sign) to make internationalization easier

As in the original, the LMT time mode means Local Mean Time, i.e. respective Solartime at each waypoint location. This is not directly useful for tide prediction, but gives some feeling as to the time-of-day. LMT is usually within 1-1.5 hrs of the local zone time. Useful for routes spanning multiple time zones.

The settable VMG values still stay in respective waypoints - I agree this is a leg property rather than waypoint, but there is no corresponding data structure to use. Not yet a reason for major changes.

This patch follows Forums - Post 655064">Automatic-IRJDSUNE9932123321222xxeww-Daily-IRJDSUNE9932123321222xxeww-Track, Layers and Fix AtoN Reports in 0324 Beta.

Enjoy,

Piotr

PS. Included are two minor aside modifications

- when appending waypoints to a route, the Measure Tool is activated automatically to show bearing and distance (useful for e.g. planning daily hops in open water...)
- waypoint coordinates in RouteProp are given just with 1 decimal position for minutes

[antxon]

Beautiful job, Piotr. Thanks for accepting feedback. On the other hand, I understand your objections to some suggestions. Not so skilled to compile the source code (too busy with professional sailing) I'll have to wait to implementation in a next release, so unfortunately won't be able to test it in next Atlantic crossing departing in a few days, but anyway just can thank you for your hard work for the profit of all of us.

[PjotrC]

antxon...

Unfortunately, the process for building a distributable kit does break here, so all I can do is to put a Windows executable for download. Replacing it in the original 2.4.324 installation works for me under Vista, but is known also not to work for some other cases. Backup before trying.

The link is here:
opencpn.exe - 4shared.com - online file sharing and storage - download

It includes all the goodies to date.

Good luck,

Piotr

[r.fairman]

get error when i run says failed to start because wxmsw28_aui_custom.dll was not found

I am using xp

regards

Richard

[PjotrC]

Richard,

I understand you are trying the executable...
It happens often, I only put it out for download, because antxon is leaving in a few days, so maybe it will work for him.
Otherwise, it is better to wait for some real integration.

Piotr

[antxon]

Piotr,
Thank you so much. Probably leaving tomorrow from Martinique, so very busy now, but I'll try to test it. Feedback in about a month. Thank you again.

[PjotrC]

I'm a bit late with this, but attached is an Addendum, significantly improving the behaviour for Route Properties, especially for active routes. The source goes on top of the 0001 Patch.

For lucky users, the binary is here:
opencpn_2.exe - 4shared.com - online file sharing and storage - download

[antxon]

Originally Posted by PjotrC

The settable VMG values still stay in respective waypoints - I agree this is a leg property rather than waypoint, but there is no corresponding data structure to use. Not yet a reason for major changes.

Piotr

Just arrived from the crossing. I could not use the executable, but in azores I downloaded last beta, which already implements this patch; It worked like a breeze, very useful for both home and on-route planning. Anyway, I would like to ask you if the settable speed (or VMG) values were finally implemented or not (I understood they would stay as a WP property). I was not able to find how to set them. Regards,
Antonio

[PjotrC]

Antonio,

Thanks for the feedback...

The per-leg planned VMG is settable as a string in the preceding waypoint Description field, e.g.

VMG=4.5;

Also, the Estimated Time of Departure from a waypoint can be specified in a similar way, by including it in the Description field:

ETD=05/15/2011 14:30;

The terminating semicolon is necessary in both cases.

Piotr