I’m a little confused about how to correctly, or most effectively, use different caching options you are offering.
I think the basic use case for WMS/WMTS services is to have a WmsOverlay or WmtsOverlay. These both offer TileCache property and I have been using those for caching. But then again WmtsOverlay has also ProjectedTileCache property, that is not present on WmsOverlay. What’s the difference and what’s the recommended use?
I expected to find WfsOverlay for WFS services but that wasn’t the case. Instead I need to create a LayerOverlay and then add WfsFeatureLayer into that overlay.
I think with this approach overlay might cache invalid tiles in case of network/service error? This happens with both Wms- and Wmts layers when attached to LayerOverlay.
Anyway, LayerOverlay has the TileCache property but then again WfsFeatureLayer has GeoCache property in it’s FeatureSource. Can I use these both at the same time? What’s the recommended use? Is there any another cache type for vector sources (vector cache)?
- ThinkGeo Cloud offering
Both ThinkGeoCloudRasterMapsOverlay and ThinkGeoCloudVectorMapsOverlay have TileCache property. But on top of that ThinkGeoCloudVectorMapsOverlay has also VectorTileCache. I have been using only VectorTileCache but why there’s two caching properties? What’s the recommended use?
When using any web map service based overlay it seems impossible to get the correct bounding box when calling GetBoundingBox() method. Now I need to fetch the service capabilities and parse bounding box for each layer service is offering as it seems that overlay, connected to given service, is unable to provide the BB. Feature or bug? Any workarounds or recommendations?
WMS/WMTS/WFS services might offer content in multiple different coordinate systems. Is there any reasonable way to determine correct MapUnit for WPF MapView (meter, decimal degree) other than trying to figure it out from given EPSG/SRID’s projection string?
Thanks a bunch!