[[TracNav(TOC)]] [[PageOutline]] = Clients = rasdaman can interface with a large and increasing number of tools. Some clients allow direct query submission, such as rasql and directql. For rapid development of browser clients the raswct toolkit is provided. Geo tools supported include !OpenLayers, QGIS, ncWMS, THREDDS, GDAL, !MapServer, !ArcGIS; soon: !GeoServer. Geo standards supported are OGC WMS, WCS, WCPS, and WPS; hence, all clients conforming to these standards can additionally be used for interfacing. All geo semantics is implemented through the petascope component ([http://rasdaman.org/browser/applications/petascope source]) which is implemented as a Java application layer offering OGC Web services. == rasdaman clients == * '''rasql''' is a command-line utility for sending queries and saving results in local files. It is part of the rasdaman package. * '''raswct''' is the rasdaman Web Client Toolkit which allows, by way of input and output widgets, to easily compose a Web client. Simple versions need only HTML, but advanced interfaces can be created. One example for the use of raswct is [http://standards.rasdaman.org standards.rasdaman.org]. * '''rview''' is a deprecated visual query interface for desktop use (executable). It is still part of the rasdaman package, but not maintained any longer. [executable: ] * '''directql''' is not strictly a client, but a rasdaman server linked directly with the rasql utility (see above). This simplifies debugging for developers. ([http://rasdaman.org/browser/applications/directql source] ) * '''RRasdaman''' is an R package providing database interface for rasdaman; for further information see [wiki:RRasdaman installation/setup guide] and [wiki:RRasdamanTutorial tutorial] == WCS clients == * WCS Web client: a generic Web client which allows for convenient forms-based input of WCS parameters for WCS Core and Extensions; all WCS extensions are supported, but the client presents only those extensions which are supported by the server addressed. Results can be displayed graphically where feasible. ([http://rasdaman.org/browser/applications/wcs-client source] ) * mobile clients (contributed by [http://www.consorzio-cometa.it/ COMETA]): * native Android app: * Google Play: https://play.google.com/store/apps/details?id=it.infn.ct.earthserverSGmobile * source: http://sourceforge.net/p/ctsciencegtwys/mobile/14/tree/trunk/Android/EarthServerSGMobile/ * To check out the source code: {{{ svn checkout svn://svn.code.sf.net/p/ctsciencegtwys/mobile/trunk/Android/EarthServerSGMobile EarthServerSGMobile }}} * Appcelerator Titanium app built for iOS: * App Store: https://itunes.apple.com/us/app/earthserver-sg-mobile/id740603213?ls=1&mt=8 * source: http://sourceforge.net/p/ctsciencegtwys/mobile/15/tree/trunk/iOS/EarthServer-SG-Mobile/ * To check out src code: {{{ svn checkout svn://svn.code.sf.net/p/ctsciencegtwys/mobile/trunk/iOS/EarthServer-SG-Mobile EarthServer-SG-Mobile }}} == QGIS == This plugin enables the direct download, processing, integration and usage of Coverages from an OGC compliant WCPS 1.0 enabled servers within the QGIS software (v2.0+ supported). The plugin has been submitted to the official QGIS plugin repository, approval is pending; in the meantime it can be installed manually: - get the rasdaman source tree: {{{ git clone git://rasdaman.org/rasdaman.git }}} - the plugin can be found in directory `rasdaman/applications/qgis-wcps` - copy the `qgis-wcps/QgsWcpsClient1` directory to your `qgis-python-plugin directory`, usually located in `$HOME/.qgis2/python/plugins`: {{{ $ mkdir -p $HOME/.qgis2/python/plugins/ $ cp -r rasdaman/applications/qgis-wcps/QgsWcpsClient1 $HOME/.qgis2/python/plugins/ }}} - now you can start QGIS and access the `QgsWcpsClient1` plug-in via the `Qgis Menu → Plugins → WcpsClient1 → WCPS 1.0 Client` == !OpenLayers == documentation tbd == ncWMS == documentation tbd == THREDDS == documentation tbd == GDAL == To compile GDAL with rasdaman support: 1. Get latest GDAL source 2. Compile and install (in the /home/rasdaman/gdal) {{{ #!sh ./configure --prefix=/home/rasdaman/gdal --mandir=/home/rasdaman/gdal/share/man --includedir=/home/rasdaman/gdal/include/gdal --with-threads --with-grass=no --with-hide-internal-symbols=yes --with-libtiff=internal --with-geotiff=internal --with-jasper --with-netcdf --with-xerces --with-geos --with-sqlite3 --with-curl --with-pg --with-ogdi --with-python --with-odbc --with-static-proj4=yes --with-spatialite=/usr --with-cfitsio=no --with-epsilon=/usr --with-rasdaman=/home/rasdaman/install make make install }}} * '''Note:''' rasdaman should be compiled with `-fPIC`, so make sure to specify `--with-pic` when running `./configure` on rasdaman. 3. Setup environment {{{ #!sh export GDAL_HOME=/home/rasdaman/gdal export PATH=$PATH:$GDAL_HOME/bin export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$GDAL_HOME/lib }}} == ArcGIS == documentation tbd == !GeoServer == documentation tbd == rview (deprecated) == rview is a deprecated desktop visualization client of rasdaman. It is deprecated as it uses an insecure, soon-to-be-replaced client/server protocol based on RPCs. For building clients use [http://rasdaman.org/wiki/Clients one of the Web client or the raswct library] instead. Caveat: This client is fixed to RPC as client/server protocol, hence (i) rpcbind/portmapper must be installed and running and (ii) at least one rasdaman server process using RPC must be up and running; see the rasdaman Installation Guide for details on this. Background: rview is deprecated and unmaintained. Reason is that the wxWindows library has changed so substantially that, despite severe ettempts, it was not possible to adapt the rview code; therefore, only the old binary remains available. In fact, there are strong reasons not to use rview: As highlighted, RPC is '''highly insecure''' and not recommended. Further, RPC communication is deprecated and will soon be replaced (together with HTTP and RNP) by rasnet. If you have read the above and still wish to use rview, proceed as follows: start the rpcbind service has to be started in insecure mode (or rasdaman has to be started as root, which is strongly discouraged as well) in order for rview to be able to connect to rasdaman. To start rpcbind in insecure mode, edit /etc/init.d/rpcbind (more recently: /etc/init/portmap.conf) and add '-i' to the OPTIONS variable. Start rpcbind. Restart rasdaman. Open rview with {{{ #!sh cd $RMANHOME/bin ./rview }}} == rasgeo (deprecated) == rasgeo is a client component of petascope that is able to easily import data into rasdaman along with the geo-metadata into petascope, provided that the data can be read by GDAL. This has been now superceded by the [wiki:WCSTImportGuide wcst_import tool]. To setup rasgeo its configuration file (`~/.rasdaman/rasconnect`) needs to be edited as needed: {{{ #!sh # Example file: ------------------------------------------------- host=localhost rasport=7001 pgport=5432 rasdbname=RASBASE petadbname=petascopedb # RASBASE login rasuser=rasdaman raspassword=rasdaman # petascopedb login petauser=petauser petapassword=petapasswd # for rasdaman 9.0 # rasdaman login rasloginuser=rasadmin rasloginpassword=rasadmin ------------------------------------------------ }}}