@adigitoleo, you are simply seeing an inconsistency in **ncdump**.   Recent 
version of this utility are not consistent for displaying embedded newlines in 
attributes.  This varies with the type of the internal file format.  Notice 
that true newline characters are displayed with the escape sequence "**\n**" 
inside quotes, in all cases.  However, **netcdf-3** and **netcdf4-classic** 
formats also add the extra visual line break.  From **ncdump -hs**:

    :A = "line 1\n",
        "line 2" ;
    :_Format = "netCDF-4 classic model" ;

Whereas **full netcdf-4** format does not include the extra visual break:

    :A = "line 1\nline 2" ;
    :_Format = "netCDF-4" ;

The first style is traditional and was ubiquitous for several years, until 
support for string data type evolved in one of the early netcdf-4 library 
versions.   I believe that the CF readability policy was conceived early, and 
was based only on the traditional netcdf-3 behavior.

-- 
Reply to this email directly or view it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/347*issuecomment-1009420030__;Iw!!G2kpM7uM-TzIFchu!kswewLGKlhqXyUcVM4jqckHuU95_eFqH2GyvnVRvVlLVBdYrN6C7AfcvABYFzCb3tMl6NuphamM$
 
You are receiving this because you are subscribed to this thread.

Message ID: <cf-convention/cf-conventions/issues/347/[email protected]>
This list forwards relevant notifications from Github.  It is distinct from 
[email protected], although if you do nothing, a subscription to the 
UCAR list will result in a subscription to this list.
To unsubscribe from this list only, send a message to 
[email protected].

Reply via email to