| 18 | | * '''rasql''' is a command-line utility for sending queries and saving results in local files. It is part of the rasdaman package. |
| 19 | | * '''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]. Documentation can be found [wiki:raswct/guide here]. |
| 20 | | * '''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: ] |
| 21 | | * '''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] ) |
| 22 | | * '''RRasdaman''' is an R package providing database interface for rasdaman; for further information see [wiki:RRasdaman installation/setup guide] and [wiki:RRasdamanTutorial tutorial] |
| | 18 | === Rasql query language access === |
| 24 | | == WCS clients == |
| | 20 | The following clients allow to submit rasql queries: |
| | 21 | * `rasql` is a command-line utility for sending queries and saving results in local files. Invocation example (see `rasql --help` for details): |
| | 22 | {{{ |
| | 23 | rasql -q "select encode( mr, "png" ) from mr" --out file |
| | 24 | }}} |
| | 25 | * rasql queries can also be invoked via a Web service by default listening at `localhost:8080/rasdaman/rasql`. To this end, the corresponding servlet needs to be started (see [browser:manuals_and_examples/manuals/doc-guides/inst-guide.pdf Installation Guide]). |
| | 26 | * `directql` is not strictly a client, but a rasdaman server linked directly with the rasql utility (see above). Main purpose is for simplified debugging of the server by allowing command-line invocation of the server engine. ([http://rasdaman.org/browser/applications/directql source] ) |
| | 27 | * `rview` is a deprecated visual query interface for desktop use (executable). It is still part of the rasdaman package, but not maintained any longer and will soon be phased out. See [#rview below]. |
| 26 | | * 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] ) |
| 27 | | * mobile clients (contributed by [http://www.consorzio-cometa.it/ COMETA]): |
| 28 | | * native Android app: |
| 29 | | * Google Play: https://play.google.com/store/apps/details?id=it.infn.ct.earthserverSGmobile |
| 30 | | * source: http://sourceforge.net/p/ctsciencegtwys/mobile/14/tree/trunk/Android/EarthServerSGMobile/ |
| 31 | | * To check out the source code: |
| | 29 | === python === |
| | 30 | |
| | 31 | (to be documented) |
| | 32 | |
| | 33 | === Geo clients === |
| | 34 | |
| | 35 | * '''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] ) |
| | 36 | * '''mobile clients''' (contributed by [http://www.consorzio-cometa.it/ COMETA]): |
| | 37 | * native Android app: |
| | 38 | * Google Play: https://play.google.com/store/apps/details?id=it.infn.ct.earthserverSGmobile |
| | 39 | * source: http://sourceforge.net/p/ctsciencegtwys/mobile/14/tree/trunk/Android/EarthServerSGMobile/ |
| | 40 | * To check out the source code: |
| 42 | | |
| 43 | | === rview (deprecated) === |
| 44 | | 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. |
| 45 | | |
| 46 | | 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. |
| 47 | | |
| 48 | | 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. |
| 49 | | |
| 50 | | 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. |
| 51 | | |
| 52 | | 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 |
| 53 | | {{{ |
| 54 | | #!sh |
| 55 | | cd $RMANHOME/bin |
| 56 | | ./rview |
| 57 | | }}} |
| 58 | | |
| 59 | | === rasgeo (deprecated) === |
| 60 | | |
| 61 | | 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]. |
| 62 | | |
| 63 | | To setup rasgeo its configuration file (`~/.rasdaman/rasconnect`) needs to be edited as needed: |
| | 51 | * '''rasgeo''' (deprecated): 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 superseded by the [wiki:WCSTImportGuide wcst_import tool], an implementation of the OGC WCS-T standard which allows to insert, update, and delete geo raster data. |
| | 52 | To setup rasgeo its configuration file `~/.rasdaman/rasconnect` needs to be customized: |
| | 80 | |
| | 81 | === raswct (rasdaman Web Client Toolkit) === |
| | 82 | |
| | 83 | This JavaScript library 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]. See [wiki:raswct/guide documentation] for details. |
| | 84 | |
| | 85 | === rview (deprecated) === |
| | 86 | 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. |
| | 87 | |
| | 88 | 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. |
| | 89 | |
| | 90 | 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. |
| | 91 | |
| | 92 | 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. |
| | 93 | |
| | 94 | 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 |
| | 95 | {{{ |
| | 96 | #!sh |
| | 97 | cd $RMANHOME/bin |
| | 98 | ./rview |
| | 99 | }}} |
| | 100 | |
