Ok, I just gave an untiled layer a try, unfortunately though, due to the large amount of symbols being displayed on the screen, there is about a 2 second delay every time the map is panned. My client will most certainly find this unacceptable. I have tried using smaller images, but I cannot sacrifice any more quality. I believe my database query to be as optimized as it can be (has about 50 ms runtime, I honestly don't think I can get it any lower than that).
If these are the only options, is there something else besides WMS that you all would recommend using to solve this issue? Thanks, -Adam On Thu, Apr 29, 2010 at 2:54 PM, Lime, Steve D (DNR) <[email protected] > wrote: > So use two layers. One for the background, use tilecache for that. Then use > an untiled wms/mapserver layer for the overlayed points. - Steve > ________________________________________ > From: [email protected] [ > [email protected]] On Behalf Of Adam Eskreis [ > [email protected]] > Sent: Thursday, April 29, 2010 1:24 PM > To: [email protected] > Subject: Re: [mapserver-users] Re: WMS and tiles cutting off > > I have thought about using tilecache with metatiling, however there is a > caveat about this map that i forgot to mention in my main post, and it has > to do with that "categories" parameter. Basically, each point/symbol on the > map has an associated category in the database backend. I am using > mapserver/WMS parameters to change the categories which are called. Each > time the user selects a category, only the points in that category are > shown. My query in the mapfile looks something like thi: > > SELECT point_geom,gid,symbol,angle FROM mapdata WHERE category > IN(%CATEGORIES%)"; > > And each time the user changes the categories, I use openlayers to merge > new parameters, and input the new category values that should be used. Is > tilecache still useable if I have a system like this set up? > > Thanks, > -Adam > > > On Thu, Apr 29, 2010 at 6:14 AM, kaipi <[email protected]<mailto: > [email protected]>> wrote: > > Hi, > > you can use http://tilecache.org/ Tilecache with the option metatiling > enabled. With metatiling enabled Tilecache will fetch larger tiles (eg. > 4096x4096) from Mapserver and will cut them into smaller tiles (eg. > 256x256). It will also increase performance because Mapserver does not need > to render tiles when they are already in cache. > > kaipi > -- > View this message in context: > http://osgeo-org.1803224.n2.nabble.com/WMS-and-tiles-cutting-off-tp4978418p4979280.html > Sent from the Mapserver - User mailing list archive at Nabble.com. > _______________________________________________ > mapserver-users mailing list > [email protected]<mailto:[email protected]> > http://lists.osgeo.org/mailman/listinfo/mapserver-users > >
_______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
