Author Topic: kml parse errors  (Read 7313 times)

ZoomerBoomer

  • Newbie
  • *
  • Posts: 2
    • View Profile
kml parse errors
« on: September 30, 2007, 05:53:17 PM »
I've been playing with TFP for a couple of weeks and finally ponyed up the cash a couple of days ago. Great stuff! Simple and powerful.

I'm having a problem opening kml files that I exported from TFP. I've generated several and they all give me the exact same error message:
Open of file "blah blah.kml" failed: Parse error at line 4, column 21: not well-formed (invalid token).

Any ideas?

Krein

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 1203
  • TopoFusion Author
    • View Profile
    • http://www.topofusion.com/diary
kml parse errors
« Reply #1 on: September 30, 2007, 06:00:55 PM »
Interesting - I just double checked a .kml file export and GE seemed to load OK.

Can you email the offending .kml file to support@topofusion.com so we can take a look?

Thanks and sorry about the problem!

Krein

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 1203
  • TopoFusion Author
    • View Profile
    • http://www.topofusion.com/diary
kml parse errors
« Reply #2 on: October 01, 2007, 10:40:44 AM »
Thanks for sending the file along.  The problem is the ampersand in your filename.

TF uses the full filename for the 'name' field, and ampersand is a special XML character.  Our bug - for sure.

Simple fix is to open the .kml file up with a text editor and delete the & in lines 4 and 6.  It loads up fine after that.  I can also send you a fixed file, if you want.

Alternatively, you can save the .kml file out to a different directory on your computer that doesn't an ampersand in it.

The next version of TF (hopefully out soon) will have this .kml export issue fixed.

Thanks for reporting the problem!

ZoomerBoomer

  • Newbie
  • *
  • Posts: 2
    • View Profile
kml parse errors
« Reply #3 on: October 08, 2007, 08:45:39 AM »
Aha. Since the ampersand is in our account name, I wondered if that may be contributing to some other system issues (can't blame EVERYTHING on Microsoft. Well, maybe), so I changed our account name and voila, works great! I also received your notice that the version is posted that fixes the problem. Nice! Great product, great response.