`thredds` Mailing List Archives

2019 Archives: Listed By Date

Tuesday, 15 October 2019
- Subject: Re: [thredds] ncml/THREDDS Aggregation of Swath Satellite data?
  Author: Antonio S. Cofiño [antonio.cofino@xxxxxxxxx]
- Subject: Re: [thredds] ncml/THREDDS Aggregation of Swath Satellite data?
  Author: Sean Arms [sarms@xxxxxxxx]
- Subject: Re: [thredds] netCDF point subset xml/csv not supported ?
  Author: IJ Ying [tsanah@xxxxxxxxx]
- Subject: [thredds] netCDF point subset xml/csv not supported ?
  Author: IJ Ying [tsanah@xxxxxxxxx]
Monday, 14 October 2019
- Subject: [thredds] ncml/THREDDS Aggregation of Swath Satellite data?
  Author: Michael McDonald [mcdonald@xxxxxxxxxxxxx]
Friday, 20 September 2019
- Subject: Re: [thredds] thredds catalog.xml - Mix different services for different kind of files
  Author: Sean Arms [sarms@xxxxxxxx]
- Subject: Re: [thredds] Hashed password for tomcat-users.xml is not consistent so unable to login
  Author: Vu , Long [vu.long@xxxxxxxxxx]
- Subject: Re: [thredds] Hashed password for tomcat-users.xml is not consistent so unable to login
  Author: Julien Chastang [chastang@xxxxxxxx]
- Subject: Re: [thredds] Hashed password for tomcat-users.xml is not consistent so unable to login
  Author: Sean Arms [sarms@xxxxxxxx]
- Subject: [thredds] Hashed password for tomcat-users.xml is not consistent so unable to login
  Author: Vu , Long [vu.long@xxxxxxxxxx]
- Subject: [thredds] thredds catalog.xml - Mix different services for different kind of files
  Author: Patrick Brockmann [patrick.brockmann@xxxxxxxxxxxx]
Thursday, 19 September 2019
- Subject: Re: [thredds] Thredds behind Nginx reverse proxy server
  Author: Vu , Long [vu.long@xxxxxxxxxx]
Tuesday, 17 September 2019
- Subject: Re: [thredds] Thredds behind Nginx reverse proxy server
  Author: Sean Arms [sarms@xxxxxxxx]
Monday, 16 September 2019
- Subject: [thredds] Thredds behind Nginx reverse proxy server
  Author: Vu , Long [vu.long@xxxxxxxxxx]
Monday, 29 July 2019
- Subject: [thredds] NetCDF-Java/CDM and THREDDS Data Server Releases
  Author: Sean Arms [sarms@xxxxxxxx]
Tuesday, 23 July 2019
- Subject: Re: [thredds] GRIB/NetCDF in openlayers
  Author: Sean Arms [sarms@xxxxxxxx]
- Subject: [thredds] GRIB/NetCDF in openlayers
  Author: Hosenfeld, Nanette [nhosenfeld@xxxxxxx]
Friday, 21 June 2019
- Subject: [thredds] GOES East/West (16/17) Data Access via TDS
  Author: Sean Arms [sarms@xxxxxxxx]
Thursday, 20 June 2019
- Subject: Re: [thredds] THREDDS 4.6.0 fails to start due to Unidata http->https policy
  Author: Sean Arms [sarms@xxxxxxxx]
- Subject: [thredds] THREDDS 4.6.0 fails to start due to Unidata http->https policy
  Author: Shane St Savage [shane@xxxxxxxxxxxxxxxxxxxx]
- Subject: [thredds] End Of Life for access to Unidata TDS using motherlode/atm hosts
  Author: Jennifer Oxelson Ganter [oxelson@xxxxxxxx]
Sunday, 16 June 2019
- Subject: [thredds] 20190616: reminder: major upcoming change to IDD NIMAGE datastream
  Author: Unidata User Support [support@xxxxxxxxxxxxxxxx]
