Feature Requests

[Tupaia]

Originally Posted by rgleason

Rom, nice idea, can you save it and then enter that into Tracker when it gets running?

Anyone who uses Airmail - Sailmail will recognise this method under Catalogues/Gribfiles.

[rom]

Originally Posted by rgleason

Rom, nice idea, can you save it and then enter that into Tracker when it gets running?

Tracker ? sorry I have no idea what you are talking about ...

[nohal]

Originally Posted by rom

Hi everyone, how about a "rectangle select" (e.g. similar to gimp) to select an area/coordinates to create a grib request ? I am modifying the coordinates manually to optimize and save bandwidth, especially with sat phone. Possible but takes a bit longer. Cheers.

Isn't this already implemented? When I click on the "Manual selection" checkbox, I can draw a rectangle to define coordinates for the request, can't you?

Pavel

[rom]

Originally Posted by nohal

Isn't this already implemented? When I click on the "Manual selection" checkbox, I can draw a rectangle to define coordinates for the request, can't you?

Pavel

Holy cow ! yes you right, I totally missed that one ! It would be nice if we could resize the rectangle from which ever angle though. So we don't have to recreate the rectangle form the begining if we are not happy with the coordinates. Don't tell me you can do it already !

[nohal]

Originally Posted by rom

Holy cow ! yes you right, I totally missed that one ! It would be nice if we could resize the rectangle from which ever angle though. So we don't have to recreate the rectangle form the begining if we are not happy with the coordinates. Don't tell me you can do it already !

No, you can't, but don't tell me, with one degree resolution of the request, you need it

[rgleason]

Originally Posted by nohal

Isn't this already implemented? When I click on the "Manual selection" checkbox, I can draw a rectangle to define coordinates for the request, can't you?
Pavel

Pavel, the box selection sequence it much better and more intuitive IMHO, thank you. Click on @ then check Manual Location, then you can chose your selection box from any diagonal. The parameters form then disappears to the background, after selection, which is ok as most users will know to click on @ to complete.

Thanks for this improvement!
PS: I suppose keeping the selection box showing is complicated?

PSS: We are going to need to update the manual with this sequence!

[did-g]

Originally Posted by did-g

Hi,
I'm working on something like that but currently it's slow and there's no executable for testing you have to compile it yourself. it's in
https://github.com/did-g/OpenCPN.git

first you select a ring size and number of ring in boundary point tab ocpn_draw preferences dialog box, I'm using 1 and .1 nautical. It's for dangers and some boy, beacon and so on.

there's a new button in ocpn draw plugin layout manager 'S57 Quilt to layer'. it generates exclusion zones (a lot) for the visible chart view using your group charts set and safety depth setting.

Did I say it's slow as is unusable? cap_cod gpx is 30 MB, very hard on ocpn_draw_pi.

Next faster and oesenc_pi.

.

Still only US S57 but I may add oesenc and other S57 charts today.

Add ability to use an inclusion boundary so you can do something like that:

[nohal]

Originally Posted by rgleason

Pavel, the box selection sequence it much better and more intuitive IMHO, thank you. Click on @ then check Manual Location, then you can chose your selection box from any diagonal. The parameters form then disappears to the background, after selection, which is ok as most users will know to click on @ to complete.

Thanks for this improvement!
PS: I suppose keeping the selection box showing is complicated?

PSS: We are going to need to update the manual with this sequence!

Rick...
I don't know if you are reading the same manual like me, but in the one I use at https://opencpn.org/wiki/dokuwiki/do...s:grib_weather this feature is described already.

Pavel

[cagney]

Pavel & Rick

The manual does not describe the latest changes to the "Manual Select".
For example the option "Use always this area" and the way the @ button changes are not included.

Thomas

[rgleason]

Pavel, I believe we are on the same page.
The graphic needs to be changed too, because the # steps is less now.
No more "Start Graphic Select"
https://opencpn.org/wiki/dokuwiki/li...aselection.png

Also thanks Thomas. I need to get exporting working for the wiki first. To do that I need to get some dokuwiki PI working either with older version that work with PHP 5.3 or create an htaccess that increases PHP to 5.6 for just the wiki and not Tracker. Either way, it's probably a muckhole... but I've been messing around here!

[rgleason]

Rom

Holy cow ! yes you right, I totally missed that one ! It would be nice if we could resize the rectangle from which ever angle though. So we don't have to recreate the rectangle form the begining if we are not happy with the coordinates. Don't tell me you can do it already !

Just start over with a new rectangle. It is easy enough. Not worth having it editable. This is great as it is.

[bcn]

Originally Posted by did-g

Still only US S57 but I may add oesenc and other S57 charts today.

Add ability to use an inclusion boundary so you can do something like that:

Cool!

The "route checker" is getting in sight!

[did-g]

Hi,

Google summer of code first deadline is January the 23th. Maybe too late but do we want to apply for 2018 or 2019?

I don't know if we have big enough projects but O is already used for students projects and with more than 25 contributors last year finding mentors should be doable.

Seeking open source projects for Google Summer of Code 2018 | Google Open Source Blog

[stevead]

Is now an appropriate time to suggest adding support for additional connection types, namely built-in Sensors and NMEA 2000 ?

Many modern portable device include built-in GPS that may not necessarily be exposed as a COM port. On Windows devices, since Windows 7, location information has also been made available from the Sensor API. Possibly not necessary on Linux as GPSD would be expected to provide support for built-in devices.

I think we've probably hit the inflection point for marine electronics with respect to NMEA 2000 . Not that I can offer any concrete evidence, but it seems as though the majority of devices (GPS, Depth, Log, Wind, VHF and AIS) are now shipping with support for NMEA 2000 rather than NMEA 0183 or proprietary protocols.

My own personal experience is that I've had to update a few 20 year+ devices (no longer repairable) and I've bitten the bullet and replaced them with NMEA 2000 devices.

There are a few Open Source NMEA 2000 parsers such as Canboat, OpenSkipper and SignalK and some complete h/w and s/w solutions on Arduino. Together with a few low cost CAN bus interfaces, it is now feasible to either provide a NMEA 2000 to NMEA 0183 converter or a native NMEA 2000 connection type (perhaps modelled on CANopen). Not sure what this would mean wrt to NMEA intellectual property rights.

It may also be worthwhile to get ahead of the ball wrt to support for SignalK and the evolving NMEA OneNet standard.

[transmitterdan]

OpenCPN is not a hardware experimenter's platform. It works best when data is fed in via a hardware independent stream such as Ethernet. There are many open source projects and lots of commercial solutions for getting data from sensors into a stream that can feed OpenCPN. OpenCPN supports too many platforms to get into hardware like CAN or other proprietary networks. NMEA 0183 format supports nearly all sailing and navigation data needed.

Look into Open Plotter as a platform for supporting other types of sensors and interfaces. Raspberry Pi is <$50 for the base of running OP. OpenCPN runs on Open Plotter too so a really cheap starting point for what you are describing.

But I think the only universal interface available to all platforms supported by O is Ethernet either wired or Wifi. But that isn't viable for a lot of sensors so we will need a middle layer. There are lots of available solutions that can bridge the gap. Why should O reinvent those wheels?