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

[IDV #SRR-673162]: IDV Locarl Radar Display



Simply add the correct station to local station table, and load the dataset 
from local radar chooser with station selected, don't make it too complicated .

Yuan

Sent from my iPhone

> On Jun 15, 2016, at 11:44 AM, Joel Ix. <address@hidden> wrote:
> 
> New Client Reply: IDV Locarl Radar Display
> 
> Thank you very much for your assistance, I appreciate it.
> 
> I will try the Plugin and I'll let you know if it worked.
> 
> 
> 
> 
> *__________________________________________________Joel Ixcamparij*
> *INSIVUMEH*
> 
> 
> address@hidden> wrote:
> 
>> Hi Joel,
>> 
>> I reread this entire support inquiry with my colleague Tom Yoksas and I
>> wanted
>> to start from square one.
>> 
>> First, the problem is really with the data provider. They should correctly
>> geolocate the radar data.
>> 
>> That said, these problems can be corrected in the IDV in a number of ways,
>> including NCML. But as your latest response points out, this solution is
>> not
>> ideal because you would have to adjust the NCML for every new file.
>> 
>> Going back to the beginning, you mentioned "MCIDAS". Which MCIDAS is that?
>> McIDAS-X or McIDAS-V? We suspect you mean McIDAS-V. If you prefer McV to
>> view
>> the radar data (correctly positioned with your XML file), you can certainly
>> continue with McV to view the METAR surface observations.
>> 
>> https://www.ssec.wisc.edu/mcidas/doc/mcv_guide/1.5/quickstart/Point.html
>> 
>> Contact SSEC for additional questions about McV as this is not a Unidata
>> product.
>> 
>> https://www.ssec.wisc.edu/mcidas/doc/mcv_guide/1.5/quickstart/Point.html
>> 
>> Create an IDV Plugin
>> ====================
>> 
>> As for the IDV, you can correct the location of the radar station with
>> another
>> mechanism that does not involve NCML. We will, instead, create a plugin
>> that
>> contains the `nexradstations.xml' file to correct the station location.
>> 
>> IDV RBI File
>> ~~~~~~~~~~~~
>> 
>> We will first create a RBI (Resource Bundle for the IDV) file. In a text
>> editor,
>> create a `guatemala_radar.rbi' file that has these contents:
>> 
>> <?xml version="1.0" encoding="ISO-8859-1"?>
>> <resourcebundle name="Default">
>>  <resources name="idv.resource.locations">
>>    <resource
>>       id="nexrad"
>>       location="/nexradstations.xml"
>>       type="radar"/>
>>  </resources>
>> </resourcebundle>
>> 
>> Create a Plugin
>> ~~~~~~~~~~~~~~~
>> 
>> Next, go to the Tools --> Plugin Creator menu item. This action will bring
>> forth
>> a Plugin Creator window. Go to the File -> Add File menu item and add the
>> `guatemala_radar.rbi'. Also add the `nexradstations.xml'.
>> 
>> At this point, you are ready to press the "Write Plugin:" button. Call it
>> `guatemala_radar.jar' and make sure to check the "Install" option.
>> 
>> Restart the IDV for the plugin to take effect. You now have the Guatemala
>> radar
>> station available via the IDV Dashboard, Data Choosers Tab, Sat & Radar,
>> Radar
>> option, "NEXRAD - Local" tab. The "Guatemala/Las Nubes (GUA)" option will
>> be
>> available to you in the "Radar Locations" drop down menu.
>> 
>> Now select your `.uf' file. It should plot the radar data in the correct
>> location.
>> 
>> By the way, you can reuse that `guatemala_radar.jar' with other IDVs or
>> you can
>> share it will colleagues. Go to Tools --> Plugin Manager, to bring forth
>> the
>> Plugin Manager window, and go to File -> Install Plugin from File.
>> 
>> Best,
>> 
>> Unidata IDV Support
>> 
>> 
>>> I edited the path to point to the *.UF file, would I have to create a
>> NCML
>>> file for each volume? I load at least 3 or 4 volumes per hour and they
>>> change name.
>>> 
>>> 
>>> 
>>> *__________________________________________________Joel Ixcamparij*
>>> *INSIVUMEH*
>>> 
>>> 
>>> address@hidden> wrote:
>>> 
>>>> Joel,
>>>> 
>>>> If I understand what you are describing, the latitude is essentially
>>>> correct, but
>>>> the longitude is more than half a degree off (0.6177, actually). Is
>> this
>>>> correct? To fix this problem, I would recommend using some NCML. See
>> the
>>>> attached NCML file for an example. You will have to change the
>> "location"
>>>> attribute of the netcdf element to correctly point to your .uf file.
>>>> 
>>>> I've adjust (by 0.6177 longitudinal degrees) a few netcdf attributes
>>>> according to
>>>> what you describe. See the NCML file for details.
>>>> 
>>>> Load that NCML file into the IDV as you would the .uf file. As you can
>> see
>>>> from the
>>>> attached image, the NCML moved the data to the correct location
>>>> (hopefully).
>>>> 
>>>> Let us know if this strategy was successful.
>>>> 
>>>> Best,
>>>> 
>>>> Unidata IDV Support
>>>> 
>>>> 
>>>> 
>>>>> It is located in Guatemala, but the station (center of the Radar
>> data) is
>>>>> slightly moved to* Lat. 14.6, Lon. -89.7.* Correct Coordinates are
>> *Lat.
>>>>> 14.552083, Lon. -90.301611. *Latitude should be fine, it is
>> approximately
>>>>> *14.6* but Longitude is moved almost one degree.
>>>>> 
>>>>> 
>>>>> 
>>>>> *__________________________________________________Joel Ixcamparij*
>>>>> *INSIVUMEH*
>>>>> 
>>>>> 
>>>>> address@hidden> wrote:
>>>>> 
>>>>>> Joel,
>>>>>> 
>>>>>> As far as I can tell, these data load correctly into the IDV. See
>>>> attached
>>>>>> image. In the IDV dashboard, Data Choosers tab, select a Data
>> Source
>>>> Type
>>>>>> of
>>>>>> "Radar files (NEXRAD/DORADE/UF)".
>>>>>> 
>>>>>> I don't think the XML file is necessary. The data are already
>>>> geolocated.
>>>>>> 
>>>>>> Best,
>>>>>> 
>>>>>> Unidata IDV Support
>>>>>> 
>>>>>>> Thanks for the response, What I am trying to do is add the
>> station,
>>>> or
>>>>>> load
>>>>>>> those UF volumes centered at the station. If I select Im Feeling
>>>> Lucky it
>>>>>>> locates the volume in the wrong coordinate (see the image
>> attached).
>>>> Is
>>>>>> it
>>>>>>> possible to add that station to the Local Radar Stations?
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> The correct coordinates are the ones that are included in that
>> XML
>>>> file.
>>>>>>> 
>>>>>>> 
>>>>>>> ?Also I have uploaded the file
>>>>>>> 
>>>>>>> Thank you
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> *__________________________________________________Joel
>> Ixcamparij*
>>>>>>> *INSIVUMEH*
>>>>>>> 
>>>>>>> 
>>>>>>> address@hidden> wrote:
>>>>>>> 
>>>>>>>> Joel,
>>>>>>>> 
>>>>>>>> The XML file does not seem to have any problems: I was able to
>>>>>> correctly
>>>>>>>> geolocate the station in Guatemala (see the attached image).
>>>>>>>> 
>>>>>>>> Can you upload the radar data in question here:
>>>>>>>> 
>>>>>>>> http://motherlode.ucar.edu/repository/alias/idvupload
>>>>>>>> 
>>>>>>>> and let us know when it has been uploaded?
>>>>>>>> 
>>>>>>>> Best,
>>>>>>>> 
>>>>>>>> Unidata IDV Support
>>>>>>>> 
>>>>>>>>> Full Name: Joel Ixcamparij
>>>>>>>>> Email Address: address@hidden
>>>>>>>>> Organization: INSIVUMEH
>>>>>>>>> Package Version: IDV 5.3
>>>>>>>>> Operating System: Linux 64 bits
>>>>>>>>> Hardware:
>>>>>>>>> Description of problem:
>>>>>>>>> 
>>>>>>>>> How can I add my station to the Local Radar Data. I am
>> loading UF
>>>>>> Volumes
>>>>>>>>> but it locates them in the wrong coordinates. I send here an
>> XML
>>>> file
>>>>>>>>> I use with MCIDAS to use that station, but I want to use IDV
>>>> since
>>>>>> IDV
>>>>>>>>> uses Surface Metar Data which can be of use for us.
>>>>>>>>> 
>>>>>>>>> Thanks in advance
>>>>>>>> 
>>>>>>>> 
>>>>>>>> Ticket Details
>>>>>>>> ===================
>>>>>>>> Ticket ID: SRR-673162
>>>>>>>> Department: Support IDV
>>>>>>>> Priority: Normal
>>>>>>>> Status: Closed
>>>>>>>> ===================
>>>>>>>> NOTE: All email exchanges with Unidata User Support are
>> recorded
>>>> in the
>>>>>>>> Unidata inquiry tracking system and then made publicly
>> available
>>>>>> through
>>>>>>>> the web.  If you do not want to have your interactions made
>>>> available
>>>>>> in
>>>>>>>> this way, you must let us know in each email you send to us.
>>>>>> 
>>>>>> 
>>>>>> Ticket Details
>>>>>> ===================
>>>>>> Ticket ID: SRR-673162
>>>>>> Department: Support IDV
>>>>>> Priority: Normal
>>>>>> Status: Closed
>>>>>> ===================
>>>>>> NOTE: All email exchanges with Unidata User Support are recorded
>> in the
>>>>>> Unidata inquiry tracking system and then made publicly available
>>>> through
>>>>>> the web.  If you do not want to have your interactions made
>> available
>>>> in
>>>>>> this way, you must let us know in each email you send to us.
>>>> 
>>>> 
>>>> Ticket Details
>>>> ===================
>>>> Ticket ID: SRR-673162
>>>> Department: Support IDV
>>>> Priority: Normal
>>>> Status: Closed
>>>> ===================
>>>> NOTE: All email exchanges with Unidata User Support are recorded in the
>>>> Unidata inquiry tracking system and then made publicly available
>> through
>>>> the web.  If you do not want to have your interactions made available
>> in
>>>> this way, you must let us know in each email you send to us.
>> 
>> 
>> Ticket Details
>> ===================
>> Ticket ID: SRR-673162
>> Department: Support IDV
>> Priority: Normal
>> Status: Closed
>> ===================
>> NOTE: All email exchanges with Unidata User Support are recorded in the
>> Unidata inquiry tracking system and then made publicly available through
>> the web.  If you do not want to have your interactions made available in
>> this way, you must let us know in each email you send to us.
> 
> 
> 
> Ticket Details
> ===================
> Ticket ID: SRR-673162
> Department: Support IDV
> Priority: Normal
> Status: Open
> Link:  
> https://andy.unidata.ucar.edu/esupport/staff/index.php?_m=tickets&_a=viewticket&ticketid=27185
> 



Ticket Details
===================
Ticket ID: SRR-673162
Department: Support IDV
Priority: Normal
Status: Open
===================
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.



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.