From gcpp.kalxas at gmail.com Mon Apr 7 22:29:21 2025 From: gcpp.kalxas at gmail.com (Angelos Tzotsos) Date: Tue, 8 Apr 2025 08:29:21 +0300 Subject: [Board] OGC Compliance Renewal Notification - 60 Day Expiration Notice In-Reply-To: References: <1731251221.515743.10416.nullmailer@tic.ogcinc.net> <79edb085-2234-4739-af72-a7f8351b574f@spatialys.com> <948b11dd-1239-474f-ae81-9bcc61567bd7@gmail.com>

Message-ID: 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: https://git.osgeo.org/gitea/osgeo/standards-committee/issues/10#issuecomment-13445 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: > 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@ogc.org | ogc.org | @opengeospatial > > [cid:911e275f-ef14-4789-a8ae-c16831bb67ef] Book time to meet with me > ________________________________ > From: Angelos Tzotsos > Sent: Wednesday, January 22, 2025 11:43 PM > To: Micah Brachman > Cc: Angelos Tzotsos ; Even Rouault ; OGC Compliance ; info at osgeo.org ; OSGeo Board ; Tom Kralidis > Subject: Re: OGC Compliance Renewal Notification - 60 Day Expiration Notice > > 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 > wrote: > Hi Angelos, > > Thank you ? I've approved your submission and you can see the updated listings at this link. > > Hopefully I've addressed all of your questions/requests below with this 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. > > Thanks again for your support of the compliance program, and please feel free to book time with me using the link below if you'd like to discuss further. > > Best, > > Micah > > > > > > Micah Brachman, PhD > > Community Manager | Open Geospatial Consortium (OGC) > > +1 (508) 655-5858 ex 706 > > mbrachman@ogc.org | ogc.org | @opengeospatial > > [cid:ii_194921c7027982c5fce1] Book time to meet with me > ________________________________ > From: Angelos Tzotsos > > Sent: Sunday, January 5, 2025 6:18 AM > To: Micah Brachman > > Cc: Angelos Tzotsos >; Even Rouault >; OGC Compliance >; info at osgeo.org >; OSGeo Board >; Tom Kralidis > > Subject: Re: OGC Compliance Renewal Notification - 60 Day Expiration Notice > > 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 compliance page. > 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 listed. > I added the latest 8.2 release that includes support for OGC API Features (no cite tests yet). > > 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 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? > We did not manage to run new tests for OGC API - EDR so we would like to keep RI to the previous pygeoapi 0.9 version for now. > > 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 like to keep that version as CSW 2.0.2 and 3.0.0 reference implementation. > OGC API Records is implemented in pycsw 3.0.0 (not yet released as final). We are waiting for the specification to be finalized and looking forward to testing against a Records cite test. > > 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 would like to ask to move all reference implementation status to that version. Is that possible? > > 5. For GeoServer we have version 2.24 > We do not have new compliance tests available so we would like to keep version 2.24 listed. > > Best regards, > Angelos > > > On Wed, Nov 13, 2024 at 7:09?PM Micah Brachman > wrote: > > That sounds great, Angelos ? please let me know if you have any questions or need assistance. > > > > From: Angelos Tzotsos > > Date: Wednesday, November 13, 2024 at 6:39 AM > To: Micah Brachman >, Even Rouault >, Compliance >, info at osgeo.org > > Cc: Angelos Tzotsos >, OSGeo Board > > Subject: Re: OGC Compliance Renewal Notification - 60 Day Expiration Notice > > 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: >> Thanks for sharing these, Even. >> >> Angelos- >> >> I can see that you have submitted the last few compliance results. Are you planning to submit these as well? >> >> Best, >> >> Micah >> >> >> Micah Brachman, PhD >> Community Manager | Open Geospatial Consortium (OGC) >> +1 (508) 655-5858 ex 706 >> mbrachman@ogc.org> | ogc.org | @opengeospatial >> >> >> >> From: Even Rouault > >> Date: Monday, November 11, 2024 at 3:56 PM >> To: Compliance >, info at osgeo.org > >> Cc: Angelos Tzotsos >, OSGeo Board >, Angelos Tzotsos > >> Subject: Re: OGC Compliance Renewal Notification - 60 Day Expiration Notice >> >> 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, compliance at ogc.org a ?crit : >> Open Source Geospatial Foundation >> >> This is an automated email to inform you that your OGC-certified 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. >> >> Since you have reference implementations in your listings please be aware of the following: >> >> * You need to retest if you want to continue being listed as a reference implementation. >> * If you want to provide a new version as a reference implementation you need to test that new version. The older version will no longer hold the status of reference implementations. >> * If you want to continue displaying the certification for the older version of your product, then you will be required to pay for the certification. >> >> Additional expiration warnings may be sent to you 1 month and 2 weeks prior to expiration, please begin the renewal process as soon as possible. >> >> We invite you to easily renew online in our implementation portal: https://www.ogc.org/resource/products/registration >> >> As a reminder, the account used to manage your certification listings is: osgeo (info at osgeo.org>) >> >> If you have any questions please send an email to compliance at ogc.org. The OGC compliance team will be more than glad to help you. >> >> ________________________________ >> 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 Information 1.0 >> (OGC Reference Implementation) >> 2024-01-09 >> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Acquisition Parameters 1.0 >> (OGC Reference Implementation) >> 2024-01-09 >> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Data Identification 1.0 >> (OGC Reference Implementation) >> 2024-01-09 >> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Earth Observation 1.0 >> (OGC Reference Implementation) >> 2024-01-09 >> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Earth Observation Collection 1.0 >> (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 Information 1.0 >> (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 Information 1.0 >> (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 Service for the Web] 2.0.2 >> (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 (OpenSearch) 3.0 >> (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 Service for the Web] 2.0.2 >> (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 >> >> -- >> >> http://www.spatialys.com >> >> My software is free, but my time generally not. >> >> Butcher of all kinds of standards, open or closed formats. At the end, this is just about bytes. >> > > -- > Angelos Tzotsos, PhD > President, Board of Directors > Open Source Geospatial Foundation > https://www.osgeo.org/member/angelos-tzotsos/ > > > -- > Angelos Tzotsos, PhD > President, Board of Directors > Open Source Geospatial Foundation > https://www.osgeo.org/member/angelos-tzotsos/ > > > -- > Angelos Tzotsos, PhD > President, Board of Directors > Open Source Geospatial Foundation > https://www.osgeo.org/member/angelos-tzotsos/ -- Angelos Tzotsos, PhD President, Board of Directors Open Source Geospatial Foundation https://www.osgeo.org/member/angelos-tzotsos/ From amangaf at gmail.com Tue Apr 15 04:30:38 2025 From: amangaf at gmail.com (=?UTF-8?Q?Alen_Mangafi=C4=87?=) Date: Tue, 15 Apr 2025 13:30:38 +0200 Subject: [Board] Request - formal recognition - OSGeo Slovenija as an official OSGeo Local Chapter Message-ID: Dear OSGeo Board, We are writing to request formal recognition of *OSGeo Slovenija* as an *official OSGeo Local Chapter*. Our community has been evolving organically over the past years, shaped by contributions from a diverse group of researchers, students, professionals, and enthusiasts across disciplines - including GIS, geodesy, biology, computer science, forestry, social sciences, etc. From the beginning, inclusivity and openness have been core to how we operate and grow. Over the last three years, we have been connecting with interested individuals from all over our little country. Through shared activities, informal meetups, and regular presence at FOSS4G events, we?ve grown together into a critical mass that decided to take this step collectively. While we are more focused on geeking out, building (and destroying) things, and fostering community than on formal structures or bureaucracy, we felt it was the right moment to make this official. A cornerstone of this journey has been our annual *Open Source Geospatial Slovenija* conference in Ljubljana, which has become a central platform for collaboration, idea exchange, and showcasing open geospatial work in our region. Over the years, we?ve also had the pleasure of hosting members of the global OSGeo community at this event, strengthening our ties with the broader network. While many Local Chapters have served as valuable references, it was especially the story of the Romanian Local Chapter - presented at FOSS4G 2022 Firenze and later again at our Slovenian conference (2024) - that motivated us to move forward with formal recognition. Throughout this incubation period, we have: - *Organized annual *(totally DIY, free-of-charge, 100+ attendees) *Open Source Geospatial Slovenija* conferences in *Ljubljana* 2024 2023 2022 - *Launched a series of technical meetups under the name GeoDev * ? open, hands-on gatherings focused on geospatial development. We joined forces with other IT-crazy people to create a space where geo-developers can share tools, workflows, and experiments in a relaxed, community-driven setting with beer and pizza (the last one was yesterday), - *Supported field-based use cases* like dragonfly tracking (in collaboration with the local odonata society) and analyzing beaver population spread by tracking their poo - both carried out using QField in support of environmental and academic projects. We are formally organized as a non-profit, with a statute aligned with OSGeo values. Our current membership includes *50 active individuals*, and all core information is published on our wiki page: *https://wiki.osgeo.org/wiki/Slovenia * Our logo is currently under development. We feel ready to formally join the OSGeo family and continue contributing - as we already do - the global open geospatial movement. We hope we didn?t mess up the formal steps too badly along the way. Thank you for your time and consideration. Please let us know if there are any next steps or additional information needed to support this request. Best Regards, *Alen Mangafi?* Secretary, OSGeo Slovenija osgeoslovenija at gmail.com https://osgeo.si https://wiki.osgeo.org/wiki/Slovenia -------------- next part -------------- An HTML attachment was scrubbed... URL: From gcpp.kalxas at gmail.com Wed Apr 16 23:45:52 2025 From: gcpp.kalxas at gmail.com (Angelos Tzotsos) Date: Thu, 17 Apr 2025 09:45:52 +0300 Subject: [Board] Fwd: OGC Compliance Renewal Notification - 60 Day Expiration Notice In-Reply-To: References: Message-ID: <062196f1-6078-49cf-98b4-5c4e5badb255@gmail.com> -------- Forwarded Message -------- Subject: Re: OGC Compliance Renewal Notification - 60 Day Expiration Notice Date: Thu, 17 Apr 2025 09:43:25 +0300 From: Angelos Tzotsos To: Peter Smythe CC: OGC Compliance , info at osgeo.org , OSGeo Board , Even Rouault , Tom Kralidis , Angelos Tzotsos , Gobe Hobona (OGC) Dear Peter, With the help from Gobe, we have identified the standards where GeoServer can be a Reference Implementation (and get certified for free) under the OGC/OSGeo MOU. The list is the following: WMTS 1.0.0 GeoTiff 1.1 WCS 1.0 WCS 1.1.1 WCS 2.0.1 WFS 1.0.0 For the following standards, certification is not free, since OGC has reached the limit of free waivers for Reference Implementations: GeoPackage 1.2 WMS 1.1.1 WMS 1.3.0 OGC API - Features 1.0 WFS 1.1.0 WFS 2.0 According to https://www.ogc.org/how-our-compliance-program-works/ we will need to pay 150$ per certification, a total of 900$ Best regards, Angelos On Tue, Apr 15, 2025 at 10:52?AM Gobe Hobona (OGC) wrote: > 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 > *Date: *Tuesday, 15 April 2025 at 08:37 > *To: *Angelos Tzotsos, Gobe Hobona (OGC) < > ghobona at ogc.org> > *Cc: *Micah Brachman, OGC Compliance < > compliance at ogc.org>, info at osgeo.org , OSGeo Board < > board at lists.osgeo.org>, Even Rouault , Tom > Kralidis, Angelos Tzotsos > *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 > https://github.com/petersmythe > > > > > > On Sat, 12 Apr 2025 at 16:38, Peter Smythe 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.https://geoserver.org/roadmap Is that > feasible/reasonable? > > > > Thank you > > > > Peter > > GeoServer PSC > > > > On Tue, 08 Apr 2025, 07:29 Angelos Tzotsos, 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: > > https://git.osgeo.org/gitea/osgeo/standards-committee/issues/10#issuecomment-13445 > > 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: >> 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@ogc.org | > ogc.org | @opengeospatial >> [cid:911e275f-ef14-4789-a8ae-c16831bb67ef]< > https://outlook.office.com/bookwithme/user/471ab05d3c7047e0bde9468e040936ac at ogc.org?anonymous&ep=bwmEmailSignature> > Book time to meet with me< > https://outlook.office.com/bookwithme/user/471ab05d3c7047e0bde9468e040936ac at ogc.org?anonymous&ep=bwmEmailSignature >> ________________________________ >> From: Angelos Tzotsos >> Sent: Wednesday, January 22, 2025 11:43 PM >> To: Micah Brachman >> Cc: Angelos Tzotsos; Even Rouault < > even.rouault at spatialys.com>; OGC Compliance ; > info at osgeo.org ; OSGeo Board; Tom > Kralidis >> Subject: Re: OGC Compliance Renewal Notification - 60 Day Expiration > Notice >> 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 > wrote: >> Hi Angelos, >> >> Thank you ? I've approved your submission and you can see the updated > listings at this link< > https://portal.ogc.org/public_ogc/compliance/compliant.php?display_opt=1&org_match=Open%20Source%20Geospatial%20Foundation >> . >> >> Hopefully I've addressed all of your questions/requests below with this > 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. >> Thanks again for your support of the compliance program, and please feel > free to book time with me using the link below if you'd like to discuss > further. >> Best, >> >> Micah >> >> >> >> >> >> Micah Brachman, PhD >> >> Community Manager | Open Geospatial Consortium (OGC) >> >> +1 (508) 655-5858 ex 706 >> >> mbrachman@ogc.org | > ogc.org | @opengeospatial >> [cid:ii_194921c7027982c5fce1]< > https://outlook.office.com/bookwithme/user/471ab05d3c7047e0bde9468e040936ac at ogc.org?anonymous&ep=bwmEmailSignature> > Book time to meet with me< > https://outlook.office.com/bookwithme/user/471ab05d3c7047e0bde9468e040936ac at ogc.org?anonymous&ep=bwmEmailSignature >> ________________________________ >> From: Angelos Tzotsos > >> Sent: Sunday, January 5, 2025 6:18 AM >> To: Micah Brachman > >> Cc: Angelos Tzotsos >; > Even Rouault >; > OGC Compliance >; > info at osgeo.org >; OSGeo Board >; Tom Kralidis > >> Subject: Re: OGC Compliance Renewal Notification - 60 Day Expiration > Notice >> 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 > compliance page. >> 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 > listed. >> I added the latest 8.2 release that includes support for OGC API > Features (no cite tests yet). >> 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 > 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? >> We did not manage to run new tests for OGC API - EDR so we would like to > keep RI to the previous pygeoapi 0.9 version for now. >> 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 > like to keep that version as CSW 2.0.2 and 3.0.0 reference implementation. >> OGC API Records is implemented in pycsw 3.0.0 (not yet released as > final). We are waiting for the specification to be finalized and looking > forward to testing against a Records cite test. >> 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 > would like to ask to move all reference implementation status to that > version. Is that possible? >> 5. For GeoServer we have version 2.24 >> We do not have new compliance tests available so we would like to keep > version 2.24 listed. >> Best regards, >> Angelos >> >> >> On Wed, Nov 13, 2024 at 7:09?PM Micah Brachman > wrote: >> That sounds great, Angelos ? please let me know if you have any > questions or need assistance. >> >> >> From: Angelos Tzotsos gcpp.kalxas at gmail.com>> >> Date: Wednesday, November 13, 2024 at 6:39 AM >> To: Micah Brachman >, Even > Rouault >, > Compliance >, info at osgeo.org > > >> Cc: Angelos Tzotsos >, > OSGeo Board > >> Subject: Re: OGC Compliance Renewal Notification - 60 Day Expiration > Notice >> 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: >>> Thanks for sharing these, Even. >>> >>> Angelos- >>> >>> I can see that you have submitted the last few compliance results. Are > you planning to submit these as well? >>> Best, >>> >>> Micah >>> >>> >>> Micah Brachman, PhD >>> Community Manager | Open Geospatial Consortium (OGC) >>> +1 (508) 655-5858 ex 706 >>> mbrachman@ogc.org > | > ogc.org | @opengeospatial >>> >>> >>> From: Even Rouault even.rouault at spatialys.com>> >>> Date: Monday, November 11, 2024 at 3:56 PM >>> To: Compliance >, > info at osgeo.org > >>> Cc: Angelos Tzotsos >, > OSGeo Board >, > Angelos Tzotsos > >>> Subject: Re: OGC Compliance Renewal Notification - 60 Day Expiration > Notice >>> 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,compliance at ogc.org> a ?crit : >>> Open Source Geospatial Foundation >>> >>> This is an automated email to inform you that your OGC-certified > 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. >>> Since you have reference implementations in your listings please be > aware of the following: >>> * You need to retest if you want to continue being listed as a > reference implementation. >>> * If you want to provide a new version as a reference > implementation you need to test that new version. The older version will no > longer hold the status of reference implementations. >>> * If you want to continue displaying the certification for the > older version of your product, then you will be required to pay for the > certification. >>> Additional expiration warnings may be sent to you 1 month and 2 weeks > prior to expiration, please begin the renewal process as soon as possible. >>> We invite you to easily renew online in our implementation portal: > https://www.ogc.org/resource/products/registration >>> As a reminder, the account used to manage your certification listings > is: osgeo (info at osgeo.org >) >>> If you have any questions please send an email tocompliance at ogc.org > . The OGC > compliance team will be more than glad to help you. >>> ________________________________ >>> 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 > Information 1.0 >>> (OGC Reference Implementation) >>> 2024-01-09 >>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Acquisition > Parameters 1.0 >>> (OGC Reference Implementation) >>> 2024-01-09 >>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Data > Identification 1.0 >>> (OGC Reference Implementation) >>> 2024-01-09 >>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Earth > Observation 1.0 >>> (OGC Reference Implementation) >>> 2024-01-09 >>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Earth > Observation Collection 1.0 >>> (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 > Information 1.0 >>> (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 > Information 1.0 >>> (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 > Service for the Web] 2.0.2 >>> (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 > (OpenSearch) 3.0 >>> (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 > Service for the Web] 2.0.2 >>> (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 >>> >>> -- >>> >>> http://www.spatialys.com >>> >>> My software is free, but my time generally not. >>> >>> Butcher of all kinds of standards, open or closed formats. At the end, > this is just about bytes. >> >> -- >> Angelos Tzotsos, PhD >> President, Board of Directors >> Open Source Geospatial Foundation >> https://www.osgeo.org/member/angelos-tzotsos/ >> >> >> -- >> Angelos Tzotsos, PhD >> President, Board of Directors >> Open Source Geospatial Foundation >> https://www.osgeo.org/member/angelos-tzotsos/ >> >> >> -- >> Angelos Tzotsos, PhD >> President, Board of Directors >> Open Source Geospatial Foundation >> https://www.osgeo.org/member/angelos-tzotsos/ > > > -- > Angelos Tzotsos, PhD > President, Board of Directors > Open Source Geospatial Foundation > https://www.osgeo.org/member/angelos-tzotsos/ > > -- Angelos Tzotsos, PhD President, Board of Directors Open Source Geospatial Foundation https://www.osgeo.org/member/angelos-tzotsos/ -------------- next part -------------- An HTML attachment was scrubbed... URL: