Originally Posted by cagney
There is a very simple solution to this. Think thoroughly through your needs and preferences, when it comes to charts. Then organize your charts in different directories, for example small scale charts for the Indian Ocean
in a separate directory that you only load when it is actually needed, and so on.
Yes, that would work. However, OpenCPN
already has code to build a chart catalogue... should we all have to create one too, independently, given that all the charts already have the necessary metadata, and OpenCPN
already reads it and builds a perfectly good index?
For the coast of the UK and France
alone, a full chart folio would be around 1500 charts. Sorting through those is a VERY longwinded and painful task (particularly given that the filenames of BSB/KAP charts are not generally meaningful, and either MapCal or OpenCPN needs to be used to look up each chart's filename/meta-data details, one chart at a time)
OpenCPN could filter charts by scale quite simply, and negate the need for separate scale directories.
Alternatively, if it's really necessary to bodge a scale based delineation into the chart store directory structure to get this kind of functionality, well, it would be possible to write a binary to extract scale information from the BSB
header, and then implement a shellscript allowing BSB
charts to be sorted out by scale. I might do this when I've finished my current
chart-related bit of programming - it's not rocket science. I still think a solution inside OpenCPN would be a better approach.
What I'm not keen to do is sort all my BSB charts by hand... I've already done this for a small proportion of the areas for which I've got BSB/KAP chart coverage, and it's a right pain in the neck!