How the heck did I miss that in the documentation! Too much focus on the
REST API maybe!
Facepalms as well!
Thanks all for the info.
On Sun, Apr 15, 2012 at 9:45 PM, Adon Metcalfe wrote:
> Facepalm - that's much better, also has great docs =)
>
> http://docs.geoserver.org/latest/en/user/tutoria
Facepalm - that's much better, also has great docs =)
http://docs.geoserver.org/latest/en/user/tutorials/wmsreflector.html
On Mon, Apr 16, 2012 at 9:37 AM, Gabriel Roldan wrote:
> On Sun, Apr 15, 2012 at 10:23 PM, Adon Metcalfe
> wrote:
> > I had the same problem and ended up crafting a WMS Ge
On Sun, Apr 15, 2012 at 10:23 PM, Adon Metcalfe wrote:
> I had the same problem and ended up crafting a WMS GetMap request based on
> the bounding box retreived via REST, with a proportional size, e.g.
>
> GET /geoserver/rest/workspaces/myworkspace/featuretypes/mylayer.json
>
> """
> 'latLonBoundi
I had the same problem and ended up crafting a WMS GetMap request based on
the bounding box retreived via REST, with a proportional size, e.g.
GET /geoserver/rest/workspaces/myworkspace/featuretypes/mylayer.json
"""
'latLonBoundingBox': {u'crs': u'EPSG:4326',
u'maxx': 129.00192885,
u'maxy':
List,
I am using the REST API to create a layer picker (using openlayers) which
programmatically displays the the available wms layers in a given
workspace. In this way users can explore the layer metadata prior to
adding them to the map and thereby reducing load time so lots of layers are
not lo
On Sun, Apr 15, 2012 at 9:53 PM, Gabriel Roldan wrote:
> apparently we lost the ability of logging the full wms request with
> the stack trace. I'll file a bug report about that.
> But in any case it looks more like the client is misconfigured or
> trying to use the WMS-C end point as a pure WMS.
apparently we lost the ability of logging the full wms request with
the stack trace. I'll file a bug report about that.
But in any case it looks more like the client is misconfigured or
trying to use the WMS-C end point as a pure WMS.
Check out the list of advertised resolutions for the two gridset
G'Day all,
We started seeing this message popping up in the logs after a big
session of adding new data to our GeoServer 2.1.2 installation,
Has anyone seen similar or have a clue where to track this down?
575 ERROR [geowebcache.GeoWebCacheDispatcher] - Requested horizontal
resolution: 0.11
