Even Rouault

> It should not impact the elevation. it does not for me: ``` $ echo 50.60861389 5.73340278 299.16 | PROJ_NETWORK=ON bin/cs2cs "$(cat /home/even/gdal/gdal/build_cmake/GdalSupportCase/Wgs84_Ellipsoidal_3D.txt)" "$(cat /home/even/gdal/gdal/build_cmake/GdalSupportCase/BelgianLambert_OstendHeight.txt)" 246588.12 145103.98 254.94 $ echo...

> I remember a tweet from you mentioning the wish/will Actually somebody else raised this. Not sure who :-) Thanks for having a try at this. I've absolutely bad design...

Perhaps we should have some informal "competition" to have potentially several propositions from different people. Like was done with PROJ. Happy to let anyone organize that.

> how much time do we give said person to come forward before we conclude it might not happen? :) There's no emergency. Maybe January 17th as deadline for submitting...

> https://proj.org/en/9.4/specifications/projjson.html Ah that's an oversight. Just updated to https://proj.org/schemas/v0.7/projjson.schema.json per 5f725fb720aa53946af3a6a4d1a6349744835363 (master branch) and 0caf671083e3b78f15819e4337a2888b399ecd47 (9.4 branch) Regarding CORS issues, I'm not familiar with that. The thing is that...

wondering if using RTD sub-projects (https://docs.readthedocs.io/en/stable/subprojects.html) couldn't be a solution. If we had a "schemas" sub-project, only fed from master builds, that might perhaps do it

> One solution is to use the [replacements](https://github.com/OSGeo/PROJ/blob/master/docs/source/_extensions/replacements.py) extension that uses a [mapping configuration](https://github.com/OSGeo/PROJ/blob/5f725fb720aa53946af3a6a4d1a6349744835363/docs/source/conf.py#L102-L106) which is used in a few places like [here](https://github.com/OSGeo/PROJ/blob/master/docs/source/install.rst#build-steps). This would require this one variable PROJJSONVERSION...

> is it really good if the schemas are versioned twice? Well, that hasn't been specifically designed. That's a consequence of having the versioning of the schemas in the /schemas...

> What's responsible for the redirects? We need to hook into there, I think. This is this RtD mechanism: https://docs.readthedocs.io/en/stable/user-defined-redirects.html#user-defined-redirects In https://readthedocs.org/dashboard/osgeo-proj/redirects/20195/edit/ we have setup an "exact redirect" from ``/schemas/*``...

I've filed an issue at RtD at https://github.com/readthedocs/readthedocs.org/issues/11223 . Let's see if we get some response