[Met_help] [rt.rap.ucar.edu #65414] History for MADIS mesonet data
John Halley Gotway via RT
met_help at ucar.edu
Mon Jun 2 14:19:39 MDT 2014
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hello,
Is there currently a way to use the MADIS mesonet data in point-stat? I have seen some archive met_help messages that indicate that it is possible to reformat the mesonet data to ascii format and then run it through ascii2nc, but I am looking for a more streamlined approach such as madis2nc.
Thanks!
Leela Watson
Leela R. Watson, PhD
Meteorologist
(321) 853-8264
1980 N. Atlantic Ave., Suite 830
Cocoa Beach, FL 32931
www.ensco.com
[cid:image001.gif at 01CF27E0.B2A7C250]
Innovation. Collaboration. Solutions. Success.
________________________________
The information contained in this email message is intended only for the use of the individual(s) to whom it is addressed and may contain information that is privileged and sensitive. If you are not the intended recipient, or otherwise have received this communication in error, please notify the sender immediately by email at the above referenced address and note that any further dissemination, distribution or copying of this communication is strictly prohibited.
The U.S. Export Control Laws regulate the export and re-export of technology originating in the United States. This includes the electronic transmission of information and software to foreign countries and to certain foreign nationals. Recipient agrees to abide by these laws and their regulations -- including the U.S. Department of Commerce Export Administration Regulations and the U.S. Department of State International Traffic in Arms Regulations -- and not to transfer, by electronic transmission or otherwise, any content derived from this email to either a foreign national or a foreign destination in violation of such laws.
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
From: John Halley Gotway
Time: Wed Feb 12 13:25:17 2014
Leela,
It looks like the mesonet data is not currently supported by the
madis2nc tool. However, it shouldn't be too difficult to add that
functionality. Perhaps we could work together to get that
implemented and tested. Could you send me a sample MADIS mesonet file
that you'd like to use?
Thanks,
John Halley Gotway
met_help at ucar.edu
On 02/12/2014 08:53 AM, Watson.Leela via RT wrote:
>
> Wed Feb 12 08:53:55 2014: Request 65414 was acted upon.
> Transaction: Ticket created by watson.leela at ensco.com
> Queue: met_help
> Subject: MADIS mesonet data
> Owner: Nobody
> Requestors: watson.leela at ensco.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>
>
> Hello,
>
> Is there currently a way to use the MADIS mesonet data in point-
stat? I have seen some archive met_help messages that indicate that it
is possible to reformat the mesonet data to ascii format and then run
it through ascii2nc, but I am looking for a more streamlined approach
such as madis2nc.
>
> Thanks!
>
> Leela Watson
>
> Leela R. Watson, PhD
> Meteorologist
> (321) 853-8264
> 1980 N. Atlantic Ave., Suite 830
> Cocoa Beach, FL 32931
> www.ensco.com
>
> [cid:image001.gif at 01CF27E0.B2A7C250]
> Innovation. Collaboration. Solutions. Success.
>
>
> ________________________________
> The information contained in this email message is intended only for
the use of the individual(s) to whom it is addressed and may contain
information that is privileged and sensitive. If you are not the
intended recipient, or otherwise have received this communication in
error, please notify the sender immediately by email at the above
referenced address and note that any further dissemination,
distribution or copying of this communication is strictly prohibited.
>
> The U.S. Export Control Laws regulate the export and re-export of
technology originating in the United States. This includes the
electronic transmission of information and software to foreign
countries and to certain foreign nationals. Recipient agrees to abide
by these laws and their regulations -- including the U.S. Department
of Commerce Export Administration Regulations and the U.S. Department
of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived
from this email to either a foreign national or a foreign destination
in violation of such laws.
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
From: Watson.Leela
Time: Wed Feb 26 05:59:35 2014
John,
Have you had a chance to look at possibly adding mesonet data to the
madis2nc tool?
Leela Watson
-----Original Message-----
From: Watson.Leela
Sent: Thursday, February 13, 2014 7:14 AM
To: 'met_help at ucar.edu'
Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
Thanks so much. I have attached the zipped file.
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, February 12, 2014 3:25 PM
To: Watson.Leela
Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
Leela,
It looks like the mesonet data is not currently supported by the
madis2nc tool. However, it shouldn't be too difficult to add that
functionality. Perhaps we could work together to get that implemented
and tested. Could you send me a sample MADIS mesonet file that you'd
like to use?
Thanks,
John Halley Gotway
met_help at ucar.edu
On 02/12/2014 08:53 AM, Watson.Leela via RT wrote:
>
> Wed Feb 12 08:53:55 2014: Request 65414 was acted upon.
> Transaction: Ticket created by watson.leela at ensco.com
> Queue: met_help
> Subject: MADIS mesonet data
> Owner: Nobody
> Requestors: watson.leela at ensco.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414
> >
>
>
> Hello,
>
> Is there currently a way to use the MADIS mesonet data in point-
stat? I have seen some archive met_help messages that indicate that it
is possible to reformat the mesonet data to ascii format and then run
it through ascii2nc, but I am looking for a more streamlined approach
such as madis2nc.
>
> Thanks!
>
> Leela Watson
>
> Leela R. Watson, PhD
> Meteorologist
> (321) 853-8264
> 1980 N. Atlantic Ave., Suite 830
> Cocoa Beach, FL 32931
> www.ensco.com
>
> [cid:image001.gif at 01CF27E0.B2A7C250]
> Innovation. Collaboration. Solutions. Success.
>
>
> ________________________________
> The information contained in this email message is intended only for
the use of the individual(s) to whom it is addressed and may contain
information that is privileged and sensitive. If you are not the
intended recipient, or otherwise have received this communication in
error, please notify the sender immediately by email at the above
referenced address and note that any further dissemination,
distribution or copying of this communication is strictly prohibited.
>
> The U.S. Export Control Laws regulate the export and re-export of
technology originating in the United States. This includes the
electronic transmission of information and software to foreign
countries and to certain foreign nationals. Recipient agrees to abide
by these laws and their regulations -- including the U.S. Department
of Commerce Export Administration Regulations and the U.S. Department
of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived
from this email to either a foreign national or a foreign destination
in violation of such laws.
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
From: John Halley Gotway
Time: Wed Feb 26 11:26:26 2014
Leela,
Can you please send me a sample MADIS mesonet data file?
Thanks,
John
On 02/26/2014 05:59 AM, Watson.Leela via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>
> John,
>
> Have you had a chance to look at possibly adding mesonet data to the
madis2nc tool?
>
> Leela Watson
>
> -----Original Message-----
> From: Watson.Leela
> Sent: Thursday, February 13, 2014 7:14 AM
> To: 'met_help at ucar.edu'
> Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> Thanks so much. I have attached the zipped file.
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, February 12, 2014 3:25 PM
> To: Watson.Leela
> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> Leela,
>
> It looks like the mesonet data is not currently supported by the
madis2nc tool. However, it shouldn't be too difficult to add that
functionality. Perhaps we could work together to get that implemented
and tested. Could you send me a sample MADIS mesonet file that you'd
like to use?
>
> Thanks,
> John Halley Gotway
> met_help at ucar.edu
>
> On 02/12/2014 08:53 AM, Watson.Leela via RT wrote:
>>
>> Wed Feb 12 08:53:55 2014: Request 65414 was acted upon.
>> Transaction: Ticket created by watson.leela at ensco.com
>> Queue: met_help
>> Subject: MADIS mesonet data
>> Owner: Nobody
>> Requestors: watson.leela at ensco.com
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414
>>>
>>
>>
>> Hello,
>>
>> Is there currently a way to use the MADIS mesonet data in point-
stat? I have seen some archive met_help messages that indicate that it
is possible to reformat the mesonet data to ascii format and then run
it through ascii2nc, but I am looking for a more streamlined approach
such as madis2nc.
>>
>> Thanks!
>>
>> Leela Watson
>>
>> Leela R. Watson, PhD
>> Meteorologist
>> (321) 853-8264
>> 1980 N. Atlantic Ave., Suite 830
>> Cocoa Beach, FL 32931
>> www.ensco.com
>>
>> [cid:image001.gif at 01CF27E0.B2A7C250]
>> Innovation. Collaboration. Solutions. Success.
>>
>>
>> ________________________________
>> The information contained in this email message is intended only
for the use of the individual(s) to whom it is addressed and may
contain information that is privileged and sensitive. If you are not
the intended recipient, or otherwise have received this communication
in error, please notify the sender immediately by email at the above
referenced address and note that any further dissemination,
distribution or copying of this communication is strictly prohibited.
>>
>> The U.S. Export Control Laws regulate the export and re-export of
technology originating in the United States. This includes the
electronic transmission of information and software to foreign
countries and to certain foreign nationals. Recipient agrees to abide
by these laws and their regulations -- including the U.S. Department
of Commerce Export Administration Regulations and the U.S. Department
of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived
from this email to either a foreign national or a foreign destination
in violation of such laws.
>>
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
From: Watson.Leela
Time: Wed Feb 26 11:48:38 2014
John,
I just sent the MADIS mesonet file, but I suspect you didn't receive
it (I also sent it on Feb. 13). The file size is 19 MB - is this too
large to come through the met_help email address?
Leela
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, February 26, 2014 1:26 PM
To: Watson.Leela
Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
Leela,
Can you please send me a sample MADIS mesonet data file?
Thanks,
John
On 02/26/2014 05:59 AM, Watson.Leela via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>
> John,
>
> Have you had a chance to look at possibly adding mesonet data to the
madis2nc tool?
>
> Leela Watson
>
> -----Original Message-----
> From: Watson.Leela
> Sent: Thursday, February 13, 2014 7:14 AM
> To: 'met_help at ucar.edu'
> Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> Thanks so much. I have attached the zipped file.
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, February 12, 2014 3:25 PM
> To: Watson.Leela
> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> Leela,
>
> It looks like the mesonet data is not currently supported by the
madis2nc tool. However, it shouldn't be too difficult to add that
functionality. Perhaps we could work together to get that implemented
and tested. Could you send me a sample MADIS mesonet file that you'd
like to use?
>
> Thanks,
> John Halley Gotway
> met_help at ucar.edu
>
> On 02/12/2014 08:53 AM, Watson.Leela via RT wrote:
>>
>> Wed Feb 12 08:53:55 2014: Request 65414 was acted upon.
>> Transaction: Ticket created by watson.leela at ensco.com
>> Queue: met_help
>> Subject: MADIS mesonet data
>> Owner: Nobody
>> Requestors: watson.leela at ensco.com
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414
>>>
>>
>>
>> Hello,
>>
>> Is there currently a way to use the MADIS mesonet data in point-
stat? I have seen some archive met_help messages that indicate that it
is possible to reformat the mesonet data to ascii format and then run
it through ascii2nc, but I am looking for a more streamlined approach
such as madis2nc.
>>
>> Thanks!
>>
>> Leela Watson
>>
>> Leela R. Watson, PhD
>> Meteorologist
>> (321) 853-8264
>> 1980 N. Atlantic Ave., Suite 830
>> Cocoa Beach, FL 32931
>> www.ensco.com
>>
>> [cid:image001.gif at 01CF27E0.B2A7C250]
>> Innovation. Collaboration. Solutions. Success.
>>
>>
>> ________________________________
>> The information contained in this email message is intended only
for the use of the individual(s) to whom it is addressed and may
contain information that is privileged and sensitive. If you are not
the intended recipient, or otherwise have received this communication
in error, please notify the sender immediately by email at the above
referenced address and note that any further dissemination,
distribution or copying of this communication is strictly prohibited.
>>
>> The U.S. Export Control Laws regulate the export and re-export of
technology originating in the United States. This includes the
electronic transmission of information and software to foreign
countries and to certain foreign nationals. Recipient agrees to abide
by these laws and their regulations -- including the U.S. Department
of Commerce Export Administration Regulations and the U.S. Department
of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived
from this email to either a foreign national or a foreign destination
in violation of such laws.
>>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
From: John Halley Gotway
Time: Wed Feb 26 11:50:49 2014
Leela,
Yes, that's probably true. Please post it to our anonymous ftp site
following these instructions:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
Thanks,
John
On 02/26/2014 11:48 AM, Watson.Leela via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>
> John,
>
> I just sent the MADIS mesonet file, but I suspect you didn't receive
it (I also sent it on Feb. 13). The file size is 19 MB - is this too
large to come through the met_help email address?
>
> Leela
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, February 26, 2014 1:26 PM
> To: Watson.Leela
> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> Leela,
>
> Can you please send me a sample MADIS mesonet data file?
>
> Thanks,
> John
>
> On 02/26/2014 05:59 AM, Watson.Leela via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>>
>> John,
>>
>> Have you had a chance to look at possibly adding mesonet data to
the madis2nc tool?
>>
>> Leela Watson
>>
>> -----Original Message-----
>> From: Watson.Leela
>> Sent: Thursday, February 13, 2014 7:14 AM
>> To: 'met_help at ucar.edu'
>> Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>
>> Thanks so much. I have attached the zipped file.
>>
>> -----Original Message-----
>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>> Sent: Wednesday, February 12, 2014 3:25 PM
>> To: Watson.Leela
>> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>
>> Leela,
>>
>> It looks like the mesonet data is not currently supported by the
madis2nc tool. However, it shouldn't be too difficult to add that
functionality. Perhaps we could work together to get that implemented
and tested. Could you send me a sample MADIS mesonet file that you'd
like to use?
>>
>> Thanks,
>> John Halley Gotway
>> met_help at ucar.edu
>>
>> On 02/12/2014 08:53 AM, Watson.Leela via RT wrote:
>>>
>>> Wed Feb 12 08:53:55 2014: Request 65414 was acted upon.
>>> Transaction: Ticket created by watson.leela at ensco.com
>>> Queue: met_help
>>> Subject: MADIS mesonet data
>>> Owner: Nobody
>>> Requestors: watson.leela at ensco.com
>>> Status: new
>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414
>>>>
>>>
>>>
>>> Hello,
>>>
>>> Is there currently a way to use the MADIS mesonet data in point-
stat? I have seen some archive met_help messages that indicate that it
is possible to reformat the mesonet data to ascii format and then run
it through ascii2nc, but I am looking for a more streamlined approach
such as madis2nc.
>>>
>>> Thanks!
>>>
>>> Leela Watson
>>>
>>> Leela R. Watson, PhD
>>> Meteorologist
>>> (321) 853-8264
>>> 1980 N. Atlantic Ave., Suite 830
>>> Cocoa Beach, FL 32931
>>> www.ensco.com
>>>
>>> [cid:image001.gif at 01CF27E0.B2A7C250]
>>> Innovation. Collaboration. Solutions. Success.
>>>
>>>
>>> ________________________________
>>> The information contained in this email message is intended only
for the use of the individual(s) to whom it is addressed and may
contain information that is privileged and sensitive. If you are not
the intended recipient, or otherwise have received this communication
in error, please notify the sender immediately by email at the above
referenced address and note that any further dissemination,
distribution or copying of this communication is strictly prohibited.
>>>
>>> The U.S. Export Control Laws regulate the export and re-export of
technology originating in the United States. This includes the
electronic transmission of information and software to foreign
countries and to certain foreign nationals. Recipient agrees to abide
by these laws and their regulations -- including the U.S. Department
of Commerce Export Administration Regulations and the U.S. Department
of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived
from this email to either a foreign national or a foreign destination
in violation of such laws.
>>>
>>
>>
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
From: Watson.Leela
Time: Wed Feb 26 11:54:40 2014
Okay...I have uploaded the file '20130910_0000.gz' to directory
'Watson'.
Leela
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, February 26, 2014 1:51 PM
To: Watson.Leela
Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
Leela,
Yes, that's probably true. Please post it to our anonymous ftp site
following these instructions:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
Thanks,
John
On 02/26/2014 11:48 AM, Watson.Leela via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>
> John,
>
> I just sent the MADIS mesonet file, but I suspect you didn't receive
it (I also sent it on Feb. 13). The file size is 19 MB - is this too
large to come through the met_help email address?
>
> Leela
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, February 26, 2014 1:26 PM
> To: Watson.Leela
> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> Leela,
>
> Can you please send me a sample MADIS mesonet data file?
>
> Thanks,
> John
>
> On 02/26/2014 05:59 AM, Watson.Leela via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>>
>> John,
>>
>> Have you had a chance to look at possibly adding mesonet data to
the madis2nc tool?
>>
>> Leela Watson
>>
>> -----Original Message-----
>> From: Watson.Leela
>> Sent: Thursday, February 13, 2014 7:14 AM
>> To: 'met_help at ucar.edu'
>> Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>
>> Thanks so much. I have attached the zipped file.
>>
>> -----Original Message-----
>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>> Sent: Wednesday, February 12, 2014 3:25 PM
>> To: Watson.Leela
>> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>
>> Leela,
>>
>> It looks like the mesonet data is not currently supported by the
madis2nc tool. However, it shouldn't be too difficult to add that
functionality. Perhaps we could work together to get that implemented
and tested. Could you send me a sample MADIS mesonet file that you'd
like to use?
>>
>> Thanks,
>> John Halley Gotway
>> met_help at ucar.edu
>>
>> On 02/12/2014 08:53 AM, Watson.Leela via RT wrote:
>>>
>>> Wed Feb 12 08:53:55 2014: Request 65414 was acted upon.
>>> Transaction: Ticket created by watson.leela at ensco.com
>>> Queue: met_help
>>> Subject: MADIS mesonet data
>>> Owner: Nobody
>>> Requestors: watson.leela at ensco.com
>>> Status: new
>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414
>>>>
>>>
>>>
>>> Hello,
>>>
>>> Is there currently a way to use the MADIS mesonet data in point-
stat? I have seen some archive met_help messages that indicate that it
is possible to reformat the mesonet data to ascii format and then run
it through ascii2nc, but I am looking for a more streamlined approach
such as madis2nc.
>>>
>>> Thanks!
>>>
>>> Leela Watson
>>>
>>> Leela R. Watson, PhD
>>> Meteorologist
>>> (321) 853-8264
>>> 1980 N. Atlantic Ave., Suite 830
>>> Cocoa Beach, FL 32931
>>> www.ensco.com
>>>
>>> [cid:image001.gif at 01CF27E0.B2A7C250]
>>> Innovation. Collaboration. Solutions. Success.
>>>
>>>
>>> ________________________________
>>> The information contained in this email message is intended only
for the use of the individual(s) to whom it is addressed and may
contain information that is privileged and sensitive. If you are not
the intended recipient, or otherwise have received this communication
in error, please notify the sender immediately by email at the above
referenced address and note that any further dissemination,
distribution or copying of this communication is strictly prohibited.
>>>
>>> The U.S. Export Control Laws regulate the export and re-export of
technology originating in the United States. This includes the
electronic transmission of information and software to foreign
countries and to certain foreign nationals. Recipient agrees to abide
by these laws and their regulations -- including the U.S. Department
of Commerce Export Administration Regulations and the U.S. Department
of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived
from this email to either a foreign national or a foreign destination
in violation of such laws.
>>>
>>
>>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
From: John Halley Gotway
Time: Wed Feb 26 11:57:39 2014
Leela,
Great, I have it now. I'll let you know when I've made progress.
Thanks,
John
On 02/26/2014 11:54 AM, Watson.Leela via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>
> Okay...I have uploaded the file '20130910_0000.gz' to directory
'Watson'.
>
> Leela
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, February 26, 2014 1:51 PM
> To: Watson.Leela
> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> Leela,
>
> Yes, that's probably true. Please post it to our anonymous ftp site
following these instructions:
> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>
> Thanks,
> John
>
> On 02/26/2014 11:48 AM, Watson.Leela via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>>
>> John,
>>
>> I just sent the MADIS mesonet file, but I suspect you didn't
receive it (I also sent it on Feb. 13). The file size is 19 MB - is
this too large to come through the met_help email address?
>>
>> Leela
>>
>> -----Original Message-----
>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>> Sent: Wednesday, February 26, 2014 1:26 PM
>> To: Watson.Leela
>> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>
>> Leela,
>>
>> Can you please send me a sample MADIS mesonet data file?
>>
>> Thanks,
>> John
>>
>> On 02/26/2014 05:59 AM, Watson.Leela via RT wrote:
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>>>
>>> John,
>>>
>>> Have you had a chance to look at possibly adding mesonet data to
the madis2nc tool?
>>>
>>> Leela Watson
>>>
>>> -----Original Message-----
>>> From: Watson.Leela
>>> Sent: Thursday, February 13, 2014 7:14 AM
>>> To: 'met_help at ucar.edu'
>>> Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>>
>>> Thanks so much. I have attached the zipped file.
>>>
>>> -----Original Message-----
>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>> Sent: Wednesday, February 12, 2014 3:25 PM
>>> To: Watson.Leela
>>> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>>
>>> Leela,
>>>
>>> It looks like the mesonet data is not currently supported by the
madis2nc tool. However, it shouldn't be too difficult to add that
functionality. Perhaps we could work together to get that implemented
and tested. Could you send me a sample MADIS mesonet file that you'd
like to use?
>>>
>>> Thanks,
>>> John Halley Gotway
>>> met_help at ucar.edu
>>>
>>> On 02/12/2014 08:53 AM, Watson.Leela via RT wrote:
>>>>
>>>> Wed Feb 12 08:53:55 2014: Request 65414 was acted upon.
>>>> Transaction: Ticket created by watson.leela at ensco.com
>>>> Queue: met_help
>>>> Subject: MADIS mesonet data
>>>> Owner: Nobody
>>>> Requestors: watson.leela at ensco.com
>>>> Status: new
>>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414
>>>>>
>>>>
>>>>
>>>> Hello,
>>>>
>>>> Is there currently a way to use the MADIS mesonet data in point-
stat? I have seen some archive met_help messages that indicate that it
is possible to reformat the mesonet data to ascii format and then run
it through ascii2nc, but I am looking for a more streamlined approach
such as madis2nc.
>>>>
>>>> Thanks!
>>>>
>>>> Leela Watson
>>>>
>>>> Leela R. Watson, PhD
>>>> Meteorologist
>>>> (321) 853-8264
>>>> 1980 N. Atlantic Ave., Suite 830
>>>> Cocoa Beach, FL 32931
>>>> www.ensco.com
>>>>
>>>> [cid:image001.gif at 01CF27E0.B2A7C250]
>>>> Innovation. Collaboration. Solutions. Success.
>>>>
>>>>
>>>> ________________________________
>>>> The information contained in this email message is intended only
for the use of the individual(s) to whom it is addressed and may
contain information that is privileged and sensitive. If you are not
the intended recipient, or otherwise have received this communication
in error, please notify the sender immediately by email at the above
referenced address and note that any further dissemination,
distribution or copying of this communication is strictly prohibited.
>>>>
>>>> The U.S. Export Control Laws regulate the export and re-export of
technology originating in the United States. This includes the
electronic transmission of information and software to foreign
countries and to certain foreign nationals. Recipient agrees to abide
by these laws and their regulations -- including the U.S. Department
of Commerce Export Administration Regulations and the U.S. Department
of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived
from this email to either a foreign national or a foreign destination
in violation of such laws.
>>>>
>>>
>>>
>>
>>
>
>
------------------------------------------------
Subject: MADIS mesonet data
From: John Halley Gotway
Time: Fri Feb 28 10:35:49 2014
Leela,
I've worked on this a bit and have attached updated versions of
madis2nc.h/.cc. The "process_madis_mesonet()" function I added maps
the following input NetCDF variable names to GRIB codes listed
below. Here's where the GRIB codes are defined:
http://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html
- temperature -> 11
- dewpoint -> 17
- relHumidity -> 52
- stationPressure -> 1
- sealLevelPressure -> 2
- windDir -> 31
- windSpeed -> 32
- convert wind direction and wind speed to U and V components -> 33,
34
- windGust -> 180
- visibility -> 20
- precipRate -> 59
- solarRadiation -> 250
- seaSurfaceTemp -> 80
- totalColumnPWV -> 54
- soilTemperature -> 85
- minTemp24Hour -> 16
- maxTemp24Hour -> 15
- precip3hr, precip12hr, precip10min, precip1min -> 61 (with different
accumulation intervals)
- windDir10 -> 31 (with height = 10)
- windSpeed10 -> 32 (with height = 10)
- convert 10m speed and direction to U and V components -> 33, 34
(with height = 10)
There are some input NetCDF variables for which I couldn't find a
mapping to a GRIB code. By convention, the MET tools associate each
point observation type with a corresponding GRIB code. I have
two main questions remaining...
(1) Are the mappings that I've used above correct?
(2) Do the units used in the input NetCDF files match the prescribed
units for that GRIB code? Or do I need to do some unit conversion?
Please try replacing the METv4.1 versions of madis2nc.h/.cc and
recompile. And then try running some mesonet data through it. And
please let me know how it looks to you - any questions or issues?
FYI - running madis2nc a verbosity level 3 or higher (-v 3) prints out
very detailed information about the observations being processed.
Thanks,
John
On 02/26/2014 05:59 AM, Watson.Leela via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>
> John,
>
> Have you had a chance to look at possibly adding mesonet data to the
madis2nc tool?
>
> Leela Watson
>
> -----Original Message-----
> From: Watson.Leela
> Sent: Thursday, February 13, 2014 7:14 AM
> To: 'met_help at ucar.edu'
> Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> Thanks so much. I have attached the zipped file.
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, February 12, 2014 3:25 PM
> To: Watson.Leela
> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> Leela,
>
> It looks like the mesonet data is not currently supported by the
madis2nc tool. However, it shouldn't be too difficult to add that
functionality. Perhaps we could work together to get that implemented
and tested. Could you send me a sample MADIS mesonet file that you'd
like to use?
>
> Thanks,
> John Halley Gotway
> met_help at ucar.edu
>
> On 02/12/2014 08:53 AM, Watson.Leela via RT wrote:
>>
>> Wed Feb 12 08:53:55 2014: Request 65414 was acted upon.
>> Transaction: Ticket created by watson.leela at ensco.com
>> Queue: met_help
>> Subject: MADIS mesonet data
>> Owner: Nobody
>> Requestors: watson.leela at ensco.com
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414
>>>
>>
>>
>> Hello,
>>
>> Is there currently a way to use the MADIS mesonet data in point-
stat? I have seen some archive met_help messages that indicate that it
is possible to reformat the mesonet data to ascii format and then run
it through ascii2nc, but I am looking for a more streamlined approach
such as madis2nc.
>>
>> Thanks!
>>
>> Leela Watson
>>
>> Leela R. Watson, PhD
>> Meteorologist
>> (321) 853-8264
>> 1980 N. Atlantic Ave., Suite 830
>> Cocoa Beach, FL 32931
>> www.ensco.com
>>
>> [cid:image001.gif at 01CF27E0.B2A7C250]
>> Innovation. Collaboration. Solutions. Success.
>>
>>
>> ________________________________
>> The information contained in this email message is intended only
for the use of the individual(s) to whom it is addressed and may
contain information that is privileged and sensitive. If you are not
the intended recipient, or otherwise have received this communication
in error, please notify the sender immediately by email at the above
referenced address and note that any further dissemination,
distribution or copying of this communication is strictly prohibited.
>>
>> The U.S. Export Control Laws regulate the export and re-export of
technology originating in the United States. This includes the
electronic transmission of information and software to foreign
countries and to certain foreign nationals. Recipient agrees to abide
by these laws and their regulations -- including the U.S. Department
of Commerce Export Administration Regulations and the U.S. Department
of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived
from this email to either a foreign national or a foreign destination
in violation of such laws.
>>
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
From: Watson.Leela
Time: Mon Mar 03 05:24:33 2014
Thanks John. I will work on it and let you know how it works.
Leela
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Friday, February 28, 2014 12:36 PM
To: Watson.Leela
Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
Leela,
I've worked on this a bit and have attached updated versions of
madis2nc.h/.cc. The "process_madis_mesonet()" function I added maps
the following input NetCDF variable names to GRIB codes listed below.
Here's where the GRIB codes are defined:
http://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html
- temperature -> 11
- dewpoint -> 17
- relHumidity -> 52
- stationPressure -> 1
- sealLevelPressure -> 2
- windDir -> 31
- windSpeed -> 32
- convert wind direction and wind speed to U and V components -> 33,
34
- windGust -> 180
- visibility -> 20
- precipRate -> 59
- solarRadiation -> 250
- seaSurfaceTemp -> 80
- totalColumnPWV -> 54
- soilTemperature -> 85
- minTemp24Hour -> 16
- maxTemp24Hour -> 15
- precip3hr, precip12hr, precip10min, precip1min -> 61 (with different
accumulation intervals)
- windDir10 -> 31 (with height = 10)
- windSpeed10 -> 32 (with height = 10)
- convert 10m speed and direction to U and V components -> 33, 34
(with height = 10)
There are some input NetCDF variables for which I couldn't find a
mapping to a GRIB code. By convention, the MET tools associate each
point observation type with a corresponding GRIB code. I have two
main questions remaining...
(1) Are the mappings that I've used above correct?
(2) Do the units used in the input NetCDF files match the prescribed
units for that GRIB code? Or do I need to do some unit conversion?
Please try replacing the METv4.1 versions of madis2nc.h/.cc and
recompile. And then try running some mesonet data through it. And
please let me know how it looks to you - any questions or issues?
FYI - running madis2nc a verbosity level 3 or higher (-v 3) prints out
very detailed information about the observations being processed.
Thanks,
John
On 02/26/2014 05:59 AM, Watson.Leela via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>
> John,
>
> Have you had a chance to look at possibly adding mesonet data to the
madis2nc tool?
>
> Leela Watson
>
> -----Original Message-----
> From: Watson.Leela
> Sent: Thursday, February 13, 2014 7:14 AM
> To: 'met_help at ucar.edu'
> Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> Thanks so much. I have attached the zipped file.
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, February 12, 2014 3:25 PM
> To: Watson.Leela
> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> Leela,
>
> It looks like the mesonet data is not currently supported by the
madis2nc tool. However, it shouldn't be too difficult to add that
functionality. Perhaps we could work together to get that implemented
and tested. Could you send me a sample MADIS mesonet file that you'd
like to use?
>
> Thanks,
> John Halley Gotway
> met_help at ucar.edu
>
> On 02/12/2014 08:53 AM, Watson.Leela via RT wrote:
>>
>> Wed Feb 12 08:53:55 2014: Request 65414 was acted upon.
>> Transaction: Ticket created by watson.leela at ensco.com
>> Queue: met_help
>> Subject: MADIS mesonet data
>> Owner: Nobody
>> Requestors: watson.leela at ensco.com
>> Status: new
>> Ticket <URL:
>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414
>>>
>>
>>
>> Hello,
>>
>> Is there currently a way to use the MADIS mesonet data in point-
stat? I have seen some archive met_help messages that indicate that it
is possible to reformat the mesonet data to ascii format and then run
it through ascii2nc, but I am looking for a more streamlined approach
such as madis2nc.
>>
>> Thanks!
>>
>> Leela Watson
>>
>> Leela R. Watson, PhD
>> Meteorologist
>> (321) 853-8264
>> 1980 N. Atlantic Ave., Suite 830
>> Cocoa Beach, FL 32931
>> www.ensco.com
>>
>> [cid:image001.gif at 01CF27E0.B2A7C250]
>> Innovation. Collaboration. Solutions. Success.
>>
>>
>> ________________________________
>> The information contained in this email message is intended only
for the use of the individual(s) to whom it is addressed and may
contain information that is privileged and sensitive. If you are not
the intended recipient, or otherwise have received this communication
in error, please notify the sender immediately by email at the above
referenced address and note that any further dissemination,
distribution or copying of this communication is strictly prohibited.
>>
>> The U.S. Export Control Laws regulate the export and re-export of
technology originating in the United States. This includes the
electronic transmission of information and software to foreign
countries and to certain foreign nationals. Recipient agrees to abide
by these laws and their regulations -- including the U.S. Department
of Commerce Export Administration Regulations and the U.S. Department
of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived
from this email to either a foreign national or a foreign destination
in violation of such laws.
>>
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
From: Watson.Leela
Time: Wed Mar 05 06:37:57 2014
John,
Everything looks good except for the units for totalColumnPWV and
precipRate. totalColumnPWV is in centimeters in the NetCDF mesonet
file, but in the GRIB code it is listed as mm. precipRate is in
meters/second in the NetCDF file, but is in millimeters/second in the
GRIB code. So these two variables need unit conversion. I would do it
myself, but I really have no knowledge about reading/writing NetCDF!
Otherwise, everything else looks good.
Leela
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Friday, February 28, 2014 12:36 PM
To: Watson.Leela
Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
Leela,
I've worked on this a bit and have attached updated versions of
madis2nc.h/.cc. The "process_madis_mesonet()" function I added maps
the following input NetCDF variable names to GRIB codes listed below.
Here's where the GRIB codes are defined:
http://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html
- temperature -> 11
- dewpoint -> 17
- relHumidity -> 52
- stationPressure -> 1
- sealLevelPressure -> 2
- windDir -> 31
- windSpeed -> 32
- convert wind direction and wind speed to U and V components -> 33,
34
- windGust -> 180
- visibility -> 20
- precipRate -> 59
- solarRadiation -> 250
- seaSurfaceTemp -> 80
- totalColumnPWV -> 54
- soilTemperature -> 85
- minTemp24Hour -> 16
- maxTemp24Hour -> 15
- precip3hr, precip12hr, precip10min, precip1min -> 61 (with different
accumulation intervals)
- windDir10 -> 31 (with height = 10)
- windSpeed10 -> 32 (with height = 10)
- convert 10m speed and direction to U and V components -> 33, 34
(with height = 10)
There are some input NetCDF variables for which I couldn't find a
mapping to a GRIB code. By convention, the MET tools associate each
point observation type with a corresponding GRIB code. I have two
main questions remaining...
(1) Are the mappings that I've used above correct?
(2) Do the units used in the input NetCDF files match the prescribed
units for that GRIB code? Or do I need to do some unit conversion?
Please try replacing the METv4.1 versions of madis2nc.h/.cc and
recompile. And then try running some mesonet data through it. And
please let me know how it looks to you - any questions or issues?
FYI - running madis2nc a verbosity level 3 or higher (-v 3) prints out
very detailed information about the observations being processed.
Thanks,
John
On 02/26/2014 05:59 AM, Watson.Leela via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>
> John,
>
> Have you had a chance to look at possibly adding mesonet data to the
madis2nc tool?
>
> Leela Watson
>
> -----Original Message-----
> From: Watson.Leela
> Sent: Thursday, February 13, 2014 7:14 AM
> To: 'met_help at ucar.edu'
> Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> Thanks so much. I have attached the zipped file.
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, February 12, 2014 3:25 PM
> To: Watson.Leela
> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> Leela,
>
> It looks like the mesonet data is not currently supported by the
madis2nc tool. However, it shouldn't be too difficult to add that
functionality. Perhaps we could work together to get that implemented
and tested. Could you send me a sample MADIS mesonet file that you'd
like to use?
>
> Thanks,
> John Halley Gotway
> met_help at ucar.edu
>
> On 02/12/2014 08:53 AM, Watson.Leela via RT wrote:
>>
>> Wed Feb 12 08:53:55 2014: Request 65414 was acted upon.
>> Transaction: Ticket created by watson.leela at ensco.com
>> Queue: met_help
>> Subject: MADIS mesonet data
>> Owner: Nobody
>> Requestors: watson.leela at ensco.com
>> Status: new
>> Ticket <URL:
>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414
>>>
>>
>>
>> Hello,
>>
>> Is there currently a way to use the MADIS mesonet data in point-
stat? I have seen some archive met_help messages that indicate that it
is possible to reformat the mesonet data to ascii format and then run
it through ascii2nc, but I am looking for a more streamlined approach
such as madis2nc.
>>
>> Thanks!
>>
>> Leela Watson
>>
>> Leela R. Watson, PhD
>> Meteorologist
>> (321) 853-8264
>> 1980 N. Atlantic Ave., Suite 830
>> Cocoa Beach, FL 32931
>> www.ensco.com
>>
>> [cid:image001.gif at 01CF27E0.B2A7C250]
>> Innovation. Collaboration. Solutions. Success.
>>
>>
>> ________________________________
>> The information contained in this email message is intended only
for the use of the individual(s) to whom it is addressed and may
contain information that is privileged and sensitive. If you are not
the intended recipient, or otherwise have received this communication
in error, please notify the sender immediately by email at the above
referenced address and note that any further dissemination,
distribution or copying of this communication is strictly prohibited.
>>
>> The U.S. Export Control Laws regulate the export and re-export of
technology originating in the United States. This includes the
electronic transmission of information and software to foreign
countries and to certain foreign nationals. Recipient agrees to abide
by these laws and their regulations -- including the U.S. Department
of Commerce Export Administration Regulations and the U.S. Department
of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived
from this email to either a foreign national or a foreign destination
in violation of such laws.
>>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
From: John Halley Gotway
Time: Wed Mar 05 11:52:47 2014
Leela,
Thanks for letting me know. When I get a chance, I'll update the
logic in the madis2nc tool to perform that unit conversion and send
you an updated version.
I may not get to it today but hope to get it done by tomorrow.
Thanks,
John
On 03/05/2014 06:37 AM, Watson.Leela via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>
> John,
>
> Everything looks good except for the units for totalColumnPWV and
precipRate. totalColumnPWV is in centimeters in the NetCDF mesonet
file, but in the GRIB code it is listed as mm. precipRate is in
meters/second in the NetCDF file, but is in millimeters/second in the
GRIB code. So these two variables need unit conversion. I would do it
myself, but I really have no knowledge about reading/writing NetCDF!
Otherwise, everything else looks good.
>
> Leela
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Friday, February 28, 2014 12:36 PM
> To: Watson.Leela
> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> Leela,
>
> I've worked on this a bit and have attached updated versions of
madis2nc.h/.cc. The "process_madis_mesonet()" function I added maps
the following input NetCDF variable names to GRIB codes listed below.
Here's where the GRIB codes are defined:
> http://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html
>
> - temperature -> 11
> - dewpoint -> 17
> - relHumidity -> 52
> - stationPressure -> 1
> - sealLevelPressure -> 2
> - windDir -> 31
> - windSpeed -> 32
> - convert wind direction and wind speed to U and V components -> 33,
34
> - windGust -> 180
> - visibility -> 20
> - precipRate -> 59
> - solarRadiation -> 250
> - seaSurfaceTemp -> 80
> - totalColumnPWV -> 54
> - soilTemperature -> 85
> - minTemp24Hour -> 16
> - maxTemp24Hour -> 15
> - precip3hr, precip12hr, precip10min, precip1min -> 61 (with
different accumulation intervals)
> - windDir10 -> 31 (with height = 10)
> - windSpeed10 -> 32 (with height = 10)
> - convert 10m speed and direction to U and V components -> 33, 34
(with height = 10)
>
> There are some input NetCDF variables for which I couldn't find a
mapping to a GRIB code. By convention, the MET tools associate each
point observation type with a corresponding GRIB code. I have two
main questions remaining...
> (1) Are the mappings that I've used above correct?
> (2) Do the units used in the input NetCDF files match the prescribed
units for that GRIB code? Or do I need to do some unit conversion?
>
> Please try replacing the METv4.1 versions of madis2nc.h/.cc and
recompile. And then try running some mesonet data through it. And
please let me know how it looks to you - any questions or issues?
>
> FYI - running madis2nc a verbosity level 3 or higher (-v 3) prints
out very detailed information about the observations being processed.
>
> Thanks,
> John
>
> On 02/26/2014 05:59 AM, Watson.Leela via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>>
>> John,
>>
>> Have you had a chance to look at possibly adding mesonet data to
the madis2nc tool?
>>
>> Leela Watson
>>
>> -----Original Message-----
>> From: Watson.Leela
>> Sent: Thursday, February 13, 2014 7:14 AM
>> To: 'met_help at ucar.edu'
>> Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>
>> Thanks so much. I have attached the zipped file.
>>
>> -----Original Message-----
>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>> Sent: Wednesday, February 12, 2014 3:25 PM
>> To: Watson.Leela
>> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>
>> Leela,
>>
>> It looks like the mesonet data is not currently supported by the
madis2nc tool. However, it shouldn't be too difficult to add that
functionality. Perhaps we could work together to get that implemented
and tested. Could you send me a sample MADIS mesonet file that you'd
like to use?
>>
>> Thanks,
>> John Halley Gotway
>> met_help at ucar.edu
>>
>> On 02/12/2014 08:53 AM, Watson.Leela via RT wrote:
>>>
>>> Wed Feb 12 08:53:55 2014: Request 65414 was acted upon.
>>> Transaction: Ticket created by watson.leela at ensco.com
>>> Queue: met_help
>>> Subject: MADIS mesonet data
>>> Owner: Nobody
>>> Requestors: watson.leela at ensco.com
>>> Status: new
>>> Ticket <URL:
>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414
>>>>
>>>
>>>
>>> Hello,
>>>
>>> Is there currently a way to use the MADIS mesonet data in point-
stat? I have seen some archive met_help messages that indicate that it
is possible to reformat the mesonet data to ascii format and then run
it through ascii2nc, but I am looking for a more streamlined approach
such as madis2nc.
>>>
>>> Thanks!
>>>
>>> Leela Watson
>>>
>>> Leela R. Watson, PhD
>>> Meteorologist
>>> (321) 853-8264
>>> 1980 N. Atlantic Ave., Suite 830
>>> Cocoa Beach, FL 32931
>>> www.ensco.com
>>>
>>> [cid:image001.gif at 01CF27E0.B2A7C250]
>>> Innovation. Collaboration. Solutions. Success.
>>>
>>>
>>> ________________________________
>>> The information contained in this email message is intended only
for the use of the individual(s) to whom it is addressed and may
contain information that is privileged and sensitive. If you are not
the intended recipient, or otherwise have received this communication
in error, please notify the sender immediately by email at the above
referenced address and note that any further dissemination,
distribution or copying of this communication is strictly prohibited.
>>>
>>> The U.S. Export Control Laws regulate the export and re-export of
technology originating in the United States. This includes the
electronic transmission of information and software to foreign
countries and to certain foreign nationals. Recipient agrees to abide
by these laws and their regulations -- including the U.S. Department
of Commerce Export Administration Regulations and the U.S. Department
of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived
from this email to either a foreign national or a foreign destination
in violation of such laws.
>>>
>>
>>
>
>
------------------------------------------------
Subject: MADIS mesonet data
From: John Halley Gotway
Time: Thu Mar 06 16:58:20 2014
Leela,
Thanks for catching those unit conversion issues. I modified two
lines of the madis2nc.cc file:
1665 process_obs(f_in, "precipRate", cur, dim, 59, 1000.0,
1675 process_obs(f_in, "totalColumnPWV", cur, dim, 54, 10.0,
I'm not specifying conversion factors for those two variables. The
input precipRate value is now multiplied by 1000, and the input
precipitable water is now multiplied by 10 before writing them to
the output file.
The updated version of madis2nc.cc is attached.
Please let me know if you run into any more issues. If this all works
fine, I'll include these changes in the next official release of MET.
Thanks!
John
On 03/05/2014 06:37 AM, Watson.Leela via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>
> John,
>
> Everything looks good except for the units for totalColumnPWV and
precipRate. totalColumnPWV is in centimeters in the NetCDF mesonet
file, but in the GRIB code it is listed as mm. precipRate is in
meters/second in the NetCDF file, but is in millimeters/second in the
GRIB code. So these two variables need unit conversion. I would do it
myself, but I really have no knowledge about reading/writing NetCDF!
Otherwise, everything else looks good.
>
> Leela
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Friday, February 28, 2014 12:36 PM
> To: Watson.Leela
> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> Leela,
>
> I've worked on this a bit and have attached updated versions of
madis2nc.h/.cc. The "process_madis_mesonet()" function I added maps
the following input NetCDF variable names to GRIB codes listed below.
Here's where the GRIB codes are defined:
> http://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html
>
> - temperature -> 11
> - dewpoint -> 17
> - relHumidity -> 52
> - stationPressure -> 1
> - sealLevelPressure -> 2
> - windDir -> 31
> - windSpeed -> 32
> - convert wind direction and wind speed to U and V components -> 33,
34
> - windGust -> 180
> - visibility -> 20
> - precipRate -> 59
> - solarRadiation -> 250
> - seaSurfaceTemp -> 80
> - totalColumnPWV -> 54
> - soilTemperature -> 85
> - minTemp24Hour -> 16
> - maxTemp24Hour -> 15
> - precip3hr, precip12hr, precip10min, precip1min -> 61 (with
different accumulation intervals)
> - windDir10 -> 31 (with height = 10)
> - windSpeed10 -> 32 (with height = 10)
> - convert 10m speed and direction to U and V components -> 33, 34
(with height = 10)
>
> There are some input NetCDF variables for which I couldn't find a
mapping to a GRIB code. By convention, the MET tools associate each
point observation type with a corresponding GRIB code. I have two
main questions remaining...
> (1) Are the mappings that I've used above correct?
> (2) Do the units used in the input NetCDF files match the prescribed
units for that GRIB code? Or do I need to do some unit conversion?
>
> Please try replacing the METv4.1 versions of madis2nc.h/.cc and
recompile. And then try running some mesonet data through it. And
please let me know how it looks to you - any questions or issues?
>
> FYI - running madis2nc a verbosity level 3 or higher (-v 3) prints
out very detailed information about the observations being processed.
>
> Thanks,
> John
>
> On 02/26/2014 05:59 AM, Watson.Leela via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>>
>> John,
>>
>> Have you had a chance to look at possibly adding mesonet data to
the madis2nc tool?
>>
>> Leela Watson
>>
>> -----Original Message-----
>> From: Watson.Leela
>> Sent: Thursday, February 13, 2014 7:14 AM
>> To: 'met_help at ucar.edu'
>> Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>
>> Thanks so much. I have attached the zipped file.
>>
>> -----Original Message-----
>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>> Sent: Wednesday, February 12, 2014 3:25 PM
>> To: Watson.Leela
>> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>
>> Leela,
>>
>> It looks like the mesonet data is not currently supported by the
madis2nc tool. However, it shouldn't be too difficult to add that
functionality. Perhaps we could work together to get that implemented
and tested. Could you send me a sample MADIS mesonet file that you'd
like to use?
>>
>> Thanks,
>> John Halley Gotway
>> met_help at ucar.edu
>>
>> On 02/12/2014 08:53 AM, Watson.Leela via RT wrote:
>>>
>>> Wed Feb 12 08:53:55 2014: Request 65414 was acted upon.
>>> Transaction: Ticket created by watson.leela at ensco.com
>>> Queue: met_help
>>> Subject: MADIS mesonet data
>>> Owner: Nobody
>>> Requestors: watson.leela at ensco.com
>>> Status: new
>>> Ticket <URL:
>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414
>>>>
>>>
>>>
>>> Hello,
>>>
>>> Is there currently a way to use the MADIS mesonet data in point-
stat? I have seen some archive met_help messages that indicate that it
is possible to reformat the mesonet data to ascii format and then run
it through ascii2nc, but I am looking for a more streamlined approach
such as madis2nc.
>>>
>>> Thanks!
>>>
>>> Leela Watson
>>>
>>> Leela R. Watson, PhD
>>> Meteorologist
>>> (321) 853-8264
>>> 1980 N. Atlantic Ave., Suite 830
>>> Cocoa Beach, FL 32931
>>> www.ensco.com
>>>
>>> [cid:image001.gif at 01CF27E0.B2A7C250]
>>> Innovation. Collaboration. Solutions. Success.
>>>
>>>
>>> ________________________________
>>> The information contained in this email message is intended only
for the use of the individual(s) to whom it is addressed and may
contain information that is privileged and sensitive. If you are not
the intended recipient, or otherwise have received this communication
in error, please notify the sender immediately by email at the above
referenced address and note that any further dissemination,
distribution or copying of this communication is strictly prohibited.
>>>
>>> The U.S. Export Control Laws regulate the export and re-export of
technology originating in the United States. This includes the
electronic transmission of information and software to foreign
countries and to certain foreign nationals. Recipient agrees to abide
by these laws and their regulations -- including the U.S. Department
of Commerce Export Administration Regulations and the U.S. Department
of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived
from this email to either a foreign national or a foreign destination
in violation of such laws.
>>>
>>
>>
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
From: Watson.Leela
Time: Thu Mar 13 08:23:15 2014
John,
I am running into some problems with the mesonet data in point_stat.
The updated code for madis2nc works great. But when I try to run
point_stat using the mesonet data, I am not getting any matched pairs.
I have looked at the mesonet output from madis2nc and there looks to
me like there are some data points that fall within my WRF domain.
However, when I run point_stat it is telling me that there is a level
mismatch (here is part of the output):
DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type ADPSFC,
over region FULL, for interpolation method UW_MEAN(1), using 0 pairs.
DEBUG 3: Number of matched pairs = 0
DEBUG 3: Observations processed = 721845
DEBUG 3: Rejected: GRIB code = 636758
DEBUG 3: Rejected: valid time = 0
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 84984
DEBUG 3: Rejected: level mismatch = 103
DEBUG 3: Rejected: quality marker = 0
DEBUG 3: Rejected: message type = 0
DEBUG 3: Rejected: masking region = 0
DEBUG 3: Rejected: bad fcst value = 0
DEBUG 3: Rejected: duplicates = 0
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Processing DPT/Z2 versus DPT/Z2, for observation type ADPSFC,
over region FULL, for interpolation method UW_MEAN(1), using 0 pairs.
DEBUG 3: Number of matched pairs = 0
DEBUG 3: Observations processed = 721845
DEBUG 3: Rejected: GRIB code = 648350
DEBUG 3: Rejected: valid time = 0
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 73402
DEBUG 3: Rejected: level mismatch = 93
DEBUG 3: Rejected: quality marker = 0
DEBUG 3: Rejected: message type = 0
DEBUG 3: Rejected: masking region = 0
DEBUG 3: Rejected: bad fcst value = 0
DEBUG 3: Rejected: duplicates = 0
DEBUG 2:
The mesonet output from madis2nc looks very similar to the metar
output (same grib codes etc) and I have no problems getting matched
pairs from point_stat using the metar data (using the same
PointStatConfig file options). Is there something that I am missing?
I have uploaded my raw mesonet data (mesonet_20130924_1800), mesonet
data that has been run through madis2nc (meso_out.nc), and a WRF
forecast file (2013092412_d02.06) to the anonymous ftp site for you to
look at if you would like (located under 'Watson').
Thanks,
Leela
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Thursday, March 06, 2014 6:58 PM
To: Watson.Leela
Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
Leela,
Thanks for catching those unit conversion issues. I modified two
lines of the madis2nc.cc file:
1665 process_obs(f_in, "precipRate", cur, dim, 59, 1000.0,
1675 process_obs(f_in, "totalColumnPWV", cur, dim, 54, 10.0,
I'm not specifying conversion factors for those two variables. The
input precipRate value is now multiplied by 1000, and the input
precipitable water is now multiplied by 10 before writing them to the
output file.
The updated version of madis2nc.cc is attached.
Please let me know if you run into any more issues. If this all works
fine, I'll include these changes in the next official release of MET.
Thanks!
John
On 03/05/2014 06:37 AM, Watson.Leela via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>
> John,
>
> Everything looks good except for the units for totalColumnPWV and
precipRate. totalColumnPWV is in centimeters in the NetCDF mesonet
file, but in the GRIB code it is listed as mm. precipRate is in
meters/second in the NetCDF file, but is in millimeters/second in the
GRIB code. So these two variables need unit conversion. I would do it
myself, but I really have no knowledge about reading/writing NetCDF!
Otherwise, everything else looks good.
>
> Leela
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Friday, February 28, 2014 12:36 PM
> To: Watson.Leela
> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> Leela,
>
> I've worked on this a bit and have attached updated versions of
madis2nc.h/.cc. The "process_madis_mesonet()" function I added maps
the following input NetCDF variable names to GRIB codes listed below.
Here's where the GRIB codes are defined:
> http://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html
>
> - temperature -> 11
> - dewpoint -> 17
> - relHumidity -> 52
> - stationPressure -> 1
> - sealLevelPressure -> 2
> - windDir -> 31
> - windSpeed -> 32
> - convert wind direction and wind speed to U and V components -> 33,
> 34
> - windGust -> 180
> - visibility -> 20
> - precipRate -> 59
> - solarRadiation -> 250
> - seaSurfaceTemp -> 80
> - totalColumnPWV -> 54
> - soilTemperature -> 85
> - minTemp24Hour -> 16
> - maxTemp24Hour -> 15
> - precip3hr, precip12hr, precip10min, precip1min -> 61 (with
different
> accumulation intervals)
> - windDir10 -> 31 (with height = 10)
> - windSpeed10 -> 32 (with height = 10)
> - convert 10m speed and direction to U and V components -> 33, 34
> (with height = 10)
>
> There are some input NetCDF variables for which I couldn't find a
mapping to a GRIB code. By convention, the MET tools associate each
point observation type with a corresponding GRIB code. I have two
main questions remaining...
> (1) Are the mappings that I've used above correct?
> (2) Do the units used in the input NetCDF files match the prescribed
units for that GRIB code? Or do I need to do some unit conversion?
>
> Please try replacing the METv4.1 versions of madis2nc.h/.cc and
recompile. And then try running some mesonet data through it. And
please let me know how it looks to you - any questions or issues?
>
> FYI - running madis2nc a verbosity level 3 or higher (-v 3) prints
out very detailed information about the observations being processed.
>
> Thanks,
> John
>
> On 02/26/2014 05:59 AM, Watson.Leela via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>>
>> John,
>>
>> Have you had a chance to look at possibly adding mesonet data to
the madis2nc tool?
>>
>> Leela Watson
>>
>> -----Original Message-----
>> From: Watson.Leela
>> Sent: Thursday, February 13, 2014 7:14 AM
>> To: 'met_help at ucar.edu'
>> Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>
>> Thanks so much. I have attached the zipped file.
>>
>> -----Original Message-----
>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>> Sent: Wednesday, February 12, 2014 3:25 PM
>> To: Watson.Leela
>> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>
>> Leela,
>>
>> It looks like the mesonet data is not currently supported by the
madis2nc tool. However, it shouldn't be too difficult to add that
functionality. Perhaps we could work together to get that implemented
and tested. Could you send me a sample MADIS mesonet file that you'd
like to use?
>>
>> Thanks,
>> John Halley Gotway
>> met_help at ucar.edu
>>
>> On 02/12/2014 08:53 AM, Watson.Leela via RT wrote:
>>>
>>> Wed Feb 12 08:53:55 2014: Request 65414 was acted upon.
>>> Transaction: Ticket created by watson.leela at ensco.com
>>> Queue: met_help
>>> Subject: MADIS mesonet data
>>> Owner: Nobody
>>> Requestors: watson.leela at ensco.com
>>> Status: new
>>> Ticket <URL:
>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414
>>>>
>>>
>>>
>>> Hello,
>>>
>>> Is there currently a way to use the MADIS mesonet data in point-
stat? I have seen some archive met_help messages that indicate that it
is possible to reformat the mesonet data to ascii format and then run
it through ascii2nc, but I am looking for a more streamlined approach
such as madis2nc.
>>>
>>> Thanks!
>>>
>>> Leela Watson
>>>
>>> Leela R. Watson, PhD
>>> Meteorologist
>>> (321) 853-8264
>>> 1980 N. Atlantic Ave., Suite 830
>>> Cocoa Beach, FL 32931
>>> www.ensco.com
>>>
>>> [cid:image001.gif at 01CF27E0.B2A7C250]
>>> Innovation. Collaboration. Solutions. Success.
>>>
>>>
>>> ________________________________
>>> The information contained in this email message is intended only
for the use of the individual(s) to whom it is addressed and may
contain information that is privileged and sensitive. If you are not
the intended recipient, or otherwise have received this communication
in error, please notify the sender immediately by email at the above
referenced address and note that any further dissemination,
distribution or copying of this communication is strictly prohibited.
>>>
>>> The U.S. Export Control Laws regulate the export and re-export of
technology originating in the United States. This includes the
electronic transmission of information and software to foreign
countries and to certain foreign nationals. Recipient agrees to abide
by these laws and their regulations -- including the U.S. Department
of Commerce Export Administration Regulations and the U.S. Department
of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived
from this email to either a foreign national or a foreign destination
in violation of such laws.
>>>
>>
>>
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
From: Watson.Leela
Time: Thu Mar 13 08:36:37 2014
I've also just uploaded my PointStatConfig file.
Leela
-----Original Message-----
From: Watson.Leela
Sent: Thursday, March 13, 2014 10:23 AM
To: 'met_help at ucar.edu'
Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
John,
I am running into some problems with the mesonet data in point_stat.
The updated code for madis2nc works great. But when I try to run
point_stat using the mesonet data, I am not getting any matched pairs.
I have looked at the mesonet output from madis2nc and there looks to
me like there are some data points that fall within my WRF domain.
However, when I run point_stat it is telling me that there is a level
mismatch (here is part of the output):
DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type ADPSFC,
over region FULL, for interpolation method UW_MEAN(1), using 0 pairs.
DEBUG 3: Number of matched pairs = 0
DEBUG 3: Observations processed = 721845
DEBUG 3: Rejected: GRIB code = 636758
DEBUG 3: Rejected: valid time = 0
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 84984
DEBUG 3: Rejected: level mismatch = 103
DEBUG 3: Rejected: quality marker = 0
DEBUG 3: Rejected: message type = 0
DEBUG 3: Rejected: masking region = 0
DEBUG 3: Rejected: bad fcst value = 0
DEBUG 3: Rejected: duplicates = 0
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Processing DPT/Z2 versus DPT/Z2, for observation type ADPSFC,
over region FULL, for interpolation method UW_MEAN(1), using 0 pairs.
DEBUG 3: Number of matched pairs = 0
DEBUG 3: Observations processed = 721845
DEBUG 3: Rejected: GRIB code = 648350
DEBUG 3: Rejected: valid time = 0
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 73402
DEBUG 3: Rejected: level mismatch = 93
DEBUG 3: Rejected: quality marker = 0
DEBUG 3: Rejected: message type = 0
DEBUG 3: Rejected: masking region = 0
DEBUG 3: Rejected: bad fcst value = 0
DEBUG 3: Rejected: duplicates = 0
DEBUG 2:
The mesonet output from madis2nc looks very similar to the metar
output (same grib codes etc) and I have no problems getting matched
pairs from point_stat using the metar data (using the same
PointStatConfig file options). Is there something that I am missing?
I have uploaded my raw mesonet data (mesonet_20130924_1800), mesonet
data that has been run through madis2nc (meso_out.nc), and a WRF
forecast file (2013092412_d02.06) to the anonymous ftp site for you to
look at if you would like (located under 'Watson').
Thanks,
Leela
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Thursday, March 06, 2014 6:58 PM
To: Watson.Leela
Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
Leela,
Thanks for catching those unit conversion issues. I modified two
lines of the madis2nc.cc file:
1665 process_obs(f_in, "precipRate", cur, dim, 59, 1000.0,
1675 process_obs(f_in, "totalColumnPWV", cur, dim, 54, 10.0,
I'm not specifying conversion factors for those two variables. The
input precipRate value is now multiplied by 1000, and the input
precipitable water is now multiplied by 10 before writing them to the
output file.
The updated version of madis2nc.cc is attached.
Please let me know if you run into any more issues. If this all works
fine, I'll include these changes in the next official release of MET.
Thanks!
John
On 03/05/2014 06:37 AM, Watson.Leela via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>
> John,
>
> Everything looks good except for the units for totalColumnPWV and
precipRate. totalColumnPWV is in centimeters in the NetCDF mesonet
file, but in the GRIB code it is listed as mm. precipRate is in
meters/second in the NetCDF file, but is in millimeters/second in the
GRIB code. So these two variables need unit conversion. I would do it
myself, but I really have no knowledge about reading/writing NetCDF!
Otherwise, everything else looks good.
>
> Leela
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Friday, February 28, 2014 12:36 PM
> To: Watson.Leela
> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> Leela,
>
> I've worked on this a bit and have attached updated versions of
madis2nc.h/.cc. The "process_madis_mesonet()" function I added maps
the following input NetCDF variable names to GRIB codes listed below.
Here's where the GRIB codes are defined:
> http://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html
>
> - temperature -> 11
> - dewpoint -> 17
> - relHumidity -> 52
> - stationPressure -> 1
> - sealLevelPressure -> 2
> - windDir -> 31
> - windSpeed -> 32
> - convert wind direction and wind speed to U and V components -> 33,
> 34
> - windGust -> 180
> - visibility -> 20
> - precipRate -> 59
> - solarRadiation -> 250
> - seaSurfaceTemp -> 80
> - totalColumnPWV -> 54
> - soilTemperature -> 85
> - minTemp24Hour -> 16
> - maxTemp24Hour -> 15
> - precip3hr, precip12hr, precip10min, precip1min -> 61 (with
different
> accumulation intervals)
> - windDir10 -> 31 (with height = 10)
> - windSpeed10 -> 32 (with height = 10)
> - convert 10m speed and direction to U and V components -> 33, 34
> (with height = 10)
>
> There are some input NetCDF variables for which I couldn't find a
mapping to a GRIB code. By convention, the MET tools associate each
point observation type with a corresponding GRIB code. I have two
main questions remaining...
> (1) Are the mappings that I've used above correct?
> (2) Do the units used in the input NetCDF files match the prescribed
units for that GRIB code? Or do I need to do some unit conversion?
>
> Please try replacing the METv4.1 versions of madis2nc.h/.cc and
recompile. And then try running some mesonet data through it. And
please let me know how it looks to you - any questions or issues?
>
> FYI - running madis2nc a verbosity level 3 or higher (-v 3) prints
out very detailed information about the observations being processed.
>
> Thanks,
> John
>
> On 02/26/2014 05:59 AM, Watson.Leela via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>>
>> John,
>>
>> Have you had a chance to look at possibly adding mesonet data to
the madis2nc tool?
>>
>> Leela Watson
>>
>> -----Original Message-----
>> From: Watson.Leela
>> Sent: Thursday, February 13, 2014 7:14 AM
>> To: 'met_help at ucar.edu'
>> Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>
>> Thanks so much. I have attached the zipped file.
>>
>> -----Original Message-----
>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>> Sent: Wednesday, February 12, 2014 3:25 PM
>> To: Watson.Leela
>> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>
>> Leela,
>>
>> It looks like the mesonet data is not currently supported by the
madis2nc tool. However, it shouldn't be too difficult to add that
functionality. Perhaps we could work together to get that implemented
and tested. Could you send me a sample MADIS mesonet file that you'd
like to use?
>>
>> Thanks,
>> John Halley Gotway
>> met_help at ucar.edu
>>
>> On 02/12/2014 08:53 AM, Watson.Leela via RT wrote:
>>>
>>> Wed Feb 12 08:53:55 2014: Request 65414 was acted upon.
>>> Transaction: Ticket created by watson.leela at ensco.com
>>> Queue: met_help
>>> Subject: MADIS mesonet data
>>> Owner: Nobody
>>> Requestors: watson.leela at ensco.com
>>> Status: new
>>> Ticket <URL:
>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414
>>>>
>>>
>>>
>>> Hello,
>>>
>>> Is there currently a way to use the MADIS mesonet data in point-
stat? I have seen some archive met_help messages that indicate that it
is possible to reformat the mesonet data to ascii format and then run
it through ascii2nc, but I am looking for a more streamlined approach
such as madis2nc.
>>>
>>> Thanks!
>>>
>>> Leela Watson
>>>
>>> Leela R. Watson, PhD
>>> Meteorologist
>>> (321) 853-8264
>>> 1980 N. Atlantic Ave., Suite 830
>>> Cocoa Beach, FL 32931
>>> www.ensco.com
>>>
>>> [cid:image001.gif at 01CF27E0.B2A7C250]
>>> Innovation. Collaboration. Solutions. Success.
>>>
>>>
>>> ________________________________
>>> The information contained in this email message is intended only
for the use of the individual(s) to whom it is addressed and may
contain information that is privileged and sensitive. If you are not
the intended recipient, or otherwise have received this communication
in error, please notify the sender immediately by email at the above
referenced address and note that any further dissemination,
distribution or copying of this communication is strictly prohibited.
>>>
>>> The U.S. Export Control Laws regulate the export and re-export of
technology originating in the United States. This includes the
electronic transmission of information and software to foreign
countries and to certain foreign nationals. Recipient agrees to abide
by these laws and their regulations -- including the U.S. Department
of Commerce Export Administration Regulations and the U.S. Department
of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived
from this email to either a foreign national or a foreign destination
in violation of such laws.
>>>
>>
>>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
From: John Halley Gotway
Time: Thu Mar 13 11:35:00 2014
Leela,
Thanks for sending your data. I was able to replicate the behavior
you describe. The source of the problem is the message type of the
point observations. I had madis2nc encode the message type as
"MESONET" in its output.
In Point-Stat the "ADPSFC" string has special meaning. It means that
the observation occurs at the surface, and it shouldn't check the
vertical level information. The string "MESONET" does not have
special meaning. For each observation in the input file, Point-Stat
tries to add it to each verification task. It performs several
logical checks to see if the observation value should be used.
Those checks are performed in the order listed in the DEBUG 3 output:
DEBUG 3: Rejected: GRIB code = 636758
DEBUG 3: Rejected: valid time = 0
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 84984
DEBUG 3: Rejected: level mismatch = 103
DEBUG 3: Rejected: quality marker = 0
DEBUG 3: Rejected: message type = 0
DEBUG 3: Rejected: masking region = 0
DEBUG 3: Rejected: bad fcst value = 0
DEBUG 3: Rejected: duplicates = 0
When it gets down to checking the "level", since the observation
message type is "MESONET" (which is not a pre-defined "surface"
message type, "ADPSFC" or "SFCSHP"), it checks to see if the
observation level matches what was requested. When verifying 2-meter
temperature, it's checking to see if the observation's level value is
exactly 2. If not, it throws it out. So in this example,
Point-Stat made it down to checking the level value 103 times, and in
all cases the level value was never exactly 2.
Looking in the point observations, I see that the level value for
these observations is set to 0. So I modified the config file and
reran...
Config file setting...
fcst = {
field = [
{
name = "TMP";
level = [ "Z2" ];
cat_thresh = [ <=273, >273 ];
}
];
};
obs = {
wind_thresh = [ NA ];
message_type = [ "MESONET" ];
field = [
{
name = "TMP";
level = [ "Z0" ];
cat_thresh = [ <=273, >273 ];
}
];
};
Here, I'm telling Point-Stat to extract the 2-m temperature field from
the forecast file and verify against point observations of temperature
whose level value is exactly 0.
Here's the corresponding Point-Stat output...
DEBUG 2: Processing TMP/Z2 versus TMP/Z0, for observation type
MESONET, over region FULL, for interpolation method UW_MEAN(1), using
103 pairs.
DEBUG 3: Number of matched pairs = 103
DEBUG 3: Observations processed = 721845
DEBUG 3: Rejected: GRIB code = 636758
DEBUG 3: Rejected: valid time = 0
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 84984
DEBUG 3: Rejected: level mismatch = 0
DEBUG 3: Rejected: quality marker = 0
DEBUG 3: Rejected: message type = 0
DEBUG 3: Rejected: masking region = 0
DEBUG 3: Rejected: bad fcst value = 0
DEBUG 3: Rejected: duplicates = 0
DEBUG 2: Computing Categorical Statistics.
As you can see, we now have 103 matched pairs.
The main question now is this - are all observations in MADIS MESONET
files at the surface? If so, we should just encode the message type
as "ADPSFC" and skip the checking of the level value. If
not, we should leave it as, and require the user to explicitly state
what level values should be used.
Forgive my ignorance on this, I'm just not that familiar with all the
different sources of observation data.
Thanks,
John
On 03/13/2014 08:36 AM, Watson.Leela via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>
> I've also just uploaded my PointStatConfig file.
>
> Leela
>
> -----Original Message-----
> From: Watson.Leela
> Sent: Thursday, March 13, 2014 10:23 AM
> To: 'met_help at ucar.edu'
> Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> John,
>
> I am running into some problems with the mesonet data in point_stat.
The updated code for madis2nc works great. But when I try to run
point_stat using the mesonet data, I am not getting any matched pairs.
I have looked at the mesonet output from madis2nc and there looks to
me like there are some data points that fall within my WRF domain.
However, when I run point_stat it is telling me that there is a level
mismatch (here is part of the output):
>
> DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type
ADPSFC, over region FULL, for interpolation method UW_MEAN(1), using 0
pairs.
> DEBUG 3: Number of matched pairs = 0
> DEBUG 3: Observations processed = 721845
> DEBUG 3: Rejected: GRIB code = 636758
> DEBUG 3: Rejected: valid time = 0
> DEBUG 3: Rejected: bad obs value = 0
> DEBUG 3: Rejected: off the grid = 84984
> DEBUG 3: Rejected: level mismatch = 103
> DEBUG 3: Rejected: quality marker = 0
> DEBUG 3: Rejected: message type = 0
> DEBUG 3: Rejected: masking region = 0
> DEBUG 3: Rejected: bad fcst value = 0
> DEBUG 3: Rejected: duplicates = 0
> DEBUG 2:
> DEBUG 2:
--------------------------------------------------------------------------------
> DEBUG 2:
> DEBUG 2: Processing DPT/Z2 versus DPT/Z2, for observation type
ADPSFC, over region FULL, for interpolation method UW_MEAN(1), using 0
pairs.
> DEBUG 3: Number of matched pairs = 0
> DEBUG 3: Observations processed = 721845
> DEBUG 3: Rejected: GRIB code = 648350
> DEBUG 3: Rejected: valid time = 0
> DEBUG 3: Rejected: bad obs value = 0
> DEBUG 3: Rejected: off the grid = 73402
> DEBUG 3: Rejected: level mismatch = 93
> DEBUG 3: Rejected: quality marker = 0
> DEBUG 3: Rejected: message type = 0
> DEBUG 3: Rejected: masking region = 0
> DEBUG 3: Rejected: bad fcst value = 0
> DEBUG 3: Rejected: duplicates = 0
> DEBUG 2:
>
> The mesonet output from madis2nc looks very similar to the metar
output (same grib codes etc) and I have no problems getting matched
pairs from point_stat using the metar data (using the same
PointStatConfig file options). Is there something that I am missing?
>
> I have uploaded my raw mesonet data (mesonet_20130924_1800), mesonet
data that has been run through madis2nc (meso_out.nc), and a WRF
forecast file (2013092412_d02.06) to the anonymous ftp site for you to
look at if you would like (located under 'Watson').
>
> Thanks,
>
> Leela
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Thursday, March 06, 2014 6:58 PM
> To: Watson.Leela
> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> Leela,
>
> Thanks for catching those unit conversion issues. I modified two
lines of the madis2nc.cc file:
>
> 1665 process_obs(f_in, "precipRate", cur, dim, 59,
1000.0,
> 1675 process_obs(f_in, "totalColumnPWV", cur, dim, 54,
10.0,
>
> I'm not specifying conversion factors for those two variables. The
input precipRate value is now multiplied by 1000, and the input
precipitable water is now multiplied by 10 before writing them to the
output file.
>
> The updated version of madis2nc.cc is attached.
>
> Please let me know if you run into any more issues. If this all
works fine, I'll include these changes in the next official release of
MET.
>
> Thanks!
> John
>
> On 03/05/2014 06:37 AM, Watson.Leela via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>>
>> John,
>>
>> Everything looks good except for the units for totalColumnPWV and
precipRate. totalColumnPWV is in centimeters in the NetCDF mesonet
file, but in the GRIB code it is listed as mm. precipRate is in
meters/second in the NetCDF file, but is in millimeters/second in the
GRIB code. So these two variables need unit conversion. I would do it
myself, but I really have no knowledge about reading/writing NetCDF!
Otherwise, everything else looks good.
>>
>> Leela
>>
>> -----Original Message-----
>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>> Sent: Friday, February 28, 2014 12:36 PM
>> To: Watson.Leela
>> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>
>> Leela,
>>
>> I've worked on this a bit and have attached updated versions of
madis2nc.h/.cc. The "process_madis_mesonet()" function I added maps
the following input NetCDF variable names to GRIB codes listed below.
Here's where the GRIB codes are defined:
>> http://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html
>>
>> - temperature -> 11
>> - dewpoint -> 17
>> - relHumidity -> 52
>> - stationPressure -> 1
>> - sealLevelPressure -> 2
>> - windDir -> 31
>> - windSpeed -> 32
>> - convert wind direction and wind speed to U and V components ->
33,
>> 34
>> - windGust -> 180
>> - visibility -> 20
>> - precipRate -> 59
>> - solarRadiation -> 250
>> - seaSurfaceTemp -> 80
>> - totalColumnPWV -> 54
>> - soilTemperature -> 85
>> - minTemp24Hour -> 16
>> - maxTemp24Hour -> 15
>> - precip3hr, precip12hr, precip10min, precip1min -> 61 (with
different
>> accumulation intervals)
>> - windDir10 -> 31 (with height = 10)
>> - windSpeed10 -> 32 (with height = 10)
>> - convert 10m speed and direction to U and V components -> 33, 34
>> (with height = 10)
>>
>> There are some input NetCDF variables for which I couldn't find a
mapping to a GRIB code. By convention, the MET tools associate each
point observation type with a corresponding GRIB code. I have two
main questions remaining...
>> (1) Are the mappings that I've used above correct?
>> (2) Do the units used in the input NetCDF files match the
prescribed units for that GRIB code? Or do I need to do some unit
conversion?
>>
>> Please try replacing the METv4.1 versions of madis2nc.h/.cc and
recompile. And then try running some mesonet data through it. And
please let me know how it looks to you - any questions or issues?
>>
>> FYI - running madis2nc a verbosity level 3 or higher (-v 3) prints
out very detailed information about the observations being processed.
>>
>> Thanks,
>> John
>>
>> On 02/26/2014 05:59 AM, Watson.Leela via RT wrote:
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>>>
>>> John,
>>>
>>> Have you had a chance to look at possibly adding mesonet data to
the madis2nc tool?
>>>
>>> Leela Watson
>>>
>>> -----Original Message-----
>>> From: Watson.Leela
>>> Sent: Thursday, February 13, 2014 7:14 AM
>>> To: 'met_help at ucar.edu'
>>> Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>>
>>> Thanks so much. I have attached the zipped file.
>>>
>>> -----Original Message-----
>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>> Sent: Wednesday, February 12, 2014 3:25 PM
>>> To: Watson.Leela
>>> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>>
>>> Leela,
>>>
>>> It looks like the mesonet data is not currently supported by the
madis2nc tool. However, it shouldn't be too difficult to add that
functionality. Perhaps we could work together to get that implemented
and tested. Could you send me a sample MADIS mesonet file that you'd
like to use?
>>>
>>> Thanks,
>>> John Halley Gotway
>>> met_help at ucar.edu
>>>
>>> On 02/12/2014 08:53 AM, Watson.Leela via RT wrote:
>>>>
>>>> Wed Feb 12 08:53:55 2014: Request 65414 was acted upon.
>>>> Transaction: Ticket created by watson.leela at ensco.com
>>>> Queue: met_help
>>>> Subject: MADIS mesonet data
>>>> Owner: Nobody
>>>> Requestors: watson.leela at ensco.com
>>>> Status: new
>>>> Ticket <URL:
>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414
>>>>>
>>>>
>>>>
>>>> Hello,
>>>>
>>>> Is there currently a way to use the MADIS mesonet data in point-
stat? I have seen some archive met_help messages that indicate that it
is possible to reformat the mesonet data to ascii format and then run
it through ascii2nc, but I am looking for a more streamlined approach
such as madis2nc.
>>>>
>>>> Thanks!
>>>>
>>>> Leela Watson
>>>>
>>>> Leela R. Watson, PhD
>>>> Meteorologist
>>>> (321) 853-8264
>>>> 1980 N. Atlantic Ave., Suite 830
>>>> Cocoa Beach, FL 32931
>>>> www.ensco.com
>>>>
>>>> [cid:image001.gif at 01CF27E0.B2A7C250]
>>>> Innovation. Collaboration. Solutions. Success.
>>>>
>>>>
>>>> ________________________________
>>>> The information contained in this email message is intended only
for the use of the individual(s) to whom it is addressed and may
contain information that is privileged and sensitive. If you are not
the intended recipient, or otherwise have received this communication
in error, please notify the sender immediately by email at the above
referenced address and note that any further dissemination,
distribution or copying of this communication is strictly prohibited.
>>>>
>>>> The U.S. Export Control Laws regulate the export and re-export of
technology originating in the United States. This includes the
electronic transmission of information and software to foreign
countries and to certain foreign nationals. Recipient agrees to abide
by these laws and their regulations -- including the U.S. Department
of Commerce Export Administration Regulations and the U.S. Department
of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived
from this email to either a foreign national or a foreign destination
in violation of such laws.
>>>>
>>>
>>>
>>
>>
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
From: Watson.Leela
Time: Mon Mar 24 10:13:41 2014
John,
Thanks for looking into this and sorry for my slow response - I have
been working on some other projects.
Yes, the observations in the MESONET files are at the surface. So it
would be easiest to encode the message type as "ADPSFC".
Leela
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Thursday, March 13, 2014 1:35 PM
To: Watson.Leela
Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
Leela,
Thanks for sending your data. I was able to replicate the behavior
you describe. The source of the problem is the message type of the
point observations. I had madis2nc encode the message type as
"MESONET" in its output.
In Point-Stat the "ADPSFC" string has special meaning. It means that
the observation occurs at the surface, and it shouldn't check the
vertical level information. The string "MESONET" does not have
special meaning. For each observation in the input file, Point-Stat
tries to add it to each verification task. It performs several
logical checks to see if the observation value should be used.
Those checks are performed in the order listed in the DEBUG 3 output:
DEBUG 3: Rejected: GRIB code = 636758
DEBUG 3: Rejected: valid time = 0
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 84984
DEBUG 3: Rejected: level mismatch = 103
DEBUG 3: Rejected: quality marker = 0
DEBUG 3: Rejected: message type = 0
DEBUG 3: Rejected: masking region = 0
DEBUG 3: Rejected: bad fcst value = 0
DEBUG 3: Rejected: duplicates = 0
When it gets down to checking the "level", since the observation
message type is "MESONET" (which is not a pre-defined "surface"
message type, "ADPSFC" or "SFCSHP"), it checks to see if the
observation level matches what was requested. When verifying 2-meter
temperature, it's checking to see if the observation's level value is
exactly 2. If not, it throws it out. So in this example, Point-Stat
made it down to checking the level value 103 times, and in all cases
the level value was never exactly 2.
Looking in the point observations, I see that the level value for
these observations is set to 0. So I modified the config file and
reran...
Config file setting...
fcst = {
field = [
{
name = "TMP";
level = [ "Z2" ];
cat_thresh = [ <=273, >273 ];
}
];
};
obs = {
wind_thresh = [ NA ];
message_type = [ "MESONET" ];
field = [
{
name = "TMP";
level = [ "Z0" ];
cat_thresh = [ <=273, >273 ];
}
];
};
Here, I'm telling Point-Stat to extract the 2-m temperature field from
the forecast file and verify against point observations of temperature
whose level value is exactly 0.
Here's the corresponding Point-Stat output...
DEBUG 2: Processing TMP/Z2 versus TMP/Z0, for observation type
MESONET, over region FULL, for interpolation method UW_MEAN(1), using
103 pairs.
DEBUG 3: Number of matched pairs = 103
DEBUG 3: Observations processed = 721845
DEBUG 3: Rejected: GRIB code = 636758
DEBUG 3: Rejected: valid time = 0
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 84984
DEBUG 3: Rejected: level mismatch = 0
DEBUG 3: Rejected: quality marker = 0
DEBUG 3: Rejected: message type = 0
DEBUG 3: Rejected: masking region = 0
DEBUG 3: Rejected: bad fcst value = 0
DEBUG 3: Rejected: duplicates = 0
DEBUG 2: Computing Categorical Statistics.
As you can see, we now have 103 matched pairs.
The main question now is this - are all observations in MADIS MESONET
files at the surface? If so, we should just encode the message type
as "ADPSFC" and skip the checking of the level value. If not, we
should leave it as, and require the user to explicitly state what
level values should be used.
Forgive my ignorance on this, I'm just not that familiar with all the
different sources of observation data.
Thanks,
John
On 03/13/2014 08:36 AM, Watson.Leela via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>
> I've also just uploaded my PointStatConfig file.
>
> Leela
>
> -----Original Message-----
> From: Watson.Leela
> Sent: Thursday, March 13, 2014 10:23 AM
> To: 'met_help at ucar.edu'
> Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> John,
>
> I am running into some problems with the mesonet data in point_stat.
The updated code for madis2nc works great. But when I try to run
point_stat using the mesonet data, I am not getting any matched pairs.
I have looked at the mesonet output from madis2nc and there looks to
me like there are some data points that fall within my WRF domain.
However, when I run point_stat it is telling me that there is a level
mismatch (here is part of the output):
>
> DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type
ADPSFC, over region FULL, for interpolation method UW_MEAN(1), using 0
pairs.
> DEBUG 3: Number of matched pairs = 0
> DEBUG 3: Observations processed = 721845
> DEBUG 3: Rejected: GRIB code = 636758
> DEBUG 3: Rejected: valid time = 0
> DEBUG 3: Rejected: bad obs value = 0
> DEBUG 3: Rejected: off the grid = 84984
> DEBUG 3: Rejected: level mismatch = 103 DEBUG 3: Rejected: quality
> marker = 0
> DEBUG 3: Rejected: message type = 0
> DEBUG 3: Rejected: masking region = 0
> DEBUG 3: Rejected: bad fcst value = 0
> DEBUG 3: Rejected: duplicates = 0
> DEBUG 2:
> DEBUG 2:
>
----------------------------------------------------------------------
> ----------
> DEBUG 2:
> DEBUG 2: Processing DPT/Z2 versus DPT/Z2, for observation type
ADPSFC, over region FULL, for interpolation method UW_MEAN(1), using 0
pairs.
> DEBUG 3: Number of matched pairs = 0
> DEBUG 3: Observations processed = 721845
> DEBUG 3: Rejected: GRIB code = 648350
> DEBUG 3: Rejected: valid time = 0
> DEBUG 3: Rejected: bad obs value = 0
> DEBUG 3: Rejected: off the grid = 73402
> DEBUG 3: Rejected: level mismatch = 93 DEBUG 3: Rejected: quality
> marker = 0
> DEBUG 3: Rejected: message type = 0
> DEBUG 3: Rejected: masking region = 0
> DEBUG 3: Rejected: bad fcst value = 0
> DEBUG 3: Rejected: duplicates = 0
> DEBUG 2:
>
> The mesonet output from madis2nc looks very similar to the metar
output (same grib codes etc) and I have no problems getting matched
pairs from point_stat using the metar data (using the same
PointStatConfig file options). Is there something that I am missing?
>
> I have uploaded my raw mesonet data (mesonet_20130924_1800), mesonet
data that has been run through madis2nc (meso_out.nc), and a WRF
forecast file (2013092412_d02.06) to the anonymous ftp site for you to
look at if you would like (located under 'Watson').
>
> Thanks,
>
> Leela
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Thursday, March 06, 2014 6:58 PM
> To: Watson.Leela
> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> Leela,
>
> Thanks for catching those unit conversion issues. I modified two
lines of the madis2nc.cc file:
>
> 1665 process_obs(f_in, "precipRate", cur, dim, 59,
1000.0,
> 1675 process_obs(f_in, "totalColumnPWV", cur, dim, 54,
10.0,
>
> I'm not specifying conversion factors for those two variables. The
input precipRate value is now multiplied by 1000, and the input
precipitable water is now multiplied by 10 before writing them to the
output file.
>
> The updated version of madis2nc.cc is attached.
>
> Please let me know if you run into any more issues. If this all
works fine, I'll include these changes in the next official release of
MET.
>
> Thanks!
> John
>
> On 03/05/2014 06:37 AM, Watson.Leela via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>>
>> John,
>>
>> Everything looks good except for the units for totalColumnPWV and
precipRate. totalColumnPWV is in centimeters in the NetCDF mesonet
file, but in the GRIB code it is listed as mm. precipRate is in
meters/second in the NetCDF file, but is in millimeters/second in the
GRIB code. So these two variables need unit conversion. I would do it
myself, but I really have no knowledge about reading/writing NetCDF!
Otherwise, everything else looks good.
>>
>> Leela
>>
>> -----Original Message-----
>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>> Sent: Friday, February 28, 2014 12:36 PM
>> To: Watson.Leela
>> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>
>> Leela,
>>
>> I've worked on this a bit and have attached updated versions of
madis2nc.h/.cc. The "process_madis_mesonet()" function I added maps
the following input NetCDF variable names to GRIB codes listed below.
Here's where the GRIB codes are defined:
>> http://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html
>>
>> - temperature -> 11
>> - dewpoint -> 17
>> - relHumidity -> 52
>> - stationPressure -> 1
>> - sealLevelPressure -> 2
>> - windDir -> 31
>> - windSpeed -> 32
>> - convert wind direction and wind speed to U and V components ->
33,
>> 34
>> - windGust -> 180
>> - visibility -> 20
>> - precipRate -> 59
>> - solarRadiation -> 250
>> - seaSurfaceTemp -> 80
>> - totalColumnPWV -> 54
>> - soilTemperature -> 85
>> - minTemp24Hour -> 16
>> - maxTemp24Hour -> 15
>> - precip3hr, precip12hr, precip10min, precip1min -> 61 (with
>> different accumulation intervals)
>> - windDir10 -> 31 (with height = 10)
>> - windSpeed10 -> 32 (with height = 10)
>> - convert 10m speed and direction to U and V components -> 33, 34
>> (with height = 10)
>>
>> There are some input NetCDF variables for which I couldn't find a
mapping to a GRIB code. By convention, the MET tools associate each
point observation type with a corresponding GRIB code. I have two
main questions remaining...
>> (1) Are the mappings that I've used above correct?
>> (2) Do the units used in the input NetCDF files match the
prescribed units for that GRIB code? Or do I need to do some unit
conversion?
>>
>> Please try replacing the METv4.1 versions of madis2nc.h/.cc and
recompile. And then try running some mesonet data through it. And
please let me know how it looks to you - any questions or issues?
>>
>> FYI - running madis2nc a verbosity level 3 or higher (-v 3) prints
out very detailed information about the observations being processed.
>>
>> Thanks,
>> John
>>
>> On 02/26/2014 05:59 AM, Watson.Leela via RT wrote:
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>>>
>>> John,
>>>
>>> Have you had a chance to look at possibly adding mesonet data to
the madis2nc tool?
>>>
>>> Leela Watson
>>>
>>> -----Original Message-----
>>> From: Watson.Leela
>>> Sent: Thursday, February 13, 2014 7:14 AM
>>> To: 'met_help at ucar.edu'
>>> Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>>
>>> Thanks so much. I have attached the zipped file.
>>>
>>> -----Original Message-----
>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>> Sent: Wednesday, February 12, 2014 3:25 PM
>>> To: Watson.Leela
>>> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>>
>>> Leela,
>>>
>>> It looks like the mesonet data is not currently supported by the
madis2nc tool. However, it shouldn't be too difficult to add that
functionality. Perhaps we could work together to get that implemented
and tested. Could you send me a sample MADIS mesonet file that you'd
like to use?
>>>
>>> Thanks,
>>> John Halley Gotway
>>> met_help at ucar.edu
>>>
>>> On 02/12/2014 08:53 AM, Watson.Leela via RT wrote:
>>>>
>>>> Wed Feb 12 08:53:55 2014: Request 65414 was acted upon.
>>>> Transaction: Ticket created by watson.leela at ensco.com
>>>> Queue: met_help
>>>> Subject: MADIS mesonet data
>>>> Owner: Nobody
>>>> Requestors: watson.leela at ensco.com
>>>> Status: new
>>>> Ticket <URL:
>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414
>>>>>
>>>>
>>>>
>>>> Hello,
>>>>
>>>> Is there currently a way to use the MADIS mesonet data in point-
stat? I have seen some archive met_help messages that indicate that it
is possible to reformat the mesonet data to ascii format and then run
it through ascii2nc, but I am looking for a more streamlined approach
such as madis2nc.
>>>>
>>>> Thanks!
>>>>
>>>> Leela Watson
>>>>
>>>> Leela R. Watson, PhD
>>>> Meteorologist
>>>> (321) 853-8264
>>>> 1980 N. Atlantic Ave., Suite 830
>>>> Cocoa Beach, FL 32931
>>>> www.ensco.com
>>>>
>>>> [cid:image001.gif at 01CF27E0.B2A7C250]
>>>> Innovation. Collaboration. Solutions. Success.
>>>>
>>>>
>>>> ________________________________
>>>> The information contained in this email message is intended only
for the use of the individual(s) to whom it is addressed and may
contain information that is privileged and sensitive. If you are not
the intended recipient, or otherwise have received this communication
in error, please notify the sender immediately by email at the above
referenced address and note that any further dissemination,
distribution or copying of this communication is strictly prohibited.
>>>>
>>>> The U.S. Export Control Laws regulate the export and re-export of
technology originating in the United States. This includes the
electronic transmission of information and software to foreign
countries and to certain foreign nationals. Recipient agrees to abide
by these laws and their regulations -- including the U.S. Department
of Commerce Export Administration Regulations and the U.S. Department
of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived
from this email to either a foreign national or a foreign destination
in violation of such laws.
>>>>
>>>
>>>
>>
>>
>
>
------------------------------------------------
Subject: MADIS mesonet data
From: John Halley Gotway
Time: Mon Mar 24 13:02:27 2014
Leela,
Please find an updated version of madis2nc.cc that encodes MESONET
observations using the ADPSFC message type.
Hopefully that does the trick.
Thanks,
John
On 03/24/2014 10:13 AM, Watson.Leela via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>
> John,
>
> Thanks for looking into this and sorry for my slow response - I have
been working on some other projects.
>
> Yes, the observations in the MESONET files are at the surface. So it
would be easiest to encode the message type as "ADPSFC".
>
> Leela
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Thursday, March 13, 2014 1:35 PM
> To: Watson.Leela
> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>
> Leela,
>
> Thanks for sending your data. I was able to replicate the behavior
you describe. The source of the problem is the message type of the
point observations. I had madis2nc encode the message type as
"MESONET" in its output.
>
> In Point-Stat the "ADPSFC" string has special meaning. It means
that the observation occurs at the surface, and it shouldn't check the
vertical level information. The string "MESONET" does not have
special meaning. For each observation in the input file, Point-Stat
tries to add it to each verification task. It performs several
logical checks to see if the observation value should be used.
> Those checks are performed in the order listed in the DEBUG 3
output:
> DEBUG 3: Rejected: GRIB code = 636758
> DEBUG 3: Rejected: valid time = 0
> DEBUG 3: Rejected: bad obs value = 0
> DEBUG 3: Rejected: off the grid = 84984
> DEBUG 3: Rejected: level mismatch = 103
> DEBUG 3: Rejected: quality marker = 0
> DEBUG 3: Rejected: message type = 0
> DEBUG 3: Rejected: masking region = 0
> DEBUG 3: Rejected: bad fcst value = 0
> DEBUG 3: Rejected: duplicates = 0
>
> When it gets down to checking the "level", since the observation
message type is "MESONET" (which is not a pre-defined "surface"
message type, "ADPSFC" or "SFCSHP"), it checks to see if the
observation level matches what was requested. When verifying 2-meter
temperature, it's checking to see if the observation's level value is
exactly 2. If not, it throws it out. So in this example, Point-Stat
made it down to checking the level value 103 times, and in all cases
the level value was never exactly 2.
>
> Looking in the point observations, I see that the level value for
these observations is set to 0. So I modified the config file and
reran...
>
> Config file setting...
>
> fcst = {
>
> field = [
> {
> name = "TMP";
> level = [ "Z2" ];
> cat_thresh = [ <=273, >273 ];
> }
> ];
> };
> obs = {
> wind_thresh = [ NA ];
> message_type = [ "MESONET" ];
>
> field = [
> {
> name = "TMP";
> level = [ "Z0" ];
> cat_thresh = [ <=273, >273 ];
> }
> ];
> };
>
> Here, I'm telling Point-Stat to extract the 2-m temperature field
from the forecast file and verify against point observations of
temperature whose level value is exactly 0.
>
> Here's the corresponding Point-Stat output...
>
> DEBUG 2: Processing TMP/Z2 versus TMP/Z0, for observation type
MESONET, over region FULL, for interpolation method UW_MEAN(1), using
103 pairs.
> DEBUG 3: Number of matched pairs = 103
> DEBUG 3: Observations processed = 721845
> DEBUG 3: Rejected: GRIB code = 636758
> DEBUG 3: Rejected: valid time = 0
> DEBUG 3: Rejected: bad obs value = 0
> DEBUG 3: Rejected: off the grid = 84984
> DEBUG 3: Rejected: level mismatch = 0
> DEBUG 3: Rejected: quality marker = 0
> DEBUG 3: Rejected: message type = 0
> DEBUG 3: Rejected: masking region = 0
> DEBUG 3: Rejected: bad fcst value = 0
> DEBUG 3: Rejected: duplicates = 0
> DEBUG 2: Computing Categorical Statistics.
>
> As you can see, we now have 103 matched pairs.
>
> The main question now is this - are all observations in MADIS
MESONET files at the surface? If so, we should just encode the
message type as "ADPSFC" and skip the checking of the level value. If
not, we should leave it as, and require the user to explicitly state
what level values should be used.
>
> Forgive my ignorance on this, I'm just not that familiar with all
the different sources of observation data.
>
> Thanks,
> John
>
> On 03/13/2014 08:36 AM, Watson.Leela via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>>
>> I've also just uploaded my PointStatConfig file.
>>
>> Leela
>>
>> -----Original Message-----
>> From: Watson.Leela
>> Sent: Thursday, March 13, 2014 10:23 AM
>> To: 'met_help at ucar.edu'
>> Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>
>> John,
>>
>> I am running into some problems with the mesonet data in
point_stat. The updated code for madis2nc works great. But when I try
to run point_stat using the mesonet data, I am not getting any matched
pairs. I have looked at the mesonet output from madis2nc and there
looks to me like there are some data points that fall within my WRF
domain. However, when I run point_stat it is telling me that there is
a level mismatch (here is part of the output):
>>
>> DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type
ADPSFC, over region FULL, for interpolation method UW_MEAN(1), using 0
pairs.
>> DEBUG 3: Number of matched pairs = 0
>> DEBUG 3: Observations processed = 721845
>> DEBUG 3: Rejected: GRIB code = 636758
>> DEBUG 3: Rejected: valid time = 0
>> DEBUG 3: Rejected: bad obs value = 0
>> DEBUG 3: Rejected: off the grid = 84984
>> DEBUG 3: Rejected: level mismatch = 103 DEBUG 3: Rejected: quality
>> marker = 0
>> DEBUG 3: Rejected: message type = 0
>> DEBUG 3: Rejected: masking region = 0
>> DEBUG 3: Rejected: bad fcst value = 0
>> DEBUG 3: Rejected: duplicates = 0
>> DEBUG 2:
>> DEBUG 2:
>>
----------------------------------------------------------------------
>> ----------
>> DEBUG 2:
>> DEBUG 2: Processing DPT/Z2 versus DPT/Z2, for observation type
ADPSFC, over region FULL, for interpolation method UW_MEAN(1), using 0
pairs.
>> DEBUG 3: Number of matched pairs = 0
>> DEBUG 3: Observations processed = 721845
>> DEBUG 3: Rejected: GRIB code = 648350
>> DEBUG 3: Rejected: valid time = 0
>> DEBUG 3: Rejected: bad obs value = 0
>> DEBUG 3: Rejected: off the grid = 73402
>> DEBUG 3: Rejected: level mismatch = 93 DEBUG 3: Rejected: quality
>> marker = 0
>> DEBUG 3: Rejected: message type = 0
>> DEBUG 3: Rejected: masking region = 0
>> DEBUG 3: Rejected: bad fcst value = 0
>> DEBUG 3: Rejected: duplicates = 0
>> DEBUG 2:
>>
>> The mesonet output from madis2nc looks very similar to the metar
output (same grib codes etc) and I have no problems getting matched
pairs from point_stat using the metar data (using the same
PointStatConfig file options). Is there something that I am missing?
>>
>> I have uploaded my raw mesonet data (mesonet_20130924_1800),
mesonet data that has been run through madis2nc (meso_out.nc), and a
WRF forecast file (2013092412_d02.06) to the anonymous ftp site for
you to look at if you would like (located under 'Watson').
>>
>> Thanks,
>>
>> Leela
>>
>> -----Original Message-----
>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>> Sent: Thursday, March 06, 2014 6:58 PM
>> To: Watson.Leela
>> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>
>> Leela,
>>
>> Thanks for catching those unit conversion issues. I modified two
lines of the madis2nc.cc file:
>>
>> 1665 process_obs(f_in, "precipRate", cur, dim, 59,
1000.0,
>> 1675 process_obs(f_in, "totalColumnPWV", cur, dim, 54,
10.0,
>>
>> I'm not specifying conversion factors for those two variables. The
input precipRate value is now multiplied by 1000, and the input
precipitable water is now multiplied by 10 before writing them to the
output file.
>>
>> The updated version of madis2nc.cc is attached.
>>
>> Please let me know if you run into any more issues. If this all
works fine, I'll include these changes in the next official release of
MET.
>>
>> Thanks!
>> John
>>
>> On 03/05/2014 06:37 AM, Watson.Leela via RT wrote:
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>>>
>>> John,
>>>
>>> Everything looks good except for the units for totalColumnPWV and
precipRate. totalColumnPWV is in centimeters in the NetCDF mesonet
file, but in the GRIB code it is listed as mm. precipRate is in
meters/second in the NetCDF file, but is in millimeters/second in the
GRIB code. So these two variables need unit conversion. I would do it
myself, but I really have no knowledge about reading/writing NetCDF!
Otherwise, everything else looks good.
>>>
>>> Leela
>>>
>>> -----Original Message-----
>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>> Sent: Friday, February 28, 2014 12:36 PM
>>> To: Watson.Leela
>>> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>>
>>> Leela,
>>>
>>> I've worked on this a bit and have attached updated versions of
madis2nc.h/.cc. The "process_madis_mesonet()" function I added maps
the following input NetCDF variable names to GRIB codes listed below.
Here's where the GRIB codes are defined:
>>> http://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html
>>>
>>> - temperature -> 11
>>> - dewpoint -> 17
>>> - relHumidity -> 52
>>> - stationPressure -> 1
>>> - sealLevelPressure -> 2
>>> - windDir -> 31
>>> - windSpeed -> 32
>>> - convert wind direction and wind speed to U and V components ->
33,
>>> 34
>>> - windGust -> 180
>>> - visibility -> 20
>>> - precipRate -> 59
>>> - solarRadiation -> 250
>>> - seaSurfaceTemp -> 80
>>> - totalColumnPWV -> 54
>>> - soilTemperature -> 85
>>> - minTemp24Hour -> 16
>>> - maxTemp24Hour -> 15
>>> - precip3hr, precip12hr, precip10min, precip1min -> 61 (with
>>> different accumulation intervals)
>>> - windDir10 -> 31 (with height = 10)
>>> - windSpeed10 -> 32 (with height = 10)
>>> - convert 10m speed and direction to U and V components -> 33, 34
>>> (with height = 10)
>>>
>>> There are some input NetCDF variables for which I couldn't find a
mapping to a GRIB code. By convention, the MET tools associate each
point observation type with a corresponding GRIB code. I have two
main questions remaining...
>>> (1) Are the mappings that I've used above correct?
>>> (2) Do the units used in the input NetCDF files match the
prescribed units for that GRIB code? Or do I need to do some unit
conversion?
>>>
>>> Please try replacing the METv4.1 versions of madis2nc.h/.cc and
recompile. And then try running some mesonet data through it. And
please let me know how it looks to you - any questions or issues?
>>>
>>> FYI - running madis2nc a verbosity level 3 or higher (-v 3) prints
out very detailed information about the observations being processed.
>>>
>>> Thanks,
>>> John
>>>
>>> On 02/26/2014 05:59 AM, Watson.Leela via RT wrote:
>>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414 >
>>>>
>>>> John,
>>>>
>>>> Have you had a chance to look at possibly adding mesonet data to
the madis2nc tool?
>>>>
>>>> Leela Watson
>>>>
>>>> -----Original Message-----
>>>> From: Watson.Leela
>>>> Sent: Thursday, February 13, 2014 7:14 AM
>>>> To: 'met_help at ucar.edu'
>>>> Subject: RE: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>>>
>>>> Thanks so much. I have attached the zipped file.
>>>>
>>>> -----Original Message-----
>>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>>> Sent: Wednesday, February 12, 2014 3:25 PM
>>>> To: Watson.Leela
>>>> Subject: Re: [rt.rap.ucar.edu #65414] MADIS mesonet data
>>>>
>>>> Leela,
>>>>
>>>> It looks like the mesonet data is not currently supported by the
madis2nc tool. However, it shouldn't be too difficult to add that
functionality. Perhaps we could work together to get that implemented
and tested. Could you send me a sample MADIS mesonet file that you'd
like to use?
>>>>
>>>> Thanks,
>>>> John Halley Gotway
>>>> met_help at ucar.edu
>>>>
>>>> On 02/12/2014 08:53 AM, Watson.Leela via RT wrote:
>>>>>
>>>>> Wed Feb 12 08:53:55 2014: Request 65414 was acted upon.
>>>>> Transaction: Ticket created by watson.leela at ensco.com
>>>>> Queue: met_help
>>>>> Subject: MADIS mesonet data
>>>>> Owner: Nobody
>>>>> Requestors: watson.leela at ensco.com
>>>>> Status: new
>>>>> Ticket <URL:
>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65414
>>>>>>
>>>>>
>>>>>
>>>>> Hello,
>>>>>
>>>>> Is there currently a way to use the MADIS mesonet data in point-
stat? I have seen some archive met_help messages that indicate that it
is possible to reformat the mesonet data to ascii format and then run
it through ascii2nc, but I am looking for a more streamlined approach
such as madis2nc.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> Leela Watson
>>>>>
>>>>> Leela R. Watson, PhD
>>>>> Meteorologist
>>>>> (321) 853-8264
>>>>> 1980 N. Atlantic Ave., Suite 830
>>>>> Cocoa Beach, FL 32931
>>>>> www.ensco.com
>>>>>
>>>>> [cid:image001.gif at 01CF27E0.B2A7C250]
>>>>> Innovation. Collaboration. Solutions. Success.
>>>>>
>>>>>
>>>>> ________________________________
>>>>> The information contained in this email message is intended only
for the use of the individual(s) to whom it is addressed and may
contain information that is privileged and sensitive. If you are not
the intended recipient, or otherwise have received this communication
in error, please notify the sender immediately by email at the above
referenced address and note that any further dissemination,
distribution or copying of this communication is strictly prohibited.
>>>>>
>>>>> The U.S. Export Control Laws regulate the export and re-export
of technology originating in the United States. This includes the
electronic transmission of information and software to foreign
countries and to certain foreign nationals. Recipient agrees to abide
by these laws and their regulations -- including the U.S. Department
of Commerce Export Administration Regulations and the U.S. Department
of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived
from this email to either a foreign national or a foreign destination
in violation of such laws.
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
------------------------------------------------
More information about the Met_help
mailing list