Personal tools
You are here: Home → Documentation → References
Navigation
 

18. Web

Document Actions
Up one level
Next: Article Info Previous: Variable Substitution  
Defines how a web interface will operate. Starts with the keyword WEB and terminates with the keyword END.
EMPTY [url]
URL to forward users to if a query fails. If not defined the value for ERROR is used.
ERROR [url]
URL to forward users to if an error occurs. Ugly old MapServer error messages will appear if this is not defined
FOOTER [filename]
Template to use AFTER anything else is sent. Multiresult query modes only.
HEADER [filename]
Template to use BEFORE everything else has been sent. Multiresult query modes only.
IMAGEPATH [path]
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.
IMAGEURL [path]
Base URL for IMAGEPATH. This is the URL that will take the web browser to IMAGEPATH to get the images.
LOG [filename]
File to log MapServer activity in. Must be writable by the user the web server is running as.
MAXSCALE [double]
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.
MAXTEMPLATE [file|url]
Template to be used if above the maximum scale for the app, useful for nesting apps.
METADATA

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
MINSCALE [double]
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.
MINTEMPLATE
Template to be used if above the minimum scale for the app, useful for nesting apps.
OUTPUTFORMAT [mime-type]
Format of the query output. Default is "text/html". This is experimental, the use of the OUTPUTFORMAT object is recommended instead.
TEMPLATE [filename|url]
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 ... )
Next: Article Info Previous: Variable Substitution  
by Jeff McKenna — last modified 2005-12-15 19:52

MINSCALE/MAXSCALE - terminology

Posted by Håvard Tveite at 2005-07-19 04:15
Mapserver uses the opposite to normal terminology for scale.
Normal terminology is that 1:1000 is a *larger* scale than 1:100000. This should be stated explicitly in the documentation. Suggestions for new explanations:

MAXSCALE [double]
Minimum scale at which this interface is valid (Mapserver terminology is the opposite of normal terminology for scales). When a user requests a map at a smaller scale, MapServer automatically returns the map at this scale. This effectively prevents the user from zooming too far out.

MINSCALE [double]
Maximum scale at which this interface is valid (Mapserver terminology is the opposite of normal terminology for scales). When a user reuqests a map at a larger scale, MapServer automatically returns the map at this scale. This effectively prevents the user from zooming in too far in.

An alternative is to "clean" this up by changing the the keywords to MINSCALE_DENOMINATOR and MAXSCALE_DENOMINATOR.

Mapserver 5 - changes

Posted by Håvard Tveite at 2007-09-27 04:55
MINSCALE/MAXSCALE has in Mapserver 5 been changed to MINSCALEDENOM/MAXSCALEDENOM. See the "MapServer 4.10 to 5.0 Migration Guide".
Powered by Plone