Skip to content
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

Open
ReimarBauer opened this issue Feb 5, 2025 · 7 comments
Open

problem in get_projection_params #2622

ReimarBauer opened this issue Feb 5, 2025 · 7 comments
Assignees

Comments

@ReimarBauer
Copy link
Member

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.

@ReimarBauer ReimarBauer added this to the 10.0.0 milestone Feb 5, 2025
@annapurna-gupta
Copy link
Contributor

@ReimarBauer Are AUTO and AUTO2 projections intended to be supported, or should the raise stay and the unreachable code be removed?

@ReimarBauer
Copy link
Member Author

ReimarBauer commented Feb 15, 2025

Please ask @joernu76. I assigned the issue to.

@annapurna-gupta
Copy link
Contributor

@joernu76 can i work on this issue?

@ReimarBauer
Copy link
Member Author

ReimarBauer commented Feb 19, 2025

@ReimarBauer Are AUTO and AUTO2 projections intended to be supported, or should the raise stay and the unreachable code be removed?

I have no idea. That´s why I think it is a task for Joern because he is familiar with that math.

@joernu76
Copy link
Member

These are projections described in the WMS standards, e.g. here https://portal.ogc.org/files/?artifact_id=14416
I do not know why we do not support them (judging from the raise ValueError).

This commit 71de73e tried to make MSWMS more standards compliant in this regard.
The message indicates "AUTO/AUTO2 projections are not yet supported due to technical difficulties in basemap", which isn't a lot of information. basemap hasn't really changed in the last seven years, so if the statement was true, this likely hasn't changed.
On the other hand, I do not immediately see why we couldn't work around basemaps problems...?

I personally would leave this code in there as minder and maybe add an issue to revisit this?

@ReimarBauer
Copy link
Member Author

ReimarBauer commented Feb 20, 2025

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
When we have on basemap an issue about Auto/Auto2 we can link it here and label this one with Upstream Fix needed.

What do you think?

@ReimarBauer ReimarBauer removed this from the 10.0.0 milestone Feb 20, 2025
@joernu76
Copy link
Member

fine, if we use the issue to track it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants