nyuuzyou/wikis huggingface dataset:
MapServer 2011 SOC Ideas

* Back to the main OSGeo Google Summer of Code 2011 wiki page.
* Back to the main OSGeo Google Summer of Code 2011 Ideas wiki page.
= MapServer 2011 SoC Ideas =
Enter ideas for development projects here. Note these are just suggestions - students are welcome to propose projects based on their own interests that relate to MapServer. 
== Layer plug-in for AcidMaps ==
AcidMaps: https://github.com/XoomCode/AcidMaps
== Native SpatialLite driver ==
SpatiaLite: http://www.gaia-gis.it/spatialite/
OGR currently supports SpatiaLite and may prove as a valuable code reference.
== Flash support ==
Adopt Flash support to the new renderer architecture.
== INSPIRE View Service ==
Implement missing features to enhance the support of the INSPIRE View Service specification in MapServer. First discussions are documented at the MapServer wiki.
This is the latest specification document: Technical Guidance for the implementation of INSPIRE View Services, version 3.0
If interested subscribe to the mapserver-inspire mailing list.
== Node.js Bindings ==
Node.js http://www.nodejs.org/
Make Node.js bindings for MapScript. By MapScript, I mean, make Node.js bindings for the WMS serving functions.
== Other Ideas ==
See also the MapServer 2010 SOC Ideas or MapServer 2009 SOC Ideas.
= Mentor Candidates =
The following individuals are potentially willing to serve as MapServer mentors or co-mentors. 
* Stephan Meißl
* Dan "Ducky" Little
Category:Google Summer of Code
MapServer 2012 SOC Ideas

* Back to the main OSGeo Google Summer of Code 2012 wiki page. 
* Back to the main OSGeo Google Summer of Code 2012 Ideas wiki page.
= MapServer Suite 2012 SOC Ideas =
Enter ideas for development projects here. Note these are just suggestions - students are welcome to propose projects based on their own interests that relate to the MapServer Suite. Our current efforts are based on the following projects: 
* Mapserver Suite This is the mapserver cartographic server, which now includes TinyOWS and MapCache.
You can find the source code, tutorials, the project mailing list and various other information at the links above. 
To give you an idea about possible SoC projects, here are some suggestions: 
== MapServer core related ideas ==
== TinyOWS related ideas ==
=== GSoC project : SpatiaLite support in TinyOWS ===
TinyOWS is a geographical feature server, implementing WFS and WFS-T OGC 
protocols. TinyOWS focus on performance, KISS design, and strong compliance to 
the standards. It will be included in the MapServer Suite project as soon as the forthcoming 6.2 release.
TinyOWS currently relies heavily on PostGIS, to get a strong transactionnel 
backend, and be as close as possible from the data. This leads to good 
performances and avoid duplication of features (such as GML format I/O for instance).
This SoC project consists in the implementation of a Spatialite additional support for TinyOWS. The aim is to use this lightweight database as a backend, enabling TinyOWS deployment without the need of a PostGIS server.
SpatiaLite is indeed a SQLite spatial extension, adding a whole lot of 
geographical features to SQLite, creating a convenient and lightweight self-
contained spatial database. While being less efficient than PostGIS in a multi-
user context, SpatiaLite supports transactions and most of the spatial 
features needed to act as TinyOWS backend.
The project will include the following steps :
* Inclusion of SpatiaLite libraries into TinyOWS build system (as optional)
* Identify all TinyOWS codes related to PostGIS functions. 
* Add missing features into SpatiaLite to be able to act as TinyOWS backend (GeomFromGML for instance)
* And provide a clean enough patch to get these features commited into the trunk
* Add multi-database abstraction layer into TinyOWS (to support either PostGIS or SpatiaLite)
* CreateTinyOWS and SpatiaLite units tests cases
* Check compliance to CITE tests for OGC standards with SpatiaLite backend
* Compare performances between PostGIS backend and SpatiaLite backend
* SQL Injection audit, on the new backend (with a tool like SQLMap)
== Other ideas ==
== Lots of other options ==
There are a lot of other possibilities that we would be happy to discuss with any students interested. Best you contact us on the MapServer mailing list:
* http://lists.osgeo.org/mailman/listinfo/mapserver-dev
= Mentor Candidates =
The following individuals are potentially willing to serve as MapServer mentors or co-mentors. 
* Olivier Courtin <olivier.courtin (at) oslandia.com>
* Brad Hards <bradh (at) frogmouth.net> (on SpatiaLite stuff)
Category:Google_Summer_of_Code
MapServer Annual Report 2007

