Re: [gdal-dev] Convert alpha to nodata?

Rob, https://github.com/OSGeo/gdal/pull/9128 should do what you wish. As usual, the hardest part is the naming of options... Even Le 19/01/2024 à 18:32, Even Rouault via gdal-dev a écrit : Hi Rob, I can't think an easy way of doing what you want. Well, you can definitely do that using a VR

Re: [gdal-dev] units=km not working

Hi, Because the units mean the units of the projected coordinates. An example: https://epsg.io/map#srs=3067-1149&x=295545.168414&y=6836388.322477&z=4&layer=streets Here x and y are in meters: "+proj=utm +zone=35 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs +type=crs". By changing the th

Re: [gdal-dev] units=km not working

Le 23/01/2024 à 20:56, Wilco K via gdal-dev a écrit : Hi, why is *units=km* not working? * * *gdaltransform -s_srs EPSG:4326 -t_srs "+proj=stere +lat_0=90 +lon_0=0 +lat_ts=60 +a=6378.14 +b=6356.75 +x_0=0 +y_0=0 **+units=km" * The following error is returned: ERROR 1: PROJ: proj_create_operat

[gdal-dev] units=km not working

Hi, why is units=km not working? gdaltransform -s_srs EPSG:4326 -t_srs "+proj=stere +lat_0=90 +lon_0=0 +lat_ts=60 +a=6378.14 +b=6356.75 +x_0=0 +y_0=0 +units=km" The following error is returned: ERROR 1: PROJ: proj_create_operations: Source and target ellipsoid do not belong to the same celesti

Re: [gdal-dev] Layerstack multiple images, of different extents and variable number of bands

Hi, I recommend to study gdalbuildvrt https://gdal.org/programs/gdalbuildvrt.html and consider if it might be good for you with the -separate option. -Jukka Rahkonen- Lähettäjä: lef...@gmail.com Lähetetty: tiistai 23. tammikuuta 2024 21.51 Vastaanottaja: Rahkonen Jukka Kopio: gdal-dev@lists.o

Re: [gdal-dev] Layerstack multiple images, of different extents and variable number of bands

You've interpreted that correctly. On Tue, Jan 23, 2024 at 12:13 PM Rahkonen Jukka < jukka.rahko...@maanmittauslaitos.fi> wrote: > Hi, > > > > Please clarify what is the desired result. A multiband image that covers > the union of extents of all the input images, with a number of bands that > is

Re: [gdal-dev] Layerstack multiple images, of different extents and variable number of bands

Hi, Please clarify what is the desired result. A multiband image that covers the union of extents of all the input images, with a number of bands that is the sum of bands in all the inputs or what? -Jukka Rahkonen- Lähettäjä: gdal-dev Puolesta lefsky--- via gdal-dev Lähetetty: tiistai 23. t

[gdal-dev] Layerstack multiple images, of different extents and variable number of bands

I've been incorporating gdal into my processing pipelines and have a question about a feature. I need to be able to layer stack multiple images with different extents and varying numbers of bands, usually exceeding 1. I haven't been able to find a single command to do this in gdal. Am I missing so

Re: [gdal-dev] Non able to manage properly vitual file, warping and black edges

Hi Even, On Tue, 23 Jan 2024 at 14:59, Even Rouault wrote: > Perhaps due to a difference in the overview resampling method. The COG > driver uses cubic by default. Perhaps try adding -co RESAMPLING=AVERAGE to > compare compareable things. > using -co RESAMPLING=AVERAGE the total time is 30 min

Re: [gdal-dev] Non able to manage properly vitual file, warping and black edges

Hi, Please try to imagine that you are a stranger that might volunteer to help by running similar commands with same kind of imagery. Imagine a list of information and commands that you would need to know before you can do that. Then please share that information with us. -Jukka Rahkonen- Läh

Re: [gdal-dev] Non able to manage properly vitual file, warping and black edges

Perhaps due to a difference in the overview resampling method. The COG driver uses cubic by default. Perhaps try adding -co RESAMPLING=AVERAGE to compare compareable things. Le 23/01/2024 à 14:45, andy a écrit : Even, the verbose process lasts 24 minutes, the COG process lasts 36 minutes. Ther

Re: [gdal-dev] Non able to manage properly vitual file, warping and black edges

Even, the verbose process lasts 24 minutes, the COG process lasts 36 minutes. There is a 50% difference. Best regards -- ___ Andrea Borruso website: https://medium.com/tantotanto 38° 7' 48" N, 13° 21' 9" E, EPSG:4326 ___ "cercare e saper riconoscere chi e cosa,

Re: [gdal-dev] Non able to manage properly vitual file, warping and black edges

Hi Even, because it creates the overviews. You can disable creating them with -co > OVERVIEWS=NO > Sorry, but I didn't write down my whole procedure. After gdal_translate, I run gdaladdo --config GDAL_NUM_THREADS ALL_CPUS --config BIGTIFF_OVERVIEW YES --config INTERLEAVE_OVERVIEW PIXEL -r averag

Re: [gdal-dev] Non able to manage properly vitual file, warping and black edges

Le 23/01/2024 à 13:38, andy a écrit : Hi Even, the COG is a much simpler command, it keeps everything in a little bit, but it is much slower than the more verbose procedure I wrote. So I ruled it out. because it creates the overviews. You can disable creating them with -co OVERVIEWS=NO Than

Re: [gdal-dev] Non able to manage properly vitual file, warping and black edges

Hi Even, the COG is a much simpler command, it keeps everything in a little bit, but it is much slower than the more verbose procedure I wrote. So I ruled it out. Thank you very much for the information you gave me, valuable -- ___ Andrea Borruso website: https://medium.com/tant

Re: [gdal-dev] Non able to manage properly vitual file, warping and black edges

But I need another piece of advice. Using alpha transparency, with the 4 bands, I cannot use PHOTOMETRIC=YCBCR, and I used PHOTOMETRIC=RGB. This way the compression is a little less effective. Is there anything comparable, in terms of compression effectiveness, when using alpha transparency