Interesting article in GeoInformatics (December 2009) entitled "Geoprocessing in the Clouds". The authors implement the 52North Web Processing Service on Google's and Amazon's cloud services.
They compare response times for both implementations and find that both scale well.
A more detailed paper describing the project can be found on the 52North website.
Tuesday 8 December 2009
Two contrasting views of GeoWeb processing
Now my MSc is done and dusted, I've decided to keep the blog going, focussing on the OGC's Web Processing Service.
I came across a couple of quotes recently. First from Jack Dangermond, ESRI CEO:
"So I think even 45 years ago when we were first inventing computer mapping at Harvard, our first attempts were to make beautiful maps. They weren't very beautiful; they were pretty crude. But very quickly thereafter, we moved from mapping into analytics, spatial decision-making to support land use planning and business planning of various sorts. So I think if you're asking me where will the web and the geospatial world move, it will be from simple map displays to analytics on the web. It'll move from simply a basemap with overlays on it to the notion of multiple distributed services that do spatial analysis, but combine various kinds of spatial data together and serve it back out as visualization communications."
full article...
And from an article on the Chrome JavaScript engine on the Spatial Miscellany blog:
"Chrome isn’t the only web browser to recognize the importance of working with JavaScript heavy web sites, for example, much work is being done on a new JavaScript engine for Firefox. Perhaps in the future, as this approach gains support, spatial analysis functionality can move from the server to the client, which would make for a more engaging web mapping experience?" full article...
So processing via services or on the client...?
I came across a couple of quotes recently. First from Jack Dangermond, ESRI CEO:
"So I think even 45 years ago when we were first inventing computer mapping at Harvard, our first attempts were to make beautiful maps. They weren't very beautiful; they were pretty crude. But very quickly thereafter, we moved from mapping into analytics, spatial decision-making to support land use planning and business planning of various sorts. So I think if you're asking me where will the web and the geospatial world move, it will be from simple map displays to analytics on the web. It'll move from simply a basemap with overlays on it to the notion of multiple distributed services that do spatial analysis, but combine various kinds of spatial data together and serve it back out as visualization communications."
full article...
And from an article on the Chrome JavaScript engine on the Spatial Miscellany blog:
"Chrome isn’t the only web browser to recognize the importance of working with JavaScript heavy web sites, for example, much work is being done on a new JavaScript engine for Firefox. Perhaps in the future, as this approach gains support, spatial analysis functionality can move from the server to the client, which would make for a more engaging web mapping experience?" full article...
So processing via services or on the client...?
Subscribe to:
Posts (Atom)