I recently noticed the above data available in the WxData Expedition menu. Not seen that before, so not sure it is new or silly me never noticed that. I recall on a recent course with Will Oxley where he mentioned this type of data would cost north of $150K per year. 

Am I getting things mixed up? Any help clarifying this would be appreciated.

Thanks Nick. Also I am not using CMAPs nor ENC's, just the base map. Is that a contributing factor, e.g. if I bought a CMAP subscription ( I am assuming better coastal line resolution), would the issue go away?

Hi, I would like to know how to solve a problem I experience sometimes. It seems there is a narrow gap between the edge of the grib file grid and the coastline, i.e. NSW coast. When asking Expedition to calculate a coastal routing with a head current, the result is a route that seems to fit into that gap. I tried to create one or more notes to "close the gap", but if the current is strong enough that is not effective. Anyone has any ideas/suggestions?

Thanks Nick.

Yes I had loaded Access G, Access PH, Access VT, EC and GFS and selected "All models". I clicked Ensemble hoping to get 3 routes, but I can see Expedition tries to calculate 5 and fails on 2 as the hi res models durations are not long enough. The 3 resulting route names are:
"AXS I Med 19:19:13", "ECMWF 0 153 I Med 19:19:19" and "GFS I Med 19:19:26".

Than I pressed Optimize with "All models" selected. It calculates a route, but it is not clear to me which model was used. The result name was "I Med 19:20:29" 

Than I unselected the the EC and the GFS in Settings, selected "All models" as you suggested and I could optimise. The result name was "I Med 19:21:38". The outcome was slightly different from "AXS I Med 19:19:13" which I think it means it used the high res model where and when it could.

Nick wrote:

I suspect the Triton won't be adding TWD & TWS to the network.

Yes, after your post I checked an log file I had stored and PGN 130306 only has "Apparent" instances.