Replies to This Discussion

Permalink Reply by aaron.reyna on December 6, 2011 at 2:57pm

The change of note from GE changelog:

To conform more closely with the OGC KML 2.2 standard, we've made the parsing of the <coordinates> tag more strict in version 6.1. Spaces must only be used to separate the (longitude,latitude,altitude) triplets which specify the coordinates of a single point. It is invalid to add spaces between individual coordinates. We understand that previous versions of the client were more lenient, so if your KML files contain spaces beween coordinates in coordinate triplets, an easy workaround is to remove all whitespace located immediately before or after commas inside a <coordinates> tag.

• ▶ Reply

DeveloperPermalink Reply by Michael Oborne on December 6, 2011 at 3:07pm

is this from a tlog or a dataflash log?

• ▶ Reply

Permalink Reply by aaron.reyna on December 6, 2011 at 3:10pm

Should be both, as I tried the two on sunday with no success. I'll have to check when I get home though.

Aaron

• ▶ Reply

DeveloperPermalink Reply by Michael Oborne on December 6, 2011 at 3:11pm

well ive been uisng ge 6.1 for some time, and no issue here

• ▶ Reply

Permalink Reply by aaron.reyna on December 6, 2011 at 3:21pm

This was updated withing the past 24-48 hours. I'd try it again. I bet the dataflash log has spaces in it.

• ▶ Reply

Permalink Reply by aaron.reyna on December 6, 2011 at 3:22pm

Also, to be clear, it causes to extent of the KML to be invalid, not necessarily the KML itself. If you zoom into the extent of the flight path, it should be there.

• ▶ Reply

DeveloperPermalink Reply by Michael Oborne on December 6, 2011 at 3:27pm

wehn you get home, can you post the bad one the planner created? all mine are the 3 tupiles, a single space or line break, then 3 tuples again. which is valid.

• ▶ Reply