Opened 6 years ago

Closed 3 months ago

#5200 closed defect (wontfix)

georaster - not reading the VAT as RAT

Reported by: ilucena Owned by: ilucena
Priority: normal Milestone: closed_because_of_github_migration
Component: GDAL_Raster Version: unspecified
Severity: normal Keywords: georaster
Cc:

Description

After loading an RAT into GeoRaster VAT, the table is created, the data is loaded and the GeoRaster metadata as updated correctly but gdalinfo is not reporting the VAT as a GDAL RAT.

Change History (5)

comment:1 Changed 6 years ago by ilucena

That problem was addressed on r26360

The reason the gdalinfo was not showing the VAT as RAT was because of a bug on the GeoRaster driver related to GetStatistics?. In that same revision another problem was fixed on SetDefaultRAT. Floating value data type could no be loaded properly. A new create-option was added for users to specify the name of the VAT table instead of using the automatic generate name. -co VATNAME

But we still have problem loading files with RAT to GeoRaster because of problem on the VRT driver so we can't say that this bug is fixed. On gdal_translate, if a file with RAT is the input and the user specify an option that requires gdal_translate to create an in-memory VRT, like -a_nodata, the VRT function GetDefaultRAT will return NULL and the data is not going to be loaded to GeoRaster.

comment:2 Changed 6 years ago by Even Rouault

The 1.10.1 milestone is incorrect. This went to trunk rather than 1.10 branch

comment:3 Changed 5 years ago by Even Rouault

Milestone: 1.10.11.11.0

comment:4 Changed 4 years ago by Even Rouault

Milestone: 1.11.0

comment:5 Changed 3 months ago by Even Rouault

Milestone: closed_because_of_github_migration
Resolution: wontfix
Status: newclosed

This ticket has been automatically closed because Trac is no longer used for GDAL bug tracking, since the project has migrated to GitHub?. If you believe this ticket is still valid, you may file it to https://github.com/OSGeo/gdal/issues if it is not already reported there.

Note: See TracTickets for help on using tickets.