GSoC 2010
From MapbenderWiki
Contents
|
FAQ
Read this FAQ from Google. If you didn't find what you were looking for, join us on IRC, or ask at the Mapbender Mailing Lists.
If you have no idea what Mapbender is all about, take a look at the Gallery.
Ideas of all the OSGeo-Projects
- http://wiki.osgeo.org/wiki/Category:Google_Summer_of_Code
- http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2010_Ideas OSGEO Ideas 2010
Ideas
Create Ajax administration interfaces w/ jQuery
Replace the old HTML forms generated by PHP with a state-of-the-art HTML/JavaScript/jQuery/CSS-Frontend, communicating with the server side via Ajax. You will also be using jQuery UI.
Your work will base on the achievement of last years GSoC student Karim, see demo (log in as test/test). You will have to work closely with the Mapbender team. Note: The implementation has to be finished by the end of June, the rest of the time will be used for writing tutorials.
Requirements:
- advanced PHP and JavaScript skills
- advanced jQuery (UI) skills
- advanced CSS knowledge is an advantage, as well as knowledge about the jQuery UI CSS framework
Willing to mentor:
Create a RESTful API for Mapbender
Currently, Mapbender interacts with the administrator through a web interface. It would be helpful to have a RESTful API. Basci functionality will include * Authentication with Mapbender
- OGC WMS resource CRUD (create, read, update, delete)
Read more about what an OGC WMS is and how it is managed with Mapbender.
An OGC WMS resource has various representations. Some of them are already well defined and standardized including the Capabilities document, GetMap "operation", etc.. Others are not well defined yet. One task of this project will include the design of the representations following a resource oriented pattern. All tasks that involve deeper knwowledge of the standards and specifications will be supported by the mentor including access to the documents and work groups at OGC.
The student will get to know the entities in the Mapbender database and design and implement the resources and representations for OGC WMS through the API. The results of this project will be used as the foundation for a resource oriented metadata repository.
How to design a resource oriented service
One requirement to be able to implement a usable RESTful service is up front design of the resource and their representations. Richardson and Ruby propose a way of doing this in the O'Reilly book RESTful Web Services.
1. Figure out the data set
2. Split the data set into resources
For each kind of resource:
3. Name the resources with URIs
4. Expose a subset of the uniform interface
5. Design the representation(s) accepted from the client
6. Design the representation(s) served to the client
7. Integrate this resource into existing resources, using hypermedia links and forms
8. Consider the typical course of events: what's supposed to happen?
9. Consider error conditions: what might go wrong?
Requirements:
- advanced PHP skills
- advanced knowledge on RESTful Web Services
- basic SQL skills
Willing to mentor:
Secondary Mentor:
Further Reading
- REST Wiki
- RESTful Web Services; Richardson and Ruby; O'Reilly
- How to create a REST Protocol; Joe Gregorio
Replace the current vector graphics library (wz_jsGraphics) with a current one (like RaphaelJS)
already implemented to a significant degree.
Enhance the current WFS forms by adding jQuery plugins like validation
The Wfs configuration uses an "html" field to link a WFS featuretype to a form element. By this, you can create advanced forms to search for features (or update them). The idea is to make this configuration more powerful and easier, by relying on the validation plugin.
Requirements:
- advanced JavaScript and HTML skills
- advanced jQuery (UI) skills
- knowledge of jQuery validation plugin
- advanced CSS knowledge is an advantage, as well as knowledge about the jQuery UI CSS framework
Willing to mentor:
What's YOUR idea?
Let us know!
