In areas that someone else has already viewed it should be blazing fast,
as it's automatically cached by squid. Since OpenLayers requests tiles
from WMS directly, in the same way every time, simply standing squid in
front of GeoServer turns it in to a tiling engine similar to Google Maps.
The other thing I love about OpenLayers is that it's great to use as a
developer. After Google Maps hit a number of projects rushed to
replicate the ajax feel. But that missed what was actually most
exciting about google maps for me - that it became super easy for anyone
to make their own map.
OpenLayers extends that ease, but takes it even more open, allows for
even more innovation in mixing and mashing the map. It uses standard
SLD, so a client could specify a different way to view the map. And I
hope they get WFS-T support some time, so that users can edit the base
Anyways, I'll stop rambling, but it's a great piece of technology. Read
on for details on where to get it.
applications on the Web. OpenLayers offer offers the ability to
display a number of different types of data in a configurable mapping
On behalf of the OpenLayers development team, I have the honor and
pleasure of presenting version 1.0 of OpenLayers.
Development continues at a fast pace. Currently, the development
branch of OpenLayers supports:
* ka-Map data
* WorldWind data
* Untiled WMS Requests
* GeoRSS data
Our next release will support drawing and reprojection of vector data on
* Google Maps
* Yahoo Maps
* Microsoft Virtual Earth
One of the many goals of OpenLayers is to allow users to use one API,
and one look and feel, but display data from any source. To that end, we
have created a system which allows for any data provider to create their
own layers to be displayed alongside any others in OpenLayers. The API
is inspired by the Google Maps API, designed to make the simple things
easy, and the difficult things possible.
Development of OpenLayers is currently funded in part by MetaCarta: