Skip to main content
Question

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


jakethepainter
Contributor
Forum|alt.badge.img+6

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

 

 

 

 

 

8 replies

debbiatsafe
Safer
Forum|alt.badge.img+20

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.


jakethepainter
Contributor
Forum|alt.badge.img+6

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


jakethepainter
Contributor
Forum|alt.badge.img+6

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.


jakethepainter
Contributor
Forum|alt.badge.img+6

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


debbiatsafe
Safer
Forum|alt.badge.img+20
jakethepainter wrote:

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.


setld_solutions
Contributor
Forum|alt.badge.img+7
debbiatsafe wrote:

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.


deanhowell
Influencer
Forum|alt.badge.img+23
  • Influencer
  • April 14, 2025

Any news if this has been fixed yet as I am using 2023.2.1 and am getting the same error when trying to read KMZ files


saraatsafe
Safer
Forum|alt.badge.img+8
  • Safer
  • April 17, 2025

Hi ​@deanhowell, ​@setld_solutions, & ​@jakethepainter

I followed up on this ticket and it’s been sitting for a while but dev reports that there will likely be a fix ready later this year. For now please continue to use ​@jakethepainter’s HTTPCaller workaround.

Thank you for your patience and please let me know if there are any further questions! 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings