There's more to experience when you log in!
Hi Miquel,Do you have custom bounds set on the Tile?
I have seen strange behaviour like you are describing when my bounds are not correct, sorry I cant tell you what they should be as I don't use epsg27700.
I think the bounds need to be a square, but I'm not certain of this
(maxX - minX) / (maxY - minY) = 1
tileHeight = (boundsHeight ÷ boundsWidth) × tileWidth
I still haven't discovered precisely how this fix works, but at least for myself in ESPG:28355 it's more than simply using square bounds.
1. Our .ecw imagery to be tiled has the extent shown in QGIS calculated as:
329000,5821000 : 356000,5850000 -> 27,000x 29,000y -> Using this causes incorrect tile location, mismatching the vector data2. In SSA, the only bounds to work without 'stretching' into the wrong location is:329000,5821000 : 356000,5848000 -> Which is equal to 27,000m x/y (square). The tiles show in the correct location, however it cuts of about 2km worth of imagery from the northern extent and is the only current workaround we have available.3. Seeing as the square bounds in step two work, I attempt to do a larger square bounds that doesn't cut the imagery off i.e. 30,000x 30,000y but I get the same projection error. I've tried many combinations of square bounds, such as extending the Min X rather than Max X etc, to no avail.So there's obviously some specific trick at play here. As far as mine goes the trick is to use the 3 original MinX,MinY,MaxX and (if the original Y axis is larger than X) reduce the Max Y until it forms a square, which will obviously clip part of your tile extent
Hi Timothy,The Bounds I use for EPSG:28355 are