On 8/31/19 6:58 PM, Antonio Valentino wrote:
> it seems to me that the issue is in basemap rather then pyresample.
basemap most likely also needs to be updated to support PROJ 6
correctly, as pretty much everything using PROJ should.
> As far as I can understand it has been already fixed [1,2] in the latest
> version of basemap (1.2.1) which is still not in debian.
>
> The problem seems to be related to the recent proj/pyproj updates and
> the location of EPSG data. In particular it seems that the "epsg" data
> file used by basemap was provided by proj-data v5.2.0 but is no longer
> in the new version. Is it correct?
The init files like epsg are not longer provided in PROJ 6, this data
moved to the proj.db SQLite database.
Now you shouldn't specify the init file when doing a transformation.
An example from the proj-rdnap test suite, for PROJ <= 5 it does:
cs2cs -r +init=epsg:4258 +to +init=rdnap:rdnap -f %.4f
For PROJ 6 it does:
cs2cs EPSG:4937 +to EPSG:7415 -f %.4f
Note that EPSG:4937 is the 3D equivalent of EPSG:4258. The epsg & rdnap
init files are no longer used, instead the projection database is used.
> I'm going to reassign.
That doesn't seem appropriate, pyresample needs to be updated too. It
does things like this:
pyresample/test/test_geometry.py:
projections = {'+init=epsg:3006': 'init: epsg:3006'}
Note the explicit use of init files, this is not going to work correctly
with PROJ 6.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
