2016-11-03T00:32:06Z

Wiki-Dmorissette: /* Accommodations */

''NOTE: the sprint location is unconfirmed''

=== Gold Sponsors ===

=== Silver Sponsors ===

=== Bronze Sponsors ===

=== Venue Sponsor ===

=== Other/in-kind sponsors ===

{| border=0 cellspacing=15 cellpadding=10
|
[[File:OSGeo_logo.png|260px|OSGeo|link=http://www.osgeo.org/]]
 
http://www.osgeo.org/
|}

== Purpose ==

Bring together project members to make decisions and tackle larger geospatial
problems as in previous years:

* [[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)

== Other Events from January to March 2017 ==

* FOSS4G Asia January 26-29
* '''OSGeo's 11th birthday Feb 4'''
* FOSDEM Feb 4-5
* OGC Technical meeting March 7-11

== Dates and Times ==

'''Two date options are being considered, either the week of Feb 7 to 11, or Feb 28 to March 4, 2017.
Please case your votes via http://doodle.com/poll/vyyew4ibbwcdp6ka'''

Dates:
* Welcome event: TBD
* Sprint: TBD

== Location ==
* Potentially on campus of Dayton State College (https://www.openstreetmap.org/#map=15/29.1953/-81.0537)
* Located 5 minutes from Daytona International Airport (DAB)

== Accommodations ==

A room block will be available at the Marriott Residence Inn:
* walking distance from the college (right across the street)
* 114$USD + taxes per night with 2 beds in each room
* rate includes breakfast for up to two persons
* ''room block reservation details will follow once the code sprint date is confirmed.''

== Schedule ==

=== [insert date] Welcoming Event ===

=== [insert date] First Sprint Evening ===

=== [insert date] Second Sprint Evening ===

=== [insert date] Third Sprint Evening ===

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

*
== Social ideas ==

If you need to take a break, some ideas close to the sprint place:

== 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.

{| style="border: solid grey 1px; width:100%" class="sortable"
|+ Participants
|-
| # || Participant || Country || Organization || Arrival || Departure || Project Work on || Attendance / Notes
|-
|1|| name || country code || org || date || date || project name || Confirmed, tentative, etc

|}

== 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 Daytona Beach
* Accommodation for four nights (including breakfast)

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

== Financial ==

'''Detailled budget'''
* [[Daytona_Beach_Code_Sprint_2017_:_Budget|Budget]]

== Individual preparation ==

* Bring your own laptop
* Install GIT and compiler tools, and come with a working development environment
* If your laptop need it, video export adapter to DVI and/or VGA
* Optional: something to take pictures (camera, smartphone, small tablet...)

== Sponsors ==

We have three sponsorship levels:

* Gold: >= 2500 USD
* Silver: 1500 USD
* Bronze: 750 USD

We encourage sponsors to support nutriment and entertainment for the
sprinters as they work hard and play hard for four or five productive days.
Contributions will be put towards lunch, snacks, and dinner costs for the
sprinters, and potentially bringing in sprinters who might otherwise be unable
to attend. Any surplus at the end of the event will be turned over to OSGeo or
used for a future code sprint.

Sponsors will receive the following:

* Your logo at the top of this page
* Mention in all of our public communication
* Our undying gratitude, which comes in handy when you least expect it (Remember that feature you wanted...)
* And as extra, for Silver and Gold: Kakemono in the event room (if you provide it)

To sponsor, please contact xxx directly.

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

Daytona Beach Code Sprint 2017

2016-11-03T00:31:28Z

Wiki-Dmorissette:

''NOTE: the sprint location is unconfirmed''

=== Gold Sponsors ===

=== Silver Sponsors ===

=== Bronze Sponsors ===

=== Venue Sponsor ===

=== Other/in-kind sponsors ===

{| border=0 cellspacing=15 cellpadding=10
|
[[File:OSGeo_logo.png|260px|OSGeo|link=http://www.osgeo.org/]]
 
http://www.osgeo.org/
|}

== Purpose ==

Bring together project members to make decisions and tackle larger geospatial
problems as in previous years:

* [[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)

== Other Events from January to March 2017 ==

* FOSS4G Asia January 26-29
* '''OSGeo's 11th birthday Feb 4'''
* FOSDEM Feb 4-5
* OGC Technical meeting March 7-11

== Dates and Times ==

'''Two date options are being considered, either the week of Feb 7 to 11, or Feb 28 to March 4, 2017.
Please case your votes via http://doodle.com/poll/vyyew4ibbwcdp6ka'''

Dates:
* Welcome event: TBD
* Sprint: TBD

== Location ==
* Potentially on campus of Dayton State College (https://www.openstreetmap.org/#map=15/29.1953/-81.0537)
* Located 5 minutes from Daytona International Airport (DAB)

== Accommodations ==

A room block will be available at the Marriott Residence Inn:
* 114$USD + taxes per night with 2 beds in each room
* rate includes breakfast for up to two persons
* walking distance from the college (right across the street)
* ''room block reservation details will follow once the code sprint date is confirmed.''

== Schedule ==

=== [insert date] Welcoming Event ===

=== [insert date] First Sprint Evening ===

=== [insert date] Second Sprint Evening ===

=== [insert date] Third Sprint Evening ===

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

*
== Social ideas ==

If you need to take a break, some ideas close to the sprint place:

== 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.

{| style="border: solid grey 1px; width:100%" class="sortable"
|+ Participants
|-
| # || Participant || Country || Organization || Arrival || Departure || Project Work on || Attendance / Notes
|-
|1|| name || country code || org || date || date || project name || Confirmed, tentative, etc

|}

== 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 Daytona Beach
* Accommodation for four nights (including breakfast)

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

== Financial ==

'''Detailled budget'''
* [[Daytona_Beach_Code_Sprint_2017_:_Budget|Budget]]

== Individual preparation ==

* Bring your own laptop
* Install GIT and compiler tools, and come with a working development environment
* If your laptop need it, video export adapter to DVI and/or VGA
* Optional: something to take pictures (camera, smartphone, small tablet...)

== Sponsors ==

We have three sponsorship levels:

* Gold: >= 2500 USD
* Silver: 1500 USD
* Bronze: 750 USD

We encourage sponsors to support nutriment and entertainment for the
sprinters as they work hard and play hard for four or five productive days.
Contributions will be put towards lunch, snacks, and dinner costs for the
sprinters, and potentially bringing in sprinters who might otherwise be unable
to attend. Any surplus at the end of the event will be turned over to OSGeo or
used for a future code sprint.

Sponsors will receive the following:

* Your logo at the top of this page
* Mention in all of our public communication
* Our undying gratitude, which comes in handy when you least expect it (Remember that feature you wanted...)
* And as extra, for Silver and Gold: Kakemono in the event room (if you provide it)

To sponsor, please contact xxx directly.

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

Daytona Beach Code Sprint 2017

2016-11-03T00:21:02Z

Wiki-Dmorissette: /* Dates and Times */

2015-02-18T14:54:02Z

Wiki-Dmorissette: /* Direct support for Scribe Syntax in MapServer */

= MapServer Suite 2015 SOC Ideas =

Enter ideas for development projects here. '''Note these are just suggestions - students are welcome to propose projects based on their own interests''' that relate to the MapServer Suite. Our current efforts are based on the following projects:

* [http://www.mapserver.org/ Mapserver Suite] This is the mapserver cartographic server, which now includes TinyOWS and MapCache.

You can find the source code, tutorials, the project mailing list and various other information at the link above.

To give you an idea about possible SoC projects, here are some suggestions:

== MapServer core related ideas ==

=== Direct support for Scribe Syntax in MapServer ===

The Scribe syntax is a variant of the traditional MapServer mapfile format that was created to facilitate the development of mapfiles with large number of scale-dependent rules, which is becoming very common with today's tile-based mapping environments with discrete zoom levels. More information about the format is available at http://scribeui.org/scribe-syntax.html

There is currently no direct support for the Scribe syntax in the MapServer core, so users of the Scribe syntax currently have two options:
* use the scribe.py python utility (https://github.com/solutionsmapgears/Scribe) to convert their scribe mapfile to a regular MapServer mapfile
or
* use the ScribeUI online editor (http://scribeui.org/index.html) to manage their mapfiles

The goal of this project is to implement direct (or transparent) support for the Scribe syntax in the MapServer core, either through a dedicated parser, or simply by writing a converter that translates the Scribe syntax into regular mapfile syntax in memory at runtime for each request (possibly with some caching). The second option would be less performant, but simpler. Both options should be considered with their pros and cons. User documentation and test suite would also need to be updated accordingly.

Possible mentors: Daniel Morissette, Julien-Samuel Lacroix

== TinyOWS related ideas ==

=== SpatiaLite support in TinyOWS ===

TinyOWS is a geographical feature server, implementing WFS and WFS-T OGC
protocols. TinyOWS focus on performance, KISS design, and strong compliance to
the standards. It will be included in the MapServer Suite project as soon as the forthcoming 6.2 release.

TinyOWS currently relies heavily on PostGIS, to get a strong transactionnel
backend, and be as close as possible from the data. This leads to good
performances and avoid duplication of features (such as GML format I/O for instance).

This SoC project consists in the implementation of a Spatialite additional support for TinyOWS. The aim is to use this lightweight database as a backend, enabling TinyOWS deployment without the need of a PostGIS server.

SpatiaLite is indeed a SQLite spatial extension, adding a whole lot of
geographical features to SQLite, creating a convenient and lightweight self-
contained spatial database. While being less efficient than PostGIS in a multi-
user context, SpatiaLite supports transactions and most of the spatial
features needed to act as TinyOWS backend.

The project will include the following steps :
* Inclusion of SpatiaLite libraries into TinyOWS build system (as optional)
* Identify all TinyOWS codes related to PostGIS functions.
* Add missing features into SpatiaLite to be able to act as TinyOWS backend (GeomFromGML for instance)
* And provide a clean enough patch to get these features commited into the trunk
* Add multi-database abstraction layer into TinyOWS (to support either PostGIS or SpatiaLite)
* CreateTinyOWS and SpatiaLite units tests cases
* Check compliance to CITE tests for OGC standards with SpatiaLite backend
* Compare performances between PostGIS backend and SpatiaLite backend
* SQL Injection audit, on the new backend (with a tool like SQLMap)

Possible mentors:
* Olivier Courtin <olivier.courtin (at) oslandia.com>
* Brad Hards <bradh (at) frogmouth.net> (on SpatiaLite stuff)

== Other ideas ==

== Lots of other options ==

There are a lot of other possibilities that we would be happy to discuss with any students interested. Best you contact us on the MapServer mailing list:

* http://lists.osgeo.org/mailman/listinfo/mapserver-dev

[[Category:Google_Summer_of_Code]]

MapServer 2015 SOC Ideas

2015-02-18T14:53:25Z

Wiki-Dmorissette: /* MapServer core related ideas */

= MapServer Suite 2015 SOC Ideas =

Enter ideas for development projects here. '''Note these are just suggestions - students are welcome to propose projects based on their own interests''' that relate to the MapServer Suite. Our current efforts are based on the following projects:

* [http://www.mapserver.org/ Mapserver Suite] This is the mapserver cartographic server, which now includes TinyOWS and MapCache.

You can find the source code, tutorials, the project mailing list and various other information at the link above.

To give you an idea about possible SoC projects, here are some suggestions:

== MapServer core related ideas ==

=== Direct support for Scribe Syntax in MapServer ===

The Scribe syntax is a variant of the traditional MapServer mapfile format that was created to facilitate the development of mapfiles with large number of scale-dependent rules, which is becoming very common with today's tile-based mapping environments with discrete zoom levels. More information about the format is available at http://scribeui.org/scribe-syntax.html

There is currently no direct support for the Scribe syntax in the MapServer core, so users of the Scribe syntax currently have two options:
* use the scribe.py python utility (https://github.com/solutionsmapgears/Scribe) to convert their scribe mapfile to a regular MapServer mapfile
or
* use the ScribeUI online editor (http://scribeui.org/index.html) to manage their mapfiles

The goal of this project is to implement direct (or transparent) support for the Scribe syntax in the MapServer core, either through a dedicated parser, or simply by writing a converter that translates the Scribe syntax into regular mapfile syntax in memory at runtime for each request. The second option would be less performant, but simpler. Both options should be considered with their pros and cons. User documentation and test suite would also need to be updated accordingly.

Possible mentors: Daniel Morissette, Julien-Samuel Lacroix

== TinyOWS related ideas ==

=== SpatiaLite support in TinyOWS ===

TinyOWS is a geographical feature server, implementing WFS and WFS-T OGC
protocols. TinyOWS focus on performance, KISS design, and strong compliance to
the standards. It will be included in the MapServer Suite project as soon as the forthcoming 6.2 release.

TinyOWS currently relies heavily on PostGIS, to get a strong transactionnel
backend, and be as close as possible from the data. This leads to good
performances and avoid duplication of features (such as GML format I/O for instance).

This SoC project consists in the implementation of a Spatialite additional support for TinyOWS. The aim is to use this lightweight database as a backend, enabling TinyOWS deployment without the need of a PostGIS server.

SpatiaLite is indeed a SQLite spatial extension, adding a whole lot of
geographical features to SQLite, creating a convenient and lightweight self-
contained spatial database. While being less efficient than PostGIS in a multi-
user context, SpatiaLite supports transactions and most of the spatial
features needed to act as TinyOWS backend.

The project will include the following steps :
* Inclusion of SpatiaLite libraries into TinyOWS build system (as optional)
* Identify all TinyOWS codes related to PostGIS functions.
* Add missing features into SpatiaLite to be able to act as TinyOWS backend (GeomFromGML for instance)
* And provide a clean enough patch to get these features commited into the trunk
* Add multi-database abstraction layer into TinyOWS (to support either PostGIS or SpatiaLite)
* CreateTinyOWS and SpatiaLite units tests cases
* Check compliance to CITE tests for OGC standards with SpatiaLite backend
* Compare performances between PostGIS backend and SpatiaLite backend
* SQL Injection audit, on the new backend (with a tool like SQLMap)

Possible mentors:
* Olivier Courtin <olivier.courtin (at) oslandia.com>
* Brad Hards <bradh (at) frogmouth.net> (on SpatiaLite stuff)

== Other ideas ==

== Lots of other options ==

There are a lot of other possibilities that we would be happy to discuss with any students interested. Best you contact us on the MapServer mailing list:

* http://lists.osgeo.org/mailman/listinfo/mapserver-dev

[[Category:Google_Summer_of_Code]]

MapServer 2015 SOC Ideas

2015-02-18T14:48:46Z

Wiki-Dmorissette: Created page with "= MapServer Suite 2015 SOC Ideas = Enter ideas for development projects here. '''Note these are just suggestions - students are welcome to propose projects based on their own i..."

= MapServer Suite 2015 SOC Ideas =

Enter ideas for development projects here. '''Note these are just suggestions - students are welcome to propose projects based on their own interests''' that relate to the MapServer Suite. Our current efforts are based on the following projects:

* [http://www.mapserver.org/ Mapserver Suite] This is the mapserver cartographic server, which now includes TinyOWS and MapCache.

You can find the source code, tutorials, the project mailing list and various other information at the link above.

To give you an idea about possible SoC projects, here are some suggestions:

== MapServer core related ideas ==

=== Direct support for Scribe Syntax in MapServer ===

The Scribe syntax is a variant of the traditional MapServer mapfile format that was created to facilitate the development of mapfiles with large number of scale-dependent rules, which is becoming very common with today's tile-based mapping environments with discrete zoom levels. More information about the format is available at http://scribeui.org/scribe-syntax.html

There is currently no direct support for the Scribe syntax in the MapServer core, so users of the Scribe syntax currently have two options:
* use the scribe.py python utility (https://github.com/solutionsmapgears/Scribe) to convert their scribe mapfile to a regular MapServer mapfile
or
* use the ScribeUI online editor (http://scribeui.org/index.html) to manage their mapfiles

The goal of this project is to implement direct (or transparent) support for the Scribe syntax in the MapServer core, either through a dedicated parser, or simply by writing a converter that translates the Scribe syntax into regular mapfile syntax in memory at runtime for each request. The second option would be less performant, but simpler. Both options should be considered with their pros and cons.

Possible mentors: Daniel Morissette, Julien-Samuel Lacroix

== TinyOWS related ideas ==

=== SpatiaLite support in TinyOWS ===

TinyOWS is a geographical feature server, implementing WFS and WFS-T OGC
protocols. TinyOWS focus on performance, KISS design, and strong compliance to
the standards. It will be included in the MapServer Suite project as soon as the forthcoming 6.2 release.

TinyOWS currently relies heavily on PostGIS, to get a strong transactionnel
backend, and be as close as possible from the data. This leads to good
performances and avoid duplication of features (such as GML format I/O for instance).

This SoC project consists in the implementation of a Spatialite additional support for TinyOWS. The aim is to use this lightweight database as a backend, enabling TinyOWS deployment without the need of a PostGIS server.

SpatiaLite is indeed a SQLite spatial extension, adding a whole lot of
geographical features to SQLite, creating a convenient and lightweight self-
contained spatial database. While being less efficient than PostGIS in a multi-
user context, SpatiaLite supports transactions and most of the spatial
features needed to act as TinyOWS backend.

The project will include the following steps :
* Inclusion of SpatiaLite libraries into TinyOWS build system (as optional)
* Identify all TinyOWS codes related to PostGIS functions.
* Add missing features into SpatiaLite to be able to act as TinyOWS backend (GeomFromGML for instance)
* And provide a clean enough patch to get these features commited into the trunk
* Add multi-database abstraction layer into TinyOWS (to support either PostGIS or SpatiaLite)
* CreateTinyOWS and SpatiaLite units tests cases
* Check compliance to CITE tests for OGC standards with SpatiaLite backend
* Compare performances between PostGIS backend and SpatiaLite backend
* SQL Injection audit, on the new backend (with a tool like SQLMap)

Possible mentors:
* Olivier Courtin <olivier.courtin (at) oslandia.com>
* Brad Hards <bradh (at) frogmouth.net> (on SpatiaLite stuff)

== Other ideas ==

== Lots of other options ==

There are a lot of other possibilities that we would be happy to discuss with any students interested. Best you contact us on the MapServer mailing list:

* http://lists.osgeo.org/mailman/listinfo/mapserver-dev

[[Category:Google_Summer_of_Code]]