From gcpp.kalxas at gmail.com  Sun Jan  4 06:36:32 2026
From: gcpp.kalxas at gmail.com (Angelos Tzotsos)
Date: Sun, 4 Jan 2026 16:36:32 +0200
Subject: [MapServer-dev] Fwd: OGC Compliance Renewal Notification - 30
 Day Expiration Notice
In-Reply-To: <c2a46fb8-bca8-4c2b-aca1-0d5273c31bbb@gmail.com>
References: <1765361161.695827.236279.nullmailer@tic.ogc.org>
 <c2a46fb8-bca8-4c2b-aca1-0d5273c31bbb@gmail.com>
Message-ID: <963d3e39-9d57-4313-a1c9-fde32b47a8aa@gmail.com>

Happy New Year!

I have prepared the new compliance submission including CITE tests from 
pycsw, GeoServer and pygeoapi.
I have kept MapServer and GDAL listed, as last year.
Should I wait for new tests or should I continue with submission?

Best regards,
Angelos

On 12/10/25 14:57, Angelos Tzotsos wrote:
> Dear all,
>
> Please prepare your OGC CITE tests and let us know by the end of the 
> month so we can prepare the submission.
>
> Best regards,
> Angelos
>
>
> -------- Forwarded Message --------
> Subject:???? OGC Compliance Renewal Notification - 30 Day Expiration 
> Notice
> Date:???? Wed, 10 Dec 2025 10:06:01 +0000
> From:???? compliance at ogc.org
> Reply-To:???? compliance at ogc.org
> To:???? info at osgeo.org
> CC:???? Angelos Tzotsos <tzotsos at osgeo.org>, Michael Smith 
> <info at osgeo.org>, Even Roualt <even.rouault at spatialys.com>
>
>
>
> ?Open Source Geospatial Foundation (OSGeo)
>
> 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, 2026*. 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.
>
> If you have already received an earlier notice and have started the 
> renewal process please ignore this message.
>
> 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 3.10
>
> Specification(s)???? Original Certification
> OGC GeoTIFF Standard 1.1
> (OGC Reference Implementation)???? 2025-01-10
> OGC KML 2.2.0
> (OGC Reference Implementation)???? 2025-01-10
> OGC KML (Level 2) 2.2.0
> (OGC Reference Implementation)???? 2025-01-10
> OGC KML (Level 3) 2.2.0
> (OGC Reference Implementation)???? 2025-01-10
> OGC? GeoPackage Encoding Standard 1.2
> (OGC Reference Implementation)???? 2025-01-10
> OGC? GeoPackage Encoding Standard: Extension Mechanism 1.2
> (OGC Reference Implementation)???? 2025-01-10
> OGC? GeoPackage Encoding Standard: Features 1.2
> (OGC Reference Implementation)???? 2025-01-10
> OGC? GeoPackage Encoding Standard: Metadata 1.2
> (OGC Reference Implementation)???? 2025-01-10
> OGC? GeoPackage Encoding Standard: RTree Spatial Indexes 1.2
> (OGC Reference Implementation)???? 2025-01-10
> OGC? GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core 2.0
> (OGC Reference Implementation)???? 2025-01-10
>
>
> ???? GeoServer 2.27
>
> Specification(s)???? Original Certification
> OGC API - Features - Part 1: Core 1.0???? 2025-07-10
> OGC API - Features - Part 2: Coordinate Reference Systems by Reference 
> 1.0???? 2025-07-10
> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard 1.0
> (OGC Reference Implementation)???? 2025-07-10
> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Acquisition 
> Information 1.0
> (OGC Reference Implementation)???? 2025-07-10
> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Acquisition 
> Parameters 1.0
> (OGC Reference Implementation)???? 2025-07-10
> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Data 
> Identification 1.0
> (OGC Reference Implementation)???? 2025-07-10
> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Earth 
> Observation 1.0
> (OGC Reference Implementation)???? 2025-07-10
> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Earth 
> Observation Collection 1.0
> (OGC Reference Implementation)???? 2025-07-10
> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Geometry 1.0
> (OGC Reference Implementation)???? 2025-07-10
> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Links 1.0
> (OGC Reference Implementation)???? 2025-07-10
> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Metadata 
> Information 1.0
> (OGC Reference Implementation)???? 2025-07-10
> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Offering 1.0
> (OGC Reference Implementation)???? 2025-07-10
> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Product 
> Information 1.0
> (OGC Reference Implementation)???? 2025-07-10
> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Properties 1.0
> (OGC Reference Implementation)???? 2025-07-10
> OGC GeoTIFF Standard 1.1
> (OGC Reference Implementation)???? 2025-07-10
> OGC? GeoPackage Encoding Standard 1.2
> (OGC Reference Implementation)???? 2025-07-10
> OGC? GeoPackage Encoding Standard: Extension Mechanism 1.2
> (OGC Reference Implementation)???? 2025-07-10
> OGC? GeoPackage Encoding Standard: Features 1.2
> (OGC Reference Implementation)???? 2025-07-10
> OGC? GeoPackage Encoding Standard: Metadata 1.2
> (OGC Reference Implementation)???? 2025-07-10
> OGC? GeoPackage Encoding Standard: RTree Spatial Indexes 1.2
> (OGC Reference Implementation)???? 2025-07-10
> OGC? GeoPackage Encoding Standard: Schema 1.2
> (OGC Reference Implementation)???? 2025-07-10
> OGC? WCS 2.0 Interface Standard- Core: Corrigendum 2.0.1
> (OGC Reference Implementation)???? 2025-07-10
> OGC? Web Coverage Service Interface Standard - Interpolation Extension 
> 1.0
> (OGC Reference Implementation)???? 2025-07-10
> OGC? Web Coverage Service Interface Standard - Scaling Extension 1.0
> (OGC Reference Implementation)???? 2025-07-10
> OGC? Web Coverage Service Interface Standard - CRS Extension 1.0
> (OGC Reference Implementation)???? 2025-07-10
> OGC? Web Coverage Service Interface Standard - Range Subsetting 
> Extension 1.0
> (OGC Reference Implementation)???? 2025-07-10
> OpenGIS Web Coverage Service (WCS) Implementation Specification 
> (Corrigendum) 1.0.0
> (OGC Reference Implementation)???? 2025-07-10
> OpenGIS Web Coverage Service (WCS) Implementation Specification 
> Corrigendum 1 1.1.1
> (OGC Reference Implementation)???? 2025-07-10
> OpenGIS Web Feature Service (WFS) Implementation Specification 1.1.0 
> 2025-07-10
> OpenGIS Web Feature Service (WFS) Implementation Specification (Basic) 
> 1.1.0???? 2025-07-10
> OpenGIS Web Feature Service (WFS) Implementation Specification 
> (Transactional) 1.1.0???? 2025-07-10
> OpenGIS Web Feature Service - Basic 2.0???? 2025-07-10
> OpenGIS Web Feature Service - Locking 2.0???? 2025-07-10
> OpenGIS Web Feature Service - Transactional 2.0???? 2025-07-10
> OpenGIS Web Feature Service 2.0 Interface Standard (also ISO 19142) 
> 2.0 2025-07-10
> OpenGIS Web Map Service (WMS) Implementation Specification 1.3.0 
> 2025-07-10
> OpenGIS Web Map Tile Service Implementation Standard 1.0.0 2025-07-10
> Web Feature Service 1.0.0
> (OGC Reference Implementation)???? 2025-07-10
> Web Feature Service (Transactional) 1.0.0
> (OGC Reference Implementation)???? 2025-07-10
> Web Map Service 1.1.1???? 2025-07-10
>
>
> ???? istSOS 2.3.1
>
> Specification(s)???? Original Certification
> OpenGIS Sensor Observation Service 1.0.0
> (OGC Reference Implementation)???? 2018-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.19.0
>
> Specification(s)???? Original Certification
> OGC API - Environmental Data Retrieval Standard 1.0.1
> (OGC Reference Implementation)???? 2025-01-10
> OGC API - Environmental Data Retrieval Standard: Collections 1.0.1
> (OGC Reference Implementation)???? 2025-01-10
> OGC API - Environmental Data Retrieval Standard: CoverageJSON 1.0.1
> (OGC Reference Implementation)???? 2025-01-10
> OGC API - Environmental Data Retrieval Standard: EDRGeoJSON 1.0.1
> (OGC Reference Implementation)???? 2025-01-10
> OGC API - Environmental Data Retrieval Standard: GeoJSON 1.0.1
> (OGC Reference Implementation)???? 2025-01-10
> OGC API - Environmental Data Retrieval Standard: HTML 1.0.1
> (OGC Reference Implementation)???? 2025-01-10
> OGC API - Environmental Data Retrieval Standard: JSON 1.0.1
> (OGC Reference Implementation)???? 2025-01-10
> OGC API - Features - Part 1: Core 1.0
> (OGC Reference Implementation)???? 2025-01-10
> OGC API - Tiles - Part 1: Core 1.0
> (OGC Reference Implementation)???? 2025-01-10
> OGC API - Tiles - Part 1: DatasetTilesets 1.0
> (OGC Reference Implementation)???? 2025-01-10
> OGC API - Tiles - Part 1: GeoDataTilesets 1.0
> (OGC Reference Implementation)???? 2025-01-10
>
>
>

-- 
Angelos Tzotsos, PhD
President, Board of Directors
Open Source Geospatial Foundation
https://www.osgeo.org/member/angelos-tzotsos/



From sethg at geographika.co.uk  Wed Jan  7 00:37:10 2026
From: sethg at geographika.co.uk (Seth G)
Date: Wed, 07 Jan 2026 09:37:10 +0100
Subject: [MapServer-dev] Proposal: OSGeo Budget 2026
Message-ID: <06986364-9e6d-49f5-983d-83f7ff650152@app.fastmail.com>

Hi all,

The deadline for budget requests is fast approaching. See https://wiki.osgeo.org/wiki/OSGeo_Budget_2026
The page includes the line "Board decided that the maximum amount per project this year cannot be more than $2,000 USD." Rather than requesting more than this and having to revise the budget again later. I propose we submit a request for:

- $1,000 for codesprint and workshop attendance
- $1,000 for release manager support

If funds are required for emergency operations such as vulnerabilities, I think we should make a request to the board as and when needed. As mentioned by Mike in a previous thread, there have been no sponsorship funds for MapServer for the last 2 (maybe more) years. 

The 2025 budget proposal can be found at https://github.com/MapServer/MapServer/wiki/MapServer-2025-Budget

I'll start with my +1. 

Seth

--
mastodon: @geographika at mastodon.social

From michael.smith.erdc at gmail.com  Wed Jan  7 02:44:19 2026
From: michael.smith.erdc at gmail.com (Michael Smith)
Date: Wed, 07 Jan 2026 05:44:19 -0500
Subject: [MapServer-dev] Proposal: OSGeo Budget 2026
In-Reply-To: <06986364-9e6d-49f5-983d-83f7ff650152@app.fastmail.com>
References: <06986364-9e6d-49f5-983d-83f7ff650152@app.fastmail.com>
Message-ID: <801D6E72-0969-4757-8C5B-ECBDEA4EEBBA@gmail.com>

+1 (as MapServer PSC) 

Mike


-- 

Michael Smith 
RSGIS Center ? ERDC CRREL NH 
US Army Corps 





?On 1/7/26, 3:37 AM, "MapServer-dev on behalf of Seth G via MapServer-dev" <mapserver-dev-bounces at lists.osgeo.org <mailto:mapserver-dev-bounces at lists.osgeo.org> on behalf of mapserver-dev at lists.osgeo.org <mailto:mapserver-dev at lists.osgeo.org>> wrote:


Hi all,


