Ticket #3616 (closed enhancement: fixed)

Opened 2 years ago

Last modified 2 years ago

ability to use alternative renderers

Reported by: assefa Owned by: tbonfort
Priority: normal Milestone:
Component: Renderer API Version: unspecified
Severity: normal Keywords:
Cc:

Description

The first case would be able to use an agg renderer for raster layers in the kml driver.

Attachments

bug_3616.patch Download (2.4 KB) - added by assefa 2 years ago.

Change History

Changed 2 years ago by assefa

Changed 2 years ago by assefa

As discussed off list, we could use a processing tag to use an alternative renderer. We could do that in mapdraw.c possible. Attached patch was tested with kml driver. Is this approach ok or another one needed?

Changed 2 years ago by tbonfort

Assefa,

The approach you are taking seems correct to me, although I have not tested this. It should be noted however that in the patch you attached, the opacity of the requested layer won't be honored.

Changed 2 years ago by assefa

Regarding opacity, I was not sure how it was working. In the case I am using it now, I set the opacity in the kml docuement (the groundoverlay color that contains the refernece to the png file). You are right the png file by itself does not honor the opacity, but the resulting kml layer is transparent.

Id the transparency done when the mergeRasterBuffer process?

Changed 2 years ago by tbonfort

There are two problems with the current behavior:

  • potential problem with symbolset that can contain cached versions of the symbol, see #3834
  • the first msSelectOutputFormat updates the map outputformat. it should be set back to what was used once the layer is finished.

Changed 2 years ago by tbonfort

  • status changed from new to closed
  • resolution set to fixed

my bad, msSelectOutputFormat does not update the map outputformat, but it does change the map image type.

both issues fixed in r11558

Note: See TracTickets for help on using tickets.