# WPF

**URL:** https://community.thinkgeo.com/c/thinkgeo-ui-for-desktop/thinkgeo-ui-for-desktop-wpf/7.md

[Latest](https://community.thinkgeo.com/latest.md) · [Categories](https://community.thinkgeo.com/categories.md)

---

## [About the WPF category](https://community.thinkgeo.com/t/about-the-wpf-category/15)

<div class="topic-metadata">

**Author:** [@system](https://community.thinkgeo.com/u/system)\
**Replies:** 0\
**Last updated:** [March 22, 2016, 5:56am UTC](https://community.thinkgeo.com/t/about-the-wpf-category/15 "2016-03-22T05:56:08Z")

</div>

This is where you can discuss any questions or issues with the ThinkGeo UI Desktop control for WPF, both for .NET Framework and .NET Core. If you are new to ThinkGeo, check out the wiki where you can find a Quick Start …

---

## [OgcApiFeatureLayer gets stuck with slow network](https://community.thinkgeo.com/t/ogcapifeaturelayer-gets-stuck-with-slow-network/12496)

<div class="topic-metadata">

**Author:** [@Simo\_Karjalainen](https://community.thinkgeo.com/u/Simo_Karjalainen)\
**Replies:** 1\
**Last updated:** [October 30, 2026, 2:45pm UTC](https://community.thinkgeo.com/t/ogcapifeaturelayer-gets-stuck-with-slow-network/12496 "2026-10-30T14:45:51Z")

</div>

Hi, It seems that when using OgcApiFeatureLayer with slow network connection or if the server does not reply the whole application is freezed while OgcApiFeatureSource tries to get columns from server. After WebRequest …

---

## [File GDB shared-resource lifetime and finalizer crash](https://community.thinkgeo.com/t/file-gdb-shared-resource-lifetime-and-finalizer-crash/12495)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 3\
**Last updated:** [October 29, 2026, 2:59pm UTC](https://community.thinkgeo.com/t/file-gdb-shared-resource-lifetime-and-finalizer-crash/12495 "2026-10-29T14:59:10Z")

</div>

Hi ThinkGeo team, Separate FileGeoDatabaseFeatureSource instances pointing to the same database can interfere with each other’s native resource lifetime. We observed process termination with this finalizer exception: …

---

## [FeatureLayerTranslator translates a ZoomLevel's default styles even when it has CustomStyles (15.0.0-beta232)](https://community.thinkgeo.com/t/featurelayertranslator-translates-a-zoomlevels-default-styles-even-when-it-has-customstyles-15-0-0-beta232/12494)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 1\
**Last updated:** [October 22, 2026, 4:22pm UTC](https://community.thinkgeo.com/t/featurelayertranslator-translates-a-zoomlevels-default-styles-even-when-it-has-customstyles-15-0-0-beta232/12494 "2026-10-22T16:22:25Z")

</div>

Hi! In 15.0.0-beta232, FeatureLayerTranslator translates a zoom level’s DefaultAreaStyle/DefaultLineStyle/DefaultPointStyle/DefaultTextStyle alongside its CustomStyles. Classic drawing uses the defaults only when Custom…

---

## [Open issues after beta230](https://community.thinkgeo.com/t/open-issues-after-beta230/12493)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 1\
**Last updated:** [October 21, 2026, 3:27pm UTC](https://community.thinkgeo.com/t/open-issues-after-beta230/12493 "2026-10-21T15:27:28Z")

</div>

Hi Ben! We got a few new issues with the latest betas - here’s is an overview: Thank you for the composite WFS work in beta218/219; AGK now uses several component types, ReadUntilEmptyPage and the draw-scoped completio…

---

## [WFS composite features: resolved ATKIS geometry and spatial query limitations](https://community.thinkgeo.com/t/wfs-composite-features-resolved-atkis-geometry-and-spatial-query-limitations/12490)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 6\
**Last updated:** [October 13, 2026, 3:46am UTC](https://community.thinkgeo.com/t/wfs-composite-features-resolved-atkis-geometry-and-spatial-query-limitations/12490 "2026-10-13T03:46:07Z")

</div>

Hi ThinkGeo team, We need to display and query adv:AX\_Strasse from the public Bayern ATKIS WFS. It is a composite object: the street’s id and attributes belong to AX\_Strasse, while its geometry belongs to the objects…

---

## [Attribute-only reads and inconsistent query semantics](https://community.thinkgeo.com/t/attribute-only-reads-and-inconsistent-query-semantics/12486)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 7\
**Last updated:** [October 9, 2026, 3:41pm UTC](https://community.thinkgeo.com/t/attribute-only-reads-and-inconsistent-query-semantics/12486 "2026-10-09T15:41:49Z")

</div>

Hi ThinkGeo team, Our application matches business keys against feature attributes: it reads the id and two or three key columns of every feature in a layer, then fetches only the matching features by id. QueryTools.G…

---

## [GPU rendering (15.0.0-beta202): thin dark line along the centre of polygon outlines and lines, classic renders correctly](https://community.thinkgeo.com/t/gpu-rendering-15-0-0-beta202-thin-dark-line-along-the-centre-of-polygon-outlines-and-lines-classic-renders-correctly/12487)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 1\
**Last updated:** [October 5, 2026, 3:21pm UTC](https://community.thinkgeo.com/t/gpu-rendering-15-0-0-beta202-thin-dark-line-along-the-centre-of-polygon-outlines-and-lines-classic-renders-correctly/12487 "2026-10-05T15:21:49Z")

</div>

Environment ThinkGeo.Core / ThinkGeo.UI.Wpf / ThinkGeo.Gpu 15.0.0-beta202 .NET 8 WPF, Windows Styles translated with FeatureLayerTranslator.Translate(layer, source, source.TileMatrixSet.GetScales()) , added with new …

---

## [GPU mode: RequestMapRefresh calls MapView.RefreshAsync() from worker threads (unobserved InvalidOperationException), 15.0.0-beta197](https://community.thinkgeo.com/t/gpu-mode-requestmaprefresh-calls-mapview-refreshasync-from-worker-threads-unobserved-invalidoperationexception-15-0-0-beta197/12485)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 1\
**Last updated:** [October 3, 2026, 2:22pm UTC](https://community.thinkgeo.com/t/gpu-mode-requestmaprefresh-calls-mapview-refreshasync-from-worker-threads-unobserved-invalidoperationexception-15-0-0-beta197/12485 "2026-10-03T14:22:17Z")

</div>

Hi Team, With GpuBasemap enabled (ThinkGeo.UI.Wpf / ThinkGeo.Gpu 15.0.0-beta197), our log fills with unobserved task exceptions. They appear after we add a layer or toggle WMS/WFS layers. Dozens arrive in bursts wheneve…

---

## [Some highlights disappear when zooming in](https://community.thinkgeo.com/t/some-highlights-disappear-when-zooming-in/12475)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 17\
**Last updated:** [October 2, 2026, 10:15pm UTC](https://community.thinkgeo.com/t/some-highlights-disappear-when-zooming-in/12475 "2026-10-02T22:15:08Z")

</div>

Hi Ben, sorry it’s me again. We noticed that some highlights disappear when zooming in in the latest beta. I think you know our setup by now - if there’s anything else you need to debug this let me know! (GPU Render…

---

## [PdfGeoCanvas: clip from MapPrinterLayoutAsyncLayer stays active after drawing a layer with Opacity \< 1](https://community.thinkgeo.com/t/pdfgeocanvas-clip-from-mapprinterlayoutasynclayer-stays-active-after-drawing-a-layer-with-opacity-1/12484)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 1\
**Last updated:** [October 2, 2026, 8:53pm UTC](https://community.thinkgeo.com/t/pdfgeocanvas-clip-from-mapprinterlayoutasynclayer-stays-active-after-drawing-a-layer-with-opacity-1/12484 "2026-10-02T20:53:17Z")

</div>

Environment ThinkGeo.Core 15.0.0-beta197 (also present in beta191) .NET 10, Windows, PdfGeoCanvas with MapPrinterLayoutAsyncLayer in MapPrinterDrawingMode.Vector Summary We export a print layout to PDF: a page …

---

## [Fills and Labels stopped working in latest beta191 (GPU)](https://community.thinkgeo.com/t/fills-and-labels-stopped-working-in-latest-beta191-gpu/12483)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 6\
**Last updated:** [October 2, 2026, 8:41pm UTC](https://community.thinkgeo.com/t/fills-and-labels-stopped-working-in-latest-beta191-gpu/12483 "2026-10-02T20:41:37Z")

</div>

We found that our fills and labels dont show up anymore in the latest beta191 when switching to GPU. Here is a repro project. Translation produces the fill, outline and label layers without warnings. Offline inspection …

---

## [WFS 2.0: unqualified property names and silently ignored service errors in beta191](https://community.thinkgeo.com/t/wfs-2-0-unqualified-property-names-and-silently-ignored-service-errors-in-beta191/12482)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 5\
**Last updated:** [October 2, 2026, 12:30pm UTC](https://community.thinkgeo.com/t/wfs-2-0-unqualified-property-names-and-silently-ignored-service-errors-in-beta191/12482 "2026-10-02T12:30:01Z")

</div>

Hi Ben, I found two issues in WfsV2AsyncFeatureSource in ThinkGeo.Core 15.0.0-beta191 when requesting adv:AX\_Bahnstrecke from this public WFS: https://geoservices.bayern.de/wfs/v1/ogc\_atkis\_basisdlm.cgi The service u…

---

## [Layer transparency applies after layer rendered on zoom](https://community.thinkgeo.com/t/layer-transparency-applies-after-layer-rendered-on-zoom/12427)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 22\
**Last updated:** [October 1, 2026, 4:14pm UTC](https://community.thinkgeo.com/t/layer-transparency-applies-after-layer-rendered-on-zoom/12427 "2026-10-01T16:14:40Z")

</div>

Hi, when we set a transparency (50%) on a layer, on every zoom the transparency only applies after a few seconds. So, I zoom, it renders as 0% transparent, then rerenders as 50% transparent. Is this a known issue? I can…

---

## [Features cut off on tile border with GPU rendering](https://community.thinkgeo.com/t/features-cut-off-on-tile-border-with-gpu-rendering/12481)

<div class="topic-metadata">

**Author:** [@Simo\_Karjalainen](https://community.thinkgeo.com/u/Simo_Karjalainen)\
**Replies:** 3\
**Last updated:** [October 1, 2026, 1:19pm UTC](https://community.thinkgeo.com/t/features-cut-off-on-tile-border-with-gpu-rendering/12481 "2026-10-01T13:19:26Z")

</div>

Hi, When using OgcApiAsyncFeatureSource and InMemoryFeatureSource with GPU rendering it seems that features from InMemoryFeatureSource are cut off on tile border. On below image black circles are from OgcApiAsyncFeature…

---

## [Bug: GPU raster tiles from previous zooms remain visible](https://community.thinkgeo.com/t/bug-gpu-raster-tiles-from-previous-zooms-remain-visible/12479)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 5\
**Last updated:** [September 28, 2026, 11:24pm UTC](https://community.thinkgeo.com/t/bug-gpu-raster-tiles-from-previous-zooms-remain-visible/12479 "2026-09-28T23:24:21Z")

</div>

Observed in the WPF GPU map with a transparent WMS: after zooming and waiting for the new tiles to finish loading, symbols from previous zoom levels remain visible under the current tiles. Repeated zooming accumulates …

---

## [WMS/WFS Feedback / Wishes](https://community.thinkgeo.com/t/wms-wfs-feedback-wishes/12476)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 10\
**Last updated:** [September 28, 2026, 10:07pm UTC](https://community.thinkgeo.com/t/wms-wfs-feedback-wishes/12476 "2026-09-28T22:07:58Z")

</div>

Hi Ben, we recently moved WMS and WFS into our GPU workflow and noticed following friction points where we had to write workarounds or guards where we thought that ThinkGeo could natively handle this. Take this as a wis…

---

## [Multiple FeatureSourceVectorTileSources in MapStyle](https://community.thinkgeo.com/t/multiple-featuresourcevectortilesources-in-mapstyle/12478)

<div class="topic-metadata">

**Author:** [@Simo\_Karjalainen](https://community.thinkgeo.com/u/Simo_Karjalainen)\
**Replies:** 1\
**Last updated:** [September 28, 2026, 5:36pm UTC](https://community.thinkgeo.com/t/multiple-featuresourcevectortilesources-in-mapstyle/12478 "2026-09-28T17:36:21Z")

</div>

Hi, Is it possible to have multiple FeatureSourceVectorTileSources in one MapStyle ? I tried to use MapStyle::AddStyle() to add two FeatureSourceVectorTileSources but from some reason only the one which was added first …

---

## [WmsRasterTileSource/WmtsRasterTileSource and authentication](https://community.thinkgeo.com/t/wmsrastertilesource-wmtsrastertilesource-and-authentication/12470)

<div class="topic-metadata">

**Author:** [@Simo\_Karjalainen](https://community.thinkgeo.com/u/Simo_Karjalainen)\
**Replies:** 5\
**Last updated:** [September 24, 2026, 12:25am UTC](https://community.thinkgeo.com/t/wmsrastertilesource-wmtsrastertilesource-and-authentication/12470 "2026-09-24T00:25:00Z")

</div>

Hi, I have been checking those new classes for WMS and WMTS for GPU rendering. In our case we need to also support authentication for these services either with username/pwd or API key. Currently we have done it by hoo…

---

## [Highlights are sometimes cut off against transparent background](https://community.thinkgeo.com/t/highlights-are-sometimes-cut-off-against-transparent-background/12474)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 4\
**Last updated:** [September 24, 2026, 12:13am UTC](https://community.thinkgeo.com/t/highlights-are-sometimes-cut-off-against-transparent-background/12474 "2026-09-24T00:13:49Z")

</div>

the surrounding accent is a transparent circle with a blue outline, added as a separate PointStyle. This path does not set PointStyle.Mask. InMemoryFeatureLayer layer = new(); ZoomLevel zoomLevel = layer.ZoomLevel…

---

## [Transparent layers show tiles in latest beta (CPU only)](https://community.thinkgeo.com/t/transparent-layers-show-tiles-in-latest-beta-cpu-only/12473)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 1\
**Last updated:** [September 23, 2026, 9:36pm UTC](https://community.thinkgeo.com/t/transparent-layers-show-tiles-in-latest-beta-cpu-only/12473 "2026-09-23T21:36:57Z")

</div>

CPU Render On GPU Render it does not show the tiles. No thinkgeo debugging activated.

---

## [InMemoryFeatureLayer.Columns.Add() is silently discarded — contradicts documented usage](https://community.thinkgeo.com/t/inmemoryfeaturelayer-columns-add-is-silently-discarded-contradicts-documented-usage/12471)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 3\
**Last updated:** [September 23, 2026, 2:02pm UTC](https://community.thinkgeo.com/t/inmemoryfeaturelayer-columns-add-is-silently-discarded-contradicts-documented-usage/12471 "2026-09-23T14:02:34Z")

</div>

Version: ThinkGeo.Core 15.0.0-beta163 (also reproduced on 15.0.0-beta001 - appears to affect the entire 15.0 beta line) Summary Columns added via InMemoryFeatureLayer.Columns never reach the feature source. The Add() c…

---

## [ThinkGeo v15 beta160: individual GPU tiles flicker or disappear during zoom](https://community.thinkgeo.com/t/thinkgeo-v15-beta160-individual-gpu-tiles-flicker-or-disappear-during-zoom/12469)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 4\
**Last updated:** [September 22, 2026, 10:17pm UTC](https://community.thinkgeo.com/t/thinkgeo-v15-beta160-individual-gpu-tiles-flicker-or-disappear-during-zoom/12469 "2026-09-22T22:17:22Z")

</div>

We are seeing individual tiles flash or disappear while zooming with GPU rendering enabled. The affected map contains shapefile layers only. A short GIF and the GPU log are attached. We noticed this after updating to be…

---

## [WfsV2FeatureLayer vs WfsV2AsyncLayer](https://community.thinkgeo.com/t/wfsv2featurelayer-vs-wfsv2asynclayer/12449)

<div class="topic-metadata">

**Author:** [@Simo\_Karjalainen](https://community.thinkgeo.com/u/Simo_Karjalainen)\
**Replies:** 7\
**Last updated:** [September 22, 2026, 8:15pm UTC](https://community.thinkgeo.com/t/wfsv2featurelayer-vs-wfsv2asynclayer/12449 "2026-09-22T20:15:21Z")

</div>

Hi, We have been using WfsV2FeatureLayer for a while but now it’s marked as obsolete and WfsV2AsyncLayer should be used instead. There are couple of problems related to this change from your POV. It seems that WfsV2…

---

## [V15 beta160 follow-up: remaining GPU style parity, source lifecycle, WFS V2 and WMS gaps](https://community.thinkgeo.com/t/v15-beta160-follow-up-remaining-gpu-style-parity-source-lifecycle-wfs-v2-and-wms-gaps/12468)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 1\
**Last updated:** [September 21, 2026, 10:20pm UTC](https://community.thinkgeo.com/t/v15-beta160-follow-up-remaining-gpu-style-parity-source-lifecycle-wfs-v2-and-wms-gaps/12468 "2026-09-21T22:20:24Z")

</div>

Thanks for the beta155–160 fixes. We have updated our integration and removed the workarounds covered by those changes. Our application combines shapefiles, database feature layers and rasters. Users frequently edit sym…

---

## [Feature request: label opacity independent of Layer.Opacity (classic and GPU)](https://community.thinkgeo.com/t/feature-request-label-opacity-independent-of-layer-opacity-classic-and-gpu/12464)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 4\
**Last updated:** [September 21, 2026, 3:37pm UTC](https://community.thinkgeo.com/t/feature-request-label-opacity-independent-of-layer-opacity-classic-and-gpu/12464 "2026-09-21T15:37:02Z")

</div>

When a FeatureLayer is see-through ( Opacity below 1), its labels become see-through too, in both renderers. Users often set a layer to 50–70 % so the base map shows through, but they still want readable labels. Classic…

---

## [GenerateTileCacheAsync: MaxConcurrency has almost no effect — rendering is serialized by a per-layer lock](https://community.thinkgeo.com/t/generatetilecacheasync-maxconcurrency-has-almost-no-effect-rendering-is-serialized-by-a-per-layer-lock/12447)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 3\
**Last updated:** [September 19, 2026, 8:48pm UTC](https://community.thinkgeo.com/t/generatetilecacheasync-maxconcurrency-has-almost-no-effect-rendering-is-serialized-by-a-per-layer-lock/12447 "2026-09-19T20:48:04Z")

</div>

Package: ThinkGeo.Core 15.0.0-beta136 (also ThinkGeo.UI.Wpf / Gpu / Gdal / SqlServer / PostgreSql / FileGeoDatabase 15.0.0-beta136) Platform: .NET 10, WPF, win-x64 API: LayerBase.GenerateTileCacheAsync(...) with TileCa…

---

## [WPF beta 147: bad performance GPU render / lag](https://community.thinkgeo.com/t/wpf-beta-147-bad-performance-gpu-render-lag/12456)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 9\
**Last updated:** [September 19, 2026, 7:43pm UTC](https://community.thinkgeo.com/t/wpf-beta-147-bad-performance-gpu-render-lag/12456 "2026-09-19T19:43:26Z")

</div>

Hi Ben, I’m back We are getting terrible performance from dragging a map with highlights: GPU: CPU: As you can see GPU is rubberbanding and generally way slower. With beta148, the background map pans smoothly…

---

## [Classic renderer and data sources: five small gaps](https://community.thinkgeo.com/t/classic-renderer-and-data-sources-five-small-gaps/12466)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 2\
**Last updated:** [September 19, 2026, 7:11pm UTC](https://community.thinkgeo.com/t/classic-renderer-and-data-sources-five-small-gaps/12466 "2026-09-19T19:11:46Z")

</div>

We use ThinkGeo.Core / UI.Wpf 15.0.0-beta154 in a WPF desktop GIS. These are gaps in the classic (CPU) renderer and the data readers. We have a workaround for each, but they cost us code we would rather not keep. 1. Sha…

---

## [Performance: see-through layers encode a PNG per tile](https://community.thinkgeo.com/t/performance-see-through-layers-encode-a-png-per-tile/12465)

<div class="topic-metadata">

**Author:** [@Julian\_Thoms](https://community.thinkgeo.com/u/Julian_Thoms)\
**Replies:** 1\
**Last updated:** [September 19, 2026, 2:35am UTC](https://community.thinkgeo.com/t/performance-see-through-layers-encode-a-png-per-tile/12465 "2026-09-19T02:35:57Z")

</div>

In ThinkGeo.Core 15.0.0-beta154, Layer.DrawWithColorTransformation (used for every layer with Opacity \< 1 ) renders the layer offscreen, applies the opacity into a new bitmap, and then calls GetImageBytes() followed by n…

[Next page](https://community.thinkgeo.com/c/thinkgeo-ui-for-desktop/thinkgeo-ui-for-desktop-wpf/7.md?page=1)