Project Name = MapServer
* Period covered by report: Jan-Dec 2007
* Contact name: Steve Lime
== Key Accomplishments ==
* the top 5-10 key items that the project or PSC accomplished this period
== Areas for Improvement ==
* any weaknesses in process, software, management, etc. that you plan to address or recognise need some help
 
== Opportunities to Help ==
* list areas that could use some help from members and readers of the report
== Outlook for 2008 ==
* this is the motivational part that is meant to inspire readers to keep their eyes open for great stuff in 2008 :)
Category: Reports 2007
MapServer Project Update - 2007 Q1

== About MapServer ==
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.
== Recent Events ==
=== October 2006 ===
* MapServer 4.10.0 release
=== February 2007 ===
* MapServer 4.10.1 release
 
== Future development - MapServer 5.0 ==
The MapServer development team plans to release version 5.0 by the end of summer 2007. The 5.0 Release Plan outlines a number of planned updates, including:
* Support for AGG, an up and coming image renderer as an alternative to GD
* Upgrade of WMS support to version 1.3.0
* Improved OGC SOS Server support
* New OGC OWS Common support version 1.0.0
* Dynamic charting capability
* Label prioritization
* MapScript memory management fixes
* Redesign of the LOG/DEBUG output mechanism
* ... and much more ...
== Statistics ==
* Mapserver-Users list statistics (for 2007-Q1):
** Number of subscribers: 2344
** Number of countries represented: 67 (In all continents but Antarctica)
** Number of posts per month: 415 (average for Jan-Mar 2007)
* Also take a look at MapServer Development 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 is actually older than the source control history. The project started around 1996 but started using CVS only in 2000.
MapServer Provenance Review