The deadline for budget requests is fast approaching. See https://wiki.osgeo.org/wiki/OSGeo_Budget_2026 <https://wiki.osgeo.org/wiki/OSGeo_Budget_2026>
The page includes the line "Board decided that the maximum amount per project this year cannot be more than $2,000 USD." Rather than requesting more than this and having to revise the budget again later. I propose we submit a request for:


- $1,000 for codesprint and workshop attendance
- $1,000 for release manager support


If funds are required for emergency operations such as vulnerabilities, I think we should make a request to the board as and when needed. As mentioned by Mike in a previous thread, there have been no sponsorship funds for MapServer for the last 2 (maybe more) years. 


The 2025 budget proposal can be found at https://github.com/MapServer/MapServer/wiki/MapServer-2025-Budget <https://github.com/MapServer/MapServer/wiki/MapServer-2025-Budget>


I'll start with my +1. 


Seth


--
mastodon: @geographika at mastodon.soci <mailto:geographika at mastodon.soci>al
_______________________________________________
MapServer-dev mailing list
MapServer-dev at lists.osgeo.org <mailto:MapServer-dev at lists.osgeo.org>
https://lists.osgeo.org/mailman/listinfo/mapserver-dev <https://lists.osgeo.org/mailman/listinfo/mapserver-dev>





From even.rouault at spatialys.com  Wed Jan  7 02:47:26 2026
From: even.rouault at spatialys.com (Even Rouault)
Date: Wed, 7 Jan 2026 11:47:26 +0100
Subject: [MapServer-dev] Proposal: OSGeo Budget 2026
In-Reply-To: <06986364-9e6d-49f5-983d-83f7ff650152@app.fastmail.com>
References: <06986364-9e6d-49f5-983d-83f7ff650152@app.fastmail.com>
Message-ID: <37329a69-126e-4e5d-a3f1-6b9f84307ae8@spatialys.com>

+1 Even

Le 07/01/2026 ? 09:37, Seth G via MapServer-dev a ?crit?:
> Hi all,
>
> The deadline for budget requests is fast approaching. See https://wiki.osgeo.org/wiki/OSGeo_Budget_2026
> The page includes the line "Board decided that the maximum amount per project this year cannot be more than $2,000 USD." Rather than requesting more than this and having to revise the budget again later. I propose we submit a request for:
>
> - $1,000 for codesprint and workshop attendance
> - $1,000 for release manager support
>
> If funds are required for emergency operations such as vulnerabilities, I think we should make a request to the board as and when needed. As mentioned by Mike in a previous thread, there have been no sponsorship funds for MapServer for the last 2 (maybe more) years.
>
> The 2025 budget proposal can be found at https://github.com/MapServer/MapServer/wiki/MapServer-2025-Budget
>
> I'll start with my +1.
>
> Seth
>
> --
> mastodon: @geographika at mastodon.social
> _______________________________________________
> MapServer-dev mailing list
> MapServer-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-dev

-- 
http://www.spatialys.com
My software is free, but my time generally not.


From jukka.rahkonen at maanmittauslaitos.fi  Wed Jan  7 02:58:10 2026
From: jukka.rahkonen at maanmittauslaitos.fi (Rahkonen Jukka)
Date: Wed, 7 Jan 2026 10:58:10 +0000
Subject: [MapServer-dev] Proposal: OSGeo Budget 2026
In-Reply-To: <06986364-9e6d-49f5-983d-83f7ff650152@app.fastmail.com>
References: <06986364-9e6d-49f5-983d-83f7ff650152@app.fastmail.com>
Message-ID: <PA3PR09MB8258FC7753079B61F1E8B93DFD84A@PA3PR09MB8258.eurprd09.prod.outlook.com>

+1

-Jukka Rahkonen-
________________________________________
L?hett?j?: MapServer-dev <mapserver-dev-bounces at lists.osgeo.org> k?ytt?j?n Seth G via MapServer-dev <mapserver-dev at lists.osgeo.org> puolesta
L?hetetty: Keskiviikko 7. tammikuuta 2026 10.37
Vastaanottaja: MapServer Devs <mapserver-dev at lists.osgeo.org>
Aihe: [MapServer-dev] Proposal: OSGeo Budget 2026


Hi all,

The deadline for budget requests is fast approaching. See https://wiki.osgeo.org/wiki/OSGeo_Budget_2026
The page includes the line "Board decided that the maximum amount per project this year cannot be more than $2,000 USD." Rather than requesting more than this and having to revise the budget again later. I propose we submit a request for:

- $1,000 for codesprint and workshop attendance
- $1,000 for release manager support

If funds are required for emergency operations such as vulnerabilities, I think we should make a request to the board as and when needed. As mentioned by Mike in a previous thread, there have been no sponsorship funds for MapServer for the last 2 (maybe more) years.

The 2025 budget proposal can be found at https://github.com/MapServer/MapServer/wiki/MapServer-2025-Budget

I'll start with my +1.

Seth

--
mastodon: @geographika at mastodon.social
_______________________________________________
MapServer-dev mailing list
MapServer-dev at lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-dev



From tomkralidis at gmail.com  Wed Jan  7 03:02:57 2026
From: tomkralidis at gmail.com (Tom Kralidis)
Date: Wed, 7 Jan 2026 06:02:57 -0500
Subject: [MapServer-dev] Proposal: OSGeo Budget 2026
In-Reply-To: <801D6E72-0969-4757-8C5B-ECBDEA4EEBBA@gmail.com>
References: <06986364-9e6d-49f5-983d-83f7ff650152@app.fastmail.com>
 <801D6E72-0969-4757-8C5B-ECBDEA4EEBBA@gmail.com>
Message-ID: <CAFWXLWXFXWP7_s=X=x_eY4ASEjXzbUfdAqcAudEhAtEYX3TY7Q@mail.gmail.com>

+1 as MapServer PSC

Thanks

..Tom

On Wed, Jan 7, 2026 at 5:44?AM Michael Smith via MapServer-dev
<mapserver-dev at lists.osgeo.org> wrote:
>
> +1 (as MapServer PSC)
>
> Mike
>
>
> --
>
> Michael Smith
> RSGIS Center ? ERDC CRREL NH
> US Army Corps
>
>
>
>
>
> ?On 1/7/26, 3:37 AM, "MapServer-dev on behalf of Seth G via MapServer-dev" <mapserver-dev-bounces at lists.osgeo.org <mailto:mapserver-dev-bounces at lists.osgeo.org> on behalf of mapserver-dev at lists.osgeo.org <mailto:mapserver-dev at lists.osgeo.org>> wrote:
>
>
> Hi all,
>
>
> The deadline for budget requests is fast approaching. See https://wiki.osgeo.org/wiki/OSGeo_Budget_2026 <https://wiki.osgeo.org/wiki/OSGeo_Budget_2026>
> The page includes the line "Board decided that the maximum amount per project this year cannot be more than $2,000 USD." Rather than requesting more than this and having to revise the budget again later. I propose we submit a request for:
>
>
> - $1,000 for codesprint and workshop attendance
> - $1,000 for release manager support
>
>
> If funds are required for emergency operations such as vulnerabilities, I think we should make a request to the board as and when needed. As mentioned by Mike in a previous thread, there have been no sponsorship funds for MapServer for the last 2 (maybe more) years.
>
>
> The 2025 budget proposal can be found at https://github.com/MapServer/MapServer/wiki/MapServer-2025-Budget <https://github.com/MapServer/MapServer/wiki/MapServer-2025-Budget>
>
>
> I'll start with my +1.
>
>
> Seth
>
>
> --
> mastodon: @geographika at mastodon.soci <mailto:geographika at mastodon.soci>al
> _______________________________________________
> MapServer-dev mailing list
> MapServer-dev at lists.osgeo.org <mailto:MapServer-dev at lists.osgeo.org>
> https://lists.osgeo.org/mailman/listinfo/mapserver-dev <https://lists.osgeo.org/mailman/listinfo/mapserver-dev>
>
>
>
>
> _______________________________________________
> MapServer-dev mailing list
> MapServer-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-dev

From jbo-ads at mailo.com  Wed Jan  7 02:52:55 2026
From: jbo-ads at mailo.com (jbo-ads at mailo.com)
Date: Wed, 7 Jan 2026 11:52:55 +0100
Subject: [MapServer-dev] Proposal: OSGeo Budget 2026
In-Reply-To: <06986364-9e6d-49f5-983d-83f7ff650152@app.fastmail.com>
References: <06986364-9e6d-49f5-983d-83f7ff650152@app.fastmail.com>
Message-ID: <8e774595-d77d-40fa-9d11-c427454e61a3@mailo.com>

+1? J?rome

On 1/7/26 09:37, Seth G via MapServer-dev wrote:
> Hi all,
>
> The deadline for budget requests is fast approaching. See https://wiki.osgeo.org/wiki/OSGeo_Budget_2026
> The page includes the line "Board decided that the maximum amount per project this year cannot be more than $2,000 USD." Rather than requesting more than this and having to revise the budget again later. I propose we submit a request for:
>
> - $1,000 for codesprint and workshop attendance
> - $1,000 for release manager support
>
> If funds are required for emergency operations such as vulnerabilities, I think we should make a request to the board as and when needed. As mentioned by Mike in a previous thread, there have been no sponsorship funds for MapServer for the last 2 (maybe more) years.
>
> The 2025 budget proposal can be found at https://github.com/MapServer/MapServer/wiki/MapServer-2025-Budget
>
> I'll start with my +1.
>
> Seth
>
> --
> mastodon: @geographika at mastodon.social
> _______________________________________________
> MapServer-dev mailing list
> MapServer-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-dev



From sdlime at gmail.com  Wed Jan  7 06:57:33 2026
From: sdlime at gmail.com (Steve Lime)
Date: Wed, 7 Jan 2026 08:57:33 -0600
Subject: [MapServer-dev] Proposal: OSGeo Budget 2026
In-Reply-To: <06986364-9e6d-49f5-983d-83f7ff650152@app.fastmail.com>
References: <06986364-9e6d-49f5-983d-83f7ff650152@app.fastmail.com>
Message-ID: <CAMrKZ9-vaa2_1mG4YgTHMuiSdebE-TWxYCCH+fuSGtfnX571ZQ@mail.gmail.com>

+1

On Wed, Jan 7, 2026 at 2:37?AM Seth G via MapServer-dev <
mapserver-dev at lists.osgeo.org> wrote:

> Hi all,
>
> The deadline for budget requests is fast approaching. See
> https://wiki.osgeo.org/wiki/OSGeo_Budget_2026
> The page includes the line "Board decided that the maximum amount per
> project this year cannot be more than $2,000 USD." Rather than requesting
> more than this and having to revise the budget again later. I propose we
> submit a request for:
>
> - $1,000 for codesprint and workshop attendance
> - $1,000 for release manager support
>
> If funds are required for emergency operations such as vulnerabilities, I
> think we should make a request to the board as and when needed. As
> mentioned by Mike in a previous thread, there have been no sponsorship
> funds for MapServer for the last 2 (maybe more) years.
>
> The 2025 budget proposal can be found at
> https://github.com/MapServer/MapServer/wiki/MapServer-2025-Budget
>
> I'll start with my +1.
>
> Seth
>
> --
> mastodon: @geographika at mastodon.social
> _______________________________________________
> MapServer-dev mailing list
> MapServer-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20260107/c1dd59bb/attachment.htm>

From dmorissette at mapgears.com  Wed Jan  7 07:38:08 2026
From: dmorissette at mapgears.com (Daniel Morissette)
Date: Wed, 7 Jan 2026 10:38:08 -0500
Subject: [MapServer-dev] Proposal: OSGeo Budget 2026
In-Reply-To: <06986364-9e6d-49f5-983d-83f7ff650152@app.fastmail.com>
References: <06986364-9e6d-49f5-983d-83f7ff650152@app.fastmail.com>
Message-ID: <4322cac9-e6a8-43de-acdc-fb3a968a95bf@mapgears.com>

