Dear Mr.Mike Dixon, Thank you for accepting my proposal. I will be happy to provide any clarification or input in this regard during the course of implementation. I confirm the intent of the sub-convention spelled out by you. Regards S B Thampi -----Original Message----- From: Mike Dixon <address@hidden> Reply-to: address@hidden To: Bagulayan Thampi <address@hidden> Cc: Russ Rew <address@hidden>, address@hidden, address@hidden Subject: Re: [cfradial-users] "S B Thampi": New Ticket - [netCDF ! YYV-457201]: CF/Radial data model need for sub-convention on scan_parameters Date: Wed, 19 Oct 2011 22:15:24 -0600 (MDT) Dear Mr Thampi Thank you for your email, and I apologize for the long delay in responding. I agree with your suggestion - we will discuss your proposed addition and decide how best to include this. Just to confirm the intent - this extra meta-data would cover information on how the data fields have been censored/filtered using criteria such as SNR limits, CSI limits etc. Is that correct? Thank you Kind regards Mike Dixon > Thanks .Awaiting some positive response from the users. > S B Thampi > On Sep 22, 2011, at 8:09 PM, Russ Rew wrote: > >> Hi, >> >> I'm forwarding this to the cfradial-users mailing list, in hopes someone >> on the list can respond to this request for consideration of an addition >> to the CfRadial convention. >> >> Thanks! >> >> --Russ >> >> >> From: "S B Thampi" <address@hidden> >> Date: September 22, 2011 7:32:37 PM GMT+05:30 >> To: address@hidden >> Subject: New Ticket - [netCDF !YYV-457201]: CF/Radial data model need >> for sub-convention on scan_parameters >> Reply-To: address@hidden >> >> >> New Ticket: CF/Radial data model need for sub-convention on >> scan_parameters >> >> Hello, >> First of all my sincere appreciation to one and all involved in the >> development of CF/Radial data model. >> >> This is regarding a CF/Radial sub-convention requirement. >> We have about ten years Doppler weather radar data in OEM proprietary >> format (Gematronik Rainbow - .vol format). I am on the job of >> converting the data format from .vol to .nc compliant with CF/Radial >> data model developing at your end. I am already in touch with Mr.Yuan >> from the IDV support group. He directed me to post my requirement >> here. >> >> >> Now coming to my requirement: >> >> In the CF/Radial model there is need for a sub-convention to say about >> the optional scan_parameter settings made while acquiring the data, may >> be under a head called scan_parameters, covering the data quality >> measures like SQI (Signal Quality Index) , SNR (signal to Noise Ratio), >> CSR (Clutter to signal ratio when frequency domain clutter filters are >> used), type of Clutter filter used and the depth and width of doppler >> filters etc. >> If I am in a different support forum, please forward this mail to the >> right people under intimation to me. >> >> thanks in advance and best wishes for all your endeavors. >> -- >> S B Thampi, >> Director, CDR Station, Chennai, >> Regional Meteorological Centre, >> India Meteorological Department >> >> 10th Floor, Port Trust Centenary Building, >> Rajaji Salai, Chennai 600001 >> >> Ph : +91 44 25393180 (O), >> : +91 44 22248530 (R) >> FAX : +91 44 25360187 >> Mobil: +91 97 91035198 >> >> >> >> >> >> >> Ticket Details >> =================== >> Ticket ID: YYV-457201 >> Department: Support netCDF >> Priority: Normal >> Status: Open >> Link: >> https://www.unidata.ucar.edu/esupport/staff/index.php?_m=tickets&_a=viewticket&ticketid=18796 >> >> > > _______________________________________________ > cfradial-users mailing list > address@hidden > http://www.eol.ucar.edu/mailman/listinfo/cfradial-users > -- S B Thampi, Director, CDR Station, Chennai, Regional Meteorological Centre, India Meteorological Department 10th Floor, Port Trust Centenary Building, Rajaji Salai, Chennai 600001 Ph : +91 44 25393180 (O), : +91 44 22248530 (R) FAX : +91 44 25360187 Mobil: +91 97 91035198
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.