www.archive-org-2014.com » ORG » O » OPENDAP

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".

    Archived pages: 580 . Archive date: 2014-01.

  • Title: DODS Programmers Guide -- A.2.1 Request types
    Descriptive info: Go backward to.. A.. 2 Inputs.. Go up to.. Go forward to.. 2.. 2 Constraint expressions.. 1 Request types.. A DODS server is equipped to respond to several different request types.. Each request type is signified by a different URL suffix.. The server itself is just a dispatch script, that determines the type of a request, and dispatches the request to the appropriate service program, and relays its result back to the client.. In.. figure.. 1.. , a DODS client makes a GET request to a DODS server (which is just an.. httpd.. daemon equipped with a bunch of CGI programs).. The daemon invokes the DODS Server, which is a simple-minded dispatch script which in turn invokes the  ...   Data Descriptor Structure for the specified dataset.. das.. * das.. Returns the Data Attribute Structure for the specified dataset.. dods.. * dods.. Returns binary data in the form of a DODS data document.. See.. Section.. 3.. asc.. asciival.. Converts data requests to ASCII values before sending them back to the client.. This service is useful for invoking from simple web browsers.. info.. usage.. Returns an HTML formatted version of the dataset DDS and DAS, and any other server and dataset information provided in *.. ovr files.. html.. none.. Returns a URL constraint expression builder form, based on the dataset DDS and DAS.. This is the DODS WWW interface.. ver.. Returns the server version information.. Tom Sgouros, July 2, 2004..

    Original link path: /api/pguide-html/pguide_47.html
    Open archive

  • Title: DODS Programmers Guide -- A.2.2 Constraint expressions
    Descriptive info: 3 Server functions.. A DODS server can accept a "constraint expression" contained in the URL query string.. The DODS constraint expression describes how a DODS server should subsample a DODS dataset before sending the data back to the client.. The details of the constraint expresssion syntax are covered in.. The OPeNDAP User Guide.. What's important here is simply that the  ...   The "projection" clause of a constraint expression specifies the data variables requested by the client, and the "selection" clause specifies the condition under which the client wants them.. That is, the projection clause might specify that the client wants to see oceanic temperature data, and the selection clause would specify that only records from below 1000 meters should be returned..

    Original link path: /api/pguide-html/pguide_48.html
    Open archive

  • Title: DODS Programmers Guide -- A.2.3 Server functions
    Descriptive info: B Overview of the DODS Client.. Within the context of a constraint expression, a server can implement functions a client would use to specify data.. Since the constraint expression has two kinds of clauses, there are two kinds of server functions: projection and selection.. To implement another server-side constraint function, see.. Following is a list of the canonical server-side functions implemented in all DODS servers.. Selection.. yes.. Projection..

    Original link path: /api/pguide-html/pguide_49.html
    Open archive

  • Title: DODS Programmers Guide -- B Overview of the DODS Client
    Descriptive info: Contents.. Index.. A DODS client is any web client that makes a service request to a DODS server.. Since several of the DODS services return ASCII and HTML data, any web browser, such as Netscape Navigator can be considered a DODS client, so long as it is in the process of making a suitable request to a DODS server.. The clients of interest in this appendix, however, are clients that use the DODS DAP (Data Access Protocol) library to make their requests for data.. Of these clients, there are two varieties: clients that have been written expressly for DODS, and clients that existed in some form already, and that have been adapted to  ...   disk files to read data.. The Modified Program, using the DODS netCDF client library.. The application's code now accesses data by calls to the DODS netCDF library functions.. These are written to be functionally identical to the original netCDF functions, but instead of using a local disk to retrieve data, this library invokes functions from the DODS DAP library, which makes HTTP GET requests to a DODS server.. The client code is unchanged.. Another Way.. An application program can also call the DODS DAP directly, eliminating the need for a client library.. When starting from scratch, this is probably easiest, unless you are an old hand at one of the supported data access APIs..

    Original link path: /api/pguide-html/pguide_50.html
    Open archive

  • Title: DODS Programmers Guide -- Footnotes
    Descriptive info: Footnotes.. (1).. While this manual describes the C toolkit in detail, all of the concepts and much of the structure can be directly translated to the Java toolkit.. (2).. Whatever it is.. The DODS client can be another server, a user application linked with a DODS-compliant API, or a standalone program using the DODS data access protocl API.. In any case, the use of the class libraries described in this document is identical.. (3).. Actually, there is no reason that type, etc.. cannot be stored as an attribute; however, it must be in the.. DDS.. regardless.. (4).. A.. Pix.. is a "pseudoindex" object.. See the libstdc++ documentation for more information.. (5).. For example, the subclasses.. JGConnect.. and.. NCConnect.. exist for JGOFS and NetCDF, respectively.. (6).. A single entry in a sequence, modelled as a row in a relational table, is sometimes called an instance of the sequence.. This is useful terminology, but is occasionally confusing when we are also talking about instances of objects.. (7).. The.. NetCDF.. client library has been rewritten a couple of times  ...   Web and the first http standards.. It stands for "Non-Parsing Header" (See the CGI 1.. 1 Standard for more information.. ), and is the only way to pass data through many httpd servers unparsed.. (9).. You can use this even if you want to access files outside that subtree.. Simply use a symbolic link and make sure that your server is set to follow symbolic links.. (10).. The "Data:" keyword is not in the scope of the text.. so it is possible to have the text.. Data:.. in the.. (11).. Remember that the "how" is to be answered very specifically, and on the user's level (i.. "Do such-and-such, spelled like.. this.. , to make the array returned be nx5 instead of 5xn.. "), and not on the programmer's level (i.. "You use the invert method to return an array of 5xn instead of nx5.. ").. (12).. For the.. Sequence.. data type, the.. contains only the current instance of the data.. Repeated calls to the.. 's.. deserialize.. function are required to return successive instances of the sequence..

    Original link path: /api/pguide-html/pguide_52.html
    Open archive

  • Title: libdap++: Related Pages
    Descriptive info: libdap++.. Updated for version 3.. 11.. 4.. Main Page.. Related Pages.. Namespaces.. Classes.. Files.. Here is a list of all related documentation pages:.. Todo List.. Deprecated List.. Generated on Thu May 3 2012 17:29:41 for libdap++ by.. 1.. 7.. 3..

    Original link path: /api/pref/html/pages.html
    Open archive

  • Title: libdap++: Namespace List
    Descriptive info: Namespace List.. Namespace Members.. Here is a list of all namespaces with brief descriptions:.. libdap.. Generated on Thu May 3 2012 17:29:43 for libdap++ by..

    Original link path: /api/pref/html/namespaces.html
    Open archive

  • Title: libdap++: Class List
    Descriptive info: Class List.. Class Index.. Class Hierarchy.. Class Members.. Here are the classes, structs, unions and interfaces with brief descriptions:.. libdap::AISConnect.. libdap::AISDatabaseParser.. libdap::AISDatabaseReadFailed.. libdap::AISDatabaseWriteFailed.. libdap::AISMerge.. Merge AIS resources.. libdap::AISResources.. Manage AIS resources.. libdap::AlarmHandler.. libdap::Ancillary.. libdap::Array.. A multidimensional array of identical data types.. libdap::ArrayGeoConstraint.. libdap::AttrTable.. Contains the attributes for a dataset.. libdap::BaseType.. The basic data type for the DODS DAP types.. libdap::BaseTypeFactory.. binary_function.. libdap::Byte.. Holds a single byte.. libdap::HTTPCacheTable::CacheEntry.. libdap::ce_parser_arg.. libdap::Clause.. Holds a fragment of a constraint expression.. libdap::Cmp T1, T2.. libdap::Connect.. Holds information about the link from a DAP2 client to a dataset.. libdap::ConstraintEvaluator.. Evaluate a constraint expression.. libdap::Constructor.. libdap::DapIndent.. Class with static methods to help with indentation of debug information.. libdap::DapObj.. Libdap base object for common functionality of libdap objects.. libdap::DAS.. Hold attribute data for a DAP2 dataset.. libdap::DataDDS.. Holds a DAP2.. libdap::DDS.. libdap::DDXParseFailed.. libdap::DDXParser.. libdap::Array::dimension.. libdap::DODSFilter.. Common functions for DODS server filter programs.. libdap::AttrTable::entry.. libdap::Error.. A class for error processing.. libdap::EventHandler.. libdap::fdinbuf.. libdap::fdistream.. libdap::fdostream.. libdap::fdoutbuf.. libdap::Float32.. Holds a 32-bit floating point value.. libdap::Float64.. Holds a 64-bit  ...   Pass parameters by reference to a parser.. libdap::PipeResponse.. Encapsulate a response.. This class provides special treatment for 'stream pipes.. ' It arranges to close them using pclose() instead of fclose().. libdap::RCReader.. libdap::Resource.. Associate a rule with an ancillary resource.. libdap::Response.. libdap::ResponseBuilder.. Build responses for Hyrax server modules/handlers.. libdap::ResponseTooBigErr.. libdap::rvalue.. libdap::Sequence.. Holds a sequence.. libdap::SignalHandler.. libdap::SignalHandlerRegisteredErr.. libdap::StdinResponse.. Encapsulate a response read from stdin.. libdap::Str.. Holds character string data.. libdap::StrCmp T1, T2.. streambuf.. libdap::Structure.. Holds a structure (aggregate) type.. libdap::SUCmp T1, UT2.. libdap::TestHandler.. libdap::UInt16.. Holds an unsigned 16-bit integer.. libdap::UInt32.. Holds a 32-bit unsigned integer.. libdap::UnMarshaller.. Abstract base class used to unmarshall/deserialize dap data objects.. libdap::Url.. Holds an Internet address (URL).. libdap::USCmp UT1, T2.. libdap::Vector.. Holds a one-dimensional collection of DAP2 data types.. libdap::XDRFileMarshaller.. Marshaller.. that knows how to marshall/serialize dap data objects to a file using XDR.. libdap::XDRFileUnMarshaller.. Unmarshaller that knows how to unmarshall/deserialize dap objects using XDR from a file.. libdap::XDRStreamMarshaller.. that knows how to marshal/serialize dap data objects to a C++ iostream using XDR.. libdap::XDRStreamUnMarshaller.. libdap::XDRUtils.. XMLWriter..

    Original link path: /api/pref/html/annotated.html
    Open archive

  • Title: libdap++: File List
    Descriptive info: File List.. File Members.. Here is a list of all files with brief descriptions:.. AISConnect.. cc.. [code].. h.. AISDatabaseParser.. AISExceptions.. AISMerge.. AISResources.. AlarmHandler.. Ancillary.. Array.. ArrayGeoConstraint.. AttrTable.. BaseType.. BaseTypeFactory.. Byte.. ce_functions.. ce_parser.. cgi_util.. Clause.. config.. config_dap.. Connect.. ConstraintEvaluator.. Constructor.. DapIndent.. DapObj.. DAS.. DataDDS.. DDXExceptions.. DDXParserSAX2.. debug.. dods-datatypes-config.. dods-datatypes-static.. dods-datatypes.. dods-limits.. DODSFilter.. EncodingType.. error-test.. Error.. escaping..  ...   HTTPCacheInterruptHandler.. HTTPCacheMacros.. HTTPCacheResponse.. HTTPCacheTable.. HTTPConnect.. HTTPResponse.. Int16.. Int32.. InternalErr.. Keywords2.. main_page.. doxygen.. mime_util.. ObjectType.. Operators.. parser-util.. parser.. PipeResponse.. RCReader.. regex_test.. Resource.. Response.. ResponseBuilder.. ResponseTooBigErr.. RValue.. SignalHandler.. SignalHandlerRegisteredErr.. StdinResponse.. Str.. Structure.. UInt16.. UInt32.. UnMarshaller.. Url.. util.. util_mit.. Vector.. xdr-datatypes-config.. xdr-datatypes-static.. xdr-datatypes.. XDRFileMarshaller.. XDRFileUnMarshaller.. XDRStreamMarshaller.. XDRStreamUnMarshaller.. XDRUtils.. Generated on Thu May 3 2012 17:29:46 for libdap++ by..

    Original link path: /api/pref/html/files.html
    Open archive

  • Title: Writing an OPeNDAP Server -- 1 Preface
    Descriptive info: Top.. 2 Before you write any code.. 1 Preface.. Writing your own OPeNDAP server is one way to serve data to clients that understand the Data Access Protocol (DAP).. This tutorial describes the writing of such a server.. James Gallagher jgallagher@gso.. uri.. edu , 2006-08-17, Revision: 14349..

    Original link path: /api/ws-html/writing_server_1.html
    Open archive

  • Title: Writing an OPeNDAP Server -- 2 Before you write any code
    Descriptive info: 3 Writing your own OPeNDAP server.. Even if the data you want to serve are stored in some idiosyncratic format, or accessed using an API that you or your group have developed, there may already be a server which, with the correct configuration, can work with your data.. The OPeNDAP project has developed two servers which can be customized to read different types of data.. One, the FreeForm server can be used to provide table and array data, with some restrictions on the data's storage format.. The JGOFS server can only serve table-like data but has a more flexible -- and more complicated -- customization scheme.. More introductory information about these two servers can be found in the.. Server Installation Guide.. 2.. 1 The FreeForm server.. The FreeForm server is configured for a specific dataset using a `format specification file.. ' Detailed information about writing these files for your data may be found in the.. OPeNDAP Freeform ND Server Manual.. The main limitation of the FreeForm server is that it requires that all information be rigidly column-oriented.. For example, consider the two ASCII data files shown below:.. 1 one 13.. 4 1 one 13.. 4 2 two 27.. 8 2 two 27.. 8 3 three 17.. 4 3 three 17.. 4 ASCII data that cannot Data that can be served with FreeForm.. The first file cannot be served by the  ...   or floating point numbers.. This enables the JGOFS server to efficiently serve data that are hierarchical without duplicating values at the outer levels.. Compare JGOFS' nested tables with a regular flat table scheme:.. station depth temp station depth temp 1 10 10.. 2 1 10 10.. 2 20 10.. 3 1 20 10.. 3 30 10.. 0 1 30 10.. 0 2 10 10.. 2 2 10 10.. 35 2 20 10.. 35 30 10.. 0 2 30 10.. 0 Nested Tables A Flat Table Duplicates Values.. The JGOFS server can also read data that's organized in many files, making access to the individual files seamless.. In practice this is quite powerful.. If information about stations, continuing with the example above, is stored in one file and information about each depth/temperature sounding is stored in separate files, JGOFS can easily be configured to serve these data.. In fact, the JGOFS server comes with a standard `method' that can serve data stored in just this configuration as long the data are stored as ASCII values.. However, JOGFS is far more flexible than just a scheme to serve ASCII data.. The JGOFS server is customized by writing a specialized access method for a new data storage format.. For more information about the JGOFS system see the.. JGOFS Data System Overview.. There is also a detailed.. method writing guide.. with examples available for JGOFS..

    Original link path: /api/ws-html/writing_server_2.html
    Open archive





  • Archived pages: 580