Hi Howard, as you already know, spatialreference.org is generating the PROJJSON output. As a curiosity, some of the data displayed for the CRS in the html page is extracted directly from the PROJJSON (the axes info IIRC. I was thinking on adding more stuff, but stopped there).
Best regards Javier On Mon, 21 Oct 2024 at 22:03, Howard Butler via PROJ <proj@lists.osgeo.org> wrote: > All, > > I am participating in the OGC CRS SWG [1] who is currently investigating > the standardization of a JSON-based CRS definition such as PROJJSON [2]. > One question that came up in our discussion is whether or not there are any > alternative software implementations of PROJJSON besides PROJ's itself. Did > you write one? Are you using PROJJSON in commercial or open source software > that isn't PROJ-based? Is forward/backward compatibility of PROJJSON a > priority for you? Information about these questions would be useful for us > to know regarding possible enhancement or evolution of PROJJSON going > forward. > > There was also some interest in knowing where PROJJSON has been used in > unexpected or unintentional ways. Are you using it as the CRS definition > for your custom format or network protocol? We know of it being used by > GeoParquet at the moment, but are there others? > > Please help inform our discussion around standardization of JSON-based CRS > definitions with some feedback on your use of PROJJSON in the wild. > > Regards, > > Howard > > > > [1] https://github.com/opengeospatial/CRS-JSON-Encoding > [2] https://proj.org/specifications/projjson.html > _______________________________________________ > PROJ mailing list > PROJ@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/proj >
_______________________________________________ PROJ mailing list PROJ@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/proj
