Have you tried sending the feaures to the Inspector and check for the presence of the attributes there?

Try connecting the Inspector to the last transformer before the writer.

I have inspected the values there and they are fine. If I rename attributes to be shorter and use a ShapeFile writer then I can get the values but would rather use a KML (or other format) that copes with longer attribute name.

Can you post a minimal workspace that reproduces the behavior here?

Here one is joiner.zip

As far as I can tell, the attributes are all there in the KML, inside the CDATA block of the <description> tag. Or am I missing something?

Here's from importing the KML in Google Earth:

When I look the FME Data Inspector or QGIS I see the following in the table.

The attributes are visible in the FME Inspector by looking at the "kml_description" attribute:

I don't know how QGIS handles KML attributes, however.

David,

Thanks for looking into this. Do you know why the INSPIREID is shown in the attribute table and the other values end up in the kml_description instead?

And why there are columns shown in the table that don't contain the data?

I have some other workflows that just read in a Shapefiles, filter the features using the clipper and then write a KML. In these cases all the values are visible in the data inspector's table.

It would be great if the FME could always put the values into the table.

Ian

Unfortunately I don't know, I very rarely use KML. Let's hope someone else can chime in here.

Hi @ianashley,

There is a list attribute from the source KML (kml_schema_data{}) that is overriding the User Attributes set on the output feature type. We are working on correcting this, but in the meantime removing this list will ensure your attributes are written correctly.

Please open the source KML feature type Properties and select the Format Attribute tab. Click the boxes next to kml_schema_data{}.name and kml_schema_data{}.value. This will expose the list to the workspace.

Next, add an AttributeRemover transformer (the AttributeManager cannot remove lists), and select kml_schema_data{} in Lists to Remove. You can leave Attributes to Remove unset.

Run the workspace again - the attributes in the output should now be properly filled.

Thanks very much. That worked perfectly.

BTW I think outputting as GML suffers from the same problem, they could be related.