Thanks for this tip, very useful. I see though that QGIS doesn’t seem to like the KML MultiGeometry node being present and gives a ‘cannot establish connection’ error. I wonder if you know a way round this issue?

Thanks.

I have a KML file of a set of polygons digitized in Google Earth. First thing I did was add a new layer in QGIS [set to view All Files (*.*)]. From there I save the KML imported layer as a shapefile (to allow editing, etc.). QGIS will ask what projection the shapefile will be saved in. For my purposes, since I needed to do an affine transformation (move) on my polygon set, I chose to save it in UTM projection for my region in the Philippines (+proj=utm +zone=51 +ellps=WGS84 +datum=WGS84 +units=m +no_defs) since I needed to overlay the polygon on an image in the same UTM projection. Once the KML file layer had been saved to SHP, I discard it and use the saved shapefile in UTM projection for editing, etc.

After doing the necessary transformations on the polygon shapefile (GE does not allow moving or any other affine transformation on the features in it), I now need to put it back in GE as a KML. I do so by saving the file once again as a shapefile, but this time having geographic coordinates (+proj=longlat +ellps=WGS84 +datum=WGS84 +no_defs). This edited shapefile in lat-long coordinates is then converted to a KML using the above-mentioned OGR Layer Converter Plugin of QGIS. The shapefile NEEDS TO BE IN lat-long when converted to KML as GE will only correctly recognize a KML in geographic coordinates. Don’t forget to type in the .kml extension when you convert the shapefile to KML so the system can easily associate it with GE. Open the KML file in GE et le voila! Your new shapefile is now ready as an overlay in GE.

So no shareware, limited freewares and plugins necessary, etc. for converting SHP to KML and VV, really. QGIS does the job if you know these basic steps… and now you know. ;-)

Cheers.

if I try this with lat/lon i always get the error: index result for “..” too long, >100 characters (254)

anyone knows the problem ? :(