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: Report on the First Workshop for DODS, 29 Sept. to 1 Oct. 1993 | OPeNDAP
    Descriptive info: › Report on the First Workshop for DODS, 29 Sept.. to 1 Oct.. 1993.. Report on the First Workshop for DODS, 29 Sept.. Fri, 10/01/1993 - 01:00 —.. nehal bathani.. Available as a.. PostScript.. file.. to post comments..

    Original link path: /node/224
    Open archive

  • Title: What is OPeNDAP software? | 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.. › What is OPeNDAP software?.. What is OPeNDAP software?.. OPeNDAP has developed a software framework.. that simplifies all aspects of scientific data networking, allowing simple access to remote data.. Local data can be made accessible to remote locations regardless of local storage format by using.. servers.. Existing, familiar data analysis and visualization applications can be transformed into.. clients.. (i.. , applications able to access remote served data).. Take a look at our answer to the question.. "What Will OPeNDAP Do For Me?".. The OPeNDAP Data Access Protocol (DAP) is a protocol.. for requesting and transporting data across the web.. DAP 2.. 0 uses HTTP to frame the requests and responses.. For details on DAP, see.. Data Access Protocol (DAP), version 2.. which is a technical description of the Data Access Protocol.. This was submitted to NASA's Earth Science Data Systems Standards Process Group and has been accepted as a Recommended Standard (submitted on 8/8/2004, accepted 10/8/2007).. The official.. NASA ESE/RFC distribution point for DAP2.. may provide a more up to date version and also has additional documentation regarding NASA/ESE's adoption of DAP2 as a community standard.. OPeNDAP supports.. a community  ...   projects for developing end-to-end systems which can locate, understand, access, and use scientific data.. OPeNDAP has already developed:.. a flexible data model.. a transport protocol.. software frameworks.. C++ and Java implementations of the data model and transport protocol.. a set of DODS servers.. a set of DODS clients.. Not Just Oceanography.. Although the OPeNDAP software was originally designed and developed by oceanographers and computer scientists for oceanographic data (as part of the DODS and NVODS projects), there is nothing in the design of the OPeNDAP software that constrains its use to oceanography.. Indeed, it has been adopted by the High Altitude Observatory community and is being considered by segments of the meteorological and space science communities.. User Application -- DAP Client.. Once a user's data analysis application (or API) is made network-savvy with the OPeNDAP tools, the scope of an application's search for data is extended because remote data becomes as accessible as local data.. A DAP-enabled application can:.. Get any data anywhere on the Internet that is served by a DAP server.. Use data from any DAP server, pretty much regardless of its native format.. Still perform all its original functions for accessing data locally.. The truly remarkable part:.. you don't have to rewrite the code.. to enable many applications to work as a DAP clients..

    Original link path: /support?q=What_is_OPeNDAP_software
    Open archive

  • Title: Available DAP Servers | OPeNDAP
    Descriptive info: › Available Servers.. Available DAP Servers.. Currently available DAP servers:.. OPeNDAP Hyrax.. Hyrax can serve data stored in netCDF3, netCDF4, HDF4, HDF5, FITS, CSV, and ASCII or Binary column-formatted data.. Also available for Hyrax are a number of other handlers which are provided as source-code only.. Hyrax is based on the reference implementation of DAP2 and supports a wide variety of insallation and customization options.. OPeNDAP Test Server.. The test server serves pseudo-data.. Very useful when you want to test client software on a data structure for which you don t have an example.. ERDDAP.. ERDDAP (the NOAA Environmental Research Division s Data Access Program) makes data from multiple data sources available via OPeNDAP and in common file formats.. THREDDS Data Server.. Use this to aggregate multiple data sources.. This server works with local netCDF file as well as data accessible from a DAP-compliant server.. It can also serve some HDF4 and HDF5 files.. PyDAP.. A DAP server written in Python.. COLA GrADS Data Server (GDS).. The GDS makes data available using GrADS.. The types of data that can be served include GRIB, netCDF, HDF, and GrADS binary.. NOAA/PMEL/EPIC Dapper Server.. makes in-situ data in various netCDF formats available.. OPeNDAP server development toolkits:.. OPeNDAP C++ Server Development Framework.. The OPeNDAP C++ implementation contains a DAP API/library and CGI dispatch framework for developing OPeNDAP servers.. OPeNDAP Java Server Development Framework.. The OPeNDAP Java implementation contains a DAP API and servlet framework for developing OPeNDAP servers.. COLA Anagram (from GDS).. Anagram, a Java servlet framework for  ...   from this web site.. Send questions to.. support@opendap.. org.. Anagram.. is a modular Java framework for high-performance scientific data servers, which forms the basis for the GDS version 1.. 2.. The THREDDS Data Server is a Java servlet that can serve data in netcdf as well as some kinds of HDF4, HDF5 and BUFR files.. It uses NCML and can be used to serve aggregations of files.. It also can work as a WMS/WCS server.. For more information see the.. page.. is a server written entirely in Python.. It can serve a variety of file formats and also supports WMS and KML responses.. (the NOAA Environmental Research Division s Data Access Program) is an OPeNDAP server that lets you download subsets of scientific datasets via DAP (or in common file formats) and make graphs and maps.. It supports gridded data (via DAP hyperslab queries) and tabular data (via DAP constraint expression queries).. To download go to the.. ERDDAP installation.. Dapper Server.. Dapper makes in-situ data available via the DAP using.. EPIC tools.. See the.. dapper website.. for more information or to obtain dapper.. GrADS Data Server (GDS).. The GDS makes data available using.. GrADS.. GDS web page.. DODS/OPeNDAP Test Server (DTS).. The test server serves pseudo-data (i.. , made up by the server but consistent) for any DDS/DAS.. To Download.. : Go to the.. OPeNDAP Java.. web page and read the README and SERVLETS files.. The.. OPeNDAP C++ implementation.. contains a DAP API/library and CGI dispatch framework for developing OPeNDAP servers.. Java DAP web page..

    Original link path: /support?q=whatServers
    Open archive

  • Title: Available OPeNDAP Client Software | OPeNDAP
    Descriptive info: ›.. › Available Clients.. Available OPeNDAP Client Software.. OPeNDAP Clients:.. NCL.. a scientific data analysis and visualization software package freely available from NCAR.. CDAT (Climate Data Analysis Tools).. a software infrastructure that forms an integrated environment for solving model diagnosis problems.. OPeNDAP geturl.. a simple command-line client for testing datasets.. Matlab 2012a.. includes built-in support for access to OPeNDAP servers, using the netCDF interface.. Matlab Command-line client.. a Matlab tool which provides access to data using Matlab.. Matlab (a commercial data analysis and visualization package) is required.. OPeNDAP Matlab Toolkit (GUI).. a GUI for accessing oceanographic data from DAP-compliant servers in Matlab.. Ferret.. a data analysis and visualization package available from NOAA/PMEL.. a data analysis and visualization package available from COLA.. IDV (Integrated Data Viewer).. a Java application for visualizing and analyzing geoscience data.. LAS (Live Access Server).. a highly configurable Web server designed to provide flexible access to geo-referenced scientific data.. ncBrowse.. a Java application that provides flexible, interactive graphical displays of data and attributes from a wide range of netCDF data file conventions.. ncdump.. a tool for displaying netCDF files as netCDF CDL.. NCO (netCDF Operators).. NCO is a set of command line tools that perform operations (e.. g.. , average or concatenate) on netCDF or HDF files.. ncview.. a visual browser for gridded data.. OPeNDAP Data Connector.. The ODC is a graphical application which allows you to search for OPeNDAP datasets, download them to your machine, save them, and import them into client applications like IDL, Matlab, SPSS, Excel, or into databases such as Access and Oracle.. It also has viewing and plotting capabilities.. Compatible with Unix/Linux, Windows, and Mac.. DChart.. DChart is a web interface for OPeNDAP/dapper in-situ data collections that uses AJAX technologies (like Google Maps) for interactive data selection and data graphics.. See the DChart installation website with realtime global Argo data, TAO data and more.. Client Libraries:.. OPeNDAP DAP library.. the OPeNDAP C++ implementation DAP library (libdap++.. a) can be used to develop OPeNDAP clients.. OPeNDAP Java API.. the OPeNDAP Java implementation DAP API can be used to develop OPeNDAP clients.. The NetCDF Client Library.. a DAP-enabled version of the standard netCDF library.. netCDF Java library.. the Java implementation of netCDF.. pydods.. a simple Python library for interfacing with a OPeNDAP server.. Other applications that can access DAP-compliant servers:.. Generic Web Browser.. any generic web browser like Internet Explorer, Mozzilla, or Netscape can access OPeNDAP data in a restricted manner.. Since the browsers do not understand the OPeNDAP protocol, the user will need some understanding of the protocol.. Spreadsheet Applications.. (e.. , Excel, StarOffice).. any application that can dereference a URL can access a OPeNDAP URL.. Since the applications don t understand the protocol, the user will need some understanding of the protocol.. NCL - Scientific data analysis and visualization software.. NCL is a scientific data analysis and visualization software package freely available from.. NCAR.. (http://www.. ncar.. ucar.. edu).. For more information and to download, go to the.. NCL Home Page.. ncl.. DChart - A web interface to OPeNDAP in-situ data.. The Dapper Data Viewer (aka DChart) allows you to visualize and download in-situ oceanographic or atmospheric data from a Dapper OpenDap server.. Features include an interactive map that is draggable, an in-situ station layer that allows you to select data stations, and a plot window that allows you to plot data from one or more stations.. Three plot types are supported (profile, property-property, and time series) and users can interact directly with the plot to pan or zoom in  ...   data directly into Matlab variables.. Matlab.. is a commercial data analysis and visualization package.. Matlab client page.. NetCDF client library.. The OPeNDAP netCDF client library is a DAP-enabled version of the netCDF API library.. netCDF.. is an interface for array-oriented data access and a library that provides an implementation of the interface developed and maintained by.. UCAR/Unidata.. NetCDF Client Library page.. is a data analysis and visualization package available from.. NOAA/PMEL.. that can access data.. Ferret home page.. is a data analysis and visualization package for earth system data.. It is available from.. COLA.. web page.. Because OPeNDAP servers are accessed through URLs, any application that can dereference a URL can access those servers.. Thus, any generic web browser (e.. , Internet Explorer, Mozzilla, or Netscape) can access those data in a restricted manner.. Since generic web browsers do not understand the OPeNDAP protocol, the user will need some understanding of the protocol.. A brief explaination of how to access OPeNDAP data in a web browser is available at our FAQ.. Using a Web Browser with OPeNDAP servers.. IDV.. is a Java application for visualizing and analyzing geoscience data.. The IDV was developed at UCAR/Unidata and uses the.. VisAD.. library for data and display models as well as other Java utility packages.. IDV home page.. LAS.. is a highly configurable Web server designed to provide flexible access to geo-referenced scientific data.. LAS, by default, uses Ferret (.. see above.. ) to produce plots of datasets which means the LAS can be configured to display data from OPeNDAP servers.. LAS home page.. is a Java application that provides flexible, interactive graphical displays of data and attributes from a wide range of netCDF data file conventions.. Version 1.. 3.. 3Beta5 and later can access OPeNDAP servers.. ncBrowse home page.. ncdump is a utility for displaying netCDF files in the netCDF CDL (Common Data Language).. It comes with the netCDF distribution from Unidata.. We distribute a version with support for OPeNDAP servers built in.. NetCDF Clients page.. NCO.. is a set of command line tools that perform operations, e.. , average or concatenate, on netCDF or HDF files.. NCO home page.. ncview is a visual browser for gridded data that is available from the.. ncview home page.. We provide a version that can access data from OPeNDAP servers as well as local netCDF files.. NetCDF clients page.. Java implementation of netCDF.. comes with support for OPeNDAP servers enabled.. Therefore, any application that uses this library can access data via the servers.. netCDF Java home page.. OPeNDAP Data Connector (ODC).. ODC.. is a graphical application which allows you to search for OPeNDAP datasets, download them to your machine, save them, and import them into client applications like IDL, Matlab, SPSS, Excel, or into databases such as Access and Oracle.. OPeNDAP Data Connector home page.. pydods is a simple Python library for interfacing with OPeNDAP servers.. pydods was developed by Roberto A.. F.. De Almeida (Universidade de São Paulo).. and for more information, go to the.. pydods home page.. Because OPeNDAP servers are accessed through URLs, any application that can dereference a URL can access those data.. Since most spreadsheet applications (e.. , MS Excel and StarOffice) can open URLs, they can access those data in a restricted manner.. However, since spreadsheet applications do not understand the OPeNDAP protocol, the user will need some understanding of the protocol.. A brief explaination of how to access OPeNDAP data from a spreadsheet is available at our FAQ.. Using a Spreadsheet Application with OPeNDAP servers..

    Original link path: /support?q=whatClients
    Open archive

  • Title: How do I find the version of the server I'm talking to? | OPeNDAP
    Descriptive info: Server Issues.. How do I find the version of the server I m talking to?.. Wed, 05/11/2011 - 17:15 —.. 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..

    Original link path: /support?q=serverVersion
    Open archive

  • Title: How to Build DODS | OPeNDAP
    Descriptive info: › 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.. 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.. Notes:.. 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.. 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 to the file listed.. Name log files as desired.. The names shown here are my  ...   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: /support?q=buildProcedureDODS
    Open archive

  • Title: How do I build the netCDF Fortran jackets? | OPeNDAP
    Descriptive info: Build and Install.. 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 g77), generally  ...   FFLAGS, CXX, and CXXFLAGS (and perhaps LIBS) to represent [your] environment.. " The documentation (i.. , the.. INSTALL.. 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.. let us know.. so we can list it here.. GNU Fortran.. CC=gcc.. CXX=g++.. FC=gfortran.. FFLAGS=-g.. CPPFLAGS=-Df2cFortran.. 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: /support?q=buildnetCDFfortranJackets
    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.. g++ -g -o sample sample.. 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  ...   Fortran compiler, you will need 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.. 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:.. 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: /support?q=link_Fortran_program_to_netCDF
    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: /support?q=whatPlatforms
    Open archive

  • Title: Microsoft Windows Support | OPeNDAP
    Descriptive info: › Microsoft Windows Support.. Microsoft Windows Support.. Note:.. Windows versions of the OPeNDAP software is available here and on the main.. download.. This page provides some background information on the port, especially on the different types of libraries supported.. You can get the same software, or in some cases.. newer software.. , from the main download page by following the.. Windows links there.. 4 Native Win32 port.. 4 is available for Windows 2000 and Windows XP.. This distribution contains the DODS core (DAP) library, the netCDF client library, the Matlab command-line client, the IDL command-line client and the FreeForm Server.. A Dods Development environment for Win32 is also included.. This development environment includes the Dods Core Library (libdap) as well as other select libraries upon which the core library depends (libcurl, libz, libxml2 and libxdr) and all supporting headers.. Each of these libraries are provided in 6 different models - Static Singly-Threaded, Static Multi-Threaded, Dynamic Multi-Threaded plus debug versions of each of these three libraries.. These six models of libraries are provided for libdap, libcurl, libz, libxml2, libxdr and the Freeform library.. Four models of the NetCDF library are provided (no DLL models).. The below table outlines the 6 library models:.. Library Model.. Microsoft Compiler Option Used to Build.. Format of Library Name.. Format of Name of the Associated DLL.. Static Singly-Threaded.. /ML.. lib*ST.. lib.. N/A.. Static Multi-Threaded.. /MT.. lib*MT.. Dynamic Multi-Threaded.. /MD.. lib*MD.. dll.. Static Singly-Threaded Debug.. /MLd.. lib*STD.. Static Multi-Threaded Debug.. /MTd.. lib*MTD.. Dynamic Multi-Threaded Debug.. /MDd.. lib*MDD.. To install Dods for Windows, download the.. distribution.. to your desktop and double click on it.. Then Follow the on-screen instructions.. If you have a previous version of Dods installed,.. you must first uninstall.. it via "Add/Remove Programs" component within the Control Panel.. 4 for win32 was built with Microsoft Visual C++ 7.. If you use the development environment provided to construct or relink a Dods client, you must also use MS VC++ 7.. 4 Native Win32 port(beta).. 4 is available for Windows NT, Windows 2000 and Windows XP.. Other versions of Windows are not supported.. It contains the DODS core library (DAP), the netCDF client library, the Matlab command-line client, the IDL command-line client, the Matlab Toolbox (a GUI) and our  ...   is now available as a Windows port (6 February 2002).. It contains: the Matlab client; the IDL client; our test client, geturl; the DODS core (DAP) library; and the netCDF client library.. Note: We support this port for NT-based kernals only (NT, W2K and XP).. We do not support this port on win9x-based systems though it may work fine.. To install this port: first, uninstall any existing version of DODS; download the.. installShield self-extracting archive.. ; double click; and follow the on-screen instructions.. To run DODS exe's and dll's, you will need to set various environment variables, e.. , path, IDL_PATH, and MATLABPATH, depending on which tools you are going to run.. Other environment variables must be set to use the DODS libraries.. 1 native Win32 port.. DODS has a port for MS Windows platforms (95, 98, 2000, and NT).. It is a native Windows port (using the Visual C++ compiler) and is available as a beta release.. Download our.. self-extracting archive.. This port is of three DODS clients: the Matlab client, the IDL client, and geturl.. (The Matlab GUI is not included, you will need to get that directly from the.. FTP site.. Tip:.. From a DODS support email, a discussion of setting your PATH so Matlab can find the DODS client (probably applies to IDL as well):.. I believe it is just a matter of having the directory of the.. dll's on your PATH.. To pick up the matlab dll for instance I have C:\Program Files\URI\DODS\bin in my path.. Your location of this dll will vary somewhat depending upon where to choose to install Dods at installation time.. How you set the path varies by the win32 host you are on.. 95/98 - edit autoexec.. bat.. In Win2000, double click on "System" in the control panel and select the Environment Variables push button.. In NT, it is probably set the same or similar to the way it is in Win2000.. Here's the URL for that email,.. http://www.. unidata.. edu/glimpse/dods/287.. An older port using Cygwin to emulate the Unix environment contained a number of DODS servers.. The Cygwin port is no longer supported but is available if desired.. If you are interested in the Cygwin port, please email us at.. support@unidata.. edu..

    Original link path: /support?q=winPort
    Open archive

  • Title: SGI Issues | OPeNDAP
    Descriptive info: › SGI Issues.. SGI Issues.. There are a number of issues that have caused problems with builds (and running the resulting binaries) on SGI machines.. The main issue with respect to DODS is how the different architectures affect use of the DODS libraries and the Matlab and IDL clients.. Here is a.. description of our standard SGI binary distribution.. Issues:.. Other Issues:.. Third-party Packages:.. Architectures.. OS Versions.. Hardware.. Compiler Versions.. IDL.. Standard SGI Distribution.. Our standard SGI binary distribution is built on an SGI Irix 6.. 5 machine for the n32/mips-3 architecture.. The Matlab client will come with two loaddods.. mexsgi files: loaddods.. mexsgi is the binary for the n32 architecture, loaddods.. mexsgi64 is a binary for the 64 architecture.. Details for the IDL distribution are still being decided.. If you are using DODS version 3.. 0 (we recommend using 3.. 1), see the.. 0 note below.. We are still developing our strategies for dealing with these issues.. If you have comments, please let us know by emailing.. Architecture.. There are a variety of SGI architectures.. Each one is some combination of the four possible instruction sets and the three binary formats (ABI).. Instruction Sets.. '-mips1';.. '-mips2';.. '-mips3'; and.. '-mips4';.. Application Binary Interface (ABI), i.. , the format/interface of the binary files.. '-o32' - for the "old" 32-bit ABI (which was standard on IRIX 5) and is either mips-1 or mips-2;.. '-64' - the 64-bit ABI (which was introduced on IRIX 6.. 0) and is either mips-3 or mips-4; and.. '-n32' - the new, high-performance 32-bit ABI (which was introduced on IRIX 6.. 2) and is either mips-3 or mips-4.. Though these architecures are backward compatible (i.. , a 64 bit machine can run binaries built in any architectures), every part (all objects and libraries) for a given executable must be in the same architecture.. In other words, you cannot link together objects that are built for different architectures.. This means caution must be taken when linking applications with the DODS libraries we build (i.. , the DODS core (DAP) library, libdap++.. a; the netCDF API library, libnc-dods.. a; and the JGOFS API library, libjg-dods.. a) and with the architectures of the commercial applications we build clients for (i.. , Matlab and IDL).. See the information below on the architectures of.. and.. Also, see the.. note on shared objects.. The basic problem here is that several Irix OS versions work exclusively on certain hardware platforms.. Here's a (not terribly detailed) summary:.. Irix  ...   five different architectures.. Please send us (.. ) the output so we can add to this list.. We have been recommending use of gcc 2.. 8 for some time now due to some (former) dependence on the Gnu library.. However, we have had some difficulties on SGIs due to the version of the libstdc++.. a library that was distributed with gcc 2.. Using gcc 2.. 8 with a newer version of libstdc++.. a holds promise but we have not thoroughly tested it.. The egcs compiler works.. And, now that egcs and gcc have merged back together, gcc 2.. 95 also works.. Note: The dependence on the Gnu library has been removed.. We are working to make the build process more generic so DODS can be built on development environments other than GNU.. The required architecture of the DODS Matlab client (which is used by the DODS Matlab GUI) depends on a selection during installation of Matlab.. The two available installations (and the architecture of the respective shared libraries, with which the DODS Matlab client needs to link) are:.. SGI - has o32/mips2 shared objects.. SGI64 - has 64/mips4 shared objects.. You can determine the architecture of your Matlab installation by running 'ver' at the Matlab prompt.. The first line containing Matlab version info will state either 'SGI' or 'SGI64', e.. MATLAB Version 5.. 10183 (R11) on SGI64.. The required architecture of the DODS IDL client depends on the version of IDL you are running.. The architecture of the IDL shared libraries, with which the DODS IDL client needs to link, is as follows:.. o32 (mips 1) shared objects for IRIX IDL 5.. 2 and.. n32 (mips 3) shared objects for IRIX IDL 5.. 1 and above.. Notes.. Shared Objects Note.. : Remember when dealing with shared objects, since the objects are linked at runtime, any error including architecture mismatch will be a runtime error.. 0 Note.. : For DODS version 3.. 0, we skirted the issue by providing an Irix 5.. 3 build.. It has been tested in a very limited way on Irix 6.. 5 machines.. However, we've heard of incompatibilities between Irix 5.. x and 6.. x at least in terms of linking to the 5.. x libraries on 6.. x machines.. Which means that if you plan to link your applications against any of the DODS libraries, this solution may not (probably won't?) work for you.. As far as the servers go, they seem to work fine on 6..

    Original link path: /support?q=sgiProbs
    Open archive





  • Archived pages: 580