-
Notifications
You must be signed in to change notification settings - Fork 15
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
Add support for CRS #6
Comments
While that doesn’t solve the issue fully, you can use ’cjio reproject’ on CityJSON files before it’s implemented. |
That's true. I already did that, but it's kind of a mess to try and find an appropriate projection for the dataset. |
selfishly I would also like to see CRS support added in, but I fully understand that the app is much simpler without it and it could be a pain to add in and maintain. I'm curious if instead of fully trying to support CRS identification and transformation if it's perhaps possible to support a basic transform of just the Z value of each coordinate? I would imagine this being a setting applied by choice after a file is opened similar to the way For example, in the case of EPSG:4979 where X and Y are in degrees and Z is in meters, to transform the Z into degrees so that Azul will render everything properly you simply do Just thinking out loud. |
It would be useful to add support for CRS when reading a CityJSON (or CityGML) file.
This is really important in cases where horizontal and vertical coordinates are using different units, for instance EPSG:4979 where X and Y are in degrees and Z is in meters (also related to issue #4).
The text was updated successfully, but these errors were encountered: