ThinkGeo.com    |     Documentation    |     Premium Support

14.5 and DrawingQuality

#1

Hi,

It seems that handling of DrawingQuality has been updated to 14.5 to be overlay specific. With previous versions we have had combinations like:

Overlay - HighSpeed
InMemoryFeatureLayer - HighSpeed
InMemoryFeatureLayer - Default

Is it now so that we need to split layers to different overlays if layers need to have different quality ?

Also I noticed that with new 14.5 HighSpeed quality is not the same compared to previous version. Is this correct observation ? Here is an example where on the left 14.4.5 both overlay/layer are HighSpeed and on the right 14.5 with overlay as HighSpeed.

image

It can be seen that text and outline quality is worse in 14.5.

Br, Simo

#2

Hi Simo,

You’re right.

  1. Skia (the rendering engine used by ThinkGeo) has moved away from the concept of High/Medium/Low quality levels, so we updated our API to align with that direction. The main reason is that a single “HighQuality” setting cannot produce optimal results across different types of maps.

  2. Instead, we now provide more fine-grained control over rendering quality:

  • For Vector rendering (your case): you can use TileOverlay.RenderingOptions to control anti-aliasing for Image, Vector, and Text individually.
  • For Map Tiles you can adjust the resampling algorithm.

By default, DrawingQuality.Standard enables anti-aliasing for Vector and Text, but disables it for Image. When set to HighSpeed , anti-aliasing is also disabled for Text and Vector, which reduces label quality—that’s the trade-off for better performance. In that sense, the newer behavior is more accurate and predictable. We’d recommend you to just leave it to DrawingQuality.Standard which should be good for most of the cases.

If you’re interested, you can find more details here:
https://docs.thinkgeo.com/products/thinkgeo-core/thinkgeo-raster-sampling-matrix/

Thanks,
Ben