Question

Error reading KML: Could not determine the root kml file of


Badge +5

I'm trying to read some USFS wildland fire data. There's a link to the kml on their website:

http://www.wfas.net/google-earth/wfas_nfdr.kmz

When I use the url in the kml reader, it downloads it to a temp file location successfully (I can see it there) and it's unzipped. It's got a folder structure about 5 deep.

Then I get

FATAL |KML: Could not determine the root kml file of `C:\\Users\\xxx\\AppData\\Local\\Temp\\FME_OGCKML_KMZ_1562607566639_14376'

 

If I go to the temp file location and navigate down to the kml, I can read it in no problem.

C:\\Users\\xxx\\AppData\\Local\\Temp\\FME_OGCKML_KMZ_1562607566639_14376\\fsfiles\\office\\wfas2\\dir-obs\\wfas_nfdr.kml

 

 

 

 

 


6 replies

Userlevel 3
Badge +17

Hi @jakethepainter

It appears this is related to a known issue where FME cannot determine the KML file to read if there are multiple levels of nesting folders. I will attach this post to the issue (FMEENGINE-29795) and update you once it has been resolved.

Badge +5

Thanks. Is there any sort of workaround? Or do you have a sense of the timeframe?

Badge +5

Here's my workaround for now. Use an httpcaller to get the data down to a known location. Then embed the rest of my workspace in a separate workspace and call it from the workspace runner. The kml reader in the inner workspace uses the recursive subfolder searcher to get all the way down to the kml.

Badge +5

Does anyone know if this issue has been fixed in 2019.2?

Userlevel 3
Badge +17

Does anyone know if this issue has been fixed in 2019.2?

Hi @jakethepainter

According to our internal records, this issue was not been fixed in 2019.2.

Badge +4

Hi @jakethepainter

According to our internal records, this issue was not been fixed in 2019.2.

Doesn't seem fixed at 2020.1.0.1, either.

Reply