Re: [mapserver-users] WMS rendering

2014-10-21 Thread Francesco Palermo
No, I don't get any error message. I tried to remove UNITS on mapfile but it doesn't change anything. Then I tried to remove SIZEUNITS from the layer and the map finally appears! Thanks to all! Now I'll try to overlay this map on the Google Maps ;) Francesco Il 17/10/2014 11:03, Håvard

Re: [mapserver-users] WMS rendering

2014-10-17 Thread Håvard Tveite
Hi Francesco, Do you get any error messages? Your map file looks a bit like the example from the WMS Server documentation (http://mapserver.org/ogc/wms_server.html), and that should be a good starting point. To make it easier to find the source of your problems, I suggest that you start with

Re: [mapserver-users] WMS rendering

2014-10-17 Thread Rahkonen Jukka (Tike)
Hi, I tested your mapfile and I believe that you indeed have trouble with 0.0019 meters wide box symbol that does not show easily. If you leave out sizeunits or use the default unit pixels and size of around 10 the symbol should show at all scales. Of course you can use meters as well with

[mapserver-users] WMS rendering

2014-10-16 Thread Francesco Palermo
Hello, I'm experimenting the use of Mapserver as WMS and I'm encountering some problems on map rendering. I'm using a shapefile as a map source and it's a map of points (generated by a csv using ogr2ogr - Could I use directly csv with Mapserver? I don't know). I can't get the rendering of

Re: [mapserver-users] WMS rendering

2014-10-16 Thread Jörg Thomsen
Hello Francesco, no error-message, only a blank image? What's in the error-log? The MS_ERRORFILE ist set in httpd.conf? I think symbol is veryvery small. Try = 1. You can use a csv-file in MapServer via OGR :) http://mapserver.org/input/vector/ogr.html Jörg Am 16.10.2014 um 17:04 schrieb

Re: [mapserver-users] WMS rendering

2014-10-16 Thread thomas bonfort
sizeunits meters along with size 0.0019 is very probably false unless you're mapping microscopic particles :) try removing the sizeunits parameter completely and setting size to something visible in pixels (e.g. 3-5), once that is working you can start looking into scale-dependant rendering with