ramazanalic / kml-samples

Automatically exported from code.google.com/p/kml-samples
0 stars 0 forks source link

Region/Lod behaviour is not according to KML specs #242

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
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.

Original issue reported on code.google.com by google@good-heavens.nl on 14 Feb 2009 at 6:42

Attachments:

GoogleCodeExporter commented 8 years ago
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.

Original comment by paul.m...@gmail.com on 10 Mar 2009 at 7:09

GoogleCodeExporter commented 8 years ago
Great defect report and test case. Thanks.

Original comment by api.roman.public@gmail.com on 10 Mar 2009 at 8:16

GoogleCodeExporter commented 8 years ago
Fixed in Google Earth 5.0.11733.9347

Original comment by api.roman.public@gmail.com on 2 Jun 2009 at 11:24