WIP Route analysis and bugfix.

[did-g]

Hi, Add the ability to compute speed along an existing route.

Regards Didier

[rgleason]

Didier, This is a big important change. What a huge contributor you are! All users will thank you! WR Route --> Track --> Route Manager JSON message to request Grib Values Add SOG to route position I am sure there are other things I have not noticed. The plugin works well. This is an aside, there are a couple of things I have noticed in the past that are a little flakey:

• When the route isobars are being calculated, I have to refresh the screen to get it to draw, (ie zoom in or out). This is on a Windows machine.
  • In Grib_pi I set the grib date and time, then I go to wxRoute and pick "Grib Time", I find this is kind of stuck and does not change. I have not figured out what causes this, but the Compute is failing, until I get the "Grib Time" to actually work. I will keep an eye on this.

I have some screen shots to show a little what I did. First completed a new routing.

• Weather tracks are added complete with name and date when "Export" is hit. SOW added to weather route report!

• Under Tracks pick "Route from Track".

• The Route Position cursor shows more useful information about weather.

• Route Properties shows each leg of the new Weather_routing Route created. The speed shown is 6 knots, unlike the Track which has a time stamp and the speed for that leg. I would be great if this were fixed.

I really need to check this one out more.

isochron reaching end point, set the right timespan

[rgleason]

Different Leg Speed & Arrival Dates for Track and Route. I feel guilty showing this after all the improvements!

[seandepagnier]

wow, I intend to merge in a few days, give me time to review this

[rgleason]

Also this resolves the speed confusion in FR #248

[did-g]

Two things

• It doesn't solve the rendering issue on windows with wx3.1 (ie redraw is blocked until you zoom or collapse the config dialog).

• The route analysis isn't finished, it should compute intermediate points on grib step, I should make two PR one for fixes , one for the route stuff but they are badly mixed.

On Fri, May 17, 2019 at 2:31 PM Rick Gleason notifications@github.com wrote:

Also this resolves the speed confusion in FR #248 https://github.com/seandepagnier/weather_routing_pi/issues/248

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/seandepagnier/weather_routing_pi/pull/249?email_source=notifications&email_token=AC4TMKTGMDIDQBCKO275AA3PV2QSBA5CNFSM4HNQJBTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVUT35Q#issuecomment-493436406, or mute the thread https://github.com/notifications/unsubscribe-auth/AC4TMKWJRNK3MPYHCSFTG7TPV2QSBANCNFSM4HNQJBTA .

[rgleason]

Related to this improvement: UI Improvement: Provide a yellow box "Info" tooltip at the Cursor along the Optimal Route #177

[rgleason]

Related to this improvement: Feature Request: Grib Weather at current Optimal Route Position (option) checkbox #203

[rgleason]

I suppose this is piling onto Didier, which is unfair, but this little bug needs a fix too: ov50 - Bug - wx-Routing requires Climatology_pi installed to be able to disable Climatology use. #241

[did-g]

@rgleason about

isochron reaching end point, set the right timespan

for computing legs speed WR is using distance/time with time being the configured step, but it doesn't work for the last leg. Let say you have a 3h hours step but you reach the end point in 1 hour, last leg speed is distance/1h not distance/3h

[rgleason]

Ah. Ha. The light bulb just turned on. Thanks. This is very similar to the solution "Slow Route", but it is an ending or completing case, rather than starting in the middle of constrained land areas, and going through mid route land areas.

Is there some "slow route" code that could be used for begining, middle and end, when in constrained areas.

[seandepagnier]

@rgleason about

isochron reaching end point, set the right timespan

for computing legs speed WR is using distance/time with time being the configured step, but it doesn't work for the last leg. Let say you have a 3h hours step but you reach the end point in 1 hour, last leg speed is distance/1h not distance/3h

Do you mean the propagate to end routine? Yes, the weather route has a special update just to reach the end position which it uses to compute the time to reach it rather than moving a fixed time step.

[rgleason]

Thank Sean, This seems like a very similar problem to various "Failures" at the start and middle of routes....something, some set of parameters for calculation have to be modified, in order to continue the calculation to completion (IE reaching Finish). So I ask this again...

Is there some "slow route" code that could be used for beginning, middle and end, when in constrained areas.

If this were possible and works better, then identifyng "failure types" might become less important.

[did-g]

@seandepagnier This fixes a display issue not a computation one. master PR

[rgleason]

Tested. Please see http://www.cruisersforum.com/forums/f134/weather-routing-100060.html#post2892375 At various Climatology and Grib data created Isochrones

[rgleason]

From my forum notes...

Didier, I tested the plugin you reference above. Oddly, the SOG and SOW do not show together as in your screenshot. Do I need to adjust a setting?

Well I turned on average speed and average speed ground. (I don't think these settings control the "Route Positon" Panel. I believe they control the parameters shown in the Configurations area.

Then I discovered several things:

1. Weather_routing seems to favor the left panel. Properly showing the isochrones as they are created. The right panel is not drawn until the route is completed.
2. Grib_pi seems to favor the right panel, showing the grib wind indications in that panel only.
3. Climatology_pi seems to do any panel that has been activated, and then the Wind Roses show.
4. When "View > Route Position" is activated and hover over Climatology sourced data/isochrones the SOG and SOW show on various isochrones, but not all of them. Some are left out, - is this because of interopolation?
5. When "View > Position" is activated and hover over Grib sourced data/isochrones the Boat Speed SOG is the only parameter that seems to show.

Can someone please confirm this and report back using Didier's appveyor "Artifact Tab" build of the plugin above? https://ci.appveyor.com/project/sean...5223/artifacts