Custom Query (2765 matches)

One needs to run this command normally

chmod o+r /opt/rasdaman/etc/log-client.conf

or when he logged in as another user (not rasdaman user), he will have the error:

testVM:~$ rasql -q 'select 1' --user rasadmin --passwd kxeApVopWphBpglI6reM --out string
ASSERTION FAILURE FROM EASYLOGGING++ (LINE: 341) [fileStream_.is_open()] WITH MESSAGE "Unable to open configuration file [/opt/rasdaman/etc/log-client.conf] for parsing."
terminate called after throwing an instance of 'std::out_of_range'
  what():  _Map_base::at
Aborted (core dumped)

WCPS should support a couple of fixed axis aliases:

• x for spatial axis (Lon, Long, E)
• y for spatial axis (Lat, N)
• z for first non-spatiotemporal axis (e.g. height, depth, pressure)
• t for first temporal axis (ansi, unix)

On data import, petascope disallows setting axis names

• x/y for non-spatial axes
• t for non-temporal axes
• z for spatio-temporal axes

These aliases can be used in operations where axis names are referenced:

• subsetting
• scale
• crsTransform
• extend
• flip, sort
• coverage constructor/condenser
• imageCrsDomain, domain

for example, DGM coverage has this style: with WCPS fragment

$c[ansi("2014-01-01T00:00:00.000Z")]

and the WMS request is:

http://localhost:8080/rasdaman/ows?service=WMS&version=1.3.0&request=GetMap&layers=DGM&bbox=49.69649414746458,8.513773134598562,49.78671538251737,8.584016519387294&width=800&height=600&crs=EPSG:4326&format=image/png&transparent=true&styles=gray_time_slice_1

and it has error, because ansi axis is sliced two times (first time from WMS GetMap coverage request, second time from the WMS style)

Coverage's axis not found 'ansi'