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.
Hi Verónica, This is very likely related to a non-standard character in your NCML file specifically on line 4. Perhaps it is an accented character or an apostrophe? Please replace the non-standard character with a standard ASCII character. Also, note the IDV may trying to automatically create an NCML file in the "userpath", \Users\Verónica\, which has an accented character. You can alter the userpath with the -userpath command line option. For example, from the Windows command prompt (cmd.exe), you can start the IDV with C:\Program Files\IDV_5.3\runIDV.bat -userpath C:\<Some directory> See here for more information about command line options: https://www.unidata.ucar.edu/software/idv/docs/workshop/installandstart/CommandLineArguments.html The problem is you have to find a directory path that you have ownership that does not contain an accented character. Please keep up us up to date on your progress. Best, Unidata IDV Support > Full Name: Verónica Belchior > Email Address: address@hidden > Organization: FCUP > Package Version: 5.3 build date:2016-05-23 19:17 UTC > Operating System: Windows 8.1 > Hardware: Java: home: C:\Program Files\IDV_5.3\jre version: 1.8.0_45 > j3d:1.6.0-pre9-daily-experimental daily > Description of problem: Updating data source > Grid data source failed making data set: > C:\Users\Verónica\.unidata\idv\DefaultIdv\tmp\multigrid_90c12a70-6f18-42ca-8b80-976198a1fcd90.ncml > Error on line 4 of document > file:C:/Users/Verónica/.unidata/idv/DefaultIdv/tmp/multigrid_90c12a70-6f18-42ca-8b80-976198a1fcd90.ncml: > Invalid byte 2 of 4-byte UTF-8 sequence. > > ****************** > Stack trace: > java.io.IOException: Error on line 4 of document > file:C:/Users/Verónica/.unidata/idv/DefaultIdv/tmp/multigrid_90c12a70-6f18-42ca-8b80-976198a1fcd90.ncml: > Invalid byte 2 of 4-byte UTF-8 sequence. > at ucar.nc2.ncml.NcMLReader.readNcML(NcMLReader.java:237) > at ucar.nc2.ncml.NcMLReader.readNcML(NcMLReader.java:206) > at ucar.nc2.dataset.NetcdfDataset.acquireNcml(NetcdfDataset.java:1081) > at ucar.nc2.dataset.NetcdfDataset.openOrAcquireFile(NetcdfDataset.java:723) > at ucar.nc2.dataset.NetcdfDataset.openDataset(NetcdfDataset.java:427) > at ucar.nc2.dataset.NetcdfDataset.acquireDataset(NetcdfDataset.java:528) > at ucar.nc2.dt.grid.GridDataset.open(GridDataset.java:117) > at ucar.nc2.dt.grid.GridDataset.open(GridDataset.java:103) > at > ucar.unidata.data.grid.GeoGridDataSource.doMakeDataSet(GeoGridDataSource.java:1189) > at > ucar.unidata.data.grid.GeoGridDataSource.getDataset(GeoGridDataSource.java:1211) > at > ucar.unidata.data.grid.GeoGridDataSource.doMakeDataChoices(GeoGridDataSource.java:1238) > at ucar.unidata.data.DataSourceImpl.getDataChoices(DataSourceImpl.java:1856) > at > ucar.unidata.data.grid.GeoGridDataSource.reloadData(GeoGridDataSource.java:619) > at > ucar.unidata.idv.IdvPersistenceManager.changeState(IdvPersistenceManager.java:3507) > at > ucar.unidata.idv.IdvPersistenceManager.changeState(IdvPersistenceManager.java:3456) > 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:1217) > at ucar.unidata.util.Misc$3.run(Misc.java:1243) > > > Ticket Details =================== Ticket ID: RFT-251731 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.