GeoServer GeoWebCache produces incomplete or partial tile cache Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?GeoWebCache WMTS always replacing tiles in cacheWMS Request not served to OpenLayers 2 by GeoWebCache off GeoServer?Can I use GeoWebCache with GeoServer Layers which have different native and declared SRS?Can I create a TMS layer on geoserver or geowebcacheHow to cache Geowebcache tiles from applicationsGeoserver set the Geowebcache Max Cache LevelGeoserver GeoWebCache caches tiles of incomplete layersGeoWebCache, GeoServer and Apache Architecturegeowebcache-miss-reason:not a tile layerViewing GeoServer tile layers in QGIS through WMS
How to tell that you are a giant?
What is the longest distance a player character can jump in one leap?
Is there any way for the UK Prime Minister to make a motion directly dependent on Government confidence?
Most bit efficient text communication method?
Declining "dulcis" in context
What's the meaning of "fortified infraction restraint"?
If my PI received research grants from a company to be able to pay my postdoc salary, did I have a potential conflict interest too?
What does this Jacques Hadamard quote mean?
Crossing US/Canada Border for less than 24 hours
Is it ethical to give a final exam after the professor has quit before teaching the remaining chapters of the course?
Would "destroying" Wurmcoil Engine prevent its tokens from being created?
How to react to hostile behavior from a senior developer?
Is there a kind of relay only consumes power when switching?
Fundamental Solution of the Pell Equation
How do I stop a creek from eroding my steep embankment?
Why are the trig functions versine, haversine, exsecant, etc, rarely used in modern mathematics?
An adverb for when you're not exaggerating
How do pianists reach extremely loud dynamics?
First console to have temporary backward compatibility
Wu formula for manifolds with boundary
Amount of permutations on an NxNxN Rubik's Cube
Compare a given version number in the form major.minor.build.patch and see if one is less than the other
What causes the direction of lightning flashes?
Is "Reachable Object" really an NP-complete problem?
GeoServer GeoWebCache produces incomplete or partial tile cache
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?GeoWebCache WMTS always replacing tiles in cacheWMS Request not served to OpenLayers 2 by GeoWebCache off GeoServer?Can I use GeoWebCache with GeoServer Layers which have different native and declared SRS?Can I create a TMS layer on geoserver or geowebcacheHow to cache Geowebcache tiles from applicationsGeoserver set the Geowebcache Max Cache LevelGeoserver GeoWebCache caches tiles of incomplete layersGeoWebCache, GeoServer and Apache Architecturegeowebcache-miss-reason:not a tile layerViewing GeoServer tile layers in QGIS through WMS
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I have looked at previous threads regarding this topic, but did not find the exact problems described - but they might be related - in short:
- I have the new GeoServer 2.15.0 and configured the GeoWebCache for the WMS service
- I have a layer from a PostGIS source with 6 million points
- I have configured a GEOWEBCACHE_CACHE_DIR env variable set to a path which is accessible for Geoserver
- I have a webapp requesting a WMS layers in a TILED fashin
- GeoServer creates tiles in the cache for rendering the map with each layer)
- All sent images (to the client) of my background layer (GeoTIFF) are cached and get served from there
Now the problem:
My layer with the many points gets only partially cached, even GeoServer renders them completely and serves the client - but it only saves some of the tiles to the cache. I also have the same problem with pre-seeding my layer. It produces the tiles, but not all.
Purple (=files sent to client), Yellow (=tiles actually getting cached)
My setup proves to be working. Caching on demand (when a client requests the tiles for the first time) and pre-seeding work. But in both cases GeoWebCache reproducibly does not cache certain tiles. Also when setting a large enough and larger extent for the pre-seeding, I end up with the same number of tiles being cached. The tiles also render fast enough in the client, so I'm sure this has nothing to do with a timeout.
The log shows me the following...
geoserver | 10 Mar 20:33:02 WARN [lite.gridcoverage2d] - Could not
reduce the grid geometry inside the valid area bounds:
ReferencedEnvelope[-2.147483647E9 : 2.147483647E9, -85.0 : 85.0]
geoserver | Grid geometry isGridGeometry2D[GridEnvelope2D[267..581,
0..4], PARAM_MT["Affine", geoserver | PARAMETER["num_row", 3], geoserver | PARAMETER["num_col", 3], geoserver |
PARAMETER["elt_0_0", 8.996714848883048], geoserver |
PARAMETER["elt_0_2", 172421.68534038262], geoserver |
PARAMETER["elt_1_1", -9.48768472906404], geoserver |
PARAMETER["elt_1_2", 21728.98232072473]]]
...for the tiles that cannot be cached. I checked now again the layer configuration and noted that the native extent (EPSG:900913/3857) doesn't match in the layer settings and in the GeoWebCache seed dialog. It seems, that the GeoWebCache treats only a smaller extent as valid. Both layer extent values come from the same PostGIS layer. I use an out of the box geoserver running on a docker image.
Is this a misconfiguration by me, or maybe a bug in GeoWebCache?
postgis geoserver wms cache
add a comment |
I have looked at previous threads regarding this topic, but did not find the exact problems described - but they might be related - in short:
- I have the new GeoServer 2.15.0 and configured the GeoWebCache for the WMS service
- I have a layer from a PostGIS source with 6 million points
- I have configured a GEOWEBCACHE_CACHE_DIR env variable set to a path which is accessible for Geoserver
- I have a webapp requesting a WMS layers in a TILED fashin
- GeoServer creates tiles in the cache for rendering the map with each layer)
- All sent images (to the client) of my background layer (GeoTIFF) are cached and get served from there
Now the problem:
My layer with the many points gets only partially cached, even GeoServer renders them completely and serves the client - but it only saves some of the tiles to the cache. I also have the same problem with pre-seeding my layer. It produces the tiles, but not all.
Purple (=files sent to client), Yellow (=tiles actually getting cached)
My setup proves to be working. Caching on demand (when a client requests the tiles for the first time) and pre-seeding work. But in both cases GeoWebCache reproducibly does not cache certain tiles. Also when setting a large enough and larger extent for the pre-seeding, I end up with the same number of tiles being cached. The tiles also render fast enough in the client, so I'm sure this has nothing to do with a timeout.
The log shows me the following...
geoserver | 10 Mar 20:33:02 WARN [lite.gridcoverage2d] - Could not
reduce the grid geometry inside the valid area bounds:
ReferencedEnvelope[-2.147483647E9 : 2.147483647E9, -85.0 : 85.0]
geoserver | Grid geometry isGridGeometry2D[GridEnvelope2D[267..581,
0..4], PARAM_MT["Affine", geoserver | PARAMETER["num_row", 3], geoserver | PARAMETER["num_col", 3], geoserver |
PARAMETER["elt_0_0", 8.996714848883048], geoserver |
PARAMETER["elt_0_2", 172421.68534038262], geoserver |
PARAMETER["elt_1_1", -9.48768472906404], geoserver |
PARAMETER["elt_1_2", 21728.98232072473]]]
...for the tiles that cannot be cached. I checked now again the layer configuration and noted that the native extent (EPSG:900913/3857) doesn't match in the layer settings and in the GeoWebCache seed dialog. It seems, that the GeoWebCache treats only a smaller extent as valid. Both layer extent values come from the same PostGIS layer. I use an out of the box geoserver running on a docker image.
Is this a misconfiguration by me, or maybe a bug in GeoWebCache?
postgis geoserver wms cache
what do the log files say? Also using "tiled" wms is not a good plan use WMTS or TMS to make sure GWC matches the tile boundaries
– Ian Turton♦
Mar 10 at 12:05
Added more details with log below. I have already tried WMTS, but that didn't change anything on the observed behaviour.
– geotom
Mar 10 at 21:02
add a comment |
I have looked at previous threads regarding this topic, but did not find the exact problems described - but they might be related - in short:
- I have the new GeoServer 2.15.0 and configured the GeoWebCache for the WMS service
- I have a layer from a PostGIS source with 6 million points
- I have configured a GEOWEBCACHE_CACHE_DIR env variable set to a path which is accessible for Geoserver
- I have a webapp requesting a WMS layers in a TILED fashin
- GeoServer creates tiles in the cache for rendering the map with each layer)
- All sent images (to the client) of my background layer (GeoTIFF) are cached and get served from there
Now the problem:
My layer with the many points gets only partially cached, even GeoServer renders them completely and serves the client - but it only saves some of the tiles to the cache. I also have the same problem with pre-seeding my layer. It produces the tiles, but not all.
Purple (=files sent to client), Yellow (=tiles actually getting cached)
My setup proves to be working. Caching on demand (when a client requests the tiles for the first time) and pre-seeding work. But in both cases GeoWebCache reproducibly does not cache certain tiles. Also when setting a large enough and larger extent for the pre-seeding, I end up with the same number of tiles being cached. The tiles also render fast enough in the client, so I'm sure this has nothing to do with a timeout.
The log shows me the following...
geoserver | 10 Mar 20:33:02 WARN [lite.gridcoverage2d] - Could not
reduce the grid geometry inside the valid area bounds:
ReferencedEnvelope[-2.147483647E9 : 2.147483647E9, -85.0 : 85.0]
geoserver | Grid geometry isGridGeometry2D[GridEnvelope2D[267..581,
0..4], PARAM_MT["Affine", geoserver | PARAMETER["num_row", 3], geoserver | PARAMETER["num_col", 3], geoserver |
PARAMETER["elt_0_0", 8.996714848883048], geoserver |
PARAMETER["elt_0_2", 172421.68534038262], geoserver |
PARAMETER["elt_1_1", -9.48768472906404], geoserver |
PARAMETER["elt_1_2", 21728.98232072473]]]
...for the tiles that cannot be cached. I checked now again the layer configuration and noted that the native extent (EPSG:900913/3857) doesn't match in the layer settings and in the GeoWebCache seed dialog. It seems, that the GeoWebCache treats only a smaller extent as valid. Both layer extent values come from the same PostGIS layer. I use an out of the box geoserver running on a docker image.
Is this a misconfiguration by me, or maybe a bug in GeoWebCache?
postgis geoserver wms cache
I have looked at previous threads regarding this topic, but did not find the exact problems described - but they might be related - in short:
- I have the new GeoServer 2.15.0 and configured the GeoWebCache for the WMS service
- I have a layer from a PostGIS source with 6 million points
- I have configured a GEOWEBCACHE_CACHE_DIR env variable set to a path which is accessible for Geoserver
- I have a webapp requesting a WMS layers in a TILED fashin
- GeoServer creates tiles in the cache for rendering the map with each layer)
- All sent images (to the client) of my background layer (GeoTIFF) are cached and get served from there
Now the problem:
My layer with the many points gets only partially cached, even GeoServer renders them completely and serves the client - but it only saves some of the tiles to the cache. I also have the same problem with pre-seeding my layer. It produces the tiles, but not all.
Purple (=files sent to client), Yellow (=tiles actually getting cached)
My setup proves to be working. Caching on demand (when a client requests the tiles for the first time) and pre-seeding work. But in both cases GeoWebCache reproducibly does not cache certain tiles. Also when setting a large enough and larger extent for the pre-seeding, I end up with the same number of tiles being cached. The tiles also render fast enough in the client, so I'm sure this has nothing to do with a timeout.
The log shows me the following...
geoserver | 10 Mar 20:33:02 WARN [lite.gridcoverage2d] - Could not
reduce the grid geometry inside the valid area bounds:
ReferencedEnvelope[-2.147483647E9 : 2.147483647E9, -85.0 : 85.0]
geoserver | Grid geometry isGridGeometry2D[GridEnvelope2D[267..581,
0..4], PARAM_MT["Affine", geoserver | PARAMETER["num_row", 3], geoserver | PARAMETER["num_col", 3], geoserver |
PARAMETER["elt_0_0", 8.996714848883048], geoserver |
PARAMETER["elt_0_2", 172421.68534038262], geoserver |
PARAMETER["elt_1_1", -9.48768472906404], geoserver |
PARAMETER["elt_1_2", 21728.98232072473]]]
...for the tiles that cannot be cached. I checked now again the layer configuration and noted that the native extent (EPSG:900913/3857) doesn't match in the layer settings and in the GeoWebCache seed dialog. It seems, that the GeoWebCache treats only a smaller extent as valid. Both layer extent values come from the same PostGIS layer. I use an out of the box geoserver running on a docker image.
Is this a misconfiguration by me, or maybe a bug in GeoWebCache?
postgis geoserver wms cache
postgis geoserver wms cache
edited Mar 11 at 9:20
Ian Turton♦
50.3k548119
50.3k548119
asked Mar 9 at 20:46
geotomgeotom
513
513
what do the log files say? Also using "tiled" wms is not a good plan use WMTS or TMS to make sure GWC matches the tile boundaries
– Ian Turton♦
Mar 10 at 12:05
Added more details with log below. I have already tried WMTS, but that didn't change anything on the observed behaviour.
– geotom
Mar 10 at 21:02
add a comment |
what do the log files say? Also using "tiled" wms is not a good plan use WMTS or TMS to make sure GWC matches the tile boundaries
– Ian Turton♦
Mar 10 at 12:05
Added more details with log below. I have already tried WMTS, but that didn't change anything on the observed behaviour.
– geotom
Mar 10 at 21:02
what do the log files say? Also using "tiled" wms is not a good plan use WMTS or TMS to make sure GWC matches the tile boundaries
– Ian Turton♦
Mar 10 at 12:05
what do the log files say? Also using "tiled" wms is not a good plan use WMTS or TMS to make sure GWC matches the tile boundaries
– Ian Turton♦
Mar 10 at 12:05
Added more details with log below. I have already tried WMTS, but that didn't change anything on the observed behaviour.
– geotom
Mar 10 at 21:02
Added more details with log below. I have already tried WMTS, but that didn't change anything on the observed behaviour.
– geotom
Mar 10 at 21:02
add a comment |
1 Answer
1
active
oldest
votes
I deleted the layer and re-added it. Now it seems also GeoWebCache properly detects the real extent and does the caching for he whole of the dataset. A strange problem, that cost me a few hours...and no clue why.
For everyone else with a smiliar problem of partially cached layers. Try to readd the layer and check if GeoWebCache and Geoserver have the same layer extent configured.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "79"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f314941%2fgeoserver-geowebcache-produces-incomplete-or-partial-tile-cache%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I deleted the layer and re-added it. Now it seems also GeoWebCache properly detects the real extent and does the caching for he whole of the dataset. A strange problem, that cost me a few hours...and no clue why.
For everyone else with a smiliar problem of partially cached layers. Try to readd the layer and check if GeoWebCache and Geoserver have the same layer extent configured.
add a comment |
I deleted the layer and re-added it. Now it seems also GeoWebCache properly detects the real extent and does the caching for he whole of the dataset. A strange problem, that cost me a few hours...and no clue why.
For everyone else with a smiliar problem of partially cached layers. Try to readd the layer and check if GeoWebCache and Geoserver have the same layer extent configured.
add a comment |
I deleted the layer and re-added it. Now it seems also GeoWebCache properly detects the real extent and does the caching for he whole of the dataset. A strange problem, that cost me a few hours...and no clue why.
For everyone else with a smiliar problem of partially cached layers. Try to readd the layer and check if GeoWebCache and Geoserver have the same layer extent configured.
I deleted the layer and re-added it. Now it seems also GeoWebCache properly detects the real extent and does the caching for he whole of the dataset. A strange problem, that cost me a few hours...and no clue why.
For everyone else with a smiliar problem of partially cached layers. Try to readd the layer and check if GeoWebCache and Geoserver have the same layer extent configured.
answered Mar 10 at 21:25
geotomgeotom
513
513
add a comment |
add a comment |
Thanks for contributing an answer to Geographic Information Systems Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f314941%2fgeoserver-geowebcache-produces-incomplete-or-partial-tile-cache%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
what do the log files say? Also using "tiled" wms is not a good plan use WMTS or TMS to make sure GWC matches the tile boundaries
– Ian Turton♦
Mar 10 at 12:05
Added more details with log below. I have already tried WMTS, but that didn't change anything on the observed behaviour.
– geotom
Mar 10 at 21:02