+1

Daniel


On 2026-01-07 03:37, Seth G via MapServer-dev wrote:
> Hi all,
>
> The deadline for budget requests is fast approaching. Seehttps://wiki.osgeo.org/wiki/OSGeo_Budget_2026
> The page includes the line "Board decided that the maximum amount per project this year cannot be more than $2,000 USD." Rather than requesting more than this and having to revise the budget again later. I propose we submit a request for:
>
> - $1,000 for codesprint and workshop attendance
> - $1,000 for release manager support
>
> If funds are required for emergency operations such as vulnerabilities, I think we should make a request to the board as and when needed. As mentioned by Mike in a previous thread, there have been no sponsorship funds for MapServer for the last 2 (maybe more) years.
>
> The 2025 budget proposal can be found athttps://github.com/MapServer/MapServer/wiki/MapServer-2025-Budget
>
> I'll start with my +1.
>
> Seth
>
> --
> mastodon: @geographika at mastodon.social
> _______________________________________________
> MapServer-dev mailing list
> MapServer-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-dev


-- 
Daniel Morissette
Mapgears Inc
T: +1 418-696-5056 #201
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20260107/70287c5c/attachment.htm>

From sdlime at gmail.com  Wed Jan  7 08:52:19 2026
From: sdlime at gmail.com (Steve Lime)
Date: Wed, 7 Jan 2026 10:52:19 -0600
Subject: [MapServer-dev] Fwd: OGC Compliance Renewal Notification - 30
 Day Expiration Notice
In-Reply-To: <963d3e39-9d57-4313-a1c9-fde32b47a8aa@gmail.com>
References: <1765361161.695827.236279.nullmailer@tic.ogc.org>
 <c2a46fb8-bca8-4c2b-aca1-0d5273c31bbb@gmail.com>
 <963d3e39-9d57-4313-a1c9-fde32b47a8aa@gmail.com>
Message-ID: <CAMrKZ9_4kTuWwFP2FvobbqjJnAw_UXmZSj05jPfdkVMEgZ2jwQ@mail.gmail.com>

Feels like you should continue w/submission - unless someone is working
through the CITE tests w/MapServer?

On Sun, Jan 4, 2026 at 8:36?AM Angelos Tzotsos via MapServer-dev <
mapserver-dev at lists.osgeo.org> wrote:

> Happy New Year!
>
> I have prepared the new compliance submission including CITE tests from
> pycsw, GeoServer and pygeoapi.
> I have kept MapServer and GDAL listed, as last year.
> Should I wait for new tests or should I continue with submission?
>
> Best regards,
> Angelos
>
> On 12/10/25 14:57, Angelos Tzotsos wrote:
> > Dear all,
> >
> > Please prepare your OGC CITE tests and let us know by the end of the
> > month so we can prepare the submission.
> >
> > Best regards,
> > Angelos
> >
> >
> > -------- Forwarded Message --------
> > Subject:     OGC Compliance Renewal Notification - 30 Day Expiration
> > Notice
> > Date:     Wed, 10 Dec 2025 10:06:01 +0000
> > From:     compliance at ogc.org
> > Reply-To:     compliance at ogc.org
> > To:     info at osgeo.org
> > CC:     Angelos Tzotsos <tzotsos at osgeo.org>, Michael Smith
> > <info at osgeo.org>, Even Roualt <even.rouault at spatialys.com>
> >
> >
> >
> >  Open Source Geospatial Foundation (OSGeo)
> >
> > 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, 2026*. 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.
> >
> > If you have already received an earlier notice and have started the
> > renewal process please ignore this message.
> >
> > 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 3.10
> >
> > Specification(s)     Original Certification
> > OGC GeoTIFF Standard 1.1
> > (OGC Reference Implementation)     2025-01-10
> > OGC KML 2.2.0
> > (OGC Reference Implementation)     2025-01-10
> > OGC KML (Level 2) 2.2.0
> > (OGC Reference Implementation)     2025-01-10
> > OGC KML (Level 3) 2.2.0
> > (OGC Reference Implementation)     2025-01-10
> > OGC? GeoPackage Encoding Standard 1.2
> > (OGC Reference Implementation)     2025-01-10
> > OGC? GeoPackage Encoding Standard: Extension Mechanism 1.2
> > (OGC Reference Implementation)     2025-01-10
> > OGC? GeoPackage Encoding Standard: Features 1.2
> > (OGC Reference Implementation)     2025-01-10
> > OGC? GeoPackage Encoding Standard: Metadata 1.2
> > (OGC Reference Implementation)     2025-01-10
> > OGC? GeoPackage Encoding Standard: RTree Spatial Indexes 1.2
> > (OGC Reference Implementation)     2025-01-10
> > OGC? GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core 2.0
> > (OGC Reference Implementation)     2025-01-10
> >
> >
> >      GeoServer 2.27
> >
> > Specification(s)     Original Certification
> > OGC API - Features - Part 1: Core 1.0     2025-07-10
> > OGC API - Features - Part 2: Coordinate Reference Systems by Reference
> > 1.0     2025-07-10
> > OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard 1.0
> > (OGC Reference Implementation)     2025-07-10
> > OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Acquisition
> > Information 1.0
> > (OGC Reference Implementation)     2025-07-10
> > OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Acquisition
> > Parameters 1.0
> > (OGC Reference Implementation)     2025-07-10
> > OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Data
> > Identification 1.0
> > (OGC Reference Implementation)     2025-07-10
> > OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Earth
> > Observation 1.0
> > (OGC Reference Implementation)     2025-07-10
> > OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Earth
> > Observation Collection 1.0
> > (OGC Reference Implementation)     2025-07-10
> > OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Geometry 1.0
> > (OGC Reference Implementation)     2025-07-10
> > OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Links 1.0
> > (OGC Reference Implementation)     2025-07-10
> > OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Metadata
> > Information 1.0
> > (OGC Reference Implementation)     2025-07-10
> > OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Offering 1.0
> > (OGC Reference Implementation)     2025-07-10
> > OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Product
> > Information 1.0
> > (OGC Reference Implementation)     2025-07-10
> > OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Properties 1.0
> > (OGC Reference Implementation)     2025-07-10
> > OGC GeoTIFF Standard 1.1
> > (OGC Reference Implementation)     2025-07-10
> > OGC? GeoPackage Encoding Standard 1.2
> > (OGC Reference Implementation)     2025-07-10
> > OGC? GeoPackage Encoding Standard: Extension Mechanism 1.2
> > (OGC Reference Implementation)     2025-07-10
> > OGC? GeoPackage Encoding Standard: Features 1.2
> > (OGC Reference Implementation)     2025-07-10
> > OGC? GeoPackage Encoding Standard: Metadata 1.2
> > (OGC Reference Implementation)     2025-07-10
> > OGC? GeoPackage Encoding Standard: RTree Spatial Indexes 1.2
> > (OGC Reference Implementation)     2025-07-10
> > OGC? GeoPackage Encoding Standard: Schema 1.2
> > (OGC Reference Implementation)     2025-07-10
> > OGC? WCS 2.0 Interface Standard- Core: Corrigendum 2.0.1
> > (OGC Reference Implementation)     2025-07-10
> > OGC? Web Coverage Service Interface Standard - Interpolation Extension
> > 1.0
> > (OGC Reference Implementation)     2025-07-10
> > OGC? Web Coverage Service Interface Standard - Scaling Extension 1.0
> > (OGC Reference Implementation)     2025-07-10
> > OGC? Web Coverage Service Interface Standard - CRS Extension 1.0
> > (OGC Reference Implementation)     2025-07-10
> > OGC? Web Coverage Service Interface Standard - Range Subsetting
> > Extension 1.0
> > (OGC Reference Implementation)     2025-07-10
> > OpenGIS Web Coverage Service (WCS) Implementation Specification
> > (Corrigendum) 1.0.0
> > (OGC Reference Implementation)     2025-07-10
> > OpenGIS Web Coverage Service (WCS) Implementation Specification
> > Corrigendum 1 1.1.1
> > (OGC Reference Implementation)     2025-07-10
> > OpenGIS Web Feature Service (WFS) Implementation Specification 1.1.0
> > 2025-07-10
> > OpenGIS Web Feature Service (WFS) Implementation Specification (Basic)
> > 1.1.0     2025-07-10
> > OpenGIS Web Feature Service (WFS) Implementation Specification
> > (Transactional) 1.1.0     2025-07-10
> > OpenGIS Web Feature Service - Basic 2.0     2025-07-10
> > OpenGIS Web Feature Service - Locking 2.0     2025-07-10
> > OpenGIS Web Feature Service - Transactional 2.0     2025-07-10
> > OpenGIS Web Feature Service 2.0 Interface Standard (also ISO 19142)
> > 2.0 2025-07-10
> > OpenGIS Web Map Service (WMS) Implementation Specification 1.3.0
> > 2025-07-10
> > OpenGIS Web Map Tile Service Implementation Standard 1.0.0 2025-07-10
> > Web Feature Service 1.0.0
> > (OGC Reference Implementation)     2025-07-10
> > Web Feature Service (Transactional) 1.0.0
> > (OGC Reference Implementation)     2025-07-10
> > Web Map Service 1.1.1     2025-07-10
> >
> >
> >      istSOS 2.3.1
> >
> > Specification(s)     Original Certification
> > OpenGIS Sensor Observation Service 1.0.0
> > (OGC Reference Implementation)     2018-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.19.0
> >
> > Specification(s)     Original Certification
> > OGC API - Environmental Data Retrieval Standard 1.0.1
> > (OGC Reference Implementation)     2025-01-10
> > OGC API - Environmental Data Retrieval Standard: Collections 1.0.1
> > (OGC Reference Implementation)     2025-01-10
> > OGC API - Environmental Data Retrieval Standard: CoverageJSON 1.0.1
> > (OGC Reference Implementation)     2025-01-10
> > OGC API - Environmental Data Retrieval Standard: EDRGeoJSON 1.0.1
> > (OGC Reference Implementation)     2025-01-10
> > OGC API - Environmental Data Retrieval Standard: GeoJSON 1.0.1
> > (OGC Reference Implementation)     2025-01-10
> > OGC API - Environmental Data Retrieval Standard: HTML 1.0.1
> > (OGC Reference Implementation)     2025-01-10
> > OGC API - Environmental Data Retrieval Standard: JSON 1.0.1
> > (OGC Reference Implementation)     2025-01-10
> > OGC API - Features - Part 1: Core 1.0
> > (OGC Reference Implementation)     2025-01-10
> > OGC API - Tiles - Part 1: Core 1.0
> > (OGC Reference Implementation)     2025-01-10
> > OGC API - Tiles - Part 1: DatasetTilesets 1.0
> > (OGC Reference Implementation)     2025-01-10
> > OGC API - Tiles - Part 1: GeoDataTilesets 1.0
> > (OGC Reference Implementation)     2025-01-10
> >
> >
> >
>
> --
> Angelos Tzotsos, PhD
> President, Board of Directors
> Open Source Geospatial Foundation
> https://www.osgeo.org/member/angelos-tzotsos/
>
>
> _______________________________________________
> MapServer-dev mailing list
> MapServer-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20260107/6372f456/attachment-0001.htm>

From gcpp.kalxas at gmail.com  Thu Jan  8 07:34:20 2026
From: gcpp.kalxas at gmail.com (Angelos Tzotsos)
Date: Thu, 8 Jan 2026 17:34:20 +0200
Subject: [MapServer-dev] Fwd: OGC Compliance Renewal Notification - 30
 Day Expiration Notice
