<html aria-label="message body"><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><meta http-equiv="content-type" content="text/html; charset=utf-8"><div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Even,<div><br></div><div>Furthermore, we see a precedents in existing projections of Proj that are substrates of DGGS - such as <span style="font-size: medium;">HEALPix</span>.</div><div>Don’t get me wrong - I’m not averse to including DGGAL as an additional library - but Project has an edge for integration purposes, and especially for PostGIS, etc.</div><div>If my project was a DGGS without a supporting CRS - then I would not be looking to Proj.</div><div><br></div><div>Best regards</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Ben.</div><div></div><div><br></div><div><div><blockquote type="cite"><div>On 22 Mar 2026, at 16:47, Even Rouault <even.rouault@spatialys.com> wrote:</div><br class="Apple-interchange-newline"><div><div>Hi Ben,<br>I don't think PROJ API is the best fit for DGGS implementations. Probably https://github.com/ecere/dggal would be a better host (I haven't used it myself)<br>And AFAIK, WKT / ISO-19111 hasn't been designed with DGGS use cases in mind either.<br><br>Even<br></div></div></blockquote></div></div><div><br></div></div></body></html>