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
This idea would be a manual way to bridge the poor inshore tide/current representation of RTOFS and other ocean current gribs and the Tidal Stations and harmonic file, which is not easily interpolated because currents drop off and change fast.
The idea would require agumenting the Plugin API to include the User Current information I think, or perhaps that could be done in Weather_routing, but that application does not handle gribs really.
The other way is to involve the Grib_pi program with boundaries....
Here is what I would like to be able to do:
Draw a boundary.
Attach a simple current matrix to the boundary.
Have Weather_routing recieve the tide/current boundary and include that grib data in its calculations for optimal route.
The Tide/Current Matrix would be a Table representing time + tide/current vector ( velocity and direction).
Table
| Time | Direction | Velocity |
| ____ | _____ | ______ |
Would there be a limit on how many time entries? It would be nice if it could be flexible about time intervals (1hour, 2hr, 3hr, 6hr, 12hr) and would allow a large number of time records.
Also it would be useful if you could make 2 or three of these along the general route expected.
Then weather_routing would pick these up and include them in a configuration for routing purposes, using the tide/current in the calcs.
That's the idea anyway
The text was updated successfully, but these errors were encountered:
Weather_Routing <-----Plugin API -----> ODraw Boundary
jongough/ocpn_draw_pi#337
This idea would be a manual way to bridge the poor inshore tide/current representation of RTOFS and other ocean current gribs and the Tidal Stations and harmonic file, which is not easily interpolated because currents drop off and change fast.
The idea would require agumenting the Plugin API to include the User Current information I think, or perhaps that could be done in Weather_routing, but that application does not handle gribs really.
The other way is to involve the Grib_pi program with boundaries....
Here is what I would like to be able to do:
Would there be a limit on how many time entries? It would be nice if it could be flexible about time intervals (1hour, 2hr, 3hr, 6hr, 12hr) and would allow a large number of time records.
Also it would be useful if you could make 2 or three of these along the general route expected.
Then weather_routing would pick these up and include them in a configuration for routing purposes, using the tide/current in the calcs.
That's the idea anyway
The text was updated successfully, but these errors were encountered: