Even if I use the scale denominator I have to repeat the class for each category for every priority. The style of each category remain still the same, which means I have a lot of duplicated classes.

Daniel

Am 15/07/2010 20:03, schrieb Lime, Steve D (DNR):
I wonder if you could access the current computed scale denominator in 
expression (or the DATA statement) and get the same effect...

e.g.:

   CLASS
      EXPRESSION ('[category]' eq 'poi'&&  [priority]<  SCALE)
      ...
   END

Steve



-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Daniel Degasperi
Sent: Thursday, July 15, 2010 5:02 AM
To: Lime, Steve D (DNR)
Cc: [email protected]
Subject: Re: [mapserver-users] MAXSCALEDENOM [scale_field]

Hi Steve,
maybe it's easier to explain with a mapfile example:

LAYER
      NAME "POI"
      TYPE POINT
      CONNECTIONTYPE postgis
      CONNECTION "user=somebody password=something dbname=test
host=localhost"
      DATA "the_geom FROM (SELECT gid, category, priority, the_geom FROM
poi) AS foo USING UNIQUE gid"
      ...
      CLASS
          EXPRESSION ('[category]' eq 'poi')
          MAXSCALEDENOM [priority]
          ...
      END
      ...
END

In this case I've one single class  for each category and the
MAXSCALEDENOM get the value from the priority attribute of my datasource.
As it is now, MapServer does not support this feature and I've to repeat
every single category for each different priority value.

Best regards,
Daniel


Am 14/07/2010 23:53, schrieb Lime, Steve D (DNR):
MapServer doesn't support layer-level binding only feature-level binding. I'm 
having trouble seeing the value. Can you explain further?

Steve
________________________________________
From: [email protected] 
[[email protected]] On Behalf Of Daniel Degasperi 
[[email protected]]
Sent: Wednesday, July 14, 2010 7:54 AM
To: [email protected]
Subject: [mapserver-users] MAXSCALEDENOM [scale_field]

Hi,
I've tried to read the MAXSCALEDENOM value from a attribute in my
datasource, but mapserver throw's a parsing error.
Probably because such feature does not exist in mapserver.

Are there any intentions to implement this?
It could be interesting for layers, whose data has different priorities
but the same styling.
With this feature I can avoid repeating the classes for every priority.

Best regards,
Daniel
_______________________________________________
mapserver-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapserver-users

_______________________________________________
mapserver-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapserver-users

_______________________________________________
mapserver-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Reply via email to