[gdal-dev] ogr2ogr from MySQL to FileGDB not working correctly in 2.x

2017-12-18 Thread Thanny
I hope this is the correct place to post about this. There are several use cases I have for moving data into MySQL for processing, then exporting back out to ESRI FileGDB, using the ogr2ogr utility. Long story short, if I use a GDAL 1.x install, I'm able to export from MySQL to FileGDB without

[gdal-dev] gpkg file convrsion

2017-12-18 Thread omerz
I have a gpkg thats populated exclusively by .jpeg files. I am attempting to use the gdaladdo to add overviews into that gpkg. However, gdaladdo adds some of them as .jpeg, and adds the rest as .png. I was wondering if there is any way to configure gdaladdo so that it will only add the overviews

Re: [gdal-dev] GDAL 2.2.3 planning

2017-12-18 Thread Sebastiaan Couwenberg
On 11/01/2017 11:32 AM, Even Rouault wrote: > I've add an exchange with Sebastiaan Couwenberg about a schedule that would > give GDAL 2.2.3 a chance to enter the next Ubuntu LTS 18.04. While the date > for the import freeze from Debian to Ubuntu is not know yet, based on the > last > release

Re: [gdal-dev] SetNoDataValue on in-memory datasets via python

2017-12-18 Thread Even Rouault
Jake, > > mem_s_fh = gdal.GetDriverByName("MEM").Create('', temp_cols, temp_rows, > 1, gdal.GDT_Float32) mem_s_fh.SetGeoTransform([0, cell_size, 0, 0, 0, > cell_size]) > mem_s_fh.SetNoDataValue(s_nodata) SetNoDataValue() is a rasterband level method, not dataset. So should be

[gdal-dev] SetNoDataValue on in-memory datasets via python

2017-12-18 Thread Jacob Adams
I think I've found a bug in the python bindings, but I want to run it by the list before I open a ticket to make sure I'm not missing anything (I'm assuming you'd rather I check it out on the list first rather than cluttering the ticket system with bugs that aren't actually bugs). Environment:

Re: [gdal-dev] Why gdal_rasterize fails with MBTiles output?

2017-12-18 Thread Rahkonen Jukka (MML)
Hi Even, I agree that the first error message says it all and I guessed that the issue was in initializing the output to suit with the tile boundaries. I would also say that the documentation of MBTiles format is not so clear for users who have as little experience as I have, or less. "The

Re: [gdal-dev] Why gdal_rasterize fails with MBTiles output?

2017-12-18 Thread Even Rouault
Jukka, > > gdal_rasterize -ot Byte -burn 255 -burn 0 -burn 0 -ts 4950 4950 > -of MBTiles points_3857.json points_3857.mbtiles > ERROR 6: Could not find an appropriate zoom level that matches raster pixel > size The error message says it all, doesn't it ? MBTiles only accepts a single tiling

[gdal-dev] Why gdal_rasterize fails with MBTiles output?

2017-12-18 Thread Rahkonen Jukka (MML)
Hi, Captured from gis.stackexchange https://gis.stackexchange.com/questions/264899/create-mbtiles-from-geojson-in-raster-format I made some test data in EPSG:3857 and while GeoTIFF output works fine with GDAL 2.3dev gdal_rasterize -ot Byte -burn 255 -burn 0 -burn 0 -ts 4950 4950 -of GTiff