[postgis-devel] Proj 9.2

[Paul Ramsey]

Oh, useful reading material for all consumers of proj:

https://proj.org/en/9.2/usage/network.html


> On Jun 19, 2023, at 11:52 AM, Paul Ramsey <pramsey at cleverelephant.ca> wrote:
> 
> I was wondering why we were only seeing new proj regressions with proj 9.2 and I think it is this change in policy that is driving it. From proj.ini:
> 
> ; Can be set to on so that by default the lack of a known resource files needed
> ; for the best transformation PROJ would normally use causes an error, or off
> ; to accept missing resource files without errors or warnings.
> ; This default value itself is overriden by the PROJ_ONLY_BEST_DEFAULT environment
> ; variable if set, and then by the ONLY_BEST setting that can be
> ; passed to the proj_create_crs_to_crs() method, or with the --only-best
> ; option of the cs2cs program.
> ; (added in PROJ 9.2)
> ; only_best_default = on
> 
> Basically until recently proj was quietly falling back to less accurate transforms when grids were missing. Now the default policy is to complain and fail if the best transform is missing.
> 
> I think I must be missing something, since the combination of the default of having network set to off and best default set to on would seem likely to generate a lot of errors. 
> 
> I’m still turning over in my head what kind of advice I’d give to deb and rpm packagers with respect to the proj network options. From a PostGIS point-of-view, having a working proj with access to the latest grids seems like the scenario we’d prefer, but it also seems like packagers would want to default to a very locked-down proj that doesn’t go off and do network access on its own.
> 
> Has the proj project provided any guidance to packagers?
> 
> P

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20230619/d8965514/attachment.htm>