Hi,
We are trying here to get WMS-layer to work on Google maps. Basically it works, the problem now is the edges of tiles. As objects outside the tiles may render on the tile (especially labels).
We have now tried using the buffer-parameter, but it seams to have no effect, compared to the query without buffer-parameter. The WMS-query is following:
http://xxx:8080/geoserver/wms?&REQUEST=GetMap&SERVICE=WMS&reaspect=false&VERSION=1.1.1&LAYERS=xxx&FORMAT=image/png&BGCOLOR=0xFFFFFF&TRANSPARENT=TRUE&SRS=EPSG:900913&BBOX=2778027.355474912,8438648.052592598,2778638.851701079,8439259.548833366&WIDTH=256&HEIGHT=256&buffer=30
(Sorry, the server is not publically available, so real life example is not possible.)
The same query with '&tiled=true&tilesorigin=xxx' works fine. It just seems un-necessary to render 3x3 times bigger area the get points ~15 pixels away..
Any ideas, what we are doing wrong?
Best regards,
Kylli Ek
Kylli Ek ha scritto:
Hi,
We are trying here to get WMS-layer to work on Google maps. Basically it works, the problem now is the edges of tiles. As objects outside the tiles may render on the tile (especially labels).
We have now tried using the buffer-parameter, but it seams to have no effect, compared to the query without buffer-parameter. The WMS-query is following:
http://xxx:8080/geoserver/wms?&REQUEST=GetMap&SERVICE=WMS&reaspect=false&VERSION=1.1.1&LAYERS=xxx&FORMAT=image/png&BGCOLOR=0xFFFFFF&TRANSPARENT=TRUE&SRS=EPSG:900913&BBOX=2778027.355474912,8438648.052592598,2778638.851701079,8439259.548833366&WIDTH=256&HEIGHT=256&buffer=30
(Sorry, the server is not publically available, so real life example is not possible.)
The same query with '&tiled=true&tilesorigin=xxx' works fine. It just seems un-necessary to render 3x3 times bigger area the get points ~15 pixels away..
By your description I don't understand if you're getting cut
labels or you're missing labels that would cross the tile borders.
The first is a bug, but I'll need you to help me reproduce it,
the second is a feature, as there is now way to tell if the
label will be really rendered on the adjacent cell as well,
given that label conflict resolution might find other labels
that conflict with it and end up not rendering it at all.
This old page I wrote has examples of what might go wrong:
http://geoserver.org/display/GEOS/Rendering+and+tiling+issues+research
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea Aime wrote:
Kylli Ek ha scritto:
Hi,
We are trying here to get WMS-layer to work on Google maps. Basically it works, the problem now is the edges of tiles. As objects outside the tiles may render on the tile (especially labels).
We have now tried using the buffer-parameter, but it seams to have no effect, compared to the query without buffer-parameter. The WMS-query is following:
http://xxx:8080/geoserver/wms?&REQUEST=GetMap&SERVICE=WMS&reaspect=false&VERSION=1.1.1&LAYERS=xxx&FORMAT=image/png&BGCOLOR=0xFFFFFF&TRANSPARENT=TRUE&SRS=EPSG:900913&BBOX=2778027.355474912,8438648.052592598,2778638.851701079,8439259.548833366&WIDTH=256&HEIGHT=256&buffer=30
(Sorry, the server is not publically available, so real life example is not possible.)
The same query with '&tiled=true&tilesorigin=xxx' works fine. It just seems un-necessary to render 3x3 times bigger area the get points ~15 pixels away..
By your description I don't understand if you're getting cut
labels or you're missing labels that would cross the tile borders.
The first is a bug, but I'll need you to help me reproduce it,
the second is a feature, as there is now way to tell if the
label will be really rendered on the adjacent cell as well,
given that label conflict resolution might find other labels
that conflict with it and end up not rendering it at all.
This old page I wrote has examples of what might go wrong:
http://geoserver.org/display/GEOS/Rendering+and+tiling+issues+research
Cheers
Andrea
Thanks for your answer!
There is no labels over the tiling borders with the buffer-parameter. If that is meant to be like that, then ok. Good to know.
But the same applies, if we have no labels at all, just points as 12px circles. If there is a point close enough to the tile border, it is on 2 (worst case 4) tiles. It always shows on the tile, where the center point is, but not on the other neighbouring tiles..
Best regards,
Kylli Ek
Kylli Ek ha scritto:
But the same applies, if we have no labels at all, just points as 12px circles. If there is a point close enough to the tile border, it is on 2 (worst case 4) tiles. It always shows on the tile, where the center point is, but not on the other neighbouring tiles..
Hum, we've seen the issue already:
http://jira.codehaus.org/browse/GEOS-2742
but we did not find any way to reproduce the issue on the 1.7.3
release...
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea Aime wrote:
Kylli Ek ha scritto:
But the same applies, if we have no labels at all, just points as 12px circles. If there is a point close enough to the tile border, it is on 2 (worst case 4) tiles. It always shows on the tile, where the center point is, but not on the other neighbouring tiles..
Hum, we've seen the issue already:
http://jira.codehaus.org/browse/GEOS-2742
but we did not find any way to reproduce the issue on the 1.7.3
release...
Cheers
Andrea
Hi,
Thank you again.
Yes, we experieced exactly the same as in the bug report. And we are currently using 1.7.2 release.
We are installing also 1.7.3, so I will get back next week, if the same problem occurs with it also.
Kylli Ek