Skip to content

Conversation

@asinghvi17
Copy link
Member

Fixes #102 by automatically appending +type=crs to ProjString objects when creating a CRS. Without this parameter, proj_create() creates a projection object instead of a CRS object, causing Transformation to fail with "source_crs is not a CRS".

The fix ensures ProjString works consistently with plain strings when used in Transformation and other CRS operations.

🤖 Generated with Claude Code

Human reviewed, seems reasonable to me and a small change.

asinghvi17 and others added 2 commits November 13, 2025 22:25
Fixes #102 by automatically appending +type=crs to ProjString objects
when creating a CRS. Without this parameter, proj_create() creates a
projection object instead of a CRS object, causing Transformation to
fail with "source_crs is not a CRS".

The fix ensures ProjString works consistently with plain strings when
used in Transformation and other CRS operations.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
Tests verify that ProjString objects work identically to plain strings
when used in Transformation. Includes test cases for:
- Original issue #102 example (aeqd projection)
- Simple longlat projection
- ProjString with +type=crs already present
- Both source and target as ProjString

All tests verify that the same transformation pipeline is created
regardless of whether String or ProjString is used.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
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

Successfully merging this pull request may close these issues.

Transformation from ProjString type does not work

2 participants