[mapserver-dev] layer masking rfc

Lime, Steve D (DNR) Steve.Lime at state.mn.us
Thu Dec 1 11:26:38 EST 2011


Sorry, I noticed that at the end of the RFC *after* I replied. I guess will have to see if that causes issues down the road. The functionality proposed will still be a welcome addition without it though.

Is there any reason to denote the mask layer itself differently? For example, tileindex layers can be given a special type (e.g. TYPE TILEINDEX) so that they can be avoided during the drawing process until a layer that references them is encountered. I'd think that would be helpful from a getCapabilities perspective too. So from your RFC example you'd get:

LAYER
 NAME "parcels"
 TYPE MASK
 STATUS OFF
 DATA "the_geom from parcels where clientid='%token%'"
 CLASS
  STYLE
   COLOR 0 0 0
  END
 END
END

LAYER
 NAME "meteo"
 STATUS ON
 TYPE RASTER
 DATA "raster.tif"
 MASK "parcels"
END

Steve


-----Original Message-----
From: thomas bonfort [mailto:thomas.bonfort at gmail.com] 
Sent: Thursday, December 01, 2011 10:18 AM
To: Lime, Steve D (DNR)
Cc: MapServer Dev Mailing List
Subject: Re: [mapserver-dev] layer masking rfc

Steve,
querying will not be supported, i.e. features will not be masked out
from a query (c.f.
http://mapserver.org/trunk/development/rfc/ms-rfc-79.html#limitations).
Stepping down that path means that vector intersections need to be
computed, which is an entirely different workload.

--
thomas

On Thu, Dec 1, 2011 at 17:11, Lime, Steve D (DNR)
<Steve.Lime at state.mn.us> wrote:
> How does this impact query operations? Seems like you'd want to restrict queries based on the mask too. -Steve
>
>
> -----Original Message-----
> From: mapserver-dev-bounces at lists.osgeo.org [mailto:mapserver-dev-bounces at lists.osgeo.org] On Behalf Of thomas bonfort
> Sent: Wednesday, November 30, 2011 11:33 AM
> To: MapServer Dev Mailing List
> Subject: [mapserver-dev] layer masking rfc
>
> Devs,
>
> I have just committed rfc 79 that proposes pixel level layer masking.
> This is a minor enhancement so I went straight to the rfc process
> without a mail to this list beforehand, but feel free to comment on it
> here.
> I would like to move rather fast on this issue, so will call for a
> vote on this this weekend if no objections have arisen until then.
>
> http://trac.osgeo.org/mapserver/browser/trunk/docs/en/development/rfc/ms-rfc-79.txt
>
> best regards,
>
> thomas
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>
>



More information about the mapserver-dev mailing list