I have layers for the
Netherlands with more then 10.000 points and this (as the manual also states) is sort of bringing down the performance of
OpenCPN ;-)
When trying to show the data stored with a specific point, it can take some time to get it visible.
For the
Netherlands I use self-generated rastermaps (.kap-files) generated from Open Street Map. And I created layers (gpx-files) from available open data, like buoys and mooring-spots.
It would be nice to be able to create layer-files somehow that are "coupled" to the underlying
charts.
For example I have a ONC-Ned_1304.kap-file, and it would be nice if then dynamicaly a ONC-Ned_1304.gpx would be loaded.
The number of visible/loaded points could then dramatically go down.
I could then "distribute" the points from the layers, that now cover the whole of the Netherlands, over the 200+ rasterfiles.
This could be done based on the filename of the charts (like in my example).
Or maybe by a "indexing" function in
OpenCPN that would run once through the gpx's and then "know" when to show which layer-files, like it knows that after indexing the charts.
That would be the better solution I guess, because then you could still have layers that would cover the whole of the Netherlands (in my case) beside layers that would cover only a small area.