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: How do I get data as ASCII (or NetCDF) | OPeNDAP
    Descriptive info: ›.. Frequently Asked Questions.. General.. How do I get data as ASCII (or NetCDF).. Tue, 07/12/2011 - 08:59 —.. jimg.. For a given URL (e.. g.. , http://test.. opendap.. org/dap/data/nc/coads_climatology.. nc) and a given variable in that data set (e.. , SST), you would ask for a those data to be returned as ASCII using the following:.. http://test.. nc.. ascii?SST.. Note that you can take the base URL (http://test.. nc) and append '.. html' to it and get a web page that provides a way to see the names of the variables in a data file, a way to build up more complex constraints interactively and to get those data in several different formats, including ASCII and  ...   NCO (NetCDF Operators) package like this:.. ncks http://test.. nc?SST out.. The NCO package supplies various command line tools for manipulating netCDF files and can be made OPeNDAP aware.. See our "Available OPeNDAP Clients" web page for more information on NCO.. Notes:.. * NCO tools can also be used to dump data in ASCII (like the OPeNDAP '.. asc' extension) or IEEE binary format.. * In this example, the client expects to be passed a DAP URL, so the response format component is not used (i.. , ''coads_climatology.. nc'' is used with a DAP-aware client like NCO, while ''coads_climatology.. ascii'' is used with a browser that does not contain special code to process the DAP URL).. to post comments..

    Original link path: /node/226
    Open archive

  • Title: How do I build DODS? | OPeNDAP
    Descriptive info: Build and Install.. How do I build DODS?.. Wed, 05/11/2011 - 10:49 —.. nehal bathani.. See our.. Build Procedures?.. web page..

    Original link path: /node/148
    Open archive

  • Title: How to Build DODS | OPeNDAP
    Descriptive info: QuickStart.. Support.. Documentation.. User Documentation.. Design Documentation.. Movies.. Project Documentation.. Available Clients.. Available Servers.. Workshops Presentations.. Sources of Data.. Mail Lists.. OPeNDAP Wiki.. › How to Build DODS.. How to Build DODS.. Required or recommended tools.. Setup environment variables (.. more details.. ).. cd $DODS_ROOT.. make sure bin/, lib/, and include/ directories exist.. Currently, make does not create them if needed.. /configure |& tee $LOG_DIR/log.. sun.. 1.. configure (.. note on log files.. $MAKE World |& tee $LOG_DIR/log.. 2.. make.. World (.. Check the ".. Special Directions.. " section below for items applicable to your build.. For developers making a binary or source distribution:.. $MAKE update-version (not yet available from $DODS_ROOT must do this in each component directory).. For binary distribution: $MAKE binary-tar.. For source distribution: $MAKE distclean, $MAKE source.. See the ".. Testing DODS.. " section below for directions on how to test your DODS software.. If any components did not build properly, read the log files and attempt to build each component individually.. I.. , cd to the component directory and follow the steps shown.. below.. in the DAP build.. Required and recommended tools/packages.. GNU gcc/g++ (recommended): has not been tested with other compilers.. May work but will probably need some tweaking of make files.. GNU Make (recommended): the make you use must support the "-C" flag and should set $(MAKE).. GNU tar (recommended).. bison & flex (recommended if you will be rebuilding the grammar stuff, you probably don't want to do this).. DejaGNU (recommended for developers, currently used for testing software).. Setup Your Environment.. Be sure to set all the necessary environment variables for your build environment.. Below is a list of the most commonly required environment variables in the DODS build.. Required:.. DODS_ROOT (e.. , /usr/local/DODS).. Set those appropriate to the DODS components you are building:.. HDF_PATH, MATLAB_ROOT, IDL_ROOT, DSP_ROOT.. Set according to your build environment:.. CPPFLAGS, CC, CFLAGS, CXX, CXXFLAGS, FC, FFLAGS, LDFLAGS, LIBS.. (More than likely you won't need to set any of these.. Set CC and CXX if you don't want to use gcc/g++ or they aren't found on your path.. ).. Set if not found (or wrong version is found) on your path:.. MAKE, PERL, TAR, LEX, YACC.. At this time, GNU make is recommended.. If you are going to be using the netCDF Fortran interface, be sure to set the FC, FFLAGS, and CPPFLAGS appropriately.. See the.. related question.. in our FAQ.. Note on log files.. Saving log files from runs of make and configure is optional (but often useful).. The notation used here '|&' works in csh and tcsh to pipe stdout and stderr.. For sh and ksh, use '|' to pipe stdout.. 'tee' writes back to stdout and  ...   I accomplished it on Redhat 6.. 1 (it is different on Redhat 5.. 2 and I don't have the details):.. Copy /usr/lib/libc.. so into another directory (e.. , /usr/local/dods/rhLib/).. Edit the new copy of libc.. so to remove the reference to libc.. so.. x.. ,.. Original version:.. /* GNU ld script Use the shared library, but some functions are only in the static library, so.. try that secondarily.. */.. GROUP ( /lib/libc.. 6 /usr/lib/libc_nonshared.. a ).. New version:.. */.. GROUP ( /usr/lib/libc_nonshared.. unsetenv LD_LIBRARY_PATH.. add '-L /usr/local/dods/rhLib' to the cmex command.. During the SGI build of the Matlab command line client, if you are building for an architecture that does not match the architecture of the Matlab libraries (o32/mips2 or 64/mips4), the linking of loaddods.. mex* will fail.. For details on building a working version of ml-cmdln, see the.. "Matlab on SGI" FAQ.. At this time, tests for many of the DODS components are specific to our build environment and may not succeed on your local machine without some setup.. This mainly concerns the server software where the tests access the software through a web server.. The tests for the DAP should work and are a good start if you want to make sure your build is succeeding.. From the $DODS_ROOT directory, run '$MAKE check' to test all the available components of DODS.. Or you can run '$MAKE check' from any of the component directories.. Several components have different kinds of tests.. These are listed below:.. Testing of the Matlab command line client is done in two steps.. The first, by running '$MAKE check', tests 'writeval'.. The second tests loaddods/writeval through Matlab.. To run this test, start Matlab with a log file (if desired), e.. , 'matlab | & tee log'.. And then run the following Matlab commands:.. addpath testsuite/matlab.. matlab_tests.. dload.. exit.. And here's a few more you can try:.. loaddods('-V').. loaddods('http://maewest.. gso.. uri.. edu/cgi-bin/nph-dsp/dods/sst_clima_reynolds/reynolds_01.. avg').. das = loaddods('-A', 'http://maewest.. The Matlab GUI does not currently have any prepackaged tests.. When Building Static.. Sun Some system libraries can't be linked statically.. Run with '-Xlinker -Bstatic' instead of '-static' and '-Xlinker -Bdynamic -ldl' at the end g++ -v -g -Xlinker -Bstatic -L/upc/dods/build/DODS/packages-2.. 17/lib -L.. -L.. /.. /lib -o geturl geturl.. o TestByte.. o TestInt32.. o TestFloat64.. o TestStr.. o TestUrl.. o TestArray.. o TestStructure.. o TestList.. o TestSequence.. o TestFunction.. o TestGrid.. o TestUInt32.. o -ldap++ -lwww -lsocket -lnsl -lz -lrx -ltcl7.. 6 -Xlinker -Bdynamic -ldl.. SGI Doesn't seem to like static linking.. Could it be similar to Sun? g++ hdf_dods.. o funcs.. o -o hdf_dods -g -L/upc/dods/hdf4.. 1r2/mips-sgi-irix6.. 2/lib -L/upc/dods/cvsRel3.. 0.. 2/mips-sgi-irix6.. 5/DODS/packages-2.. /lib -Lhdfclass -lhdf-dods -ldap++ -lhdfclass -lwww -lmfhdf -ldf -ljpeg -lz -lz -lrx -lexpect5.. 21 -ltcl7.. 6..

    Original link path: /faq?q=buildProcedureDODS
    Open archive

  • Title: How do I link my application to the netCDF Client Library? | OPeNDAP
    Descriptive info: How do I link my application to the netCDF Client Library?.. Wed, 05/11/2011 - 10:52 —.. 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'  ...   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..

    Original link path: /node/149
    Open archive

  • Title: How do I link my Fortran program to the netCDF Client Library? | OPeNDAP
    Descriptive info: How do I link my Fortran program to the netCDF Client Library?.. Wed, 05/11/2011 - 10:54 —.. There are several possible ways to link your Fortran program with the DODS netCDF library.. The libraries you must specify in the linking step depend on how you compile and link your program.. If linking with g++, you must specify '-lg2c' to make sure you link with the GNU Fortran libraries.. For example,.. g77 -g -c `ncdap-config --fflags` sample.. f.. o `ncdap-config --flibs`.. If you link with g77, use '-lstdc++' to include the C++ library.. If you link with gcc, use '-lstdc++ -lg2c', to link with both the C++ and Fortran libraries.. (You can compile your program with gcc, g++, or g77.. ).. If you are not using the GNU Fortran compiler, you  ...   to specify the GNU C++ library, i.. , '-lstdc++'.. To build the DODS netCDF library yourself, please take a look at the FAQ ".. How do I build the netCDF Fortran jackets?.. " and look for suggestions on building for your compiler (be sure to look in the non-DODS netCDF.. INSTALL.. file).. As you may have guessed, we stick with the GNU compilers when building our binary releases, generally from GCC 4.. 1 (as of 22 Jul 2009).. Here are the environment variables we set:.. CC=gcc.. CXX=g++.. FC=gfortran.. FFLAGS=-g.. CPPFLAGS=-Df2cFortran.. I believe our standard binary release should work for you if you are using g77, f2c, or fort77 (which uses f2c).. This may work for other compilers as well.. Please.. if you successfully link to our binary releases with other compilers..

    Original link path: /link_Fortran_program_to_netCDF
    Open archive

  • Title: How do I build the netCDF Fortran jackets? | OPeNDAP
    Descriptive info: How do I build the netCDF Fortran jackets?.. Wed, 05/11/2011 - 10:56 —.. The main problem here is that, even though no Fortran is compiled while building the netCDF library, you must specify a working Fortran compiler to get the Fortran jackets.. More to the point, you must specify the compiler that you will be using on your Fortran code.. Since every Fortran compiler is different, the C code (the netCDF Fortran jackets) needs to be configured properly to allow communication with the Fortran code (your application).. So, this means that your netCDF library has to have been built with the same Fortran compiler you use to build your Fortran code.. The DODS provided binary releases are built with the GNU compilers (gcc, g++, and  ...   CPPFLAGS, CC, CFLAGS, FC, FFLAGS, CXX, and CXXFLAGS (and perhaps LIBS) to represent [your] environment.. " The documentation (i.. , the.. file) for the non-DODS netCDF package gives environment setups successfully used for a variety of platform/compiler combinations.. Below are the settings we have used with the DODS netCDF client library.. If you need to build it for a different compiler, take a look at the INSTALL file mentioned above.. If you have success with other Fortran compilers, please.. so we can list it here.. GNU Fortran.. Also good when using f2c (or fort77 on Linux).. NAG f90.. FC=f90.. CPPFLAGS=-DNAGf90Fortran.. Now for linking your Fortran code to these libraries, see our FAQ ".. How do I link my Fortran program to the DODS netCDF library?.. "..

    Original link path: /faq?q=buildnetCDFfortranJackets
    Open archive

  • Title: How do I build the netCDF Fortran jackets? | OPeNDAP
    Original link path: /buildnetCDFfortranJackets
    (No additional info available in detailed archive for this subpage)

  • Title: How do I link my Fortran program to the netCDF Client Library? | OPeNDAP
    Original link path: /faq?q=link_Fortran_program_to_netCDF
    (No additional info available in detailed archive for this subpage)

  • Title: How do I build the netCDF Client Library on Mac OS/X ? | OPeNDAP
    Descriptive info: How do I build the netCDF Client Library on Mac OS/X ?.. Wed, 05/11/2011 - 11:00 —.. As is standard practice for OS/X, I replaced etc/config.. guess and config.. sub with /usr/libexec/config.. guess and /usr/libexec/config.. sub.. This allows configure to correctly identify the platform as powerpc-apple-darwin5.. I believe that the latest versions of autoconf come with config.. guess/.. sub files that handle OS/X properly so this should be easy to fix.. The gcc version test in the dap and nc3 configure scripts fails for Apple's modified gcc, because "gcc -v" gives the following output: Reading specs from /usr/libexec/gcc/darwin/ppc/2.. 2/specs Apple Computer, Inc.. version gcc-934.. 3, based on gcc version 2.. 2 19991024 (release) The regexp gets stuck on the ".. " in "Inc.. ", and GCC_VER ends up set to: Apple Computer, I.. 2 19991024 (release) My quick fix for this was to comment out the error message in the case statement and instead set GCC_VER = `gcc --version`, which gives the following output: 2.. 2 I am not knowledgeable enough with autoconf to say how the test  ...   I just commented out the line.. I expect this introduced a memory leak so I we will have to figure out a better solution.. ".. Since I was working with the 3.. 1 release and not the current SVN sources, I commented out various references to libdap++-gui in the dap and nc3/ncdump makefiles.. I had to run ranlib on lib/libwww.. a.. There was a file called "__.. SYMDEF SORTED" which looks like it was supposed to be the symbol table for libwww sitting in the lib/ directory, so perhaps the ranlib command line didn't work quite right the first time.. At this point libdap++.. a and libnc-dods.. a both built successfully.. The linker reported unresolved symbols for add_connect(NCConnect), del_connect(NCConnect), and a few other members of the Connections template.. According to some messages on the web, there are template instantiation bugs in Apple's gcc, and the best fix they had found was to include the instantation as a separate object file.. So I added ".. /inst.. o" to the link line for dncdump and lo and behold, it worked..

    Original link path: /node/152
    Open archive

  • Title: What does DODS run on? | OPeNDAP
    Descriptive info: Platforms Portability.. What does DODS run on?.. Wed, 05/11/2011 - 15:48 —.. DODS Supported Platforms.. page..

    Original link path: /node/153
    Open archive

  • Title: DODS Supported Platforms | OPeNDAP
    Descriptive info: › DODS Supported Platforms.. DODS Supported Platforms.. Sun Sparc Solaris.. DODS 3.. 4 build for Solaris 2.. 6 [.. ftp.. ].. Intel PC Linux.. 4 build for RedHat 7.. 3 (linux kernel 2.. 20-24.. 7smp #1 SMP) [.. 4 build for RedHat 8.. 0 [.. 4 build for RedHat 9.. Dec Alpha OSF.. 4 build for OSF 4.. 0f [.. SGI Mips IRIX.. 4 build for IRIX 6.. 5 (n32/mips3) [.. Win32.. 2 build for Win32 (NT, 2000, XP) [.. info.. ] [..

    Original link path: /faq?q=whatPlatforms
    Open archive





  • Archived pages: 580