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
The position of the vertices of the geometries is taken from the vertices values in the CityJSON files. However, we encountered problems when trying to view files with "high" vertex x,y-values. The viewer now uses mesh.geometry.normalize() which rescales and translates the geometry, making the geometry centered at (0, 0, 0) and have a bounding sphere of radius 1.0. For viewing purposes this is fine, however, maybe the sizes need to be maintained for certain applications (e.g. measuring distances in the viewer) if the viewer would be extended with other functionalities in the future. This doesn't seem to be a problem for now.
The text was updated successfully, but these errors were encountered:
I am not sure what normalize() does, but you could use the trick from geo1015-hw02 and translate to (minx,miny,minz) first and then normalise? Or does it do this?
The position of the vertices of the geometries is taken from the vertices values in the CityJSON files. However, we encountered problems when trying to view files with "high" vertex x,y-values. The viewer now uses
mesh.geometry.normalize()
which rescales and translates the geometry, making the geometry centered at (0, 0, 0) and have a bounding sphere of radius 1.0. For viewing purposes this is fine, however, maybe the sizes need to be maintained for certain applications (e.g. measuring distances in the viewer) if the viewer would be extended with other functionalities in the future. This doesn't seem to be a problem for now.The text was updated successfully, but these errors were encountered: