Internal error: The index found more cells than allowed

[Alan Beccati <beccati@…>]

The use of rasgeo (rasimport) to load overlapping data into a 3d collection breaks select operation on the collection.

To reproduce install rasdaman, rasgeo and petascope
unpack the attached archive and run script.sh into it to load the images into the created "lol" collection at given raster coordinates

execute the following select to raise the error:

rasql -q "select t from lol as t" —out string
rasql: rasdaman query tool v1.0, rasdaman v8 — generated on 23.11.2011 14:34:26.
opening database RASBASE at localhost:7001...ok
Executing retrieval query…rasdaman error 2016: Internal error: The index found more cells than allowed.
aborting transaction…ok
rasql done.

[Alan Beccati <beccati@…>]

Test dataset to reproduce the error

[Dimitar Misev]

I'm not sure about this, is rasgeo meant for importing 3D data?

[herziga@…]

updated script to demonstrate usage of rasgeo for Alan's use case

[herziga@…]

Replying to dmisev:

I'm not sure about this, is rasgeo meant for importing 3D data?

rasgeo supports creating and importing/updating of 2D x/y slices into/in 3D cubes. When ever rasgeo performs an update operation (i.e. -oid is specified) it automatically imports the named file into its correct 2D geospatial location as provided by its geospatial meta data info. In order to calculate the appropriate shift parameters, rasgeo needs to know about the geospatial location of the image meant to be updated. It achieves that by storing/updating meta data in the nm_meta table within the rasdaman data base after each rasgeo operation. Since in Alan's script the collection/image to be updated is not created by rasgeo, no meaningful meta data is available to calculate the proper shift vector for the file to be imported. In Alan's case that results in this spatial domain [-2147483648:1,-2147483648:1,0:10]. I'm not familiar with rasdaman internals, but obviously this causes the rasql select query to fail.

Using exclusively rasgeo to create and update the collection (see script in updated attachment) results in this spatial domain [-443:116,0:3740,10:10], and the rasql select query is executed successfully.

I'll update the README to emphasise that rasgeo depends on the geospatial meta data in nm_meta.

Alex

[Dimitar Misev]

Thanks Alex! I'll close the ticket as fixed then.