Re: [gdal-dev] WriteBlock() not supported using JP2ECW driver?

For future doc readers: https://github.com/OSGeo/gdal/pull/9211 Le 07/02/2024 à 20:45, Even Rouault via gdal-dev a écrit : Scott, I’m trying to create a JPEG2000 file using the JP2ECW driver, but I’m getting “WriteBlock() not supported…”.  The same code works using the PNM driver. What am

Re: [gdal-dev] WriteBlock() not supported using JP2ECW driver?

Scott, I’m trying to create a JPEG2000 file using the JP2ECW driver, but I’m getting “WriteBlock() not supported…”.  The same code works using the PNM driver. What am I missing? This comment in the code

[gdal-dev] WriteBlock() not supported using JP2ECW driver?

Hi, I'm trying to create a JPEG2000 file using the JP2ECW driver, but I'm getting "WriteBlock() not supported...". The same code works using the PNM driver. What am I missing? Thanks, Scott Disclaimer The information contained in this electronic message and any attachments to this message

Re: [gdal-dev] axis order in gdal_translate

Thank you. Yes, I got confused with gdal.VectorTranslate and gdal_translate, when I really meant ogr2ogr. But you realized that already. Great catch. On Wed, 7 Feb 2024 at 18:09, Even Rouault wrote: > Javier, > > > Is there a way to tell gdal.VectorTranslate that transformation is >

Re: [gdal-dev] What is the empty pixel value for datasets?

Hi Sean, good question. gdal_create just calls GDALCreate(), and doesn't "burn" any pixel value by itself, unless you use the -burn switch Which brings the question to the behavior of GDALCreate() itself. And I don't think this is specified indeed and behavior will be driver dependant. I

[gdal-dev] What is the empty pixel value for datasets?

Hi all, I haven't found a specification for the empty pixel value of datasets created by, say, gdal_create. Is it format specific? -- Sean Gillies ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev

Re: [gdal-dev] axis order in gdal_translate

Javier, Is there a way to tell gdal.VectorTranslate that transformation is "always_xy", and I do not have to do the swaps manually? Or maybe there is a better way to do it? If you specify a pipeline, you need to make sure it is written in a way where its input coordinates are in the order

[gdal-dev] axis order in gdal_translate

Hi I am calling the python method osgeo.gdal.VectorTranslate to convert a GeoJSON (with CRS) to shapefile. To keep consistency among EPSG versions, I have the pipeline of the conversion, using what in pyproj was "always_xy=True" gdal.VectorTranslate( dst_file,

Re: [gdal-dev] Compyle gdal >=3.7: lib2to3 error

Hi, I have renamed my "/usr/bin/python3.9" and restarted all and I was able to close the thing, because it only took '/usr/bin/python3.11' into account Cheers -- ___ Andrea Borruso website: https://medium.com/tantotanto 38° 7' 48" N, 13° 21' 9" E, EPSG:4326