MapServer Project Update - 2007 Q1
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Work in progress...
MapServer is a development environment for building spatially-enabled web mapping applications and services. It is fast, flexible, reliable and can be integrated into just about any GIS environment. It supports many popular spatial data formats including OGC web services.
MapServer features MapScript, a powerful scripting environment, that supports PHP, Python, Perl, C#, Java and more. Using MapScript makes it fast and easy to build complex geospatial web applications.
- MapServer 4.10.0 release
- MapServer 4.10.1 release
- Support for AGG, an up and coming image renderer as an alternative to GD is on the horizon for 5.0. Numerous other planned updates are described on the 5.0 release plan.
Take a look at MapServer statistics at Ohloh. Here are some excerpts:
- 27 developers: " Over the past twelve months, 12 developers contributed new code to MapServer. This is a relatively large team, putting this project among the top 5% of all project teams on Ohloh. For this measurement, Ohloh considered only recent changes to the code. Over the entire history of the project, 27 developers have contributed."
- Mature, well-established codebase: "The first lines of source code were added to MapServer in 2000. This is a relatively long time for an open source project to stay active, and can be a very good sign.
A long source control history like this one shows that the project has enough merit to hold contributors's interest for a long time. It might indicate a mature and relatively bug-free code base, and can be a sign of an organized, dedicated development team.
Note: The source code for MapServer might actually be older than the source control history can reveal. Many projects begin by duplicating a large amount of source code from an existing, older project. You can usually tell whether this is the case by looking for a rapid rise in the amount of code early in the project's history."