[geos-commits] [SCM] GEOS branch gh-pages updated. cfc5eb5ef26bed0aa5dfe1eea2b626be67e7e1b3
git at osgeo.org
git at osgeo.org
Thu Nov 11 09:44:36 PST 2021
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GEOS".
The branch, gh-pages has been updated
via cfc5eb5ef26bed0aa5dfe1eea2b626be67e7e1b3 (commit)
from 41f8b814f8e9f714adbba4fc641c5e8c6f9637bb (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit cfc5eb5ef26bed0aa5dfe1eea2b626be67e7e1b3
Author: pramsey <pramsey+github at cleverelephant.ca>
Date: Thu Nov 11 17:44:07 2021 +0000
Deploying to gh-pages from @ libgeos/geos at f0d7ac29dffae2318ae130cd1775fe3c755d8312 🚀
diff --git a/404.html b/404.html
index 3d1e43e8e..b6df12fca 100644
--- a/404.html
+++ b/404.html
@@ -42,7 +42,7 @@
<header class="gdoc-header">
<div class="container flex align-center justify-between">
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
@@ -62,7 +62,7 @@
<div class="gdoc-error__line gdoc-error__code">Error 404</div>
<div class="gdoc-error__line gdoc-error__help">
Seems like what you are looking for can't be found. Don't worry we can
- bring you back to the <a class="gdoc-error__link" href="http://libgeos.org/">homepage</a>.
+ bring you back to the <a class="gdoc-error__link" href="https://libgeos.org/">homepage</a>.
</div>
</div>
</div>
diff --git a/categories/index.xml b/categories/index.xml
index 62cb7ad27..a10188fc2 100644
--- a/categories/index.xml
+++ b/categories/index.xml
@@ -2,9 +2,9 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Categories on GEOS</title>
- <link>http://libgeos.org/categories/</link>
+ <link>https://libgeos.org/categories/</link>
<description>Recent content in Categories on GEOS</description>
<generator>Hugo -- gohugo.io</generator>
- <language>en-us</language><atom:link href="http://libgeos.org/categories/index.xml" rel="self" type="application/rss+xml" />
+ <language>en-us</language><atom:link href="https://libgeos.org/categories/index.xml" rel="self" type="application/rss+xml" />
</channel>
</rss>
diff --git a/development/ci_status/index.html b/development/ci_status/index.html
index a68757c95..c20809498 100644
--- a/development/ci_status/index.html
+++ b/development/ci_status/index.html
@@ -48,7 +48,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
@@ -682,7 +682,7 @@
</tr>
</tbody>
</table>
-<div class="gdoc-page__anchorwrap"><h2 id="runners">Runners<a data-clipboard-text="http://libgeos.org/development/ci_status/#runners" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Runners" href="#runners"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="runners">Runners<a data-clipboard-text="https://libgeos.org/development/ci_status/#runners" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Runners" href="#runners"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<ul>
<li><strong>GitHub</strong> - Ubuntu various, Windows various, CMake</li>
<li><strong>GitLab</strong> - Debian 8.2, GNU/Linux 64bit, GCC, automake</li>
diff --git a/development/index.html b/development/index.html
index a40b4237e..7666cb835 100644
--- a/development/index.html
+++ b/development/index.html
@@ -31,7 +31,7 @@
<link rel="preload" href="/custom.css" as="style">
<link rel="stylesheet" href="/custom.css" media="all">
-<link rel="alternate" type="application/rss+xml" href="http://libgeos.org/development/index.xml" title="GEOS" />
+<link rel="alternate" type="application/rss+xml" href="https://libgeos.org/development/index.xml" title="GEOS" />
<!-- Made with Geekdoc theme https://github.com/thegeeklab/hugo-geekdoc -->
</head>
@@ -49,7 +49,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
@@ -597,7 +597,7 @@
-<div class="gdoc-page__anchorwrap"><h2 id="developer-resources">Developer Resources<a data-clipboard-text="http://libgeos.org/development/#developer-resources" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Developer Resources" href="#developer-resources"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="developer-resources">Developer Resources<a data-clipboard-text="https://libgeos.org/development/#developer-resources" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Developer Resources" href="#developer-resources"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<ul>
<li><strong>git</strong> repository: <a href="https://github.com/libgeos/geos">https://github.com/libgeos/geos</a></li>
<li><a href="https://lists.osgeo.org/mailman/listinfo/geos-devel"><strong>geos-devel</strong> mailing list</a> and <a href="https://lists.osgeo.org/pipermail/geos-devel/">archive</a></li>
@@ -608,17 +608,17 @@
</ul>
</li>
</ul>
-<div class="gdoc-page__anchorwrap"><h2 id="bug-reporting">Bug Reporting<a data-clipboard-text="http://libgeos.org/development/#bug-reporting" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Bug Reporting" href="#bug-reporting"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="bug-reporting">Bug Reporting<a data-clipboard-text="https://libgeos.org/development/#bug-reporting" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Bug Reporting" href="#bug-reporting"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>Defects should be reported using <a href="https://github.com/libgeos/geos/issues">GitHub Issues</a>.</p>
-<p>When submitting bugs caused by particular geometries, you must submit the geometries that cause the failure, preferably in hex-encoded <a href="http://libgeos.org/specifications/wkb/">WKB</a>, so that we can re-produce the failure cases.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="contributing">Contributing<a data-clipboard-text="http://libgeos.org/development/#contributing" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Contributing" href="#contributing"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<p>When submitting bugs caused by particular geometries, you must submit the geometries that cause the failure, preferably in hex-encoded <a href="https://libgeos.org/specifications/wkb/">WKB</a>, so that we can re-produce the failure cases.</p>
+<div class="gdoc-page__anchorwrap"><h2 id="contributing">Contributing<a data-clipboard-text="https://libgeos.org/development/#contributing" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Contributing" href="#contributing"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>To contribute fixes to outstanding issues, enhancements, and other smaller changes, open a <a href="https://github.com/libgeos/geos/pulls">pull request</a> with your change and a fullsome description of what you are trying to achieve.</p>
<p>If you have any doubts as to whether your work, or planned work, is not a “smaller” change, please join the <a href="https://lists.osgeo.org/mailman/listinfo/geos-devel"><strong>geos-devel</strong> mailing list</a> and describe your plans. <strong>Join the list!</strong> It is a great way to get acquainted with what the development community is working on.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="relationship-to-jts">Relationship to JTS<a data-clipboard-text="http://libgeos.org/development/#relationship-to-jts" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Relationship to JTS" href="#relationship-to-jts"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="relationship-to-jts">Relationship to JTS<a data-clipboard-text="https://libgeos.org/development/#relationship-to-jts" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Relationship to JTS" href="#relationship-to-jts"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>GEOS started as a direct port to C++ of the <a href="http://tsusiatsoftware.net/jts/main.html">JTS Topology Suite</a> (JTS), and remains tightly bound to that project. Most core algorithms have been prototyped in JTS and ported to GEOS when complete.</p>
<p>The projects attempt to share testing data, and to ascertain when failures are caused by differences in implementation (GEOS fails and JTS does not) and when they are caused by algorithm (both libraries fail).</p>
-<div class="gdoc-page__anchorwrap"><h2 id="governance">Governance<a data-clipboard-text="http://libgeos.org/development/#governance" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Governance" href="#governance"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
-<p>The GEOS project is run by a <a href="(http://libgeos.org/development/psc/)">Project Steering Committee</a> made up of developers and contributors to the project and is a project of <a href="https://www.osgeo.org/projects/geos/">OSGeo</a>.</p>
+<div class="gdoc-page__anchorwrap"><h2 id="governance">Governance<a data-clipboard-text="https://libgeos.org/development/#governance" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Governance" href="#governance"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<p>The GEOS project is run by a <a href="(https://libgeos.org/development/psc/)">Project Steering Committee</a> made up of developers and contributors to the project and is a project of <a href="https://www.osgeo.org/projects/geos/">OSGeo</a>.</p>
</article>
diff --git a/development/index.xml b/development/index.xml
index f0f5e08ff..e4bd801ad 100644
--- a/development/index.xml
+++ b/development/index.xml
@@ -2,17 +2,17 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Development on GEOS</title>
- <link>http://libgeos.org/development/</link>
+ <link>https://libgeos.org/development/</link>
<description>Recent content in Development on GEOS</description>
<generator>Hugo -- gohugo.io</generator>
<language>en-us</language>
- <lastBuildDate>Mon, 04 Oct 2021 14:21:00 -0700</lastBuildDate><atom:link href="http://libgeos.org/development/index.xml" rel="self" type="application/rss+xml" />
+ <lastBuildDate>Mon, 04 Oct 2021 14:21:00 -0700</lastBuildDate><atom:link href="https://libgeos.org/development/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Project Steering Committee</title>
- <link>http://libgeos.org/development/psc/</link>
+ <link>https://libgeos.org/development/psc/</link>
<pubDate>Wed, 27 Oct 2021 00:00:00 -0700</pubDate>
- <guid>http://libgeos.org/development/psc/</guid>
+ <guid>https://libgeos.org/development/psc/</guid>
<description>The GEOS project is run by a Project Steering Committee made up of developers and contributors to the project and is a project of OSGeo. Major project decisions are made via a Request for Comments (RFC) process, where proposals are first documented and then voted on by the steering committee.
This PSC list is valid as of November 10, 2021.
Sandro Santilli (chair) Martin Davis Howard Butler Regina Obe Dale Lutz Paul Ramsey Dan Baston The PSC approves major changes and RFC documents.</description>
@@ -20,10 +20,10 @@ This PSC list is valid as of November 10, 2021.
<item>
<title>CI Status</title>
- <link>http://libgeos.org/development/ci_status/</link>
+ <link>https://libgeos.org/development/ci_status/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/development/ci_status/</guid>
+ <guid>https://libgeos.org/development/ci_status/</guid>
<description>CI main 3.10 3.9 3.8 3.7 GitHub GitLab Azure Debbie Winnie Dronie Bessie Bessie32 Runners GitHub - Ubuntu various, Windows various, CMake GitLab - Debian 8.</description>
</item>
diff --git a/development/psc/index.html b/development/psc/index.html
index 85a019cb8..e8330edfa 100644
--- a/development/psc/index.html
+++ b/development/psc/index.html
@@ -48,7 +48,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
@@ -604,7 +604,7 @@
-<p>The GEOS project is run by a Project Steering Committee made up of developers and contributors to the project and is a project of <a href="https://www.osgeo.org/projects/geos/">OSGeo</a>. Major project decisions are made via a <a href="http://libgeos.org/development/rfcs/">Request for Comments</a> (RFC) process, where proposals are first documented and then voted on by the steering committee.</p>
+<p>The GEOS project is run by a Project Steering Committee made up of developers and contributors to the project and is a project of <a href="https://www.osgeo.org/projects/geos/">OSGeo</a>. Major project decisions are made via a <a href="https://libgeos.org/development/rfcs/">Request for Comments</a> (RFC) process, where proposals are first documented and then voted on by the steering committee.</p>
<p>This PSC list is valid as of November 10, 2021.</p>
<ul>
<li><a href="https://gitlab.com/strk">Sandro Santilli</a> (chair)</li>
diff --git a/development/rfcs/index.html b/development/rfcs/index.html
index 1146ff9a9..ac8145130 100644
--- a/development/rfcs/index.html
+++ b/development/rfcs/index.html
@@ -31,7 +31,7 @@
<link rel="preload" href="/custom.css" as="style">
<link rel="stylesheet" href="/custom.css" media="all">
-<link rel="alternate" type="application/rss+xml" href="http://libgeos.org/development/rfcs/index.xml" title="GEOS" />
+<link rel="alternate" type="application/rss+xml" href="https://libgeos.org/development/rfcs/index.xml" title="GEOS" />
<!-- Made with Geekdoc theme https://github.com/thegeeklab/hugo-geekdoc -->
</head>
@@ -49,7 +49,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
@@ -604,7 +604,7 @@
-<div class="gdoc-page__anchorwrap"><h2 id="process">Process<a data-clipboard-text="http://libgeos.org/development/rfcs/#process" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Process" href="#process"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="process">Process<a data-clipboard-text="https://libgeos.org/development/rfcs/#process" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Process" href="#process"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>The Request for Comments process is as follows:</p>
<ol>
<li>Create a pull request against this repository adding a new RFC document outlining your planned change.</li>
@@ -612,7 +612,7 @@
<li>Call for a vote on the RFC.</li>
<li>Note the status and commit the RFC to the web site for the record.</li>
</ol>
-<div class="gdoc-page__anchorwrap"><h2 id="rfcs">RFCs<a data-clipboard-text="http://libgeos.org/development/rfcs/#rfcs" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor RFCs" href="#rfcs"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="rfcs">RFCs<a data-clipboard-text="https://libgeos.org/development/rfcs/#rfcs" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor RFCs" href="#rfcs"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
diff --git a/development/rfcs/index.xml b/development/rfcs/index.xml
index 9d578bceb..74ef91106 100644
--- a/development/rfcs/index.xml
+++ b/development/rfcs/index.xml
@@ -2,17 +2,17 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Requests for Comment on GEOS</title>
- <link>http://libgeos.org/development/rfcs/</link>
+ <link>https://libgeos.org/development/rfcs/</link>
<description>Recent content in Requests for Comment on GEOS</description>
<generator>Hugo -- gohugo.io</generator>
<language>en-us</language>
- <lastBuildDate>Mon, 04 Oct 2021 14:21:00 -0700</lastBuildDate><atom:link href="http://libgeos.org/development/rfcs/index.xml" rel="self" type="application/rss+xml" />
+ <lastBuildDate>Mon, 04 Oct 2021 14:21:00 -0700</lastBuildDate><atom:link href="https://libgeos.org/development/rfcs/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>GEOS RFC 10 - Move Project to GitHub</title>
- <link>http://libgeos.org/development/rfcs/rfc10/</link>
+ <link>https://libgeos.org/development/rfcs/rfc10/</link>
<pubDate>Fri, 29 Oct 2021 00:00:00 -0700</pubDate>
- <guid>http://libgeos.org/development/rfcs/rfc10/</guid>
+ <guid>https://libgeos.org/development/rfcs/rfc10/</guid>
<description>RFC 10 Move Project to GitHub Author Paul Ramsey Contact pramsey at cleverelephant.ca Status Accepted, November 9, 2021 GitHub has been the largest source of 3rd party code contribution via pull-requests for some time now.
Moving to Github has the following components:
Move the canonical (writeable) repository to GitHub Migrate the (current, useful) contents of the Trac wiki to the new web framework Deleting the migrated and out-of-date contents of the Trac wiki Switching the Trac tickets to read-only Web scraping the Trac ticket contents and placing in a geos-old-tickets repo At that point:</description>
@@ -20,20 +20,20 @@ Moving to Github has the following components:
<item>
<title>GEOS RFC 1 - Project Steering Committee</title>
- <link>http://libgeos.org/development/rfcs/rfc01/</link>
+ <link>https://libgeos.org/development/rfcs/rfc01/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/development/rfcs/rfc01/</guid>
+ <guid>https://libgeos.org/development/rfcs/rfc01/</guid>
<description>This document describes how the PSC GEOS Project Steering Committee determines membership, and makes decisions on all aspects of the GEOS project - both technical and non-technical.
RFC 1 Project Steering Committee Author Paul Ramsey Contact pramsey at cleverelephant.ca Status Approved, April 10, 2008 Summary This document describes how the GEOS Project Steering Committee (PSC) determines membership, and makes decisions on all aspects of the GEOS project - both technical and non-technical.</description>
</item>
<item>
<title>GEOS RFC 2 - Committer Guidelines </title>
- <link>http://libgeos.org/development/rfcs/rfc02/</link>
+ <link>https://libgeos.org/development/rfcs/rfc02/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/development/rfcs/rfc02/</guid>
+ <guid>https://libgeos.org/development/rfcs/rfc02/</guid>
<description>This document describes the technical and legal responsibilities of [wiki:PSC GEOS committers].
RFC 2 Committer Guidelines Author Paul Ramsey, Regina Obe Contact pramsey at cleverelephant.ca, lr at pcorp.us Status Draft Summary This document describes the technical and legal responsibilities of [wiki:PSC GEOS committers].
Election to GIT Commit Access Permission for GIT commit access shall be provided to new developers only if accepted by the [wiki:PSC GEOS Project Steering Committee].</description>
@@ -41,10 +41,10 @@ Election to GIT Commit Access Permission for GIT commit access shall be provided
<item>
<title>GEOS RFC 3 - Thread Safe CAPI </title>
- <link>http://libgeos.org/development/rfcs/rfc03/</link>
+ <link>https://libgeos.org/development/rfcs/rfc03/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/development/rfcs/rfc03/</guid>
+ <guid>https://libgeos.org/development/rfcs/rfc03/</guid>
<description>Summary The current CAPI in GEOS is not thread safe. The error handling and initialization/finalization process specifically can cause problems.
Definitions (As defined by Frank Warmerdam in http://trac.osgeo.org/gdal/wiki/rfc16_ogr_reentrancy)
Reentrant: A reentrant function can be called simultaneously by multiple threads provided that each invocation of the function references unique data.
@@ -53,10 +53,10 @@ Thread-safe: A thread-safe function can be called simultaneously by multiple thr
<item>
<title>GEOS RFC 4 - Code Formatting Style</title>
- <link>http://libgeos.org/development/rfcs/rfc04/</link>
+ <link>https://libgeos.org/development/rfcs/rfc04/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/development/rfcs/rfc04/</guid>
+ <guid>https://libgeos.org/development/rfcs/rfc04/</guid>
<description>This document proposes and describes desired code formatting style used across C/C++ source code in GEOS.
RFC 4 Code Formatting Style Author Mateusz Łoskot Contact mateusz at loskot.net Status Dropped (no agreement) Summary The document proposes and describes desired default code formatting style guidelines for GEOS programming in C and C++ languages.
The goal of this document is to initiate process to reach an agreement for the default code formatting style.</description>
@@ -64,10 +64,10 @@ The goal of this document is to initiate process to reach an agreement for the d
<item>
<title>GEOS RFC 5 - C++11 Compilation Mode</title>
- <link>http://libgeos.org/development/rfcs/rfc05/</link>
+ <link>https://libgeos.org/development/rfcs/rfc05/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/development/rfcs/rfc05/</guid>
+ <guid>https://libgeos.org/development/rfcs/rfc05/</guid>
<description>This document proposes and describes desired code formatting style used across C/C++ source code in GEOS.
RFC 5 C++11 Compilation Mode Author Mateusz Łoskot Contact mateusz at loskot.net Status Accepted (no agreement) Summary The document proposes to switch to C++11 compilation mode as default throughout the whole C++ source code of GEOS.
The goal of the document is to request and achieve agreement on using C++11 as the minimum required version of the C++ programming language standard.</description>
@@ -75,19 +75,19 @@ The goal of the document is to request and achieve agreement on using C++11 as t
<item>
<title>GEOS RFC 6 - Require explicit configure to use the C++ API</title>
- <link>http://libgeos.org/development/rfcs/rfc06/</link>
+ <link>https://libgeos.org/development/rfcs/rfc06/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/development/rfcs/rfc06/</guid>
+ <guid>https://libgeos.org/development/rfcs/rfc06/</guid>
<description>RFC 9 Require explicit configure to use the C++ API Author Regina Obe Contact lr at pcorp.us Status Not Passed Past discussions Trac ticket to deprecate another request to deprecate and osm2pgsql mess more examples about how apps linking directly to GEOS C++ causing problems for other applications Pointing out removing ability to use GEOS C++ reduces users freedoms</description>
</item>
<item>
<title>GEOS RFC 7 - Use CMake for Build System</title>
- <link>http://libgeos.org/development/rfcs/rfc07/</link>
+ <link>https://libgeos.org/development/rfcs/rfc07/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/development/rfcs/rfc07/</guid>
+ <guid>https://libgeos.org/development/rfcs/rfc07/</guid>
<description>RFC 7 Use CMake for build system Author Daniel Baston Contact dbaston at gmail.com Status Accepted, January 15, 2021 This document proposes to use CMake as the build system for GEOS and discontinue use of autotools and NMake.
Since version 3.5, we have officially supported building GEOS with CMake: https://trac.osgeo.org/geos/wiki/BuildingOnUnixWithCMake
GEOS is also required to build with autotools and NMake.</description>
@@ -95,10 +95,10 @@ GEOS is also required to build with autotools and NMake.</description>
<item>
<title>GEOS RFC 8 - Improve Coordinate Sequence API (WIP)</title>
- <link>http://libgeos.org/development/rfcs/rfc08/</link>
+ <link>https://libgeos.org/development/rfcs/rfc08/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/development/rfcs/rfc08/</guid>
+ <guid>https://libgeos.org/development/rfcs/rfc08/</guid>
<description>RFC 8 Improve Coordinate Sequence API Author Martin Davis Contact martin.davis at crunchydata.com Status In Discussion This document proposes to modify the Coordinate Sequence API to improve performance and adaptiveness.
These improvements are (likely to be) breaking changes to the C++ API.
These may require extensions to the C API to be externally available, but should not result in breaking the current C API.</description>
@@ -106,10 +106,10 @@ These may require extensions to the C API to be externally available, but should
<item>
<title>GEOS RFC 9 - Restore the C++ API (WIP)</title>
- <link>http://libgeos.org/development/rfcs/rfc09/</link>
+ <link>https://libgeos.org/development/rfcs/rfc09/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/development/rfcs/rfc09/</guid>
+ <guid>https://libgeos.org/development/rfcs/rfc09/</guid>
<description>RFC 9 Restore the C++ API Author Mateusz Łoskot Contact mateusz at loskot.net Status [https://lists.osgeo.org/pipermail/geos-devel/2019-May/008972.html Proposed] The GEOS library is a C++ library offering two kinds of public API: C++ API and C API.
The GEOS library started as a C++ library. The C API was introduced in version 2.2.
The GEOS library has never promised any stability of the C++ API and this fact has always been documented and clearly stated:</description>
diff --git a/development/rfcs/rfc01/index.html b/development/rfcs/rfc01/index.html
index a472bb8a3..0b85a1f70 100644
--- a/development/rfcs/rfc01/index.html
+++ b/development/rfcs/rfc01/index.html
@@ -48,7 +48,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
@@ -638,7 +638,7 @@
</tr>
</tbody>
</table>
-<div class="gdoc-page__anchorwrap"><h2 id="summary">Summary<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc01/#summary" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Summary" href="#summary"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="summary">Summary<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc01/#summary" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Summary" href="#summary"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>This document describes how the GEOS Project Steering Committee (PSC) determines membership, and makes decisions on all aspects of the GEOS project - both technical and non-technical.</p>
<p>Examples of PSC management responsibilities:</p>
<ul>
@@ -652,7 +652,7 @@
<li>creation and oversight of specialized sub-committees (e.g. project infrastructure, training)</li>
</ul>
<p>In brief the project team votes on proposals on <a href="http://lists.osgeo.org/mailman/listinfo/geos-devel">geos-devel</a>. Proposals are available for review for at least two days, and a single veto is sufficient delay progress though ultimately a majority of members can pass a proposal.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="detailed-process">Detailed Process<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc01/#detailed-process" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Detailed Process" href="#detailed-process"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="detailed-process">Detailed Process<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc01/#detailed-process" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Detailed Process" href="#detailed-process"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<ol>
<li>Proposals are announced on the <a href="http://lists.osgeo.org/mailman/listinfo/geos-devel">geos-devel</a> mailing list for discussion and voting, by any interested party, not just committee members.</li>
<li>Proposals need to be available for review for at least two business days before a final decision can be made.</li>
@@ -668,7 +668,7 @@
<li>Addition and removal of members from the committee, as well as selection of a Chair should be handled as a proposal to the committee.</li>
<li>The Chair adjudicates in cases of disputes about voting.</li>
</ol>
-<div class="gdoc-page__anchorwrap"><h2 id="when-is-vote-required">When is Vote Required?<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc01/#when-is-vote-required" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor When is Vote Required?" href="#when-is-vote-required"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="when-is-vote-required">When is Vote Required?<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc01/#when-is-vote-required" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor When is Vote Required?" href="#when-is-vote-required"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<ul>
<li>Any change to committee membership (new members, removing inactive members)</li>
<li>Changes to project infrastructure (e.g. tool, location or substantive configuration)</li>
@@ -680,27 +680,27 @@
<li>Anything dealing with relationships with external entities such as OSGeo</li>
<li>Anything that might be controversial.</li>
</ul>
-<div class="gdoc-page__anchorwrap"><h2 id="observations">Observations<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc01/#observations" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Observations" href="#observations"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="observations">Observations<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc01/#observations" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Observations" href="#observations"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<ul>
<li>The Chair is the ultimate adjudicator if things break down.</li>
<li>The absolute majority rule can be used to override an obstructionist veto, but it is intended that in normal circumstances voters need to be convinced to withdraw their veto. We are trying to reach consensus.</li>
<li>It is anticipated that separate “committees” will exist to manage conferences, documentation and web sites. That said, it is expected that the PSC will be the entity largely responsible for creating any such committees.</li>
</ul>
-<div class="gdoc-page__anchorwrap"><h2 id="committee-membership">Committee Membership<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc01/#committee-membership" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Committee Membership" href="#committee-membership"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="committee-membership">Committee Membership<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc01/#committee-membership" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Committee Membership" href="#committee-membership"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>The PSC is made up of individuals consisting of technical contributors (e.g. developers) and prominent members of the GEOS user community.</p>
-<div class="gdoc-page__anchorwrap"><h3 id="adding-members">Adding Members<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc01/#adding-members" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Adding Members" href="#adding-members"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h3 id="adding-members">Adding Members<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc01/#adding-members" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Adding Members" href="#adding-members"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>Any member of the <a href="http://lists.osgeo.org/mailman/listinfo/geos-devel">geos-devel</a> mailing list may nominate someone for committee membership at any time. Only existing PSC committee members may vote on new members. Nominees must receive a majority vote from existing members to be added to the PSC.</p>
-<div class="gdoc-page__anchorwrap"><h3 id="stepping-down">Stepping Down<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc01/#stepping-down" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Stepping Down" href="#stepping-down"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h3 id="stepping-down">Stepping Down<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc01/#stepping-down" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Stepping Down" href="#stepping-down"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>If for any reason a PSC member is not able to fully participate then they certainly are free to step down. If a member is not active (e.g. no voting, no IRC or email participation) for a period of two months then the committee reserves the right to seek nominations to fill that position.</p>
<p>Should that person become active again (hey, it happens) then they would certainly be welcome, but would require a nomination.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="membership-responsibilities">Membership Responsibilities<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc01/#membership-responsibilities" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Membership Responsibilities" href="#membership-responsibilities"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
-<div class="gdoc-page__anchorwrap"><h3 id="guiding-development">Guiding Development<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc01/#guiding-development" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Guiding Development" href="#guiding-development"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h2 id="membership-responsibilities">Membership Responsibilities<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc01/#membership-responsibilities" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Membership Responsibilities" href="#membership-responsibilities"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h3 id="guiding-development">Guiding Development<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc01/#guiding-development" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Guiding Development" href="#guiding-development"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>Members should take an active role guiding the development of new features they feel passionate about. Once a change request has been accepted and given a green light to proceed does not mean the members are free of their obligation. PSC members voting “+1” for a change request are expected to stay engaged and ensure the change is implemented and documented in a way that is most beneficial to users. Note that this applies not only to change requests that affect code, but also those that affect the web site, technical infrastructure, policies and standards.</p>
-<div class="gdoc-page__anchorwrap"><h3 id="irc-meeting-attendance">IRC Meeting Attendance<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc01/#irc-meeting-attendance" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor IRC Meeting Attendance" href="#irc-meeting-attendance"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h3 id="irc-meeting-attendance">IRC Meeting Attendance<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc01/#irc-meeting-attendance" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor IRC Meeting Attendance" href="#irc-meeting-attendance"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>PSC members are expected to participate in pre-scheduled IRC development meetings. If known in advance that a member cannot attend a meeting, the member should let the meeting organizer know via e-mail.</p>
-<div class="gdoc-page__anchorwrap"><h3 id="mailing-list-participation">Mailing List Participation<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc01/#mailing-list-participation" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Mailing List Participation" href="#mailing-list-participation"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h3 id="mailing-list-participation">Mailing List Participation<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc01/#mailing-list-participation" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Mailing List Participation" href="#mailing-list-participation"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>PSC members are expected to be active on both the <a href="http://lists.osgeo.org/mailman/listinfo/geos-devel">geos-devel</a> mailing lists, subject to open source mailing list etiquette. Non-developer members of the PSC are not expected to respond to coding level questions on the developer mailing list, however they are expected to provide their thoughts and opinions on user level requirements and compatibility issues when RFC discussions take place.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="bootstrapping">Bootstrapping<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc01/#bootstrapping" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Bootstrapping" href="#bootstrapping"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="bootstrapping">Bootstrapping<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc01/#bootstrapping" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Bootstrapping" href="#bootstrapping"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>Prior to anointing itself the PSW must distribute this RFC to the GEOS community via <a href="http://lists.osgeo.org/mailman/listinfo/geos-devel">geos-devel</a> for comment. Any and all substantive comments must be discussed (and hopefully, but not necessarily, addressed via <a href="http://lists.osgeo.org/mailman/listinfo/geos-devel">geos-devel</a>.</p>
<p>Initial members are:</p>
<ul>
diff --git a/development/rfcs/rfc02/index.html b/development/rfcs/rfc02/index.html
index a80cef78a..8b8b65777 100644
--- a/development/rfcs/rfc02/index.html
+++ b/development/rfcs/rfc02/index.html
@@ -48,7 +48,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
@@ -638,9 +638,9 @@
</tr>
</tbody>
</table>
-<div class="gdoc-page__anchorwrap"><h2 id="summary">Summary<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc02/#summary" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Summary" href="#summary"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="summary">Summary<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc02/#summary" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Summary" href="#summary"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>This document describes the technical and legal responsibilities of [wiki:PSC GEOS committers].</p>
-<div class="gdoc-page__anchorwrap"><h2 id="election-to-git-commit-access">Election to GIT Commit Access<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc02/#election-to-git-commit-access" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Election to GIT Commit Access" href="#election-to-git-commit-access"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="election-to-git-commit-access">Election to GIT Commit Access<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc02/#election-to-git-commit-access" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Election to GIT Commit Access" href="#election-to-git-commit-access"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>Permission for GIT commit access shall be provided to new developers only if accepted by the [wiki:PSC GEOS Project Steering Committee]. A proposal should be written to the PSC for new committers and voted on normally. It is not necessary to write an <a href="http://en.wikipedia.org/wiki/Request_for_Comments">RFC</a> document for these votes, a proposal to <a href="http://lists.osgeo.org/mailman/listinfo/geos-devel">geos-devel</a> is sufficient.</p>
<p>Every developer position in the project is represented by an individual, and commit access will be granted to individuals only, group accounts are not permitted.</p>
<p>Removal of GIT commit access should be handled by the same process.</p>
@@ -648,7 +648,7 @@
<p>The new committer should also be prepared to support any new feature or changes that he/she commits to the GEOS source tree in future releases, or to find someone to which to delegate responsibility for them if he/she stops being available to support the portions of code that he/she is responsible for.</p>
<p>All committers should also be a member of the <a href="http://lists.osgeo.org/mailman/listinfo/geos-devel">geos-devel</a> mailing list so they can stay informed on policies, technical developments and release preparation.</p>
<p><strong>Before being approved, new committers must send an email to the <a href="http://lists.osgeo.org/mailman/listinfo/geos-devel">geos-devel</a> mailing list confirming that they have read, understand, and agree to follow the terms of this document.</strong></p>
-<div class="gdoc-page__anchorwrap"><h2 id="committer-tracking">Committer Tracking<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc02/#committer-tracking" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Committer Tracking" href="#committer-tracking"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="committer-tracking">Committer Tracking<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc02/#committer-tracking" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Committer Tracking" href="#committer-tracking"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>A list of all project committers will be kept in the GEOS source tree in <code>AUTHORS</code> , listing for each committer:</p>
<ul>
<li>Userid: the id that will appear in the SVN logs for this person.</li>
@@ -656,9 +656,9 @@
<li>Email address: A current email address at which the committer can be reached. It may be altered in normal ways to make it harder to auto-harvest.</li>
<li>A brief indication of areas of responsibility.</li>
</ul>
-<div class="gdoc-page__anchorwrap"><h2 id="git-administrator">GIT Administrator<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc02/#git-administrator" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor GIT Administrator" href="#git-administrator"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="git-administrator">GIT Administrator<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc02/#git-administrator" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor GIT Administrator" href="#git-administrator"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>One member of the Project Steering Committee will be designated the <a href="https://git.osgeo.org/gitea/geos/">GEOS GIT</a> repository Administrator. That person will be responsible for giving GIT commit access to folks, updating the committers list, and other GIT related management.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="legal-responsibilities">Legal Responsibilities<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc02/#legal-responsibilities" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Legal Responsibilities" href="#legal-responsibilities"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="legal-responsibilities">Legal Responsibilities<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc02/#legal-responsibilities" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Legal Responsibilities" href="#legal-responsibilities"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>Committers are the front line gatekeepers to keep the code base clear of improperly contributed code. It is important to the GEOS users, developers and the OSGeo foundation to avoid contributing any code to the project without it being clearly licensed under the project license.</p>
<p>Every GEOS code contribution should meet the following tests:</p>
<ol>
@@ -694,7 +694,7 @@
<p>If there is uncertainty about whether a change is proper to contribute to the code base, please seek more information from the project steering committee, or the foundation legal counsel.</p>
</li>
</ul>
-<div class="gdoc-page__anchorwrap"><h2 id="technical-responsibilities">Technical Responsibilities<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc02/#technical-responsibilities" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Technical Responsibilities" href="#technical-responsibilities"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="technical-responsibilities">Technical Responsibilities<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc02/#technical-responsibilities" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Technical Responsibilities" href="#technical-responsibilities"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>The following are considered good SVN commit practices for the GEOS project.</p>
<ul>
<li>
diff --git a/development/rfcs/rfc03/index.html b/development/rfcs/rfc03/index.html
index 1f668470d..07271e1ff 100644
--- a/development/rfcs/rfc03/index.html
+++ b/development/rfcs/rfc03/index.html
@@ -48,7 +48,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
@@ -611,18 +611,18 @@
-<div class="gdoc-page__anchorwrap"><h2 id="summary">Summary<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc03/#summary" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Summary" href="#summary"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="summary">Summary<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc03/#summary" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Summary" href="#summary"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>The current CAPI in GEOS is not thread safe. The error handling and initialization/finalization process specifically can cause problems.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="definitions">Definitions<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc03/#definitions" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Definitions" href="#definitions"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="definitions">Definitions<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc03/#definitions" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Definitions" href="#definitions"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>(As defined by Frank Warmerdam in <a href="http://trac.osgeo.org/gdal/wiki/rfc16_ogr_reentrancy">http://trac.osgeo.org/gdal/wiki/rfc16_ogr_reentrancy</a>)</p>
<p><strong>Reentrant:</strong> A reentrant function can be called simultaneously by multiple threads provided that each invocation of the function references unique data.</p>
<p><strong>Thread-safe:</strong> A thread-safe function can be called simultaneously by multiple threads when each invocation references shared data. All access to the shared data is serialized.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="objective">Objective<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc03/#objective" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Objective" href="#objective"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="objective">Objective<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc03/#objective" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Objective" href="#objective"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>Allow the GEOS CAPI to be thread safe.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="implementation">Implementation<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc03/#implementation" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Implementation" href="#implementation"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="implementation">Implementation<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc03/#implementation" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Implementation" href="#implementation"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>In order to implement the thread safe API, the current API will be copied and all static variables will be placed into a ‘handle.’ This handle will be initialized on the initGeos call. Once initialized it will be passed to all subsequent GEOS functions, allowing each thread to have it’s own copy of the data. This will not affect the current API as it will be provided in addition to the old API. In order to prevent maintenance issues the OLD API will be changed to call the NEW API with a global handle. The handle (GEOSContextHandle_t) will be an opaque type to allow exentensions without recompilation being required. Function names in the new API will be updated with an _r, as is the familiar C standard for reentrant/thread safe versions. Current GEOS functions that do not make reference to the context handle will not be changed.</p>
<p>The intent will be to altogether replace the existing functions with the _r functions in a future release, making the thread safe versions the only supported functions.</p>
-<div class="gdoc-page__anchorwrap"><h3 id="handle-definition">Handle Definition<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc03/#handle-definition" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Handle Definition" href="#handle-definition"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h3 id="handle-definition">Handle Definition<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc03/#handle-definition" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Handle Definition" href="#handle-definition"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>Here are the internals of the handle and how the application visual handle will look.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-c" data-lang="c"><span class="k">typedef</span> <span class="k">struct</span> <span class="n">GEOSContextHandleInternal</span>
<span class="p">{</span>
@@ -636,7 +636,7 @@
<span class="k">typedef</span> <span class="k">struct</span> <span class="n">GEOSContextHandle_HS</span> <span class="o">*</span><span class="n">GEOSContextHandle_t</span><span class="p">;</span>
</code></pre></div><p>The typedef for GEOSContextHandle_t will make it easier for the compiler to help detect an incorrect pointer being passed to the functions.</p>
-<div class="gdoc-page__anchorwrap"><h3 id="example-prototypes">Example Prototypes<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc03/#example-prototypes" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Example Prototypes" href="#example-prototypes"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h3 id="example-prototypes">Example Prototypes<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc03/#example-prototypes" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Example Prototypes" href="#example-prototypes"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>Here are examples of what some of the new function prototypes would be.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-c" data-lang="c"><span class="n">GEOSContextHandle_t</span> <span class="n">GEOS_DLL</span> <span class="nf">initGEOS_r</span><span class="p">(</span> <span class="n">GEOSMessageHandler</span> <span class="n">notice_function</span><span class="p">,</span>
<span class="n">GEOSMessageHandler</span> <span class="n">error_function</span><span class="p">);</span>
@@ -657,9 +657,9 @@
<span class="k">extern</span> <span class="n">GEOSGeometry</span> <span class="n">GEOS_DLL</span> <span class="o">*</span><span class="nf">GEOSGeom_createPoint</span><span class="p">(</span><span class="n">GEOSCoordSequence</span><span class="o">*</span> <span class="n">s</span><span class="p">);</span>
<span class="k">extern</span> <span class="n">GEOSGeometry</span> <span class="n">GEOS_DLL</span> <span class="o">*</span><span class="nf">GEOSGeom_createLinearRing</span><span class="p">(</span><span class="n">GEOSCoordSequence</span><span class="o">*</span> <span class="n">s</span><span class="p">);</span>
<span class="k">extern</span> <span class="n">GEOSGeometry</span> <span class="n">GEOS_DLL</span> <span class="o">*</span><span class="nf">GEOSGeom_createLineString</span><span class="p">(</span><span class="n">GEOSCoordSequence</span><span class="o">*</span> <span class="n">s</span><span class="p">);</span>
-</code></pre></div><div class="gdoc-page__anchorwrap"><h2 id="limitations">Limitations<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc03/#limitations" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Limitations" href="#limitations"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+</code></pre></div><div class="gdoc-page__anchorwrap"><h2 id="limitations">Limitations<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc03/#limitations" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Limitations" href="#limitations"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>This change will focus on making a thread safe version of the API. Other extensions to the context handle have been suggested, e.g. Access to other geometry factories, overriding memory allocators. These extensions are beyond the current scope of this design, but this design will be implemented to allow such extensions in the future.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="testing">Testing<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc03/#testing" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Testing" href="#testing"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="testing">Testing<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc03/#testing" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Testing" href="#testing"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>An example test executable will be provided that shows the current problem. It is copied from the existing CAPI test tool. Once the thread safe API is created the test tool will be updated to the new interface which will address the former problems.</p>
diff --git a/development/rfcs/rfc04/index.html b/development/rfcs/rfc04/index.html
index 778d70614..b1e6ceb12 100644
--- a/development/rfcs/rfc04/index.html
+++ b/development/rfcs/rfc04/index.html
@@ -48,7 +48,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
@@ -638,15 +638,15 @@
</tr>
</tbody>
</table>
-<div class="gdoc-page__anchorwrap"><h2 id="summary">Summary<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc04/#summary" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Summary" href="#summary"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="summary">Summary<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc04/#summary" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Summary" href="#summary"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>The document proposes and describes desired default code formatting style guidelines for GEOS programming in C and C++ languages.</p>
<p>The goal of this document is to initiate process to reach an agreement for the default code formatting style.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="motivation">Motivation<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc04/#motivation" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Motivation" href="#motivation"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="motivation">Motivation<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc04/#motivation" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Motivation" href="#motivation"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>There is a need to decide on format of GEOS source code and apply such globally consistent format to GEOS C/C++ codebase.</p>
<p>A uniform, codebase-wide formatting style makes reading and comprehending existing code easier, writing code focused on important aspects of new developments and more pleasant, removes burden during a patch or pull request code reviews and prevents <a href="http://wiki.c2.com/?WhereDoTheBracesGo">bikeshedding religious arguments</a>. Even in small projects, contributing developers discover the problems of working without an agreed upon code format.</p>
<p>The utility of such guidelines has been proven by many open source software projects.</p>
<p>The scope of the proposal is specifically limited to formatting style guidelines. It is not an intention to develop a general coding guide covering other aspects of writing software like naming, etc.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="proposal">Proposal<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc04/#proposal" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Proposal" href="#proposal"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="proposal">Proposal<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc04/#proposal" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Proposal" href="#proposal"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>It is important to make effortless for developers to produce properly formatted code.</p>
<p>The proposal suggests to use <a href="https://clang.llvm.org/docs/ClangFormat.html">clang-format</a> version 3.8 or higher to define C++ code formatting rules for GEOS code.</p>
<p>The <code>clang-format</code> is a tool to automatically format C/C++ code, so that developers don’t need to worry about style issues.
@@ -656,7 +656,7 @@ This guarantees correct output is produced and offers unique features (eg. wrapp
<p>The <code>clang-format</code> is straightforward to run and can support development workflow as standalone tool or as one of many editor integrations or other bespoke utilities (eg. <code>git cl format</code> [Chromium]).</p>
<p>No automation of code reformatting is proposed. It would be treating the symptomps, no cause: developers not following the code formatting standard.</p>
<p>Although no means to enforce the default formatting style are proposed, currently used CI services (eg. Travis CI) may be employed as a post-commit safety valve - a clang-format lint failure as a compile break (eg. <a href="https://github.com/mongodb/mongo/blob/master/buildscripts/clang_format.py">clang_format.py</a> build script used by MongoDB). Alternatively, a gatekeeper may be installed in SVN/Git, rejecting commits with code not conforming to the code formatting style.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="code-formatting-rules">Code Formatting Rules<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc04/#code-formatting-rules" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Code Formatting Rules" href="#code-formatting-rules"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="code-formatting-rules">Code Formatting Rules<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc04/#code-formatting-rules" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Code Formatting Rules" href="#code-formatting-rules"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>What code formatting rules to use?</p>
<blockquote>
<p>“A mature engineers know that a standard is more important than which standard.” ~ MongoDB</p>
@@ -668,7 +668,7 @@ This guarantees correct output is produced and offers unique features (eg. wrapp
<li>make GEOS code unified with the wide spectrum of well-established C/C++ projects</li>
<li>long arguments and religious wars prevention.</li>
</ul>
-<div class="gdoc-page__anchorwrap"><h3 id="clang-format"><code>.clang-format</code><a data-clipboard-text="http://libgeos.org/development/rfcs/rfc04/#clang-format" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor <code>.clang-format</code>" href="#clang-format"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h3 id="clang-format"><code>.clang-format</code><a data-clipboard-text="https://libgeos.org/development/rfcs/rfc04/#clang-format" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor <code>.clang-format</code>" href="#clang-format"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>Below is complete set of settings suggested, sufficient to maintain the clean code formatting style.</p>
<p><strong>NOTE:</strong> It remains open for refinements, use different <code>BasedOnStyle</code> as base style, etc.</p>
<pre tabindex="0"><code>---
@@ -697,20 +697,20 @@ BreakBeforeBraces: Allman
BreakBeforeTernaryOperators: true
</code></pre><p>For brevity, the settings above are limited to the base style and points of customizations.</p>
<p>For actual implementation, full version of <code>.clang-format</code> should be generated using <code>clang-format -dump-config</code> option and the <code>BasedOnStyle: Mozilla</code> setting commented with <code>#</code>.</p>
-<div class="gdoc-page__anchorwrap"><h3 id="editorconfig"><code>.editorconfig</code><a data-clipboard-text="http://libgeos.org/development/rfcs/rfc04/#editorconfig" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor <code>.editorconfig</code>" href="#editorconfig"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h3 id="editorconfig"><code>.editorconfig</code><a data-clipboard-text="https://libgeos.org/development/rfcs/rfc04/#editorconfig" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor <code>.editorconfig</code>" href="#editorconfig"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>[http://editorconfig.org/ EditorConfig] is currently in use and <code>.editorconfig</code> file is provided to automatically tell popular code editors about the basic style settings like indentation, whitespaces and end-of-line markers for distinguished types of plain text files.</p>
<p>The <code>.editorconfig</code> file will have to be updated to match the chosen <code>.clang-format</code> settings.</p>
-<div class="gdoc-page__anchorwrap"><h3 id="eol">EOL<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc04/#eol" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor EOL" href="#eol"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h3 id="eol">EOL<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc04/#eol" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor EOL" href="#eol"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p><code>clang-format</code> does not enforce line endings.</p>
<p>The EOL marker is considered to be [http://lists.llvm.org/pipermail/cfe-commits/Week-of-Mon-20130930/090200.html a part of a file encoding decision] and not part of any coding style.</p>
<p>The EOL marker can be enforced as project-wide setting controlled with <code>.gitattributes</code> and <code>.editorconfig</code>.</p>
<p>However, it shall still be left as configurable setting in developer’s environment of choice (eg. <code>git config</code>) independently from the project-wide setting.</p>
-<div class="gdoc-page__anchorwrap"><h3 id="big-reformat">Big Reformat<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc04/#big-reformat" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Big Reformat" href="#big-reformat"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h3 id="big-reformat">Big Reformat<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc04/#big-reformat" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Big Reformat" href="#big-reformat"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>What to do about the existing code?</p>
<p>The proposal recommends to just do one big reformat of the codebase.</p>
<p>While it may seem causing clutter in the repository log (eg. <code>svn blame</code>), if it occurs infrequently (eg. yearly) and is applied to the entire codebase at that time, it should not be very disruptive to the source code history. One way to cope with skewed history is to use <code>git blame -w</code> which ignores whitespace when comparing commits.</p>
<p>Partial application of the code formatting rules would create more work without delivering the full benefit [MongoDB] leading to codebase with different styles mixed.</p>
-<div class="gdoc-page__anchorwrap"><h4 id="implementation">Implementation<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc04/#implementation" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Implementation" href="#implementation"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h4></div>
+<div class="gdoc-page__anchorwrap"><h4 id="implementation">Implementation<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc04/#implementation" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Implementation" href="#implementation"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h4></div>
<p>Branches to run the big reformat in are:</p>
<ul>
<li><code>trunk</code></li>
@@ -718,7 +718,7 @@ BreakBeforeTernaryOperators: true
<li><code>branches/3.5</code></li>
<li><code>branches/3.4</code></li>
</ul>
-<div class="gdoc-page__anchorwrap"><h2 id="after-big-reformat">After Big Reformat<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc04/#after-big-reformat" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor After Big Reformat" href="#after-big-reformat"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="after-big-reformat">After Big Reformat<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc04/#after-big-reformat" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor After Big Reformat" href="#after-big-reformat"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>How to work against the natural entropy in a codebase:</p>
<ul>
<li>It is highly recommended to use <code>clang-format</code> integration while writing a code.</li>
@@ -732,9 +732,9 @@ BreakBeforeTernaryOperators: true
<blockquote>
<p>“After all, every moment of time wasted on code formatting or discussion thereof is eliminated.” ~ MongoDB</p>
</blockquote>
-<div class="gdoc-page__anchorwrap"><h4 id="implementation-1">Implementation<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc04/#implementation-1" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Implementation" href="#implementation-1"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h4></div>
+<div class="gdoc-page__anchorwrap"><h4 id="implementation-1">Implementation<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc04/#implementation-1" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Implementation" href="#implementation-1"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h4></div>
<p>Set up Travis CI “style safety valve” build dedicated to run clang-format lint based on the approach used in <code>clang_format.py</code> script by MongoDB.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="miscellaneous">Miscellaneous<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc04/#miscellaneous" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Miscellaneous" href="#miscellaneous"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="miscellaneous">Miscellaneous<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc04/#miscellaneous" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Miscellaneous" href="#miscellaneous"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>Those who build GEOS with GCC 6+ may appreciate consistent code format style as it will help to avoid some dozens of the <a href="https://developers.redhat.com/blog/2016/02/26/gcc-6-wmisleading-indentation-vs-goto-fail/">new compiler warnings</a>:</p>
<pre tabindex="0"><code>src/geom/Polygon.cpp: In member function ‘virtual int geos::geom::Polygon::getCoordinateDimension() const’:
src/geom/Polygon.cpp:154:5: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
@@ -743,7 +743,7 @@ src/geom/Polygon.cpp:154:5: warning: this ‘if’ clause does not guard... [-Wm
src/geom/Polygon.cpp:157:2: note: ...this statement, but the latter is misleadingly indented as if it is guarded by the ‘if’
size_t nholes=holes->size();
^~~~~~
-</code></pre><div class="gdoc-page__anchorwrap"><h2 id="references">References<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc04/#references" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor References" href="#references"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+</code></pre><div class="gdoc-page__anchorwrap"><h2 id="references">References<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc04/#references" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor References" href="#references"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<ul>
<li>MongoDB Succeeding With ClangFormat:
<ul>
diff --git a/development/rfcs/rfc05/index.html b/development/rfcs/rfc05/index.html
index ce54cf816..e71efe7f6 100644
--- a/development/rfcs/rfc05/index.html
+++ b/development/rfcs/rfc05/index.html
@@ -48,7 +48,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
@@ -638,10 +638,10 @@
</tr>
</tbody>
</table>
-<div class="gdoc-page__anchorwrap"><h2 id="summary">Summary<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc05/#summary" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Summary" href="#summary"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="summary">Summary<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc05/#summary" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Summary" href="#summary"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>The document proposes to switch to <a href="https://en.wikipedia.org/wiki/C%2B%2B11">C++11</a> compilation mode as default throughout the whole C++ source code of GEOS.</p>
<p>The goal of the document is to request and achieve agreement on using C++11 as the minimum required version of the C++ programming language standard.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="motivation">Motivation<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc05/#motivation" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Motivation" href="#motivation"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="motivation">Motivation<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc05/#motivation" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Motivation" href="#motivation"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>The C++11 is the first major update of the C++ standard since 1998. (C++03 was a bug fix release.)</p>
<p>The C++11 features aim to promote writing clean, compact, type-safe and fast code. It also delivers better feature-wise compatibility with C language (C99).</p>
<p>The Wikipedia article at <a href="https://en.wikipedia.org/wiki/C++11">https://en.wikipedia.org/wiki/C++11</a> does a great job describing all changes in C++11 extensively.</p>
@@ -649,9 +649,9 @@
<p>The new compilers provide better diagnostics.</p>
<p>Enabling C++11 compilation mode will improve the programming environment making it much friendlier than C++98.</p>
<p>A social factor: since (many) C++ programmers no longer enjoy C++98, allowing C++11 mode may increase potential for new contributions.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="compilers-landscape">Compilers Landscape<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc05/#compilers-landscape" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Compilers Landscape" href="#compilers-landscape"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="compilers-landscape">Compilers Landscape<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc05/#compilers-landscape" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Compilers Landscape" href="#compilers-landscape"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>Summary of compilers supported by GEOS with their minimal versions required to compile source code based on [http://en.cppreference.com/w/cpp/compiler_support C++11 features].</p>
-<div class="gdoc-page__anchorwrap"><h3 id="c11">C++11<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc05/#c11" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor C++11" href="#c11"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h3 id="c11">C++11<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc05/#c11" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor C++11" href="#c11"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<table>
<thead>
<tr>
@@ -682,7 +682,7 @@
</tr>
</tbody>
</table>
-<div class="gdoc-page__anchorwrap"><h3 id="c14">C++14<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc05/#c14" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor C++14" href="#c14"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h3 id="c14">C++14<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc05/#c14" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor C++14" href="#c14"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>The C++14 compilers are listed for comparison only:</p>
<table>
<thead>
@@ -706,7 +706,7 @@
</tr>
</tbody>
</table>
-<div class="gdoc-page__anchorwrap"><h2 id="plan">Plan<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc05/#plan" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Plan" href="#plan"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="plan">Plan<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc05/#plan" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Plan" href="#plan"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>This proposal only requests agreement for the C++11 compilation mode switch in the current <code>trunk</code> branch only.</p>
<p>If accepted, currently available build configurations (Autotools, CMake, NMake) will be updated to switch the compilation mode to C++11.</p>
<p>This proposal does not suggest any detailed roadmap of big refactoring of the GEOS C++ codebase.</p>
@@ -716,21 +716,21 @@
<p>However, if the proposal is accepted, any new C++ code written for GEOS can be C++11-compliant.</p>
<p>Prior acceptance of this proposal is necessary in order to start any source code refactoring using C++11 features.</p>
<p>Once accepted, first step will be to update the build configurations to require C++11-compliant compiler.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="issues">Issues<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc05/#issues" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Issues" href="#issues"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="issues">Issues<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc05/#issues" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Issues" href="#issues"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>This section outlines issues potentially caused by upgrade to C++11 language.</p>
<ul>
<li>C++11 destructors, by default, have now the new exception specification of <code>nothrow(true)</code>. Destructors of GEOS classes should be reviewed and any that are allowed/expected to throw exceptions must be marked with <code>nothrow(false)</code>. Otherwise, any user of the existing GEOS codebase would find the program terminating whenever GEOS destructor throws an exception. Such review would be beneficial anyway.</li>
</ul>
-<div class="gdoc-page__anchorwrap"><h2 id="release">Release<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc05/#release" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Release" href="#release"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="release">Release<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc05/#release" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Release" href="#release"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>First release of GEOS with C++11 compiler requirement could be 3.7.0 or, perhaps, 4.0.0.</p>
-<div class="gdoc-page__anchorwrap"><h3 id="c14-1">C++14<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc05/#c14-1" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor C++14" href="#c14-1"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h3 id="c14-1">C++14<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc05/#c14-1" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor C++14" href="#c14-1"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>This section clarifies status of C++14 support in GEOS.</p>
<ul>
<li>Once C++11 is adopted as default compilation mode, GEOS developers and maintainers must ensure it also successfully compiles in C++14 and C++17 modes.</li>
<li>Are contributors allowed to add <code>ifdef</code>’s for C++14 and C++17? No.</li>
<li>Is there a plan to upgrade to C++14 or C++17 to allow use of the C++ latest features? No, there is no plan. It is, however, recognized, such motion may be put to the vote around 2020.</li>
</ul>
-<div class="gdoc-page__anchorwrap"><h2 id="references">References<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc05/#references" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor References" href="#references"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="references">References<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc05/#references" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor References" href="#references"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<ul>
<li><a href="http://en.cppreference.com/w/cpp/compiler_support">C++ compiler support</a></li>
</ul>
diff --git a/development/rfcs/rfc06/index.html b/development/rfcs/rfc06/index.html
index 102037099..cc80330d8 100644
--- a/development/rfcs/rfc06/index.html
+++ b/development/rfcs/rfc06/index.html
@@ -48,7 +48,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
@@ -637,12 +637,12 @@
</tr>
</tbody>
</table>
-<div class="gdoc-page__anchorwrap"><h2 id="past-discussions">Past discussions<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc06/#past-discussions" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Past discussions" href="#past-discussions"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="past-discussions">Past discussions<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc06/#past-discussions" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Past discussions" href="#past-discussions"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p><a href="https://trac.osgeo.org/geos/ticket/553">Trac ticket to deprecate</a>
<a href="https://lists.osgeo.org/pipermail/geos-devel/2017-January/007652.html">another request to deprecate and osm2pgsql mess</a>
<a href="https://lists.osgeo.org/pipermail/geos-devel/2012-June/005861.html">more examples about how apps linking directly to GEOS C++ causing problems for other applications</a>
<a href="https://lists.osgeo.org/pipermail/geos-devel/2017-January/007653.html">Pointing out removing ability to use GEOS C++ reduces users freedoms</a></p>
-<div class="gdoc-page__anchorwrap"><h2 id="summary">Summary<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc06/#summary" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Summary" href="#summary"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="summary">Summary<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc06/#summary" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Summary" href="#summary"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>This document proposes to change the <code>./configure</code> and CMake to by default only allow use of the C-API.</p>
<p>The C++ API headers and library will only be installed if explicitly asked for
as detailed in <a href="https://lists.osgeo.org/pipermail/geos-devel/2017-October/008054.html">https://lists.osgeo.org/pipermail/geos-devel/2017-October/008054.html</a></p>
diff --git a/development/rfcs/rfc07/index.html b/development/rfcs/rfc07/index.html
index 91e4c7f26..9ff76770a 100644
--- a/development/rfcs/rfc07/index.html
+++ b/development/rfcs/rfc07/index.html
@@ -48,7 +48,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
diff --git a/development/rfcs/rfc08/index.html b/development/rfcs/rfc08/index.html
index 45f79bf8b..0815b1700 100644
--- a/development/rfcs/rfc08/index.html
+++ b/development/rfcs/rfc08/index.html
@@ -48,7 +48,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
@@ -640,7 +640,7 @@
<p>This document proposes to modify the Coordinate Sequence API to improve performance and adaptiveness.</p>
<p>These improvements are (likely to be) breaking changes to the C++ API.</p>
<p>These may require extensions to the C API to be externally available, but should not result in breaking the current C API.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="background">Background<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc08/#background" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Background" href="#background"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="background">Background<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc08/#background" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Background" href="#background"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>The Coordinate Sequence API as it stands imposes a large cost on clients.</p>
<ul>
<li>It requires copying coordinate list structures one or more times</li>
@@ -658,7 +658,7 @@
<li>Shapely - there are several allocations required to marshall from NumPY to GEOS</li>
<li>PostGIS - hopefully this will allow calling GEOS without copying out of LWGEOM structure</li>
</ul>
-<div class="gdoc-page__anchorwrap"><h2 id="goals">Goals<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc08/#goals" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Goals" href="#goals"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="goals">Goals<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc08/#goals" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Goals" href="#goals"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<ul>
<li>
<p>Allow using external coordinate list structures with no copying (except as needed by GEOS algorithms, e.g. removing repeated points)</p>
@@ -679,7 +679,7 @@
<p>Optimized storage of Point and Multi Point data</p>
</li>
</ul>
-<div class="gdoc-page__anchorwrap"><h2 id="ideas">Ideas<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc08/#ideas" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Ideas" href="#ideas"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="ideas">Ideas<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc08/#ideas" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Ideas" href="#ideas"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p><strong>Memory-based Coordinate Sequence implementation</strong></p>
<ul>
<li>Class which contains pointer to memory block of coordinates, length, dimension</li>
@@ -701,7 +701,7 @@
<ul>
<li>C++ <a href="https://www.modernescpp.com/index.php/c-17-avoid-copying-with-std-string-view">string_view</a></li>
</ul>
-<div class="gdoc-page__anchorwrap"><h2 id="tasks">Tasks<a data-clipboard-text="http://libgeos.org/development/rfcs/rfc08/#tasks" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Tasks" href="#tasks"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="tasks">Tasks<a data-clipboard-text="https://libgeos.org/development/rfcs/rfc08/#tasks" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Tasks" href="#tasks"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<ol>
<li>Remove extraneous operations from CoordinateSequence (e.g. removeRepeatedPoints)</li>
<li>Create a MemoryBasedCoordinateSequence (better name?) which allows access to external blocks of memory</li>
diff --git a/development/rfcs/rfc09/index.html b/development/rfcs/rfc09/index.html
index 4c9c6db32..8341449f8 100644
--- a/development/rfcs/rfc09/index.html
+++ b/development/rfcs/rfc09/index.html
@@ -48,7 +48,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
diff --git a/development/rfcs/rfc10/index.html b/development/rfcs/rfc10/index.html
index 46365295e..322235449 100644
--- a/development/rfcs/rfc10/index.html
+++ b/development/rfcs/rfc10/index.html
@@ -48,7 +48,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
diff --git a/index.html b/index.html
index b8aec052f..a055eef93 100644
--- a/index.html
+++ b/index.html
@@ -32,7 +32,7 @@
<link rel="preload" href="/custom.css" as="style">
<link rel="stylesheet" href="/custom.css" media="all">
-<link rel="alternate" type="application/rss+xml" href="http://libgeos.org/index.xml" title="GEOS" />
+<link rel="alternate" type="application/rss+xml" href="https://libgeos.org/index.xml" title="GEOS" />
<!-- Made with Geekdoc theme https://github.com/thegeeklab/hugo-geekdoc -->
</head>
@@ -50,7 +50,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
@@ -592,7 +592,7 @@
<p>GEOS is a C/C++ library for spatial computational geometry of the sort generally used by “geographic information systems” software. GEOS is a core dependency of <a href="https://postgis.net">PostGIS</a>, <a href="https://qgis.org">QGIS</a>, <a href="https://gdal.org">GDAL</a>, and <a href="https://shapely.readthedocs.io/en/stable/project.html">Shapely</a>.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="capabilities">Capabilities<a data-clipboard-text="http://libgeos.org/#capabilities" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Capabilities" href="#capabilities"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="capabilities">Capabilities<a data-clipboard-text="https://libgeos.org/#capabilities" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Capabilities" href="#capabilities"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>Spatial Model and Functions</p>
<ul>
<li><strong>Geometries</strong>: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, GeometryCollection</li>
@@ -602,13 +602,13 @@
<li>STR spatial index</li>
<li>OGC Well Known Text (WKT) and Well Known Binary (WKB) encoders and decoders.</li>
</ul>
-<div class="gdoc-page__anchorwrap"><h2 id="api-features">API Features<a data-clipboard-text="http://libgeos.org/#api-features" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor API Features" href="#api-features"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="api-features">API Features<a data-clipboard-text="https://libgeos.org/#api-features" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor API Features" href="#api-features"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<ul>
<li><a href="http://libgeos.github.io/geos/doxygen/geos__c_8h.html">C API</a> (provides long-term API and ABI stability)</li>
<li><a href="doxygen/cpp_iface.html">C++ API</a> (will likely change across versions)</li>
<li>Thread safety (using the reentrant API)</li>
</ul>
-<div class="gdoc-page__anchorwrap"><h2 id="license">License<a data-clipboard-text="http://libgeos.org/#license" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor License" href="#license"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="license">License<a data-clipboard-text="https://libgeos.org/#license" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor License" href="#license"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>GEOS is <a href="https://opensource.com/resources/what-open-source">open source software</a> available under the terms of <a href="http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html">GNU Lesser General Public License</a> (LGPL).</p>
diff --git a/index.xml b/index.xml
index 398d777aa..e15437f86 100644
--- a/index.xml
+++ b/index.xml
@@ -2,17 +2,17 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>GEOS</title>
- <link>http://libgeos.org/</link>
+ <link>https://libgeos.org/</link>
<description>Recent content on GEOS</description>
<generator>Hugo -- gohugo.io</generator>
<language>en-us</language>
- <lastBuildDate>Mon, 04 Oct 2021 14:13:20 -0700</lastBuildDate><atom:link href="http://libgeos.org/index.xml" rel="self" type="application/rss+xml" />
+ <lastBuildDate>Mon, 04 Oct 2021 14:13:20 -0700</lastBuildDate><atom:link href="https://libgeos.org/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>GEOS RFC 10 - Move Project to GitHub</title>
- <link>http://libgeos.org/development/rfcs/rfc10/</link>
+ <link>https://libgeos.org/development/rfcs/rfc10/</link>
<pubDate>Fri, 29 Oct 2021 00:00:00 -0700</pubDate>
- <guid>http://libgeos.org/development/rfcs/rfc10/</guid>
+ <guid>https://libgeos.org/development/rfcs/rfc10/</guid>
<description>RFC 10 Move Project to GitHub Author Paul Ramsey Contact pramsey at cleverelephant.ca Status Accepted, November 9, 2021 GitHub has been the largest source of 3rd party code contribution via pull-requests for some time now.
Moving to Github has the following components:
Move the canonical (writeable) repository to GitHub Migrate the (current, useful) contents of the Trac wiki to the new web framework Deleting the migrated and out-of-date contents of the Trac wiki Switching the Trac tickets to read-only Web scraping the Trac ticket contents and placing in a geos-old-tickets repo At that point:</description>
@@ -20,10 +20,10 @@ Moving to Github has the following components:
<item>
<title>Project Steering Committee</title>
- <link>http://libgeos.org/development/psc/</link>
+ <link>https://libgeos.org/development/psc/</link>
<pubDate>Wed, 27 Oct 2021 00:00:00 -0700</pubDate>
- <guid>http://libgeos.org/development/psc/</guid>
+ <guid>https://libgeos.org/development/psc/</guid>
<description>The GEOS project is run by a Project Steering Committee made up of developers and contributors to the project and is a project of OSGeo. Major project decisions are made via a Request for Comments (RFC) process, where proposals are first documented and then voted on by the steering committee.
This PSC list is valid as of November 10, 2021.
Sandro Santilli (chair) Martin Davis Howard Butler Regina Obe Dale Lutz Paul Ramsey Dan Baston The PSC approves major changes and RFC documents.</description>
@@ -31,40 +31,40 @@ This PSC list is valid as of November 10, 2021.
<item>
<title>Reference Docs</title>
- <link>http://libgeos.org/usage/doxygen/</link>
+ <link>https://libgeos.org/usage/doxygen/</link>
<pubDate>Mon, 04 Oct 2021 13:44:59 -0700</pubDate>
- <guid>http://libgeos.org/usage/doxygen/</guid>
+ <guid>https://libgeos.org/usage/doxygen/</guid>
<description>The Doxygen documentation is the most up-to-date reference for the C and C++ API of GEOS.
C API C++ API For a quick start, see the C API tutorial or the C++ API tutorial. There are also working examples available in the code repository.</description>
</item>
<item>
<title>C API Programming</title>
- <link>http://libgeos.org/usage/c_api/</link>
+ <link>https://libgeos.org/usage/c_api/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/usage/c_api/</guid>
+ <guid>https://libgeos.org/usage/c_api/</guid>
<description>Most programs using GEOS use the C API, rather than building against the C++ headers. The C API offers the a number of benefits:
Stable API, that preserves behaviour and function naming over multiple releases. Stable ABI, allowing new binaries to be dropped into place without requiring a rebuild of dependent applications. Simple access pattern, using the simple features model as the basis for most operations. In exchange for this simplicity and stability, the C API has a few requirements from application authors:</description>
</item>
<item>
<title>C++ API Programming</title>
- <link>http://libgeos.org/usage/cpp_api/</link>
+ <link>https://libgeos.org/usage/cpp_api/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/usage/cpp_api/</guid>
+ <guid>https://libgeos.org/usage/cpp_api/</guid>
<description>The GEOS C++ API is included in the collection of header files installed in include/geos which is a very large collection. Effectively it includes both “public” headers that a user might be expected to make use of and “private” headers that are mostly only used by internal algorithms. Currently, the two kinds of headers are not marked in any way, nor is there an easy way to disentagle them.
Using the C++ API means giving up:</description>
</item>
<item>
<title>Version 3.10.0</title>
- <link>http://libgeos.org/posts/2021-10-01-geos-3-10-released/</link>
+ <link>https://libgeos.org/posts/2021-10-01-geos-3-10-released/</link>
<pubDate>Thu, 21 Oct 2021 00:00:00 +0000</pubDate>
- <guid>http://libgeos.org/posts/2021-10-01-geos-3-10-released/</guid>
+ <guid>https://libgeos.org/posts/2021-10-01-geos-3-10-released/</guid>
<description>The 3.10 release of GEOS is now available to download.
This release includes the following new features in the C API (and of course underlying changes to the C++ code to support these features):
CAPI additions for testing whether geometries are within a distance of each other, GEOSDistanceWithin and GEOSPreparedDistanceWithin CAPI addition for adding extra vertices to a geometry, GEOSDensify CAPI additions for high-performance construction/reading of coordinate sequences from/to memory buffers, GEOSCoordSeq_copyFromArrays, GEOSCoordSeq_copyFromBuffer, GEOSCoordSeq_copyToArrays, and GEOSCoordSeq_copyToBuffer CAPI addition for new validity enforement algorithm, GEOSMakeValidWithParams CAPI addition for ISO WKB output, GEOSWKBWriter_getFlavor and GEOSWKBWriter_setFlavor CAPI addition to create a constrained delaunay of polygonal input, GEOSConstrainedDelaunayTriangulation There is a new utility for running arbitrary GEOS commands against input files, geosop.</description>
@@ -72,29 +72,29 @@ Using the C++ API means giving up:</description>
<item>
<title>CI Status</title>
- <link>http://libgeos.org/development/ci_status/</link>
+ <link>https://libgeos.org/development/ci_status/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/development/ci_status/</guid>
+ <guid>https://libgeos.org/development/ci_status/</guid>
<description>CI main 3.10 3.9 3.8 3.7 GitHub GitLab Azure Debbie Winnie Dronie Bessie Bessie32 Runners GitHub - Ubuntu various, Windows various, CMake GitLab - Debian 8.</description>
</item>
<item>
<title>GEOS RFC 1 - Project Steering Committee</title>
- <link>http://libgeos.org/development/rfcs/rfc01/</link>
+ <link>https://libgeos.org/development/rfcs/rfc01/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/development/rfcs/rfc01/</guid>
+ <guid>https://libgeos.org/development/rfcs/rfc01/</guid>
<description>This document describes how the PSC GEOS Project Steering Committee determines membership, and makes decisions on all aspects of the GEOS project - both technical and non-technical.
RFC 1 Project Steering Committee Author Paul Ramsey Contact pramsey at cleverelephant.ca Status Approved, April 10, 2008 Summary This document describes how the GEOS Project Steering Committee (PSC) determines membership, and makes decisions on all aspects of the GEOS project - both technical and non-technical.</description>
</item>
<item>
<title>GEOS RFC 2 - Committer Guidelines </title>
- <link>http://libgeos.org/development/rfcs/rfc02/</link>
+ <link>https://libgeos.org/development/rfcs/rfc02/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/development/rfcs/rfc02/</guid>
+ <guid>https://libgeos.org/development/rfcs/rfc02/</guid>
<description>This document describes the technical and legal responsibilities of [wiki:PSC GEOS committers].
RFC 2 Committer Guidelines Author Paul Ramsey, Regina Obe Contact pramsey at cleverelephant.ca, lr at pcorp.us Status Draft Summary This document describes the technical and legal responsibilities of [wiki:PSC GEOS committers].
Election to GIT Commit Access Permission for GIT commit access shall be provided to new developers only if accepted by the [wiki:PSC GEOS Project Steering Committee].</description>
@@ -102,10 +102,10 @@ Election to GIT Commit Access Permission for GIT commit access shall be provided
<item>
<title>GEOS RFC 3 - Thread Safe CAPI </title>
- <link>http://libgeos.org/development/rfcs/rfc03/</link>
+ <link>https://libgeos.org/development/rfcs/rfc03/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/development/rfcs/rfc03/</guid>
+ <guid>https://libgeos.org/development/rfcs/rfc03/</guid>
<description>Summary The current CAPI in GEOS is not thread safe. The error handling and initialization/finalization process specifically can cause problems.
Definitions (As defined by Frank Warmerdam in http://trac.osgeo.org/gdal/wiki/rfc16_ogr_reentrancy)
Reentrant: A reentrant function can be called simultaneously by multiple threads provided that each invocation of the function references unique data.
@@ -114,10 +114,10 @@ Thread-safe: A thread-safe function can be called simultaneously by multiple thr
<item>
<title>GEOS RFC 4 - Code Formatting Style</title>
- <link>http://libgeos.org/development/rfcs/rfc04/</link>
+ <link>https://libgeos.org/development/rfcs/rfc04/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/development/rfcs/rfc04/</guid>
+ <guid>https://libgeos.org/development/rfcs/rfc04/</guid>
<description>This document proposes and describes desired code formatting style used across C/C++ source code in GEOS.
RFC 4 Code Formatting Style Author Mateusz Łoskot Contact mateusz at loskot.net Status Dropped (no agreement) Summary The document proposes and describes desired default code formatting style guidelines for GEOS programming in C and C++ languages.
The goal of this document is to initiate process to reach an agreement for the default code formatting style.</description>
@@ -125,10 +125,10 @@ The goal of this document is to initiate process to reach an agreement for the d
<item>
<title>GEOS RFC 5 - C++11 Compilation Mode</title>
- <link>http://libgeos.org/development/rfcs/rfc05/</link>
+ <link>https://libgeos.org/development/rfcs/rfc05/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/development/rfcs/rfc05/</guid>
+ <guid>https://libgeos.org/development/rfcs/rfc05/</guid>
<description>This document proposes and describes desired code formatting style used across C/C++ source code in GEOS.
RFC 5 C++11 Compilation Mode Author Mateusz Łoskot Contact mateusz at loskot.net Status Accepted (no agreement) Summary The document proposes to switch to C++11 compilation mode as default throughout the whole C++ source code of GEOS.
The goal of the document is to request and achieve agreement on using C++11 as the minimum required version of the C++ programming language standard.</description>
@@ -136,19 +136,19 @@ The goal of the document is to request and achieve agreement on using C++11 as t
<item>
<title>GEOS RFC 6 - Require explicit configure to use the C++ API</title>
- <link>http://libgeos.org/development/rfcs/rfc06/</link>
+ <link>https://libgeos.org/development/rfcs/rfc06/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/development/rfcs/rfc06/</guid>
+ <guid>https://libgeos.org/development/rfcs/rfc06/</guid>
<description>RFC 9 Require explicit configure to use the C++ API Author Regina Obe Contact lr at pcorp.us Status Not Passed Past discussions Trac ticket to deprecate another request to deprecate and osm2pgsql mess more examples about how apps linking directly to GEOS C++ causing problems for other applications Pointing out removing ability to use GEOS C++ reduces users freedoms</description>
</item>
<item>
<title>GEOS RFC 7 - Use CMake for Build System</title>
- <link>http://libgeos.org/development/rfcs/rfc07/</link>
+ <link>https://libgeos.org/development/rfcs/rfc07/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/development/rfcs/rfc07/</guid>
+ <guid>https://libgeos.org/development/rfcs/rfc07/</guid>
<description>RFC 7 Use CMake for build system Author Daniel Baston Contact dbaston at gmail.com Status Accepted, January 15, 2021 This document proposes to use CMake as the build system for GEOS and discontinue use of autotools and NMake.
Since version 3.5, we have officially supported building GEOS with CMake: https://trac.osgeo.org/geos/wiki/BuildingOnUnixWithCMake
GEOS is also required to build with autotools and NMake.</description>
@@ -156,10 +156,10 @@ GEOS is also required to build with autotools and NMake.</description>
<item>
<title>GEOS RFC 8 - Improve Coordinate Sequence API (WIP)</title>
- <link>http://libgeos.org/development/rfcs/rfc08/</link>
+ <link>https://libgeos.org/development/rfcs/rfc08/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/development/rfcs/rfc08/</guid>
+ <guid>https://libgeos.org/development/rfcs/rfc08/</guid>
<description>RFC 8 Improve Coordinate Sequence API Author Martin Davis Contact martin.davis at crunchydata.com Status In Discussion This document proposes to modify the Coordinate Sequence API to improve performance and adaptiveness.
These improvements are (likely to be) breaking changes to the C++ API.
These may require extensions to the C API to be externally available, but should not result in breaking the current C API.</description>
@@ -167,10 +167,10 @@ These may require extensions to the C API to be externally available, but should
<item>
<title>GEOS RFC 9 - Restore the C++ API (WIP)</title>
- <link>http://libgeos.org/development/rfcs/rfc09/</link>
+ <link>https://libgeos.org/development/rfcs/rfc09/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/development/rfcs/rfc09/</guid>
+ <guid>https://libgeos.org/development/rfcs/rfc09/</guid>
<description>RFC 9 Restore the C++ API Author Mateusz Łoskot Contact mateusz at loskot.net Status [https://lists.osgeo.org/pipermail/geos-devel/2019-May/008972.html Proposed] The GEOS library is a C++ library offering two kinds of public API: C++ API and C API.
The GEOS library started as a C++ library. The C API was introduced in version 2.2.
The GEOS library has never promised any stability of the C++ API and this fact has always been documented and clearly stated:</description>
@@ -178,46 +178,46 @@ The GEOS library has never promised any stability of the C++ API and this fact h
<item>
<title>GeoJSON</title>
- <link>http://libgeos.org/specifications/geojson/</link>
+ <link>https://libgeos.org/specifications/geojson/</link>
<pubDate>Mon, 04 Oct 2021 14:18:42 -0700</pubDate>
- <guid>http://libgeos.org/specifications/geojson/</guid>
+ <guid>https://libgeos.org/specifications/geojson/</guid>
<description>content</description>
</item>
<item>
<title>Well-Known Binary (WKB)</title>
- <link>http://libgeos.org/specifications/wkb/</link>
+ <link>https://libgeos.org/specifications/wkb/</link>
<pubDate>Mon, 04 Oct 2021 14:18:42 -0700</pubDate>
- <guid>http://libgeos.org/specifications/wkb/</guid>
+ <guid>https://libgeos.org/specifications/wkb/</guid>
<description>content</description>
</item>
<item>
<title>Well-Known Text (WKT)</title>
- <link>http://libgeos.org/specifications/wkt/</link>
+ <link>https://libgeos.org/specifications/wkt/</link>
<pubDate>Mon, 04 Oct 2021 14:18:42 -0700</pubDate>
- <guid>http://libgeos.org/specifications/wkt/</guid>
+ <guid>https://libgeos.org/specifications/wkt/</guid>
<description>content</description>
</item>
<item>
<title>Download Source</title>
- <link>http://libgeos.org/usage/download/</link>
+ <link>https://libgeos.org/usage/download/</link>
<pubDate>Mon, 04 Oct 2021 13:44:59 -0700</pubDate>
- <guid>http://libgeos.org/usage/download/</guid>
+ <guid>https://libgeos.org/usage/download/</guid>
<description>Release Date Release Download Link 2021/11/02 3.10.1 geos-3.10.1.tar.bz2 2021/11/01 3.9.2 geos-3.9.2.tar.bz2 2021/04/10 3.8.2 geos-3.8.2.tar.bz2 2019/10/04 3.7.3 geos-3.7.3.tar.bz2 2020/12/11 3.6.5 geos-3.6.5.tar.bz2 2019/10/04 3.5.2 geos-3.5.2.tar.bz2 Build From Source Build Requirements CMake 3.13 or later. C++11 compiler. We regularly test GCC, Clang and Microsoft Visual C++. Doxygen to build the API documentation. Build Builds with CMake are done “outside the tree” either in a build directory in the source tree or next to the tree.</description>
</item>
<item>
<title>Install Packages</title>
- <link>http://libgeos.org/usage/install/</link>
+ <link>https://libgeos.org/usage/install/</link>
<pubDate>Mon, 04 Oct 2021 13:44:59 -0700</pubDate>
- <guid>http://libgeos.org/usage/install/</guid>
+ <guid>https://libgeos.org/usage/install/</guid>
<description>Red Hat There is a GEOS package in the EPEL (Extra Packages for Enterprise Linux) repository.
# Add the EPEL repository yum -y install epel-release # Install the GEOS runtime and development packages rpm -Uvh geos geos-devel Ubuntu The Ubuntu GIS project maintains a collection of repositories with builds of common open source geospatial projects, including GEOS.
# Add the Ubuntu GIS PPA sudo apt-get install python-software-properties sudo add-apt-repository ppa:ubuntugis/ppa # Install the packages sudo apt-get install geos Debian The Debian GIS project maintains GEOS packages and pushes them into the appropriate Debian respositories.</description>
diff --git a/posts/2021-10-01-geos-3-10-released/index.html b/posts/2021-10-01-geos-3-10-released/index.html
index b426a2735..9f533e316 100644
--- a/posts/2021-10-01-geos-3-10-released/index.html
+++ b/posts/2021-10-01-geos-3-10-released/index.html
@@ -48,7 +48,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
@@ -562,7 +562,7 @@
-<p>The 3.10 release of GEOS is now available <a href="http://libgeos.org/usage/download/">to download</a>.</p>
+<p>The 3.10 release of GEOS is now available <a href="https://libgeos.org/usage/download/">to download</a>.</p>
<ul>
<li>
<p>This release includes the following new features in the C API (and of course underlying changes to the C++ code to support these features):</p>
diff --git a/posts/index.html b/posts/index.html
index ea99034b0..ae1c7602b 100644
--- a/posts/index.html
+++ b/posts/index.html
@@ -31,7 +31,7 @@
<link rel="preload" href="/custom.css" as="style">
<link rel="stylesheet" href="/custom.css" media="all">
-<link rel="alternate" type="application/rss+xml" href="http://libgeos.org/posts/index.xml" title="GEOS" />
+<link rel="alternate" type="application/rss+xml" href="https://libgeos.org/posts/index.xml" title="GEOS" />
<!-- Made with Geekdoc theme https://github.com/thegeeklab/hugo-geekdoc -->
</head>
@@ -49,7 +49,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
diff --git a/posts/index.xml b/posts/index.xml
index 017d26c16..91a87bfb2 100644
--- a/posts/index.xml
+++ b/posts/index.xml
@@ -2,17 +2,17 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>News on GEOS</title>
- <link>http://libgeos.org/posts/</link>
+ <link>https://libgeos.org/posts/</link>
<description>Recent content in News on GEOS</description>
<generator>Hugo -- gohugo.io</generator>
<language>en-us</language>
- <lastBuildDate>Thu, 21 Oct 2021 00:00:00 +0000</lastBuildDate><atom:link href="http://libgeos.org/posts/index.xml" rel="self" type="application/rss+xml" />
+ <lastBuildDate>Thu, 21 Oct 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://libgeos.org/posts/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Version 3.10.0</title>
- <link>http://libgeos.org/posts/2021-10-01-geos-3-10-released/</link>
+ <link>https://libgeos.org/posts/2021-10-01-geos-3-10-released/</link>
<pubDate>Thu, 21 Oct 2021 00:00:00 +0000</pubDate>
- <guid>http://libgeos.org/posts/2021-10-01-geos-3-10-released/</guid>
+ <guid>https://libgeos.org/posts/2021-10-01-geos-3-10-released/</guid>
<description>The 3.10 release of GEOS is now available to download.
This release includes the following new features in the C API (and of course underlying changes to the C++ code to support these features):
CAPI additions for testing whether geometries are within a distance of each other, GEOSDistanceWithin and GEOSPreparedDistanceWithin CAPI addition for adding extra vertices to a geometry, GEOSDensify CAPI additions for high-performance construction/reading of coordinate sequences from/to memory buffers, GEOSCoordSeq_copyFromArrays, GEOSCoordSeq_copyFromBuffer, GEOSCoordSeq_copyToArrays, and GEOSCoordSeq_copyToBuffer CAPI addition for new validity enforement algorithm, GEOSMakeValidWithParams CAPI addition for ISO WKB output, GEOSWKBWriter_getFlavor and GEOSWKBWriter_setFlavor CAPI addition to create a constrained delaunay of polygonal input, GEOSConstrainedDelaunayTriangulation There is a new utility for running arbitrary GEOS commands against input files, geosop.</description>
diff --git a/posts/page/1/index.html b/posts/page/1/index.html
index bfde5598a..a9d6fe4bf 100644
--- a/posts/page/1/index.html
+++ b/posts/page/1/index.html
@@ -1 +1 @@
-<!DOCTYPE html><html><head><title>http://libgeos.org/posts/</title><link rel="canonical" href="http://libgeos.org/posts/"/><meta name="robots" content="noindex"><meta charset="utf-8" /><meta http-equiv="refresh" content="0; url=http://libgeos.org/posts/" /></head></html>
\ No newline at end of file
+<!DOCTYPE html><html><head><title>https://libgeos.org/posts/</title><link rel="canonical" href="https://libgeos.org/posts/"/><meta name="robots" content="noindex"><meta charset="utf-8" /><meta http-equiv="refresh" content="0; url=https://libgeos.org/posts/" /></head></html>
\ No newline at end of file
diff --git a/sitemap.xml b/sitemap.xml
index 66396cec7..51d231ac0 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -2,89 +2,89 @@
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
xmlns:xhtml="http://www.w3.org/1999/xhtml">
<url>
- <loc>http://libgeos.org/development/rfcs/rfc10/</loc>
+ <loc>https://libgeos.org/development/rfcs/rfc10/</loc>
<lastmod>2021-10-29T00:00:00-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/posts/</loc>
+ <loc>https://libgeos.org/posts/</loc>
<lastmod>2021-10-21T00:00:00+00:00</lastmod>
</url><url>
- <loc>http://libgeos.org/development/psc/</loc>
+ <loc>https://libgeos.org/development/psc/</loc>
<lastmod>2021-10-27T00:00:00-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/development/rfcs/</loc>
+ <loc>https://libgeos.org/development/rfcs/</loc>
<lastmod>2021-10-04T14:21:00-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/usage/doxygen/</loc>
+ <loc>https://libgeos.org/usage/doxygen/</loc>
<lastmod>2021-10-04T13:44:59-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/usage/c_api/</loc>
+ <loc>https://libgeos.org/usage/c_api/</loc>
<lastmod>2021-10-04T14:21:00-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/usage/cpp_api/</loc>
+ <loc>https://libgeos.org/usage/cpp_api/</loc>
<lastmod>2021-10-04T14:21:00-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/posts/2021-10-01-geos-3-10-released/</loc>
+ <loc>https://libgeos.org/posts/2021-10-01-geos-3-10-released/</loc>
<lastmod>2021-10-21T00:00:00+00:00</lastmod>
</url><url>
- <loc>http://libgeos.org/development/ci_status/</loc>
+ <loc>https://libgeos.org/development/ci_status/</loc>
<lastmod>2021-10-04T14:21:00-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/development/</loc>
+ <loc>https://libgeos.org/development/</loc>
<lastmod>2021-10-04T14:21:00-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/specifications/</loc>
+ <loc>https://libgeos.org/specifications/</loc>
<lastmod>2021-10-04T14:21:00-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/development/rfcs/rfc01/</loc>
+ <loc>https://libgeos.org/development/rfcs/rfc01/</loc>
<lastmod>2021-10-04T14:21:00-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/development/rfcs/rfc02/</loc>
+ <loc>https://libgeos.org/development/rfcs/rfc02/</loc>
<lastmod>2021-10-04T14:21:00-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/development/rfcs/rfc03/</loc>
+ <loc>https://libgeos.org/development/rfcs/rfc03/</loc>
<lastmod>2021-10-04T14:21:00-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/development/rfcs/rfc04/</loc>
+ <loc>https://libgeos.org/development/rfcs/rfc04/</loc>
<lastmod>2021-10-04T14:21:00-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/development/rfcs/rfc05/</loc>
+ <loc>https://libgeos.org/development/rfcs/rfc05/</loc>
<lastmod>2021-10-04T14:21:00-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/development/rfcs/rfc06/</loc>
+ <loc>https://libgeos.org/development/rfcs/rfc06/</loc>
<lastmod>2021-10-04T14:21:00-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/development/rfcs/rfc07/</loc>
+ <loc>https://libgeos.org/development/rfcs/rfc07/</loc>
<lastmod>2021-10-04T14:21:00-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/development/rfcs/rfc08/</loc>
+ <loc>https://libgeos.org/development/rfcs/rfc08/</loc>
<lastmod>2021-10-04T14:21:00-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/development/rfcs/rfc09/</loc>
+ <loc>https://libgeos.org/development/rfcs/rfc09/</loc>
<lastmod>2021-10-04T14:21:00-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/usage/</loc>
+ <loc>https://libgeos.org/usage/</loc>
<lastmod>2021-10-04T14:21:00-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/specifications/geojson/</loc>
+ <loc>https://libgeos.org/specifications/geojson/</loc>
<lastmod>2021-10-04T14:18:42-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/specifications/wkb/</loc>
+ <loc>https://libgeos.org/specifications/wkb/</loc>
<lastmod>2021-10-04T14:18:42-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/specifications/wkt/</loc>
+ <loc>https://libgeos.org/specifications/wkt/</loc>
<lastmod>2021-10-04T14:18:42-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/</loc>
+ <loc>https://libgeos.org/</loc>
<lastmod>2021-10-04T14:13:20-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/usage/download/</loc>
+ <loc>https://libgeos.org/usage/download/</loc>
<lastmod>2021-10-04T13:44:59-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/usage/install/</loc>
+ <loc>https://libgeos.org/usage/install/</loc>
<lastmod>2021-10-04T13:44:59-07:00</lastmod>
</url><url>
- <loc>http://libgeos.org/categories/</loc>
+ <loc>https://libgeos.org/categories/</loc>
</url><url>
- <loc>http://libgeos.org/tags/</loc>
+ <loc>https://libgeos.org/tags/</loc>
</url>
</urlset>
diff --git a/specifications/geojson/index.html b/specifications/geojson/index.html
index 647d207b8..7c04efbed 100644
--- a/specifications/geojson/index.html
+++ b/specifications/geojson/index.html
@@ -48,7 +48,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
diff --git a/specifications/index.html b/specifications/index.html
index 8034e4a83..213822dd9 100644
--- a/specifications/index.html
+++ b/specifications/index.html
@@ -31,7 +31,7 @@
<link rel="preload" href="/custom.css" as="style">
<link rel="stylesheet" href="/custom.css" media="all">
-<link rel="alternate" type="application/rss+xml" href="http://libgeos.org/specifications/index.xml" title="GEOS" />
+<link rel="alternate" type="application/rss+xml" href="https://libgeos.org/specifications/index.xml" title="GEOS" />
<!-- Made with Geekdoc theme https://github.com/thegeeklab/hugo-geekdoc -->
</head>
@@ -49,7 +49,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
diff --git a/specifications/index.xml b/specifications/index.xml
index 7d68bb492..401d2b8b3 100644
--- a/specifications/index.xml
+++ b/specifications/index.xml
@@ -2,35 +2,35 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Geometry Formats on GEOS</title>
- <link>http://libgeos.org/specifications/</link>
+ <link>https://libgeos.org/specifications/</link>
<description>Recent content in Geometry Formats on GEOS</description>
<generator>Hugo -- gohugo.io</generator>
<language>en-us</language>
- <lastBuildDate>Mon, 04 Oct 2021 14:21:00 -0700</lastBuildDate><atom:link href="http://libgeos.org/specifications/index.xml" rel="self" type="application/rss+xml" />
+ <lastBuildDate>Mon, 04 Oct 2021 14:21:00 -0700</lastBuildDate><atom:link href="https://libgeos.org/specifications/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>GeoJSON</title>
- <link>http://libgeos.org/specifications/geojson/</link>
+ <link>https://libgeos.org/specifications/geojson/</link>
<pubDate>Mon, 04 Oct 2021 14:18:42 -0700</pubDate>
- <guid>http://libgeos.org/specifications/geojson/</guid>
+ <guid>https://libgeos.org/specifications/geojson/</guid>
<description>content</description>
</item>
<item>
<title>Well-Known Binary (WKB)</title>
- <link>http://libgeos.org/specifications/wkb/</link>
+ <link>https://libgeos.org/specifications/wkb/</link>
<pubDate>Mon, 04 Oct 2021 14:18:42 -0700</pubDate>
- <guid>http://libgeos.org/specifications/wkb/</guid>
+ <guid>https://libgeos.org/specifications/wkb/</guid>
<description>content</description>
</item>
<item>
<title>Well-Known Text (WKT)</title>
- <link>http://libgeos.org/specifications/wkt/</link>
+ <link>https://libgeos.org/specifications/wkt/</link>
<pubDate>Mon, 04 Oct 2021 14:18:42 -0700</pubDate>
- <guid>http://libgeos.org/specifications/wkt/</guid>
+ <guid>https://libgeos.org/specifications/wkt/</guid>
<description>content</description>
</item>
diff --git a/specifications/wkb/index.html b/specifications/wkb/index.html
index a94df4a69..51824454f 100644
--- a/specifications/wkb/index.html
+++ b/specifications/wkb/index.html
@@ -48,7 +48,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
diff --git a/specifications/wkt/index.html b/specifications/wkt/index.html
index 9611e764a..7c61c1f5d 100644
--- a/specifications/wkt/index.html
+++ b/specifications/wkt/index.html
@@ -48,7 +48,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
diff --git a/tags/index.xml b/tags/index.xml
index 2e63bf4f2..48f82c2db 100644
--- a/tags/index.xml
+++ b/tags/index.xml
@@ -2,9 +2,9 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Tags on GEOS</title>
- <link>http://libgeos.org/tags/</link>
+ <link>https://libgeos.org/tags/</link>
<description>Recent content in Tags on GEOS</description>
<generator>Hugo -- gohugo.io</generator>
- <language>en-us</language><atom:link href="http://libgeos.org/tags/index.xml" rel="self" type="application/rss+xml" />
+ <language>en-us</language><atom:link href="https://libgeos.org/tags/index.xml" rel="self" type="application/rss+xml" />
</channel>
</rss>
diff --git a/usage/c_api/index.html b/usage/c_api/index.html
index 363985070..314477450 100644
--- a/usage/c_api/index.html
+++ b/usage/c_api/index.html
@@ -48,7 +48,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
@@ -615,7 +615,7 @@
<li>Explicit memory management. If you create a GEOS object with a GEOS function, you have to remember to free it using the appropriate GEOS destructor.</li>
</ul>
<p>The C API is entirely contained in the <a href="../../doxygen/geos__c_8h.html">geos_c.h</a> header file.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="building-a-program">Building a Program<a data-clipboard-text="http://libgeos.org/usage/c_api/#building-a-program" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Building a Program" href="#building-a-program"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="building-a-program">Building a Program<a data-clipboard-text="https://libgeos.org/usage/c_api/#building-a-program" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Building a Program" href="#building-a-program"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>The simplest GEOS C API application needs to include the API header, declare a message handler, initialize the GEOS globals, and link to the GEOS C library when built.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-c" data-lang="c"><span class="cm">/* geos_hello_world.c */</span>
@@ -669,7 +669,7 @@
<span class="p">}</span>
</code></pre></div><p>When compiling the program, remember to link in the GEOS C library.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash">cc geos_hello_world.c -o geos_hello_world -l geos_c
-</code></pre></div><div class="gdoc-page__anchorwrap"><h2 id="reentrantthreadsafe-api">Reentrant/Threadsafe API<a data-clipboard-text="http://libgeos.org/usage/c_api/#reentrantthreadsafe-api" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Reentrant/Threadsafe API" href="#reentrantthreadsafe-api"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+</code></pre></div><div class="gdoc-page__anchorwrap"><h2 id="reentrantthreadsafe-api">Reentrant/Threadsafe API<a data-clipboard-text="https://libgeos.org/usage/c_api/#reentrantthreadsafe-api" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Reentrant/Threadsafe API" href="#reentrantthreadsafe-api"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>Every function in the examples above and below is shadowed by a reentrant function carrying a <code>_r</code> suffix. The reentrant functions work the same as their simple counterparts, but they all have one extra parameter, a <code>GEOSContextHandle_t</code>.</p>
<p>The <code>GEOSContextHandle_t</code> carries a thread-local state that is equivalent to the state initialized by the <code>initGEOS()</code> call in the simple example above.</p>
<p>To use the reentrant API, you skip calling <code>initGEOS()</code> and instead call <code>GEOS_init_r()</code> to create a context local to your thread. Each thread that will be running GEOS operations should create its own context prior to working with the GEOS API.</p>
@@ -717,9 +717,9 @@
<span class="k">return</span> <span class="mi">0</span><span class="p">;</span>
<span class="p">}</span>
</code></pre></div><p>Note that the overall structure of the code is identical, but the reentrant variants are used, and the preamble and cleanup are slightly different.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="object-model">Object Model<a data-clipboard-text="http://libgeos.org/usage/c_api/#object-model" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Object Model" href="#object-model"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="object-model">Object Model<a data-clipboard-text="https://libgeos.org/usage/c_api/#object-model" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Object Model" href="#object-model"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>The <code>GEOSCoordSequence</code> and <code>GEOSGeometry</code> objects are at the heart of the GEOS object model.</p>
-<div class="gdoc-page__anchorwrap"><h3 id="geoscoordsequence">GEOSCoordSequence<a data-clipboard-text="http://libgeos.org/usage/c_api/#geoscoordsequence" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor GEOSCoordSequence" href="#geoscoordsequence"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h3 id="geoscoordsequence">GEOSCoordSequence<a data-clipboard-text="https://libgeos.org/usage/c_api/#geoscoordsequence" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor GEOSCoordSequence" href="#geoscoordsequence"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p><code>GEOSCoordSequence</code> is an ordered list of coordinates (2 or 3 dimensional). There are a number of ways to make a <code>GEOSCoordSequence</code>.</p>
<p>You can create a <code>GEOSCoordSequence</code> by creating a blank one and then setting the coordinate values.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-c" data-lang="c"><span class="kt">double</span> <span class="n">xList</span><span class="p">[]</span> <span class="o">=</span> <span class="p">{</span><span class="mf">1.0</span><span class="p">,</span> <span class="mf">2.0</span><span class="p">,</span> <span class="mf">3.0</span><span class="p">};</span>
@@ -766,7 +766,7 @@
<li>GEOSCoordSeq_copyToBuffer()</li>
</ul>
<p>Using the array or buffer methods can often be <strong>faster</strong> than using direct coordinate reading or serialization formats, if the target structures use coordinate arrays or XY binary buffers.</p>
-<div class="gdoc-page__anchorwrap"><h3 id="geosgeometry">GEOSGeometry<a data-clipboard-text="http://libgeos.org/usage/c_api/#geosgeometry" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor GEOSGeometry" href="#geosgeometry"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h3 id="geosgeometry">GEOSGeometry<a data-clipboard-text="https://libgeos.org/usage/c_api/#geosgeometry" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor GEOSGeometry" href="#geosgeometry"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>The workhorse of the GEOS C API is the <code>GEOSGeometry</code>. <code>GEOSGeometry</code> can be a point, linestring, polygon, multipoint, multilinestring, multipolygon, or geometrycollection. Most functions in the GEOS C API have a <code>GEOSGeometry</code> as a parameter or return type. Clean up <code>GEOSGeometry</code> using <code>GEOSGeom_destroy()</code>.</p>
<p>There are many constructors for <code>GEOSGeometry</code>:</p>
<ul>
@@ -817,11 +817,11 @@
<span class="cm">/* frees the containing array */</span>
<span class="n">free</span><span class="p">(</span><span class="n">points</span><span class="p">);</span>
-</code></pre></div><div class="gdoc-page__anchorwrap"><h3 id="readers-and-writers">Readers and Writers<a data-clipboard-text="http://libgeos.org/usage/c_api/#readers-and-writers" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Readers and Writers" href="#readers-and-writers"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+</code></pre></div><div class="gdoc-page__anchorwrap"><h3 id="readers-and-writers">Readers and Writers<a data-clipboard-text="https://libgeos.org/usage/c_api/#readers-and-writers" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Readers and Writers" href="#readers-and-writers"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>The examples above build <code>GEOSCoordSequence</code> from arrays of double, and <code>GEOSGeometry</code> from coordinate sequences, but it is also possible to directly read from and write to standard geometry formats:</p>
<ul>
-<li>Well-Known Text (<a href="http://libgeos.org/specifications/wkt/">WKT</a>)</li>
-<li>Well-Known Binary (<a href="http://libgeos.org/specifications/wkb/">WKB</a>)</li>
+<li>Well-Known Text (<a href="https://libgeos.org/specifications/wkt/">WKT</a>)</li>
+<li>Well-Known Binary (<a href="https://libgeos.org/specifications/wkb/">WKB</a>)</li>
<li><a href="https://datatracker.ietf.org/doc/html/rfc7946">GeoJSON</a></li>
</ul>
<p>For example, reading and writing WKT:</p>
@@ -850,7 +850,7 @@
<li>GEOSGeoJSONReader / GEOSGeoJSONWriter</li>
</ul>
<p>For a complete example using a reader and writer, see <a href="https://github.com/libgeos/geos/blob/main/examples/capi_read.c">capi_read.c</a>.</p>
-<div class="gdoc-page__anchorwrap"><h3 id="prepared-geometry">Prepared Geometry<a data-clipboard-text="http://libgeos.org/usage/c_api/#prepared-geometry" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Prepared Geometry" href="#prepared-geometry"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h3 id="prepared-geometry">Prepared Geometry<a data-clipboard-text="https://libgeos.org/usage/c_api/#prepared-geometry" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Prepared Geometry" href="#prepared-geometry"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>The GEOS “prepared geometry” is conceptually similar to a database “prepared statement”: by doing a little up-front work to set-up a handler, you can reap a performance benefit when you execute repeated function calls on that object.</p>
<p>Prepared geometries contain internal indexes that make calls to the “spatial predicate” functions like <code>GEOSPreparedIntersects()</code> and <code>GEOSPreparedContains()</code> much much faster. These are functions that take in two geometries and return true or false.</p>
<p>If you are going to be making repeated calls to predicates on the same geometry, using a prepared geometry could be a big performance boost, at the cost of a little extra complexity.</p>
@@ -878,7 +878,7 @@
<span class="n">GEOSGeom_destroy</span><span class="p">(</span><span class="n">geom</span><span class="p">);</span>
<span class="n">GEOSGeom_destroy</span><span class="p">(</span><span class="n">pt</span><span class="p">);</span>
</code></pre></div><p>For a complete example of using prepared geometry to accelerate multiple predicate tests, see the <a href="https://github.com/libgeos/geos/blob/main/examples/capi_prepared.c">capi_prepared.c</a> example.</p>
-<div class="gdoc-page__anchorwrap"><h3 id="strtree-index">STRTree Index<a data-clipboard-text="http://libgeos.org/usage/c_api/#strtree-index" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor STRTree Index" href="#strtree-index"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h3 id="strtree-index">STRTree Index<a data-clipboard-text="https://libgeos.org/usage/c_api/#strtree-index" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor STRTree Index" href="#strtree-index"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<ul>
<li>GEOSSTRtree</li>
</ul>
diff --git a/usage/cpp_api/index.html b/usage/cpp_api/index.html
index 38c31b186..cee6dd3dd 100644
--- a/usage/cpp_api/index.html
+++ b/usage/cpp_api/index.html
@@ -48,7 +48,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
@@ -618,7 +618,7 @@
<li>Use the <code>PreparedGeometry</code> class as needed.</li>
</ul>
<p>One benefit of using the C++ API is access to more modern C++ facilities, like the <code>std::unique_ptr</code> and <code>std::string</code>.</p>
-<div class="gdoc-page__anchorwrap"><h2 id="building-a-program">Building a Program<a data-clipboard-text="http://libgeos.org/usage/cpp_api/#building-a-program" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Building a Program" href="#building-a-program"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h2 id="building-a-program">Building a Program<a data-clipboard-text="https://libgeos.org/usage/cpp_api/#building-a-program" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Building a Program" href="#building-a-program"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
<p>The simplest GEOS C++ API application needs to include the <code>geom::Geometry.h</code> header and <code>geom::GeometryFactory.h</code> header, to construct new geometries. To read geometries from input formats, a reader such as <code>geom::WKTReader.h</code> will also be required.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-c++" data-lang="c++"><span class="cm">/*
</span><span class="cm">* # GEOS C++ example 1
diff --git a/usage/download/index.html b/usage/download/index.html
index e03b12337..b175e575f 100644
--- a/usage/download/index.html
+++ b/usage/download/index.html
@@ -48,7 +48,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
@@ -645,14 +645,14 @@
</tr>
</tbody>
</table>
-<div class="gdoc-page__anchorwrap"><h2 id="build-from-source">Build From Source<a data-clipboard-text="http://libgeos.org/usage/download/#build-from-source" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Build From Source" href="#build-from-source"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
-<div class="gdoc-page__anchorwrap"><h3 id="build-requirements">Build Requirements<a data-clipboard-text="http://libgeos.org/usage/download/#build-requirements" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Build Requirements" href="#build-requirements"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h2 id="build-from-source">Build From Source<a data-clipboard-text="https://libgeos.org/usage/download/#build-from-source" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Build From Source" href="#build-from-source"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h2></div>
+<div class="gdoc-page__anchorwrap"><h3 id="build-requirements">Build Requirements<a data-clipboard-text="https://libgeos.org/usage/download/#build-requirements" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Build Requirements" href="#build-requirements"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<ul>
<li><a href="https://cmake.org/download/">CMake</a> 3.13 or later.</li>
<li>C++11 compiler. We regularly test GCC, Clang and Microsoft Visual C++.</li>
<li><a href="https://www.doxygen.nl/">Doxygen</a> to build the API documentation.</li>
</ul>
-<div class="gdoc-page__anchorwrap"><h3 id="build">Build<a data-clipboard-text="http://libgeos.org/usage/download/#build" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Build" href="#build"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h3 id="build">Build<a data-clipboard-text="https://libgeos.org/usage/download/#build" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Build" href="#build"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>Builds with CMake are done “outside the tree” either in a build directory in the source tree or next to the tree.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="c1"># Unpack and setup build directory</span>
tar xvfz geos-3.10.1.tar.bz2
@@ -668,7 +668,7 @@ cmake <span class="se">\
make
ctest
make install
-</code></pre></div><div class="gdoc-page__anchorwrap"><h3 id="build-options">Build Options<a data-clipboard-text="http://libgeos.org/usage/download/#build-options" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Build Options" href="#build-options"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+</code></pre></div><div class="gdoc-page__anchorwrap"><h3 id="build-options">Build Options<a data-clipboard-text="https://libgeos.org/usage/download/#build-options" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Build Options" href="#build-options"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>The GEOS build can be customized using build options.</p>
<table>
<thead>
@@ -706,7 +706,7 @@ make install
</tr>
</tbody>
</table>
-<div class="gdoc-page__anchorwrap"><h3 id="test-options">Test Options<a data-clipboard-text="http://libgeos.org/usage/download/#test-options" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Test Options" href="#test-options"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h3 id="test-options">Test Options<a data-clipboard-text="https://libgeos.org/usage/download/#test-options" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Test Options" href="#test-options"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>It is possible to run ctest directly. This gives access to ctest command line options (see ctest –help for a listing).</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash">ctest
ctest --verbose
diff --git a/usage/doxygen/index.html b/usage/doxygen/index.html
index 959f16b55..dcc5e9d27 100644
--- a/usage/doxygen/index.html
+++ b/usage/doxygen/index.html
@@ -48,7 +48,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
@@ -609,7 +609,7 @@
<li><a href="../../doxygen/geos__c_8h.html">C API</a></li>
<li><a href="../../doxygen/cpp_iface.html">C++ API</a></li>
</ul>
-<p>For a quick start, see the <a href="http://libgeos.org/usage/c_api/">C API tutorial</a> or the <a href="http://libgeos.org/usage/cpp_api/">C++ API tutorial</a>. There are also <a href="https://github.com/libgeos/geos/tree/main/examples">working examples</a> available in the code repository.</p>
+<p>For a quick start, see the <a href="https://libgeos.org/usage/c_api/">C API tutorial</a> or the <a href="https://libgeos.org/usage/cpp_api/">C++ API tutorial</a>. There are also <a href="https://github.com/libgeos/geos/tree/main/examples">working examples</a> available in the code repository.</p>
</article>
diff --git a/usage/index.html b/usage/index.html
index c6c85632f..8b8f583d4 100644
--- a/usage/index.html
+++ b/usage/index.html
@@ -31,7 +31,7 @@
<link rel="preload" href="/custom.css" as="style">
<link rel="stylesheet" href="/custom.css" media="all">
-<link rel="alternate" type="application/rss+xml" href="http://libgeos.org/usage/index.xml" title="GEOS" />
+<link rel="alternate" type="application/rss+xml" href="https://libgeos.org/usage/index.xml" title="GEOS" />
<!-- Made with Geekdoc theme https://github.com/thegeeklab/hugo-geekdoc -->
</head>
@@ -49,7 +49,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
diff --git a/usage/index.xml b/usage/index.xml
index 0e77e8579..039b3adf9 100644
--- a/usage/index.xml
+++ b/usage/index.xml
@@ -2,56 +2,56 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Usage on GEOS</title>
- <link>http://libgeos.org/usage/</link>
+ <link>https://libgeos.org/usage/</link>
<description>Recent content in Usage on GEOS</description>
<generator>Hugo -- gohugo.io</generator>
<language>en-us</language>
- <lastBuildDate>Mon, 04 Oct 2021 14:21:00 -0700</lastBuildDate><atom:link href="http://libgeos.org/usage/index.xml" rel="self" type="application/rss+xml" />
+ <lastBuildDate>Mon, 04 Oct 2021 14:21:00 -0700</lastBuildDate><atom:link href="https://libgeos.org/usage/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Reference Docs</title>
- <link>http://libgeos.org/usage/doxygen/</link>
+ <link>https://libgeos.org/usage/doxygen/</link>
<pubDate>Mon, 04 Oct 2021 13:44:59 -0700</pubDate>
- <guid>http://libgeos.org/usage/doxygen/</guid>
+ <guid>https://libgeos.org/usage/doxygen/</guid>
<description>The Doxygen documentation is the most up-to-date reference for the C and C++ API of GEOS.
C API C++ API For a quick start, see the C API tutorial or the C++ API tutorial. There are also working examples available in the code repository.</description>
</item>
<item>
<title>C API Programming</title>
- <link>http://libgeos.org/usage/c_api/</link>
+ <link>https://libgeos.org/usage/c_api/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/usage/c_api/</guid>
+ <guid>https://libgeos.org/usage/c_api/</guid>
<description>Most programs using GEOS use the C API, rather than building against the C++ headers. The C API offers the a number of benefits:
Stable API, that preserves behaviour and function naming over multiple releases. Stable ABI, allowing new binaries to be dropped into place without requiring a rebuild of dependent applications. Simple access pattern, using the simple features model as the basis for most operations. In exchange for this simplicity and stability, the C API has a few requirements from application authors:</description>
</item>
<item>
<title>C++ API Programming</title>
- <link>http://libgeos.org/usage/cpp_api/</link>
+ <link>https://libgeos.org/usage/cpp_api/</link>
<pubDate>Mon, 04 Oct 2021 14:21:00 -0700</pubDate>
- <guid>http://libgeos.org/usage/cpp_api/</guid>
+ <guid>https://libgeos.org/usage/cpp_api/</guid>
<description>The GEOS C++ API is included in the collection of header files installed in include/geos which is a very large collection. Effectively it includes both “public” headers that a user might be expected to make use of and “private” headers that are mostly only used by internal algorithms. Currently, the two kinds of headers are not marked in any way, nor is there an easy way to disentagle them.
Using the C++ API means giving up:</description>
</item>
<item>
<title>Download Source</title>
- <link>http://libgeos.org/usage/download/</link>
+ <link>https://libgeos.org/usage/download/</link>
<pubDate>Mon, 04 Oct 2021 13:44:59 -0700</pubDate>
- <guid>http://libgeos.org/usage/download/</guid>
+ <guid>https://libgeos.org/usage/download/</guid>
<description>Release Date Release Download Link 2021/11/02 3.10.1 geos-3.10.1.tar.bz2 2021/11/01 3.9.2 geos-3.9.2.tar.bz2 2021/04/10 3.8.2 geos-3.8.2.tar.bz2 2019/10/04 3.7.3 geos-3.7.3.tar.bz2 2020/12/11 3.6.5 geos-3.6.5.tar.bz2 2019/10/04 3.5.2 geos-3.5.2.tar.bz2 Build From Source Build Requirements CMake 3.13 or later. C++11 compiler. We regularly test GCC, Clang and Microsoft Visual C++. Doxygen to build the API documentation. Build Builds with CMake are done “outside the tree” either in a build directory in the source tree or next to the tree.</description>
</item>
<item>
<title>Install Packages</title>
- <link>http://libgeos.org/usage/install/</link>
+ <link>https://libgeos.org/usage/install/</link>
<pubDate>Mon, 04 Oct 2021 13:44:59 -0700</pubDate>
- <guid>http://libgeos.org/usage/install/</guid>
+ <guid>https://libgeos.org/usage/install/</guid>
<description>Red Hat There is a GEOS package in the EPEL (Extra Packages for Enterprise Linux) repository.
# Add the EPEL repository yum -y install epel-release # Install the GEOS runtime and development packages rpm -Uvh geos geos-devel Ubuntu The Ubuntu GIS project maintains a collection of repositories with builds of common open source geospatial projects, including GEOS.
# Add the Ubuntu GIS PPA sudo apt-get install python-software-properties sudo add-apt-repository ppa:ubuntugis/ppa # Install the packages sudo apt-get install geos Debian The Debian GIS project maintains GEOS packages and pushes them into the appropriate Debian respositories.</description>
diff --git a/usage/install/index.html b/usage/install/index.html
index 43b5b6522..c72dbdd2a 100644
--- a/usage/install/index.html
+++ b/usage/install/index.html
@@ -48,7 +48,7 @@
<svg class="icon arrow-back"><use xlink:href="#arrow_back"></use></svg>
</label>
- <a class="gdoc-header__link" href="http://libgeos.org/">
+ <a class="gdoc-header__link" href="https://libgeos.org/">
<span class="gdoc-brand flex align-center">
<img class="gdoc-brand__img" src="/web-logo.png" alt="" width=38 height=38>
GEOS
@@ -604,7 +604,7 @@
-<div class="gdoc-page__anchorwrap"><h3 id="red-hat">Red Hat<a data-clipboard-text="http://libgeos.org/usage/install/#red-hat" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Red Hat" href="#red-hat"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+<div class="gdoc-page__anchorwrap"><h3 id="red-hat">Red Hat<a data-clipboard-text="https://libgeos.org/usage/install/#red-hat" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Red Hat" href="#red-hat"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>There is a GEOS package in the EPEL (Extra Packages for Enterprise Linux) repository.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="c1"># Add the EPEL repository</span>
yum -y install epel-release
@@ -612,7 +612,7 @@ yum -y install epel-release
<span class="c1"># Install the GEOS runtime and development packages</span>
rpm -Uvh geos geos-devel
-</code></pre></div><div class="gdoc-page__anchorwrap"><h3 id="ubuntu">Ubuntu<a data-clipboard-text="http://libgeos.org/usage/install/#ubuntu" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Ubuntu" href="#ubuntu"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+</code></pre></div><div class="gdoc-page__anchorwrap"><h3 id="ubuntu">Ubuntu<a data-clipboard-text="https://libgeos.org/usage/install/#ubuntu" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Ubuntu" href="#ubuntu"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>The <a href="https://wiki.ubuntu.com/UbuntuGIS">Ubuntu GIS</a> project maintains a collection of repositories with builds of common open source geospatial projects, including GEOS.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="c1"># Add the Ubuntu GIS PPA</span>
sudo apt-get install python-software-properties
@@ -620,20 +620,20 @@ sudo add-apt-repository ppa:ubuntugis/ppa
<span class="c1"># Install the packages</span>
sudo apt-get install geos
-</code></pre></div><div class="gdoc-page__anchorwrap"><h3 id="debian">Debian<a data-clipboard-text="http://libgeos.org/usage/install/#debian" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Debian" href="#debian"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+</code></pre></div><div class="gdoc-page__anchorwrap"><h3 id="debian">Debian<a data-clipboard-text="https://libgeos.org/usage/install/#debian" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Debian" href="#debian"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>The <a href="https://wiki.debian.org/DebianGis">Debian GIS</a> project maintains <a href="https://tracker.debian.org/pkg/geos">GEOS packages</a> and pushes them into the appropriate Debian respositories.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash">sudo apt-get install geos
-</code></pre></div><div class="gdoc-page__anchorwrap"><h3 id="amazon-linux">Amazon Linux<a data-clipboard-text="http://libgeos.org/usage/install/#amazon-linux" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Amazon Linux" href="#amazon-linux"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+</code></pre></div><div class="gdoc-page__anchorwrap"><h3 id="amazon-linux">Amazon Linux<a data-clipboard-text="https://libgeos.org/usage/install/#amazon-linux" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Amazon Linux" href="#amazon-linux"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>Amazon Linux is based on RH7, and can read from the EPEL repository. To enable using Amazon tools, use the <code>amazon-linux-extras</code> utility.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash">sudo yum install -y amazon-linux-extras
sudo amazon-linux-extras <span class="nb">enable</span> epel
sudo yum search geos
sudo yum install geos geos-devel
-</code></pre></div><div class="gdoc-page__anchorwrap"><h3 id="homebrew">Homebrew<a data-clipboard-text="http://libgeos.org/usage/install/#homebrew" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Homebrew" href="#homebrew"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+</code></pre></div><div class="gdoc-page__anchorwrap"><h3 id="homebrew">Homebrew<a data-clipboard-text="https://libgeos.org/usage/install/#homebrew" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Homebrew" href="#homebrew"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>For MacOS, GEOS can be installed using the <a href="https://brew.sh/">Homebrew</a> package repository, which downloads source packages and builds them in place using a recipe to ensure all packages integrate with each other nicely.</p>
<p>First <a href="https://brew.sh/">install Homebrew</a>. Then:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash">brew install geos
-</code></pre></div><div class="gdoc-page__anchorwrap"><h3 id="macports">Macports<a data-clipboard-text="http://libgeos.org/usage/install/#macports" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Macports" href="#macports"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
+</code></pre></div><div class="gdoc-page__anchorwrap"><h3 id="macports">Macports<a data-clipboard-text="https://libgeos.org/usage/install/#macports" class="gdoc-page__anchor gdoc-page__anchor--right clip" aria-label="Anchor Macports" href="#macports"><svg class="icon link"><use xlink:href="#link"></use></svg></a></h3></div>
<p>For MacOS, GEOS can be installed using the <a href="https://www.macports.org/">MacPorts</a> package repository, which downloads source packages and builds them in place using a recipe to ensure all packages integrate with each other nicely.</p>
<p>First <a href="https://www.macports.org/install.php">install MacPorts</a>. Then:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash">port install geos
-----------------------------------------------------------------------
Summary of changes:
404.html | 4 +-
categories/index.xml | 4 +-
development/ci_status/index.html | 4 +-
development/index.html | 18 +++---
development/index.xml | 12 ++--
development/psc/index.html | 4 +-
development/rfcs/index.html | 8 +--
development/rfcs/index.xml | 44 ++++++-------
development/rfcs/rfc01/index.html | 26 ++++----
development/rfcs/rfc02/index.html | 14 ++--
development/rfcs/rfc03/index.html | 18 +++---
development/rfcs/rfc04/index.html | 28 ++++----
development/rfcs/rfc05/index.html | 22 +++----
development/rfcs/rfc06/index.html | 6 +-
development/rfcs/rfc07/index.html | 2 +-
development/rfcs/rfc08/index.html | 10 +--
development/rfcs/rfc09/index.html | 2 +-
development/rfcs/rfc10/index.html | 2 +-
index.html | 10 +--
index.xml | 88 +++++++++++++-------------
posts/2021-10-01-geos-3-10-released/index.html | 4 +-
posts/index.html | 4 +-
posts/index.xml | 8 +--
posts/page/1/index.html | 2 +-
sitemap.xml | 58 ++++++++---------
specifications/geojson/index.html | 2 +-
specifications/index.html | 4 +-
specifications/index.xml | 16 ++---
specifications/wkb/index.html | 2 +-
specifications/wkt/index.html | 2 +-
tags/index.xml | 4 +-
usage/c_api/index.html | 22 +++----
usage/cpp_api/index.html | 4 +-
usage/download/index.html | 12 ++--
usage/doxygen/index.html | 4 +-
usage/index.html | 4 +-
usage/index.xml | 24 +++----
usage/install/index.html | 14 ++--
38 files changed, 258 insertions(+), 258 deletions(-)
hooks/post-receive
--
GEOS
More information about the geos-commits
mailing list