Would it be possible to make the max layers value a parameter that is set at the top of your map file? ... compiled with a default value, but settable to a higher value when needed? Or would that introduce inefficencies into the memory management?
I think those of us who live in the Windows world and are 'compile challenged' tend to bump into this problem ... in a less trivial way, and this seems to pop up on the list every few months. Cheers, Ken Lord Vancouver BC On 1/13/06, Stephen Woodbridge <[EMAIL PROTECTED]> wrote: > James Net wrote: > > Sorry to butt in, but does changing the max limit in "map.h" (to say > > 1000) and then recompiling have any effect on the speed / efficiency of > > mapserver if you have have a map file wth only 1 - 5 layers? > > I should not effect speed, but it does effect memory consumed as the > number of layers is staticly allocated. This might indirectly effect > speed but making less memory available for system buffers, but probably not. > > -Steve W. > > >> From: Stephen Woodbridge <[EMAIL PROTECTED]> > >> Reply-To: Stephen Woodbridge <[EMAIL PROTECTED]> > >> To: [email protected] > >> Subject: Re: [UMN_MAPSERVER-USERS] Mapfile - 50 Layers Maximum ? > >> Date: Fri, 13 Jan 2006 13:09:51 -0500 > >> > >> Randy, > >> > >> The limit is set in map.h > >> You can change the limit and recompile > >> More resent version have a higher limit I think, but I'm not sure what. > >> > >> -Steve W. > >> > >> Randy How wrote: > >> > >>> Greetings, > >>> I've come across this rumor/fact, that there is a maximum of 50 > >>> layers in a > >>> map file. Unknowingly I was experimenting the use of MapServer for > >>> QC'ing > >>> a project, that I put in 2,500 layers into a mapfile. Yes, not > >>> surprisingly > >>> MapServer baucked about this. Then the first question is what is the > >>> limit, > >>> then I found out that it was 50! > >>> I looked in to an existing mapfile that we have and it has 45 > >>> layers. These > >>> layers are represented at different scales, and/or by spatial reference > >>> (i.e. Indices for different UTM zones), then a watermark. > >>> We are moving into more global datasets which may be represented the > >>> same > >>> way. There's 60 UTM zones. So the 50 layer limit is going to be a > >>> problem > >>> in the short term. > >>> Can anyone verify this fact? And is there a work around in place to > >>> accomplish these needs? > >>> Thanks, Randy ________________________________________________ > >>> Randy How > >>> > >>> Geospatial Applications Developer > >>> Voice: +1-970-482-4400 > >>> Fax: +1-970-482-4499 > >>> Web: http://www.i3.com/ > >>> > >>> i-cubed > >>> 201 Linden, Third Floor > >>> Fort Collins, CO 80524 > >>> > > > > _________________________________________________________________ > > ASUS M5 Ultra-slim lightweight is Now $1999 (was $2,999) > > http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fwww%2Easus%2Ecom%2Eau%2F&_t=752129232&_r=Hotmail_tagline_23Nov05&_m=EXT > > > > >
