How do you specify the the kml_open attribute to force folders to be expanded in a KML?

danilo_fme wrote:

Hi @tbuckler,

Did you expose the attribute kml_open in Writer?

Thanks,

Danilo

Yes, it doesn't appear to apply the open tag to the root document.

 

 

redgeographics wrote:

I had a closer look and it appears FME is writing the <open> tag on the placemarks rather than the folder. I suspect it's a bug so I'll pass this on to support.

Hi @tbuckler and @redgeographics,

 

I am investigating this and will let you know what I discover. Thank you for pointing this out.

 

 

Hi @tbuckler after chatting with development, I have this response :

 

 

In KML, each feature can have its own `<open>`, which is what we get from the `kml_open` attribute. So in that sense the behaviour is correct. However, it doesn't really help in this scenario, because you would want the folder which contains the features to be open, not the features themselves. In a typical workspace, FME will create a new folder for each feature type, and we don't have a way for the workspace to control the "open-ness" of that folder. A potential enhancement would be to add a feature type parameter which would allow users to control the open/closed behaviour of the auto-generated folder. We already have a number of other styling parameters which are set per feature type, so there is precedent for this type of thing.There is a workaround, which is somewhat complicated. You could write a new feature to a `Folder` feature type, and set the `kml_id` and `kml_open` values on this feature. Then, each "real" feature would have to have a `kml_parent` attribute set to the id of the folder. Basically this is manually creating a folder, rather than relying on the auto-generated folder.

 

 

If you would be interested in added a feature type parameter to add support the open/closed behaviour, please consider posting this idea at https://knowledge.safe.com/content/idea/post.html Kind Regards, Annabelle