Re: [gdal-dev] gdalwarp ERROR 6: PHOTOMETRIC=YCBCR requires a source raster with only 3 bands (RGB)

OK, digging deep into my old emails I think I found a solution ( still to be proved): gdalwarp -t_srs EPSG:4326 -r bilinear -co TILED=YES -co BIGTIFF=YES -dstalpha -multi  '00010.jp2' '/data/satmap/tmp.tif' This took 39 min and expanded the 2.1G jp2 into 87G tif, then this gets followed by:

Re: [gdal-dev] gdalwarp ERROR 6: PHOTOMETRIC=YCBCR requires a source raster with only 3 bands (RGB)

On dimanche 1 juillet 2018 11:18:39 CEST Stephen Woodbridge wrote: > Right, but the point 1 is the message says: > ERROR 6: PHOTOMETRIC=YCBCR requires a source raster with only 3 bands (RGB) > ie: requires a source raster with only 3 bands (RGB) and the source > raster has only 3 bands! > -dstalpha

Re: [gdal-dev] gdalwarp ERROR 6: PHOTOMETRIC=YCBCR requires a source raster with only 3 bands (RGB)

Right, but the point 1 is the message says: ERROR 6: PHOTOMETRIC=YCBCR requires a source raster with only 3 bands (RGB) ie: requires a source raster with only 3 bands (RGB) and the source raster has only 3 bands! -dstalpha if I understand correctly is to create a alpha band in the output file. S

Re: [gdal-dev] gdalwarp ERROR 6: PHOTOMETRIC=YCBCR requires a source raster with only 3 bands (RGB)

Steve, Setting that alpha channel makes it 4 bands. RGB + alpha channel. Either remove the ycbcr or the alpha channel. Michael Smith Remote Sensing/GIS Center US Army Corps of Engineers > On Jul 1, 2018, at 10:07 AM, Stephen Woodbridge > wrote: > > Hi all, > > I'm trying to convert a utm j

[gdal-dev] gdalwarp ERROR 6: PHOTOMETRIC=YCBCR requires a source raster with only 3 bands (RGB)

Hi all, I'm trying to convert a utm jp2 file to a wgs84 tif file and getting "ERROR 6: PHOTOMETRIC=YCBCR requires a source raster with only 3 bands (RGB)" but the src file has only 3 RBG bands. gdalwarp -t_srs EPSG:4326 -dstalpha -r bilinear -of GTiff -co BIGTIFF=YES -co TILED=YES -co COMPRE

Re: [gdal-dev] GDALWARP Error

Am 16.01.18 um 14:24 schrieb Rasika Chinchwade: Please find attachment of files ​ 3DIMG_01JAN2018__L3B_HEM_DLY.h5 ​​ 3DIMG_01JAN2018_0130_L2B_LST.h5

Re: [gdal-dev] GDALWARP Error

Please find attachment of files ​ 3DIMG_01JAN2018__L3B_HEM_DLY.h5 ​​ 3DIMG_01JAN2018_0130_L2B_LST.h5 ​ On Tue, Jan 16

[gdal-dev] GDALWARP Error

Please guide me so that I will not stuck at this problem. I have used STD dataset of INSAT-3D https://www.mosdac.gov.in/catalog?field_satellitenode_nid=69 you can download the datset from www.mosdac.gov.in HEM daily ,LST product. product of INSAT3D .This all are in disc shape. I am trying to conv

Re: [gdal-dev] gdalwarp error 6 issues

Hi Even, Many thanks, will try gdal_edit.py permutations again over the weekend. Tomorrow is a busy day. Regards, Zoltan On 2016-09-01 21:12, Even Rouault wrote: Le jeudi 01 septembre 2016 19:41:18, Zoltan Szecsei a écrit : Hi Even, Long time no chat - Hope all is well with you. :-) When comp

Re: [gdal-dev] gdalwarp error 6 issues

Le jeudi 01 septembre 2016 19:41:18, Zoltan Szecsei a écrit : > Hi Even, > Long time no chat - Hope all is well with you. :-) > > When compiling GDAL, I just used all defaults, so it was just a > "straight" ./configure. > > The errant images are ENU on WGS84 Lo17 and Lo21, and I need to > reproje

Re: [gdal-dev] gdalwarp error 6 issues

Hi Even, Long time no chat - Hope all is well with you. :-) When compiling GDAL, I just used all defaults, so it was just a "straight" ./configure. The errant images are ENU on WGS84 Lo17 and Lo21, and I need to reproject to same but Lo19 (They are on the fringes of Lo19) I tried gdal_edit.

Re: [gdal-dev] gdalwarp error 6 issues

Zoltan, > Hi, > I've been struggling to get some 3200 orthos mosaicked and tiled. > They are very old and have really bad projection definitions, pixel > sizes and metadata funnies. > I'm down to the last 261, and have hit a brick wall. > Given that gdalwarp works on this image when I leave out s_

[gdal-dev] gdalwarp error 6 issues

Hi, I've been struggling to get some 3200 orthos mosaicked and tiled. They are very old and have really bad projection definitions, pixel sizes and metadata funnies. I'm down to the last 261, and have hit a brick wall. Given that gdalwarp works on this image when I leave out s_srs and t_srs (se

Re: [gdal-dev] gdalwarp: ERROR 2: Out of memory allocating {number} byte destination buffer.

Hi Frank, Thanks for the clear explanation. I've added, with light editing, to http://trac.osgeo.org/gdal/wiki/UserDocs/GdalWarp. I imagine you will just have to use more modest buffers or else get a 64bit executable for gdalwarp. Running gdalwarp with defaults (no options specified) seems

Re: [gdal-dev] gdalwarp: ERROR 2: Out of memory allocating {number} byte destination buffer.

On 11-06-08 03:05 PM, Matt Wilkie wrote: Hi Folks, Can anyone tell me what this error means and how to work around it? Win7 x64 command shell osgeo4w gdal 1.8 13gb ram (~4.7gb free according to Process Explorer) 121gb free on the drive (mapped to network) 20gb free on drive pointed to by %TEMP%

Re: [gdal-dev] gdalwarp: ERROR 2: Out of memory allocating {number} byte destination buffer.

Hey Matt, If i remember correctly osgeo4w is 32bit (its been a while since iv looked at the osgeo4w binaries however so i may be incorrect). If they are 32bit and you are setting -wm to 2048 (2GB) you might be having memory limitation issues (which i believe 2GB virtual memory for x86 exe

[gdal-dev] gdalwarp: ERROR 2: Out of memory allocating {number} byte destination buffer.

Hi Folks, Can anyone tell me what this error means and how to work around it? Win7 x64 command shell osgeo4w gdal 1.8 13gb ram (~4.7gb free according to Process Explorer) 121gb free on the drive (mapped to network) 20gb free on drive pointed to by %TEMP% There are 26 input files whose size rang

[gdal-dev] Gdalwarp error: warping imagery with coordinates across the international date line

I have an image with UTM coordinates across the international date line (longitude 180E or 180W) - please refer to the header information below, and now I want to convert this to a global projection Geographic WGS84 with GDALWARP. It seems the calculation for the output image size is wrong. Plea