New answers tagged

0

At the moment the answer is no, but it may be possible to use dynamic scaling and classification together soon. See the ticket https://github.com/mapserver/mapserver/issues/5830#issuecomment-516913638 for details. Perhaps you can get more pressure to include this enhancement into version 7.6 by adding a comment and volunteering to test.


0

My issue was I did not include the VALIDATION Block. Once I created a VALIDATION block and validated the parameters it worked immediately


2

Neither the WMS protocol nor any of the other MapServer APIs have a mechanism to automatically set the map position and zoom level based on a geometry object. You have to retrieve the bounding box with a separate query (through WFS, or directly to the database).


1

After struggling one week I'm able to configure tilecache in Linux o.s. I also tested alongwith OL3 and working fine. The main problem is that the it is not reading tilecache.cfg files from correct path. So you have to give your absolute path for cfg files wherever required like in tilecache.cgi and services.py files. For mapserver service the mapscript ...


0

The TileCache installation instructions have one more step: Permit CGI execution in the TileCache directory. For example, if TileCache is to be run with Apache, the following must be added in your Apache configuration, where /var/www/tilecache is the directory resulting from the code extraction. On Debian, this is typically /usr/lib/cgi-bin. <...


0

Allright, forget that question. ¶ The answer is: Not the WMS-URL should be opened in the client but the url to the mapcache-software: ¶ e.g.: ¶ var wmsSource = new ImageWMS({ url: 'http://blabla/mapcache/?', params: {'LAYERS': 'kachelnkanal'}, serverType: 'mapserver', crossOrigin: 'anonymous' }); var wmsLayer = new ImageLayer({ ...


Top 50 recent answers are included