<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<div class="moz-forward-container"><br>
<br>
-------- Forwarded Message --------
<table cellpadding="0" cellspacing="0" border="0"
class="moz-email-headers-table">
<tbody>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">Subject:
</th>
<td>Re: OGC Compliance Renewal Notification - 60 Day
Expiration Notice</td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">Date: </th>
<td>Thu, 17 Apr 2025 09:43:25 +0300</td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">From: </th>
<td>Angelos Tzotsos <a class="moz-txt-link-rfc2396E" href="mailto:tzotsos@gmail.com"><tzotsos@gmail.com></a></td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">To: </th>
<td>Peter Smythe <a class="moz-txt-link-rfc2396E" href="mailto:gs@smythe.co.za"><gs@smythe.co.za></a></td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">CC: </th>
<td>OGC Compliance <a class="moz-txt-link-rfc2396E" href="mailto:compliance@ogc.org"><compliance@ogc.org></a>,
<a class="moz-txt-link-abbreviated" href="mailto:info@osgeo.org">info@osgeo.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:info@osgeo.org"><info@osgeo.org></a>, OSGeo Board
<a class="moz-txt-link-rfc2396E" href="mailto:board@lists.osgeo.org"><board@lists.osgeo.org></a>, Even Rouault
<a class="moz-txt-link-rfc2396E" href="mailto:even.rouault@spatialys.com"><even.rouault@spatialys.com></a>, Tom Kralidis
<a class="moz-txt-link-rfc2396E" href="mailto:tomkralidis@gmail.com"><tomkralidis@gmail.com></a>, Angelos Tzotsos
<a class="moz-txt-link-rfc2396E" href="mailto:gcpp.kalxas@gmail.com"><gcpp.kalxas@gmail.com></a>, Gobe Hobona (OGC)
<a class="moz-txt-link-rfc2396E" href="mailto:ghobona@ogc.org"><ghobona@ogc.org></a></td>
</tr>
</tbody>
</table>
<br>
<br>
Dear Peter,<br>
<br>
With the help from Gobe, we have identified the standards where
GeoServer<br>
can be a Reference Implementation (and get certified for free)
under the<br>
OGC/OSGeo MOU.<br>
<br>
The list is the following:<br>
WMTS 1.0.0<br>
GeoTiff 1.1<br>
WCS 1.0<br>
WCS 1.1.1<br>
WCS 2.0.1<br>
WFS 1.0.0<br>
<br>
For the following standards, certification is not free, since OGC
has<br>
reached the limit of free waivers for Reference Implementations:<br>
GeoPackage 1.2<br>
WMS 1.1.1<br>
WMS 1.3.0<br>
OGC API - Features 1.0<br>
WFS 1.1.0<br>
WFS 2.0<br>
<br>
According to <a class="moz-txt-link-freetext" href="https://www.ogc.org/how-our-compliance-program-works/">https://www.ogc.org/how-our-compliance-program-works/</a>
we will<br>
need to pay 150$ per certification, a total of 900$<br>
<br>
Best regards,<br>
Angelos<br>
<br>
On Tue, Apr 15, 2025 at 10:52 AM Gobe Hobona (OGC)
<a class="moz-txt-link-rfc2396E" href="mailto:ghobona@ogc.org"><ghobona@ogc.org></a> wrote:<br>
<br>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">Hi Peter,
I am in contact with Angelos regarding certification of GeoServer 2.27.
The latest correspondence was yesterday.
I will copy you into further correspondence.
Regards,
Gobe
*From: *Peter Smythe <a class="moz-txt-link-rfc2396E" href="mailto:gs@smythe.co.za"><gs@smythe.co.za></a>
*Date: *Tuesday, 15 April 2025 at 08:37
*To: *Angelos Tzotsos <a class="moz-txt-link-rfc2396E" href="mailto:gcpp.kalxas@gmail.com"><gcpp.kalxas@gmail.com></a>, Gobe Hobona (OGC) <
<a class="moz-txt-link-abbreviated" href="mailto:ghobona@ogc.org">ghobona@ogc.org</a>>
*Cc: *Micah Brachman <a class="moz-txt-link-rfc2396E" href="mailto:mbrachman@ogc.org"><mbrachman@ogc.org></a>, OGC Compliance <
<a class="moz-txt-link-abbreviated" href="mailto:compliance@ogc.org">compliance@ogc.org</a>>, <a class="moz-txt-link-abbreviated" href="mailto:info@osgeo.org">info@osgeo.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:info@osgeo.org"><info@osgeo.org></a>, OSGeo Board <
<a class="moz-txt-link-abbreviated" href="mailto:board@lists.osgeo.org">board@lists.osgeo.org</a>>, Even Rouault <a class="moz-txt-link-rfc2396E" href="mailto:even.rouault@spatialys.com"><even.rouault@spatialys.com></a>, Tom
Kralidis <a class="moz-txt-link-rfc2396E" href="mailto:tomkralidis@gmail.com"><tomkralidis@gmail.com></a>, Angelos Tzotsos <a class="moz-txt-link-rfc2396E" href="mailto:tzotsos@osgeo.org"><tzotsos@osgeo.org></a>
*Subject: *Re: OGC Compliance Renewal Notification - 60 Day Expiration
Notice
Hi all, adding Gobe
I am trying to find out what the status of the GeoServer 2.27.0
certification is.
I received this automated response:
Changed Employment - Please update your address book for Micah Brachman
Thank you for your email. Micah Brachman no longer works for the OGC.
For all your questions or inquiries regarding the
Standards Program, please contact Scott Simmons (ssimmons AT ogc.org),
for the
Compliance Program, please contact Gobe Hobona (ghobona AT ogc.org).
I also know that Angelos has said that, with a family member in hospital,
he will not be quick to respond.
I am about to go on leave for 2 weeks from Friday, but I need to report
back to the GeoServer PSC.
Could someone please give me an update of who is driving this forward,
what still needs to be done, timelines (if possible) and if there is any
information that I can supply before I disappear?
Thank you very much.
Peter
GeoServer PSC
AWS Solutions Architect
<a class="moz-txt-link-freetext" href="https://github.com/petersmythe">https://github.com/petersmythe</a>
On Sat, 12 Apr 2025 at 16:38, Peter Smythe <a class="moz-txt-link-rfc2396E" href="mailto:gs@smythe.co.za"><gs@smythe.co.za></a> wrote:
Hi Micah, Angelos
Could I ask, is there any update on this GeoServer certification? Would it
make it simpler to just focus on the certification of 2.27.0, and discuss
any reference implementation later? Sorry, I'm not 100% sure of the whole
arrangement/MoU.
FYI, our (current) intention is to request certification twice a year,
whenever we have a .0 release. <a class="moz-txt-link-freetext" href="https://geoserver.org/roadmap">https://geoserver.org/roadmap</a> Is that
feasible/reasonable?
Thank you
Peter
GeoServer PSC
On Tue, 08 Apr 2025, 07:29 Angelos Tzotsos, <a class="moz-txt-link-rfc2396E" href="mailto:gcpp.kalxas@gmail.com"><gcpp.kalxas@gmail.com></a> wrote:
Dear Micah,
We have received a request from the GeoServer PSC to also include
GeoServer in the compliance program.
We now have CITE tests passing for several standards:
<a class="moz-txt-link-freetext" href="https://git.osgeo.org/gitea/osgeo/standards-committee/issues/10#issuecomment-13445">https://git.osgeo.org/gitea/osgeo/standards-committee/issues/10#issuecomment-13445</a>
My questions are:
Should I include all the previous projects as well in the new
certification application?
If we ask GeoServer to become reference implementation for all these
standards is there a cost?
Best regards,
Angelos
On 1/23/25 16:17, Micah Brachman wrote:
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">Excellent -- thanks again for your support of the compliance program!
Micah Brachman, PhD
Community Manager | Open Geospatial Consortium (OGC)
+1 (508) 655-5858 ex 706
mbrachman<a class="moz-txt-link-rfc2396E" href="mailto:mbrachman@ogc.org"><mailto:mbrachman@ogc.org></a>@ogc.org<a class="moz-txt-link-rfc2396E" href="mailto:mbrachman@ogc.org"><mailto:mbrachman@ogc.org></a> |
</pre></blockquote>ogc.org<a class="moz-txt-link-rfc2396E" href="http://ogc.org/"><http://ogc.org/></a> | @opengeospatial
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
[<a class="moz-txt-link-freetext" href="cid:911e275f-ef14-4789-a8ae-c16831bb67ef">cid:911e275f-ef14-4789-a8ae-c16831bb67ef</a>]<
</pre></blockquote><a class="moz-txt-link-freetext" href="https://outlook.office.com/bookwithme/user/471ab05d3c7047e0bde9468e040936ac@ogc.org?anonymous&ep=bwmEmailSignature">https://outlook.office.com/bookwithme/user/471ab05d3c7047e0bde9468e040936ac@ogc.org?anonymous&ep=bwmEmailSignature</a>>
Book time to meet with me<
<a class="moz-txt-link-freetext" href="https://outlook.office.com/bookwithme/user/471ab05d3c7047e0bde9468e040936ac@ogc.org?anonymous&ep=bwmEmailSignature">https://outlook.office.com/bookwithme/user/471ab05d3c7047e0bde9468e040936ac@ogc.org?anonymous&ep=bwmEmailSignature</a>
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
________________________________
From: Angelos Tzotsos <a class="moz-txt-link-rfc2396E" href="mailto:tzotsos@osgeo.org"><tzotsos@osgeo.org></a>
Sent: Wednesday, January 22, 2025 11:43 PM
To: Micah Brachman <a class="moz-txt-link-rfc2396E" href="mailto:mbrachman@ogc.org"><mbrachman@ogc.org></a>
Cc: Angelos Tzotsos <a class="moz-txt-link-rfc2396E" href="mailto:gcpp.kalxas@gmail.com"><gcpp.kalxas@gmail.com></a>; Even Rouault <
</pre></blockquote><a class="moz-txt-link-abbreviated" href="mailto:even.rouault@spatialys.com">even.rouault@spatialys.com</a>>; OGC Compliance <a class="moz-txt-link-rfc2396E" href="mailto:compliance@ogc.org"><compliance@ogc.org></a>;
<a class="moz-txt-link-abbreviated" href="mailto:info@osgeo.org">info@osgeo.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:info@osgeo.org"><info@osgeo.org></a>; OSGeo Board <a class="moz-txt-link-rfc2396E" href="mailto:board@lists.osgeo.org"><board@lists.osgeo.org></a>; Tom
Kralidis <a class="moz-txt-link-rfc2396E" href="mailto:tomkralidis@gmail.com"><tomkralidis@gmail.com></a>
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">Subject: Re: OGC Compliance Renewal Notification - 60 Day Expiration
</pre></blockquote>Notice
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
Hi Micah,
Thank you for reviewing the submission and accepting our application.
The list looks good.
Best regards,
Angelos
On Thu, Jan 23, 2025 at 12:38 AM Micah Brachman <<a class="moz-txt-link-abbreviated" href="mailto:mbrachman@ogc.org">mbrachman@ogc.org</a>
</pre></blockquote><a class="moz-txt-link-rfc2396E" href="mailto:mbrachman@ogc.org"><mailto:mbrachman@ogc.org></a>> wrote:
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">Hi Angelos,
Thank you — I've approved your submission and you can see the updated
</pre></blockquote>listings at this link<
<a class="moz-txt-link-freetext" href="https://portal.ogc.org/public_ogc/compliance/compliant.php?display_opt=1&org_match=Open%20Source%20Geospatial%20Foundation">https://portal.ogc.org/public_ogc/compliance/compliant.php?display_opt=1&org_match=Open%20Source%20Geospatial%20Foundation</a>
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">.
Hopefully I've addressed all of your questions/requests below with this
</pre></blockquote>updated listing, if I missed anything please let me know. It did seem
like you submitted pygeoapi 0.19 tests for OGC API - EDR so I updated that
listing as well.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
Thanks again for your support of the compliance program, and please feel
</pre></blockquote>free to book time with me using the link below if you'd like to discuss
further.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
Best,
Micah
Micah Brachman, PhD
Community Manager | Open Geospatial Consortium (OGC)
+1 (508) 655-5858 ex 706
mbrachman<a class="moz-txt-link-rfc2396E" href="mailto:mbrachman@ogc.org"><mailto:mbrachman@ogc.org></a>@ogc.org<a class="moz-txt-link-rfc2396E" href="mailto:mbrachman@ogc.org"><mailto:mbrachman@ogc.org></a> |
</pre></blockquote>ogc.org<a class="moz-txt-link-rfc2396E" href="http://ogc.org/"><http://ogc.org/></a> | @opengeospatial
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
[<a class="moz-txt-link-freetext" href="cid:ii_194921c7027982c5fce1">cid:ii_194921c7027982c5fce1</a>]<
</pre></blockquote><a class="moz-txt-link-freetext" href="https://outlook.office.com/bookwithme/user/471ab05d3c7047e0bde9468e040936ac@ogc.org?anonymous&ep=bwmEmailSignature">https://outlook.office.com/bookwithme/user/471ab05d3c7047e0bde9468e040936ac@ogc.org?anonymous&ep=bwmEmailSignature</a>>
Book time to meet with me<
<a class="moz-txt-link-freetext" href="https://outlook.office.com/bookwithme/user/471ab05d3c7047e0bde9468e040936ac@ogc.org?anonymous&ep=bwmEmailSignature">https://outlook.office.com/bookwithme/user/471ab05d3c7047e0bde9468e040936ac@ogc.org?anonymous&ep=bwmEmailSignature</a>
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
________________________________
From: Angelos Tzotsos <<a class="moz-txt-link-abbreviated" href="mailto:tzotsos@osgeo.org">tzotsos@osgeo.org</a><a class="moz-txt-link-rfc2396E" href="mailto:tzotsos@osgeo.org"><mailto:tzotsos@osgeo.org></a>>
Sent: Sunday, January 5, 2025 6:18 AM
To: Micah Brachman <<a class="moz-txt-link-abbreviated" href="mailto:mbrachman@ogc.org">mbrachman@ogc.org</a><a class="moz-txt-link-rfc2396E" href="mailto:mbrachman@ogc.org"><mailto:mbrachman@ogc.org></a>>
Cc: Angelos Tzotsos <<a class="moz-txt-link-abbreviated" href="mailto:gcpp.kalxas@gmail.com">gcpp.kalxas@gmail.com</a><a class="moz-txt-link-rfc2396E" href="mailto:gcpp.kalxas@gmail.com"><mailto:gcpp.kalxas@gmail.com></a>>;
</pre></blockquote>Even Rouault <<a class="moz-txt-link-abbreviated" href="mailto:even.rouault@spatialys.com">even.rouault@spatialys.com</a><a class="moz-txt-link-rfc2396E" href="mailto:even.rouault@spatialys.com"><mailto:even.rouault@spatialys.com></a>>;
OGC Compliance <<a class="moz-txt-link-abbreviated" href="mailto:compliance@ogc.org">compliance@ogc.org</a><a class="moz-txt-link-rfc2396E" href="mailto:compliance@ogc.org"><mailto:compliance@ogc.org></a>>;
<a class="moz-txt-link-abbreviated" href="mailto:info@osgeo.org">info@osgeo.org</a><a class="moz-txt-link-rfc2396E" href="mailto:info@osgeo.org"><mailto:info@osgeo.org></a> <<a class="moz-txt-link-abbreviated" href="mailto:info@osgeo.org">info@osgeo.org</a><a class="moz-txt-link-rfc2396E" href="mailto:info@osgeo.org"><mailto:
info@osgeo.org></a>>; OSGeo Board <<a class="moz-txt-link-abbreviated" href="mailto:board@lists.osgeo.org">board@lists.osgeo.org</a><a class="moz-txt-link-rfc2396E" href="mailto:board@lists.osgeo.org"><mailto:
board@lists.osgeo.org></a>>; Tom Kralidis <<a class="moz-txt-link-abbreviated" href="mailto:tomkralidis@gmail.com">tomkralidis@gmail.com</a><a class="moz-txt-link-rfc2396E" href="mailto:tomkralidis@gmail.com"><mailto:
tomkralidis@gmail.com></a>>
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">Subject: Re: OGC Compliance Renewal Notification - 60 Day Expiration
</pre></blockquote>Notice
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
Dear Micah,
We have gathered all compliance tests and we are ready to submit.
Here is our status list, I would like to ask some questions:
Under the OSGeo organization we have several products listed in the OGC
</pre></blockquote>compliance page.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">1. For MapServer we have versions 5.0, 6.0, 6.2, 6.4, 7.0, 8.2
Only 6.2 has passed certification in the past so I assume we keep that
</pre></blockquote>listed.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">I added the latest 8.2 release that includes support for OGC API
</pre></blockquote>Features (no cite tests yet).
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
2. For pygeoapi we have versions 0.7, 0.9, 0.17 and 0.19
We have provided new compliance tests against the latest 0.19 version
</pre></blockquote>and we would like to ask to move reference implementation status (OGC API -
Features, OGC API - Processes and OGC API - Tiles) to that version . Is
that possible?
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">We did not manage to run new tests for OGC API - EDR so we would like to
</pre></blockquote>keep RI to the previous pygeoapi 0.9 version for now.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
3. For pycsw we have versions 1.1, 2.0, 2.2, 2.4 and 2.6
We provided certification tests against the latest version and we would
</pre></blockquote>like to keep that version as CSW 2.0.2 and 3.0.0 reference implementation.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">OGC API Records is implemented in pycsw 3.0.0 (not yet released as
</pre></blockquote>final). We are waiting for the specification to be finalized and looking
forward to testing against a Records cite test.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
4. GDAL/OGR we have versions 1.11, 2.1, 2.4, 3.0 and now 3.10
We provided certification tests against the latest version (3.10) and we
</pre></blockquote>would like to ask to move all reference implementation status to that
version. Is that possible?
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
5. For GeoServer we have version 2.24
We do not have new compliance tests available so we would like to keep
</pre></blockquote>version 2.24 listed.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
Best regards,
Angelos
On Wed, Nov 13, 2024 at 7:09 PM Micah Brachman <<a class="moz-txt-link-abbreviated" href="mailto:mbrachman@ogc.org">mbrachman@ogc.org</a>
</pre></blockquote><a class="moz-txt-link-rfc2396E" href="mailto:mbrachman@ogc.org"><mailto:mbrachman@ogc.org></a>> wrote:
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
That sounds great, Angelos – please let me know if you have any
</pre></blockquote>questions or need assistance.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
From: Angelos Tzotsos <<a class="moz-txt-link-abbreviated" href="mailto:gcpp.kalxas@gmail.com">gcpp.kalxas@gmail.com</a><mailto:
</pre></blockquote><a class="moz-txt-link-abbreviated" href="mailto:gcpp.kalxas@gmail.com">gcpp.kalxas@gmail.com</a>>>
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">Date: Wednesday, November 13, 2024 at 6:39 AM
To: Micah Brachman <<a class="moz-txt-link-abbreviated" href="mailto:mbrachman@ogc.org">mbrachman@ogc.org</a><a class="moz-txt-link-rfc2396E" href="mailto:mbrachman@ogc.org"><mailto:mbrachman@ogc.org></a>>, Even
</pre></blockquote>Rouault <<a class="moz-txt-link-abbreviated" href="mailto:even.rouault@spatialys.com">even.rouault@spatialys.com</a><a class="moz-txt-link-rfc2396E" href="mailto:even.rouault@spatialys.com"><mailto:even.rouault@spatialys.com></a>>,
Compliance <<a class="moz-txt-link-abbreviated" href="mailto:compliance@ogc.org">compliance@ogc.org</a><a class="moz-txt-link-rfc2396E" href="mailto:compliance@ogc.org"><mailto:compliance@ogc.org></a>>, <a class="moz-txt-link-abbreviated" href="mailto:info@osgeo.org">info@osgeo.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:info@osgeo.org"><mailto:info@osgeo.org></a> <<a class="moz-txt-link-abbreviated" href="mailto:info@osgeo.org">info@osgeo.org</a><a class="moz-txt-link-rfc2396E" href="mailto:info@osgeo.org"><mailto:info@osgeo.org></a>>
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">Cc: Angelos Tzotsos <<a class="moz-txt-link-abbreviated" href="mailto:tzotsos@osgeo.org">tzotsos@osgeo.org</a><a class="moz-txt-link-rfc2396E" href="mailto:tzotsos@osgeo.org"><mailto:tzotsos@osgeo.org></a>>,
</pre></blockquote>OSGeo Board <<a class="moz-txt-link-abbreviated" href="mailto:board@lists.osgeo.org">board@lists.osgeo.org</a><a class="moz-txt-link-rfc2396E" href="mailto:board@lists.osgeo.org"><mailto:board@lists.osgeo.org></a>>
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">Subject: Re: OGC Compliance Renewal Notification - 60 Day Expiration
</pre></blockquote>Notice
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
Hi Micah,
Thank you for the update.
I am going to submit once I gather info from all projects involved.
Best,
Angelos
On 11/13/24 02:48, Micah Brachman wrote:
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">Thanks for sharing these, Even.
Angelos-
I can see that you have submitted the last few compliance results. Are
</pre></blockquote></pre></blockquote>you planning to submit these as well?
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">
Best,
Micah
Micah Brachman, PhD
Community Manager | Open Geospatial Consortium (OGC)
+1 (508) 655-5858<a class="moz-txt-link-rfc2396E" href="tel:+15086555858"><tel:+15086555858></a> ex 706
mbrachman<a class="moz-txt-link-rfc2396E" href="mailto:mbrachman@ogc.org"><mailto:mbrachman@ogc.org></a>@ogc.org<<a class="moz-txt-link-freetext" href="mailto:mbrachman@ogc.org">mailto:mbrachman@ogc.org</a>
</pre></blockquote></pre></blockquote><a class="moz-txt-link-rfc2396E" href="mailto:mbrachman@ogc.org%3e@ogc.org%3cmailto:mbrachman@ogc.org"><mailto:mbrachman@ogc.org%3e@ogc.org%3cmailto:mbrachman@ogc.org></a>> |
ogc.org<a class="moz-txt-link-rfc2396E" href="http://ogc.org"><http://ogc.org></a><a class="moz-txt-link-rfc2396E" href="http://ogc.org/"><http://ogc.org/></a> | @opengeospatial
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">
From: Even Rouault <<a class="moz-txt-link-abbreviated" href="mailto:even.rouault@spatialys.com">even.rouault@spatialys.com</a><mailto:
</pre></blockquote></pre></blockquote><a class="moz-txt-link-abbreviated" href="mailto:even.rouault@spatialys.com">even.rouault@spatialys.com</a>>>
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">Date: Monday, November 11, 2024 at 3:56 PM
To: Compliance <<a class="moz-txt-link-abbreviated" href="mailto:compliance@ogc.org">compliance@ogc.org</a><a class="moz-txt-link-rfc2396E" href="mailto:compliance@ogc.org"><mailto:compliance@ogc.org></a>>,
</pre></blockquote></pre></blockquote><a class="moz-txt-link-abbreviated" href="mailto:info@osgeo.org">info@osgeo.org</a><a class="moz-txt-link-rfc2396E" href="mailto:info@osgeo.org"><mailto:info@osgeo.org></a> <<a class="moz-txt-link-abbreviated" href="mailto:info@osgeo.org">info@osgeo.org</a><a class="moz-txt-link-rfc2396E" href="mailto:info@osgeo.org"><mailto:
info@osgeo.org></a>>
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">Cc: Angelos Tzotsos <<a class="moz-txt-link-abbreviated" href="mailto:tzotsos@osgeo.org">tzotsos@osgeo.org</a><a class="moz-txt-link-rfc2396E" href="mailto:tzotsos@osgeo.org"><mailto:tzotsos@osgeo.org></a>>,
</pre></blockquote></pre></blockquote>OSGeo Board <<a class="moz-txt-link-abbreviated" href="mailto:board@lists.osgeo.org">board@lists.osgeo.org</a><a class="moz-txt-link-rfc2396E" href="mailto:board@lists.osgeo.org"><mailto:board@lists.osgeo.org></a>>,
Angelos Tzotsos <<a class="moz-txt-link-abbreviated" href="mailto:gcpp.kalxas@gmail.com">gcpp.kalxas@gmail.com</a><a class="moz-txt-link-rfc2396E" href="mailto:gcpp.kalxas@gmail.com"><mailto:gcpp.kalxas@gmail.com></a>>
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">Subject: Re: OGC Compliance Renewal Notification - 60 Day Expiration
</pre></blockquote></pre></blockquote>Notice
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">
Hi,
here are the results of running CITE tests for GDAL *3.10* :
- KML 2.2: s0028, s0029, s0030, s0031
- GeoTIFF 1.1: s0032 and s0033
- GMLJP2 v2: s0034
- GeoPackage 1.2: s0035, s0036, s0037 and s0038
Even
Le 10/11/2024 à 16:07, <a class="moz-txt-link-abbreviated" href="mailto:compliance@ogc.org">compliance@ogc.org</a><<a class="moz-txt-link-freetext" href="mailto:compliance@ogc.org">mailto:compliance@ogc.org</a>
</pre></blockquote><a class="moz-txt-link-rfc2396E" href="mailto:compliance@ogc.org"><mailto:compliance@ogc.org></a> a écrit :
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">Open Source Geospatial Foundation
This is an automated email to inform you that your OGC-certified
</pre></blockquote></pre></blockquote>compliance license(s) for the following products are due to be renewed by
January 9th, 2025. After that date, your products will no longer be listed
as certified OGC compliant and you may not claim that they are compliant.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">
Since you have reference implementations in your listings please be
</pre></blockquote></pre></blockquote>aware of the following:
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">
* You need to retest if you want to continue being listed as a
</pre></blockquote></pre></blockquote>reference implementation.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre"> * If you want to provide a new version as a reference
</pre></blockquote></pre></blockquote>implementation you need to test that new version. The older version will no
longer hold the status of reference implementations.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre"> * If you want to continue displaying the certification for the
</pre></blockquote></pre></blockquote>older version of your product, then you will be required to pay for the
certification.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">
Additional expiration warnings may be sent to you 1 month and 2 weeks
</pre></blockquote></pre></blockquote>prior to expiration, please begin the renewal process as soon as possible.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">
We invite you to easily renew online in our implementation portal:
</pre></blockquote></pre></blockquote><a class="moz-txt-link-freetext" href="https://www.ogc.org/resource/products/registration">https://www.ogc.org/resource/products/registration</a>
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">
As a reminder, the account used to manage your certification listings
</pre></blockquote></pre></blockquote>is: osgeo (<a class="moz-txt-link-abbreviated" href="mailto:info@osgeo.org">info@osgeo.org</a><a class="moz-txt-link-rfc2396E" href="mailto:info@osgeo.org"><mailto:info@osgeo.org></a><<a class="moz-txt-link-freetext" href="mailto:info@osgeo.org">mailto:info@osgeo.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:info@osgeo.org"><mailto:info@osgeo.org></a>>)
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">
If you have any questions please send an email to <a class="moz-txt-link-abbreviated" href="mailto:compliance@ogc.org">compliance@ogc.org</a>
</pre></blockquote></pre></blockquote><a class="moz-txt-link-rfc2396E" href="mailto:compliance@ogc.org"><mailto:compliance@ogc.org></a><a class="moz-txt-link-rfc2396E" href="mailto:compliance@ogc.org"><mailto:compliance@ogc.org></a>. The OGC
compliance team will be more than glad to help you.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">
________________________________
Current OGC-Compliant Listings
GDAL/OGR 1.11
Specification(s)
Original Certification
OGC KML 2.2.0
(OGC Reference Implementation)
2014-08-15
OGC KML (Level 2) 2.2.0
(OGC Reference Implementation)
2014-08-15
OGC KML (Level 3) 2.2.0
(OGC Reference Implementation)
2014-08-15
GDAL/OGR 3.0.0
Specification(s)
Original Certification
OGC GeoTIFF Standard 1.1
(OGC Reference Implementation)
2020-07-29
OGC KML 2.2.0
(OGC Reference Implementation)
2020-01-09
OGC KML (Level 2) 2.2.0
(OGC Reference Implementation)
2020-01-09
OGC® GeoPackage Encoding Standard 1.2
(OGC Reference Implementation)
2022-01-09
OGC® GeoPackage Encoding Standard: Extension Mechanism 1.2
(OGC Reference Implementation)
2022-01-09
OGC® GeoPackage Encoding Standard: Features 1.2
(OGC Reference Implementation)
2022-01-09
OGC® GeoPackage Encoding Standard: Metadata 1.2
(OGC Reference Implementation)
2022-01-09
OGC® GeoPackage Encoding Standard: RTree Spatial Indexes 1.2
(OGC Reference Implementation)
2022-01-09
OGC® GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core 2.0
(OGC Reference Implementation)
2020-04-28
GeoServer 2.24
Specification(s)
Original Certification
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard 1.0
(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Acquisition
</pre></blockquote></pre></blockquote>Information 1.0
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Acquisition
</pre></blockquote></pre></blockquote>Parameters 1.0
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Data
</pre></blockquote></pre></blockquote>Identification 1.0
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Earth
</pre></blockquote></pre></blockquote>Observation 1.0
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Earth
</pre></blockquote></pre></blockquote>Observation Collection 1.0
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Geometry 1.0
(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Links 1.0
(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Metadata
</pre></blockquote></pre></blockquote>Information 1.0
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Offering 1.0
(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Product
</pre></blockquote></pre></blockquote>Information 1.0
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Properties 1.0
(OGC Reference Implementation)
2024-01-09
MapServer 6.2
Specification(s)
Original Certification
OpenGIS Web Map Service (WMS) Implementation Specification 1.3.0
(OGC Reference Implementation)
2016-01-12
pycsw 2.4.0
Specification(s)
Original Certification
OpenGIS Catalogue Service Implementation Specification [Catalogue
</pre></blockquote></pre></blockquote>Service for the Web] 2.0.2
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">(OGC Reference Implementation)
2020-01-09
pycsw 2.6.0
Specification(s)
Original Certification
OGC GeoRSS Encoding Standard 1.0
(OGC Reference Implementation)
2022-04-28
OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding 3.0
(OGC Reference Implementation)
2021-01-09
OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding
</pre></blockquote></pre></blockquote>(OpenSearch) 3.0
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">(OGC Reference Implementation)
2021-01-09
OpenGIS Catalogue Service Implementation Specification 2.0.2
(OGC Reference Implementation)
2021-01-09
OpenGIS Catalogue Service Implementation Specification [Catalogue
</pre></blockquote></pre></blockquote>Service for the Web] 2.0.2
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">(OGC Reference Implementation)
2021-01-09
pygeoapi 0.17.0
Specification(s)
Original Certification
OGC API - Processes - Part 1: Core 1.0
2024-07-24
pygeoapi 0.9.0
Specification(s)
Original Certification
OGC API - Environmental Data Retrieval Standard 1.0.1
(OGC Reference Implementation)
2022-11-10
OGC API - Environmental Data Retrieval Standard: Collections 1.0.1
(OGC Reference Implementation)
2022-11-10
OGC API - Environmental Data Retrieval Standard: JSON 1.0.1
(OGC Reference Implementation)
2022-11-10
OGC API - Features - Part 1: Core 1.0
(OGC Reference Implementation)
2021-01-09
OGC API - Tiles - Part 1: Core 1.0
(OGC Reference Implementation)
2024-02-08
OGC API - Tiles - Part 1: GeoDataTilesets 1.0
(OGC Reference Implementation)
2024-02-08
OGC API - Tiles - Part 1: TilesetsList 1.0
(OGC Reference Implementation)
2024-02-08
________________________________
OGC Privacy Policy<a class="moz-txt-link-rfc2396E" href="http://www.ogc.org/ogc/policies/privacy"><http://www.ogc.org/ogc/policies/privacy></a>
--
<a class="moz-txt-link-freetext" href="http://www.spatialys.com">http://www.spatialys.com</a>
My software is free, but my time generally not.
Butcher of all kinds of standards, open or closed formats. At the end,
</pre></blockquote></pre></blockquote>this is just about bytes.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"><blockquote
type="cite"><pre wrap="" class="moz-quote-pre">
</pre></blockquote>
--
Angelos Tzotsos, PhD
President, Board of Directors
Open Source Geospatial Foundation
<a class="moz-txt-link-freetext" href="https://www.osgeo.org/member/angelos-tzotsos/">https://www.osgeo.org/member/angelos-tzotsos/</a>
--
Angelos Tzotsos, PhD
President, Board of Directors
Open Source Geospatial Foundation
<a class="moz-txt-link-freetext" href="https://www.osgeo.org/member/angelos-tzotsos/">https://www.osgeo.org/member/angelos-tzotsos/</a>
--
Angelos Tzotsos, PhD
President, Board of Directors
Open Source Geospatial Foundation
<a class="moz-txt-link-freetext" href="https://www.osgeo.org/member/angelos-tzotsos/">https://www.osgeo.org/member/angelos-tzotsos/</a>
</pre></blockquote>
--
Angelos Tzotsos, PhD
President, Board of Directors
Open Source Geospatial Foundation
<a class="moz-txt-link-freetext" href="https://www.osgeo.org/member/angelos-tzotsos/">https://www.osgeo.org/member/angelos-tzotsos/</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature">--
Angelos Tzotsos, PhD
President, Board of Directors
Open Source Geospatial Foundation
<a class="moz-txt-link-freetext" href="https://www.osgeo.org/member/angelos-tzotsos/">https://www.osgeo.org/member/angelos-tzotsos/</a>
</pre>
</div>
</body>
</html>