As part of a batch release of patches for stable branches, the 3.8.4 and
3.9.5 releases of GEOS are now available for download
https://libgeos.org/usage/download/ .
Note that GEOS 3.8.4 is the final release for the GEOS 3.8 series.
If you haven't already upgraded to a newer GEOS minor version
GEOS development team is happy to release GEOS 3.10.6, 3.11.3, and 3.12.1
releases.
Note these are bug fix and improvement releases.
Details at https://libgeos.org/posts/2023-11-11-geos-3-12-1-released/
We'll be releasing GEOS 3.8.4 EOL and GEOS 3.9.5 soon as well.
Thanks,
GEOS Development
Hmm what about GDAL built with GEOS on Mac, anything fun happen there?
From: Paul Ramsey
Sent: Friday, November 10, 2023 6:51 PM
To: Regina Obe
Cc: GEOS Development List ; PostGIS Development
Discussion
Subject: Re: [geos-devel] MacOS DYLD Fix
On Nov 10, 2023, at 3:46 PM
locations of
the dylib files in the ./configure.
P.
On Nov 9, 2023, at 6:38 PM, Regina Obe mailto:l...@pcorp.us> >
wrote:
I’ll hold off on releasing until there is consensus on this issue.
From: geos-devel mailto:geos-devel-boun...@lists.osgeo.org> > On Behalf Of Pau
I'll hold off on releasing until there is consensus on this issue.
From: geos-devel On Behalf Of Paul
Ramsey via geos-devel
Sent: Thursday, November 9, 2023 4:47 PM
To: GEOS Development List
Cc: Paul Ramsey
Subject: [geos-devel] MacOS DYLD Fix
>From XCode 15, the dyld linker no longer
>
> +1 for release of 3.8.4, 3.9.5, 3.10.6, 3.11.3, 3.12.1
> +1 for EOL 3.8
>
> --strk;
>
> On Mon, Nov 06, 2023 at 02:48:47PM -0500, Regina Obe via geos-devel
> wrote:
> > According to our chart here:
> >
> > https://libgeos.org/usage/download/
> &
Vote: Mark GEOS 3.8 EOL after GEOS 3.8.4 and
release 3.9.5, 3.10.6, 3.11.3, 3.12.1
+1. I can do the releases if you wish
On Nov 6, 2023, at 11:52 AM, Martin Davis via geos-devel
mailto:geos-devel@lists.osgeo.org> > wrote:
+1
On Mon, Nov 6, 2023 at 11:48 AM Regina Obe vi
According to our chart here:
https://libgeos.org/usage/download/
We should have EOL'd GEOS 3.8 last month.
Looks like we have only 2 changes for 3.8.4
https://github.com/libgeos/geos/blob/3.8/NEWS
Are we ready to release them and sunset this minor, or should we wait a
little longer?
I'm
FWIW Debian Buster I think ships with cmake 3.13 and it’s not that old. Old
but not that old.
-1 to increase the cmake version until the pressing reason can be better
explained or there are more pressing reasons.
As I recall I think Amazon had to upgrade their CMake to build the latest
> Paul Ramsey
> Sent: Sunday, June 25, 2023 7:46 PM
> To: GEOS Development List
> Subject: [geos-devel] Vote on 3.12.0 Release
>
> Does anyone object to a 3.12.0 release on Monday/Tuesday?
>
> P.
I don't. +1 to release.
___
geos-devel mailing list
> On Thu, Jun 15, 2023 at 6:30 AM Greg Troxel wrote:
>
> > Looking at the logs (at end), overall this smells like either a
> > systematic issue where the floating point on my system is broken, or
> > there is some slight floating point difference from x86, and geos
> > tests are very sensitive
No objection from me :)
Cut please
> -Original Message-
> From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of
> Paul Ramsey
> Sent: Wednesday, June 7, 2023 1:53 PM
> To: GEOS Development List
> Subject: [geos-devel] 3.12.0beta1
>
> Any objections to my cutting a
No objections.
+1 to push on.
> -Original Message-
> From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of
> Paul Ramsey
> Sent: Wednesday, March 15, 2023 6:35 PM
> To: GEOS Development List
> Subject: [geos-devel] Release 3.11.2, 3.10.5?
>
> Given a potentially
Graham,
Please do keep us posted on this with your trials and share your code.
As a fellow member of the “not one of us” crowd, I am interested in pushing
GEOS beyond the very confined geography domain.
Thanks,
Regina
From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On
I concur. Great work Dan :)
> -Original Message-
> From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of
> Paul Ramsey
> Sent: Monday, February 27, 2023 12:12 PM
> To: Howard Butler
> Cc: gdal dev ; GEOS Development List de...@lists.osgeo.org>
> Subject: Re:
t;
> > So I’m assuming such work, to even gain traction, would require some more
> concerted effort on the viewing side of things.
> >
> >
> >
> > Regina
> >
> >
> >
> > From: Even Rouault [mailto:even.roua...@spatialys.com]
> > Sent: Sunday, Ja
traction, would require some more
concerted effort on the viewing side of things.
Regina
From: Even Rouault [mailto:even.roua...@spatialys.com]
Sent: Sunday, January 29, 2023 6:19 AM
To: GEOS Development List ; Regina Obe
Subject: Re: [geos-devel] Writing a wrapper around LibGEOS
Sad yes
Graham,
At a glance looks good and I love the diagrams.
The doc doesn’t seem to mention how to use the API, more conceptual stuff. I
assume that will come once your API is more fleshed out. Would be interesting
to see the code. Probably easier to see major mistakes misunderstandings that
Can you roll out 3.6 too so we can end its life for good :)
https://github.com/libgeos/geos/blob/svn-3.6/NEWS
I know it has only 2 changes, but do we plan to ever push anymore to it?
I'm also okay with just calling it dead and saying it died in 3.6.5 if
everyone else is okay with that.
Thanks,
Just a side note to think about since we are discussing this.
The only issue I see possibly is with the Redhat/CentOS systems.
I know that yum.postgresql.org tries to offer the latest GEOS even on ancient
systems such as CentOS 7 which sadly many of my clients are still on. I think
though
No concerns from me. +1 for embracing C++14
From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of
Daniel Baston
Sent: Tuesday, January 17, 2023 7:56 PM
To: GEOS Development List
Subject: [geos-devel] Switching to C++14
Back in 2018, we discussed whether we should
I vote for drop for GEOS 3.12+
I guess technically we can’t drop for 3.11 and below since those would be
considered breaking changes.
I personally don’t have an interest in MSVC in general and I only have MSVC
2019 installed if I cared to use MSVC for anything. So dropping MSVC2015 is
: [geos-devel] GEOS 3.12 regression failure in PostGIS
Validity is only tested in the XY dimensions. So it's actually more
appropriate that only the XY value is reported.
On Fri, Oct 21, 2022 at 7:35 AM Regina Obe mailto:l...@pcorp.us> > wrote:
Hi all,
PostGIS geos310 regressio
: [geos-devel] GEOS 3.12 regression failure in PostGIS
It's not intentional. I will fix it in GEOS and add a test there. You might
consider removing the PostGIS test because it's only testing GEOS behavior.
Dan
On Fri, Oct 21, 2022 at 10:35 AM Regina Obe mailto:l...@pcorp.us> >
Hi all,
PostGIS geos310 regression test, detailed here:
https://trac.osgeo.org/postgis/ticket/5260
Started failing around October 18th.
The test is this:
SELECT '#168', ST_NPoints(g), ST_AsText(g), ST_isValidReason(g)
FROM ( VALUES
t;
> ATB,
> P
>
> > On Sep 23, 2022, at 11:46 AM, Sandro Santilli wrote:
> >
> > On Fri, Sep 23, 2022 at 02:29:12PM -0400, Regina Obe wrote:
> >>
> >> I just ask for votes when I feel whatever I am thinking of doing
> >> could be opposed by many or I my
> As you may have noticed I seem to be unable to keep up with the fast pace
> in which GEOS development and project organization is moving lately, so I
> think it is fair to step down from the PSC chair role to avoid becoming a
> bottleneck to decisions making.
>
> I won't go anywhere but
.
Thanks,
Regina
From: Regina Obe [mailto:l...@pcorp.us]
Sent: Tuesday, September 20, 2022 10:31 AM
To: 'GEOS Development List'
Subject: RE: [geos-devel] PSC Vote: RFC 11 Geos Versioning and EOL Policy -
MOTION PASSED
Passed with:
Regina +1
Paul +1
Martin +1
Dan +1
Sandro – don’t care
Versioning and EOL Policy
+1
On Mon, Sep 19, 2022 at 4:59 PM Martin Davis mailto:mtncl...@gmail.com> > wrote:
+1.
On Mon, Sep 12, 2022 at 11:34 AM Regina Obe mailto:l...@pcorp.us> > wrote:
Here is my formal request to vote on:
https://libgeos.org/development/rfcs/rfc11/
I am resending this again since no one bothered to vote.
+1 from me.
Sandro already gave a remark about "You made this voting business a second
job. Why don't you just do things and eventually we rage and cut your head?"
I'll keep that in mind next time I want to push something I know Sandro
> I would not take on the committment of "releases a new minor release every
> 1-2 years". It's really not a mandatory thing, as nobody has fixed funding
to
> implement new features while it may be possible we raise funds for more
> than one feature during a single year thus triggering 4 different
> Martin Davis writes:
>
> > Our development resource bandwidth, and also downstream pipeline size.
> >
> > I think we should have a policy of one minor release per year (if
> > needed) And (try to) make them somewhat scheduled (which we already
> do
> > informally, to align with PostGIS).
>
In
> To me, this policy is about saying that after 4 years, it's basically out
of the
> question to have an updated version.
Yes that is my intent.
So
A) no one not willing to fork over money dares to ask us to backport a
change to what we consider "an ancient version"
B) As developers not have
Here is my formal request to vote on:
https://libgeos.org/development/rfcs/rfc11/
To accompany that change we will
1) Put a link on https://libgeos.org/usage/download/ to that policy.
2) Put in a Final Release Date column on the download page (maybe
color-coded, though not sure how to color
Final release is pretty Boss. It kind of nicely makes the policy clear w/o
having
> to wade through a bunch of text and then do mental math to answer the
> question "is this EOL" and "when will this EOL".
>
>
>
> > On Sep 12, 2022, at 10:55 AM, Regina Obe
at the meeting.
-kurt
On Mon, Sep 12, 2022 at 9:19 AM Regina Obe mailto:l...@pcorp.us> > wrote:
That works for me :)
So I'll draft up an RFC to that effect. So just to be clear, that leaves
space open to:
We may put an update on such a release like 3.4 to the 3.4 branch
quot;support" does not appear in the text. Perhaps "will
not
> have any further numbered releases" is more correct than "not supported".
>
> P
>
> > On Sep 12, 2022, at 8:34 AM, Regina Obe wrote:
> >
> > I'm thinking simple fixes and
ginal Message-
> From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of
> Paul Ramsey
> Sent: Monday, September 12, 2022 11:20 AM
> To: GEOS Development List
> Subject: Re: [geos-devel] End of Life Policy (EOL)
>
>
>
> > On Sep 12, 2022, at 8
I'd like to make an RFC proposing a standardish End of Like Policy
Does anyone have an issue with that?
I'm thinking of a policy along the lines of
We support a release generally at most X plus years after the first version
of it, but we have discretion to increase that if needed.
X = 3 - 5
> > A key question is how to expose these operations in the GEOS C API. I
> > see two options:
> > 1) Model a Polygonal Coverage as an array of simple Polygons (and
> > possibly
> > MultiPolygons)
> > 2) Provide a Polygonal Coverage datatype (which might contain internal
> > topology)
>
> Could
+1
> -Original Message-
> From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of
> Paul Ramsey
> Sent: Tuesday, June 28, 2022 7:28 PM
> To: GEOS Development List
> Subject: [geos-devel] 3.11.0 Release Vote
>
> 3.11.0beta2 has been out for a week, and no complaints.
file libs changed
>
>
>
> > On Jun 15, 2022, at 9:32 AM, Regina Obe wrote:
> >
> > Now I see libgeos_c-1.dll and libgeos.dll.
> >
> > It's different from 3.9 and 3.10, which had libgeos_c.dll for the
> > c-api lib file but I'm fine with that. Just want to make sure
l-boun...@lists.osgeo.org] On Behalf Of
> Paul Ramsey
> Sent: Wednesday, June 15, 2022 12:17 PM
> To: GEOS Development List
> Cc: roger.biv...@nhh.no
> Subject: Re: [geos-devel] mingw64 file libs changed
>
> This is in main now.
>
> P
>
> > On Jun 14, 2022, at 1
and uninstall as part of an install process.
> -Original Message-
> From: Sandro Mani [mailto:manisan...@gmail.com]
> Sent: Tuesday, June 14, 2022 1:50 PM
> To: Regina Obe ; 'GEOS Development List' de...@lists.osgeo.org>; roger.biv...@nhh.no
> Subject: Re: [geos-devel] mingw64
g to want to
totally
> hide the c++ DLL inside the c DLL.
> But it's closer to what you were happy with before.
> ???
> P
>
> > On Jun 14, 2022, at 9:21 AM, Regina Obe wrote:
> >
> > In my case, I need the c++ library statically linked into the geos
C-api.
> >
In my case, I need the c++ library statically linked into the geos C-api.
I need the geos c-API shared but not the c++ one. The main reason for need
of c-api shared is all the extensions I ship rely on that.
So I don't want both statically linked.
Also for regression testing I do want to replace
which is stable?
> -Original Message-
> From: Sandro Mani [mailto:manisan...@gmail.com]
> Sent: Monday, June 13, 2022 1:33 PM
> To: GEOS Development List ; Regina Obe
>
> Subject: Re: [geos-devel] mingw64 file libs changed
>
> Hi
>
> I'm actually packa
Sent: Monday, June 13, 2022 12:32 PM
> To: GEOS Development List
> Subject: Re: [geos-devel] mingw64 file libs changed
>
>
>
> > On Jun 13, 2022, at 9:29 AM, Regina Obe wrote:
> >
> > Okay guess the question has been answered by
> >
> >
> https:/
Okay guess the question has been answered by
https://github.com/manisandro/geos/commit/927e442ab1da361d3f487e2b620a878dd1
1f191d
I'll have to live with it moving forward.
Thanks,
Regina
> -Original Message-
> From: Regina Obe [mailto:l...@pcorp.us]
> Sent: Monday, June 13, 2
I mentioned this on IRC, and Paul is looking into why the change was made.
I'm mentioning here in case someone knows the reason. Why was this change
made?
The library files on mingw64 changed:
For geos < 3.11 the files were
libgeos.dll, libgeos_c.dll
For geos 3.11 (including the just
None from me.
> -Original Message-
> From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of
> Paul Ramsey
> Sent: Thursday, June 9, 2022 3:10 PM
> To: GEOS Development List
> Subject: [geos-devel] DDISABLE_GEOS_INLINE
>
> A few months ago we removed all the .inl
No objection from me.
> -Original Message-
> From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of
> Paul Ramsey
> Sent: Monday, June 6, 2022 2:36 PM
> To: GEOS Development List
> Subject: [geos-devel] 3.11.0beta1
>
> Any objection to a beta release? We are feature
> They are coming for us, they are in the ceiling, they are in the room wtih
us...
>
> https://dewey.dunnington.ca/post/2022/building-bridges-arrow-parquet-and-
> geospatial-computing/
>
>
[Regina Obe]
Yah I've been hearing a lot about GeoParquet in the last month or so.
I
> Just getting the last changes to the CAPI into main, but in the meanwhile,
> would like approval to push out all the extant stable patch releases, 3.7,
3.8,
> 3.9, 3.10.
>
> +1!
>
> P
[Regina Obe]
+1
___
geos-devel ma
) Linked to the support page from the home page.
5) Got rid of the Navigation header
6) Added community resources to the git README.md page.
Thanks,
Regina
> -Original Message-
> From: Regina Obe [mailto:l...@pcorp.us]
> Sent: Monday, February 21, 2022 1:20 PM
> To: 'GEOS Deve
stuff than just a link to the mailing
list.
> One possible way to go about it.
>
> Howard
>
[Regina Obe]
This whole page should actually be called community
It's all about interacting with the community and a little about GEOS
governance
https://libgeos.org/development/
So perhaps th
Well touching the homepage and closing a ticket, I could not find where we
tell people how to get support from the project.
It wasn't on the home page - https://libgeos.org/
But instead was buried in the Development header -
https://libgeos.org/development/
Can I move the geos chat / matrix
+1 let's just copy it.
Thanks,
Regina
> -Original Message-
> From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of
> Paul Ramsey
> Sent: Wednesday, February 16, 2022 11:46 AM
> To: GEOS Development List
> Subject: Re: [geos-devel] [gdal-dev] GEOS Maintenance Grant
>
GEOS PSC +1
> -Original Message-
> From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of
> Howard Butler
> Sent: Tuesday, February 15, 2022 10:38 AM
> To: gdal dev
> Cc: GEOS Development List
> Subject: [geos-devel] GEOS Maintenance Grant
>
> GDAL PSC,
>
> When we
+1
Let's roll.
> -Original Message-
> From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of
> Paul Ramsey
> Sent: Thursday, January 13, 2022 7:55 PM
> To: GEOS Development List
> Subject: [geos-devel] 3.10.2 release
>
> I should roll a new patch release, any
es to that room
> > from the website ( http://libgeos.org/development/ ) and only keeping
> > the Matrix room ( https://matrix.to/#/#geos:osgeo.org ) ?
>
> Well if it's never going to work or whatnot, I guess, but surprise, I'd
rather
> use the osgeo slack and deprecate th
+1 for simple STRTree example and if you want the http -- put in a separate
repo.
Adding http examples into GEOS just feels like getting into too many waters.
> -Original Message-
> From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of
> Paul Ramsey
> Sent: Wednesday,
on this, but I did want to verify that
everything still
> worked at least for me, so I built against GEOS 3.6 and then swapped in
> everything from 3.6 to main at runtime, and it all worked fine.
>
> P
[Regina Obe]
What are your libraries called? Did the names stay the same?
In case
>> I know it probably sucks for most people, but for me it was great, cause
it
>> meant I don't have to deal with removing those
>> Old 3.10.0, 3.9.0 etc when I build installers.
> I would expect some packaging system that would remove them at
> uninstall/replace time.
My installer does remove
-x on
> /usr/pkg/bin/shp2pgsql has this output:
>
[Regina Obe]
It looks in the directory of the dependent executable first for dependencies
and then looks in PATH for what it couldn't find in the direct path.
I use the same trick (except export and $ signs) on Debbie and Berrie
> > So my PostGIS is compiled with GEOS 3.9.0, but it should work with
> > GEOS 3.11.
>
> You presumably have swapped out the geos implementation? How?
>
[Regina Obe]
I test PostGIS / PostgreSQL with a PostgreSQL launch script that sets the
path of all the key de
I was always under the assumption that the C-API should be upward compatible
(only the C++ API is unstable).
Normally I can do the following:
Compile PostGIS with GEOS say 3.9.0
Launch my PostgreSQL with GEOS 3.9.0
Then launch again with newer GEOS - in this case GEOS 3.11.
So my PostGIS is
> requests, did anyone test this ? Could a policy be to use these different
> syntax to refer to GitHub ?
>
> --strk;
>
> Libre GIS consultant/developer
> https://strk.kbt.io/services.html
[Regina Obe]
I'm all for prefixing the new tickets with GH-
That will also solve the
#2) The osgeo website (that is probably why google is ranking
geos.osgeo.org so highly)
https://www.osgeo.org/projects/geos/
Need to change visit website link to libgeos.org
> -Original Message-
> From: Regina Obe [mailto:l...@pcorp.us]
> Sent: Tuesday, November 9, 202
lete migration of all current and useful content from the wiki into
the
> web site.
> - Delete wiki content and replace front page with reference to new web
site
> location (libgeos.org)
> - Set trac to read-only
> - Scrape trac contents for posterity
>
> Anything I am missing
> On Fri, Oct 29, 2021 at 12:13:19PM -0700, Paul Ramsey wrote:
> > http://libgeos.org/development/rfcs/rfc10/
>
> That's a 404 for me.
>
[Regina Obe]
It will come back once pramsey has reset the config. It's really because
gh-pages is a branch of our
, and keeping just the one master table in the web site. Seems
silly to
> have a big master CI table in 3.9 that includes 3.8, 3.7, etc.
>
> P.
[Regina Obe]
+1
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel
> Paul Ramsey
> Sent: Friday, October 29, 2021 9:43 PM
> To: GEOS Development List
> Subject: [geos-devel] 3.9.2 Release?
>
> I call for approval of a 3.9.2 release! (rah!) The list of fixes is pretty
chunky at
> this point and it's been a while.
>
> +1 fro
stream projects
> Far easier story on how to we manage the project and where the
> important things happen
> Far less dependence on individual contributors for infrastructure
> work that only they can do
>
[Regina Obe]
-0
_
I'm fine with it.
> -Original Message-
> From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of
> Paul Ramsey
> Sent: Tuesday, October 26, 2021 10:40 AM
> To: GEOS Development List
> Subject: [geos-devel] NEWS.md
>
> Anyone have a strong objection to this?
>
>
+1
From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of
Daniel Baston
Sent: Monday, October 18, 2021 6:20 PM
To: GEOS Development List
Subject: Re: [geos-devel] 3.10.0 Release Vote
+1
On Mon, Oct 18, 2021 at 4:34 PM Paul Ramsey mailto:pram...@cleverelephant.ca> >
gt; GPG Key ID: 4096R/6750F10AE88D4AF1
> Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
[Regina Obe]
Okay that sucks :(
Looking at the story on debian
Bullseye (11) appears to be at 3.18.4 (fine)
Buster (10) 3.13.4 (barely good enough)
Stretch already doesn't have the minimum so gu
opining.
>
> pkgsrc has 3.21.2 now (and it looks like 3.21.3 just came out).
>
> 3.13.0 was released on 2018-11-20. That's almost 5 years ago, and I
therefore
> think it's entirely reasonable to require it if it makes anything even a
little bit
> better.
[Regina Obe]
FWIW
lib/libgcc_s.so.1 (0x800ca5000)
> libc.so.7 => /lib/libc.so.7 (0x800cbf000)
>
> [Regina Obe]
> This is what I see when I look at her latest run folder
>
> cd
> ~/workspace/GEOS_Worker_Run/label/bessie/4c38944f8b5ef440398ba5f8db
> 14b75489de5d68/build/lib]$
> ls
>
> -- Set runtime path of "/usr/bin/geosop" to ""
>
> Seems like it's actually doing exactly the right thing. Stuff in the build
> directory is all given a temporary run path to point into that directory
and for
> things being installed that path is
n in GH is now two days old, notwithstanding my
> pushing a lot of stuff in as we move to release.
> Is the replicator not running?
> P
[Regina Obe]
Should be fixed now
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel
e committed them.
>
> P
>
> > On Oct 1, 2021, at 2:41 AM, Sebastiaan Couwenberg
> wrote:
> >
> > The lintian QA tool reported a spelling error for the Debian package
build:
> >
> > * nunber -> number
> >
> > The attached patch fixes the issue.
> >
nDistance though, as
> maybe there's not much to improve there.
>
> --strk;
[Regina Obe]
If you are simply exposing functionality that was already in C++ API in the
C-API then I retract my -1. If you are doing more than that - like planning
to rewrite said C++ logic, my -1 stands.
just stubs) in a few hours.
>
> --strk;
> _______
> geos-devel mailing list
> geos-devel@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geos-devel
[Regina Obe]
So you are putting in non-functional features to be functional in 3.1
do want to roll this to release in time for PostGIS
3.2 to
> sit on top of it. What's your planned schedule?
>
> P
>
> >
> > --strk;
> > ___
> > geos-devel mailing list
> > geos-devel@lists.osgeo.org
> &
I do get 2.23606 on PostGIS so we are in agreement there.
As to what the right answer is I have no clue and reading math equations gives
me a headache.
I’ve added geos-develop to mailing list for comment.
Thanks,
Regina
From: Mobilitydb-dev
>
> A cron on some random computer somewhere with cached credentials is
> fragile, brittle, tied to the person who knows the details of it, and
probably
> insecure.
>
> Howard
>
[Regina Obe]
Howard -- I don't know who you are thinking of. I don't hate the Github
empir
existing LXC containers with letsencrypt and NGIX setup ?
>
> Setting up a cron job or git hook to build & publish the site upon commit
to a
> git repository would be easy (under Gitea).
>
[Regina Obe]
I think GH has a mechanism for autogenerating sites triggered on commit or
using a GH a
issue.
On Mon, Aug 23, 2021 at 9:08 AM Regina Obe mailto:l...@pcorp.us> > wrote:
As Paul mentioned he already has put in work for a new geos site.
Plan is to just host it on GH pages.
I'll start with a +1 from me.
Thanks,
Regina
__
gt; corner cases in the "hosting your own domain" aspects of GH pages, so a
bit
> of a research project.
>
[Regina Obe]
Yes it does -- aka gdal.org https://gdal.org
The only issue with (at least when GDAL was setup is that GH couldn't SSL
gdal.org and www.gdal.org so we h
As Paul mentioned he already has put in work for a new geos site.
Plan is to just host it on GH pages.
I'll start with a +1 from me.
Thanks,
Regina
___
geos-devel mailing list
geos-devel@lists.osgeo.org
> clean place for examples and documentation beyond just header doco and
> doxygen.
>
> > On Aug 22, 2021, at 11:16 PM, Regina Obe wrote:
> >
> > Right now GEOS does not have a real site.
> >
> > geos.osgeo.org is sitting on OSGeo6, which the index page simply
Right now GEOS does not have a real site.
geos.osgeo.org is sitting on OSGeo6, which the index page simply redirects
to trac.osgeo.org/geos.
The snapshot and doxygen build was done under pramsey's account on osgeo6
and that's the only thing that is hosted on geos.osgeo.org (which is on
osgeo6).
ibgeos/geos/pull/447 for a possible fix for
> > these issues.
> >
> > Cheers,
> > Mike
> >
[Regina Obe]
Just add a diff to the end like so?
https://github.com/libgeos/geos/pull/447.diff
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel
+1
From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of Paul
Ramsey
Sent: Friday, April 9, 2021 2:16 PM
To: GEOS Development List
Subject: [geos-devel] 3.8.2 ?
I'd like to do a release of 3.8.2, there is a shockingly large backlog and some
crashers hiding in there
> > That last one is quite a nasty one, do take a look. The fact that we
have a
> major correctness issue argues for quick release.
> >
> > https://github.com/libgeos/geos/issues/408
>
> With the soft freeze this Friday, it's too late to get this into the next
Debian
> stable release.
>
>
+1
> -Original Message-
> From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of
> Paul Ramsey
> Sent: Tuesday, February 9, 2021 6:56 PM
> To: GEOS Development List
> Subject: [geos-devel] 3.9.1 Release?
>
> I'd like to release 3.9.1 tomorrow. Some important fixes
I'm fine with having only cmake if the issue Paul raised below is fixed.
That is what I currently use for building.
> -Original Message-
> From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of
> Paul Ramsey
> Sent: Friday, January 8, 2021 12:30 PM
> To: GEOS
+1 for getting rid of the compile time switch.
> -Original Message-
> From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of
> Paul Ramsey
> Sent: Thursday, December 10, 2020 12:17 PM
> To: roger.biv...@nhh.no
> Cc: GEOS Development List
> Subject: Re: [geos-devel]
Yeh +1
> -Original Message-
> From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of
> Paul Ramsey
> Sent: Wednesday, December 9, 2020 11:47 AM
> To: GEOS Development List
> Subject: [geos-devel] 3.9.0 Train Departing
>
> I am going to package a release today, and
1 - 100 of 229 matches
Mail list logo