In-Reply-To: <963d3e39-9d57-4313-a1c9-fde32b47a8aa@gmail.com>
References: <1765361161.695827.236279.nullmailer@tic.ogc.org>
 <c2a46fb8-bca8-4c2b-aca1-0d5273c31bbb@gmail.com>
 <963d3e39-9d57-4313-a1c9-fde32b47a8aa@gmail.com>
Message-ID: <8edf1a4b-1688-428f-b9b3-71204aa02eb9@gmail.com>

Hi all,

The compliance submission has been completed.
We are waiting for feedback from OGC.

Best,
Angelos

On 1/4/26 16:36, Angelos Tzotsos wrote:
> Happy New Year!
>
> I have prepared the new compliance submission including CITE tests 
> from pycsw, GeoServer and pygeoapi.
> I have kept MapServer and GDAL listed, as last year.
> Should I wait for new tests or should I continue with submission?
>
> Best regards,
> Angelos
>
> On 12/10/25 14:57, Angelos Tzotsos wrote:
>> Dear all,
>>
>> Please prepare your OGC CITE tests and let us know by the end of the 
>> month so we can prepare the submission.
>>
>> Best regards,
>> Angelos
>>
>>
>> -------- Forwarded Message --------
>> Subject:???? OGC Compliance Renewal Notification - 30 Day Expiration 
>> Notice
>> Date:???? Wed, 10 Dec 2025 10:06:01 +0000
>> From:???? compliance at ogc.org
>> Reply-To:???? compliance at ogc.org
>> To:???? info at osgeo.org
>> CC:???? Angelos Tzotsos <tzotsos at osgeo.org>, Michael Smith 
>> <info at osgeo.org>, Even Roualt <even.rouault at spatialys.com>
>>
>>
>>
>> ?Open Source Geospatial Foundation (OSGeo)
>>
>> 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, 2026*. 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.
>>
>> If you have already received an earlier notice and have started the 
>> renewal process please ignore this message.
>>
>> 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 3.10
>>
>> Specification(s)???? Original Certification
>> OGC GeoTIFF Standard 1.1
>> (OGC Reference Implementation)???? 2025-01-10
>> OGC KML 2.2.0
>> (OGC Reference Implementation)???? 2025-01-10
>> OGC KML (Level 2) 2.2.0
>> (OGC Reference Implementation)???? 2025-01-10
>> OGC KML (Level 3) 2.2.0
>> (OGC Reference Implementation)???? 2025-01-10
>> OGC? GeoPackage Encoding Standard 1.2
>> (OGC Reference Implementation)???? 2025-01-10
>> OGC? GeoPackage Encoding Standard: Extension Mechanism 1.2
>> (OGC Reference Implementation)???? 2025-01-10
>> OGC? GeoPackage Encoding Standard: Features 1.2
>> (OGC Reference Implementation)???? 2025-01-10
>> OGC? GeoPackage Encoding Standard: Metadata 1.2
>> (OGC Reference Implementation)???? 2025-01-10
>> OGC? GeoPackage Encoding Standard: RTree Spatial Indexes 1.2
>> (OGC Reference Implementation)???? 2025-01-10
>> OGC? GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core 2.0
>> (OGC Reference Implementation)???? 2025-01-10
>>
>>
>> ???? GeoServer 2.27
>>
>> Specification(s)???? Original Certification
>> OGC API - Features - Part 1: Core 1.0???? 2025-07-10
>> OGC API - Features - Part 2: Coordinate Reference Systems by 
>> Reference 1.0???? 2025-07-10
>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard 1.0
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Acquisition 
>> Information 1.0
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Acquisition 
>> Parameters 1.0
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Data 
>> Identification 1.0
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Earth 
>> Observation 1.0
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Earth 
>> Observation Collection 1.0
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Geometry 1.0
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Links 1.0
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Metadata 
>> Information 1.0
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Offering 1.0
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Product 
>> Information 1.0
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Properties 1.0
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC GeoTIFF Standard 1.1
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC? GeoPackage Encoding Standard 1.2
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC? GeoPackage Encoding Standard: Extension Mechanism 1.2
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC? GeoPackage Encoding Standard: Features 1.2
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC? GeoPackage Encoding Standard: Metadata 1.2
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC? GeoPackage Encoding Standard: RTree Spatial Indexes 1.2
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC? GeoPackage Encoding Standard: Schema 1.2
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC? WCS 2.0 Interface Standard- Core: Corrigendum 2.0.1
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC? Web Coverage Service Interface Standard - Interpolation 
>> Extension 1.0
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC? Web Coverage Service Interface Standard - Scaling Extension 1.0
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC? Web Coverage Service Interface Standard - CRS Extension 1.0
>> (OGC Reference Implementation)???? 2025-07-10
>> OGC? Web Coverage Service Interface Standard - Range Subsetting 
>> Extension 1.0
>> (OGC Reference Implementation)???? 2025-07-10
>> OpenGIS Web Coverage Service (WCS) Implementation Specification 
>> (Corrigendum) 1.0.0
>> (OGC Reference Implementation)???? 2025-07-10
>> OpenGIS Web Coverage Service (WCS) Implementation Specification 
>> Corrigendum 1 1.1.1
>> (OGC Reference Implementation)???? 2025-07-10
>> OpenGIS Web Feature Service (WFS) Implementation Specification 1.1.0 
>> 2025-07-10
>> OpenGIS Web Feature Service (WFS) Implementation Specification 
>> (Basic) 1.1.0???? 2025-07-10
>> OpenGIS Web Feature Service (WFS) Implementation Specification 
>> (Transactional) 1.1.0???? 2025-07-10
>> OpenGIS Web Feature Service - Basic 2.0???? 2025-07-10
>> OpenGIS Web Feature Service - Locking 2.0???? 2025-07-10
>> OpenGIS Web Feature Service - Transactional 2.0???? 2025-07-10
>> OpenGIS Web Feature Service 2.0 Interface Standard (also ISO 19142) 
>> 2.0 2025-07-10
>> OpenGIS Web Map Service (WMS) Implementation Specification 1.3.0 
>> 2025-07-10
>> OpenGIS Web Map Tile Service Implementation Standard 1.0.0 2025-07-10
>> Web Feature Service 1.0.0
>> (OGC Reference Implementation)???? 2025-07-10
>> Web Feature Service (Transactional) 1.0.0
>> (OGC Reference Implementation)???? 2025-07-10
>> Web Map Service 1.1.1???? 2025-07-10
>>
>>
>> ???? istSOS 2.3.1
>>
>> Specification(s)???? Original Certification
>> OpenGIS Sensor Observation Service 1.0.0
>> (OGC Reference Implementation)???? 2018-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.19.0
>>
>> Specification(s)???? Original Certification
>> OGC API - Environmental Data Retrieval Standard 1.0.1
>> (OGC Reference Implementation)???? 2025-01-10
>> OGC API - Environmental Data Retrieval Standard: Collections 1.0.1
>> (OGC Reference Implementation)???? 2025-01-10
>> OGC API - Environmental Data Retrieval Standard: CoverageJSON 1.0.1
>> (OGC Reference Implementation)???? 2025-01-10
>> OGC API - Environmental Data Retrieval Standard: EDRGeoJSON 1.0.1
>> (OGC Reference Implementation)???? 2025-01-10
>> OGC API - Environmental Data Retrieval Standard: GeoJSON 1.0.1
>> (OGC Reference Implementation)???? 2025-01-10
>> OGC API - Environmental Data Retrieval Standard: HTML 1.0.1
>> (OGC Reference Implementation)???? 2025-01-10
>> OGC API - Environmental Data Retrieval Standard: JSON 1.0.1
>> (OGC Reference Implementation)???? 2025-01-10
>> OGC API - Features - Part 1: Core 1.0
>> (OGC Reference Implementation)???? 2025-01-10
>> OGC API - Tiles - Part 1: Core 1.0
>> (OGC Reference Implementation)???? 2025-01-10
>> OGC API - Tiles - Part 1: DatasetTilesets 1.0
>> (OGC Reference Implementation)???? 2025-01-10
>> OGC API - Tiles - Part 1: GeoDataTilesets 1.0
>> (OGC Reference Implementation)???? 2025-01-10
>>
>>
>>
>

-- 
Angelos Tzotsos, PhD
President, Board of Directors
Open Source Geospatial Foundation
https://www.osgeo.org/member/angelos-tzotsos/



From sethg at geographika.co.uk  Sat Jan 10 02:02:29 2026
From: sethg at geographika.co.uk (Seth G)
Date: Sat, 10 Jan 2026 11:02:29 +0100
Subject: [MapServer-dev] Proposal: OSGeo Budget 2026
In-Reply-To: <4322cac9-e6a8-43de-acdc-fb3a968a95bf@mapgears.com>
References: <06986364-9e6d-49f5-983d-83f7ff650152@app.fastmail.com>
 <4322cac9-e6a8-43de-acdc-fb3a968a95bf@mapgears.com>
Message-ID: <691acc6c-adb1-4866-8e10-dde9c1a0d91e@app.fastmail.com>

Thanks all for voting, with +1s from Seth, Mike, Even, Jukka, Tom, J?rome, Steve, and Daniel. 

I have created a wiki page at https://github.com/MapServer/MapServer/wiki/MapServer-2026-Budget and submitted the budget proposal to the board - see https://lists.osgeo.org/pipermail/board/2026-January/013807.html.

Seth


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20260110/ea00f971/attachment.htm>

From gcpp.kalxas at gmail.com  Tue Jan 13 09:45:30 2026
From: gcpp.kalxas at gmail.com (Angelos Tzotsos)
Date: Tue, 13 Jan 2026 19:45:30 +0200
Subject: [MapServer-dev] Fwd: OGC Compliance Renewal Notification - 30
 Day Expiration Notice
In-Reply-To: <8edf1a4b-1688-428f-b9b3-71204aa02eb9@gmail.com>
References: <1765361161.695827.236279.nullmailer@tic.ogc.org>
 <c2a46fb8-bca8-4c2b-aca1-0d5273c31bbb@gmail.com>
 <963d3e39-9d57-4313-a1c9-fde32b47a8aa@gmail.com>
 <8edf1a4b-1688-428f-b9b3-71204aa02eb9@gmail.com>
Message-ID: <f9e0eedf-8a9d-4dfc-b91d-ee9db11de6e7@gmail.com>

Hi all.

The submission has been approved:

https://portal.ogc.org/public_ogc/compliance/compliant.php?display_opt=1&org_match=Open%20Source%20Geospatial%20Foundation

Thanks all for your feedback and testing.

Regards,
Angelos

