I have a workspace projecting 3D airspaces to a KML. I am trying to color each different type of airspace certain colors for each type and opacity value but the writer seems to ignore the kmlstyler and I end up with random colors with no opacity. Anyone run into this before?
Page 1 / 1
Hello @fredjudson, thanks for posting! I ran a quick test in FME 2023.0.0.1 and everything appears to be styled as per the KMLStyler parameters. May I ask what version of FME Form you're currently using? Also, what format are the airspaces read in as? If you're able to share a simple workspace, subset of data, or how the KMLStyler is configured in your workspace, that may also be helpful! Best, Kailin.
Hi, I was using the 2023.3.6 but just installed 2023.0.0.1 and still did not get the results I am expecting. I created a new workspace paired down to just the airspaces. The data format is a ESRI rest service https://services6.arcgis.com/ssFJjBXIUyZDrSYZ/ArcGIS/rest/services/Class_Airspace/FeatureServer/. Here is a screen shot where the colors should be all the same:
Thank you for looking into this!
Just adding an update in the event others stumble upon a similar issue! The workaround was to use the GeometryColorSetter. The Alpha parameter is responsible for opacity, where 1 is solid/filled and 0 is transparent. If the goal is to only color certain features or parts of, you're able to specify an Geometry XQuery, otherwise feel free to leave it blank.
The color settings in the KMLStyler only work on vector data (lines, polygons, points). 3D features are styled based on the appearance settings of the 3D geometry. Once the data passed through the Extruder, it became 3D. In this case, the extrusion geometries being written did not have any appearance information, so it appears that Google Earth was assigning random colors. There are a few different ways we can get around this, but the easiest is likely the GeometryColorSetter. Hope this helps! Best, Kailin.