[Geoserver-users] Parameter Pass-Thru on KML_reflect

GeoServer GeoServer User
1

I would think that these basic parameters that affect the way it works in GEarth, like KMScore and KMAttr, should be passed through. This still gets you the benefits of not having to worry about all the other crap (EPSG, VERSION, BBOX, etc. etc.) in a normal WMS request.

thanks,
mike

brentowens@anonymised.com wrote:

No, parameters get cut off and default parameters are set.
The only ones that are changeable are the bounding box, and layers, and I think styles.

All the reflector does is return a regular WMS getMap request, with KML output, so you can just use that once, get the proper URL, and use that from then on with your specific parameters.
Its intent is just a quick and dirty way of getting data, with default parameters, into Google Earth.

Brent Owens
(The Open Planning Project)

mfrumin wrote:
  

something I'm not completely clear on -- for the whole kml_reflect thing, are
you supposed to be able to change the default parameters by tacking on more
GET params, eg:

http://localhost:8080/geoserver/wms/kml_reflect?layers=topp:states&KMScore=100&KMAttr=false

because when i add them onto the request, the WMS request inside the kml
file returned still has >
KMScore=30&KMAttr=true

thanks,
mike
  

2

I agree that kmscore and kmattr should be passed through, but the rest of the parameters shouldn't. It would make the kml reflector more complicated than it needs to be. If you start passing in the other parameters you essentially have the regular getMap request. So I would like the reflector to remain simple, and a starting point for figuring out how to get KML out of geoserver.

I will take a look into the kmscore and kmattr values and see that they get passed through, and set a jira for it.

Brent Owens
(The Open Planning Project)

Michael Frumin wrote:

I would think that these basic parameters that affect the way it works in GEarth, like KMScore and KMAttr, should be passed through. This still gets you the benefits of not having to worry about all the other crap (EPSG, VERSION, BBOX, etc. etc.) in a normal WMS request.

thanks,
mike

brentowens@anonymised.com wrote:

No, parameters get cut off and default parameters are set.
The only ones that are changeable are the bounding box, and layers, and I think styles.

All the reflector does is return a regular WMS getMap request, with KML output, so you can just use that once, get the proper URL, and use that from then on with your specific parameters.
Its intent is just a quick and dirty way of getting data, with default parameters, into Google Earth.

Brent Owens
(The Open Planning Project)

mfrumin wrote:

something I'm not completely clear on -- for the whole kml_reflect thing, are
you supposed to be able to change the default parameters by tacking on more
GET params, eg:

http://localhost:8080/geoserver/wms/kml_reflect?layers=topp:states&KMScore=100&KMAttr=false

because when i add them onto the request, the WMS request inside the kml
file returned still has >
KMScore=30&KMAttr=true

thanks,
mike
  

3

I wouldn't say it definitely makes things more complicated - the thing that's much nicer than a regular getmap request is it supplies defaults. But if you really want to change things, then let people over-ride.

Now, if it's a matter of having to over-ride each, then yeah, doing epsg over-rides is silly. But if it's easy to do it'd be better to just reflect everything by default, providing defaults if things aren't there.

C

Brent Owens wrote:

I agree that kmscore and kmattr should be passed through, but the rest of the parameters shouldn't. It would make the kml reflector more complicated than it needs to be. If you start passing in the other parameters you essentially have the regular getMap request. So I would like the reflector to remain simple, and a starting point for figuring out how to get KML out of geoserver.

I will take a look into the kmscore and kmattr values and see that they get passed through, and set a jira for it.

Brent Owens
(The Open Planning Project)

Michael Frumin wrote:

I would think that these basic parameters that affect the way it works in GEarth, like KMScore and KMAttr, should be passed through. This still gets you the benefits of not having to worry about all the other crap (EPSG, VERSION, BBOX, etc. etc.) in a normal WMS request.

thanks,
mike

brentowens@anonymised.com wrote:

No, parameters get cut off and default parameters are set.
The only ones that are changeable are the bounding box, and layers, and I think styles.

All the reflector does is return a regular WMS getMap request, with KML output, so you can just use that once, get the proper URL, and use that from then on with your specific parameters.
Its intent is just a quick and dirty way of getting data, with default parameters, into Google Earth.

Brent Owens
(The Open Planning Project)

mfrumin wrote:

something I'm not completely clear on -- for the whole kml_reflect thing, are
you supposed to be able to change the default parameters by tacking on more
GET params, eg:

http://localhost:8080/geoserver/wms/kml_reflect?layers=topp:states&KMScore=100&KMAttr=false

because when i add them onto the request, the WMS request inside the kml
file returned still has >
KMScore=30&KMAttr=true

thanks,
mike
  
!DSPAM:1003,45e5e13e245249771116852!

--
Chris Holmes
The Open Planning Project
http://topp.openplans.org