An organization seeks to integrate DAP support into their client software in order to allow their software access to data hosted on OPeNDAP servers. Their developer team reaches out to the OPeNDAP team to learn how to best integrate DAP support using the programming language used by the organization’s software.

An organization is interested in serving data through the Hyrax server, but the data storage format used is not covered by the data readers in Hyrax. A developer within the organization reaches out to OPeNDAP and, with help and direction from the OPeNDAP team, contributes a new data reader that can provide access to the organization’s data in the various output encodings available in Hyrax. OPeNDAP team reviews the contribution and, after the appropriate modifications, merges the new feature onto the OPeNDAP code base. The data format can now be read by Hyrax.

An organization is interested in serving data through the Hyrax server, but the workflow of the organization requires a specific data input encoding that is not available in Hyrax. A developer within the organization reaches to OPeNDAP to propose a new response format encoder. With green light from the team, the developer submits the new code for review and, after the appropriate and necessary modifications, the contribution is merged into the base code. The new response format encoder now allows Hyrax to return the requested data in the encoding that the organization workflow needs.