On 1/8/26 17:34, Angelos Tzotsos wrote:
> Hi all,
>
> The compliance submission has been completed.
> We are waiting for feedback from OGC.
>
> Best,
> Angelos
>
> On 1/4/26 16:36, Angelos Tzotsos wrote:
>> Happy New Year!
>>
>> I have prepared the new compliance submission including CITE tests 
>> from pycsw, GeoServer and pygeoapi.
>> I have kept MapServer and GDAL listed, as last year.
>> Should I wait for new tests or should I continue with submission?
>>
>> Best regards,
>> Angelos
>>
>> On 12/10/25 14:57, Angelos Tzotsos wrote:
>>> Dear all,
>>>
>>> Please prepare your OGC CITE tests and let us know by the end of the 
>>> month so we can prepare the submission.
>>>
>>> Best regards,
>>> Angelos
>>>
>>>
>>> -------- Forwarded Message --------
>>> Subject:???? OGC Compliance Renewal Notification - 30 Day Expiration 
>>> Notice
>>> Date:???? Wed, 10 Dec 2025 10:06:01 +0000
>>> From:???? compliance at ogc.org
>>> Reply-To:???? compliance at ogc.org
>>> To:???? info at osgeo.org
>>> CC:???? Angelos Tzotsos <tzotsos at osgeo.org>, Michael Smith 
>>> <info at osgeo.org>, Even Roualt <even.rouault at spatialys.com>
>>>
>>>
>>>
>>> ?Open Source Geospatial Foundation (OSGeo)
>>>
>>> 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, 2026*. 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.
>>>
>>> If you have already received an earlier notice and have started the 
>>> renewal process please ignore this message.
>>>
>>> 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 3.10
>>>
>>> Specification(s)???? Original Certification
>>> OGC GeoTIFF Standard 1.1
>>> (OGC Reference Implementation)???? 2025-01-10
>>> OGC KML 2.2.0
>>> (OGC Reference Implementation)???? 2025-01-10
>>> OGC KML (Level 2) 2.2.0
>>> (OGC Reference Implementation)???? 2025-01-10
>>> OGC KML (Level 3) 2.2.0
>>> (OGC Reference Implementation)???? 2025-01-10
>>> OGC? GeoPackage Encoding Standard 1.2
>>> (OGC Reference Implementation)???? 2025-01-10
>>> OGC? GeoPackage Encoding Standard: Extension Mechanism 1.2
>>> (OGC Reference Implementation)???? 2025-01-10
>>> OGC? GeoPackage Encoding Standard: Features 1.2
>>> (OGC Reference Implementation)???? 2025-01-10
>>> OGC? GeoPackage Encoding Standard: Metadata 1.2
>>> (OGC Reference Implementation)???? 2025-01-10
>>> OGC? GeoPackage Encoding Standard: RTree Spatial Indexes 1.2
>>> (OGC Reference Implementation)???? 2025-01-10
>>> OGC? GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core 2.0
>>> (OGC Reference Implementation)???? 2025-01-10
>>>
>>>
>>> ???? GeoServer 2.27
>>>
>>> Specification(s)???? Original Certification
>>> OGC API - Features - Part 1: Core 1.0???? 2025-07-10
>>> OGC API - Features - Part 2: Coordinate Reference Systems by 
>>> Reference 1.0???? 2025-07-10
>>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard 1.0
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Acquisition 
>>> Information 1.0
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Acquisition 
>>> Parameters 1.0
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Data 
>>> Identification 1.0
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Earth 
>>> Observation 1.0
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Earth 
>>> Observation Collection 1.0
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Geometry 1.0
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Links 1.0
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Metadata 
>>> Information 1.0
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Offering 1.0
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Product 
>>> Information 1.0
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Properties 1.0
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC GeoTIFF Standard 1.1
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC? GeoPackage Encoding Standard 1.2
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC? GeoPackage Encoding Standard: Extension Mechanism 1.2
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC? GeoPackage Encoding Standard: Features 1.2
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC? GeoPackage Encoding Standard: Metadata 1.2
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC? GeoPackage Encoding Standard: RTree Spatial Indexes 1.2
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC? GeoPackage Encoding Standard: Schema 1.2
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC? WCS 2.0 Interface Standard- Core: Corrigendum 2.0.1
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC? Web Coverage Service Interface Standard - Interpolation 
>>> Extension 1.0
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC? Web Coverage Service Interface Standard - Scaling Extension 1.0
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC? Web Coverage Service Interface Standard - CRS Extension 1.0
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OGC? Web Coverage Service Interface Standard - Range Subsetting 
>>> Extension 1.0
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OpenGIS Web Coverage Service (WCS) Implementation Specification 
>>> (Corrigendum) 1.0.0
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OpenGIS Web Coverage Service (WCS) Implementation Specification 
>>> Corrigendum 1 1.1.1
>>> (OGC Reference Implementation)???? 2025-07-10
>>> OpenGIS Web Feature Service (WFS) Implementation Specification 1.1.0 
>>> 2025-07-10
>>> OpenGIS Web Feature Service (WFS) Implementation Specification 
>>> (Basic) 1.1.0???? 2025-07-10
>>> OpenGIS Web Feature Service (WFS) Implementation Specification 
>>> (Transactional) 1.1.0???? 2025-07-10
>>> OpenGIS Web Feature Service - Basic 2.0???? 2025-07-10
>>> OpenGIS Web Feature Service - Locking 2.0???? 2025-07-10
>>> OpenGIS Web Feature Service - Transactional 2.0???? 2025-07-10
>>> OpenGIS Web Feature Service 2.0 Interface Standard (also ISO 19142) 
>>> 2.0 2025-07-10
>>> OpenGIS Web Map Service (WMS) Implementation Specification 1.3.0 
>>> 2025-07-10
>>> OpenGIS Web Map Tile Service Implementation Standard 1.0.0 2025-07-10
>>> Web Feature Service 1.0.0
>>> (OGC Reference Implementation)???? 2025-07-10
>>> Web Feature Service (Transactional) 1.0.0
>>> (OGC Reference Implementation)???? 2025-07-10
>>> Web Map Service 1.1.1???? 2025-07-10
>>>
>>>
>>> ???? istSOS 2.3.1
>>>
>>> Specification(s)???? Original Certification
>>> OpenGIS Sensor Observation Service 1.0.0
>>> (OGC Reference Implementation)???? 2018-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.19.0
>>>
>>> Specification(s)???? Original Certification
>>> OGC API - Environmental Data Retrieval Standard 1.0.1
>>> (OGC Reference Implementation)???? 2025-01-10
>>> OGC API - Environmental Data Retrieval Standard: Collections 1.0.1
>>> (OGC Reference Implementation)???? 2025-01-10
>>> OGC API - Environmental Data Retrieval Standard: CoverageJSON 1.0.1
>>> (OGC Reference Implementation)???? 2025-01-10
>>> OGC API - Environmental Data Retrieval Standard: EDRGeoJSON 1.0.1
>>> (OGC Reference Implementation)???? 2025-01-10
>>> OGC API - Environmental Data Retrieval Standard: GeoJSON 1.0.1
>>> (OGC Reference Implementation)???? 2025-01-10
>>> OGC API - Environmental Data Retrieval Standard: HTML 1.0.1
>>> (OGC Reference Implementation)???? 2025-01-10
>>> OGC API - Environmental Data Retrieval Standard: JSON 1.0.1
>>> (OGC Reference Implementation)???? 2025-01-10
>>> OGC API - Features - Part 1: Core 1.0
>>> (OGC Reference Implementation)???? 2025-01-10
>>> OGC API - Tiles - Part 1: Core 1.0
>>> (OGC Reference Implementation)???? 2025-01-10
>>> OGC API - Tiles - Part 1: DatasetTilesets 1.0
>>> (OGC Reference Implementation)???? 2025-01-10
>>> OGC API - Tiles - Part 1: GeoDataTilesets 1.0
>>> (OGC Reference Implementation)???? 2025-01-10
>>>
>>>
>>>
>>
>

-- 
Angelos Tzotsos, PhD
President, Board of Directors
Open Source Geospatial Foundation
https://www.osgeo.org/member/angelos-tzotsos/



From andrea.aime at geo-solutions.it  Tue Jan 13 10:19:50 2026
From: andrea.aime at geo-solutions.it (Andrea Aime)
Date: Tue, 13 Jan 2026 19:19:50 +0100
Subject: [MapServer-dev] Fwd: OGC Compliance Renewal Notification - 30
 Day Expiration Notice
In-Reply-To: <f9e0eedf-8a9d-4dfc-b91d-ee9db11de6e7@gmail.com>
References: <1765361161.695827.236279.nullmailer@tic.ogc.org>
 <c2a46fb8-bca8-4c2b-aca1-0d5273c31bbb@gmail.com>
 <963d3e39-9d57-4313-a1c9-fde32b47a8aa@gmail.com>
 <8edf1a4b-1688-428f-b9b3-71204aa02eb9@gmail.com>
 <f9e0eedf-8a9d-4dfc-b91d-ee9db11de6e7@gmail.com>
Message-ID: <CALHQADU-+geozX6JQcZk7TbgpZQQF-f7H+N9uCfU4zCjNQJ4BA@mail.gmail.com>

Nice! And thanks for pushing this forward!

Cheers
Andrea

On Tue, Jan 13, 2026 at 6:45?PM Angelos Tzotsos <gcpp.kalxas at gmail.com>
wrote:

