Difference between revisions of "OpenLayers Report 2008"
Line 15: | Line 15: | ||
=== Areas for Improvement === | === Areas for Improvement === | ||
− | + | * Documentation, as with any open source project, is always in need of expansion and improvement. With the new OpenLayers documentation site up and running, it is now easier to create documentation. | |
− | + | * Thorough API review. As we bend towards the 8th release of the 2nd OpenLayers API, there are many who long for a massive spring cleaning session to build a 3.0 version of the library. | |
− | + | * Improved access to third party services. With the new protocols and formats, it is now possible to easily create tools which allow OpenLayers to communicate with more servers. One target which has thus far been neglected, for example, is ESRI's server products, both in access to map tiles and vector data. It would be great to see the community step up to help support these important targets. | |
+ | |||
=== Opportunities to Help === | === Opportunities to Help === | ||
Revision as of 07:35, 5 March 2009
OpenLayers
- Contact name: Erik Uzureau, Chris Schmidt, Tim Schaub
Key Accomplishments
In 2008, OpenLayers had two major releases that demonstrate the majority of our work on the library in this time frame.
The OpenLayers 2.6 release added significant visual improvements, including animated panning of the map and improved popup support for better in-map visualization. In support of our growing international usage, we added internationalization support. We also added a powerful new API for styling client side data, and added support for connecting to MapGuide data sources.
OpenLayers 2.7 added improved rendering capabilities, and added the ability to read OGC standard SLD style documents. There was also a significant development in pushing for vector behaviors, allowing users to easily extend OpenLayers to support communication with custom data providers through open or proprietary protocols.
In addition to code improvements, in 2008 OpenLayers added a revamped demonstration gallery, showing off more than 75 uses of OpenLayers with descriptions, screenshots, and more. In addition to the gallery, the OpenLayers website now has case studies -- organizations which have shared their usage of OpenLayers by explaining how that decision came about and is supported.
Areas for Improvement
- Documentation, as with any open source project, is always in need of expansion and improvement. With the new OpenLayers documentation site up and running, it is now easier to create documentation.
- Thorough API review. As we bend towards the 8th release of the 2nd OpenLayers API, there are many who long for a massive spring cleaning session to build a 3.0 version of the library.
- Improved access to third party services. With the new protocols and formats, it is now possible to easily create tools which allow OpenLayers to communicate with more servers. One target which has thus far been neglected, for example, is ESRI's server products, both in access to map tiles and vector data. It would be great to see the community step up to help support these important targets.
Opportunities to Help
* The now-formalized Case Studies section needs more contributions. Help others to understand why/how you chose to use the OpenLayers library. * Internationalization - We currently have only 15 of the 7,000 living languages translated in the library. The translation process is simple (only 28 strings total). * Ticket Review - As always, there are many more tickets with patches waiting review than available developer hours. * Documentation - Efforts continue to improve the library's documentation, but the *users* are really those who can best help with this mission.
Outlook for 2009
2009 brings new leadership to the project's Steering Committee as Tim Schaub takes over the reigns as the new PSC chair.
Efforts are already underway for a 2.8 release which will include long-awaited WFS Protocol functionality, as well as a massive improvement to OpenLayers's vector capabilities which increase performance and interactivity for maps integrating multiple vector layers.