<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">I’m mainly a lurker on these exchanges. But from afar it seems like there are three key underlying efforts in the whole spatial data and analysis world – gdal, geos, and proj. It’s really good to see cooperation (and funding!) for the gdal
and geos part of the triumvirate. Would it make sense to see about adding proj to it?
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="text-align:justify">Gerald C. Nelson<o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify">Professor Emeritus, UIUC<o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify">+1 217-390-7888 (cell)<o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify">+1 970-639-2079 (land line)<o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify">Skype: jerrynelson<o:p></o:p></p>
</div>
<p class="MsoNormal">http://bit.ly/1arho7d<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">gdal-dev <gdal-dev-bounces@lists.osgeo.org> on behalf of Daniel Baston <dbaston@gmail.com><br>
<b>Date: </b>Thursday, February 17, 2022 at 10:47 AM<br>
<b>To: </b>GEOS Development List <geos-devel@lists.osgeo.org><br>
<b>Cc: </b>gdal dev <gdal-dev@lists.osgeo.org><br>
<b>Subject: </b>Re: [gdal-dev] [geos-devel] GEOS Maintenance Grant<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">Thank you, all. I'm honored by your support.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Please don't hesitate to open issues on the GEOS GitHub page to share any ideas you have about how GEOS can better support GDAL and friends.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Dan<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Thu, Feb 17, 2022 at 11:13 AM Howard Butler <<a href="mailto:howard@hobu.co">howard@hobu.co</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">Declaring this motion passed with +1's from<br>
<br>
DanielM, EvenR, NormanB, TamasS, HowardB, MateuszL, FrankW, KurtS, and SeanG<br>
<br>
The GDAL PSC is fully delegating these resources to the GEOS PSC to use as it sees fit. Paul Ramsey has agreed to be the administrative contact for the GEOS PSC, and will coordinate the effort in regards to payment sign-off, work task development, rate negotiation,
and reporting to the GDAL PSC. <br>
<br>
Howard<br>
<br>
PS: As a member of both PSCs, I will abstain from any funding or resource direction votes in the GEOS PSC to avoid any potential conflict.<br>
<br>
> On Feb 15, 2022, at 9:37 AM, Howard Butler <<a href="mailto:howard@hobu.co" target="_blank">howard@hobu.co</a>> wrote:<br>
> <br>
> GDAL PSC,<br>
> <br>
> When we wrote the GDAL RFCs on sponsorship, we provided an escape clause to allow us to direct resources to other projects upon which GDAL depends. Our sponsorship numbers are still increasing, which provides us an opportunity to directly support some of
those projects, and one of them is obviously GEOS. GEOS provides all of the geometry algebra support for GDAL/OGR and many other open source geospatial softwares including Shapely, PostGIS, GeoPandas, MapServer, and more.
<br>
> <br>
> Dan Baston of the GEOS PSC has been identified as the developer with capacity and interest in the next year to take on GEOS development on APIs and performance, which he has a long history of doing for the project. This support should allow him to work longer,
multi-release upgrades that will provide strong performance and convenience benefits for the project.<br>
> <br>
> I motion to provide the GEOS PSC with a $50,000 USD grant to address performance, API, and other work that does not attract directed funding in GEOS. The GEOS PSC will be responsible for coordinating work tasks, rates, and development timelines. Howard Butler
or Even Rouault of the GDAL NumFocus liaison team will coordinate dispersement as directed by the GEOS PSC and NumFocus rules.<br>
> <br>
> Thank you again to the GDAL Sponsors <a href="https://gdal.org/sponsors/index.html" target="_blank">
https://gdal.org/sponsors/index.html</a> who have made this kind of grant possible. A better GEOS makes for a better GDAL.<br>
> <br>
> Howard<br>
> <br>
<br>
_______________________________________________<br>
geos-devel mailing list<br>
<a href="mailto:geos-devel@lists.osgeo.org" target="_blank">geos-devel@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geos-devel" target="_blank">https://lists.osgeo.org/mailman/listinfo/geos-devel</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</body>
</html>