OpenCPN Version 5 Released

[Hurricane]

Originally Posted by LeaseOnLife

I have this on Kubuntu too, any version in the past few years and now 18.10.
Try to close the settings window first, then I can close the NMEA debug window also. You may have to move the debug window to get to close the settings window.
Dirk

I always close the NMEA debug window by clicking the same checkbox in the Options window (i.e. click "Show NMEA Debug Window" to close it) that I used to open it.
I'm running under Linux Mint 19.1 - derivative of Ubuntu.
Incidentally, closing the Options window then clicking the window close X button also works.

[Lance]

Where do I find the charts to use with Open CPN ?
I HAVE THE NAME BUT NO URL TO FINISH DOWNLOADER PROCESS ?

[Gilletarom]

Hello Lance,

Originally Posted by Lance

Where do I find the charts to use with Open CPN ?
I HAVE THE NAME BUT NO URL TO FINISH DOWNLOADER PROCESS ?

Have you read this part of the OpenCPN manual?
https://opencpn.org/wiki/dokuwiki/do..._manual:charts

You will find all the useful information. You will see that depending on the area where you want to navigate, there is always a map solution for OpenCPN. Some solutions are free, others not.
Free solutions include the USA, Brazil, Argentina, New Zealand, the inland water channels of Western Europe.
Is your navigation zone in Western Europe? Then see either :
- VisitMyHarbour's paid raster nautical charts

- NV-Charts paid raster nautical charts

- O-charts' paid vector nautical charts.
"Pescott, Whitehaven" is it in Australia? See the vector nautical charts of O-Charts. And if "Pescott, Whitehaven" is in the Caribbean zone, see the :
- vector nautical charts of O-Charts,
- NV-Charts paid raster nautical charts
"Pescott, Whitehaven" is in Canada, see your own national mapping service and you should be able to display nautical charts rasters with the BSB4 plugin for OpenCPN.

The official free nautical charts are downloadable thanks to the "Chartdownloader" plugin.
For the nautical charts pay, it is necessary to use one of the plugin BSB4, S63, oeSENC, NV Charts.

And I forget about it .. Read the documentation.

[ejs]

Hi,

I have three Pi devices I am trying to run OpenCPN V5 on. One is a Raspberry Pi 3B+ running Openplotter which runs openCPN installed from the PPA just fine.

When I try to install Raspbian myself (latest version, Stretch with all updates done) on the same PI 3B+ OpenCPN will run once and then Seg faults all subsequent times until I delete the config folder and then I get the welcome message and can run it once again.

I have run it in GDB and the last line in the output is:

Thread 1 "opencpn" received signal SIGSEGV, Segmentation fault.
0xb648f1a0 in glXDestroyContext () from /usr/lib/arm-linux-gnueabihf/libGL.so.1
(gdb)

I've tried with Open Gl on, off, and with "Fake KMS" in Raspbi-config.
I've also built from source with the same results.

What is even more puzzling to me is that I have tried it in my main navigation computer, an Orange Pi 2plus also fully updated with the same result and the same error message. On this one I can only compile from source and can only use no_opengl, but that has run fine on previous versions all across the pacific.

Any thoughts on what I can do to get OpenCPN runing on the other two devices? Or tests I can do to get more info on the problem?

-Eric

[phiggins]

Is there a way to specify the depth units for a mbtiles chart?

[bcn]

mbTiles is raster - no way to define parameters on the chart.

Is your question about the meta data?

[nohal]

Originally Posted by phiggins

Is there a way to specify the depth units for a mbtiles chart?

You can specify anything you want in the tileset metadata. There is nothing in the standard about metadata for depth units (https://github.com/mapbox/mbtiles-sp...er/1.3/spec.md).
Nobody does that as far as I know, not even NOAA in their single chart tilesets, so OpenCPN does not do anything to try to find out if the tileset contains metadata that could be depth unit.
We will probably implement support for it if there are some tilesets that actually do contain such metadata.

[bcn]

What might be a "(no)standard" implemented by OCPN...

[phiggins]

Yes I was thinking of the metadata. I guess I'll start putting it in the name along with the zoom level and creation date and the name. But that won't set it OpenCPN.

[nohal]

Originally Posted by phiggins

Yes I was thinking of the metadata. I guess I'll start putting it in the name along with the zoom level and creation date and the name. But that won't set it OpenCPN.

This is exactly what will never make it work... Do create the metadata, while we will never implement it based on filenames, we will implement it based on the metadata.

[phiggins]

SasPlanet allows you to specify the Name, Description and Attribution. Would you take the depth units from the Attribution?

[nohal]

Originally Posted by phiggins

SasPlanet allows you to specify the Name, Description and Attribution. Would you take the depth units from the Attribution?

Sure we will not be supporting the abuse of attribute with clearly completely different meaning.
If you read the specification of the standard I have linked above, you will see that the definition of it is "attribution (HTML string): An attribution string, which explains the sources of data and/or style for the map."
So the answer is no, we will not parse any html for clues of what the depth unit might be.
Introduce a new metadata field, clearly being the depth unit, like "depth_unit" and use a clear set of values for it, like METERS, FEET, FATHOMS (Which is what the standard S57, and well behaved KAP, charts use) if this has to make any sense.

[phiggins]

The thing is there is a ton of mbtiles created them from SasPlanet so if you don't use one of their 3 fields they will have no depthunits, creation date etc. Most people are not capable of creating their own metadata for mbtiles.

[phiggins]

Why not simply look in the Description and parse out various information like the depthunits=xxx creationdate=xxxxxx

[nohal]

Originally Posted by phiggins

The thing is there is a ton of mbtiles created them from SasPlanet so if you don't use one of their 3 fields they will have no depthunits, creation date etc. Most people are not capable of creating their own metadata for mbtiles.

Too bad. There are more trivial to use tools to do it than I am able to count.

Why not simply look in the Description and parse out various information like the depthunits=xxx creationdate=xxxxxx

Because this madness has to stop somewhere. And for MBtiles it stops here. We simply can't do all the work for everybody out there and this particular "problem" is trivial to resolve on tileset producer's side, while non-trivial to do right on our side.