> Hi all.
>
> The submission has been approved:
>
>
> https://portal.ogc.org/public_ogc/compliance/compliant.php?display_opt=1&org_match=Open%20Source%20Geospatial%20Foundation
>
> Thanks all for your feedback and testing.
>
> Regards,
> Angelos
>
> On 1/8/26 17:34, Angelos Tzotsos wrote:
> > Hi all,
> >
> > The compliance submission has been completed.
> > We are waiting for feedback from OGC.
> >
> > Best,
> > Angelos
> >
> > On 1/4/26 16:36, Angelos Tzotsos wrote:
> >> Happy New Year!
> >>
> >> I have prepared the new compliance submission including CITE tests
> >> from pycsw, GeoServer and pygeoapi.
> >> I have kept MapServer and GDAL listed, as last year.
> >> Should I wait for new tests or should I continue with submission?
> >>
> >> Best regards,
> >> Angelos
> >>
> >> On 12/10/25 14:57, Angelos Tzotsos wrote:
> >>> Dear all,
> >>>
> >>> Please prepare your OGC CITE tests and let us know by the end of the
> >>> month so we can prepare the submission.
> >>>
> >>> Best regards,
> >>> Angelos
> >>>
> >>>
> >>> -------- Forwarded Message --------
> >>> Subject:     OGC Compliance Renewal Notification - 30 Day Expiration
> >>> Notice
> >>> Date:     Wed, 10 Dec 2025 10:06:01 +0000
> >>> From:     compliance at ogc.org
> >>> Reply-To:     compliance at ogc.org
> >>> To:     info at osgeo.org
> >>> CC:     Angelos Tzotsos <tzotsos at osgeo.org>, Michael Smith
> >>> <info at osgeo.org>, Even Roualt <even.rouault at spatialys.com>
> >>>
> >>>
> >>>
> >>>  Open Source Geospatial Foundation (OSGeo)
> >>>
> >>> 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, 2026*. 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.
> >>>
> >>> If you have already received an earlier notice and have started the
> >>> renewal process please ignore this message.
> >>>
> >>> 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 3.10
> >>>
> >>> Specification(s)     Original Certification
> >>> OGC GeoTIFF Standard 1.1
> >>> (OGC Reference Implementation)     2025-01-10
> >>> OGC KML 2.2.0
> >>> (OGC Reference Implementation)     2025-01-10
> >>> OGC KML (Level 2) 2.2.0
> >>> (OGC Reference Implementation)     2025-01-10
> >>> OGC KML (Level 3) 2.2.0
> >>> (OGC Reference Implementation)     2025-01-10
> >>> OGC? GeoPackage Encoding Standard 1.2
> >>> (OGC Reference Implementation)     2025-01-10
> >>> OGC? GeoPackage Encoding Standard: Extension Mechanism 1.2
> >>> (OGC Reference Implementation)     2025-01-10
> >>> OGC? GeoPackage Encoding Standard: Features 1.2
> >>> (OGC Reference Implementation)     2025-01-10
> >>> OGC? GeoPackage Encoding Standard: Metadata 1.2
> >>> (OGC Reference Implementation)     2025-01-10
> >>> OGC? GeoPackage Encoding Standard: RTree Spatial Indexes 1.2
> >>> (OGC Reference Implementation)     2025-01-10
> >>> OGC? GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core 2.0
> >>> (OGC Reference Implementation)     2025-01-10
> >>>
> >>>
> >>>      GeoServer 2.27
> >>>
> >>> Specification(s)     Original Certification
> >>> OGC API - Features - Part 1: Core 1.0     2025-07-10
> >>> OGC API - Features - Part 2: Coordinate Reference Systems by
> >>> Reference 1.0     2025-07-10
> >>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard 1.0
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Acquisition
> >>> Information 1.0
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Acquisition
> >>> Parameters 1.0
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Data
> >>> Identification 1.0
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Earth
> >>> Observation 1.0
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Earth
> >>> Observation Collection 1.0
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Geometry 1.0
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Links 1.0
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Metadata
> >>> Information 1.0
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Offering 1.0
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Product
> >>> Information 1.0
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Properties 1.0
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC GeoTIFF Standard 1.1
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC? GeoPackage Encoding Standard 1.2
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC? GeoPackage Encoding Standard: Extension Mechanism 1.2
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC? GeoPackage Encoding Standard: Features 1.2
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC? GeoPackage Encoding Standard: Metadata 1.2
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC? GeoPackage Encoding Standard: RTree Spatial Indexes 1.2
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC? GeoPackage Encoding Standard: Schema 1.2
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC? WCS 2.0 Interface Standard- Core: Corrigendum 2.0.1
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC? Web Coverage Service Interface Standard - Interpolation
> >>> Extension 1.0
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC? Web Coverage Service Interface Standard - Scaling Extension 1.0
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC? Web Coverage Service Interface Standard - CRS Extension 1.0
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OGC? Web Coverage Service Interface Standard - Range Subsetting
> >>> Extension 1.0
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OpenGIS Web Coverage Service (WCS) Implementation Specification
> >>> (Corrigendum) 1.0.0
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OpenGIS Web Coverage Service (WCS) Implementation Specification
> >>> Corrigendum 1 1.1.1
> >>> (OGC Reference Implementation)     2025-07-10
> >>> OpenGIS Web Feature Service (WFS) Implementation Specification 1.1.0
> >>> 2025-07-10
> >>> OpenGIS Web Feature Service (WFS) Implementation Specification
> >>> (Basic) 1.1.0     2025-07-10
> >>> OpenGIS Web Feature Service (WFS) Implementation Specification
> >>> (Transactional) 1.1.0     2025-07-10
> >>> OpenGIS Web Feature Service - Basic 2.0     2025-07-10
> >>> OpenGIS Web Feature Service - Locking 2.0     2025-07-10
> >>> OpenGIS Web Feature Service - Transactional 2.0     2025-07-10
> >>> OpenGIS Web Feature Service 2.0 Interface Standard (also ISO 19142)
> >>> 2.0 2025-07-10
> >>> OpenGIS Web Map Service (WMS) Implementation Specification 1.3.0
> >>> 2025-07-10
> >>> OpenGIS Web Map Tile Service Implementation Standard 1.0.0 2025-07-10
> >>> Web Feature Service 1.0.0
> >>> (OGC Reference Implementation)     2025-07-10
> >>> Web Feature Service (Transactional) 1.0.0
> >>> (OGC Reference Implementation)     2025-07-10
> >>> Web Map Service 1.1.1     2025-07-10
> >>>
> >>>
> >>>      istSOS 2.3.1
> >>>
> >>> Specification(s)     Original Certification
> >>> OpenGIS Sensor Observation Service 1.0.0
> >>> (OGC Reference Implementation)     2018-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.19.0
> >>>
> >>> Specification(s)     Original Certification
> >>> OGC API - Environmental Data Retrieval Standard 1.0.1
> >>> (OGC Reference Implementation)     2025-01-10
> >>> OGC API - Environmental Data Retrieval Standard: Collections 1.0.1
> >>> (OGC Reference Implementation)     2025-01-10
> >>> OGC API - Environmental Data Retrieval Standard: CoverageJSON 1.0.1
> >>> (OGC Reference Implementation)     2025-01-10
> >>> OGC API - Environmental Data Retrieval Standard: EDRGeoJSON 1.0.1
> >>> (OGC Reference Implementation)     2025-01-10
> >>> OGC API - Environmental Data Retrieval Standard: GeoJSON 1.0.1
> >>> (OGC Reference Implementation)     2025-01-10
> >>> OGC API - Environmental Data Retrieval Standard: HTML 1.0.1
> >>> (OGC Reference Implementation)     2025-01-10
> >>> OGC API - Environmental Data Retrieval Standard: JSON 1.0.1
> >>> (OGC Reference Implementation)     2025-01-10
> >>> OGC API - Features - Part 1: Core 1.0
> >>> (OGC Reference Implementation)     2025-01-10
> >>> OGC API - Tiles - Part 1: Core 1.0
> >>> (OGC Reference Implementation)     2025-01-10
> >>> OGC API - Tiles - Part 1: DatasetTilesets 1.0
> >>> (OGC Reference Implementation)     2025-01-10
> >>> OGC API - Tiles - Part 1: GeoDataTilesets 1.0
> >>> (OGC Reference Implementation)     2025-01-10
> >>>
> >>>
> >>>
> >>
> >
>
> --
> 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: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20260113/a21292d0/attachment-0001.htm>

From sethg at geographika.co.uk  Mon Jan 19 13:13:47 2026
From: sethg at geographika.co.uk (Seth G)
Date: Mon, 19 Jan 2026 22:13:47 +0100
Subject: [MapServer-dev] MapServer User Survey
Message-ID: <aeaf6f2b-759d-49f0-bde7-285249290f37@app.fastmail.com>

Hi all,

At the last OSGeo codesprint, we discussed running a MapServer user survey, modelled on the GDAL survey [1]. Since MapServer has no analytics or "phone home" functionality, we have little insight into how it is used beyond mailing lists and in-person discussions.

A first draft of the survey is available for feedback:
https://docs.google.com/forms/d/e/1FAIpQLSfNLqslbM6IhocnwTst9c29eaD89yD81hdUKW2ctn2uZK0Z3g/viewform (please don't submit answers until we're happy with the questions!). 

Thanks to Howard for sharing the GDAL survey on which this is based.

Please let me know of any additional questions that should be added, or any edits to existing questions (options, phrasing etc.).

Unlike the GDAL survey, which informed budget decisions, the aim is to prioritise limited time and resources, identify features for potential deprecation, and highlight areas needing continued support.

It will also be interesting to see how many responses we get, as this will give a sense of overall interest in MapServer.

Seth

[1] https://gdal.org/en/stable/community/user_survey_2024.html

--
web:https://geographika.net & https://mapserverstudio.net
mastodon: @geographika at mastodon.social

From maris.gis at gmail.com  Mon Jan 19 23:33:01 2026
From: maris.gis at gmail.com (Maris Nartiss)
Date: Tue, 20 Jan 2026 09:33:01 +0200
Subject: [MapServer-dev] MapServer User Survey
In-Reply-To: <aeaf6f2b-759d-49f0-bde7-285249290f37@app.fastmail.com>
References: <aeaf6f2b-759d-49f0-bde7-285249290f37@app.fastmail.com>
Message-ID: <CAK8GbeC5_Xa-fOU9kN6aqRu2otX=ut55ok6=3OapZU1vPn=uag@mail.gmail.com>

Hello Seth,
"The web server run MapServer on most is" question is duplicated;
"I obtain MapServer from" should be rephrased to something like "For
production environments I obtain MapServer from" or should be made as
a multiple answer question (e.g. I use packages but also build from
source for dev needs);
One question to ask might be something like: "Within last X years I
have used MapServer for" (multiple choice): "commercial projects",
"volunteer projects", "just playing around".

Regards,
M?ris.

pirmd., 2026. g. 19. janv., plkst. 23:15 ? lietot?js Seth G via
MapServer-dev (<mapserver-dev at lists.osgeo.org>) rakst?ja:
>
> Hi all,
>
> At the last OSGeo codesprint, we discussed running a MapServer user survey, modelled on the GDAL survey [1]. Since MapServer has no analytics or "phone home" functionality, we have little insight into how it is used beyond mailing lists and in-person discussions.
>
> A first draft of the survey is available for feedback:
> https://docs.google.com/forms/d/e/1FAIpQLSfNLqslbM6IhocnwTst9c29eaD89yD81hdUKW2ctn2uZK0Z3g/viewform (please don't submit answers until we're happy with the questions!).
>
> Thanks to Howard for sharing the GDAL survey on which this is based.
>
> Please let me know of any additional questions that should be added, or any edits to existing questions (options, phrasing etc.).
>
> Unlike the GDAL survey, which informed budget decisions, the aim is to prioritise limited time and resources, identify features for potential deprecation, and highlight areas needing continued support.
>
> It will also be interesting to see how many responses we get, as this will give a sense of overall interest in MapServer.
>
> Seth
>
> [1] https://gdal.org/en/stable/community/user_survey_2024.html
>
> --
> web:https://geographika.net & https://mapserverstudio.net
> mastodon: @geographika at mastodon.social
> _______________________________________________
> MapServer-dev mailing list
> MapServer-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-dev

From sethg at geographika.co.uk  Tue Jan 20 02:25:59 2026
From: sethg at geographika.co.uk (Seth G)
Date: Tue, 20 Jan 2026 11:25:59 +0100
Subject: [MapServer-dev] MapServer User Survey
In-Reply-To: <CAK8GbeC5_Xa-fOU9kN6aqRu2otX=ut55ok6=3OapZU1vPn=uag@mail.gmail.com>
References: <aeaf6f2b-759d-49f0-bde7-285249290f37@app.fastmail.com>
 <CAK8GbeC5_Xa-fOU9kN6aqRu2otX=ut55ok6=3OapZU1vPn=uag@mail.gmail.com>
Message-ID: <0b684f30-7f6e-4375-915f-3d983e2687a4@app.fastmail.com>

Thanks M?ris for the feedback - I have updated the survey with your suggestions.

Seth

--
web:https://geographika.net & https://mapserverstudio.net
mastodon: @geographika at mastodon.social

On Tue, Jan 20, 2026, at 8:33 AM, Maris Nartiss wrote:
> Hello Seth,
> "The web server run MapServer on most is" question is duplicated;
> "I obtain MapServer from" should be rephrased to something like "For
> production environments I obtain MapServer from" or should be made as
> a multiple answer question (e.g. I use packages but also build from
> source for dev needs);
> One question to ask might be something like: "Within last X years I
> have used MapServer for" (multiple choice): "commercial projects",
> "volunteer projects", "just playing around".
>
> Regards,
> M?ris.
>
> pirmd., 2026. g. 19. janv., plkst. 23:15 ? lietot?js Seth G via
> MapServer-dev (<mapserver-dev at lists.osgeo.org>) rakst?ja:
>>
>> Hi all,
>>
>> At the last OSGeo codesprint, we discussed running a MapServer user survey, modelled on the GDAL survey [1]. Since MapServer has no analytics or "phone home" functionality, we have little insight into how it is used beyond mailing lists and in-person discussions.
>>
>> A first draft of the survey is available for feedback:
>> https://docs.google.com/forms/d/e/1FAIpQLSfNLqslbM6IhocnwTst9c29eaD89yD81hdUKW2ctn2uZK0Z3g/viewform (please don't submit answers until we're happy with the questions!).
>>
>> Thanks to Howard for sharing the GDAL survey on which this is based.
>>
>> Please let me know of any additional questions that should be added, or any edits to existing questions (options, phrasing etc.).
>>
>> Unlike the GDAL survey, which informed budget decisions, the aim is to prioritise limited time and resources, identify features for potential deprecation, and highlight areas needing continued support.
>>
>> It will also be interesting to see how many responses we get, as this will give a sense of overall interest in MapServer.
>>
>> Seth
>>
>> [1] https://gdal.org/en/stable/community/user_survey_2024.html
>>
>> --
>> web:https://geographika.net & https://mapserverstudio.net
>> mastodon: @geographika at mastodon.social
>> _______________________________________________
>> MapServer-dev mailing list
>> MapServer-dev at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/mapserver-dev

