S63 PlugIn Version 1.0 Released

[bdbcat]

Murray...


Thanks for the pix.
1. OCPN does not know about virtual ATONs. This is a relatively new Object Class, and not yet implemented in OCPN. I agree that they should be shown, at least in category "All", and probably in "Standard" as well. Adding to the list....


2. I will investigate the feature names you mention. I do not know off-hand the symbolization rules for named rocks.


Thanks
Dave

[bcn]

Originally Posted by bdbcat

Murray...


Thanks for the pix.
1. OCPN does not know about virtual ATONs. This is a relatively new Object Class, and not yet implemented in OCPN. I agree that they should be shown, at least in category "All", and probably in "Standard" as well. Adding to the list....

Thanks
Dave

In ENC chart portrayal mode - when receiving via AIS information about virtual AtoN (MsgType 21) those are getting displayed.
Sailing in those waters with an AIS receiver connected, you shall see the V-AtoN.

[Hakan]

About Aton...
Are we talking different Atons here?
The Aton, see shot, has what I know "always" been there. What's the other type not shown? Please inform.
Thanks
Håkan

[bcn]

Håkan,

are those ones received by AIS? What does the ENC say on this place? Is there a Virtual AtoN object?

Hubert

[Hakan]

Hubert..
Yes, received by AIS.
Ahaa, so there could be a chart object for these as well?
One of the Atons on my prev shot has this info, see INFORM. Sweden chart oeSENC

[bcn]

Yes, the question from NZ about portrayal of V-AtoN.
See the paper chart with the symbol.

Shaking my logic a bit ("Why should something virtual being shown on a chart'"), but this is how it is defined:
https://nauticalcharts.noaa.gov/publ...avigation.html

[Hakan]

Hubert..
OK, very good thanks for the info.
So I agree it should have been shown on our oeSENC charts.
Two pics from SE charts, raster and ENC. The raster charts has the correct symbol and probably there is the same info in the ENC charts we use to make oeSENC. Position as of pic 2 if want to check for it in the data base. (Dave?)

[cagney]

Looking at US Chart 1 from April 15th 2019.
Section S 10-15. Column for ECDIS display:

The presence of an AIS transmitted
signal intended for use as an aid to
navigation associated with a physical
aid, including AIS MMSI Number,
can be obtained by cursor pick on the
physical aid.

OpenCPN already does just that, if it is available in the chart source. See Håkan's second post above. No need to do anything more!
Raster and Ecdis standard presentation are not the same in this case.

Thomas

Thomas

[petter5]

For sure AIS AtoN's show up in Opencpn.



Aton object MMSI 0024420... at 385.13 Nautical mile distance recieved from Fulehuk lighthouse in Norway, 29 June 2019 - see attached screen shoot.


Using Raspberrypi with dAISy AIS hat.

[Chiko]

Originally Posted by bcn

Shaking my logic a bit ("Why should something virtual being shown on a chart'"), but this is how it is defined:
https://nauticalcharts.noaa.gov/publ...avigation.html

Hubert
I see one value of a charted V-AIS when you’re preparing a passage plan into unfamiliar waters. Eg a V-AIS mark may indicate to stay south or simply isolated danger. The fact that its Virtual, tells me not to expect to see a physical buoy or beacon with an AIS transmitter out on the water. It still needs to be shown on the charts for this planning purpose though.
Murray

[aboon]

I am seeing some strange effects with the boundaries of some objects and areas on my AusENC and some NZ S57 charts. I am using OpenCPN 5.2.0 and S63 pi V 1.16.725 on Windows 10.
The boundaries of Restricted areas, Seabed areas, Administration areas, Anchorage areas and some shore structures appear to be discontinuous and as if the plotter pen is up when it should be down and vv. I have tried various graphics options (OpenGL on/off) with no change.
Attached are screenshots of some examples. The Administration area example changes with the display scale but, as far as I can see, the other areas do not change with scale.
The oeSENC Aus charts do not show these effects.
What might I be doing wrong?

Andrew

[bcn]

Andrew..


there is an update of the S-63 plug-in available, addressing the issue of the boundaries.
Managed plug-in. Can you give it a try?


Hubert

[aboon]

Hubert,
All of the boundary lines on my AusENC charts and the NZ charts now look 'clean'. Thank you very much!
A couple of minor points: the anchor symbol is sometimes on the wrong side of the boundary line of a small craft anchorage area and the 'tick' marks sometimes point away from the area bounded rather than into the area. I am using the Paper Chart graphics style with Symbolized boundaries. An example is shown in the attached image, where the small craft anchorage area extends along the shore.
It's probably the wrong place to report it, but in the Australian oeSENC charts, there is sometimes a boundary line with 'tick' marks on the shoreline, which do not appear on the S63 charts (and I don't think should appear). The second image shows that.

Thanks again,

Andrew

[aboon]

I've noticed a minor issue with my AusENC S63 charts not displaying an underwater pipeline.
In one instance, the pipeline is not displayed at all and in another the pipeline is displayed but Object Query does not return any information about the PIPSOL. In all cases, the oeSENC version displays the pipeline and returns the object information.
The three images attached show the S63 display for a pipeline to a marine farm in Long Bay (ie nothing shown); the same display using oeSENC charts; and an overzoomed oeSENC display showing the Object Query result.
The cell is AusENC AUPAU01.
In another area (Port Esperance, 43 20.5' S 147 02.6'E) pipelines are displayed on the S63 display but Object Query does not return any PIPSOL information. The oeSENC version displays the pipeline and the object data.
I don't think this is a new issue as I recall seeing part only of the Long Bay pipeline displayed in S63 a year or so ago (maybe 2 years).
Windows 10, OCPN V5.2.4, S63 pi V1.17.1 and oeSENC pi V4.2.17.1.

Andrew

[moseriw]

Hi,
Problem with

s63_pi-1.17.9-0_debian-arm64-10.tar.gz

arm64 debian 10.10
Linux pinebook 5.10.43-rockchip64 #21.05.4 SMP PREEMPT Wed Jun 16 08:02:12 UTC 2021 aarch64 GNU/Linux

conpilation went fine but importing the plugin with OpenCPN 5.2.0 Plugin-API: 117
Error: Import Plugin-Tarball Metadaten missing.

Well... howto solve it?
Thank you for solutions.