[Geoserver-users] Cross Layer Filtering and alternatives

Stephen V. Mather

2012-04-04 21:05:34 UTC

Hi Mike,
With WMS, I'd call it a request, rather than a query.
Try just commas between your requested layers, ala:

http://localhost:8080/geoserver/test/wms/kml?layers=test:Locations,test:Othe
rLocations&bbox=40,15,76,36

Best,
Steve

Stephen Mather
Geographic Information Systems (GIS) Manager
(216) 635-3243
***@clevelandmetroparks.com
clevelandmetroparks.com

-----Original Message-----
From: Digital.goetz [mailto:***@gmail.com]
Sent: Wednesday, April 04, 2012 4:37 PM
To: geoserver-***@lists.sourceforge.net
Subject: [Geoserver-users] Cross Layer Filtering and alternatives

Hello,

I'm fairly new to the geo-spatial field and I am looking into merging the
results of two WMS (i believe this is the term) queries.

As it stands, I can obtain a KML file (or some other output format) from
each the following URLS:

http://localhost:8080/geoserver/test/wms/kml?layers=test:Locations&bbox=40,1
5,76,36
http://localhost:8080/geoserver/test/wms/kml?layers=test:OtherLocations&bbox
=40,15,76,36

However, I'm wanting to combine the two outputs into a single URL. I'm not
performing any complex merge methods, but simply wanting the data from 2
layers that share the same bounding box. Is Cross Layer Filtering the way
to go, or am I looking in the wrong area?

Thank you in advance,
Mike

--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/Cross-Layer-Filtering-and-alternatives-t
p4687709p4687709.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

----------------------------------------------------------------------------
--
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev