and if I set in GeoServer “Enable direct integration with GeoServer WMS”,
does I'm using catching or not?
I ask it because I've read that to be able to apply catching, We need to
define a grid and its tile size and projection parameters. Furthermore, I'm
not using “classic” tile size (256*256px) and If I go to the list of the
cached layers, all have 0.0k.
Other thing : if I quit the tilesorigin parameters in OpenLayers it doesn't
change anything, my script works.
2) I want to use meta-tilling to visualize my layers because I don't want
labels repetition:
I know that “GeoServer, if being used as the backend, will ignore the
directive for requests that are not 256x256 pixels”. So, in my case, it's
impossible to use meta-tilling via GeoServer because of my size tile?
It's possible to use GeoWebCache to do meta-tilles? Is it compatible with
tile size different of 256*256 px?
If yes, that's why I we you generally set this (GeoServer) to false to
prevent the backend from metatiling the metatiles? In this case, how to set
GeoServer meta-tilling to false?
3) I saw that in Openlayers we can pass to GeoServer the parameters tiled:
“yes” to avoid labels repetition. This parameters is linking to the
meta-tilling in GeoServer? I suppose that in my case it's impossible to use
it because of my size tile?
4) When we turn off the computer, what happen with the tiles cached? They
are eliminated?
1) Yes ... setting "tiled: true" & "direct integration with GeoServer WMS"
combination does use caching.. You should enable "disk quota" in GeoServer
and then you can go back to see the amount of disk space used for caching.
4) Cached tiles remain intact even if you turn off your computer.
I did some tests and this is my conclusions:
If I put tiled = true in OpenLayers script and set direct integration with
GeoServer WMS and without create a new grid:
- with parameters by default (eg 4326 or 3857 and tile sixe of 256px, it
create a cache and I can confirm it in the cached layers list).
-- If I change the parameters (projection and / or tileSize), GeoWebCache
doesn't catch my layers because in the cached layers list, the layer size is
= 0,0k.
GeoServer forwards the WMS requests to GeoWebCache only if ‘tiled=true’.
Then GeoWebCache creates tiles in conformance to the settings provided in the ‘Tile Caching’
section of the ‘Edit Layer’ page. Here you can set also the metatiling (‘Metatiling factor’)
and the Gridset to use for your layer’s tile cache. So each WMS request must to respect these settings
(tiled=true, bbox, srs, tile size and so on) to ensure that the cache is created.
If you need to use a tile size different from 256*256 px, I think you have to configure a new
Gridset for that.
I did some tests and this is my conclusions:
If I put tiled = true in OpenLayers script and set direct integration with
GeoServer WMS and without create a new grid:
with parameters by default (eg 4326 or 3857 and tile sixe of 256px, it
create a cache and I can confirm it in the cached layers list).
– If I change the parameters (projection and / or tileSize), GeoWebCache
doesn’t catch my layers because in the cached layers list, the layer size is
= 0,0k.
Sent from the GeoServer - User mailing list archive at Nabble.com.
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don’t have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk