This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
>From: "Salottolo Greg" <address@hidden> >Organization: NTSB >Keywords: 200601091524.k09FOr7s009632 station tables Hi Greg- >Good Morning: > >Just wondering has the file been updated to reflect greater precision >in the NEXRAD lat/lon list? Sorry, that fell through the cracks. It's not in the 1.3b1 distribution. I made an update today to use DD:MM:SS precision (from McIDAS). Download the one from: ftp://ftp.unidata.ucar.edu/pub/idv/tables/nexradstns.xml and place it in your <home>/.metapps/DefaultIdv directory, where <home> is your home directory. (e.g., /home/salottg on Unix or C:/Documents And Settings/salottg on windows). In that directory, you will find a file idv.rbi. Edit that and change the lines: <!-- The list of station table xml files --> <resources name="application.resource.locations"> </resources> to <!-- The list of station table xml files --> <resources name="application.resource.locations"> <resource location="%USERPATH%/nexradstns.xml" id="nexrad"/> </resources> The next time you start the IDV, you will pick up the new station lat/lon information. Let me know if you find any errors in the table. This will be in the next release. >-----Original Message----- >From: Unidata Support [mailto:address@hidden] >Sent: Wednesday, March 23, 2005 3:20 PM >To: Salottolo Greg >Subject: 20050323: NEXRAD locations > > >>From: "Salottolo Greg" <address@hidden> >>Organization: NTSB >>Keywords: 200503231905.j2NJ5Rv2004947 IDV radar locations > >Hi Greg- > >Thanks for your help on this. Our nexradstns.xml was generated >from either a GEMPAK or McIDAS list. Since either of these has >DD:MM:SS precision, it looks like we only took 2 decimal places >when we converted to decimal degrees. I'll just redo the >list again when I get a chance and keep them as DD:MM:SS. >We probably only handled decimal degrees when we generated the >list, but now that either works, we'll keep it in the most >common form. > >Thanks for bringing this to our attention. > >Don Murray Don Murray 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.