IF you have a 3D feature and you need it to be 2D then the 2DForcer is what you need.
IF you have a 3D feature and you need it to be 2D then the 2DForcer is what you need.
Maybe 3DForcer with an elevation value of 0 would be better ?
I do not want it to be 2D, I need my 3D model to "land" on WGS84 surface instead of hanging several meters above the surface.
I do not want it to be 2D, I need my 3D model to "land" on WGS84 surface instead of hanging several meters above the surface.
@lifalin2016 suggestion's sounds like something I would try...
IF you have a 3D feature and you need it to be 2D then the 2DForcer is what you need.
3D Forcer it is, thanks dude! But not with elevation value of 0, but I have feature's elevation as an attribute. So by using arithmetic functions it is possible to do that.
Now I am gonna use 3DForcer to reduce Z values of all points of a feature.
I have a MARK_Z value attribute and need to use Arithmetic Editor so that resulting z value becomes as z - MARK_Z. (z value of every single point of a feature minus MARK_Z attribute of that feature)
But I cannot get current z value in Arithmetic Editor. Any suggestion?
you can try the @ZValue() function in the Arithmetic Editor