I have a view carrying out a proximity search over at Viking Visions - Proximity Search and switched on the KML module to provide a KML download of people's results. This is a sample placemark produced by the KML feed:

<Placemark>
  <name>
    <![CDATA[<a href="/node/1950">St. John&#039;s Kirk, Norwick</a>]]>
  </name>
  <description>
    <![CDATA[<p>Credit:<br />
Morris, Christopher D. “Norse Settlement in Shetland: The Shetland Chapel Sites.” In <em>Denmark and Scotland: The Cultural and Environmental Resources of Small Nations</em>. Edited by Gillian Fellows-Jenson. Denmark: Det Kongelige Danske Videnskabernes Selskab, 2001.</p>
]]>
  </description>
    <Point>
    <coordinates>POINT (-0.804431 60.804679),,0</coordinates>
  </Point>
</Placemark>

When the file is viewed in Google Earth, firstly the "CDATA"s appear in the point labels. More worryingly is the latitude and longitude have been reversed. Thirdly, all the points in the KML file show up at the geographical equivalent of 0,0, just off the west coast of Africa! Not great as I don't think the Vikings made it that far (though I'm prepared to be wrong).

Lat and Long are both stored inside the same geofield and I have to pick the same field for each of Latitude and Longitude when setting up the feed. I can't see a way to separate them.

Clues? Pointers?