Java 2018 Code Sprint

2018-10-04T06:50:46Z

Moovida: /* Participants */

The Java tribe has a real challenge for 2018 - updating our open source projects for the Java roadmap.

== Location ==

Sprint scheduled for Q4 2018, proposed date:

* October 22-26th

We are looking at setting up a distributed sprint with locations in:

* North America - Victoria, Boundless Office, billeting options available for those travelling
* Europe
** Software Engineer and Computer Science School, University of Sevilla, Spain
** Astun Office in Epsom, UK several point are gathering there

=== Contacts ===

Jody Garnett

== Sponsors ==

We would like to thank our sponsors!

=== Gold Sponsors ===

TBD

=== Bronze Sponsors ===

TBD

=== In-Kind Support ===

[[File:Boundless_Logo.png|350px|link=http://boundlessgeo.com]] [[File:GeoCat.png|350px|link=https://www.geocat.net]] [[File:astun.png|350px|link=https://astuntechnology.com/]]

== Participants ==

Please add your name and the projects you are planning to sprint and note the likehood of your attendance.

{| style="border: solid grey 1px; width:100%" class="sortable"
|+ Participants
|-
| # || Participant || Country || Organization || Arrival || Departure || Project Work on || Notes || Attendance
|-
| 1 || [[User:Delawen|María Arias de Reyna]] || Spain || GeoCat bv || local || local || GeoNetwork || Notes || Confirmed
|-
| 2 || [[User:Jive|Jody Garnett]] || Canada || Boundless || local || local || GeoTools || Able to host guests || Confirmed
|-
| 3 || [[User:Tbarsballe|Torben Barsballe]] || Canada || Boundless || local || local || GT/GS || || Confirmed
|-
| 4 || [[User:ksmith|Kevin Smith]] || Canada || Boundless || local || local || GT/GWC/GS || || Confirmed
|-
| 5 || [[User:dvntucker|Devon Tucker]] || Canada || Boundless || local || local || GT/GS || || Confirmed
|-
| 6 || [[User:moovida|Antonello Andrea]] || Italy || HydroloGIS || TBD || TBD || GT/JTS, Hortonmachine || || Confirmed
|-
| 7 || [[User:ianturton|Ian Turton]] || UK || Astun || local || local || GT/GS || Epsom ||
|-
| 8 || [[User:Aaime|Andrea Aime]] || Italy || GeoSolutions || TBD || TBD || GT/GWC/GS/jai-ext/imageio-ext/jaitools || Home || Confirmed
|-
| 9 || [[User:jhughes|Jim Hughes]] || US || CCRi || TBD || TBD || JTS/GT/GS/GeoMesa || || Confirmed
|-
| 10 || [[User:Surveyor|Landon Blake]] || US || BKF Engineers || Working Remotely || Working Remotely || JTS/Proj4J || || Confirmed
|}

== Discussion ==

=== Java has a roadmap? ===

Yes, we had a previous sprint focused on Java 8 compatibility, several features had changed breaking compatibility.

More importantly the Java roadmap has changed to a six-month release cycle:

* six month release cycle is already well underway having started with Java 9 and Java 10.

* Oracle is offering three year LTS releases commercially

* AdoptOpenJDK is setting up LTS releases of OpenJDK .. backed by IBM, Microsoft and others.

* RedHat is focusing on LTS (skipping Java 9 and Java 10) and plans to ship OpenJDK based on Java SE 11

=== Why is updating our open source projects for the Java roadmap a challenge? ===

- Java changed the service provider interface plugin system used by GeoTools, forcing the project to write its own replacement.

- The java runtime has been broken up into modules, not all of which are activated by default. We need to review what sections of the JRE we require and ensure they are turned on.

- Java introduced the module system "jigsaw" providing both a class-path and module-path for loading jars.

- When loaded on the module-path jars are prevented from using the same package. This breaks multi-jar projects like GeoTools library where gt-api defining interfaces, and gt-main providing implementations.

- Jigsaw also locks down aspects of Java reflection, affecting projects like Spring that make heavy use of reflection to "auto wire" GeoServer together. Spring 5 has been released and upgrading to this release will be a key focus.

- With these changes projects like GeoServer need to review of hundreds open source dependencies to determine what other libraries are broken, if an update is available or replacement can be found.

- The java web service framework (responsible for concepts like Servlet and Session) is being removed from Oracle oversight and has been setup as [Jakarta EE Software](https://jakarta.ee).

=== Recommended reading ===

* [https://www.azul.com/what-comes-after-jdk-8/ What Comes After JDK 8?]
* [https://medium.com/criciumadev/its-time-migrating-to-java-11-5eb3868354f9 It's time! Migrating to Java 11] - contains working example of updating spring application
* [http://openjdk.java.net/projects/jigsaw/spec/sotms The State of the Module System] / [https://www.oracle.com/corporate/features/understanding-java-9-modules.html Understanding Java 9 modules]

=== Do you have any experience running sprints? ===

The GeoServer team really benefited from [[Java 2017 Code Sprint|java 2017 code sprint]] and is eager to repeat the success.

== GeoServer Planning ==

Initial planning has started:

* [https://github.com/geoserver/geoserver/wiki/GSIP-171 GSIP 171 Java 18.9 Compatibility] (GeoServer)

Preflight activities:

* dependency audit

Required updates:

* Spring 5 - Older versions of spring are not compatible with Java 11. Upgrading to from Spring 4 to Spring 5 does involve handling some API changes.
* HazelCast - Like Spring, HazelCast involves a lot of reflection.

Module refactor:

* Repackage GeoServer application jars to prevent conflicts at the package level.
* Resulting application can be used on either the CLASSPATH (Java 8) or MODULEPATH (Java 11)

== GeoTools Planning ==

Planning and work is already well underway:

* [https://github.com/geotools/geotools/wiki/Java-9-Compatibility GeoTools Java-9-Compatibility] (GeoTools)

The first completed phase is to allow GeoTools to be used on the classpath:

* [https://github.com/geotools/geotools/wiki/Migrate-Units-to-JSR-363 Migrate Units to JSR-363] (GeoTools)
* [https://github.com/geotools/geotools/wiki/FactoryRegistry-Refactoring-for-Java-9-Compatibility FactoryRegistry Refactoring for Java 9 Compatibility] (GeoTools)

The sprint goal is to refactor the geotools library into modules, allowing the jars to be used on either the classpath (Java 8) or the module path (Java 11).

* [https://github.com/geotools/geotools/wiki/Restructure-GeoTools-into-Jigsaw-modules Restructure GeoTools into Jigsaw modules] (GeoTools)

* Core library refactored into modules

[[File:Gt-modules.png|frameless|GeoTools Java 11 modules ]]

* plugins used to automatic modules to dependencies on the classpath

[[File:Module-path.png|800px|module-path bridge to classpath]]

In the above illustration the gt-svg module is used as an automatic module publishing org.geotools.renderer.style.svg package. It acts as a bridge to the multi-jar project batik still on the classpath, completely masking the fact batik is used used to read and render svg files. The core module gt-renderer publishes select packages for use, while hiding others. It makes use of ServiceLocator to access the IconFactory implemented by gt-svg and never has direct use of the batik implementation.

For this to work the gt-svg jar has been refactored, moving the icon factory the new package org.geotools.style.svg. This was required as the package org.geotools.renderer.style was already published by gt-renderer.

We expect:

* Initial focus is on the core library, refactoring to allow jars to be used on the module path as named modules
* plugins will remain on the classpath, accessed via service locator, any conflicting packages will not be visible to client code

== JTS Topology Suite Activities ==

Results of bonn code sprint:

* [https://github.com/locationtech/jts/pull/274 Add module names for better Java 9/Jigsaw support] (JTS Topology Suite)

JTS jars can be placed on the module-path used as an automatic module, the jars have been supplied am Automatic-Module-Name using a MANIFEST.MF entry.

For an example.application using jts-core as a module add '''module-info''':

module example.application {
requires org.locationtech.jts; // jts-core
}

== GeoNetwork Planning ==

[[https://github.com/geonetwork/core-geonetwork/wiki/OSGeo-Java-codesprint-2018 Strategy for GeoNetwork]]

== How to sponsorship ==

Contributions will be put towards travel costs for sprint participants who would be otherwise unable to attend. Any surplus at the end of the event will be turned over to OSGeo or used for a future code sprint. We have set-up the sprint to minimize travel and accommodation costs.

Sponsors will receive the following benefits / honours:

* Your logo at the top of this page
* Mention in project communication (for example the GeoServer 2.15 release announcement)
* The ability to run on a supported java platform
* Our gratitude :)

This event provides the following sponsorship levels:

{| class="wikitable"
|-
| Gold
| style="text-align:right;" | $2500 USD
|-
| Silver
| style="text-align:right;" | $1500 USD
|-
| Bronze
| style="text-align:right;" | $750 USD
|-
| In-Kind || colspan="3" | In-kind support graciously accepted
|}

This is an official OSGeo event, your contribution counts towards being recognized as an [https://www.osgeo.org/about/how-to-become-a-sponsor/ OSGeo Sponsors].

For more information on sponsorship, please contact [[Jody Garnett]], [[User:Aaime|Andrea Aime]].

=== How to Sponsor ===

# Contact OSGeo [[Treasurer]] for details on using PayPal or to request an invoice: treasurer@osgeo.org
# The OSGeo [[Treasurer]] will contact both you and the event organizers to acknowledge your sponsorship
#* Please have a logo ready for your organization if you wish to be acknowledged publicly
#* Your event sponsorship, at your request, can contribute towards [http://www.osgeo.org/sponsorship being recognized] as an OSGeo Foundation sponsor

=== Sponsorship Outreach ===

We are reaching out to organizations to see if there is interest in sponsorship:

* Prior sponsors: gaia3d, boundless, ian, geodan, how2map, fossgis, atol, geosolutions, astun
* Local sponsors: astun, vivid solutions, transient software

If there is a lot of local sponsorship we expect to drag the developers away from the task at hand and meet the local community (at a social evening or similar).

=== OSGeo Funding Request ===

The following information is requested by OSGeo Board [[Code_Sprint_Guidelines]], the projects involved indicated that we would be planning a sprint during the 2018 budget process.

* [https://docs.google.com/spreadsheets/d/1bSuf32MjgP7NKZcqvV7IilpxakKdocJ4CPUEF8jq5Z4/edit#gid=990228872 Java 2018 Code Sprint Budget]

It is intended to that OSGeo be recognized as hosting this event, rather than acknowledged as a sponsor.

[[Category:Code Sprints]]
[[Category:Java Tribe Code Sprint]]

Java 2018 Code Sprint

2018-10-02T11:10:21Z

Moovida: /* Participants */

The Java tribe has a real challenge for 2018 - updating our open source projects for the Java roadmap.

== Location ==

Sprint scheduled for Q4 2018, proposed date:

* October 22-26th

We are looking at setting up a distributed sprint with locations in:

* North America - Victoria, Boundless Office, billeting options available for those travelling
* Europe - Sevilla, Spain half.confirmed. Italy or Astun Office in Epsom, UK if anyone would like to join us.
* Oceania - recommendations welcome

=== Contacts ===

Jody Garnett

== Sponsors ==

We would like to thank our sponsors!

=== Gold Sponsors ===

TBD

=== Bronze Sponsors ===

TBD

=== In-Kind Support ===

[[File:Boundless_Logo.png|350px|link=http://boundlessgeo.com]] [[File:GeoCat.png|350px|link=https://www.geocat.net]] [[File:astun.png|350px|link=https://astuntechnology.com/]]

== Participants ==

Please add your name and the projects you are planning to sprint and note the likehood of your attendance.

{| style="border: solid grey 1px; width:100%" class="sortable"
|+ Participants
|-
| # || Participant || Country || Organization || Arrival || Departure || Project Work on || Notes || Attendance
|-
| 1 || [[User:Delawen|María Arias de Reyna]] || Spain || GeoCat bv || working remotely || working remotely || GeoNetwork || Notes || Partially working on the codesprint
|-
| 2 || [[User:Jive|Jody Garnett]] || Canada || Boundless || local || local || GeoTools || Able to host guests || Confirmed
|-
| 3 || [[User:Tbarsballe|Torben Barsballe]] || Canada || Boundless || local || local || GT/GS || || Confirmed
|-
| 4 || [[User:ksmith|Kevin Smith]] || Canada || Boundless || local || local || GT/GWC/GS || || Confirmed
|-
| 5 || [[User:dvntucker|Devon Tucker]] || Canada || Boundless || local || local || GT/GS || || Confirmed
|-
| 6 || [[User:moovida|Antonello Andrea]] || Italy || HydroloGIS || TBD || TBD || GT/JTS, Hortonmachine || Epsom || Confirmed
|-
| 7 || [[User:ianturton|Ian Turton]] || UK || Astun || local || local || GT/GS || Epsom ||
|-
| 8 || [[User:Aaime|Andrea Aime]] || Italy || GeoSolutions || TBD || TBD || GT/GWC/GS/jai-ext/imageio-ext/jaitools || || Either Italy or remote
|-
| 9 || [[User:jhughes|Jim Hughes]] || US || CCRi || TBD || TBD || JTS/GT/GS/GeoMesa || || Confirmed
|-
| 10 || [[User:Surveyor|Landon Blake]] || US || BKF Engineers || Working Remotely || Working Remotely || JTS/Proj4J || || Confirmed
|}

== Discussion ==

=== Java has a roadmap? ===

Yes, we had a previous sprint focused on Java 8 compatibility, several features had changed breaking compatibility.

More importantly the Java roadmap has changed to a six-month release cycle:

* six month release cycle is already well underway having started with Java 9 and Java 10.

* Oracle is offering three year LTS releases commercially

* AdoptOpenJDK is setting up LTS releases of OpenJDK .. backed by IBM, Microsoft and others.

* RedHat is focusing on LTS (skipping Java 9 and Java 10) and plans to ship OpenJDK based on Java SE 11

=== Why is updating our open source projects for the Java roadmap a challenge? ===

- Java changed the service provider interface plugin system used by GeoTools, forcing the project to write its own replacement.

- The java runtime has been broken up into modules, not all of which are activated by default. We need to review what sections of the JRE we require and ensure they are turned on.

- Java introduced the module system "jigsaw" providing both a class-path and module-path for loading jars.

- When loaded on the module-path jars are prevented from using the same package. This breaks multi-jar projects like GeoTools library where gt-api defining interfaces, and gt-main providing implementations.

- Jigsaw also locks down aspects of Java reflection, affecting projects like Spring that make heavy use of reflection to "auto wire" GeoServer together. Spring 5 has been released and upgrading to this release will be a key focus.

- With these changes projects like GeoServer need to review of hundreds open source dependencies to determine what other libraries are broken, if an update is available or replacement can be found.

- The java web service framework (responsible for concepts like Servlet and Session) is being removed from Oracle oversight and has been setup as [Jakarta EE Software](https://jakarta.ee).

=== Recommended reading ===

* [https://www.azul.com/what-comes-after-jdk-8/ What Comes After JDK 8?]
* [https://medium.com/criciumadev/its-time-migrating-to-java-11-5eb3868354f9 It's time! Migrating to Java 11] - contains working example of updating spring application
* [http://openjdk.java.net/projects/jigsaw/spec/sotms The State of the Module System] / [https://www.oracle.com/corporate/features/understanding-java-9-modules.html Understanding Java 9 modules]

=== Do you have any experience running sprints? ===

The GeoServer team really benefited from [[Java 2017 Code Sprint|java 2017 code sprint]] and is eager to repeat the success.

== GeoServer Planning ==

Initial planning has started:

* [https://github.com/geoserver/geoserver/wiki/GSIP-171 GSIP 171 Java 18.9 Compatibility] (GeoServer)

Preflight activities:

* dependency audit

Required updates:

* Spring 5 - Older versions of spring are not compatible with Java 11. Upgrading to from Spring 4 to Spring 5 does involve handling some API changes.
* HazelCast - Like Spring, HazelCast involves a lot of reflection.

Module refactor:

* Repackage GeoServer application jars to prevent conflicts at the package level.
* Resulting application can be used on either the CLASSPATH (Java 8) or MODULEPATH (Java 11)

== GeoTools Planning ==

Planning and work is already well underway:

* [https://github.com/geotools/geotools/wiki/Java-9-Compatibility GeoTools Java-9-Compatibility] (GeoTools)

The first completed phase is to allow GeoTools to be used on the classpath:

* [https://github.com/geotools/geotools/wiki/Migrate-Units-to-JSR-363 Migrate Units to JSR-363] (GeoTools)
* [https://github.com/geotools/geotools/wiki/FactoryRegistry-Refactoring-for-Java-9-Compatibility FactoryRegistry Refactoring for Java 9 Compatibility] (GeoTools)

The sprint goal is to refactor the geotools library into modules, allowing the jars to be used on either the classpath (Java 8) or the module path (Java 11).

* [https://github.com/geotools/geotools/wiki/Restructure-GeoTools-into-Jigsaw-modules Restructure GeoTools into Jigsaw modules] (GeoTools)

* Core library refactored into modules

[[File:Gt-modules.png|frameless|GeoTools Java 11 modules ]]

* plugins used to automatic modules to dependencies on the classpath

[[File:Module-path.png|800px|module-path bridge to classpath]]

In the above illustration the gt-svg module is used as an automatic module publishing org.geotools.renderer.style.svg package. It acts as a bridge to the multi-jar project batik still on the classpath, completely masking the fact batik is used used to read and render svg files. The core module gt-renderer publishes select packages for use, while hiding others. It makes use of ServiceLocator to access the IconFactory implemented by gt-svg and never has direct use of the batik implementation.

For this to work the gt-svg jar has been refactored, moving the icon factory the new package org.geotools.style.svg. This was required as the package org.geotools.renderer.style was already published by gt-renderer.

We expect:

* Initial focus is on the core library, refactoring to allow jars to be used on the module path as named modules
* plugins will remain on the classpath, accessed via service locator, any conflicting packages will not be visible to client code

== JTS Topology Suite Activities ==

Results of bonn code sprint:

* [https://github.com/locationtech/jts/pull/274 Add module names for better Java 9/Jigsaw support] (JTS Topology Suite)

JTS jars can be placed on the module-path used as an automatic module, the jars have been supplied am Automatic-Module-Name using a MANIFEST.MF entry.

For an example.application using jts-core as a module add '''module-info''':

module example.application {
requires org.locationtech.jts; // jts-core
}

== GeoNetwork Planning ==

[[https://github.com/geonetwork/core-geonetwork/wiki/OSGeo-Java-codesprint-2018 Strategy for GeoNetwork]]

== How to sponsorship ==

Contributions will be put towards travel costs for sprint participants who would be otherwise unable to attend. Any surplus at the end of the event will be turned over to OSGeo or used for a future code sprint. We have set-up the sprint to minimize travel and accommodation costs.

Sponsors will receive the following benefits / honours:

* Your logo at the top of this page
* Mention in project communication (for example the GeoServer 2.15 release announcement)
* The ability to run on a supported java platform
* Our gratitude :)

This event provides the following sponsorship levels:

{| class="wikitable"
|-
| Gold
| style="text-align:right;" | $2500 USD
|-
| Silver
| style="text-align:right;" | $1500 USD
|-
| Bronze
| style="text-align:right;" | $750 USD
|-
| In-Kind || colspan="3" | In-kind support graciously accepted
|}

This is an official OSGeo event, your contribution counts towards being recognized as an [https://www.osgeo.org/about/how-to-become-a-sponsor/ OSGeo Sponsors].

For more information on sponsorship, please contact [[Jody Garnett]], [[User:Aaime|Andrea Aime]].

=== How to Sponsor ===

# Contact OSGeo [[Treasurer]] for details on using PayPal or to request an invoice:
# The OSGeo [[Treasurer]] will contact both you and the event organizers to acknowledge your sponsorship
#* Please have a logo ready for your organization if you wish to be acknowledged publicly
#* Your event sponsorship, at your request, can contribute towards [http://www.osgeo.org/sponsorship being recognized] as an OSGeo Foundation sponsor

=== Sponsorship Outreach ===

We are reaching out to organizations to see if there is interest in sponsorship:

* Prior sponsors: gaia3d, boundless, ian, geodan, how2map, fossgis, atol, geosolutions, astun
* Local sponsors: astun, vivid solutions, transient software

If there is a lot of local sponsorship we expect to drag the developers away from the task at hand and meet the local community (at a social evening or similar).

=== OSGeo Funding Request ===

The following information is requested by OSGeo Board [[Code_Sprint_Guidelines]], we provided an indication that we would be planning a sprint during the 2018 budget process.

* [[Java_2018_Code_Sprint_Budget_:_Budget|Java 2018 Code Sprint Budget]]

It is intended to that OSGeo be recognized as hosting this event, rather than acknowledged as a sponsor.

[[Category:Code Sprints]]
[[Category:Java Tribe Code Sprint]]

User:Moovida

2018-09-19T07:58:53Z

Moovida:

{{OSGeo Member
|Name=Andrea Antonello
|JobTitle=Tech lead
|Company=HydroloGIS
|Address=Bolzano, Alto Adige, Italia
|Country=Italia
|City=Bolzano
|Coordinate=46.497364, 11.348983
|LocalChapter=GFOSS.it
|Email=andrea.antonello@gmail.com
|SocialMedia=http://twitter.com/themoovida;
|Website=http://www.andreaantonello.com/
|Photo=moovida.jpg
|Languages=Italian; German; English;
|Info=I'm an environmental engineer addicted to GIS development playing in the field of hydrologic and geomorphologic modelling with gvSIG and the Hortonmachine.

Since 2005 I'm cofounder of [http://www.hydrologis.com HydroloGIS], were we mainly develop around and make advanced use of gvSIG, Hortonmachine and Geopaparazzi.
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=Yes
|Translate=No
|PSC=No
|ExBoard=No
|Charter=Yes
|Chair=No
|SolKatz=No
|Committer=No
}}
{{OSGeo Member FormEdit}}
=== [[User:Moovida|Andrea Antonello]] ===

[[File:moovida.jpg|thumb|right|100px|Andrea Antonello]]

[[Category:OSGeo Member]][[Category:Italy]]

Tech lead, HydroloGIS

Location: Bolzano, Alto Adige, Italia

I'm an environmental engineer addicted to GIS development playing in the field of hydrologic and geomorphologic modelling with gvSIG and the Hortonmachine.

Since 2005 I'm cofounder of [http://www.hydrologis.com HydroloGIS], were we mainly develop around and make advanced use of gvSIG, uDig, Hortonmachine and Geopaparazzi.

;OSGeo Experience [[File:OSGeo_coder.png]] [[File:OSGeo_psc.png]] [[File:OSGeo_user.png]]

* core developer of the [http://www.hortonmachine.org/ Hortonmachine] project.
* core developer of the [http://www.geopaparazzi.eu Geopaparazzi] project.
* plugin developer of the [http://www.gvsig.org gvSIG] desktop GIS.
* loves (and goes regularly to) FOSS4G conferences and code sprints
* does training courses on a regular basis

;Contact:
: Personal page: http://www.andreaantonello.com
: Email: andrea DOT antonello AT gmail DOT com
: Twitter: [http://twitter.com/themoovida themoovida]

;Spoken Language(s): Italian, German, English, Spanish

;Profile last updated: 19 September 2018

[[Category:OSGeo Advocate]]

User:Moovida

2018-09-19T07:57:17Z

Moovida:

{{OSGeo Member
|Name=Andrea Antonello
|JobTitle=Tech lead
|Company=HydroloGIS
|Address=Bolzano, Alto Adige, Italia
|Country=Italia
|City=Bolzano
|Coordinate=46.497364, 11.348983
|LocalChapter=GFOSS.it
|Email=andrea DOT antonello AT gmail DOT com
|SocialMedia=http://twitter.com/themoovida;
|Website=http://www.andreaantonello.com/
|Photo=moovida.jpg
|Languages=Italian; German; English;
|Info=I'm an environmental engineer addicted to GIS development playing in the field of hydrologic and geomorphologic modelling with gvSIG and the Hortonmachine.

Since 2005 I'm cofounder of [http://www.hydrologis.com HydroloGIS], were we mainly develop around and make advanced use of gvSIG, Hortonmachine and Geopaparazzi.
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=Yes
|Translate=No
|PSC=No
|ExBoard=No
|Charter=Yes
|Chair=No
|SolKatz=No
|Committer=No
}}
{{OSGeo Member FormEdit}}
=== [[User:Moovida|Andrea Antonello]] ===

[[File:moovida.jpg|thumb|right|100px|Andrea Antonello]]

[[Category:OSGeo Member]][[Category:Italy]]

Tech lead, HydroloGIS

Location: Bolzano, Alto Adige, Italia

I'm an environmental engineer addicted to GIS development playing in the field of hydrologic and geomorphologic modelling with gvSIG and the Hortonmachine.

Since 2005 I'm cofounder of [http://www.hydrologis.com HydroloGIS], were we mainly develop around and make advanced use of gvSIG, uDig, Hortonmachine and Geopaparazzi.

;OSGeo Experience [[File:OSGeo_coder.png]] [[File:OSGeo_psc.png]] [[File:OSGeo_user.png]]

* core developer of the [http://www.hortonmachine.org/ Hortonmachine] project.
* core developer of the [http://www.geopaparazzi.eu Geopaparazzi] project.
* plugin developer of the [http://www.gvsig.org gvSIG] desktop GIS.
* loves (and goes regularly to) FOSS4G conferences and code sprints
* does training courses on a regular basis

;Contact:
: Personal page: http://www.andreaantonello.com
: Email: andrea DOT antonello AT gmail DOT com
: Twitter: [http://twitter.com/themoovida themoovida]

;Spoken Language(s): Italian, German, English, Spanish

;Profile last updated: 19 September 2018

[[Category:OSGeo Advocate]]

Java 2018 Code Sprint

2018-09-19T07:53:30Z

Moovida: /* Participants */

The Java tribe has a real challenge for 2018 - updating our open source projects for the Java roadmap.

== Location ==

Sprint scheduled for Q4 2018, proposed date:

* October 22-26th

We are looking at setting up a distributed sprint with locations in:

* North America - Victoria, Boundless Office, billeting options available for those travelling
* Europe - Sevilla, Spain half.confirmed. Italy or UK have been proposed, recommendations welcome!
* Oceania - recommendations welcome

=== Contacts ===

Jody Garnett

== Sponsors ==

We would like to thank our sponsors!

=== Gold Sponsors ===

TBD

=== Bronze Sponsors ===

TBD

=== In-Kind Support ===

[[File:Boundless_Logo.png|350px|link=http://boundlessgeo.com]] [[File:GeoCat.png|350px|link=https://www.geocat.net]]

== Participants ==

Please add your name and the projects you are planning to sprint and note the likehood of your attendance.

{| style="border: solid grey 1px; width:100%" class="sortable"
|+ Participants
|-
| # || Participant || Country || Organization || Arrival || Departure || Project Work on || Notes || Attendance
|-
| 1 || [[User:Delawen|María Arias de Reyna]] || Spain || GeoCat bv || working remotely || working remotely || GeoNetwork || Notes || Partially working on the codesprint
|-
| 2 || [[User:Jive|Jody Garnett]] || Canada || Boundless || local || local || GeoTools || Able to host guests || Confirmed
|-
| 3 || [[User:Tbarsballe|Torben Barsballe]] || Canada || Boundless || local || local || GT/GS || || Confirmed
|-
| 4 || [[User:ksmith|Kevin Smith]] || Canada || Boundless || local || local || GT/GWC/GS || || Confirmed
|-
| 5 || [[User:dvntucker|Devon Tucker]] || Canada || Boundless || local || local || GT/GS || || Confirmed
|-
| 6 || [[User:moovida|Antonello Andrea]] || Italy || HydroloGIS || TBD || TBD || GT/JTS, Hortonmachine || || Confirmed, waiting on Europa location to be revealed :-)
|-
|}

== Discussion ==

=== Java has a roadmap? ===

Yes, we had a previous sprint focused on Java 8 compatibility, several features had changed breaking compatibility.

More importantly the Java roadmap has changed to a six-month release cycle:

* six month release cycle is already well underway having started with Java 9 and Java 10.

* Oracle is offering three year LTS releases commercially

* AdoptOpenJDK is setting up LTS releases of OpenJDK .. backed by IBM, Microsoft and others.

* RedHat is focusing on LTS (skipping Java 9 and Java 10) and plans to ship OpenJDK based on Java SE 11

=== Why is updating our open source projects for the Java roadmap a challenge? ===

- Java changed the service provider interface plugin system used by GeoTools, forcing the project to write its own replacement.

- The java runtime has been broken up into modules, not all of which are activated by default. We need to review what sections of the JRE we require and ensure they are turned on.

- Java introduced the module system "jigsaw" providing both a class-path and module-path for loading jars.

- When loaded on the module-path jars are prevented from using the same package. This breaks multi-jar projects like GeoTools library where gt-api defining interfaces, and gt-main providing implementations.

- Jigsaw also locks down aspects of Java reflection, affecting projects like Spring that make heavy use of reflection to "auto wire" GeoServer together. Spring 5 has been released and upgrading to this release will be a key focus.

- With these changes projects like GeoServer need to review of hundreds open source dependencies to determine what other libraries are broken, if an update is available or replacement can be found.

- The java web service framework (responsible for concepts like Servlet and Session) is being removed from Oracle oversight and has been setup as [Jakarta EE Software](https://jakarta.ee).

=== Recommended reading ===

* [https://www.azul.com/what-comes-after-jdk-8/ What Comes After JDK 8?]
* [https://medium.com/criciumadev/its-time-migrating-to-java-11-5eb3868354f9 It's time! Migrating to Java 11] - contains working example of updating spring application
* [http://openjdk.java.net/projects/jigsaw/spec/sotms The State of the Module System] / [https://www.oracle.com/corporate/features/understanding-java-9-modules.html Understanding Java 9 modules]

=== Do you have any experience running sprints? ===

The GeoServer team really benefited from [[Java 2017 Code Sprint|java 2017 code sprint]] and is eager to repeat the success.

== GeoServer Planning ==

Initial planning has started:

* [https://github.com/geoserver/geoserver/wiki/GSIP-171 GSIP 171 Java 18.9 Compatibility] (GeoServer)

Preflight activities:

* dependency audit

Required updates:

* Spring 5 - Older versions of spring are not compatible with Java 11. Upgrading to from Spring 4 to Spring 5 does involve handling some API changes.
* HazelCast - Like Spring, HazelCast involves a lot of reflection.

Module refactor:

* Repackage GeoServer application jars to prevent conflicts at the package level.
* Resulting application can be used on either the CLASSPATH (Java 8) or MODULEPATH (Java 11)

== GeoTools Planning ==

Planning and work is already well underway:

* [https://github.com/geotools/geotools/wiki/Java-9-Compatibility GeoTools Java-9-Compatibility] (GeoTools)

The first completed phase is to allow GeoTools to be used on the classpath:

* [https://github.com/geotools/geotools/wiki/Migrate-Units-to-JSR-363 Migrate Units to JSR-363] (GeoTools)
* [https://github.com/geotools/geotools/wiki/FactoryRegistry-Refactoring-for-Java-9-Compatibility FactoryRegistry Refactoring for Java 9 Compatibility] (GeoTools)

The sprint goal is to refactor the geotools library into modules, allowing the jars to be used on either the classpath (Java 8) or the module path (Java 11).

* [https://github.com/geotools/geotools/wiki/Restructure-GeoTools-into-Jigsaw-modules Restructure GeoTools into Jigsaw modules] (GeoTools)

* Core library refactored into modules

[[File:Gt-modules.png|frameless|GeoTools Java 11 modules ]]

* plugins used to automatic modules to dependencies on the classpath

[[File:Module-path.png|800px|module-path bridge to classpath]]

In the above illustration the gt-svg module is used as an automatic module publishing org.geotools.renderer.style.svg package. It acts as a bridge to the multi-jar project batik still on the classpath, completely masking the fact batik is used used to read and render svg files. The core module gt-renderer publishes select packages for use, while hiding others. It makes use of ServiceLocator to access the IconFactory implemented by gt-svg and never has direct use of the batik implementation.

For this to work the gt-svg jar has been refactored, moving the icon factory the new package org.geotools.style.svg. This was required as the package org.geotools.renderer.style was already published by gt-renderer.

We expect:

* Initial focus is on the core library, refactoring to allow jars to be used on the module path as named modules
* plugins will remain on the classpath, accessed via service locator, any conflicting packages will not be visible to client code

== JTS Topology Suite Activities ==

Results of bonn code sprint:

* [https://github.com/locationtech/jts/pull/274 Add module names for better Java 9/Jigsaw support] (JTS Topology Suite)

JTS jars can be placed on the module-path used as an automatic module, the jars have been supplied am Automatic-Module-Name using a MANIFEST.MF entry.

For an example.application using jts-core as a module add '''module-info''':

module example.application {
requires org.locationtech.jts; // jts-core
}

== GeoNetwork Planning ==

[[https://github.com/geonetwork/core-geonetwork/wiki/OSGeo-Java-codesprint-2018 Strategy for GeoNetwork]]

== How to sponsorship ==

Contributions will be put towards travel costs for sprint participants who would be otherwise unable to attend. Any surplus at the end of the event will be turned over to OSGeo or used for a future code sprint. We have set-up the sprint to minimize travel and accommodation costs.

Sponsors will receive the following benefits / honours:

* Your logo at the top of this page
* Mention in project communication (for example the GeoServer 2.15 release announcement)
* The ability to run on a supported java platform
* Our gratitude :)

This event provides the following sponsorship levels:

{| class="wikitable"
|-
| Gold
| style="text-align:right;" | $2500 USD
|-
| Silver
| style="text-align:right;" | $1500 USD
|-
| Bronze
| style="text-align:right;" | $750 USD
|-
| In-Kind || colspan="3" | In-kind support graciously accepted
|}

This is an official OSGeo event, your contribution counts towards being recognized as an [https://www.osgeo.org/about/how-to-become-a-sponsor/ OSGeo Sponsors].

For more information on sponsorship, please contact [[Jody Garnett]], [[User:Aaime|Andrea Aime]].

=== How to Sponsor ===

# Contact OSGeo [[Treasurer]] for details on using PayPal or to request an invoice:
# The OSGeo [[Treasurer]] will contact both you and the event organizers to acknowledge your sponsorship
#* Please have a logo ready for your organization if you wish to be acknowledged publicly
#* Your event sponsorship, at your request, can contribute towards [http://www.osgeo.org/sponsorship being recognized] as an OSGeo Foundation sponsor

=== Sponsorship Outreach ===

We are reaching out to organizations to see if there is interest in sponsorship:

* Prior sponsors: gaia3d, boundless, ian, geodan, how2map, fossgis, atol, geosolutions, astun
* Local sponsors: astun, vivid solutions, transient software

If there is a lot of local sponsorship we expect to drag the developers away from the task at hand and meet the local community (at a social evening or similar).

=== OSGeo Funding Request ===

The following information is requested by OSGeo Board [[Code_Sprint_Guidelines]], we provided an indication that we would be planning a sprint during the 2018 budget process.

* [[Java_2018_Code_Sprint_Budget_:_Budget|Java 2018 Code Sprint Budget]]

It is intended to that OSGeo be recognized as hosting this event, rather than acknowledged as a sponsor.

[[Category:Code Sprints]]
[[Category:Java Tribe Code Sprint]]

OSGeo Code Sprint 2018

2018-04-15T05:21:39Z

Moovida: /* Press Release */

Annual Code Sprint comes to Bonn (Germany) in 2018!

Powered by [[Image:Osgeo-logo.png|250px|link=https://www.osgeo.org]]

'''Sponsoring ''' Find out about [[OSGeo_Code_Sprint_2018#Sponsoring |Sponsoring the Event]].

;Gold Sponsors

{| border=0 cellspacing=15 cellpadding=10
||
[[File:Logo-FOSSGIS-e.V.png‎|280px|FOSSGIS e.V.|link=http://www.fossgis.de]]
 
http://www.fossgis.de
||
[[File:RIEGL.png|310px|RIEGL|link=http://www.riegl.com/]]
 
http://www.riegl.com/
|}

; Silver Sponsors

{| border=0 cellspacing=15 cellpadding=10
||
[[File:Logo-Hobu.png|140px|Hobu|link=https://hobu.co/]]
 
https://hobu.co/
||
[[File:GC-Group logo.png|140px|GeoCue|link=http://www.geocue.com/]]
 
http://www.geocue.com/
|}
; Bronze Sponsors

{| border=0 cellspacing=15 cellpadding=10
||
[[File:Logo-Azavea.png|280px|Azavea|link=http://www.azavea.com/]]
 
http://www.azavea.com/
||
[[File:WhereGroup_logo_418x110.png|290px|WhereGroup|link=https://www.wheregroup.com/]]
 
https://www.wheregroup.com/
||
[[File:Logo-EOX.png|120px|EOX IT Services GmbH|link=http://eox.at]]
 
[http://eox.at http://eox.at]
|-
||
[[File:Synth_Inline_Fill_Gradient_RGB.png|210px|synth3d|link=http://www.synth3d.co]]
 
http://www.synth3d.co
||
[[File:Logo-LocationTech.png|320px|LocationTech|link=https://www.locationtech.org/]]
 
https://www.locationtech.org/
||
[[File:BH PantoneUncoated Preferred BH.PNG|320px|Bohannan Huston, Inc.|link=https://www.bhinc.com]]
 
https://www.bhinc.com
|}

In 2018 we once again want to invite you to Bonn to meet for codesprint at Basecamp! ....

[[Image:FOSS4G_2016_OSGeo_Code_Sprint_indoor_hacking_overview.jpg|400px|thumb|right]]
[[Image:FOSS4G_OSGeo_Code_Sprint_in_Action1.jpg|400px|thumb|right]]

[[Image:Basecamp5.png|300px|thumb]]
[[Image:Basecamp6.png|300px|thumb]]
[[Image:Basecamp7.png|300px|thumb]]
[[Image:Basecamp1.png|300px|thumb]]

[[Image:FOSS4G_2016_OSGeo_Code_Sprint_sponsors.jpg|400px]]

== Purpose ==

Bring together project members to make decisions and tackle larger geospatial
problems as in previous years:
* [[Daytona Beach Code Sprint 2017|Daytona_Beach]] (2017)
* [[Paris Code Sprint 2016|Paris]] (2016)
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)
* [[Vienna Code Sprint 2014|Vienna]] (2014)
* [[Boston Code Sprint 2013|Boston]] (2013)
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)
* [[Montreal Code Sprint 2011|Montreal]] (2011)
* [[New York Code Sprint 2010|New York City]] (2010)
* [[Toronto Code Sprint 2009|Toronto]] (2009)

== Dates and Times ==

Dates:
* Sprint: Sunday-Sunday, March 18 to 25, 2018 (8 days - Arrival/Departure Sundays)

== Other Events from January to March 2018 ==

* '''OSGeo's 12th birthday Feb 4'''
* FOSDEM 3-4 Feb https://fosdem.org/2018/
* FOSS4G IT 19-22 Feb http://foss4g-it2018.gfoss.it/
* [https://github.com/qgis/QGIS/wiki/DeveloperMeetingMadeira2018 QGis Hackfest] 21-25 Feb, 2018
* FOSSGIS 21-24 March https://www.fossgis-konferenz.de/2018/
* ''please add your event''

== Location ==

=== Coding Venue ===
* Venue & Accommodation BaseCamp.
* For more informations: http://www.basecamp-bonn.com/
* [http://www.openstreetmap.org/way/44335958#map=18/50.70763/7.12316| OpenStreetMap]

=== Accommodations ===
* Make sure that you book your accommodation on your own. And also you have to pay for it.
* you can book at BaseCamp directly: http://www.basecamp-bonn.com/
* BONNOX http://www.bonnox.de/en
* You can use this official hotel booking system: http://www.bonn-region.de/events/fossgis-konferenz-english.html

=== How to get there ===
* http://alienus.de/basecamp1/en/arrival-bonn-hostel/
* http://www.openstreetmap.org/search?query=raste%201%20bonn#map=18/50.70762/7.12383

By train
* From Bonn Main station take the U-Trains (Underground platform) 16, 63 or 68. Get off after 6 min at stop Dt. Telekom / Ollenhauerstr.
* http://alienus.de/basecamp1/en/arrival-bonn-hostel/
* http://www.openstreetmap.org/search?query=raste%201%20bonn#map=18/50.70762/7.12383
* [https://www.vrsinfo.de/englisch/the-vrs/vrs-about-us.html online public transport planner]

By Car
* Coming from the highway A59 Basecamp is located at the end of the highway A562. For navigation systems it is best to type Basecamp's address: "''In der Raste 3, 53129 Bonn''")

== Schedule ==
* lunch every day at 12:30
* only sunday march 19th at 19:00

== OSGeo Member Meeting ==
* OSGeo [[Member_Meeting_Bonn_2018]] is scheduled for Monday 19 March 2018 18:00 in Bonn
* you are all welcome to join
* We would like to have a discussion on OSGeo topics for about 2 hours. And OSGeo will provide food and drinks.

== Social Events ==

BaseCamp ist great. But you should also see the outside of BaseCamp and we want to bring you in contact with Bonn and the FOSSGIS e.V. Community (german language Local Chapter of OSGeo)

=== Tuesday 20th March: FOSSGIS ===
* 19:00 Uhr Inofficial Start of FOSSGIS Konferenz
* Gesindehaus in Poppelsdorf (Clemens-August Straße 59)
* everyone pays for themself
* you are welcome to join
* https://www.gesindehaus-bonn.de/
* https://www.openstreetmap.org/way/30070888

=== Wednesday 21th March: FOSSGIS Conference Social Event ===
* Wednesday 21th March 19:00-01:00
* we want to invite you to the event
* with buffet, loo-session and dj team
* Dad's Phonkey in action with his Loop-Station https://de-de.facebook.com/dadsphonkey
* Rafa from DJ Kollektiv Lucha Amada http://luchaamada.blogsport.de/
* see also https://fossgis-konferenz.de/2018/socialevents/
* ''we need the information, whether you need a ticket for the social event - please add to you information in the wiki table above!!!'''

; all evenings ''Pub race'' - find out about pubs in Bonn
* meet at
** Namenlos: http://www.openstreetmap.org/node/1581262116
** Pawlow: http://www.openstreetmap.org/node/225642197

== OSGeo Exhibition Pack ==
* take your OSGeo Exhibition Pack home - get information and make an order [[Talk:Exhibition_Pack#Ordering]]

== Project Plans ==
(i.e what do you wish/want/plan to work on during the sprint ?)

* '''GRASS GIS project''': See [https://grasswiki.osgeo.org/wiki/GRASS_Community_Sprint_Bonn_2018 dedicated Wiki page]
* '''OSGeo Website''':
** document website roles
** double check with attendees that they are setup correctly
* '''OSGeoLive'''
** build documentation - mo 12:00-17:00
** start Release cycle: more info: [https://docs.google.com/spreadsheets/d/1kO6zzmLFfprZGgp5x7Sjwi-EVN6NTGDR4KXvFVtNpR0/edit?hl=en_GB&hl=en_GB#gid=0 OSGeoLive 12 Schedule]
** start of the build cycle for the next OSGeoLive release, 12.0 19 - 23 March
** OSGeoLive12 - how to configure for specific purpose like an INSPIRE flavor 22 - 23 March
* '''OSGeo Europe''' - preparing the website pages, further organizing, coordinate common activities
* '''pycsw''': see [https://github.com/geopython/pycsw/wiki/2018-Bonn-sprint dedicated Wiki page]
* '''MapServer''': see [https://github.com/mapserver/mapserver/wiki/Bonn-2018-Codesprint dedicated Wiki page]
* '''ZOO-Project''': see [http://zoo-project.org/trac/wiki/OSGeoCodeSprint2018 dedicated Wiki page]
* '''Geopaparazzi/gvSIG Mobile''':
** bugfixing
** testing of rspatialite 4.5
** API for synchronization with cloud for server+serverless modes
* '''pgRouting''':
** Release of version 2.5.3
** Release of version 2.6.0
* '''PyWPS''':
** Check Pull-Requests.
** New Release.
** Planning WPS 2.0.0 implementation.
** Having a look at OWSContext: http://www.owscontext.org/
** Discuss WPS2.0-REST: https://52north.github.io/tamis-rest-api/
** Look at Docker extension pull-request
** OSGeo incubation: one last review before submitting for graduation ([[User:Tomkralidis]])
* '''OWSLib''':
** fix test-suite.
** pep8.
** owslib.wps:
*** Planning WPS 2.0.0 implementation.
*** Handling SSL certificates.
* '''TEAM Engine''': See [https://github.com/opengeospatial/teamengine/issues/322 TEAM Engine code sprint at OSGeo Code Sprint in Bonn, Germany (2018-03-20)]
* '''Raster Processing Engine''': architecture / api spike
* '''JTS Topoligy Suite''':
** Java jigsaw module manifests
* '''GeoTools''':
** re [https://github.com/geotools/geotools/wiki/GeoTools-Codebase-Reformat code-format all active branches]
** branch to [https://github.com/geotools/geotools/wiki/Java-9-Compatibility repackage library modules] for java jigsaw
** [https://github.com/geotools/geotools/wiki/Replace-JSR-275-Units-Library replace JSR-275 Unit library] to avoid Java 18.3 conflict
* '''uDig''':
** Look at minimal viable code-contribution for LocationTech, avoiding JAI dependency
* '''GeoHealthCheck''':
** re [https://github.com/geopython/GeoHealthCheck/ high prio issues and PRs]
** re-architecture/REST API
* '''deegree project''': See [https://github.com/deegree/deegree3/wiki/2018-OSGeo-CodeSprint dedicated Wiki page]

== Participants ==

Please add your name and the projects you are planning to sprint and note the likeliness of your attendance.

{| border="1" cellpadding="2" class="wikitable sortable"
!width="25"|No
!width="250"|Name
!width="100"|Country
!width="250"|Email
!width="250"|Organisation
!width="250"|Projects
!width="25"|sun
!width="25"|mon
!width="25"|tue
!width="25"|wed
!width="25"|thu
!width="25"|fri
!width="25"|sat
!width="25"|sun
!width="60"|Accommodation
!width="30"|vegetarian food
!width="60"|social event
|-
| 1 ||[[Jeff McKenna]] <libravatar email="jmckenna@gatewaygeomatics.com"/> || CA || jmckenna(at)osgeo.org || OSGeo || MapServer, MS4W, ZOO-Project || x || x || x || x || x || x || || || AirBNB || || x
|-
| 2 ||[[Howard Butler]] || US || howard@hobu.co || Hobu, Inc. || Proj.4, PDAL, GDAL, Point clouds || || x || x || x || x || x || || || || No thank you. ||
|-
| 3 ||[[Even Rouault]] || FR || even.rouault(at)spatialys.com || Spatialys || Proj.4, GDAL, MapServer || || x || x || x || x || x || || || BaseCamp || || x
|-
| 4 ||[[Markus Neteler]] || DE || neteler(at)osgeo.org || mundialis || GRASS GIS (Proj.4, GDAL, OTB, QGIS) || x || x || x || x || x || x || x || x || || preferably ||
|-
| 5 ||[[User:Djay|Gérald Fenoy]] || FR || gerald.fenoy(at)geolabs.fr || GeoLabs || MS4W, ZOO-Project || x || x || x || x || x || x || x || x || shared accommodation || ||
|-
| 6 ||[[User:Schpidi|Stephan Meißl]] || AT || stephan(at)meissl.name || EOX || MapServer, EOxServer || || x || x || x || x || x || || || BaseCamp || || x ||
|-
| 7 ||[[User:martinl|Martin Landa]] || CZ || landa.martin(at)gmail.com || CTU in Prague || GRASS GIS (Proj.4, GDAL, PostGIS, QGIS) || x || x || x || x || x || x || x || x || BaseCamp || ||
|-
| 8 ||[[User:connormanning|Connor Manning]] || US || connor@hobu.co || Hobu, Inc. || Entwine, Greyhound, PDAL, Point clouds || x || x || x || x || x || x || x || x || || ||
|-
| 9 ||Markus Schütz || AT || mschuetz@potree.org|| TU Wien|| Potree, point clouds|| || x || x || x || x || x || || || || ||
|-
| 10 ||[[User:Tomkralidis|Tom Kralidis]] || CA || tomkralidis(at)gmail.com || self || pycsw, OWSLib, pygeometa, MapServer, geocatalogo || x || x || x || x || x || || || || tbd || sure || x ||
|-
| 11 ||[[User:kalxas|Angelos Tzotsos]] || GR || tzotsos(at)osgeo.org || OSGeo || pycsw, OSGeoLive, GeoNode, UbuntuGIS, OTB, ZOO-Project || x || x || x || x || x || x || x || x || booked || No || x ||
|-
| 12 ||[[User:jjesus|Jorge Samuel Mendes de Jesus]] || NL || jorge.dejesus(at)geocat.net || Geocat || pywps || || || || x || x || x || x || || AirBNB || NO! ||
|-
| 13 ||[[User:ingenieroariel|Ariel Núñez]] || CO || ariel(at)terranodo.io || Terranodo || GeoNode || x || x || x || x || x || x || x || x || tbd || ||
|-
| 14 ||[[User:Lads|Luís de Sousa]] || PT & NL || luis.de.sousa(at)protonmail.ch || [http://www.isric.org ISRIC] || PyWPS, GRASS || || || || x || x || x || x || x || BaseCamp || ||
|-
| 15 ||[[User:Vmische|Volker Mische]] || DE || volker.mische(at)gmail,com || Myself || Noise, CouchDB || x || x || x || x || x || x || x || x || BaseCamp || 50% ||
|-
| 16 ||[[User:Just|Just van den Broecke]] || NL || justb4(at)gmail,com || Myself || GeoHealthCheck, Stetl || x || x || x || x || x || x || x || x || Booked || - || x
|-
| 17 ||[[User:Jgrocha|Jorge Gustavo Rocha]] || PT || jgr@geomaster.pt || Geomaster || QGIS, GeoExt 3, Nominatim || || x || x || x || x || x || 2 x || 2 x || BaseCamp || || x
|-
| 18 ||[[User:tfr42|Torsten Friebe]] || DE || friebe AT lat-lon DOT de || lat/lon || deegree || || x || || x || x || x || || || not needed || yes, please ||
|-
| 19 ||[[User:Stenger|Dirk Stenger]] || DE || stenger AT lat-lon DOT de || lat/lon || deegree, TEAM Engine || || x || x || || || || || || not needed || ||
|-
| 20 ||[[User:Lgoltz|Lyn Goltz]] || DE || goltz AT lat-lon DOT de || lat/lon || deegree, TEAM Engine || || x || x || || || || || || not needed || yes ||
|-
| 21 ||[[User:remanuele|Rob Emanuele]] || US || remanuele@azavea.com ||Azavea || PDAL, GDAL, Point clouds, GeoTrellis, LocationTech || || x || x || x || x || x || || || || ||
|-
| 22 || Grigory Pomadchin || RU || gr.pomadchin AT gmail DOT com || Azavea || PDAL, GDAL, Point clouds, GeoTrellis || || x || x || x || x || x || || || || ||
|-
| 23 ||[[User:tomvantilburg|Tom van Tilburg]] || NL || tom.van.tilburg@geodan.nl || geodan || Pointcloud || || x || x || x || x || x || x || || tbd || x|- ||
|-
| 24 ||[[User:chambbj|Brad Chambers]] || US || bradley.chambers@digitalglobe.com || Radiant Solutions || PDAL, Point Clouds || || x || x || x || x || x || || || TBD || No thanks! ||
|-
| 25 || Eugene Cheipesh || USA || echeipesh AT azavea DOT com || Azavea || LocationTech, JTS, JAI Replacement || || x || x || x || x || x || || || || x || x ||
|-
| 26 || [[User:Lucadelu|Luca Delucchi]] || IT || lucadeluge AT gmail DOT com || Fondazione Edmund Mach || GRASS GIS, OSGeoLive, pyModis || x || x || x || x || x || x || ? || ? || Basecamp || | || x
|-
| 27 || [[User:Veroandreo|Veronica Andreo]] || AR/NL || veroandreo AT gmail.com || on-my-own-time || GRASS GIS || x || x || x || x || x || x || x || ? || Basecamp || | || x
|-
| 28 || [[User:dirkf|Dirk Frigne]] || BE || Dirk AT Geosparc.com || OSGeo Europe || GeoMajas OSGeo Live || x || x || x || - || x || x || || || motor home || | ||
|-
| 29 ||[[User:msmitherdc|Michael Smith]] || US || michael.smith.erdc at gmail.com || US Army Corps || MapServer, PDAL || x || x || x || x || x || x || x || x || hotel || | ||
|-
| 30 ||[[User:cvvergara| Vicky Vergara]] || MX || vicky at georepublic DOT de || Georepublic || pgRouting, OSgeoLive, PDAL, Point clouds || x || x || x || x || x || x || x || x || Basecamp || | ||
|-
| 31 ||Marco Hugentobler || CH || marco at sourcepole dot com || Sourcepole || QGIS || || x || x || x || x || x || || || BaseCamp || ||
|-
| 32 ||[[User:Pirmin_Kalberer|Pirmin Kalberer]] || CH || pka at sourcepole dot com || Sourcepole || QGIS, GDAL, t-rex || || x || x || x || x || x || || || BaseCamp || ||
|-
| 33 ||[[User:Mlennert|Moritz Lennert]] || BE || mlennert at club dot worldonline dot be || ULB || GRASS GIS || x || x || x || x || || || || || BaseCamp || preferably ||
|-
| 34 ||[[Andrew Bell]] || US || andrew@hobu.co || Hobu, Inc. || Proj.4, PDAL, Point clouds, meshes || || x || x || x || x || x || || || || ||
|-
| 35 ||[[User:theduckylittle|Dan "Ducky" Little]] || US || dlittle@boundlessgeo.com || Boundless || React + OpenLayers, MapServer || || || x || x || x || x || x || FeWo || || || x
|-
| 36 ||[[User:nicklas|Nicklas Avén]] || SE/NO || nicklas.aven@jordogskog.no || Just me || TilelessMap, PostGIS || x || x || x || x || x || x || x || || BaseCamp || || x
|-
| 37 ||[[User:Clucas|Chris Lucas]] || NL || chris.lucas@geodan.nl || Geodan || PDAL, point clouds || || x || x || x || x || x || || || tbd || | ||
|-
| 38 ||[[User:Marcjansen|Marc Jansen]] || DE || jansen@terrestris.de || terrestris || OpenLayers, react-geo, GeoExt || (x) || x || x || (x) || (x) || (x) || || || not needed || | ||
|-
| 39 ||[[User:Mlechner|Marco Lechner]] || DE || marco.lechner@fossgis.de || [https://www.fossgis.de FOSSGIS e.V.]/[https://github.com/OpenBfS BfS] || OpenLayers, Geonetwork, Geoserver, everything || (x) || x || x || (x) || (x) || (x) || || || BaseCamp || veg. ||
|-
| 40 ||[[Martinheidegger|Martin Heidegger]] || JP/AT || martin.heidegger@gmail.com || Freelancer (Georepublic) || Point clouds, dotloom, pix4d/potree || (x) || x || x || x || (x) || || || || BaseCamp || || x ||
|-
| 41 ||[[User:moovida|Andrea Antonello]] || IT || andrea.antonello@gmail.com || HydroloGIS / Free University of Bolzano || Geopaparazzi, gvSIG, gvSIG Mobile, everything || (x) || x || x || x || x || x || || || TBD || no ||
|-
| 42 ||[[User:Astrid_Emde|Astrid Emde]] || DE || astrid_emde@osgeo.org || WhereGroup/OSGeo || Mapbender, OSGeoLive, OSGeo || x || x || x || || || || x || x || BaseCamp || vegetarian ||
|-
| 43 ||[[User:GeoFootballer|Christian Mayer]] || DE || chris@meggsimum.de || meggsimum || OpenLayers, GeoExt || (x) || x || x || (x) || (x) || (x) || || || not needed || | ||
|-
| 44 || Andreas Schmitz || DE || schmitz@terrestris.de || terrestris || OpenLayers, react-geo, GeoExt || (x) || x || x || (x) || (x) || (x) || || || not needed || | ||
|-
| 45 ||[[User:Ckuntzsch|Christian Kuntzsch]] || DE || Christian.Kuntzsch@wheregroup.com || WhereGroup || Mapbender || x || x || x || x || || || || || BaseCamp || ||
|-
| 46 || Nina Moelkner || DE || nina.moelkner@wheregroup.com || WhereGroup || Mapbender || || x || x || || || || || || not needed || ||
|-
| 47 || Robin Schwammborn || DE || robin.schwammborn@wheregroup.com || WhereGroup || Mapbender || || x || x || || || || || || not needed || ||
|-
| 48 ||[[User:dispiste|Cesar Martinez]] || ES || cesar.izq@gmail.com || gvSIG/Scolab || gvSIG, gvSIG Mobile, Geopaparazzi || x || x || x || x || x || || || || BaseCamp if possible || not needed ||
|-
| 49 || Thekla Wirkus || DE || thekla.wirkus@wheregroup.com || WhereGroup || Mapbender || || x || || || || || || || not needed || ||
|-
| 50 || [[User:axxl|Axel Schaefer]] || DE || axel.schaefer@wheregroup.com || WhereGroup || Mapbender || || x || (x) || || || || || || not needed || ||
|-
| 51 || [[User:mmetz|Markus Metz]] || DE || metz@mundialis.de || mundialis || GRASS GIS (Proj.4, GDAL, OTB, QGIS) || x || x || x || x || || || || || Base Camp || not needed || x
|-
| 52 || [[User:Taehoon.Kim|Taehoon Kim]] || JP/KR || kim.taehoon@aist.go.jp || AIST || Point clouds || (x) || x || x || x || x || x || x || || || ||
|-
| 53 || Marco Pochert || DE || mpochert@bfs.de || [https://github.com/OpenBfS BfS] || OpenLayers, Geonetwork, GeoExt, everything || (x) || x || x || (x) || (x) || (x) || || || BaseCamp || ||
|-
| 54 ||[[User:bartvde2|Bart van den Eijnden]] || Netherlands || bartvde@boundlessgeo.com || Boundless || React + OpenLayers || x || x || x || x || x || || || || || || x
|-
| 55 ||[[User:FxKu|Felix Kunde]] || DE || felix-kunde@gmx.de || Beuth University || 3DCityDB and testing GMLAS tools || || x || x || || || || || || HBF || ||
|-
| 56 ||[[User:SBL|Stefan Blumentrath]] || NO || stefan.blumentrath@nina.no || Norwegian Institute for Nature Research (NINA) || GRASS GIS || || || x || x || x || x || x || x || ? || ||
|-
| 57 ||[[User:elpaso|Alessandro Pasotti]] || IT || elpaso@itopen.it || ItOpen || QGIS || x || x || x || x || x || x || || || Base Camp || ||
|-
| 58 ||[[Milena Nowotarska]] || PL || milena.osgeo(at)gmail.com || OSGeo / GISTRA|| GRASS GIS, QGIS, OSGeoLive || || || || || || x || x || x || || gluten free ||
|-
| 59 ||[[Vasile Craciunescu]] || RO || vasile(at)geo-spatial.org || OSGeo / geo-spatial.org|| FOSS4G2019 || x || x || x || || || || || || BaseCamp || ||
|-
| 60 ||[[User:Olr|Oliver Rudzick]] || DE || osm(at)rudzick.de || FOSSGIS || OSM || x || || x || (x) || (x) || (x) || x || x || not needed || ||
|-
| 61 ||[[User:Uli|Uli Rothstein]] || DE || uli.rothstein(at)fossgis.de || terrestris / FOSSGIS || Orga || x || || x || (x) || (x) || (x) || x || x || not needed || ||
|-
| 62 ||Nils Bühner || DE || buehner(at)terrestris.de || terrestris || SHOGun, react-geo || || x || x || || || || || || not needed || ||
|-
| 63 ||Daniel Koch || DE || koch(at)terrestris.de || terrestris || SHOGun, react-geo || || x || x || (x) || (x) || (x) || || || not needed || ||
|-
| 64 ||Kai Volland || DE || volland(at)terrestris.de || terrestris || react-geo || || x || x || || || || || || not needed || ||
|-
| 65 ||Johannes Weskamm || DE || weskamm(at)terrestris.de || terrestris || OSM-Vector-Tiles / react-geo || x || x || x || || || || || || not needed || ||
|-
| 66 ||Carmen Tawalika || DE || tawalika(at)mundialis.de || mundialis || actinia || x || x || x || x || || || x || x || not needed || ||
|-
| 67 ||Frank Gasdorf|| DE || fgdrf(at)users.sourceforge.net || || uDig, Geotools, LocationTech, JTS, JAI Replacement|| || || || x || x || x || || || TBD || ||
|-
| 68 ||[[User:Rzoller|Roman Zoller]] || CH || roman.zoller ät camptocamp.com || Camptocamp || OpenLayers / react-geo / TBD? || || || || (x) || (x) || (x) || x || x || Hotel || ||
|-
| 69 ||[[User:Jive|Jody garnett]] || CA || jody.garnett@gmail.com || OSGeo || GeoTools || x || x || x || x || x || x || x || || base camp|| whiskey ||
|-
| 70 || Seth Girvin || IE || sgirvin@compass.ie || Compass Informatics || MapServer, GeoExt || || x || x || x || x || x || || || Basecamp || ||
|-
| 71 ||[[User:Delawen|María Arias de Reyna]] || ES || maria.arias@geocat.net || GeoCat bv,OSGeo || GeoNetwork || x || x || x || || || || || || - || no ||
|-
| 72 ||Mario Härtwig || DE || mario.haertwig(at)geops.de || geOps || OpenLayers Editor || x || x || x || || || || || || BaseCamp || ||
|-
| 73 ||[[User:Friedjoff|Friedjoff Trautwein]] || DE || friedjoff.trautwein(at)geops.de || geOps || OpenLayers Editor || x || x || x || || || || || || BaseCamp || ||
|-
| 74 ||[[User:Bluemates|Kyoung-Sook Kim]] || JP || ks.kim(at)aist.go.jp || AIST || Point clouds || || || || (x) || x || x || x || || || ||
|-
| 75 ||[[User:CEhbrecht|Carsten Ehbrecht]] || DE || ehbrecht(at)dkrz.de || DKRZ || pywps, owslib || || || x || x || x || (x) || || || Hotel || no ||
|-
| 76 ||[[User:johanvdw|Johan Van de Wauw]] || BE || johan AT gisky.be || gisky || saga, osgeo live, owslib, debian/ubuntu || || || || x || x || x || x || || Basecamp || none || x
|-
| 77 ||[[User:plimkilde|Peter Limkilde Svendsen]] || DK || pelis åt sdfe dot dk|| [http://sdfe.dk SDFE] || Point clouds || (x) || x || x || x || x || (x) || || || - || ||
|-
| 78 ||[[User:Akotsev|Alexander Kotsev]] || IT || alexander.kotsev åt ec dot europa dot eu|| [https://ec.europa.eu/jrc/en EC/JRC] || || || || || || x || x || || || || ||
|-
| 79 ||[[User:pesekon2|Ondřej Pešek]] || CZ || pesej.ondrek(at)gmail.com || CTU in Prague || GRASS GIS || x || x || x || x || x || x || x || x || BaseCamp || ||
|-
| 80 ||[[User:ctoma|Charlotte Toma]] || DE || charlotte.toma(at)wheregroup.com || WhereGroup || Mapbender || || x || x || || || || || || no || no || x
|-
| 81 ||Paul S || DE || paul.schell(at)wheregroup.com || WhereGroup || Mapbender || || x || x || || || || || || no || no || x
|-
| 82 ||Julius Krey || DE || julius.krey(at)wheregroup.com || WhereGroup || Mapbender || || x || x || || || || || || no || no ||
|-
| 83 ||Daniel Santillan || AT || daniel.santillan@eox.at || EOX || plotty, 3D JavaScript in general || || x || x || x || || || || || BaseCamp || ||
|-
| 84 ||Anton Wagensonner || AT || awagensonner(at)riegl.com || RIEGL || point clouds, PDAL || || x || x || || || || || || hotel || no ||
|-
| 85 || Norbert Wenzel || AT || nwenzel(at)riegl.com || RIEGL || point clouds, PDAL || || x || x || || || || || || hotel || no ||
|-
| 86 || Kris Depril || BE || Kris.depril@geosparc.com || Geosparc || OSGeoLive || x || x || x || || || || || || not needed || ||
|-
| 87 || Sophie Herrmann || AT || sophie.herrmann@eodc.eu || eodc || pycsw || x || x || x || || || || || || hotel || ||
|-
| 88 || André Henn || DE || henn@terrestris.de || terrestris || react-geo / SHOGun || || x || x || || || || || || not needed || ||
|-
| 89 || Anika Bettge || DE || bettge@mundialis.de || mundialis || GRASS GIS || || || x || || || || || || || ||
|-
| 90 || Hajar Benelcadi || DE || benelcadi@mundialis.de || mundialis || OTB, GRASS GIS, snappy || || || || x || || || || || yes please || ||
|-
| 91 ||[[User:Hannes|Johannes Kröger]] || DE || hannes ät enjoys dot it || me || GDAL, QGIS || || x || x || || || || || || || ||
|-
| 92 ||[[User:StephanR|Stephan Reichhelm]] || DE || reichhelm AT grit.de|| grit GmbH || deegree || || x || || || || || || || not needed || No ||
|-
| 93 ||[[User:Radeknovotny94|Radek Novotný]] || CZ || radeknovotny94(at)gmail.com || CTU in Prague || GRASS GIS || x || x || x || x || x || x || || || || ||
|-
| 94 ||[[User:Nikos|Nikos Alexandris]] || DE || nik@nikosalexandris.net || Freelancer || GRASS GIS || || x || x || x || x || x || || || ? || - ||
|-
| 95 ||[[User:Hholzgra|Hartmut Holzgraefe]] || DE || hartmut@php.net || MariaDB Corp. || maposmatic, mapnik || (x) || x || x || (x) || (x) || (x) || - || (?) || hotel || ||
|-
| # ||[[User:your osgeo profile|Your name]] || DE || email || organization || project || x || x || x || x || x || x || x || x || ?Accommodation || ?vegetarian || do you need a ticket for the social event? yes=x
|}

== Communication ==

* Please join the mailing list: https://lists.osgeo.org/mailman/listinfo/tosprint
* IRC chat during the event: #tosprint Server: irc.freenode.net
* Twitter: #TOSprint ( https://twitter.com/search?q=tosprint )

== Costs ==

Participants should plan for the following costs:

* Travel to Bonn
* Accommodation for x nights

All other costs - food, outings and entertainment - should/will be covered by the sponsors

== Individual preparation ==

* Bring your own laptop
* Bring [https://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:Schuko_plug_and_socket.png Germany]). See also http://www.power-plugs-sockets.com/
* Install Git and compiler tools, and come with a working development environment

== Sponsoring ==

The Open Source Geospatial Foundation (OSGeo) has a long tradition of organizing code sprints for developers of Open Source GIS software.
(https://wiki.osgeo.org/wiki/Category:Code_Sprints).

Simultaneously with the [https://www.fossgis-konferenz.de/2018/ FOSSGIS Conference 2018 in Bonn] an international code sprint of the OSGeo will take place from 19 to 25 March 2018.
We expect about 80 developers from all over the world to come from various [https://www.osgeo.org/] projects. Whether desktop application, geospatial library, metadata catalog or web mapping: be sure to find products in the list that you use. Thus, the Code Sprint is also an opportunity for your developers to meet with the core developers of the projects, get a deeper insight into the software and participate in the development.

The code sprint will take place at [http://www.basecamp-bonn.de/ BaseCamp] in Bonn. During the [http://www.foss4g2016.org/home.html FOSS4G 2016] in Bonn we have already organized a code sprint at this location, in which about 100 developers worked on the open source projects every day. (https://wiki.osgeo.org/wiki/FOSS4G_2016_Code_Sprint)

In addition to the costs of providing the technical infrastructure, the cost of food and drinks for the developers is the main cost. A buffet at lunchtime and drinks during the whole day are intended.

So far, the code sprint is already sponsored by [https://www.osgeo.org/ OSGeo] and [https://www.fossgis.de/ FOSSGIS e. V.].

In order to cover the costs, we would be very pleased about further sponsors!

What we offer:
* Your logo on top of the [https://www.osgeo.org/events/osgeo-code-sprint-2018/ websites of the Code Sprint] [https://wiki.osgeo.org/wiki/OSGeo_Code_Sprint_2018 1] as well as on all official documents around the Code Sprint
* Mention in all code sprint related mails
* Our undying gratitude, which comes in handy when you least expect it (Remember that feature you wanted...)

Our sponsorship levels:
* Gold: >= 2500 USD
* Silver: 1500 USD
* Bronze: 750 USD

So...
* get your company talking to the top developers of the scene!
* enable your GIS developers to take advantage of this opportunity, there is no better opportunity to learn!
* support the software you use - you benefit immediately.

Thank you very much!

Contact: To sponsor, please contact codesprint@osgeo.org directly.

== Event Owner ==
* [[User:Astrid_Emde|Astrid Emde]]
* Uli Rothstein
* Carmen Tawalika
* [[User:Olr|Oliver Rudzick]]
* Mirko Blinn

; Supported by
* [[User:Lucadelu|Luca Delucchi]]

== Press Release ==

; Impressions from OSGeo Code Sprint 2018 in Bonn

For a whole week from March 18 to 25, 2018 nearly 100 active members of the OSGeo Community came to Bonn for the OSGeo Code Sprint 2018 to discuss and work on their projects.

'''Photo Impressions '''
There are some photos from the event at flickr:
https://www.flickr.com/photos/143943250@N05/albums/72157691529787542
Find also some Photos from FOSSGIS Conference https://www.flickr.com/groups/4529299@N22/

Read about the '''goals of the projects and what happened during the week:'''

'''Entwine'''
* [https://github.com/connormanning/ept EPT] implementation for [http://potree.org Potree]

'''GeoHealthCheck (GHC)'''
* Per-Resource Scheduling ([https://github.com/geopython/GeoHealthCheck/tree/per_resource_scheduling link])
* Re-architecture to run in all-in-one daemon mode
* Docker deployment improvements
* Presented [https://media.ccc.de/v/2018-5294-geohealthcheck GHC at FOSSGIS]
* OSGeo Community Project start

'''GRASS GIS'''
* A lot of work, please look at the [https://grasswiki.osgeo.org/wiki/Talk:GRASS_Community_Sprint_Bonn_2018 dedicated GRASS GIS wiki page]
* press release forthcoming

'''MoU TIB'''
During the Code Sprint the Mou between OSGeo and Technische Informationsbibliothek (TIB) – German National Library of Science and Technology was signed. Maria Arias de Reyna, President, Open Source Geospatial Foundation and Dr. Bastian Drees on behalf of Prof. Dr. Sören Auer, Director, Technische Informationsbibliothek (TIB) signed the MoU. Read more at [[MOU_TIB]].

'''PyWPS'''
* Code sprint summary at the [https://github.com/geopython/pywps/wiki/Code-Sprint-2018-Bonn GitHub Wiki]
* [http://osgeo-org.1560.x6.nabble.com/recommend-PyWPS-for-graduation-td5359073.html PyWPS was proposed for OSGeo graduation]

'''OSGeoLive'''
* Tasks for incubation were done
** Provenance review
** Final touches of the new Documentation framework

'''OpenLayers'''
Mapbox styles generation library from OpenLayers (ol-mapbox-style) and upgrading the Boundless SDK (not an OSGeo project, but open source: https://github.com/boundlessgeo/sdk/) to OpenLayers 5.

'''OWSLib'''
* Merged Pull-Requests
* Fixed test-suite

'''PDAL'''
* [https://medium.com/@chambbj/pdal-at-the-osgeo-code-sprint-cf0a56eee59d Refactored documentation and website]
* Conda builds
* Numpy reader support
* 1.7.0 release preparation
* OSGeo4W builds
* Windows building and testing

'''PgRouting'''
* Released 2.5.3
* Released 2.6.0
* [https://www.osgeo.org/foundation-news/pgrouting-v2-6-0-release/ on the news]

'''SAC'''
* Website roles assignment to project members
* Open issues when needed

'''TEAM Engine'''
* Discussed test strategies for test suites and enhanced the existing tests for ETS WFS 2.0 [https://github.com/opengeospatial/teamengine/issues/318 #318].
* Enhanced the transformation from the CTL log to the EARL report by mapping hierarchies. In addition some bugs was fixes in the transformation [https://github.com/opengeospatial/teamengine/issues/319 #319].

'''Geopaparazzi'''
* Added Cloud Profiles, allowing users to easily download complex data sets from the web [https://github.com/geopaparazzi/geopaparazzi/issues/441 #441].
* Added view-only of geographic feature attributes
* Enhanced the viewing of files (images, PDFs, etc) linked to geographic features [https://github.com/geopaparazzi/geopaparazzi/issues/454 #454].
* Various bug fixes [https://github.com/geopaparazzi/geopaparazzi/issues/456 #456], [https://github.com/geopaparazzi/geopaparazzi/issues/460 #460], [https://github.com/geopaparazzi/geopaparazzi/issues/461 #461], [https://github.com/geopaparazzi/geopaparazzi/issues/466 #466].

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]

OSGeo Code Sprint 2018

2018-03-13T11:04:43Z

Moovida: /* Project Plans */

Annual Code Sprint comes to Bonn (Germany) in 2018!

Powered by [[Image:Osgeo-logo.png|250px|link=https://www.osgeo.org]]

'''Sponsoring ''' Find out about [[OSGeo_Code_Sprint_2018#Sponsoring |Sponsoring the Event]].

;Gold Sponsors

{| border=0 cellspacing=15 cellpadding=10
||
[[File:Logo-FOSSGIS-e.V.png‎|280px|FOSSGIS e.V.|link=http://www.fossgis.de]]
 
http://www.fossgis.de
||
[[File:RIEGL.png|310px|RIEGL|link=http://www.riegl.com/]]
 
http://www.riegl.com/
|}

; Silver Sponsors

[[File:Logo-Hobu.png|140px|Hobu|link=https://hobu.co/]]
 
https://hobu.co/

; Bronze Sponsors

{| border=0 cellspacing=15 cellpadding=10
||
[[File:Logo-Azavea.png|280px|Azavea|link=http://www.azavea.com/]]
 
http://www.azavea.com/
||
[[File:WhereGroup_logo_418x110.png|290px|WhereGroup|link=https://www.wheregroup.com/]]
 
https://www.wheregroup.com/
||
[[File:Logo-EOX.png|120px|EOX IT Services GmbH|link=http://eox.at]]
 
[http://eox.at http://eox.at]
|-
||
[[File:Synth_Inline_Fill_Gradient_RGB.png|210px|synth3d|link=http://www.synth3d.co]]
 
http://www.synth3d.co
||
[[File:Logo-LocationTech.png|320px|LocationTech|link=https://www.locationtech.org/]]
 
https://www.locationtech.org/
||
[[File:BH PantoneUncoated Preferred BH.PNG|320px|Bohannan Huston, Inc.|link=https://www.bhinc.com]]
 
https://www.bhinc.com
|}

In 2018 we once again want to invite you to Bonn to meet for codesprint at Basecamp! ....

[[Image:FOSS4G_2016_OSGeo_Code_Sprint_indoor_hacking_overview.jpg|400px|thumb|right]]
[[Image:FOSS4G_OSGeo_Code_Sprint_in_Action1.jpg|400px|thumb|right]]

[[Image:Basecamp5.png|300px|thumb]]
[[Image:Basecamp6.png|300px|thumb]]
[[Image:Basecamp7.png|300px|thumb]]
[[Image:Basecamp1.png|300px|thumb]]

[[Image:FOSS4G_2016_OSGeo_Code_Sprint_sponsors.jpg|400px]]

== Purpose ==

Bring together project members to make decisions and tackle larger geospatial
problems as in previous years:
* [[Daytona Beach Code Sprint 2017|Daytona_Beach]] (2017)
* [[Paris Code Sprint 2016|Paris]] (2016)
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)
* [[Vienna Code Sprint 2014|Vienna]] (2014)
* [[Boston Code Sprint 2013|Boston]] (2013)
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)
* [[Montreal Code Sprint 2011|Montreal]] (2011)
* [[New York Code Sprint 2010|New York City]] (2010)
* [[Toronto Code Sprint 2009|Toronto]] (2009)

== Dates and Times ==

Dates:
* Sprint: Sunday-Sunday, March 18 to 25, 2018 (8 days - Arrival/Departure Sundays)

== Other Events from January to March 2018 ==

* '''OSGeo's 12th birthday Feb 4'''
* FOSDEM 3-4 Feb https://fosdem.org/2018/
* FOSS4G IT 19-22 Feb http://foss4g-it2018.gfoss.it/
* [https://github.com/qgis/QGIS/wiki/DeveloperMeetingMadeira2018 QGis Hackfest] 21-25 Feb, 2018
* FOSSGIS 21-24 March https://www.fossgis-konferenz.de/2018/
* ''please add your event''

== Location ==

=== Coding Venue ===
* Venue & Accommodation BaseCamp.
* For more informations: http://www.basecamp-bonn.com/
* [http://www.openstreetmap.org/way/44335958#map=18/50.70763/7.12316| OpenStreetMap]

=== Accommodations ===
* Make sure that you book your accommodation on your own. And also you have to pay for it.
* you can book at BaseCamp directly: http://www.basecamp-bonn.com/
* BONNOX http://www.bonnox.de/en
* You can use this official hotel booking system: http://www.bonn-region.de/events/fossgis-konferenz-english.html

=== How to get there ===
* http://alienus.de/basecamp1/en/arrival-bonn-hostel/
* http://www.openstreetmap.org/search?query=raste%201%20bonn#map=18/50.70762/7.12383

By train
* From Bonn Main station take the U-Trains (Underground platform) 16, 63 or 68. Get off after 6 min at stop Dt. Telekom / Ollenhauerstr.
* http://alienus.de/basecamp1/en/arrival-bonn-hostel/
* http://www.openstreetmap.org/search?query=raste%201%20bonn#map=18/50.70762/7.12383
* [https://www.vrsinfo.de/englisch/the-vrs/vrs-about-us.html online public transport planner]

By Car
* Coming from the highway A59 Basecamp is located at the end of the highway A562. For navigation systems it is best to type Basecamp's address: "''In der Raste 3, 53129 Bonn''")

== Schedule ==
* lunch every day at 12:30
* only sunday march 19th at 19:00

== OSGeo Member Meeting ==
* OSGeo [[Member_Meeting_Bonn_2018]] is scheduled for Monday 19 March 2018 18:00 UTC in Bonn
* you are all welcome to join
* We would like to have a discussion on OSGeo topics for about 2 hours. And OSGeo will provide food and drinks.

== Social Events ==

BaseCamp ist great. But you should also see the outside of BaseCamp and we want to bring you in contact with Bonn and the FOSSGIS e.V. Community (german language Local Chapter of OSGeo)

=== Wednesday 21th March: FOSSGIS Conference Social Event ===
* Wednesday 21th March 19:00-01:00
* we want to invite you to the event
* with buffet, loo-session and dj team
* Dad's Phonkey in action with his Loop-Station https://de-de.facebook.com/dadsphonkey
* Rafa from DJ Kollektiv Lucha Amada http://luchaamada.blogsport.de/
* see also https://fossgis-konferenz.de/2018/socialevents/
* ''we need the information, whether you need a ticket for the social event - please add to you information in the wiki table above!!!'''

; all evenings ''Pub race'' - find out about pubs in Bonn
* meet at Namenlos or Pawlows

== OSGeo Exhibition Pack ==
* take your OSGeo Exhibition Pack home - get information and make an order [[Talk:Exhibition_Pack#Ordering]]

== Project Plans ==
(i.e what do you wish/want/plan to work on during the sprint ?)

* '''GRASS GIS project''': See [https://grasswiki.osgeo.org/wiki/GRASS_Community_Sprint_Bonn_2018 dedicated Wiki page]
* '''OSGeoLive'''
** build documentation - mo 12:00-17:00
** start Release cycle: more info: [https://docs.google.com/spreadsheets/d/1kO6zzmLFfprZGgp5x7Sjwi-EVN6NTGDR4KXvFVtNpR0/edit?hl=en_GB&hl=en_GB#gid=0 OSGeoLive 12 Schedule]
** start of the build cycle for the next OSGeoLive release, 12.0 19 - 23 March
** OSGeoLive12 - how to configure for specific purpose like an INSPIRE flavor 22 - 23 March
* '''OSGeo Europe''' - preparing the website pages, further organizing, coordinate common activities
* '''pycsw''': see [https://github.com/geopython/pycsw/wiki/2018-Bonn-sprint dedicated Wiki page]
* '''MapServer''': see [https://github.com/mapserver/mapserver/wiki/Bonn-2018-Codesprint dedicated Wiki page]
* '''ZOO-Project''': see [http://zoo-project.org/trac/wiki/OSGeoCodeSprint2018 dedicated Wiki page]
* '''Geopaparazzi/gvSIG Mobile''':
** bugfixing
** testing of rspatialite 4.5
** API for synchronization with cloud for server+serverless modes

== Participants ==

Please add your name and the projects you are planning to sprint and note the likeliness of your attendance.

{| border="1" cellpadding="2" class="wikitable sortable"
!width="25"|No
!width="250"|Name
!width="100"|Country
!width="250"|Email
!width="250"|Organisation
!width="250"|Projects
!width="25"|sun
!width="25"|mon
!width="25"|tue
!width="25"|wed
!width="25"|thu
!width="25"|fri
!width="25"|sat
!width="25"|sun
!width="60"|Accommodation
!width="30"|vegetarian food
!width="60"|social event
|-
| 1 ||[[Jeff McKenna]] <libravatar email="jmckenna@gatewaygeomatics.com"/> || CA || jmckenna(at)osgeo.org || OSGeo || MapServer, MS4W, ZOO-Project || x || x || x || x || x || x || || || AirBNB || || x
|-
| 2 ||[[Howard Butler]] || US || howard@hobu.co || Hobu, Inc. || Proj.4, PDAL, GDAL, Point clouds || || x || x || x || x || x || || || || No thank you. ||
|-
| 3 ||[[Even Rouault]] || FR || even.rouault(at)spatialys.com || Spatialys || Proj.4, GDAL, MapServer || || x || x || x || x || x || || || BaseCamp || ||
|-
| 4 ||[[Markus Neteler]] || DE || neteler(at)osgeo.org || mundialis || GRASS GIS (Proj.4, GDAL, OTB, QGIS) || x || x || x || x || x || x || x || x || || preferably ||
|-
| 5 ||[[User:Djay|Gérald Fenoy]] || FR || gerald.fenoy(at)geolabs.fr || GeoLabs || MS4W, ZOO-Project || x || x || x || x || x || x || x || x || shared accommodation || ||
|-
| 6 ||[[User:Schpidi|Stephan Meißl]] || AT || stephan(at)meissl.name || EOX || MapServer, EOxServer || || x || x || x || x || x || || || BaseCamp || || x ||
|-
| 7 ||[[User:martinl|Martin Landa]] || CZ || landa.martin(at)gmail.com || CTU in Prague || GRASS GIS (Proj.4, GDAL, PostGIS, QGIS) || x || x || x || x || x || x || x || x || BaseCamp || ||
|-
| 8 ||[[User:connormanning|Connor Manning]] || US || connor@hobu.co || Hobu, Inc. || Entwine, Greyhound, PDAL, Point clouds || x || x || x || x || x || x || x || x || || ||
|-
| 9 ||Markus Schütz || AT || mschuetz@potree.org|| TU Wien|| Potree, point clouds|| || x || x || x || x || x || || || || ||
|-
| 10 ||[[User:Tomkralidis|Tom Kralidis]] || CA || tomkralidis(at)gmail.com || self || pycsw, OWSLib, pygeometa, MapServer, geocatalogo || x || x || x || x || x || || || || tbd || sure || x ||
|-
| 11 ||[[User:kalxas|Angelos Tzotsos]] || GR || tzotsos(at)osgeo.org || OSGeo || pycsw, OSGeoLive, GeoNode, UbuntuGIS, OTB, ZOO-Project || x || x || x || x || x || x || x || x || booked || No || x ||
|-
| 12 ||[[User:jjesus|Jorge Samuel Mendes de Jesus]] || NL || jorge.dejesus(at)geocat.net || Geocat || pywps || || || || x || x || x || x || || AirBNB || NO! ||
|-
| 13 ||[[User:ingenieroariel|Ariel Núñez]] || CO || ariel(at)terranodo.io || Terranodo || GeoNode || x || x || x || x || x || x || x || x || tbd || ||
|-
| 14 ||[[User:Lads|Luís de Sousa]] || PT & NL || luis.de.sousa(at)protonmail.ch || [http://www.isric.org ISRIC] || PyWPS, GRASS || || || || x || x || x || x || x || BaseCamp || ||
|-
| 15 ||[[User:Vmische|Volker Mische]] || DE || volker.mische(at)gmail,com || Myself || Noise, CouchDB || x || x || x || x || x || x || x || x || BaseCamp || 50% ||
|-
| 16 ||[[User:Just|Just van den Broecke]] || NL || justb4(at)gmail,com || Myself || GeoHealthCheck, Stetl || x || x || x || x || x || x || x || x || tbd || - ||
|-
| 17 ||[[User:Jgrocha|Jorge Gustavo Rocha]] || PT || jgr@geomaster.pt || Geomaster || QGIS, GeoExt 3, Nominatim || || x || x || x || x || x || 2 x || 2 x || BaseCamp || || x
|-
| 18 ||[[User:tfr42|Torsten Friebe]] || DE || friebe AT lat-lon DOT de || lat/lon || deegree || x || x || x || x || x || x || x || x || not needed || yes, please ||
|-
| 19 ||[[User:Stenger|Dirk Stenger]] || DE || stenger AT lat-lon DOT de || lat/lon || deegree, TEAM Engine || || x || x || || || || || || not needed || ||
|-
| 20 ||[[User:Lgoltz|Lyn Goltz]] || DE || goltz AT lat-lon DOT de || lat/lon || deegree, TEAM Engine || || x || x || x || x || x || || || not needed || yes ||
|-
| 21 ||[[User:remanuele|Rob Emanuele]] || US || remanuele@azavea.com ||Azavea || PDAL, GDAL, Point clouds, GeoTrellis, LocationTech || || x || x || x || x || x || || || || ||
|-
| 22 || Grigory Pomadchin || RU || gr.pomadchin AT gmail DOT com || Azavea || PDAL, GDAL, Point clouds, GeoTrellis || || x || x || x || x || x || || || || ||
|-
| 23 ||[[User:tomvantilburg|Tom van Tilburg]] || NL || tom.van.tilburg@geodan.nl || geodan || Pointcloud || || x || x || x || x || x || x || || tbd || x|- ||
|-
| 24 ||[[User:chambbj|Brad Chambers]] || US || bradley.chambers@digitalglobe.com || Radiant Solutions || PDAL, Point Clouds || || x || x || x || x || x || || || TBD || No thanks! ||
|-
| 25 || Eugene Cheipesh || USA || echeipesh AT azavea DOT com || Azavea || LocationTech, JTS, JAI Replacement || || x || x || x || x || x || || || || x ||
|-
| 26 || [[User:Lucadelu|Luca Delucchi]] || IT || lucadeluge AT gmail DOT com || Fondazione Edmund Mach || GRASS GIS, OSGeoLive, pyModis || x || x || x || x || x || x || ? || ? || Basecamp || | || x
|-
| 27 || [[User:Veroandreo|Veronica Andreo]] || AR/NL || veroandreo AT gmail.com || on-my-own-time || GRASS GIS || x || x || x || x || x || x || x || ? || Basecamp || | || x
|-
| 28 || [[User:dirkf|Dirk Frigne]] || BE || Dirk AT Geosparc.com || OSGeo Europe || GeoMajas OSGeo Live || x || x || x || - || x || x || || || motor home || | ||
|-
| 29 ||[[User:msmitherdc|Michael Smith]] || US || michael.smith.erdc at gmail.com || US Army Corps || MapServer, PDAL || x || x || x || x || x || x || x || x || hotel || | ||
|-
| 30 ||[[User:cvvergara| Vicky Vergara]] || MX || vicky at georepublic DOT de || Georepublic || pgRouting, OSgeoLive, PDAL, Point clouds || x || x || x || x || x || x || x || x || Basecamp || | ||
|-
| 31 ||Marco Hugentobler || CH || marco at sourcepole dot com || Sourcepole || QGIS || || x || x || x || x || x || || || BaseCamp || ||
|-
| 32 ||[[User:Pirmin_Kalberer|Pirmin Kalberer]] || CH || pka at sourcepole dot com || Sourcepole || QGIS, GDAL, t-rex || || x || x || x || x || x || || || BaseCamp || ||
|-
| 33 ||[[User:Mlennert|Moritz Lennert]] || BE || mlennert at club dot worldonline dot be || ULB || GRASS GIS || x || x || x || x || || || || || BaseCamp || preferably ||
|-
| 34 ||[[Andrew Bell]] || US || andrew@hobu.co || Hobu, Inc. || Proj.4, PDAL, Point clouds, meshes || || x || x || x || x || x || || || || ||
|-
| 35 ||[[User:theduckylittle|Dan "Ducky" Little]] || US || dlittle@boundlessgeo.com || Boundless || React + OpenLayers, MapServer || || || x || x || x || x || x || FeWo || || || x
|-
| 36 ||[[User:nicklas|Nicklas Avén]] || SE/NO || nicklas.aven@jordogskog.no || Just me || TilelessMap, PostGIS || x || x || x || x || x || x || x || || BaseCamp || || x
|-
| 37 ||[[User:Clucas|Chris Lucas]] || NL || chris.lucas@geodan.nl || Geodan || PDAL, point clouds || || x || x || x || x || x || || || tbd || | ||
|-
| 38 ||[[User:Marcjansen|Marc Jansen]] || DE || jansen@terrestris.de || terrestris || OpenLayers, react-geo, GeoExt || (x) || x || x || (x) || (x) || (x) || || || not needed || | ||
|-
| 39 ||[[User:Mlechner|Marco Lechner]] || DE || marco.lechner@fossgis.de || [https://www.fossgis.de FOSSGIS e.V.]/[https://github.com/OpenBfS BfS] || OpenLayers, Geonetwork, Geoserver, everything || (x) || x || x || (x) || (x) || (x) || || || BaseCamp || veg. ||
|-
| 40 ||[[Martinheidegger|Martin Heidegger]] || JP/AT || martin.heidegger@gmail.com || Freelancer (Georepublic) || Point clouds, dotloom, pix4d/potree || (x) || x || x || x || (x) || || || || BaseCamp || || x ||
|-
| 41 ||[[User:moovida|Andrea Antonello]] || IT || andrea.antonello@gmail.com || HydroloGIS / Free University of Bolzano || Geopaparazzi, gvSIG, gvSIG Mobile, everything || (x) || x || x || x || x || x || || || TBD || no ||
|-
| 42 ||[[User:Astrid_Emde|Astrid Emde]] || DE || astrid_emde@osgeo.org || WhereGroup/OSGeo || Mapbender, OSGeoLive, OSGeo || x || x || x || || || || x || x || BaseCamp || vegetarian ||
|-
| 43 ||[[User:GeoFootballer|Christian Mayer]] || DE || chris@meggsimum.de || meggsimum || OpenLayers, GeoExt || (x) || x || x || (x) || (x) || (x) || || || not needed || | ||
|-
| 44 || Andreas Schmitz || DE || schmitz@terrestris.de || terrestris || OpenLayers, react-geo, GeoExt || (x) || x || x || (x) || (x) || (x) || || || not needed || | ||
|-
| 45 ||[[User:Ckuntzsch|Christian Kuntzsch]] || DE || Christian.Kuntzsch@wheregroup.com || WhereGroup || Mapbender || x || x || x || x || || || || || BaseCamp || ||
|-
| 46 || Nina Moelkner || DE || nina.moelkner@wheregroup.com || WhereGroup || Mapbender || || x || x || || || || || || not needed || ||
|-
| 47 || Robin Schwammborn || DE || robin.schwammborn@wheregroup.com || WhereGroup || Mapbender || || x || x || || || || || || not needed || ||
|-
| 48 ||[[User:dispiste|Cesar Martinez]] || ES || cesar.izq@gmail.com || gvSIG/Scolab || gvSIG, gvSIG Mobile, Geopaparazzi || x || x || x || x || x || || || || BaseCamp if possible || not needed ||
|-
| 49 || Thekla Wirkus || DE || thekla.wirkus@wheregroup.com || WhereGroup || Mapbender || || x || || || || || || || not needed || ||
|-
| 50 || [[User:axxl|Axel Schaefer]] || DE || axel.schaefer@wheregroup.com || WhereGroup || Mapbender || || x || (x) || || || || || || not needed || ||
|-
| 51 || [[User:mmetz|Markus Metz]] || DE || metz@mundialis.de || mundialis || GRASS GIS (Proj.4, GDAL, OTB, QGIS) || x || x || x || x || || || || || Base Camp || not needed || x
|-
| 52 || [[User:Taehoon.Kim|Taehoon Kim]] || JP/KR || kim.taehoon@aist.go.jp || AIST || Point clouds || (x) || x || x || x || x || x || x || || || ||
|-
| 53 || Marco Pochert || DE || mpochert@bfs.de || [https://github.com/OpenBfS BfS] || OpenLayers, Geonetwork, GeoExt, everything || (x) || x || x || (x) || (x) || (x) || || || BaseCamp || ||
|-
| 54 ||[[User:bartvde2|Bart van den Eijnden]] || Netherlands || bartvde@boundlessgeo.com || Boundless || React + OpenLayers || x || x || x || x || x || || || || || || x
|-
| 55 ||[[User:FxKu|Felix Kunde]] || DE || felix-kunde@gmx.de || Beuth University || 3DCityDB || || x || x || || || || || || HBF || ||
|-
| 56 ||[[User:SBL|Stefan Blumentrath]] || NO || stefan.blumentrath@nina.no || Norwegian Institute for Nature Research (NINA) || GRASS GIS || || || x || x || x || x || x || x || ? || ||
|-
| 57 ||[[User:elpaso|Alessandro Pasotti]] || IT || elpaso@itopen.it || ItOpen || QGIS || x || x || x || x || x || x || || || Base Camp || ||
|-
| 58 ||[[Milena Nowotarska]] || PL || milena.osgeo(at)gmail.com || OSGeo / GISTRA|| GRASS GIS, QGIS, OSGeoLive || x || x || x || x || x || x || || || || gluten free ||
|-
| 59 ||[[Vasile Craciunescu]] || RO || vasile(at)geo-spatial.org || OSGeo / geo-spatial.org|| FOSS4G2019 || x || x || x || || || || || || BaseCamp || ||
|-
| 60 ||[[User:Olr|Oliver Rudzick]] || DE || osm(at)rudzick.de || FOSSGIS || OSM || x || || x || (x) || (x) || (x) || x || x || not needed || ||
|-
| 61 ||[[User:Uli|Uli Rothstein]] || DE || uli.rothstein(at)fossgis.de || terrestris / FOSSGIS || Orga || x || || x || (x) || (x) || (x) || x || x || not needed || ||
|-
| 62 ||Nils Bühner || DE || buehner(at)terrestris.de || terrestris || SHOGun, react-geo || || x || x || || || || || || not needed || ||
|-
| 63 ||Daniel Koch || DE || koch(at)terrestris.de || terrestris || SHOGun, react-geo || || x || x || (x) || (x) || (x) || || || not needed || ||
|-
| 64 ||Kai Volland || DE || volland(at)terrestris.de || terrestris || react-geo || || x || x || || || || || || not needed || ||
|-
| 65 ||Johannes Weskamm || DE || weskamm(at)terrestris.de || terrestris || OSM-Vector-Tiles / react-geo || x || x || x || || || || || || not needed || ||
|-
| 66 ||Carmen Tawalika || DE || tawalika(at)mundialis.de || mundialis || actinia || x || x || x || x || || || x || x || not needed || ||
|-
| 67 ||Frank Gasdorf|| DE || fgdrf(at)users.sourceforge.net || || uDig, Geotools, LocationTech, JTS, JAI Replacement|| || || || x || x || x || || || TBD || ||
|-
| 68 ||[[User:Rzoller|Roman Zoller]] || CH || roman.zoller ät camptocamp.com || Camptocamp || OpenLayers / react-geo / TBD? || || || || (x) || (x) || (x) || x || x || Hotel || ||
|-
| 69 ||[[User:Jive|Jody garnett]] || CA || jody.garnett@gmail.com || OSGeo || GeoTools || x || x || x || x || x || x || x || || base camp|| whiskey ||
|-
| 70 || Seth Girvin || IE || sgirvin@compass.ie || Compass Informatics || MapServer, GeoExt || || x || x || x || x || x || || || Basecamp || ||
|-
| 71 ||[[User:Delawen|María Arias de Reyna]] || ES || maria.arias@geocat.net || GeoCat bv,OSGeo || GeoNetwork || x || x || x || || || || || || - || no ||
|-
| 72 ||Mario Härtwig || DE || mario.haertwig(at)geops.de || geOps || OpenLayers Editor || x || x || x || || || || || || BaseCamp || ||
|-
| 73 ||[[User:Friedjoff|Friedjoff Trautwein]] || DE || friedjoff.trautwein(at)geops.de || geOps || OpenLayers Editor || x || x || x || || || || || || BaseCamp || ||
|-
| 74 ||[[User:Bluemates|Kyoung-Sook Kim]] || JP || ks.kim(at)aist.go.jp || AIST || Point clouds || || || || (x) || x || x || x || || || ||
|-
| 75 ||[[User:CEhbrecht|Carsten Ehbrecht]] || DE || ehbrecht(at)dkrz.de || DKRZ || pywps, owslib || || || x || x || x || (x) || || || Hotel || no ||
|-
| 76 ||[[User:johanvdw|Johan Van de Wauw]] || BE || johan AT gisky.be || gisky || saga, osgeo live, owslib, debian/ubuntu || || || || x || x || x || x || || Basecamp || none ||
|-
| 77 ||[[User:plimkilde|Peter Limkilde Svendsen]] || DK || pelis åt sdfe dot dk|| [http://sdfe.dk SDFE] || Point clouds || (x) || x || x || x || x || (x) || || || - || ||
|-
| 78 ||[[User:Akotsev|Alexander Kotsev]] || IT || alexander.kotsev åt ec dot europa dot eu|| [https://ec.europa.eu/jrc/en EC/JRC] || || || || || || x || x || || || || ||
|-
| 79 ||[[User:pesekon2|Ondřej Pešek]] || CZ || pesej.ondrek(at)gmail.com || CTU in Prague || GRASS GIS || x || x || x || x || x || x || x || x || BaseCamp || ||
|-
| 80 ||[[User:ctoma|Charlotte Toma]] || DE || charlotte.toma(at)wheregroup.com || WhereGroup || Mapbender || || x || x || || || || || || no || no ||
|-
| 81 ||Paul S || DE || paul.schell(at)wheregroup.com || WhereGroup || Mapbender || || x || x || || || || || || no || no ||
|-
| 82 ||Julius Krey || DE || julius.krey(at)wheregroup.com || WhereGroup || Mapbender || || x || x || || || || || || no || no ||
|-
| 83 ||Daniel Santillan || AT || daniel.santillan@eox.at || EOX || plotty, 3D JavaScript in general || || x || x || x || || || || || BaseCamp || ||
|-
| 84 ||Anton Wagensonner || AT || awagensonner(at)riegl.com || RIEGL || point clouds, PDAL || || x || x || || || || || || hotel || no ||
|-
| 85 || Norbert Wenzel || AT || nwenzel(at)riegl.com || RIEGL || point clouds, PDAL || || x || x || || || || || || hotel || no ||
|-
| 86 || Kris Depril || BE || Kris.depril@geosparc.com || Geosparc || OSGeoLive || x || x || x || || || || || || not needed || ||
|-

| # ||[[User:your osgeo profile|Your name]] || DE || email || organization || project || x || x || x || x || x || x || x || x || ?Accommodation || ?vegetarian || do you need a ticket for the social event? yes=x
|}

== Communication ==

* Please join the mailing list: https://lists.osgeo.org/mailman/listinfo/tosprint
* IRC chat during the event: #tosprint Server: irc.freenode.net
* Twitter: #TOSprint ( https://twitter.com/search?q=tosprint )

== Costs ==

Participants should plan for the following costs:

* Travel to Bonn
* Accommodation for x nights

All other costs - food, outings and entertainment - should/will be covered by the sponsors

== Individual preparation ==

* Bring your own laptop
* Bring [https://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:Schuko_plug_and_socket.png Germany]). See also http://www.power-plugs-sockets.com/
* Install GIT and compiler tools, and come with a working development environment

== Sponsoring ==

The Open Source Geospatial Foundation (OSGeo) has a long tradition of organizing code sprints for developers of Open Source GIS software.
(https://wiki.osgeo.org/wiki/Category:Code_Sprints).

Simultaneously with the [https://www.fossgis-konferenz.de/2018/ FOSSGIS Conference 2018 in Bonn] an international code sprint of the OSGeo will take place from 19 to 25 March 2018.
We expect about 80 developers from all over the world to come from various [https://www.osgeo.org/] projects. Whether desktop application, geospatial library, metadata catalog or web mapping: be sure to find products in the list that you use. Thus, the Code Sprint is also an opportunity for your developers to meet with the core developers of the projects, get a deeper insight into the software and participate in the development.

The code sprint will take place at [http://www.basecamp-bonn.de/ BaseCamp] in Bonn. During the [http://www.foss4g2016.org/home.html FOSS4G 2016] in Bonn we have already organized a code sprint at this location, in which about 100 developers worked on the open source projects every day. (https://wiki.osgeo.org/wiki/FOSS4G_2016_Code_Sprint)

In addition to the costs of providing the technical infrastructure, the cost of food and drinks for the developers is the main cost. A buffet at lunchtime and drinks during the whole day are intended.

So far, the code sprint is already sponsored by [https://www.osgeo.org/ OSGeo] and [https://www.fossgis.de/ FOSSGIS e. V.].

In order to cover the costs, we would be very pleased about further sponsors!

What we offer:
* Your logo on top of the [https://www.osgeo.org/events/osgeo-code-sprint-2018/ websites of the Code Sprint] [https://wiki.osgeo.org/wiki/OSGeo_Code_Sprint_2018 1] as well as on all official documents around the Code Sprint
* Mention in all code sprint related mails
* Our undying gratitude, which comes in handy when you least expect it (Remember that feature you wanted...)

Our sponsorship levels:
* Gold: >= 2500 USD
* Silver: 1500 USD
* Bronze: 750 USD

So...
* get your company talking to the top developers of the scene!
* enable your GIS developers to take advantage of this opportunity, there is no better opportunity to learn!
* support the software you use - you benefit immediately.

Thank you very much!

Contact: To sponsor, please contact codesprint@osgeo.org directly.

== Event Owner ==
* [[User:Astrid_Emde|Astrid Emde]]
* Uli Rothstein
* Carmen Tawalika
* [[User:Olr|Oliver Rudzick]]
* Mirko Blinn

; Supported by
* [[User:Lucadelu|Luca Delucchi]]

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]

OSGeo Code Sprint 2018

2018-01-24T09:43:37Z

Moovida: /* Participants */

Annual Code Sprint comes to Bonn (Germany) in 2018!

Powered by [[Image:Osgeo-logo.png|250px|link=http://www.osgeo.org]]

'''Sponsoring ''' Find out about [[OSGeo_Code_Sprint_2018#Sponsoring |Sponsoring the Event]].

;Gold Sponsors

[[File:Logo-FOSSGIS-e.V.png‎|260px|FOSSGIS e.V.|link=http://www.fossgis.de]]

; Silver Sponsors

; Bronze Sponsors

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-Azavea.png|280px|Azavea|link=http://www.azavea.com/]]
 
http://www.azavea.com/
|
[[File:WhereGroup_logo_418x110.png|290px|WhereGroup|link=https://www.wheregroup.com/]]
 
https://www.wheregroup.com/
|
[[File:Logo-EOX.png|120px|EOX IT Services GmbH|link=http://eox.at]]
 
[http://eox.at http://eox.at]
|}

In 2018 we once again want to invite you to Bonn to meet for codesprint at Basecamp! ....

[[Image:FOSS4G_2016_OSGeo_Code_Sprint_indoor_hacking_overview.jpg|400px|thumb|right]]
[[Image:FOSS4G_OSGeo_Code_Sprint_in_Action1.jpg|400px|thumb|right]]

[[Image:Basecamp5.png|300px|thumb]]
[[Image:Basecamp6.png|300px|thumb]]
[[Image:Basecamp7.png|300px|thumb]]
[[Image:Basecamp1.png|300px|thumb]]

[[Image:FOSS4G_2016_OSGeo_Code_Sprint_sponsors.jpg|400px]]

== Purpose ==

Bring together project members to make decisions and tackle larger geospatial
problems as in previous years:
* [[Daytona Beach Code Sprint 2017|Daytona_Beach]] (2017)
* [[Paris Code Sprint 2016|Paris]] (2016)
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)
* [[Vienna Code Sprint 2014|Vienna]] (2014)
* [[Boston Code Sprint 2013|Boston]] (2013)
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)
* [[Montreal Code Sprint 2011|Montreal]] (2011)
* [[New York Code Sprint 2010|New York City]] (2010)
* [[Toronto Code Sprint 2009|Toronto]] (2009)

== Dates and Times ==

Dates:
* Sprint: Sunday-Sunday, March 18 to 25, 2018 (8 days - Arrival/Departure Sundays)

== Other Events from January to March 2018 ==

* '''OSGeo's 12th birthday Feb 4'''
* FOSDEM 3-4 Feb https://fosdem.org/2018/
* FOSS4G IT 19-22 Feb http://foss4g-it2018.gfoss.it/
* [https://github.com/qgis/QGIS/wiki/DeveloperMeetingMadeira2018 QGis Hackfest] 21-25 Feb, 2018
* FOSSGIS 21-24 March https://www.fossgis-konferenz.de/2018/
* ''please add your event''

== Location ==

=== Coding Venue ===
* Venue & Accommodation BaseCamp.
* For more informations: http://www.basecamp-bonn.com/
* [http://www.openstreetmap.org/way/44335958#map=18/50.70763/7.12316| OpenStreetMap]

=== Accommodations ===
* Please use this official hotel booking system: http://www.bonn-region.de/events/fossgis-konferenz-english.html
* Using this system you can book the caravans in base camp. All bookers that use this system will receive a free public transport ticket that is valid during your stay.

=== How to get there ===
* http://alienus.de/basecamp1/en/arrival-bonn-hostel/
* http://www.openstreetmap.org/search?query=raste%201%20bonn#map=18/50.70762/7.12383

By train
* From Bonn Main station take the U-Trains (Underground platform) 16, 63 or 68. Get off after 6 min at stop Dt. Telekom / Ollenhauerstr.
* http://alienus.de/basecamp1/en/arrival-bonn-hostel/
* http://www.openstreetmap.org/search?query=raste%201%20bonn#map=18/50.70762/7.12383
* [https://www.vrsinfo.de/englisch/the-vrs/vrs-about-us.html online public transport planner]

By Car
* Coming from the highway A59 Basecamp is located at the end of the highway A562. For navigation systems it is best to type Basecamp's address: "''In der Raste 3, 53129 Bonn''")

== Schedule ==
* tbd

== Project Plans ==
(i.e what do you wish/want/plan to work on during the sprint ?)

* '''GRASS GIS project''': See [https://grasswiki.osgeo.org/wiki/GRASS_Community_Sprint_Bonn_2018 dedicated Wiki page]
* tbd

== Social ideas ==

== Participants ==

We are planning for attendance of ~50. Please add your name and the projects
you are planning to sprint and note the likeliness of your attendance.

{| border="1" cellpadding="2" class="wikitable sortable"
!width="25"|No
!width="250"|Name
!width="100"|Country
!width="250"|Email
!width="250"|Organisation
!width="250"|Projects
!width="25"|sun
!width="25"|mon
!width="25"|tue
!width="25"|wed
!width="25"|thu
!width="25"|fri
!width="25"|sat
!width="25"|sun
!width="60"|Accommodation
!width="30"|vegetarian food
|-
| 1 ||[[Jeff McKenna]] <libravatar email="jmckenna@gatewaygeomatics.com"/> || CA || jmckenna(at)osgeo.org || OSGeo || MapServer, MS4W, ZOO-Project || x || x || x || x || x || x || x || x || shared accommodation ||
|-
| 2 ||[[Howard Butler]] || US || howard@hobu.co || Hobu, Inc. || Proj.4, PDAL, GDAL, Point clouds || || x || x || x || x || x || || || || No thank you.
|-
| 3 ||[[Even Rouault]] || FR || even.rouault(at)spatialys.com || Spatialys || Proj.4, GDAL, MapServer || || x || x || x || x || x || || || BaseCamp if possible ||
|-
| 4 ||[[Markus Neteler]] || DE || neteler(at)osgeo.org || mundialis || GRASS GIS (Proj.4, GDAL, OTB, QGIS) || x || x || x || x || x || x || x || x || || preferably
|-
| 5 ||[[User:Djay|Gérald Fenoy]] || FR || gerald.fenoy(at)geolabs.fr || GeoLabs || MS4W, ZOO-Project || x || x || x || x || x || x || x || x || shared accommodation ||
|-
| 6 ||[[User:Schpidi|Stephan Meißl]] || AT || stephan(at)meissl.name || EOX || MapServer, EOxServer || x || x || x || x || x || x || x || x || BaseCamp ||
|-
| 7 ||[[User:martinl|Martin Landa]] || CZ || landa.martin(at)gmail.com || CTU in Prague || GRASS GIS (Proj.4, GDAL, PostGIS, QGIS) || x || x || x || x || x || x || x || x || BaseCamp ||
|-
| 8 ||[[User:connormanning|Connor Manning]] || US || connor@hobu.co || Hobu, Inc. || Entwine, Greyhound, PDAL, Point clouds || x || x || x || x || x || x || x || x || ||
|-
| 9 ||Markus Schütz || AT || mschuetz@potree.org|| TU Wien|| Potree, point clouds|| x || x || x || || || || || || ||
|-
| 10 ||[[User:Tomkralidis|Tom Kralidis]] || CA || tomkralidis(at)gmail.com || self || pycsw, OWSLib, pygeometa, MapServer, geocatalogo || x || x || x || x || x || || || || tbd || sure
|-
| 11 ||[[User:kalxas|Angelos Tzotsos]] || GR || tzotsos(at)osgeo.org || OSGeo || pycsw, OSGeoLive, GeoNode, UbuntuGIS, geocatalogo, OTB, ZOO-Project || x || x || x || x || x || x || x || x || tbd || probably
|-
| 12 ||[[User:jjesus|Jorge Samuel Mendes de Jesus]] || NL || jorge.dejesus(at)geocat.net || Geocat || pywps || || x || x || x || x || x || x || || tbd || NO!
|-
| 13 ||[[User:ingenieroariel|Ariel Núñez]] || CO || ariel(at)terranodo.io || Terranodo || GeoNode || x || x || x || x || x || x || x || x || tbd ||
|-
| 14 ||[[User:Lads|Luís de Sousa]] || PT & NL || luis.de.sousa(at)protonmail.ch || [http://www.isric.org ISRIC] || PyWPS, GRASS || || || || x || x || x || x || x || BaseCamp ||
|-
| 15 ||[[User:Vmische|Volker Mische]] || DE || volker.mische(at)gmail,com || Myself || Noise, CouchDB || x || x || x || x || x || x || x || x || BaseCamp || 50%
|-
| 16 ||[[User:Just|Just van den Broecke]] || NL || justb4(at)gmail,com || Myself || GeoHealthCheck, Stetl || x || x || x || x || x || x || x || x || tbd || -
|-
| 17 ||[[User:Jgrocha|Jorge Gustavo Rocha]] || PT || jgr@geomaster.pt || Geomaster || QGIS, GeoExt 3 || || x || x || x || x || x || 2 x || 2 x || BaseCamp (+ extra bed for the last 2 days for my daughter Rita, if possible) ||
|-
| 18 ||[[User:tfr42|Torsten Friebe]] || DE || friebe AT lat-lon DOT de || organization || deegree || x || x || x || x || x || x || x || x || not needed || yes, please
|-
| 19 ||[[User:Stenger|Dirk Stenger]] || DE || stenger AT lat-lon DOT de || organization || deegree || || x || x || x || x || x || || || not needed ||
|-
| 20 ||[[User:Lgoltz|Lyn Goltz]] || DE || goltz AT lat-lon DOT de || organization || deegree || || x || x || x || x || x || x || x || not needed || yes
|-
| 21 ||[[User:remanuele|Rob Emanuele]] || US || remanuele@azavea.com ||Azavea || PDAL, GDAL, Point clouds, GeoTrellis, LocationTech || || x || x || x || x || x || || || ||
|-
| 22 || Grigory Pomadchin || RU || gr.pomadchin AT gmail DOT com || Azavea || PDAL, GDAL, Point clouds, GeoTrellis || || x || x || x || x || x || || || ||
|-
| 23 ||[[User:tomvantilburg|Tom van Tilburg]] || NL || tom.van.tilburg@geodan.nl || geodan || Pointcloud || x || x || x || x || x || x || x || x || tbd || x|-
|-
| 24 ||[[User:chambbj|Brad Chambers]] || US || bradley.chambers@digitalglobe.com || Radiant Solutions || PDAL, Point Clouds || || x || x || x || x || x || || || TBD || No thanks!
|-
| 25 || Eugene Cheipesh || USA || echeipesh AT azavea DOT com || Azavea || LocationTech, JTS, JAI Replacement || || x || x || x || x || x || || || ||
|-
| 26 || [[User:Lucadelu|Luca Delucchi]] || IT || lucadeluge AT gmail DOT com || Fondazione Edmund Mach || GRASS GIS, OSGeoLive, pyModis || x || x || x || x || x || x || ? || ? || Basecamp || |
|-
| 27 || [[User:Veroandreo|Veronica Andreo]] || AR/NL || veroandreo AT gmail.com || ITC || GRASS GIS || x || x || x || x || x || x || x || ? || Basecamp || |
|-
| 28 || [[User:dirkf|Dirk Frigne]] || BE || Dirk AT Geosparc.com || OSGeo Europe || GeoMajas OSGeo Live || x || x || x || x || x || x || x || ? || motor home || |
|-
| 29 ||[[User:msmitherdc|Michael Smith]] || US || michael.smith.erdc at gmail.com || US Army Corps || MapServer, PDAL || x || x || x || x || x || x || x || x || hotel || |
|-
| 30 ||[[User:cvvergara| Vicky Vergara]] || MX || vicky at georepublic DOT de || Georepublic || pgRouting, OSgeoLive, PDAL, Point clouds || x || x || x || x || x || x || x || x || Basecamp || |
|-
| 31 ||Marco Hugentobler || CH || marco at sourcepole dot com || Sourcepole || QGIS || || x || x || x || x || x || || || BaseCamp ||
|-
| 32 ||[[User:Pirmin_Kalberer|Pirmin Kalberer]] || CH || pka at sourcepole dot com || Sourcepole || QGIS, GDAL, t-rex || || x || x || x || x || x || || || BaseCamp ||
|-
| 33 ||[[User:Mlennert|Moritz Lennert (tbc)]] || BE || mlennert at club dot worldonline dot be || ULB || GRASS GIS || x || x || x || x || || || || || BaseCamp ||
|-
| 34 ||[[Andrew Bell]] || US || andrew@hobu.co || Hobu, Inc. || Proj.4, PDAL, Point clouds, meshes || || x || x || x || x || x || || || ||
|-
| 35 ||[[User:theduckylittle|Dan "Ducky" Little]] || US || dlittle@boundlessgeo.com || Boundless || React + OpenLayers, MapServer || || || x || x || x || x || x || || ||
|-
| 36 ||[[User:nicklas|Nicklas Avén]] || SE/NO || nicklas.aven@jordogskog.no || Just me || TilelessMap, PostGIS || x || x || x || x || x || x || x || || BaseCamp ||
|-
| 37 ||[[User:Clucas|Chris Lucas]] || NL || chris.lucas@geodan.nl || Geodan || PDAL || x || x || x || x || x || x || x || x || tbd || |
|-
| 38 ||[[User:Marcjansen|Marc Jansen]] || DE || jansen@terrestris.de || terrestris || OpenLayers, react-geo, GeoExt || (x) || x || x || (x) || (x) || (x) || || || not needed || |
|-
| 39 ||[[User:Mlechner|Marco Lechner]] || DE || marco.lechner@fossgis.de || FOSSGIS e.V. / BfS || OpenLayers, Geonetwork, Geoserver, everything || (x) || x || x || (x) || (x) || (x) || || || BaseCamp || veg.
|-
| 40 ||[[Martinheidegger|Martin Heidegger]] || JP/AT || martin.heidegger@gmail.com || Freelancer (Georepublic) || Point clouds || (x) || x || x || x || (x) || || || || BaseCamp || |
|-
| 41 ||[[User:moovida|Andrea Antonello]] || IT || andrea.antonello@gmail.com || HydroloGIS / Free University of Bolzano || Geopaparazzi, gvSIG, gvSIG Mobile, everything || (x) || x || x || x || x || x || || || TBD || no
|-
| # ||[[User:your osgeo profile|Your name]] || DE || email || organization || project || || x || x || x || x || x || x || x || || |-
|}

== Communication ==

* Please join the mailing list: http://lists.osgeo.org/mailman/listinfo/tosprint
* IRC chat during the event: #tosprint Server: irc.freenode.net
* Twitter: #TOSprint ( https://twitter.com/search?q=tosprint )

== Photos ==

== Costs ==

Participants should plan for the following costs:

* Travel to Bonn
* Accommodation for x nights

All other costs - food, outings and entertainment - should/will be covered by the sponsors

== Financial ==

'''Detailed budget'''
* [[Bonn_Code_Sprint_2018_:_Budget|Budget]]

== Individual preparation ==

* Bring your own laptop
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:Schuko_plug_and_socket.png Germany]). See also http://www.power-plugs-sockets.com/
* Install GIT and compiler tools, and come with a working development environment

== Sponsoring ==

The Open Source Geospatial Foundation (OSGeo) has a long tradition of organizing code sprints for developers of Open Source GIS software.
(https://wiki.osgeo.org/wiki/Category:Code_Sprints).

Simultaneously with the [https://www.fossgis-konferenz.de/2018/ FOSSGIS Conference 2018 in Bonn] an international code sprint of the OSGeo will take place from 19 to 25 March 2018.
We expect about 80 developers from all over the world to come from various [http://www.osgeo.org/] projects. Whether desktop application, geospatial library, metadata catalog or web mapping: be sure to find products in the list that you use. Thus, the Code Sprint is also an opportunity for your developers to meet with the core developers of the projects, get a deeper insight into the software and participate in the development.

The code sprint will take place at [http://www.basecamp-bonn.de/ BaseCamp] in Bonn. During the [http://www.foss4g2016.org/home.html FOSS4G 2016] in Bonn we have already organized a code sprint at this location, in which about 100 developers worked on the open source projects every day. (https://wiki.osgeo.org/wiki/FOSS4G_2016_Code_Sprint)

In addition to the costs of providing the technical infrastructure, the cost of food and drinks for the developers is the main cost. A buffet at lunchtime and drinks during the whole day are intended.

So far, the code sprint is already sponsored by [http://www.osgeo.org/ OSGeo] and [https://www.fossgis.de/ FOSSGIS e. V.].

In order to cover the costs, we would be very pleased about further sponsors!

What we offer:
* Your logo on top of the [http://osgeo.getinteractive.nl/events/osgeo-code-sprint-2018/ websites of the Code Sprint] [https://wiki.osgeo.org/wiki/OSGeo_Code_Sprint_2018 1] as well as on all official documents around the Code Sprint
* Mention in all code sprint related mails
* Our undying gratitude, which comes in handy when you least expect it (Remember that feature you wanted...)

Our sponsorship levels:
* Gold: >= 2500 USD
* Silver: 1500 USD
* Bronze: 750 USD

So...
* get your company talking to the top developers of the scene!
* enable your GIS developers to take advantage of this opportunity, there is no better opportunity to learn!
* support the software you use - you benefit immediately.

Thank you very much!

Contact: To sponsor, please contact codesprint@osgeo.org directly.

== Event Owner ==
* [[User:Astrid_Emde|Astrid Emde]]
* Uli Rothstein
* Carmen Tawalika
* [[User:Olr|Oliver Rudzick]]
* Mirko Blinn

; Supported by
* [[User:Lucadelu|Luca Delucchi]]
[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]

Java 2017 Code Sprint

2017-03-08T08:27:54Z

Moovida: /* Participants */

The current plan is for the Java tribe to meet in Italy the week of March 27th. This page will allow us to plan the event.

Questions:

1. Who would be interested in joining as a participating? Please add your name under "participants" below, availability is limited.

2. Who would be interested in sponsoring? ;-) Thanks to Gaia3d and OSGeo for sponsoring, and GeoSolutions for the generous In-Kind contribution of sprint venue.

== Location ==

We will be hosted at the GeoSolutions offices in beautiful Tuscany for a week long sprint.
Available seats are limited to 10 to 15!

Additional travel information is outlined in the budget details provided below.

== Sponsors ==

We would like to extend our thanks to the following sponsors:

=== Gold Sponsors ===

{| cellpadding="20"
| [[File:Gaia3d.png|250px|link=http://www.gaia3d.com/]]
| [[File:Boundless_Logo.png|250px|link=http://boundlessgeo.com]]
|-
| [[File:OSGeo logo 750 317.png|250px|link=http://www.osgeo.org]]
| [[File:insurance_australia_group_logo.png|250px|link=https://www.iag.com.au]]
|}

=== Bronze Sponsors ===

{| cellpadding="20"
| [[File:How2map logo.png|250px|link=http://www.how2map.com]]
| [[File:German-speaking local-chapter-fossgis logo.png|250px|link=https://www.fossgis.de/]]
|}

=== In-Kind Sponsors ===

{| cellpadding="20"
| [[File:Geosolutions_logo.png|250px|link=http://www.geo-solutions.it]]
|}

== Participants ==

Please add your name and the projects you are planning to sprint and note the likehood of your attendance.

{| style="border: solid grey 1px; width:100%" class="sortable"
|+ Participants
|-
| # || Participant || Country || Organization || Arrival || Departure || Project Work on || Notes || Attendance
|-
| 1 || Andrea Aime || Italy || GeoSolutions || || || CITE or REST API switch || Preference for CITE, I'm game for the REST API switch too || Confirmed
|-
| 2 || Ian Turton || UK || Astun || || || CITE, Java 8 upgrade || || Confirmed
|-
| 3 || Andrea Antonello || Italy || HydroloGIS || || || gvSIG and cross-project ideas || I have a strong preference for the end of March || Canceled
|-
| 4 || Jody Garnett || Canada || Boundless || || || GeoServer and GeoTools || Enthusiastic about CITE and REST API work || Booked
|-
| 5 || Niels Charlier || Belgium || Scitus Development || || || GeoServer and GeoTools || Keen to do REST API work, MapBox seems interesting too. || Tentatively planning, possibly partially
|-
| 6 || Torben Barsballe || Canada || Boundless || || || REST API or CITE || Preference for REST API, would also be fine with CITE || Booked
|-
| 7 || Mike Pumphrey || USA || Boundless || || || Documentation || I'll help out with whatever you all decide on || Confirmed
|-
| 8 || [[User:ksmith|Kevin Smith]] || Canada || Boundless || || || GeoServer, GeoTools, and GeoWebCache || REST update, Language Update prep, library updates, deguavafication are all interesting || Booked
|-
| 9 || Nuno Oliveira || Portugal|| GeoSolutions|| || || GeoServer, GeoTools || REST update, CITE tests, Clustering, Language Update prep, library updates || Confirmed
|-
| 10 || Matt Kruszewski || St. Louis || Boundless || || || GeoServer || REST update or CITE tests || Confirmed
|-
| 11 || Quinn Scripter || Washington, DC || Boundless || || || GeoServer || REST update or CITE tests || Booked
|-
| 12 || David Vick || St Louis, MO || Boundless || || || GeoServer || REST update || Booked
|}

== Sponsorship ==

Contributions will be put towards travel costs for overseas sprinters who would be otherwise unable to attend. Any surplus at the end of the event will be turned over to OSGeo or used for a future code sprint. We have set-up the sprint to minimize travel and accommodation costs.

Sponsors will receive the following benefits / honours:

* Your logo at the top of this page
* Mention in all of our public communication, including GeoServer 2.12 release announcement
* Our gratitude :)

This event provides the following sponsorship levels:

{| class="wikitable"
|-
| Gold
| style="text-align:right;" | $1000 USD
| style="text-align:right;" | €950 EUR
|-
| Silver
| style="text-align:right;" | $500 USD
| style="text-align:right;" | €470 EUR
|-
| Bronze
| style="text-align:right;" | $250 USD
| style="text-align:right;" | €235 EUR
|-
| In-Kind || colspan="3" | In-kind contributions are graciously accepted
|}

This is an official OSGeo event, your contribution counts towards being recognized as an [http://www.osgeo.org/content/sponsorship/sponsors.html OSGeo Sponsors].

For more information on sponsorship, please contact [[Jody Garnett]], [[User:Aaime|Andrea Aime]].

=== How to Sponsor ===

Sponsorship is accepted through PayPal:

# Navigate to the [http://www.osgeo.org/ OSGeo website]
# Click on the "Donate" button in the top right corner
# Donations are handled through PayPal, when making the donation be sure to:
#* Check the currency (USD rates are provided above)
#* Use the "Add special instructions to the seller" field on the confirmation page to mention the event (example "GeoServer code sprint sponsorship")
#* To make alternative arrangements contact OSGeo [[Treasurer]]
# The OSGeo [[Treasurer]] will contact both you and the event organizers to acknowledge your sponsorship
#* Please have a logo ready for your organization if you wish to be acknowledged publicly
#* Your event sponsorship, at your request, can contribute towards [http://www.osgeo.org/sponsorship being recognized] as an OSGeo Foundation sponsor

We can also ask that OSGeo provide an invoice for payment (contact [[Jody Garnett]], [[User:Aaime|Andrea Amie]] to make arrangements).

=== Sponsorship Outreach ===

We are reaching out to organizations to see if there is interest in sponsorship:

* International organizations (OSGeo, GeoSolutions, Boundless);
* Local organizations

If there is a lot of local sponsorship we expect to drag the developers away from the task at hand and meet the local community (at a social evening or similar).

=== OSGeo Funding Request ===

The following information is requested by OSGeo Board [[Code_Sprint_Guidelines]]:

* [https://docs.google.com/spreadsheets/d/1SKwH9ExjJtzONTLw04lMq3Sqy5V9m8CGis5Fpyvgp5s/edit#gid=990228872 Java 2017 Code Sprint] (Google Docs)
* [[Java_2017_Code_Sprint_Budget_:_Budget|Java 2017 Code Sprint Budget]]

== GeoServer ==

The GeoServer team really benefited from [[GeoServer Code Sprint 2016|geoserver code sprint 2016]] and is eager to repeat the success.

=== GeoServer Planning ===

The following topics were proposed:

* [https://github.com/geoserver/geoserver/wiki/CITE-Test-Upgrade CITE Test Upfrade]
* '''[https://github.com/geoserver/geoserver/wiki/REST-API-Refresh REST API Refresh]''' - see details below
* [https://github.com/geotools/geotools/wiki/Mapbox-Style Mapbox Style]
* Library Upgrade

The sprint does not have to be a single topic, if we can swarm a large beast good, but if someone wants to join and work on a side topic to leverage the presence of others, that’s good too.

==== REST API ====

''The [https://github.com/geoserver/geoserver/wiki/REST-API-Refresh REST API Refresh] focuses on migrating the module from Restlet to the more popular Spring MVC, fixing as many issues as we can, and documenting the result.''

The REST API for GeoServer is popular, but not well maintained, collecting a large number of outstanding bugs. Many of these complain about functionality and lack of documentation. The large number of bugs (API called correctly but produced an error) may be producing more requests for documentation (developer assumed they called it incorrectly, and asks for improved documentation with an example that works).

Internally the REST API is written using an early java library called "restlet" (http://restlet.com/). There is a desire to migrate to spring rest api which is annotation driven and better supported. The risk in performing a migration to Spring MVC is introducing more bugs than are fixed. This is somewhat offset by having a larger pool of developers familiar with the codebase and the technologies used.

/**
* API endpoint to get details on a specific layer
* @param wsName The workspace name
* @param name The layer name
* @param req The HTTP request
* @return The layer, encoded as a JSON object
*/
@RequestMapping(value="/{wsName}/{name:.+}", method = RequestMethod.GET)
public @ResponseBody JSONObj get(@PathVariable String wsName, @PathVariable String name, HttpServletRequest req) {

Rough plan:

* Create a rest-ng module (alongside existing rest, restconfig, importer-rest, ....)
** Module based on Spring MVC - see simple [https://github.com/boundlessgeo/suite/blob/master/geoserver/webapp/src/main/java/com/boundlessgeo/geoserver/api/controllers/ProjController.java PrjController.java] example and complex [https://github.com/boundlessgeo/suite/blob/master/geoserver/webapp/src/main/java/com/boundlessgeo/geoserver/api/controllers/LayerController.java LayerController.java] example.
** Set up converters/encoders for resources
* Migrate restconfig functionality
* Migrate importer-rest functionality
* resource-rest-api
* rest-upload
* Audit functionality against GUI
** shortlist missing functionality for proposal and implementation (examples recalculate feature type columns, rest layer bounds from SRS boudns, ...)
* Test cases should remain unchanged
* Documentation
** Set up documentation team operating concurrently, capturing each resource as it is completed
** Go for a resource description, json and xml example, example of each kind of request (GET, PUT, POST, DELETE) as appropriate. See [https://www.mapbox.com/api-documentation/?language=cURL#styles mapbox example] and [https://github.com/boundlessgeo/suite/wiki/Layers-API boundless example].
** Consider auto generating example output from test case (see [https://projects.spring.io/spring-restdocs/ spring-restdocs])

This activity will require quite a bit of people (all hands on deck).

Reference:

* [https://osgeo-org.atlassian.net/issues/?jql=project%20%3D%20GEOS%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20REST Searching for REST]
* [https://osgeo-org.atlassian.net/issues/?jql=project%20%3D%20GEOS%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20REST Searching for Module] (not always properly assigned)

==== Library upgrades ====

Last year's sprint was devoted to updating a key library and required all hands on deck to help make the transition a smooth one. Ideally we would like to stay on top of library upgrades; however often a change to one has a cascade effect as we need to update (and test) each library in turn.

{| style="border: solid grey 1px; width:100%" class="sortable"
|+ Libraries
|-
| Library || Version || Latest || Description ||
|-
| Wicket || 7.1.0 || 7.6.0 || user interface (note 8.x milestones being released presently)
|-
| hsql || 2.3.0 || 2.3.4 || java database
|-
| h2 || 1.1.119 || 1.3.176 || java database (1.4.x beta currently available)
|-
| commons-dbcp || 1.4 || 2.2 || database connection pool
|-
| commons-beanutils || 1.9.2 || 1.9.3 || java bean utility library
|-
| commons-collections || 3.2.2 || 4.1 | java collection classes
|-
| guava || 17.0 || 21.0 || java collection classes and more
|-
| log4j || 1.2.12 || 2.7 || supports java 8 lambda, consider migrating to yaml/json config?
|-
| (and much more) || ||
|}

Note:

* We may wish to migrate from guava to java 8 and commons collections; as guava often produces conflicts for downstream projects

== GeoTools ==

=== GeoTools Plans ===

The GeoTools codebase has a number of smaller of ideas that may of be of interest to volunteers:

* JDK 9 + maybe JDK 8 updates in the code base (like stream ready support for feature collection, where we can use lambda for profit)
* JDK 9 replacement for plugin system (service registry) is required

The above ideas may also be suitable to anyone attending remotely who like the focus and support of a dedicated code sprint block on the calendar.

[[Category:Code Sprints]]
[[Category:Java Tribe Code Sprint]]

Java 2017 Code Sprint

2017-01-16T16:18:22Z

Moovida: /* Participants */

The current plan is for the Java tribe to meet in Italy at the start of March. This page will allow us to plan the event.

We will be hosted at the GeoSolutions offices in beautiful Tuscany for
a week long sprint.

Questions:
# Who would be interested in joining as a participating?
# Who would be interested in sponsoring? ;-)
# Do you have any preferred week between say Feb 13 and end of March?

== Plans ==

We are still at the planning stage so please let us know if a particular topic interests you or would be a deal breaker. The sprint does not have to be a single topic, if we can swarm a large beast good, but if someone wants to join and work on a side topic to leverage the presence of others, that’s good too.

* JDK 9 + maybe JDK 8 updates in the code base (like stream ready support for feature collection, where we can use lambda for profit)
* CITE - upgrade the test harness, make sure the tests are still passing (probably they won’t), add new test that we are missing, WFS 2.0, WCS 2.0, CSW, WMTS 1.0, WPS 1.0, maybe GML and KML and GeoPackage, maybe stand up a reference server for OGC to use, with one test per workspace/virtual service?
* REST API switch to Spring MVC (Andrea and Ian worried about making things worse user wise in terms of bugs) --- idea can we couple also fixing the actual bug reports in Jira? What about the other modules using restlet, importer and resource-rest-api, rest-upload, sldService, anything else? Need quite a bit of people.
* Mapbox style
* Library upgrades

== Participants ==

Please add your name and the projects
you are planning to sprint and note the likehood of your attendance.

{| style="border: solid grey 1px; width:100%" class="sortable"
|+ Participants
|-
| # || Participant || Country || Organization || Arrival || Departure || Project Work on || Attendance / Notes||
|-
| 1 || Andrea Aime || Italy || GeoSolutions || || || CITE or REST API switch || Preference for CITE, I'm game for the REST API switch too
|-
| 2 || Ian Turton || UK || Astun || || || CITE, Java 8 upgrade
|-
| 3 || Andrea Antonello || Italy || HydroloGIS || || || gvSIG and cross-project ideas || I have a strong preference for the end of March
|-

User:Moovida

2016-07-04T07:56:50Z

Moovida:

{{OSGeo Member
|Name=Andrea Antonello
|JobTitle=Tech lead
|Company=HydroloGIS
|Address=Bolzano, Alto Adige, Italia
|Country=Italia
|City=Bolzano
|Coordinate=46.497364, 11.348983
|LocalChapter=GFOSS.it
|Email=andrea DOT antonello AT gmail DOT com
|SocialMedia=http://twitter.com/themoovida;
|Website=http://www.andreaantonello.com/
|Photo=moovida.jpg
|Languages=Italian; German; English;
|Info=I'm an environmental engineer addicted to GIS development playing in the field of hydrologic and geomorphologic modelling with gvSIG and JGrasstools.

Since 2005 I'm cofounder of [http://www.hydrologis.com HydroloGIS], were we mainly develop around and make advanced use of gvSIG, JGrasstools and Geopaparazzi.
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=Yes
|Translate=No
|PSC=No
|ExBoard=No
|Charter=Yes
|Chair=No
|SolKatz=No
|Committer=No
}}
{{OSGeo Member FormEdit}}
=== [[User:Moovida|Andrea Antonello]] ===

[[File:moovida.jpg|thumb|right|100px|Andrea Antonello]]

[[Category:OSGeo Member]][[Category:Italy]]

Tech lead, HydroloGIS

Location: Bolzano, Alto Adige, Italia

I'm an environmental engineer addicted to GIS development playing in the field of hydrologic and geomorphologic modelling with uDig and JGrasstools.

Since 2005 I'm cofounder of [http://www.hydrologis.com HydroloGIS], were we mainly develop around and make advanced use of uDig, JGrasstools and Geopaparazzi.

;OSGeo Experience [[File:OSGeo_coder.png]] [[File:OSGeo_psc.png]] [[File:OSGeo_user.png]]

* core developer and PSC of [http://udig.refractions.net uDig].
* core developer of the [http://www.jgrasstools.org/ JGrasstools] project.
* core developer of the [http://www.geopaparazzi.eu Geopaparazzi] project.
* core developer of the [http://www.beegis.org BeeGIS] project.
* loves (and goes regularly to) FOSS4G conferences and code sprints
* does training courses on a regular basis

;Contact:
: Personal page: http://www.andreaantonello.com
: Email: andrea DOT antonello AT gmail DOT com
: Twitter: [http://twitter.com/themoovida themoovida]

;Spoken Language(s): Italian, German, English

;Profile last updated: 11 July 2012

[[Category:OSGeo Advocate]]

FOSS4G 2016 Code Sprint

2016-06-15T08:13:42Z

Moovida:

== CodeSprint ==

Venue: Bonn, Germany

This year, once again, we are following the old tradition of hosting a codesprint on the FOSS4G. More precisely, we offer a setting so that individual projects can meet for their codesprint. Since projects benefit from each other as well, the codesprint will naturally be held conjointly at one place.
Unfortunately, circumstances have forced us to divide the codesprint timetable-wise.

[[Image:Basecamp5.png|200px|thumb|right]]
[[Image:Basecamp6.png|200px|thumb|right]]
[[Image:Basecamp7.png|200px|thumb|right]]
[[Image:Basecamp1.png|200px|thumb|right]]

'''The first part''' is scheduled to take place directly before the conference, the second immediately after. The first two and a half days start on Sunday, August 21, 2016 at around noon and are scheduled to end on Tuesday, August 23, 2016 (open end). The '''second part''' starts in the morning of Saturday, August 27, 2016 and ends on Sunday at 12 pm.

[[Image:Basecamp2.png|200px|thumb|right]]
[[Image:Basecamp3.png|200px|thumb|right]]

We are happy to have found a really '''awesome location''' for you. Codesprint and accommodations are combined in one hall. Check out http://www.basecamp-bonn.com/ for details about the venue.
Working zones will be created for you in the breakfast area and hallways. There’s the option of finding relatively inexpensive sleeping accommodations in train sleeping cars, camping buses, classic cars and more. Additionally, an outdoor area is available for you to enjoy Bonn’s summer weather in August, while working. Healthy and not-so-healthy catering of drinks and snacks will be provided by us. Participation in codesprint is free of charge. However, overnight stays will have to be reserved and paid for by you.

[[Image:Basecamp4.png|200px|thumb|right]]

Another hint: the BaseCamp is within '''walking distance from the conference venue''' (WCCB) and has good access to public transportation – the Icebreaker takes place here, too.
You see, it’s worthwhile booking here!

As the accommodations are available to all FOSS4G participants, we will make an effort to make advance booking possible for you a few days ahead, to ensure you have the opportunity to sleep on-site and wrap up the evenings jointly. For that, it’s necessary for you to sign up (https://wiki.osgeo.org/wiki/FOSS4G_2016_Code_Sprint) and leave your email address so that we can contact you immediately accomodation booking is available. We need your sign-up for the planning of snacks and drinks, too!

This is open to all who wish to participate in one or more projects. There’s always plenty to do – it’s not all about programming. Translation, documentation, feedback, discussions, testing – all this is also important for project so everyone is cordially invited to attend the codesprints! Registration with the conference is not a prerequisite for participation in codesprint.

One thing we’d like to ask you: with an approx. 120 participants anticipated, the WLAN capacity will naturally be exhausted at some point. Please be sure to avoid huge on-site downloads of data, as this could impact the work of others. Thank you!

The Codesprint Organizing Team is looking forward to your coming!

'''In summary:'''

'''When:'''
* Part I: Sun 2016-08-21 12:00 noon - Tue 2016-08-23 (open end)
* Part II: Sat 2016-08-27 - Sun 2016-08-28 12:00 noon

'''Where:'''
* Venue & Accommodation: BaseCamp. (For more informations: http://www.basecamp-bonn.com/) [[http://www.openstreetmap.org/way/44335958#map=18/50.70763/7.12316| OpenStreetMap]]
* Nearby Hotel: Bonnox (http://www.bonnox.de/en/)

'''Questions/Comments/Ideas'''

* If you have questions/comments/ideas please let us know. Send an email to codesprint@foss4g2016.org. You are welcome!

== Sponsors ==
Thanks to our great sponsors!

[[File:FOSSGIS_OSGeo_DACH.png]]

== Registered Attendees ==

The Code Sprint does not cost any money. For us it makes planning easier if we know who is coming. So please leave your Name and mark the days you will come.

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|No
!width="250"|Name
!width="250"|Email
!width="250"|Projects
!width="30"|sun
!width="30"|mon
!width="30"|tue
!width="30"|sat
!width="30"|sun
!width="60"|Accomodation
!width="30"|vegetarian food
|-
| 1 ||[[User:Astrid Emde|Astrid Emde]] || astrid_emde@osgeo.org || [[Mapbender]] & Organization || x || x || x || x || x || other || x
|-
| 2 ||[[User:rcoup|Rob Coup]] || robert@coup.net.nz || [[GDAL]], [[GeoServer]] || - || x || x || - || - || Basecamp ||
|-
| 3 ||[[User:alfonx|Stefan Tzeggai]] || tzeggai@wikisquare.de || || - || - || x || x || - || Basecamp? ||
|-
| 4 ||[[User:Neteler|Markus Neteler]] || neteler@osgeo.org || [[GRASS GIS]] || x || x || x || x || x || other || x
|-
| 5 ||[[User:pcav|Paolo Cavallini]] || cavallini@faunalia.it || [[QGIS]] || x || x || x || x || x || Basecamp? ||
|-
| 6 ||[[User:Pirmin_Kalberer|Pirmin Kalberer]] || pka [ät] sourcepole.ch || [[QGIS]], [[GDAL]] || x || x || x || - || - || Basecamp ||
|-
| 7 ||[[User:neumann|Andreas Neumann]] || andreas [ät] qgis.org || [[QGIS]] || x || x || x || x || - || Basecamp ||
|-
| 8 ||[[User:timlinux|Tim Sutton]] || tim [ät] qgis.org || [[QGIS]] || x || x || x || x || - || Basecamp || yes
|-
| 9 ||[[User:Lucadelu|Luca Delucchi]] || lucadeluge @ gmail.com || [[GRASS GIS]] || x || x || x || x || x || Basecamp ||
|-
| 10 ||[[User:Schpidi|Stephan Meißl]]||stephan [ät] meissl.name||MapServer, EOxServer||?||?||x||-||-||Basecamp||
|-
| 11 ||[[User:lastools|Martin Isenburg]] || martin near rapidlasso.com || LASzip for LAS 1.4 || x || x || x || x || x || Basecamp ||
|-
| 12 || [[User:jgrocha|Jorge Gustavo Rocha]] || jgr@di.uminho.pt || GeoExt 3 || x || x || x || x || x || Basecamp ||
|-
| 13 || [[User:alexbruy|Alex Bruy]] || alexander.bruy at gmail.com || [[QGIS]] || x || x || x || x || x || Basecamp ||
|-
| 14 || [[User:volaya|Victor Olaya]] || volayaf at gmail.com || [[QGIS]] || x || x || x || x || x || Basecamp ||
|-
| 15 || [[bartvde2|Bart van den Eijnden]] || bartvde at osgis.nl || [[OpenLayers]] || ? || x || x || ? || ? || Basecamp? ||
|-
| 16 || [[User:anitagraser|Anita Graser]] || anitagraser [ät] gmx.at || [[QGIS]] || x || x || x || ? || ? || Basecamp ||
|-
| 17 ||[[User:Dmorissette|Daniel Morissette]]||dmorissette at mapgears.com||MapServer, GDAL/OGR||?||?||x||x||?||Basecamp||
|-
| 18 ||[[User:Stranger | Andreas Schmitz]] || hwbllmnn@mailbox.org || Mapbender || || || || || || other ||
|-
| 19 ||[[User:Uli | Uli Rothstein]] || || Mapbender || || || || || || other ||
|-
| 20 ||[[User:Tbonfort|Thomas Bonfort]]||thomas.bonfort@gmail.com||MapServer||?||?||x||x||?||Basecamp||
|-
| 21 || CCC VOC Team || || video || || || || || || Basecamp ||
|-
| 22 || CCC VOC Team|| || video || || || || || || Basecamp ||
|-
| 23 || CCC VOC Team || || video || || || || || || Basecamp ||
|-
| 24 || CCC VOC Team || || video || || || || || || Basecamp ||
|-
| 25 ||CCC VOC Team || || video || || || || || || Basecamp ||
|-
| 26 ||[[User:Martinl|Martin Landa]] || || [[GRASS GIS]], [[GDAL]], [[QGIS]], [[PyWPS]], GIS.lab || x || x || x || x || x|| Basecamp? ||
|-
| 27 ||[[User:jachym|Jáchym Čepický]] || jachym.cepicky at gmail || [[PyWPS]], GIS.lab || x || x || x || x || x|| Basecamp ||
|-
| 28 ||[[User:Jonaseberle|Jonas Eberle]] || jonas.eberle at gmx.de || [[PyWPS]] || x || x || x || x || x || Basecamp/other? ||
|-
| 29 ||[[User:dassau|Otto Dassau]] ||otto at qgis.org || [[QGIS]] || x || x || x || - || - || other || yes
|-
| 30 ||[[User:rouault|Even Rouault]]||even.rouault @ spatialys.com||GDAL, MapServer, QGIS||?||?||x||x||?||Basecamp||
|-
| 31 ||[[User:grizonnetm|Manuel Grizonnet]]||manuel.grizonnet @ cnes.fr||OTB, OSGeo-Live, QGIS||x||x||x||-||-||Basecamp||
|-
| 32 ||[[User:mlennert|Moritz Lennert]]||mlennert at club worldonline be||GRASS GIS||x||x||x||?||?||Other/Basecamp||
|-
| 33 ||Verena Diewald || || Mapbender || || || || || || other ||
|-
| 34 ||Andriy Oblivantsev || || Mapbender || || || || || || other ||
|-
| 35 ||Axel Schaefer || || Mapbender || || || || || || other ||
|-
| 36 || David Patzke || || Mapbender || || || || || || other ||
|-
| 37 || Thekla Wirkus || || Mapbender || || || || || || other ||
|-
| 38 || Charly Toma || || Mapbender || || || || || || other ||
|-
| 39 ||[[User:Lads|Luís de Sousa]] ||luis de sousa @ protonmail ch || [[PyWPS]] || ? || x || x || x || ? || Basecamp? ||
|-
| 40 ||[[User:ajolma|Ari Jolma]]||ari.jolma @ gmail.com||GDAL, MapServer, QGIS||?||?||x||x||?||Beethoven||
|-
| 41 ||[[User:magicgate|Jakob Miksch]]||jakob.miksch [ät] posteo.eu||QGIS||x||?||?||x||x||Basecamp||
|-
| 42 ||[[User:Yjacolin|yjacolin]] ([[User talk:Yjacolin|talk]]) || yves dot jacolin [at] camptocamp.com ||QGIS||x||x||x|| || ||Basecamp?||
|-
| 43 || Arnaud Morvan ||arnaud dot morvan @ camptocamp.com||QGIS||x||x||x|| || ||Basecamp||
|-
| 44 || Stéphane Brunner || stephane dot brunner [at] camptocamp.com || QGIS || x || x || x || || || Basecamp? ||
|-
| 45 || [[User:asgerskovbopetersen|Asger Skovbo Petersen]] || asger ãt septima.dk || QGIS || - || x || x || - || - || Other ||
|-
| 46 ||[[User:Tudorbarascu|Tudor Bărăscu ]] || tudor dot barascu [at] qtibia.ro || [[QGIS]] || x || x || x || x || x || Basecamp? ||
|-
| 47 ||[[User:moovida|Andrea Antonello ]] || andrea dot antonello [at] gmail dot com || gvSIG || - || - || x || - || - || other ||
|-
| 48 ||[[User:Silli|Silvia Franceschi ]] || silvia dot franceschi [at] gmail dot com || gvSIG || - || - || x || - || - || other ||
|}

= Workgroups =

== Mapbender ==

'''Attending:'''

* [[User:Astrid Emde|Astrid Emde]]
* [[User:Stranger | Andreas Schmitz]]
* [[User:Uli | Uli Rothstein]]
* Axel Schaefer
* David Patzke
* Andriy Oblivantsev
* Verena Diewald
* Charly Toma
* Thekla Wirkus

'''Goals:'''
* modularisation
* tests
* documentation
* & more

== GRASS GIS ==

'''Attending:'''

* [[User:Neteler|Markus Neteler]]
* [[User:Lucadelu|Luca Delucchi]]
* [[User:Martinl|Martin Landa]]
* [[User:mlennert|Moritz Lennert]]

'''Goals:'''

* planning towards GRASS GIS 8
* integrating GSoC results

== QGIS ==

'''Attending:'''

* [[User:pcav|Paolo Cavallini]]
* [[User:Pirmin_Kalberer|Pirmin Kalberer]]
* [[User:neumann|Andreas Neumann]]
* [[User:volaya|Victor Olaya]]
* [[User:alexbruy|Alex Bruy]]
* [[User:anitagraser|Anita Graser]]
* [[User:dassau|Otto Dassau]]
* [[User:Yjacolin|yjacolin]]
* Arnaud Morvan
* [[User:Tudorbarascu|Tudor Bărăscu]]

'''Goals:'''

* working on QGIS 3.0
* porting plugins to Python 3
* Working on QWC II
* Working on QGIS Processing framework
* Working on Documentation 2.14/2.16

== PyWPS ==

'''Attending:'''

* [[User:jachym|Jachym Cepicky]]
* [[User:Jonaseberle|Jonas Eberle]]
* [[User:Lads|Luís de Sousa]]

'''Goals:'''

* What is needed for PyWPS-4
* Discuss new steps
* WPS 2.0.0 start

== GIS.lab ==

'''Attending:'''

* [[User:martinl|Martin Landa]]
* [[User:jachym|Jachym Cepicky]]

'''Goals:'''

* GIS.lab 1.0
* GIS.lab QGIS Plugin
* new generation of GIS.lab Web Client
* WPS Processing

== OSGeo-Live ==

'''Attending:'''

*[[User: Astrid Emde]]
* [[User:grizonnetm|Manuel Grizonnet]]

'''Goals:'''

* next version
* documentation
* translation

== GeoMoose ==

'''Attending:'''

* [[User:theduckylittle|Dan "Ducky" Little]]

''Goals:'''

* 3.0 release!

== ORFEO ToolBox ==

'''Attending:'''

* [[User:grizonnetm|Manuel Grizonnet]]

''Goals:'''

* Documentation
* QGIS/OTB compatibility
* Bugs

== gvSIG ==

'''Attending:'''

* [[User:moovida|Andrea Antonello]]
* [[User:Silli|Silvia Franceschi]]

''Goals:'''

* Developer Documentation
* JGrasstools integration
* Geopaparazzi integration
* Bug fixes

== Project-name ==

To participate, copy this project skeleton and start a section below for your project.

'''Attending:'''

*user
*user

'''Goals:'''

*your goals

[[Category:FOSS4G2016]] [[Category:FOSS4G]] [[Category:Code_Sprints]]

Google Summer of Code 2016 Administrative

2016-03-03T09:20:00Z

Moovida: /* Mentors */

<center>
[[Image:GSoC2016Logo.jpg|500px|link=https://summerofcode.withgoogle.com/]] @ [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]
</center>

* Back to the main OSGeo [[Google Summer of Code 2016]] @ OSGeo wiki page.

This is the central page for OSGeo administrative information in Google Summer of Code 2016.

== GSoC general information ==

* [https://developers.google.com/open-source/gsoc/timeline The official timeline]
* [https://developers.google.com/open-source/gsoc/resources/ Google's FAQ on the program]
* [https://summerofcode.withgoogle.com/ Official 2016 GSoC site]

== Contacts ==

* [[User:Madi|Margherita Di Leo]] acts as Administrative contact, with support from [[User:Aghisla|Anne Ghisla]]. Feel free to email us with any questions, we're here to help mentor the mentors as much as anything else!

* Would-be mentors and students: you are invited to sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailing list] right away. The list is the central communication channel for mentors, students and administrators. It is used for general GSoC announcements, specific OSGeo announcements, and for clarification about the program. As soon as you subscribe it, you are encouraged to introduce yourself and your role. We look forward to hear from you!

== Mentors ==

If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please add your name, email, OSGeo/guest software and the projects you're interested in mentoring here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#D7E3D1; font-size:95%; empty-cells:show;"
|width=30px|'''Number'''
|width=100px|'''Name'''
|width=100px|'''Surname'''
|width=100px|'''Nickname (IRC)'''
|width=200px|'''email'''
|width=100px|'''Software'''
|'''Project / Idea(s) you are available to mentor'''
|-
|1
|Margherita
|Di Leo
|madi
|diregola AT gmail DOT com
|admin at OSGeo
|Administrator of GSoC at OSGeo
|-
|2
|Alexander
|Bruy
|alexbruy
|alexander.bruy AT gmail.com
|QGIS
|QGIS
|-
|3
|Victor
|Olaya
|volaya
|volayaf AT gmail DOT com
|QGIS
|QGIS
|-
|4
|Daniel
|Kastl
|dkastl
|daniel AT georepublic DOT de
|pgRouting
|pgRouting
|-
|5
|Massimiliano
|Cannata
|maxi
|massimiliano.cannata AT gmail DOT com
|istSOS
|istSOS
|-
|6
|Milan
|Antonovic
|milan
|milan.antonovic AT gmail DOT com
|istSOS
|istSOS
|-
|7
|Jachym
|Cepicky
|jachym
|jachym.cepicky AT gmail
|PyWPS
|PyWPS
|-
|8
|Andrea
|Antonello
|moovida
|andrea.antonello AT gmail DOT com
|JGrasstools, gvSIG, Geopaparazzi
|JGrasstools, gvSIG, Geopaparazzi
|-
|}

== A Mentor's Responsibilities ==

Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find :). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.

Every student project will also have a '''backup mentor''', this person should come from your programming team and should at minimum keep up to date with the student's weekly developments. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.

You '''must''' be available at some time during the '''midterm and final evaluation period'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filed within these dates.

== Guides for mentors ==

* [http://en.flossmanuals.net/GSoCMentoring/ The GSoC Mentoring Guide] - A must. Do get all useful info and tips from many years of experience from GSoC mentors.
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]

== Learn more ==

* Previous years SoC involvement: [http://code.google.com/soc/2008/osgeo/about.html 2008], [http://www.google-melange.com/gsoc/org/google/gsoc2009/osgeo 2009], [http://www.google-melange.com/gsoc/org/google/gsoc2010/osgeo 2010], [http://www.google-melange.com/gsoc/org/google/gsoc2011/osgeo 2011], [http://www.google-melange.com/gsoc/org/google/gsoc2012/osgeo 2012], [http://www.google-melange.com/gsoc/org/google/gsoc2013/osgeo 2013], [https://www.google-melange.com/gsoc/org2/google/gsoc2015/osgeo 2015]

* OSGeo GSoC wiki pages: [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2009|2009]], [[Google Summer of Code 2010|2010]], [[Google Summer of Code 2011|2011]], [[Google Summer of Code 2012|2012]], [[Google Summer of Code 2013|2013]], [[Google Summer of Code 2014|2014]], [[Google Summer of Code 2015|2015]]

* OSGeo Applications: [[Google SoC Application 2009|2009]], [[Google SoC Application 2010|2010]], [[Google Summer of Code Application 2011|2011]], [[Google Summer of Code Application 2012|2012]], [[Google Summer of Code Application 2013|2013]], [[Google Summer of Code Application 2014|2014]], [[Google Summer of Code Application 2015|2015]], [[Google Summer of Code Application 2016|2016]]

[[Category: Google Summer of Code]]

LIDAR Format Letter

2015-04-16T11:17:30Z

Moovida: /* Signed */

=Open Letter of the Need for Open Standards in LiDAR=
April 2015.

We, the undersigned, are concerned that the current interoperability between LiDAR applications, through use of the open "LAS" format, is being threatened by ESRI's introduction and promotion of an alternative "Optimized LAS" '''''proprietary format.''''' This is of grave concern given that fragmentation of the LAS format will reduce interoperability between applications and organisations, and introduce vendor lock-in.

We request that:
# The OGC initiate the formalisation of an open standard for storing LiDAR data, and that OGC sponsors help prioritise the development of this open LiDAR standard.
# ESRI support the OGC in their [http://www.opengeospatial.org/ogc/vision mission] "to advance the development and use of international standards and supporting services that promote geospatial interoperability." In particular, ESRI join the OGC in consolidating an Open Standard for use of LiDAR data. This might include proposing ESRI's "Optimized LAS" as an Open Standard to remove any technical or legal hurdles in use of "Optimized LAS" as an Open Standard. A simple test to determine if "Optimized LAS" can be used as an Open Standard would be if "Optimized LAS" can legally be implemented by Open Source software such as libLAS or LASzip.
# Users and sponsors of LiDAR data, publicly state their preference for the use of an open LiDAR format over proprietary when selecting software and services.
# The custodians of the open LAS format [http://www.asprs.org/LD-Division/LAS-Working-Group.html LAS Working Group (LWG)], who are part of [http://www.asprs.org/ American Society for Photogrammetry and Remote Sensing (ASPRS)], request the term "LAS" not to be included in the name of a proprietary format, as it makes such a proprietary format appear to be an approved derivative of LAS.

=Signed=
Name, Affiliation(s), Optional comment on interest in Open LiDAR format

# Suchith Anand, Geo for All, committed to Open Principles in Geo Education and Policy.
# Martin Isenburg, founder of [http://rapidlasso.com rapidlasso GmbH] and creator of [http://rapidlasso.com/LASzip LASzip], [http://rapidlasso.com/LAStools LAStools], and [http://rapidlasso.com/PulseWaves PulseWaves].
# Cameron Shorter, GeoSpatial Director at [http://lisasoft.com LISAsoft], Core contributor and coordinator of [http://live.osgeo.org OSGeo-Live], Contributor to numerous OGC testbeds, technical lead on a range of previous Australian and New Zealand Open Government initiatives.
# Stefan Keller, founder and director of [http://www.hsr.ch/geometalab Geometa Lab]; researcher in GIS, databases, open (government) data and interoperability; maintainer of GeoConverter; contributor to open source software (GDAL/OGR, QGIS).
# Patrick Hogan, NASA World Wind Project Manager, committed to the US National Spatial Data Infrastructure principles, one being "to make geographic data more accessible to the public" [http://www.fgdc.gov/nsdi/nsdi.html NSDI]. Open standards are essential for this.
# Lene Fischer, Associate Professor, Department of Geosciences and Natural Resource Management, University of Copenhagen. User of Open and free Data from The Danish Geodata Agency - Using LAZ and LAS http://download.kortforsyningen.dk/content/dhmpunktsky.
# [http://www.ege-como.polimi.it/index.php?content=maria_brovelli Maria Antonia Brovelli], Full Professor, Department of Civil and Environmental Engineering, Politecnico di Milano. Geo For All, committed to Open Principles in Geo Education and Policy. Committed to Open Principles in Research.
# Ron Fortunato, President of [http://www.trilliumlearning.com/AmericaBridge/ Trillium Learning] LLC. Committed to open data standards that are necessary for education and all levels of communication.
# Armin Schmidt, Chief Developer at [http://www.GeodataWIZ.com GeodataWIZ Ltd] and Chairman of [http://www.archprospection.org ISAP], committed to better science through Open Data.
# [http://www.linkedin.com/in/gconti Giuseppe Conti], CTO Trilogis Srl, Italy. Committed to open data standards that maximize opportunity for innovative solutions, unencumbered by artificial obstacles to data exchange.
# Jorge Gustavo Rocha, Professor, Computer Science Department, University of Minho, Portugal, committed to better science through Open Data.
# Jim Miller, University of Kansas, Professor, Computer Science, http://people.eecs.ku.edu/~miller/ Open standards for data exchange are essential for education and research.
# Alex Paza Makini, National University Solomon Islands, Natural Resources and Applied Science. Committed to open data standards for education and research, and everything beyond.
# Prof. Jorg M. Hacker, Director/Chief Scientist of [http://www.airborneresearchaustralia.com Airborne Research Australia], Flinders University, Adelaide, Australia. Open formats have always been a great benefit to airborne LiDAR.
# Didier Richard, Head of IS Training Dept. in Education and Research Directorate of [http://www.ign.fr Institut National de l'Information Géographique et Forestière], France. OGC user, Contributor to OSGeO projects like GDAL.
# [http://www.linkedin.com/pub/adryane-gorayeb/74/517/96a Adryane Gorayeb], [http://www.ufc.br/ Federal University of Ceará Brazil], Geography Department. Open standards for data exchange are essential for education and research.
# [http://www.linkedin.com/in/yuryryabov Yury Ryabov], PhD, Senior researcher at [http://www.istc.ru/istc/db/inst.nsf/wsu/i0001823 Russian Scientific-Research Centre for Ecological Safety], [http://www.interacademies.net/Academies/ByRegion/CentralEasternEurope/13383.aspx Russian Academy of Sciences], Saint Petersburg, Russia. Open data formats are essential for successful and reproducible scientific research.
# [http://www.linkedin.com/pub/teresa-lamelas-gracia/40/4a7/20b María Teresa Lamelas], [http://cud.unizar.es/ Centro Universitario de la Defensa Zaragoza], [http://geoforest.unizar.es/es/index.php GeoForest-IUCA]. Committed to open data standards for education and research.
# [http://www.linkedin.com/in/davidherries David Herries], [http://www.interpine.co.nz/SitePages/Home.aspx Using LiDAR for forest yield modelling at Interpine Innovation], Establishing open data standards provide scope for exponential growth in innovation. This is key to a rapidly developing technology like LiDAR.
# [[User:Ivansanchez|Iván Sánchez Ortega]], [http://www.mazemap.no Mazemap]. OSGeo Charter member and Open Data nerd.
# [[User:AnitaGraser|Anita Graser]], GIS specialist with AIT Austrian Institute of Technology, OSGeo Charter member and QGIS team member. Committed to open data standards for education and research.
# [[User:vehrka|Pedro-Juan Ferrer]], [http://www.geomaticblog.net Geomaticblog]. OSGeo Charter member and member of the Open Knowledge Foundation.
# [http://www.linkedin.com/pub/karl-donert/3/160/571 Professor Karl Donert], President European Association of Geographers (http://www.eurogeo.nl/ EUROGEO)
# Drew Fenton. Please Protect Open Standards for Geospatial data!
# [[User:Bolosig|Wladimir Szczerban]], [http://www.geoinquiets.cat Geoinquiets] Geogeek & OSGeo Spanish Local Chapter Member, Spain
# [http://vmx.cx Volker Mische], OSGeo Charter member and creator of GeoCouch
# [[User:carlos_psig|Carlos López Quintanilla]], [http://www.psig.es PSIG] [http://www.geoinquiets.cat Geoinquiets] GIS consultant, Spain
# [[User:woodbri|Stephen Woodbridge]], [http://imaptools.com iMaptools], OSGeo Charter member.
# [[User:odoepner|Oliver Doepner]], [http://oliver.doepner.net doepner.net], Software Engineer (Java,Linux), Open Standards and Open Source advocate
# [[User:Lucadelu|Luca Delucchi]], [http://gis.cri.fmach.it Fondazione Edmund Mach], OSGeo Charter member, FOSS4G and Open Data developer, advocate, contributor and user.
# Antoine Cottin, CTO of [http://www.carbomap.com Carbomap Ltd.] and creator of [https://github.com/carbomap/Fleurdelas Fleurdelas], Edinburgh, United Kingdom.
# [http://strk.keybit.net Sandro Santilli], [http://strk.keybit.net/services.html NetLab], Free Software Hacker. There are already too many users slave to their tools, let's stop that!
# [http://www.itopen.it Alessandro Pasotti], [http://www.itopen.it ItOpen], GIS Free Software Developer.
# [http://www.roccatello.com Eduard Roccatello], [http://www.3dgis.it 3DGIS], 3DGIS CTO and co-Founder
# [[User:moovida|Andrea Antonello]], [http://www.hydrologis.com HydroloGIS], OSGeo Charter member, Open Source GIS developer, HydroloGIS co-founder.

=Background=
==About LiDAR==

[http://en.wikipedia.org/wiki/Lidar LiDAR] (Light Detection And Ranging) is a form of high precision range measurement, much like a radar system, that uses laser light instead of electromagnetic waves. The standard LiDAR product is a 3D point cloud that can be conceptualized as a series of point measurements representing distance between the sensor to a returned emission.

For over a decade (since 2003), there has been a common format for storing LiDAR data, the [http://www.asprs.org/Committee-General/LASer-LAS-File-Format-Exchange-Activities.html “LAS” format], and open source libraries have been developed to read, write and process these LAS files: [http://live.osgeo.org/en/overview/liblas_overview.html libLAS] and [http://github.com/LASlib/LASlib LASlib]. These libraries have been incorporated within many LiDAR applications, allowing read/write access to a common exchange format, and resulting in full interoperability between the applications. There is also an open source compression algorithm for the LAS format called [http://laszip.org LASzip] that many LiDAR data portals use to compress LAS into smaller LAZ files for faster download. Many LiDAR software packages have added [http://laszip.org/#software-with-native-laz-support native support] for these compressed LAZ files.

==LAS Limitations==

Quoting [http://boundlessgeo.com/2014/01/lidar-format-wars/ Paul Ramsey]:

: LAS format is not without its drawbacks:

:* While it is a binary format and does not waste any space unnecessarily, neither does it apply any compression to the data it stores. That’s not good for archival use.
:* Also, LAS stores points in scan order, so accessing any particular chunk of points involves reading the whole file. That’s not good for random access.
: Clearly there is a little more work to be done. Can LAS be improved? In fact, it already has been:
:* An open source compression library, LASzip can apply 20''':'''1 lossless compression to LAS files, making them great for archival purposes.
:* Other LAS users have experimented with re-ordering points in a LAS or LASzip file to allow random access to internal chunks of the LIDAR point cloud.
: Basically, making LAS smaller and faster is not rocket science, and if the work were incorporated into libLAS then the whole LIDAR community could leverage it together, and the user community would only have one file type to interchange.

=="Optimized LAS" A ''' ''Proprietary'' ESRI Format'''==
ESRI has announced the release of an [http://www.lidarnews.com/content/view/10214 "Optimized LAS"] format which is claimed to provide faster access and smaller file sizes (similar to the open [http://laszip.org LASzip] format). This announcement created a outburst of vocal protest in the LiDAR community [[http://rapidlasso.com/2013/12/30/new-compressed-las-format-by-esri/ 1] [http://boundlessgeo.com/2014/01/lidar-format-wars/ 2] [http://www.spatiallyadjusted.com/2014/01/15/las-laz-lazzip-zlas-and-you/ 3] [http://www.northrivergeographic.com/archives/lidar-software 4] [http://boundlessgeo.com/2014/01/lidar-format-wars-2/ 5] [http://boundlessgeo.com/2014/02/lidar-format-wars-3/ 6]].

The "Optimized LAS" format is neither published, nor available under any open license, which provides both technical as well as legal barriers for other applications reading and/or writing to this proprietary format. This creates a vendor lock-in scenario which is contrary to the principles of the Open Geospatial Consortium, the OSGeo Foundation, and many government IT procurement policies.

One year after releasing the "Optimized LAS" format, ESRI released a free Windows DLL that is claimed to convert between LAS and "Optimized LAS". Note there is a distinct difference between "free" and "open". Unless the Windows DLL is released under an "open" license, libLAS and related products will be legally prevented from incorporating ESRI's reader/writer code into their codebase, or from fixing any underlying bugs or performance limitations which may exist in ESRI's product.

==OGC's Efforts For An ''' ''Open'' LiDAR Standard'''==

The [http://www.opengeospatial.org/ Open Geospatial Consortium (OGC)] has indicated their interest in developing a standard LiDAR format.

Carl Reed (formerly on OGC staff) provided the following information on OGC's previous efforts to work toward enabling Open Standards in LiDAR:

: "Over the last 8 or so years, the OGC approached ASPRS at least twice regarding LAS and worked with ASPRS to bring LAS into the OGC for consideration as both a Best Practice and an OGC standard. OGC member Rick Pearsall worked diligently on this. Rick worked for NGA, was active in the OGC, and was also the Standards Committee chair at ASPRS. Rick and Carl tried and failed. These attempts go back to [http://www.asprs.org/a/society/divisions/ppd/ppd_meetings/2007springppdreport.pdf at least 2007]. More recently, Carl Reed had an email dialogue with Lewis Graham to bring LAS into OGC as an OGC Best Practice. Carl thought progress was being made, but then for some reason all communication stopped."

[http://www.opengeospatial.org/ogc/organization/staff/ssimmons Scott Simmons] (Executive Director, Standards Program) has explained the OGC's continuing interest in pursuing point cloud encoding standards, including a member-initiated mechanism to extend LAS data with OGC-standard XML content.
: The OGC invites interested members who wish to work on this effort to please contact Scott Simmons (Executive Director, Standards Program E-mail : ssimmons@opengeospatial.org) to register their interest and discuss details. OGC will also be holding an ad hoc session at the OGC's next [http://www.opengeospatial.org/event/1506tc Technical Committee meeting in Boulder, CO, USA in early June] to bring together all interested parties from all sectors (government, industry, academia) for this and plan next steps.

==History: LAS and ESRI's "Optimized LAS"==

Martin Isenburg, one of the leading experts in LIDAR formats, and creator of [http://rapidlasso.com/LASzip LASzip], [http://rapidlasso.com/LAStools LAStools] and [http://rapidlasso.com/PulseWaves PulseWaves], explains the history of LAS and "Optimized LAS":

: '''Summary:'''

:* The LAS format has been used successfully for over a decade.
:* Within last couple of years, ESRI has added native LAS support into ESRI products.
:* ESRI discussed embracing the open [http://laszip.org LAZ] format and simultaneously developed a proprietary "Optimized LAS" format.
:* The open geospatial community offered, on numerous occasions, to work with ESRI to avoid format fragmentation.
:* ESRI's proprietary "Optimized LAS" format is very similar in design and performance to the open [http://laszip.org LASzip] format.

: '''1998: Original LAS format definition'''

: The original development of the LAS format started in 1998 according to [http://groups.google.com/forum/#!topic/lasroom/zKqchDj1JL4/discussion Lewis Graham]. The effort was at first led by pioneers of the LiDAR industry until the format was donated to the [http://www.asprs.org/Committee-General/LASer-LAS-File-Format-Exchange-Activities.html ASPRS]. Since then ASPRS's [http://www.asprs.org/LD-Division/LAS-Working-Group.html LAS Working Group (LWG)] has been maintaining the LAS format, guiding it from the initial LAS 1.0 version until today's LAS 1.4 version. This effort successfully created an open data exchange format for discrete LiDAR points that is currently supported by practically every LiDAR-related software program.

: '''2011: ESRI joins LAS Working Group'''

: ESRI did not join the LWG of the ASPRS until rather late, the 24th of August in 2011. At that time ESRI was not a significant "player" in the LiDAR market given they did not have much support for LiDAR in any of their products. That was to change soon as they were planning to add LAS as a native data type in ArcGIS 10.1.

: Shortly before that, in June 2011, Martin Isenburg received a personal message from the ESRI development team: "I have a question about LAS compression. I’m evaluating some potential enhancements and support for [LAS and] LAZ is one of them. Compression time and amount is impressive." When inquiring two months later about the status of [http://laszip.org LAZ] integration Martin was told: "We’re in beta and working to finish the current release. I very much doubt LAZ will make it in because it’s too big a change at this time. So, we’ll be considering, for the following release, [for] what we want to do regarding compression and spatial indexing."

: '''June 2012: ArcGIS 10.1 includes [proprietary] LAS Dataset file'''

: In June 2012 ESRI released ArcGIS 10.1 and introduced the proprietary "LAS Dataset file (*.lasd)" that groups collections of files into one logical unit. This format of this useful LAS container file was not shared with others despite several private and eventually [http://groups.google.com/d/topic/lastools/jwHpi0efUgA/discussion public] requests.

: '''2012/2013: Collaboration Discussions'''

: There were encouraging follow-ups from the ESRI team about adopting the open LAZ format in January 2012: "I would be interested in having a more in depth meeting with you to better understand the great work you are doing with LAS and how we can possibly better partner on this." and again in December 2012: "If you have time, I'd like to set some time aside Tuesday afternoon to meet with <an important person> at the ESRI booth. Does 2pm sound okay?" The meeting went well and it looked as if ESRI was going to embrace the LAZ format because shortly after the meeting Martin got word that: "I hear from <an important person> that it was a success and that he had a good meeting with you. I wanted to see if we can have a telephone discussion on Wednesday or Thursday this week related to the potential of incorporating LAZ into ArcGIS."

: Then the first signs of hesitation showed. First there were legal issues raised in February 2013: "Currently the legal aspects are being reviewed. They were having some issues separating the LPGL aspects from LASzip from the remainder of LAStools etc." and then in April 2013 concerns about the code were made: "We have started to look into the integration of LAZ, but came across some issues. We don’t want to copy files from the other package, mix and match or hack around. We were hoping for an API to stream points out of a LAZ file as well as write LAZ files. There should be a simple code sample for that?" and - following up on that - in June 2013 Martin was told "I see value in LASzip becoming a de-facto standard that provides compression to the LAS format. If this is to happen then it needs to be bundled together with appropriate reference implementations, examples and documentation as a standard and so ensure that issues as defined earlier in email do not occur."

: '''June 2013: ESRI asked to sponsor clean LASzip DLL'''

: At that time [http://laszip.org LASzip] was an open source project without sponsorship. The original funding from [http://www.erdc.usace.army.mil/Locations/ColdRegionsResearchandEngineeringLaboratory.aspx USACE] that had turned [http://laszip.org LASzip] from an academic prototype into an industry strength compression engine had long run out. So Martin asked ESRI to become a sponsor to create the clean [http://laszip.org LASzip] API that ESRI was after. The answer was: "ESRI often helps in the financing of Open Source projects and I could foresee ESRI possibly helping in LASzip. [...] If you are interested in promoting LASzip as such a standard and doing the required work then I would recommend you put together a proposal and I can look to get ESRI as a sponsor."

: Immediately Martin proposed to ESRI: "I hereby propose to write an easy to use open source DLL wrapper for LASzip that will make it easier to integrate LASzip in a standardized manner into other software products such as ArcGIS, LP 360, or Terrasolid. This will come with example code on how to use the DLL for reading and writing LAZ files and include a few compressed example files. I hereby ask ESRI to provide funding for this effort without imposing any limitations on the produced DLL API."

: '''July 2013: ArcGIS 10.2 includes [proprietary] LAS indexing '''

: With the release of ArcGIS 10.2 in July 2013, ESRI introduced spatial indexing to speed up area-of-interest queries. The new proprietary *.lasx files with seemingly identical functionality to the open *.lax files that had been [http://groups.google.com/d/topic/lastools/j0qA8NBMHJs/discussion announced] in May 2011 and were [http://rapidlasso.com/2012/12/03/lasindex-spatial-indexing-of-lidar-data/ presented] at ELMF in November 2012.

: '''July 2013: Open LASzip API released'''

: After more requests for an easier interface to [http://laszip.org LASzip] (in particular for [http://forsys.cfr.washington.edu/fusion/fusionlatest.html USDA's FUSION]), Martin [http://groups.google.com/d/topic/lastools/oplsDhhnhDQ/discussion released] a clean, well-documented, and easy-to-use LASzip DLL (without ESRI funding). Martin expected that developers at ESRI would now use it to add read and write support for [http://laszip.org LAZ] to their next release of ArcGIS.

: '''December 2013 : ESRI discovered to be secretly developing proprietary LAS format'''

: In December of 2013, several LAStools users contacted Martin with suspicions that ESRI may be creating a proprietary LAS compression. Martin [http://rapidlasso.com/2013/12/30/new-compressed-las-format-by-esri/ broke the news] as soon as it became evident that ESRI had used the time it needed to resolve "legal issues" and "code problems" to put together their own proprietary compressed format with near-identical performance and functionality to [http://laszip.org LASzip]. A few days later ESRI released an [http://www.lidarnews.com/content/view/10214/ official FAQ] to confirming this was the case.

: From day one, Martin has worked with stakeholders, including ESRI, to avoid format fragmentation. Martin's core argument for resolving this to everybody's benefit was that - coincidentally - a natural break was happening in the LAS format with the introduction of the new LAS 1.4 point types. Martin outlined a detailed plan for how a joint development of [http://laszip.org LASzip] for LAS 1.4 between rapidlasso and ESRI could exploit this natural break in the LAS format to accomplish two things at once:
:# Add the unspecified technical additions that ESRI had hinted at desiring, and
:# Extend the [http://laszip.org LASzip] compression scheme to handle the new point types introduced with the LAS 1.4 specification. As there was no pressing need at the time to handle LAS 1.4 Martin had delayed the extension of [http://laszip.org LASzip] to the new LAS 1.4 point types to make sure a cooperation with ESRI would remain a viable option.

: '''1 April 2014: Positive reception to "Optimized LAS" / LASzip collaboration April Fools announcement'''

: In an attempt to convince ESRI management of the community desire for an open standard, Martin released an April Fools' Day [http://rapidlasso.com/2014/04/01/esri-and-rapidlasso-develop-joint-lidar-compressor/ prank press release] pretending that ESRI had already agreed to the envisioned collaboration to develop a joint LiDAR compressor. Community [http://rapidlasso.com/2014/04/01/esri-and-rapidlasso-develop-joint-lidar-compressor/ jubilant reactions (see comments)] left no doubt about the sentiment on this issue within the LiDAR community.

: '''October 2014: Announcement of [open] LAS Compatibility mode'''

: [http://www.csc.noaa.gov/digitalcoast/ Digital Coast, NOAA Coastal Services Center] became a Gold Sponsor of [http://laszip.org LASzip] for the development of the [http://rapidlasso.com/2014/10/06/rapidlasso-announces-laszip-compatibility-mode-for-las-1-4/ LAS 1.4 compatibility mode] that was [http://groups.google.com/d/topic/lastools/nUFMkKSz53g/discussion beta-released] in November 2014. This allowed support for the new point types in [http://laszip.org LASzip] without closing the door on a potential cooperation with ESRI for a joint LAS 1.4 compressor.

: '''November 2014: ESRI announces proprietary extension to LAS 1.4'''

: In November 2014 [http://blog.lidarnews.com/esri-las-optimizer-updated ESRI announced] that they had added their [http://blog.lidarnews.com/esri-las-optimizer-updated own extension] for the new LAS 1.4 point types to "Optimized LAS", dismissing the opportunity to develop a joint compressor and avoid format fragmentation by exploiting this "natural break" in the LAS format as Martin had suggested.

: Since then, ESRI has been [http://rapidlasso.com/2014/11/06/keeping-esri-honest/ promoting] "Optimized LAS". By including the term "LAS" in "Optimized LAS" and "zLAS", the distinction between the open LAS format and proprietary format is blurred. This is likely to mislead novice and future users, thereby endangering many years of standardization work. To date, [April 2014], the [http://www.asprs.org/a/society/committees/standards/LAS_1_4_r13.pdf custodians of the LAS format], the LAS Working Group (LWG) of the ASPRS has [http://rapidlasso.com/2015/02/22/lidar-las-asprs-esri-and-the-laz-clone/ yet to make an official statement] regarding use of the "LAS" name in promoting a proprietary LiDAR format.

=Value of Standards=

The importance of Open Standards is described in most government IT policies. For instance, the United Kingdom policy states:
: … Government assets should be interoperable and open for re-use in order to maximise return on investment, avoid technological or supplier lock-in, reduce operational risk in ICT projects and provide responsive services for citizens and business. This should also lower barriers to entry for more diverse sources of IT services, including citizens and SMEs. <ref>All about Open Source – An Introduction to Open Source Software for Government IT, Version 2.0, United Kingdom Cabinet Office https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/78959/All_About_Open_Source_v2_0.pdf</ref>

The value of Open Standards has been described in numerous national studies on the effects of standards on economic growth.

: ... the national studies demonstrate that standards have a positive influence on economic growth due to the resulting improved diffusion of knowledge. The contribution of standards to the growth rate in each country is equivalent to 0.9% in Germany, 0.8% in 0.3% in the UK and 0.2% in Canada. <ref>Prof. Dr. Knut Blind, Prof. Dr. Andre Jungmittag, Dr. Axel Mangelsdorf [http://www.din.de/sixcms_upload/media/2896/DIN_GNN_2011_engl_akt_neu.pdf "The Economic Benefits of Standardization"], ''DINN, 2000''. Retrieved March 2015.</ref>

=Further Reading=

# Paul Ramsey provides background to LAS vs Optimised LAS, http://boundlessgeo.com/2014/01/lidar-format-wars/
# Running commentary by Martin Isenburg, author of LASlib, http://rapidlasso.com/2015/02/22/lidar-las-asprs-esri-and-the-laz-clone/
# Earlier comment from Martin Isenburg, http://rapidlasso.com/2014/11/06/keeping-esri-honest/
# First call-to-action by Martin Isenburg, http://rapidlasso.com/2013/12/30/new-compressed-las-format-by-esri/
# ESRI Announces "Optimised LAS", http://blog.lidarnews.com/esri-announces-las-compression/
# ESRI description of "Optimised LAS", http://www.lidarnews.com/content/view/10214
# Discussion background on this topic at Geo for All list , http://lists.osgeo.org/pipermail/ica-osgeo-labs/2015-March/001225.html

=References=

<references />

FOSS4G-Europe 2015 Code Sprint

2015-04-15T04:50:37Z

Moovida:

= Organizing Contacts =

* Luca DELUCCHI (Fondazione Edmund Mach)
* Jachym CEPICKY (OpenGeoLabs s.r.o.)
* Simone CORTI (Politecnico di Milano)
* Jeff MCKENNA (Gateway Geomatics)
* Marco NEGRETTI (Politecnico di Milano)
* Stefano PIFFER (Trilogis)

= Code Sprint =

The code sprint represent an opportunity for the open source communities to get together, make future plans for their software projects, write code and documentation.

Projects can use the time and venue for organizational discussions, development roadmaps, and group resolution of thorny issues in their code bases.

= When and where =

The code sprint will be the 18th July 2015 in the [http://www.polo-como.polimi.it/en/campus-life/study-room/laps/ LAPS room] of Como Campus ([http://osm.org/go/0CkuOoy7~?layers=N Valleggio building, 1st floor]).
The room is booked from 8:00 to 18:00

= Workgroups =
To participate, start a section below for your project like this:

== Project Name ==

'''Attending:'''
* Add your self

'''Goals:'''
* Add your goal

== GRASS GIS ==

'''Attending:'''
* Markus Neteler
* Luca Delucchi
* [[User:Madi | Margherita Di Leo]]
* Anna Petrasova
* Vaclav Petras
* Martin Landa

'''Goals:'''
*

The GRASS GIS community sprint will be longer than one day, please join at http://grasswiki.osgeo.org/wiki/GRASS_Community_Sprint_Como_2015

== pycsw ==

'''Attending:'''
* [[User:kalxas | Angelos Tzotsos]]

'''Goals:'''
*

== QGIS ==

'''Attending:'''
* [[User:pcav | Paolo Cavallini]]

'''Goals:'''
* improving QGIS, work on QGIS 3.0

== Geopaparazzi ==

'''Attending:'''
* [[User:moovida | Andrea Antonello]]

'''Goals:'''
* OSM POI collection and upload to OSM accounts for version 4
* Creation of the Geopaparazzi 4 manual

= Individual preparation =
* Bring your own computer
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed ([http://en.wikipedia.org/wiki/File:L_plug.jpg Italy])

[[Category:FOSS4G]]
[[Category:Code Sprints]]
[[Category:FOSS4G-Europe]]

Google Summer of Code 2015 Ideas

2015-03-10T20:36:28Z

Moovida: Added zoo-project to list, since one project from JGrasstools has been moved to that project.

[[Image:GoogleSummer_2015logo.png|600px|link=http://code.google.com/soc/]] @ [[Image:OSGeo_300_127_pixel.png|link=http://www.osgeo.org]]

-----
* Back to the main OSGeo [[Google Summer of Code 2015]] wiki page.

* See also ideas from [[2007_SoC_Merged_Ideas|2007]], [[2008_SoC_Merged_Ideas|2008]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[Google Summer of Code 2010 Ideas|2010]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2012 Ideas|2012]], [[Google Summer of Code 2013 Ideas|2013]] and [[Google Summer of Code 2014 Ideas|2014]].
-----

== OSGeo Google Summer of Code 2015 ==

The [http://www.osgeo.org Open Source Geospatial Foundation] would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.

These ideas are '''*only*''' to motivate you, and serve as example of the kind of hills we want to charge up. Your own ideas are more than welcomed - they are encouraged. We view you as the next wave of open source leaders; show us what you've got.

* '''Students: check out the [[Google Summer of Code Recommendations for Students]] page. If you need more information on how to apply you can contact all the mentors via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])

* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.

* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.

* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google Summer of Code 2015]] wiki page.

== The ideas pages ==
'''''[Check back often, it's a work in progress]'''''

Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:

=== OSGeo Foundation member projects ===

* ''More coming soon: Get started talking to your favorite project's development team today!''

[[Image:logo-grass.png|60px|right]]
* [https://trac.osgeo.org/grass/wiki/GSoC/2015 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look!

[[Image:logo-qgis.png|60px|right]]
* [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2015 '''QGIS''' SoC Ideas]: [http://www.qgis.org QGIS] is a user friendly Open Source Geographic Information System (GIS) that runs on Linux, Unix, Mac OSX, and Windows. QGIS supports vector, raster, and database formats. It is written in C++ and Python.

[[Image:logo-gdal.png|60px|right]]
* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: [http://www.gdal.org GDAL] is a C++ library for reading and writing geospatial data raster and vector formats.



[[Image:logo-gvSIG.png|60px|right]]
* [[GvSIG_GSoC_2015_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.com/en/web/guest/products/gvsig-desktop Desktop]. The gvSIG project looks for students with Java or Python skills that want to develop new ideas on this software.

[[Image:logo-opticks.png|right]]
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: [http://opticks.org/ Opticks] is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.





[[Image:Logo_OTB.png|60px|right]]
* [http://wiki.orfeo-toolbox.org/index.php/Proposals_for_GSoC_2015 '''OTB''' SoC Ideas]: [http://www.orfeo-toolbox.org ORFEO ToolBox] (OTB) is an open source library for remote sensing image processing.Targeted algorithms for high resolution optical images (Pleiades, SPOT, QuickBird, WorldView, Landsat, Ikonos), hyperspectral sensors (Hyperion) or SAR (TerraSarX, ERS, Palsar) are available. The software has been under active development since 2006 and is written in C++ and it includes also side projects also open source with GUI like Monteverdi. OTB has recently started the incubation process into OSGeo.

[[Image:Mapserver.png|100px|right]]
* [http://wiki.osgeo.org/wiki/MapServer_2015_SOC_Ideas '''Mapserver''' SoC Ideas]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.

[[Image:Logo-istSOS.png|60px|right]]
* [http://sourceforge.net/p/istsos/wiki/GSoC%20ideas%202015/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] (Istituto Scienze della Terra Sensor Observation Service) is an implementation of the Sensor Observation Service (SOS) standard from the Open Geospatial Consortium (OGC). The development of istSOS was started in 2009 in order to provide a simple implementation of the SOS standard for the management, provision and integration of hydro-meteorological data collected in Canton Ticino (Switzerland). istSOS is entirely written in Python.



[[Image:logo-geoserver-crop.png|50px|right]]
* [https://github.com/geoserver/geoserver/wiki/GSOC-Ideas GSOC Ideas]: [http://live.osgeo.org/en/overview/geoserver_overview.html '''GeoServer'''] is a web server that allows you to serve maps and data from a variety of formats to standard clients such as web browsers and desktop GIS applications. GeoServer works with the Open Geospatial Consortium (OGC) standards Web Feature Service (WFS), Web Coverage Service (WCS), Web Processing Service (WPS) and Web Map Service (WMS) standards.
:* The GeoServer team asks applicants to introduce themselves on the geoserver-devel list ( Communicating in public is a key success factor to open source development )

[[Image:Geotools-logo.png|50px|right]]
* [http://docs.codehaus.org/display/GEOTOOLS/Google+Summer+of+Code ''GSOC'']: [http://live.osgeo.org/en/overview/geotools_overview.html '''GeoTools'''] GeoTools is an open source Java library for working with geospatial data, including both data access, data structures, processing and a powerful rendering engine. GeoTools is a modular library used in a wide range of web service, command line tools and desktop applications.





=== Guest projects ===

Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact [[User:Madi|Madi]] or Anne.

[[Image:Pgrouting-logo.png|60px|right]]
* [https://github.com/pgRouting/pgrouting/wiki/GSoC-Ideas '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.

[[Image:Pywps-logo.png|60px|right]]
* [https://github.com/jachym/pywps-4/wiki/GSOC-2015-ideas '''PyWPS''' Ideas]: [http://pywps.wald.intevation.org PyWPS] is server implementation of OGC WPS standard on server side using Python programming language. Currently, [http://github.com/jachym/pywps-4/ new version of PyWPS] is being done, were we would like to implement several new attractive features.

[[Image:logo-uDig.png|60px|right]]
* [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-Ideas-2015 '''JGrasstools''' and '''uDig''' Spatial Toolbox SoC Ideas]: The JGrasstools project is a geospatial modules library dedicated to hydrology and geomorphology. It is the base of the modules for uDig's Spatial Toolbox.

[[Image:zoo-logo.png|60px|right]]
* [http://zoo-project.org/trac/wiki/ZOO_SoC_Idea_2015 '''Zoo-Project''' Soc Ideas]: ZOO is a WPS (Web Processing Service) open source project released under MIT/X-11 style license. It provides an OGC WPS compliant developer-friendly framework to create and chain WPS Web services.

[[Image:otp-logo.png|80px|right]]
* [http://github.com/opentripplanner/OpenTripPlanner/wiki/2015-Google-Summer-of-Code-Ideas '''OpenTripPlanner''' Ideas]: [http://github.com/opentripplanner/OpenTripPlanner OpenTripPlanner] is an open source multi-modal trip planner. It depends on open data in open standard file formats (GTFS and OpenStreetMap), includes a REST API for journey planning, a map-based Javascript client, and an [http://github.com/CUTR-at-USF/OpenTripPlanner-for-Android/wiki Android App].









=== See also ===

Other like minded projects do not participate to GSoC under OSGeo umbrella, but with their own organization. You may want to visit also their page:

* [https://wiki.52north.org/bin/view/Projects/GSoC2015ProjectIdeas '''52°North''' Ideas]


* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2015/Project_Ideas '''OpenStreetMap''' Ideas]



=== Don't see in the list the project you're interested in? ===

Contact them in their developers mailing list! Feel free to propose your own idea and get feedback!

== I want to apply as a student ==

Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.

=== Which project do I choose? ===

Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.
: View the documents and download the ISO from http://live.osgeo.org
[[File:Osgeolive wordle.png|400px|center]]

=== Important dates ===

* [http://www.google-melange.com/gsoc/events/google/gsoc2015 '''The official timeline''']


* March 2nd: Google announces accepted organizations.
: Please start talking to the dev communities you are interested in ''now''.
* March 16: Student applications open.
: The earlier you start the more probable it is that you will be accepted!
: ''There is two way feedback during the application process which really helps you improve and clarify your application before the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''
* March 27: Student application deadline.
* April 27: '''Accepted student proposals are announced and Community Bonding Period begins.'''
* May 25: '''Coding begins!'''
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')
* June 26: Mid-term evaluation begins
* August 17-21: '''Pencils down!'''
* August 28: Final evaluations
* August 28: Students begin submitting required code samples to Google
* August 31: Final results announced

[Back to [[Google Summer of Code 2015]] @ OSGeo]
[[Category: Google Summer of Code]]

File:Zoo-logo.png

2015-03-10T20:34:18Z

Moovida: the zoo-project logo

the zoo-project logo

Google Summer of Code 2015 Ideas

2015-03-10T20:29:51Z

Moovida: /* Guest projects */

[[Image:GoogleSummer_2015logo.png|600px|link=http://code.google.com/soc/]] @ [[Image:OSGeo_300_127_pixel.png|link=http://www.osgeo.org]]

-----
* Back to the main OSGeo [[Google Summer of Code 2015]] wiki page.

* See also ideas from [[2007_SoC_Merged_Ideas|2007]], [[2008_SoC_Merged_Ideas|2008]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[Google Summer of Code 2010 Ideas|2010]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2012 Ideas|2012]], [[Google Summer of Code 2013 Ideas|2013]] and [[Google Summer of Code 2014 Ideas|2014]].
-----

== OSGeo Google Summer of Code 2015 ==

The [http://www.osgeo.org Open Source Geospatial Foundation] would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.

These ideas are '''*only*''' to motivate you, and serve as example of the kind of hills we want to charge up. Your own ideas are more than welcomed - they are encouraged. We view you as the next wave of open source leaders; show us what you've got.

* '''Students: check out the [[Google Summer of Code Recommendations for Students]] page. If you need more information on how to apply you can contact all the mentors via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])

* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.

* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.

* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google Summer of Code 2015]] wiki page.

== The ideas pages ==
'''''[Check back often, it's a work in progress]'''''

Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:

=== OSGeo Foundation member projects ===

* ''More coming soon: Get started talking to your favorite project's development team today!''

[[Image:logo-grass.png|60px|right]]
* [https://trac.osgeo.org/grass/wiki/GSoC/2015 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look!

[[Image:logo-qgis.png|60px|right]]
* [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2015 '''QGIS''' SoC Ideas]: [http://www.qgis.org QGIS] is a user friendly Open Source Geographic Information System (GIS) that runs on Linux, Unix, Mac OSX, and Windows. QGIS supports vector, raster, and database formats. It is written in C++ and Python.

[[Image:logo-gdal.png|60px|right]]
* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: [http://www.gdal.org GDAL] is a C++ library for reading and writing geospatial data raster and vector formats.



[[Image:logo-gvSIG.png|60px|right]]
* [[GvSIG_GSoC_2015_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.com/en/web/guest/products/gvsig-desktop Desktop]. The gvSIG project looks for students with Java or Python skills that want to develop new ideas on this software.

[[Image:logo-opticks.png|right]]
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: [http://opticks.org/ Opticks] is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.





[[Image:Logo_OTB.png|60px|right]]
* [http://wiki.orfeo-toolbox.org/index.php/Proposals_for_GSoC_2015 '''OTB''' SoC Ideas]: [http://www.orfeo-toolbox.org ORFEO ToolBox] (OTB) is an open source library for remote sensing image processing.Targeted algorithms for high resolution optical images (Pleiades, SPOT, QuickBird, WorldView, Landsat, Ikonos), hyperspectral sensors (Hyperion) or SAR (TerraSarX, ERS, Palsar) are available. The software has been under active development since 2006 and is written in C++ and it includes also side projects also open source with GUI like Monteverdi. OTB has recently started the incubation process into OSGeo.

[[Image:Mapserver.png|100px|right]]
* [http://wiki.osgeo.org/wiki/MapServer_2015_SOC_Ideas '''Mapserver''' SoC Ideas]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.

[[Image:Logo-istSOS.png|60px|right]]
* [http://sourceforge.net/p/istsos/wiki/GSoC%20ideas%202015/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] (Istituto Scienze della Terra Sensor Observation Service) is an implementation of the Sensor Observation Service (SOS) standard from the Open Geospatial Consortium (OGC). The development of istSOS was started in 2009 in order to provide a simple implementation of the SOS standard for the management, provision and integration of hydro-meteorological data collected in Canton Ticino (Switzerland). istSOS is entirely written in Python.



[[Image:logo-geoserver-crop.png|50px|right]]
* [https://github.com/geoserver/geoserver/wiki/GSOC-Ideas GSOC Ideas]: [http://live.osgeo.org/en/overview/geoserver_overview.html '''GeoServer'''] is a web server that allows you to serve maps and data from a variety of formats to standard clients such as web browsers and desktop GIS applications. GeoServer works with the Open Geospatial Consortium (OGC) standards Web Feature Service (WFS), Web Coverage Service (WCS), Web Processing Service (WPS) and Web Map Service (WMS) standards.
:* The GeoServer team asks applicants to introduce themselves on the geoserver-devel list ( Communicating in public is a key success factor to open source development )

[[Image:Geotools-logo.png|50px|right]]
* [http://docs.codehaus.org/display/GEOTOOLS/Google+Summer+of+Code ''GSOC'']: [http://live.osgeo.org/en/overview/geotools_overview.html '''GeoTools'''] GeoTools is an open source Java library for working with geospatial data, including both data access, data structures, processing and a powerful rendering engine. GeoTools is a modular library used in a wide range of web service, command line tools and desktop applications.





=== Guest projects ===

Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact [[User:Madi|Madi]] or Anne.

[[Image:Pgrouting-logo.png|60px|right]]
* [https://github.com/pgRouting/pgrouting/wiki/GSoC-Ideas '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.

[[Image:Pywps-logo.png|60px|right]]
* [https://github.com/jachym/pywps-4/wiki/GSOC-2015-ideas '''PyWPS''' Ideas]: [http://pywps.wald.intevation.org PyWPS] is server implementation of OGC WPS standard on server side using Python programming language. Currently, [http://github.com/jachym/pywps-4/ new version of PyWPS] is being done, were we would like to implement several new attractive features.

[[Image:logo-uDig.png|60px|right]]
* [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-Ideas-2015 '''JGrasstools''' and '''uDig''' Spatial Toolbox SoC Ideas]: The JGrasstools project is a geospatial modules library dedicated to hydrology and geomorphology. It is the base of the modules for uDig's Spatial Toolbox.

[[[]]]
* [http://zoo-project.org/trac/wiki/ZOO_SoC_Idea_2015 '''Zoo-Project''' Soc Ideas]: ZOO is a WPS (Web Processing Service) open source project released under MIT/X-11 style license. It provides an OGC WPS compliant developer-friendly framework to create and chain WPS Web services.

[[Image:otp-logo.png|80px|right]]
* [http://github.com/opentripplanner/OpenTripPlanner/wiki/2015-Google-Summer-of-Code-Ideas '''OpenTripPlanner''' Ideas]: [http://github.com/opentripplanner/OpenTripPlanner OpenTripPlanner] is an open source multi-modal trip planner. It depends on open data in open standard file formats (GTFS and OpenStreetMap), includes a REST API for journey planning, a map-based Javascript client, and an [http://github.com/CUTR-at-USF/OpenTripPlanner-for-Android/wiki Android App].









=== See also ===

Other like minded projects do not participate to GSoC under OSGeo umbrella, but with their own organization. You may want to visit also their page:

* [https://wiki.52north.org/bin/view/Projects/GSoC2015ProjectIdeas '''52°North''' Ideas]


* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2015/Project_Ideas '''OpenStreetMap''' Ideas]



=== Don't see in the list the project you're interested in? ===

Contact them in their developers mailing list! Feel free to propose your own idea and get feedback!

== I want to apply as a student ==

Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.

=== Which project do I choose? ===

Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.
: View the documents and download the ISO from http://live.osgeo.org
[[File:Osgeolive wordle.png|400px|center]]

=== Important dates ===

* [http://www.google-melange.com/gsoc/events/google/gsoc2015 '''The official timeline''']


* March 2nd: Google announces accepted organizations.
: Please start talking to the dev communities you are interested in ''now''.
* March 16: Student applications open.
: The earlier you start the more probable it is that you will be accepted!
: ''There is two way feedback during the application process which really helps you improve and clarify your application before the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''
* March 27: Student application deadline.
* April 27: '''Accepted student proposals are announced and Community Bonding Period begins.'''
* May 25: '''Coding begins!'''
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')
* June 26: Mid-term evaluation begins
* August 17-21: '''Pencils down!'''
* August 28: Final evaluations
* August 28: Students begin submitting required code samples to Google
* August 31: Final results announced

[Back to [[Google Summer of Code 2015]] @ OSGeo]
[[Category: Google Summer of Code]]

Google Summer of Code 2015 Ideas

2015-02-19T11:29:53Z

Moovida: /* Guest projects */

[[Image:GoogleSummer_2015logo.png|600px|link=http://code.google.com/soc/]] @ [[Image:OSGeo_300_127_pixel.png|link=http://www.osgeo.org]]

-----
* Back to the main OSGeo [[Google Summer of Code 2015]] wiki page.

* See also ideas from [[2007_SoC_Merged_Ideas|2007]], [[2008_SoC_Merged_Ideas|2008]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[Google Summer of Code 2010 Ideas|2010]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2012 Ideas|2012]], [[Google Summer of Code 2013 Ideas|2013]] and [[Google Summer of Code 2014 Ideas|2014]].
-----

== OSGeo Google Summer of Code 2015 ==

The [http://www.osgeo.org Open Source Geospatial Foundation] would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.

These ideas are '''*only*''' to motivate you, and serve as example of the kind of hills we want to charge up. Your own ideas are more than welcomed - they are encouraged. We view you as the next wave of open source leaders; show us what you've got.

* '''Students: If you need more information on how to apply you can contact all the mentoring organisations via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])

* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.

* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.

* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google Summer of Code 2015]] wiki page.

== Important dates ==

* [http://www.google-melange.com/gsoc/events/google/gsoc2015 '''The official timeline''']


* March 2nd: Google announces accepted organizations.
: Please start talking to the dev communities you are interested in ''now''.
* March 16: Student applications open.
: The earlier you start the more probable it is that you will be accepted!
: ''There is two way feedback during the application process which really helps you improve and clarify your application before the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''
* March 27: Student application deadline.
* April 27: '''Accepted student proposals are announced and Community Bonding Period begins.'''
* May 25: '''Coding begins!'''
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')
* June 26: Mid-term evaluation begins
* August 17-21: '''Pencils down!'''
* August 28: Final evaluations
* August 28: Students begin submitting required code samples to Google
* August 31: Final results announced

== The ideas pages ==
'''''[Check back often, it's a work in progress]'''''

Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:

=== OSGeo Foundation member projects ===

* ''More coming soon: Get started talking to your favorite project's development team today!''

[[Image:logo-grass.png|60px|right]]
* [https://trac.osgeo.org/grass/wiki/GSoC/2015 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look!

[[Image:logo-qgis.png|60px|right]]
* [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2015 '''QGIS''' SoC Ideas]: [http://www.qgis.org QGIS] is a user friendly Open Source Geographic Information System (GIS) that runs on Linux, Unix, Mac OSX, and Windows. QGIS supports vector, raster, and database formats. It is written in C++ and Python.

[[Image:logo-gdal.png|60px|right]]
* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: [http://www.gdal.org GDAL] is a C++ library for reading and writing geospatial data raster and vector formats.



[[Image:logo-gvSIG.png|60px|right]]
* [[GvSIG_GSoC_2015_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.com/en/web/guest/products/gvsig-desktop Desktop]. The gvSIG project looks for students with Java or Python skills that want to develop new ideas on this software.

[[Image:logo-opticks.png|right]]
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: [http://opticks.org/ Opticks] is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.






[[Image:Mapserver.png|100px|right]]
* [http://wiki.osgeo.org/wiki/MapServer_2015_SOC_Ideas '''Mapserver''' SoC Ideas]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.

[[Image:Logo-istSOS.png|60px|right]]
* [http://sourceforge.net/p/istsos/wiki/GSoC%20ideas%202015/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] (Istituto Scienze della Terra Sensor Observation Service) is an implementation of the Sensor Observation Service (SOS) standard from the Open Geospatial Consortium (OGC). The development of istSOS was started in 2009 in order to provide a simple implementation of the SOS standard for the management, provision and integration of hydro-meteorological data collected in Canton Ticino (Switzerland). istSOS is entirely written in Python.









=== Guest projects ===

Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact Hamish, Anne and Dustan.

[[Image:Logo-osm6.png|60px|right]]
* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2015/Project_Ideas '''OpenStreetMap''' Ideas]: [http://osm.org/ OSM] is a project aimed squarely at creating and providing free geographic data such as street maps to anyone who wants them. The project was started because most maps you think of as free actually have legal or technical restrictions on their use, holding back people from using them in creative, productive or unexpected ways.
:* ''This year OpenStreetMap students will again be hosted under OSGeo's GSoC umbrella. Talk to OSM, but apply with us. Begin your proposal description with "OSM: " so we know which way to direct it.''
Related ideas:
* [https://github.com/hotosm/HOT-Project-Ideas/issues/15 Create a Portable OSM Toolkit]

[[Image:Pgrouting-logo.png|60px|right]]
* [https://github.com/pgRouting/pgrouting/wiki/GSoC-Ideas '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.

[[Image:Pywps-logo.png|60px|right]]
* [https://github.com/jachym/pywps-4/wiki/GSOC-2015-ideas '''PyWPS''' Ideas]: [http://pywps.wald.intevation.org PyWPS] is server implementation of OGC WPS standard on server side using Python programming language. Currently, [http://github.com/jachym/pywps-4/ new version of PyWPS] is being done, were we would like to implement several new attractive features.

[[Image:logo-uDig.png|60px|right]]
* [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-Ideas-2015 '''JGrasstools''' and '''uDig''' Spatial Toolbox SoC Ideas]: The JGrasstools project is a geospatial modules library dedicated to hydrology and geomorphology. It is the base of the modules for uDig's Spatial Toolbox.















== Which project do I choose? ==

Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.
: View the documents and download the ISO from http://live.osgeo.org
[[File:Osgeolive wordle.png|400px|center]]

== How to get in contact via mailing lists ==

Since OSGeo is an umbrella organisation for multiple projects, each project has their own discussion and development mailing lists.

'''Main OSGeo mailing lists of interest to students:'''
: Please start here, when contacting us for the first time with questions about Google Summer of Code.

:* OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc)
:* OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)

Also see the [[Mailing Lists]] page for project specific lists, as well as the longer list at http://lists.osgeo.org.

== How to get in contact via IRC ==

Primary channel:

* irc://irc.freenode.net/#osgeo (Web based [http://irc.telascience.org/cgi-bin/irc.cgi IRC client], [http://webchat.freenode.net alternative])

GSoC @ OSGeo inter-project discussions:

* irc://irc.freenode.net/#osgeo-soc

Project irc channels:

* irc://irc.freenode.net/#gdal
* irc://irc.freenode.net/#geoserver
* irc://irc.freenode.net/#geotools
* irc://irc.freenode.net/#grass
* irc://irc.freenode.net/#gvsig
* irc://irc.freenode.net/#mapguide
* irc://irc.freenode.net/#mapnik
* irc://irc.freenode.net/#mapserver
* irc://irc.freenode.net/#openlayers
* irc://irc.freenode.net/#opticks
* irc://irc.freenode.net/#osgeolive
* irc://irc.freenode.net/#ossimplanet
* irc://irc.freenode.net/#pgrouting-project
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#qgis
* irc://irc.freenode.net/#udig
* irc://irc.oftc.net/#osm-dev
* irc://irc.freenode.net/#geonode

== Application questions we'll ask you ==

* All questions must be answered, ''no exceptions''. Treat this as something between a formal job application and a scholarship application, because that's exactly what it is.

Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

Title:
(please include the name of the member project as part of
the title, for example: "Gee Whiz Foobar 2001 for QGIS")

Describe your idea
1. Introduction
2. Background
3. The idea
4. Project plan ('''detailed timeline''': how do you plan to spend your summer?)
5. Future ideas / How can your idea be expanded?

Explain how your SoC task would benefit the OSGeo member
project and more generally the OSGeo Foundation as a whole:

Please provide details of general computing experience:
(operating systems you use on a day-to-day basis, languages you
could write a program in, hardware, networking experience, etc.)

Please provide details of previous GIS experience:

Please provide details of any previous involvement with
GIS programming and other software programming:

Please tell us why you are interested in GIS and open
source software:

Please tell us why you are interested in working for OSGeo
and the software project you have selected:

Please tell us why you are interested in your specific
coding project:

Would your application contribute to your ongoing studies/
degree? If so, how?

Please explain how you intend to continue being an active
member of your project and/or OSGeo AFTER the summer is over:

Do you understand this is a serious commitment, equivalent
to a full-time paid summer internship or summer job?

Do you have any known time conflicts during the official coding
period? (May 19 to August 18)

== What to expect during the summer ==

* A group of past GSoC students, mentors, and Googlers have prepared this short book just for you:
: [https://flossmanuals.net/GSoCStudentGuide/ The Student's Guide to the Summer of Code]

=== Be prepared to be in constant communication with your mentors and project ===

You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to integrate you into the developer community, so you should get involved with them from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you in case of problems, like making sure you get paid.

University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.

=== Weekly reports ===

Yes, every week we expect to see a report posted to the soc@osgeo mailing list that at least answers the following questions:

# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?

These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process]. ;)

If you want, feel free to write *more*. But three sentences is the bare minimum. *IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME*, if you don't send this email your mentors will start to get twitchy, and *especially* if they don't get any responses to their emails / don't see you in IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's cool. We have all studied at some point, just tell us about it up front, be honest, and we'll work around it. If you don't know how to proceed and your mentor isn't answering *definitely* tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)

During past years this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.

=== Code repository and documentation ===

Publishing your progress online is a GSoC requirement. Therefore, all students have to decide, before GSoC coding period starts, where to publish the code they will write. We ask students to give the link to the public repository in the first weekly report.

The possibilities are:
* get a sandbox in your software project's repository (your mentor will tell you how to get write access)
* work on a branch of the main code repository (for centralized versioning systems like SVN)
* work on a fork of the code repository (for DCVS like Mercurial and Git)
* work on an independent codebase (if you are developing a plugin or some other extra functionality that is not yet part of main codebase)

Your mentor is the best guide regarding this choice. Please discuss it as soon as possible, and learn how to use the related version control tool well before GSoC coding starts.

Documentation of your code is important! Don't leave all documentation writing to the last weeks of GSoC. It makes sense to outline it at the beginning of coding period, then refine it while you code. It is an important support to coding, as it is a mirror of the overall plan for the summer, and an essential source of information for who will use your code.

=== Wiki page and blogs ===

In addition to weekly reports we require you to maintain a wiki or blog page for your project. You should store your weekly reports there and add other information, like how to compile and test your program. If applicable add screenshots and other nice info.

Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this.

We plan to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.

Final reports from those blogs and wiki pages will be collected into a OSGeoofcode posting about what everyone did during the summer, ensuring you long lasting fame and fortune. (''Or failing that, a bit of public press, a bit of cash from Google, and a lot of gratitude and kudos from us, your peers.'')

[Back to [[Google Summer of Code 2015]] @ OSGeo]
[[Category: Google Summer of Code]]

Google Summer of Code 2014 Ideas

2014-02-13T09:58:04Z

Moovida: /* Guest projects */

[[Image:GoogleSummer_2014logo.jpg|300px|link=http://code.google.com/soc/]] @ [[Image:OSGeo_300_127_pixel.png|link=http://www.osgeo.org]]

-----
* Back to the main OSGeo [[Google Summer of Code 2014]] wiki page.

* See also ideas from [[2007_SoC_Merged_Ideas|2007]], [[2008_SoC_Merged_Ideas|2008]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[Google Summer of Code 2010 Ideas|2010]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2012 Ideas|2012]], and [[Google Summer of Code 2013 Ideas|2013]].
-----

== OSGeo Google Summer of Code 2014 ==

The [http://www.osgeo.org Open Source Geospatial Foundation] would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.

These ideas are '''*only*''' to motivate you, and serve as example of the kind of hills we want to charge up. Your own ideas are more than welcomed - they are encouraged. We view you as the next wave of open source leaders; show us what you've got.

* '''If you need more information on how to apply you can contact all the mentoring organisations via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])

* There is a [http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers Google SoC flyer] to look at and post in appropriate places and [http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2013.pdf an OSGeo flavoured one as well].

* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.

== Important dates ==

* [http://www.google-melange.com/gsoc/events/google/gsoc2014 '''The official timeline''']


* February 24: Google announces accepted organizations.
: If OSGeo is accepted as an organization for Google Summer of Code, '''start talking to us earlier rather than later.'''

* March 10: Student applications open.
: The earlier you start the more probable it is that you will be accepted!
: ''There is two way feedback during the application process which really helps you improve and clarify your application before the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''
* March 21: Student application deadline.
* April 21: '''Accepted student proposals are announced and Community Bonding Period begins.'''
* May 19: '''Coding begins!'''
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')
* June 23: Mid-term evaluation begins
* August 11-18: '''Pencils down!'''
* August 18-22: Final evaluations
* August 22: Students begin submitting required code samples to Google
* August 25: Final results announced

== The ideas pages ==
'''''[Check back often, it's a work in progress]'''''

Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:

=== OSGeo Foundation member projects ===

* ''More coming soon: Get started talking to your favorite project's development team today!''

[[Image:logo-grass.png|60px|right]]
* [https://trac.osgeo.org/grass/wiki/GSoC/2014 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look!

[[Image:logo-qgis.png|60px|right]]
* [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2014 '''QGIS''' SoC Ideas]: [http://www.qgis.org QGIS] is a user friendly Open Source Geographic Information System (GIS) that runs on Linux, Unix, Mac OSX, and Windows. QGIS supports vector, raster, and database formats. It is written in C++ and Python.

[[Image:logo-gdal.png|60px|right]]

* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: [http://www.gdal.org GDAL] is a C++ library for reading and writing geospatial data raster and vector formats.

 
[[Image:logo-gvSIG.png|60px|right]]
* [[GvSIG_GSoC_2014_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.org/web/projects/gvsig-desktop/description2/view?set_language=en Desktop], [http://www.gvsig.org/web/projects/gvsig-mobile/description-2/view?set_language=en PDAs], and [http://gvsigmini.org mobile phones]. The gvSIG project looks for students with Java skills that want to develop new ideas on any of these products.
  



  

=== Guest projects ===

[[Image:Logo-osm6.png|60px|right]]
* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2014/Project_Ideas '''OpenStreetMap''' Ideas]: [http://osm.org/ OSM] is a project aimed squarely at creating and providing free geographic data such as street maps to anyone who wants them. The project was started because most maps you think of as free actually have legal or technical restrictions on their use, holding back people from using them in creative, productive or unexpected ways.
:* ''This year OpenStreetMap students will again be hosted under OSGeo's GSoC umbrella. Talk to OSM, but apply with us. Begin your proposal description with "OSM: " so we know which way to direct it.''

[[Image:Pgrouting-logo.png|60px|right]]

* [https://github.com/pgrouting/pgrouting/wiki/GSOC-Ideas '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.

[[Image:Pywps-logo.png|60px|right]]

* [https://github.com/jachym/pywps-4/wiki/GSOC-2014-ideas '''PyWPS''' Ideas]: [http://pywps.wald.intevation.org PyWPS] is server implementation of OGC WPS standard on server side using Python programming language. Currently, [http://github.com/jachym/pywps-4/ new version of PyWPS] is being done, were we would like to implement several new attractive features.

* [https://sourceforge.net/p/istsos/wiki/GSoC_ideas_2014/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] [[Image:Logo-istSOS.png|100px|right]] (Istituto Scienze della Terra Sensor Observation Service) is an implementation of the Sensor Observation Service (SOS) standard from the Open Geospatial Consortium (OGC). The development of istSOS was started in 2009 in order to provide a simple implementation of the SOS standard for the management, provision and integration of hydro-meteorological data collected in Canton Ticino (Switzerland). istSOS is entirely written in Python.

[[Image:logo-uDig.png|60px|right]]
* [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-Ideas-2014 '''JGrasstools''' and '''uDig''' SoC Ideas]: User-friendly Desktop GIS is a Java application written with the Eclipse RCP framework. The project has a community svn area to host student plug-ins, tutorials cover how to package up a custom application to show off your work.

* '''FIXME''': move to a member project's idea page:
: ''[http://sites.google.com/site/foss4gku/projects/gsoc-feature-based-map-algebra '''Feature-based Map Algebra''' SoC Ideas] Map algebra (or cartographic modeling) operations provide powerful tools for analyzing and manipulating geographic data in the raster data model both in commercial and open source GIS software. This project extends these operations to the vector data model and makes them available in PostGIS and QGIS. It will be implemented primarily using the Python programming language.''



== Which project do I choose? ==

Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.
: View the documents and download the ISO from http://live.osgeo.org
[[File:Osgeolive wordle.png|400px|center]]

== How to get in contact via mailing lists ==

Since OSGeo is an umbrella organisation for multiple projects, each project has their own discussion and development mailing lists.

'''Main OSGeo mailing lists of interest to students:'''
: Please start here, when contacting us for the first time with questions about Google Summer of Code.

:* OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc)
:* OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)

Also see the [[Mailing Lists]] page for project specific lists, as well as the longer list at http://lists.osgeo.org.

== How to get in contact via IRC ==

Primary channel:

* irc://irc.freenode.net/#osgeo (Web based [http://irc.telascience.org/cgi-bin/irc.cgi IRC client], [http://webchat.freenode.net alternative])

GSoC @ OSGeo inter-project discussions:

* irc://irc.freenode.net/#osgeo-soc

Project irc channels:

* irc://irc.freenode.net/#gdal
* irc://irc.freenode.net/#geoserver
* irc://irc.freenode.net/#geotools
* irc://irc.freenode.net/#grass
* irc://irc.freenode.net/#gvsig
* irc://irc.freenode.net/#mapguide
* irc://irc.freenode.net/#mapnik
* irc://irc.freenode.net/#mapserver
* irc://irc.freenode.net/#openlayers
* irc://irc.freenode.net/#opticks
* irc://irc.freenode.net/#osgeolive
* irc://irc.freenode.net/#ossimplanet
* irc://irc.freenode.net/#pgrouting-project
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#qgis
* irc://irc.freenode.net/#udig
* irc://irc.oftc.net/#osm-dev

== Application questions we'll ask you ==
'''''[Provisional]'''''

* All questions must be answered, ''no exceptions''. Treat this as something between a formal job application and a scholarship application, because that's exactly what it is.

Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

Title:
(please include the name of the member project as part of
the title, for example: "Gee Whiz Foobar 2001 for QGIS")

Describe your idea
1. Introduction
2. Background
3. The idea
4. Project plan ('''detailed timeline''': how do you plan to spend your summer?)
5. Future ideas / How can your idea be expanded?

Explain how your SoC task would benefit the OSGeo member
project and more generally the OSGeo Foundation as a whole:

Please provide details of general computing experience:
(operating systems you use on a day-to-day basis, languages you
could write a program in, hardware, networking experience, etc.)

Please provide details of previous GIS experience:

Please provide details of any previous involvement with
GIS programming and other software programming:

Please tell us why you are interested in GIS and open
source software:

Please tell us why you are interested in working for OSGeo
and the software project you have selected:

Please tell us why you are interested in your specific
coding project:

Would your application contribute to your ongoing studies/
degree? If so, how?

Please explain how you intend to continue being an active
member of your project and/or OSGeo AFTER the summer is over:

Do you understand this is a serious commitment, equivalent
to a full-time paid summer internship or summer job?

Do you have any known time conflicts during the official coding
period? (May 19 to August 18)

== What to expect during the summer ==

* A group of past GSoC students, mentors, and Googlers have prepared this short book just for you:
: [http://google-opensource.blogspot.com/2011/02/flip-bits-not-burgers-student-guide.html Flip bits not Burgers: The Student's Guide to the Summer of Code] -- READ THIS eBOOK

=== Be prepared to be in constant communication with your mentors and project ===

You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to integrate you into the developer community, so you should get involved with them from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you in case of problems, like making sure you get paid.

University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.

=== Weekly reports ===

Yes, every week we expect to see a report posted to the soc@osgeo mailing list that at least answers the following questions:

# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?

These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process]. ;)

If you want, feel free to write *more*. But three sentences is the bare minimum. *IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME*, if you don't send this email your mentors will start to get twitchy, and *especially* if they don't get any responses to their emails / don't see you in IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's cool. We have all studied at some point, just tell us about it up front, be honest, and we'll work around it. If you don't know how to proceed and your mentor isn't answering *definitely* tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)

Last year this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.

=== Wiki page and blogs ===

In addition to weekly reports we require you to maintain a wiki or blog page for your project. You should store your weekly reports there and add other information, like how to compile and test your program. If applicable add screenshots and other nice info.

Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this.

We plan to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.

Final reports from those blogs and wiki pages will be collected into a OSGeoofcode posting about what everyone did during the summer, ensuring you long lasting fame and fortune. (''Or failing that, a bit of public press, a bit of cash from Google, and a lot of gratitude and kudos from us, your peers.'')

[Back to [[Google Summer of Code 2014]] @ OSGeo]
[[Category: Google Summer of Code]]

2009-10-13T07:35:43Z

Moovida: /* Geometry */

FOSS4G 2009 Code Sprint

2009-10-10T14:49:41Z

Moovida: /* uDig & friends */

FOSS4G 2009 Code Sprint

2009-10-10T14:49:04Z

Moovida: /* uDig & friends */