<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
All,<br>
Sorry to have taken so long to get some clarification on this old
question. This got lost in the email flood. Hopefully, this will
clarify any remaining concerns:<br>
<br>
US NODC has data from OCSEAP 1976-1978 attributed to RESOLUTION,
NODC/ICES code=32RS. This platform had an 'originator code' assigned
as 'RN', which was recorded in NODC numeric code set 0133 used in
the OCSEAP data files, but we created the 32RS code back in the
1970s. There are (as far as I can tell) 5 NODC accessions that are
properly attributed to the R/V RESOLUTION (I have not been able to
find a call sign or other info about this vessel yet, other than an
attribution as R/V in an OCSEAP report (See p.130 of Environmental
Assessment of the Alaskan Continental Shelf Annual Reports of
Principal Investigators for the year ending March 1977 Volume 1.
Receptors - Mammals. Online at
<a class="moz-txt-link-freetext" href="http://www.arlis.org/docs/vol1/OCSEAP2/Annual/5721406/A1977">http://www.arlis.org/docs/vol1/OCSEAP2/Annual/5721406/A1977</a> v01.pdf).<br>
<br>
US NODC has one MBT stripchart data set (NODC Accession 8700048)
that is labeled with "J. RESOLUTION" from 1986, which coincides with
the whereabouts of the Sedco/BP 471 (code 54SD) that was
colloquially called the 'JOIDES RESOLUTION' even though the name was
not officially registered as such until 1996.<br>
<br>
So, I concur (at long last!) that there is a separate US platform
R/V RESOLUTION, code=32RS. The US NODC platforms list now includes
R/V RESOLUTION (32RS), UK RESOLUTION (74E8), JOIDES RESOLUTION
(54JR), and Sedco/BP 471 (code 54SD).<br>
<br>
I also concur that there is no need for multiple JOIDES Resolution
codes.<br>
Cheers,<br>
Don<br>
<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 2/16/2011 9:17 AM,
<a class="moz-txt-link-abbreviated" href="mailto:accessions@ices.dk">accessions@ices.dk</a> wrote:<br>
</div>
<blockquote
cite="mid:OCTOPUSWpGtK1k8yzib0000028f@octopus.ices.local"
type="cite">
<style type="text/css">
.h1 { font-family: Tahoma, Verdana, Arial, Helvetica, sans-serif; font-size: 14px; font-weight: bold;}
.h2 { font-family: Tahoma, Verdana, Arial, Helvetica, sans-serif; font-size: 12px; font-weight: bold; }
.p { font-family: Tahoma, Verdana, Arial, Helvetica, sans-serif; font-size: 12px; }
</style>
<p>Dear Platform Group,<br>
<br>
A call sign error has been spotted by Roy Lowry for the US
vessel RESOLUTION. Can someone help identify the vessel
RESOLUTION from UNITED STATES? This is a relatively old code
(before 1996). <br>
<br>
ROSCOPS:<br>
There are ROSCOPS listed for United States "RESOLUTION" with
vessel names:<br>
Resolution: OCSEAP data from 1976-1978<br>
Joides Resolution/Sedco/BP 471: 1985-1992<br>
<br>
Platform list:<br>
Resolution: code 32RS<br>
Sedco/BP 471: listed as a Liberian vessel with code 54SD<br>
<br>
I have 2 questions:<br>
<br>
1) Can someone supply attributes for 32RS? I assume this should
be associated with the OCSEAP data.<br>
Code : 32RS<br>
Name : RESOLUTION<br>
Flag : UNITED STATES - US (ISO Country Code)<br>
<br>
<b>Important Comments (Conflict to be resolved!):</b><br>
Call sign GBZX incorrect for this vessel. GBZX is for the UK
vessel RESOLUTION with code 74E8.<br>
(added by: Marilynn Sorensen - 16/02/2011 00:00:00)<br>
<br>
<br>
2) Should a code be created for the JOIDES RESOLUTION?<br>
<br>
NOAA needs to respond to this query.<br>
<br>
Kind regards,<br>
The ICES Data Centre<br>
<br>
International Council for the Exploration of the Sea <br>
Email: <a class="moz-txt-link-abbreviated" href="mailto:accessions@ices.dk">accessions@ices.dk</a><br>
Web: <a class="moz-txt-link-freetext" href="http://www.ices.dk">http://www.ices.dk</a><br>
<br>
Tel: +45 3338 6718 Fax: +45 3393 4215<br>
H.C. Andersens Boulevard 44-46<br>
1553 Copenhagen V. Denmark<br>
<br>
<a moz-do-not-send="true"
href="http://www.ices.dk/datacentre/requests" target="_new">ICES
Platform Code Requests Application</a><br>
Read the latest ICES Data Centre e-News <a
moz-do-not-send="true"
href="http://www.ices.dk/datacentre/updates/DC_update.htm"
target="_new">online</a><br>
<br>
</p>
<hr>
<p>This email has been generated by the ICES Platform Code
Requests Application</p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Platforms mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Platforms@mailman.nerc-liv.ac.uk">Platforms@mailman.nerc-liv.ac.uk</a>
<a class="moz-txt-link-freetext" href="http://mailman.nerc-liv.ac.uk/mailman/listinfo/platforms">http://mailman.nerc-liv.ac.uk/mailman/listinfo/platforms</a></pre>
</blockquote>
<br>
</body>
</html>