Both SYMBOL 0 + SIZE 1 and WIDTH 1 should work, but why don't
you want to use WIDTH?
WIDTH is now the recommended way of specifying the width of
lines. It is also used in
http://mapserver.org/mapfile/symbology/construction.html
Håvard
On 8/28/2013 4:29 PM, andy wrote:
It still draw's
The implementation of GAP has been fixed (center to center
distance between symbols), and so has the calculation of
symbol height.
I guess that the following should work:
STYLE
SYMBOL wavy_line
WIDTH 1
SIZE 2
GAP -6
COLOR 0 0 0
END
Since you have y values from -1 to 1, and x values
Given that there's alot of undefined behavior with vector symbols, the
documentation for anchorpoint is pretty clear about what is supported:
quote
ANCHORPOINT can be used with SYMBOLs of TYPE ellipse, pixmap, svg,
truetype and vector. To ensure proper behaviour for vector symbols,
the left and
Thanks Havard, for the pointer to the answer and explanation of the ratio
between SIZE and GAP. I feel like I will use that a lot.
Thanks Thomas for your clarification - my misunderstanding was regarding
the negative values, I hadn't fully internalized that y=0 was the top of
the symbol.
Tanya
Hello,
I have a number of geotiffs which are currently using epsg:4326 and I would
like to output a region using epsg:3857.
I am new to mapserver but from what I have read the way achieve this is by
setting the projection of the map to epsg:3857 and the layer to epsg:4326.
When I set the
David,
Take a look at the map extent and units. They should be the units used by your
output spatial reference system.
In your current map file, you have DD for the units, for 3857, they should be
meters. You will also want to express your extent in 3857 coords.
David.
From:
On 2013-08-29 12:00 PM, David Power wrote:
Hello,
I have a number of geotiffs which are currently using epsg:4326 and I
would like to output a region using epsg:3857.
I am new to mapserver but from what I have read the way achieve this is
by setting the projection of the map to epsg:3857
Hi,
i ran into s small problem with setting up a WCS service on umn
mapserver 6.2 and newer.
When requesting the capabilities for VERSION=1.0.0 i get the following
Warning printed to the Capabilities Doc:
?xml version='1.0' encoding=ISO-8859-1 standalone=no ?
WCS_Capabilities
version=1.0.0
Thanks David,
Using the correct units seems to have fixed the problem.
@Jeff : Thanks for pointer, now that I have re-read it all makes sense
Cheers
David
On 29 Aug 2013, at 16:43, Fawcett, David (MNIT) wrote:
David,
Take a look at the map extent and units. They should be the units
Le jeudi 29 août 2013 18:56:48, Peter Freimuth a écrit :
Hi,
i ran into s small problem with setting up a WCS service on umn
mapserver 6.2 and newer.
When requesting the capabilities for VERSION=1.0.0 i get the following
Warning printed to the Capabilities Doc:
Any idea what is missing.
Hello,
A year and a half ago I inquired about how to deal with labeling complex
polygons. The basic issue is that the center of the bbox does not always fall
within the boundary of complex polygons. At the time one of the developers
mentioned that using the bbox is much faster than trying to
11 matches
Mail list logo
