tile_map_edge_buffer Raster Rendering Corruption #4418

Closed
IslandJohn opened this Issue Aug 7, 2012 · 1 comment

Comments

Projects
None yet
2 participants
@IslandJohn

It appears that using tile_map_edge_buffer to render tiles (mode=tiles) cause raster layers near the left/right edges of the map extents to be clipped. The clipping seems to be correlated with the size of the buffer. The example below using 256px is a test.

The map excerpt follows:

WEB
    METADATA
        "tile_map_edge_buffer" "256" # 256 pixel rendering buffer
        "tile_metatile_level" "1" # metatile 1 level up (2:1 = 512px)
    END
END

PROJECTION
    "proj=merc"
    "datum=WGS84"
END
EXTENT -20037508.343 -20037508.343 20037508.343 20037508.343

LAYER
    #PROCESSING "RESAMPLE=AVERAGE"
    TYPE RASTER
    NAME "gtopo30"
    DATA "gtopo30/gtopo30.tif"
    STATUS ON

gtopo30.tif is the GTOPO30 DEMs gdalwarp-ed to EPSG:900913. Requesting tile 0/0/1 causes nearly all of Alaska's elevation to be omitted. As you zoom in, the clipped area stays the same (pixel-wise) but more and more raster data is displayed. The leftmost and rightmost tiles have a clipped, or rather cropped, region. This appears to affect only raster, as SHP file are rendered correctly.

@mapserver-bot

This comment has been minimized.

Show comment Hide comment
@mapserver-bot

mapserver-bot Feb 23, 2016

This is an automated comment

This issue has been closed due to lack of activity. This doesn't mean the issue is invalid, it simply got no attention within the last year. Please reopen with missing/relevant information if still valid.

Typically, issues fall in this state for one of the following reasons:

  • Hard, impossible or not enough information to reproduce
  • Missing test case
  • Lack of a champion with interest and/or funding to address the issue

This is an automated comment

This issue has been closed due to lack of activity. This doesn't mean the issue is invalid, it simply got no attention within the last year. Please reopen with missing/relevant information if still valid.

Typically, issues fall in this state for one of the following reasons:

  • Hard, impossible or not enough information to reproduce
  • Missing test case
  • Lack of a champion with interest and/or funding to address the issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment