Hi @karnil,

To cut right to the chase, this is how you could do it:

You should not use the GeometryInstantiator here, as it does the exact opposite of what you want to achieve: it "flattens" a geometry instance (which is called "instantiation"), so that the transformation matrix is applied and each instance becomes its own independent geometry, which could take up a lot of memory.

To add your tree into FME's internal library of reusable textures, appearances, rasters and geometry definitions, you have to use the SharedItemAdder. This will give you an ID, which can be merged onto the point features. Then, use the SharedItemIDSetter to set the ID of the geometry definition to your point, so that the tree instance is positioned there. Better read the documentation of that last transformer, as it provides some useful additional information!

Hope this works for you.

PS: Don't remove the geometry on your points (or trees for that matter) like in your example! The SharedItemIDSetter uses this. Also, the stuff in the purple bookmark is unnecessary: you only need to add 1 tree (of each kind) to the library.

Hi @karnil,

I have created a Knowledge Center article illustrating how to replace points with an instanced model, which you can find at Creating and using geometry instances.

sorry to revive this tread, but this method does not work for me, I am not sure why...Do you have any ideas? Thank you!!