?KML with ExtendedData to Shapefile

There are multiple ways to do this, but I'd choose a PythonCaller, since this is the cleanest option imho. You would have to expose the attributes somehow, because FME needs to know what it has to write out. I've chosen to do this in the PythonCaller as well, because the schema of your data seems to be fixed anyway.

Have a look at my solution in the attachment. You can now simply add a Shapefile writer to it in Automatic mode, but be aware that the attribute names can be too long for a Shapefile and might get truncated.

In case you don't have FME 2017, this is the Python code you can paste in the PythonCaller. Be sure to set the "Class or Function to Process Data" value to "processKmlData", so that it calls the feature function.

import fme
import fmeobjects
 
def processKmlData(feature):
    names = feature.getAttribute('kml_data{}.name')
    values = feature.getAttribute('kml_data{}.value')
    if not (isinstance(names, list) and isinstance(values, list)):
        return
    num_attributes = len(names)
    if num_attributes != len(values):
        return
    for i in range(num_attributes):
        feature.setAttribute(names[i], values[i])

FYI @krostir: I have just uploaded a custom transformer to the FME Hub that achieves the above in a more generic/elegant way. Check out the ListKeyValuePairExtractor!

Hi @krostir,

I am sorry to hear that! I spent a lot of time trying to write clear documentation... Unfortunately, those key and value list parameters are a bit confusing, but that's mainly because of a limitation of the FME GUI types. As far as I know, there's no way to create an input parameter for a single nested list.

Anyway, did you see that there is a Download Test button next the Download button on the FME Hub page? In that workspace, I create a couple of list types so you can see what it does.

For your specific case though, here is another example workspace that uses the ListKeyValuePairExtractor and your KML example file! On my machine, it took a long time to run by the way, but that was caused by some HTTP connection timeouts on the KML Reader.