OpenLayers Blog

All the maps that are fit to blog

OpenLayers 3 on GitHub

June 30th, 2010 by Tim Schaub · 2 Comments

In recent discussion on the OpenLayers development list, we decided to start working towards the next major version of OpenLayers. During a subsequent meeting on irc, we chose to use git for working towards v3 and are hosting a central repository on GitHub. Anyone interested in helping us in the OpenLayers 3 effort is encouraged to fork the repository, make changes, and send pull requests (we will likely formalize this process as development proceeds). As with all repositories on GitHub, if you prefer svn to git, you can read from and write to the repository using Subversion.

We’ve got solid set of goals for OpenLayers 3. The list below is summarizes the fundamental ideas:

  • Trigger custom application events from the map.
  • Streamline the drag flow.
  • Map properties rule. Layers derive projection and related properties from the map.
  • Layers advertise their ability to render in a projection.
  • Location is the future, and it is smart. Geometry comes from Location, and is also smart. LonLat is gone.
  • Layer visibility can be mutually exclusive within a group.
  • Improve performance of hot code (stuff that is executed a lot).
  • Create a simple core set of utilities and provide adapters for people that are using other JavaScript libraries that duplicate this functionality (reducing the amount of redundant code that has to be loaded).
  • Look for ways to refactor the code so things can be excluded in applications where it is not needed (e.g. advanced geometry operations).
  • Provide a simple set of widgets (like the layer switcher) but make it easy for people to use other widget libraries of their choosing.
  • Facilitate mobile browser support.

How’s that for ambitious?

During development towards OpenLayers 3, we will continue to work on the 2.x line of development. We’re excited about some good new features and fixes in the next release (2.10).

Thanks for any help in the effort to get to OpenLayers 3.0.

Tags: Future · Release

2 responses so far ↓

  • 1 chrelad // Jun 30, 2010 at 9:30 pm

    Awesome, that’s the way to do it! I’d recommend using Chrome’s developer tools to figure out where the hot code can be improved. Check out the developer tools video on youtube for a cool walkthrough of how easy it is to track down (

  • 2 alpha // Oct 9, 2012 at 3:17 pm

    I would like to hear changes about performance most. Especially for tiled wms layers, because 20 layers x 16 tile for each layer makes browser unusable. Other solutions like grouping layers cancels serverside caching technologies. This is the most important problem about openlayers.

    Secondly, have you ever considered webgl? Maybe the solution for all performance issues can be using pc hardware more and it seems webgl makes it possible.

    I wish you best luck for your further improvements.