My favorites | Sign in
Logo
             
New issue | Search
for
| Advanced search | Search tips
Issue 242: Region/Lod behaviour is not according to KML specs
3 people starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  ----
Closed:  Jun 02
Type-Defect
Priority-Medium
Product-Earth
Internal-1702698


Sign in to add a comment
 
Reported by google@good-heavens.nl, Feb 14, 2009
Which products are affected?
Google Earth 5.0

What steps will reproduce the problem?
1. Open the attached KML file in GE
2. Zoom in so that all the five boxes are visible
3. Zoom out slowly

What is the expected output or behavior? What do you see instead?
The boxes should disappear all at the same time. That is not the case: the 
narrow/high box disappears first and the wide/low box last.

What application versions (if any) are you using?
Google Earth 5.0
KML 2.2

Please provide any additional information (code snippets/links) below.
According to the KML specification, the turnover point for the visibility 
of a region is determined by the square root of the number of pixels the 
region covers as displayed in Google Earth. The test KML file is created 
so that the turnover point is the same for all boxes. However, it appears 
that it is the *width in pixels* of the box that determines the turnover 
point.
Region-test.kml
4.7 KB   Download
Comment 1 by paul.mace, Mar 10, 2009
YES! Changing the 'square pixels' value does nothing until it begins to approach
region width on screen.  In my case, alaska and texas data always appears before
california...because they are wide regions rather than tall.
Comment 2 by api.roman.public, Mar 10, 2009
Great defect report and test case. Thanks.
Labels: Product-Earth Internal-1702698
Comment 3 by api.roman.public, Jun 02, 2009
Fixed in Google Earth 5.0.11733.9347
Status: Fixed
Sign in to add a comment

Hosted by Google Code