Wednesday, 05 June 2019
- Subject: Re: [thredds] [ldm-users] 20190604: major upcoming change to IDD NIMAGE datastream
  Author: Gilbert Sebenste [gilbert@xxxxxxxxxxxxxxxx]
Tuesday, 04 June 2019
- Subject: [thredds] 20190604: major upcoming change to IDD NIMAGE datastream
  Author: Unidata User Support [support@xxxxxxxxxxxxxxxx]
Friday, 17 May 2019
- Subject: [thredds] THREDDS FMRC Issue with partial/fragmented model runs
  Author: Michael McDonald [michael.mcdonald@xxxxxxxxx]
Tuesday, 19 February 2019
- Subject: [thredds] Netcdf-Java and TDS v4.6.13 Stable Release
  Author: Sean Arms [sarms@xxxxxxxx]
Friday, 18 January 2019
- Subject: Re: [thredds] NetCDF Access failure with matlab and python
  Author: Thomas Cook [tmcook@xxxxxxxx]
- Subject: Re: [thredds] NetCDF Access failure with matlab and python
  Author: Jennifer Oxelson Ganter [oxelson@xxxxxxxx]
- Subject: Re: [thredds] NetCDF Access failure with matlab and python
  Author: Thomas Cook [tmcook@xxxxxxxx]
- Subject: Re: [thredds] NetCDF Access failure with matlab and python
  Author: Thomas Cook [tmcook@xxxxxxxx]
- Subject: Re: [thredds] NetCDF Access failure with matlab and python
  Author: Antonio S. Cofiño [cofinoa@xxxxxxxxx]
- Subject: Re: [thredds] NetCDF Access failure with matlab and python
  Author: Dennis Heimbigner [dmh@xxxxxxxx]
- Subject: Re: [thredds] NetCDF Access failure with matlab and python
  Author: Antonio S. Cofiño [cofinoa@xxxxxxxxx]
- Subject: Re: [thredds] NetCDF Access failure with matlab and python
  Author: Nathan Potter [ndp@xxxxxxxxxxx]
- Subject: Re: [thredds] NetCDF Access failure with matlab and python
  Author: Sean Arms [sarms@xxxxxxxx]
- Subject: Re: [thredds] NetCDF Access failure with matlab and python
  Author: Nathan Potter [ndp@xxxxxxxxxxx]
- Subject: Re: [thredds] NetCDF Access failure with matlab and python
  Author: Sean Arms [sarms@xxxxxxxx]
Thursday, 17 January 2019
- Subject: Re: [thredds] NetCDF Access failure with matlab and python
  Author: Nathan Potter [ndp@xxxxxxxxxxx]
- Subject: Re: [thredds] NetCDF Access failure with matlab and python
  Author: Thomas Cook [tmcook@xxxxxxxx]
- Subject: Re: [thredds] NetCDF Access failure with matlab and python
  Author: Nathan Potter [ndp@xxxxxxxxxxx]
- Subject: Re: [thredds] NetCDF Access failure with matlab and python
  Author: Christian Skarby [christians@xxxxxx]
- Subject: Re: [thredds] NetCDF Access failure with matlab and python
  Author: Thomas Cook [tmcook@xxxxxxxx]
- Subject: Re: [thredds] NetCDF Access failure with matlab and python
  Author: Dennis Heimbigner [dmh@xxxxxxxx]
- Subject: Re: [thredds] NetCDF Access failure with matlab and python
  Author: Thomas Cook [tmcook@xxxxxxxx]
- Subject: Re: [thredds] NetCDF Access failure with matlab and python
  Author: Sean Arms [sarms@xxxxxxxx]
- Subject: Re: [thredds] NetCDF Access failure with matlab and python
  Author: Thomas Cook [tmcook@xxxxxxxx]
- Subject: [thredds] NetCDF Access failure with matlab and python
  Author: Thomas Cook [tmcook@xxxxxxxx]
Thursday, 03 January 2019
- Subject: [thredds] 20190103: impending availability of GOES-17 ABI imagery and products
  Author: Unidata User Support [support@xxxxxxxxxxxxxxxx]