-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
problem in get_projection_params #2622
Comments
@ReimarBauer Are AUTO and AUTO2 projections intended to be supported, or should the raise stay and the unreachable code be removed? |
Please ask @joernu76. I assigned the issue to. |
@joernu76 can i work on this issue? |
I have no idea. That´s why I think it is a task for Joern because he is familiar with that math. |
These are projections described in the WMS standards, e.g. here https://portal.ogc.org/files/?artifact_id=14416 This commit 71de73e tried to make MSWMS more standards compliant in this regard. I personally would leave this code in there as minder and maybe add an issue to revisit this? |
pylint or similiar will always show the lines as not reachable. We maybe should comment them and add a hint to the issue. Also it would be good to add an issue what we need in basemap https://github.com/matplotlib/basemap What do you think? |
fine, if we use the issue to track it. |
after the raise that code is unreachable
https://github.com/Open-MSS/MSS/blame/develop/mslib/utils/get_projection_params.py#L45
https://github.com/Open-MSS/MSS/blob/develop/mslib/utils/get_projection_params.py#L64
The function was moved, that can be also fixed in stable and I redo the changes at merge time if needed.
The text was updated successfully, but these errors were encountered: