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

Vertical Projections #425

Open
jb10016 opened this issue Feb 16, 2022 · 4 comments
Open

Vertical Projections #425

jb10016 opened this issue Feb 16, 2022 · 4 comments

Comments

@jb10016
Copy link
Contributor

jb10016 commented Feb 16, 2022

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 ...

@philipbaileynar
Copy link
Contributor

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?

@jb10016
Copy link
Contributor Author

jb10016 commented Feb 16, 2022

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.

@philipbaileynar
Copy link
Contributor

@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.)

@jb10016
Copy link
Contributor Author

jb10016 commented Feb 16, 2022

@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.

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

No branches or pull requests

2 participants