Abstract
This document is a reference to the MapFile syntax for MapServer version 4.0.
Last Updated: 07-02-2003
Table of Contents
MapFiles are the basic configuration mechanism for the Mapserver. Anything associated with a particular application is defined here, although most options can be changed via a web form (CGI Variables).
The Mapfile is NOT case-sensitive.
Strings containing non-alphanumeric characters or a MapServer keyword MUST be quoted. It is recommended to put ALL strings in double-quotes.
There is a maximum of 50 layers per mapfile. This can be changed by editing the map.h file to change the value of MS_MAXLAYERS to the desired number and recompiling.
File paths may be given as absolute paths, or as paths relative to the location of the mapfile. In addition, data files may be specified relative to the SHAPEPATH
The mapfile has a hierarchical structure, with the Map object being the "root". All other objects fall under this one.
Comments are designated with a #.
Attributes are named using the following syntax: [ATTRIBUTENAME] ... Note that the name of the attribute included between the square brackets IS CASE SENSITIVE. Generally ESRI generated shapefiles have their attributes (.dbf column names) all in upper-case for instance, and for PostGIS, ALLWAYS use lower-case.
MapServer Regular Expressions are used through the operating system's C Library. For information on how to use and write Regular Expressions on your system, you should read the documentation provided with your C Library. On Linux, this is GLibC, and you can read "man 7 regex" ... This man page is also available on most UNIX's. Since these RegEx's are POSIX compliant, they should be the same on Windows as well, so windows users can try searching the web for "man 7 regex" since man pages are available all over the web.
Defines the master object of the MapFile, that is the object that holds all other objects (i.e. the "root"). It defines application/map wide parameters.
This defines a regular expression to be applied to requests to change DATA parameters via URL requests (i.e. map_layername_data=...). If a pattern doesn't exist then web users can't monkey with support files via URLs. This allows you to isolate one application from another if you desire, with the default operation being very conservative. See also TEMPLATEPATTERN.
Enables debugging of the map object. Verbose output is generated and sent to the standard error output (STDERR) or the MapServer logfile if one is set using the LOG parameter in the WEB object.
The spatial extent of the map to be created. Most often you will want to specify this, although mapserver will extrapolate one if none is specified.
Full filename of fontset file to use.
Color to initialize the map with (i.e. background color). When transparency is enabled (TRANSPARENT ON) for the typical case of 8-bit pseudocolored map generation, this color will be marked as transparent in the output file palette. Any other map components drawn in this color will also be transparenct, so for map generation with transparency it is best to use an otherwise unused color as the background color.
Compression quality for JPEG output. This keyword is now deprecated in favour of using FORMATOPTION "QUALITY=n" in the OUTPUTFORMAT declaration.
Output format to generate. See details in the OUTPUTFORMAT section for available formats. The name here must match the 'NAME' of a user defined or internally generated OUTPUTFORMAT section.
Should output images be interlaced? Default is [on]. This keyword is now depcrecated in favour of using the FORMATOPTION "INTERLACE=ON" line in the OUTPUTFORMAT declaration.
Signals the start of a LAYERobject.
Signals the start of a LEGENDobject.
Prefix attached to map, scalebar and legend GIF filenames created using this MapFile. It should be kept short.
Signals the start of a PROJECTION object.
Signals the start of a QUERYMAP object.
Signals the start of a REFERENCE MAP object.
Sets the pixels per inch for output, only affects scale computations and nothing else, default is 72
Computed scale of the map. Set most often by the application.
Signals the start of a SCALEBAR object.
Path to the directory holding the shapefiles or tiles. There can be further subdirectories under SHAPEPATH.
Size in pixels of the output image (i.e. the map).
Is the map active? Sometimes you may wish to turn this off to use only the reference map or scale bar.
Full filename of the symbolset to use.
Signals the start of a SYMBOL object.
This defines a regular expression to be applied to requests to change TEMPLATE parameters via URL requests (i.e. map_layername_template=...). If a pattern doesn't exist then web users can't monkey with support files via URLs. This allows you to isolate one application from another if you desire, with the default operation being very conservative. See also DATAPATTERN.
Should the background color for the maps be transparent. This flag is now deprecated in favour of declaring transparency within OUTPUTFORMAT declarations. Default is off.
Units of the map coordinates. Used for scalebar and scale computations.
Signals the start of a WEB object.
This object is used to define a label, which is in turn usually used to annotate a feature with a piece of text. Labels can however also be used as symbols through the use of various TrueType fonts.
Angle, given in degrees, to draw the label or AUTO to allow the software to compute the angle, AUTO is valid for LINE layers only.
Should text be antialiased? Note that this requires more available colors and results in slightly larger output images.
Color to draw a background rectangle (i.e. billboard). Off by default.
Color to draw a background rectangle (i.e. billboard) shadow. Off by default.
How far should the background rectangle be offset? Default is 1.
Padding, in pixels, around labels. Useful for maintaining spacing around text to enhance readability. Available only for cached labels. Default is 0.
Color to draw text with.
Font alias (as defined in the FONTSET) to use for labeling.
Forces labels for a particular class on, regardless of collisions. Available only for cached labels. Default is false.
Maximum font size to use when scaling text (pixels). Default is 256.
Minimum distance between duplicate labels. Given in pixels.
Minimum size a feature must be to be labeled. Given in pixels. For line data the overall length of the displayed line is used, for polygons features the smallest dimension of the bounding box is used. "Auto" keyword tells MapServer to only label features that are larger than their corresponding label. Available for cached labels only.
Minimum font size to use when scaling text (pixels). Default is 4.
Offset values for labels, relative to the lower left hand corner of the label and the label point. Given in pixels. In the case of rotated text specify the values as if all labels are horizontal and any rotation will be compensated for.
Color to draw a one pixel outline around the text.
Can text run off the edge of the map? Default is true.
Position of the label relative to the labeling point (layers only). First letter is "Y" position, second letter is "X" position. "Auto" tells MapServer to calculate a label position that will not interfere with other labels. With points and polygons, MapServer selects from the 8 outer positions (i.e. excluding cc). With lines, it only uses lc or uc, until it finds a position that doesn't collide with labels that have already been drawn. If all positions cause a conflict, then the label is not drawn (Unless the label's FORCE a parameter is set to "true"). "Auto" placement is only available with cached labels.
Color of drop shadow.
Shadow offset in pixels.
Text size. Use "integer" to give the size in pixels of your TrueType font based label, or any of the other 5 listed keywords to bitmap fonts.
Type of font to use. Generally bitmap fonts are faster to draw then TrueType fonts. However, TrueType fonts are scalable and available in a variety of faces. Be sure to set the FONT parameter if you select TrueType.
Character that represents an end-of-line condition in label text, thus resulting in a multi-line label.
The most used object in a MapFile, this one describes layers used to make up a map. Layers are drawn in their order of appearance in the MapFile (first layer is at the bottom, last in on top).
Signals the start of a CLASS object.
Item name in attribute table to use for class lookups.
Database connection string to retrieve remote data.
An SDE connection string consists of a hostname, instance name, database name, username and password separated by commas.
A PostGIS connection string is basically a regular PostgreSQL connection string, it takes the form of "user=nobody password=****** dbname=dbname host=localhost port=5432"
An Oracle connection string: user/pass[@db]
Type of connection. Default is local. See additional documentation for any other type.
Full filename of the spatial data to process. No file extension is necessary for shapefiles. Can be specified relative to the SHAPEPATH option from the Map Object.
If this is an SDE layer, the parameter should include the name of the layer as well as the geometry column, i.e. "mylayer,shape".
If this is a PostGIS layer, the parameter should be in the form of "<columnname> from <tablename>", where "columnname" is the name of the column containing the geometry objects and "tablename" is the name of the table from which the geometry data will be read.
For Oracle, use "shape FROM table" or "shape FROM (SELECT statement)" or even more complex Oracle compliant queries! Note that there are important performance impacts when using spatial subqueries however. Try using MapServer's FILTER whenever possible instead. You can also see the SQL submitted by forcing an error, for instance by submitting a DATA parameter you know won't work, using for example a bad column name.
Enables debugging of the layer object. Verbose output is generated and sent to the standard error output (STDERR) or the MapServe r logfile if one is set using the LOG parameter in the WEB object.
Switch to allow mapserver to return data in GML format. Usefull when used with WMS GetFeatureInfo operations. "false" by default
Signals the start of a FEATURE object.
This parameter allows for data specific attribute filtering that is done at the same time spatial filtering is done, but before any CLASS expressions are evaluated. For OGR and shapefiles the string is simply a mapserver regular expression. For spatial databases the string is a SQL WHERE clause that is valid with respect to the underlying database.
For example: FILTER "type='road' and size <2"
Item to use with simple FILTER expressions. OGR and shapefiles only.
Template to use after a layer's set of results have been sent. Multiresult query modes only.
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.
Template to use before a layer's set of results have been sent. Multiresult query modes only.
Item name in attribute table to use for class annotation angles. Values should be in degrees.
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.
Item name in attribute table to use for class annotation (i.e. labeling).
Maximum scale at which the layer is labeled.
Minimum scale at which the layer is labeled.
Sets context for labeling this layer, for example:
LABELREQUIRES ([orthoquads] != 1)
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 layers STATUS and then evaluated as normal. Logical operators AND and OR can be used.
Item name in attribute table to use for class annotation sizes. Values should be in pixels.
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).
Maximum scale at which this layer is drawn.
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.
Example:
METADATA title "My layer title" author "Me!" END
Minimum scale at which this layer is drawn.
Short name for this layer. Limit is 20 characters. 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.
Sets the color index to treat as transparent for raster layers.
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.
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. Currently the SCALE,BANDS and DITHER directives are supported for raster layers processed via the GDAL driver. This is further explained in the Raster HOWTO.
Example:
PROCESSING "SCALE_1=AUTO" PROCESSING "SCALE_2=AUTO" PROCESSING "SCALE_3=AUTO" PROCESSING "BANDS=3,2,1,4"
Signals the start of a PROJECTION object.
Sets context for displaying this layer (see LABELREQUIRES).
Sets the unit of CLASS object SIZE values (default is pixels). Usefull for simulating buffering.
Sets the current status of the layer. Often modified by MapServer itself. Default turns the layer on permanently.
Item to use for feature specific styling. This is *very* experimental and OGR only at the moment.
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.
Full filename for the index or tile definition for this layer. Similar to an ArcInfo library index, this shapefile contains polygon features for each tile. The item that contains the location of the tiled data is given using the TILEITEM parameter. If the DATA parameter contains a value then it is added to the end of the location. If DATA is empty then the location should contain the entire filename.
Item that contains the location of an individual tile, default is "location".
Sensitivity for point based queries (i.e. via mouse and/or map coordinates). Given in TOLERANCEUNITS with a default of 3 pixels. To restrict polygon searches so that the point must occur in the polygon set the tolerance to zero.
Units of the TOLERANCE value. Default is pixels.
Sets the transparency level of all classed pixels for a given layer. The value is a percentage (0-100) where 100 is opaque and 0 is fully transparent.
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.
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. Annotation means that a label point will be calculated for the features, but the feature itself will not be drawn although a marker symbol can be optionally drawn. this allows for advanced labeling like numbered highway shields. Points are labeled at that point. Polygons are labeled first using a centroid, and if that doesn't fall in the polygon a scanline approach is used to guarantee the label falls within the feature. Lines are labeled at the middle of the longest arc in the visible portion of the line. Query only means the layer can be queried but not drawn.
In order to differentiate between POLYGONs and POLYLINEs (which do not exist as a type), simply respectively use or ommit 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, 2 points that define the smallest square that can contain it. These 2 points are the two opposite corners of said box.
Defines thematic classes for a given layer and each layer must have at least one class. In cases with more than one class, membership is determined using attribute values and expressions. Starts with the keyword CLASS and terminates with the keyword END.
Color to use for non-transparent symbols.
Color to use for drawing features.
Enables debugging of the class object. Verbose output is generated and sent to the standard error output (STDERR) or the MapServe r logfile if one is set using the LOG parameter in the WEB object.
Three types of expressions are now supported to define class membership. String comparisons, regular expressions, and simple logical expressions. If no expression is given, then all features are said to belong to this class.
String comparisons are case sensitive and are the fastest to evaluate. No special delimiters are necessary although string must be quoted if they contain special characters. (As a matter of good habit, it is recommended you quote all strings).
Regular expressions function just like previous versions of MapServer. However, you must now delimit a regular expression using /regex/. No quotes should be used.
Logical expressions allow you to build fairly complex tests based on one or more attributes and therefore are only available with shapefiles. Logical expressions are delimited by parentheses "(expression)". Attribute names are delimited by square brackets "[ATTRIBUTE]". These names are case sensitive and must match the items in the shapefile. For example: EXPRESSION ([POPULATION] > 50000 AND '[LANGUAGE]' eq 'FRENCH') ... The following logical operators are supported : =,>,<,<=,>=,=,or,and,lt,gt,ge,le,eq. As you might expect this level of complexity is slower to process.
String comparisons and regular expressions work from the classitem defined at the layer level. You may mix expression types within the different classes of a layer.
Signals the start of a JOIN object.
Signals the start of a LABEL object.
Maximum size in pixels to draw a symbol. Default is 50.
Minimum size in pixels to draw a symbol. Default is 0.
Name to use in legends for this class. If not set class won't show up in legend.
Color to use for outlining polygons and certain marker symbols. Line symbols do not support outline colors.
Height, in pixels, of the symbol/pattern to be used. Only useful with scalable symbols. Default is 1.
Signals the start of a STYLE object. A class can contain multiple styles.
The symbol name or number to use for all features if attribute tables are not used. The number is the index of the symbol in the symbol file, starting at 1, the 5th symbol in the file is therefore symbol number 5. You can also give your symbols names using the NAME keyword in the symbol definition file, and use those to refer to them. Default is 0, which results in a single pixel, single width line, or solid polygon fill, depending on layer type.
Template file or URL to use in presenting query results to the user.
Static text to label features in this class with. This overrides values obtained from the LABELTIEM. The string may be given as an expression delimited using the ()'s. This allows you to concatenate multiple attributes into a single label. For example: ([FIRSTNAME],[LASTNAME]).
You can also "stack" 2 symbols to achieve interesting effects. You define the second symbol, which effectively sits "on top" of the symbol normally defined above.
The following parameters allow you to define the symbol, and they are equivalent to their non-overlay counterparts:
OVERLAYBACKGROUNDCOLOR
OVERLAYCOLOR
OVERLAYOUTLINECOLOR
OVERLAYSIZE
OVERLAYMINSIZE
OVERLAYMAXSIZE
OVERLAYSYMBOL
This object holds parameters for symbolization. Multiple styles may be applied within a class. This object is new in 4.0 and is intended to seperate logic from looks. The final intent is to have named styles (Not yet supported) that will be re-usable through the mapfile. This is the new, preferred way of defining the appearance of an object, notably a class.
Should TrueType fonts be antialiased.
Color to use for non-transparent symbols.
Color to use for drawing features.
Maximum size in pixels to draw a symbol. Default is 50.
Minimum size in pixels to draw a symbol. Default is 0.
Offset values for shadows, hollow symbols, etc ...
Color to use for outlining polygons and certain marker symbols. Line symbols do not support outline colors.
Height, in pixels, of the symbol/pattern to be used. Only useful with scalable symbols. Default is 1.
The symbol name or number to use for all features if attribute tables are not used. The number is the index of the symbol in the symbol file, starting at 1, the 5th symbol in the file is therefore symbol number 5. You can also give your symbols names using the NAME keyword in the symbol definition file, and use those to refer to them. Default is 0, which results in a single pixel, single width line, or solid polygon fill, depending on layer type.
Defines inline features. You can use inline features when it's not possible (or too much trouble) to create a shapefile. Inline features can also be built via urls or forms. Starts with the keyword FEATURE and terminates with the keyword END.
A set of xy pairs terminated with an END, for example:
POINTS 1 1 50 50 1 50 1 1 END
Note that with POLYGON/POLYLINE layers POINTS must start and end with the same point (i.e. close the feature).
String to use for labeling this feature.
Defines how a legend is to be built. Legend components are built automatically from class objects from individual layers. Starts with the keyword LEGEND and terminates with the keyword END. The size of the legend image is NOT known prior to creation so be careful not to hard-code width and height in the <IMG> tag in the template file.
Color to initialize the legend with (i.e. the background).
Should the output image be interlaced? Default is [on]. This keyword is now depcrecated in favour of using the FORMATOPTION "INTERLACE=ON" line in the OUTPUTFORMAT declaration.
Signals the start of a LABEL object
Color to use for outlining symbol key boxes.
Where to place an embedded legend in the map. Default is lr.
Size of symbol key boxes in pixels. Default is 20 by 10.
Spacing between symbol key boxes ([y]) and labels ([x]) in pixels. Default is 5 by 5.
Tells MapServer to render this legend after all labels in the cache have been drawn. Useful for adding neatlines and similar elements. Default is false.
Is the legend image to be created.
Should the background color for the legend be transparent. This flag is now deprecated in favour of declaring transparency within OUTPUTFORMAT declarations. Default is off.
Defines a mechanism to map the results of a query. Starts with the keyword QUERYMAP and terminates with the keyword END.
Color in which features are highlighted. Default is yellow.
Size of the map in pixels. Defaults to the size defined in the map object.
Is the query map to be drawn ?
Sets how selected features are to be handled. Layers not queried are drawn as usual.
Normal: Draws all features according to the settings for that layer.
Hilite: Draws selected features using COLOR. Non-selected features are drawn normally.
Selected: draws only the selected features normally.
Defines how a specific join is handled. Starts with the keyword JOIN and terminates with the keyword END. Joins are defined within a query object.
Join item in the shapefile.
Unique name for this join. Required.
Name of XBase file (DBF, must be a full path) to join TO.
Template to use with one-to-many joins. The template is processed once for each record and can only contain substitutions for items in the joined table.
Join item in the table to be joined.
The type of join. Default is single (i.e. one-to-one).
Defines how reference maps are to be created. Starts with the keyword REFERENCE and terminates with the keyword END. Three types of reference maps are supported. The most common would be one showing the extent of a map in an interactive interface. It is also possible to request reference maps as part of a query. Point queries will generate an image with a marker (see below) placed at the query point. Region based queries will depict the extent of the area of interest. Finally, feature based queries will display the selection feature(s) used.
Color in which the reference box is drawn. Set any component to -1 for no fill. Default is red.
The spatial extent of the base reference image.
Full filename of the base reference image. Must be a GIF image.
Defines a symbol (from the symbol file) to use when the box becomes too small (see MINBOXSIZE and MAXBOXSIZE below). Uses a crosshair by default.
Defines the size of the symbol to use instead of a box (see MARKER above).
If box is smaller than MINBOXSIZE (use box width or height) then use the symbol defined by MARKER and MARKERSIZE.
If box is greater than MAXBOXSIZE (use box width or height) then draw nothing (Often the whole map gets covered when zoomed way out and it's perfectly obvious where you are).
Color to use for outlining the reference box. Set any component to -1 for no outline.
Size, in pixels, of the base reference image.
Is the reference map to be created? Default it off.
Defines how a scalebar should be built. Starts with the keyword SCALEBAR and terminates with the keyword END. Scalebars currently do not make use of TrueType fonts. The size of the scalebar image is NOT known prior to rendering, so be careful not to hard-code width and height in the <IMG> tag in the template file. Future versions will make the image size available.
Color to use for scalebar background, not the image background.
Color to use for drawing all features if attribute tables are not used.
Color to initialize the scalebar with (i.e. background).
Should output images be interlaced? Default is [on]. This keyword is now depcrecated in favour of using the FORMATOPTION "INTERLACE=ON" line in the OUTPUTFORMAT declaration.
Number of intervals to break the scalebar into. Default is 4.
Signals the start of a LABEL object
Color to use for outlining individual intervals. Set any component to -1 for no outline which is the default.
Where to place an embedded scalebar in the image. Default is lr.
For use with embedded scalebars only. Tells the MapServer to embed the scalebar after all labels in the cache have been drawn. Default is false.
Size in pixels of the scalebar. Labeling is not taken into account.
Is the scalebar image to be created, and if so should it be embedded into the image? Default is off. (Please note that embedding scalebars require that you define a markerset. In essence the scalebar becomes a custom marker that is handled just like any other annotation.)
Chooses the scalebar style. Valid styles are 0 and 1.
Should the background color for the scalebar be transparent. This flag is now deprecated in favour of declaring transparency within OUTPUTFORMAT declarations. Default is off.
Output scalebar units, default is miles. Used in conjunction with the map's units to develop the actual graphic. Note that decimal degrees are not valid scalebar units.
Defines how a web interface will operate. Starts with the keyword WEB and terminates with the keyword END.
URL to forward users to if a query fails. If not defined the value for ERROR is used
URL to forward users to if an error occurs. Ugly old MapServer error messages will appear if this is not defined
Template to use AFTER anything else is sent. Multiresult query modes only.
Template to use BEFORE everything else has been sent. Multiresult query modes only.
Path to the temporary directory fro writing temporary files and images. Must be writable by the user the web server is running as. Must end with a / or \ depending on your platform.
Base URL for IMAGEPATH. This is the URL that will take the web browser to IMAGEPATH to get the images.
File to log MapServer activity in. Must be writable by the user the web server is running as.
Maximum scale at which this interface is valid. When a user requests a map at a bigger scale, MapServer automatically returns the map at this scale. This effectively prevents user from zooming too far out.
Template to be used if above the maximum scale for the app, useful for nesting apps.
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.
Example:
METADATA title "My layer title" author "Me!" END
Minimum scale at which this interface is valid. When a user reuqests a map at a smaller scale, MapServer automatically returns the map at this scale. This effectively prevents the user from zooming in too far.
Template to be used if above the minimum scale for the app, useful for nesting apps.
Template file or URL to use in presenting the results to the user in an interactive mode (i.e. map generates map and so on ... )
To set up projections you must define two projection objects: one for the output image (In the MAP object) and one for each layer (In the LAYER objects) to be projected. Projection objects simply consist of a series of PROJ.4 keywords. Here is an example defining UTM zone 15, NAD83:
PROJECTION "proj=utm" "ellps=GRS80" "zone=15" "north" "no_defs" END
Geographic coordinates are defined as:
PROJECTION "proj=latlong" END
See the PROJ.4 user guides for complete descriptions of supported projections and coordinate systems.
This section discusses how output formats are defined and selected.
A map file may have zero, one or more OUTPUTFORMAT object declarations, defining available output formats supported including formats like PNG, GIF, JPEG, GeoTIFF and Flash (SWF).
If OUTPUTFORMAT sections declarations are not found in the map file, the following implicit declarations will be made. Only those for which support is compiled in will actually be available. The GeoTIFF depends on building with GDAL support, and the Flash (SWF) depends on compiling with support for the MING library.
OUTPUTFORMAT NAME gif DRIVER "GD/GIF" MIMETYPE "image/gif" IMAGEMODE PC256 EXTENSION "gif" END OUTPUTFORMAT NAME png DRIVER "GD/PNG" MIMETYPE "image/png" IMAGEMODE PC256 EXTENSION "png" END OUTPUTFORMAT NAME jpeg DRIVER "GD/JPEG" MIMETYPE "image/jpeg" IMAGEMODE RGB EXTENSION "jpg" END OUTPUTFORMAT NAME wbmp DRIVER "GD/WBMP" MIMETYPE "image/wbmp" IMAGEMODE PC256 EXTENSION "wbmp" END OUTPUTFORMAT NAME swf DRIVER "SWF" MIMETYPE "application/x-shockwave-flash" EXTENSION "swf" IMAGEMODE PC256 FORMATOPTION "OUTPUT_MOVIE=SINGLE" END OUTPUTFORMAT NAME GTiff DRIVER "GDAL/GTiff" MIMETYPE "image/tiff" IMAGEMODE RGB EXTENSION "tif" END
The name to use use in the IMAGETYPE keyword of the map file to select this output format.(optional)
The name of the driver to use to generate this output format. Some driver names include the definition of the format if the driver supports multiple formats. For GD the possible driver names are "GD/Gif", "GD/PNG", "GD/WBMP" and "GD/JPEG". For flash the driver is just called "SWF". For output through GDAL the GDAL shortname for the format is appeneded, such as "GDAL/GTiff". Note that PNG, JPEG and GIF output can be generated with either GDAL or GD (GD is generally more efficient).(manditory)
Selects the imaging mode in which the output is generated. Does matter for non-raster formats like Flash. Not all formats support all combinations. For instance GD/GIF supports only PC256. (optional)
PC256: Produced a pseudocolored result with up to 256 colors in the palette (traditional MapServer mode)
RGB: Render in 24bit Red/Green/Blue mode. Supports all colors but does not support transparency.
RGBA: Render in 32bit Red/Green/Blue/Alpha mode. Supports all colors, and alpha based transparency.
INT16: Render one band of data in 16 bit integer depth. Only works for RASTER layers (through GDAL) and WMS layers currently.
FLOAT32: Render one band of data in 32bit floating point depth. Only works for RASTER layers (through GDAL) and WMS layers currently.
Provide the mime type to be used when returning results over the web. (optional)
Provide the extension to use when creating files of this type. (optional)
Indicates whether transparency should be enabled for this format. Note that transparency does not work for IMAGEMODE RGB output. Not all formats support transparency (optional). When transparency is enabled for the typical case of 8-bit pseudocolored map generation, the IMAGECOLOR color will be marked as transparent in the output file palette. Any other map components drawn in this color will also be transparent, so for map generation with transparency it is best to use an otherwise unused color as the background color.
Provides a driver or format specific option. Zero or more FORMATOPTION statement may be present within a OUTPUTFORMAT declaration. (optional)
GD/JPEG: The "QUALITY=n" option may be used to set the quality of jpeg produced (value from 0-100).
GD/PNG: The "INTERLACE=[ON/OFF]" option may be used to turn interlacing on or off.
GD/GIF: The "INTERLACE=[ON/OFF]" option may be used to turn interlacing on or off.
GDAL/GTiff: Supports the TILED=YES, BLOCKXSIZE=n, BLOCKYSIZE=n, INTERLEAVE=[PIXEL/BAND] and COMPRESS=[NONE,PACKBITS,JPEG,LZW,DEFLATE] format specific options.
GDAL/*: All FORMATOPTIONs are passed onto the GDAL create function. Options supported by GDAL are described in the detailed documentation for each GDAL format.
New in MapServer 4.0, variables can be substituted within mapfile parameter values. At this time, cookie and CGI parameter values are supported. This allows mapserver mapfiles to be aware of a user's cookies (Good for implementing security), or non-mapserver request parameters (Good for integrating with other systems).
Syntax: '%' + variable name + '%'
Example 1. Connecting securely to a Spatial Database
You want to map some senstitive data held in a PostGIS database. The username and password to be used for the database connection are held in 2 cookies previously set by a seperate authentication mechanism, "uid" and "passwd".
CONNECTION "user=%uid% password=%passwd% dbname=postgis"
Example 2. Handling temporary files
You have a user based discovery application that generates shapefiles and stores them in a user's home directory on the server. The "username" comes from a cookie, the "filename" comes from a request parameter.
DATA "/home/%username%/tempshp/%filename%"
This feature is only available in the CGI version of MapServer through a mapfile pre-processor. If you are using MapScript, you will have to code the substitution logic into your application yourself (By writing your own pre-processor).
This section explains how to work with and define symbology in MapServer.
Symbol definitions can be included within the main MapFile or, more commonly, in a separate file. Symbol definitions in a separate file are designated using the SYMBOLSET keyword, as part of the Map Object. This recommended setup is ideal for re-using symbol definitions across multiple MapServer applications.
There are 3 main types of symbols in MapServer: Markers, Shadesets, and Lines.
Symbol 0 is always the degenerate case for a particular class of symbol. For points, symbol 0 is a single pixel, for shading (i.e. filled polygons) symbol 0 is a solid fill, and for lines, symbol 0 is a single pixel wide line.
Symbol definitions contain no color information, colors are set within CLASS objects.
There is a maximum of 64 symbols per file. This can be changed by editing mapsymbol.h and changing the value of MS_MAXSYMBOLS at the top of the file.
Should TrueType fonts be antialiased.
Character used to reference a particular TrueType font character. You'll need to figure out the mapping from the keyboard character to font character.
Sets the symbol to be filled with a user defined color (See the CLASS object). For marker symbols, if OUTLINECOLOR was specified then the symbol is outlined with it.
Name of TrueType font to use as defined in the FONTSET.
Given in pixels. This defines a distance between symbols for TrueType lines.
Image (GIF or PNG) to use as a marker or brush for type PIXMAP symbols.
Alias for this font to be used in CLASS objects
Signifies the start of the definition of points that make up a vector symbol or that define the x and y radius of an ellipse symbol. The end of this section is signified with the keyword END. Coordinates are given in pixels and define the default size of the symbol before any scaling. You can create non-contiguous paths by inserting negative coordinates at the appropriate place. For ellipse symbols you provide a single point that defines the x and y radius of an ellipse. Circles are created when x and y are equal.
Defines a dash style or pattern.
Sets a transparent color for the input GIF image for pixmap symbols, or determines whether all shade symbols should have a transparent background. For shade symbols it may be desirable to have background features "show through" a transparent hatching pattern, creating a more complex map. By default a symbol's background is the same as the parent image (i.e. color 0). This is user configurable.
vector: a simple drawing is used to define the shape of the symbol.
ellipse: radius values in the x and y directions define an ellipse.
pixmap: a user supplied GIF image will be used as the symbol.
truetype: TrueType font to use as defined in the FONTSET.
Here are some examples illustrating the various ways to create symbols in MapServer:
Example 3. Dashed Line
SYMBOL NAME 'dashed1' TYPE ELLIPSE POINTS 1 1 END FILLED true STYLE 10 5 5 10 END END
This creates a dashed line with 10 pixels on, 5 off, 5 on, 10 off ...
Example 4. TrueType font marker symbol
SYMBOL NAME "natcap" TYPE TRUETYPE FONT geo FILLED true ANTIALIAS true CHARACTER "r" END
This symbol is a star, used to represent the national capital, hence the name. The font name in defined in the FONTSET file. The code number "114" varies, you can use MS Windows' character map to figure it out, or guestimate.
Example 5. Vector triangle marker symbol
SYMBOL
NAME "triangle"
TYPE vector
POINTS
0 4
2 0
4 4
0 4
END
END
This is fairly straight forward. Note that to have 3 sides you need 4 points, hence the first and last points are identical.
Example 6. Non-contiguous vector marker symbol (Cross)
SYMBOL
NAME "cross"
TYPE vector
POINTS
2 0
2 4
-99 -99
0 2
4 2
END
END
This example draws a cross, that is 2 lines (vectors) that are not connected end-to-end (Like the triangle in the previous example). The negative values separate the two.
Example 7. Circle vector symbol
SYMBOL
NAME "circle"
TYPE ellipse
FILLED true
POINTS
1 1
END
END
A simple filled circle. Using non-equal values for the point will give you an actual ellipse.
Example 8. Downward diagonal fill
SYMBOL
NAME "downwarddiagonalfill"
TYPE vector
TRANSPARENT 0
POINTS
0 1
1 0
END
END
| Add a Comment |