Re: [mapserver-users] Unexpected result from overlapping images in tile index

Stephen Woodbridge wrote: Re: [mapserver-users] Unexpected result from overlapping images in tile index > Right, you can not rely on the tileindex from doing anything more than say > these are the objects that intersect with your bbox. True, if you use an unsorted shapefile tileind

Re: [mapserver-users] Unexpected result from overlapping images in tile index

Right, you can not rely on the tileindex from doing anything more than say these are the objects that intersect with your bbox. There are no specific controls over how the objects interact other than items are draw in the order they are found in the data sources. This is why sorting efected yo

Re: [mapserver-users] Unexpected result from overlapping images in tile index

Thanks for the sortshp tip! You are correct -- sorting the tileindex yields the result I expected. If the black pixels cover the full extents of black.tif (ie. with zero NODATA values), then Mapserver will render either an all black or an all gray image, regardless of the sorting order in the non

Re: [mapserver-users] Unexpected result from overlapping images in tile index

Peter, if I understand correctly I'm not aware that there is any documentation or requirement that using a tileindex with mapserver garantees any ordering in the stacking of the images returned by the tileindex. Namely, if your tileindex returns your gray (opaque) image after (i.e. on top of) y

[mapserver-users] Unexpected result from overlapping images in tile index

Hi, I have a tile index to render a layer from two images. The images are black.png https://github.com/pedros007/mapserver-tindex-problem/blob/master/black.png?raw=true which has NODATA values over the white areas and grayscale pixels with intensity 1 and gray.png with intensity 128 and zero NODA