ah they are! I don't have pyproj 2.0+ installed on any environments right now so couldn't test. Found the
__hash__ method
If you do, make sure that the length of the list isn't too big until 2.3 is released. Seepyproj4/pyproj#374
*set/dict, not list.
side question @snowman2: any knowledge on when a rasterio version compatible with PROJ 6.0+ will be released? I'm having a real hard time get a preferred conda environment with xarray, rasterio, gdal, and pyproj 2.0+ installed
do DataArray accessors get created every time you access them?
They should be retained for the life of the data array after it is first accessed (unless it is modified with another operation that drops/copies things) as far as I can tell.
Getting some only on Linux but Windows and OSX seem fine on travis
issue right now is I'm not really getting a good indication of why/what is causing the seg fault
or which package to blame
I would recommend checking the version of PROJ and making sure it is 6.1+ and ensuring that a wheel wasn't installed by accident.
@snowman2 Have you ever had different experiences with proj from Linux to Windows on what it accepts? Pyresample had some old documentation that was doing the equivalent of
Proj({'proj': 'eqc', 'lon_0': 0.0, 'lat_0': 0.0}) and it seems to error on Windows with RuntimeError: b'major axis or radius = 0 or not given' with pyproj 1.9.6 but with pyproj 2.3 it is fine. I would have assumed pyproj/proj to get more strict, not less strict. And I've never seen this error before. FYI this is PROJ 5.2.0 on Windows that fails.
$ conda list proj
# packages in environment at /home/snowal/miniconda3/envs/geocube:
#
# Name Version Build Channel
proj4 5.2.0 he1b5a44_1003 conda-forge
pyproj 1.9.6 py36h516909a_1002 conda-forge
(geocube) snowal@snowal-lx2:~$ python
Python 3.6.7 | packaged by conda-forge | (default, Jul 2 2019, 02:18:42)
[GCC 7.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from pyproj import Proj
>>> pj = Proj({'proj': 'eqc', 'lon_0': 0.0, 'lat_0': 0.0})
>>> pj
pyproj.Proj('+units=m +proj=eqc +lon_0=0.0 +lat_0=0.0 ', preserve_units=True)
>>> import pyproj
>>> pyproj.__version__
'1.9.6'
@snowman2 Just because I'm a pain, ETA on pyproj 2.3.1?
FYI, did you know you can do
pip install git+https://github.com/pyproj4/pyproj.git?
(no need to make a release)
can even add
@branch-or-tag
will have to search through PROJ source for where it is coming from
*working
Hey all, I'm working on upgrading pyproj from 1.9.4 to a more recent version. But I can't get past a change in output from pyproj.transform if I go to 2.2.1 and higher.
import pyproj
result = pyproj.transform(pyproj.Proj(init='EPSG:4326'),
pyproj.Proj(init='EPSG:31370'),
-50, -50)
print(result)
# 2.2.1: (-16648000.756625965, -13287157.707139067)
# 1.9.4: (-16647936.738681808, -13287195.77167615)The outputs are in the comments, and the difference is really too big to ignore.
What exactly is going wrong here?
so use
pyproj.Proj('EPSG:4326') instead
I also have been struggling with this (also with EPSG:31370 ;)), but thought for me the difference was smaller (not in the meters order)
I do have smaller differences with more realistic data rather than
But still..
-50, -50149372.267141, 175495.954088 vs 149372.214872, 175495.952055.But still..