How to enable persistent caching on WMTS capabilities URL
See original GitHub issueHi,
We are using the WmtsParser to recover available WMTS Tile Sources. However it seems impossible to enable persistent caching on a selected tilesource, since you can’t provide a persitent cache object with the parser.
var tileSources = WmtsParser.Parse(httpClient.GetStreamAsync(addr).Result);
Do you have any advice on getting this done?
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Caching defaults — GeoServer 2.21.x User Manual
Enables the Web Map Tiled Service (WMTS) endpoint in GeoWebCache. When this setting is enabled, GeoWebCache will respond to its own WMTS endpoint:...
Read more >GeoServer not caching tiles when using WMS with Direct ...
I opted to call the cache using WMTS. If the tiles are not in the cache then GeoWebCache generates them on the fly...
Read more >Tiles are not caching after enabling Tile cache for WMTS in ...
1. Check if the specified folder has writing permission. · 2. Clear the cache and try to restart the machine · 3. If...
Read more >WMTS Capabilities (Map Service)—ArcGIS REST APIs
An individual WMTS Capabilities (Service Metadata) resource allows WMTS clients to retrieve service metadata for this tiled map service.
Read more >How to enable persistent object caching?
You can enable Object Caching in Performance>General settings. Please check the screenshot. However, I would advise using Redis as a caching method for...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Simply made PersistentCache settable. Had to remove the internal TileProvider. Released as 2.2.0.
I just tried to envision how that would work. One thing that you see a lot in .net core is build options like these. I thought they could maybe be used here. That would be possible but this specific case makes it a step harder because you have to find a solution to deal with multiple tilesources. This will be hard to understand for users. So I now think we should just make the PersistenCache settable. I have to think about removing the TileProvider from the HttpTileSource.