MapServer is a graduated OSGeo project. This page is part of the archive of the incubation process.
= Library/Component Review =
See spreadsheets.
= Code Copyright Review =
The objective here is to visit every source file, and identify possible issues, and work to "regularize" things. 
See spreadsheets.
* Maintain a list of all copyright holders identified in the review document (see REAMDE in the trunk root of the SVN). 
= Review Document =
The result of the provenance review is two fold. First, there is clarification and "fixes" done during the review. For instance, adding missing copyright notices, or factoring out external libraries. The second is a review report with a fairly detailed list of outstanding issues, ambiguities and information of note. 
The review document will be distributed to the project PSC members, as well as the incubation committee. Based on it, the incubation committee may require the project to do additional work, either resolving ambiguities, factoring items out, or rewriting questional components. 
When completed, a much briefer form of the review document should be prepared, just listing information that would be pertinent to folks using the project. Essentially a summary. This summary might live in source control as README.LICENSE or something similar.
== Copyright Header ==
It is sufficient to refer to a single copy of the license agreement for the project, but each file should include an indication of what the license is, and the location of the full license document. 
The [MapServer] MapServer license text (retrieved from mapserv.c Revision 7147:
 Project: MapServer
 Purpose: MapServer CGI mainline.
 Author: Steve Lime and the MapServer team.
 Copyright (c) 1996-2005 Regents of the University of Minnesota.
 Permission is hereby granted, free of charge, to any person obtaining a
 copy of this software and associated documentation files (the "Software"),
 to deal in the Software without restriction, including without limitation
 the rights to use, copy, modify, merge, publish, distribute, sublicense,
 and/or sell copies of the Software, and to permit persons to whom the
 Software is furnished to do so, subject to the following conditions:
 The above copyright notice and this permission notice shall be included in
 all copies of this Software or works derived from this Software.
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
 OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
 FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
 THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
 FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
 DEALINGS IN THE SOFTWARE.
Category:Incubation
Category:MapServer
MapServer Report 2007

Project Name = MapServer
* Period covered by report: Jan-Dec 2007
* Contact name: Steve Lime
== Key Accomplishments ==
* Transformed the MapServer Technical Steering Committee (TSC) into the MapServer Project Steering Committee (PSC) (see RFC-23)
* Added four new members to the PSC
* Three maintenance releases of MapServer 4.10
* Migrated significant portions of MapServer project infrastructure, specifically CVS and Bugzilla, from the University of Minnesota to OSGeo infrastructure (SVN and Trac) in April 2007
* Implemented a buildbot 
* Released MapServer 5.0 in early September 2007 closing more than 200 tickets. Key features include:
** Support for the AGG rendering engine
** Label prioritization control
** Style and label attribute binding
** Dynamic charting capabilities
** Raster color correction via color lookup table
** Dynamic allocation for most statically allocated elements (e.g. layers, classes and styles)
** Improved memory management and garbage collection for MapScript
** Enhanced debug/logging capabilies
== Areas for Improvement ==
* OSGeo incubation process was slow, primarily limited to infrastructure migration from UMN to OSGeo.
* Like most projects, keeping documentation up-to-date with development remains a challenge.
* There was little or no time for collaboration with other similar (e.g. MapNik, GeoServer, MapGuide) projects although I guess this is only natural given the other demands of working on a project.
* The MapServer development team did a poor job representing the new release of MapServer (5.0) at the FOSS4G conference in Victoria.
== Opportunities to Help ==
* list areas that could use some help from members and readers of the report
== Outlook for 2008 ==
* this is the motivational part that is meant to inspire readers to keep their eyes open for great stuff in 2008 :)
Category: Reports 2007
MapServer Report 2008

== MapServer ==
* Contact name: Steve Lime
=== Key Accomplishments ===
the top 5-10 key items that the project or PSC accomplished this period
* Project graduated from OSGeo incubation process in December
* MapServer 5.2 released in July:
** Nearly 200 tickets were closed as part of this effort.
** Notable features and enhancements include:
*** Performance enhancements for large shapefile handling (following Geoserver comparison)
*** Performance enhancements for AGG rendering (an order of magnitude faster in some cases)
*** Rendering improvements:
**** fuzzy label outlines for AGG
**** style-level opacity for AGG
**** quantization and palette support for PNGs and RGBA modes
**** pre-clip label point computation (helps in tile generation) 
*** OGC Web Services:
**** WCS 1.1.0 support (RFC-41)
**** SOS 1.0.0 support
**** WFS 1.1.0 support
**** Compliance testing (WMS 1.1.1 ready to certify) 
*** proxy and http authentication support for cascaded WMS requests
*** Support for auth cookie forwarding (RFC-42)
*** Direct tile generation for Google Maps API (RFC-43)
*** Native Microsoft SQL Server 2008 Support (RFC-38)
*** extent (e.g. shpext, mapext) template tag attribute handling
*** Simplified Template Support for Query Output (MS RFC 36) 
* New website launched in December! Quite an improvement for usability and maintainability over the previous site!
* We moved from the UMN to OSGeo infrastructure (thanks to UMN for hosting us for all those years!)
* We finally got a hold of the mapserver.org domain which has become our new home
=== Areas for Improvement ===
any weaknesses in process, software, management, etc. that you plan to address or recognize need some help
* Keeping documentation up-to-date with development remains a challenge
** Content is spread between the new website and the MapServer trac wiki and it is unclear when to transition between the two
* The project still doesn't do a great job marketing itself at OSGeo conferences.
* Google Summer of Code: try to attract some students in the next editions
=== Opportunities to Help ===
list areas that could use some help from members and readers of the report
* general website and documentation maintenance
* multilingual documentation support
* new coders always welcome, a good way to start is by contributing bug reports and patches
* experienced users can contribute to the release process by testing the betas and RCs and reporting their results
=== Outlook for 2009 ===
this is the motivational part that is meant to inspire readers to keep their eyes open for great stuff in 2009 :)
* MapServer 5.4 to be released in early March
* Strong presence at the Toronto Code Sprint in March where we will focus on 6.0 release features and performance improvements
* MapServer 6.0 release sometimes in the fall (hopefully before FOSS4G)
* Reestablish features lost in the website transition (specifically the gallery section)
__notoc__
Category: Reports 2008
Category:MapServer
MapServer Report 2011

