- (buffer([shape],dist)): Buffer the geometry ( [shape] ) using dist pixels as buffer distance. For polygons, a negative dist will produce a setback.
- (simplify([shape],tolerance)): simplifies a geometry ( [shape] ) using the standard Douglas-Peucker algorithm.
- (simplifypt([shape], tolerance)): simplifies a geometry ( [shape] ), ensuring that the result is a valid geometry having the same dimension and number of components as the input. tolerance must be non-negative.
- (generalize([shape],tolerance)): simplifies a geometry ( [shape] ) in way comparable to FME’s ThinNoPoint algorithm. See http://trac.osgeo.org/gdal/ticket/966 for more information.
There is a difference between STYLE and LAYER GEOMTRANSFORM. LAYER-level will receive ground coordinates (meters, degress, etc) and STYLE-level will receive pixel coordinates. The argument to methods such as simplify() must be in the same units as the coordinates of the shapes at that point of the rendering workflow, i.e. pixels at the STYLE-level and in ground units at the LAYER-level.
LAYER NAME "my_layer" TYPE LINE STATUS DEFAULT DATA "lines.shp" GEOMTRANSFORM (simplify([shape], 10)) ## 10 ground units CLASS STYLE GEOMTRANSFORM (buffer([shape], 5) ## 5 pixels WIDTH 2 COLOR 255 0 0 END END END
The [map_cellsize] variable is available if you need to pass a pixel value at the LAYER-level.
LAYER NAME "my_layer" TYPE LINE STATUS DEFAULT DATA "lines.shp" UNITS meters # 10 * [map_cellsize] == 10 pixels converted to ground units GEOMTRANSFORM (simplify([shape], [map_cellsize]*10)) .
To get this variable working in the math expression parser, the [map_cellsize] has to be converted into the layer ground unit. If you choose to use [map_cellsize] in your GEOMTRANSFORM expression, you must explicitly set the UNITS option in the layer.
LAYER . GEOMTRANSFORM "javascript://transform.js" # relative path END
LAYER . GEOMTRANSFORM "javascript:///home/user/transform.js" # absolute path ENDНове в версії 7.0. Примітка Requires V8 MapScript Support . Дивись також GEOMTRANSFORM - Geometry Transformations
Name of a group that this layer belongs to. The group name can then be reference as a regular layer name in the template files, allowing to do things like turning on and off a group of layers at once.
If a group name is present in the LAYERS parameter of a CGI request, all the layers of the group are returned (the STATUS of the LAYER s have no effect).
HEADER [filename] Template to use before a layer’s set of results have been sent. Multiresult query modes only. JOIN Signals the start of a JOIN object. LABELANGLEITEM [attribute]
(As of MapServer 5.0 this parameter is no longer available. Please see the LABEL object’s ANGLE parameter) For MapServer versions < 5.0, this is the item name in attribute table to use for class annotation angles. Values should be in degrees.
Застаріло починаючи з версії 5.0.
LABELCACHE [on|off] Specifies whether labels should be drawn as the features for this layer are drawn, or whether they should be cached and drawn after all layers have been drawn. Default is on. Label overlap removal, auto placement etc. are only available when the label cache is active. LABELITEM [attribute] Item name in attribute table to use for class annotation (i.e. labeling). LABELMAXSCALEDENOM [double]
Minimum scale at which this LAYER is labeled. Scale is given as the denominator of the actual scale fraction, for example for a map at a scale of 1:24,000 use 24000. Implemented in MapServer 5.0, to replace the deprecated LABELMAXSCALE parameter.
LABELMINSCALEDENOM [double]Maximum scale at which this LAYER is labeled. Scale is given as the denominator of the actual scale fraction, for example for a map at a scale of 1:24,000 use 24000. Implemented in MapServer 5.0, to replace the deprecated LABELMINSCALE parameter.
LABELREQUIRES [expression]Sets context for labeling this layer, for example:
LABELREQUIRES "![orthoquads]"
means that this layer would NOT be labeled if a layer named “orthoquads” is on. The expression consists of a boolean expression based on the status of other layers, each [layer name] substring is replaced by a 0 or a 1 depending on that layer’s STATUS and then evaluated as normal. Logical operators AND and OR can be used.
(As of MapServer 5.0 this parameter is no longer available. Please see the LABEL object’s SIZE parameter) For MapServer versions < 5.0, this is the item name in attribute table to use for class annotation sizes. Values should be in pixels.
Застаріло починаючи з версії 5.0.
MASK [layername]The data from the current layer will only be rendered where it intersects features from the [layername] layer. [layername] must reference the NAME of another LAYER defined in the current mapfile. can be any kind of mapserver layer, i.e. vector or raster. If the current layer has labelling configured, then only labels who’s label-point fall inside the unmasked area will be added to the labelcache (the actual glyphs for the label may be rendered ontop of the masked-out area.
Unless you want the features of [layername] to actually appear on the generated map, [layername] should usually be set to STATUS OFF.
MAXFEATURES [integer] Specifies the number of features that should be drawn for this layer in the CURRENT window. Has some interesting uses with annotation and with sorted data (i.e. lakes by area). MAXGEOWIDTH [double]
Maximum width, in the map’s geographic units, at which this LAYER is drawn. If MAXSCALEDENOM is also specified then MAXSCALEDENOM will be used instead.
The width of a map in geographic units can be found by calculating the following from the extents:
[maxx] - [minx]
Нове в версії 5.4.0.
MAXSCALEDENOM [double]Minimum scale at which this LAYER is drawn. Scale is given as the denominator of the actual scale fraction, for example for a map at a scale of 1:24,000 use 24000.
Нове в версії 5.0.0: Replaced MAXSCALE.
This keyword allows for arbitrary data to be stored as name value pairs. This is used with OGC WMS to define things such as layer title. It can also allow more flexibility in creating templates, as anything you put in here will be accessible via template tags.
METADATA "title" "My layer title" "author" "Me!" END
Minimum width, in the map’s geographic units, at which this LAYER is drawn. If MINSCALEDENOM is also specified then MINSCALEDENOM will be used instead.
The width of a map in geographic units can be found by calculating the following from the extents:
[maxx] - [minx]
Нове в версії 5.4.0.
MINSCALEDENOM [double]Maximum scale at which this LAYER is drawn. Scale is given as the denominator of the actual scale fraction, for example for a map at a scale of 1:24,000 use 24000. Implemented in MapServer 5.0, to replace the deprecated MINSCALE parameter.
NAME [string] Short name for this layer. This name is the link between the mapfile and web interfaces that refer to this name. They must be identical. The name should be unique, unless one layer replaces another at different scales. Use the GROUP option to associate layers with each other. It is recommended that the name not contain spaces, special characters, or begin with a number (which could cause problems through interfaces such as OGC services). OFFSITE [r] [g] [b] Sets the color index to treat as transparent for raster layers.
Застаріло починаючи з версії 7.0: Use a COMPOSITE block instead.
PLUGIN [filename]Additional library to load by MapServer, for this layer. This is commonly used to load specific support for SDE and Microsoft SQL Server layers, such as:
CONNECTIONTYPE PLUGIN CONNECTION "hostname,port:xxx,database,username,password" PLUGIN "C:/ms4w/Apache/specialplugins/msplugin_sde_92.dll" DATA "layername,geometrycolumn,SDE.DEFAULT"
POSTLABELCACHE [true|false] Tells MapServer to render this layer after all labels in the cache have been drawn. Useful for adding neatlines and similar elements. Default is false. PROCESSING [string]
Passes a processing directive to be used with this layer. The supported processing directives vary by layer type, and the underlying driver that processes them.
-
Attributes Directive - The ITEMS processing option allows to specify the name of attributes for inline layers or specify the subset of the attributes to be used by the layer, such as:
PROCESSING "ITEMS=itemname1,itemname2,itemname3"
PROCESSING "CLOSE_CONNECTION=DEFER"
PROCESSING "KERNELDENSITY_RADIUS=10"Нове в версії 7.0.
PROCESSING "KERNELDENSITY_COMPUTE_BORDERS=ON|OFF"Нове в версії 7.0.
PROCESSING "KERNELDENSITY_NORMALIZATION=AUTO|numeric"Нове в версії 7.0.
PROCESSING "LABEL_NO_CLIP=True"
PROCESSING "POLYLINE_NO_CLIP=True"
PROCESSING "GETSHAPE_STYLE_ITEMS=all"
PROCESSING "NATIVE_FILTER=id=234"Нове в версії 7.0.
PROCESSING "GAMMA=0.5"
PROCESSING "SCALE=AUTO" PROCESSING "BANDS=3,2,1"
Sets the current status of the layer. Often modified by MapServer itself. Default turns the layer on permanently.
In CGI mode, layers with STATUS DEFAULT cannot be turned off using normal mechanisms. It is recommended to set layers to STATUS DEFAULT while debugging a problem, but set them back to ON/OFF in normal use.
For WMS , layers in the server mapfile with STATUS DEFAULT are always sent to the client.
The STATUS of the individual layers of a GROUP has no effect when the group name is present in the LAYERS parameter of a CGI request - all the layers of the group will be returned.
STYLEITEM [Styling based on attributes or generated with Javascript
-
: Item to use for feature specific styling. The style information may be represented by a separate attribute (style string) attached to the feature. MapServer supports the following style string representations:
-
MapServer STYLE definition - The style string can be represented as a MapServer STYLE block according to the following example:
STYLE BACKGROUNDCOLOR 128 0 0 COLOR 0 0 208 END
ogr2ogr -sql "select *, OGR_STYLE from srclayer" "dstlayer" "srclayer"
- AUTO: The value: AUTO can be used for automatic styling.
- Automatic styling can be provided by the driver. Currently, only the OGR driver supports automatic styling.
- When used for a Union Layer , the styles from the source layers will be used.
LAYER . STYLEITEM "javascript://myscript.js" # relative path CLASS END END
LAYER . STYLEITEM "javascript:///home/user/myscript.js" # absolute path CLASS END END
Нове в версії 6.6. Примітка Requires V8 MapScript Support .The scale at which symbols and/or text appear full size. This allows for dynamic scaling of objects based on the scale of the map. If not set then this layer will always appear at the same size. Scaling only takes place within the limits of MINSIZE and MAXSIZE as described above. Scale is given as the denominator of the actual scale fraction, for example for a map at a scale of 1:24,000 use 24000. Implemented in MapServer 5.0, to replace the deprecated SYMBOLSCALE parameter.
TEMPLATE [file|url] Used as a global alternative to CLASS TEMPLATE . See Templating for more info. TILEINDEX [filename|layername]
Name of the tileindex file or layer. A tileindex is similar to an ArcInfo library index. The tileindex contains polygon features for each tile. The item that contains the location of the tiled data is given using the TILEITEM parameter. When a file is used as the tileindex for shapefile or raster layers, the tileindex should be a shapefile. For CONNECTIONTYPE OGR layers, any OGR supported datasource can be a tileindex. Normally the location should contain the path to the tile file relative to the shapepath, not relative to the tileindex itself. If the DATA parameter contains a value then it is added to the end of the location. When a tileindex layer is used, it works similarly to directly referring to a file, but any supported feature source can be used (ie. postgres, oracle).
All files in the tileindex should have the same coordinate system, and for vector files the same set of attributes in the same order.
Starting with MapServer 6.4, raster layers can use a tileindex with tiles of different projections. For that, the TILESRS parameter must be specified.
TILEITEM [attribute] Item that contains the location of an individual tile, default is “location”. TILESRS [attribute]
Name of the attribute that contains the SRS of an individual tile. That SRS can be expressed in WKT format, as an EPSG:XXXX code or as a PROJ.4 string. If the tileindex contains rasters in different projections, this option must be specified. If the tileindex has been generated with gdaltindex (GDAL >= 2.0), the value of TILESRS is the value of the -src_srs_name option of gdaltindex. See Tileindexes with tiles in different projections
This option is currently available only on raster layers.
TOLERANCE [double] Sensitivity for point based queries (i.e. via mouse and/or map coordinates). Given in TOLERANCEUNITS. If the layer is a POINT or a LINE, the default is 3. For all other layer types, the default is 0. To restrict polygon searches so that the point must occur in the polygon set the tolerance to zero. This setting does not apply to WFS GetFeature operations. TOLERANCEUNITS [pixels|feet|inches|kilometers|meters|miles|nauticalmiles|dd] Units of the TOLERANCE value. Default is pixels. Nauticalmiles was added in MapServer 5.6.
TRANSPARENCY [integer|alpha] - deprecated
Застаріло починаючи з версії 5.0: Use OPACITY instead.
Застаріло починаючи з версії 7.0: Use COMPOSITE instead.
TRANSFORM [true|false ul|uc|ur|lc|cc|lr|ll|lc|lr]Tells MapServer whether or not a particular layer needs to be transformed from some coordinate system to image coordinates. Default is true. This allows you to create shapefiles in image/graphics coordinates and therefore have features that will always be displayed in the same location on every map. Ideal for placing logos or text in maps. Remember that the graphics coordinate system has an origin in the upper left hand corner of the image, contrary to most map coordinate systems.
Version 4.10 introduces the ability to define features with coordinates given in pixels (or percentages, see UNITS), most often inline features, relative to something other than the UL corner of an image. That is what ‘TRANSFORM FALSE’ means. By setting an alternative origin it allows you to anchor something like a copyright statement to another portion of the image in a way that is independent of image size.
Specifies how the data should be drawn. Need not be the same as the shapefile type. For example, a polygon shapefile may be drawn as a point layer, but a point shapefile may not be drawn as a polygon layer. Common sense rules.
In order to differentiate between POLYGONs and POLYLINEs (which do not exist as a type), simply respectively use or omit the COLOR keyword when classifying. If you use it, it’s a polygon with a fill color, otherwise it’s a polyline with only an OUTLINECOLOR.
A circle must be defined by a a minimum bounding rectangle. That is, two points that define the smallest square that can contain it. These two points are the two opposite corners of said box. The following is an example using inline points to draw a circle:
LAYER NAME 'inline_circles' TYPE CIRCLE STATUS ON FEATURE POINTS 74.01 -53.8 110.7 -22.16 END END CLASS STYLE COLOR 0 0 255 END END END
TYPE query means the layer can be queried but not drawn.
TYPE annotation has been deprecated since version 6.2. Identical functionality can be obtained by adding LABEL level STYLE blocks, and do not require loading the datasets twice in two different layers as was the case with layers of TYPE annotation .
The Dynamic Charting HowTo for TYPE chart .
UNITS [dd|feet|inches|kilometers|meters|miles|nauticalmiles|percentages|pixels] Units of the layer. percentages (in this case a value between 0 and 1) was added in MapServer 4.10 and is mostly geared for inline features. nauticalmiles was added in MapServer 5.6. UTFDATA [string]
A UTFGrid JSON template. MapServer expression syntax (expressionObj). If no UTFDATA is provided, no data beyond the UTFITEM values will be exposed. If UTFITEM is set, the UTFDATA expose those so that keys and data can be connected. See MS RFC 93: UTF Grid Support and UTFGrid Output .
UTFDATA "\"id\":\"[fid]\", \"name\":\"[name]\", \"area\":\"[area]\">"
Нове в версії 7.0.
UTFITEM [string]The attribute to use as the ID for the UTFGrid. If a UTFITEM is not set, the sequential id (based on rendering order) is being used. If UTFITEM is set, the UTFDATA expose those so that keys and data can be connected. See MS RFC 93: UTF Grid Support and UTFGrid Output .
UTFITEM "fid"
Нове в версії 7.0.
VALIDATIONSignals the start of a VALIDATION block.
As of MapServer 5.4.0, VALIDATION blocks are the preferred mechanism for specifying validation patterns for CGI param runtime substitutions. See Run-time Substitution .
