Which products are affected?
Google Earth v. 5.1.3533.1731
What steps will reproduce the problem?
1. Cut and paste the KML code at the bottom of this bug description into
file
2. Load the new .kml file into Google Earth
What is the expected output or behavior? What do you see instead?
Expected output is that the four corners of the overlay will be -
210.00,45.00 -130.00,48.00 -115.00,75.00 -210.00,72.00.
Actual output is that the four corners of the overlay are -180.00,45.00 -
130.00,48.00 -115.00,75.00 -180.00,72.00
What application versions (if any) are you using?
Google Earth v. 5.1.3533.1731
Which operating systems (and/or relevant web browsers) are affected?
N/A
Please provide any additional information (code snippets/links) below.
I am using the gx:LatLonQuad kml tag to specify the corners of my
overlay. The lower left and upper left corners are to the left of the
dateline (when viewing north), and the lower right and upper right corners
are to the right of the dateline. I have tried using the normal
coordinate specification for these corners, but then Google Earth wraps
the overlay all the way around the earth (and reverses it too!).
So then I tried using unwrapped lat-long coordinates. This also does not
work, because Google Earth will stop at the dateline in displaying the
overlay - it ignores the unwrapped coordinates!
The KML code that reproduces this issue is below.
-----------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://www.opengis.net/kml/2.2"
xmlns:gx="http://www.google.com/kml/ext/2.2">
<Folder>
<name>Ground Overlays</name>
<description>Alaska Ground Overlay</description>
<GroundOverlay>
<name>Large-scale overlay on terrain</name>
<description>Overlay shows Alaska IFR VFR areas
on July 13th, 2001.</description>
<Icon>
<href>http://aawu.arh.noaa.gov/fcstgraphics/ifr.gif</href>
</Icon>
<gx:LatLonQuad>
<coordinates>
-210.00,45.00 -130.00,48.00 -115.00,75.00 -210.00,72.00
</coordinates>
</gx:LatLonQuad>
</GroundOverlay>
</Folder>
</kml>
-----------------------------------------------
Original issue reported on code.google.com by Christin...@gmail.com on 22 Mar 2010 at 6:09
Original issue reported on code.google.com by
Christin...@gmail.com
on 22 Mar 2010 at 6:09