I haven't used tilecache for this, I know someone that did rent about $60k worth of EC2 time to cache a bunch of tiles; I could find out more specifics on this (it was months ago). I do realize it's not a 5 minute solution; but this still makes more sense to me than trying to create the "rc5des <a href="http://distributed.net">distributed.net</a>" of imagery tiling.<br>
<br><div class="gmail_quote">On Wed, Dec 9, 2009 at 9:48 AM, Jeffrey Johnson <span dir="ltr"><<a href="mailto:ortelius@gmail.com" target="_blank">ortelius@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>> seamless has WMS services; they're not tiled.<br>
><br>
> If you want them tiled get a bunch of hardware, stick tilecache on it and<br>
> serve WMS-C tiles.<br>
<br>
</div>Have you tried to do this on any reasonable scale? You would bring<br>
their hardware to its knees with a handful of tilecache_seed.py<br>
requests if you were not banned from making more requests very<br>
quickly.<br>
<div><br>
>OR continue to pressure USGS to do it.<br>
<br>
</div>Could be that they will do it.<br></blockquote><div><br>I think it's worth a try. I don't deal with non-defense much; but NGA has basically the same administrative structure as USGS (from what I can tell, although USGS is more progressive); often it's just finding the right person and establishing the requirements. From a technical standpoint they have most of what they need to do it; it's more an aspect of them agreeing to the business case/requirements.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>
> Right now I still don't see what's compelling about tiling NAIP.<br>
</div><br>Its not NAIP per se, its about having a reasonable archive of imagery<br>
that can actually be used by people to plug into their web apps in a<br>
plug and play fashion similar to the way people use the Google Maps or<br>
Bing APIs. The original OAM service was great where it had coverage,<br>
but many people were simply not interested in using it when it did NOT<br>
have coverage where they wanted it ... even though such imagery<br>
existed for free out from various sources.<br>
<br>
The point is to have a service that people can actually just use to do<br>
useful things ... not a committee of a bunch of people talking about<br>
how to organize OTHER people to help them create a service that they<br>
can actually do useful things with.<br></blockquote><div><br>I agree, and this is where I'd like to see it go. Establishing a baseline of 15m landsat is sound in that it works well for many purposes and paves the way for your 1m/0.5m imagery. Because there really is a jump there. Getting 10m imagery when you have 15m isn't much more useful. Having 2m instead of 15m is significantly more useful. <br>
<br>I don't think tilecache is a magic bullet (it might suck), but I like the basic model of absorbing WMS and serving them out as tiles. It seems more feasible than a lot of other proposals on here.<br><br>Backtracking a bit, I agree the distributed concept is the right one; but I think doing it with large trusted supernodes (more of a federated model) is much more sensible than a truly distributed one.<br>
<br>Incidentally, does anyone have any contacts at NASA? They host a lot of imagery albeit at smaller scales.<br><br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Jeff<br>
<div><div></div><div><br>
_______________________________________________<br>
talk mailing list<br>
<a href="mailto:talk@openaerialmap.org" target="_blank">talk@openaerialmap.org</a><br>
<a href="http://openaerialmap.org/mailman/listinfo/talk_openaerialmap.org" target="_blank">http://openaerialmap.org/mailman/listinfo/talk_openaerialmap.org</a><br>
</div></div></blockquote></div><br>