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.
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.
Replies
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.
well ive been uisng ge 6.1 for some time, and no issue here
Should be both, as I tried the two on sunday with no success. I'll have to check when I get home though.
Aaron
is this from a tlog or a dataflash log?
The change of note from GE changelog: