Skip to content

Commit c9faf3b

Browse files
authored
Blog post cite certification (#271)
1 parent 02f3700 commit c9faf3b

File tree

2 files changed

+18
-17
lines changed

2 files changed

+18
-17
lines changed

Gemfile

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,4 +7,5 @@ gem 'tzinfo-data'
77
gem 'rouge'
88

99
gem "webrick", "~> 1.7"
10+
gem 'wdm', '>= 0.1.0' if Gem.win_platform?
1011

_posts/2025-07-15-cite-certification.md

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,14 @@ release: release_227
1111
version: 2.27.0
1212
---
1313

14+
<div style="text-align: center; margin: 20px 0;">
15+
<iframe src="https://portal.ogc.org/public_ogc/compliance/srv_ogc_compliance_badge2.php?id=102&pid=1846"
16+
width="250"
17+
frameborder="0"
18+
style="float: right; margin: 0 0 10px 15px; border: none; height: auto; min-height: 1500px">
19+
</iframe>
20+
</div>
21+
1422
# CITE Certification
1523

1624
The GeoServer team are really pleased to announce that our long-lost CITE Certification has been regained (for 2.27) over the last 6 months.
@@ -22,31 +30,23 @@ OGC CITE Certification is important for two reasons:
2230

2331
Recent activity:
2432

25-
* As part of a Camptocamp organized ``OGC API - Features`` sprint Gabriel was able setup a GitHub workflow restoring the use of CITE testing for black-box testing of GeoServer. Gabriel focused on ``OGC API - Features`` certification but found WMS 1.1 and WCS 1.1 tests would also pass out of the box, providing a setup for running the tests in each new pull request.
26-
* Andrea made further progress certifying the output produced by GeoServer, restoring the WMS 1.3, WFS 1.0 and WFS 1.1 tests, as well as upgrading the test engine to the latest production release. In addition, CITE tests that weren’t run in the past have been added, like WFS 2.0 and GeoTIFF, while other new tests are in progress, like WCS 2.0, WMTS 1.0 and GeoPackage.
27-
* Peter set up multiple GeoServers for the testing and to act as reference implementations (hosting graciously provided by the Open Source Geospatial Foundation) and ran the test suites.
28-
* Angelos Tzotsos (OSGeo) submitted the certification request to OGC.
29-
* Gobe Hobona (OGC) approved all of our submissions.
33+
* As part of a Camptocamp organized ``OGC API - Features`` sprint **Gabriel** was able setup a GitHub workflow restoring the use of CITE testing for black-box testing of GeoServer. Gabriel focused on ``OGC API - Features`` certification but found WMS 1.1 and WCS 1.1 tests would also pass out of the box, providing a setup for running the tests in each new pull request.
34+
* **Andrea** made further progress certifying the output produced by GeoServer, restoring the WMS 1.3, WFS 1.0 and WFS 1.1 tests, as well as upgrading the test engine to the latest production release. In addition, CITE tests that weren’t run in the past have been added, like WFS 2.0 and GeoTIFF, while other new tests are in progress, like WCS 2.0, WMTS 1.0 and GeoPackage.
35+
* **Peter** set up multiple GeoServers for the testing and to act as reference implementations (hosting graciously provided by the Open Source Geospatial Foundation) and ran the test suites.
36+
* **Angelos** Tzotsos (OSGeo) submitted the certification request to OGC.
37+
* **Gobe** Hobona (OGC) approved all of our submissions.
3038

3139
Many thanks to all who were involved! After approximately 10 years, we can once again officially confirm that GeoServer is OGC compliant.
3240

3341
## Documentation
3442

35-
Read more about the [developer process](https://docs.geoserver.org/latest/en/developer/cite-test-guide/index.html#cite-certification)
43+
For developers, read more about the [certification process](https://docs.geoserver.org/latest/en/developer/cite-test-guide/index.html#cite-certification) and how to expand on it.
3644

37-
## The bad news
45+
## The Bad News
3846

39-
This certification process is expensive, and we no longer have funding to repeat it. As mentioned above, these CITE tests are automatically run as part of our build process for each new pull request, so we can unofficially verify that we remain OGC compliant - and that is our guarantee to you.
47+
This certification process is expensive, and we no longer have funding to repeat it. However, as mentioned above, these CITE tests are automatically run as part of our build process for each new pull request, so we can **unofficially** verify that we remain OGC compliant - and that is our guarantee to you.
4048

41-
However, if you/your company finds the CITE Certification valuable to your business, then you should contact the PSC to offer to fund the annual renewal. The more companies do this, the more the financial load (approx USD 1000 pa) can be spread.
42-
43-
<div style="text-align: center; margin: 20px 0;">
44-
<iframe src="https://portal.ogc.org/public_ogc/compliance/srv_ogc_compliance_badge2.php?id=102&pid=1846"
45-
width="190"
46-
frameborder="0"
47-
style="border: none; max-width: 100%;">
48-
</iframe>
49-
</div>
49+
But, if you/your company finds the CITE Certification valuable to your business, then you should please contact the PSC to offer to fund the annual renewal. The more companies are able to do this, the more the financial load (approx USD 1000 per year) can be shared.
5050

5151
# About GeoServer 2.27 Series
5252

0 commit comments

Comments
 (0)