Opened 11 years ago
Closed 10 years ago
#767 closed defect (invalid)
band names shown in dbinfo() differ from designated during rasimport
Reported by: | gxinghua | Owned by: | gxinghua |
---|---|---|---|
Priority: | major | Milestone: | 9.0.x |
Component: | rasgeo | Version: | development |
Keywords: | rasimport, marray type, band name | Cc: | Piero Campalani |
Complexity: | Medium |
Description (last modified by )
ingest a 3_band image using "rasimport -f SampleDataset/2D_multiband/N-32-50_ul_2000.tif —coll Multiband -t MultibandImage:MultibandSet —crs-uri '%SECORE_URL%/crs/EPSG/0/32632' —crs-order 0:1 —coverage-name Multiband".
The MultibandImage is defined as:
> rasdl -p | grep MultibandImage typedef marray <struct { char band1, char band2, char band3 }, 2> MultibandImage; typedef set <MultibandImage> MultibandSet;
But after ingesttion, "rasql -q 'select dbinfo(e) from Multiband as e' —out string" gives the type info:
> rasql -q 'select dbinfo(test3band) from test3band' --out string | grep baseType "baseType": "marray <struct { char red, char green, char blue }>",
Seemingly it happens only when import 3 char band image. As test with a 4 char band image, the problem do not happen.
Change History (4)
comment:1 by , 10 years ago
Cc: | added |
---|---|
Priority: | minor → major |
comment:2 by , 10 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:3 by , 10 years ago
Description: | modified (diff) |
---|
comment:4 by , 10 years ago
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
It seems to have happened due to some local issue.