Help Needed: WMTS Support & GWC Optimization in GeoNode 4.4 #13326
Replies: 4 comments 7 replies
-
WMTS map layer configuration for datasets is not currently supported in GeoNode. However, I think that with a properly configured cache (GWC) in front of your WMS layer, you should be ok. |
Beta Was this translation helpful? Give feedback.
-
Hi Giovanni,
Thanks for the info. This is what I'm getting
[image: image.png]
I'm not sure why it says the request does not align to the grid? What could
be the reasons and how can I address it?
Thanks,
Ibrahim
…On Wed, Jul 2, 2025 at 1:15 PM Giovanni Allegri ***@***.***> wrote:
Hi @IbrahimMalik2002 <https://github.com/IbrahimMalik2002>.
WMTS map layer configuration for datasets is not currently supported in
GeoNode.
If you really want WMTS an option would adding the layer directly from the
Geoserver (or any other WMTS source) using the map tool inside the map
viewer (see Fig.1 below).
However, I think that with a properly configured cache (GWC) in front of
your WMS layer, you should be ok.
I invite you to take a look at the GWC headers that are returned for each
request (see Fig.2) and verify that you get HITs as expected.
In case you get a MISS the header will also tell the reason why it
couldn't use the cache
Fig.1
image.png (view on web)
<https://github.com/user-attachments/assets/d57437fc-a561-495c-b24b-977e600d51f6>
Fig.2
image.png (view on web)
<https://github.com/user-attachments/assets/d28f2ec4-82f0-4614-9bfc-003cc945a70a>
—
Reply to this email directly, view it on GitHub
<#13326 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A444SN7RUWWD6F2HBR6LZUL3GOIJVAVCNFSM6AAAAACATFIZGOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNRTG44DINI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Sorry, not sure why. I've attached it to this email.
…On Wed, Jul 2, 2025 at 2:21 PM Giovanni Allegri ***@***.***> wrote:
I cannot see the image
—
Reply to this email directly, view it on GitHub
<#13326 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A444SN4VVMAFBN5DREOJYK33GOQC5AVCNFSM6AAAAACATFIZGOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNRTHA3DKOA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Ok so now my requests are hitting the GWC and relevant tiles are being fetched. Although, I am now facing a new issue, this one is now resolved after I upgraded my geonode to the latest version. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone!
I'm working with GeoNode 4.4, and I have some questions regarding tile caching and performance optimization.
Current Setup:
I confirmed from the GWC logs that tiles are being served from cache (file sizes, response times, etc. - see the attached image

)
Problem:
Despite this, map loading is still slower than expected. I suspect that while some tiles are served from GWC, others are still being rendered on the fly.
What I Need:
WMTS Access in GeoNode:
Tile Request Optimization:
Is there a way to restrict GeoNode to only request tiles within the current BBOX at the current zoom level, instead of extra surrounding tiles?
This would greatly help reduce unnecessary tile requests.
WMTS vs Tiled WMS:
In real-world performance, is WMTS actually faster than WMS with TILED=true?
If performance is similar, is enabling WMTS worth the effort?
Any insights, suggestions, or experiences would be really helpful!
Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions