You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The get_area_def function is there for historical reasons. It uses a conversion from a PROJ.4 string to a PROJ.4 dictionary of parameters which results in the warning you're seeing. That conversion is no longer needed as pyresample's AreaDefinition now depends on pyproj's CRS object which can take many common ways of describing a projection and have it "just work" and with no warning. I'm 99% sure I can remove that conversion from that function and no user would notice a problem.
Second long answer: You could also use the create_area_def (create_ versus get_) which allows for different variations of parameters and will "do the math" for you to create the area you're trying to describe. For example, you have the size of the pixels for the area you want to make and the number of pixels in that area, but you don't want to calculate the extents. create_area_def will accept the information you have and compute any values it needs from that information.
I will plan on making a PR to remove that conversion in get_area_def, but as I said creating your AreaDefinition directly should work just as well (better in fact).
Code Sample, a minimal, complete, and verifiable piece of code
Problem description
D:\anaconda3\envs\NewsstsrPredata\lib\site-packages\pyproj\crs\crs.py:1293: UserWarning: You will likely lose important projection information when converting to a PROJ string from another format. See: https://proj.org/faq.html#what-is-the-best-format-for-describing-coordinate-reference-systems
proj = self._crs.to_proj4(version=version)
The text was updated successfully, but these errors were encountered: