SoC Report 2007 - Revision history

Wiki-Mloskot: Tiny fix

2014-06-12T15:01:56Z

Tiny fix

Neteler at 08:56, 15 April 2008

2008-04-15T08:56:13Z

Wiki-Wolf: Updates from late mentors

2008-03-05T18:21:36Z

Updates from late mentors

Helena: /* v.generalize */

2008-03-05T04:12:35Z

v.generalize

Neteler: markup fix

2008-03-04T13:48:21Z

markup fix

Neteler: converted from original XHTML to Wiki with http://labs.seapine.com/htmltowiki.cgi

2008-03-04T13:20:09Z

converted from original XHTML to Wiki with http://labs.seapine.com/htmltowiki.cgi

Show changes

Neteler at 11:31, 24 February 2008

2008-02-24T11:31:00Z

Tmitchell: note about offline file

2008-02-18T23:06:46Z

note about offline file

New page

Latex file emailed to Tyler 17Feb08

@@ Line 35: / Line 35: @@
 ==== KML read support for the existing driver ====
-'''Student:''' Mateusz Loskot '''Mentor:''' Jens Oberender
+'''Student:''' Jens Oberender '''Mentor:''' Mateusz Loskot
 This project added KML vector read support.

← Older revision		Revision as of 08:56, 15 April 2008
Line 259:		Line 259:

	[[Category: Reports 2007]]		[[Category: Reports 2007]]
		+	[[Category:Google Summer of Code]]

@@ Line 90: / Line 90: @@
 A feature cache. A RAM cache might use the LRU algorithm and have a maximum amount of RAM to consume setting. A local disk cache and local disk cache might use a size-only and/or maximum age based algorithm. Ideally as items fall out of RAM, they would be written to disk. At session close, remaining items in RAM would also be written to disk (much like Google Earth). Upon startup, cache could be polled to see if anything already exists within the current spatial window (if it hasn't expired).
-For more information see the [http://docs.codehaus.org/display/GEOTOOLS/SoC 2007 Caching data Wiki page]
+For more information see the [http://docs.codehaus.org/display/GEOTOOLS/SoC+2007+Caching data Wiki page]
 ==== Interactive GeoRSS Tool ====
@@ Line 118: / Line 144: @@
 * Intuitive - easy to learn but not cumbersome or limiting for the advanced user.
-For more information see the [http://docs.codehaus.org/display/GEOTOOLS/GeoServer Style Editor Wiki page]
+For more information see the [http://docs.codehaus.org/display/GEOTOOLS/GeoServer+Style+Editor Wiki page]
 === GeoTools ===
@@ Line 135: / Line 161: @@
 * GRIB1 is a data format standardized by the World Meteorological Organization's Commission (http://www.wmo.ch/) for Basic Systems, which is commonly used in meteorology to store historical and forecasted weather data.
-For more information see [http://docs.codehaus.org/display/GEOTOOLS/Plugins for multidimensional raster data sources Wiki page]
+For more information see [http://docs.codehaus.org/display/GEOTOOLS/Plugins+for+multidimensional+raster+data+sources Wiki page]
 ==== 3D Rendering Pipeline ====

@@ Line 66: / Line 66: @@
 For more information see the [http://grass.osgeo.org/grass63/manuals/html63_user/v.generalize.html module documentation]
-v.generalize is included in the new 6.3.0 release of GRASS (as of RC4)
+v.generalize is included in the new 6.3.0 release of GRASS (as of RC4).
 ==== v.net.visibility ====

@@ Line 1: / Line 1: @@
-= OSGeo participation in Google Summer of Code 2007 =
+== OSGeo participation in Google Summer of Code 2007 ==
-== Wolf Bergenheim ==
+by Wolf Bergenheim
 Last summer, from May 1st 2007 to August 31st 2007, OSGeo participated in the Google Summer of Code. This article sums up that experience and gives a short presentation of each Summer of Code project.
@@ Line 11: / Line 9: @@
 Quoting [http://code.google.com/support/bin/answer.py?answer=60266&topic=10726 Google FAQ]
-<blockquote> Google Summer of Code TM is a program that offers student developers stipends to write code for various open source projects. Google will be working with a several open source, free software and technology-related groups to identify and fund several projects over a three month period. Historically, the program has brought together over 1,000 students with over 100 open source projects, to create hundreds of thousands of lines of code. The program, which kicked off in 2005, is now in its third year, following on from a very successful 2006. </blockquote><blockquote> While the majority of past student participants were enrolled in university Computer Science and Computer Engineering programs, GSoCers come from a wide variety of educational backgrounds, from computational biology to mining engineering. Many of our past participants had never participated in an open-source project before GSoC; others used the GSoC stipend as an opportunity to concentrate fully on their existing open source coding activities over the summer. Several of our 2005 students went on to become mentors in 2006.
+<blockquote> Google Summer of Code TM is a program that offers student developers stipends to write code for various open source projects. Google will be working with a several open source, free software and technology-related groups to identify and fund several projects over a three month period. Historically, the program has brought together over 1,000 students with over 100 open source projects, to create hundreds of thousands of lines of code. The program, which kicked off in 2005, is now in its third year, following on from a very successful 2006. </blockquote><blockquote> While the majority of past student participants were enrolled in university Computer Science and Computer Engineering programs, GSoCers come from a wide variety of educational backgrounds, from computational biology to mining engineering. Many of our past participants had never participated in an open-source project before GSoC; others used the GSoC stipend as an opportunity to concentrate fully on their existing open source coding activities over the summer. Several of our 2005 students went on to become mentors in 2006.</blockquote>
 == What projects participated? ==

← Older revision		Revision as of 11:31, 24 February 2008
Line 1:		Line 1:
	Latex file emailed to Tyler 17Feb08		Latex file emailed to Tyler 17Feb08
		+
		+
		+	[[Category: Reports 2007]]