David- I am indeed sorry it took so long. I kept thinking this was an ncml problem and it was not. > I believe the netcdf libraries use the opendap protocol to access remote > datasets, is this correct? Yes, by default, most data is accessed using opendap. The most recent version of tds supports (now) a new protocol called cdmremote which properly handles groups. But I see in looking at your catalog, that is option is not available to you. >Are there not potential work around solutions to explore, within for >example ucar.nc2.Group class and its addVariable method? At a minimum >perhaps a try catch could be used instead of throwing a new exception. There are two short term solutions I can think of. 1. when duplicate variables are encountered, the second one is renamed to some unique name. 2. record the fact that there is a duplicate variable as an attribute 3. Use structs to simulate groups. The best current solution is to do consistent renaming of variables, dimensions, etc. to include the group path as part of the name. This is on our list of tasks to do (see https://www.unidata.ucar.edu/jira/browse/CDM-66). I will bump the priority on this. > As someone that relies on the netCDF library, I am surprised that 3 > months after submitting this issue, the ticket is closed with a > recommendation to use a different protocol. The issue is not closed for me. I want to see if we can find a usable quick fix (well, 3 months makes any solution not quick). The "closed" state in our e-support is just an artifact of e-support. The Jira issue is still open. =Dennis Heimbigner Unidata Ticket Details =================== Ticket ID: SBZ-133456 Department: Support netCDF Java Priority: Critical 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.