Contents
How does the connection pooling work in MapServer?
Connection pooling will allow MapServer to share the handle to an open database or layer connection throughout a single map draw process. Additionally, if you have FastCGI enabled, the connection handle will stay open indefinitely, or according to the options specified in the FastCGI configuration.
How to use a native filter in MapServer?
The string is simply a MapServer expression: Native filters are supported through the NATIVE_FILTER PROCESSING key: FILTER ‘where id=234’. But this is no longer supported. Item to use with simple FILTER expressions. OGR and shapefiles only. Template to use after a layer’s set of results have been sent.
How does a composite block in MapServer work?
The options defined inside the COMPOSITE block will determine how this merging should be done (e.g. by appying opacity, composition operator, or pixel filters) Database connection string to retrieve remote data.
Which is the debug option in Apache MapServer?
Apache users will see timing details for drawing in Apache’s error_log file. Requires MapServer to be built with the DEBUG=MSDEBUG option (–with-debug configure option). Deprecated since version 6.0: use LAYER METADATA instead. Switch to allow MapServer to return data in GML format.
Where do I find the layer name in MapServer?
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,myversion”.
What is Sde connection string in MapServer 7.0?
An SDE connection string consists of a hostname, instance name, database name, username and password separated by commas. MapServer’s native SDE driver was removed for the MapServer 7.0 release (see discussion ). SDE support can still be accessed through the OGR driver.