Custom Query (2765 matches)

bug derived by a discussion on rasdaman-users mailing list at ​http://groups.google.com/group/rasdaman-users/browse_thread/thread/54d698e038a98fb9?hl=en

I'm working with the latest rasdaman version available by git.

When I select data from a collection and I try to encode results into a specific file format, the files selected are always saved with the ".unknown" extension instead of the correct file type suffix.

It seems a little problem related only to the file name because the data are encoded correctly.

X Peter and Dimitar, if you want to verify this issue you can use the System provided in Munich by EOX. Also the rasdaman installed on the Key is affected by this problem. I can not verify if the virtual machines provided for the Earth Server project by EOX are OK. Currently i'm working with an own installation of Rasdaman and I don't use the packages prepared by EOX.

Examples:

rasql -q "select tiff(i) from rgb as i" —out file rasql: rasdaman query tool v1.0, rasdaman v8 — generated on 14.10.2011 17:27:00. opening database RASBASE at localhost:7001...ok Executing retrieval query…ok Query result collection has 1 element(s):

Result object 1: going into file rasql_1.unknown…ok.

rasql done.

rasql -q "select png(i) from mr as i" —out file rasql: rasdaman query tool v1.0, rasdaman v8 — generated on 14.10.2011 17:27:00. opening database RASBASE at localhost:7001...ok Executing retrieval query…ok Query result collection has 3 element(s):

Result object 1: going into file rasql_1.unknown…ok. Result object 2: going into file rasql_2.unknown…ok. Result object 3: going into file rasql_3.unknown…ok.

rasql done.

rasql -q "select jpeg(i) from aatsr as i" —out file rasql: rasdaman query tool v1.0, rasdaman v8 — generated on 14.10.2011 17:27:00. opening database RASBASE at localhost:7001...ok Executing retrieval query…ok Query result collection has 8 element(s):

Result object 1: going into file rasql_1.unknown…ok. Result object 2: going into file rasql_2.unknown…ok. Result object 3: going into file rasql_3.unknown…ok. Result object 4: going into file rasql_4.unknown…ok. Result object 5: going into file rasql_5.unknown…ok. Result object 6: going into file rasql_6.unknown…ok. Result object 7: going into file rasql_7.unknown…ok. Result object 8: going into file rasql_8.unknown…ok.

rasql done.

Damiano

The netcdf converter should be documented in the query language guide.

netcdf can be invoked without any parameters in which case the data is saved under a variable with name "data" for primitive types and using the attribute names as variables for struct types, or with "vars=VAR1;VAR2;…;VARN" which specifies the names of the struct attributes which hold the exported data. Example:

select netcdf(c[10:20,*:*], "vars=Global_radiation") from Global_radiation as c

inv_netcdf can be invoked without any parameters, or with "vars=VAR1;VAR2;…;VARN" which imports only the specified VARi from the file, e.g:

insert into Coll values inv_netcdf($1, "vars=Global_radiation:Snow")

as ticket #89 shows (​http://kahlua.eecs.jacobs-university.de/trac/rasdaman/attachment/ticket/89/tifftest.sh), one can encode 3D coverages into 2D formats. While in the case on hand this is not critical (3rd dimension has thickness 1, thus allowing to map) in general this should be caught for TIFF and others