search

sduclos / S52

OpENCview project - a viewer of ENC.
GNU Lesser General Public License v3.0
75 stars 28 forks source link

S-52 Presentation Library 4.0.0 Draft #5

Open chenzunfeng opened 8 years ago

chenzunfeng commented 8 years ago

Hi, sduclos

I downloaded "S-52 Presentation Library 4.0.0 Draft" from IHO's website. I noticed that, The first few pages of this PDF document says that most mariner's objects have been deleted from Presentation Library, and only 3 ones left. They're dnghlt, marfea, and marnot. Does it mean the mariner's objects like waypnt, vessel, leglin.. should be implemented all by the developers? Should we merge the mariner's objects from edition 3.2 to 4.0?

sduclos commented 8 years ago

My understanding is that mariner's object have been remove to align S52 to IEC61174 where the specs and implementation of Mariner's Object are left to the vendor. But the various LOOK-UP of the old PLib are still useful. So downgrading the PLib seem counter productive. You can load various PLib (.DAI) at any time, the code will resolve / merge the new LUPT. The old one are still active.

sduclos commented 8 years ago

Hi chenzunfeng,

We can continue by e-mail rather than github to discuss the implication of PLib 4.0 I don't think its official yet .. wait and see ..

rgds,

Sylvain.

On Wed, 5/11/16, Johnphan Chen notifications@github.com wrote:

Subject: [sduclos/S52] S-52 Presentation Library 4.0.0 Draft (#5) To: "sduclos/S52" S52@noreply.github.com Received: Wednesday, May 11, 2016, 4:57 AM

Hi, sduclos

I downloaded "S-52 Presentation Library 4.0.0 Draft" from IHO's website. I noticed that, The first few pages of this PDF document says that most mariner's objects have been deleted from Presentation Library, and only 3 ones left. They're dnghlt, marfea, and marnot. Does it mean the mariner's objects like waypnt, vessel, leglin.. should be implemented all by the developers? Should we merge the mariner's objects from edition 3.2 to 4.0?

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub