Difference between revisions of "Talk:PLTSRV"
(New section: Multiple pilot service providers) |
|||
Line 48: | Line 48: | ||
In such a situation, in general, the way each pilot agency operates, the kinds of vessels they serve, and certain other details can theoretically be slightly different for the different pilot agencies. I wound up using different [[pltsrv]] objects which does not seem entirely satisfactory. | In such a situation, in general, the way each pilot agency operates, the kinds of vessels they serve, and certain other details can theoretically be slightly different for the different pilot agencies. I wound up using different [[pltsrv]] objects which does not seem entirely satisfactory. | ||
+ | |||
+ | (Updated: I'll see if things work out satisfactorily using [[chalim]], but it may not work.) | ||
+ | |||
--[[User:Rmm|raphael]] 06:54, 29 April 2009 (CEST) | --[[User:Rmm|raphael]] 06:54, 29 April 2009 (CEST) |
Revision as of 04:56, 29 April 2009
Drafted by Northern before SNPWG 6
14.07.2006 Jens deleted superfluous attributes; inserted ass. Inf. Obj.
17.08.2006 DA Do not see the need for us to produce pltrqs
8.Nov.2006 Northern Notice: See our comments given for authority srvhrs: We agree putting all the information into srvhrs
11 Dec 06 DA Added definitions. Pltrqs and catpsv deleted. We see duplication between pltsrv and mrnsrv. Perhaps we need to remove Pilotage from mrnsrv and catmsv? Do not see how rgdata works in this object. Remarks added.
29.01.2007 Jens seen on different places where the pilot requires other data than the e.g. VTS ((Belfast /UKHO NtM 5/07))
SNPWG 7 Added guide to inf obj
SNPWG 7 agreed
19.02.07 Jens added catrgd
14 May 07 DA Replaced guides by rcmdts; reglts; resdes;
SNPWG8 Needs work
05.11.2007 Jens added shprep;and deleted catrgd which is covered by shprep and rgdata which is covered nowhere
11.01. Jens M3 reference
11 Feb 08 DA pltrqs reinstated and added instead of catrep8
12 Feb08 WEG All OK except restvc in shprep
11 Aug 08 DA I think we need the condet on pltsrv in the same way that we have condet on mrnsrv. Added.
jens 13:59, 28 April 2009 (CEST)
I think we should consider chalim for the ProdSpec as well. It will not work in all circumstances and I see the problems software manufactures might have when trying to write the code, but for simple structured pilot regulations it is a little thought worth.
raphael 06:05, 29 April 2009 (CEST) : Yes, or maybe attach some chalim attributes to pltsrv or PILBOP. I will try a few hypothetical cases and see how it works in conjunction with the other attributes especially pltmov and dstntn.
Submitted to Hydro register manager Date
Submitted to Nav register manager Date
Multiple pilot service providers
I am trying to model a situtation where there are two agencies providing pilot services for New York Harbor and approaches. The text seems to imply two overlapping (possibly identical) service areas in this region. Does anybody know of similar situations elsewehere?
In such a situation, in general, the way each pilot agency operates, the kinds of vessels they serve, and certain other details can theoretically be slightly different for the different pilot agencies. I wound up using different pltsrv objects which does not seem entirely satisfactory.
(Updated: I'll see if things work out satisfactorily using chalim, but it may not work.)
--raphael 06:54, 29 April 2009 (CEST)