On Sun, Jan 29, 2023 at 12:24 AM Regina Obe wrote:
> With that said, might be helpful to look at some other projects that use
> the C-API like “PostGIS”, or maybe you have already (all the files in that
> folder with geos in the name are wrappers around GEOS api:
>
Thank you! The two projects
I'm writing an interface library to wrap around LibGEOS which I hope will
simplify its use a little in other domains besides GIS. (Mainly for myself
but I'm documenting it in case it's useful to anyone else.)
Rather than look at the (currently somewhat fluid) API, I was hoping one or
two people
I'm using GEOS with the C API - I am trying to do something that as far as
I can tell from the documentation should be possible but I've tried every
call I think might do it and cannot get it to work:
I have a GEOS_POLYGON (or GEOS_MULTIPOLYGON) in one GEOSGeometry object and
a GEOS_LINESTRING
On Wed, Mar 8, 2023 at 1:12 PM Martin Davis wrote:
> As others have said on this thread, adding curve support to GEOS is likely
> to be a big effort.
>
> My opinion is that to consider an extension of this magnitude, there needs
> to be evidence that this initiative is feasible and sustainable
On Mon, Jan 30, 2023 at 9:09 AM Regina Obe wrote:
> Nyall,
>
> Thanks for the input. I got to check out QGIS more closely with PostGIS
> curved geometries. I admit to being a closeted Server/Database Admin
> person, not paying much attention to UIs beyond pgAdmin. It's good to know
> there is
Appreciate the pointer, thanks!
On Thu, Apr 6, 2023 at 6:08 AM Sandro Santilli wrote:
> FYI: the rttopo library is a fork of a library internally used by
> PostGIS to provide various algorithms on geographic datatypes
> including curves. The library does call into GEOS for many algorithms,
> in
OK, I have the solution now.
1) Starting at point X,Y draw a circle of radius B (B = buffering dist)
2) Construct the visibility polygon from X,Y limited by the circle.
3) The visibility polygon will be effectively a list of rays from
X,Y to points on the obstacles. Collect the list of
On Thu, Oct 12, 2023 at 4:25 AM Graham Toal wrote:
> You need a variation of the shortest path algorithm; it's basically a
> breadth-first flood fill, which is usually implemented by a raster
> algorithm, however it *is* possible to come up with something less
> expensive (but
You need a variation of the shortest path algorithm; it's basically a
breadth-first flood fill, which is usually implemented by a raster
algorithm, however it *is* possible to come up with something less
expensive (but more complex to code) by using a ray-tracing algorithm (or
more specifically
