You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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 show edges or show bounding box are applied.
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 Z/111139.0 which converts meters to degrees. Maybe there is an easy way to expose something like this so that users put in a coefficient and the Z coordinates are transformed?
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: