<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: [UMN_MAPSERVER-USERS] Rename: Getting DBF data for symbology</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>I also use hatch-style symbology, but I will define classes that have lines only running in one direction, e.g. vertical, horizontal, diagonal-left, and diagonal-right, and combinations of these directions (in combination with different colors). This will help even more to distinguish between classes.<BR>
Note that you may have to specify "TRANSPARENCY 100", in order for your hatch symbology to render as transparent. If I don't, my hatch has an opaque white background.<BR>
<BR>
regards,<BR>
<BR>
Jacob<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: UMN MapServer Users List on behalf of Todd Harris<BR>
Sent: Tue 10/16/2007 09:21<BR>
To: MAPSERVER-USERS@LISTS.UMN.EDU<BR>
Subject: Re: [UMN_MAPSERVER-USERS] Rename: Getting DBF data for symbology<BR>
<BR>
I have recently had the same problem with overlapping polygons at the<BR>
CLASS level, I solved it by using a hatch symbol that had a minimum<BR>
spacing value, thus allowing linework to appear through the hatching. It<BR>
will have a slight affect on the colour of the polygon on top but works<BR>
well.<BR>
<BR>
<BR>
<BR>
STYLE<BR>
<BR>
SYMBOL 'hatch135'<BR>
<BR>
OUTLINECOLOR 0 0 0<BR>
<BR>
COLOR 255 200 255 # light pink<BR>
<BR>
END #STYLE<BR>
<BR>
<BR>
<BR>
Todd<BR>
<BR>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<BR>
<BR>
-----Original Message-----<BR>
From: UMN MapServer Users List [<A HREF="mailto:MAPSERVER-USERS@LISTS.UMN.EDU">mailto:MAPSERVER-USERS@LISTS.UMN.EDU</A>] On<BR>
Behalf Of Fawcett, David<BR>
Sent: Monday, 15 October 2007 9:39 PM<BR>
To: MAPSERVER-USERS@LISTS.UMN.EDU<BR>
Subject: Re: [UMN_MAPSERVER-USERS] Rename: Getting DBF data for<BR>
symbology<BR>
<BR>
<BR>
<BR>
I believe that transparency/opacity currently is only available at the<BR>
layer level, not the class level as Hayden appears to want. <BR>
<BR>
<BR>
<BR>
If you really need the transparency option, you could break out your<BR>
classes into separate layers. This would allow you to use transparency,<BR>
but would of course multiply the number of layers and may give you a<BR>
very small performance hit (which may likely be negligible). <BR>
<BR>
<BR>
<BR>
David. <BR>
<BR>
-----Original Message-----<BR>
From: UMN MapServer Users List<BR>
[<A HREF="mailto:MAPSERVER-USERS@LISTS.UMN.EDU">mailto:MAPSERVER-USERS@LISTS.UMN.EDU</A>] On Behalf Of Mevima Winn<BR>
Sent: Friday, October 12, 2007 12:23 PM<BR>
To: MAPSERVER-USERS@LISTS.UMN.EDU<BR>
Subject: Re: [UMN_MAPSERVER-USERS] Rename: Getting DBF data for<BR>
symbology<BR>
<BR>
There are a couple of ways.<BR>
<BR>
<BR>
<BR>
First is to set a transparency level, if the polygons have to be<BR>
solid. Underlying polygon doesn't have to have any, while the top<BR>
polygon can have any transparency level you want - probably somewhere<BR>
between 40 and 60% if you want both to be approximately equally visible.<BR>
<BR>
<BR>
<BR>
Or you can simply set an OUTLINECOLOR and no COLOR, which means<BR>
you will get an outline and no fill, which will show any underlying<BR>
polygons as long as they don't directly overlap the same lines. Any<BR>
overlapping lines can be identified by making the outline line thicker<BR>
and a different color, so whoever is viewing the map can see that there<BR>
are multiple polygons there.<BR>
<BR>
<BR>
<BR>
Regards,<BR>
<BR>
-Mevima<BR>
<BR>
-----Original Message-----<BR>
From: UMN MapServer Users List<BR>
[<A HREF="mailto:MAPSERVER-USERS@LISTS.UMN.EDU">mailto:MAPSERVER-USERS@LISTS.UMN.EDU</A>]On Behalf Of Hayden Fisher<BR>
Sent: Thursday, October 11, 2007 10:47 PM<BR>
To: MAPSERVER-USERS@LISTS.UMN.EDU<BR>
Subject: [UMN_MAPSERVER-USERS] Rename: Getting DBF data<BR>
for symbology<BR>
<BR>
Also polygons on top of polygons, is there a way to make<BR>
it so you can see both?<BR>
<BR>
<BR>
<BR>
<BR>
This e-mail and any files transmitted with it are intended only for the use of the addressee(s). It may contain information that is confidential and privileged, in which case neither is intended to be waived or lost by mistaken delivery to you. If you are not an intended recipient, any use, interference with, disclosure, distribution or copying of this material is unauthorised and prohibited. If you receive this e-mail in error, please notify the sender by return e-mail and delete the message and any attachments from your system. Unless specifically indicated, this e-mail does not constitute formal advice or commitment by the sender or the Western Australian Land Information Authority (Landgate). Information in this message not relating to the official business of Landgate shall be understood as neither given nor endorsed by it. It is your responsibility to check any attachments for viruses and defects before opening or sending them on. Landgate's liability is limited to re-supplying affected attachments.<BR>
<BR>
<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>