From sdlime at gmail.com  Tue Jan 20 09:59:46 2026
From: sdlime at gmail.com (Steve Lime)
Date: Tue, 20 Jan 2026 11:59:46 -0600
Subject: [MapServer-dev] MapServer User Survey
In-Reply-To: <0b684f30-7f6e-4375-915f-3d983e2687a4@app.fastmail.com>
References: <aeaf6f2b-759d-49f0-bde7-285249290f37@app.fastmail.com>
 <CAK8GbeC5_Xa-fOU9kN6aqRu2otX=ut55ok6=3OapZU1vPn=uag@mail.gmail.com>
 <0b684f30-7f6e-4375-915f-3d983e2687a4@app.fastmail.com>
Message-ID: <CAMrKZ9_xWJ2NPuydJQFJr5mCu3k_751r-yrJ8ZEhGdtjaUMpeQ@mail.gmail.com>

I like that first question... ;-)

Other comments at first glance:

   1. On the "Within the last 5 years..." question I'd explicitly add a
   government option.
   2. For communications, I'd change "I follow the mapserver-users mailing
   lists" to "Which mailing lists do you follow?" with 3 choices:
   mapserver-users, mapserver-dev, and mapserver-announce.

Otherwise, my big question would be is this the time to ask about
functionality. Some that come to mind are:

   1. What version are you using?
   2. Are you using MapScript? If yes, what language binding?
   3. What OGC services are you using, if any?
   4. What native MapServer CGI modes are you using, if any?
   5. What input formats are you using, if any? (e.g. PostGIS, Oracle,
   GDAL, etc...)
   6. What output formats are you using, if any? (e.g. template, KML, OGR,
   etc...)

It could get quite involved though and perhaps 2 surveys - a general one
and a functional one, would make sense.

--Steve

On Tue, Jan 20, 2026 at 4:36?AM Seth G via MapServer-dev <
mapserver-dev at lists.osgeo.org> wrote:

> Thanks M?ris for the feedback - I have updated the survey with your
> suggestions.
>
> Seth
>
> --
> web:https://geographika.net & https://mapserverstudio.net
> mastodon: @geographika at mastodon.social
>
> On Tue, Jan 20, 2026, at 8:33 AM, Maris Nartiss wrote:
> > Hello Seth,
> > "The web server run MapServer on most is" question is duplicated;
> > "I obtain MapServer from" should be rephrased to something like "For
> > production environments I obtain MapServer from" or should be made as
> > a multiple answer question (e.g. I use packages but also build from
> > source for dev needs);
> > One question to ask might be something like: "Within last X years I
> > have used MapServer for" (multiple choice): "commercial projects",
> > "volunteer projects", "just playing around".
> >
> > Regards,
> > M?ris.
> >
> > pirmd., 2026. g. 19. janv., plkst. 23:15 ? lietot?js Seth G via
> > MapServer-dev (<mapserver-dev at lists.osgeo.org>) rakst?ja:
> >>
> >> Hi all,
> >>
> >> At the last OSGeo codesprint, we discussed running a MapServer user
> survey, modelled on the GDAL survey [1]. Since MapServer has no analytics
> or "phone home" functionality, we have little insight into how it is used
> beyond mailing lists and in-person discussions.
> >>
> >> A first draft of the survey is available for feedback:
> >>
> https://docs.google.com/forms/d/e/1FAIpQLSfNLqslbM6IhocnwTst9c29eaD89yD81hdUKW2ctn2uZK0Z3g/viewform
> (please don't submit answers until we're happy with the questions!).
> >>
> >> Thanks to Howard for sharing the GDAL survey on which this is based.
> >>
> >> Please let me know of any additional questions that should be added, or
> any edits to existing questions (options, phrasing etc.).
> >>
> >> Unlike the GDAL survey, which informed budget decisions, the aim is to
> prioritise limited time and resources, identify features for potential
> deprecation, and highlight areas needing continued support.
> >>
> >> It will also be interesting to see how many responses we get, as this
> will give a sense of overall interest in MapServer.
> >>
> >> Seth
> >>
> >> [1] https://gdal.org/en/stable/community/user_survey_2024.html
> >>
> >> --
> >> web:https://geographika.net & https://mapserverstudio.net
> >> mastodon: @geographika at mastodon.social
> >> _______________________________________________
> >> MapServer-dev mailing list
> >> MapServer-dev at lists.osgeo.org
> >> https://lists.osgeo.org/mailman/listinfo/mapserver-dev
> _______________________________________________
> MapServer-dev mailing list
> MapServer-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20260120/ba58725f/attachment-0001.htm>

From sethg at geographika.co.uk  Tue Jan 20 11:10:22 2026
From: sethg at geographika.co.uk (Seth G)
Date: Tue, 20 Jan 2026 20:10:22 +0100
Subject: [MapServer-dev] MapServer User Survey
In-Reply-To: <CAMrKZ9_xWJ2NPuydJQFJr5mCu3k_751r-yrJ8ZEhGdtjaUMpeQ@mail.gmail.com>
References: <aeaf6f2b-759d-49f0-bde7-285249290f37@app.fastmail.com>
 <CAK8GbeC5_Xa-fOU9kN6aqRu2otX=ut55ok6=3OapZU1vPn=uag@mail.gmail.com>
 <0b684f30-7f6e-4375-915f-3d983e2687a4@app.fastmail.com>
 <CAMrKZ9_xWJ2NPuydJQFJr5mCu3k_751r-yrJ8ZEhGdtjaUMpeQ@mail.gmail.com>
Message-ID: <7bc17488-0ab6-49e6-a6c5-df2029797aa4@app.fastmail.com>

Thanks Steve - that first question was an update on the Frank Warmerdam/ GDAL question :-)

I have added the government option and changed the mailing list question.

In regard to the functionality - you may have missed sections 2-4 which cover most of these (you need to click Next at the bottom of the page)? I didn't have a version question though - I'll add that to the first section. 

Seth


--
web:https://geographika.net & https://mapserverstudio.net
mastodon: @geographika at mastodon.social

On Tue, Jan 20, 2026, at 6:59 PM, Steve Lime wrote:
> I like that first question... ;-)
> 
> Other comments at first glance:
>  1. On the "Within the last 5 years..." question I'd explicitly add a government option. 
>  2. For communications, I'd change "I follow the mapserver-users mailing lists" to "Which mailing lists do you follow?" with 3 choices: mapserver-users, mapserver-dev, and mapserver-announce. 
> Otherwise, my big question would be is this the time to ask about functionality. Some that come to mind are:
>  1. What version are you using?
>  2. Are you using MapScript? If yes, what language binding?
>  3. What OGC services are you using, if any?
>  4. What native MapServer CGI modes are you using, if any?
>  5. What input formats are you using, if any? (e.g. PostGIS, Oracle, GDAL, etc...)
>  6. What output formats are you using, if any? (e.g. template, KML, OGR, etc...) 
> It could get quite involved though and perhaps 2 surveys - a general one and a functional one, would make sense.
> 
> --Steve
> 
> On Tue, Jan 20, 2026 at 4:36?AM Seth G via MapServer-dev <mapserver-dev at lists.osgeo.org> wrote:
>> Thanks M?ris for the feedback - I have updated the survey with your suggestions.
>> 
>> Seth
>> 
>> --
>> web:https://geographika.net & https://mapserverstudio.net
>> mastodon: @geographika at mastodon.social
>> 
>> On Tue, Jan 20, 2026, at 8:33 AM, Maris Nartiss wrote:
>> > Hello Seth,
>> > "The web server run MapServer on most is" question is duplicated;
>> > "I obtain MapServer from" should be rephrased to something like "For
>> > production environments I obtain MapServer from" or should be made as
>> > a multiple answer question (e.g. I use packages but also build from
>> > source for dev needs);
>> > One question to ask might be something like: "Within last X years I
>> > have used MapServer for" (multiple choice): "commercial projects",
>> > "volunteer projects", "just playing around".
>> >
>> > Regards,
>> > M?ris.
>> >
>> > pirmd., 2026. g. 19. janv., plkst. 23:15 ? lietot?js Seth G via
>> > MapServer-dev (<mapserver-dev at lists.osgeo.org>) rakst?ja:
>> >>
>> >> Hi all,
>> >>
>> >> At the last OSGeo codesprint, we discussed running a MapServer user survey, modelled on the GDAL survey [1]. Since MapServer has no analytics or "phone home" functionality, we have little insight into how it is used beyond mailing lists and in-person discussions.
>> >>
>> >> A first draft of the survey is available for feedback:
>> >> https://docs.google.com/forms/d/e/1FAIpQLSfNLqslbM6IhocnwTst9c29eaD89yD81hdUKW2ctn2uZK0Z3g/viewform (please don't submit answers until we're happy with the questions!).
>> >>
>> >> Thanks to Howard for sharing the GDAL survey on which this is based.
>> >>
>> >> Please let me know of any additional questions that should be added, or any edits to existing questions (options, phrasing etc.).
>> >>
>> >> Unlike the GDAL survey, which informed budget decisions, the aim is to prioritise limited time and resources, identify features for potential deprecation, and highlight areas needing continued support.
>> >>
>> >> It will also be interesting to see how many responses we get, as this will give a sense of overall interest in MapServer.
>> >>
>> >> Seth
>> >>
>> >> [1] https://gdal.org/en/stable/community/user_survey_2024.html
>> >>
>> >> --
>> >> web:https://geographika.net & https://mapserverstudio.net
>> >> mastodon: @geographika at mastodon.social
>> >> _______________________________________________
>> >> MapServer-dev mailing list
>> >> MapServer-dev at lists.osgeo.org
>> >> https://lists.osgeo.org/mailman/listinfo/mapserver-dev
>> _______________________________________________
>> MapServer-dev mailing list
>> MapServer-dev at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/mapserver-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20260120/2d312782/attachment.htm>

From steve.lime at state.mn.us  Tue Jan 20 12:22:57 2026
From: steve.lime at state.mn.us (Lime, Steve D (MNIT))
Date: Tue, 20 Jan 2026 20:22:57 +0000
Subject: [MapServer-dev] MapServer User Survey
In-Reply-To: <7bc17488-0ab6-49e6-a6c5-df2029797aa4@app.fastmail.com>
References: <aeaf6f2b-759d-49f0-bde7-285249290f37@app.fastmail.com>
 <CAK8GbeC5_Xa-fOU9kN6aqRu2otX=ut55ok6=3OapZU1vPn=uag@mail.gmail.com>
 <0b684f30-7f6e-4375-915f-3d983e2687a4@app.fastmail.com>
 <CAMrKZ9_xWJ2NPuydJQFJr5mCu3k_751r-yrJ8ZEhGdtjaUMpeQ@mail.gmail.com>
 <7bc17488-0ab6-49e6-a6c5-df2029797aa4@app.fastmail.com>
Message-ID: <SA1PR09MB118310A2EBFAE783D5F00E63FDA89A@SA1PR09MB11831.namprd09.prod.outlook.com>

Yeah, I didn?t see the multiple pages ? my apologies.


  *   I?d be curious specifically about vector tiles as an output format. That?s an area for possible investment.
  *   I?d explicitly list WMS and WFS as input formats since they are native clients.
  *   Maybe move the open-ended questions from page one to the end?  I think that is part of the reason I didn?t notice multiple pages.

Any reason to ask about use of or interest in related projects (e.g. MS4W, Mappyfile, MapCache, etc?)?


From: MapServer-dev <mapserver-dev-bounces at lists.osgeo.org> On Behalf Of Seth G via MapServer-dev
Sent: Tuesday, January 20, 2026 1:10 PM
To: MapServer Devs <mapserver-dev at lists.osgeo.org>
Subject: Re: [MapServer-dev] MapServer User Survey

