Details
-
Type:
Improvement
-
Status:
Reopened
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Google Earth KML Output
-
Labels:None
-
Number of attachments :
Description
In KML output, one style is encoded for each feature/placemark. We could probably save a bit of bandwidth by recycling those styles for features using the same sets of rules, and it would likely make things easier on Google Earth as well.
Activity
David Winslow
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | Closed [ 6 ] |
| Resolution | Won't Fix [ 2 ] |
David Winslow
made changes -
| Resolution | Won't Fix [ 2 ] | |
| Status | Closed [ 6 ] | Reopened [ 4 ] |
I took a look at this and it doesn't seem like it would be very useful. For one thing, KML styles don't do dynamic anything, so there are a lot of SLDs for which we can't translate directly (so we'd have to enumerate all possible values with a predictable ID so that they could be referenced from the actual KML...). On top of that, KML styles are inherently pretty short (you can only have one icon, one line, ...) so compressing it all down to a single reference only saves you so much. In comparison to a typical polygon geometry, it's not even that big a win (in my tests, the 230 kb or so of KML for topp:states went to about 220, plus a second request for a 4kb style library).