Skip to content

Projection Extension migrate doesn't handle "proj:epsg": None case correctly #1543

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

Closed
Kirill888 opened this issue Apr 4, 2025 · 0 comments · Fixed by #1544
Closed

Projection Extension migrate doesn't handle "proj:epsg": None case correctly #1543

Kirill888 opened this issue Apr 4, 2025 · 0 comments · Fixed by #1544
Labels
bug Things which are broken

Comments

@Kirill888
Copy link

When "proj:epsg": None is set on input, migrate code will generate "proj:code": "EPSG:None" on output breaking CRS access.

Culprit is here:

if "proj:epsg" in obj["properties"]:
epsg = obj["properties"]["proj:epsg"]
obj["properties"]["proj:code"] = f"EPSG:{epsg}"
del obj["properties"]["proj:epsg"]

it should include check for None in there.

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

Successfully merging a pull request may close this issue.

2 participants