Hi Jon, all, Ethan here. Yes, those last few messages were from John. The current plan is to get a 4.3 release out in the next few (3-6?) months and a 4.2.9 release out in the next few weeks. Moving up to the ncWMS trunk wasn't in the plans for 4.2.9 but we can revisit that. Am I understanding correctly that upgrading TDS 4.2.9 (which does NOT have the CDM 4.3 calendar handling) to use the ncWMS trunk would fix the problem Jennifer is seeing? That it is not dependent on the CDM calendar upgrade? Thanks, Ethan > Hi (is this John by the way?), > > It will need more than a sync with CdmUtils - the ncWMS code went > through a significant refactoring some time ago, which affects > several classes. It's not too complicated but let me know when > you plan to do the sync and I can work on the WMS side if it helps. > > Jon > > -----Original Message----- > From: Unidata THREDDS Support [mailto:address@hidden > Sent: 12 September 2011 21:56 > To: address@hidden > Cc: address@hidden; address@hidden; address@hidden; address@hidden; > address@hidden > Subject: [THREDDS #DMW-148403]: Godiva not working with 365 day calendar > > Hi Jennifer: > > this is what im getting with new code: > > 7284.5 days since 2020-01-01 00:00 == 2039-12-16T12:00:00.000Z > > is that what you expect? > > Jon: > > I assume that uk.ac.rdg.resc.ncwms.cdm.CdmUtils needs to by synced with ncWms > trunk? > > If so, we are expecting to do this for 4.2.9 release. Jon Blower wrote: > Hi Jennifer, all, > > The code to do this already exists in ncWMS - we just need to fold it > in to THREDDS, which I guess will happen for TDS 4.3 (John?) > > Some folk on this list have I think already created their own version > of THREDDS that's synced to the ncWMS codebase, so one of them might > be able to send you their own build. > > (BTW, ncWMS supports 360-day, 365-day and 366-day calendars.) > > HTH, > Jon > > -----Original Message----- > From: Unidata THREDDS Support [mailto:address@hidden > Sent: 12 September 2011 18:23 > To: address@hidden > Cc: address@hidden; address@hidden; address@hidden; address@hidden > Subject: [THREDDS #DMW-148403]: Godiva not working with 365 day calendar > > Hi Jennifer: > > 1) i am forwarding this to jon blower to see what he thinks. > > 2) can i get the file that has this calendar in it? im adding > calendar support to TDS 4.3 and need some test cases. > > thanks for reporting > > > Hello, > > > > We are trying to upgrade our TDS so that we can leverage Godiva's > > viewing capability with our climate change data. We get the > > following error from Godiva. Is there any way to extend Godiva to > > support 365 day times, since most climate data will have this > > structure. Or do you have any other suggestions on how we can make this > > work. > > > > Thanks Jennifer > > > > --------------------------------------------------------------------- > > 2011-09-09T17:45:05.267 -0600 [ 101148][ 31] INFO - > > thredds.server.wms.ThreddsWmsController - Remote host: 18.104.22.168 - > > Request: "GET > > /thredds/wms/anomalies/downscaled/seasonal/tas_SRESB1_near_seasonal_do > > wn_anomaly.nc?item=menu&menu=&request=GetMetadata > > HTTP/1.1" > > 2011-09-09T17:45:05.278 -0600 [ 101159][ 31] ERROR - > > thredds.server.wms.ThreddsWmsController - dispatchWmsRequest(): Exception: > > java.lang.IllegalArgumentException: The calendar system 365_day cannot > > be handled > > at uk.ac.rdg.resc.ncwms.cdm.CdmUtils.getTimesteps(CdmUtils.java:335) > > at uk.ac.rdg.resc.ncwms.cdm.CdmUtils.findAndUpdateLayers(CdmUtils.java:191) > > at thredds.server.wms.ThreddsDataset.<init>(ThreddsDataset.java:105) > > at > > thredds.server.wms.ThreddsWmsController.dispatchWmsRequest(ThreddsWmsController.java:163) > > at > > uk.ac.rdg.resc.ncwms.controller.AbstractWmsController.handleRequestInternal(AbstractWmsController.java:195) > > at > > org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153) Ticket Details =================== Ticket ID: DMW-148403 Department: Support THREDDS 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.