-
Notifications
You must be signed in to change notification settings - Fork 5
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
Vertical Projections #425
Comments
Do you mean vertical "datums"? I'm unfamiliar with vertical projections. Does this require different handling of the raster cell values, or is this more about users encountering problems importing rasters into projects with inconsistent vertical projections? |
My bad Pip - so used to using the language Pro spits out in its ortho processing tools! Yes, of course - vertical datums. The issue appears to be with loading rasters where these have been set as opposed to undefined. |
@jb10016 see this recent comment for a temporary workaround. It's a hack, but it has helped get folks over the hump. (Of course it runs the risk of users ignoring the true vertical datum associated with their data and just forcing ArcGIS to override any differences.) |
@philipbaileynar - I think the easiest workaround is to remove the vertical datum in the raster properties - that does the trick - but as you say - the user needs to ensure that they are being consistent. |
Had a few queries about people working with datasets where the rasters have vertical projection systems defined. The simplest workaround has been to simply remove the projection (retaining the horizontal projection obviously), but am wondering if this would be something easy to catch on loading and ignore/track to ensure consistency ...
The text was updated successfully, but these errors were encountered: