Talk:Vessel traffic service area
Drafted by before SNPWG 6
Da 17.08.2006 I prefer this to be an Information object and the associated geographic object is Service Area “srcare”. This allows the service details to be provided even if we do not know the limits of the srvare svcare; Changed notice to ntctim; rgdata deleted;
Northern 7.Nov. 2006 Rgdata: see our comments under authority
Where do we need rgdata if not here???? David replied Need to discuss rgdata
Service area: We do not found service areas somewhere on the files. Fixed
Info objects always must be associated with a geo object. Therefore Davids argumentation will not work. Changed abbreviation of prcdre (see Attribute list) Accepted
DA 13 Dec 06 Should have been svcare.
Do not believe that Pilotage should be included here as it covered by pltsrv. Distinction: add pltsrv
Jens 29.01.07 David, have done your work for you
SNPWG 7 Done some work
Jens 19.02 added rgdata and catrgd as attributes
Jens 11.07.07 cntltw added
Jens 05.11.2007 added shprep, shprep carries catrgd; catrep; nctim; rgdata; therefore some of them deleted here
Jens 04.01. 2008 added condet; telcom
Jens 11.01. question mark to Ref M3
WEG 12 Feb 08 calnam; CALSGN;; COMCHA; inserted in place of telcom. Not sure about cntltw.
DA 9 Aug 08 There is a case for calnam to be in condet. If agreed we can take calnam off here.
DavidAcland 16:08, 18 August 2008 (CEST)
Started checking attributes and found svaprc to be frmtxt. Therefore changed it to TXTDSC ... But ... it seems to me now that this is redundant. All we need to do is use TXTDSC and NTXTDS. So we need an entry in Remarks to put in the encoding guide that the Service Access Prodecdure is described in TXTDSC and NTXTDS, and delete svaprc.
jens 14:00, 19 August 2008 (CEST)
good point David. The only wrong thing is, that this argument could work for all our Information objects too.
I see this problem a bit different. We all know that it will be a challenge for ECDIS systems to check the content of the extenal files referenced by TXT... However, if we are able to limit the intention of the content by using attributes or even inf object seems to me is helpful.
DavidAcland 12:45, 20 August 2008 (CEST)
OK. I changed the svaprc attribute type to S.
jens 12:16, 19 September 2008 (CEST) replaced cntltw by <rlstwt>. Having had a long discussion with David about the intention of the listening watch and decided finally to replace by requirements for maintenance of listening watch which fits our ideas much better. Sent cntltw to deleted items
By David. 23 Sep 08
Jens. I have taken your <rlstwt> above to be rmltwt. I have amended the Definiton of rmltwt a touch.
raphael 02:00, 10 September 2012 (UTC): MPA mapping for NOAA dataset has attribute CATREP bound to MRNSRV but it is not bound in the Wiki.
jens 16:33, 10 September 2012 (UTC) Raphael, Please ccan you send me the NOAA file back and highlight the relevant part. I think I have to introduce a SHPREP association to MRNSRV. SHPREP will carry the CATREP attribute. It is possible that I accidentally bypassed the intended construction.