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

[THREDDS #DGS-484777]: TDS maxStrlen64 attribute injection?

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.


  • Subject: [THREDDS #DGS-484777]: TDS maxStrlen64 attribute injection?
  • Date: Wed, 01 Nov 2017 09:51:08 -0600

The maxstrlen attribute is coming the fact that the file is being
accessed using the DAP2 (/dodsC/) protocol. Is the user accessing the
server using the netcdf-c library?


> 
> Dear TDS support
> 
> I’m running a production instance of TDS 4.6.10
> 
> One of our users is reporting that TDS seems to be injecting a maxStrlen64 
> attribute into downloaded data, which is subsequently causing strings within 
> the data to be truncated to 64 chars. Is it possible to override this 
> behaviour?
> 
> eg:
> 
> [jgs900@raijin3 ~]$ module load netcdf
> [jgs900@raijin3 ~]$ ncdump -h 
> http://dapds00.nci.org.au/thredds/dodsC/fj6/PTHA/AustPTHA_1/SOURCE_ZONES/sunda/TSUNAMI_EVENTS/unit_source_statistics_sunda.nc
>  | grep maxStrlen64
> maxStrlen64 = 64 ;
> char initial_condition_file(table_rows, maxStrlen64) ;
> char tide_gauge_file(table_rows, maxStrlen64) ;
> 
> whereas:
> 
> [jgs900@raijin3 ~]$ ncdump -h 
> /g/data/fj6/PTHA/AustPTHA_1/SOURCE_ZONES/sunda/TSUNAMI_EVENTS/unit_source_statistics_sunda.nc
>  | grep maxStrlen64
> [jgs900@raijin3 ~]$
> 
> 
> Thanks for your help, Jon
> 
> ----
> Jon Smillie
> Virtual Laboratories
> National Computational Infrastructure
> nci.org.au
> 
> 
> 
> 
> 
> 

=Dennis Heimbigner
  Unidata


Ticket Details
===================
Ticket ID: DGS-484777
Department: Support THREDDS
Priority: Normal
Status: Open
===================
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.