[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[McIDAS #KVW-130097]: FW: EXTERNAL: Re: TEMP SHIP data



Hi Bryan,

re:
> It occurs to me that you folks might be able to offer an opinion on this.
> Has any Unidata affiliate needed a decoder for TEMP SHIP Raob data before?

Not that I know of.

Question:

- are the ship raobs different from regular ones?

  If not, you should be able to use the regular XCD decoder/data monitor
  to decode the obs

By the way, I am on travel at the moment, so my ability to respond to email is
limited (and will be non-existent for at least a day starting in about an
hour).

> Thanks,
> 
> Bryan
> 
> From: McIDAS Help Desk [mailto:address@hidden
> Sent: Thursday, June 07, 2012 3:37 PM
> To: Biggerstaff, Brice A9
> Subject: EXTERNAL: Re: TEMP SHIP data
> 
> Hi Brice,
> 
> I found our reply (from Jay) back on 14 Feb 2012. Here's what it said:
> 
> I talked with our XCD programmer and he had some comments and questions
> about this data:
> 
> 
> If raobs are not in the list from NWS, then it won't process them (or
> know to look for them).  Probably the best thing to do is for someone
> to give me a raw TEMP SHIP RAOB report. Then, I can pass it through -XCD
> and see what happens.  Another issue is if this data is coming across on
> NOAAPORT or not. We've had quite a few issues lately with reports that
> other users are looking for, but there's nothing we can do if it's not
> coming across NOAAPORT.
> 
> Let us know what other information you can give us and we'll see
> what we can come up with.  (Also, does TEMP stand for 'temporary'
> or 'temperature'?  Just curious.)  Thanks for today's update and the
> sample data. I will pass this along to the McXCD programmer and ask him
> to take a look and comment on when/if this can be done. However, please
> note that we're currently very busy working on trying to get the McX and
> McXCD 2012.1 releases out soon. So it may be a couple/few days before the
> -XCD programmer can take a good look and give feedback. Hope that's ok.
> 
> Thanks,
> Barry
> 
> 
> On 6/7/2012 2:09 PM Biggerstaff, Brice A9 said the following:
> A while back I sent this in and got a response back requesting some test 
> data.  I managed to misplace the reply, so I just use this as a 
> re-introduction.  I am enclosing samples of test data that were captured off 
> the NOAAPort stream, so ya'll up there should have access to additional test 
> data as you need it.  Our local forecaster, Tim Garner, tells me that more 
> ships have been reporting recently.
> 
> Please take a look at this and see if there is an easy fix to allow the data 
> to be decoded and stored.  The format should be like standard RAOB data with 
> the exception of the first couple of lines which include the Lat/Lon 
> information and ship ID.
> 
> Thanks,
> 
> Brice
> 
> Brice Biggerstaff
> MIDDS Software Support
> 281-853-3011 (w)
> 713-764-2601 (p)
> address@hidden<mailto:address@hidden>  (alpha pager for text and email)
> 
> Res Confacti Erimus
> "We Get Things Done!"
> 
> 
> From: Biggerstaff, Brice A9
> Sent: Tuesday, February 14, 2012 10:22 AM
> To: 'MUG Help Desk'
> Subject: TEMP SHIP data
> 
> Howdy,
> 
> Got an inquiry from one of our forecasters wanting to know if McIDAS-XCD 
> (2010 in our case) should be decoding  and storing TEMP SHIP RAOB data.  It 
> appears that there might be some issues with mismatches between station ID's 
> and how ships report, but that the format of the data would be compatible.  
> Can you let me know if there are configuration changes that could be made to 
> pick up this data or are we going to have to modify the base code (or is that 
> something you guy would do ;-) ).  Our forecaster is looking into this data 
> to support new vehicles which may be doing splashdown recoveries.
> 
> Thanks,
> 
> Brice
> 
> Brice Biggerstaff
> MIDDS Software Support
> 281-853-3011 (w)
> 713-764-2601 (p)
> address@hidden<mailto:address@hidden>  (alpha pager for text and email)
> 
> Res Confacti Erimus
> "We Get Things Done!"
> 
> 
> 
> 

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: KVW-130097
Department: Support McIDAS
Priority: Normal
Status: Closed


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.