Search results

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
  • WCS GetCapabilities request with pre-built response. ...ES involved in the WCS system, with the BES providing the response to this request.
    4 KB (659 words) - 23:27, 8 January 2009
  • == Proposed Capabilities == ...e to implement the "getCapabilities" service so that clients can query the server about what it can do.
    3 KB (456 words) - 01:07, 24 October 2007
  • Limit data response sizes. Reduce server loading by limiting response sizes for non-authenticated users. This limitation may be extended to authe
    3 KB (553 words) - 21:17, 16 November 2010
  • ...are at least two good ideas floating around for a syntax for building the server-side function URL -- the one used by the F-TDS/GDS servers and the one used For example:
    4 KB (625 words) - 22:36, 17 November 2007
  • ...t implemented, many new technologies have emerged which greatly expand the capabilities of a web-based UI. In this proposal we outline the enhancements possible to * Ubiquitous: The interface is part of the server so it is always present
    4 KB (583 words) - 02:47, 13 April 2010
  • ...support for multiple encodings of the various OPeNDAP services. Providing capabilities documents can also make it easier to plan for extensibility and the future ...scription of server and dataset capabilities (e.g., server-side processing capabilities)
    18 KB (2,567 words) - 20:48, 10 May 2012
  • ...data may take tens of minutes. Another use case that has been discussed is server-side processing which, depending on the processing, may take some time to c ...readily available. The proposal builds on some of the ideas in the [[DAP4: Capabilities and Versioning]].
    11 KB (1,434 words) - 18:11, 24 April 2012
  • The RDH receives and responds to a bes:showCatalog request for the Datasets (ODBC Data Sources) that it is offering. The BES receives a request for a catalog that it identifies as being serviceable by the RDH.
    6 KB (998 words) - 17:46, 29 April 2009
  • The RDH receives and responds to a bes:get request for DAP2 data. The BES receives a request for a DAP2 data that it identifies as being serviceable by the RDH.<font co
    8 KB (1,317 words) - 17:48, 5 May 2009
  • * 1400-1700 Server-side functions * 1000-1030 Beyond DAP 2.0 (DAP4, Semantics, Request/Response-Types, etc.)
    2 KB (204 words) - 21:59, 6 June 2008
  • ...data may take tens of minutes. Another use case that has been discussed is server-side processing which, depending on the processing, may take some time to c ...e not readily available, and it builds on some of the ideas in the [[DAP4: Capabilities and Versioning]] document.
    28 KB (4,197 words) - 17:09, 1 October 2013
  • ...ions]] for information about the OLFS design, implementation and extension capabilities). Thus, it makes the most sense to build a new front-end dedicated to AMQP. ...while the other three interfaces/protocols all use the URL and ignore the request document body. However, it's still part of the OLFS because Hyrax uses SOAP
    17 KB (2,710 words) - 20:45, 19 December 2013
  • #* [[DAP4 Extension: CSV Data Encoding and Response]] #* [[DAP4 Extension: NetCDF Data Response]]
    13 KB (1,672 words) - 17:53, 4 January 2016
  • * [[Hyrax: Asynchronous Response Implementation]] * [[DAP Test Server]]
    4 KB (473 words) - 17:00, 11 April 2019
  • == The Hyrax Data Server Architecture == An overview of the architecture of the Hyrax server. This presentation is intended for software developers. (lecture - 40m)
    6 KB (1,040 words) - 15:57, 2 October 2014
  • ...services return the data in a form Hyrax has been configured to serve. For example, if a web service returns data using HDF4 files, then Hyrax, using the gate ...://host.domain:port'' that will be passed through the gateway module. If a request is made to access a web service not listed on the Whitelist, Hyrax returns
    7 KB (1,180 words) - 22:10, 10 October 2011
  • # Server-side functions as loadable modules for the BES ==== Server Side Functions ====
    14 KB (2,221 words) - 18:10, 18 October 2010
  • These three server operations are required ...et to ''SOS'' an SOS service returns an sos:Capabilities document. The sos:Capabilities document is formed form of the three OWS defined sections ''ows:ServiceIden
    30 KB (4,662 words) - 20:13, 23 August 2009
  • ...t is not practical since large numbers of wcs:Coverages will cause the wcs:Capabilities document to grow to such a size as to be indigestible by clients. Thus it s ...d it is accomplished using NcML configurations similar to the THREDDS Data Server.
    24 KB (3,147 words) - 20:47, 19 December 2013
  • We intend to provide a 'Services' or 'Capabilities' response for DAP4. ...03 error if direct access to the underlying files has been disabled in the server configuration.
    38 KB (5,326 words) - 19:13, 31 August 2012

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)