Re: [gdal-dev] Python API: Geometry.Buffer with JOIN_STYLE

2024-10-04 Thread Even Rouault via gdal-dev
Le 04/10/2024 à 23:06, Barry DeZonia via gdal-dev a écrit : I don't know a lot about gdal but what if your call was just: geom.Buffer(6, ["JOIN_STYLE=MITRE"]) Yes, or using a dict. Cf https://github.com/OSGeo/gdal/blob/f1f750e1b25cfe22f2b2ce4795ee459beb3fa8d8/autotest/ogr/ogr_geom.py#L4711

Re: [gdal-dev] Python API: Geometry.Buffer with JOIN_STYLE

2024-10-04 Thread Barry DeZonia via gdal-dev
I don't know a lot about gdal but what if your call was just: geom.Buffer(6, ["JOIN_STYLE=MITRE"]) On Fri, Oct 4, 2024 at 3:55 PM Martin Landa via gdal-dev < gdal-dev@lists.osgeo.org> wrote: > Hi all, > > in the documentation [1] is mentioned: > > """ > Buffer(Geometry self, double distance, cha

[gdal-dev] Python API: Geometry.Buffer with JOIN_STYLE

2024-10-04 Thread Martin Landa via gdal-dev
Hi all, in the documentation [1] is mentioned: """ Buffer(Geometry self, double distance, char ** options)→ Geometry """ where the options argument points to [2]. But """ geom.Buffer(6, options=["JOIN_STYLE=MITRE"]) """ fails with """ File "/usr/lib/python3.11/site-packages/osgeo/ogr.py", l

Re: [gdal-dev] libkml: providing more information about builds that include LIBKML to steer users away from security pitfalls and questions for packagers who may build with libkml

2024-10-04 Thread Simon Eves via gdal-dev
Even Rouault wrote: > @SimonEves I was confused by your mention of autogen.sh and stuff. I > presume you're still using google/libkml. You'd probably have a slightly > better experience with libkml/libkml which has only a CMake build system. > Thanks. I'll pass that on. > ___

Re: [gdal-dev] libkml: providing more information about builds that include LIBKML to steer users away from security pitfalls and questions for packagers who may build with libkml

2024-10-04 Thread Even Rouault via gdal-dev
Hi, My thought would be that a few people (at least 2 as being a sole maintainer isn't a good idea) from the community would stand up and act as the new keepers of libkml. I guess we could host it at OSGeo/libkml because I'm not optimistic we can recover libkml/libkml. A few years ago I tried