Le samedi 18 janvier 2014 16:52:51, Ivan Lucena a écrit : > > From: even.roua...@mines-paris.org > > To: lucena_i...@hotmail.com > > Subject: Re: [gdal-dev] Fwd: Color Columns in Raster Attribute Tables > > Date: Sat, 18 Jan 2014 16:23:10 +0100 > > CC: gillingham....@gmail.com; gdal-dev@lists.osgeo.org > > > > Le samedi 18 janvier 2014 15:40:15, Ivan Lucena a écrit : > > > > From: even.roua...@mines-paris.org > > > > To: lucena_i...@hotmail.com > > > > Subject: Re: [gdal-dev] Fwd: Color Columns in Raster Attribute > > > > Tables Date: Sat, 18 Jan 2014 15:22:43 +0100 > > > > CC: gillingham....@gmail.com; gdal-dev@lists.osgeo.org > > > > > > > > Le samedi 18 janvier 2014 15:18:20, Ivan Lucena a écrit : > > > > > Hi Even, > > > > > > > > > > In a parallel and almost not related topic, I am getting users > > > > > complains that gdal_translate crashes > > > > > > > > Well, that should be debugged and fixed... You don't have more > > > > details ? > > > > > > I waiting to get a sample file to debug it, but even when it doesn't > > > crash they need to manage what to do with the useless VAT table on the > > > database. > > > > > > > > or waste their time and storage space with > > > > > some ridiculous RAT that doesn't make any sense for their use case. > > > > > Maybe we should have a -noRAT option on gdal_translate. I could > > > > > also add an "RAT2VAT=NO" create-option on GeoRaster driver. > > > > > > > > Yes, -norat option in gdal_translate makes sense. > > > > > > IMHO, I don't think we should go to big deal of RPC discussion and > > > voting to add that option to gdal_translate. > > > > I've just added the option. Yes that's not worth a RFC ! > > Wow, that was fast. Look at the code, it seems that you are taking > advantage of the lack of support for RAT in VRT. Is that right? But I > think there was a discussion about adding that support for some other > reasons. Perhaps when someone wants to translate the RAT but also wants to > enter one of those gdal_translate parameters that triggers the VRT. So I > think that in the future we would need to add support for RAT to the VRT > driver
Yes, the implementation was trivial due to the lack of support for RAT in VRT. That's why I've added a regression test for -norat, so that if somebody implements RAT copying in VRT, they know that they must do something to unset it explicitely in gdal_translate -norat mode. > and also add a create-option on that same driver to tell it not do > create the RAT. Does it makes sense? If you've other use cases, yes the creation option makes sense. -- Geospatial professional services http://even.rouault.free.fr/services.html _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
