OSGeo - User contributions [en]

Google Summer of Code 2016 Administrative

2016-03-03T13:56:32Z

Wiki-Woodbri: /* 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=250px|'''email'''
|'''Software'''
|'''Idea(s) you are available to mentor'''
|-
|1
|Margherita
|Di Leo
|madi
|diregola AT gmail DOT com
|admin at OSGeo
|Idea I would like to mentor
|-
|2
|Alexander
|Bruy
|alexbruy
|alexander.bruy AT gmail.com
|QGIS
|
|-
|3
|Victor
|Olaya
|volaya
|volayaf AT gmail DOT com
|QGIS
|
|-
|4
|Daniel
|Kastl
|dkastl
|daniel AT georepublic DOT de
|pgRouting
|
|-
|5
|Massimiliano
|Cannata
|maxi
|massimiliano.cannata AT gmail DOT com
|istSOS
|
|-
|6
|Milan
|Antonovic
|milan
|milan.antonovic AT gmail DOT com
|istSOS
|
|-
|7
|Jachym
|Cepicky
|jachym
|jachym.cepicky AT gmail
|PyWPS
|
|-
|8
|Andrea
|Antonello
|moovida
|andrea.antonello AT gmail DOT com
|JGrasstools, gvSIG, Geopaparazzi
|
|-
|-
|9
|Rashad
|Kanavath
|rashadkm
|rashadkm AT gmail DOT com
|GRASS GIS, OSSIM, GDAL
|
|-
|10
|Cameron
|Shorter
|CameronShorter
|cameronDOTs h o r ter AT gmail com
|OSGeo-Live
|
|-
|-
|11
|Stephen
|Woodbridge
|woodbri
|woodbri AT swoodbridge DOT com
|pgRouting
|
|-|}

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

Stephen Woodbridge

2015-11-20T19:43:38Z

Wiki-Woodbri:

{{OSGeo Member
|Name=Stephen Woodbridge
|Country=USA
|State=MA
|City=Chelmsford
|Coordinate=42.62276,-71.36612
|Email=woodbri@swoodbridge.com
|Website=http://imaptools.com/
}}
<tt>[[Category:OSGeo Member]]

Stephen Woodbridge is a member of the Mapserver PSC and has been actively using, supporting the Mapserver since 2000. Stephen works extensively with pgRouting and is a developer and PSC member for pgRouting. He also works and supports PostGIS, OpenLayers and does geospatial consulting via "http://imaptools.com/". Stephen has worked for two of the largest commercial users of mapserver. He has developed geocoders, reverse geocoders, mapping solutions using mapserver and OpenLayers and developed various applications and tools in C/C++, plpgsql, Perl, and Javascript.

Stephen Woodbridge

2015-11-20T19:31:39Z

Wiki-Woodbri:

<tt>[[Category:OSGeo Member]]

Stephen Woodbridge is a member of the Mapserver PSC and has been actively using, supporting the Mapserver since 2000. Stephen works extensively with pgRouting and is a developer and PSC member for pgRouting. He also works and supports PostGIS, OpenLayers and does geospatial consulting via "http://imaptools.com/". Stephen has worked for two of the largest commercial users of mapserver. He has developed geocoders, reverse geocoders, mapping solutions using mapserver and OpenLayers and developed various applications and tools in C/C++, plpgsql, Perl, and Javascript.

User:Woodbri

2015-04-16T00:38:56Z

Wiki-Woodbri: /* Stephen Woodbridge */

===Stephen Woodbridge===

[[File:Stephen.woodbridge.jpg|thumb|right|100px|Stephen Woodbridge]]

