On Fri, 1 Jul 2022, Ainslie Johnstone wrote:
Hi there,
I am trying to downsample a high-resolution file of gridded
population estimates (1km res over the whole world). I want the
downsampled version to give the total population in the new
lower-resolution grid. However, whenever I downsample us
Hi there,
I am trying to downsample a high-resolution file of gridded population
estimates (1km res over the whole world). I want the downsampled version to
give the total population in the new lower-resolution grid. However, whenever I
downsample using gdalwarp -r sum, I don’t seem to be gett
Le 01/07/2022 à 13:59, DELEPINE Christophe a écrit :
Hi Even
I managed to get it working. There was a bug in my code which
prevented features to be added to the second layer. In that case, the
driver does not export the empty layer.
In the MVT driver documentation, it says : Part of the co
Hi Even
I managed to get it working. There was a bug in my code which prevented
features to be added to the second layer. In that case, the driver does not
export the empty layer.
In the MVT driver documentation, it says : Part of the conversion is
multi-threaded by default, using as many threa
> cmake -DSQLITE3_INCLUDE_DIR=~/build/include
> -DSQLITE3_LIBRARY=~/build/lib/libsqlite3.a ..
For static linkage, this may work for sqlite3, But often just providing the
library file path is not enough because it lacks transitive usage requirements
(i.e. additional libs like iconv).
> ld: lib
Looking at driver code and testing a bit with the following, I don't see
any issue or need to create all layers before adding features to them
e.g with the following OGR Python script:
from osgeo import ogr, osr
srs = osr.SpatialReference()
srs.SetFromUserInput('EPSG:3857')
ds = ogr.GetDriverBy
I also tried the MVT driver and got the same problem : the output metadata.json
only lists one layer.
Should I create all layers first before adding features to them ?
The C++ API documentation does not explain how to write several layers in the
case of a MBTILES/MVT dataset
De : DELEPINE Chri
Hi Nik,
Great context you provided, along with your question, in this email comm.
Don't know if this is going to be of any help for you.
But, I noticed you had an uppercase S to system somewhere, while using
an lowercase s to system elsewhere.
Note,
somewhere=[email line number unknown],[em
Nik,
regarding the build isssue with Mac system sqlite3, I've filed this as
https://github.com/OSGeo/gdal/issues/6011
regarding your other "Configuring incomplete, errors occurred!" issue,
I've found that generally the CMakeOutput.log and CMakeError.log files
aren't the best way to spot the
Thanks again for all the replies and advice. I should have provided more
context around my initial query about building GDAL with cmake on macOS. So
here goes… (this is quite long, so bear with me…)
My ultimate aim is to build GDAL 3.6 (not yet released) for iOS on ARM (as well
as for macOS o
+1 Mateusz
On Fri, 1 Jul 2022 at 09:14, Even Rouault wrote:
>
> Hi,
>
> Motion:
>
> Adopt GDAL 3.5.1RC2 as final 3.5.1 release
>
> Starting with my +1
>
> Even
>
> --
> http://www.spatialys.com
> My software is free, but my time generally not.
>
> ___
>
Hi,
Motion:
Adopt GDAL 3.5.1RC2 as final 3.5.1 release
Starting with my +1
Even
--
http://www.spatialys.com
My software is free, but my time generally not.
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/
12 matches
Mail list logo