== MapServer ==
* Contact name: Steve Lime, PSC Chair
=== Key Accomplishments ===
* One major release:
** MapServer 6.0 released on May 12, 2011. See the Release Announcement for the list of new features and enhancements in this release
* Several minor releases tied to bug fixes and security improvements:
** Release of 5.6.6 on January 17, see announcement
** Release of 6.0.1, 5.6.7 and 4.10.7 with security fixes, see announcement
* Very strong participation in the Montreal Code Sprint in March 2011
* Participation in the web mapping server shoot out at FOSS4G 2011.
* Integration of two new components in the MapServer project, to be included for the first time in the 6.2 release:
** TinyOWS (formerly at tinyows.org) providing WFS and WFS-T, see also RFC-70
** MapCache (formerly at Mod-Geocache) providing high performance tile caching and more, see also RFC-71.
=== Areas for Improvement ===
* Keeping documentation up-to-date with development remains a challenge
* Continue work to attract additional developer talent to the project.
* Cleanup bug backlog (550+ open bugs), and triage new bugs more effectively.
* Google Summer of Code: continue to try and attract more students
=== Opportunities to Help ===
* General website, documentation and translations maintenance.
* New coders always welcome, a good way to start is by contributing bug reports and patches.
* Experienced users can contribute to the release process by testing the betas and release candidates and reporting their results.
=== Outlook for 2012 ===
* Participation in the Seattle/IslandWood Code Sprint in February 2012
* MapServer 6.2 to be release sometime in mid-2012.
** Planned enhancements include:
*** see the 6.2 Release Plan
__notoc__
Category: Reports 2011
MapServer Report 2012

== MapServer ==
* Contact name: Steve Lime, PSC Chair
=== Key Accomplishments ===
* One major release:
** MapServer 6.2 released on November 14, 2012. See the Release Announcement for the list of new features and enhancements in this release
* Several minor releases tied to bug fixes and security improvements:
** Release of 6.0.2 and 5.6.8 on February 8, see announcement
** Release of 6.0.3 on May 18, see announcement
* Participation in the Seattle/IslandWood Code Sprint in February 2012
* Migration of source repository and tickets management from SVN/Trac to GitHub, see RFC 84
=== Areas for Improvement ===
* Keeping documentation up-to-date with development remains a challenge
* Continue work to attract additional developer talent to the project.
* Cleanup bug backlog (550+ open bugs), and triage new bugs more effectively.
* Google Summer of Code: continue to try and attract more students
=== Opportunities to Help ===
* General website, documentation and translations maintenance.
* New coders always welcome, a good way to start is by contributing bug reports and patches.
* Experienced users can contribute to the release process by testing the betas and release candidates and reporting their results.
=== Outlook for 2013 ===
* Participation in the Boston Code Sprint in March 2013
* MapServer 6.4 to be released sometime in 2013.
** Planned enhancements include:
*** see the 6.4 Release Plan
__notoc__
Category: Reports 2012
Category:MapServer
MapSlicer

