FYI: http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=4782703
Sort of antithesis to WPS. What I'm playing with is creating a distributed architecture for web mapping that, on the back end, handles petabytes of data but allows for insanely high traffic bursts. WMS and WPS don't quite hack it. So, you push the basemap rendering back further away from the user and any analysis and computation closer towards the user. Google's solved some of these issues but they only have one static basemap with a very limited set of features. They also are able to rely on essentially infinite processing power. They also don't provide for any real analysis (yet). What I'm trying to piece together is a system that lets privileged users combine layers and design and generate a tile cache rapidly in order to support bursts in traffic. For example, the USGS earthquake.usgs.gov site typically sees 250K hits per second immediately following an earthquake event. Currently, maps on that site are generated as static images that get pushed out to Akamai. I definitely have enough for an MS - especially in CompSci. But coming up with a Geography question is much tougher. -Eric -=--=---=----=----=---=--=-=--=---=----=---=--=-=- Eric B. Wolf 720-209-6818 USGS Geographer Center of Excellence in GIScience PhD Student CU-Boulder - Geography On Wed, Mar 11, 2009 at 3:07 PM, Raj Singh <[email protected]> wrote: > Web Processing Service > http://www.opengeospatial.org/standards/wps > --- > Raj > > > On Mar 11, at 12:58 PM, Sean Gillies wrote: > >> "OGC Web Pipe Service" > > > _______________________________________________ > Geowanking mailing list > [email protected] > http://geowanking.org/mailman/listinfo/geowanking_geowanking.org > _______________________________________________ Geowanking mailing list [email protected] http://geowanking.org/mailman/listinfo/geowanking_geowanking.org
