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.
Thanks John, We'll take a look at the file and see what is causing the error. Sean > Classification: UNCLASSIFIED > Caveats: NONE > > Yuan - > > The file appears to have been successfully uploaded. See attached. > > R/ > John > > > -----Original Message----- > From: Unidata IDV Support [mailto:address@hidden] > Sent: Monday, May 06, 2013 9:42 AM > To: Raby, John W CIV USARMY ARL (US) > Cc: address@hidden; Flanigan, Robert T CIV (US); Raby, Yasmina R > CTR USARMY ARL (US); Johnson, Jeffrey O CIV (US); Raby, John W CIV USARMY ARL > (US); address@hidden > Subject: [IDV #VVG-632378]: Unable to view IDV KML in Google Earth > > Greetings John, > > Would you mind uploading the GRIB file? > > http://motherlode.ucar.edu/repository/alias/idvupload > > Don't worry about filling out any of the information - I'll be looking for it. > Just make sure to upload the file using the "Choose File" button shown next to > the Resources input. > > Also, when dealing with WRF output, it's best to post-process the data in > order to destagger the grids. > The IDV can handle the staggered grids, but it increases the computation time > due to the interpolation that needs to occur. > > Cheers, > > Sean > > > Classification: UNCLASSIFIED > > Caveats: NONE > > > > Yuan - > > > > We tested the fix last week and it works fine, however, while testing > > we found another problem. > > > > I can't seem to display certain GRIB files from the Air Force WRF model. > > Filename is us057g1011t48b180000000.grb > > > > Could you help with this problem? > > > > The error dialog is as follows: > > > > IDV 4.0u2 > > > > There was an error loading the data: > > java.lang.NullPointerException > > > > Java.lang.NullPointerException > > at java.lang.String.compareTo(Unknown Source) at > > ucar.nc2.grib.VertCoord$1.compare(VertCoord.java:62) > > at ucar.nc2.grib.VertCoord$1.compare(VertCoord.java:60) > > at java.util.Arrays.mergeSort(Unknown Source) at > > java.util.Arrays.mergeSort(Unknown Source) at > > java.util.Arrays.mergeSort(Unknown Source) at > > java.util.Arrays.mergeSort(Unknown Source) at > > java.util.Arrays.sort(Unknown Source) at > > java.util.Collections.sort(Unknown Source) at > > ucar.nc2.grib.VertCoord.assignVertNames(VertCoord.java:60) > > at ucar.nc2.grib.grib1.Grib1Iosp.addGroup(Grib1Iosp.java:211) > > at ucar.nc2.grib.grib1.Grib1Iosp.open(Grib1Iosp.java:159) > > at ucar.nc2.NetcdfFile.<init>(NetcdfFile.java:1494) > > at ucar.nc2.NetcdfFile.open(NetcdfFile.java:786) > > at ucar.nc2.NetcdfFile.open(NetcdfFile.java:395) > > at > > ucar.nc2.dataset.NetcdfDataset.openOrAcquireFile(NetcdfDataset.java:68 > > 7) at > > ucar.nc2.dataset.NetcdfDataset.openDataset(NetcdfDataset.java:418) > > at > > ucar.nc2.dataset.NetcdfDataset.acquireDataset(NetcdfDataset.java:513) > > at ucar.nc2.dt.grid.GridDataset.open(GridDataset.java:104) > > at ucar.nc2.dt.grid.GridDataset.open(GridDataset.java:90) > > at > > ucar.unidata.data.grid.GeoGridDataSource.doMakeDataSet(GeoGridDataSour > > ce.java:1113) > > at > > ucar.unidata.data.grid.GeoGridDataSource.getDataset(GeoGridDataSource. > > java:1135) > > at > > ucar.unidata.data.grid.GeoGridDataSource.initAfterCreation(GeoGridData > > Source.java:499) at > > ucar.unidata.data.DataManager.createDataSource(DataManager.java:1597) > > at > > ucar.unidata.idv.IntegratedDataViewer.createDataSource(IntegratedDataV > > iewer.java:1980) > > at > > ucar.unidata.idv.IntegratedDataViewer.makeDataSource(IntegratedDataVie > > wer.java:1897) > > at > > ucar.unidata.idv.IntegratedDataViewer.makeDataSource(IntegratedDataVie > > wer.java:1831) > > at > > ucar.unidata.idv.IntegratedDataViewer.makeDataSource(IntegratedDataVie > > wer.java:1804) at > > ucar.unidata.idv.chooser.IdvChooser.makeDataSource(IdvChooser.java:943 > > ) > > at > > ucar.unidata.idv.chooser.FileChooser.selectFilesInner(FileChooser.java > > :656) at > > ucar.unidata.idv.chooser.FileChooser.selectFiles(FileChooser.java:525) > > at > > ucar.unidata.idv.chooser.FileChooser.doLoadInThread(FileChooser.java:5 > > 47) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at > > sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at > > java.lang.reflect.Method.invoke(Unknown Source) at > > ucar.unidata.util.Misc$2.run(Misc.java:1223) > > at ucar.unidata.util.Misc$3.run(Misc.java:1251) > > > > > > -----Original Message----- > > From: Unidata IDV Support [mailto:address@hidden] > > Sent: Thursday, April 25, 2013 2:54 PM > > To: Raby, John W CIV USARMY ARL (US) > > Cc: address@hidden; Flanigan, Robert T CIV (US); Raby, > > Yasmina R CTR USARMY ARL (US); Johnson, Jeffrey O CIV (US) > > Subject: [IDV #VVG-632378]: Unable to view IDV KML in Google Earth > > > > John, > > > > We believe we have a fix. Please download and test the nightly build > > tomorrow with the fix. > > > > http://www.unidata.ucar.edu/downloads/idv/nightly/index.jsp > > > > Best Wishes, > > > > Unidata IDV Support > > > > > Yuan - > > > > > > Thanks for the update. Will be happy to conduct testing if you want. > > > R/ > > > John > > > > > > ________________________________________ > > > From: Unidata IDV Support [address@hidden] > > > Sent: Thursday, April 25, 2013 2:15 PM > > > To: Raby, John W CIV USARMY ARL (US) > > > Cc: address@hidden; Flanigan, Robert T CIV (US); Raby, > > > Yasmina R CTR USARMY ARL (US); Johnson, Jeffrey O CIV (US) > > > Subject: [IDV #VVG-632378]: Unable to view IDV KML in Google Earth > > > > > > > > Yuan - > > > > > > > > > > I tried two times to upload, but get the error shown in the attached. > > > > > I've attached the file to this email. > > > > > > > > > > R/ > > > > > John > > > > > > > > > > > > > Got it, I will take a look. > > > > > > > > > > > > Yuan > > > > > > I see the problem, we will fix this asap. > > > > > > > > > Yuan > > > > > ________________________________________ > > > > > From: Unidata IDV Support [address@hidden] > > > > > Sent: Thursday, April 25, 2013 10:11 AM > > > > > To: Raby, John W CIV USARMY ARL (US) > > > > > Cc: address@hidden; Flanigan, Robert T CIV (US); > > > > > Raby, Yasmina R CTR USARMY ARL (US); Johnson, Jeffrey O CIV (US) > > > > > Subject: [IDV #VVG-632378]: Unable to view IDV KML in Google > > > > > Earth > > > > > > > > > > > Classification: UNCLASSIFIED > > > > > > Caveats: NONE > > > > > > > > > > > > Yuan - > > > > > > > > > > > > Thanks for your reply. Would it help you if I attached the KML > > > > > > file which contains the problem longitude and another KML file > > > > > > which has been corrected to properly render in GE Pro so you > > > > > > can see the difference? > > > > > > > > > > > > I am planning to conduct a test of your suggested workaround, > > > > > > but that may take me a little time. > > > > > > > > > > > > R/ > > > > > > John > > > > > > > > > > If you can upload a sample file (grid file, not kml), it > > > > > certainly helps. > > > > > > > > > > http://motherlode.ucar.edu/repository/alias/idvupload > > > > > > > > > > > > > > > Yuan > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > From: Unidata IDV Support > > > > > > [mailto:address@hidden] > > > > > > Sent: Thursday, April 25, 2013 9:58 AM > > > > > > To: Raby, John W CIV USARMY ARL (US) > > > > > > Cc: address@hidden; Flanigan, Robert T CIV (US); > > > > > > Raby, Yasmina R CTR USARMY ARL (US) > > > > > > Subject: [IDV #VVG-632378]: Unable to view IDV KML in Google > > > > > > Earth > > > > > > > > > > > > > I cannot visualize images captured using IDV in Google Earth > > > > > > > Pro (V7.1.0.8015). The KML files produced by IDV contain > > > > > > > longitude values exceeding 180 degrees which causes the > > > > > > > failure in Google Earth Pro. > > > > > > > Conducted a test to assure that I used the procedure for > > > > > > > capturing KML files per the User's Guide, by executing > > > > > > > "Projections>Use displayed area" before "View>Capture>Image". > > > > > > > Please contact me regarding the resolution of this problem. > > > > > > > > > > > > > > Thanks. > > > > > > > > > > > > > > John Raby > > > > > > > > > > > > > > U.S. Army Research Laboratory White Sands Missile Range, NM > > > > > > > 88002 > > > > > > > (575) 678-2004 > > > > > > > > > > > > > > > > > > > > Hi John, > > > > > > I don't have any dataset with longitude 0 to 360. Otherwise, I > > > > > > would reproduce your problem locally and get better understand > > > > > > of the issue . > > > > > > One option is to call the Formula > Grid > Define a grid > > > > > > diagnostic, and type lonFlip(a). This lonFlip can flip > > > > > > longitudes in a grid from 0 - 360 to -180-180 if the grid is > > > > > > in cyclic rectilinear grids. > > > > > > > > > > > > Let us know if this can help. > > > > > > > > > > > > > > > > > > Yuan > > > > > > > > > > > > Ticket Details > > > > > > =================== > > > > > > Ticket ID: VVG-632378 > > > > > > Department: Support IDV > > > > > > Priority: Normal > > > > > > Status: Open > > > > > > > > > > > > > > > > > > Classification: UNCLASSIFIED > > > > > > Caveats: NONE > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Ticket Details > > > > > =================== > > > > > Ticket ID: VVG-632378 > > > > > Department: Support IDV > > > > > Priority: Normal > > > > > Status: Open > > > > > > > > > > > > > > > > > > > > > > > > > > > > Ticket Details > > > =================== > > > Ticket ID: VVG-632378 > > > Department: Support IDV > > > Priority: Normal > > > Status: Open > > > > > > > > > > > > Ticket Details > > =================== > > Ticket ID: VVG-632378 > > Department: Support IDV > > Priority: Normal > > Status: Closed > > > > > > Classification: UNCLASSIFIED > > Caveats: NONE > > > > > > > > > > Ticket Details > =================== > Ticket ID: VVG-632378 > Department: Support IDV > Priority: High > Status: Open > > > Classification: UNCLASSIFIED > Caveats: NONE > > > > Ticket Details =================== Ticket ID: VVG-632378 Department: Support IDV Priority: High Status: Open