[Tilecache] Virtual Earth compatible TC-cache

[Christopher Schmidt]

On Tue, Feb 12, 2008 at 03:48:19PM +0100, Steven M. Ottens wrote:
> Hi all,
> 
> Once I finished it, I realised that it is actually quite a useless piece 
> of code. There is hardly any asiteuation where you want to store the 
> cache inside TC as VE-tiles without exposing them to the outer world. So 
> I decided to write a service instead. The will take a request with a 
> quadkey and calculate the row and column in epsg:900913:
> A typical request would be
> http://steef/tilecache.py?ve=true&layer=hoogtes&tile=120
> 
> where ve=true triggers the VETMS service in Service.py
> layer=hoogtes gives yoou the layer
> tile=120 gives you the quad key number.
> 120 in this case means z= 3, x=4 and y=5
> 
> In virtual earth you can add a tilecache-based layer this way:
> var tileSourceSpec = new VETileSourceSpecification("ahn", 
> "http://steef/tilecache.py?ve=true&layer=hoogtes&tile=%4");
> 
> Once again the only reason why you want to use this is if you're somehow 
> stuck with the VE-client, instead of a more friendly one like OpenLayers.
> 
> Attached the VETMS service also you need to add the following lines to 
> Service.py
>       elif params.has_key("ve") and \
>             params['ve'] == "true":
>            from TileCache.Services.VETMS import VETMS
>            tile = VETMS(self).parse(params, path_info, host)
> 
> just above:
>       else:
>            from TileCache.Services.TMS import TMS
>            tile = TMS(self).parse(params, path_info, host)
> (line 173)

Can you turn this into a patch? checkout a copy of svn, add your file
via svn add, make the above change, and then 'svn diff' and send it ot
the list? I'll try and get it in if you do.

Regards,
-- 
Christopher Schmidt
MetaCarta