pyproj/crs FutureWarning: '+init=<authority>:<code>' syntax is deprecated.

[eracle]

When I run this:

from leuvenmapmatching.map.inmem import InMemMap

map_con = InMemMap("myosm", use_latlon=True, use_rtree=True, index_edges=True)

I get this warning:

/home/user/anaconda3/envs/ox/lib/python3.8/site-packages/pyproj/crs/crs.py:55: FutureWarning: '+init=<authority>:<code>' syntax is deprecated. '<authority>:<code>' is the preferred initialization method. When making the change, be mindful of axis order changes: https://pyproj4.github.io/pyproj/stable/gotchas.html#axis-order-changes-in-proj-6
  return _prepare_from_string(" ".join(pjargs))

/home/user/anaconda3/envs/ox/lib/python3.8/site-packages/pyproj/crs/crs.py:55: FutureWarning: '+init=<authority>:<code>' syntax is deprecated. '<authority>:<code>' is the preferred initialization method. When making the change, be mindful of axis order changes: https://pyproj4.github.io/pyproj/stable/gotchas.html#axis-order-changes-in-proj-6
  return _prepare_from_string(" ".join(pjargs))

pip freeze gives me:

attrs==19.3.0
backcall==0.1.0
branca==0.4.0
certifi==2019.11.28
cffi==1.13.2
chardet==3.0.4
Click==7.0
click-plugins==1.1.1
cligj==0.5.0
cryptography==2.8
cycler==0.10.0
decorator==4.4.2
descartes==1.1.0
entrypoints==0.3
Fiona==1.8.13
folium==0.10.1
GDAL==3.0.4
geographiclib==1.50
geopandas==0.7.0
geopy==1.21.0
idna==2.9
ipykernel==5.1.4
ipython==7.13.0
ipython-genutils==0.2.0
jedi==0.16.0
Jinja2==2.11.1
joblib==0.14.1
jupyter-client==6.0.0
jupyter-core==4.6.3
kiwisolver==1.1.0
leuvenmapmatching==0.5.3
MarkupSafe==1.1.1
matplotlib==3.1.3
munch==2.5.0
networkx==2.4
numpy==1.18.1
osmnx==0.11.4
pandas==1.0.1
parso==0.6.2
pexpect==4.8.0
pickleshare==0.7.5
Pillow==7.0.0
prompt-toolkit==3.0.3
ptyprocess==0.6.0
pycparser==2.19
Pygments==2.5.2
pyOpenSSL==19.1.0
pyparsing==2.4.6
pyproj==2.5.0
PySocks==1.7.1
python-dateutil==2.8.1
pytz==2019.3
pyzmq==19.0.0
requests==2.23.0
Rtree==0.9.4
scikit-learn==0.22.1
scipy==1.4.1
Shapely==1.7.0
six==1.14.0
smopy==0.0.7
tornado==6.0.3
traitlets==4.3.3
urllib3==1.25.7
vincent==0.4.4
wcwidth==0.1.8

[gottfriedmrs]

Hello !

In most cases coordinate reference systems with geodetic coordinates expect the input ordered as latitude/longitude (typically with the EPSG dataset), however, internally PROJ expects an longitude/latitude ordering for all projections. This is generally hidden for users but in a few cases it is exposed at the surface level of PROJ, most prominently in the proj utility which expects longitude/latitude ordering of input date (unless proj -r is used).

from https://proj.org/faq.html#why-is-the-axis-ordering-in-proj-not-consistent