v2.0.22 UWTROCK are very dominant especially when zoomed out.

[Hakansv]

On Win10 using the current master. o-charts_pi updated today to 2.0.22 (from 2.0.13)

The underwater rocks symbol have changed in this version. (To S52 standard?) Was this intentional and if so why? What's more critical is the crowded not scaled view while zoomed out. See pict. My Win is scaled to 175% but a similar view is also on a Win 100% scaled.

For info was the first view after plugin update showing enormous soundings font size. About 50 mm height! After some zooming, lights toggle and more they gradually returned to normal.

o-charts v2.0.13 oesu (the same on pure ENC) to the left and o-charts v2.0.22, oesu to the right

oesu zoomed out.

[bdbcat]

Do you have SCAMIN enabled? Options->Charts->Vector Chart Display->Reduced Detail at small scale.

[Hakansv]

Yes I have. But there are differences for the two canvas. Pict 1.

[bdbcat]

I seems pretty clear that SCAMIN is not being honored. The SCAMIN on most of these objects may be around 90,000. S should not be visible at all in this shot.

[Hakansv]

To quick posting..

For left side several pictures: On scale 1:540000 they are visible: On scale 1:418000 not visible

And on scale 1:247000 again visible:

[bdbcat]

I think I am missing your point.

[Hakansv]

Three pictures from smaller scale to bigger. The one in between has no symbols but the two other has. See the view scale on each

[bdbcat]

Hmmmm...

[Hakansv]

And why the decision to change symbol? I'm just curious.

[Hakansv]

Also other objects are show on smaller scale than before: Like traffic separation zones. And BOYSPP has grown.

[bcn2]

Don't see that issue neither on our Mac nor on the W10 system, both with the latest 2.0.22 - however changing the "Display Category" at Chart Panel Options, this makes a difference. "All" and "User Standard" for example. The TSS are ok in any case.

[Hakansv]

On my W10 I have category "All" on all pictures.

[bdbcat]

I seems as though maybe our view scale calculation is not quite correct, maybe latitude dependent. To check this, create a 1.0 NMi vertical route segment. Measure the physical length of this segment on YOUR screen, using a caliper, or so. Do the calculation. Display scale = 1852m / {length on screen, m} By my measurements, we seem to be somewhat in error.

Approved ECDIS systems specify the screen resolution (pixels per mm) pretty strictly. We have to adjust to a much wider variety of displays.

This change arose on studying a particular WRECK in France. We discovered an error in our S52 PLIB implementation. Corrected that to pure S52 requirements, and this is what you see.

But again, I agree that results are not good in SE. Lots of awash rocks there.

I agree the some areas in SE have become overly dense with Isolated Danger symbols.

[bcn2]

[Hakansv]

Measurement: 1852/0.0564 = 32836.88 View scale = 1:33000

[bdbcat]

Pretty close. I wonder if, contrary to Mercator paper nav methods, we are meant to compare SCAMIN value to a horizontal scale? Would make a big difference in SE. I'll explore...

[Hakansv]

Here at about 57° N Horizontal route: 1852/0.0504 = 36746.0 View scale = 1:33000

And measure in this strange way 1 horizontal Nm is about 1.8 minutes at close to 58°N

[bdbcat]

Taking a simplistic approach: I have paper chart NOAA 11300. A relic of the past. Chart scale (printed on the paper chart) is 1:460,000. I take my trusty brass navigator's divider, measure 15 NMi on latitude scale of paper chart. I sit at OPCN, zoom in to the same area as depicted on the paper chart. Using the unchanged divider setting, I adjust OCPN zoom so that 15 miles vertically matches the divider setting. I read the OCPN view scale, Result: 709, 000. Something definitely wrong here.