4.10.0: Some vectors not rendering for a layer

[Eijnden, Bart van den (AGI)]

Are you using a spatial index (qix file)?

If so, did you regenerate the spatial index after the changes?

Best regards,
Bart

-----Oorspronkelijk bericht-----
Van: UMN MapServer Users List
[mailto:MAPSERVER-USERS at LISTS.UMN.EDU]Namens Andre Lockhart
Verzonden: donderdag 19 oktober 2006 9:41
Aan: MAPSERVER-USERS at LISTS.UMN.EDU
Onderwerp: Re: [UMN_MAPSERVER-USERS] 4.10.0: Some vectors not rendering
for a layer


Thanks, Andreas.

We've been on 4.10.0 for a few weeks and already have quotes around our
expression variables. This problem only appeared after we drew new vectors
for existing shapefiles.

 
 

               André Lockhart
               andre at CoValuate.com
         510.333.7189
 

-----Original Message-----
From: Andreas Albarello [mailto:andreas.albarello at territoriumonline.com] 
Sent: Thursday, October 19, 2006 12:30 AM
To: Andre Lockhart
Cc: MAPSERVER-USERS at LISTS.UMN.EDU
Subject: Re: [UMN_MAPSERVER-USERS] 4.10.0: Some vectors not rendering for a
layer

Andre Lockhart wrote:
> We have a layer with a few hundred vectors/segments that renders in 
> different colors based on a class expression. Some of the vectors 
> render, others do not.
> 
> We are well under the limit for classes and layers.
> 
> One clue is that it is the most recently drawn vectors that do not render.
> 
> We've tried rebooting/reinitializing everything, to no avail.

Andre,

I assume everything was working fine with Mapserver prior to version 
4.10. If that is the case, I suspect you might have run into a problem 
that I encountered myself with the new release and which I think is 
related to some changes made in the mapfile lexer.

In particular, I noticed that, when using class expressions of the form

EXPRESSION abcd

(that is a simple string based expression) Mapserver now requires you to 
put quotes around those expressions (i.e. EXPRESSION "abcd") or it 
*might* fail to recognize them as such. This applies to a layer's FILTER 
as well, but, as with EXPRESSION, only when using string expressions, no 
regular or nested logical expressions (which are still delimited by 
slashes and brackets, respectively).

Hope this helps.

Best regards,
Andreas


Disclaimer
************************************************************************
Aan dit bericht kunnen geen rechten worden ontleend. Dit bericht is
uitsluitend bestemd voor de geadresseerde. Als u dit bericht per abuis
hebt ontvangen, wordt u verzocht het te vernietigen en de afzender te 
informeren. Wij adviseren u om bij twijfel over de juistheid of de 
volledigheid van de mail contact met afzender op te nemen.

This message shall not constitute any rights or obligations.
This message is intended solely for the addressee.
If you have received this message in error, please delete it and
notify the sender immediately. When in doubt whether this message
is correct or complete, please contact the sender.
************************************************************************