[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[THREDDS #FYW-620774]: TDS: forward slashes only in "location"?



Hi Rich,

Sorry, my mistake. I didn't catch that these were location attributes in NcML. 
I tried this in address@hidden values and that worked. Though address@hidden 
values in aggregations are handled behind the scenes with the same code that 
handles address@hidden values, there must be a layer on top that restricts the 
location values in aggregations.

Yes, John's response is correct, forward slashes will always work in both 
situations.

Sorry for the confusion.

Ethan

> Below is the actual dataset that failed in TDS4.  And when I change
> the location to forward slashes, it works.  I just tried it again and
> confirmed.    And I also saw that John (I think) also responded to the
> ticket and said to use forward slashes because they always work
> (windows and linux).
> 
> <netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2";>
> <aggregation type="union">
> <netcdf
> location="http://coast-enviro.er.usgs.gov/models/gom_interop/coastwatch_northeast_lonlat.nc"/>
> <netcdf
> xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2";>
> <variable name="time" shape="time" type="double">
> <attribute name="units" value="seconds since
> 1970-01-01 00:00:00 UTC"/>
> <attribute name="_CoordinateAxisType" value="Time"/>
> <values>1208616253 </values>
> </variable>
> <aggregation dimName="time" type="joinNew">
> <variableAgg name="Rrs_667"/>
> 
> <!--          <netcdf
> location="c:\rps\cf\coastwatch\2009_009_1710_aqua_ex1_Rrs667.hdf"/>-->
> <netcdf
> location="c:/rps/cf/coastwatch/2009_009_1710_aqua_ex1_Rrs667.hdf"/>
> </aggregation>
> </netcdf>
> </aggregation>
> <variable name="Rrs_667">
> <attribute name="coordinates" value="lon lat"/>
> </variable>
> <attribute name="Conventions" value="CF-1.0"/>
> </netcdf>


Ticket Details
===================
Ticket ID: FYW-620774
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.