Thanks Steve - that first question was an update on the Frank Warmerdam/ GDAL question :-)

I have added the government option and changed the mailing list question.

In regard to the functionality - you may have missed sections 2-4 which cover most of these (you need to click Next at the bottom of the page)? I didn't have a version question though - I'll add that to the first section.

Seth

--
web:https://geographika.net<https://geographika.net/> & https://mapserverstudio.net<https://mapserverstudio.net/>
mastodon: @geographika at mastodon.social<mailto:geographika at mastodon.social>

On Tue, Jan 20, 2026, at 6:59 PM, Steve Lime wrote:
I like that first question... ;-)

Other comments at first glance:

  1.  On the "Within the last 5 years..." question I'd explicitly add a government option.
  2.  For communications, I'd change "I follow the mapserver-users mailing lists" to "Which mailing lists do you follow?" with 3 choices: mapserver-users, mapserver-dev, and mapserver-announce.
Otherwise, my big question would be is this the time to ask about functionality. Some that come to mind are:

  1.  What version are you using?
  2.  Are you using MapScript? If yes, what language binding?
  3.  What OGC services are you using, if any?
  4.  What native MapServer CGI modes are you using, if any?
  5.  What input formats are you using, if any? (e.g. PostGIS, Oracle, GDAL, etc...)
  6.  What output formats are you using, if any? (e.g. template, KML, OGR, etc...)
It could get quite involved though and perhaps 2 surveys - a general one and a functional one, would make sense.

--Steve

On Tue, Jan 20, 2026 at 4:36?AM Seth G via MapServer-dev <mapserver-dev at lists.osgeo.org<mailto:mapserver-dev at lists.osgeo.org>> wrote:
Thanks M?ris for the feedback - I have updated the survey with your suggestions.

Seth

--
web:https://geographika.net<https://geographika.net/> & https://mapserverstudio.net<https://mapserverstudio.net/>
mastodon: @geographika at mastodon.social

On Tue, Jan 20, 2026, at 8:33 AM, Maris Nartiss wrote:
> Hello Seth,
> "The web server run MapServer on most is" question is duplicated;
> "I obtain MapServer from" should be rephrased to something like "For
> production environments I obtain MapServer from" or should be made as
> a multiple answer question (e.g. I use packages but also build from
> source for dev needs);
> One question to ask might be something like: "Within last X years I
> have used MapServer for" (multiple choice): "commercial projects",
> "volunteer projects", "just playing around".
>
> Regards,
> M?ris.
>
> pirmd., 2026. g. 19. janv., plkst. 23:15 ? lietot?js Seth G via
> MapServer-dev (<mapserver-dev at lists.osgeo.org<mailto:mapserver-dev at lists.osgeo.org>>) rakst?ja:
>>
>> Hi all,
>>
>> At the last OSGeo codesprint, we discussed running a MapServer user survey, modelled on the GDAL survey [1]. Since MapServer has no analytics or "phone home" functionality, we have little insight into how it is used beyond mailing lists and in-person discussions.
>>
>> A first draft of the survey is available for feedback:
>> https://docs.google.com/forms/d/e/1FAIpQLSfNLqslbM6IhocnwTst9c29eaD89yD81hdUKW2ctn2uZK0Z3g/viewform (please don't submit answers until we're happy with the questions!).
>>
>> Thanks to Howard for sharing the GDAL survey on which this is based.
>>
>> Please let me know of any additional questions that should be added, or any edits to existing questions (options, phrasing etc.).
>>
>> Unlike the GDAL survey, which informed budget decisions, the aim is to prioritise limited time and resources, identify features for potential deprecation, and highlight areas needing continued support.
>>
>> It will also be interesting to see how many responses we get, as this will give a sense of overall interest in MapServer.
>>
>> Seth
>>
>> [1] https://gdal.org/en/stable/community/user_survey_2024.html
>>
>> --
>> web:https://geographika.net<https://geographika.net/> & https://mapserverstudio.net<https://mapserverstudio.net/>
>> mastodon: @geographika at mastodon.social
>> _______________________________________________
>> MapServer-dev mailing list
>> MapServer-dev at lists.osgeo.org<mailto:MapServer-dev at lists.osgeo.org>
>> https://lists.osgeo.org/mailman/listinfo/mapserver-dev
_______________________________________________
MapServer-dev mailing list
MapServer-dev at lists.osgeo.org<mailto:MapServer-dev at lists.osgeo.org>
https://lists.osgeo.org/mailman/listinfo/mapserver-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20260120/415e5b36/attachment-0001.htm>

From sethg at geographika.co.uk  Tue Jan 20 14:49:05 2026
From: sethg at geographika.co.uk (Seth G)
Date: Tue, 20 Jan 2026 23:49:05 +0100
Subject: [MapServer-dev] MapServer User Survey
In-Reply-To: <SA1PR09MB118310A2EBFAE783D5F00E63FDA89A@SA1PR09MB11831.namprd09.prod.outlook.com>
References: <aeaf6f2b-759d-49f0-bde7-285249290f37@app.fastmail.com>
 <CAK8GbeC5_Xa-fOU9kN6aqRu2otX=ut55ok6=3OapZU1vPn=uag@mail.gmail.com>
 <0b684f30-7f6e-4375-915f-3d983e2687a4@app.fastmail.com>
 <CAMrKZ9_xWJ2NPuydJQFJr5mCu3k_751r-yrJ8ZEhGdtjaUMpeQ@mail.gmail.com>
 <7bc17488-0ab6-49e6-a6c5-df2029797aa4@app.fastmail.com>
 <SA1PR09MB118310A2EBFAE783D5F00E63FDA89A@SA1PR09MB11831.namprd09.prod.outlook.com>
Message-ID: <5a909e7d-12a7-4264-a943-b0f7af030ba6@app.fastmail.com>

Good suggestions. I have moved the open-ended questions to the end, and added questions on usage of vector tiles, the WMS client, and the WFS client. 

I also added a question to see if MapServer users are also using TinyOWS, MapCache. ms4w, or mappyfile. 

Seth

--
web:https://geographika.net & https://mapserverstudio.net
mastodon: @geographika at mastodon.social

On Tue, Jan 20, 2026, at 9:22 PM, Lime, Steve D (MNIT) wrote:
> Yeah, I didn?t see the multiple pages ? my apologies.
>  
>  ? I?d be curious specifically about vector tiles as an output format. That?s an area for possible investment.
>  ? I?d explicitly list WMS and WFS as input formats since they are native clients.
>  ? Maybe move the open-ended questions from page one to the end?  I think that is part of the reason I didn?t notice multiple pages.
>  
> Any reason to ask about use of or interest in related projects (e.g. MS4W, Mappyfile, MapCache, etc?)?
>  
>  
> *From:* MapServer-dev <mapserver-dev-bounces at lists.osgeo.org> *On Behalf Of *Seth G via MapServer-dev
> *Sent:* Tuesday, January 20, 2026 1:10 PM
> *To:* MapServer Devs <mapserver-dev at lists.osgeo.org>
> *Subject:* Re: [MapServer-dev] MapServer User Survey
>  
> Thanks Steve - that first question was an update on the Frank Warmerdam/ GDAL question :-)
>  
> I have added the government option and changed the mailing list question.
>  
> In regard to the functionality - you may have missed sections 2-4 which cover most of these (you need to click Next at the bottom of the page)? I didn't have a version question though - I'll add that to the first section. 
>  
> Seth
>  
> --
> web:https://geographika.net & https://mapserverstudio.net
> mastodon: @geographika at mastodon.social
>  
> On Tue, Jan 20, 2026, at 6:59 PM, Steve Lime wrote:
>> I like that first question... ;-)
>>  
>> Other comments at first glance:
>>  1. On the "Within the last 5 years..." question I'd explicitly add a government option. 
>>  2. For communications, I'd change "I follow the mapserver-users mailing lists" to "Which mailing lists do you follow?" with 3 choices: mapserver-users, mapserver-dev, and mapserver-announce. 
>> Otherwise, my big question would be is this the time to ask about functionality. Some that come to mind are:
>>  1. What version are you using?
>>  2. Are you using MapScript? If yes, what language binding?
>>  3. What OGC services are you using, if any?
>>  4. What native MapServer CGI modes are you using, if any?
>>  5. What input formats are you using, if any? (e.g. PostGIS, Oracle, GDAL, etc...)
>>  6. What output formats are you using, if any? (e.g. template, KML, OGR, etc...) 
>> It could get quite involved though and perhaps 2 surveys - a general one and a functional one, would make sense.
>>  
>> --Steve
>>  
>> On Tue, Jan 20, 2026 at 4:36?AM Seth G via MapServer-dev <mapserver-dev at lists.osgeo.org> wrote:
>>> Thanks M?ris for the feedback - I have updated the survey with your suggestions.
>>>  
>>> Seth
>>>  
>>> --
>>> web:https://geographika.net & https://mapserverstudio.net
>>> mastodon: @geographika at mastodon.social
>>>  
>>> On Tue, Jan 20, 2026, at 8:33 AM, Maris Nartiss wrote:
>>> > Hello Seth,
>>> > "The web server run MapServer on most is" question is duplicated;
>>> > "I obtain MapServer from" should be rephrased to something like "For
>>> > production environments I obtain MapServer from" or should be made as
>>> > a multiple answer question (e.g. I use packages but also build from
>>> > source for dev needs);
>>> > One question to ask might be something like: "Within last X years I
>>> > have used MapServer for" (multiple choice): "commercial projects",
>>> > "volunteer projects", "just playing around".
>>> > 
>>> > Regards,
>>> > M?ris.
>>> > 
>>> > pirmd., 2026. g. 19. janv., plkst. 23:15 ? lietot?js Seth G via
>>> > MapServer-dev (<mapserver-dev at lists.osgeo.org>) rakst?ja:
>>> >> 
>>> >> Hi all,
>>> >> 
>>> >> At the last OSGeo codesprint, we discussed running a MapServer user survey, modelled on the GDAL survey [1]. Since MapServer has no analytics or "phone home" functionality, we have little insight into how it is used beyond mailing lists and in-person discussions.
>>> >> 
>>> >> A first draft of the survey is available for feedback:
>>> >> https://docs.google.com/forms/d/e/1FAIpQLSfNLqslbM6IhocnwTst9c29eaD89yD81hdUKW2ctn2uZK0Z3g/viewform (please don't submit answers until we're happy with the questions!).
>>> >> 
>>> >> Thanks to Howard for sharing the GDAL survey on which this is based.
>>> >> 
>>> >> Please let me know of any additional questions that should be added, or any edits to existing questions (options, phrasing etc.).
>>> >> 
>>> >> Unlike the GDAL survey, which informed budget decisions, the aim is to prioritise limited time and resources, identify features for potential deprecation, and highlight areas needing continued support.
>>> >> 
>>> >> It will also be interesting to see how many responses we get, as this will give a sense of overall interest in MapServer.
>>> >> 
>>> >> Seth
>>> >> 
>>> >> [1] https://gdal.org/en/stable/community/user_survey_2024.html
>>> >> 
>>> >> --
>>> >> web:https://geographika.net & https://mapserverstudio.net
>>> >> mastodon: @geographika at mastodon.social
>>> >> _______________________________________________
>>> >> MapServer-dev mailing list
>>> >> MapServer-dev at lists.osgeo.org
>>> >> https://lists.osgeo.org/mailman/listinfo/mapserver-dev
>>> _______________________________________________
>>> MapServer-dev mailing list
>>> MapServer-dev at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/mapserver-dev
>  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20260120/30b327ae/attachment.htm>