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: OPeNDAP Presentations | OPeNDAP
    Descriptive info: QuickStart.. Support.. Documentation.. User Documentation.. Design Documentation.. Movies.. Project Documentation.. Available Clients.. Available Servers.. Workshops Presentations.. Sources of Data.. Frequently Asked Questions.. Mail Lists.. OPeNDAP Wiki.. › OPeNDAP Presentations.. OPeNDAP Presentations.. Workshops/Presentations.. Globally Distributed Data and the Issues Faced in Building Such a System.. , James Gallagher.. Presentation at the UNESCO IOC/IODE Third Workshop on Ocean Modeling, Ostend, Belgium, Oct.. 19, 2009.. Data Model Evolution in the Data Access Protocol.. , James Gallagher, John Caron, Dennis Hiembigner, Hyo-Kyung Lee, Rikki McQueary, Russ Rew, Muqun Yang.. Poster presented at the Summer ESIP Federation meeting, Santa Barbara, CA, July 2009.. Merging the Data Models of NetCDF and DAP: Design Choices and Benefits.. , James Gallagher, Russ Rew, Rikki McQueary, Dennis Heimbigner and Ed Hartnett.. Poster presented at the Fall 2008 AGU meeting.. The OPeNDAP and Remote NetCDF Invocation (RNI) middleware platform for Scientific Data Fusion.. , Stephan Zednik (zednik@ucar.. edu), Jose Garcia (jgarcia@ucar.. edu), Peter Fox (pfox@cs.. rpi.. edu), Patrick West (pwest@ucar.. edu).. Using Semantic Web Technologies to Streamline the Implementation of the OGC Web Service Interface Specifications for Coverage and Feature Data within OPeNDAP.. , Daniel Holloway1 (d.. holloway@opendap.. org), M.. Benno Blumenthal2 (benno@iri.. columbia.. edu), Nathan Potter2 (ndp@opendap.. org), Patrick West3 (pwest@ucar.. Infusing semantic web into operational data systems: real application experience.. , , Patrick West (pwest@ucar.. edu), Deborah McGuinness, Stephan Zednik.. HDF5-OPeNDAP Project Facilitates se of HDF-EOS Data to track Beijing Air Quality.. This one-page PDF file describes how HDF5 data served using Hyrax has been used to asses and track changes in the air quality of Beijing.. ESIP Federation Hyrax Workshop.. Presentations and other materials for a Hyrax installation and customization workshop presented at the July 2008 ESIP Federation meeting.. The workshop will be presented on the 15th of July.. OPeNDAP/Hyrax Interfaces.. This presentation covers the Hyrax server's various interfaces and was given at the.. Ocean Observatories Initiative.. (OOI) Workshop at UCSD on June 30th 2008.. The presentation focuses on extending Hyrax so that it can be adapted to different systems by adding new functions (aka modules) and protocol handlers to the server.. OPeNDAP Workshops at APAC and the Australian BOM, Oct.. 2007.. Presentations and other materials from the Australian Partnership for Advanced Computing (APAC) and Bureau of Meteorology (BoM) OPeNDAP Workshops.. These workshops focused  ...   to make the poster, so it's large.. However, it will print well, so it's worth a look if you missed the meeting.. The same poster is available as a.. Presentations for the OPeNDAP Data Discovery Workshop.. held at UCAR, 15-16 May 2006.. This page holds presentations (PowerPoint and PDF files) given at the workshop, along with use cases written as a result of discussions.. Also included is a report.. Under constructions as of 30 May 2006.. Presentations for the OPeNDAP/NOAA-PMEL Workshop.. held at the Stennis Space Center, 29-31 September 2004.. These PowerPoint slides cover the ODC, Matlab client, Server installation (including configuration of the Aggregation server developed by Unidata), construction of THREDDS catalogs, Using Ferret, What is FDS and setup of LAS.. In addition, the workshop started with an overview of OPeNDAP and the evolution of networked data systems for science.. NVODS and OPeNDAP (a.. k.. a.. DODS) an Overview.. Presented to TEDS Development group at Antheon Corporation in Newport RI on 7-8 Feb, 2002.. DODS Technical Overview.. NVODS in the End-to-End Oceanographic Data Environment.. Presented at Ocean.. US on 20 November 2001.. NVODS ExComm meeting.. Presentation at the NVODS ExComm meeting, August 2001.. The DODS-NOPP National Workshop.. Presentation at the NVODS National meeting, May 2001.. Oceanology International 2001.. Possibilities of an Interoperable Data System: The DODS Model -- A presentation made at the Oceanology International Americas Symposium.. DODS Regional Workshops 2000-2001.. Summary of the regional workshops.. An overview of DODS.. Based on presentations made at the April 1995.. TOS.. meeting in Newport RI.. and the Nov.. 1995.. SISIC.. meeting in Washington, D.. C.. Updated with version 2 information not presented at either of those meetings.. The.. original overview presentation.. describes version 1.. x of DODS.. Accessing Data using the Distributed Oceanographic Data System.. A general discussion of the DODS data delivery design (SIGNIDR, 3/95).. Data Transport Within The Distributed Oceanographic Data System.. Published in the first issue of the World Wide Web Journal and presented at the.. Fourth International World Wide Web Conference.. The Distributed Oceanographic Data System: Requirements for Data Analysis Applications.. Presented at the Twenty-sixth International Symposium on Remote sensing of Environment, on 25 March 1996.. Report on the First Workshop for DODS, 29 Sept.. to 1 Oct.. 1993.. Available as a.. PostScript.. file..

    Original link path: /workshops
    Open archive

  • Title: SQL Database Server (DRDS) | OPeNDAP
    Descriptive info: About Software Downloads.. All Software.. Hyrax.. WCS.. Matlab - loaddap.. IDL Client.. libdap.. Java Library.. OC.. ODC.. Software from other groups.. ›.. › SQL Database Server (DRDS).. SQL Database Server (DRDS).. The DRDS (DODS Relational Database Server) uses JDBC to communicate with a SQL database.. This hightly configurable server passes virutally all of the DAP constraint expression to the SQL database for evaluation..  ...   DRDS.. war.. file also contains the DODS Test Server (DTS) a highly configurable server used to test client programs.. DRDS 1.. 1.. 7 (31 August 2004).. Binaries.. APache/Tomcat, JVM 1.. 4.. Web Archive file.. (2.. 6 MB).. Source code.. Version 1.. 7.. source jar.. 0 MB),.. documentation jar.. (1.. 5 MB).. 5 (12 March 2004).. 4 MB).. 5.. (6.. 7 MB),.. (980 KB)..

    Original link path: /drds_server
    Open archive

  • Title: The Matlab OPeNDAP Ocean Toolbox | OPeNDAP
    Descriptive info: › The Matlab OPeNDAP Ocean Toolbox.. The Matlab OPeNDAP Ocean Toolbox.. This is a temporary page.. The main web site for the Matlab OPeNDAP Ocean data toolbox is off line due to hardware problems.. We'll get that back up and running ASAP.. This toolbox provides users with access to a number of ocean data sets via OPeNDAP.. The strength of these GUIs is that they expose complicated data sets (often multi-variable, multi-file data sets spread over a number of directories) in an easy to use interface, allowing the user to request only the subset of data -- parameters, spatial and temporal  ...   familiar with one, the others are straightforward to use.. Each of the GUIs calls a function that configures the OPeNDAP request and reformats the returned data stream.. The user can either have the data returned in native mode or OPeNDAP mode.. These functions can also be called directly from the user's scripts by-passing the actual GUI if the user wants scripted access to the data.. To get started, you will first need to download the Matlab Structs Tool onto your system.. Ocean Surface GUIs.. The directory that holds all of the toolbox releases is.. here.. The current release is 2.. 2..

    Original link path: /ml-toolbox
    Open archive

  • Title: netCDF handler | OPeNDAP
    Descriptive info: › netCDF handler.. netCDF handler.. This is the netCDF file module for.. Note: This page lists our 'full releases' of the handler.. Sometimes we make source-only releases or internal releases and don't bother to include them here.. That is why the version numbers you see here have 'gaps.. '.. Our software distributions are signed using a public/private key pair.. See.. Public Key.. for more information.. netCDF handler 3.. 3 / Hyrax 1.. 0 (27 April 2011).. Note:.. This version is part of the Hyrax 1.. 0 Release and requires this version of the server to function.. This version can read netcdf 4 files that have been created using the 'netcdf 4 classic' API/format.. Available soon.. Version 3.. 3.. tar.. gz.. ,.. gpg signature.. Required:.. libdap 3.. 11.. bes 3.. (for Hyrax –this is required to build the BES modules).. Contributed builds.. Contributed.. : Sharing your binary builds for those operating systems not available here.. 2 / Hyrax 1.. 6.. 2 (15 September 2010).. 2 Release and requires this version of the server to function.. This version includes:.. Minor bug fixes and compatibility upgrades for Hyrax 1.. Makes the default setting for adding extra maps and Arrays to Grids be true, since current Java NetCDF library depends on this behavior.. Linux (x86_64).. CentOS 5.. 2, RPMs.. (gcc 4.. 1).. Linux (i386).. 0.. 1 (13 May 2010).. In this release the handler now implements its own transfer_attributes code to merge attributes from its DAS response into the DDS.. This handler now builds with netcdf 4.. 10.. 8.. 0 (09 February 2010).. This release adds information about the 'Shared Dimensions' special option which controls the  ...   handler source code is unchanged.. Fedora Core 8, RPMs.. 9 (5 March 2008).. This release includes modifications for the BES 3.. 0 changes, updated pkg-config support and modernized headers.. This version of the handlers is needed for BES 3.. Fedora Core 6, RPMs.. 8 (4 December 2007).. Fedora Core 6, RPMs (gcc 4.. Intel DMG.. (.. ) , PPC DMG.. 7 (14 November 2007).. 6 (13 March 2007).. Fedora Core 5, RPMs.. Fedora Core 4, RPMs.. 0).. SPARC/Solaris.. Solaris 5.. 8.. 5 (13 Feb 2007).. IRIX.. IRIX 6.. (for the new server–this is required to build the BES modules).. 0 (2 Mar 2006).. Linux (x86_64/i386).. Red Hat Enterprise Linux 3, RPMs.. (gcc 3.. 3).. dap-server 3.. Contributed:.. Sharing your binary builds for those operating systems not available here.. 2 (16 Nov 2005).. (130 KB).. 5 MB),.. (287 KB).. 1 (16 Nov 2005).. Solaris 2.. 0 (31 Oct 2005).. netCDF file module 3.. 7 (9 July 2004).. Win32.. Coming soon!.. Mac OS/X.. OS/X 10.. 3 (Panther), tar.. gz format.. 2 MB).. Build: dynamically linked.. Linux (x86).. Red Hat 7.. 3, tar.. (3.. 7 MB).. Build: gcc 3.. 0, glibc 2.. 5, Kernel 2.. 20, statically linked.. Red Hat 8.. 0, tar.. 2, glibc 2.. 2, kernel 2.. Fedora Core 1, tar.. 8 MB).. 22, dynamically linked.. 2, dynamically linked.. SGI/IRIX.. Build: gcc 2.. 95.. Alpha/OSF1.. OSF1, v5.. 9 MB).. 3, dynamically linked.. (479 KB).. libdap++ 3.. 7 MB).. asciival 3.. (86 KB).. www-interface 3.. (79 KB) and.. packages 3.. (4.. 8 MB).. 6 (17 March 2004).. Linux (i686).. 0 MB).. 1 MB).. 3 MB).. (483 KB).. 4 MB).. (85 KB).. (76 KB) and..

    Original link path: /nc_server
    Open archive

  • Title: CGI Server MATLab file module | OPeNDAP
    Descriptive info: › CGI Server MATLab file module.. CGI Server MATLab file module.. This is the MATLab file module for the.. CGI Server.. You'll also need the CGI Server software.. MATLab file module 3.. 3 (9 July 2004).. (57 KB).. 2 (17 March 2004).. (997 KB).. (56 KB)..

    Original link path: /mat_server
    Open archive

  • Title: CGI Server JGOFS module | OPeNDAP
    Descriptive info: › CGI Server JGOFS module.. CGI Server JGOFS module.. This is the JGOFS module for the.. JGOFS module 3..

    Original link path: /jgofs_server
    Open archive

  • Title: FreeForm Handler | OPeNDAP
    Descriptive info: › FreeForm Handler.. FreeForm Handler.. This is the FreeForm file module for.. '.. FreeForm handler 3.. This version is packaged as part of the Hyrax 1.. 2 release.. Minor build fix and Hyrax 1.. 2 compatibility release.. The handler now implements its own transfer_attributes code to mergeattributes from its DAS response into the DDS.. Fixes:.. Tests no longer require special software.. The new BES configuration file format system is supported.. 12  ...   libdap and the BES.. This release includes modifications for the libdap 3.. 2 and BES 3.. 2 changes.. 8 (6 March 2008).. 7 (4 December 2007).. 6 (14 November 2007).. 5 (13 March 2007).. (for Hyrax – this is required to build the BES modules).. 4 (12 Feb 2007).. (675 KB).. FreeForm File module 3.. 3 (9 July 2004 updated 1 Nov for Win32).. Win32 InstallShield.. (23 MB).. (606 KB).. (609 KB)..

    Original link path: /FreeForm_Handler
    Open archive

  • Title: Bug Fixes and Main Branches | OPeNDAP
    Descriptive info: Get Involved.. Developer Blogs.. Forums.. OPeNDAP Trac.. Developer s TWiki.. › Bug Fixes and Main Branches.. Bug Fixes and Main Branches.. It is useful to understand the structure of the DODS code archives before using CVS to get part of it.. The DODS code evolves along a main trunk (we like the tree metaphor).. When it is deemed ready for a new release, the evolution is halted, and the new revision of the code is released.. However unlikely it seems, there are occasionally bugs in the released code.. Evolution of new features continues apace, however, often rendering the development versions of the code incompatible with the released code.. As bugs are found, therefore, the bug fixes create a new side branch from the main trunk.. When a new release is ready, the bug fixes applied to the side branches are reviewed to see whether they are relevant to  ...   released code may be useless for the next revision.. Here's what it looks like:.. The revision numbers contain clues to the sort of release they are.. Releases along the main branch are numbered 2.. 20, 2.. 21, 2.. 22, 3.. 0 and so on.. The bug-fix releases are numbered starting at the point of departure: 2.. 21.. 1, 2.. 2, 2.. 3, and so on.. When bugs are fixed for the released software, the third part of the version number is incremented.. If features are added to the released software, the first or second part is incremented, depending on the scale of the changes.. So Version 2.. 3 turns into 2.. 4 if a bug fix is added, but might turn into 2.. 22 (or 2.. 22.. 0) if features are added as well.. It might also turn into version 3.. 0 if enough new features are added..

    Original link path: /bug-fixes
    Open archive

  • Title: CGI Server DSP file module | OPeNDAP
    Descriptive info: › CGI Server DSP file module.. CGI Server DSP file module.. This is the Univ.. of Miami DSP file module for the.. DSP handler 3.. 0 (27 October 2006).. This will be a 'source-only' distribution product, and that building this product requires having the Miami DSP Software installed on their build platform.. DSP file module 3.. (115KB)..

    Original link path: /dsp_server
    Open archive

  • Title: How do I find the version of the server I'm talking to? | OPeNDAP
    Descriptive info: How do I find the version of the server I m talking to?.. Wed, 05/11/2011 - 16:20 —.. nehal bathani.. Append `.. ver' to a DODS URL.. Or you can use `version' as the dataset name to get the version of a server without knowing any of the data file names.. returns an XML document that describes the server's software components and their versions in addition to the DAP protocol versions supported by the server.. Older servers return a plain text document with less information.. to post comments..

    Original link path: /node/158
    Open archive

  • Title: OPeNDAP FAQ | OPeNDAP
    Descriptive info: › FAQs.. OPeNDAP FAQ.. General.. What is the OPeNDAP software?.. How do I make my data accessible?.. What is the data format of OPeNDAP servers encoded ?.. What servers are available?.. How do I look at data using OPeNDAP software?.. What clients are available?.. What is the version of ?.. What are the current versions of the OPeNDAP software?.. What happens when an old (core 2.. 22 or before) client talks to a new (core 3.. 0 or after) server?.. OR.. I keep getting an "Expected a variable declaration" error.. How do I announce/publicize that I have a dataset available via OPeNDAP?.. Can I get a netCDF file from an OPeNDAP server?.. Build and Install.. How do I build the software?.. How do I link my application to the netCDF Client Library?.. How do I link my Fortran program to the netCDF Client Library?.. How do I build the netCDF Fortran jackets?.. How do I build the netCDF Client Library on Mac OS/X ?.. Platforms Portability.. On which platforms does the OPeNDAP software run?.. Is the OPeNDAP software available for Windows 95/98 or Windows NT?.. What are the issues involved in building and running the software on the SGI platform?.. How do I build the Matlab server and client on the SGI platform?.. Server Issues.. How do I test my OPeNDAP server(s)?.. How do I find the version of the server I'm talking to?.. How do I configure a secure (i.. , password protected) server?.. How can I determine the usage statistics for my OPeNDAP Server once it is installed?.. How do I report the monthly usage statistics of my OPeNDAP Server to the OPeNDAP team?.. My server works except that really big HDF files and/or compressed files fail and the error message is really odd.. Why can't I get my FreeForm server to serve my data?.. What is the status of the Matlab OPeNDAP Server?.. My aggregation server sits behind a firewall.. When I start it I get a message that the catalog is not valid.. My server doesn't return the ASCII or HTML responses, but all the others (DAS,.. , Info) work fine.. Client Issues.. The Matlab GUI can't find writeval.. The Matlab GUI can't find Inputdlg.. m.. API.. What APIs are available for developing OPeNDAP servers?.. What APIs are available for developing OPeNDAP clients?.. Problems Bugs.. The URLs for all the datasets I serve stopped working when I upgraded my server software to 3.. What is going on and how do I fix the broken URLs?.. It seems that something has changed about the handling of "deflate" in vesion 3.. 4, which is preventing my client from reading station data off the GDS.. What is DODS?.. See our.. What is DODS?.. web page.. How do I make my data accessible?.. Available OPeNDAP servers are listed on our.. "Available OPeNDAP Servers".. If your data is in a format for which an OPeNDAP server has already been written, simply.. download the appropriate server.. and install it on your machine.. (See the.. User's Guide.. for details on how to install a server.. ).. If your data is not in a format with an existing server, you have two options.. First, you can describe your data using the.. FreeForm.. data description language.. Once you can describe your data with FreeForm, you can use the FreeForm server to make your data available.. The second option would be to write a new server for your data format.. The difficulty of this task would depend on the complexity of your data format.. For developing a server in C++, see the.. Programmer's Guide.. and the.. Programmer's Reference.. and the tutorial.. Writing a Server.. For developing a server in Java, see the.. OPeNDAP Java JavaDocs.. Please contact us at.. support@unidata.. ucar.. edu.. to discuss the options before you begin.. What is the data format of OPeNDAP servers encoded?.. The data of OPeNDAP server's response is encoded using the XDR standard (eXternal Data Representation), and packed into the second part of the response document.. For more information on XDR, see.. Internet RFC 1014.. For further details, see.. OPeNDAP Programmer's Guide Section A.. What OPeNDAP servers are available?.. How do I look at data using OPeNDAP software?.. Available OPeNDAP clients are listed on our.. "Available OPeNDAP Clients".. Many of the available clients come OPeNDAP enabled.. Several of them need to be relinked with the OPeNDAP libraries.. Any application that can dereference a URL can be used as a simple OPeNDAP client.. For instance, a standard web browser like Netscape or Internet Explorer can be used to look at various aspects of a OPeNDAP dataset.. description of how to access OPeNDAP data with a browser.. Several spreadsheet applications (e.. g.. , MS Excel and the StarOffice spreadsheet) can also be used as clients.. They still do not have any specific knowledge of the special capabilities of the servers but are more data savvy than completely genereic Web clients.. description of how to access data from an OPeNDAP server with a spreadsheet.. What clients are available?.. "Available OPeNDAP clients".. What is the version of ?.. A few possibilities:.. Run.. ident.. on a particular program.. This will give you the RCS $Id $ information for the pieces of software that make up that program.. For checking the version of a server, see the question.. How do I find a server's version?.. In Matlab or IDL run.. loaddods.. with the '-V' option.. What are the current versions of the OPeNDAP software?.. See our current.. Software Downloads.. or.. 0 or after) server?.. The major change in the core software from version 2.. 22 to 3.. 0 is the addition of several new data types (Int16, UInt16, and Float32).. While old servers will continue to work fine, old clients (those built with core 2.. 22 or before) will not be able to process the new data types.. However, they will work fine if none of the new data types are returned.. This problem can be solved by upgrading to the latest version of the client you are using.. You can.. check on the version of the server you are accessing.. in several ways.. Here's an example of the output old clients will display when handed data in one of the new data types (this example is from loaddods in Matlab):.. loaddods('http://dcz/etc/nph-ff/data/ff/test1.. dat') Reading: http://dcz/etc/nph-ff/data/ff/test1.. dat Constraint: In the dataset descriptor object: Expected a varaible declaration (e.. , Int32 i;).. Make sure that the variable name is not a reserved word (Byte, Int32, Float64, String, Url Structure, Sequence or Grid - all forms, byte, Byte and BYTE, are the same) Could not parse data DDS.. ??? Error in == /usr/local/DODS/src/writeval-2.. 23/loaddods.. mexsol.. How do I announce/publicize that I have a dataset available via OPeNDAP?.. There are several ways to publicize a dataset, depending on the dataset and the community for which it is relevant.. Register the dataset with the OPeNDAP project.. Currently (June 2003),.. go to the web site: http://unidata.. edu/packages/dods.. go to the "Datasets" pull-down menu at the top of the page.. on that menu, go to "NVODS DODS Dataset" item.. This will bring up the NVODS DODS Datasets list of known datasets.. at the top of that page, under the title, click on "Click here to submit a dataset" This will bring up a form asking for the basic information.. Fill out the form and submit it.. If there is other information you would like to provide to potential users, contact user support at support@unidata.. OPeNDAP datasets automatically provide web pages to access the data.. The page is basic, and provides no special information about the dataset beyond the variables in it.. The next step in providing intelligent access for users is to.. Create a web page that describes the data and provides access to the data through OPeNDAP.. Examples of such pages are given on the NVODS site: http://nvods.. org Click on the "Data Access Routes" button and go down the page to "Individual Data Provider Sites".. Examples of pages devised and served by various data providers are given there.. Once you have created and served such a page,.. let us know at: contact@nvods.. org and we will add your page to the list if is appropriate to NVODS list.. Make sure that the web page you created provides direct OPeNDAP access to the dataset.. We will work with you to write an appropriate news release to broadcast on the DODS, NVODS, and OPeNDAP web sites.. OPeNDAP is a partner in the DODS (Earth Science Information Partner) in the ESIP Federation.. We will work with you to write an "ESIP Nugget" to send to the Federation for their publicity machine.. See esipfed.. org for more information about the Federation.. Can I get a netCDF file from an OPeNDAP server?.. The OPeNDAP servers do not currently support a service that can return a netCDF files.. So the best bet is to use a client that can access OPeNDAP data and knows how to output netCDF files.. A simple example is the NCO (NetCDF Operators) package, e.. ,.. ncks http://dods_server/dataset.. nc out.. nc.. The NCO package supplies various command line tools for manipulating netCDF files and can be made OPeNDAP aware.. "Available OPeNDAP Clients" web page.. for.. more information on NCO.. Note: NCO tools can also be used to dump data in ASCII (like the OPeNDAP '.. asc' extension) or IEEE binary format.. How do I build DODS?.. Build Procedures?.. How do I link my application to the netCDF Client Library?.. If your application accesses netCDF data through the standard netCDF library, it should be fairly straight forward to relink it with the OPeNDAP enabled netCDF library.. First off, you will need some OPeNDAP libraries: the third-party-packages libraries; the OPeNDAP core (DAP) libraries; and the OPeNDAP netCDF library (see the.. Note.. below for some comments on library and compiler compatibilities).. Second, you need to link your application with these libraries.. This should involve adding several library flags to your normal compiling/linking commands.. In particular:.. Instead of '-I/usr/local/netcdf/include' use the results of ncdap-config --cflags.. Instead of '-L/usr/local/netcdf/lib' and '-lnetcdf' use the results of ncdap-config --libs.. For instance,.. OPeNDAP libnc-dap 3.. 4 release.. g++ -c -o sample.. o `ncdap-config --cflags` sample.. c.. g++ -g -o sample sample.. o `ncdap-config --libs`.. We have found that using our pre-built binary versions of the libraries for relinking with your application can be problematic.. The reason is that the compiler used to compile your application must match the compiler used to build the OPeNDAP libraries (often the version of compiler is important, too).. For this reason, we generally suggest that you build the OPeNDAP libraries from source using the compiler you use to build your application.. We are using the GNU compilers (GCC 4.. 1 as of 22 Jul 2009).. So, if you are using the same compiler and would like to try linking with our pre-built binaries, please.. let us know.. if you successfully link to our binary releases.. How do I link my Fortran  ...   used for the second argument is relative to the server's DocumentRoot) and use HTTP/1.. Following the GET line there are one or more HTTP/1.. 1 headers which supply additional information to the server.. HTTP/1.. 1 only.. requires.. that the Host: header be present.. There are other request headers you can use.. Consult the HTTP/1.. 1 specification.. Here is an example.. The matching URL is http://dodsdev.. gso.. uri.. edu/dods-test/nph-dods/data/nc/fnoc1.. dds.. [jimg@comet jimg]$ telnet dodsdev.. edu 80 Trying 198.. 116.. 229.. Connected to dodsdev.. Escape character is '^]'.. GET /dods-test/nph-dods/data/nc/fnoc1.. dds HTTP/1.. 1 Host: dodsdev.. edu HTTP/1.. 0 200 OK XDODS-Server: DAP/3.. 2 Date: Thu, 08 Jul 2004 17:01:59 GMT Last-Modified: Mon, 15 Apr 2002 22:49:39 GMT Content-type: text/plain Content-Description: dods_dds Dataset { Int16 u[time_a = 16][lat = 17][lon = 21]; Int16 v[time_a = 16][lat = 17][lon = 21]; Float32 lat[lat = 17]; Float32 lon[lon = 21]; Float32 time[time = 16]; } fnoc1.. nc; Connection closed by foreign host.. A few things to think about if your server isn't working:.. Check the permissions on your CGI scripts.. They must have execute permission.. If you are using a FreeForm server, see the question.. Why can't I get my FF server to serve my data?.. How do I find the version of the server I'm talking to?.. How can I determine the usage statistics for my OPeNDAP Server once it is installed?.. OPeNDAP server software resides on the same computer (in general) as the data being served.. The OPeNDAP server will use some lower-level web server software (e.. , Apache Server or Tomcat) to make the actual connection to the Internet.. Most web server software creates and maintains a log file of all the incoming (http, e.. ) requests, and some indication of the success and/or failure mode of the response.. The log files are often in a standardized form but are individually configurable by the system administrator.. Most sites that are interested in the usage of their OPeNDAP server(s) have developed scripts they run, typically once per month, to derive "metrics" of the usage of their server.. These "metrics" might include: number of hits, number of successful hits, number of repeat users, and volume of data delivered.. A few details for Linux or unix machines running an Apache web server.. A typical place to look for the web server logs is.. /usr/local/apache/logs.. but the actual location depends on how and where the server was installed.. Check with your system administrator for the specifics on your machine.. You can find more information on Apache's server software at http://www.. apache.. org, including more information on log files.. There are also freeware log analysis packages available that could be useful.. For instance, you can check out Analog logfile analysis at:.. http://www.. analog.. cx/.. How do I report the monthly usage statistics of my OPeNDAP Server to the OPeNDAP team?.. You are under no obligation to report your OPeNDAP server usage statistics to the OPeNDAP project.. However, if you are willing to share this information, it will help us direct future software development efforts more effectively.. For the OPeNDAP C++ servers, you can enable the sharing of this information when you install your servers with the.. installServers.. script.. When the install script asks about gathering access statistics, answer yes ("y") and provide the additional information requested.. Your servers usage statistics will only be accessible by the local host (your machine) and the official OPeNDAP machine.. Your server has one or both of the following (easy to fix) problems.. The cache directory is too small and/or your server cannot find gzip.. If the cache directory is too small then files will be purged from the cache too soon resulting in a huge performance degradation.. If your server cannot find gzip, it won't be able to decompress files before serving them.. When the OPeNDAP software is used to serve compressed files (e.. files compressed using gzip), the files are first decompressed and then stored in a cache; data served are read from those cached files.. The location of the cache directory is /usr/tmp by default.. This can be changed by editing nph-dods and changing the value of $cache_dir.. The software is set by default to limit the size of this directory to 50 MB.. However, if you're serving large files, or are experiencing a large volume of traffic, you should increase this.. To do so, edit the value of of the second parameter to 'purge_cache()' on line 125 of nph-dods.. The cache size is given in MB, so changing the 50 to 100 would increase the cache size from 50MB to 100MB.. Finally, the decompression software uses the gzip program to do its work.. If your computer does not have the gzip program in its /bin directory you'll need to edit the DODS_Cache.. pm so that the correct version of gzip is used.. Look in that file for "/bin/gzip" and replace that text with the correct pathname.. To figure out where gzip is on you computer, type 'which gzip' in a shell.. Why can't I get my FF server to serve my data?.. Here are a few suggestions for troubleshooting your FF server:.. 1) First, test that your format files are defined properly and that it fits your data files by running.. chkform.. on them.. You can also check that your data is being interpreted as you desire by running.. newform.. Both.. and.. are FreeForm tools that come with the DODS FreeForm Server distributions.. (They should be located in the bin/ directory of your distribution.. So that.. can display your data, you will need an 'ASCII_output_data' section in your format description file.. Like this:.. ASCII_input_data "test".. Time 1 10 double 4.. Test 12 33 enote 20.. ASCII_output_data "test".. Test 12 33 enote 16.. 2) If you are serving ASCII data, pay attention to the whitespace in your data files.. FreeForm will gag if whitespace extends beyond the line length determined by the format description.. For instance, if the format descriptor fits.. '34.. 523 1.. 45'.. FF will give an error on.. 45 '.. There needs to be whitespace filler if the data in a line doesn't cover the entire format.. For instance, if the format descriptor fits this data.. 456 234.. 456'.. FF will die on this data.. but will not die on.. The enote type doesn't seem to work quite like that.. For instance, if the format fits.. 456 2.. 34e-2'.. FF will die on.. 3e-2 '.. What is the status of the Matlab OPeNDAP Server?.. As of September 2003.. The Matlab OPeNDAP Server was written when Matlab 4 was current.. The server supports all of the data types Matlab supported at the time.. The server was never updated to handle the newer data types (structures and cell arrays, e.. ) because there was no demand for that capability.. So, when the current server encounters variables of the newer types in a file, it chokes.. The level of interest in adding these capabilities is currently unclear.. If anyone is actively interested in these capabilities, please let us know at.. The best way to move forward with this activity would be to find a champion for the Matlab server who can drive the development effort.. We can provide them with as much help as they need, although experience with C++ would be required.. If no one comes forward we can add it to our schedule but we're booked pretty tight for the next six months.. If you know of someone who might be interested in working to expand the capabilities of the Matlab server, please have them contact us at.. When I start my Aggregation Server, I get the following:.. DEBUG: AggServer: CatalogServlet copy /usr/local/jakarta-tomcat/webapps/thredds/initialContent/dodsC/ to /usr/local/jakarta-tomcat-4.. 27-LE-jdk14/content/thredds/dodsC/ (04-04-19 10:57:08 ) DEBUG: AggServer: catalog config /usr/local/jakarta-tomcat-4.. 27-LE-jdk14/content/thredds/dodsC/catalogConfig.. xml is not valid (04-04-19 10:57:09 ).. From: Tony Jolibois tjolibois at cls.. fr.. The error didn't come from the catalog itself, but from the network configuration of my computer.. In the configuration catalog of the AS server, there are some http URLs:.. !DOCTYPE catalog SYSTEM "http://www.. unidata.. edu/projects/THREDDS/xml/AggServerCatalog.. dtd" catalog name="MERCATOR DODS Aggregation Server Catalog" version="0.. 6" xmlns="http://www.. edu/thredds" xmlns:xlink="http://www.. w3.. org/1999/xlink".. My environment was this: I have a firewall, and my computer was not open to Internet, so it could not connect to the two sites.. org.. I tested the local copy of.. AggServerCatalog.. dtd.. InvCatalog.. but it didn't work.. After opening the connection to these two URLs at the firewall, all works fine now.. Conclusion: if your computer cannot connect to these sites, you won't be able to run an Aggregating server.. Thanks Tony for tracking this down and providing this FAQ!.. My server doesn't return the ASCII or HTML responses, but all the others (DAS,.. The ASCII and HTML responses are generated by accessing the server using the URL (a future version of the server may use a different design; this is true for version 3.. 4 and may be true for some later versions).. If you are serving data behind a firewall which uses NAT for address traslation, the DNS lookup for the host name can fail.. Greg Miller from the USGS tracked down this problem and came up with a solution:.. I am behind a firewall that uses NAT translation, so if it was relying on DNS to find the address, it would fail.. I checked my host file and discovered that Red Hat maps the server name into the loopback address and not the IP address of the ethernet interface.. I corrected the host file, and everything works fine.. Thanks Greg!.. Make sure your DODS_ROOT environment variable is set properly.. It should points towards the DODS top level directory.. For instance, if you expanded the DODS binary release tar file in /usr/local, set DODS_ROOT to "/usr/local/DODS".. If you are running the GUI from within the $DODS_ROOT/bin/matlab-gui directory, make sure PATH includes the current working directory (i.. , '.. ').. The Matlab GUI can't find inputdlg.. If you get a message in Matlab that the function/file 'inputdlg' cannot be found, go to $DODS_ROOT/bin/matlab-gui/ and copy inputdlg.. tpl to inputdlg.. API Issues.. What APIs are available for developing OPeNDAP servers?.. The OPeNDAP C++ implementation contains a DAP API/library and CGI dispatch framework.. The OPeNDAP Java implementation contains a DAP API and servlet framework.. The GrADS DODS Server (GDS) includes a Java servlet framework for developing OPeNDAP servers.. What APIs are available for developing OPeNDAP clients?.. The OPeNDAP C++ implementations DAP API/library can be used to develop OPeNDAP clients.. The OPeNDAP Java implementations DAP API can be used to develop OPeNDAP clients.. The OPeNDAP C++ implementations netCDF client library is an OPeNDAP enabled version of the netCDF interface.. The Unidata netCDF Java library is OPeNDAP enabled "out of the box" and includes OPeNDAP specific extensions for dealing with OPeNDAP data types that don't fit in the netCDF data model.. Problems and Bugs.. What is going on and how do I fix the broken URLs?.. See our web page on the.. changing of the servers name..

    Original link path: /faq2
    Open archive

  • Archived pages: 580