[gdal-dev] Re: 254 into 255

On 28/10/2011 20:08, Chaitanya kumar CH wrote: I meant the nodata value of ch00_form.tif This *is* the nodata value of ch00_form.tif. The vrt which I posted has been generated through a simple: $ gdal_translate -of vrt ch00_form.tif ch00_form.vrt The only modifications I made was to change S

[gdal-dev] Re: 254 into 255

I meant the nodata value of ch00_form.tif On Fri, Oct 28, 2011 at 11:33 PM, Hermann Peifer wrote: > On 28/10/2011 20:02, Chaitanya kumar CH wrote: > >> What was the nodata value in the original? >> >> >0.**00E+00 > > Hermann > -- Best regards, Chaitanya kumar CH. +91-9494447

[gdal-dev] Re: 254 into 255

On 28/10/2011 20:02, Chaitanya kumar CH wrote: What was the nodata value in the original? 0.00E+00 Hermann ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev

[gdal-dev] Re: 254 into 255

What was the nodata value in the original? On Fri, Oct 28, 2011 at 11:28 PM, Hermann Peifer wrote: > On 27/10/2011 10:58, Chaitanya kumar CH wrote: > >> >> A vrt file can implement your requirements. It can create a 'lookup >> table' to translate your pixel values... >> > > Chaitanya, > > I just

[gdal-dev] Re: 254 into 255

On 27/10/2011 10:58, Chaitanya kumar CH wrote: A vrt file can implement your requirements. It can create a 'lookup table' to translate your pixel values... Chaitanya, I just tried to translate an Int32 GeoTIFF with pixel values 111..523 into a byte-type GeoTIFF with values 1..44, using the L

Re: [gdal-dev] Re: 254 into 255

Try it with one file and list all the error messages. On Fri, Oct 28, 2011 at 9:43 PM, joolek wrote: > Seriously guys... I do admire your knowledge!! > Still can't get it to work :) > > -- > View this message in context: > http://osgeo-org.1803224.n2.nabble.com/254-into-255-tp6931988p6940762.htm

Re: [gdal-dev] Re: 254 into 255

Seriously guys... I do admire your knowledge!! Still can't get it to work :) -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/254-into-255-tp6931988p6940762.html Sent from the GDAL - Dev mailing list archive at Nabble.com. ___ gda

[gdal-dev] Re: 254 into 255

On 28/10/2011 09:09, Chaitanya kumar CH wrote: I'm sorry. I should have said that gdalbuildvrt does not support creation of the lookup table. Thanks for the clarification and for posting the vrt-lookup-table trick. This was very helpful. Hermann _

[gdal-dev] Re: 254 into 255

I'm sorry. I should have said that gdalbuildvrt does not support creation of the lookup table. On Fri, Oct 28, 2011 at 12:22 PM, Hermann Peifer wrote: > On 27/10/2011 14:48, Chaitanya kumar CH wrote: > >> However it [gdalbuildvrt] doesn't support complex sources.. >> > > Chaitanya, could you per

[gdal-dev] Re: 254 into 255

On 27/10/2011 14:48, Chaitanya kumar CH wrote: However it [gdalbuildvrt] doesn't support complex sources.. Chaitanya, could you perhaps elaborate on the above statement? joolek, About the batch-processing of 3000 files: in my Linux/Bash/GDAL-from-trunk environment, I would do something like

Re: [gdal-dev] Re: 254 into 255

J, The example I provided is for some other raster with three bands and resolution 500x500. Please go through the GDAL Virtual Format Tutorial[1] to get acquainted with what you are doing. You can dispose off the rasterXSize, rasterYSize, ScaleOffset, ScaleRatio, SrcRect and DstRect elements. If

Re: [gdal-dev] Re: 254 into 255

You can also modify the existing val_repl.py script, which modifies a specific value found in an input dataset. You would have to modify it because it changes the values for all bands, which is different from your case, that all bands must have that value (254). The doownside is that it's a littl

Re: [gdal-dev] Re: 254 into 255

Thanks for posting this! I had to no idea that this functionality existed. Is this documented somewhere? On Thu, Oct 27, 2011 at 4:58 AM, Chaitanya kumar CH wrote: > J, > > A vrt file[1] can implement your requirements. It can create a 'lookup > table' to translate your pixel values. > Start by

[gdal-dev] Re: 254 into 255

Thank you for that, really really thank you. I'll definitelly give a go. If u don't mind me asking two questions: - what do you mean by appropriate parts? - I have around 3000 files... can I batch it somehow? If so... would you be able to give me a hint how to do it? J -- View this message in co

[gdal-dev] Re: 254 into 255

Thank you for that, really really thank you. I'll definitelly give a go. If u don't mind me asking two questions: - what do you mean by appropriate parts? - I have around 3000 files... can I batch it somehow? If so... would you be able to give me a hint how to do it? J -- View this message in co

Re: [gdal-dev] Re: 254 into 255

J, A vrt file[1] can implement your requirements. It can create a 'lookup table' to translate your pixel values. Start by running gdalbuildvrt on your raster file and modify it to contain the LUT element. It will look something like this: utm.tif 1 0 1 0:0,2

[gdal-dev] Re: 254 into 255

Yes, this is exactly what I am struggling to do. Gdal is so powerful - but I can't get it working. J On 26 Oct 2011, at 17:10, "Chaitanya kumar CH [via OSGeo.org]" wrote: > Do you want to convert just the pixels with the values (254,254,254)? > > On Wed, Oct 26, 2011 at 9:33 PM, joolek <[hidd

Re: [gdal-dev] Re: 254 into 255

Do you want to convert just the pixels with the values (254,254,254)? On Wed, Oct 26, 2011 at 9:33 PM, joolek wrote: > Hi I basically want to convert all the 254 254 254 into 255 255 255... is > this possible? > > -- > View this message in context: > http://osgeo-org.1803224.n2.nabble.com/254-in

[gdal-dev] Re: 254 into 255

Hi I basically want to convert all the 254 254 254 into 255 255 255... is this possible? -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/254-into-255-tp6931988p6933182.html Sent from the GDAL - Dev mailing list archive at Nabble.com. ___