[gdal-dev] gdal_fillnodata - odd artifacts

2024-02-09 Thread Stephen Knox via gdal-dev
Hi all, I'm seeing an odd artifact when using gdal_fillnodata.py. My source raster is (https://i.stack.imgur.com/t42tR.png) (purple is no data, white and black are two different numeric values). Using a mask exactly corresponding to the no data pixels (i.e. all no data pixels are set to 0 in the

[gdal-dev] GeoParquet / GeoArrow docs

2022-04-20 Thread Stephen Knox
Just looked at the docs since the GeoParquet pull request was merged. ( https://gdal.org/drivers/vector/parquet.html) Wondering if might be useful to add that the Parquet and Arrow Drivers are only present since version 3.5. I know it's experimental, so not finalised, but people might be confused

Re: [gdal-dev] ogr2ogr for windows

2019-10-18 Thread Stephen Knox
I think you can install the ESRI FileGDB from OSGeo4W: http://download.osgeo.org/osgeo4w/x86/versions.html - see gdal-filegdb On Fri, Oct 18, 2019 at 11:49 AM jratike80 < jukka.rahko...@maanmittauslaitos.fi> wrote: > Hi, > > You may be behind a proxy server and you must use the Advanced Install

[gdal-dev] GIS Stack Exchange questions - delete geopackage layer

2019-10-17 Thread Stephen Knox
I've got a couple of questions here - I know this is not an official support channel, but wondered if anyone could take a look, particularly at the first one, which I will reproduce here. Thanks in advance. https://gis.stackexchange.com/questions/339011/gdal-delete-geopackage-layer This seems lik

Re: [gdal-dev] ogr2ogr for windows

2019-10-17 Thread Stephen Knox
You probably need to install osgeo4w (https://trac.osgeo.org/osgeo4w/) On Thu, Oct 17, 2019 at 8:30 AM wrote: > Hi List! > > I’m looking for ogr2ogr for Windows with "FileGDB" (R/W) and “aeronavFAA“ > included is there a place where I can download it? > > > > I’ve tried: > > C:\>pip install C\Do

[gdal-dev] Confusion between OSM Open options USE_CUSTOM_INDEXING and OSM_USE_CUSTOM_INDEXING

2019-08-04 Thread Stephen Knox
Hi list, There seem to be inconsistencies between the code, the API docs and error messages about whether the correct parameter name is USE_CUSTOM_INDEXING or OSM_USE_CUSTOM_INDEXING. I assume from the docs that it is USE_CUSTOM_INDEXING, so was planning to make a pull request to ensure the docs