Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation update re: DAP2 protocol reserved keywords #308

Closed
WardF opened this issue Aug 24, 2016 · 2 comments
Closed

Documentation update re: DAP2 protocol reserved keywords #308

WardF opened this issue Aug 24, 2016 · 2 comments

Comments

@WardF
Copy link
Member

WardF commented Aug 24, 2016

The following was sent out by @DennisHeimbigner to the thredds community; it contains information that needs to be propagated into the netCDF-C documentation.


I have been asked to share this information with the
thredds community.

In the OPeNDAP DAP2 protocol, there are a number of
keywords. These keywords are case insensitive and if
you use one of them as your variable names, you may
encounter odd behavior such as case changes
(depending on the client DDS/DAS parser)

Anyway, below is the list of reserved keywords as used by the
netcdf-C library parser.
=Dennis Heimbigner
Unidata

"alias",
"array",
"attributes",
"byte",
"dataset",
"error",
"float32",
"float64",
"grid",
"int16",
"int32",
"maps",
"sequence",
"string",
"structure",
"uint16",
"uint32",
"url",
"code",
"message",
"program_type",
"program",

@WardF
Copy link
Member Author

WardF commented Sep 19, 2016

Documentation updated in branch gh308; when travis checks end, I will merge over.

WardF added a commit that referenced this issue Sep 19, 2016
@WardF
Copy link
Member Author

WardF commented Sep 20, 2016

Fixed, merged.

@WardF WardF closed this as completed Sep 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant