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 distributed.net" of imagery tiling.
On Wed, Dec 9, 2009 at 9:48 AM, Jeffrey Johnson <[email protected]> wrote: > > seamless has WMS services; they're not tiled. > > > > If you want them tiled get a bunch of hardware, stick tilecache on it and > > serve WMS-C tiles. > > Have you tried to do this on any reasonable scale? You would bring > their hardware to its knees with a handful of tilecache_seed.py > requests if you were not banned from making more requests very > quickly. > > >OR continue to pressure USGS to do it. > > Could be that they will do it. > 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. > > Right now I still don't see what's compelling about tiling NAIP. > > Its not NAIP per se, its about having a reasonable archive of imagery > that can actually be used by people to plug into their web apps in a > plug and play fashion similar to the way people use the Google Maps or > Bing APIs. The original OAM service was great where it had coverage, > but many people were simply not interested in using it when it did NOT > have coverage where they wanted it ... even though such imagery > existed for free out from various sources. > > The point is to have a service that people can actually just use to do > useful things ... not a committee of a bunch of people talking about > how to organize OTHER people to help them create a service that they > can actually do useful things with. > 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. 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. 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. Incidentally, does anyone have any contacts at NASA? They host a lot of imagery albeit at smaller scales. > Jeff > > _______________________________________________ > talk mailing list > [email protected] > http://openaerialmap.org/mailman/listinfo/talk_openaerialmap.org >
_______________________________________________ talk mailing list [email protected] http://openaerialmap.org/mailman/listinfo/talk_openaerialmap.org