Owner, [http://imaptools.com/ iMaptools.com]

Location: North Chelmsford, MA, USA

Stephen works on PointClouds, Vehicle Routing Problems, Mapserver, pgRouting, Geocoding, Reverse Geocoding, GDAL/OGR, OpenLayers as well as other open source products. Stephen can be found at [http://iMapTools.com/ iMapTools.com] where he provides geospatial products, consulting and advocates [http://osgeo.org/ OSGeo] and OpenSource products to his clients.
[http://swoodbridge.com/?id=3 Resume.]
[http://www.linkedin.com/pub/stephen-woodbridge/18/bb0/284 LinkedIn Profile.]

;OSGeo Experience [[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]][[File:OSGeo_psc.png|link=OSGeo_Advocate#Voted_position_in_an_OSGeo_community]][[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]][[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]] :
:* [http://mapserver.org/ Mapserver] PSC member and user. Stephen constructs mapfiles and manages client production environments that collectively serve billions map of draws per year.
:* [http://www.pgrouting.org/ pgRouting] PSC member, user and developer. Stephen prepares client data for use with pgRouting, has developed driving directions module, and has mentored Google of Summer Code students developing pgRouting.
:* [http://www.pagcgeo.org/ PAGC] (Postal Address Geocoder) PSC member and user, tester and developer.
:* A knowledgeable user of [http://www.gdal.org/ GDAL/OGR] and [http://openlayers.org/ OpenLayers] as well as other Open Source projects.

;Contact:
: Email: woodbri AT swoodbridge DOT com
: Phone (work): 1-978-251-4502
: Skype: stephen.woodbridge

;Spoken Language(s): English

;Profile last updated: 28 JUNE 2012

LIDAR Format Letter

2015-04-16T00:36:25Z

Wiki-Woodbri: /* 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.

=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 is 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 have 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 />

Contacts

2014-10-09T00:11:11Z

Wiki-Woodbri: /* Software Projects */

OSGeo Projects are freestanding entities, handled by their own Project Steering Committees. Each project has been asked to provide a representative to help coordinate OSGeo involvement. These volunteers are listed by project below:

== General ==
* General Foundation Info - info@osgeo.org - [mailto:info@osgeo.org] (emails are currently forwarded to 3 people: FrankW, JeffM, Jachym)
* [[President]]
* [[Treasurer]]
* [[Secretary]]
* [[Board of Directors]]

== Software Projects ==
'''Web Mapping'''
* [http://www.degree.org/ deegree]: [http://wiki.deegree.org/deegreeWiki/StructuresAndProcedures PSC] - Contact: [[User:JensFitzke | Jens Fitzke]]
* [http://geomajas.org Geomajas]: [http://www.geomajas.org/community/project-steering-committee PSC] - Chair: Pieter De Graef (pieter.degraef at geosparc.com)
* [http://www.geomoose.org/ GeoMoose]: [http://www.geomoose.org/rfc/rfc-1.html PSC] - Chair: - Brian Fischer (bfischer at houstoneng.com)
* [http://geoserver.org GeoServer]: [http://docs.geoserver.org/latest/en/developer/policies/psc.html PSC] - Project Officer: Andrea Aime (andrea dot aime at geo-solutions.it) (checked 2014-10-09)
* [http://www.mapbender.org Mapbender]: [http://www.mapbender.org/index.php/Category:PSC PSC] - Chair: Christian Wygoda
* [http://www.mapfish.org MapFish]: [http://trac.mapfish.org/trac/mapfish/wiki/Community/PSC PSC] - Chair: [[User:Elem | Eric Lemoine]]
* [http://mapguide.osgeo.org/ MapGuide Open Source]: [http://mapguide.osgeo.org/psc.html PSC] - Chair: Robert Bray (robert.bray at autodesk.com)
* [http://mapserver.org/ MapServer]: [http://mapserver.org/development/rfc/ms-rfc-23.html PSC] - Chair: Stephen Lime (sdlime at comcast.net)
* [http://openlayers.org/ OpenLayers]: [http://trac.openlayers.org/wiki/SteeringCommittee PSC] - Chair: [[User:Tschaub | Tim Schaub]]

'''Desktop Applications'''
* [http://grass.osgeo.org/ GRASS GIS]: [http://trac.osgeo.org/grass/wiki/PSC PSC] - Chair: [[Markus Neteler]]
* [http://www.gvsig.org/ gvSIG]: - [[GvSIG Technical Project Committee|PSC]] - Chair: [[Manuel Madrid]]
* [http://marble.kde.org/ Marble]: [http://edu.kde.org/marble/authors.php Authors] - Liaison Officer: [[Torsten Rahn]]
* [http://www.ossim.org/ OSSIM]: [http://trac.osgeo.org/ossim/wiki/ossimgovernance PSC] - Chair: Garrett Potts
* [http://www.qgis.org/ Quantum GIS]: [http://wiki.qgis.org/qgiswiki/Project_Organigram PSC] (outdated, see [http://spatialgalaxy.net/2013/08/25/welcome-to-new-qgis-psc-members/ this blog post] by Gary Sherman for the current PSC members - Chair: Gary Sherman (sherman at mrcc.com)

'''Geospatial Libraries'''
* [http://fdo.osgeo.org/ FDO]: [http://fdo.osgeo.org/ Home Page] (link to PSC broken) - Chair: Greg Boone (greg.boone at autodesk.com)
* [http://www.gdal.org/ GDAL/OGR]: [http://trac.osgeo.org/gdal/wiki/GovernanceAndCommunity PSC] - Chair: Frank Warmerdam (warmerdam@pobox.com)
* [http://www.geotools.org/ GeoTools]: [http://docs.codehaus.org/display/GEOT/4+Project+Management+Committee PSC] - Project Officer Jody Garnett (jody.garnett at gmail.com) (checked 2014-10-09)
* [http://geos.osgeo.org/ GEOS]: [http://trac.osgeo.org/geos/wiki/PSC PSC] - Chair: [[User:Strk | Sandro Santilli]] (strk at keybit.net)
* [http://metacrs.osgeo.org/ MetaCRS]: [http://metacrs.osgeo.org PSC] - Chair: Frank Warmerdam (warmerdam@pobox.com)
* [http://postgis.org/ PostGIS]: [http://postgis.org/documentation/manual-svn/ch01.html#psc PSC] - Chair: [[User:Pwramsey3 | Paul Ramsey]]
* [http://pgrouting.org/ pgRouting]: [http://pgrouting.org/development.html PSC] - Chair: [[User:Woodbri | Stephen Woodbridge]]

'''Metadata Catalog'''
* [http://geonetwork-opensource.org GeoNetwork opensource]: [http://trac.osgeo.org/geonetwork/wiki/PSC PSC] - Chair: [[User:Ticheler | Jeroen Ticheler]] (Jeroen.Ticheler at geocat.net) (checked 2014-10-09)

== Committees ==
* [[Conference Committee]] - Jeff McKenna - jmckenna at gatewaygeomatics.com (checked 2014-10-09)
* [[Education and Curriculum Committee]] - Charlie Schweik - cschweik at pubpol.umass.edu (checked 2014-10-09)
* [[Finance Committee]] - [[User:Dmorissette|Daniel Morissette]] - dmorissette at mapgears.com (checked 2014-10-09)
* [[Incubation Committee]] - Jody Garnett - jody.garnett at gmail.com (checked 2014-10-09)
* [[Marketing Committee]] - Cameron Shorter - cameron.shorter at gmail.com (checked 2014-10-09)
* [[Public Geospatial Data Committee]] - [[User:Bitner|David Bitner]] - bitner at dbspatial dot com (checked 2014-10-09)
* [[SAC|System Administration Committee]] - Alex Mandel - tech_dev at wildintellect.com (checked 2014-10-09)
* [[Website Committee]] - Christopher Schmidt - crschmidt at metacarta.com '''(mail not delivered)'''
* OSGeo [[Journal]]

== Packaging ==
* [http://live.osgeo.org OSGeo-Live] - Cameron Shorter - cameron.shorter at gmail.com

== Local Chapters ==

Contacts list for the [[:Category:Local_Chapters|local chapters]]:
* [[Africa Local Chapter]] - [[User:Gfleming|Gavin Fleming]]
* [[Aust-NZ]] - Australia and New Zealand Chapter- Bruce Bannerman - bruce.bannerman.osgeo at gmail.com
* [[Brazil]] - Helton Uchoa - engenheiro.uchoa at gmail.com
* [[California]] - Landon Blake - sunburned.surveyor at gmail dot com
* [[Cascadia|CUGOS Cascadia Chapter US]] - [[User:Racicot|Aaron Racicot]] - aaronr at cugos.org (checked 2014-10-09)
* [[China]] - Chen Rongguo - chenrg at lreis.ac.cn
* [[D-A-CH]] (German language) - [[User:Mlechner|Marco Lechner]] (checked 2014-09-30)
* [[Finland]] - [[User:AJolma|Ari Jolma]] - ajolma at osgeo.org (checked 2014-10-09)
* [[Francophone]] - board at osgeo.asso dot fr / president at osgeo.asso.fr (Etienne Delay) (checked 2014-09-30)
* [[Greek]] - [[User:kotzino|Dimitris Kotzinos]] - kotzino at csd dot uoc dot gr (checked 2014-09-30)
* [[India]] - P.S. Roy - psroy13 at gmail.com
* [[Italy]] - [[User:epifanio|Massimo Di Stefano]] - IT -- epiesasha at me dot com
* [[Japan]] - Mr. Mori Toru - moritoru at orkney.co.jp (checked 2014-09-30)
* [[Korea | Korean Chapter]] - [[User:Endofcap|Sanghee Shin]] - shshin at gaia3d.com or endofcap at gmail.com (checked 2014-09-30)
* [[KSA Chapter]] - Awase Khirni Syed - awasekhirni at gmail.com
* [[Nederlands | Dutch language Chapter]] - [[User:Just|Just van den Broecke]] (secretary) [[User:Geejee|Gert-Jan van der Weijden]] (president). info at osgeo dot nl (checked 2014-10-08)
* [[Ottawa Chapter]] - Fabien Ancelin - fabien.ancelin at gmail.com
* [[PDX-OSGEO]] - Oregon, US Chapter -- [[User:EliL|Eli L Adam]] - contact on user page (checked 2014-09-30)
* [[Philippines]] - [[User:maning|Maning Sambale]] - emmanuel dot sambale at gmail dot com (checked 2014-10-09)
* [[Poland]] - Tomasz Kubik - tomasz kubik at pwr wroc pl (checked 2014-09-30)
* [[Portugal]] - Jorge Gustavo Rocha - [[Jorge_Gustavo_Rocha]], Giovanni Manghi - [[Giovanni_Manghi]]
* [[Romanian]] - [[User:Vasile|Vasile Crăciunescu]] - vasile at geo-spatial dot org
* [[Quebec]] - [[User:Dmorissette|Daniel Morissette]] - dmorissette at mapgears dot com (checked 2014-10-09)
* [[Spanish]] - [[Pedro-Juan Ferrer]] - vehrka at gmail.com (checked 2014-10-09)
* [[Taiwan]] - Sander Borghuis - s.borghuis at geo.uu.nl '''(mail not delivered)'''
* [[Twin_Cities]] - Twin Cities, MN -- [[User:Bitner|David Bitner]] - bitner at dbspatial dot com
* [http://www.osgeo.org/uk UK] - [[User:JoCook|Jo Cook]]

== Infrastructure ==

* [[SAC:Primary Administrators]]

[[Category:Board]]
[[Category:Education]]
[[Category:Incubation]]
[[Category:Infrastructure]]
[[Category:PSC]]

Geoservices REST API

2013-05-08T01:20:20Z

Wiki-Woodbri: /* Signed */

This wiki page aims to collate community concerns related to the proposed acceptance of the "Geoservices REST API" becoming an OGC standard.

= Open Letter to OGC and voting members =

''Please don't edit this "Open Letter" statement, comments and discussion should go below.''

May 2013

We, the undersigned, have concerns that approving the "Geoservices REST API" as an OGC standard, would have detrimental impacts on interoperability within the spatial industry.

We strongly urge that the proposed "Geoservices REST API", as it stands in May 2013, be rejected as an OGC standard.

People have listed different reasons for concern. They are described below.

== Signed ==
''Please add your name here if you agree with the above statement. Include name, work title (if appropriate), very brief title/involvement in OSGeo if appropriate. (Link to OSGeo profile if appropriate). You may sign as a group, such as the Project Steering Committee of XXX project if you wish, or as Your Name on behalf of YYY company.''

* [[User:camerons|Cameron Shorter]], Geospatial Solutions Director at LISAsoft, core contributor & coordinator of [http://live.osgeo.org OSGeo-Live]
* [[User:Woodbri|Stephen Woodbridge]], Director of [http://imaptools.com iMaptools.com], Contributor and/or PSC of [http://mapserver.org Mapserver], [http://pgrouting.org/ pgRouting], [http://www.pagcgeo.org/ PAGC], and [http://www.postgis.org/ PostGIS]
*

= Concerns =
--- DRAFT ____

''Please add concerns as bullet points below. Try to be concise. Where appropriate, link to external web pages (such as email achieves)''

== Summary ==
To do: Add a brief 3 paragraphs or so summarising the issues.

== Political Concerns ==

== Commercial Concerns ==

== Technical Concerns ==

= History =

Todo: please expand
* Explain how this standard came to be
* Based on Arc GIS Server API
* Attempted but failed to go through OGC fast track process
* Recent voting history: refer to: http://lists.osgeo.org/pipermail/discuss/2013-May/011602.html

= References =
Todo: Link to key external docs, such as the proposed standards

[[Category: OGC]]
[[Category: Standards]]

Boston Code Sprint 2013

2013-03-13T15:21:08Z

Wiki-Woodbri: /* Participation */

[[Image:boston_codesprint_2012.png|700px|right]]

{| class="wikitable" style="float:right"
! '''Gold Sponsors'''
|-
| [http://www.enterprisedb.com EnterpriseDb]
| [[File:EDB_logo_rgb_300.jpg‎]]
|-
! '''Silver Sponsors'''
|-
| [http://www.geosynergy.com.au GeoSynergy]
| [[File:GeoSynergy_650.jpg‎|600px]]
|-
| [http://www.airborneinteractive.com/ Airborne Interactive]
| [[Image:AirborneInteractive 400.png|200px|AirborneInteractive 400.png]]
|-
! '''Bronze Sponsors'''
|-
| [http://www.azavea.com Azavea]
| [[File:Logo-azavea.png‎]]
|-
| [http://www.hobu.biz Hobu]
| [[File:Logo-Hobu.png‎]]
|-
| [http://www.1ocean.com OneOcean]
| [[File:Bos_code_sprint_oneocean.png|300px]]
|-
! ''Other in-kind Sponsors''
|-
| Paragon Corporation
|}

{|width="290px" border="0" cellpadding="2" cellspacing="0"
|
== Purpose ==
Get together project members to make decisions and tackle larger geospatial problems (as done last year at the [[IslandWood Code Sprint 2012]] and previous years: [[Montreal Code Sprint 2011|Montreal]] (2011), [[New York Code Sprint 2010|New York City]] (2010), and [[Toronto Code Sprint 2009|Toronto]] (2009)). This code sprint is targeting members of the "C Tribe" (eg, MapServer, GRASS, GDAL, Proj, PostGIS, MapGuide, OpenLayers). Other tribes are welcome to join the sprint, of course, but we hope that "C Tribe" members will give this event special consideration.

We have started a [[Boston Sprint 2013 Agenda]] page for preliminary planning of tasks.

== Timing ==
Dates: '''Weekday: Monday - Thursday 3/25-3/28'''
Duration: Four days (9AM - 5PM)

|}
== Venue ==
''' Planned Location: ''' [http://www.devonshireboston.com/skyclub.html Devonshire Sky Club Conference Room] (42.358187,-71.057593) and if needed
spill over into Paragon Offices

Both across the street from Boston City Hall. Right on the [http://www.thefreedomtrail.org/ Freedom Trail] and about 2 blocks away
from the [http://www.fsf.org/about/contact/ Free Software Foundation head quarters].

Walking distance from all subway lines, commuter rail stations, and Amtrak.

= Agenda=
'''Sunday (March 24th)'''

* 5:00pm to 10:00pm - check-in
** ''if you plan to arrive earlier than 4pm or later than 11:55 PM, contact Leo to make arrangements''
** ''You can hang out with rest of Boston hackers if you want''

'''Monday (March 25th)'''

* 8:00am - breakfast
* 8:00am to noon - ''sprinting''
* noon - lunch (in meeting room) informal presentations
* 12 - 1pm (Google Hangout?) - just quick intro from each group
* 2pm to 4:00pm - ''sprinting''
* 4:00pm to 5:00pm - drinks/social hour
* 5:00pm to 7:00pm - dinner
* 7:00pm - watch Hockey somewhere or [http://lists.osgeo.org/pipermail/tosprint/2013-February/000389.html Hangout with Eclipse folks who invited us to their party]

'''Tuesday (March 26th)'''

* 8:00am - breakfast
* 8:00am to noon - ''sprinting''
* noon - lunch (in meeting room)
* 1pm - 2pm (Google Hangout? - dedicated to specific working group )
* 2pm to 5:00pm - ''sprinting''
* 5:00pm to 7:00pm - dinner
* 7:00pm to 8:00pm - walk around Boston the most walkable city :)

'''Wednesday (March 27th)'''

* 8:00am - breakfast
* 8:00am to noon - ''sprinting''
* noon - lunch (in meeting room)
* 1pm - 2pm (Google Hangout? )
* 2pm to 5:00pm - ''sprinting''
* 5:00pm to 7:00pm - dinner

'''Thursday (March 28th)'''
* 8:00am - breakfast
* 9:30am - '''checkout'''
* 8:00am to noon - ''sprinting''
* 11:00am - lunch (in meeting room)
* 12:00pm - hard stop, meeting room closes
* Farewells

== Project Plans ==
* [[Boston Sprint 2013 Agenda]]
* [https://github.com/mapserver/mapserver/wiki/Boston-Codesprint-Agenda MapServer sprint plan]

== Sponsor Demos ==

During the lunch hour, our sponsors will have the opportunity to talk briefly and informally about their products/services and how they use open source.

* Monday
** 12:00 - Azavea: GeoTrellis
** 12:30
* Tuesday
** 12:00
** 12:30
* Wednesday
** 12:00
** 12:30

== Sponsors ==
We have three sponsorship levels:

* Gold: >= $2000
* Silver: $1500
* Bronze: $750

We will again be looking for sponsors ($750+) to support food and fun for the sprinters as they work hard and play hard for four productive days. Each sponsorship will be put towards lunch and dinner costs for the sprinters, and potentially bringing in sprinters who might otherwise be unable to attend.

Sponsors get the following benefits:

* Your banner at the top of this page
* 30-minute slot to talk about how you are using FOSS GIS (first come first serve)
* Get to sit with us at the sprint and have input in project road map of an OSGeo project you are interested in
* Our undying gratitude, which comes in handy when you least expect it. Remember that feature you wanted in X :)
* The good feeling that you have contributed to the FOSS GIS movement (priceless and good for the health too)

To sponsor, please contact Leo Hsu and Regina Obe (lr at pcorp dot us) directly regarding sponsorship and level of sponsorship you'd like to provide

=== 2013 Sponsors ===
This is the current list of pledges
==== Gold ====
#EnterpriseDb

==== Silver ====
# Mobile Geographics
# Airborne Interactive
# GeoSynergy

==== Bronze ====
# OneOcean
# Azavea
# Hobu, Inc.

== Budget ==

== Hotel ==
We've decided not to get a block of rooms because it seems it is pricier than having people pick the hotel they like best.

Our recommendation is to book your own room via Hotwire or Priceline.

For Hotwire, any hotel in the Financial District will be within walking distance.

For Price Line, any hotel within ½ mile of 1 DEVONSHIRE PL BOSTON MA 02109 will be within walking distance.

Boston has no major conventions during the Code Sprint. Note: [http://www.eclipsecon.org/2013/ EclipseCon 2013] is running during the same period.

There are over a dozen hotels name-brand and boutique within a ½ mile, all rated above three stars.

Should you have specific questions, feel free to email us directly: lr at pcorp.us.
We’ll help you find the perfect accommodation.

== Costs ==

Participants should plan for the following costs:

* Travel to Boston, variable depending on where you are.
* Accommodation for four nights, $300 to $600 depending on what room you choose and whether you room share.
* Breakfast, dinner and other snacks.
* The sponsorship moneys will be put towards: conference room rent, morning snacks, lunches, dinner (1), social event (?), and trip subsidies (e.g. travel costs for core developers)

== Communication ==

* Please join the mailing list: http://lists.osgeo.org/mailman/listinfo/tosprint

* IRC chat during the event: Channel: #tosprint Server: irc.freenode.net

== Participation ==

We are planning for attendance of 20-30. Please add your name and the projects you are hoping to sprint and note the likeliness of your attendance.

For room if you need a room - put either:
single room - if you want your own
room share - if you'd prefer to share or don't care
local arrangements - put if you already have arrangements planned

# Leo Hsu (Definite) Paragon Corporation - PostGIS, pgRouting, PDAL 3/25, 3/18, 3/11, any
# Regina Obe (Definite) Paragon Corporation - PostGIS, pgRouting, PDAL 3/25, 3/18, 3/11, any
# Michael Smith - US Army Corps - MapServer; PDAL; GDAL/OGR - Will definitely be here
# [[User:dmorissette|Daniel Morissette]] - Mapgears - MapServer; GDAL/OGR - flight booked
# [[User:pwramsey3|Paul Ramsey]] - PostGIS - Arriving Mar 24 @ 18:11 on AC364
# Thomas Bonfort - Terriscope - MapServer - flight booked - "any"
# [[Jeff McKenna]] - Gateway Geomatics - MapServer - flight booked, shared room
# Olivier Courtin - Oslandia - PostGIS, TinyOWS - flight booked
# Hugo Mercier - Oslandia - PostGIS - flight booked
# Stephan Meissl - EOX - MapServer - flight booked, room share
# Bborie Park - PostGIS Raster - flight booked, single room
# Howard Butler - Hobu, Inc. - arriving Mar 24 @ 4:30 on United 1235
# [[User:Woodbri|Steve Woodbridge]] - iMaptools.com - MapServer; pgRouting; postGIS - Will definitely be here, live locally
# Norman Barker - Cloudant - very likely - "ANY"
# Steve Lime - MapServer - flight booked
# [[User:kshepard|Kenny Shepard]] - Azavea - PostGIS, very likely, single room
# [[User:Dzwarg|David Zwarg]] - Azavea - PostGIS Raster; GDAL/OGR - 99.73% sure, any, local arrangements
# <strike>[[User:kirk|Kirk McKelvey]] - LizardTech - PDAL/GDAL - likely, 3/4, 3/18, 3/25, single room</strike> (will sorely miss this - until next year then)
# Michael P. Gerlek (or designee) - OneOcean - PDAL & Friends - ("possible"), will make own lodging arrangements
# Tom Kralidis - MapServer, pycsw, owslib - Possible
# Jim Klassen - SharedGeo - flight booked
# [[User:Jwalgran|Justin Walgran]] - Azavea - OpenLayers; PostGIS - likely, single room
# Norman Vine - self - likely - any
# Brad Chambers - RadiantBlue - PDAL - likely - single room
# Rob Emanuele - Azavea - PostGIS Raster - very likeable
# Stephen Mather - PostGIS/Raster/PDAL, Definite, local arrangements
# Pierre Racine - University Laval - PostGIS Raster - very likely
# Alan Boudreault - Mapgears - MapServer; GDAL/OGR - flight booked
# [[User:Djay|Gérald Fenoy]] - GeoLabs SARL - ZOO-Project - flight booked, local arrangements
# Frank Warmerdam - Google - GDAL; MapServer; PROJ.4 - Possible
# [[User:Mloskot|Mateusz Loskot]] - PostGIS/PDAL - unlikely, any
# Jonas Lund Nielsen - Danish Geodata Agency - MapServer - very likely - local arrangements

Virtual participants (irc #tosprint)

== Room Share ==

If you would like to room share,

# Reserve a room at the hotel, choosing a type with more than one bed.
# Put your name in this section, indicating the amount of space in your room.

Put your names below:

* example entry: B has a triple room, needs two roommates.

== Individual Preparation ==

* Bring your own computer
* Install subversion and the compiler tools, and come with a working development environment if possible.

== FAQ ==

* Is the Boston Code Sprint just a coding event?
** Yes, a coding, testing and documentation event. It is a working session for people who are already participants in open source projects.
* Will it be possible to present new projects during this event?
** No, this is not a presentation-oriented event. People will get together in small groups and work on areas of mutual interest within their projects.
* Will there be presentation time to show case innovative uses of technology?
** Yes, Sponsors and sprinters actively working on projects will have their moment of glory

== Social Events ==

Here are some events happening around town that would be fun:

=== Hockey ===

* '''Mon Mar 25''' 7:00 PM: Maple Leafs vs. Bruins
* '''Wed Mar 27''' 7:30 PM: Canadiens vs. Bruins

=== Basketball ===

* '''Tues Mar 26''' 7:00 PM: Knicks vs. Celtics

=== Crashing Parties ===
* '''Mon Mar 25''' 1:00 PM [http://locationtech.org/content/information-session LocationTech] will be having their meetup as part of Eclipse 2013 which will be in Boston running same days we are.
* '''Mon Mar 25''' 7-10 PM [http://ignitelocationtechboston1.eventbrite.com/ Ignite LocationTech Boston] (follow link to register)
* [http://www.meetup.com/avidgeo/ AvidGeo] might be having a meetup around that time too.

== Getting to the Sprint ==
From Logan Airport -- Take Blue Line to State Street.

== Recaps ==

=== Photos ===

[[Category:Code Sprints]]
[[Category:Past Events]]

Boston Sprint 2013 Agenda

2013-03-05T14:26:13Z

Wiki-Woodbri: /* PostGIS / pgRouting */

Meeting times and locations can be found: [[Boston Code Sprint 2013]]
=== MapServer ===

=== GDAL ===

=== PostGIS / pgRouting ===
General Stuff
# When are we going to release 2.1. Steps remaining before we can
# SpGist -- when is that going to happen will make cut for 2.1 or push to 2.2
# How best to integrate Oslandia 3D work, concerns etc.
## Exact Geometry support
## Reference Geometry support
## (SF)CGAL
# Google SoC 2013
# Regression suites (performance, valgrind?)

Geocoding specific stuff
# Integrating Steve Woodbridge - address normalizer into PostGIS
# Packaging as part of windows builds at very least

pgRouting
# Packaging pgRouting for windows to be availabe in stack builder along side PostGIS
# Discussion of how pgRouting / PostGIS can better work together and melding the two projects
# Side note both Oslandia 3D work and pgRouting both use CGAL, possible opportunity/concern there ?
## pgRouting is looking into the possibility of drop CGAL and GAUL dependency to simplify builds
# pgRouting 2.0 release (working on building that plan now)

Raster
# Raster seems in darn good shape for 2.1 so least worried about raster. Great job :)
# Raster WKB version 1 format to address shortcomings of version 0 related to out-db rasters
# Rework of MapAlgebra for 2.1 or push to 2.2
## Performance of expression-based mapalgebra
## Performance of ST_Clip
# GDAL raster driver - good support for overviews, irregularly tiled coverage. Some nice todo improvements:
## Add write support. Related ticket [http://trac.osgeo.org/gdal/ticket/4617 #4617]
## Fix bug with metadata precission. Related ticket [http://trac.osgeo.org/gdal/ticket/4214 #4214]
## Check out-db raster support. Related ticket [http://trac.osgeo.org/gdal/ticket/3234 #3234]
## Low range pixel type should be transformed to a higher one. Related ticket [http://trac.osgeo.org/gdal/ticket/4562 #4562]
## Check tickets [http://trac.osgeo.org/gdal/ticket/4531 #4531], [http://trac.osgeo.org/gdal/ticket/4560 #4560] and [http://trac.osgeo.org/gdal/ticket/4561 #4561]
## Rewrite tests (gdal_autotest). Related ticket [http://trac.osgeo.org/gdal/ticket/5010 #5010]
## More tests with Mapserver. Related ticket [http://trac.osgeo.org/gdal/ticket/5010 #5010]
## Tests with QGIS plugin. Related ticket [http://trac.osgeo.org/gdal/ticket/5010 #5010]
## Deal with really BIG raster data in IRasterIO (recursion? split in several calls?). Related ticket [http://trac.osgeo.org/gdal/ticket/5012 #5012]
## Take default user, host, password. Related ticket [http://trac.osgeo.org/gdal/ticket/4533 #4533]
## Review SQL strings (avoid SQL injection). Related ticket [http://trac.osgeo.org/gdal/ticket/5013 #5013]
## Take care of locale (I needed to export LC_ALL=C to make it work with QGIS). Related ticket [http://trac.osgeo.org/gdal/ticket/5014 #5014]
## Allow user to specify resolution strategy when dealing with different pixel size sources (maybe an option in connection string). Related ticket [http://trac.osgeo.org/gdal/ticket/5011 #5011]
## Allow user to specify the desired srid when dealing with different srids. Related ticket [http://trac.osgeo.org/gdal/ticket/5011 #5011]
# QGIS - good support for large coverage (overviews, irregularly tiled coverage), import export. What need to be enhanced?
# ST_CreateOverview()
# Test performance of ST_Union() when number of pixel increase
# Define another (faster?) way to rasterize a vector coverage with ST_MakeEmptyTiledCovererage(), ST_BurnToRaster(geometry, raster) & ST_UnionToRaster()
# Discuss a more flexible way to rasterize a vector coverage
# Raster using pthreads in the future?
# Rewrite parts of raster2pgsql
# pgsql2raster prototype?
# Discuss "PostGIS Extra PL/pgSQL Function Set"
# Discuss interpolation - from some point, from millions of points
# Test regular blocking constraint
# Discuss viewshed
# Discuss integration of raster2pgsql into the GUI

=== PDAL ===

Boston Sprint 2013 Agenda

2013-03-04T22:03:01Z

Wiki-Woodbri: /* PostGIS / pgRouting */

OpenGeocoder

2012-12-09T15:17:58Z

Wiki-Woodbri: /* Relevant Existing Open Source Technologies */

== Special Announcement ==

[[Image:Foss4g2010_logo.jpg||FOSS4G2010]]

[http://2010.foss4g.org/ FOSS4G 2010 Conference]

== Open Source Geocoder ==

For those not familiar with the concept, Geocoding takes a human readable address and turns it into coordinates.

===Project Purpose===

The intention of this project is to work towards creation of open source software providing geocoding capability.

===Google Summer of Code Ideas===

We have proposed some ideas for Google Summer of Code projects. You can read more about them [[OpenGeocoder 2009 SOC Ideas]].

===Design goals===

Desired attributes:
* Handle international addressing schemes (expected to be pluggable to support internationalization)
* Library Coded in C (or C wrapper to C++)
* Architected and designed for performance
* Abstracted storage to allow for use of data from various sources e.g. shapefiles, RDBMS, others

===Contact information===

Please join us on the [http://lists.osgeo.org/mailman/listinfo/routergeocoder mailing list].

NOTE: This mailing list is shared between this project and the [http://wiki.osgeo.org/wiki/OpenRouter OpenRouter] project.

===Relevant Existing Open Source Technologies===

* [http://www.extendthereach.com/products/OpenSourceGeocoder.srct SRC Explorer Geocoder]
* [http://www.geocoder.us Geocoder.us]
* [http://www.postlbs.org/en/geocoder PostLBS]
* [http://www.pagcgeo.org PAGC]
* [http://www.gisgraphy.com/ Gisgraphy]

===Relevant Existing Close Source Technologies===

* http://www.batchgeocode.com/

===Target Licensing===

* Preference for a liberal license to encourage adoption by maximum number of technologies both proprietary and open source

===Project Support===

====Development====

The following list are people who are interested in participating in development of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Andrew Turner - [http://www.geocommons.com GeoCommons] & [http://www.highearthorbit.com HighEarthOrbit]
* Daniel Kastl - [http://pggeocoder.postlbs.org/ pgGeocoder] | [http://georepublic.de Georepublic]
* Anton Patrushev - [http://pggeocoder.postlbs.org/ pgGeocoder] | [http://georepublic.de Georepublic]
* Toru Mori - [http://pggeocoder.postlbs.org/ pgGeocoder] | [http://www.orkney.co.jp Orkney]
* Stephen Woodbridge - http://imaptools.com/
* Robert Hollingsworth

====Testing====

The following list are people who are interested in participating in testing of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Andrew Turner - [http://www.geocommons.com GeoCommons] & [http://www.highearthorbit.com HighEarthOrbit]
* Daniel Kastl - [http://pggeocoder.postlbs.org/ pgGeocoder] | [http://georepublic.de Georepublic]
* Anton Patrushev - [http://pggeocoder.postlbs.org/ pgGeocoder] | [http://georepublic.de Georepublic]
* Toru Mori - [http://pggeocoder.postlbs.org/ pgGeocoder] | [http://www.orkney.co.jp Orkney]
* Stephen Woodbridge - http://imaptools.com/
* Ian Turton - [http://www.geovista.psu.edu/members/turton/index.html GeoVISTA Center ]

====Consumers====

The following list are people that plan to make use of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Dave McIlhagga - [http://wwww.dmsolutions.ca DM Solutions Group]
* Andrew Turner - [http://www.geocommons.com GeoCommons] & [http://www.highearthorbit.com HighEarthOrbit]
* Daniel Kastl - [http://pggeocoder.postlbs.org/ pgGeocoder] | [http://georepublic.de Georepublic]
* Anton Patrushev - [http://pggeocoder.postlbs.org/ pgGeocoder] | [http://georepublic.de Georepublic]
* Toru Mori - [http://pggeocoder.postlbs.org/ pgGeocoder] | [http://www.orkney.co.jp Orkney]
* Stephen Woodbridge - http://imaptools.com/
* V.Ravi Kumar - OSGeo India
* Yves Jacolin - OSGeo-fr, Camptocamp
* Ian Turton - [http://www.geovista.psu.edu/members/turton/index.html GeoVISTA Center ]
* David Jonglez - [http://wwww.capgemini.com Capgemini]
* Claude Philipona - [http://wwww.camptocamp.com Camptocamp]
* Cédric Moullet - [http://wwww.camptocamp.com Camptocamp]
* Robert Hollingsworth

Boston Code Sprint 2013

2012-07-14T00:48:27Z

Wiki-Woodbri: /* Participation */

[[Image:boston_codesprint_2012.png|right]]

== Purpose ==

Get together project members to make decisions and tackle larger problems (as done last year at the [[IslandWood Code Sprint 2012]]). This code sprint is targeting members of the "C Tribe" (eg, Mapserver, GRASS, GDAL, Proj, PostGIS, MapGuide, OpenLayers). Other tribes are welcome to join the sprint, of course, but we hope that "C Tribe" members will give this event special consideration.

We have started a [[Boston Sprint 2013 Agenda]] page for preliminary planning of tasks.

== Timing ==

Dates: TBD (March 2013)
Possible options we have available
Duration: Four days (9AM - 4PM)

'''Weekday options run Monday - Thursday''': 3/4, 3/11, 3/18, 3/25

'''Weekend options run Thursday - Sunday''': 2/28, 3/7, 3/14, 3/21

== Venue ==
Downtown Boston we have 2 options going across the street from each other.
Both locations are across the street from Boston City Hall.

=== Weekend Access ===

== Sponsors ==
We have three sponsorship levels:

* Gold: >$2000
* Silver: $1500
* Bronze: $750

We will again be looking for sponsors ($750+) to support food and fun for the sprinters as they work hard and play hard for four productive days. Each sponsorship will be put towards lunch and dinner costs for the sprinters, and potentially bringing in sprinters who might otherwise be unable to attend.

To sponsor, please contact Leo Hsu and Regina Obe (lr at pcorp dot us) directly regarding sponsorship and level of sponsorship you'd like to provide

=== 2013 Sponsors ===
This is the current list of those who have pledged
''Bronze''
# Flaxen Consulting
# Azavea

== Budget ==

== Hotel ==

== Costs ==

Participants should plan for the following costs:

* Travel to Boston, variable depending on where you are.
* Accommodation for four nights, $300 to $600 depending on what room you choose and whether you room share.
* Breakfast, dinner and other snacks.
* The sponsorship moneys will be put towards: morning snacks, lunches, dinner (1), social event (?), and supporting

== Communication ==

* Please join the mailing list: http://lists.osgeo.org/mailman/listinfo/tosprint

* IRC chat during the event: Channel: #tosprint Server: irc.freenode.net

== Participation ==

We are planning for attendance of 20-40. Please add your name and the projects you are hoping to sprint on, if you have a strong intention to attend.

# Leo Hsu (Definite) PostGIS 3/25, 3/18, 3/11, any
# Regina Obe (Definite) PostGIS 3/25, 3/18, 3/11, any
# Michael Smith - US Army Corps - MapServer; PDAL; GDAL/OGR - Will definitely be here
# Daniel Morissette - Mapgears - MapServer; GDAL/OGR - 99.72% sure
# Pierre Racine - University Laval - PostGIS Raster - Possible
# Paul Ramsey - PostGIS - 3/4, 3/25, 2/28
# Michael P. Gerlek - Flaxen Consulting - PDAL & Friends - very likely - "ANY"
# Frank Warmerdam - Google - GDAL; MapServer; PROJ.4 - Possible
# Tom Kralidis - MapServer, pycsw, owslib - Possible
# Mike Rosen - LizardTech - PDAL, GDAL - likely
# Thomas Bonfort - Terriscope - MapServer - very likely - "any"
# Olivier Courtin - Oslandia - MapServer ; PostGIS - 2/28, any
# [[User:Dzwarg|David Zwarg]] - Azavea - PostGIS Raster; GDAL/OGR - 99.73% sure, any
# [[User:kirk|Kirk McKelvey]] - LizardTech - PDAL/GDAL - likely, 3/4, 3/18, 3/25
# Jim Klassen - SharedGeo - likely
# Howard Butler - Hobu, Inc. - very likely, any
# Bborie Park - CVEC, UC Davis - PostGIS Raster - likely, any
# Steve Lime - MapServer - very likely - 3/4, 3/18, 3/25
# [[User:Woodbri|Steve Woodbridge]] - iMaptools.com - MapServer; pgRouting; postGIS - very likely, any
Virtual participants (irc #tosprint)

== Room Share ==

If you would like to room share,

# Reserve a room at the hotel, choosing a type with more than one bed.
# Put your name in this section, indicating the amount of space in your room.

Put your names below:

* example entry: B has a triple room, needs two roommates.

== Individual Preparation ==

* Bring your own computer
* Install subversion and the compiler tools, and come with a working development environment if possible.

== FAQ ==

* Is the Boston Code Sprint just a coding event?
** Yes, a coding and documentation event. It is a working session for people who are already participants in open source projects.
* Will it be possible to present new projects during this event?
** No, this is not a presentation-oriented event. People will get together in small groups and work on areas of mutual interest within their projects.
* Will there be presentation time to show case innovative uses of technology?
** Yes, Sponsors and sprinters actively working on projects will have their moment of glory

== Social Events ==

== Eating Options ==
== Lunch ==
[http://www.samlagrassas.com/home.php Sam LaGrassa]

== Dinner ==
Dim Sum - China Pearl - Boston Down town Chinatown

Korean Barbecue Boston Chinatown

Various locations in North End for good Home Italian cooking and pastries

Irish Pubs

== Getting to the Sprint ==

== Recaps ==

=== Photos ===

[[Category:Code Sprints]]
[[Category:Past Events]]

Boston Code Sprint 2013

2012-07-14T00:46:59Z

Wiki-Woodbri: /* Participation */

[[Image:boston_codesprint_2012.png|right]]

== Purpose ==

Get together project members to make decisions and tackle larger problems (as done last year at the [[IslandWood Code Sprint 2012]]). This code sprint is targeting members of the "C Tribe" (eg, Mapserver, GRASS, GDAL, Proj, PostGIS, MapGuide, OpenLayers). Other tribes are welcome to join the sprint, of course, but we hope that "C Tribe" members will give this event special consideration.

We have started a [[Boston Sprint 2013 Agenda]] page for preliminary planning of tasks.

== Timing ==

Dates: TBD (March 2013)
Possible options we have available
Duration: Four days (9AM - 4PM)

'''Weekday options run Monday - Thursday''': 3/4, 3/11, 3/18, 3/25

'''Weekend options run Thursday - Sunday''': 2/28, 3/7, 3/14, 3/21

== Venue ==
Downtown Boston we have 2 options going across the street from each other.
Both locations are across the street from Boston City Hall.

=== Weekend Access ===

== Sponsors ==
We have three sponsorship levels:

* Gold: >$2000
* Silver: $1500
* Bronze: $750

We will again be looking for sponsors ($750+) to support food and fun for the sprinters as they work hard and play hard for four productive days. Each sponsorship will be put towards lunch and dinner costs for the sprinters, and potentially bringing in sprinters who might otherwise be unable to attend.

To sponsor, please contact Leo Hsu and Regina Obe (lr at pcorp dot us) directly regarding sponsorship and level of sponsorship you'd like to provide

=== 2013 Sponsors ===
This is the current list of those who have pledged
''Bronze''
# Flaxen Consulting
# Azavea

== Budget ==

== Hotel ==

== Costs ==

Participants should plan for the following costs:

* Travel to Boston, variable depending on where you are.
* Accommodation for four nights, $300 to $600 depending on what room you choose and whether you room share.
* Breakfast, dinner and other snacks.
* The sponsorship moneys will be put towards: morning snacks, lunches, dinner (1), social event (?), and supporting

== Communication ==

* Please join the mailing list: http://lists.osgeo.org/mailman/listinfo/tosprint

* IRC chat during the event: Channel: #tosprint Server: irc.freenode.net

== Participation ==

We are planning for attendance of 20-40. Please add your name and the projects you are hoping to sprint on, if you have a strong intention to attend.

# Leo Hsu (Definite) PostGIS 3/25, 3/18, 3/11, any
# Regina Obe (Definite) PostGIS 3/25, 3/18, 3/11, any
# Michael Smith - US Army Corps - MapServer; PDAL; GDAL/OGR - Will definitely be here
# Daniel Morissette - Mapgears - MapServer; GDAL/OGR - 99.72% sure
# Pierre Racine - University Laval - PostGIS Raster - Possible
# Paul Ramsey - PostGIS - 3/4, 3/25, 2/28
# Michael P. Gerlek - Flaxen Consulting - PDAL & Friends - very likely - "ANY"
# Frank Warmerdam - Google - GDAL; MapServer; PROJ.4 - Possible
# Tom Kralidis - MapServer, pycsw, owslib - Possible
# Mike Rosen - LizardTech - PDAL, GDAL - likely
# Thomas Bonfort - Terriscope - MapServer - very likely - "any"
# Olivier Courtin - Oslandia - MapServer ; PostGIS - 2/28, any
# [[User:Dzwarg|David Zwarg]] - Azavea - PostGIS Raster; GDAL/OGR - 99.73% sure, any
# [[User:kirk|Kirk McKelvey]] - LizardTech - PDAL/GDAL - likely, 3/4, 3/18, 3/25
# Jim Klassen - SharedGeo - likely
# Howard Butler - Hobu, Inc. - very likely, any
# Bborie Park - CVEC, UC Davis - PostGIS Raster - likely, any
# Steve Lime - MapServer - very likely - 3/4, 3/18, 3/25
# [[User:Woodbri|Steve Woodbridge]] - MapServer - pgRouting - postGIS - very likely, any
Virtual participants (irc #tosprint)

== Room Share ==

If you would like to room share,

# Reserve a room at the hotel, choosing a type with more than one bed.
# Put your name in this section, indicating the amount of space in your room.

Put your names below:

* example entry: B has a triple room, needs two roommates.

== Individual Preparation ==

* Bring your own computer
* Install subversion and the compiler tools, and come with a working development environment if possible.

== FAQ ==

* Is the Boston Code Sprint just a coding event?
** Yes, a coding and documentation event. It is a working session for people who are already participants in open source projects.
* Will it be possible to present new projects during this event?
** No, this is not a presentation-oriented event. People will get together in small groups and work on areas of mutual interest within their projects.
* Will there be presentation time to show case innovative uses of technology?
** Yes, Sponsors and sprinters actively working on projects will have their moment of glory

== Social Events ==

== Eating Options ==
== Lunch ==
[http://www.samlagrassas.com/home.php Sam LaGrassa]

== Dinner ==
Dim Sum - China Pearl - Boston Down town Chinatown

Korean Barbecue Boston Chinatown

Various locations in North End for good Home Italian cooking and pastries

Irish Pubs

== Getting to the Sprint ==

== Recaps ==

=== Photos ===

[[Category:Code Sprints]]
[[Category:Past Events]]

OSGeo Advocate

2012-06-29T01:02:23Z

Wiki-Woodbri: /* United States */

__FORCETOC__

= Introduction =

OSGeo Advocates are authoritative OSGeo personalities who have volunteered to talk on behalf of the [http://osgeo.org OSGeo foundation]. Advocates should be able to speak well, even better if they are entertaining.

There are hundreds, if not thousands of conferences around the world which have an interest in seeing presentations from authoritative speakers, with deep insights into topics related to Open Source Geospatial Software. Luckily, OSGeo is fortunate to draw extensive membership from around the world, and has access to such authoritative figures within most countries.

= OSGeo Advocates =
This section lists current OSGeo Advocates:

== Australia ==
{{User:camerons}}

{{User:jive}}

== Europe ==
{{User:Arnulf Christl}}

{{User:Ticheler}}

{{User:Jsanz}}

{{User:Vehrka}}

{{User:JoCook}}

{{User:Kalxas}}

{{User:Ianturton}}

{{User:Aghisla}}

{{User:volaya}}

{{User:Lluís}}

{{User:ArArgyridis}}

{{User:grizonnetm}}

{{User:Astrid_Emde}}

== Canada ==
{{User:Gzeiss}}

== United States ==
{{User:Alex Mandel}}
{{User:Woodbri}}

== Latin America ==
{{User:Aborrell}}

= Past OSGeo Advocates =
This section lists prior listed Advocates who have not recently updated their profiles.

= Understanding OSGeo roles =

Below is an explanation of roles which Advocates might have been involved in as part of OSGeo:

====[[File:OSGeo_board.png]] [[File:OSGeo_exboard.png]] OSGeo Board Members====
: We only have 8 active board members in the world, which have been peer selected based upon their outstanding leadership in the greater OSGeo community.

====[[File:OSGeo_charter.png]] OSGeo Charter Members====
: Charter membership is obtained through a strongly contested selection process. Members tend to be developers and leaders in one or more OSGeo projects, and/or OSGeo business leaders, and have a deep understanding in many of the OSGeo projects and principles of Open Source.

====[[File:OSGeo_chair.png]] [[File:OSGeo_psc.png]] Voted position in an OSGeo community====
: These people hold a position of responsibility within one of the OSGeo sub-communities. This may be a chair of an OSGeo committee or Regional Chapter, or as a member of a project's Project Steering Committee (PSC).

====[[File:OSGeo_coder.png]] [[File:OSGeo_committee.png]] Developers and Committee Members====
: This is where the real work gets done developing and coordinating development of OSGeo Software.

====[[File:OSGeo_user.png]] OSGeo Community Members====
: These people are actively involved in one or more OSGeo communities, acting as practitioners, users, promoters or supporters of OSGeo software. These people tend to have a practical understanding about how OSGeo software works.

= Process for becoming an OSGeo Advocate =

Anyone fitting one of the [[OSGeo_Advocate#Understanding_OSGeo_roles|OSGeo Advocate categories]], may put themselves forward as an OSGeo Advocate. To do so, you will need to:
* Create an OSGeo wiki account, to edit this wiki (See "login" link in top right of this page).
* Create a new wiki page http://wiki.osgeo.org/wiki/User:YourOSGeoWikiUserName, and populate as per [[User:Template]], (copy and paste from the [http://wiki.osgeo.org/index.php?title=User:Template&action=edit source] so that you see comments in the template).
* You can then add your profile on [[OSGeo_Advocate#OSGeo_Advocates|this wiki page]], under your Country, using the following:
{{User:<YourOSGeoWikiUserName>}}

= Annual Refresh of Advocate list =
* The list of OSGeo Advocates will be refreshed annually, after the annual voting of OSGeo Charter Members. This will be achieved by removing lapsed Advocates, then moving all Current Advocates into the Past Advocate section. All Advocates will be invited to update their profile, and move their profile back into the current Advocates section.

= Other Resources =
Links to other organizations running a similar process.
* http://www.ogcnetwork.net/node/1585

User:Woodbri

2012-06-29T00:59:55Z

Wiki-Woodbri: /* Stephen Woodbridge */

===Stephen Woodbridge===

[[File:Stephen.woodbridge.jpg|thumb|right|100px|Stephen Woodbridge]]

Owner,[http://imaptools.com/ iMaptools.com]

Location: North Chelmsford, MA, USA

Stephen works with Mapserver, pgRouting, PAGC Geocoder, GDAL/OGR, OpenLayers as well as other open source products. Stephen can be found at [http://iMapTools.com/ iMapTools.com] where he provides geospatial products, consulting and advocates [http://osgeo.org/ OSGeo] and OpenSource products to his clients.

[http://swoodbridge.com/?id=3 Resume.]
[http://www.linkedin.com/pub/stephen-woodbridge/18/bb0/284 LinkedIn Profile.]

;OSGeo Experience [[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]][[File:OSGeo_psc.png|link=OSGeo_Advocate#Voted_position_in_an_OSGeo_community]][[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]][[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]]

:
:* Member of the [http://mapserver.org/ Mapserver] PSC and an active user. Stephen constructs mapfiles for clients and works with clients to manage their production environments that collectively serve billions map draws per year.
:* Member of the [http://www.pgrouting.org/ pgRouting] PSC and an active user and developer. Stephen prepares client data for use with pgRouting and has developed driving directions module, mentored three years of GSoC students developing for pgRouting.
:* Member of the [http://www.pagcgeo.org/ PAGC] (Postal Address Geocoder) PSC and an active user. Stephen also works witht he developer to refactor the code, and actively supports it with testing and bug fixes and minor enhancements.
:* A knowledgeable user of [http://www.gdal.org/ GDAL/OGR] and [http://openlayers.org/ OpenLayers] as well as other OpenSource projects.

;Contact:
: Email: woodbri AT swoodbridge DOT com
: Phone (work): 1-978-251-4502
: Skype: stephen.woodbridge

;Spoken Language(s): English

;Profile last updated: 28 JUNE 2012

File:Stephen.woodbridge.jpg

2012-06-29T00:58:47Z

Wiki-Woodbri: Stephen Woodbridge

Stephen Woodbridge

User:Woodbri

2012-06-29T00:55:01Z

Wiki-Woodbri: /* Stephen Woodbridge */

===Stephen Woodbridge===

[[File:OSGeo_compass300.png|thumb|right|100px|Stephen Woodbridge]]

Owner,[http://imaptools.com/ iMaptools.com]

Location: North Chelmsford, MA, USA

Stephen works with Mapserver, pgRouting, PAGC Geocoder, GDAL/OGR, OpenLayers as well as other open source products. Stephen can be found at [http://iMapTools.com/ iMapTools.com] where he provides geospatial products, consulting and advocates [http://osgeo.org/ OSGeo] and OpenSource products to his clients.

[http://swoodbridge.com/?id=3 Resume.]
[http://www.linkedin.com/pub/stephen-woodbridge/18/bb0/284 LinkedIn Profile.]

;OSGeo Experience [[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]][[File:OSGeo_psc.png|link=OSGeo_Advocate#Voted_position_in_an_OSGeo_community]][[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]][[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]]

:
:* Member of the [http://mapserver.org/ Mapserver] PSC and an active user. Stephen constructs mapfiles for clients and works with clients to manage their production environments that collectively serve billions map draws per year.
:* Member of the [http://www.pgrouting.org/ pgRouting] PSC and an active user and developer. Stephen prepares client data for use with pgRouting and has developed driving directions module, mentored three years of GSoC students developing for pgRouting.
:* Member of the [http://www.pagcgeo.org/ PAGC] (Postal Address Geocoder) PSC and an active user. Stephen also works witht he developer to refactor the code, and actively supports it with testing and bug fixes and minor enhancements.
:* A knowledgeable user of [http://www.gdal.org/ GDAL/OGR] and [http://openlayers.org/ OpenLayers] as well as other OpenSource projects.

;Contact:
: Email: woodbri AT swoodbridge DOT com
: Phone (work): 1-978-251-4502
: Skype: stephen.woodbridge

;Spoken Language(s): English

;Profile last updated: 28 JUNE 2012

User:Woodbri

2012-06-29T00:54:28Z

Wiki-Woodbri:

===Stephen Woodbridge===

[[File:OSGeo_compass300.png|thumb|right|100px|Stephen Woodbridge]]

Owner,[http://imaptools.com/ iMaptools.com]

Location: North Chelmsford, MA, USA

Stephen works with Mapserver, pgRouting, PAGC Geocoder, GDAL/OGR, OpenLayers as well as other open source products. Stephen can be found at [http://iMapTools.com/ iMapTools.com] where he provides geospatial products, consulting and advocates [http://osgeo.org/ OSGeo] and OpenSource products to his clients.

[http://swoodbridge.com/?id=3 Resume.]
[http://www.linkedin.com/pub/stephen-woodbridge/18/bb0/284 LinkedIn Profile.]

;OSGeo Experience [[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]][[File:OSGeo_psc.png|link=OSGeo_Advocate#Voted_position_in_an_OSGeo_community]]][[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]][[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]]

:
:* Member of the [http://mapserver.org/ Mapserver] PSC and an active user. Stephen constructs mapfiles for clients and works with clients to manage their production environments that collectively serve billions map draws per year.
:* Member of the [http://www.pgrouting.org/ pgRouting] PSC and an active user and developer. Stephen prepares client data for use with pgRouting and has developed driving directions module, mentored three years of GSoC students developing for pgRouting.
:* Member of the [http://www.pagcgeo.org/ PAGC] (Postal Address Geocoder) PSC and an active user. Stephen also works witht he developer to refactor the code, and actively supports it with testing and bug fixes and minor enhancements.
:* A knowledgeable user of [http://www.gdal.org/ GDAL/OGR] and [http://openlayers.org/ OpenLayers] as well as other OpenSource projects.

;Contact:
: Email: woodbri AT swoodbridge DOT com
: Phone (work): 1-978-251-4502
: Skype: stephen.woodbridge

;Spoken Language(s): English

;Profile last updated: 28 JUNE 2012

User:Woodbri

2011-11-17T14:51:56Z

Wiki-Woodbri:

Stephen Woodbridge is a member of the [http://mapserver.org/ Mapserver] PSC, [http://www.pgrouting.org/ pgRouting] PSC, [http://www.pagcgeo.org/ PAGC] (Postal Address Geocoder) PSC and works with many of the OSGeo products like [http://mapserver.org/ Mapserver], [http://www.gdal.org/ GDAL/OGR] and [http://openlayers.org/ OpenLayers] as well as other OpenSource projects. Stephen can be found at [http://iMapTools.com/ iMapTools.com] where he provides geospatial products, consulting and advocates [http://osgeo.org/ OSGeo] and OpenSource products to his clients.

FOSS4G 2011 Breakout Sessions

2011-09-13T00:30:17Z

Wiki-Woodbri: /* SpatiaLite */

= Introduction =
During the [http://2011.foss4g.org/ FOSS4G2011 conference] in Denver, there will be conference rooms available for people to hold Breakout Sessions (aka Birds-of-a-Feather).

Breakout Sessions are unstructured timeslots where people can self-organize themselves to discuss topics of interest.

'''Room allocation to be determined'''

== Organising Contact ==

== Timeslots Available ==

Wednesday 5:30pm to 6:30pm and 7:00pm to 8:00pm

= Room Assignments =

== Rooms Available ==
All rooms can hold 50+ people, some are a bit larger as noted below. Amount of room may vary depending on seating arrangement and size of group. If you need a larger space for your group, use the ballroom. If you need a smaller separate room for one group, use Denver, Spruce, or Century. At the venue, please check the room size to confirm it's what you want.

Pick a room, add to '''reserved:#''' beside room name below and mention the room name in your planning section further down on the page.

Tower Court A - 50+ (2 groups) - '''Reserved: 0/2'''
Tower Court B - 50+ (2 groups) - '''Reserved: 0/2'''
Tower Court C - 50+ (2 groups) - '''Reserved: 0/2'''
Tower Court D - 75+ (2 groups) - '''Reserved: 0/2'''
Windows - 125+ people (2-4 groups) - '''Reserved: 0/4'''
Silver - 100+ people (2-3 groups) - '''Reserved: 0/3'''
<s>Denver - 1 group - '''Reserved: 1/1'''</s>
Spruce - 1 group - '''Reserved: 0/1'''
Century - 1 group - '''Reserved: 0/1'''
'''Grand Ballroom''' - huge, can fit 10+ groups - '''Reserved: 0/10'''

= Proposed Topics =

== GeoMoose ==

*Scheduling:
**5:30 - 6:30, With get together afterwards. Any suggestions for a location for Drinks afterwards?
*Proposed Topics
**Overview
**GeoMoose 2.6
**Ideas for CodeSprint.
**Talk up your successes with GeoMoose.
**Meet developers and learn how you can help.
*Attending:
**Bob Basques (City of Saint Paul, MN.)
**Dan Little (GeoMoose)
**Jim Klassen (SharedGeo)
**Brian Fischer (Houston Engineering)
**[[User:EliL|Eli Adam (Lincoln County, Oregon)]]
**Steve Swazee (MnGeo Emergency Preparedness Committee)

== Tiling ==

*Proposed Topics
**standardised sqlite schema for tile caches
**TMS/WMTS evolutions:
***Tile merging (i.e. equivalent of WMS LAYERS=baselayer,overlaylayer)
***TMS multiple grids per tileset
***WMTS multiple url endpoints (eg tile1.domain.tld, tile2.domain.tld...): is this still needed now that browsers allow many more connections per server?
**add yours...
*Attending:
**[[User:Tbonfort]]
**[[User:Olt|Oliver Tonnhofer (Omniscale, MapProxy)]]
**[[User:Stvn|Steven M. Ottens]]
**[[User:Lagerratrobe|Roger Andre (Tableau Software, Seattle)]]
**[[User:Springmeyer|Dane Springmeyer (Development Seed)]]
**[[User:Mloskot|Mateusz Loskot (Cadcorp)]]
**Brian Fischer (Houston Engineering)
**[[User:woodbri|Stephen Woodbridge (iMaptools.com)]]

== GeoNode ==

*Proposed topics:
**Brief overview
**Get involved with the community!
**Meet developers and institutional partners
***Opportunities for work around the world, especially in South America and Indonesia
***Positions available at the World Bank and OpenGeo
**[http://geonode.org/2011/08/geonode-at-foss4g/ Join us for drinks afterwards!]
*Attending:
**Rolando Peñate (OpenGeo)
**David Winslow (OpenGeo)
**Robert Soden (World Bank)
**Ariel Nuñez (World Bank)
**Seb Benthall (UC Berkeley)
**Ben Lewis(Harvard University)
**Matt Bertrand (Harvard University)
**Sachindra Singh (SOPAC)
**[[User:Ortelius|Jeffrey Johnson (OpenGeo)]]
**Jubal Harpster (SpatialDev)
**[[User:Ebwolf|Eric Wolf (USGS, CU-Boulder)]]
**[[User:Wildintellect|Alex Mandel (UC Davis)]]
**[[User:Assefa|Yewondwossen Assefa (DM Solutions)]]
**[[User:epifanio|Massimo Di Stefano (RPI - WHOI)]]
**Christian Spanring (MAPC)

== Python ==

*Scheduling: let's do this one in the 5:30-6:30 slot and tiling afterwards?
*Proposed topics:
**High fives
**Extension modules, Pyrex, Cython, ctypes
**Python 3
**PyPy
**Packaging and distributions
*Attending:
**Sean Gillies (NYU, Shapely and friends)
**[[User:Ebwolf|Eric Wolf (USGS, CU-Boulder)]]
**Michael Weisman (Urban Mapping)
**Derek Hohls (CSIR, South Africa)
**[[User:Dandye|Dan Dye (WeoGeo)]]
**[[User:Davidfawcett|David Fawcett (MPCA)]]
**[[User:Wildintellect|Alex Mandel (UC Davis)]]
**[[User:Hobu|Howard Butler (Hobu, Inc.)]]
**[[User:Olt|Oliver Tonnhofer (Omniscale)]] MapProxy, Imposm, Shapely, etc. I'm in conflict with the tiling BOF, try to come for the high five at least.
**Marc Pfister (nothing to see here)
**[[User:Lagerratrobe|Roger Andre (Tableau Software, Seattle)]]
**Thomas Emge (Esri)
**Alan Boudreault (Mapgears)
**[[User:jlhgis|Julia Harrell (NC DENR)]]
**Jachym Cepicky
**[[User:epifanio|Massimo Di Stefano (RPI-WHOI)]]

== Opengeoportal ==

http://opengeoportal.org/

*Proposed topics: governance models, federated searching and coordinating code development
*Attending:
**Stephen McDonald (Tufts)
**Patrick Florance (Tufts)
**Chris Barnett (Tufts)
**David Siegel (Harvard)
**[[User:Lsweeney|Lisa Sweeney (MIT)]]
**Garey Mills (Berkeley)
**John Ridener (Berkeley)
**Patricia Carbajales (Stanford)
**Renzo Sanchez-Silva (Stanford)
**Karel Charvat (CCSS)
**[[User:epifanio|Massimo Di Stefano (RPI - WHOI)]]

* There will also be a gathering for developers to meet during the Tuesday evening Welcome Social at the Wynkoop Brewing Company.

== Spatial Data InfraStructure (SDI) ==

*Scheduling: 7pm - 8pm. Get started with these topics then go get some food/drinks together.
*Proposed topics: data sharing and discovery, metadata, web services, and portals.
*Attending:
**Christine White (Esri)
**Andy Gup (Esri)
**Karel Charvat (CCSS)

== Mobile GIS ==

*Proposed Topics
**General discussion about development of mobile mapping/GIS apps
**"OpenLayers-like" SDK for Android (Android GIS)
**add yours...
*Attending:
**[[User:Danielkastl|Daniel Kastl (Georepublic)]]
**[[User:Hal sk|Haruyuki Seki (Georepublic)]]
**Jaak Laineste (Nutiteq)
**[[User:Dmorissette| Daniel Morissette (Mapgears)]]
**Alan Boudreault (Mapgears)
**[[User:Mloskot|Mateusz Loskot (Cadcorp)]]
**[[User:Assefa|Yewondwossen Assefa (DM Solutions)]]
**Karel Charvat (CCSS)
**[[User:woodbri|Stephen Woodbridge (iMaptools.com)]]

== Education / Academic ==
* '''Room: Denver - 5:30-7'''
* Separate sign up page: [[FOSS4G 2011 Edu BOF sign up]]

== Spatial Databases ==

*Proposed Topics
**Do we need some more
**Where are we heading to (distributed databases?)
**Do the processing within the database or outside?
**Add yours...
*Attending:
**Volker Mische (Couchbase)

== SpatiaLite ==

*Scheduling: let's not conflict with the Python session? maybe we should do something less formal another day if the BOF all conflict too much?
*Proposed topics:
**Community organization strategies
**Meet and Greet

*Attending:
**[[User:Davidfawcett|David Fawcett (MPCA)]]
**[[User:putler|Dan Putler (Anemoi Analytics)]]
**[[User:wildintellect|Alex Mandel (UC Davis)]]
**[[User:dnewcomb|Doug Newcomb (USFWS)]] ( I will not be available for much of Wed. Evening)
**[[User:jlhgis|Julia Harrell (NC DENR)]]
**[[User:woodbri|Stephen Woodbridge (iMaptools.com)]]

== Web Processing Services (WPS) ==

*Scheduling: 5:30-6:30

*Proposed topics:
** Web Processing Services Ideas exchange and get-together
** WPS 2.0 status and community input
** Meet and Greet

*Attending:
** Gėrald Fenoy (ZOO-Project)
** Nicolas Bozon (ZOO-Project)
** Bastian Schäffer (52North)
** Benjamin Pross (52North)
** Jachym Cepicky

== Free meditation and relaxing movements sessions ==

There are so many interesting people and ideas at FOSS4G that I’ve found it can be really helpful to have a quiet, meditative moment or two to let it all sink in. The intention is to help one release stress and relax muscles that commonly become tight from computer/desk work, travel, carrying bags.. the common issues that tend to manifest at a week-long conference! I’ve been leading meditation sessions for co-workers at MIT and receiving very positive feedback about how helpful they are.

My plan is to hold a few 30-minute, sessions of relaxed meditative breathing and gentle movements during the FOSS4G conference at the following times:

*Wed. 8 pm
*Thurs 5:30 pm
*Friday 5 pm - after the Annual General Meeting

These sessions are available to anyone, including people with no prior experience with any movement styles, those who do not feel particularly flexible, and folks who are in their work/meeting clothes. These sessions are being hosted by [[User:Lsweeney|Lisa Sweeney]] If you are interested please add your name below. I'll be seeking out room options and post them to this wiki page once identified.

== Add yours below ==

[[Category:FOSS4G]] [[Category:FOSS4G2011]]

FOSS4G 2011 Breakout Sessions

2011-09-13T00:29:44Z

Wiki-Woodbri: /* Mobile GIS */

= Introduction =
During the [http://2011.foss4g.org/ FOSS4G2011 conference] in Denver, there will be conference rooms available for people to hold Breakout Sessions (aka Birds-of-a-Feather).

Breakout Sessions are unstructured timeslots where people can self-organize themselves to discuss topics of interest.

'''Room allocation to be determined'''

== Organising Contact ==

== Timeslots Available ==

Wednesday 5:30pm to 6:30pm and 7:00pm to 8:00pm

= Room Assignments =

== Rooms Available ==
All rooms can hold 50+ people, some are a bit larger as noted below. Amount of room may vary depending on seating arrangement and size of group. If you need a larger space for your group, use the ballroom. If you need a smaller separate room for one group, use Denver, Spruce, or Century. At the venue, please check the room size to confirm it's what you want.

Pick a room, add to '''reserved:#''' beside room name below and mention the room name in your planning section further down on the page.

Tower Court A - 50+ (2 groups) - '''Reserved: 0/2'''
Tower Court B - 50+ (2 groups) - '''Reserved: 0/2'''
Tower Court C - 50+ (2 groups) - '''Reserved: 0/2'''
Tower Court D - 75+ (2 groups) - '''Reserved: 0/2'''
Windows - 125+ people (2-4 groups) - '''Reserved: 0/4'''
Silver - 100+ people (2-3 groups) - '''Reserved: 0/3'''
<s>Denver - 1 group - '''Reserved: 1/1'''</s>
Spruce - 1 group - '''Reserved: 0/1'''
Century - 1 group - '''Reserved: 0/1'''
'''Grand Ballroom''' - huge, can fit 10+ groups - '''Reserved: 0/10'''

= Proposed Topics =

== GeoMoose ==

*Scheduling:
**5:30 - 6:30, With get together afterwards. Any suggestions for a location for Drinks afterwards?
*Proposed Topics
**Overview
**GeoMoose 2.6
**Ideas for CodeSprint.
**Talk up your successes with GeoMoose.
**Meet developers and learn how you can help.
*Attending:
**Bob Basques (City of Saint Paul, MN.)
**Dan Little (GeoMoose)
**Jim Klassen (SharedGeo)
**Brian Fischer (Houston Engineering)
**[[User:EliL|Eli Adam (Lincoln County, Oregon)]]
**Steve Swazee (MnGeo Emergency Preparedness Committee)

== Tiling ==

*Proposed Topics
**standardised sqlite schema for tile caches
**TMS/WMTS evolutions:
***Tile merging (i.e. equivalent of WMS LAYERS=baselayer,overlaylayer)
***TMS multiple grids per tileset
***WMTS multiple url endpoints (eg tile1.domain.tld, tile2.domain.tld...): is this still needed now that browsers allow many more connections per server?
**add yours...
*Attending:
**[[User:Tbonfort]]
**[[User:Olt|Oliver Tonnhofer (Omniscale, MapProxy)]]
**[[User:Stvn|Steven M. Ottens]]
**[[User:Lagerratrobe|Roger Andre (Tableau Software, Seattle)]]
**[[User:Springmeyer|Dane Springmeyer (Development Seed)]]
**[[User:Mloskot|Mateusz Loskot (Cadcorp)]]
**Brian Fischer (Houston Engineering)
**[[User:woodbri|Stephen Woodbridge (iMaptools.com)]]

== GeoNode ==

*Proposed topics:
**Brief overview
**Get involved with the community!
**Meet developers and institutional partners
***Opportunities for work around the world, especially in South America and Indonesia
***Positions available at the World Bank and OpenGeo
**[http://geonode.org/2011/08/geonode-at-foss4g/ Join us for drinks afterwards!]
*Attending:
**Rolando Peñate (OpenGeo)
**David Winslow (OpenGeo)
**Robert Soden (World Bank)
**Ariel Nuñez (World Bank)
**Seb Benthall (UC Berkeley)
**Ben Lewis(Harvard University)
**Matt Bertrand (Harvard University)
**Sachindra Singh (SOPAC)
**[[User:Ortelius|Jeffrey Johnson (OpenGeo)]]
**Jubal Harpster (SpatialDev)
**[[User:Ebwolf|Eric Wolf (USGS, CU-Boulder)]]
**[[User:Wildintellect|Alex Mandel (UC Davis)]]
**[[User:Assefa|Yewondwossen Assefa (DM Solutions)]]
**[[User:epifanio|Massimo Di Stefano (RPI - WHOI)]]
**Christian Spanring (MAPC)

== Python ==

*Scheduling: let's do this one in the 5:30-6:30 slot and tiling afterwards?
*Proposed topics:
**High fives
**Extension modules, Pyrex, Cython, ctypes
**Python 3
**PyPy
**Packaging and distributions
*Attending:
**Sean Gillies (NYU, Shapely and friends)
**[[User:Ebwolf|Eric Wolf (USGS, CU-Boulder)]]
**Michael Weisman (Urban Mapping)
**Derek Hohls (CSIR, South Africa)
**[[User:Dandye|Dan Dye (WeoGeo)]]
**[[User:Davidfawcett|David Fawcett (MPCA)]]
**[[User:Wildintellect|Alex Mandel (UC Davis)]]
**[[User:Hobu|Howard Butler (Hobu, Inc.)]]
**[[User:Olt|Oliver Tonnhofer (Omniscale)]] MapProxy, Imposm, Shapely, etc. I'm in conflict with the tiling BOF, try to come for the high five at least.
**Marc Pfister (nothing to see here)
**[[User:Lagerratrobe|Roger Andre (Tableau Software, Seattle)]]
**Thomas Emge (Esri)
**Alan Boudreault (Mapgears)
**[[User:jlhgis|Julia Harrell (NC DENR)]]
**Jachym Cepicky
**[[User:epifanio|Massimo Di Stefano (RPI-WHOI)]]

== Opengeoportal ==

http://opengeoportal.org/

*Proposed topics: governance models, federated searching and coordinating code development
*Attending:
**Stephen McDonald (Tufts)
**Patrick Florance (Tufts)
**Chris Barnett (Tufts)
**David Siegel (Harvard)
**[[User:Lsweeney|Lisa Sweeney (MIT)]]
**Garey Mills (Berkeley)
**John Ridener (Berkeley)
**Patricia Carbajales (Stanford)
**Renzo Sanchez-Silva (Stanford)
**Karel Charvat (CCSS)
**[[User:epifanio|Massimo Di Stefano (RPI - WHOI)]]

* There will also be a gathering for developers to meet during the Tuesday evening Welcome Social at the Wynkoop Brewing Company.

== Spatial Data InfraStructure (SDI) ==

*Scheduling: 7pm - 8pm. Get started with these topics then go get some food/drinks together.
*Proposed topics: data sharing and discovery, metadata, web services, and portals.
*Attending:
**Christine White (Esri)
**Andy Gup (Esri)
**Karel Charvat (CCSS)

== Mobile GIS ==

*Proposed Topics
**General discussion about development of mobile mapping/GIS apps
**"OpenLayers-like" SDK for Android (Android GIS)
**add yours...
*Attending:
**[[User:Danielkastl|Daniel Kastl (Georepublic)]]
**[[User:Hal sk|Haruyuki Seki (Georepublic)]]
**Jaak Laineste (Nutiteq)
**[[User:Dmorissette| Daniel Morissette (Mapgears)]]
**Alan Boudreault (Mapgears)
**[[User:Mloskot|Mateusz Loskot (Cadcorp)]]
**[[User:Assefa|Yewondwossen Assefa (DM Solutions)]]
**Karel Charvat (CCSS)
**[[User:woodbri|Stephen Woodbridge (iMaptools.com)]]

== Education / Academic ==
* '''Room: Denver - 5:30-7'''
* Separate sign up page: [[FOSS4G 2011 Edu BOF sign up]]

== Spatial Databases ==

*Proposed Topics
**Do we need some more
**Where are we heading to (distributed databases?)
**Do the processing within the database or outside?
**Add yours...
*Attending:
**Volker Mische (Couchbase)

== SpatiaLite ==

*Scheduling: let's not conflict with the Python session? maybe we should do something less formal another day if the BOF all conflict too much?
*Proposed topics:
**Community organization strategies
**Meet and Greet

*Attending:
**[[User:Davidfawcett|David Fawcett (MPCA)]]
**[[User:putler|Dan Putler (Anemoi Analytics)]]
**[[User:wildintellect|Alex Mandel (UC Davis)]]
**[[User:dnewcomb|Doug Newcomb (USFWS)]] ( I will not be available for much of Wed. Evening)
**[[User:jlhgis|Julia Harrell (NC DENR)]]

== Web Processing Services (WPS) ==

*Scheduling: 5:30-6:30

*Proposed topics:
** Web Processing Services Ideas exchange and get-together
** WPS 2.0 status and community input
** Meet and Greet

*Attending:
** Gėrald Fenoy (ZOO-Project)
** Nicolas Bozon (ZOO-Project)
** Bastian Schäffer (52North)
** Benjamin Pross (52North)
** Jachym Cepicky

== Free meditation and relaxing movements sessions ==

There are so many interesting people and ideas at FOSS4G that I’ve found it can be really helpful to have a quiet, meditative moment or two to let it all sink in. The intention is to help one release stress and relax muscles that commonly become tight from computer/desk work, travel, carrying bags.. the common issues that tend to manifest at a week-long conference! I’ve been leading meditation sessions for co-workers at MIT and receiving very positive feedback about how helpful they are.

My plan is to hold a few 30-minute, sessions of relaxed meditative breathing and gentle movements during the FOSS4G conference at the following times:

*Wed. 8 pm
*Thurs 5:30 pm
*Friday 5 pm - after the Annual General Meeting

These sessions are available to anyone, including people with no prior experience with any movement styles, those who do not feel particularly flexible, and folks who are in their work/meeting clothes. These sessions are being hosted by [[User:Lsweeney|Lisa Sweeney]] If you are interested please add your name below. I'll be seeking out room options and post them to this wiki page once identified.

== Add yours below ==

[[Category:FOSS4G]] [[Category:FOSS4G2011]]

FOSS4G 2011 Breakout Sessions

2011-09-13T00:26:59Z

Wiki-Woodbri: /* Tiling */

= Introduction =
During the [http://2011.foss4g.org/ FOSS4G2011 conference] in Denver, there will be conference rooms available for people to hold Breakout Sessions (aka Birds-of-a-Feather).

Breakout Sessions are unstructured timeslots where people can self-organize themselves to discuss topics of interest.

'''Room allocation to be determined'''

== Organising Contact ==

== Timeslots Available ==

Wednesday 5:30pm to 6:30pm and 7:00pm to 8:00pm

= Room Assignments =

== Rooms Available ==
All rooms can hold 50+ people, some are a bit larger as noted below. Amount of room may vary depending on seating arrangement and size of group. If you need a larger space for your group, use the ballroom. If you need a smaller separate room for one group, use Denver, Spruce, or Century. At the venue, please check the room size to confirm it's what you want.

Pick a room, add to '''reserved:#''' beside room name below and mention the room name in your planning section further down on the page.

Tower Court A - 50+ (2 groups) - '''Reserved: 0/2'''
Tower Court B - 50+ (2 groups) - '''Reserved: 0/2'''
Tower Court C - 50+ (2 groups) - '''Reserved: 0/2'''
Tower Court D - 75+ (2 groups) - '''Reserved: 0/2'''
Windows - 125+ people (2-4 groups) - '''Reserved: 0/4'''
Silver - 100+ people (2-3 groups) - '''Reserved: 0/3'''
<s>Denver - 1 group - '''Reserved: 1/1'''</s>
Spruce - 1 group - '''Reserved: 0/1'''
Century - 1 group - '''Reserved: 0/1'''
'''Grand Ballroom''' - huge, can fit 10+ groups - '''Reserved: 0/10'''

= Proposed Topics =

== GeoMoose ==

*Scheduling:
**5:30 - 6:30, With get together afterwards. Any suggestions for a location for Drinks afterwards?
*Proposed Topics
**Overview
**GeoMoose 2.6
**Ideas for CodeSprint.
**Talk up your successes with GeoMoose.
**Meet developers and learn how you can help.
*Attending:
**Bob Basques (City of Saint Paul, MN.)
**Dan Little (GeoMoose)
**Jim Klassen (SharedGeo)
**Brian Fischer (Houston Engineering)
**[[User:EliL|Eli Adam (Lincoln County, Oregon)]]
**Steve Swazee (MnGeo Emergency Preparedness Committee)

== Tiling ==

*Proposed Topics
**standardised sqlite schema for tile caches
**TMS/WMTS evolutions:
***Tile merging (i.e. equivalent of WMS LAYERS=baselayer,overlaylayer)
***TMS multiple grids per tileset
***WMTS multiple url endpoints (eg tile1.domain.tld, tile2.domain.tld...): is this still needed now that browsers allow many more connections per server?
**add yours...
*Attending:
**[[User:Tbonfort]]
**[[User:Olt|Oliver Tonnhofer (Omniscale, MapProxy)]]
**[[User:Stvn|Steven M. Ottens]]
**[[User:Lagerratrobe|Roger Andre (Tableau Software, Seattle)]]
**[[User:Springmeyer|Dane Springmeyer (Development Seed)]]
**[[User:Mloskot|Mateusz Loskot (Cadcorp)]]
**Brian Fischer (Houston Engineering)
**[[User:woodbri|Stephen Woodbridge (iMaptools.com)]]

== GeoNode ==

*Proposed topics:
**Brief overview
**Get involved with the community!
**Meet developers and institutional partners
***Opportunities for work around the world, especially in South America and Indonesia
***Positions available at the World Bank and OpenGeo
**[http://geonode.org/2011/08/geonode-at-foss4g/ Join us for drinks afterwards!]
*Attending:
**Rolando Peñate (OpenGeo)
**David Winslow (OpenGeo)
**Robert Soden (World Bank)
**Ariel Nuñez (World Bank)
**Seb Benthall (UC Berkeley)
**Ben Lewis(Harvard University)
**Matt Bertrand (Harvard University)
**Sachindra Singh (SOPAC)
**[[User:Ortelius|Jeffrey Johnson (OpenGeo)]]
**Jubal Harpster (SpatialDev)
**[[User:Ebwolf|Eric Wolf (USGS, CU-Boulder)]]
**[[User:Wildintellect|Alex Mandel (UC Davis)]]
**[[User:Assefa|Yewondwossen Assefa (DM Solutions)]]
**[[User:epifanio|Massimo Di Stefano (RPI - WHOI)]]
**Christian Spanring (MAPC)

== Python ==

*Scheduling: let's do this one in the 5:30-6:30 slot and tiling afterwards?
*Proposed topics:
**High fives
**Extension modules, Pyrex, Cython, ctypes
**Python 3
**PyPy
**Packaging and distributions
*Attending:
**Sean Gillies (NYU, Shapely and friends)
**[[User:Ebwolf|Eric Wolf (USGS, CU-Boulder)]]
**Michael Weisman (Urban Mapping)
**Derek Hohls (CSIR, South Africa)
**[[User:Dandye|Dan Dye (WeoGeo)]]
**[[User:Davidfawcett|David Fawcett (MPCA)]]
**[[User:Wildintellect|Alex Mandel (UC Davis)]]
**[[User:Hobu|Howard Butler (Hobu, Inc.)]]
**[[User:Olt|Oliver Tonnhofer (Omniscale)]] MapProxy, Imposm, Shapely, etc. I'm in conflict with the tiling BOF, try to come for the high five at least.
**Marc Pfister (nothing to see here)
**[[User:Lagerratrobe|Roger Andre (Tableau Software, Seattle)]]
**Thomas Emge (Esri)
**Alan Boudreault (Mapgears)
**[[User:jlhgis|Julia Harrell (NC DENR)]]
**Jachym Cepicky
**[[User:epifanio|Massimo Di Stefano (RPI-WHOI)]]

== Opengeoportal ==

http://opengeoportal.org/

*Proposed topics: governance models, federated searching and coordinating code development
*Attending:
**Stephen McDonald (Tufts)
**Patrick Florance (Tufts)
**Chris Barnett (Tufts)
**David Siegel (Harvard)
**[[User:Lsweeney|Lisa Sweeney (MIT)]]
**Garey Mills (Berkeley)
**John Ridener (Berkeley)
**Patricia Carbajales (Stanford)
**Renzo Sanchez-Silva (Stanford)
**Karel Charvat (CCSS)
**[[User:epifanio|Massimo Di Stefano (RPI - WHOI)]]

* There will also be a gathering for developers to meet during the Tuesday evening Welcome Social at the Wynkoop Brewing Company.

== Spatial Data InfraStructure (SDI) ==

*Scheduling: 7pm - 8pm. Get started with these topics then go get some food/drinks together.
*Proposed topics: data sharing and discovery, metadata, web services, and portals.
*Attending:
**Christine White (Esri)
**Andy Gup (Esri)
**Karel Charvat (CCSS)

== Mobile GIS ==

*Proposed Topics
**General discussion about development of mobile mapping/GIS apps
**"OpenLayers-like" SDK for Android (Android GIS)
**add yours...
*Attending:
**[[User:Danielkastl|Daniel Kastl (Georepublic)]]
**[[User:Hal sk|Haruyuki Seki (Georepublic)]]
**Jaak Laineste (Nutiteq)
**[[User:Dmorissette| Daniel Morissette (Mapgears)]]
**Alan Boudreault (Mapgears)
**[[User:Mloskot|Mateusz Loskot (Cadcorp)]]
**[[User:Assefa|Yewondwossen Assefa (DM Solutions)]]
**Karel Charvat (CCSS)

== Education / Academic ==
* '''Room: Denver - 5:30-7'''
* Separate sign up page: [[FOSS4G 2011 Edu BOF sign up]]

== Spatial Databases ==

*Proposed Topics
**Do we need some more
**Where are we heading to (distributed databases?)
**Do the processing within the database or outside?
**Add yours...
*Attending:
**Volker Mische (Couchbase)

== SpatiaLite ==

*Scheduling: let's not conflict with the Python session? maybe we should do something less formal another day if the BOF all conflict too much?
*Proposed topics:
**Community organization strategies
**Meet and Greet

*Attending:
**[[User:Davidfawcett|David Fawcett (MPCA)]]
**[[User:putler|Dan Putler (Anemoi Analytics)]]
**[[User:wildintellect|Alex Mandel (UC Davis)]]
**[[User:dnewcomb|Doug Newcomb (USFWS)]] ( I will not be available for much of Wed. Evening)
**[[User:jlhgis|Julia Harrell (NC DENR)]]

== Web Processing Services (WPS) ==

*Scheduling: 5:30-6:30

*Proposed topics:
** Web Processing Services Ideas exchange and get-together
** WPS 2.0 status and community input
** Meet and Greet

*Attending:
** Gėrald Fenoy (ZOO-Project)
** Nicolas Bozon (ZOO-Project)
** Bastian Schäffer (52North)
** Benjamin Pross (52North)
** Jachym Cepicky

== Free meditation and relaxing movements sessions ==

There are so many interesting people and ideas at FOSS4G that I’ve found it can be really helpful to have a quiet, meditative moment or two to let it all sink in. The intention is to help one release stress and relax muscles that commonly become tight from computer/desk work, travel, carrying bags.. the common issues that tend to manifest at a week-long conference! I’ve been leading meditation sessions for co-workers at MIT and receiving very positive feedback about how helpful they are.

My plan is to hold a few 30-minute, sessions of relaxed meditative breathing and gentle movements during the FOSS4G conference at the following times:

*Wed. 8 pm
*Thurs 5:30 pm
*Friday 5 pm - after the Annual General Meeting

These sessions are available to anyone, including people with no prior experience with any movement styles, those who do not feel particularly flexible, and folks who are in their work/meeting clothes. These sessions are being hosted by [[User:Lsweeney|Lisa Sweeney]] If you are interested please add your name below. I'll be seeking out room options and post them to this wiki page once identified.

== Add yours below ==

[[Category:FOSS4G]] [[Category:FOSS4G2011]]

OpenRouter 2010 SOC Ideas

2010-03-08T06:11:36Z

Wiki-Woodbri: /* OpenGraphRouter related ideas */

* Back to the main OSGeo [[Google Summer of Code 2010]] wiki page.
* Back to the main OSGeo [[Google Summer of Code 2010 Ideas]] wiki page.

= OpenRouter 2010 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 OpenRouter. Our current efforts are based on the following projects:
* [http://pgrouting.postlbs.org/ pgRouting]. This routing library provides routing functionality to PostGIS/PostgreSQL.
* [http://opengraphrouter.sourceforge.net/ OpenGraphRouter]. This project is a C++ library and tools to build a commercial grade routing engine.

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

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

== pgRouting related ideas ==

=== Implement a bi-directional shortest path algorithm ===

So far pgRouting doesn't provide a bi-directional shortest path search implementation.

=== Traveling Salesperson solver enhancement ===

The current pgRouting Traveling Salesperson implementation doesn't allow to return to the start point.

=== OpenStreetMap data import tool improvement ===

The recently contributed OpenStreetMap data import tool has a couple of limitations, such as supported attributes, memory management, cross-platform support, etc..

=== Add support for time constraints ===

Real-time shortest path searches are not implemented yet in pgRouting. What if network conditions change during a trip? An example could be train or bus schedules or time restrictions in road networks. Currently pgRouting algorithms don't take into account network these changes.

=== Network layering support ===

This idea is a quite a challenging task. Network layering would allow the routing algorithm to change from more to less dense networks to enable long-distance routing.

=== Better support for turn restrictions ===

[...]

=== Explicator for driving directions ===

[...]

== OpenGraphRouter related ideas ==

Continue work on this new general purpose OpenSource Routing library that is designed to be modular and reusable and could be used with or without a database.

=== Improve existing Driving Directions Module ===

Improve the existing driving direction support and add support for richer information available through the Navteq data model.

=== Add Turn restriction support based on Navteq data model ===

Add support for turn restrictions based on the Navteq data model.

=== Add support for TeleAtlas data ===

Add support for TeleAtlas data. This would include writing a data loader, adding support to the driving directions module and anything else related to supporting TeleAtlas data.

=== Add Highway Hierarchies routing support ===

Add support for routing based on Highway Hierarchies based on algorithms developed by P. Sanders and D. Schultes.

=== Implement a graph storage based on a database ===

We currently store the graph in our own set of files that facilitate quick access. We would like to have the option of storing the data in a database. Graph structures are not inherently relation so it is like that data will need to be stored in blobs of some type, but that is open to discussion. The goal of this task would be to design an appropriate structure, and write the C++ classes that would manage moving data in and out of these structures and updating them if needed.

=== Lots of other options ===

There are a lot of other possibilities that we would be happy to discuss with any students interested.

= Mentor Candidates =

The following individuals are potentially willing to serve as OpenRouter/pgRouting mentors or co-mentors.

* Stephen Woodbridge <woodbri (at) swoodbridge (dot) com>

[[Category:Google Summer of Code]]

Google Summer of Code 2010 Ideas

2010-03-08T05:52:05Z

Wiki-Woodbri: /* The ideas pages */

[[Image:Google_soc_2010_logo.jpg|center|250px]]

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

=OSGeo Google Summer of Code 2010=

* '''''PRELIMINARY - WE HAVEN'T EVEN APPLIED TO BE IN THE PROGRAM YET THIS YEAR'''''

The 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 soc at lists.osgeo.org'''

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

=What to expect during the summer?=

==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 intergrate you into the developer community, so you should get involved 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.

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

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, be honest. 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 ask 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 or blog space can be provided by OSGeo if your project doesn't have anything already set up for this.

=Timeline=
http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline

* March 18th 2010: Google announces accepted organizations. If OSGeo is accepted as an organization for Google Summer of Code, start talking to us earlier rather than later.
* April 9th 2010: Student application deadline. 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 this final deadline.
* April 26th 2010: Accepted student proposals are announced.
* May 24th 2010: Coding begins!
* July 12-16th: Mid-term evaluation.
* August 9th: Pencils down!

= The ideas pages =
Each participating project's list of ideas is here, with a short description of the project and what type of students would be interested in it:

* [http://trac.osgeo.org/gdal/wiki/SummerOfCode GDAL SoC Ideas]: GDAL is the Geographic Data Abstraction Library, a library which provides access to spatial data in all kinds of formats via a uniform API.
* [http://grass.osgeo.org/wiki/GRASS_SoC_Ideas GRASS SoC Ideas]: GRASS GIS is an open source GIS focusing mainly on analysis. It is written as a collection of stand-alone C programs and has a new GUI written in Python. If you know Python, or want to implement algorithms in C take a look!
* [http://www.mapbender.org/GSoC_2010 Mapbender SoC ideas 2010]: Mapbender is a server and client side geographic data management tool, programmed in '''PHP''' and '''JavaScript''', using the '''jQuery''' library.
* [http://www.qgis.org/wiki/Google_Summer_of_Code_2010 Quantum GIS SoC Ideas] Quantum GIS (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.
* [http://udig.refractions.net/confluence/display/HACK/Summer+of+Code uDig SoC 2009]: 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.
* [http://sourceforge.net/apps/mediawiki/jump-pilot/index.php?title=OpenJUMP_Google_Summer_Of_Code OpenJUMP/deegree Ideas List]: deegree and OpenJUMP share code derived from the original JUMP. Both programs maintain separate development lists and source code repositories but look for opportunities to collaborate.
* [http://wiki.osgeo.org/wiki/OpenRouter_2010_SOC_Ideas OpenRouter 2010 SOC Ideas]: OpenRouter is a couple of projects that are building routing and driving direction libraries and applications that can be integrated with other applications.

= What is the main public mailing list for your organization? =
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.

= What is the main IRC channel for your organization? =

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

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/#mapbender
* irc://irc.freenode.net/#mapbuilder
* irc://irc.freenode.net/#mapguide
* irc://irc.freenode.net/#mapserver
* irc://irc.freenode.net/#openlayers
* irc://irc.freenode.net/#ossimplanet
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#qgis
* irc://irc.freenode.net/#udig

[[Category:Google Summer of Code]]

OpenRouter 2010 SOC Ideas

2010-03-08T05:44:38Z

Wiki-Woodbri: New page: * Back to the main OSGeo Google Summer of Code 2010 wiki page. * Back to the main OSGeo Google Summer of Code 2010 Ideas wiki page. = OpenRouter 2010 SOC Ideas = Enter ideas for...

* Back to the main OSGeo [[Google Summer of Code 2010]] wiki page.
* Back to the main OSGeo [[Google Summer of Code 2010 Ideas]] wiki page.

= OpenRouter 2010 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 OpenRouter. Our current efforts are based on the following projects:
* [http://pgrouting.postlbs.org/ pgRouting]. This routing library provides routing functionality to PostGIS/PostgreSQL.
* [http://opengraphrouter.sourceforge.net/ OpenGraphRouter]. This project is a C++ library and tools to build a commercial grade routing engine.

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

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

== pgRouting related ideas ==

=== Implement a bi-directional shortest path algorithm ===

So far pgRouting doesn't provide a bi-directional shortest path search implementation.

=== Traveling Salesperson solver enhancement ===

The current pgRouting Traveling Salesperson implementation doesn't allow to return to the start point.

=== OpenStreetMap data import tool improvement ===

The recently contributed OpenStreetMap data import tool has a couple of limitations, such as supported attributes, memory management, cross-platform support, etc..

=== Add support for time constraints ===

Real-time shortest path searches are not implemented yet in pgRouting. What if network conditions change during a trip? An example could be train or bus schedules or time restrictions in road networks. Currently pgRouting algorithms don't take into account network these changes.

=== Network layering support ===

This idea is a quite a challenging task. Network layering would allow the routing algorithm to change from more to less dense networks to enable long-distance routing.

=== Better support for turn restrictions ===

[...]

=== Explicator for driving directions ===

[...]

== OpenGraphRouter related ideas ==

=== General purpose Routing library ===

Continue work on this new general purpose OpenSource Routing library that could be more modular and reusable and could be used with or without a database?

Add support for turn restrictions based on the Navteq data model.

Add support for routing based on Highway Hierarchies based on algorithms developed by P. Sanders and D. Schultes.

There are a lot of other possibilities that we would be happy to discuss with any students interested.

= Mentor Candidates =

The following individuals are potentially willing to serve as OpenRouter/pgRouting mentors or co-mentors.

* Stephen Woodbridge <woodbri (at) swoodbridge (dot) com>

[[Category:Google Summer of Code]]

User:Woodbri

2010-02-01T22:55:28Z

Wiki-Woodbri: New page: Stephen Woodbridge is a member of the Mapserver PSC and works with many of the OSGeo products like Mapserver and OpenLayers as well as other OpenSource projects. Stephen can be found at iM...

Stephen Woodbridge is a member of the Mapserver PSC and works with many of the OSGeo products like Mapserver and OpenLayers as well as other OpenSource projects. Stephen can be found at iMapTools.com [http://iMapTools.com/] where he provides geospatial products and consulting to his clients.

WMS Tile Caching

2010-02-01T22:46:42Z

Wiki-Woodbri: /* Interested Parties */

== Goal ==

The goal of a '''WMS Tile Caching''' proposal, perhaps ''WMS-C'' for short, is to find a way to optimize the delivery of map imagery across the Internet. The proposal needs to offer ideally some means by which map clients can fetch tiles from existing servers, in such a way that the images can be cached on the server, or at an intermediate location, or even be completely pre-generated, if desired. Further, the proposal needs to offer a way of advertising that a cached tile set is available for a given layer from a particular WMS or WMS proxy. The proposal should leverage the existing investment in OGC-compliant WMS servers on the 'Net.

The two main questions to be addressed are:
# How does a server advertise its cacheable image tiles?
# How does a client request possibly cached image tiles?

== Proposal ==

=== WMS-C as WMS Profile ===

One approach to take might be to define ''WMS-C'' (as in ''Web Mapping Service - Cached'') as a constrained profile of [http://www.opengeospatial.org/docs/01-068r2.pdf OGC WMS] that permits servers to optimize their image generation, and allows tiles to be cached at intermediate points. A WMS-C service would likely only deliver images for bounding boxes aligned to a given rectangular origin and grid, and only at particular scale levels.

The basic idea is that, unlike with WMS, two different requests for a given WMS-C tile should form the exact same HTTP GET request. This invites several constraints on WMS ''GetMap'' requests:

# Minimal query string arguments (i.e. no optional arguments permitted, versus §7.2)
# Fixed query string argument ordering and case (versus §6.4.1; q.v. also §7.2.2, Table 8)
# Fixed range of possible bounding boxes, computed from the WMS-C profile parameters
# Fixed precision on bounding box values (clarifying §6.5.6)
# Fixed tile size in pixels
# Fixed layer name and/or layer name ordering
# Fixed styling
# Fixed output format

Some means of identifying these constraints programmatically on a per-server basis, a la ''GetCapabilities'' might be desirable. From the table below, it appears that minimum/maximum scale (and scale quantization factor, which should probably never be other than 2) are the only suggested tiling regime parameters that would be difficult to directly express in a WMS GetCapabilities document. Is there some existing way to add custom parameters to a GetCapabilities declaration?

Note that the ''LAYERS'', ''STYLES'', ''SRS'', ''HEIGHT'', ''WIDTH'', and ''FORMAT'' arguments to a ''GetMap'' request would become fixed for a particular WMS-C tiled layer, but the WMS specification would still require the inclusion of these arguments in every WMS-C request (§ 7.2).

A WMS-C proxy or server should be free to return an exception or a redirect, if it receives a WMS request that is not WMS-C compliant, or involves a bounding box that does not correspond to a single tile in the cache.

=== Calculating Valid Tile Extents for a Given Request ===

WMS tile caching implies fixed scale or zoom levels. Typically, each valid scale level would be half that of the next larger scale. It would be worth writing reference code to help developers figure out which tiles they need to load to cover a given bounding box at a given scale.

=== Possible Tile Scheme Parameters ===

{| cellpadding="5" cellspacing="1" border="1"
| '''Parameter''' || '''Default value''' || '''Specifiable in WMS GetCapabilities?'''
|-
| "This service suppports tiling." || ''none'' || ''<KeywordList>'' contains the string 'tiled', perhaps? (§7.1.4.5.3)
|-
| Projection || EPSG:4326 || ''<SRS>''
|-
| Maximal extent || (-180,-90,180,90) || ''<BoundingBox>'' (§7.1.4.5.7)
|-
| Number of horizontal and vertical tiles at the maximal extent || ''none'' || Could be implied by ''<ScaleHint>'' (§7.1.4.5.8, but note that the format is weakly specified)... Alternately, could use ''<DataURL>'' (§7.1.4.5.14)
|-
| Tile size in pixels || some power of 2 || <Layer> attribute ''fixedWidth'', ''fixedHeight'' (§7.1.4.6)
|-
| Minimum scale || ''none'' || ''<ScaleHint>'' or ''<DataURL>'' (see note, above)
|-
| Scale quantization factor || 2 || ''<DataURL>''
|}

----

== Other Considerations ==

* Would non-rectangular tessellations yield more efficient results? If so, which tessellations to consider? Also, are the processing and bandwidth advantages of a non-rectangular tessellation outweighed by the potential implementation complexity?
* Norm Vine rightly points out that a tile request basically boils (or should boil down to) Layer + Zoom Level + Row + Column. Can we define an even simpler method for requesting tiles from servers in the know? How are those capabilities advertised, if not shoehorned into WMS? Note that WorldWind basically already has a mechanism for this. Their tiling requests basically look like:

http://domain.tld/service?L=0&X=1&Y=2
* Like all caching schemes, WMS-C caches would need to be cognizant of expiration. Easy with using the proper HTTP headers. There is a wide range of freshness/staleness, with OpenStreetMap being highly volatile, and Landsat being pretty stable (until the ice caps melt ;).
* Several people (particularly Paul Spencer and Chris Schmidt) have argued that a separate ''GetTile'' request should be used. This topic probably warrants discussion.

== Distributed Caching ==

* A WMS-C standard would permit tile caching through [http://www.coralcdn.org/ Coral]. However, the World Wind community's experience has been that using Coral to serve tiles results in frustratingly high latency.
* Alternately, one could do (distributed) [[Distributed Tile Caching|peer-to-peer tile caching]] optimized specifically for geographic space, which might still suffer the latency issues associated with P2P networks.

== Existing Tiling Schemes ==

* Mikel Maron's description of [http://lists.eogeo.org/pipermail/tiling/2006-March/000017.html OnEarth's LandSat tiling scheme]
* World Wind's LandSat tiling scheme: [http://www.ceteranet.com/nww-tile-struct.pdf PDF], [http://www.worldwindcentral.com/wiki/Making_Layers wiki]
* World Wind ''QuadTileSet'' [http://rafb.net/paste/results/S3I8Zr92.html sample description], [http://forum.worldwind.arc.nasa.gov/lofiversion/index.php?t2965.html forum discussion], [http://rafb.net/paste/results/z2dQKa54.html sample PHP code] to fetch WW tiles for a given WMS GetMap request
* osgPlanet's C++ code for [http://www.remotesensing.org/cgi-bin/cvsweb.cgi/osgPlanet/src/osgPlanet/osgPlanetGridUtility.cpp?rev=HEAD;content-type=text%2Fx-cvsweb-markup tiling the Earth]
* WorldWind Example code for tiling the Earth (needs Proj.4 and GDAL libraries)[http://download.worldwindcentral.com/dstile-0.2.tar.gz DSTile and Tilepack]
* OnEarth's code for intercepting WW requests and converting into WMS requests and caching them [http://www.twobeds.com/upload/userfiles/adamhill/lucians%20code%20-%20cache_1_1.gz?PHPSESSID=f485cf3fd66cd30ad7a4f814a127d2cb from Lucian Plesa]
* Casey Chestnut explains Microsoft Virtual Earth's tiling scheme + code to experiment with the URL's [http://www.brains-n-brawn.com/veWorldWind/]
* GeoOdyssey's [http://www.geodyssey.com/tileshare/index.html TileShare scheme]
* Chuck Stein's [http://www.geongrid.org/workshops/geonvis2005/Presentations/ChuckStein/GeoFusion.ppt GeoFusion presentation] from GEON (warning: PowerPoint)
* [http://globe.sintef.no/documentation/projection.html The Finite Nearly-Conformal Normal Cylindrical Projection] (Aasgaard's map projection)

Note: WW and OnEarth's schemes are pretty much identical, the WW client just allows you to specify arbitrary tile sizes, coverages and number of levels to accomodate a given client.

== Related Projects ==

* [http://www.ossim.org/osgPlanet.html osgPlanet]
* [http://worldwind.arc.nasa.gov/ NASA WorldWind] ([http://www.worldwindcentral.com/wiki/Main_page wiki])
* [http://worldkit.org/ worldKit]
* [http://communitymapbuilder.org/ Community MapBuilder]
* [http://ka-map.maptools.org/ ka-Map!]
* [http://openlayers.org/ OpenLayers]
* [http://www.geomoose.org/moose/ GeoMoose]
* other AJAX map clients, presumably

== Interested Parties ==

''Note:'' Interested parties should join the existing low-volume [http://lists.eogeo.org/mailman/listinfo/tiling EOGEO mailing list] dedicated to this topic.

* [[User:SchuylerErle|Schuyler Erle]]
* [[User"Adoyle"|Allan Doyle]]
* [[user"Nhv"|Norman Vine]]
* [[user"Joshli"|Josh Lieberman]]
* [[user"Adamhill"|Adam Hill]]
* [[user"bitner"|David Bitner]]
* [[user:Mikel|Mikel Maron]]
* [[user:mpg|Michael P. Gerlek]]
* [[user:stvn|Steven M. Ottens]]
* [[user:Pagameba|Paul Spencer]]
* [[user:hallkbrdz|Bryan Hall]]
* [[user:tschaub|Tim Schaub]]
* [[user:dmorissette|Daniel Morissette]]
* [[user:dpatton|Dave Patton]]
* [[user:cholmes|Chris Holmes]]
* [[user:pwramsey3|Paul Ramsey]]
* [[user:luisw|Luis W. Sevilla]]
* [[user:ominiverdi|Lorenzo Becchi]]
* [[user:wilfred|Wilfred Springer]]
* [[user:fpurcell|Frank Purcell]]
* [[user:Pauldendulk|Paul den Dulk]]
* [[user:Schpidi|Stephan Meißl]]
* [[user:Mornsunrain|Xi Chen]]
* [[user:blammo|Bob Basques]]
* [[user:Woodbri|Stephen Woodbridge]]
* ''add yourself''

[[Category:Standards]]

OpenRouter

2009-04-23T21:36:32Z

Wiki-Woodbri: /* Consumers */

== Open Source Router ==

For those not familiar with the concept, routing provides the path between two locations. Often there can be criteria considered such as time, cost, and so forth.

===Project Purpose===

The intention of this project is to work towards creation of open source software providing routing capability.

===Design goals===

Desired attributes:
* Library Coded in C (or C wrapper to C++)
* This library could SWIG wrapped for integration into scripting languages, or used in RDBMS engines like pgRouting in PostgreSQL, or via a command line or webservice tools.
* Architected and designed for performance. An ideal goal would be to handle graphs in the ballpark of 25-35 million edges and able to generate sub-sec responses.
* Abstracted storage to allow for use of data from various sources e.g. shapefiles, RDBMS, others
* Support multiple subject-matter domains, outside of transportation, such as utility and telecom networks

===Contact information===

Please join us on the [http://lists.osgeo.org/mailman/listinfo/routergeocoder mailing list].

NOTE: This mailing list is shared between this project and the [http://wiki.osgeo.org/wiki/OpenGeocoder OpenGeocoder] project.

===Relevant Existing Open Source Technologies===

* [http://pgrouting.postlbs.org/ pgRouting]
* GRASS GIS v.net.* modules see:
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.html - Vector maintenance
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.path.html - Shortest path
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.salesman.html - Traveling salesman (round trip)
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.alloc.html - Allocation of sources (create subnetworks)
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.steiner.html - Minimum Steiner trees (star-like connections)
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.visibility.html - Visibility graph construction
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.iso.html - Iso-distances (from centers)
* [http://graphserver.sourceforge.net/ GraphServer]

===Target Licensing===

* Preference for a liberal license to encourage adoption by maximum number of technologies both proprietary and open source

===Project Support===

====Development====

The following list are people who are interested in participating in development of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Daniel Kastl - [http://pgrouting.postlbs.org/ pgRouting] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://pgrouting.postlbs.org/ pgRouting] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://pgrouting.postlbs.org/ pgRouting] | [http://www.orkney.co.jp Orkney]
* [[Stephen Woodbridge]] - http://imaptools.com/
* Claude Philipona - [http://www.camptocamp.com Camptocamp]
* Dimitris Kotzinos - OSGeo Greece (possibly ...)
* Robert Hollingsworth
* Paul Ramsey - [http://www.cleverelephant.ca Clever Elephant]

====Testing====

The following list are people who are interested in participating in testing of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Daniel Kastl - [http://pgrouting.postlbs.org/ pgRouting] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://pgrouting.postlbs.org/ pgRouting] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://pgrouting.postlbs.org/ pgRouting] | [http://www.orkney.co.jp Orkney]
* [[Stephen Woodbridge]] - http://imaptools.com/
* Dirk Frigne - [http://www.frigne.be Dirk Frigne] | [http://www.geomajas.org Geomajas]
* Claude Philipona - [http://www.camptocamp.com Camptocamp]

====Consumers====

The following list are people that plan to make use of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Dave McIlhagga - [http://wwww.dmsolutions.ca DM Solutions Group]
* Daniel Kastl - [http://pgrouting.postlbs.org/ pgRouting] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://pgrouting.postlbs.org/ pgRouting] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://pgrouting.postlbs.org/ pgRouting] | [http://www.orkney.co.jp Orkney]
* [[Stephen Woodbridge]] - http://imaptools.com/
* V.Ravi Kumar - OSGeo India
* Dimitris Kotzinos - OSGeo Greece
* Dirk Frigne - [http://www.frigne.be Dirk Frigne] | [http://www.geomajas.org Geomajas]
* David Jonglez - [http://www.camptocamp.com Camptocamp]
* Claude Philipona - [http://www.camptocamp.com Camptocamp]
* Cédric Moullet - [http://www.camptocamp.com Camptocamp]
* Robert Hollingsworth

OpenRouter

2009-04-23T21:35:33Z

Wiki-Woodbri: /* Testing */

== Open Source Router ==

For those not familiar with the concept, routing provides the path between two locations. Often there can be criteria considered such as time, cost, and so forth.

===Project Purpose===

The intention of this project is to work towards creation of open source software providing routing capability.

===Design goals===

Desired attributes:
* Library Coded in C (or C wrapper to C++)
* This library could SWIG wrapped for integration into scripting languages, or used in RDBMS engines like pgRouting in PostgreSQL, or via a command line or webservice tools.
* Architected and designed for performance. An ideal goal would be to handle graphs in the ballpark of 25-35 million edges and able to generate sub-sec responses.
* Abstracted storage to allow for use of data from various sources e.g. shapefiles, RDBMS, others
* Support multiple subject-matter domains, outside of transportation, such as utility and telecom networks

===Contact information===

Please join us on the [http://lists.osgeo.org/mailman/listinfo/routergeocoder mailing list].

NOTE: This mailing list is shared between this project and the [http://wiki.osgeo.org/wiki/OpenGeocoder OpenGeocoder] project.

===Relevant Existing Open Source Technologies===

* [http://pgrouting.postlbs.org/ pgRouting]
* GRASS GIS v.net.* modules see:
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.html - Vector maintenance
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.path.html - Shortest path
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.salesman.html - Traveling salesman (round trip)
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.alloc.html - Allocation of sources (create subnetworks)
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.steiner.html - Minimum Steiner trees (star-like connections)
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.visibility.html - Visibility graph construction
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.iso.html - Iso-distances (from centers)
* [http://graphserver.sourceforge.net/ GraphServer]

===Target Licensing===

* Preference for a liberal license to encourage adoption by maximum number of technologies both proprietary and open source

===Project Support===

====Development====

The following list are people who are interested in participating in development of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Daniel Kastl - [http://pgrouting.postlbs.org/ pgRouting] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://pgrouting.postlbs.org/ pgRouting] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://pgrouting.postlbs.org/ pgRouting] | [http://www.orkney.co.jp Orkney]
* [[Stephen Woodbridge]] - http://imaptools.com/
* Claude Philipona - [http://www.camptocamp.com Camptocamp]
* Dimitris Kotzinos - OSGeo Greece (possibly ...)
* Robert Hollingsworth
* Paul Ramsey - [http://www.cleverelephant.ca Clever Elephant]

====Testing====

The following list are people who are interested in participating in testing of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Daniel Kastl - [http://pgrouting.postlbs.org/ pgRouting] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://pgrouting.postlbs.org/ pgRouting] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://pgrouting.postlbs.org/ pgRouting] | [http://www.orkney.co.jp Orkney]
* [[Stephen Woodbridge]] - http://imaptools.com/
* Dirk Frigne - [http://www.frigne.be Dirk Frigne] | [http://www.geomajas.org Geomajas]
* Claude Philipona - [http://www.camptocamp.com Camptocamp]

====Consumers====

The following list are people that plan to make use of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Dave McIlhagga - [http://wwww.dmsolutions.ca DM Solutions Group]
* Daniel Kastl - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* [[Stephen Woodbridge]] - http://imaptools.com/
* V.Ravi Kumar - OSGeo India
* Dimitris Kotzinos - OSGeo Greece
* Dirk Frigne - [http://www.frigne.be Dirk Frigne] | [http://www.geomajas.org Geomajas]
* David Jonglez - [http://www.camptocamp.com Camptocamp]
* Claude Philipona - [http://www.camptocamp.com Camptocamp]
* Cédric Moullet - [http://www.camptocamp.com Camptocamp]
* Robert Hollingsworth

OpenRouter

2009-04-23T21:34:10Z

Wiki-Woodbri: /* Development */

== Open Source Router ==

For those not familiar with the concept, routing provides the path between two locations. Often there can be criteria considered such as time, cost, and so forth.

===Project Purpose===

The intention of this project is to work towards creation of open source software providing routing capability.

===Design goals===

Desired attributes:
* Library Coded in C (or C wrapper to C++)
* This library could SWIG wrapped for integration into scripting languages, or used in RDBMS engines like pgRouting in PostgreSQL, or via a command line or webservice tools.
* Architected and designed for performance. An ideal goal would be to handle graphs in the ballpark of 25-35 million edges and able to generate sub-sec responses.
* Abstracted storage to allow for use of data from various sources e.g. shapefiles, RDBMS, others
* Support multiple subject-matter domains, outside of transportation, such as utility and telecom networks

===Contact information===

Please join us on the [http://lists.osgeo.org/mailman/listinfo/routergeocoder mailing list].

NOTE: This mailing list is shared between this project and the [http://wiki.osgeo.org/wiki/OpenGeocoder OpenGeocoder] project.

===Relevant Existing Open Source Technologies===

* [http://pgrouting.postlbs.org/ pgRouting]
* GRASS GIS v.net.* modules see:
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.html - Vector maintenance
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.path.html - Shortest path
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.salesman.html - Traveling salesman (round trip)
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.alloc.html - Allocation of sources (create subnetworks)
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.steiner.html - Minimum Steiner trees (star-like connections)
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.visibility.html - Visibility graph construction
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.iso.html - Iso-distances (from centers)
* [http://graphserver.sourceforge.net/ GraphServer]

===Target Licensing===

* Preference for a liberal license to encourage adoption by maximum number of technologies both proprietary and open source

===Project Support===

====Development====

The following list are people who are interested in participating in development of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Daniel Kastl - [http://pgrouting.postlbs.org/ pgRouting] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://pgrouting.postlbs.org/ pgRouting] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://pgrouting.postlbs.org/ pgRouting] | [http://www.orkney.co.jp Orkney]
* [[Stephen Woodbridge]] - http://imaptools.com/
* Claude Philipona - [http://www.camptocamp.com Camptocamp]
* Dimitris Kotzinos - OSGeo Greece (possibly ...)
* Robert Hollingsworth
* Paul Ramsey - [http://www.cleverelephant.ca Clever Elephant]

====Testing====

The following list are people who are interested in participating in testing of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Daniel Kastl - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* [[Stephen Woodbridge]] - http://imaptools.com/
* Dirk Frigne - [http://www.frigne.be Dirk Frigne] | [http://www.geomajas.org Geomajas]
* Claude Philipona - [http://www.camptocamp.com Camptocamp]

====Consumers====

The following list are people that plan to make use of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Dave McIlhagga - [http://wwww.dmsolutions.ca DM Solutions Group]
* Daniel Kastl - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* [[Stephen Woodbridge]] - http://imaptools.com/
* V.Ravi Kumar - OSGeo India
* Dimitris Kotzinos - OSGeo Greece
* Dirk Frigne - [http://www.frigne.be Dirk Frigne] | [http://www.geomajas.org Geomajas]
* David Jonglez - [http://www.camptocamp.com Camptocamp]
* Claude Philipona - [http://www.camptocamp.com Camptocamp]
* Cédric Moullet - [http://www.camptocamp.com Camptocamp]
* Robert Hollingsworth

Google Summer of Code 2009 Administrative

2009-04-23T14:26:54Z

Wiki-Woodbri: /* Project Mentors */

[[Image:2009 summer of code logo final r3-01.png|center|250px]]

* Back to main [[Google Summer of Code]] wiki page.

Central page for administering OSGeo participation in Google Summer of Code 2009.

= Background =

* Wolf Bergenheim will act as Administrative contact, with support from Landon Blake and Hamish Bowman
* FAQ on the program is at: http://code.google.com/opensource/gsoc/2009/faqs.html
* There is also a Google Wiki page about the program: http://code.google.com/p/google-summer-of-code/wiki/WikiStart
* Last years GSoC submission: http://code.google.com/soc/2008/osgeo/about.html
* Last years GSoC page: [[Google Summer of Code 2008]]
* Mentoring HOWTO: http://primates.ximian.com/~federico/docs/summer-of-code-mentoring-howto/index.html
* Advice for Mentors from the Google Wiki: http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors
* The [http://socghop.appspot.com/ Google Summer of Code 2009 site]
* There is an [http://svn.osgeo.org/osgeo/marketing/flyer/ OSGeo SoC flyer] to look at and post in appropriate places - Marketing Committee is working on a 2009 version.

= Timeline =

[http://code.google.com/opensource/gsoc/2009/faqs.html#0_1_timeline_5354032302481437_ The official timeline]

* {{Done}} March 9th - 13th: '''Project applications''' will be accepted:
** {{Done}} March 12th Our application needs to be ready.
* {{Done}} March 18th: List of accepted mentoring organizations published on the [http://socghop.appspot.com/ Google Summer of Code 2009] site.
* {{Done}} We are accepted - so we should start talking to students immediately after!
: {{Done}} '''Student applications''' accepted from March 23 - April 3, 2009.
* {{Done}} April 15: All mentors must be signed up and all student proposals matched with a mentor
* {{Done}} April 20: Accepted student proposals announced on the Google Summer of Code 2009 site
* May 23: Students begin coding for their GSoC projects
...

= Documents =

* OSGeo [[Google SoC Application 2009]]
* [[SoC Application Rankings by Project]]
* The "Student Landing Page" is [[Google Summer of Code 2009 Ideas]].
* The OSGeo home at melange is http://socghop.appspot.com/org/home/google/gsoc2009/osgeo

== How to register as a mentor ==

Please apply to become a mentor today! After you have applied you will get an invitation notification in the melange system. You need to accept the invitation, and fill in the form to become a registered mentor. In details:

# Register yourself [http://socghop.appspot.com/ at the Melange site]
# Subscribe to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailinglist]. Introdce yourself and give this info:
## Melange Link ID
## Project you want to/can mentor for
## Area(s) of interest
## Feel free to tell more about yourself
# [http://socghop.appspot.com/org/apply_mentor/google/gsoc2009 Apply to become a mentor]
## Accept the invitation that you receive, and fill in your Mentor information
# Go [http://socghop.appspot.com/org/list_proposals/google/gsoc2009/osgeo read and comment on student applications]

= Project Mentors =

{| class="wikitable sortable" border="1" style="margin: 1em auto 1em auto; text-align:left"
| align="center" style="background:#f0f0f0;"|'''Mentor'''
| align="center" style="background:#f0f0f0;"|'''Project'''
|-
| Tamas Szekeres||GDAL
|-
| Tim Keitt||GDAL
|-
| Andrea Aime||GeoServer
|-
| Martin Landa||GRASS
|-
| Wolf Bergenheim||GRASS
|-
| Jorge Sanz||gvSIG
|-
| Luis W. Sevilla||gvSIG
|-
| Etienne Dube||Laval University
|-
| Thierry Badard||Laval University
|-
| Christoph Baudson||Mapbender
|-
| Daniel Morissette||Mapserver
|-
| Thomas bonfort||Mapserver
|-
| Landon Blake||OpenJUMP/deegree
|-
| Anton Patrushev||[[OpenRouter]]
|-
| [[Stephen Woodbridge]]||[[OpenRouter]]
|-
| Mark Lucas||OSSIM
|-
| Gary Sherman||QGIS
|-
| Jody Garnett||uDig
|-
| Jesse Eichar||uDig
|}

= Project Milestones =
[[Google SoC Project Milestones 2009]] - todo

= Project Pages =
Each accepted Soc Project should be listed here, and the page should be updated with information about the progress of the project.

The list of proposals can be found here: [[Google Summer of Code 2009 Ranking]]

[[Category:Google Summer of Code]]

Google Summer of Code 2009 Administrative

2009-04-23T14:26:17Z

Wiki-Woodbri: /* Project Mentors */

[[Image:2009 summer of code logo final r3-01.png|center|250px]]

* Back to main [[Google Summer of Code]] wiki page.

Central page for administering OSGeo participation in Google Summer of Code 2009.

= Background =

* Wolf Bergenheim will act as Administrative contact, with support from Landon Blake and Hamish Bowman
* FAQ on the program is at: http://code.google.com/opensource/gsoc/2009/faqs.html
* There is also a Google Wiki page about the program: http://code.google.com/p/google-summer-of-code/wiki/WikiStart
* Last years GSoC submission: http://code.google.com/soc/2008/osgeo/about.html
* Last years GSoC page: [[Google Summer of Code 2008]]
* Mentoring HOWTO: http://primates.ximian.com/~federico/docs/summer-of-code-mentoring-howto/index.html
* Advice for Mentors from the Google Wiki: http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors
* The [http://socghop.appspot.com/ Google Summer of Code 2009 site]
* There is an [http://svn.osgeo.org/osgeo/marketing/flyer/ OSGeo SoC flyer] to look at and post in appropriate places - Marketing Committee is working on a 2009 version.

= Timeline =

[http://code.google.com/opensource/gsoc/2009/faqs.html#0_1_timeline_5354032302481437_ The official timeline]

* {{Done}} March 9th - 13th: '''Project applications''' will be accepted:
** {{Done}} March 12th Our application needs to be ready.
* {{Done}} March 18th: List of accepted mentoring organizations published on the [http://socghop.appspot.com/ Google Summer of Code 2009] site.
* {{Done}} We are accepted - so we should start talking to students immediately after!
: {{Done}} '''Student applications''' accepted from March 23 - April 3, 2009.
* {{Done}} April 15: All mentors must be signed up and all student proposals matched with a mentor
* {{Done}} April 20: Accepted student proposals announced on the Google Summer of Code 2009 site
* May 23: Students begin coding for their GSoC projects
...

= Documents =

* OSGeo [[Google SoC Application 2009]]
* [[SoC Application Rankings by Project]]
* The "Student Landing Page" is [[Google Summer of Code 2009 Ideas]].
* The OSGeo home at melange is http://socghop.appspot.com/org/home/google/gsoc2009/osgeo

== How to register as a mentor ==

Please apply to become a mentor today! After you have applied you will get an invitation notification in the melange system. You need to accept the invitation, and fill in the form to become a registered mentor. In details:

# Register yourself [http://socghop.appspot.com/ at the Melange site]
# Subscribe to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailinglist]. Introdce yourself and give this info:
## Melange Link ID
## Project you want to/can mentor for
## Area(s) of interest
## Feel free to tell more about yourself
# [http://socghop.appspot.com/org/apply_mentor/google/gsoc2009 Apply to become a mentor]
## Accept the invitation that you receive, and fill in your Mentor information
# Go [http://socghop.appspot.com/org/list_proposals/google/gsoc2009/osgeo read and comment on student applications]

= Project Mentors =

{| class="wikitable sortable" border="1" style="margin: 1em auto 1em auto; text-align:left"
| align="center" style="background:#f0f0f0;"|'''Mentor'''
| align="center" style="background:#f0f0f0;"|'''Project'''
|-
| Tamas Szekeres||GDAL
|-
| Tim Keitt||GDAL
|-
| Andrea Aime||GeoServer
|-
| Martin Landa||GRASS
|-
| Wolf Bergenheim||GRASS
|-
| Jorge Sanz||gvSIG
|-
| Luis W. Sevilla||gvSIG
|-
| Etienne Dube||Laval University
|-
| Thierry Badard||Laval University
|-
| Christoph Baudson||Mapbender
|-
| Daniel Morissette||Mapserver
|-
| Thomas bonfort||Mapserver
|-
| Landon Blake||OpenJUMP/deegree
|-
| Anton Patrushev||[[OpenRouter]]
|-
| Stephen woodbridge||[[OpenRouter]]
|-
| Mark Lucas||OSSIM
|-
| Gary Sherman||QGIS
|-
| Jody Garnett||uDig
|-
| Jesse Eichar||uDig
|}

= Project Milestones =
[[Google SoC Project Milestones 2009]] - todo

= Project Pages =
Each accepted Soc Project should be listed here, and the page should be updated with information about the progress of the project.

The list of proposals can be found here: [[Google Summer of Code 2009 Ranking]]

[[Category:Google Summer of Code]]

OSGeo Community Projects

2009-04-21T21:10:52Z

Wiki-Woodbri: /* Young or Experimental Projects */

= OSGeo Labs Projects =

= Purpose =
OSGeo Labs is a place to list Open Source Geospatial Software that hasn't reached Incubation status. OSGeo Labs aims to:
* Help projects progress to OSGeo Incubation.
* Advertise projects and find like minded developers.
* Merge with similar projects. A project has a greater chance of reaching Incubation when integrated with similar projects.

This is the right place to start submitting your project so other OSGeo members can review them and send you feedback.

== Criteria ==
Projects should only list themselves in OSGeo Labs if they follow the OSGeo Incubation principles.
# The code is under an OSI approved license (data & doc projects need to specify their choice for a type of license).
# The project is willing to keep code clear of encumbrances
# The project is "geospatial", or directly supports geospatial applications.
# The project hopes to become a graduated OSGeo project, or have reasons why incubation is not appropriate.

==Becoming a Labs Project==
Becoming an OSGeo Labs should be easy and encouraged to all project that respond to criterias above. All project that use the OSGeo infrastructure or that wants to assign their copyright to OSGeo should add themselves below.

==Pending Incubation==
Projects which have self assessed themselves ready for incubation and waiting for a mentor: [http://trac.osgeo.org/osgeo/query?status=new&status=assigned&component=Incubator&keywords=%7Eapplication List from OSGeo trac]

==Stable Projects==
* ...

==Young or Experimental Projects==
* GeoFunctions [http://sourceforge.net/projects/geofunctions/ Geo Functions sourceforge page]
* Geoinformatica [http://trac.osgeo.org/geoinformatica/ OSGeo trac site]
* [[OpenGeocoder]]
* [[OpenRouter]]

== Responsibilities ==
OSGeo Labs aims to have minimal red tape to reduce overhead.

===Project Champion===
The Project Champion is responsible for:
# Strongly recommended: Read Karl Fogel's book on [http://producingoss.com/ Open Source Software - How to Run a Successful Free Software Project]
# Ensure the project complies with OSGeo principles by addressing the [[#Criteria]] above.
# Create a home page for the project. The OSGeo wiki is recommended for this page. A page should answer the OSGeo [[#Criteria]].
# List the project under the appropriate heading on this page.
# Announce and discuss the project on the [http://lists.osgeo.org/mailman/listinfo/discuss OSGeo Discuss] email list.
# Move the project toward incubation.

===Incubation Committee===
The OSGeo Incubation Committee is responsible for:
# Investigate, then possibly remove a project from OSGeo Labs if it doesn't follow OSGeo Labs [[#Criteria]].
# Periodically (at least annually), review projects in OSGeo labs and remove projects which have "died" or don't follow OSGeo Labs [[#Criteria]].

== Helpful Resource ==
# Get your project a mailing-list and a bug tracker
## [http://sourceforge.net/ SourceForge] provides code repository, mailing list and bug tracker services. (contact [mailto:sunburned.surveyor@gmail.com Landon Blake] to get help on SourceForge service)
# Approach the [[Spotlights]] editors about doing a spotlight interview about your project.

===Assigning Copyright to OSGeo===
Many graduated OSGeo projects choose to assign their copyright to OSGeo. A young project can assign its copyright to OSGeo by:
* TBD: As of 15 April 2009, the process for assigning copyright has not been resolved, it is being discussed on the OSGeo discuss email list. It may involve the following:
** Asking the incubation committee and doing it
** Having a graduated OSGeo project mentor yours

===Using OSGeo infrastructure===
It's possible to use OSGeo infrastructure to host your project or to have a trac and subversion server. You can get help if your project respond to criterias above and ask the right person for it.

== Disclosure ==

OSGeo or any of its affiliates do not take responsibility or endorse any of the software listed here. OSGeo doesn't guarantee the integrity of the code or any other aspect of the above softwares.

[[Category: Software Stack]]

OpenRouter

2009-04-21T21:07:15Z

Wiki-Woodbri: /* Development */

== Open Source Router ==

For those not familiar with the concept, routing provides the path between two locations. Often there can be criteria considered such as time, cost, and so forth.

===Project Purpose===

The intention of this project is to work towards creation of open source software providing routing capability.

===Design goals===

Desired attributes:
* Library Coded in C (or C wrapper to C++)
* This library could SWIG wrapped for integration into scripting languages, or used in RDBMS engines like pgRouting in PostgreSQL, or via a command line or webservice tools.
* Architected and designed for performance. An ideal goal would be to handle graphs in the ballpark of 25-35 million edges and able to generate sub-sec responses.
* Abstracted storage to allow for use of data from various sources e.g. shapefiles, RDBMS, others
* Support multiple subject-matter domains, outside of transportation, such as utility and telecom networks

===Contact information===

Please join us on the [http://lists.osgeo.org/mailman/listinfo/routergeocoder mailing list].

NOTE: This mailing list is shared between this project and the [http://wiki.osgeo.org/wiki/OpenGeocoder OpenGeocoder] project.

===Relevant Existing Open Source Technologies===

* [http://pgrouting.postlbs.org/ pgRouting]
* GRASS GIS v.net.* modules see:
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.html - Vector maintenance
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.path.html - Shortest path
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.salesman.html - Traveling salesman (round trip)
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.alloc.html - Allocation of sources (create subnetworks)
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.steiner.html - Minimum Steiner trees (star-like connections)
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.visibility.html - Visibility graph construction
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.iso.html - Iso-distances (from centers)
* [http://graphserver.sourceforge.net/ GraphServer]

===Target Licensing===

* Preference for a liberal license to encourage adoption by maximum number of technologies both proprietary and open source

===Project Support===

====Development====

The following list are people who are interested in participating in development of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Daniel Kastl - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* [[Stephen Woodbridge]] - http://imaptools.com/
* Claude Philipona - [http://www.camptocamp.com Camptocamp]
* Dimitris Kotzinos - OSGeo Greece (possibly ...)
* Robert Hollingsworth
* Paul Ramsey - [http://www.cleverelephant.ca Clever Elephant]

====Testing====

The following list are people who are interested in participating in testing of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Daniel Kastl - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* [[Stephen Woodbridge]] - http://imaptools.com/
* Dirk Frigne - [http://www.frigne.be Dirk Frigne] | [http://www.geomajas.org Geomajas]
* Claude Philipona - [http://www.camptocamp.com Camptocamp]

====Consumers====

The following list are people that plan to make use of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Dave McIlhagga - [http://wwww.dmsolutions.ca DM Solutions Group]
* Daniel Kastl - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* [[Stephen Woodbridge]] - http://imaptools.com/
* V.Ravi Kumar - OSGeo India
* Dimitris Kotzinos - OSGeo Greece
* Dirk Frigne - [http://www.frigne.be Dirk Frigne] | [http://www.geomajas.org Geomajas]
* David Jonglez - [http://www.camptocamp.com Camptocamp]
* Claude Philipona - [http://www.camptocamp.com Camptocamp]
* Cédric Moullet - [http://www.camptocamp.com Camptocamp]
* Robert Hollingsworth

OpenRouter

2009-04-21T21:06:41Z

Wiki-Woodbri: /* Testing */

== Open Source Router ==

For those not familiar with the concept, routing provides the path between two locations. Often there can be criteria considered such as time, cost, and so forth.

===Project Purpose===

The intention of this project is to work towards creation of open source software providing routing capability.

===Design goals===

Desired attributes:
* Library Coded in C (or C wrapper to C++)
* This library could SWIG wrapped for integration into scripting languages, or used in RDBMS engines like pgRouting in PostgreSQL, or via a command line or webservice tools.
* Architected and designed for performance. An ideal goal would be to handle graphs in the ballpark of 25-35 million edges and able to generate sub-sec responses.
* Abstracted storage to allow for use of data from various sources e.g. shapefiles, RDBMS, others
* Support multiple subject-matter domains, outside of transportation, such as utility and telecom networks

===Contact information===

Please join us on the [http://lists.osgeo.org/mailman/listinfo/routergeocoder mailing list].

NOTE: This mailing list is shared between this project and the [http://wiki.osgeo.org/wiki/OpenGeocoder OpenGeocoder] project.

===Relevant Existing Open Source Technologies===

* [http://pgrouting.postlbs.org/ pgRouting]
* GRASS GIS v.net.* modules see:
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.html - Vector maintenance
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.path.html - Shortest path
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.salesman.html - Traveling salesman (round trip)
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.alloc.html - Allocation of sources (create subnetworks)
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.steiner.html - Minimum Steiner trees (star-like connections)
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.visibility.html - Visibility graph construction
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.iso.html - Iso-distances (from centers)
* [http://graphserver.sourceforge.net/ GraphServer]

===Target Licensing===

* Preference for a liberal license to encourage adoption by maximum number of technologies both proprietary and open source

===Project Support===

====Development====

The following list are people who are interested in participating in development of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Daniel Kastl - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Stephen Woodbridge - http://imaptools.com/
* Claude Philipona - [http://www.camptocamp.com Camptocamp]
* Dimitris Kotzinos - OSGeo Greece (possibly ...)
* Robert Hollingsworth
* Paul Ramsey - [http://www.cleverelephant.ca Clever Elephant]

====Testing====

The following list are people who are interested in participating in testing of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Daniel Kastl - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* [[Stephen Woodbridge]] - http://imaptools.com/
* Dirk Frigne - [http://www.frigne.be Dirk Frigne] | [http://www.geomajas.org Geomajas]
* Claude Philipona - [http://www.camptocamp.com Camptocamp]

====Consumers====

The following list are people that plan to make use of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Dave McIlhagga - [http://wwww.dmsolutions.ca DM Solutions Group]
* Daniel Kastl - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* [[Stephen Woodbridge]] - http://imaptools.com/
* V.Ravi Kumar - OSGeo India
* Dimitris Kotzinos - OSGeo Greece
* Dirk Frigne - [http://www.frigne.be Dirk Frigne] | [http://www.geomajas.org Geomajas]
* David Jonglez - [http://www.camptocamp.com Camptocamp]
* Claude Philipona - [http://www.camptocamp.com Camptocamp]
* Cédric Moullet - [http://www.camptocamp.com Camptocamp]
* Robert Hollingsworth

OpenRouter

2009-04-21T21:06:23Z

Wiki-Woodbri: /* Consumers */

== Open Source Router ==

For those not familiar with the concept, routing provides the path between two locations. Often there can be criteria considered such as time, cost, and so forth.

===Project Purpose===

The intention of this project is to work towards creation of open source software providing routing capability.

===Design goals===

Desired attributes:
* Library Coded in C (or C wrapper to C++)
* This library could SWIG wrapped for integration into scripting languages, or used in RDBMS engines like pgRouting in PostgreSQL, or via a command line or webservice tools.
* Architected and designed for performance. An ideal goal would be to handle graphs in the ballpark of 25-35 million edges and able to generate sub-sec responses.
* Abstracted storage to allow for use of data from various sources e.g. shapefiles, RDBMS, others
* Support multiple subject-matter domains, outside of transportation, such as utility and telecom networks

===Contact information===

Please join us on the [http://lists.osgeo.org/mailman/listinfo/routergeocoder mailing list].

NOTE: This mailing list is shared between this project and the [http://wiki.osgeo.org/wiki/OpenGeocoder OpenGeocoder] project.

===Relevant Existing Open Source Technologies===

* [http://pgrouting.postlbs.org/ pgRouting]
* GRASS GIS v.net.* modules see:
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.html - Vector maintenance
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.path.html - Shortest path
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.salesman.html - Traveling salesman (round trip)
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.alloc.html - Allocation of sources (create subnetworks)
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.steiner.html - Minimum Steiner trees (star-like connections)
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.visibility.html - Visibility graph construction
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.iso.html - Iso-distances (from centers)
* [http://graphserver.sourceforge.net/ GraphServer]

===Target Licensing===

* Preference for a liberal license to encourage adoption by maximum number of technologies both proprietary and open source

===Project Support===

====Development====

The following list are people who are interested in participating in development of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Daniel Kastl - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Stephen Woodbridge - http://imaptools.com/
* Claude Philipona - [http://www.camptocamp.com Camptocamp]
* Dimitris Kotzinos - OSGeo Greece (possibly ...)
* Robert Hollingsworth
* Paul Ramsey - [http://www.cleverelephant.ca Clever Elephant]

====Testing====

The following list are people who are interested in participating in testing of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Daniel Kastl - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Stephen Woodbridge - http://imaptools.com/
* Dirk Frigne - [http://www.frigne.be Dirk Frigne] | [http://www.geomajas.org Geomajas]
* Claude Philipona - [http://www.camptocamp.com Camptocamp]

====Consumers====

The following list are people that plan to make use of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Dave McIlhagga - [http://wwww.dmsolutions.ca DM Solutions Group]
* Daniel Kastl - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* [[Stephen Woodbridge]] - http://imaptools.com/
* V.Ravi Kumar - OSGeo India
* Dimitris Kotzinos - OSGeo Greece
* Dirk Frigne - [http://www.frigne.be Dirk Frigne] | [http://www.geomajas.org Geomajas]
* David Jonglez - [http://www.camptocamp.com Camptocamp]
* Claude Philipona - [http://www.camptocamp.com Camptocamp]
* Cédric Moullet - [http://www.camptocamp.com Camptocamp]
* Robert Hollingsworth

OpenRouter

2009-04-03T21:08:21Z

Wiki-Woodbri: /* Design goals */

== Open Source Router ==

For those not familiar with the concept, routing provides the path between two locations. Often there can be criteria considered such as time, cost, and so forth.

===Project Purpose===

The intention of this project is to work towards creation of open source software providing routing capability.

===Design goals===

Desired attributes:
* Library Coded in C (or C wrapper to C++)
* This library could SWIG wrapped for integration into scripting languages, or used in RDBMS engines like pgRouting in PostgreSQL, or via a command line or webservice tools.
* Architected and designed for performance. An ideal goal would be to handle graphs in the ballpark of 25-35 million edges and able to generate sub-sec responses.
* Abstracted storage to allow for use of data from various sources e.g. shapefiles, RDBMS, others
* Support multiple subject-matter domains, outside of transportation, such as utility and telecom networks

===Contact information===

Please join us on the [http://lists.osgeo.org/mailman/listinfo/routergeocoder mailing list].

NOTE: This mailing list is shared between this project and the [http://wiki.osgeo.org/wiki/OpenGeocoder OpenGeocoder] project.

===Relevant Existing Open Source Technologies===

* [http://pgrouting.postlbs.org/ pgRouting]
* GRASS GIS v.net.* modules see:
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.html - Vector maintenance
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.path.html - Shortest path
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.salesman.html - Traveling salesman (round trip)
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.alloc.html - Allocation of sources (create subnetworks)
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.steiner.html - Minimum Steiner trees (star-like connections)
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.visibility.html - Visibility graph construction
** http://grass.osgeo.org/grass64/manuals/html64_user/v.net.iso.html - Iso-distances (from centers)
* [http://graphserver.sourceforge.net/ GraphServer]

===Target Licensing===

* Preference for a liberal license to encourage adoption by maximum number of technologies both proprietary and open source

===Project Support===

====Development====

The following list are people who are interested in participating in development of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Daniel Kastl - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Stephen Woodbridge - http://imaptools.com/
* Claude Philipona - [http://www.camptocamp.com Camptocamp]
* Dimitris Kotzinos - OSGeo Greece (possibly ...)
* Robert Hollingsworth
* Paul Ramsey - [http://www.cleverelephant.ca Clever Elephant]

====Testing====

The following list are people who are interested in participating in testing of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Daniel Kastl - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Stephen Woodbridge - http://imaptools.com/
* Dirk Frigne - [http://www.frigne.be Dirk Frigne] | [http://www.geomajas.org Geomajas]
* Claude Philipona - [http://www.camptocamp.com Camptocamp]

====Consumers====

The following list are people that plan to make use of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Dave McIlhagga - [http://wwww.dmsolutions.ca DM Solutions Group]
* Daniel Kastl - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://postlbs.pgrouting.org pgRouting] | [http://www.orkney.co.jp Orkney]
* Stephen Woodbridge - http://imaptools.com/
* V.Ravi Kumar - OSGeo India
* Dimitris Kotzinos - OSGeo Greece
* Dirk Frigne - [http://www.frigne.be Dirk Frigne] | [http://www.geomajas.org Geomajas]
* David Jonglez - [http://www.camptocamp.com Camptocamp]
* Claude Philipona - [http://www.camptocamp.com Camptocamp]
* Cédric Moullet - [http://www.camptocamp.com Camptocamp]
* Robert Hollingsworth

OpenGeocoder

2009-03-27T19:53:53Z

Wiki-Woodbri:

== Open Source Geocoder ==

For those not familiar with the concept, Geocoding takes a human readable address and turns it into coordinates.

===Project Purpose===

The intention of this project is to work towards creation of open source software providing geocoding capability.

===Google Summer of Code Ideas===

We have proposed some ideas for Google Summer of Code projects. You can read more about them [[OpenGeocoder 2009 SOC Ideas]].

===Design goals===

Desired attributes:
* Handle international addressing schemes (expected to be pluggable to support internationalization)
* Library Coded in C (or C wrapper to C++)
* Architected and designed for performance
* Abstracted storage to allow for use of data from various sources e.g. shapefiles, RDBMS, others

===Contact information===

Please join us on the [http://lists.osgeo.org/mailman/listinfo/routergeocoder mailing list].

NOTE: This mailing list is shared between this project and the [http://wiki.osgeo.org/wiki/OpenRouter OpenRouter] project.

===Relevant Existing Open Source Technologies===

* [http://www.extendthereach.com/products/OpenSourceGeocoder.srct SRC Explorer Geocoder]
* [http://www.geocoder.us Geocoder.us]
* [http://www.postlbs.org/en/geocoder PostLBS]
* [http://www.pagcgeo.org PAGC]

===Target Licensing===

* Preference for a liberal license to encourage adoption by maximum number of technologies both proprietary and open source

===Project Support===

====Development====

The following list are people who are interested in participating in development of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Andrew Turner - [http://www.geocommons.com GeoCommons] & [http://www.highearthorbit.com HighEarthOrbit]
* Daniel Kastl - [http://pggeocoder.postlbs.org/ pgGeocoder] | [http://postlbs.org/en/geocoder Geocoder.ja] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://pggeocoder.postlbs.org/ pgGeocoder] | [http://postlbs.org/en/geocoder Geocoder.ja] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://pggeocoder.postlbs.org/ pgGeocoder] | [http://postlbs.org/en/geocoder Geocoder.ja] | [http://www.orkney.co.jp Orkney]
* Stephen Woodbridge - http://imaptools.com/
* Robert Hollingsworth

====Testing====

The following list are people who are interested in participating in testing of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Andrew Turner - [http://www.geocommons.com GeoCommons] & [http://www.highearthorbit.com HighEarthOrbit]
* Daniel Kastl - [http://pggeocoder.postlbs.org/ pgGeocoder] | [http://postlbs.org/en/geocoder Geocoder.ja] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://pggeocoder.postlbs.org/ pgGeocoder] | [http://postlbs.org/en/geocoder Geocoder.ja] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://pggeocoder.postlbs.org/ pgGeocoder] | [http://postlbs.org/en/geocoder Geocoder.ja] | [http://www.orkney.co.jp Orkney]
* Stephen Woodbridge - http://imaptools.com/
* Ian Turton - [http://www.geovista.psu.edu/members/turton/index.html GeoVISTA Center ]

====Consumers====

The following list are people that plan to make use of this project:

* Andrew Ross - [http://community.ingres.com/wiki/IngresGeospatial Ingres] / [http://fosslc.org fosslc.org]
* Dave McIlhagga - [http://wwww.dmsolutions.ca DM Solutions Group]
* Andrew Turner - [http://www.geocommons.com GeoCommons] & [http://www.highearthorbit.com HighEarthOrbit]
* Daniel Kastl - [http://pggeocoder.postlbs.org/ pgGeocoder] | [http://postlbs.org/en/geocoder Geocoder.ja] | [http://www.orkney.co.jp Orkney]
* Anton Patrushev - [http://pggeocoder.postlbs.org/ pgGeocoder] | [http://postlbs.org/en/geocoder Geocoder.ja] | [http://www.orkney.co.jp Orkney]
* Toru Mori - [http://pggeocoder.postlbs.org/ pgGeocoder] | [http://postlbs.org/en/geocoder Geocoder.ja] | [http://www.orkney.co.jp Orkney]
* Stephen Woodbridge - http://imaptools.com/
* V.Ravi Kumar - OSGeo India
* Yves Jacolin - OSGeo-fr, HBS-Research (http://geocoder.gloobe.org/)
* Ian Turton - [http://www.geovista.psu.edu/members/turton/index.html GeoVISTA Center ]
* David Jonglez - [http://wwww.camptocamp.com Camptocamp]
* Claude Philipona - [http://wwww.camptocamp.com Camptocamp]
* Cédric Moullet - [http://wwww.camptocamp.com Camptocamp]
* Robert Hollingsworth

OpenGeocoder 2009 SOC Ideas

2009-03-26T18:38:16Z

Wiki-Woodbri: /* PAGC Landmark Gecoder */

* Back to the main OSGeo [[Google Summer of Code 2009]] wiki page.
* Back to the main OSGeo [[Google Summer of Code 2009 Ideas]] wiki page.

= OpenGeocoder 2009 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 OpenGeocoder. Our current efforts are based on the PAGC code. This is a C language geocoder You can read more about it at:

[http://www.pagcgeo.org/ PAGC Home] that has links to download the code and to sign up for the email list.

== PAGC Code Refactoring ==

We currently have a project proposal rework the existing code to make it support SQL database(s) and to restructure it to be more modular. [http://www.deadwrite.com/pagc_restructure.pdf Project Proposal] (PDF).

== PAGC Landmark Gecoder ==

This is a project proposal that would standardize non-address type landmarks and handle geocoder requests for them. [http://www.deadwrite.com/landmarks.pdf Project Proposal] (PDF).

== PAGC Build Address parsing and standardization tools for countries ==

We currently have an address standardizer that is partially data driven, based on a Lexicon and a Gazetteer for a given reference data set. We currently have support for US Tiger data and Canada Road Network File records. We will be building similar ones for Navteq North America data. It would be interesting to integrate something like OSM (OpenStreetMap) data or other country data sets as a reference data set for any given country and have Lexicons and Gazetteers to match.

== PAGC OpenLS compatible API ==

PAGC currently has web API that allows it to handle web requests and return XML documents. [http://www.opengeospatial.org/standards/ols OpenLS] is an OGC standard for Open Location Services. OpenLS has many features described as [http://www.opengeospatial.org/standards/ols OpenLS] but we would be interested in support those appropriate to PAGC.

= Mentor Candidates =

The following individuals are potentially willing to serve as OpenGeocoder/PAGC mentors or co-mentors.

* Stephen Woodbridge

[[Category:Google Summer of Code]]

OpenGeocoder 2009 SOC Ideas

2009-03-26T18:35:30Z

Wiki-Woodbri: /* PAGC Code Refactoring */

* Back to the main OSGeo [[Google Summer of Code 2009]] wiki page.
* Back to the main OSGeo [[Google Summer of Code 2009 Ideas]] wiki page.

= OpenGeocoder 2009 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 OpenGeocoder. Our current efforts are based on the PAGC code. This is a C language geocoder You can read more about it at:

[http://www.pagcgeo.org/ PAGC Home] that has links to download the code and to sign up for the email list.

== PAGC Code Refactoring ==

We currently have a project proposal rework the existing code to make it support SQL database(s) and to restructure it to be more modular. [http://www.deadwrite.com/pagc_restructure.pdf Project Proposal] (PDF).

== PAGC Landmark Gecoder ==

This is a project proposal that would standardize non-address type landmarks and handle geocoder requests for them. '''Need to link PDF proposal here.'''

== PAGC Build Address parsing and standardization tools for countries ==

We currently have an address standardizer that is partially data driven, based on a Lexicon and a Gazetteer for a given reference data set. We currently have support for US Tiger data and Canada Road Network File records. We will be building similar ones for Navteq North America data. It would be interesting to integrate something like OSM (OpenStreetMap) data or other country data sets as a reference data set for any given country and have Lexicons and Gazetteers to match.

== PAGC OpenLS compatible API ==

PAGC currently has web API that allows it to handle web requests and return XML documents. [http://www.opengeospatial.org/standards/ols OpenLS] is an OGC standard for Open Location Services. OpenLS has many features described as [http://www.opengeospatial.org/standards/ols OpenLS] but we would be interested in support those appropriate to PAGC.

= Mentor Candidates =

The following individuals are potentially willing to serve as OpenGeocoder/PAGC mentors or co-mentors.

* Stephen Woodbridge

[[Category:Google Summer of Code]]

OpenGeocoder 2009 SOC Ideas

2009-03-26T04:33:43Z

Wiki-Woodbri: New page: * Back to the main OSGeo Google Summer of Code 2009 wiki page. * Back to the main OSGeo Google Summer of Code 2009 Ideas wiki page. = OpenGeocoder 2009 SoC Ideas = Enter ideas f...

* Back to the main OSGeo [[Google Summer of Code 2009]] wiki page.
* Back to the main OSGeo [[Google Summer of Code 2009 Ideas]] wiki page.

= OpenGeocoder 2009 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 OpenGeocoder. Our current efforts are based on the PAGC code. This is a C language geocoder You can read more about it at:

[http://www.pagcgeo.org/ PAGC Home] that has links to download the code and to sign up for the email list.

== PAGC Code Refactoring ==

We currently have a project proposal rework the existing code to make it support SQL database(s) and to restructure it to be more modular. '''Need to link PDF proposal here.'''

== PAGC Landmark Gecoder ==

This is a project proposal that would standardize non-address type landmarks and handle geocoder requests for them. '''Need to link PDF proposal here.'''

== PAGC Build Address parsing and standardization tools for countries ==

We currently have an address standardizer that is partially data driven, based on a Lexicon and a Gazetteer for a given reference data set. We currently have support for US Tiger data and Canada Road Network File records. We will be building similar ones for Navteq North America data. It would be interesting to integrate something like OSM (OpenStreetMap) data or other country data sets as a reference data set for any given country and have Lexicons and Gazetteers to match.

== PAGC OpenLS compatible API ==

PAGC currently has web API that allows it to handle web requests and return XML documents. [http://www.opengeospatial.org/standards/ols OpenLS] is an OGC standard for Open Location Services. OpenLS has many features described as [http://www.opengeospatial.org/standards/ols OpenLS] but we would be interested in support those appropriate to PAGC.

= Mentor Candidates =

The following individuals are potentially willing to serve as OpenGeocoder/PAGC mentors or co-mentors.

* Stephen Woodbridge

[[Category:Google Summer of Code]]

Google Summer of Code 2009 Ideas

2009-03-26T03:59:55Z

Wiki-Woodbri: /* The ideas pages */

[[Image:2009_summer_of_code_logo_final_r3-01.png|center|250px]]

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

=OSGeo Google Summer of Code 2009=
The 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 soc at lists.osgeo.org'''

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

=What to expect during the summer?=

==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 intergrate you into the developer community, so you should get involved 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.

==Weekly reports==
Yes, every week we expect to see a report 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?

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, be honest. 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==
In addition to weekly reports we ask you to maintain a wiki 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.

=Timeline=
http://socghop.appspot.com/document/show/program/google/gsoc2009/faqs#timeline

* March 18th 2009: Google announces accepted organisations. If OSGeo is accepted as an organization for Google Summer of Code, start talking to us earlier rather than later.
* April 3rd 2009: Student application deadline. The earlier you start the more probable it is that you will be accepted!
* April 20th 2009: Accepted student proposals are announced.
* May 23rd 2009: Coding begins!
* July 6th - July 13th: Mid-term evaluation.
* Agust 10th: Pencils down!

= The ideas pages =
Each participating project's list of ideas is here, with a short description of the project and what type of students would be interested in it.

* [http://trac.osgeo.org/gdal/wiki/SummerOfCode GDAL SoC Ideas]: GDAL is the Geographic Data Abstraction Library, a library which provides access to spatial data in all kinds of formats via a uniform API.
* [http://grass.osgeo.org/wiki/GRASS_SoC_Ideas GRASS SoC Ideas]: GRASS GIS is an open source GIS focusing mainly on analysis. It is written as a collection of stand-alone C programs and has a new GUI written in Python. If you know Python, or want to implement algorithms in C take a look!
* [http://www.mapbender.org/GSoC_2009 Mapbender SoC ideas 2009]: Mapbender is a server and client side geographic data management tool, programmed in '''PHP''' and '''JavaScript''', using the '''jQuery''' library.
* [http://wiki.qgis.org/qgiswiki/SummerOfCodeIdeas Quantum GIS SoC Ideas] Quantum GIS (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.
* [[MapServer 2009 SOC Ideas]]
* [http://geosoa.scg.ulaval.ca/en/index.php?module=pagemaster&PAGE_user_op=view_page&PAGE_id=20 Laval University 2009 SoC ideas]: Based on OpenLayers and other relevant software from OSGeo, this project aims at designing and developing a tool to produce rich and interactive geo-analytical dashboards. Such dashboards will serve as a front end for a range of Spatial OLAP technologies to better support decision makers, managers, etc. in making informed decisions.
* [http://geoserver.org/display/GEOS/Summer+of+Code+2009 GeoServer SoC 2009]: GeoServer supports Web Map Server, Web Feature Server and Web Coverage Service protocols. It makes spatial information available in a range of formats from GeoTIFF to KML. The application is Java EE based, making use of Spring to wire everything up. The application supports a plug-in system so student contributions can me distributed as they are ready.
* [http://docs.codehaus.org/display/GEOTOOLS/Summer+of+Code+2009 GeoTools SoC 2009]: GeoTools is a Java toolkit for working with spatial data, it covers everything from bits on disk to rendering. It provides client code for WFS, WMS and supports a range of data sources like shapefile and PostGIS. The library is used by a lot of the Java applications on this page. The library has a plug-in system so students work can be distributed via maven as they are ready.
* [http://udig.refractions.net/confluence/display/HACK/Summer+of+Code uDig SoC 2009]: 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.
* [http://openjump.org/wiki/show/Google+Summer+Of+Code+Ideas+List OpenJUMP/deegree Ideas List]: deegree and OpenJUMP share code derived from the original JUMP. Both programs maintain separate development lists and source code repositories but look for opportunities to collaborate.
* [[OSGeo Cartographic Library]]: A cross-project effort to define a cartography output specification, and ideally, to create an example engine or set of scripts to produce high quality ''printable'' output. Then other projects can export to this standard and share in the benefit of a common engine.
* [[OpenGeocoder 2009 SOC Ideas]]: We are trying to focus our development efforts on PAGC that uses statistical record match and fuzzy searches. We are refactoring this code to make it more modular and reusable. We want to extend it with support for countries other than North America. We are also interested in making it OpenLS compatible for the geocoding components.

= What is the main public mailing list for your organization? =
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.

= What is the main IRC channel for your organization? =

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

Project irc channels:

* irc://irc.freenode.net/#geoserver
* irc://irc.freenode.net/#geotools
* irc://irc.freenode.net/#udig
* irc://irc.freenode.net/#mapbuilder
* irc://irc.freenode.net/#mapguide
* irc://irc.freenode.net/#mapserver
* irc://irc.freenode.net/#openlayers
* irc://irc.freenode.net/#gdal
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#grass
* irc://irc.freenode.net/#qgis
* irc://irc.freenode.net/#mapbender

[[Category:Google Summer of Code]]

Google Summer of Code 2009 Ideas

2009-03-26T03:58:48Z

Wiki-Woodbri: /* The ideas pages */

[[Image:2009_summer_of_code_logo_final_r3-01.png|center|250px]]

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

=OSGeo Google Summer of Code 2009=
The 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 soc at lists.osgeo.org'''

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

=What to expect during the summer?=

==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 intergrate you into the developer community, so you should get involved 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.

==Weekly reports==
Yes, every week we expect to see a report 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?

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, be honest. 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==
In addition to weekly reports we ask you to maintain a wiki 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.

=Timeline=
http://socghop.appspot.com/document/show/program/google/gsoc2009/faqs#timeline

* March 18th 2009: Google announces accepted organisations. If OSGeo is accepted as an organization for Google Summer of Code, start talking to us earlier rather than later.
* April 3rd 2009: Student application deadline. The earlier you start the more probable it is that you will be accepted!
* April 20th 2009: Accepted student proposals are announced.
* May 23rd 2009: Coding begins!
* July 6th - July 13th: Mid-term evaluation.
* Agust 10th: Pencils down!

= The ideas pages =
Each participating project's list of ideas is here, with a short description of the project and what type of students would be interested in it.

* [http://trac.osgeo.org/gdal/wiki/SummerOfCode GDAL SoC Ideas]: GDAL is the Geographic Data Abstraction Library, a library which provides access to spatial data in all kinds of formats via a uniform API.
* [http://grass.osgeo.org/wiki/GRASS_SoC_Ideas GRASS SoC Ideas]: GRASS GIS is an open source GIS focusing mainly on analysis. It is written as a collection of stand-alone C programs and has a new GUI written in Python. If you know Python, or want to implement algorithms in C take a look!
* [http://www.mapbender.org/GSoC_2009 Mapbender SoC ideas 2009]: Mapbender is a server and client side geographic data management tool, programmed in '''PHP''' and '''JavaScript''', using the '''jQuery''' library.
* [http://wiki.qgis.org/qgiswiki/SummerOfCodeIdeas Quantum GIS SoC Ideas] Quantum GIS (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.
* [[MapServer 2009 SOC Ideas]]
* [http://geosoa.scg.ulaval.ca/en/index.php?module=pagemaster&PAGE_user_op=view_page&PAGE_id=20 Laval University 2009 SoC ideas]: Based on OpenLayers and other relevant software from OSGeo, this project aims at designing and developing a tool to produce rich and interactive geo-analytical dashboards. Such dashboards will serve as a front end for a range of Spatial OLAP technologies to better support decision makers, managers, etc. in making informed decisions.
* [http://geoserver.org/display/GEOS/Summer+of+Code+2009 GeoServer SoC 2009]: GeoServer supports Web Map Server, Web Feature Server and Web Coverage Service protocols. It makes spatial information available in a range of formats from GeoTIFF to KML. The application is Java EE based, making use of Spring to wire everything up. The application supports a plug-in system so student contributions can me distributed as they are ready.
* [http://docs.codehaus.org/display/GEOTOOLS/Summer+of+Code+2009 GeoTools SoC 2009]: GeoTools is a Java toolkit for working with spatial data, it covers everything from bits on disk to rendering. It provides client code for WFS, WMS and supports a range of data sources like shapefile and PostGIS. The library is used by a lot of the Java applications on this page. The library has a plug-in system so students work can be distributed via maven as they are ready.
* [http://udig.refractions.net/confluence/display/HACK/Summer+of+Code uDig SoC 2009]: 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.
* [http://openjump.org/wiki/show/Google+Summer+Of+Code+Ideas+List OpenJUMP/deegree Ideas List]: deegree and OpenJUMP share code derived from the original JUMP. Both programs maintain separate development lists and source code repositories but look for opportunities to collaborate.
* [[OSGeo Cartographic Library]]: A cross-project effort to define a cartography output specification, and ideally, to create an example engine or set of scripts to produce high quality ''printable'' output. Then other projects can export to this standard and share in the benefit of a common engine.
* [[OpenGeocoder]]: We are trying to focus our development efforts on PAGC that uses statistical record match and fuzzy searches. We are refactoring this code to make it more modular and reusable. We want to extend it with support for countries other than North America. We are also interested in making it OpenLS compatible for the geocoding components.

= What is the main public mailing list for your organization? =
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.

= What is the main IRC channel for your organization? =

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

Project irc channels:

* irc://irc.freenode.net/#geoserver
* irc://irc.freenode.net/#geotools
* irc://irc.freenode.net/#udig
* irc://irc.freenode.net/#mapbuilder
* irc://irc.freenode.net/#mapguide
* irc://irc.freenode.net/#mapserver
* irc://irc.freenode.net/#openlayers
* irc://irc.freenode.net/#gdal
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#grass
* irc://irc.freenode.net/#qgis
* irc://irc.freenode.net/#mapbender

[[Category:Google Summer of Code]]

Google Summer of Code 2009 Ideas

2009-03-26T03:45:26Z

Wiki-Woodbri: /* The ideas pages */

[[Image:2009_summer_of_code_logo_final_r3-01.png|center|250px]]

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

=OSGeo Google Summer of Code 2009=
The 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 soc at lists.osgeo.org'''

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

=What to expect during the summer?=

==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 intergrate you into the developer community, so you should get involved 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.

==Weekly reports==
Yes, every week we expect to see a report 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?

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, be honest. 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==
In addition to weekly reports we ask you to maintain a wiki 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.

=Timeline=
http://socghop.appspot.com/document/show/program/google/gsoc2009/faqs#timeline

* March 18th 2009: Google announces accepted organisations. If OSGeo is accepted as an organization for Google Summer of Code, start talking to us earlier rather than later.
* April 3rd 2009: Student application deadline. The earlier you start the more probable it is that you will be accepted!
* April 20th 2009: Accepted student proposals are announced.
* May 23rd 2009: Coding begins!
* July 6th - July 13th: Mid-term evaluation.
* Agust 10th: Pencils down!

= The ideas pages =
Each participating project's list of ideas is here, with a short description of the project and what type of students would be interested in it.

* [http://trac.osgeo.org/gdal/wiki/SummerOfCode GDAL SoC Ideas]: GDAL is the Geographic Data Abstraction Library, a library which provides access to spatial data in all kinds of formats via a uniform API.
* [http://grass.osgeo.org/wiki/GRASS_SoC_Ideas GRASS SoC Ideas]: GRASS GIS is an open source GIS focusing mainly on analysis. It is written as a collection of stand-alone C programs and has a new GUI written in Python. If you know Python, or want to implement algorithms in C take a look!
* [http://www.mapbender.org/GSoC_2009 Mapbender SoC ideas 2009]: Mapbender is a server and client side geographic data management tool, programmed in '''PHP''' and '''JavaScript''', using the '''jQuery''' library.
* [http://wiki.qgis.org/qgiswiki/SummerOfCodeIdeas Quantum GIS SoC Ideas] Quantum GIS (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.
* [[MapServer 2009 SOC Ideas]]
* [http://geosoa.scg.ulaval.ca/en/index.php?module=pagemaster&PAGE_user_op=view_page&PAGE_id=20 Laval University 2009 SoC ideas]: Based on OpenLayers and other relevant software from OSGeo, this project aims at designing and developing a tool to produce rich and interactive geo-analytical dashboards. Such dashboards will serve as a front end for a range of Spatial OLAP technologies to better support decision makers, managers, etc. in making informed decisions.
* [http://geoserver.org/display/GEOS/Summer+of+Code+2009 GeoServer SoC 2009]: GeoServer supports Web Map Server, Web Feature Server and Web Coverage Service protocols. It makes spatial information available in a range of formats from GeoTIFF to KML. The application is Java EE based, making use of Spring to wire everything up. The application supports a plug-in system so student contributions can me distributed as they are ready.
* [http://docs.codehaus.org/display/GEOTOOLS/Summer+of+Code+2009 GeoTools SoC 2009]: GeoTools is a Java toolkit for working with spatial data, it covers everything from bits on disk to rendering. It provides client code for WFS, WMS and supports a range of data sources like shapefile and PostGIS. The library is used by a lot of the Java applications on this page. The library has a plug-in system so students work can be distributed via maven as they are ready.
* [http://udig.refractions.net/confluence/display/HACK/Summer+of+Code uDig SoC 2009]: 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.
* [http://openjump.org/wiki/show/Google+Summer+Of+Code+Ideas+List OpenJUMP/deegree Ideas List]: deegree and OpenJUMP share code derived from the original JUMP. Both programs maintain separate development lists and source code repositories but look for opportunities to collaborate.
* [[OSGeo Cartographic Library]]: A cross-project effort to define a cartography output specification, and ideally, to create an example engine or set of scripts to produce high quality ''printable'' output. Then other projects can export to this standard and share in the benefit of a common engine.
* [[PAGC Geocoder]]: PAGC is an OpenSource geocoder using statistical record match and fuzzy searches. We are refactoring this code to make it more modular and reusable. We want to extend it with support for countries other than North America. We are also interested in making it OpenLS compatible for the geocoding components.

= What is the main public mailing list for your organization? =
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.

= What is the main IRC channel for your organization? =

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

Project irc channels:

* irc://irc.freenode.net/#geoserver
* irc://irc.freenode.net/#geotools
* irc://irc.freenode.net/#udig
* irc://irc.freenode.net/#mapbuilder
* irc://irc.freenode.net/#mapguide
* irc://irc.freenode.net/#mapserver
* irc://irc.freenode.net/#openlayers
* irc://irc.freenode.net/#gdal
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#grass
* irc://irc.freenode.net/#qgis
* irc://irc.freenode.net/#mapbender

[[Category:Google Summer of Code]]

OpenGeocoder

2008-11-06T04:41:16Z

Wiki-Woodbri: /* Project Support */

OpenRouter

2008-11-06T04:40:04Z

Wiki-Woodbri: /* Project Support */

Stephen Woodbridge

2008-08-14T01:29:20Z

Wiki-Woodbri:

<tt>[[Category:OSGeo Member]]

Stephen Woodbridge is a member of the Mapserver PSC and has been actively using, supporting the Mapserver since 2000. Stephen also has worked extensively with kaMap, OpenLayers and does geospatial consulting via "http://imaptools.com/". Stephen has worked for two of the largest commercial users of mapserver. He has developed geocoders, reverse geocoders, mapping solutions using mapserver and OpenLayers and has written a prototype routing engine.

Stephen Woodbridge

2008-08-14T01:28:37Z

Wiki-Woodbri:

<tt>[[Category:OSGeo Member]]

Stephen Woodbridge is a member of the Mapserver PSC and has been actively using, supporting the Mapserver since 2000. Stephen also has worked extensively with kaMap, OpenLayers and does geospatial consulting via "http://imaptools.com/". Stephen has work for two of the largest commercial users of mapserver. He has developed geocoders, reverse geocoders, mapping solutions using mapserver and OpenLayers and has written a prototype routing engine.

Stephen Woodbridge

2008-08-14T01:16:58Z

Wiki-Woodbri: New page: "http://wiki.osgeo.org/wiki/Stephen_Woodbridge" <tt>Category:OSGeo Member

"http://wiki.osgeo.org/wiki/Stephen_Woodbridge"

<tt>[[Category:OSGeo Member]]

2008 Google SoC Application

2008-03-11T16:33:58Z

Wiki-Woodbri: /* Who will your mentors be? Please enter their Google Account address separated by commas. If your organization is accepted we will email each mentor to invite them to take part. (optional) */

==What is your Organization's Name?==
OSGeo - Open Source Geospatial Foundation

==What is your Organization's Homepage?==
http://www.osgeo.org/

==Describe your organization.==
OSGeo is an incorporated not-for-profit organization serving as an umbrella organization for the Open Source Geospatial community in general, and 14 projects in particular.

==Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating?==
We hope to get more students involved in open source geospatial development to grow the development community, and to advance particular projects. Additionally we hope to spread the word of open source GIS in the universities.

==Did your organization participate in previous GSoC years? If so, please summarize your involvement and the successes and failures of your student projects. (optional)==

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report.

OSGeo was formed in early 2006 and hadn't participated in GSoC before 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators are involved in this years OSGeo GSoC effort.

==If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)? (optional)==

==What license does your project use?==
Different projects operate under a variety of OSI approved licenses, mainly GPL, LGPL, and MIT/X.

==URL for your ideas page==
http://wiki.osgeo.org/wiki/Google_Summer_of_Code

==What is the main development mailing list for your organization?==
discuss@lists.osgeo.org - see http://lists.osgeo.org/mailman/listinfo/discuss

==Where is the main IRC channel for your organization?==
irc://irc.freenode.net/#osgeo

'''Project irc channels:'''
* irc://irc.freenode.net/#geoserver
* irc://irc.freenode.net/#geotools
* irc://irc.freenode.net/#udig
* irc://irc.freenode.net/#mapbuilder
* irc://irc.freenode.net/#mapguide
* irc://irc.freenode.net/#mapserver
* irc://irc.freenode.net/#openlayers
* irc://irc.freenode.net/#gdal
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#grass

==Does your organization have an application template you would like to see students use? If so, please provide it now. (optional)==

==Who will be your backup organization administrator? Please enter their Google Account address. We will email them to confirm, your organization will not become active until they respond. (optional)==
Frank Warmerdam - fwarmerdam

==About Your Mentors==
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
Mentors are selected by project steering comittees based on their reputation as skilled developers, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process.

===Who will your mentors be? Please enter their Google Account address separated by commas. If your organization is accepted we will email each mentor to invite them to take part. (optional)===
* fwarmerdam []gmail.com (Frank Warmerdam) - GDAL, MapServer
* wolf[]bergenheim.net (Wolf Bergenheim) - GRASS
* crschmidt []gmail.com (Christopher Schmidt) - OpenLayers
* shemange []gmail.com (Gary Sherman) - QGIS
* ottens []gmail.com (Steven Ottens) - Mapbuilder, OpenLayers
* dmorissette []gmail.com (Daniel Morissette) - MapServer, GDAL
* thomas.bonfort []gmail.com (Thomas Bonfort) - MapServer
* mloskot [] gmail.com (Mateusz Loskot) - GDAL
* assefay []gmail.com (Yewondwossen Assefa) - MapServer
* woodbri []swoodbridge.com (Stephen Woodbridge) - MapServer

==About The Program==
===What is your plan for dealing with disappearing students?===
'''Plan A:'''

In order to minimize the likelyhood of disappearing students we will ensure that the OSGeo administrative contact and the mentor have full contact information (email, home phone, etc) so that we can keep in touch with them.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require weekly progress reports, participation on public IRC channels and mailing lists will all help ensure ongoing commitment to the work.

'''Plan B:'''

Leveraging Open Source software from the OSGeo stack, coupled with high-accuracy data sources, volunteers from the open source community will process the data, including student metadata, and the results will be used for the targeting instructions for high-powered space-based lasers. Results of this will be displayed on a large video wall, which will prove that the student really has disappeared, and should act as a deterrent to future student disappearances.

http://www.jasonbirch.com/files/space_lasers.jpg
([http://ossim.telascience.org/ossimdata/nhv/DSCF0129.JPG resized from] )

===What is your plan for dealing with disappearing mentors?===
Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period.

===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
The steps taken depend on the individual projects, as example last year GeoTools project has asked for weekly attendence at IRC meetings or status email.

Further more the mentors are encouraged to actively involve the students in the community, but having the student interact with the mentor throught the community channels rather then directly.

Other possibilities include:
# Having potential students work with their potential mentor to prepare a brief plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the appropriate OSGeo or project-specific mailing list when they have reached a milestone, giving a brief description of the work completed to that date.
# Selecting students that have shown interest previously in the geospatial field.

===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===
The steps taken depend on the individual projects, as example last year GeoTools project asked that students act as a "module maintainer" for their work. This role has an expected level of support associated with it.

Apart from that, we are relying on the open development process and the appreciation that students will receive for implementing these needed features to provide positive feedback for the students. The projects will be encouraging the students to take ownership of their work, and to contribute in other areas they may be interested in. In some cases students may also have opportunities for future contract work if they make a good impression on community members.