Hi List,
Just wondering if this is a bug or “as designed”.
I’m using a network link into Google Earth. When I access a Layer Group, rather than treat it as a single layer as happens via typical WMS, in Google Earth all of the component parts function as separate layers.
This causes a problem because some of my layer groups have 60 or more layer components (with various scale thresholds), so GE is having to ping GeoServer 60 times every time I pan.
Is this by design?
Cheers,
Jonathan
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
On Thu, Nov 7, 2013 at 4:14 PM, Jonathan Moules <
jonathanmoules@anonymised.com> wrote:
Hi List,
Just wondering if this is a bug or "as designed".
I'm using a network link into Google Earth. When I access a Layer Group,
rather than treat it as a single layer as happens via typical WMS, in
Google Earth all of the component parts function as separate layers.
This causes a problem because some of my layer groups have 60 or more
layer components (with various scale thresholds), so GE is having to ping
GeoServer 60 times every time I pan.
Is this by design?
It is. Generating the output for 60 vector layers in a single flat document
presents some challenges,
would require some internal rework to be made possible and would possibly
not work with all the options
(e.g., I believe there would be some serious issues trying to make
superoverlays work with that approach).
Cheers
Andrea
--
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
Hmmm. Ok. I guess it’s because I keep thinking of them as a WMS, when really it’s a kind of WFS/WMS hybrid.
Thinking about it, it’s not much of an issue - most of my layer groups are for OpenLayers base-maps which aren’t really necessary with Google Earth.
Thanks,
Jonathan
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
···
On 7 November 2013 15:26, Andrea Aime <andrea.aime@anonymised.com> wrote:
On Thu, Nov 7, 2013 at 4:14 PM, Jonathan Moules <jonathanmoules@anonymised.com> wrote:
Hi List,
Just wondering if this is a bug or “as designed”.
I’m using a network link into Google Earth. When I access a Layer Group, rather than treat it as a single layer as happens via typical WMS, in Google Earth all of the component parts function as separate layers.
This causes a problem because some of my layer groups have 60 or more layer components (with various scale thresholds), so GE is having to ping GeoServer 60 times every time I pan.
Is this by design?
It is. Generating the output for 60 vector layers in a single flat document presents some challenges,
would require some internal rework to be made possible and would possibly not work with all the options
(e.g., I believe there would be some serious issues trying to make superoverlays work with that approach).
Cheers
Andrea
–
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
On Thu, Nov 7, 2013 at 4:40 PM, Jonathan Moules <
jonathanmoules@anonymised.com> wrote:
Hmmm. Ok. I guess it's because I keep thinking of them as a WMS, when
really it's a kind of WFS/WMS hybrid.
Yep. Indeed with the 2.4.x code base we have a WFS KML output format that
does attributes and no styles,
and a WMS output that does styles and attributes only optionally, plus a
lot of other trickery/options that only makes
sense if you try to visualize the KML (the WFS version instead is more
meant for someone to read and process
the data somehow). Both outputs are actually generated from the same code
base, just a matter of different
flags passed down when we generate the KML
Cheers
Andrea
--
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------