MapSlicer is an open-source application, distributed under the New BSD License.
It can run on several platforms, including Linux, Microsoft Windows and Apple Mac OS X.
Map Publishing
--------------------------------------------------------------------------------
MapSlicer is a desktop application for the creation of map tiles for rapid raster map publishing. Geodata is transformed to tiles compatible with OpenStreetMap, Google Maps, Google Earth, Yahoo Maps or Bing Maps - ready for publishing via direct upload to any webserver or a cloud storage. The only thing you have to do for publishing the map is to upload the automatically generated directory with tiles into your webserver.
No extensive configuration on the server side is necessary, any simple file hosting is fine. Dynamic interaction such as panning and zooming, overlay of markers and vector data is provided by powerful browser functionality.
The application directly generates a ready to use simple viewer based on OpenLayers and Google Maps API and can be easily customized.
Core Features
--------------------------------------------------------------------------------
* Well known Javascript APIs supported: OpenLayers, Google Maps API
* No extra server software installation necessary
* Hosting almost everywhere: cloud storage such as Amazon S3 or any cheap "unlimited" webhosting with FTP access
* Easy mashup with commercial layers (Google, Bing, Yahoo) or OpenStreetMap
* Tiles follow OSGEO TMS (Tile Map Service Specification)
* Ability to process raster data in various formats: TIFF/GeoTIFF, MrSID, ECW, JPEG2000, Erdas HFA, NOAA BSB, JPEG and more...
History
--------------------------------------------------------------------------------
We would like to thank Petr Pridal - Klokan for his contribution of the original MapTiler project.
Sponsors of MapTiler/GDAL2Tiles:
* http://www.davidrumsey.com - supported improvement of Google Earth SuperOverlay rendering
* http://www.nic.cz/ and http://www.nic.cz/vip/ - Vyvíjej, Inovuj, Programuj
* http://www.brgm.fr/ (Bureau des Recherches Geologiques et Minières - French Geological Survey Office
* http://www.oldmapsonline.org/ - Moravian Library Brno, Czech Ministry of Culture
* http://code.google.com/soc/ - Google Summer of Code 2007, 2008 (GDAL2Tiles utility) - OSGeo and Google Inc.
Huge thanks to the team of http://www.gdal.org/ and also people from http://www.osgeo.org/ .
Details
--------------------------------------------------------------------------------
* Source Code: https://github.com/geopython/mapslicer
* Licence: New BSD License
* Software Version: 1.0.rc1
* Supported Platforms: Windows, Linux, Mac
Mapbender

== Summary ==
Mapbender is a web based geoportal framework to publish, register, view, navigate, monitor and grant secure access to spatial data infrastructure services.
The open source software Mapbender is a content management system for geospatial data services and map applications. With Mapbender, you can create applications without writing a single line of code. Based on state-of-the-art technologies, Mapbender is a flexible client for OGC services. 
The software is implemented in PHP and JavaScript and licensed under MIT. 
* Project page for Mapbender: https://www.mapbender.org/
* Mailing lists: https://www.mapbender.org/?q=en/community 
* Issue Tracker for Mapbender: https://github.com/mapbender/mapbender/issues
* Code repository on GitHub: https://github.com/mapbender
* OSGeo Project Page: https://www.osgeo.org/projects/mapbender/
* Mapbender on Twitter: https://twitter.com/mapbender
* Mapbender on Open Hub: https://www.openhub.net/p/mapbender
== Functionality ==
Mapbender is an SDI back end to create and maintain web based spatial applications.
End-user interfaces can be compiled from a broad selection of preconfigured modules based on jQuery and OpenLayers. Mapbender can be used to create highly focused light clients with a minimum set of modules as well as fully fledged applications with OWS security proxy, log module, digitizing with auto snapping, catalog and metadata editor components, monitoring and much more functionality.
Management interfaces help to maintain and monitor mapping and feature resources in a metadata catalog and grant access to individuals and groups. Adherence to standards, such as OGC WMS and transactional OGC WFS, make Mapbender agnostic to different brands of server software and allows to take advantage of interoperable services from various platforms.
== Community ==
Mapbender code is implemented and maintained by developers from a diverse background and different companies.
Join the community:
* Subscribe to the mailing list.
== Demo and Gallery ==
Use a sample Mapbender application in the Mapbender demo or look up specialized applications in the Mapbender Gallery.
* Mapbender Demo and Gallery
Category: Software Stack
Category:OSGeo Project