-
Notifications
You must be signed in to change notification settings - Fork 802
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
concatenated operations #3819
Comments
…g with a NADCOND (3D) transformation (use case of refs OSGeo#3819)
I've submitted #3820 with a number of related fixes, but that doesn't solve your end-to-end issue. Basically you're pushing PROJ beyond its limits with the use of complex concatenated operations between a VertCRS and a GeogCRS, and then hoping that PROJ will apply that to a CompoundCRS |
…g with a NADCOND (3D) transformation (use case of refs OSGeo#3819)
Thanks for your quick response. Are you suggesting I register a custom compound crs for EPSG:4759+NOAA:752 and then make an other_transformation with the steps in a pipeline? If I add a compound_crs (say NOAA:3000) to the proj.db would PROJ realize that EPSG:4759+NOAA:752 was equivalent and use the other_transformation for NOAA:3000? Maybe I should ask for more general advice. We have these vertical datums, which depending on when they were made, relate back to different geographic 3d crs NAD83 (CORS96, NSRS2007, 2011 etc) or IGS/ITRF (08, 14 etc). I was trying to make it easier for a user to get from a vertical datum and its corresponding horizontal CRS to a different vertical datum in another horizontal crs. Maybe someone needs the MLLW from a NAD83(NSRS2007) model to be transformed to MHHW in ITRF14. From your answer #3616 before about PROJ only making transform that makes two jumps (like a->b->c but not a->b->c->d) then I thought I would supply concatenated operations so everything could meet at NAD83(2011) and there would always be a two step a->NAD83(2011)->c path to be found. Would you still suggest making pipelines (other_transformations), some other strategy or should I just stop at the 3d CRS applicable to a specific datum and tell people to learn to use PROJ? |
…g with a NADCOND (3D) transformation (use case of refs OSGeo#3819)
yes
If the name of NOAA:3000 is exactly
That makes sense. It is just that PROJ is confused when having just the vertical transformation "TXshlmat01_8301_MLLW_1983-2001 to NAD83(2011)" to infer how to do the more complex "NAD83(NSRS2007) + TXshlmat01_8301_MLLW_1983-2001 to NAD83(2011)"
I'm not sure which answer to give that. The more registered transformations you add, the easier & more reliable PROJ will behave, but the more complicated maintenance of the registry will be. Having a pivotal CRS like NAD83(2011) as you suggest can makes sense I guess |
Thanks very much. I will try making the compound crs entries with naming as you suggest. |
Hello,
We are making a lot of vertical datums, crs and transforms which seem to work thanks to #3616 (and #3617). We wanted to add some concatenated operations and those seem to work unless I add a geographic 3d to geographic 3d step at the end. Is the problem in trying to add a 3d transform at the end of what was mostly vertical, related to our custom authority or missing a step or method code? Thanks in advance for any help or pointers on what I have done wrong, I've attached my prototype proj.db.zip.
For example, we have tidal datums of Mean Lower Low Water (MLLW) and Local Mean Sea Level (LMSL) and a transform between them. We also have a transform from LMSL to Geoid09. I've tried to create two concatenated operations, one to go from MLLW to EPSG:4893 NAD83(NSRS2007) and the other to go from MLLW to EPSG:6319 NAD83(2011). The first one works but the second fails.
Both transforms start with the same three steps.
The second transform adds one more step.
4) NAD83(NSRS2007) (EPSG:4893) to NAD83(2011) (EPSG:6319) using grid_transform EPSG:8559
Running from our tidal EPSG:4759+NOAA:752 NAD83(NSRS2007) 2D+MLLW to EPSG:4893 NAD83(NSRS2007) works
Trying to extend to NAD83(2011) fails.
Projinfo doesn't return anything for for my attempt above but by leaving off the horizontal component it does find the concatenated_operation entry. It gives the message "Error when exporting to PROJ string: Invalid nature of source and/or targetCRS for Geographic/Geocentric conversion" which I don't understand or find reference to.
Running projinfo on the MLLW to NSRS2007 seems to work whether I supply the horizontal or not.
Thanks again,
Barry
The text was updated successfully, but these errors were encountered: