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

createOperations(): use more appropriate operation when using a 'PROJ {grid_name}' geoid model, based on matching the vertical datum #4379

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rouault
Copy link
Member

@rouault rouault commented Jan 14, 2025

Helps when transforming from 'NAD83(2011) / Puerto Rico and Virgin Is. + "VIVD09 height + PROJ us_noaa_g2012bp0.tif' to NAD83(2011). Without that fix, PROJ would use the EPSG record for the NAD83(2011) <--> PRVD02 height (Puerto Rico) to get the extent of the transformation, instead of the one for NAD83(2011) <--> VIVD09 height (Virgin Islands), causing the resulting global transformation to not be usable in practice.

… {grid_name}' geoid model, based on matching the vertical datum

Helps when transforming from 'NAD83(2011) / Puerto Rico and Virgin Is. + "VIVD09 height + PROJ us_noaa_g2012bp0.tif' to NAD83(2011).
Without that fix, PROJ would use the EPSG record for the NAD83(2011) <--> PRVD02 height (Puerto Rico) to get the extent of
the transformation, instead of the one for NAD83(2011) <--> VIVD09 height (Virgin Islands), causing the
resulting global transformation to not be usable in practice.
@rouault rouault added this to the 9.6.0 milestone Jan 14, 2025
@kbevers
Copy link
Member

kbevers commented Jan 14, 2025

I am not sure I understand this. Is this specific to CRS's described in WKT or a more general thing?

@rouault
Copy link
Member Author

rouault commented Jan 14, 2025

I am not sure I understand this. Is this specific to CRS's described in WKT or a more general thing?

The fix is general to geoid grids that are referenced multiple times in the grid_transformation table with different extents. This is just the use case that triggered the need for this fix.

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.

2 participants