From: Chris H. <ch...@op...> - 2006-12-29 18:44:36
|
> In the meantime one can use tilecache, Chris says. I tried the demo, an= d I still noticed some cell cut. Is is because of the 5x5 tile mechanism = of TileCache? If it is so, does that mean TileCache "saves" many cell, bu= t not all? Apart from this, TileCache seems interesting for=20 Not all of that map was cached with metaTile, so you may just be looking=20 at areas that didn't get it. I cleared the top 8 zooms or so and redid=20 those, and everything new is with metaTile, but some aren't. But it's=20 also not perfect, just a lot better. You could try playing with bigger=20 metaSize's and buffers, ect. Also note that you'll get really good performance if you did it with=20 mod_python. We haven't even done that yet, but it's supposed to be a=20 lot faster. No need for you to write it up, it's on my todo list. But when I write=20 it up if you could review it that would be great, see if I missed=20 everything. best regards, Chris > Anyway, thank you again for your precious support, and Happy New Year! >=20 > Cheers, >=20 > Fabio >=20 >=20 > -----Messaggio originale----- > Da: Chris Holmes [mailto:ch...@op...]=20 > Inviato: venerd=EC 29 dicembre 2006 18.26 > A: Fabio Da Soghe > Cc: 'Geoserver-devel' > Oggetto: Re: [Geoserver-devel] R: Planning the next few months (warning= , long mail) >=20 > We're hoping to work on it relatively soon, at the very least the fix t= o=20 > do better rendering of labels for tiles. >=20 > But in the meantime, if you're using metacarta's TileCache -=20 > http://labs.metacarta.com/wms-c/ - they have an option called 'metaTile= '=20 > that gives pretty nice results with regards to tiles on GeoServer. >=20 > See: http://sigma.openplans.org/ for an example and=20 > http://sigma.openplans.org/tilecache-1.3/tilecache.cfg for how we set u= p=20 > the params (note that you need version 1.3 and the python imaging=20 > library for it to work properly). >=20 > What it does is request a 5x5 tile (which you can set to be even bigger= =20 > with the metaSize param) from the WMS, and cuts it up on the client=20 > side. This is how ka-map works actually, as MapServer's renderer is=20 > even more finicky for tiles than GeoServer (they also need the=20 > metaBuffer so lines don't get rounded off). Some labeling is still=20 > repeated, but it's not at every tile so it looks much better. >=20 > You also get better performance overall - the first tile will come back= =20 > a bit more slowly, but the set of tiles will come much more quickly, as= =20 > GeoServer does better rendering a large area all at once. And of cours= e=20 > that's only on areas that haven't been pre-cached. You can use their=20 > client to pre-cache you're whole map if it's not too big. (I need to=20 > take some time to write up a nice tutorial on setting all this up...) >=20 > If that's not sufficient for you and you're interested in funding the=20 > patch to the renderer immediately or getting directions on how to do it= =20 > yourself let us know. >=20 > best regards, >=20 > Chris >=20 > Fabio Da Soghe wrote: >> Hello list. >> >> I'm reading this thread with much interest. In the webmapping applicat= ion my company is building (based on GeoServer), we're sadly discovering = the issue about tiled rendering (label moving near tile boundary and cell= and text cutting). >> >> Tiled rendering is very "cool" and definitively a must for us (for bot= h performance and usability reasons), but these problem seems to put a st= op on this road. >> >> Directly supporting it in GeoServer (via WMS-C or TMS) would be great,= but in the meantime we're guessing if there could be some workaround tha= t let one use the tile mechanism and still keep getting correct maps (wit= hout at least ugly cut cells). >> >> Has anybody some hint in this direction? Maybe through a patch to GeoS= erver, as was discussed in this list some time ago (about a possible vend= or-specific option in the SLD with which to get no cross-tile label, for = example)? >> >> Many thanks in advance for any feedback. >> >> Best Regards, >> >> Fabio Da Soghe >> >> >> -----Messaggio originale----- >> Da: geo...@li... [mailto:geoserver-de= vel...@li...] Per conto di Andrea Aime >> Inviato: luned=EC 11 dicembre 2006 9.00 >> A: Paul Ramsey >> Cc: Geoserver-devel >> Oggetto: Re: [Geoserver-devel] Planning the next few months (warning, = long mail) >> >> Paul Ramsey ha scritto: >>> On 10-Dec-06, at 8:55 AM, Andrea Aime wrote: >>> >>>> * tiled WMS: this requires changes in both the gt2 renderer and >>>> a new module that builds on top on the current WMS I guess. >>>> Changes required in the renderer are not earth shattering, so >>>> I guess they could be handled in 2.3.x or 2.4.x once branched. >>> Why do you perceive tiling as a re-implementation issue? I think the=20 >>> TileCache approach already being pushed by Metacarta shows that it's=20 >>> just a layering on top of existing rendering infrastructures. So WMS= =20 >>> tiling should be handled as another layer on top of an (unchanged)=20 >>> render stack? >> Yes, you could, and it can be work very fine. >> At the minimum, we require the geotools renderer to stop moving labels= for each different rendering request, and this is in the pack of "proper= ly supporting WMS-C", that is, just fix the current WMS and make it usabl= e to serve tiles with TileCache on top of it. >> >> Supporting TMS in Geoserver is another matter. From where I stand, if = an admin is familiar with Apache and Python he would choose MapServer or = Mapnik as the backend anyways, unless he needs better looking maps. >> >> On the contrary, an organisation using already Java may be uncomfortab= le of fiddling with another piece of software, one using Microsoft stuff = would be probably even more scared away from having to install not one bu= t two foreign technologies. >> >> Having around TileCache makes it less urgent to implement one in Geose= rver, at the same time the implementation is already there and quite nice= and compact, so re-coding it in Geoserver should not be a major effort e= ither. >> >> Cheers >> Andrea Aime >> >> ----------------------------------------------------------------------= --- >> Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.n= et's Techsay panel and you'll get the chance to share your opinions on IT= & business topics through brief surveys - and earn cash http://www.techs= ay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV >> _______________________________________________ >> Geoserver-devel mailing list >> Geo...@li... >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> >> >> >> ----------------------------------------------------------------------= --- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to shar= e your >> opinions on IT & business topics through brief surveys - and earn cash >> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID= =3DDEVDEV >> _______________________________________________ >> Geoserver-devel mailing list >> Geo...@li... >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> >> >> >=20 --=20 Chris Holmes The Open Planning Project http://topp.openplans.org |