[Tilecache] tlecache and ms4w

[John Cole]

Christopher,
  I was hoping that by using a MapServer layer, it would prevent some edge
problems with some lines and markers getting cut off or not matching up;
thicker lines that cross a tile edge at an angle tend to have chunks cut out
of them, and markers that have images (in my case highway shields) get cut
off when drawn near a tile edge.  It was my understanding that a MapServer
layer would get cut up by TC after it was rendered by MS from a larger
image.

John

-----Original Message-----
From: Christopher Schmidt [mailto:crschmidt at metacarta.com] 
Sent: Saturday, March 03, 2007 10:14 AM
To: John Cole
Cc: 'tilecache at openlayers.org'
Subject: Re: [Tilecache] tlecache and ms4w

On Fri, Mar 02, 2007 at 03:53:05PM -0600, John Cole wrote:
> I'm trying to get tilecache to work with MS4W 4.10
> 
> Are there any instructions or hints on how to get this configured?  I can
> get TC to work with a separate installation of Python 2.5 but the MS4W
> python mapscript isn't available, and I haven't played with python
mapscript
> yet.  Any pointers would be greatly appreciated.

I'd recommend using the WMSLayer instead of the MapServer layer. There
isn't any real difference, and the WMSLayer is probably easier to set
up. (I use the WMSLayer for most everything these days.)  

Regards,
-- 
Christopher Schmidt
MetaCarta

-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.6/709 - Release Date: 3/3/2007
8:12 AM
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.6/709 - Release Date: 3/3/2007
8:12 AM
 
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.