<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
PS - fancy submitting "building Blocks" for PROJJSON and the STAC-projection extension to our experimental register of re-usable standards ? </div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
Docs here:</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<a href="https://ogcincubator.github.io/bblocks-docs/">Https://ogcincubator.github.io/bblocks-docs/</a> - follow the links to the tutorial - others have successfuly used this to build sets of building blocks - in this case its simpler - just copy/edit one
of the existing blocks</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
STAC sub-register is here - you could put things in here with a PR. </div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
Git: <a href="https://github.com/ogcincubator/bblocks-stac">https://github.com/ogcincubator/bblocks-stac</a> </div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
Viewer: <a href="https://ogcincubator.github.io/bblocks-stac">https://ogcincubator.github.io/bblocks-stac</a></div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
I can support this if you want to give it a go. </div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
(FYI I have a workshop as FOSS4G in NZ but not sure if current registered attendance is going to make it viable - standards and FAIR standards is a bit of a niche subject compared to playing with tools. Any people inspired let me know ASAP before I pull it..)</div>
<div class="elementToProof" id="Signature">
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="background-color: rgb(255, 255, 255);" class="elementToProof">
<div style="direction: ltr; text-align: left; text-indent: 0px; line-height: 1.284; margin-top: 0pt; margin-bottom: 0pt; font-family: Arial; font-size: 11pt; color: rgb(5, 128, 218);" class="elementToProof">
<span style="font-weight: 700;">Rob Atkinson</span></div>
<div style="direction: ltr; text-align: left; text-indent: 0px; line-height: 1.284; margin-top: 0pt; margin-bottom: 0pt; font-size: 10pt;" class="elementToProof">
<span style="font-family: Arial, sans-serif; color: rgb(47, 85, 151); line-height: 14.2667px;"><b>Senior Research Engineer
</b></span><span style="font-family: Arial; color: rgb(0, 177, 255); font-weight: 700;"> | Open Geospatial Consortium (OGC)</span></div>
<div style="direction: ltr; text-align: left; text-indent: 0px; line-height: 1.284; margin-top: 0pt; margin-bottom: 0pt; font-family: Arial; font-size: 10pt; color: rgb(34, 34, 34);" class="elementToProof">
Mobile: +61 419 202973</div>
<div style="direction: ltr; text-align: left; text-indent: 0px; margin: 0cm 0cm 0.0001pt; font-family: Arial; font-size: 10pt; color: rgb(0, 0, 0);" class="elementToProof">
<span style="color: rgb(17, 85, 204);"><a style="color: rgb(17, 85, 204);" target="_blank" href="mailto:ratkinson@ogc.org">ratkinson@ogc.org</a></span><span style="color: rgb(47, 85, 151);"> |
</span><span style="color: rgb(17, 85, 204);"><a style="color: rgb(17, 85, 204);" data-saferedirecturl="https://www.google.com/url?q=http://ogc.org/&source=gmail&ust=1728990010161000&usg=AOvVaw3vZn31cNfY71qf0irSdgTM" target="_blank" href="http://ogc.org/">ogc.org</a></span><span style="color: rgb(47, 85, 151);"> |
</span><span style="color: rgb(5, 128, 218);">@opengeospatial</span></div>
<div style="direction: ltr; text-align: left; font-family: Arial, Helvetica, sans-serif; font-size: 9.75pt; color: rgb(136, 136, 136);" class="elementToProof">
<br>
</div>
</div>
<div style="font-family: Arial, Helvetica, sans-serif; font-size: 9.75pt; color: rgb(136, 136, 136);" class="elementToProof">
<span style="background-color: rgb(255, 255, 255);"><br>
<img style="max-width: 780px;" data-bit="iit" src="https://ci3.googleusercontent.com/meips/ADKq_NYvdzG5CnR-DX7WeJyPCnJuhbJ_G7lH1yVbaql72titKCiG-t4HQ92DiCCRM2jU42bDT20Ge7sBVIodm8VpmVBlrnTKCg=s0-d-e1-ft#https://portal.ogc.org/files/?artifact_id=99287"></span></div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Standards <standards-bounces@lists.osgeo.org> on behalf of Howard Butler via Standards <standards@lists.osgeo.org><br>
<b>Sent:</b> Wednesday, November 12, 2025 2:43 PM<br>
<b>To:</b> standards@lists.osgeo.org <standards@lists.osgeo.org><br>
<b>Subject:</b> Re: [OSGeo-Standards] PROJJSON OGC Community Standard Submission?</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">No takers, interest, or guidance on this topic?<br>
<br>
> On Oct 31, 2025, at 12:37 PM, Howard Butler <howard@hobu.co> wrote:<br>
> <br>
> Hello,<br>
> <br>
> The PROJ project plans to submit PROJJSON as an OGC Community Standard. The application document was initiated three years ago [1] by myself and Even Rouault, but we were waiting to see if the OGC CRS SWG would build upon PROJJSON to create a JSON based
encoding of CRS. <br>
> <br>
> To date, no draft has been published, the survey at the previous OGC meeting was ambiguous about how the organization would move forward, and if the CRS SWG chooses to revisit ISO 19111 conceptual model enhancements and their reflection through a JSON CRS
definition, that work will in all likelihood be backwards and forwards incompatible with PROJJSON. Given the current situation, we would like to move forward with PROJJSON as a Community Standard.<br>
> <br>
> In the interim since we initiated the submission, PROJJSON adoption has continued to grow. STAC was recently recognized as a OGC Community Standard at the Boulder Members Meeting [2], and its Projection Extension references PROJJSON. GeoParquet 1.1 [3] uses
PROJJSON as its CRS definition, Parquet references PROJJSON as a possible definition in its spatial types[4], and Zarr is looking at it for its geo-proj Zarr extension [5].
<br>
> <br>
> We believe it makes sense to resume the application process for PROJJSON to be also recognized as a community standard. Even has prepared an update of the application at
<a href="https://github.com/OSGeo/projjson-submission/pull/3">https://github.com/OSGeo/projjson-submission/pull/3</a>.
<br>
> <br>
> Does OSGeo want to be mentioned as one of the submitting organizations? If so, what's the process for a project to submit one of its works to OSGeo as a Community Standard? A successful motion raised on this mailing list?<br>
> Kind regards,<br>
> <br>
> Howard and Even<br>
> <br>
> <br>
> [1] <a href="https://github.com/OSGeo/projjson-submission">https://github.com/OSGeo/projjson-submission</a>
<br>
> [2] <a href="https://www.ogc.org/announcement/ogc-announces-publication-of-the-spatiotemporal-asset-catalog-community-standards/">
https://www.ogc.org/announcement/ogc-announces-publication-of-the-spatiotemporal-asset-catalog-community-standards/</a><br>
> [3] <a href="https://geoparquet.org/releases/v1.1.0/">https://geoparquet.org/releases/v1.1.0/</a><br>
> [4] <a href="https://github.com/apache/parquet-format/blob/master/Geospatial.md">
https://github.com/apache/parquet-format/blob/master/Geospatial.md</a><br>
> [5] <a href="https://github.com/zarr-experimental/geo-proj">https://github.com/zarr-experimental/geo-proj</a><br>
> <br>
<br>
_______________________________________________<br>
Standards mailing list<br>
Standards@lists.osgeo.org<br>
<a href="https://lists.osgeo.org/mailman/listinfo/standards">https://lists.osgeo.org/mailman/listinfo/standards</a><br>
</div>
</span></font></div>
</body>
</html>