A flag indicating if the KML node is highlighted. Highlights the node if is_highlighted is true, unhighlights it otherwise. All of the connected map views will be updated. This controls whether the default style or an alternate 'highlighted' style (if present) is used for rendering the node. This is unrelated to the concept of selection in this API.
A flag indicating if the KML node is visible. Makes the node visible if is_visible is true, hides it otherwise. All of the connected map views will be updated. In order for a node to be visible, all of its ancestors must also be visible. Changing the visibility of one node may affect visibility of other nodes in the dataset hierarchy, such as child nodes.
The container's list item type. See 'listItemType' attribute of 'ListStyle' in the KML specification for more information. This defines how visibility selection should work, enabling either single or multiple selection of child nodes when shown in a list (for example, a legend). When the item type is KmlListItemType.RadioFolder, making a node visible will hide its sibling nodes.
The KML node's time extent. Represents the TimeExtent equivalent of a KML node's TimeStamp[https://docs.opengeospatial.org/is/12-007r2/12-007r2.html#1168] or https://docs.opengeospatial.org/is/12-007r2/12-007r2.html#1181. A KmlContainer node such as KmlDocument or KmlFolder may have its own TimeExtent independent of its child nodes. All KML TimeStamps and TimeSpans specified in a KML/KMZ file are converted to their UTC TimeExtent equivalents.
The color mask used to tint the node's icon. A color mask that can be used to blend the image associated with the KML node. Pixels in the image are multiplied by this color channel-by-channel. Colors in KML are specified in ABGR order. When no UX icon is specified, you can use this color to draw a placeholder for use in the UI (for example, a legend). UX icons are not pre-tinted; it is the application's responsibility to apply the tint color to the UX icon before displaying it.
Saves the node and any referenced local files into a zipped KMZ archive. The node will be saved to a KMZ file to ensure that any referenced files are available locally when sharing the file with others. If this method is called on a leaf node (e.g. KMLPlacemark, KMLGroundOverlay, etc), only that node and its referenced files will be saved. If this method is called on container node (e.g. KMLDocument, KMLFolder), the node and all of its children and referenced files will be saved. If this method is called on a KMLNetworkLink, the link will be saved but the children will not. This is because the children will simply be refetched when the saved KMLNetworkLink is loaded. Saving referenced files will differ based on the type of reference. For HTTP paths, the path will be saved as is but the referenced file will not be zipped into the archive, as it will simply be refetched when the new KMZ is loaded. For relative paths, the path will be saved as is and the referenced file will be zipped relative to the root of the KMZ file. For absolute paths, the path will be converted to a relative path, and the referenced file will be zipped into a "files" folder at the root of the KMZ file. For example, "C:/icons/some_icon.png" would be converted to "files/some_icon.png" and stored at that location in the KMZ file. The filename supports unicode characters as well as nested directories. It must be non-empty and there must not be an existing file located there. Saving a node to a KMZ file requires an ArcGIS Runtime 'Standard' license level.