NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
John et. al.,I think the server should be configurable to supply whatever URL the administrator wants to set up... however, this doesn't solve the name collision problem. It may be that more thought needs to be put into standardization of the names for data sets... maybe even a registration system whereby users can create names, or at least submit them for acceptance, as a standard name? Just sticking the name into the URL will solve the problem short-term, but I'm concerned that this will morph into many instances of names for identical products and make things more confusing. Since I'm pretty new to THREDDS, perhaps I'm missing something here... correct me if I'm wrong...
Art
On Mon, 29 Nov 2010, Rich Signell wrote:
John, You *were* fixing a problem that was brought up at the NOAA GEOIDE/DMIT/UAF meeting in Seattle two weeks ago. Some of us were complaining that when doing a search across federated THREDDS servers, the datasets that came back all just said "Best Time Series" without any indication of what dataset they were derived from. So we asked if this could be modified to have the "best" tacked onto the end of the original dataset name. I can see that this causes short-term problems, as John Maurer is pointing out, as you would have to change scripts and let users know the URLs have changed. But I'd still rather trade the short term inconvenience for the long term benefit. -Rich On Mon, Nov 29, 2010 at 7:49 PM, John Caron <caron@xxxxxxxxxxxxxxxx> wrote:On 11/29/2010 5:13 PM, John Maurer, IV wrote:Hi All, Prior to TDS 4.2, you used to be able to change the name of a dataset without adversely affecting the URL to its FMRC components (Best Time Series, Constant Forecast, etc.). Although the title is used to construct the URL, everything up to the final _best.ncd used to be arbitrary. Now I'm finding that a change in the dataset name will break the FMRC URL's. For example: http://oos.soest.hawaii.edu/thredds/dodsC/hioos/model/atm/wrf_oa/WRF_Oahu_Regional_Atmospheric_Model_(1.5km)_best.ncd The name gets appended to _best.ncd: "WRF Oahu Regional Atmospheric Model (1.5km)". It used to not matter what went before _best.ncd, and in fact you could even just use the following URL: http://oos.soest.hawaii.edu/thredds/dodsC/hioos/model/atm/wrf_oa/_best.ncd Now if I change that name to something else (e.g. "WRF Oahu Regional Atmospheric Model"), the old URL breaks because it's now expecting the following: http://oos.soest.hawaii.edu/thredds/dodsC/hioos/model/atm/wrf_oa/WRF_Oahu_Regional_Atmospheric_Model_best.ncd Is this the new way it will behave or is it a bug that can be fixed?Hi John: I thought I was fixing a problem. Is there a reason you prefer it the previous way? _______________________________________________ thredds mailing list thredds@xxxxxxxxxxxxxxxx For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/-- Dr. Richard P. Signell (508) 457-2229 USGS, 384 Woods Hole Rd. Woods Hole, MA 02543-1598 _______________________________________________ thredds mailing list thredds@xxxxxxxxxxxxxxxx For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/
Arthur A. Person Research Assistant, System Administrator Penn State Department of Meteorology email: person@xxxxxxxxxxxxx, phone: 814-863-1563
thredds archives: