Skip to main content
  • EN

When im trying to transform citygml data to ogckml, the FME data inspector does not view the data correctly in 3d view. Instead of separate individual 3D buildings, the data is just a long thin "stick". Data looks correct when viewing with google earth and with FME data inspector in 2D view.

Why is this happening?

Also when trying to convert that kml to wavefront object, the object file comes out as a long stick also.

It seems like every kml file containing 3D data is showing up as along thin stick in fme data inspector when viewed in 3d

Most of the geometries in KML are stored in lat/long coordinates. However, the Z values are stored in meters, which are much smaller than the degrees used by X and Y.

If you attempt to view the lat/long 3D data in Data Inspector, the Z values will be much larger than the X and Y, making it appear to be a long thin stick. Please use a CsmapReprojector to convert to a projected coordinate system for viewing in DI, or writing to OBJ.

Thank you for your answer @DaveAtSafe.

The Z values seems to be correct. For example one of the KML output features has minimum extends of 24.9894137996254, 60.293148440891, 20.374 and maximum extends of 24.9894889811011, 60.2931722656237, 23.704 but still shows up as a long thin stick when viewed in DI.

The KML writer also seems to automatically re-project the coordinate values to LL84 system (according to the log), if any other re-projector transformer is not used.

I tried the CsmapReprojector but it did not help at all.

When i converted the KML file to OBJ, re-projecting the data back to the original coordinate system with the CsmapReprojector helped though, and atleast the obj file looks fine now.

Reply


Community Stats

30,108
Posts
114,291
Replies
37,743
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.