https://wiki.osgeo.org/w/api.php?action=feedcontributions&user=Dkastl&feedformat=atomOSGeo - User contributions [en]2024-03-29T02:06:00ZUser contributionsMediaWiki 1.35.9https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2017_Ideas&diff=104840Google Summer of Code 2017 Ideas2017-01-23T16:24:37Z<p>Dkastl: /* Guest projects */ added pgRouting</p>
<hr />
<div><center><br />
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] <font size="+3"> @ </font> <br />
[[Image:OSGeo_300_127_pixel.png|300px|link=http://www.osgeo.org]]<br />
</center><br />
<br />
-----<br />
* Back to the main OSGeo [[Google Summer of Code 2017]] wiki page.<br />
<br />
* See also ideas from [[Google Summer of Code 2016 Ideas|2016]], [[Google Summer of Code 2015 Ideas|2015]], [[Google Summer of Code 2014 Ideas|2014]], [[Google Summer of Code 2013 Ideas|2013]], [[Google Summer of Code 2012 Ideas|2012]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2010 Ideas|2010]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[2008_SoC_Merged_Ideas|2008]], [[2007_SoC_Merged_Ideas|2007]].<br />
-----<br />
<br />
<br />
== OSGeo Google Summer of Code 2017 ==<br />
<br />
The [http://www.osgeo.org Open Source Geospatial Foundation] would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.<br />
<br />
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 and the future of the geospatial industry; show us what you've got!<br />
<br />
* '''Students: check out the [[Google Summer of Code Recommendations for Students]] page. If you need more information on how to apply you can contact all the mentors via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])<br />
<br />
* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.<br />
<br />
* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.<br />
<br />
* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google_Summer_of_Code_2017_Administrative]] wiki page.<br />
<br />
== The ideas pages ==<br />
'''''[Check back often, it's a work in progress]'''''<br />
<br />
<br />
Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:<br />
<br />
=== OSGeo Foundation member projects ===<br />
<br />
''More coming soon: Get started talking to your favorite project's development team today!''<br />
<br />
[[Image:logo-grass.png|60px|right]]<br />
* [https://trac.osgeo.org/grass/wiki/GSoC/2017 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look!<br />
<br />
<!--<br />
[[Image:logo-qgis.png|60px|right]]<br />
* [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2016 '''QGIS''' SoC Ideas]: [http://www.qgis.org QGIS] is a user friendly Open Source Geographic Information System (GIS) that runs on Linux, Unix, Mac OSX, and Windows. QGIS supports vector, raster, and database formats. It is written in C++ and Python.<br />
--><br />
<!--<br />
[[Image:logo-gdal.png|60px|right]]<br />
* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: [http://www.gdal.org GDAL] is a C++ library for reading and writing geospatial data raster and vector formats.<br />
--><br />
<!--<br />
* [http://trac.osgeo.org/osgeo4w/wiki/Reports '''OSGeo4W''']: - OSGeo4W is a binary distribution of a broad set of open source geospatial software for Win32 environments (Windows 7, XP, etc).<br />
[[Image:Logo-osgeo4w-mini.png|60px|right]]<br />
:* ''Idea'': We need to extend support to x64 based platforms to handle larger datasets and circumvent memory restrictions. This is a distribution and packaging project which will involve most/all of OSGeo member projects. (''ed. note: keep in mind that to fulfill GSoC requirements each project must have a majority coding component, so lots of scripting, testing, and Makefiles!'')<br />
--><br />
<br />
[[Image:logo-gvSIG.png|60px|right]]<br />
* [[GvSIG_GSoC_2017_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.com/en/web/guest/products/gvsig-desktop Desktop]. The gvSIG project looks for students with Java or Python skills that want to develop new ideas on this software. <br />
<br />
<!--<br />
[[Image:logo-opticks.png|right]]<br />
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: [http://opticks.org/ Opticks] is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.<br />
--><br />
<!-- <br />
[[Image:logo-postgis.png|60px|right]] <br />
* [http://trac.osgeo.org/postgis/wiki/GoogleSummerCode '''PostGIS''' Ideas]: [http://postgis.net PostGIS] spatially enables the popular PostgreSQL object-relational database, allowing it to be used as a back-end database for geographic information systems (GIS) and web-mapping applications.<br />
--><br />
<!--<br />
[[Image:logo-ossim.png|90px|right]]<br />
* [https://trac.osgeo.org/ossim/wiki/GSoC_2015 '''OSSIM''' SoC Ideas]: [http://trac.osgeo.org/ossim/wiki OSSIM] Open Source Software Image Map (OSSIM) is a high performance engine for remote sensing, image processing, geographical information systems and photogrammetry. The software has been under active development since 1996 and is deployed across a number of private, federal and civilian agencies. It is written in C++.<br />
--><br />
<!--<br />
[[Image:Logo_OTB.png|60px|right]]<br />
* [http://wiki.orfeo-toolbox.org/index.php/Proposals_for_GSoC_2015 '''OTB''' SoC Ideas]: [http://www.orfeo-toolbox.org ORFEO ToolBox] (OTB) is an open source library for remote sensing image processing.Targeted algorithms for high resolution optical images (Pleiades, SPOT, QuickBird, WorldView, Landsat, Ikonos), hyperspectral sensors (Hyperion) or SAR (TerraSarX, ERS, Palsar) are available. The software has been under active development since 2006 and is written in C++ and it includes also side projects also open source with GUI like Monteverdi. OTB has recently started the incubation process into OSGeo.<br />
--><br />
<!--<br />
[[Image:Mapserver.png|100px|right]]<br />
* [http://wiki.osgeo.org/wiki/MapServer_2015_SOC_Ideas '''Mapserver''' SoC Ideas]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.<br />
--><br />
<!--<br />
[[Image:Logo-istSOS.png|100px|right]]<br />
* [https://sourceforge.net/p/istsos/wiki/GSoC_ideas_2016 '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] is a complete sensor data management system for acquiring, storing and dispatching time-series observations. istSOS is compliant with the Sensor Observation Service (SOS) version 1.0 and 2.0 standard from the Open Geospatial Consortium (OGC) and offers unique extended capabilities to support scientific data analyses (integrated quality assurance, RESTful API, on the fly processing with virtual procedures, remote data aggregation and time-space re-projection etc.). istSOS core libraries are written in Python while it easy to use interface is Web based.<br />
--> <br />
<!--<br />
[[Image:logo-geos.png|60px|right]]<br />
* [http://trac.osgeo.org/geos/wiki/GSoC '''GEOS''' Ideas]: GEOS (Geometry Engine - Open Source) is a C++ port of the JTS Topology Suite (JTS). It includes the OpenGIS Simple Features for SQL spatial predicate functions and spatial operators, as well as specific JTS enhanced topology functions.<br />
--> <br />
<!--<br />
[[Image:logo-geoserver-crop.png|50px|right]]<br />
* [https://github.com/geoserver/geoserver/wiki/GSOC-Ideas GSOC Ideas]: [http://live.osgeo.org/en/overview/geoserver_overview.html '''GeoServer'''] is a web server that allows you to serve maps and data from a variety of formats to standard clients such as web browsers and desktop GIS applications. GeoServer works with the Open Geospatial Consortium (OGC) standards Web Feature Service (WFS), Web Coverage Service (WCS), Web Processing Service (WPS) and Web Map Service (WMS) standards.<br />
:* The GeoServer team asks applicants to introduce themselves on the geoserver-devel list ( Communicating in public is a key success factor to open source development )<br />
--><br />
<!--<br />
[[Image:Geotools-logo.png|50px|right]]<br />
* [http://docs.codehaus.org/display/GEOTOOLS/Google+Summer+of+Code ''GSOC'']: [http://live.osgeo.org/en/overview/geotools_overview.html '''GeoTools'''] GeoTools is an open source Java library for working with geospatial data, including both data access, data structures, processing and a powerful rendering engine. GeoTools is a modular library used in a wide range of web service, command line tools and desktop applications.<br />
--><br />
<!--<br />
[[Image:ZOO-Project-mini.png|right]]<br />
* [http://www.zoo-project.org/trac/wiki/ZOO_GSoC_Idea '''ZOO-Project''' Ideas]: [http://www.zoo-project.org ZOO-Project] is a WPS open source project released under a MIT/X-11 style license. It provides support for WPS 1.0.0 and 2.0.0 versions and is able to handle services implemented in various programming languages.<br />
--><br />
<!--<br />
We expect ideas also from [http://live.osgeo.org/en/overview/mapbender_overview.html MapBender], [http://live.osgeo.org/en/overview/geomoose_overview.html GeoMOOSE], [http://mapserver.org/ MapServer], ...<br />
--><br />
<!--<br />
[[Image:Osgeo-live.png|150px|right]]<br />
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2016 '''Osgeo-Live''' SoC Ideas]: [http://live.osgeo.org/en/index.html OSGeo-Live] is a self-contained bootable DVD, USB thumb drive or Virtual Machine based on Lubuntu, that allows you to try a wide variety of open source geospatial software without installing anything. It is composed entirely of free software, allowing it to be freely distributed, duplicated and passed around. It provides pre-configured applications for a range of geospatial use cases, including storage, publishing, viewing, analysis and manipulation of data. It also contains sample datasets and documentation.<br />
--><br />
<br />
=== Guest projects ===<br />
<br />
Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact the GSoC admin team, by sending an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]<br />
<br />
[[Image:Pgrouting-logo.png|60px|right]]<br />
* [https://github.com/pgRouting/pgrouting/wiki/GSoC-Ideas '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.<br />
<br />
<br />
<!--<br />
=== See also ===<br />
<br />
Other like minded projects do not participate to GSoC under OSGeo umbrella, but with their own organization. You may want to visit also their page:<br />
<br />
[[Image:Logo-osm6.png|60px|right]] <br />
* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2015/Project_Ideas '''OpenStreetMap''' Ideas]: [http://osm.org/ OSM] is a project aimed squarely at creating and providing free geographic data such as street maps to anyone who wants them. The project was started because most maps you think of as free actually have legal or technical restrictions on their use, holding back people from using them in creative, productive or unexpected ways.<br />
--><br />
<br />
=== Don't see in the list the project you're interested in? ===<br />
<br />
Contact them in their developers mailing list! Feel free to propose your own idea and get feedback!<br />
<br />
== I want to apply as a student ==<br />
<br />
Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.<br />
<br />
<br />
=== Which project do I choose? ===<br />
<br />
Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.<br />
: View the documents and download the ISO from http://live.osgeo.org<br />
[[File:Osgeolive wordle.png|500px|center]]<br />
<br />
=== Important dates ===<br />
<br />
* [https://developers.google.com/open-source/gsoc/timeline '''The official timeline''']<br />
<br />
<!-- {{done}} --><br />
* Feb 27: Google announces accepted organizations.<br />
: Please start talking to the dev communities you are interested in ''now''.<br />
* March 20: Student applications open.<br />
: The earlier you start the more probable it is that you will be accepted!<br />
: ''There is two way feedback during the application process which really helps you improve and clarify your application before the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''<br />
* April 3: Student application deadline.<br />
* May 4: '''Accepted student proposals are announced and Community Bonding Period begins.'''<br />
* May 30: '''Coding begins!'''<br />
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')<br />
* June 26 - 30: Phase 1 evaluation <br />
* July 28: Phase 2 evaluation<br />
* August 21-29: '''Pencils down!'''<br />
* August 29 - September 5: Final evaluations<br />
* September 6: Final results announced<br />
<br />
[Back to [[Google Summer of Code 2017]] @ OSGeo]<br />
[[Category: Google Summer of Code]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2016_Accepted&diff=98358Google Summer of Code 2016 Accepted2016-04-28T02:50:29Z<p>Dkastl: /* Accepted Proposals */</p>
<hr />
<div><center><br />
[[Image:GSoC2016Logo.jpg|500px|link=https://summerofcode.withgoogle.com/]] <font size="+3"> @ </font> [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]<br />
</center><br />
<br />
* Back to the main OSGeo [[Google Summer of Code 2016]] @ OSGeo wiki page.<br />
<br />
== Accepted Proposals ==<br />
<br />
This year OSGeo accepted 22 students working on the following projects.<br />
<br />
{|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;" <br />
|'''Community'''<br />
|'''Project'''<br />
|'''Student'''<br />
|'''1st mentor'''<br />
|'''2nd mentor'''<br />
|'''Links'''<br />
|-<br />
|GDAL<br />
|Introduce Triangulated Surface, Polyhedral Surface and Triangle API in the OGRGeometry core and implement their support in OGR drivers for GDAL <br />
|Avyav Kumar Singh<br />
|Rob Emanuele <br />
|Even Rouault<br />
|...<br />
|-<br />
|GDAL<br />
|GDAL DWG support <br />
|Alexandr Borzykh<br />
|Dmitry Baryshnikov <br />
|Even Rouault<br />
|...<br />
|-<br />
|GRASS GIS<br />
|Complete basic cartography suite in GRASS GIS wxGUI Map Display <br />
|Adam Laža<br />
|Anna Petrasova <br />
|Vaclav Petras<br />
|...<br />
|-<br />
|GRASS GIS<br />
|GRASS GIS - Additional segmentation algorithms for i.segment <br />
|Bo Yang<br />
|Moritz Lennert <br />
|Markus Neteler<br />
|...<br />
|-<br />
|GRASS GIS<br />
|GRASS GIS - PyQt implementation of GUI forms generated automatically from XML <br />
|Ondřej Pešek<br />
|Vaclav Petras <br />
|Anna Petrasova<br />
|...<br />
|-<br />
|GRASS GIS<br />
|GRASS GIS - WEBGRASS <br />
|Mayank Agrawal<br />
|Rashad Kanavath <br />
|Massimo Di Stefano<br />
|...<br />
|-<br />
|gvSIG<br />
|Add tests and educational games support to gvSIG Educa.<br />
|Carlos I. Colombana<br />
|Oscar Martinez<br />
|Joaquin del Cerro<br />
|...<br />
|-<br />
|gvSIG<br />
|Development of a model for woody debris flooding hazard in gvSIG<br />
|Silvia Franceschi<br />
|Andrea Antonello<br />
|Riccardo Rigon<br />
|...<br />
|-<br />
|istSOS<br />
|Android istSOS client<br />
|Cioloboc FlorinDaniel<br />
|Mirko Cardoso<br />
|Milan Antonovic<br />
|...<br />
|-<br />
|istSOS<br />
|istSOS Web API<br />
|Luka Glušica<br />
|Massimiliano Cannata<br />
|Milan Antonovic<br />
|...<br />
|-<br />
|istSOS<br />
|VistSOS: the istSOS Data Visualization Framework<br />
|Felipe Poveda<br />
|Milan Antonovic<br />
|Massimiliano Cannata<br />
|...<br />
|-<br />
|NASA World Wind<br />
|NASA Web World Wind - Multidimensional Visualization Tool for Environmental Variables<br />
|Gabriele Prestifilippo<br />
|Jakub Balhar<br />
|Patrick Hogan<br />
|...<br />
|-<br />
|OpenLayers3 - Google maps<br />
|OGC protocols support within OL3-Google-Maps<br />
|Samuel Lapointe<br />
|Alexandre Dube<br />
|Jessica Lapointe<br />
| [[OL3-GoogleMaps_GSoC_2016|Wiki]]<br />
|-<br />
|One bus Away<br />
|One bus Away Quick start<br />
|Brendan Egan<br />
|Og Crudden<br />
|Stefan Steiner<br />
|...<br />
|-<br />
|OSSIM<br />
|A complete photogrammetric OSSIM tool for automatic DSMs generation using multi-view optical and SAR images<br />
|Martina Di Rita<br />
|Oscar Kramer<br />
|Dave Burken<br />
|...<br />
|-<br />
|pgRouting<br />
|Flow Algorithms for pgRouting<br />
|Andrea Nardelli<br />
|Daniel Kastl<br />
|Vicky Vergara<br />
|[https://github.com/Illedran/pgrouting/wiki/GSoC-2016-Flow Github Wiki]<br />
|-<br />
|pgRouting<br />
|Implementation of a framework which supports addition of contraction techniques for pgRouting<br />
|Sankepally Rohith Reddy<br />
|Vicky Vergara<br />
|Daniel Kastl<br />
|[https://github.com/sankepallyrohithreddy/pgrouting/wiki/GSoc-2016-Contraction Github Wiki]<br />
|-<br />
|PyWPS<br />
|Remote Output Storage for PyWPS<br />
|Vikas Mishra<br />
|Jachym Cepicky<br />
|Jonas Eberle<br />
|...<br />
|-<br />
|PyWPS<br />
|Web-based administration & process management for PyWPS<br />
|Jan Rudolf<br />
|Jonas Eberle<br />
|Jachym Cepicky<br />
|...<br />
|-<br />
|QGIS<br />
|QGIS Styles, Symbols, and SVG Markers Sharing Repository<br />
|Akbar Gumbira<br />
|Alessandro Pasotti<br />
|Anita Graser<br />
|...<br />
|-<br />
|ZOO-Project<br />
|Bringing pyModis to the web through ZOO-Project<br />
|Chingchai Humhong<br />
|Luca Delucchi<br />
|Gerald Fenoy<br />
|...<br />
|-<br />
|ZOO-Project<br />
|Implementing WPS for Geopaparazzi field data collection tool using ZOO-Project: Simplifying integration of field data and GIS<br />
|Niroshan Sanjaya<br />
|Gerald Fenoy<br />
|Andrea Antonello<br />
|...<br />
|-<br />
|}<br />
<br />
See the [https://summerofcode.withgoogle.com/organizations/6273632556810240/ accepted projects on Google's platform].<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
[[Category: Google Summer of Code]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=PgRouting&diff=97604PgRouting2016-03-20T15:24:39Z<p>Dkastl: /* Project Deliverables */</p>
<hr />
<div>[http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality.<br />
<br />
PgRouting is an community project entering the foundation as part of the original OSGeo Labs initiative.<br />
<br />
== Basic Project Data ==<br />
*'''Project Name:''' pgRouting<br />
*'''Project Status Condition:''' Stable<br />
*'''Project Web Site:''' http://pgrouting.org<br />
*'''Project Contact:''' Daniel Kastl <project at pgrouting.org><br />
*'''Short Project Description:''' pgRouting adds routing functionality to PostGIS.<br />
<br />
== Project Infrastructure ==<br />
*'''Project Source Code:''' https://github.com/pgrouting/pgrouting<br />
*'''Project Mailing List:''' http://lists.osgeo.org/mailman/listinfo/pgrouting-users<br />
*'''Project Version Control Repository:''' git://github.com/pgRouting/pgrouting.git<br />
*'''Project Bug Tracker:''' https://github.com/pgrouting/pgrouting/issues<br />
*'''Project Feature Request Tracker:''' https://github.com/pgrouting/pgrouting/issues<br />
<br />
== Project Governance ==<br />
*'''Source Code License:''' [http://www.gnu.org/licenses/gpl-2.0.html GNU General Public License, version 2]<br />
*'''Documentation License:''' [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-Share Alike 3.0]<br />
*'''Copyright Assignment Policy:''' All contributions are licensed under the terms of the GNU General Public License, version 2 without explicit assignment<br />
*'''Decision Making Procedure:''' Project Steering Committee<br />
*'''Coding Standards:''' https://github.com/pgRouting/pgrouting/wiki/2.0-Development-Guidelines-and-Standards<br />
*'''Release Procedure:''' https://github.com/pgRouting/pgrouting/wiki/pgRouting-Release-Process-Checklist<br />
<br />
== Project Deliverables ==<br />
*'''Latest Project Release:''' Version 2.1.0 (September 2015)<br />
<br />
[[Category: OSGeo Labs]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2016_Administrative&diff=97023Google Summer of Code 2016 Administrative2016-03-03T08:52:33Z<p>Dkastl: /* Mentors */</p>
<hr />
<div><center><br />
[[Image:GSoC2016Logo.jpg|500px|link=https://summerofcode.withgoogle.com/]] <font size="+3"> @ </font> [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]<br />
</center><br />
<br />
* Back to the main OSGeo [[Google Summer of Code 2016]] @ OSGeo wiki page.<br />
<br />
This is the central page for OSGeo administrative information in Google Summer of Code 2016.<br />
<br />
== GSoC general information ==<br />
<br />
* [https://developers.google.com/open-source/gsoc/timeline The official timeline]<br />
* [https://developers.google.com/open-source/gsoc/resources/ Google's FAQ on the program]<br />
* [https://summerofcode.withgoogle.com/ Official 2016 GSoC site]<br />
<br />
== Contacts == <br />
<br />
* [[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!<br />
<br />
* 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!<br />
<br />
== Mentors ==<br />
<br />
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:<br />
<br />
{|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;" <br />
|width=30px|'''Number'''<br />
|width=100px|'''Name'''<br />
|width=100px|'''Surname'''<br />
|width=100px|'''Nickname (IRC)'''<br />
|width=200px|'''email'''<br />
|width=100px|'''Software'''<br />
|'''Project / Idea(s) you are available to mentor'''<br />
|-<br />
|1<br />
|Margherita<br />
|Di Leo <br />
|madi<br />
|diregola AT gmail DOT com <br />
|admin at OSGeo<br />
|Administrator of GSoC at OSGeo<br />
|-<br />
|2<br />
|Alexander<br />
|Bruy <br />
|alexbruy<br />
|alexander.bruy AT gmail.com <br />
|QGIS<br />
|QGIS<br />
|-<br />
|3<br />
|Victor<br />
|Olaya <br />
|volaya<br />
|volayaf AT gmail DOT com <br />
|QGIS<br />
|QGIS<br />
|-<br />
|4<br />
|Daniel<br />
|Kastl<br />
|dkastl<br />
|daniel AT georepublic DOT de <br />
|pgRouting<br />
|pgRouting<br />
|-<br />
|}<br />
<br />
== A Mentor's Responsibilities ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Guides for mentors ==<br />
<br />
* [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.<br />
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]<br />
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]<br />
<br />
== Learn more ==<br />
<br />
* 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]<br />
<br />
* 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]]<br />
<br />
* 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]] <br />
<br />
<br />
[[Category: Google Summer of Code]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2016_Ideas&diff=96644Google Summer of Code 2016 Ideas2016-02-17T07:03:11Z<p>Dkastl: uncommented pgRouting</p>
<hr />
<div><center><br />
[[Image:GSoC2016Logo.jpg|500px|link=https://summerofcode.withgoogle.com/]] <font size="+3"> @ </font> <br />
[[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]<br />
</center><br />
<br />
-----<br />
* Back to the main OSGeo [[Google Summer of Code 2016]] wiki page.<br />
<br />
* See also ideas from [[2007_SoC_Merged_Ideas|2007]], [[2008_SoC_Merged_Ideas|2008]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[Google Summer of Code 2010 Ideas|2010]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2012 Ideas|2012]], [[Google Summer of Code 2013 Ideas|2013]] , [[Google Summer of Code 2014 Ideas|2014]] and [[Google Summer of Code 2014 Ideas|2015]].<br />
-----<br />
<br />
<br />
== OSGeo Google Summer of Code 2016 ==<br />
<br />
The [http://www.osgeo.org Open Source Geospatial Foundation] would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.<br />
<br />
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.<br />
<br />
* '''Students: check out the [[Google Summer of Code Recommendations for Students]] page. If you need more information on how to apply you can contact all the mentors via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])<br />
<br />
* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.<br />
<br />
* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.<br />
<br />
* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google_Summer_of_Code_2016_Administrative]] wiki page.<br />
<br />
== The ideas pages ==<br />
'''''[Check back often, it's a work in progress]'''''<br />
<br />
<br />
Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:<br />
<br />
=== OSGeo Foundation member projects ===<br />
<br />
* ''More coming soon: Get started talking to your favorite project's development team today!''<br />
<br />
<br />
[[Image:logo-grass.png|60px|right]]<br />
* [https://trac.osgeo.org/grass/wiki/GSoC/2016 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look!<br />
<br />
<!--<br />
[[Image:logo-qgis.png|60px|right]]<br />
* [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2015 '''QGIS''' SoC Ideas]: [http://www.qgis.org QGIS] is a user friendly Open Source Geographic Information System (GIS) that runs on Linux, Unix, Mac OSX, and Windows. QGIS supports vector, raster, and database formats. It is written in C++ and Python.--><br />
<!--<br />
[[Image:logo-gdal.png|60px|right]]<br />
* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: [http://www.gdal.org GDAL] is a C++ library for reading and writing geospatial data raster and vector formats.--><br />
<!--<br />
* [http://trac.osgeo.org/osgeo4w/wiki/Reports '''OSGeo4W''']: - OSGeo4W is a binary distribution of a broad set of open source geospatial software for Win32 environments (Windows 7, XP, etc).<br />
[[Image:Logo-osgeo4w-mini.png|60px|right]]<br />
:* ''Idea'': We need to extend support to x64 based platforms to handle larger datasets and circumvent memory restrictions. This is a distribution and packaging project which will involve most/all of OSGeo member projects. (''ed. note: keep in mind that to fulfill GSoC requirements each project must have a majority coding component, so lots of scripting, testing, and Makefiles!'')--><br />
<!--<br />
[[Image:logo-gvSIG.png|60px|right]]<br />
* [[GvSIG_GSoC_2016_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.com/en/web/guest/products/gvsig-desktop Desktop]. The gvSIG project looks for students with Java or Python skills that want to develop new ideas on this software. --><br />
<!--<br />
[[Image:logo-opticks.png|right]]<br />
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: [http://opticks.org/ Opticks] is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.--><br />
<!-- <br />
[[Image:Osgeolive_60px.png|right]]<br />
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2015 '''OSGeo-Live''' Ideas]: [http://live.osgeo.org OSGeo-Live] packages over 50 of the best geospatial open source projects, preconfigured with data, quickstarts and project overviews. We have packaging and automated build projects. --><br />
<!-- <br />
[[Image:logo-postgis.png|60px|right]] <br />
* [http://trac.osgeo.org/postgis/wiki/GoogleSummerCode '''PostGIS''' Ideas]: [http://postgis.net PostGIS] spatially enables the popular PostgreSQL object-relational database, allowing it to be used as a back-end database for geographic information systems (GIS) and web-mapping applications.--><br />
<!--<br />
[[Image:logo-ossim.png|90px|right]]<br />
* [https://trac.osgeo.org/ossim/wiki/GSoC_2015 '''OSSIM''' SoC Ideas]: [http://trac.osgeo.org/ossim/wiki OSSIM] Open Source Software Image Map (OSSIM) is a high performance engine for remote sensing, image processing, geographical information systems and photogrammetry. The software has been under active development since 1996 and is deployed across a number of private, federal and civilian agencies. It is written in C++.--><br />
<!--<br />
[[Image:Logo_OTB.png|60px|right]]<br />
* [http://wiki.orfeo-toolbox.org/index.php/Proposals_for_GSoC_2015 '''OTB''' SoC Ideas]: [http://www.orfeo-toolbox.org ORFEO ToolBox] (OTB) is an open source library for remote sensing image processing.Targeted algorithms for high resolution optical images (Pleiades, SPOT, QuickBird, WorldView, Landsat, Ikonos), hyperspectral sensors (Hyperion) or SAR (TerraSarX, ERS, Palsar) are available. The software has been under active development since 2006 and is written in C++ and it includes also side projects also open source with GUI like Monteverdi. OTB has recently started the incubation process into OSGeo.--><br />
<!--<br />
[[Image:Mapserver.png|100px|right]]<br />
* [http://wiki.osgeo.org/wiki/MapServer_2015_SOC_Ideas '''Mapserver''' SoC Ideas]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.--><br />
<!--<br />
[[Image:Logo-istSOS.png|60px|right]]<br />
* [http://sourceforge.net/p/istsos/wiki/GSoC%20ideas%202015/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] (Istituto Scienze della Terra Sensor Observation Service) is an implementation of the Sensor Observation Service (SOS) standard from the Open Geospatial Consortium (OGC). The development of istSOS was started in 2009 in order to provide a simple implementation of the SOS standard for the management, provision and integration of hydro-meteorological data collected in Canton Ticino (Switzerland). istSOS is entirely written in Python.--><br />
<!--<br />
[[Image:logo-geos.png|60px|right]]<br />
* [http://trac.osgeo.org/geos/wiki/GSoC '''GEOS''' Ideas]: GEOS (Geometry Engine - Open Source) is a C++ port of the JTS Topology Suite (JTS). It includes the OpenGIS Simple Features for SQL spatial predicate functions and spatial operators, as well as specific JTS enhanced topology functions.<br />
--> <br />
<!--<br />
[[Image:logo-geoserver-crop.png|50px|right]]<br />
* [https://github.com/geoserver/geoserver/wiki/GSOC-Ideas GSOC Ideas]: [http://live.osgeo.org/en/overview/geoserver_overview.html '''GeoServer'''] is a web server that allows you to serve maps and data from a variety of formats to standard clients such as web browsers and desktop GIS applications. GeoServer works with the Open Geospatial Consortium (OGC) standards Web Feature Service (WFS), Web Coverage Service (WCS), Web Processing Service (WPS) and Web Map Service (WMS) standards.<br />
:* The GeoServer team asks applicants to introduce themselves on the geoserver-devel list ( Communicating in public is a key success factor to open source development )--><br />
<!--<br />
[[Image:Geotools-logo.png|50px|right]]<br />
* [http://docs.codehaus.org/display/GEOTOOLS/Google+Summer+of+Code ''GSOC'']: [http://live.osgeo.org/en/overview/geotools_overview.html '''GeoTools'''] GeoTools is an open source Java library for working with geospatial data, including both data access, data structures, processing and a powerful rendering engine. GeoTools is a modular library used in a wide range of web service, command line tools and desktop applications.--><br />
<!--<br />
[[Image:ZOO-Project-mini.png|right]]<br />
* [http://zoo-project.org/trac/wiki/ZOO_SoC_Idea_2015 '''ZOO-Project''' Soc Ideas]: ZOO-Project is a WPS (Web Processing Service) open source project released under MIT/X-11 style license. It provides an OGC WPS compliant developer-friendly framework to create and chain WPS Web services. --><br />
<!--<br />
[[Image:ZOO-Project-mini.png|right]]<br />
* [http://www.zoo-project.org/trac/wiki/ZOO_SoC_Ideas '''ZOO-Project''' Ideas]: [http://www.zoo-project.org ZOO-Project] is a WPS open source project released under a MIT/X-11 style license. We are seeking a developper to handle migration from SpiderMonky to Google v8 JavaScript runtime environment, upgrade the ZOO-API, build a demo package and develop new services dedicated to raster gesture.<br />
--><br />
<!--<br />
We expect ideas also from [http://live.osgeo.org/en/overview/mapbender_overview.html MapBender], [http://live.osgeo.org/en/overview/geomoose_overview.html GeoMOOSE], [http://mapserver.org/ MapServer], ...<br />
--><br />
<!--<br />
[[Image:Osgeo-live.png|230px|right]]<br />
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2015 '''Osgeo-Live''' SoC Ideas]: [http://live.osgeo.org/en/index.html OSGeo-Live] is a self-contained bootable DVD, USB thumb drive or Virtual Machine based on Lubuntu, that allows you to try a wide variety of open source geospatial software without installing anything. It is composed entirely of free software, allowing it to be freely distributed, duplicated and passed around. It provides pre-configured applications for a range of geospatial use cases, including storage, publishing, viewing, analysis and manipulation of data. It also contains sample datasets and documentation.--><br />
<br />
=== Guest projects ===<br />
<br />
Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact [[User:Madi|Madi]] or Anne.<br />
<br />
[[Image:Pgrouting-logo.png|60px|right]]<br />
* [https://github.com/pgRouting/pgrouting/wiki/GSoC-Ideas '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.<br />
<br />
[[Image:Pywps-logo.png|60px|right]]<br />
* [https://github.com/geopython/pywps/wiki/GSoC-2016-Ideas '''PyWPS''' Ideas]: [http://pywps.wald.intevation.org PyWPS] is server implementation of OGC WPS standard on server side using Python programming language. Currently, [http://github.com/jachym/pywps-4/ new version of PyWPS] is being done, were we would like to implement several new attractive features. <br />
<!--<br />
[[Image:logo-uDig.png|60px|right]]<br />
* [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-Ideas-2015 '''JGrasstools''' and '''uDig''' Spatial Toolbox SoC Ideas]: The JGrasstools project is a geospatial modules library dedicated to hydrology and geomorphology. It is the base of the modules for uDig's Spatial Toolbox.--><br />
<!--<br />
[[Image:otp-logo.png|80px|right]]<br />
* [http://github.com/opentripplanner/OpenTripPlanner/wiki/2015-Google-Summer-of-Code-Ideas '''OpenTripPlanner''' Ideas]: [http://github.com/opentripplanner/OpenTripPlanner OpenTripPlanner] is an open source multi-modal trip planner. It depends on open data in open standard file formats (GTFS and OpenStreetMap), includes a REST API for journey planning, a map-based Javascript client, and an [http://github.com/CUTR-at-USF/OpenTripPlanner-for-Android/wiki Android App].--><br />
<!-- <br />
please contact us first<br />
* [http://lsi.iiit.ac.in/redmine/projects/lsiviewer/wiki/GSoC_2015 '''LSIViewer''' Ideas]: [http://lsi.iiit.ac.in/redmine/projects/lsiviewer/wiki/Main/ LSIViewer] Libre Spatial Information Viewer (LSIViewer) is a web based geospatial data viewer which allows you to view your data, style it, export to SVG/PNG/JPEG formats and can be for used in reports and presentation. It uses Wt, a C++ web toolkit which comes with its own http server and has good support for embedded platforms. The initial version had support for only shapefiles but around 13 vector formats, OSM layer, 3D view has been experimental on the lab's internal repository.<br />
--><br />
<!--<br />
[[Image:Logo-cartaro.png|60px|right]]<br />
* [https://groups.drupal.org/node/407408 '''Cartaro''' Ideas]: [http://cartaro.org Cartaro] provides geospatial functionality and web services within the Drupal Content Management System (CMS). It is builds upon robust Open Source components: the PostGIS database, GeoServer and GeoWebCache web services, OpenLayers maps in the browser, all managed from within the powerful Drupal CMS.--><br />
<!--<br />
[[Image:Geonode logo.png|60px|right]]<br />
* [https://github.com/GeoNode/geonode/wiki/Google-Summer-of-Code-Ideas-2015 '''GeoNode''' Ideas]: [http://geonode.org/ GeoNode] is an Open Source Geospatial Content Management System: a web-based application and platform for developing Geospatial Information Systems (GIS) and for deploying spatial data infrastructures (SDI). It is designed to be easily extended and modified, and can be integrated into existing platforms. Written with the Python Django web application, it is based on other great Open Source components such as PostGIS, GeoServer, OpenLayers and GeoExplorer.--><br />
<!--<br />
[[Image:neo4j-spatial_64.png|right]]<br />
* [https://github.com/neo4j/GSoC/wiki '''Neo4j Spatial''' Ideas]: [https://github.com/neo4j/spatial Neo4j Spatial] is an Open Source library extending the popular [http://neo4j.org Neo4j Graph Database] with a number of features for GIS enabling your data model. It embeds and relies on JTS and GeoTools, and provides the ability to store your domain model in many internal formats, and has utilities for import and export of Shapefiles and OpenStreetMap data. We've received contributions from GSoC projects in 2010, 2011 and 2012.--><br />
<!--<br />
[[Image:Logo-cartoDB.png|70px|right]]<br />
* [https://github.com/CartoDB/cartodb/wiki/GoogleSummerCode '''CartoDB Ideas''']: [http://cartodb.com/develop CartoDB] is a cloud based mapping, analysis and visualization engine that lets users build spatial applications for both mobile and the web. Students will need to be able to use PHP and PostgreSQL.--><br />
<!--<br />
* '''FIXME''': move to a member project's idea page:<br />
: ''[http://sites.google.com/site/foss4gku/projects/gsoc-feature-based-map-algebra '''Feature-based Map Algebra''' SoC Ideas] Map algebra (or cartographic modeling) operations provide powerful tools for analyzing and manipulating geographic data in the raster data model both in commercial and open source GIS software. This project extends these operations to the vector data model and makes them available in PostGIS and QGIS. It will be implemented primarily using the Python programming language.''<br />
--><br />
<!--<br />
[[Image:Logo-mapnik.png|100px|right]]<br />
* [https://github.com/mapnik/mapnik/wiki/GSOC-Ideas '''Mapnik''' Ideas]: [http://mapnik.org/ Mapnik] is a Free Toolkit for developing mapping applications. It\u2019s written in C++ and there are Python bindings to facilitate fast-paced agile development. It can comfortably be used for both desktop and web development, which was something I wanted from the beginning.<br />
--><br />
<br />
=== See also ===<br />
<br />
Other like minded projects do not participate to GSoC under OSGeo umbrella, but with their own organization. You may want to visit also their page:<br />
<br />
<!--<br />
* [https://wiki.52north.org/bin/view/Projects/GSoC2015ProjectIdeas '''52°North''' Ideas]--><br />
<br />
<!-- [[Image:Logo-osm6.png|60px|right]] <br />
* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2015/Project_Ideas '''OpenStreetMap''' Ideas]--><br />
<br />
<!--<br />
[http://osm.org/ OSM] is a project aimed squarely at creating and providing free geographic data such as street maps to anyone who wants them. The project was started because most maps you think of as free actually have legal or technical restrictions on their use, holding back people from using them in creative, productive or unexpected ways.<br />
--><br />
<br />
=== Don't see in the list the project you're interested in? ===<br />
<br />
Contact them in their developers mailing list! Feel free to propose your own idea and get feedback!<br />
<br />
== I want to apply as a student ==<br />
<br />
Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.<br />
<br />
<br />
=== Which project do I choose? ===<br />
<br />
Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.<br />
: View the documents and download the ISO from http://live.osgeo.org<br />
[[File:Osgeolive wordle.png|400px|center]]<br />
<br />
<br />
=== Important dates ===<br />
<br />
* [https://developers.google.com/open-source/gsoc/timeline '''The official timeline''']<br />
<br />
<!-- {{done}} --><br />
* Feb 29: Google announces accepted organizations.<br />
: Please start talking to the dev communities you are interested in ''now''.<br />
* March 14: Student applications open.<br />
: The earlier you start the more probable it is that you will be accepted!<br />
: ''There is two way feedback during the application process which really helps you improve and clarify your application before the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''<br />
* March 25: Student application deadline.<br />
* April 22: '''Accepted student proposals are announced and Community Bonding Period begins.'''<br />
* May 23: '''Coding begins!'''<br />
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')<br />
* June 20 - 27: Mid-term evaluation <br />
* August 15-23: '''Pencils down!'''<br />
* August 23 -29: Final evaluations<br />
* August 30: Final results announced<br />
<br />
[Back to [[Google Summer of Code 2016]] @ OSGeo]<br />
[[Category: Google Summer of Code]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=User:Danielkastl&diff=89177User:Danielkastl2015-12-02T03:41:07Z<p>Dkastl: </p>
<hr />
<div>===Daniel Kastl===<br />
<br />
Owner, [http://georepublic.info Georepublic] Germany & Japan<br />
<br />
Location(s): Nishinomiya, Japan or Munich, Germany<br />
<br />
Daniel is a geographer, software developer, founder of Georepublic and Free Software advocate. <br />
<br />
{{OSGeo Experience<br />
|User=Yes<br />
|Committee=No<br />
|Board=No<br />
|Coder=Yes<br />
|Translate=Yes<br />
|PSC=No<br />
|ExBoard=No<br />
|Charter=Yes<br />
|Chair=No<br />
|SolKatz=No<br />
|Committer=No<br />
}}<br />
<br />
:* pgRouting Project Steering Committee member<br />
:* Mentor for Google Summer of Code<br />
:* OSGeo Charter Member<br />
<br />
;Contact:<br />
: Email: daniel (A T) georepublic.co.jp<br />
: Phone: +49 (089) 4161 7698-1<br />
: [http://www.linkedin.com/in/dkastl LinkedIn] and [https://twitter.com/dkastl Twitter]<br />
<br />
{{OSGeo Member<br />
|Name=Daniel Kastl<br />
|JobTitle=<br />
|Company=Georepublic<br />
|Address=<br />
|City=Nishinomiya<br />
|State=Hyogo<br />
|Country=Japan<br />
|Coordinate=34.74712, 135.35737<br />
|LocalChapter=Japan<br />
|Email=<br />
|Phone=<br />
|SocialMedia=<br />
|Website=https://georepublic.info<br />
|Photo=<br />
|Languages=German; English; Japanese;<br />
|Info=<br />
}}<br />
<br />
[[Category:OSGeo Member]]<br />
[[Category:OSGeo Charter Member]]<br />
[[Category:Germany]]<br />
[[Category:Japan]]<br />
[[Category:OSGeo Advocate]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=User:Danielkastl&diff=89176User:Danielkastl2015-12-02T03:39:03Z<p>Dkastl: Trying to get rid of empty rows in the maps extension</p>
<hr />
<div>===Daniel Kastl===<br />
<br />
Owner, [http://georepublic.info Georepublic] Germany & Japan<br />
<br />
Location(s): Nishinomiya, Japan or Munich, Germany<br />
<br />
Daniel is a geographer, software developer, founder of Georepublic and Free Software advocate. <br />
<br />
{{OSGeo Experience<br />
|User=Yes<br />
|Committee=No<br />
|Board=No<br />
|Coder=Yes<br />
|Translate=Yes<br />
|PSC=No<br />
|ExBoard=No<br />
|Charter=Yes<br />
|Chair=No<br />
|SolKatz=No<br />
|Committer=No<br />
}}<br />
<br />
:* pgRouting Project Steering Committee member<br />
:* Mentor for Google Summer of Code<br />
:* OSGeo Charter Member<br />
<br />
;Contact:<br />
: Email: daniel (A T) georepublic.co.jp<br />
: Phone: +49 (089) 4161 7698-1<br />
: [http://www.linkedin.com/in/dkastl LinkedIn] and [https://twitter.com/dkastl Twitter]<br />
<br />
;Spoken Language(s): German, English, Japanese<br />
<br />
{{OSGeo Member<br />
|Name=Daniel Kastl<br />
|JobTitle=<br />
|Company=Georepublic<br />
|Address=<br />
|City=Nishinomiya<br />
|Country=Japan<br />
|Coordinate=34.74712, 135.35737<br />
|LocalChapter=Japan<br />
|Email=<br />
|Phone=<br />
|SocialMedia=<br />
|Website=https://georepublic.info<br />
|Photo=<br />
|Languages=<br />
|Info=<br />
}}<br />
<br />
[[Category:OSGeo Member]]<br />
[[Category:OSGeo Charter Member]]<br />
[[Category:Germany]]<br />
[[Category:Japan]]<br />
[[Category:OSGeo Advocate]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=User:Danielkastl&diff=88775User:Danielkastl2015-11-22T15:57:15Z<p>Dkastl: </p>
<hr />
<div>===Daniel Kastl===<br />
<br />
[[File:OSGeo_compass300.png|thumb|right|100px|Daniel Kastl]]<br />
<br />
Owner, [http://georepublic.info Georepublic] Germany & Japan<br />
<br />
Location(s): Nishinomiya, Japan or Munich, Germany<br />
<br />
Daniel is a geographer, software developer, founder of Georepublic and Free Software advocate. <br />
<br />
;OSGeo Experience [[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]][[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]][[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]][[File:OSGeo_translate.png|link=OSGeo_Advocate#OSGeo_Community_Members]]<br />
<br />
:* pgRouting Project Steering Committee member<br />
:* Mentor for Google Summer of Code<br />
:* OSGeo Charter Member<br />
<br />
;Contact:<br />
: Email: daniel (A T) georepublic.co.jp<br />
: Phone: +49 (089) 4161 7698-1<br />
: [http://www.linkedin.com/in/dkastl LinkedIn] and [https://twitter.com/dkastl Twitter]<br />
<br />
;Spoken Language(s): German, English, Japanese<br />
<br />
{{OSGeo Member<br />
|Name=Daniel Kastl<br />
|Address=Nishinomiya, Japan<br />
|Coordinate=34.74712, 135.35737<br />
}}<br />
<br />
;Profile last updated: 23 November 2015<br />
<br />
[[Category:OSGeo Member]]<br />
[[Category:OSGeo Charter Member]]<br />
[[Category:Germany]]<br />
[[Category:Japan]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=User:Danielkastl&diff=88774User:Danielkastl2015-11-22T15:56:12Z<p>Dkastl: Added map</p>
<hr />
<div>===Daniel Kastl===<br />
<br />
[[File:OSGeo_compass300.png|thumb|right|100px|Daniel Kastl]]<br />
<br />
Owner, [http://georepublic.info Georepublic] Germany & Japan<br />
<br />
Location(s): Nishinomiya, Japan or Munich, Germany<br />
<br />
{{OSGeo Member<br />
|Name=Daniel Kastl<br />
|Address=Nishinomiya, Japan<br />
|Coordinate=34.74712, 135.35737<br />
}}<br />
<br />
Daniel is a geographer, software developer, founder of Georepublic and Free Software advocate. <br />
<br />
;OSGeo Experience [[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]][[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]][[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]][[File:OSGeo_translate.png|link=OSGeo_Advocate#OSGeo_Community_Members]]<br />
<br />
:* pgRouting Project Steering Committee member<br />
:* Mentor for Google Summer of Code<br />
:* OSGeo Charter Member<br />
<br />
;Contact:<br />
: Email: daniel (A T) georepublic.co.jp<br />
: Phone: +49 (089) 4161 7698-1<br />
: [http://www.linkedin.com/in/dkastl LinkedIn] and [https://twitter.com/dkastl Twitter]<br />
<br />
;Spoken Language(s): German, English, Japanese<br />
<br />
;Profile last updated: 23 November 2015<br />
<br />
[[Category:OSGeo Member]]<br />
[[Category:OSGeo Charter Member]]<br />
[[Category:Germany]]<br />
[[Category:Japan]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=User:Danielkastl&diff=88773User:Danielkastl2015-11-22T15:52:03Z<p>Dkastl: /* Daniel Kastl */</p>
<hr />
<div>===Daniel Kastl===<br />
<br />
[[File:OSGeo_compass300.png|thumb|right|100px|Daniel Kastl]]<br />
<br />
Owner, [http://georepublic.info Georepublic] Germany & Japan<br />
<br />
Location(s): Nishinomiya, Japan or Munich, Germany<br />
<br />
Daniel is a geographer, software developer, founder of Georepublic and Free Software advocate. <br />
<br />
;OSGeo Experience [[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]][[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]][[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]][[File:OSGeo_translate.png|link=OSGeo_Advocate#OSGeo_Community_Members]]<br />
<br />
:* pgRouting Project Steering Committee member<br />
:* Mentor for Google Summer of Code<br />
:* OSGeo Charter Member<br />
<br />
;Contact:<br />
: Email: daniel (A T) georepublic.co.jp<br />
: Phone: +49 (089) 4161 7698-1<br />
: [http://www.linkedin.com/in/dkastl LinkedIn] and [https://twitter.com/dkastl Twitter]<br />
<br />
;Spoken Language(s): German, English, Japanese<br />
<br />
;Profile last updated: 23 November 2015<br />
<br />
[[Category:OSGeo Member]]<br />
[[Category:OSGeo Charter Member]]<br />
[[Category:Germany]]<br />
[[Category:Japan]]<br />
{{#umSetParam: 135.373535|34.583475|Osaka, Japan|Danielkastl|Daniel Kastl}}</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=User:Danielkastl&diff=88772User:Danielkastl2015-11-22T15:50:03Z<p>Dkastl: Undo revision 88427 by Cwillmes (talk)</p>
<hr />
<div>===Daniel Kastl===<br />
<br />
[[File:OSGeo_compass300.png|thumb|right|100px|Daniel Kastl]]<br />
<br />
Owner, [http://georepublic.info Georepublic] Germany & Japan<br />
<br />
Location(s): Osaka, Japan or Munich, Germany<br />
<!--(-33.744 S, 18.989 E){{#umSetParam: 18.989|-33.744|Paarl|Gfleming|Gavin Fleming}}<br />
{{#umAdmin: Gfleming}} {{#umUserMap: Gfleming}}--><br />
<br />
Daniel is a geographer, software developer, founder of Georepublic and Free Software advocate. <br />
<br />
;OSGeo Experience [[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]][[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]][[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]][[File:OSGeo_translate.png|link=OSGeo_Advocate#OSGeo_Community_Members]]<br />
<br />
:* pgRouting Project Steering Committee member<br />
:* Mentor for Google Summer of Code<br />
:* OSGeo Charter Member<br />
<br />
;Contact:<br />
: Email: daniel (A T) georepublic.co.jp<br />
: Phone: +49 (089) 4161 7698-1<br />
: [http://www.linkedin.com/in/dkastl LinkedIn] and [https://twitter.com/dkastl Twitter]<br />
<br />
;Spoken Language(s): German, English, Japanese<br />
<br />
;Profile last updated: 15 March 2014<br />
<br />
[[Category:OSGeo Member]]<br />
[[Category:OSGeo Charter Member]]<br />
[[Category:Germany]]<br />
[[Category:Japan]]<br />
{{#umSetParam: 135.373535|34.583475|Osaka, Japan|Danielkastl|Daniel Kastl}}</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=UnitedNations_Committee&diff=87686UnitedNations Committee2015-11-02T21:55:19Z<p>Dkastl: /* Members */</p>
<hr />
<div>== Background ==<br />
The OSGeo Board of Directors met with the UN GIS team at FOSS4G in Seoul, Korea in September 2015. The UN GIS team is very interested in having OSGeo "at the table", and is interested in an exchange of official letters (an MoU would take many years to pass through on their side apparently) to formalize the relationship. Mr. Kyoung-Soo Eom, chief of the UN Geospatial Information Section, has invited OSGeo to be part of a working group on Geospatial Information and Services for Disasters.<br />
<br />
== Goals ==<br />
<br />
* Develop a closer relationship with the UN.<br />
<br />
* Establish a formal agreement between OSGeo and the UN.<br />
<br />
* Establish communication between the UN GIS team and the OSGeo community.<br />
<br />
* Promote the use of Open Source geospatial tools by the UN's member states and committees.<br />
<br />
== Communication ==<br />
<br />
* a new "UN" mailing list has been created, please subscribe at https://lists.osgeo.org/mailman/listinfo/un<br />
<br />
== Activities ==<br />
* OSGeo has formally expressed interest in joining the [[UN-GGIM-Working-Group]] on Geospatial Information and Services for Disasters <br />
** this was discussed at OSGeo's [[Board_Meeting_2015-10-15]]<br />
** the UN is looking for feedback on the working group's [http://wiki.osgeo.org/wiki/UN-GGIM-Working-Group#Draft_terms_of_reference_.28TOR.29 TOR draft]<br />
<br />
== Next steps ==<br />
* put out call for members for this new committee to Discuss list<br />
* organize a monthly meeting, possibly using IRC or Slack<br />
* draft official letter for formalizing relationship with UN<br />
<br />
== Meetings ==<br />
<br />
*<br />
<br />
== Members ==<br />
<br />
* [[Jeff McKenna]]<br />
* [[Jochen Albrecht]] <br />
* [[Bob Basques]]<br />
* [[Massimiliano_Cannata]]<br />
* [[User:Ticheler|Jeroen Ticheler]]<br />
* [[Micha Silver]]<br />
* [[User:GodwinYeboah|Godwin Yeboah]]<br />
* [[User:Assefa|Yewondwossen Assefa]]<br />
* [[User:Nikos|Nikos Alexandris]]<br />
* [[User:AndrewTurner|Andrew Turner]]<br />
* [[Venkatesh Raghavan]]<br />
* [[User:Djay|Gérald Fenoy]]<br />
* [[User:Pmooney|Peter MOONEY]]<br />
* [[User:13scoter|Scott Hatcher]]<br />
* [[User:kotzino|Dimitris Kotzinos]]<br />
* [[User:ElaWoloszynska|Ela Wołoszyńska-Wiśniewska]]<br />
* [[User:Jachym|Jachym Cepicky]]<br />
* [[User:endofcap|Sanghee Shin]]<br />
* [[User:Giulianoramat|Giuliano Ramat]]<br />
* [[User:Gregory.giuliani|Gregory Giuliani]]<br />
* [[User:Till Adams|Till Adams]]<br />
* [[User:Maria gridw|Maria Andrzejewska]]<br />
* [[User:rburhum|Ragi Y. Burhum (OSGeo - California / OSGeo Perú)]]<br />
* [[User:Danielkastl|Daniel Kastl]]<br />
* ''add your name''<br />
<br />
[[Category:UnitedNations]]<br />
[[Category:Committees]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=LIDAR_Format_Letter&diff=83764LIDAR Format Letter2015-04-22T09:10:44Z<p>Dkastl: /* Signed */</p>
<hr />
<div>=Open Letter of the Need for Open Standards in LiDAR=<br />
April 2015.<br />
<br />
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.<br />
<br />
<br />
We request that:<br />
# 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.<br />
# 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 joins with 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.<br />
# 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.<br />
# 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.<br />
<br />
=Signed=<br />
Name, Affiliation(s), Optional comment on interest in Open LiDAR format<br />
<br />
# Suchith Anand, Geo for All, committed to Open Principles in Geo Education and Policy.<br />
# 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].<br />
# 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.<br />
# Stefan Keller, founder and director of [http://www.hsr.ch/geometalab Geometa Lab]; Professor in GIS, databases, open (government) data and interoperability; maintainer of GeoConverter; contributor to open source software (GDAL/OGR, QGIS).<br />
# 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.<br />
# 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.<br />
# [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 and to Open Principles in Research.<br />
# 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.<br />
# [http://www.geodatawiz.com/armin-schmidt 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.<br />
# [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.<br />
# [http://pt.linkedin.com/pub/jorge-rocha/1b/560/499 Jorge Gustavo Rocha], Professor, Computer Science Department, University of Minho, Portugal, committed to better science through [http://www.gistam.org/EventChairs.aspx?y=2016 Open Data].<br />
# [http://people.eecs.ku.edu/~miller/ Jim Miller], University of Kansas, Professor, Computer Science. Open standards for data exchange are essential for education and research.<br />
# [http://www.linkedin.com/pub/brandt-melick/22/869/261 Brandt Melick], Information Technology Department Director, Springfield Oregon USA. The need to promote open solutions is paramount.<br />
# Alex Paza Makini, National University Solomon Islands, Natural Resources and Applied Science. Committed to open data standards for education and research, and everything beyond.<br />
# Jorg M. Hacker, Professor, 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.<br />
# 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.<br />
# [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.<br />
# [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.<br />
# [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.<br />
# [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.<br />
# [[User:Ivansanchez|Iván Sánchez Ortega]], [http://www.mazemap.no Mazemap]. OSGeo Charter member and Open Data nerd.<br />
# [[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.<br />
# [[User:vehrka|Pedro-Juan Ferrer]], [http://www.geomaticblog.net Geomaticblog]. OSGeo Charter member and member of the Open Knowledge Foundation.<br />
# [http://www.linkedin.com/pub/karl-donert/3/160/571 Professor Karl Donert], President European Association of Geographers (http://www.eurogeo.nl/ EUROGEO)<br />
# Drew Fenton, Boulder Creek, CA [http://www.savetheredwoods.org/redwoods/coast-redwoods/ Countdown to the Last Coast Redwood]. Please protect Open Standards for geospatial data!<br />
# [[User:Bolosig|Wladimir Szczerban]], [http://www.geoinquiets.cat Geoinquiets] Geogeek & OSGeo Spanish Local Chapter Member, Spain<br />
# [http://vmx.cx Volker Mische], OSGeo Charter member and creator of GeoCouch<br />
# [http://www.linkedin.com/in/clquintanilla Carlos López Quintanilla], [http://www.psig.es PSIG] [http://www.geoinquiets.cat Geoinquiets] GIS consultant, Spain<br />
# [[User:woodbri|Stephen Woodbridge]], [http://imaptools.com iMaptools], OSGeo Charter member.<br />
# [[User:odoepner|Oliver Doepner]], [http://oliver.doepner.net doepner.net], Software Engineer (Java,Linux), Open Standards and Open Source advocate<br />
# [[User:Lucadelu|Luca Delucchi]], [http://gis.cri.fmach.it Fondazione Edmund Mach], OSGeo Charter member, FOSS4G and Open Data developer, advocate, contributor and user.<br />
# Antoine Cottin, CTO of [http://www.carbomap.com Carbomap Ltd.] and creator of [http://github.com/carbomap/Fleurdelas Fleurdelas], Edinburgh, United Kingdom.<br />
# [http://strk.keybit.net Sandro Santilli], [http://strk.keybit.net/services.html NetLab], Free Software Hacker. There are already too many users slave to their tools, let's stop that!<br />
# [http://www.itopen.it Alessandro Pasotti], [http://www.itopen.it ItOpen], GIS Free Software Developer.<br />
# [http://www.roccatello.com Eduard Roccatello], [http://www.3dgis.it 3DGIS], 3DGIS CTO and co-Founder<br />
# [[User:moovida|Andrea Antonello]], [http://www.hydrologis.com HydroloGIS], OSGeo Charter member, Open Source GIS developer, HydroloGIS co-founder.<br />
# [http://www.associazionegfoss.it Stefano Campus], President of [http://www.associazionegfoss.it GFOSS.it] Association (Associazione Italiana per l'Informazione Geografica Libera), Italian Local Chapter of OSGeo Foundation.<br />
# [http://wiki.osgeo.org/wiki/User:Madi Margherita Di Leo], OSGeo Charter Member<br />
# [http://wiki.osgeo.org/wiki/User:Sacosta Sergio Acosta y Lara], OSGeo Charter Member<br />
# [http://wiki.osgeo.org/wiki/User:Maximdubinin Maxim Dubinin], CEO at NextGIS, OSGeo Charter Member. Another 'standard' proprietary format? No, thank you.<br />
# [[User:Steko|Stefano Costa]], Soprintendenza Archeologia della Liguria, Ministero dei Beni e delle Attività Culturali e del Turismo, Italy<br />
# [http://www.geog.illinois.edu/people/jgrn Jonathan Greenberg], Assistant Professor, [http://publish.illinois.edu/jgrn/ GEARS Laboratory], Department of Geography and Geographic Information Science, University of Illinois at Urbana-Champaign.<br />
# Bob Basques, Saint Paul, Mn., Technical Director for SharedGeo.<br />
# [http://wiki.osgeo.org/wiki/User:Maning Maning Sambale], OSGeo Charter Member<br />
# [http://wiki.osgeo.org/wiki/User:Pcav Paolo Cavallini], QGIS PSC<br />
# [http://wiki.osgeo.org/wiki/User:Dr Phillip Davis], Member OSGeo Geo For All education advisory board, Director @ GeoAcademy<br />
# [http://wiki.osgeo.org/wiki/User:Nbozon Nicolas Bozon], Researcher and software developer, OSGeo Charter Member<br />
# [http://www.linkedin.com/in/ruslanrainis Ruslan Rainis], Professor, Director, [http://www.research.usm.my/default.asp?tag=36 Centre for Research Initiatives in Liberal Arts & Social Sciences](CRI-LASS). Open GeoInformation for a Sustainable Tomorrow and the Bottom Billions.<br />
# [[User:Silli|Silvia Franceschi]], [http://www.hydrologis.com HydroloGIS], OSGeo Charter member, Environmental Engineer Open Source GIS power user, HydroloGIS co-founder.<br />
# Oscar Martinez Rubi [http://esciencecenter.nl Netherlands eScience Center] eScience engineer.<br />
# Werner Macho, QGIS team member. Committed to open data standards for education and research.<br />
# Giuseppe Patti, Geologist and Freelance Geospatial Advisor, GFOSS supporter.<br />
# [http://wiki.osgeo.org/wiki/User:Drappo Daniel Rappo], Professor, University of Applied Sciences and Arts Western Switzerland, School of Business and Engineering Vaud.<br />
# [[User:nachouve|Juan Ignacio Varela]], Freelance Geospatial Advisor and OSGeo Local Chapter Member.<br />
# [[User:dmorissette|Daniel Morissette]], President at [http://mapgears.com Mapgears], OSGeo Charter member.<br />
# [http://www.linkedin.com/in/raulnanclares Raul Nanclares], RS&GIS Specialist<br />
# [http://www.ing.unitn.it/dica/hp/index_eng.php?user=rigon Riccardo Rigon], Professor at University of Trento (Italy)<br />
# [[User:Siki| Zoltan Siki]] Budapest University of Technology and Economics (Hungary), OSGeo Charter member.<br />
# [http://lefsky.org Michael Lefsky], Professor of Remote Sensing Science, Colorado State University and Director, Center for Ecological Applications of Lidar.<br />
# [http://www.linkedin.com/pub/lucas-c-villa-real/7/a0b/b06 Lucas Villa Real], Research software engineer at IBM Research - Brazil.<br />
# [http://terraremote.com Loren Dawe], GIS Manager at Terra Remote Sensing Inc. Lidar Supplier and Open Standards Advocate<br />
# [http://wiki.osgeo.org/wiki/User:Warmerda Frank Warmerdam], Software Developer, OSGeo Charter member<br />
# [http://ch.linkedin.com/pub/jens-ingensand/0/836/6b0 Jens Ingensand], Professor, University of Applied Sciences and Arts Western Switzerland, [http://www.heig-vd.ch/international School of Business and Engineering Vaud].<br />
# [http://nsidc.org/research/bios/khalsa.html Siri Jodha Khalsa], Research Scientist, National Snow and Ice Data Center, [http://cires.colorado.edu/ Cooperative Institute for Research in Environmental Sciences], University of Colorado, Boulder, USA<br />
# [http://gis.uster.ch/ Andreas Neumann], GIS manager, City of Uster, Kanton Zurich, Switzerland<br />
# [http://www.iwmi.org/ Yann Chemin], Researcher - Remote Sensing, International Water Management Institute, Colombo, Sri Lanka<br />
# [http://www.linkedin.com/in/etiennebracine Etienne B. Racine], Geomatics and remote sensing project manager, WSP, Canada<br />
# [http://www.linkedin.com/pub/alejandro-hinojosa/7/33b/342 Alejandro Hinojosa], [http://cicese.mx CICESE Research Center], Earth Sciences Division, GIS & Remote Sensing Lab, Ensenada, Mexico<br />
# [http://wiki.osgeo.org/wiki/User:epifanio Massimo Di Stefano], OSGeo Charter Member<br />
# [http://clas.ucdenver.edu/directory/faculty-staff/Rafael-Moreno Rafael Moreno], University of Colorado Denver, [http://www.ucdenver.edu/academics/colleges/CLAS/Departments/ges/Pages/Geography.aspx Department of Geography and Environmental Sciences]. Openness is fundamental to progress.<br />
# Peter Drexel, GIS manager, [http://www.vorarlberg.at/vorarlberg/bauen_wohnen/bauen/vermessung_geoinformation/start.htm State of Vorarlberg (State Survey Office)], Austria<br />
# [http://www.linkedin.com/pub/marco-minghini/a8/3b6/198 Marco Minghini], Department of Civil and Environmental Engineering, [http://www.polimi.it Politecnico di Milano]. Committed to Open Principles in Geo Education and Research.<br />
# [http://www.linkedin.com/pub/candan-eyl%C3%BCl-kilsedar/65/380/976 Candan Eylül Kilsedar], WebGIS Developer, Research Fellow at [http://www.polimi.it Politecnico di Milano]. <br />
# [http://wiki.osgeo.org/wiki/User:AlastairMcKinstry Alastair McKinstry], Debian Linux meteorology/GIS developer, Ireland<br />
# [http://people.unibo.it/it/elena.mezzini2 Elena Mezzini], Remote-sensing in forest ecology, Research Fellow, Department of Agricultural Sciences, University of Bologna, Italy.<br />
# [http://www.linkedin.com/profile/view?id=43566064 Mihai A. Tanase], Honorary fellow, Dept. of Forest and Ecosystem Science, The University of Melbourne, Australia<br />
# [http://www.linkedin.com/pub/dave-murray/10/742/3a2 Dave Murray], GIS Coordinator at [http://www.ci.westminster.co.us/ City of Westminster]<br />
# Ayesa Martínez Serrano, Estudiante de Doctorado en [http://www.ciga.unam.mx/ Geografía del Centro de Investigaciones en Geografía Ambiental de la UNAM-México]<br />
# [http://www.linkedin.com/pub/christopher-crosby/15/b7/114 Christopher Crosby], co-founder, [http://www.opentopography.org/ OpenTopography]<br />
# [http://sg.linkedin.com/in/sgganesh Shanmugam Ganeshkumar], Vice President - Consulting, [http://www.geoicon.com GeoICON]<br />
# [[User:Chaitanya|Chaitanya Kumar CH]], GIS Developer with [http://www.egis-geoplan.com/ Egis Geoplan - India] and OSGeo Charter member.<br />
# KS Rajan, Associate Professor and Head, [http://lsi.iiit.ac.in/ Lab for Spatial Informatics, IIIT Hyderabad] and Chairman, [http://www.kaiinos.com/ KAIINOS Geospatial Technologies]; Promoter and Supported of Open Source, Open Data, Open Standards and e-Governance in India<br />
# Pericles Nacionales, RS/GIS Specialist and OSGeo Charter member.<br />
# Vasile Crăciunescu, Researcher at Romanian National Meteorological Administration and OSGeo Board member.<br />
# [http://geo.tuwien.ac.at/staff/andreas-roncat/ Andreas Roncat] PostDoc Researcher, Research Groups Photogrammetry and Remote Sensing, [http://www.geo.tuwien.ac.at/ Department of Geodesy and Geoinformation], Vienna University of Technology, Austria. In full agreement with [http://wiki.osgeo.org/wiki/User:Maximdubinin Maxim Dubinin]: Another 'standard' proprietary format? No, thank you.<br />
# [http://wiki.osgeo.org/wiki/User:remanuele Rob Emanuele], Software Developer, Azavea Inc.<br />
# Codrina Ilie, Researcher at the Groundwater Engineering Research Center, Technical University of Civil Engineering Bucharest and OSGeo Charter Member<br />
# [http://wiki.osgeo.org/wiki/User:Djay Gérald Fenoy], Software Developer, OSGeo Charter Member.<br />
# [http://www.aston.ac.uk/eas/staff/a-z/dr-lucy-bastin/ Lucy Bastin], Software Developer at the Joint Research Centre of the European Commission / Computer Science lecturer, UncertML developer, Member of OGC SWG on User Feedback.<br />
# Matt Wilkie, Geomatics Analyst at [http://www.gov.yk.ca/ Yukon Government], [http://www.env.gov.yk.ca/geomatics Department of Environment]. A practising GIS Professional for 20+ years. Throughout that time, the process of manipulating data into, through and out of proprietary formats has been the most aggravating source of inefficiency and wasted time. Things are hard enough without adding unnecessary barriers.<br />
# [[User:Annakrat|Anna Petrasova]], OSGeo Charter Member, GRASS GIS developer<br />
# [http://www.linkedin.com/pub/mark-seibel-gisp/45/517/942 Mark Seibel], Geospatial Hacker. Long live open Geo data & software.<br />
# [http://www.wrsc.org/people/ben-discoe Ben Discoe], [http://vterrain.org/ Virtual Terrain Project] and [http://www.leica-geosystems.us/en/HDS-Laser-Scanners-SW_5570.htm Leica Geosystems HDS], I wrangle point clouds every day. Semi-open E57 is bad enough. No more closed formats!<br />
# [http://www.linkedin.com/pub/ilda-clos/19/21b/391 Ilda Clos], GIS & IWRM specialist<br />
# [[User:Danielkastl|Daniel Kastl]], Founder [http://georepublic.info Georepublic] and OSGeo Charter Member<br />
<br />
=Background=<br />
==About LiDAR==<br />
<br />
[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.<br />
<br />
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.<br />
<br />
<br />
==LAS Limitations==<br />
<br />
Quoting [http://boundlessgeo.com/2014/01/lidar-format-wars/ Paul Ramsey]:<br />
<br />
: LAS format is not without its drawbacks:<br />
<br />
:* 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.<br />
:* 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.<br />
: Clearly there is a little more work to be done. Can LAS be improved? In fact, it already has been:<br />
:* An open source compression library, LASzip can apply 20''':'''1 lossless compression to LAS files, making them great for archival purposes.<br />
:* 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.<br />
: 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.<br />
<br />
<br />
=="Optimized LAS" A ''' ''Proprietary'' ESRI Format'''==<br />
ESRI announced, 12 January 2014, 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]].<br />
<br />
The implementation of the "Optimized LAS" format is not available as Open Source and the format and algorithm details itself are undocumented, which means nobody can currently create alternate implementations, neither closed nor Open Source. This causes both technical as well as legal barriers for other applications reading and/or writing to this proprietary format. It 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.<br />
<br />
One year after releasing the "Optimized LAS" format, ESRI released a Windows only library (DLL) as a free-of-charge (gratis) download that is claimed to convert between LAS and "Optimized LAS". Note there is a distinct difference between a "free-of-charge" binary distribution of DLLs and publishing something as "Open Source". Unless the source code of the library is released as Open Source under an Open Source 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.<br />
<br />
Ironically, ESRI later placed their '''binary''' library files [http://github.com/Esri/esri-zlas-io-library on github] accompanied by an Apache License, but no source code was published. The distribution of binaries without source code is allowed by Apache License, but very uncommon and misleading, to say the least. The practice goes against the basic idea of “Open Source” and the Open Source Initiative (OSI) even has an FAQ entry on the obvious contradiction of [http://opensource.org/faq#non-distribution “Open Source” without source code].<br />
<br />
==OGC's Efforts For An ''' ''Open'' LiDAR Standard'''==<br />
<br />
The [http://www.opengeospatial.org/ Open Geospatial Consortium (OGC)] has indicated their interest in developing a standard LiDAR format.<br />
<br />
Carl Reed (formerly on OGC staff) provided the following information on OGC's previous efforts to work toward enabling Open Standards in LiDAR:<br />
<br />
: "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."<br />
<br />
[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.<br />
: 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.<br />
<br />
<br />
==History: LAS and ESRI's "Optimized LAS"==<br />
<br />
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":<br />
<br />
: '''Summary:'''<br />
<br />
:* The LAS format has been used successfully for over a decade.<br />
:* Within last couple of years, ESRI has added native LAS support into ESRI products.<br />
:* ESRI discussed embracing the open [http://laszip.org LAZ] format and simultaneously developed a proprietary "Optimized LAS" format.<br />
:* The open geospatial community offered, on numerous occasions, to work with ESRI to avoid format fragmentation.<br />
:* ESRI's proprietary "Optimized LAS" format is very similar in design and performance to the open [http://laszip.org LASzip] format.<br />
<br />
: '''1998: Original LAS format definition'''<br />
<br />
: 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.<br />
<br />
: '''2011: ESRI joins LAS Working Group'''<br />
<br />
: 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.<br />
<br />
: 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."<br />
<br />
: '''June 2012: ArcGIS 10.1 includes [proprietary] LAS Dataset file'''<br />
<br />
: 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.<br />
<br />
: '''2012/2013: Collaboration Discussions'''<br />
<br />
: 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."<br />
<br />
: 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."<br />
<br />
: '''June 2013: ESRI asked to sponsor clean LASzip DLL'''<br />
<br />
: 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."<br />
<br />
: 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."<br />
<br />
: '''July 2013: ArcGIS 10.2 includes [proprietary] LAS indexing '''<br />
<br />
: With the release of ArcGIS 10.2 in July 2013, ESRI introduced spatial indexing to speed up area-of-interest queries. Their new proprietary *.lasx files were seemingly identical in functionality to the open *.lax files that had been [http://groups.google.com/d/topic/lastools/j0qA8NBMHJs/discussion announced] two years earlier - in May 2011 - and were [http://rapidlasso.com/2012/12/03/lasindex-spatial-indexing-of-lidar-data/ presented] at ELMF in November 2012.<br />
<br />
: '''July 2013: Open LASzip API released'''<br />
<br />
: 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.<br />
<br />
: '''December 2013 : ESRI discovered to be secretly developing proprietary LAS format'''<br />
<br />
: 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. <br />
<br />
: 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:<br />
:# Add the unspecified technical additions that ESRI had hinted at desiring, and <br />
:# 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.<br />
<br />
: '''1 April 2014: Positive reception to "Optimized LAS" / LASzip collaboration April Fools announcement'''<br />
<br />
: 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.<br />
<br />
: '''October 2014: Announcement of [open] LAS Compatibility mode'''<br />
<br />
: [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. <br />
<br />
: '''November 2014: ESRI announces proprietary extension to LAS 1.4'''<br />
<br />
: 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.<br />
<br />
: 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.<br />
<br />
=Value of Standards=<br />
<br />
The importance of Open Standards is described in most government IT policies. For instance, the United Kingdom policy states:<br />
: … 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 – [http://www.gov.uk/government/uploads/system/uploads/attachment_data/file/78959/All_About_Open_Source_v2_0.pdf An Introduction to Open Source Software for Government IT], Version 2.0, United Kingdom Cabinet Office</ref><br />
<br />
The value of Open Standards has been described in numerous national studies on the effects of standards on economic growth.<br />
<br />
: ... 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><br />
<br />
=Further Reading=<br />
<br />
# [http://boundlessgeo.com/2014/01/lidar-format-wars/ Paul Ramsey provides background to LAS vs Optimised LAS]<br />
# [http://rapidlasso.com/2015/02/22/lidar-las-asprs-esri-and-the-laz-clone/ Running commentary by Martin Isenburg, author of LASlib]<br />
# [http://rapidlasso.com/2014/11/06/keeping-esri-honest/ Earlier comment from Martin Isenburg]<br />
# [http://rapidlasso.com/2013/12/30/new-compressed-las-format-by-esri/ First call-to-action by Martin Isenburg]<br />
# [http://blog.lidarnews.com/esri-announces-las-compression/ ESRI Announces "Optimised LAS"]<br />
# [http://www.lidarnews.com/content/view/10214 ESRI description of "Optimised LAS"]<br />
# [http://lists.osgeo.org/pipermail/ica-osgeo-labs/2015-March/001225.html Discussion background on this topic at Geo for All list]<br />
# [http://cameronshorter.blogspot.com.au/2015/04/esris-claim-at-being-good-standards.html Refuting ESRI's response and claim to be good Open Standards citizens]<br />
<br />
News coverage:<br />
# [http://www.itnews.com.au/News/402914,open-source-devs-in-uproar-over-esri-las-lock-in-plans.aspx IT News]<br />
# [http://news.slashdot.org/story/15/04/21/1624219/osgeo-foundation-up-in-arms-over-esri-las-lock-in-plans Slashdot]<br />
# [http://www.heise.de/newsticker/meldung/LIDAR-offenes-Dateiformat-LAS-in-Bedraengnis-2609710.html Heise Online] - German speaking IT news.<br />
# [http://www.spatialsource.com.au/2015/04/21/os-developers-concerned-over-new-esri-lidar-format/ Spatial Source]<br />
<br />
=References=<br />
<br />
<references /></div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=LIDAR_Format_Letter&diff=83763LIDAR Format Letter2015-04-22T09:09:42Z<p>Dkastl: /* Signed */</p>
<hr />
<div>=Open Letter of the Need for Open Standards in LiDAR=<br />
April 2015.<br />
<br />
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.<br />
<br />
<br />
We request that:<br />
# 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.<br />
# 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 joins with 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.<br />
# 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.<br />
# 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.<br />
<br />
=Signed=<br />
Name, Affiliation(s), Optional comment on interest in Open LiDAR format<br />
<br />
# Suchith Anand, Geo for All, committed to Open Principles in Geo Education and Policy.<br />
# 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].<br />
# 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.<br />
# Stefan Keller, founder and director of [http://www.hsr.ch/geometalab Geometa Lab]; Professor in GIS, databases, open (government) data and interoperability; maintainer of GeoConverter; contributor to open source software (GDAL/OGR, QGIS).<br />
# 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.<br />
# 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.<br />
# [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 and to Open Principles in Research.<br />
# 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.<br />
# [http://www.geodatawiz.com/armin-schmidt 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.<br />
# [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.<br />
# [http://pt.linkedin.com/pub/jorge-rocha/1b/560/499 Jorge Gustavo Rocha], Professor, Computer Science Department, University of Minho, Portugal, committed to better science through [http://www.gistam.org/EventChairs.aspx?y=2016 Open Data].<br />
# [http://people.eecs.ku.edu/~miller/ Jim Miller], University of Kansas, Professor, Computer Science. Open standards for data exchange are essential for education and research.<br />
# [http://www.linkedin.com/pub/brandt-melick/22/869/261 Brandt Melick], Information Technology Department Director, Springfield Oregon USA. The need to promote open solutions is paramount.<br />
# Alex Paza Makini, National University Solomon Islands, Natural Resources and Applied Science. Committed to open data standards for education and research, and everything beyond.<br />
# Jorg M. Hacker, Professor, 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.<br />
# 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.<br />
# [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.<br />
# [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.<br />
# [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.<br />
# [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.<br />
# [[User:Ivansanchez|Iván Sánchez Ortega]], [http://www.mazemap.no Mazemap]. OSGeo Charter member and Open Data nerd.<br />
# [[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.<br />
# [[User:vehrka|Pedro-Juan Ferrer]], [http://www.geomaticblog.net Geomaticblog]. OSGeo Charter member and member of the Open Knowledge Foundation.<br />
# [http://www.linkedin.com/pub/karl-donert/3/160/571 Professor Karl Donert], President European Association of Geographers (http://www.eurogeo.nl/ EUROGEO)<br />
# Drew Fenton, Boulder Creek, CA [http://www.savetheredwoods.org/redwoods/coast-redwoods/ Countdown to the Last Coast Redwood]. Please protect Open Standards for geospatial data!<br />
# [[User:Bolosig|Wladimir Szczerban]], [http://www.geoinquiets.cat Geoinquiets] Geogeek & OSGeo Spanish Local Chapter Member, Spain<br />
# [http://vmx.cx Volker Mische], OSGeo Charter member and creator of GeoCouch<br />
# [http://www.linkedin.com/in/clquintanilla Carlos López Quintanilla], [http://www.psig.es PSIG] [http://www.geoinquiets.cat Geoinquiets] GIS consultant, Spain<br />
# [[User:woodbri|Stephen Woodbridge]], [http://imaptools.com iMaptools], OSGeo Charter member.<br />
# [[User:odoepner|Oliver Doepner]], [http://oliver.doepner.net doepner.net], Software Engineer (Java,Linux), Open Standards and Open Source advocate<br />
# [[User:Lucadelu|Luca Delucchi]], [http://gis.cri.fmach.it Fondazione Edmund Mach], OSGeo Charter member, FOSS4G and Open Data developer, advocate, contributor and user.<br />
# Antoine Cottin, CTO of [http://www.carbomap.com Carbomap Ltd.] and creator of [http://github.com/carbomap/Fleurdelas Fleurdelas], Edinburgh, United Kingdom.<br />
# [http://strk.keybit.net Sandro Santilli], [http://strk.keybit.net/services.html NetLab], Free Software Hacker. There are already too many users slave to their tools, let's stop that!<br />
# [http://www.itopen.it Alessandro Pasotti], [http://www.itopen.it ItOpen], GIS Free Software Developer.<br />
# [http://www.roccatello.com Eduard Roccatello], [http://www.3dgis.it 3DGIS], 3DGIS CTO and co-Founder<br />
# [[User:moovida|Andrea Antonello]], [http://www.hydrologis.com HydroloGIS], OSGeo Charter member, Open Source GIS developer, HydroloGIS co-founder.<br />
# [http://www.associazionegfoss.it Stefano Campus], President of [http://www.associazionegfoss.it GFOSS.it] Association (Associazione Italiana per l'Informazione Geografica Libera), Italian Local Chapter of OSGeo Foundation.<br />
# [http://wiki.osgeo.org/wiki/User:Madi Margherita Di Leo], OSGeo Charter Member<br />
# [http://wiki.osgeo.org/wiki/User:Sacosta Sergio Acosta y Lara], OSGeo Charter Member<br />
# [http://wiki.osgeo.org/wiki/User:Maximdubinin Maxim Dubinin], CEO at NextGIS, OSGeo Charter Member. Another 'standard' proprietary format? No, thank you.<br />
# [[User:Steko|Stefano Costa]], Soprintendenza Archeologia della Liguria, Ministero dei Beni e delle Attività Culturali e del Turismo, Italy<br />
# [http://www.geog.illinois.edu/people/jgrn Jonathan Greenberg], Assistant Professor, [http://publish.illinois.edu/jgrn/ GEARS Laboratory], Department of Geography and Geographic Information Science, University of Illinois at Urbana-Champaign.<br />
# Bob Basques, Saint Paul, Mn., Technical Director for SharedGeo.<br />
# [http://wiki.osgeo.org/wiki/User:Maning Maning Sambale], OSGeo Charter Member<br />
# [http://wiki.osgeo.org/wiki/User:Pcav Paolo Cavallini], QGIS PSC<br />
# [http://wiki.osgeo.org/wiki/User:Dr Phillip Davis], Member OSGeo Geo For All education advisory board, Director @ GeoAcademy<br />
# [http://wiki.osgeo.org/wiki/User:Nbozon Nicolas Bozon], Researcher and software developer, OSGeo Charter Member<br />
# [http://www.linkedin.com/in/ruslanrainis Ruslan Rainis], Professor, Director, [http://www.research.usm.my/default.asp?tag=36 Centre for Research Initiatives in Liberal Arts & Social Sciences](CRI-LASS). Open GeoInformation for a Sustainable Tomorrow and the Bottom Billions.<br />
# [[User:Silli|Silvia Franceschi]], [http://www.hydrologis.com HydroloGIS], OSGeo Charter member, Environmental Engineer Open Source GIS power user, HydroloGIS co-founder.<br />
# Oscar Martinez Rubi [http://esciencecenter.nl Netherlands eScience Center] eScience engineer.<br />
# Werner Macho, QGIS team member. Committed to open data standards for education and research.<br />
# Giuseppe Patti, Geologist and Freelance Geospatial Advisor, GFOSS supporter.<br />
# [http://wiki.osgeo.org/wiki/User:Drappo Daniel Rappo], Professor, University of Applied Sciences and Arts Western Switzerland, School of Business and Engineering Vaud.<br />
# [[User:nachouve|Juan Ignacio Varela]], Freelance Geospatial Advisor and OSGeo Local Chapter Member.<br />
# [[User:dmorissette|Daniel Morissette]], President at [http://mapgears.com Mapgears], OSGeo Charter member.<br />
# [http://www.linkedin.com/in/raulnanclares Raul Nanclares], RS&GIS Specialist<br />
# [http://www.ing.unitn.it/dica/hp/index_eng.php?user=rigon Riccardo Rigon], Professor at University of Trento (Italy)<br />
# [[User:Siki| Zoltan Siki]] Budapest University of Technology and Economics (Hungary), OSGeo Charter member.<br />
# [http://lefsky.org Michael Lefsky], Professor of Remote Sensing Science, Colorado State University and Director, Center for Ecological Applications of Lidar.<br />
# [http://www.linkedin.com/pub/lucas-c-villa-real/7/a0b/b06 Lucas Villa Real], Research software engineer at IBM Research - Brazil.<br />
# [http://terraremote.com Loren Dawe], GIS Manager at Terra Remote Sensing Inc. Lidar Supplier and Open Standards Advocate<br />
# [http://wiki.osgeo.org/wiki/User:Warmerda Frank Warmerdam], Software Developer, OSGeo Charter member<br />
# [http://ch.linkedin.com/pub/jens-ingensand/0/836/6b0 Jens Ingensand], Professor, University of Applied Sciences and Arts Western Switzerland, [http://www.heig-vd.ch/international School of Business and Engineering Vaud].<br />
# [http://nsidc.org/research/bios/khalsa.html Siri Jodha Khalsa], Research Scientist, National Snow and Ice Data Center, [http://cires.colorado.edu/ Cooperative Institute for Research in Environmental Sciences], University of Colorado, Boulder, USA<br />
# [http://gis.uster.ch/ Andreas Neumann], GIS manager, City of Uster, Kanton Zurich, Switzerland<br />
# [http://www.iwmi.org/ Yann Chemin], Researcher - Remote Sensing, International Water Management Institute, Colombo, Sri Lanka<br />
# [http://www.linkedin.com/in/etiennebracine Etienne B. Racine], Geomatics and remote sensing project manager, WSP, Canada<br />
# [http://www.linkedin.com/pub/alejandro-hinojosa/7/33b/342 Alejandro Hinojosa], [http://cicese.mx CICESE Research Center], Earth Sciences Division, GIS & Remote Sensing Lab, Ensenada, Mexico<br />
# [http://wiki.osgeo.org/wiki/User:epifanio Massimo Di Stefano], OSGeo Charter Member<br />
# [http://clas.ucdenver.edu/directory/faculty-staff/Rafael-Moreno Rafael Moreno], University of Colorado Denver, [http://www.ucdenver.edu/academics/colleges/CLAS/Departments/ges/Pages/Geography.aspx Department of Geography and Environmental Sciences]. Openness is fundamental to progress.<br />
# Peter Drexel, GIS manager, [http://www.vorarlberg.at/vorarlberg/bauen_wohnen/bauen/vermessung_geoinformation/start.htm State of Vorarlberg (State Survey Office)], Austria<br />
# [http://www.linkedin.com/pub/marco-minghini/a8/3b6/198 Marco Minghini], Department of Civil and Environmental Engineering, [http://www.polimi.it Politecnico di Milano]. Committed to Open Principles in Geo Education and Research.<br />
# [http://www.linkedin.com/pub/candan-eyl%C3%BCl-kilsedar/65/380/976 Candan Eylül Kilsedar], WebGIS Developer, Research Fellow at [http://www.polimi.it Politecnico di Milano]. <br />
# [http://wiki.osgeo.org/wiki/User:AlastairMcKinstry Alastair McKinstry], Debian Linux meteorology/GIS developer, Ireland<br />
# [http://people.unibo.it/it/elena.mezzini2 Elena Mezzini], Remote-sensing in forest ecology, Research Fellow, Department of Agricultural Sciences, University of Bologna, Italy.<br />
# [http://www.linkedin.com/profile/view?id=43566064 Mihai A. Tanase], Honorary fellow, Dept. of Forest and Ecosystem Science, The University of Melbourne, Australia<br />
# [http://www.linkedin.com/pub/dave-murray/10/742/3a2 Dave Murray], GIS Coordinator at [http://www.ci.westminster.co.us/ City of Westminster]<br />
# Ayesa Martínez Serrano, Estudiante de Doctorado en [http://www.ciga.unam.mx/ Geografía del Centro de Investigaciones en Geografía Ambiental de la UNAM-México]<br />
# [http://www.linkedin.com/pub/christopher-crosby/15/b7/114 Christopher Crosby], co-founder, [http://www.opentopography.org/ OpenTopography]<br />
# [http://sg.linkedin.com/in/sgganesh Shanmugam Ganeshkumar], Vice President - Consulting, [http://www.geoicon.com GeoICON]<br />
# [[User:Chaitanya|Chaitanya Kumar CH]], GIS Developer with [http://www.egis-geoplan.com/ Egis Geoplan - India] and OSGeo Charter member.<br />
# KS Rajan, Associate Professor and Head, [http://lsi.iiit.ac.in/ Lab for Spatial Informatics, IIIT Hyderabad] and Chairman, [http://www.kaiinos.com/ KAIINOS Geospatial Technologies]; Promoter and Supported of Open Source, Open Data, Open Standards and e-Governance in India<br />
# Pericles Nacionales, RS/GIS Specialist and OSGeo Charter member.<br />
# Vasile Crăciunescu, Researcher at Romanian National Meteorological Administration and OSGeo Board member.<br />
# [http://geo.tuwien.ac.at/staff/andreas-roncat/ Andreas Roncat] PostDoc Researcher, Research Groups Photogrammetry and Remote Sensing, [http://www.geo.tuwien.ac.at/ Department of Geodesy and Geoinformation], Vienna University of Technology, Austria. In full agreement with [http://wiki.osgeo.org/wiki/User:Maximdubinin Maxim Dubinin]: Another 'standard' proprietary format? No, thank you.<br />
# [http://wiki.osgeo.org/wiki/User:remanuele Rob Emanuele], Software Developer, Azavea Inc.<br />
# Codrina Ilie, Researcher at the Groundwater Engineering Research Center, Technical University of Civil Engineering Bucharest and OSGeo Charter Member<br />
# [http://wiki.osgeo.org/wiki/User:Djay Gérald Fenoy], Software Developer, OSGeo Charter Member.<br />
# [http://www.aston.ac.uk/eas/staff/a-z/dr-lucy-bastin/ Lucy Bastin], Software Developer at the Joint Research Centre of the European Commission / Computer Science lecturer, UncertML developer, Member of OGC SWG on User Feedback.<br />
# Matt Wilkie, Geomatics Analyst at [http://www.gov.yk.ca/ Yukon Government], [http://www.env.gov.yk.ca/geomatics Department of Environment]. A practising GIS Professional for 20+ years. Throughout that time, the process of manipulating data into, through and out of proprietary formats has been the most aggravating source of inefficiency and wasted time. Things are hard enough without adding unnecessary barriers.<br />
# [[User:Annakrat|Anna Petrasova]], OSGeo Charter Member, GRASS GIS developer<br />
# [http://www.linkedin.com/pub/mark-seibel-gisp/45/517/942 Mark Seibel], Geospatial Hacker. Long live open Geo data & software.<br />
# [http://www.wrsc.org/people/ben-discoe Ben Discoe], [http://vterrain.org/ Virtual Terrain Project] and [http://www.leica-geosystems.us/en/HDS-Laser-Scanners-SW_5570.htm Leica Geosystems HDS], I wrangle point clouds every day. Semi-open E57 is bad enough. No more closed formats!<br />
# [http://www.linkedin.com/pub/ilda-clos/19/21b/391 Ilda Clos], GIS & IWRM specialist<br />
# [https://jp.linkedin.com/in/dkastl Daniel Kastl], Founder [http://georepublic.info Georepublic] and OSGeo Charter Member<br />
<br />
=Background=<br />
==About LiDAR==<br />
<br />
[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.<br />
<br />
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.<br />
<br />
<br />
==LAS Limitations==<br />
<br />
Quoting [http://boundlessgeo.com/2014/01/lidar-format-wars/ Paul Ramsey]:<br />
<br />
: LAS format is not without its drawbacks:<br />
<br />
:* 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.<br />
:* 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.<br />
: Clearly there is a little more work to be done. Can LAS be improved? In fact, it already has been:<br />
:* An open source compression library, LASzip can apply 20''':'''1 lossless compression to LAS files, making them great for archival purposes.<br />
:* 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.<br />
: 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.<br />
<br />
<br />
=="Optimized LAS" A ''' ''Proprietary'' ESRI Format'''==<br />
ESRI announced, 12 January 2014, 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]].<br />
<br />
The implementation of the "Optimized LAS" format is not available as Open Source and the format and algorithm details itself are undocumented, which means nobody can currently create alternate implementations, neither closed nor Open Source. This causes both technical as well as legal barriers for other applications reading and/or writing to this proprietary format. It 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.<br />
<br />
One year after releasing the "Optimized LAS" format, ESRI released a Windows only library (DLL) as a free-of-charge (gratis) download that is claimed to convert between LAS and "Optimized LAS". Note there is a distinct difference between a "free-of-charge" binary distribution of DLLs and publishing something as "Open Source". Unless the source code of the library is released as Open Source under an Open Source 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.<br />
<br />
Ironically, ESRI later placed their '''binary''' library files [http://github.com/Esri/esri-zlas-io-library on github] accompanied by an Apache License, but no source code was published. The distribution of binaries without source code is allowed by Apache License, but very uncommon and misleading, to say the least. The practice goes against the basic idea of “Open Source” and the Open Source Initiative (OSI) even has an FAQ entry on the obvious contradiction of [http://opensource.org/faq#non-distribution “Open Source” without source code].<br />
<br />
==OGC's Efforts For An ''' ''Open'' LiDAR Standard'''==<br />
<br />
The [http://www.opengeospatial.org/ Open Geospatial Consortium (OGC)] has indicated their interest in developing a standard LiDAR format.<br />
<br />
Carl Reed (formerly on OGC staff) provided the following information on OGC's previous efforts to work toward enabling Open Standards in LiDAR:<br />
<br />
: "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."<br />
<br />
[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.<br />
: 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.<br />
<br />
<br />
==History: LAS and ESRI's "Optimized LAS"==<br />
<br />
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":<br />
<br />
: '''Summary:'''<br />
<br />
:* The LAS format has been used successfully for over a decade.<br />
:* Within last couple of years, ESRI has added native LAS support into ESRI products.<br />
:* ESRI discussed embracing the open [http://laszip.org LAZ] format and simultaneously developed a proprietary "Optimized LAS" format.<br />
:* The open geospatial community offered, on numerous occasions, to work with ESRI to avoid format fragmentation.<br />
:* ESRI's proprietary "Optimized LAS" format is very similar in design and performance to the open [http://laszip.org LASzip] format.<br />
<br />
: '''1998: Original LAS format definition'''<br />
<br />
: 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.<br />
<br />
: '''2011: ESRI joins LAS Working Group'''<br />
<br />
: 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.<br />
<br />
: 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."<br />
<br />
: '''June 2012: ArcGIS 10.1 includes [proprietary] LAS Dataset file'''<br />
<br />
: 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.<br />
<br />
: '''2012/2013: Collaboration Discussions'''<br />
<br />
: 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."<br />
<br />
: 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."<br />
<br />
: '''June 2013: ESRI asked to sponsor clean LASzip DLL'''<br />
<br />
: 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."<br />
<br />
: 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."<br />
<br />
: '''July 2013: ArcGIS 10.2 includes [proprietary] LAS indexing '''<br />
<br />
: With the release of ArcGIS 10.2 in July 2013, ESRI introduced spatial indexing to speed up area-of-interest queries. Their new proprietary *.lasx files were seemingly identical in functionality to the open *.lax files that had been [http://groups.google.com/d/topic/lastools/j0qA8NBMHJs/discussion announced] two years earlier - in May 2011 - and were [http://rapidlasso.com/2012/12/03/lasindex-spatial-indexing-of-lidar-data/ presented] at ELMF in November 2012.<br />
<br />
: '''July 2013: Open LASzip API released'''<br />
<br />
: 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.<br />
<br />
: '''December 2013 : ESRI discovered to be secretly developing proprietary LAS format'''<br />
<br />
: 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. <br />
<br />
: 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:<br />
:# Add the unspecified technical additions that ESRI had hinted at desiring, and <br />
:# 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.<br />
<br />
: '''1 April 2014: Positive reception to "Optimized LAS" / LASzip collaboration April Fools announcement'''<br />
<br />
: 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.<br />
<br />
: '''October 2014: Announcement of [open] LAS Compatibility mode'''<br />
<br />
: [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. <br />
<br />
: '''November 2014: ESRI announces proprietary extension to LAS 1.4'''<br />
<br />
: 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.<br />
<br />
: 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.<br />
<br />
=Value of Standards=<br />
<br />
The importance of Open Standards is described in most government IT policies. For instance, the United Kingdom policy states:<br />
: … 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 – [http://www.gov.uk/government/uploads/system/uploads/attachment_data/file/78959/All_About_Open_Source_v2_0.pdf An Introduction to Open Source Software for Government IT], Version 2.0, United Kingdom Cabinet Office</ref><br />
<br />
The value of Open Standards has been described in numerous national studies on the effects of standards on economic growth.<br />
<br />
: ... 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><br />
<br />
=Further Reading=<br />
<br />
# [http://boundlessgeo.com/2014/01/lidar-format-wars/ Paul Ramsey provides background to LAS vs Optimised LAS]<br />
# [http://rapidlasso.com/2015/02/22/lidar-las-asprs-esri-and-the-laz-clone/ Running commentary by Martin Isenburg, author of LASlib]<br />
# [http://rapidlasso.com/2014/11/06/keeping-esri-honest/ Earlier comment from Martin Isenburg]<br />
# [http://rapidlasso.com/2013/12/30/new-compressed-las-format-by-esri/ First call-to-action by Martin Isenburg]<br />
# [http://blog.lidarnews.com/esri-announces-las-compression/ ESRI Announces "Optimised LAS"]<br />
# [http://www.lidarnews.com/content/view/10214 ESRI description of "Optimised LAS"]<br />
# [http://lists.osgeo.org/pipermail/ica-osgeo-labs/2015-March/001225.html Discussion background on this topic at Geo for All list]<br />
# [http://cameronshorter.blogspot.com.au/2015/04/esris-claim-at-being-good-standards.html Refuting ESRI's response and claim to be good Open Standards citizens]<br />
<br />
News coverage:<br />
# [http://www.itnews.com.au/News/402914,open-source-devs-in-uproar-over-esri-las-lock-in-plans.aspx IT News]<br />
# [http://news.slashdot.org/story/15/04/21/1624219/osgeo-foundation-up-in-arms-over-esri-las-lock-in-plans Slashdot]<br />
# [http://www.heise.de/newsticker/meldung/LIDAR-offenes-Dateiformat-LAS-in-Bedraengnis-2609710.html Heise Online] - German speaking IT news.<br />
# [http://www.spatialsource.com.au/2015/04/21/os-developers-concerned-over-new-esri-lidar-format/ Spatial Source]<br />
<br />
=References=<br />
<br />
<references /></div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_Recommendations_for_Students&diff=82598Google Summer of Code Recommendations for Students2015-03-09T16:42:09Z<p>Dkastl: /* How to get in contact via IRC */</p>
<hr />
<div>== How to get in contact via mailing lists ==<br />
<br />
Since OSGeo is an umbrella organisation for multiple projects, each project has their own discussion and development mailing lists.<br />
<br />
'''Main OSGeo mailing lists of interest to students:'''<br />
: Please start here, when contacting us for the first time with questions about Google Summer of Code.<br />
<br />
:* OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc)<br />
:* OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)<br />
<br />
Also see the [[Mailing Lists]] page for project specific lists, as well as the longer list at http://lists.osgeo.org.<br />
<br />
<br />
== How to get in contact via IRC ==<br />
<br />
Primary channel:<br />
<br />
* irc://irc.freenode.net/#osgeo (Web based [http://irc.telascience.org/cgi-bin/irc.cgi IRC client], [http://webchat.freenode.net alternative])<br />
<br />
GSoC @ OSGeo inter-project discussions:<br />
<br />
* irc://irc.freenode.net/#osgeo-soc<br />
<br />
Project irc channels:<br />
<br />
* irc://irc.freenode.net/#gdal<br />
* irc://irc.freenode.net/#geoserver<br />
* irc://irc.freenode.net/#geotools<br />
* irc://irc.freenode.net/#grass<br />
* irc://irc.freenode.net/#gvsig<br />
* irc://irc.freenode.net/#mapguide<br />
* irc://irc.freenode.net/#mapnik<br />
* irc://irc.freenode.net/#mapserver<br />
* irc://irc.freenode.net/#openlayers<br />
* irc://irc.freenode.net/#opticks<br />
* irc://irc.freenode.net/#osgeolive<br />
* irc://irc.freenode.net/#ossimplanet<br />
* https://gitter.im/pgRouting/pgrouting<br />
* irc://irc.freenode.net/#postgis<br />
* irc://irc.freenode.net/#qgis<br />
* irc://irc.freenode.net/#udig<br />
* irc://irc.oftc.net/#osm-dev<br />
* irc://irc.freenode.net/#geonode<br />
<br />
== How to increase your chances of being selected ==<br />
<br />
If you put yourself in the shoes of the mentor that should select the student, you'll immediately realize that there are some behaviors that are usually rewarded. Here's some examples.<br />
<br />
=== Be proactive ===<br />
<br />
Mentors are more likely to select students that openly discuss the existing ideas and / or propose their own. It is a '''bad idea''' to just submit your idea only in melange, because it won't be noticed. Mentors and developers discuss ideas most in [[Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_mailing_lists | mailing lists]].<br />
<br />
=== Demonstrate your skills ===<br />
<br />
Consider that mentors are being contacted by several students that apply for the same project. A way to show that you are the best candidate, is to demonstrate that you are familiar with the software and you can code. How? Browse the bug trac, fix some bugs and propose your patch in mailing list, and/or ask mentors to challenge you!<br />
<br />
=== Demonstrate your intention to stay ===<br />
<br />
Students that are likely to disappear after GSoC are less likely to be selected. This is because there is no point in developing something that won't be maintained. And moreover, one scope of GSoC is to bring new developers to the community.<br />
<br />
=== [http://xkcd.com/293/ RTFM] ===<br />
<br />
Read the relevant information about GSoC in the wiki / web pages before asking. Most FAQs have been answered already! <br />
* OSGeo Wiki pages related to GSoC can be browsed from [http://wiki.osgeo.org/wiki/Category:Google_Summer_of_Code Category:Google Summer of Code]. <br />
* [http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2015/help_page FAQ from Melange web site].<br />
* A group of past GSoC students, mentors, and Googlers have prepared this short book just for you: [https://flossmanuals.net/GSoCStudentGuide/ The Student's Guide to the Summer of Code]<br />
* If you are new to OSGeo, take the time to familiarize with the [http://www.osgeo.org/content/foundation/about.html Open Source Geospatial Foundation]<br />
<br />
== Application questions we'll ask you ==<br />
<br />
* All questions must be answered, ''no exceptions''. Treat this as something between a formal job application and a scholarship application, because that's exactly what it is.<br />
<br />
Name:<br />
<br />
Country:<br />
<br />
School and degree:<br />
<br />
Email:<br />
<br />
Phone:<br />
<br />
OSGeo project(s):<br />
<br />
Title:<br />
(please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")<br />
<br />
Describe your idea<br />
1. Introduction<br />
2. Background<br />
3. The idea<br />
4. Project plan ('''detailed timeline''': how do you plan to spend your summer?)<br />
5. Future ideas / How can your idea be expanded? <br />
<br />
Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:<br />
<br />
Please provide details of general computing experience: <br />
(operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)<br />
<br />
Please provide details of previous GIS experience:<br />
<br />
Please provide details of any previous involvement with GIS programming and other software programming:<br />
<br />
Please tell us why you are interested in GIS and open source software:<br />
<br />
Please tell us why you are interested in working for OSGeo and the software project you have selected:<br />
<br />
Please tell us why you are interested in your specific coding project:<br />
<br />
Would your application contribute to your ongoing studies/degree? If so, how?<br />
<br />
Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over:<br />
<br />
Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?<br />
<br />
Do you have any known time conflicts during the official coding period? (May 19 to August 18)<br />
<br />
== What to expect during the summer ==<br />
<br />
=== Be prepared to be in constant communication with your mentors and project ===<br />
<br />
You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to integrate you into the developer community, so you should get involved with them from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you in case of problems, like making sure you get paid.<br />
<br />
University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.<br />
<br />
=== Weekly reports ===<br />
<br />
Yes, every week we expect to see a report posted to the soc@osgeo mailing list that at least answers the following questions:<br />
<br />
# What did you get done this week?<br />
# What do you plan on doing next week?<br />
# Are you blocked on anything?<br />
<br />
These questions BTW are the same as are used in real-work, when developing with the <br />
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process]. ;)<br />
<br />
If you want, feel free to write *more*. But three sentences is the bare minimum. *IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME*, if you don't send this email your mentors will start to get twitchy, and *especially* if they don't get any responses to their emails / don't see you in IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's cool. We have all studied at some point, just tell us about it up front, be honest, and we'll work around it. If you don't know how to proceed and your mentor isn't answering *definitely* tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)<br />
<br />
During past years this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.<br />
<br />
=== Code repository and documentation ===<br />
<br />
Publishing your progress online is a GSoC requirement. Therefore, all students have to decide, before GSoC coding period starts, where to publish the code they will write. We ask students to give the link to the public repository in the first weekly report.<br />
<br />
The possibilities are:<br />
* get a sandbox in your software project's repository (your mentor will tell you how to get write access)<br />
* work on a branch of the main code repository (for centralized versioning systems like SVN)<br />
* work on a fork of the code repository (for DCVS like Mercurial and Git)<br />
* work on an independent codebase (if you are developing a plugin or some other extra functionality that is not yet part of main codebase)<br />
<br />
Your mentor is the best guide regarding this choice. Please discuss it as soon as possible, and learn how to use the related version control tool well before GSoC coding starts.<br />
<br />
Documentation of your code is important! Don't leave all documentation writing to the last weeks of GSoC. It makes sense to outline it at the beginning of coding period, then refine it while you code. It is an important support to coding, as it is a mirror of the overall plan for the summer, and an essential source of information for who will use your code.<br />
<br />
=== Wiki page and blogs ===<br />
<br />
In addition to weekly reports we require you to maintain a wiki or blog page for your project. You should store your weekly reports there and add other information, like how to compile and test your program. If applicable add screenshots and other nice info.<br />
<br />
Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this.<br />
<br />
We plan to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.<br />
<br />
Final reports from those blogs and wiki pages will be collected into a OSGeoofcode posting about what everyone did during the summer, ensuring you long lasting fame and fortune. (''Or failing that, a bit of public press, a bit of cash from Google, and a lot of gratitude and kudos from us, your peers.'')<br />
<br />
<br />
[[Category: Google Summer of Code]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=Conference_Options_2014&diff=80287Conference Options 20142014-10-03T00:19:56Z<p>Dkastl: /* Votes/Comments */</p>
<hr />
<div>Future organisation of FOSS4G has been discussed at [http://2014.foss4g.org FOSS4G 2014] then followed onto OSGeo emails lists (Conference, Discuss and Board lists).<br />
<br />
This wiki page aims to collate background information, options, options, and recommendations in order to facilitate making decisions about guiding the future management of FOSS4G events.<br />
<br />
= Editing this wiki =<br />
All are encouraged to add to this wiki. Opinions (rather than facts) should be prefaced with your name:<br />
<br />
[First Last] Comment ...<br />
<br />
= Background =<br />
The international FOSS4G conference has grown from 100-200 attendees when it started 10+ years ago, to ~ 800 attendees now in 2014. Some regional events are also attracting large numbers. Extra attendance leads to extra effort required to coordinate, leading the OSGeo Community to consider options on how to move forward.<br />
<br />
= Options for focus = <br />
The official event policy states an OSGeo event must contribute positively to the [[OSGeo Mission]], which is a) to support the development of open source Geospatial Software, and b) to promote its widespread use.<br />
Focus for any OSGeo can balance between these 2 goals: focussing on the support of the developement probably targets on a smaller well-known inner circle, whereas focussing on promotion of its use aims at a broader audience.<br />
<br />
== Focus on supporting the development of open source geospatial software ==<br />
=== Advantages ===<br />
<br />
* Great venue to promote how open source works and attract new developers<br />
* Foss4g as a "meeting of tribes" promotes cross platform activities<br />
* Attracting new committers is a goal for projects joining a software foundation.<br />
<br />
=== Disadvantages ===<br />
<br />
* Conflict with customer focus (developers attendance often sponsored by their employer)<br />
<br />
== Focus on the promotion of use of open source geospatial software ==<br />
=== Advantages ===<br />
<br />
* Great boost for open source adoption in the hosting region (attendance often draws from nearby countries)<br />
<br />
=== Disadvantages ===<br />
<br />
* Travel hard to justify<br />
<br />
== Consideration of remaining OSGeo goals ==<br />
<br />
FOSS4G touches on all foundation goals:<br />
<br />
* To provide resources for foundation projects - eg. infrastructure, funding, legal.<br />Funds raised by foss4g support OSGeo operation.<br />
<br />
* To promote freely available geodata - free software is useless without data.<br />Topic of interest in the foss4g program.<br />
<br />
* To promote the use of open source software in the geospatial industry (not just foundation software) - eg. PR, training, outreach.<br />Foss4g presentations and workshops are not limited to foundation projects.<br />
<br />
* To encourage the implementation of open standards and standards-based interoperability in foundation projects.<br />Topic of interest in the foss4g program.<br />
<br />
* To ensure a high degree of quality in foundation projects in order to build and preserve the foundation "brand".<br />Handing out OSGeo Live (and the marketing opportunity of foss4g) helps encourage an annual release for foundation projects.<br />
<br />
* To make foundation and related software more accessible to end users - eg. binary "stack" builds, cross package documentation.<br />Workshops and presentations promote accessibility. Cross project presentations (benchmarks) less common - perhaps worth funding.<br />
<br />
* To provide support for the use of OSGeo software in education via curriculum development, outreach, and support.<br />Topic of interest in the foss4g program.<br />
<br />
* To encourage communication and cooperation between OSGeo communities on different language (eg. Java/C/Python) and operating system (eg. Win32, Unix, MacOS) platforms.<br />Foss4g is billed as the "meeting of the tribes" - this has gradually dissolved boundaries leaving a solid focus on spatial rather than language or platform.<br />
<br />
* To support use and contribution to foundation projects from the worldwide community through internationalization of software and community outreach.<br />Foss4g is our largest outreach effort, the selection process encourages the event to be held in a range of locations world wide.<br />
<br />
* To operate an annual OSGeo Conference, possibly in cooperation with related efforts (eg. EOGEO).<br /> Foss4g acts as our annual OSGeo conference. <br />
<br />
* To award the Sol Katz award for service to the OSGeo community.<br />Announced at foss4g.<br />
<br />
= Options for management of FOSS4G =<br />
Following are options which have been identified.<br />
<br />
==Same as before==<br />
For a number of years, the LOCs for large FOSS4G events have hired a new Professional Conference Organiser (PCO). This PCO is usually local and knows the city where the event is being held.<br />
<br />
===Advantages===<br />
* Minimal effort (for the board) to set up.<br />
* A local PCO likely has local experience.<br />
<br />
===Disadvantages===<br />
* Loss of knowledge between events and associated risk of failure.<br />
* Significant stress put on LOCs.<br />
<br />
===Votes/Comments===<br />
* -0 CameronShorter<br />
* -1 Darrell: This model simply doesn't scale. The idea that local knowledge is required for the PCO position is, quite simply, false. (I find it amazing that we can operate a global organization on a small budget, but are unable to conceive that others are also able to.)<br />
* -1 Jive: If we want foss4g then this model does not scale, if we were more flexible we could end up with a different flavour each annual conference<br />
* -0 DanielKastl: Pretty much every year some local community has to reinvent the wheel, setup a new infrastructure for website, payment, etc.. IMO it's currently done not very efficient.<br />
<br />
==Engage a long term (for profit) PCO==<br />
<br />
===Advantages===<br />
* Institutional knowledge. The conference knowledge carries on in the organisation, and is hopefully not entirely imbued in one person. <br />
* Simplicity.<br />
<br />
===Disadvantages===<br />
* How would an OSGeo exit out of the arrangement with the PCO if the relationship sours?<br />
* It is in the vested interests of a PCO not to share information with community, such that we become reliant upon the PCO.<br />
<br />
===Votes/Comments===<br />
* -0 CameronShorter. I'm nervous about an exit strategy if things go sour.<br />
* +1 Darrell. It's simple, the contract is renewable on an annual basis. If either party isn't happy with the arrangement, it can be ended. Put into the contract what knowledge is to be shared and how.<br />
* -0 Jive: Risk is a subject for contract negotiation<br />
* +0 DanielKastl: It's better than looking for a new PCO every year, so if there is a good candidate this might not require much work for OSGeo. I just doubt that it's easy to find a suitable PCO.<br />
<br />
== Hire a staff person to be the organiser ==<br />
<br />
This is more risk, but also offers more potential.<br />
<br />
[[Jeff McKenna]] proposed this option formally to the OSGeo Board in 2011. A full job description and rates are outlined on the wiki page: [[FOSS4G Advisor Role]]<br />
<br />
===Advantages:===<br />
<br />
* Having a staff person allows OSGeo to be more flexible in organising conferences. Is there a budding regional conference that needs some assistance? We can help with that. Would OSGeo like to foster growth in regions without a local FOSS4G event? OSGeo can do that.<br />
<br />
===Disadvantages===<br />
<br />
* You would only have one staff person, which means more risk of losing institutional knowledge if that person leaves.<br />
* Potential for being seen as less of a a volunteer led organisation. <br />
* Hiring is hard, and takes time, especially to find a good autonomous person to take on this role<br />
<br />
===Votes/Comments===<br />
* +0 CameronShorter<br />
* +0 Darrell: I think this is a good idea, if and only if OSGeo has a clear vision of how they want the organization and the role to grow. Right now, I don't see that they do.<br />
* +0 Jive: Would hate to see us responsible for an employee, easier to exit out of a relationship with PCO. Still an employee could line up PCO in region hosting foss4g (as we advise LOC committee to do) while handling community / publicity angle.<br />
* +1 DanielKastl: I wouldn't call it "hire a staff", but pay people to spend a certain amount of time to lead organizing the conference. This doesn't need to be a single person (but could be shared within a small team of 2 or 3 people). The idea is, that there is a knowledge transfer from one year to the next, and that work gets done, that volunteers may not find so motivating (ie. overlook the conference management, acquiring sponsors, boring paper work, report to OSGeo,...). German FOSSGIS is doing this way for their local conference, and I think it works pretty well.<br />
<br />
== Partner with LocationTech==<br />
<br />
===Advantages===<br />
<br />
* LocationTech works in the same space, has contacts, and the Eclipse Foundation already runs conferences<br />
* Retention of knowledge between regions<br />
* Potential for future, deepened partnerships<br />
<br />
===Disadvantages===<br />
<br />
* LocationTech works in the same space, has contacts, and the Eclipse Foundation already runs conferences, so there’s a potential for conflicts of interest<br />
* If it doesn’t work out for whatever reason, future partnership opportunities might be lost<br />
* Potential OSGeo Brand dilution due to obvious prominence of LocationTech taking responsibility. Eg, publicity emails would come from a LocationTech email address.<br />
* Reduction in OSGeo income.<br />
<br />
===Votes/Comments===<br />
* -0 CameronShorter. I think the OSGeo/LocationTech relationship discussions have further to go first. Also concerned about loss of OSGeo income and branding.<br />
* -0 VasileCraciunescu. Mostly because I'm concerned about the dilution of OSGeo brand and values.<br />
* +0 Jive: This is outreach - recommend joint events with a range of open source groups - expect LocationTech is an easy way to get started.<br />
* -0 DanielKastl: It sounds too nice to have a "win-win" collaboration, but I fear there is also some conflict of interest. It might be good to give this a try on a local conference (such as FOSS4G NA) first.<br />
<br />
= References =<br />
* http://wiki.osgeo.org/wiki/FOSS4G<br />
* http://wiki.osgeo.org/wiki/FOSS4G_Handbook<br />
* http://wiki.osgeo.org/wiki/Official_OSGeo_Event_Policy</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=Conference_Options_2014&diff=80286Conference Options 20142014-10-03T00:17:25Z<p>Dkastl: /* Votes/Comments */</p>
<hr />
<div>Future organisation of FOSS4G has been discussed at [http://2014.foss4g.org FOSS4G 2014] then followed onto OSGeo emails lists (Conference, Discuss and Board lists).<br />
<br />
This wiki page aims to collate background information, options, options, and recommendations in order to facilitate making decisions about guiding the future management of FOSS4G events.<br />
<br />
= Editing this wiki =<br />
All are encouraged to add to this wiki. Opinions (rather than facts) should be prefaced with your name:<br />
<br />
[First Last] Comment ...<br />
<br />
= Background =<br />
The international FOSS4G conference has grown from 100-200 attendees when it started 10+ years ago, to ~ 800 attendees now in 2014. Some regional events are also attracting large numbers. Extra attendance leads to extra effort required to coordinate, leading the OSGeo Community to consider options on how to move forward.<br />
<br />
= Options for focus = <br />
The official event policy states an OSGeo event must contribute positively to the [[OSGeo Mission]], which is a) to support the development of open source Geospatial Software, and b) to promote its widespread use.<br />
Focus for any OSGeo can balance between these 2 goals: focussing on the support of the developement probably targets on a smaller well-known inner circle, whereas focussing on promotion of its use aims at a broader audience.<br />
<br />
== Focus on supporting the development of open source geospatial software ==<br />
=== Advantages ===<br />
<br />
* Great venue to promote how open source works and attract new developers<br />
* Foss4g as a "meeting of tribes" promotes cross platform activities<br />
* Attracting new committers is a goal for projects joining a software foundation.<br />
<br />
=== Disadvantages ===<br />
<br />
* Conflict with customer focus (developers attendance often sponsored by their employer)<br />
<br />
== Focus on the promotion of use of open source geospatial software ==<br />
=== Advantages ===<br />
<br />
* Great boost for open source adoption in the hosting region (attendance often draws from nearby countries)<br />
<br />
=== Disadvantages ===<br />
<br />
* Travel hard to justify<br />
<br />
== Consideration of remaining OSGeo goals ==<br />
<br />
FOSS4G touches on all foundation goals:<br />
<br />
* To provide resources for foundation projects - eg. infrastructure, funding, legal.<br />Funds raised by foss4g support OSGeo operation.<br />
<br />
* To promote freely available geodata - free software is useless without data.<br />Topic of interest in the foss4g program.<br />
<br />
* To promote the use of open source software in the geospatial industry (not just foundation software) - eg. PR, training, outreach.<br />Foss4g presentations and workshops are not limited to foundation projects.<br />
<br />
* To encourage the implementation of open standards and standards-based interoperability in foundation projects.<br />Topic of interest in the foss4g program.<br />
<br />
* To ensure a high degree of quality in foundation projects in order to build and preserve the foundation "brand".<br />Handing out OSGeo Live (and the marketing opportunity of foss4g) helps encourage an annual release for foundation projects.<br />
<br />
* To make foundation and related software more accessible to end users - eg. binary "stack" builds, cross package documentation.<br />Workshops and presentations promote accessibility. Cross project presentations (benchmarks) less common - perhaps worth funding.<br />
<br />
* To provide support for the use of OSGeo software in education via curriculum development, outreach, and support.<br />Topic of interest in the foss4g program.<br />
<br />
* To encourage communication and cooperation between OSGeo communities on different language (eg. Java/C/Python) and operating system (eg. Win32, Unix, MacOS) platforms.<br />Foss4g is billed as the "meeting of the tribes" - this has gradually dissolved boundaries leaving a solid focus on spatial rather than language or platform.<br />
<br />
* To support use and contribution to foundation projects from the worldwide community through internationalization of software and community outreach.<br />Foss4g is our largest outreach effort, the selection process encourages the event to be held in a range of locations world wide.<br />
<br />
* To operate an annual OSGeo Conference, possibly in cooperation with related efforts (eg. EOGEO).<br /> Foss4g acts as our annual OSGeo conference. <br />
<br />
* To award the Sol Katz award for service to the OSGeo community.<br />Announced at foss4g.<br />
<br />
= Options for management of FOSS4G =<br />
Following are options which have been identified.<br />
<br />
==Same as before==<br />
For a number of years, the LOCs for large FOSS4G events have hired a new Professional Conference Organiser (PCO). This PCO is usually local and knows the city where the event is being held.<br />
<br />
===Advantages===<br />
* Minimal effort (for the board) to set up.<br />
* A local PCO likely has local experience.<br />
<br />
===Disadvantages===<br />
* Loss of knowledge between events and associated risk of failure.<br />
* Significant stress put on LOCs.<br />
<br />
===Votes/Comments===<br />
* -0 CameronShorter<br />
* -1 Darrell: This model simply doesn't scale. The idea that local knowledge is required for the PCO position is, quite simply, false. (I find it amazing that we can operate a global organization on a small budget, but are unable to conceive that others are also able to.)<br />
* -1 Jive: If we want foss4g then this model does not scale, if we were more flexible we could end up with a different flavour each annual conference<br />
* -0 DanielKastl: Pretty much every year some local community has to reinvent the wheel, setup a new infrastructure for website, payment, etc.. IMO it's currently done not very efficient.<br />
<br />
==Engage a long term (for profit) PCO==<br />
<br />
===Advantages===<br />
* Institutional knowledge. The conference knowledge carries on in the organisation, and is hopefully not entirely imbued in one person. <br />
* Simplicity.<br />
<br />
===Disadvantages===<br />
* How would an OSGeo exit out of the arrangement with the PCO if the relationship sours?<br />
* It is in the vested interests of a PCO not to share information with community, such that we become reliant upon the PCO.<br />
<br />
===Votes/Comments===<br />
* -0 CameronShorter. I'm nervous about an exit strategy if things go sour.<br />
* +1 Darrell. It's simple, the contract is renewable on an annual basis. If either party isn't happy with the arrangement, it can be ended. Put into the contract what knowledge is to be shared and how.<br />
* -0 Jive: Risk is a subject for contract negotiation<br />
* +0 DanielKastl: It's better than looking for a new PCO every year, so if there is a good candidate this might not require much work for OSGeo. I just doubt that it's easy to find a suitable PCO.<br />
<br />
== Hire a staff person to be the organiser ==<br />
<br />
This is more risk, but also offers more potential.<br />
<br />
[[Jeff McKenna]] proposed this option formally to the OSGeo Board in 2011. A full job description and rates are outlined on the wiki page: [[FOSS4G Advisor Role]]<br />
<br />
===Advantages:===<br />
<br />
* Having a staff person allows OSGeo to be more flexible in organising conferences. Is there a budding regional conference that needs some assistance? We can help with that. Would OSGeo like to foster growth in regions without a local FOSS4G event? OSGeo can do that.<br />
<br />
===Disadvantages===<br />
<br />
* You would only have one staff person, which means more risk of losing institutional knowledge if that person leaves.<br />
* Potential for being seen as less of a a volunteer led organisation. <br />
* Hiring is hard, and takes time, especially to find a good autonomous person to take on this role<br />
<br />
===Votes/Comments===<br />
* +0 CameronShorter<br />
* +0 Darrell: I think this is a good idea, if and only if OSGeo has a clear vision of how they want the organization and the role to grow. Right now, I don't see that they do.<br />
* +0 Jive: Would hate to see us responsible for an employee, easier to exit out of a relationship with PCO. Still an employee could line up PCO in region hosting foss4g (as we advise LOC committee to do) while handling community / publicity angle.<br />
* +1 DanielKastl: I wouldn't call it "hire a staff", but pay people to spend a certain amount of time to lead organizing the conference. This doesn't need to be a single person (but could be shared within a small team of 2 or 3 people). The idea is, that there is a knowledge transfer from one year to the next, and that work gets done, that volunteers may not find so motivating (ie. overlook the conference management, acquiring sponsors, boring paper work, report to OSGeo,...). German FOSSGIS is doing this way for their local conference, and I think it works pretty well.<br />
<br />
== Partner with LocationTech==<br />
<br />
===Advantages===<br />
<br />
* LocationTech works in the same space, has contacts, and the Eclipse Foundation already runs conferences<br />
* Retention of knowledge between regions<br />
* Potential for future, deepened partnerships<br />
<br />
===Disadvantages===<br />
<br />
* LocationTech works in the same space, has contacts, and the Eclipse Foundation already runs conferences, so there’s a potential for conflicts of interest<br />
* If it doesn’t work out for whatever reason, future partnership opportunities might be lost<br />
* Potential OSGeo Brand dilution due to obvious prominence of LocationTech taking responsibility. Eg, publicity emails would come from a LocationTech email address.<br />
* Reduction in OSGeo income.<br />
<br />
===Votes/Comments===<br />
* -0 CameronShorter. I think the OSGeo/LocationTech relationship discussions have further to go first. Also concerned about loss of OSGeo income and branding.<br />
* -0 VasileCraciunescu. Mostly because I'm concerned about the dilution of OSGeo brand and values.<br />
* +0 Jive: This is outreach - recommend joint events with a range of open source groups - expect LocationTech is an easy way to get started.<br />
<br />
= References =<br />
* http://wiki.osgeo.org/wiki/FOSS4G<br />
* http://wiki.osgeo.org/wiki/FOSS4G_Handbook<br />
* http://wiki.osgeo.org/wiki/Official_OSGeo_Event_Policy</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=Conference_Options_2014&diff=80285Conference Options 20142014-10-03T00:10:18Z<p>Dkastl: /* Votes/Comments */</p>
<hr />
<div>Future organisation of FOSS4G has been discussed at [http://2014.foss4g.org FOSS4G 2014] then followed onto OSGeo emails lists (Conference, Discuss and Board lists).<br />
<br />
This wiki page aims to collate background information, options, options, and recommendations in order to facilitate making decisions about guiding the future management of FOSS4G events.<br />
<br />
= Editing this wiki =<br />
All are encouraged to add to this wiki. Opinions (rather than facts) should be prefaced with your name:<br />
<br />
[First Last] Comment ...<br />
<br />
= Background =<br />
The international FOSS4G conference has grown from 100-200 attendees when it started 10+ years ago, to ~ 800 attendees now in 2014. Some regional events are also attracting large numbers. Extra attendance leads to extra effort required to coordinate, leading the OSGeo Community to consider options on how to move forward.<br />
<br />
= Options for focus = <br />
The official event policy states an OSGeo event must contribute positively to the [[OSGeo Mission]], which is a) to support the development of open source Geospatial Software, and b) to promote its widespread use.<br />
Focus for any OSGeo can balance between these 2 goals: focussing on the support of the developement probably targets on a smaller well-known inner circle, whereas focussing on promotion of its use aims at a broader audience.<br />
<br />
== Focus on supporting the development of open source geospatial software ==<br />
=== Advantages ===<br />
<br />
* Great venue to promote how open source works and attract new developers<br />
* Foss4g as a "meeting of tribes" promotes cross platform activities<br />
* Attracting new committers is a goal for projects joining a software foundation.<br />
<br />
=== Disadvantages ===<br />
<br />
* Conflict with customer focus (developers attendance often sponsored by their employer)<br />
<br />
== Focus on the promotion of use of open source geospatial software ==<br />
=== Advantages ===<br />
<br />
* Great boost for open source adoption in the hosting region (attendance often draws from nearby countries)<br />
<br />
=== Disadvantages ===<br />
<br />
* Travel hard to justify<br />
<br />
== Consideration of remaining OSGeo goals ==<br />
<br />
FOSS4G touches on all foundation goals:<br />
<br />
* To provide resources for foundation projects - eg. infrastructure, funding, legal.<br />Funds raised by foss4g support OSGeo operation.<br />
<br />
* To promote freely available geodata - free software is useless without data.<br />Topic of interest in the foss4g program.<br />
<br />
* To promote the use of open source software in the geospatial industry (not just foundation software) - eg. PR, training, outreach.<br />Foss4g presentations and workshops are not limited to foundation projects.<br />
<br />
* To encourage the implementation of open standards and standards-based interoperability in foundation projects.<br />Topic of interest in the foss4g program.<br />
<br />
* To ensure a high degree of quality in foundation projects in order to build and preserve the foundation "brand".<br />Handing out OSGeo Live (and the marketing opportunity of foss4g) helps encourage an annual release for foundation projects.<br />
<br />
* To make foundation and related software more accessible to end users - eg. binary "stack" builds, cross package documentation.<br />Workshops and presentations promote accessibility. Cross project presentations (benchmarks) less common - perhaps worth funding.<br />
<br />
* To provide support for the use of OSGeo software in education via curriculum development, outreach, and support.<br />Topic of interest in the foss4g program.<br />
<br />
* To encourage communication and cooperation between OSGeo communities on different language (eg. Java/C/Python) and operating system (eg. Win32, Unix, MacOS) platforms.<br />Foss4g is billed as the "meeting of the tribes" - this has gradually dissolved boundaries leaving a solid focus on spatial rather than language or platform.<br />
<br />
* To support use and contribution to foundation projects from the worldwide community through internationalization of software and community outreach.<br />Foss4g is our largest outreach effort, the selection process encourages the event to be held in a range of locations world wide.<br />
<br />
* To operate an annual OSGeo Conference, possibly in cooperation with related efforts (eg. EOGEO).<br /> Foss4g acts as our annual OSGeo conference. <br />
<br />
* To award the Sol Katz award for service to the OSGeo community.<br />Announced at foss4g.<br />
<br />
= Options for management of FOSS4G =<br />
Following are options which have been identified.<br />
<br />
==Same as before==<br />
For a number of years, the LOCs for large FOSS4G events have hired a new Professional Conference Organiser (PCO). This PCO is usually local and knows the city where the event is being held.<br />
<br />
===Advantages===<br />
* Minimal effort (for the board) to set up.<br />
* A local PCO likely has local experience.<br />
<br />
===Disadvantages===<br />
* Loss of knowledge between events and associated risk of failure.<br />
* Significant stress put on LOCs.<br />
<br />
===Votes/Comments===<br />
* -0 CameronShorter<br />
* -1 Darrell: This model simply doesn't scale. The idea that local knowledge is required for the PCO position is, quite simply, false. (I find it amazing that we can operate a global organization on a small budget, but are unable to conceive that others are also able to.)<br />
* -1 Jive: If we want foss4g then this model does not scale, if we were more flexible we could end up with a different flavour each annual conference<br />
* -0 DanielKastl: Pretty much every year some local community has to reinvent the wheel, setup a new infrastructure for website, payment, etc.. IMO it's currently done not very efficient.<br />
<br />
==Engage a long term (for profit) PCO==<br />
<br />
===Advantages===<br />
* Institutional knowledge. The conference knowledge carries on in the organisation, and is hopefully not entirely imbued in one person. <br />
* Simplicity.<br />
<br />
===Disadvantages===<br />
* How would an OSGeo exit out of the arrangement with the PCO if the relationship sours?<br />
* It is in the vested interests of a PCO not to share information with community, such that we become reliant upon the PCO.<br />
<br />
===Votes/Comments===<br />
* -0 CameronShorter. I'm nervous about an exit strategy if things go sour.<br />
* +1 Darrell. It's simple, the contract is renewable on an annual basis. If either party isn't happy with the arrangement, it can be ended. Put into the contract what knowledge is to be shared and how.<br />
* -0 Jive: Risk is a subject for contract negotiation<br />
* +0 DanielKastl: It's better than looking for a new PCO every year, so if there is a good candidate this might not require much work for OSGeo. I just doubt that it's easy to find a suitable PCO.<br />
<br />
== Hire a staff person to be the organiser ==<br />
<br />
This is more risk, but also offers more potential.<br />
<br />
[[Jeff McKenna]] proposed this option formally to the OSGeo Board in 2011. A full job description and rates are outlined on the wiki page: [[FOSS4G Advisor Role]]<br />
<br />
===Advantages:===<br />
<br />
* Having a staff person allows OSGeo to be more flexible in organising conferences. Is there a budding regional conference that needs some assistance? We can help with that. Would OSGeo like to foster growth in regions without a local FOSS4G event? OSGeo can do that.<br />
<br />
===Disadvantages===<br />
<br />
* You would only have one staff person, which means more risk of losing institutional knowledge if that person leaves.<br />
* Potential for being seen as less of a a volunteer led organisation. <br />
* Hiring is hard, and takes time, especially to find a good autonomous person to take on this role<br />
<br />
===Votes/Comments===<br />
* +0 CameronShorter<br />
* +0 Darrell: I think this is a good idea, if and only if OSGeo has a clear vision of how they want the organization and the role to grow. Right now, I don't see that they do.<br />
* +0 Jive: Would hate to see us responsible for an employee, easier to exit out of a relationship with PCO. Still an employee could line up PCO in region hosting foss4g (as we advise LOC committee to do) while handling community / publicity angle.<br />
<br />
== Partner with LocationTech==<br />
<br />
===Advantages===<br />
<br />
* LocationTech works in the same space, has contacts, and the Eclipse Foundation already runs conferences<br />
* Retention of knowledge between regions<br />
* Potential for future, deepened partnerships<br />
<br />
===Disadvantages===<br />
<br />
* LocationTech works in the same space, has contacts, and the Eclipse Foundation already runs conferences, so there’s a potential for conflicts of interest<br />
* If it doesn’t work out for whatever reason, future partnership opportunities might be lost<br />
* Potential OSGeo Brand dilution due to obvious prominence of LocationTech taking responsibility. Eg, publicity emails would come from a LocationTech email address.<br />
* Reduction in OSGeo income.<br />
<br />
===Votes/Comments===<br />
* -0 CameronShorter. I think the OSGeo/LocationTech relationship discussions have further to go first. Also concerned about loss of OSGeo income and branding.<br />
* -0 VasileCraciunescu. Mostly because I'm concerned about the dilution of OSGeo brand and values.<br />
* +0 Jive: This is outreach - recommend joint events with a range of open source groups - expect LocationTech is an easy way to get started.<br />
<br />
= References =<br />
* http://wiki.osgeo.org/wiki/FOSS4G<br />
* http://wiki.osgeo.org/wiki/FOSS4G_Handbook<br />
* http://wiki.osgeo.org/wiki/Official_OSGeo_Event_Policy</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=Conference_Options_2014&diff=80284Conference Options 20142014-10-03T00:07:57Z<p>Dkastl: /* Votes/Comments */</p>
<hr />
<div>Future organisation of FOSS4G has been discussed at [http://2014.foss4g.org FOSS4G 2014] then followed onto OSGeo emails lists (Conference, Discuss and Board lists).<br />
<br />
This wiki page aims to collate background information, options, options, and recommendations in order to facilitate making decisions about guiding the future management of FOSS4G events.<br />
<br />
= Editing this wiki =<br />
All are encouraged to add to this wiki. Opinions (rather than facts) should be prefaced with your name:<br />
<br />
[First Last] Comment ...<br />
<br />
= Background =<br />
The international FOSS4G conference has grown from 100-200 attendees when it started 10+ years ago, to ~ 800 attendees now in 2014. Some regional events are also attracting large numbers. Extra attendance leads to extra effort required to coordinate, leading the OSGeo Community to consider options on how to move forward.<br />
<br />
= Options for focus = <br />
The official event policy states an OSGeo event must contribute positively to the [[OSGeo Mission]], which is a) to support the development of open source Geospatial Software, and b) to promote its widespread use.<br />
Focus for any OSGeo can balance between these 2 goals: focussing on the support of the developement probably targets on a smaller well-known inner circle, whereas focussing on promotion of its use aims at a broader audience.<br />
<br />
== Focus on supporting the development of open source geospatial software ==<br />
=== Advantages ===<br />
<br />
* Great venue to promote how open source works and attract new developers<br />
* Foss4g as a "meeting of tribes" promotes cross platform activities<br />
* Attracting new committers is a goal for projects joining a software foundation.<br />
<br />
=== Disadvantages ===<br />
<br />
* Conflict with customer focus (developers attendance often sponsored by their employer)<br />
<br />
== Focus on the promotion of use of open source geospatial software ==<br />
=== Advantages ===<br />
<br />
* Great boost for open source adoption in the hosting region (attendance often draws from nearby countries)<br />
<br />
=== Disadvantages ===<br />
<br />
* Travel hard to justify<br />
<br />
== Consideration of remaining OSGeo goals ==<br />
<br />
FOSS4G touches on all foundation goals:<br />
<br />
* To provide resources for foundation projects - eg. infrastructure, funding, legal.<br />Funds raised by foss4g support OSGeo operation.<br />
<br />
* To promote freely available geodata - free software is useless without data.<br />Topic of interest in the foss4g program.<br />
<br />
* To promote the use of open source software in the geospatial industry (not just foundation software) - eg. PR, training, outreach.<br />Foss4g presentations and workshops are not limited to foundation projects.<br />
<br />
* To encourage the implementation of open standards and standards-based interoperability in foundation projects.<br />Topic of interest in the foss4g program.<br />
<br />
* To ensure a high degree of quality in foundation projects in order to build and preserve the foundation "brand".<br />Handing out OSGeo Live (and the marketing opportunity of foss4g) helps encourage an annual release for foundation projects.<br />
<br />
* To make foundation and related software more accessible to end users - eg. binary "stack" builds, cross package documentation.<br />Workshops and presentations promote accessibility. Cross project presentations (benchmarks) less common - perhaps worth funding.<br />
<br />
* To provide support for the use of OSGeo software in education via curriculum development, outreach, and support.<br />Topic of interest in the foss4g program.<br />
<br />
* To encourage communication and cooperation between OSGeo communities on different language (eg. Java/C/Python) and operating system (eg. Win32, Unix, MacOS) platforms.<br />Foss4g is billed as the "meeting of the tribes" - this has gradually dissolved boundaries leaving a solid focus on spatial rather than language or platform.<br />
<br />
* To support use and contribution to foundation projects from the worldwide community through internationalization of software and community outreach.<br />Foss4g is our largest outreach effort, the selection process encourages the event to be held in a range of locations world wide.<br />
<br />
* To operate an annual OSGeo Conference, possibly in cooperation with related efforts (eg. EOGEO).<br /> Foss4g acts as our annual OSGeo conference. <br />
<br />
* To award the Sol Katz award for service to the OSGeo community.<br />Announced at foss4g.<br />
<br />
= Options for management of FOSS4G =<br />
Following are options which have been identified.<br />
<br />
==Same as before==<br />
For a number of years, the LOCs for large FOSS4G events have hired a new Professional Conference Organiser (PCO). This PCO is usually local and knows the city where the event is being held.<br />
<br />
===Advantages===<br />
* Minimal effort (for the board) to set up.<br />
* A local PCO likely has local experience.<br />
<br />
===Disadvantages===<br />
* Loss of knowledge between events and associated risk of failure.<br />
* Significant stress put on LOCs.<br />
<br />
===Votes/Comments===<br />
* -0 CameronShorter<br />
* -1 Darrell: This model simply doesn't scale. The idea that local knowledge is required for the PCO position is, quite simply, false. (I find it amazing that we can operate a global organization on a small budget, but are unable to conceive that others are also able to.)<br />
* -1 Jive: If we want foss4g then this model does not scale, if we were more flexible we could end up with a different flavour each annual conference<br />
* -0 DanielKastl: Pretty much every year some local community has to reinvent the wheel, setup a new infrastructure for website, payment, etc.. IMO it's currently done not very efficient.<br />
<br />
==Engage a long term (for profit) PCO==<br />
<br />
===Advantages===<br />
* Institutional knowledge. The conference knowledge carries on in the organisation, and is hopefully not entirely imbued in one person. <br />
* Simplicity.<br />
<br />
===Disadvantages===<br />
* How would an OSGeo exit out of the arrangement with the PCO if the relationship sours?<br />
* It is in the vested interests of a PCO not to share information with community, such that we become reliant upon the PCO.<br />
<br />
===Votes/Comments===<br />
* -0 CameronShorter. I'm nervous about an exit strategy if things go sour.<br />
* +1 Darrell. It's simple, the contract is renewable on an annual basis. If either party isn't happy with the arrangement, it can be ended. Put into the contract what knowledge is to be shared and how.<br />
* -0 Jive: Risk is a subject for contract negotiation<br />
<br />
== Hire a staff person to be the organiser ==<br />
<br />
This is more risk, but also offers more potential.<br />
<br />
[[Jeff McKenna]] proposed this option formally to the OSGeo Board in 2011. A full job description and rates are outlined on the wiki page: [[FOSS4G Advisor Role]]<br />
<br />
===Advantages:===<br />
<br />
* Having a staff person allows OSGeo to be more flexible in organising conferences. Is there a budding regional conference that needs some assistance? We can help with that. Would OSGeo like to foster growth in regions without a local FOSS4G event? OSGeo can do that.<br />
<br />
===Disadvantages===<br />
<br />
* You would only have one staff person, which means more risk of losing institutional knowledge if that person leaves.<br />
* Potential for being seen as less of a a volunteer led organisation. <br />
* Hiring is hard, and takes time, especially to find a good autonomous person to take on this role<br />
<br />
===Votes/Comments===<br />
* +0 CameronShorter<br />
* +0 Darrell: I think this is a good idea, if and only if OSGeo has a clear vision of how they want the organization and the role to grow. Right now, I don't see that they do.<br />
* +0 Jive: Would hate to see us responsible for an employee, easier to exit out of a relationship with PCO. Still an employee could line up PCO in region hosting foss4g (as we advise LOC committee to do) while handling community / publicity angle.<br />
<br />
== Partner with LocationTech==<br />
<br />
===Advantages===<br />
<br />
* LocationTech works in the same space, has contacts, and the Eclipse Foundation already runs conferences<br />
* Retention of knowledge between regions<br />
* Potential for future, deepened partnerships<br />
<br />
===Disadvantages===<br />
<br />
* LocationTech works in the same space, has contacts, and the Eclipse Foundation already runs conferences, so there’s a potential for conflicts of interest<br />
* If it doesn’t work out for whatever reason, future partnership opportunities might be lost<br />
* Potential OSGeo Brand dilution due to obvious prominence of LocationTech taking responsibility. Eg, publicity emails would come from a LocationTech email address.<br />
* Reduction in OSGeo income.<br />
<br />
===Votes/Comments===<br />
* -0 CameronShorter. I think the OSGeo/LocationTech relationship discussions have further to go first. Also concerned about loss of OSGeo income and branding.<br />
* -0 VasileCraciunescu. Mostly because I'm concerned about the dilution of OSGeo brand and values.<br />
* +0 Jive: This is outreach - recommend joint events with a range of open source groups - expect LocationTech is an easy way to get started.<br />
<br />
= References =<br />
* http://wiki.osgeo.org/wiki/FOSS4G<br />
* http://wiki.osgeo.org/wiki/FOSS4G_Handbook<br />
* http://wiki.osgeo.org/wiki/Official_OSGeo_Event_Policy</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=FOSS4G-Europe_2014_workshops&diff=78457FOSS4G-Europe 2014 workshops2014-07-12T13:12:34Z<p>Dkastl: /* FOSS4G routing with pgRouting, OpenStreetMap road data and OpenLayers */</p>
<hr />
<div>== Workshops &amp; Tutorials ==<br />
<br />
Workshops are 3 hours practical course where users are expected to execute exercises on the topic/application(s) under discussion.<br />
Tutorials are 1.5 hours presentation where participants are expected to get a guided tour into the topic/application(s) under discussion.<br />
<br />
<br />
== Where &amp; When ==<br />
<br />
The day before of the main conference (Monday 14th July) has been set aside for the Workshops.<br />
For timetable see [http://foss4g-e.org/workshops-0]<br />
<br />
== PARTICIPANTS ==<br />
<br />
'''Very important: Participants will have to bring their own laptop since at the venue is not available any PC room.'''<br />
<br />
please refer to the following section to identify:<br />
* requirements (hardware and software)<br />
* preparation steps to attend (e.g. installation, etc..)<br />
* link to external resources<br />
<br />
== FOSS4G routing with pgRouting, OpenStreetMap road data and OpenLayers ==<br />
<br />
To be able to actively participate in this workshop, please prepare the following:<br />
<br />
# Bring your own notebook<br />
# Download and install [https://www.virtualbox.org VirtualBox]<br />
# Download the [http://live.osgeo.org/en/download.html Virtual Machine Image] of OSGeo-Live<br />
# [http://live.osgeo.org/en/quickstart/virtualization_quickstart.html Run OSGeo-Live in VirtualBox]<br />
# Select the correct [http://live.osgeo.org/en/quickstart/internationalisation_quickstart.html keyboard layout]<br />
<br />
If you're not familiar with Ubuntu Linux, it's now a good time to try out [http://live.osgeo.org/en/overview/overview.html OSGeo-Live] ;-)<br />
<br />
There will be a limited number of bootable USB Sticks containing OSGeo Live, but with the VirtualBox setup you will experience better performance.<br />
<br />
== Spatio-Temporal Big Data - the EarthServer approach ==<br />
<br />
== Web mapping with OGC services and GeoServer: an introduction ==<br />
<br />
The workshop will require a PC equipped with at least 2 cores and<br />
4GB or memory (8GB better) with VMWare (Player or Workstation) or<br />
Virtualbox and 20GB of free space to host the virtual machine that will run<br />
the training.<br />
<br />
The images can be downloaded from here:<br />
http://84.33.199.62/download/GeoServerWorkshop3h/<br />
<br />
Instructions on which files to download, and how to use them with<br />
VMWare and VirtualBox are provided here:<br />
http://84.33.199.62/download/GeoServerWorkshop3h/readme.txt<br />
<br />
During the worskhop some USBs will be shared with the participants that<br />
have not downloaded the material in advance too, but we strongly<br />
advise to download the material in advance if possible.<br />
<br />
== Introduction to rasdaman ==<br />
<br />
== Using R as a command line GIS ==<br />
<br />
Most people know R is a powerful, fast and free package for data analysis. Recently, it has also developed some cutting edge GIS capabilities.<br />
<br />
R is a command line GIS, so can seem 'scary' to new-comers. This tutorial is therefore introductory - for people who have some experience with R or another language but little knowledge of its amazing spatial capabilities.<br />
<br />
This workshop is based on a tutorial by Lovelace and Cheshire (2014) aimed at introducing R in an accessible way.<br />
<br />
'''Requirements:''' A laptop with a recent version of R and preferably RStudio installed. <br />
<br />
'''Preparation steps:''' Install and play with R if you have not already.<br />
<br />
'''Links to external resources:'''<br />
<br />
Lovelace, R., & Cheshire, J. (2014). Introduction to visualising spatial data in R. The Comprehensive R Archive Network. http://cran.r-project.org/doc/contrib/intro-spatial-rl.pdf<br />
<br />
Torfs and Brauer (2012). A (very) short Introduction to R. The Comprehensive R Archive Network. http://cran.r-project.org/doc/contrib/Torfs+Brauer-Short-R-Intro.pdf<br />
<br />
== Geo Reports ==<br />
<br />
<br />
Welcome to the GeoReports Tutorial.<br />
''<br />
GeoReports Tutorial – a tutorial with warranty – author guarantees the accuracy and correctness of tutorial, all the actions mentioned in the tutorial can be reproduced in accurate manner if you follow tutorial instructions..''<br />
<br />
This tutorial will show how to produce reports with maps using today’s world leading free and open source software for web mapping and reports, GeoServer and JasperReport, respectively.<br />
<br />
It is primary intended as a syllabus for GeoReports workshop and not as comprehensive guide for geo-reports cook book. Indeed source code provided in this tutorial can be used for creating a geo-reports.<br />
<br />
Tutorial will go trough a series of steps increasing a level of complexity with various integration options: from comand line application setup, over web application to GeoServer extension – embedded reporting application delivered over OGC (Open Geospatial Consortium) WPS (Web Processing Service). For a more user friendly approach, Geoserver extension – named DigMap – will be wrapped in Boundless OpenGeo Suite.<br />
<br />
Enjoy reading http://digmap.wordpress.com/georeport !<br />
<br />
'''If you would like to get free testing virtual private server (VPS) for following GeoReports tutorial and make a preparation according to tutorial setup (http://digmap.wordpress.com/georeport/installation/) please send a mail to Krunoslav@yottabyte.HR Setting up your working environment will enable you to easily keep track with tutorial. The author, Krunoslav, will be happy to help if you encounter difficulties during installation.'''<br />
<br />
== Easily manage and dispatch your sensor data with istSOS & ENORASIS ==<br />
<br />
'''Workshop contents:'''<br />
Concepts:<br />
* introduction to the ENORASIS project [ http://www.enorasis.eu ]<br />
* understanding the SOS standard<br />
* understanding istSOS UI<br />
* understanding istSOS RESTful API<br />
'''Hands-on:'''<br />
* Introduction to the standard and to istSOS<br />
* installation of the software<br />
* set-up of the service<br />
* registering new sensors<br />
* inserting observations<br />
* validation of observations (qualityIndex)<br />
* manipulating observations (load, edit, delete)<br />
* create virtual sensors (virtual procedures)<br />
* dynamic aggregation<br />
* istSOS RESTful API<br />
* mapping sensors and data with OpenLayers 3<br />
* plotting observations on the Web<br />
* analyze data for irrigation<br />
<br />
'''Workshop preparation:'''<br />
* bring your laptop<br />
* possibly, use a Linux/Debian system (native, virtual environment, in live USB)<br />
** Ubuntu VirtuaBox images: [ http://virtualboxes.org/images/ubuntu/ ], instructions: [ http://virtualboxes.org/doc/ ]<br />
** OSGeoLive USB [ http://live.osgeo.org/it/quickstart/usb_quickstart.html ] - MAC PCs DON'T BOOT FROM USB, USE VBOX IMAGE !!!<br />
<br />
== Analyzing spatial data with GRASS GIS 7 ==<br />
<br />
== PyWPS tutorial ==<br />
<br />
<br />
'''Workshop contents:'''<br />
* introduction and explanation ofWPS<br />
* instalation of pywps <br />
* basic process creation<br />
<br />
<br />
'''Workshop preparation:'''<br />
* OSGeoLive VirtualBox image<br />
* Or computer with python and apache<br />
<br />
== Building Standards Compliant Geospatial Web Application - The Quick and Easy MapMint Way ==<br />
<br />
For beeing able to run the workshop, we would require the following from attendees:<br />
<br />
* a computer with internet connection (simply to avoid pink tiles for base layers) and a free usb slot to plug the USB Stick in it (if USB 3.0 is available, it can make the experience better)<br />
* VirtualBox setup on the computer<br />
<br />
We will come with 30 MapMint USB sticks containing the required iso image for the workshop (note that the iso image is also available [https://sourceforge.net/projects/mapmintvm/files/iso-1.0.0-rc6/ here]).</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=FOSS4G-Europe_2014_workshops&diff=78306FOSS4G-Europe 2014 workshops2014-06-30T09:05:54Z<p>Dkastl: /* FOSS4G routing with pgRouting, OpenStreetMap road data and OpenLayers */</p>
<hr />
<div>== Workshops &amp; Tutorials ==<br />
<br />
Workshops are 3 hours practical course where users are expected to execute exercises on the topic/application(s) under discussion.<br />
Tutorials are 1.5 hours presentation where participants are expected to get a guided tour into the topic/application(s) under discussion.<br />
<br />
<br />
== Where &amp; When ==<br />
<br />
The day before of the main conference (Monday 14th July) has been set aside for the Workshops.<br />
For timetable see [http://foss4g-e.org/workshops-0]<br />
<br />
== PARTICIPANTS ==<br />
<br />
'''Very important: Participants will have to bring their own laptop since at the venue is not available any PC room.'''<br />
<br />
please refer to the following section to identify:<br />
* requirements (hardware and software)<br />
* preparation steps to attend (e.g. installation, etc..)<br />
* link to external resources<br />
<br />
== FOSS4G routing with pgRouting, OpenStreetMap road data and OpenLayers ==<br />
<br />
To be able to actively participate in this workshop, please prepare the following:<br />
<br />
# Bring your own notebook<br />
# Download and install [https://www.virtualbox.org VirtualBox]<br />
# Download the [http://live.osgeo.org/en/download.html Virtual Machine Image] of OSGeo-Live<br />
# [http://live.osgeo.org/en/quickstart/virtualization_quickstart.html Run OSGeo-Live in VirtualBox]<br />
# Select the correct [http://live.osgeo.org/en/quickstart/internationalisation_quickstart.html keyboard layout]<br />
<br />
If you're not familiar with Ubuntu Linux, it's now a good time to try out [http://live.osgeo.org/en/overview/overview.html OSGeo-Live] ;-)<br />
<br />
== Spatio-Temporal Big Data - the EarthServer approach ==<br />
<br />
== Web mapping with OGC services and GeoServer: an introduction ==<br />
<br />
== Introduction to rasdaman ==<br />
<br />
== Using R as a command line GIS ==<br />
<br />
== Geo Reports ==<br />
<br />
== Easily manage and dispatch your sensor data with istSOS ==<br />
<br />
== Analyzing spatial data with GRASS GIS 7 ==<br />
<br />
== Building Standards Compliant Geospatial Web Application - The Quick and Easy MapMint Way ==</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=User:Danielkastl&diff=77295User:Danielkastl2014-03-15T05:48:58Z<p>Dkastl: /* Daniel Kastl */</p>
<hr />
<div>===Daniel Kastl===<br />
<br />
[[File:OSGeo_compass300.png|thumb|right|100px|Daniel Kastl]]<br />
<br />
Owner, [http://georepublic.info Georepublic] Germany & Japan<br />
<br />
Location(s): Osaka, Japan or Munich, Germany<br />
<!--(-33.744 S, 18.989 E){{#umSetParam: 18.989|-33.744|Paarl|Gfleming|Gavin Fleming}}<br />
{{#umAdmin: Gfleming}} {{#umUserMap: Gfleming}}--><br />
<br />
Daniel is a geographer, software developer, founder of Georepublic and Free Software advocate. <br />
<br />
;OSGeo Experience [[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]][[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]][[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]][[File:OSGeo_translate.png|link=OSGeo_Advocate#OSGeo_Community_Members]]<br />
<br />
:* pgRouting Project Steering Committee member<br />
:* Mentor for Google Summer of Code<br />
:* OSGeo Charter Member<br />
<br />
;Contact:<br />
: Email: daniel (A T) georepublic.co.jp<br />
: Phone: +49 (089) 4161 7698-1<br />
: [http://www.linkedin.com/in/dkastl LinkedIn] and [https://twitter.com/dkastl Twitter]<br />
<br />
;Spoken Language(s): German, English, Japanese<br />
<br />
;Profile last updated: 15 March 2014<br />
<br />
[[Category:OSGeo Member]]<br />
[[Category:OSGeo Charter Member]]<br />
[[Category:Germany]]<br />
[[Category:Japan]]<br />
{{#umSetParam: 135.373535|34.583475|Osaka, Japan|Danielkastl|Daniel Kastl}}</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=User:Danielkastl&diff=77294User:Danielkastl2014-03-15T05:44:07Z<p>Dkastl: /* Daniel Kastl */</p>
<hr />
<div>===Daniel Kastl===<br />
<br />
[[File:OSGeo_compass300.png|thumb|right|100px|Daniel Kastl]]<br />
<br />
Owner, [http://georepublic.info Georepublic] Germany & Japan<br />
<br />
Location(s): Osaka, Japan or Munich, Germany<br />
<!--(-33.744 S, 18.989 E){{#umSetParam: 18.989|-33.744|Paarl|Gfleming|Gavin Fleming}}<br />
{{#umAdmin: Gfleming}} {{#umUserMap: Gfleming}}--><br />
<br />
Daniel is a geographer, software developer, founder of Georepublic and Free Software advocate. <br />
<br />
;OSGeo Experience [[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]][[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]][[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]][[File:OSGeo_translate.png|link=OSGeo_Advocate#OSGeo_Community_Members]]<br />
<br />
:* pgRouting Project Steering Committee member<br />
:* Mentor for Google Summer of Code<br />
:* OSGeo Charter Member<br />
<br />
;Contact:<br />
: Email: daniel (A T) georepublic.co.jp<br />
: Phone: +49 (089) 4161 7698-1<br />
: [http://www.linkedin.com/in/dkastl LinkedIn] and [https://twitter.com/dkastl Twitter]<br />
<br />
;Spoken Language(s): German, English, Japanese<br />
<br />
;Profile last updated: 15 March 2014<br />
<br />
[[Category:OSGeo Member]]<br />
[[Category:Japan]]<br />
{{#umSetParam: 135.373535|34.583475|Osaka, Japan|Danielkastl|Daniel Kastl}}</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=OSGeo_Advocate&diff=77293OSGeo Advocate2014-03-15T05:38:45Z<p>Dkastl: /* Asia:Japan */</p>
<hr />
<div>__FORCETOC__<br />
<br />
= Introduction =<br />
<br />
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.<br />
<br />
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.<br />
<br />
= Advocates =<br />
<br />
== Advocate Map ==<br />
<br />
<!-- {{#umAllUserMap: width|height|zoom|centerat|baselayer|navbar}} --><br />
{{#umAllUserMap:}}<br />
<br />
== Africa:Ghana ==<br />
{{User:Eyedol}}<br />
<br />
== Africa:South Africa ==<br />
=== Gavin Fleming ===<br />
{{User:Gfleming}}<br />
{{User:Sokolic}}<br />
{{User:Timlinux}}<br />
<br />
== Asia:India ==<br />
{{User:ravivundavalli}}<br />
<br />
== Asia:Japan ==<br />
{{User:Yoichi}}<br />
{{User:danielkastl}}<br />
<br />
===[http://cse.niaes.affrc.go.jp/niwasaki/ Nobusuke Iwasaki]===<br />
<br />
[[File:Iwasaki.jpg|thumb|right|100px|Nobusuke Iwasaki]]<br />
<br />
Senior Researcher, [http://www.niaes.affrc.go.jp/index_e.html National Institute for Agro-Environmental Sciences]<br />
<br />
Location: Tsukuba, Japan<br />
<br />
Nobusuke Iwasaki is researcher of land use change and rural planning and extensively using FOSS4G. Also, he is one of the main organizers of FOSS4G-Japan event and proactively commits promotion and dissemination of FOSS4G, especially academic sector. He strongly contributes [http://www.osgeo.jp/foss4g-mext/ some academic project which aims utilization of satellite image and FOSS4G for beginners and non-specialist user]. <br />
The major his product is [http://habs.dc.affrc.go.jp Historical Agro-Environmental Browsing System (HABS)], which is commended [http://psgsv2.gsi.go.jp/koukyou/G-award/list_award1.html the first Cyber Japan Award].<br />
<br />
;OSGeo Experience [[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]]:<br />
:* [http://www.osgeo.jp/ OSGeo Japan Chapter] Board member since 2008<br />
:* member of [http://www.gisa-japan.org/ GIS Assosiation of JAPAN] <br />
:* member of [https://sites.google.com/site/foss4gsig/ FOSS4G special interest group] in GIS Assosiation of JAPAN<br />
<br />
;Contact:<br />
: Email: wata909 AT gmail DOT com<br />
: Skype: wata909<br />
<br />
;Profile last updated<br />
:2013-07-11<br />
<br />
== Asia:Korea ==<br />
{{User:Sanghee}}<br />
<br />
==Asia:Philippines==<br />
{{User:Maning}}<br />
<br />
== Asia:Malaysia ==<br />
{{User:Thuygeo}}<br />
<br />
== Australia ==<br />
{{User:camerons}}<br />
{{User:NathanW}}<br />
{{User:jive}}<br />
<br />
== Canada ==<br />
{{User:Dmorissette}}<br />
{{User:Aross}}<br />
{{User:Gzeiss}}<br />
{{User:Mdavis}}<br />
{{User:Pwramsey3}}<br />
<br />
<br />
== Europe:Czech Republic ==<br />
{{User:Jachym}}<br />
{{User:KarelCharvat}}<br />
<br />
== Europe:France ==<br />
{{User:Djay}}<br />
{{User:JRM}}<br />
{{User:grizonnetm}}<br />
{{User:NBozon}}<br />
{{User:volaya}}<br />
<br />
=== [[User:Djay|Gérald Fenoy]] ===<br />
[[Image:Gérald Fenoy.jpg|thumb|right|100px]]<br />
<br />
Founder and CEO of [http://www.geolabs.fr GeoLabs SARL].<br />
<br />
Location: Lattes, France.<br />
<br />
;OSGeo Experience [[File:OSGeo_board.png|link=OSGeo_Advocate#OSGeo Board Members]] [[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]][[File:OSGeo_psc.png|link=OSGeo_Advocate#Voted_position_in_an_OSGeo_community]][[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]] [[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]] [[File:OSGeo_translate.png|link=OSGeo_Advocate#OSGeo_Community_Members]]<br />
<br />
* [http://www.zoo-project.org ZOO-Project] Developper and PSC Chair,<br />
* Creator of the original [http://www.postgis.fr french web site for PostGIS], <br />
* Provide training, use and develop (WEB-)GIS applications based on OSGeo Libraries / Applications,<br />
* Active in the [http://wiki.osgeo.org/wiki/Senegalease OSGeo Senegal Local chapter],<br />
* Provide Gentoo packaging and patches for proj, geos, postgis, pgRouting, mapserver and gpsbabel,<br />
* Active at all FOSS4G international events since 2006.<br />
<br />
;Contacts<br />
<!-- {{#umSetParam: 3.921261|43.585592|Lattes, France|Djay|Gérald Fenoy}}<br />
{{#umUserMap: Djay|400px|250px|6|2|y}} --><br />
: Phone: +33670082539<br />
: Skype: gfenoy<br />
: Mail: gerald DOT fenoy AT geolabs DOT fr<br />
: IRC: djay<br />
<br />
[[Category:OSGeo Charter Member]]<br />
[[Category:OSGeo Member]]<br />
<br />
=== Nicolas Bozon ===<br />
[[Image:nicolas_bozon.png|thumb|right|100px|Nick at Abikocho station]]<br />
Principle, [http://www.cartogenic.com Cartogenic].<br />
<br />
Nicolas Bozon is an open source enthusiast and specializes in designing user interfaces and experiences for mapping and web applications. Nicolas runs [http://www.cartogenic.com Cartogenic], a geospatial consutling company located in Lyon, France. He is also a researcher in geomatics and environmental sciences, and currently pursues a post-doctoral fellowship in Osaka, Japan.<br />
<br />
;OSGeo Experience [[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]] [[File:OSGeo_committee.png|link=OSGeo_Advocate#Developers_and_Committee_Members]] [[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]]<br />
<br />
* Co-founder and PSC member of [http://zoo-project.org ZOO-Project], the Open WPS platform<br />
* [http://www.osgeo.org/charter_members Charter Member] of OSGeo<br />
* Member of the [http://wiki.osgeo.org/wiki/Marketing_Committee Marketing Committee] of OSGeo<br />
<br />
;Academics<br />
* Post-doc fellowship (JP, 2011/2013)<br />
* PhD Maths/GIS (FR, 2006/2009)<br />
* Master GIS (FR, 2005)<br />
* Undergraduate Env Sc (QC, 2002/2004)<br />
* Undergraduate Geo (FR, 2000/2002)<br />
<br />
;Contact<br />
:Email: nicolas dot bozon at gmail dot com<br />
:[http://www.linkedin.com/in/nbozon Linkedin profile ]<br />
:Skype: nicboz1<br />
:IRC: nbozon<br />
<br />
{{#umSetParam: 4.856216|45.770527|Lyon, France|Nbozon|Nicolas Bozon}}<br />
<!-- {{#umUserMap: Nbozon|600px|300px|6|2|y}} --><br />
[[Category:OSGeo Member]]<br />
[[Category:OSGeo Charter Member]]<br />
<br />
== Europe:Germany ==<br />
{{User:Arnulf Christl}}<br />
{{User:Pebau}}<br />
{{User:Astrid_Emde}}<br />
{{User:Aghisla}}<br />
{{User:misev}}<br />
{{User:Stefan_A._Tzeggai}}<br />
{{User:Thomas_Baschetti}}<br />
<br />
== Europe:Greece ==<br />
{{User:Kalxas}}<br />
{{User:ArArgyridis}}<br />
{{User:kotzino}}<br />
{{User:Nikos}}<br />
<br />
== Europe:Italy ==<br />
{{User:Madi}}<br />
{{User:Lucadelu}}<br />
{{User:Aaime}}<br />
{{User:Maxi71}}<br />
{{User:epifanio}}<br />
{{User:Moovida}}<br />
{{Talk:Markus_Neteler}}<br />
<br />
== Europe:The Netherlands ==<br />
{{User:Ticheler}}<br />
{{User:BarendKobben}}<br />
{{User:Just}}<br />
{{User:bartvde}}<br />
{{User:Milovanderlinden}}<br />
{{User:Genuchten}}<br />
<br />
== Europe:Portugal==<br />
{{User:Lutra}}<br />
<br />
== Europe:Romania ==<br />
{{User:Vasile}}<br />
<br />
== Europe:Spain ==<br />
{{User:Lluís}}<br />
{{User:vehrka}}<br />
{{User:Michogar}}<br />
{{User:Delawen}}<br />
{{User:Adiez}}<br />
{{User:Jsanz}}<br />
<br />
<br />
== Europe:Switzerland ==<br />
{{User:Mbernasocchi}}<br />
== Europe:United Kingdom ==<br />
{{User:Ian}}<br />
{{User:JoCook}}<br />
{{User:Ianturton}}<br />
{{User:Stevenfeldman}}<br />
{{User:Sanand}}<br />
<br />
== Latin America:Argentina ==<br />
{{User:Maurimiranda}}<br />
<br />
== Latin America:Brazil ==<br />
{{User:Fsc7}}<br />
<br />
== Latin America:Chile ==<br />
{{User:Perriger}}<br />
<br />
== Latin America: Colombia ==<br />
{{User:Eamado}}<br />
<br />
== Latin America:Mexico ==<br />
{{User:Aborrell}}<br />
<br />
== United States ==<br />
{{User:EliL}}<br />
{{User:Alex Mandel}}<br />
{{User:Brian Hamlin}}<br />
{{User:Dnewcomb}}<br />
{{User:Amyonthemap}}<br />
{{User:warmerda}}<br />
{{User:Helena}}<br />
{{User:Surveyor}}<br />
{{User:Mark Lucas}}<br />
{{User:msmitherdc}}<br />
{{User:mpg}}<br />
{{User:pmbatty}}<br />
{{User:Rburhum}}<br />
{{User:Sdlime}}<br />
{{User:Woodbri}}<br />
<br />
<br />
=== [http://www.redefinedhorizons.com/printingpress/landon-blakes-bio/ Landon Blake] (AKA - The Sunburned Surveyor) ===<br />
<br />
[[File:landon_blake_portrait.jpg|100px|thumb|right|Landon Blake]]<br />
<br />
Owner, [http://www.redefinedhorizons.com Redefined Horizons]<br />
<br />
Location: Stockton, California, United States of America<br />
<br />
Landon Blake is a land surveyor and GIS programmer with a focus on OpenJUMP and CAD customization. <br />
<br />
* Web Page: [http://www.redefinedhorizons.com]<br />
* Blog: [http://www.redefinedhorizonsblog.com]<br />
* Twitter: [https://twitter.com/mapit4u]<br />
* LinkedIn: [http://www.linkedin.com/in/landonblake]<br />
<br />
;OSGeo Experience<br />
* Volunteer Editor of the OSGeo Journal<br />
* Board Representative for the OSGeo California Chapter<br />
<br />
;Contact:<br />
: Email: sunburned dot surveyor at gmail dot com<br />
: Phone (Home): 209-464-2612<br />
: Phone (Cell): 209-298-7521<br />
: Skype: <br />
<br />
;Profile last updated: 07 14 2013<br />
<br />
= Past OSGeo Advocates =<br />
This section lists prior listed Advocates who have not recently updated their profiles.<br />
<br />
= Understanding OSGeo roles =<br />
<br />
Below is an explanation of roles which Advocates might have been involved in as part of OSGeo:<br />
<br />
====[[File:OSGeo_board.png]] [[File:OSGeo_exboard.png]] OSGeo Board Members====<br />
: We only have 9 active OSGeo board members in the world, which have been peer selected based upon their outstanding leadership in the greater OSGeo community.<br />
<br />
====[[File:OSGeo_charter.png]] OSGeo Charter Members====<br />
: 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.<br />
<br />
==== [[File:SolKatz.png]] Sol Katz Award ====<br />
: Every year, OSGeo presents the prestigious [http://www.osgeo.org/solkatz Sol Katz Award] to one individual who has demonstrated leadership and contributed significantly to advance open source ideals in the geospatial realm.<br />
<br />
====[[File:OSGeo_chair.png]] [[File:OSGeo_psc.png]] Voted position in an OSGeo community====<br />
: These people hold a position of responsibility within one of the OSGeo sub-communities. This may be a chair of an OSGeo committee or board member of a Regional Chapter, or a member of a project's Project Steering Committee (PSC).<br />
<br />
====[[File:OSGeo_coder.png]] [[File:OSGeo_committee.png]] Developers and Committee Members====<br />
: This is where the real work gets done developing and coordinating development of OSGeo Software.<br />
<br />
====[[File:OSGeo_user.png]] OSGeo Community Members====<br />
: 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.<br />
<br />
====[[File:OSGeo_translate.png]] OSGeo Translators====<br />
: These people have translated documentation for OSGeo-Live, and/or OSGeo projects. They usually have an established understanding of OSGeo topics and can present them in local languages.<br />
<br />
= Process for becoming an OSGeo Advocate =<br />
<br />
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:<br />
* Create an OSGeo wiki account, to edit this wiki (See "login" link in top right of this page).<br />
* Add a portrait photo of yourself using the [http://wiki.osgeo.org/wiki/Special:Upload Upload file] link in left margin in each page.<br />
* 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).<br />
* You can then add your profile on [[OSGeo_Advocate#OSGeo_Advocates|this wiki page]], under your Region:Country, names ordered alphabetically by First name, using the following:<br />
{{User:<YourOSGeoWikiUserName>}}<br />
<br />
= Annual Refresh of Advocate list =<br />
* 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.<br />
<br />
= Expenses =<br />
<br />
This OSGeo Advocate list has been designed to help event organisors find local authoritative speakers. Events wishing to import keynote speakers should anticipate covering expenses of these speakers. Note that OSGeo is a volunteer driven organisation without paid positions of authority and OSGeo doesn't budget to cover travel expenses. Note also that unlike proprietary companies, a company promoting Open Source software don't earn license fees when a delegate is convinced to start using the free software.<br />
<br />
When budgeting for keynote speakers expect to cover the following expenses:<br />
* Travel, typically including:<br />
** airfare<br />
** visa<br />
** travel insurance (including overseas medical, trip disruption, lost luggage, etc)<br />
** meals during travel<br />
** transit costs to local and host airports<br />
* Accommodation<br />
** standard 3 or 4 star hotel within walking distance of the event<br />
** high speed internet<br />
* Per diem costs<br />
** 3 meals a day<br />
* Speakers fee<br />
** typically $US 1000 per day. (Note that OSGeo volunteer speakers usually have a full time job and will be loosing wages for the duration of the event)<br />
<br />
For a rough guide of travel costs refer to the [http://aoprals.state.gov/web920/per_diem.asp US Department of State costs]<br />
<br />
Individual speakers may waive any of these costs if attracted to the event for other reasons, and final costs are to be negotiated with the selected speaker.<br />
<br />
= Other Resources =<br />
Links to other organizations running a similar process. <br />
* http://www.ogcnetwork.net/node/1585</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=User:Danielkastl&diff=77292User:Danielkastl2014-03-15T05:36:48Z<p>Dkastl: </p>
<hr />
<div>===Daniel Kastl===<br />
<br />
[[File:OSGeo_compass300.png|thumb|right|100px|Daniel Kastl]]<br />
<br />
Owner, [http://georepublic.info Georepublic] Germany & Japan<br />
<br />
Location(s): Osaka, Japan or Munich, Germany<br />
<br />
Daniel is a geographer, software developer, founder of Georepublic and Free Software advocate. <br />
<br />
;OSGeo Experience [[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]][[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]][[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]][[File:OSGeo_translate.png|link=OSGeo_Advocate#OSGeo_Community_Members]]<br />
<br />
:* pgRouting Project Steering Committee member<br />
:* Mentor for Google Summer of Code<br />
:* OSGeo Charter Member<br />
<br />
;Contact:<br />
: Email: daniel (A T) georepublic.co.jp<br />
: Phone: +49 (089) 4161 7698-1<br />
: [http://www.linkedin.com/in/dkastl LinkedIn] and [https://twitter.com/dkastl Twitter]<br />
<br />
;Spoken Language(s): German, English, Japanese<br />
<br />
;Profile last updated: 15 March 2014<br />
<br />
[[Category:OSGeo Member]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=PgRouting&diff=74294PgRouting2013-09-27T23:51:12Z<p>Dkastl: /* Project Governance */</p>
<hr />
<div>== Basic Project Data ==<br />
*'''Project Name:''' pgRouting<br />
*'''Project Status Condition:''' Stable<br />
*'''Project Web Site:''' http://pgrouting.org<br />
*'''Project Contact:''' Daniel Kastl <project at pgrouting.org><br />
*'''Short Project Description:''' pgRouting adds routing functionality to PostGIS.<br />
<br />
== Project Infrastructure ==<br />
*'''Project Source Code:''' https://github.com/pgrouting/pgrouting<br />
*'''Project Mailing List:''' http://lists.osgeo.org/mailman/listinfo/pgrouting-users<br />
*'''Project Version Control Repository:''' git://github.com/pgRouting/pgrouting.git<br />
*'''Project Bug Tracker:''' https://github.com/pgrouting/pgrouting/issues<br />
*'''Project Feature Request Tracker:''' https://github.com/pgrouting/pgrouting/issues<br />
<br />
== Project Governance ==<br />
*'''Source Code License:''' [http://www.gnu.org/licenses/gpl-2.0.html GNU General Public License, version 2]<br />
*'''Documentation License:''' [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-Share Alike 3.0]<br />
*'''Copyright Assignment Policy:''' All contributions are licensed under the terms of the GNU General Public License, version 2 without explicit assignment<br />
*'''Decision Making Procedure:''' Project Steering Committee<br />
*'''Coding Standards:''' https://github.com/pgRouting/pgrouting/wiki/2.0-Development-Guidelines-and-Standards<br />
*'''Release Procedure:''' https://github.com/pgRouting/pgrouting/wiki/pgRouting-Release-Process-Checklist<br />
<br />
== Project Deliverables ==<br />
*'''Latest Project Release:''' Version 2.0.0 (September 2013)<br />
<br />
[[Category: OSGeo Labs]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=PgRouting&diff=74293PgRouting2013-09-27T23:46:44Z<p>Dkastl: /* Project Deliverables */</p>
<hr />
<div>== Basic Project Data ==<br />
*'''Project Name:''' pgRouting<br />
*'''Project Status Condition:''' Stable<br />
*'''Project Web Site:''' http://pgrouting.org<br />
*'''Project Contact:''' Daniel Kastl <project at pgrouting.org><br />
*'''Short Project Description:''' pgRouting adds routing functionality to PostGIS.<br />
<br />
== Project Infrastructure ==<br />
*'''Project Source Code:''' https://github.com/pgrouting/pgrouting<br />
*'''Project Mailing List:''' http://lists.osgeo.org/mailman/listinfo/pgrouting-users<br />
*'''Project Version Control Repository:''' git://github.com/pgRouting/pgrouting.git<br />
*'''Project Bug Tracker:''' https://github.com/pgrouting/pgrouting/issues<br />
*'''Project Feature Request Tracker:''' https://github.com/pgrouting/pgrouting/issues<br />
<br />
== Project Governance ==<br />
*'''Source Code License:''' [http://www.gnu.org/licenses/gpl-2.0.html GNU General Public License, version 2]<br />
*'''Documentation License:''' [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-Share Alike 3.0]<br />
*'''Copyright Assignment Policy:''' All contributions are licensed under the terms of the GNU General Public License, version 2 without explicit assignment<br />
*'''Decision Making Procedure:''' <br />
*'''Coding Standards:''' <br />
*'''Release Procedure:'''<br />
<br />
== Project Deliverables ==<br />
*'''Latest Project Release:''' Version 2.0.0 (September 2013)<br />
<br />
[[Category: OSGeo Labs]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=New_Member_Nominations_2013&diff=72277New Member Nominations 20132013-07-10T09:49:07Z<p>Dkastl: </p>
<hr />
<div><!-- <span style="color:#FF0000"><strong>IMPORTANT: Charter member nomination period runs from 2013-07-09 to 2013-07-23!'''</strong></span> --><br />
<br />
The Charter Member nomination period runs from 2013-07-09 to 2013-07-23! The list of nominees for the [[Election_2013#Charter_Member_Election | 2013 Charter Member Election]] is maintained by the Chief Returning Officer (cro at osgeo.org). <br />
<br />
To submit a charter member nomination: <br />
* Please confirm with the nominated person first! <br />
* Please email cro@osgeo.org with their '''name''', '''country''', '''contact email''' and '''paragraph describing why you are recommending this person as a Charter Member''' <br />
* Please also feel free to cc: the nomination to the OSGeo discussion list - discuss@lists.osgeo.org - so the community can be nudged along and have a sense of what is going on. <br />
* Also, you might want to reference your [[OSGeo Advocate]] profile.<br />
<br />
The list of nominees will be maintained by the CRO here: <br />
<br />
{| class="wikitable sortable" border="1" cellpadding="5"<br />
|-<br />
!Name<br />
!Country<br />
!Notes<br />
<br />
|- valign="top"<br />
|[[OSGeo_Advocate#Just_van_den_Broecke|Just van den Broecke]]<br />
|The Netherlands<br />
|From: Bart van den Eijnden<br />
<br />
I'd like to nominate Just van den Broecke for OSGeo charter membership. Just has invested a lot of his time in getting the Dutch language chapter of Osgeo set up recently [0]. <br />
<br />
He has worked with a lot of the OSGeo software projects and has also developed tools in the open source domain on top of this such as Heron Mapping Components [1] and Streaming ETL [2]. <br />
<br />
In 2012 he organised the OSGeo track at the [[Geospatial World Forum 2012]] (GWF) and he is a regular visitor/speaker to/on FOSS4G and the Bolsena hacking event as well. <br />
<br />
* [0] http://osgeo.nl<br />
* [1] http://heron-mc.org<br />
* [2] http://www.stetl.org<br />
<br />
<br />
|- valign="top"<br />
|Phillip Davis<br />
|USA<br />
|From: Phillip Davis<br />
<br />
I would like to nominate myself for the OSGeo Charter membership. As the Director of the GeoTech Center [0] and Project Manager of the NISGTC [1] and a 30 year educator, I have a broad, international, interest in promoting Open Source software. My immediate goal is to secure $2M in NSF funding to create a national FOSS4G Academy here in the US [2]. Please also check out my LinkedIn profile [3].<br />
<br />
* [0] http://geotechcenter.org<br />
* [1] http://nisgtc.org<br />
* [2] http://foss4geo.org<br />
* [3] http://www.linkedin.com/pub/phillip-davis/9/59/b7b/<br />
<br />
<br />
|- valign="top"<br />
|Marc Jansen<br />
|Germany<br />
|From: Bart van den Eijnden<br />
<br />
I'd like to nominate Marc Jansen for OSGeo charter membership. Marc is actively involved in the OpenLayers [0] and GeoExt [1] projects and works for the German company terrestris [2]. He also co-created the GXM (GeoExt Mobile) [3] library based on Sencha Touch and OpenLayers. Marc also co-wrote a book [4] in German on OpenLayers.<br />
<br />
In 2012 Terrestris hosted a code sprint on GeoExt 2 in Bonn at their office, which was a great experience. A lot of the initial code for GeoExt 2 was actually created at an internal code sprint by terrestris in Malta.<br />
<br />
I have met Marc many times at code sprints and FOSS4G conferences, and was surprised to see he's not actually already a charter member.<br />
<br />
* [0] http://openlayers.org/<br />
* [1] https://github.com/GeoExt/<br />
* [2] http://www.terrestris.de/<br />
* [3] https://github.com/GeoExt/GXM<br />
* [4] http://www.amazon.de/OpenLayers-Webentwicklung-dynamischen-Karten-Geodaten/dp/3937514929<br />
<br />
<br />
|- valign="top"<br />
|Volker Mische<br />
|Germany<br />
|From: Bart van den Eijnden<br />
<br />
I'd like to nominate Volker Mische for OsGeo charter membership, since to my '''GREAT''' surprise he is not already a charter member.<br />
<br />
Volker hardly needs any introduction. He is the creator of GeoCouch [0] and works at Couchbase [1]. I'm sure many of you have seen his talks @FOSS4G conferences on this subject.<br />
<br />
He also contributed to OpenLayers [2], has co-created a library that integrates OpenLayers with jQuery (MapQuery).<br />
<br />
Volker is very active member in the OSGeo community already, and was involved in the organisation of FOSS4G in 2009 in Sydney [3].<br />
<br />
See also his engagement with FOSS4G 2013 [4]. <br />
<br />
* [0] https://github.com/couchbase/geocouch/<br />
* [1] http://www.couchbase.com/<br />
* [2] http://openlayers.org/<br />
* [3] http://2009.foss4g.org/<br />
* [4] http://www.fossgis.de/konferenz/2013/programm/speakers/33.de.html<br />
<br />
|- valign="top"<br />
|[[Marco Lechner]]<br />
|Germany<br />
|From: [[Athina Trakas]]<br />
<br />
I would like to nominate Marco Lechner as OSGeo Charter member.<br />
<br />
Marco is a well known and constant supporter of the the OSGeo community and since many years involved in planning and execution of the German speaking FOSSGIS Konferenz [0].<br />
<br />
He is president of the management board of the FOSSGIS e.V. [1], the legal association supporting Free Software for Geoinformation and Open Geodata in Germany. The history of FOSSGIS goes back to the German GRASS User Community founded in 2001. The FOSSGIS e.V. is the OSGeo German speaking Local Chapter and acts as a legal entitiy for the German speaking OpenStreetMap [2] community. <br />
<br />
* [0] http://www.fossgis.de/konferenz/2013/<br />
* [1] http://www.fossgis.de/<br />
* [2] http://www.openstreetmap.de/<br />
<br />
|- valign="top"<br />
|[[User:Codrina | Codrina Maria Ilie]]<br />
|Romania<br />
|From: [[Jeff McKenna]]<br />
<br />
It is my honor to nominate Codrina [0] as a Charter Member of OSGeo.<br />
Passionate about FOSS4G and Open Data, she is well known for her<br />
enthusiasm in Romania and Denmark.<br />
<br />
Earlier this year, I was planning on giving training in Copenhagen, I<br />
might have mentioned this on the OSGeo Board mailing list, and then I<br />
received a direct email from her introducing herself and asking if we<br />
should have an OSGeo meetup in Copenhagen when I was there. Even though<br />
she recently moved from Romania to Denmark, she was somehow able to be<br />
the sparkplug to bring together a large group of Open Source geospatial<br />
passionate people in Copenhagen. <br />
<br />
Little did I know that this meeting would also spark an invite to me to<br />
the (at the time) upcoming FOSS4G-CEE event in Bucharest [1], hosted by the<br />
geo-spatial.org / Romanian Chapter team [2]. I would of course end up<br />
attending the event, and watched as her and the geo-spatial.org family<br />
brought together hundreds of FOSS4G and Open Data enthusiasts from<br />
countries all over Europe.<br />
<br />
Codrina may not write code, but she has that rare passion, that<br />
strength, that guts, that allows her to network and share her FOSS4G<br />
knowledge. She holds workshops [3], writes user guides, and organizes<br />
events [4], that bring together developers, decision makers, students, and<br />
users - these thankless tasks are so very important. I've heard from<br />
others how she repeatedly attends hi-tech events with no other females<br />
present, introduces herself and starts promoting FOSS4G and Open Data.<br />
<br />
I feel this is an international leader to-be, someone who sees the world<br />
as a very small community, willing to travel to bring the community<br />
together. It is my honor to help her grow and allow her to provide<br />
input to the shape of the OSGeo foundation.<br />
<br />
It is for all these reasons I am nominating Codrina to become a Charter<br />
Member of OSGeo.<br />
<br />
* [0] http://wiki.osgeo.osuosl.org/wiki/User:Codrina<br />
* [1] http://2013.foss4g-cee.org/<br />
* [2] http://www.osgeo.ro/<br />
* [3] http://earth.unibuc.ro/osgeo<br />
* [4] http://opensourcedays.org/2013/<br />
<br />
|- valign="top"<br />
|Eli Adam<br />
|USA<br />
|From: David Percy<br />
<br />
I would like to nominate Eli Adam as Charter Member.<br />
<br />
Eli is active on the OSGeo Journal [0], and several other committees at<br />
OSGeo. He was also instrumental in establishing the Portland, Oregon<br />
open source GIS group as an official chapter of OSGeo [1]. He has worked<br />
on a statewide campaign to get government standardized on GeoMoose for<br />
parcel data (he may have contributed code, too). As a government<br />
employee, he brings a very useful perspective.<br />
<br />
I'm sure Eli does a whole lot of other great stuff, he has so much<br />
energy and is so helpful!<br />
<br />
* [0] http://wiki.osgeo.org/wiki/PDX_OSGEO_Chapter_Annual_Report_2010<br />
* [1] http://wiki.osgeo.org/wiki/PDXOSGEO_Member_Listing<br />
* [2] http://wiki.osgeo.org/wiki/Contacts<br />
* [[OSGeo_Advocate#Eli_Adam | Eli Adam OSGeo Advocate Profile]]<br />
* [http://osgeo-org.1560.x6.nabble.com/template/NamlServlet.jtp?macro=user_nodes&user=190827 Activity on some OSGeo email lists]<br />
* [http://wiki.osgeo.org/wiki/Journal Read some OSGeo Journals] or [http://trac.osgeo.org/osgeo/search?q=EliL&noquickjump=1&changeset=on check out Journal contributions]<br />
* [http://www.ohloh.net/p/geomoose/contributors/154028264976796 GeoMoose contributions on ohloh]<br />
<br />
|- valign="top"<br />
|Alessandro Furieri<br />
|Italy<br />
|From: [[Markus Neteler]]<br />
<br />
Alessandro is an Italian developer working as a freelancer. In the<br />
FOSS4G world he is quite known as the main developer and maintainer of<br />
both the SpatiaLite and RasterLite projects [0]. Furthermore, he is a QGIS<br />
contributor [1] (the SpatiaLite data provider), and he contributed some<br />
code to GDAL/OGR [2] as well (GML Topology advanced parser,<br />
SQLite/SpatiaLite driver).<br />
<br />
Alessandro is active in the Italian community: During the last three<br />
years he was the President of the very productive OSGeo's Italian<br />
Local Chapter - GFOSS.it [3]<br />
<br />
* [0] http://www.gaia-gis.it/gaia-sins/<br />
* [1] http://www.qgis.org<br />
* [2] http://www.gdal.org<br />
* [3] http://wiki.osgeo.org/wiki/Italiano_Chapter_Report_2012.<br />
<br />
|- valign="top"<br />
|[[Vincent Picavet]]<br />
|France<br />
|From: [[Jáchym Čepický]]<br />
<br />
I would like to nominate Vincent Picavet as a Charter Member of OSGeo.<br />
<br />
I know Vincent personally as QGIS [0] and PostGIS [1] enthusiast and developer,<br />
and I share his ideas about OSGeo and it's environment, which I had the<br />
chance to know a little bit during our chats at both FOSS4G-CEE events<br />
(his idea it was, to rename it to FOSS4G-NSCNEE for<br />
Not-So-Central-Neither-Eastern-Europe, which I like).<br />
<br />
Vincent was always involved in open source world, particulary in the GIS<br />
field. He is a founding member of Francophone OSGeo local chapter [2] and<br />
its current treasurer. He has initiated the first FOSS4G event in France<br />
(FROG2013) and organized other FOSS4G-related events in France (QGIS day<br />
2011, PostGIS session 2011...)<br />
<br />
Vincent talked at a lot of international and local conferences on<br />
various FOSS4G subjects (among others about QGIS) and especially spatial<br />
databases (PostGIS).<br />
<br />
Vincent founded Oslandia [3] in 2009 with Olivier Courtin, providing<br />
services around FOSS4G and focusing on quality and innovation for<br />
opensource GIS.<br />
<br />
* [0] http://www.qgis.org<br />
* [1] http://www.postgis.org<br />
* [2] [[Francophone OSGeo Chapter]]<br />
* [3] http://www.oslandia.com/<br />
<br />
<br />
|- valign="top"<br />
|[[Taichi FURUHASHI]]<br />
|Japan<br />
|From: [[Venkatesh Raghavan]]<br />
<br />
Furahashi-san is the driving force behind the FOSS4G-Japan events and<br />
the main organizer of FOSS4G-Tokyo [0] event. He is also very<br />
active in the OSM community and took the lead in organizing<br />
SotM-Tokyo in 2012 [1]. He uses, develops and promotes OSGeo<br />
Source and Open Data in several of his projects both<br />
nationally and internationally. His recent work related to<br />
the March 11 2011 earthquake in Japan is also widely<br />
appreciated.<br />
<br />
Find out more about Furuhashi-san on his Google+ web pages [2]<br />
<br />
* [0] http://www.osgeo.jp/%E3%82%A4%E3%83%99%E3%83%B3%E3%83%88/foss4g-2011-tokyo/<br />
* [1] http://wiki.openstreetmap.org/wiki/State_Of_The_Map_2012<br />
* [2] https://plus.google.com/114377119565167633675/about <br />
<br />
<br />
|- valign="top"<br />
|Nobusuke IWASAKI <br />
|Japan<br />
|From: [[Venkatesh Raghavan]]<br />
<br />
Iwasaki-san's passion for FOSS4G in unmatched. He is one of the<br />
the main organizer of FOSS4G-Japan event [0] and also a regular at<br />
FOSS4G Global events. He is a very active user, developer, trainer and<br />
promoter of OSGeo Source geospatial and Open Data at several forums and also in his<br />
projects both nationally and internationally. Apart form several scientific works<br />
using Open Source and Open Data, his work on i18N of OSGeo software<br />
and OSGeo-Live is also a great contribution.<br />
<br />
Find out more about Iwasaki-san on his web page at: [1]<br />
<br />
* [0] http://www.osgeo.jp/<br />
* [1] http://cse.niaes.affrc.go.jp/niwasaki/ <br />
<br />
<br />
|- valign="top"<br />
|[[Daniel Kastl]]<br />
|Germany<br />
|From: [[Venkatesh Raghavan]]<br />
<br />
Daniel-san is a regular at FOSS4G since beginning. He leads the pgRouting [0]<br />
project which has become one of the regular and workshops at FOSS4G related<br />
events [1]. He is very active a a mentor in GSoC [2] and has trained several young<br />
developers. He is also very active in the OSM community. He is a very active<br />
user, developer, trainer and promoter of OSGeo Source and Open Data at several<br />
forums and projects.<br />
<br />
Learn more about Daniel-san at on his LinkedIn profile page at [3].<br />
<br />
* [0] http://pgrouting.org<br />
* [1] http://workshop.pgrouting.org/<br />
* [2] http://wiki.osgeo.org/wiki/OpenRouter_2012_SOC_Ideas#Mentor_Candidates<br />
* [3] http://jp.linkedin.com/in/dkastl<br />
<br />
<br />
<!--<br />
''Please copy this section to add new nominees''<br />
|- valign="top"<br />
|''Name''<br />
|''Country''<br />
|From: ''Nominator''<br />
<br />
''Free text to introduce the nominee''<br />
<br />
* [0] ''Add some links''<br />
--><br />
<br />
[[Category:Elections]] <br />
[[Category:Election 2013]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=User:Danielkastl&diff=71055User:Danielkastl2013-05-13T01:06:30Z<p>Dkastl: </p>
<hr />
<div>CEO and developer at [http://georepublic.de Georepublic Germany]<br />
<br />
CIO and developer at [http://georepublic.co.jp Georepublic Japan]<br />
* [http://pgrouting.postlbs.org pgRouting]<br />
* [http://pggeocoder.postlbs.org pgGeocoder]<br />
<br />
{{#umUserMap: Danielkastl|400px|250px|4}}<br />
<br />
; Location<br />
: 34.583475N 135.373535E <br />
: Osaka, Japan<br />
<br />
: [mailto:daniel.kastl@georepublic.de daniel.kastl@georepublic.de],<br />
<br />
{{#umSetParam: 135.373535|34.583475|Osaka, Japan|Danielkastl|Daniel Kastl}}<br />
<br />
[[Category:OSGeo Member]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=Geoservices_REST_API&diff=71054Geoservices REST API2013-05-13T01:05:33Z<p>Dkastl: /* Signed */</p>
<hr />
<div>This wiki page aims to collate community concerns related to the adoption of the "Geoservices REST API" document as a standard of the [http://www.opengeospatial.org/ Open Geospatial Consortium (OGC)]. The page is being collaboratively edited, targeting completion by Wednesday 15 May 2013, after which it will be delivered by the board of the [http://osgeo.org OSGeo Foundation (OSGeo)] to the OGC and OGC voting members.<br />
<br />
= Cover Letter from the OSGeo Board =<br />
''Please don't edit this "Cover Letter" statement, which has been approved by the OSGeo Board.'' <br />
<br />
The board of the [http://osgeo.org Open Source Geospatial Foundation] (OSGeo) is presenting this letter to the OGC. It highlights concerns about the "GeoServices REST API" from many people within the OSGeo community. As always, if there is anything the OSGeo board can do to help, then please let us know.<br />
<br />
Signed: Jeff McKenna (OSGeo president), <br />
Peter Batty,<br />
Jáchym Čepický,<br />
Michael Gerlek,<br />
Anne Ghisla,<br />
Mark Lucas,<br />
Daniel Morissette,<br />
Cameron Shorter,<br />
Frank Warmerdam<br />
<br />
= Open Letter to OGC and voting members =<br />
<br />
''Please don't edit this "Open Letter" statement, comments and discussion should go in the "Further Concerns" section below.'' <br />
<br />
May 2013<br />
<br />
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.<br />
<br />
We strongly urge that the proposed "Geoservices REST API", as it stands in May 2013, be rejected as an OGC standard.<br />
<br />
People have listed different reasons for concern. They are described below.<br />
<br />
== Signed ==<br />
''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.''<br />
<br />
# [[User:camerons|Cameron Shorter]], Geospatial Solutions Director at [http://lisasoft.com LISAsoft], core contributor & coordinator of [http://live.osgeo.org OSGeo-Live], OSGeo Board member<br />
# [[Mark Lucas]], Founding member and board of directors for OSGeo foundation, Prinicipal Scientist for RadiantBlue Technologies Inc.<br />
# [[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]<br />
# [[User:rouault|Even Rouault]], Geospatial developer, OSGeo Charter Member, core contributor and PSC member of [http://gdal.org GDAL/OGR], contributor of [http://mapserver.org Mapserver], [http://trac.osgeo.org/proj/ PROJ.4], [http://trac.osgeo.org/geotiff/ libgeotiff], [http://shapelib.maptools.org/ shapelib], [http://www.remotesensing.org/libtiff/ libtiff]<br />
# Gerhard Triebnig, Managing Director at [http://eox.at EOX IT Services GmbH]<br />
# [[User:pcreso|Brent Wood]], Environmental Information Delivery Programme Leader, NIWA, New Zealand. OGC member, Aust/NZ OSGEO chapter member, NZOSS Council member<br />
# [[User:Schpidi|Stephan Meissl]], CTO at [http://eox.at EOX IT Services GmbH], contributor to [http://mapserver.org Mapserver], PSC chair of [http://eoxserver.org EOxServer]<br />
# [[User:ticheler|Jeroen Ticheler]], Director of [http://geocat.net GeoCat], project founder and PSC chair of [http://geonetwork-opensource.org GeoNetwork opensource]<br />
# [[User:Just|Just van den Broecke]], Director at [http://www.justobjects.nl Just Objects], contributor to [http://heron-mc.org Heron Mapping Client], secretary of [http://osgeo.nl OSGeo Dutch Local Chapter], member at [http://www.opengeogroep.nl OpenGeoGroep]<br />
# [[User:milovanderlinden|Milo van der Linden]], member at [http://www.opengeogroep.nl OpenGeoGroep]<br />
# [[User:surveyor|Landon Blake]], GIS Department Manager/Land Surveyor at [http://www.ksninc.com KSN], OSGeo California Chapter Board Representative.<br />
# [[User:dmorissette|Daniel Morissette]], President at [http://mapgears.com/ Mapgears], core contributor and PSC member of [http://mapserver.org Mapserver] and [http://gdal.org GDAL/OGR]. Former OGC TC member and involved in the implementation of several OGC WxS services specs in MapServer.<br />
# [[User:blammo|Bob Basques]], GIS Systems Developer at the City of Saint Paul, MN. [http://gis.ci.stpaul.mn.us Public Works GIS (GISmo)], Technical Director at [http://www.sharedgeo.org SharedGeo], OSGeo Charter Member, OSGeo TCMUG local chapter member, Co-founder and PSC member of [http://www.geomoose.org GeoMoose] project.<br />
# [[User:vehrka|Pedro-Juan Ferrer Matoses]], PM at Omnium Strategic Intelligence, Spain, OSGeo Charter Member, OSGeo Spanish Local Chapter Liaison officer.<br />
# Bevan Rudge, Director Lucion Limited, IT Advisor at Conservation Strategy Fund, Esri client<br />
# [[User:Delawen|María Arias de Reyna]], software engineer at [http://geocat.net GeoCat], Spain, member of OSGeo Spanish Local Chapter.<br />
# [[User:Aghisla|Anne Ghisla]], OSGeo Board Member, Italy, member of OSGeo Italian Local Chapter.<br />
# [[User:Michogar|Micho Garcia]], Freelance and member of [http://geomati.co geomati.co], Spain, member of Spanish Local Chapter<br />
# [[User:Madi|Margherita Di Leo]], OSGeo Charter Member, Post-doctoral researcher at the European Commission, JRC, Italy<br />
# [[Jorge Sanz]], GIS Consultant at [http://www.prodevelop.es Prodevelop], OSGeo Charter Member, OSGeo Spanish Local Chapter Member, Spain<br />
# [[Pablo Sanxiao]], CTO and co-founder at [http://www.icarto.es iCarto], OSGeo Spanish Local Chapter Member, Spain<br />
# [[User:Fsteggink|Frank Steggink]], GIS software developer at [http://www.vicrea.nl Vicrea], The Netherlands, member of the Dutch Local Chapter<br />
# [[User:Olivier.courtin|Olivier Courtin]], [http://www.oslandia.com Oslandia] co-founder, core contributor or/and PSC member of [http://mapserver.org Mapserver] and [http://www.postgis.org/ PostGIS]. OGC TC member.<br />
# [[User:Bolosig|Wladimir Szczerban]], OSGeo Spanish Local Chapter Member, Spain<br />
# [[User:AnitaGraser|Anita Graser]], GIS specialist with AIT Austrian Institute of Technology, OSGeo Charter member and QGIS team member.<br />
# [[User:Vmische|Volker Mische]], geospatial software engineer, creator of GeoCouch<br />
# [[User:Ivansanchez|Iván Sánchez]], OSGeo Spanish Local Chapter Member, head of [http://www.openstreetmap.es OpenStreetMap Spain], [http://osmfoundation.org OpenStreetMap Foundation] member, [http://hot.openstreetmap.org/ Humanitarian OpenStreetMap Team] member, [http://www.idee.es/ Spanish SDI working group] member<br />
# [[User:Gabi|Gabriel Carrión]], Strategy Manager at [http://www.gvsig.com gvSIG association]<br />
# [http://strk.keybit.net Sandro Santilli], OSGeo Charter Member, [http://postgis.net PostGIS] and [http://trac.osgeo.org/geos GEOS] PSC member and core hacker.<br />
# [[User:Javiarch|Javier Diaz]], member of Geoinquietos Bs As [http://wiki.osgeo.org/wiki/Category:Geoinquietos_Buenos_Aires], member of the Organizing Committee FOSS4G Bs As 2013 [http://www.foss4g-ba.org/]<br />
# [[User: JoCook|Jo Cook]], Consultant at [http://isharemaps.com| Astun Technology], former Director of OSGeo, Charter Member, founder of UK Local Chapter, Deputy Chair of [http://2013.foss4g.org| FOSS4G 2013]<br />
# [[User: Fpenarru | Francisco José Peñarrubia]], CTO and co-founder at [http://www.scolab.es SCOLAB]. Members of [http://www.gvsig.com gvSIG Association]<br />
# [[User: Ganesh|Shanmugam Ganeshkumar]], Director of [http://www.geoicon.com GeoICON], member OSGeo Malaysia Chapter<br />
# [[User:Barryrowlingson|Barry Rowlingson]], Senior Researcher, Lancaster University and Software Sustainability Institute Fellow<br />
# [[User: Sfkeller|Stefan Keller]], University of Applied Sciences, Rapperswil (Switzerland), Member of Swiss OSM (SOSM) and QGIS association and of organizing committees of pgConf.DE and FOSSGIS 2013, and member of eCH (e-government standards of Switzerland)<br />
# [[User: AndyBMapMan|Andrew Bailey]], OSGeo member, Astun Technology<br />
# [[User: Sanand|Suchith Anand]], OSGeo Charter member, OSGeo Education member, FOSS4G 2013 LOC member<br />
# [[User: krefftc|Carlos Krefft]], GIS software developer at [http://www.cstars.miami.edu CSTARS - University of Miami], OGC and OSGeo Member.<br />
# [[User:Steko|Stefano Costa]], OSGeo member, GFOSS.it member and former board member, Ministero per i Beni e le Attività Culturali (Italy)<br />
# [[User:pebau|Peter Baumann]], [http://www.jacobs-university.de/lsis Jacobs University], OGC member, WCS.SWG chair, editor of 10+ specs (disclaimer: this is an expression of my personal opinion and not in any way endorsed by OGC)<br />
# [[User:pmbatty|Peter Batty]], CTO of Geospatial Division at [http://www.ubisense.net Ubisense], OSGeo board member, former CTO of [http://intergraph.com Intergraph] and [http://www.gedigitalenergy.com/gis.htm GE Smallworld], Technical Committee member of OGC in its formative years c 1995-97<br />
# [[User: BarendKobben | Barend K&ouml;bben]], OSGEO Chartered Member, OSGeo.nl Dutch chapter treasurer, Senior Lecturer at [http://www.itc.nl ITC-University of Twente]<br />
# [[User: pcav | Paolo Cavallini]], [http://www.faunalia.it Faunalia], OSGeo member, GFOSS.it member and former president, QGIS-PSC<br />
# [[User: fthamura| FRans Thamura]], [http://www.osgeo.or.id Indonesia], OSGeo Indonesia, organizer]<br />
# [[User: Endofcap| Sanghee Shin]], Founder and CEO of [http://www.gaia3d.com Gaia3D], OSGeo Charter Member, Representative of [http://www.osgeo.kr OSGeo Korean Chapter], Chairman of Open Source GIS Alliance Korea<br />
# [[User: rentairo| Benni Purwonegoro]],Indonesia, IT-Spatial Engineer @ Geospatial Information Agency .<br />
# [[User: jachym| Jachym Cepicky]], Czech Republic, member of OSGeo Board of Directors<br />
# [[User: cappelaere| Pat Cappelaere]], Vightel Corporation<br />
# [[User: JuergenFischer|Jürgen Fischer]], norBIT GmbH, QGIS core developer<br />
# [[User: Maria|Maria Antonia Brovelli]], OSGeo Charter member, OSGeo Education member, GIS Professor and Vice Rector for the Como Campus at [http://www.polimi.it/en Politecnico di Milano], Italy<br />
# [[User:Nachouve |Nacho Varela]], GIS Consultant, OSGeo Spanish Local Chapter Member, Spain<br />
# [[User:vasile |Vasile Craciunescu]], OSGeo Charter member, OSGeo Romania Local Chapter Leader, Researcher at Romanian National Meteorological Administration, Romania<br />
# [[User:badaveil |Abbas Abdul Wahab]], Asst. Director, Federal Department of Town & Country Planning, Peninsular Malaysia<br />
# [[User:rbraam | Roy Braam]], Software Engineer @ [http://www.b3partners.nl | B3Partners]<br />
# [[User:peteris | Peteris Bruns]], Latvia, GIS Consultant & Software Engineer @ [http://www.sungis.lv | SunGIS]<br />
# [[User:Lutra | Giovanni Manghi]], Portugal, [http://www.faunalia.pt Faunalia], OSGeo member, OSGeo-Portugal<br />
# [[User:Hfpmartins | Hugo Martins]], UK, [http://www.lutraconsulting.co.uk Lutra Consulting], WebGIS Developer, OSGeo-Portugal Member<br />
# [[User:Sabb | Saber Razmjooei]], UK, [http://www.lutraconsulting.co.uk Lutra Consulting], Co-Founder<br />
# [[User:Wellsp | Peter Wells]], UK, [http://www.lutraconsulting.co.uk Lutra Consulting], Co-Founder<br />
# [[User:SGijzen | Sidney Gijzen]], The Netherlands, Researcher GIS @ [http://www.wageningenur.nl/en/Expertise-Services/Research-Institutes/alterra.htm Alterra, Wageningen UR]<br />
# [[User:mfidelman | Miles Fidelman]], US, Principal, Protocol Technologies Group, LLC<br />
# [[User:punkish | Puneet Kishor]], OSGeo Charter Member; [http://www.geology.wisc.edu Geology, Univ. of Wisconsin-Madison]; [http://creativecommons.org/staff#puneetkishor Creative Commons]<br />
# [[User:Toze | António José Silva]], Portugal, GIS Consultant, OSGeo-Portugal Member<br />
# [[User:AndreMano | AndreMano]], Portugal, Natural History Society - GIS Department, OSGeo-Portugal Member<br />
# [[User:maurimiranda|Mauricio Miranda]], Argentina, OSGeo Charter Member, OSGeo Spanish Local Chapter Board Member<br />
# [[User:pmachado|Paulo Machado]], Portugal, Software Engineer @ PT Inovação<br />
# [[User:alvaro|Alvaro Anguix]], Spain, General Manager at [http://www.gvsig.com gvSIG Association]<br />
# [[Santiago Higuera]], CEO at [http://Mercatorlab.com Mercatorlab], OSGeo Spanish Local Chapter Board Member, Spain<br />
# [[Alan Boudreault]], Developer at [http://mapgears.com/ Mapgears], contributor to [http://mapserver.org Mapserver] and [httpo://gdal.org GDAL/OGR].<br />
# [[User:mikesaunt|Mike Saunt]], UK, Owner at [http://astuntechnology.com Astun Technology Ltd], OSGeo sponsor<br />
# [[User:msmitherdc|Michael Smith]], OSGeo Charter Member, Physical Scientist US Army Corps of Engineers Remote Sensing GIS Center<br />
# [[User:Kalxas|Angelos Tzotsos]], OSGeo Charter Member, Researcher at National Technical University of Athens<br />
# [[User:Kimaidou|Michaël Douchin]], France, GIS consultant & software engineer at [http://3liz.com/ 3liz]<br />
# [[User:PedroVenancio | Pedro Venâncio]], Portugal, GIS Analyst @ Municipality of Pinhel<br />
# [[User:Jgrocha|Jorge Gustavo Rocha]], Portugal, GIS Professor at Universidade do Minho<br />
# [[User:Danielkastl| Daniel Kastl]], Japan, [http://georepublic.info Georepublic], Founder<br />
<br />
= Summary =<br />
<br />
''Please don't edit this section - it is now locked to ensure editorial review. You may send comments to Cameron Shorter AT gmail .com''<br />
<br />
The document titled "GeoServices REST API" is currently, in May 2013, being considered to be included as one of the Open Geospatial Consortium (OGC) standards. The vote to accept the document as a standard is unusually contentious; the controversy is the cause of this page.<br />
<br />
The document was previously released for public comment and can be found [http://www.opengeospatial.org/standards/requests/89 on the request for public comment page] (though public comment has been closed for now).<br />
<br />
The document attempts to standardize a suite of web services such as a service which provides map images, a service which provides geospatial feature data, and a service which performs geospatial processing. The standard focuses on interactions via a defined hierarchy of URLs and using predominantly a particular set of JSON schemas for the exchange of geospatial data.<br />
<br />
== Criticism and Response ==<br />
<br />
The adoption of the document as an OGC Standard is contentious for a wide variety of reasons including:<br />
<br />
* the process through which the document was developed which is thought to lack sufficient flexibility to respond to input from various stakeholders, <br />
* the focus of the document on 'REST' and 'API' which is seen as not matching the ideas others have for these concepts,<br />
* the names of the standard and of the services which are seen as potentially confusing, <br />
* the functionality of the new services which are considered to duplicate that of existing services already standardized by the OGC such as WMS, WFS, WCS, and WPS,<br />
* the addition of a new set of services based on new URL patterns and new JSON exchange formats which is seen as duplicating the efforts of other working groups bringing similar ideas to the updates of existing OGC services,<br />
* the re-introduction in the new services of previously resolved interoperability issues which is seen as failing to build on the existing knowledge and experience,<br />
* the use of the particular JSON schemas which are seen as having little industry acceptance and are incompatible with other widely used schemas, and <br />
* the lack of implementation diversity which is thought to give the vendor of the one complete implementation an unusual commercial advantage on top of the vendor's already dominant position in the domain. <br />
<br />
These issues have potential impacts on the use of 'Open Standards' by governments and companies, on the interoperability of software interacting with standards compliant OGC services, on the costs to developers and users of standards compliant software, on the understanding of 'Open Standards' by the public at large, and, possibly, on the reputation of the OGC as a champion of interoperability.<br />
<br />
In particular there are concerns by some that adoption of the standard will likely result in a combination of the following:<br />
# The cost to application developers, systems integrators, testers and sponsors to support all relevant OGC standards will be substantially increased.<br />
# Consequently, organisations and/or applications may choose to only support one standard, or only support one standard fully.<br />
# Sponsors (such as governments) who require compliance with OGC standards will discover that applications don't communicate together, due to applications supporting different OGC standards that essentially do the same thing.<br />
# This will result in a diminished importance of OGC, as the "OGC standards" stamp of approval will not equate interoperability.<br />
# After a while, in order to solve interoperability issues, a respected international organisation or program will likely take the initiative to mandate one standard as the preferred standard for all agencies to follow. To date, the OGC has provided this leadership.<br />
# One standard taking prominance over the other will likely lead to the other being neglected or deprecated, resulting in many OGC compliant systems becoming legacy systems in the process. This should be considered an undesirable outcome for a standards organisation.<br />
<br />
In response to these issues, the authors of the Geoservices REST API document have stated that:<br />
<br />
* the process of the OGC has been followed completely,<br />
* the specification actually is RESTful and does define an API,<br />
* the name, due to the controversy, may be open for modification<br />
* the OGC does not forbid duplication of service functionality, already has duplication between the W*S and the S*S (sensor) family of standards, should not block progress in the name of 'one true way', and harmonization between the services can be considered in the future,<br />
* the JSON format exists and functions, and<br />
* there are alternative implementations for some of these services.<br />
<br />
The authors also stress that the existence of a large user base shows the service is useful, and that the standardization of the services at the OGC may encourage new implementations.<br />
<br />
= Positions on the vote =<br />
''Please don't edit this section - it is now locked to ensure editorial review. You may send comments to Cameron Shorter AT gmail .com''<br />
<br />
The discussion raises a number of issues, many based upon complex technical concepts and implications. This makes it difficult for voting OGC members considering whether to support "Geoservices REST API" as a standard. The following provides one analysis of the positions on the vote, aimed to simplify and summarize key points. However, it does not necessarily represent the opinions held by all signatories above.<br />
<br />
; The pros for accepting the "Geoservices REST API" document as an OGC standard:<br />
<br />
:* The OGC should be in the business of developing good standards, not in choosing which standards should be implemented.<br />
:* The proposers of the document want to make a standard and have followed all the rules of the OGC. The work of any such group of members deserves serious, good faith consideration.<br />
:* The need for an integrated suite of services using simple data, which is addressed (partially) by the document, is real. The proposed document is pushing the OGC on this issue.<br />
:* The proposed document could be useful to a number of people.<br />
:* The proposed document is not significantly more broken than the existing standards of the OGC. As one author of standards [http://lists.osgeo.org/pipermail/discuss/2013-May/011667.html notes]: <br />
:''"I know how totally impossible it is to write a good standard, so the weaknesses in the existing document seem more acceptable."''<br />
<br />
; The cons:<br />
<br />
:* The OGC actually is, whether it should be or not, in the position of recommending interoperable standards for geospatial services. The proposed document is not good enough, not widely enough implemented, and not publicly supported enough, to be considered at the same level as existing standards.<br />
:* Adopting a standard implies a desire to maintain the standard, but OGC's desire to support this approach has been questioned by some. In particular, the lack of collaboration and willingness to accept recommendations from the community on this version of the "Geoservices REST API" document bodes ill for the future.<br />
:* The overlap in functionality between the proposed services and the existing services, notably with the ongoing work to modularize the existing services, is almost 100 percent. However, compatibility is low.<br />
:* There is already a published document: http://www.esri.com/library/whitepapers/pdfs/geoservices-rest-spec.pdf so there is no need for the document to be adopted as an OGC Standard merely for interoperability with the ESRI implementation.<br />
:* The document, as a new, separate effort, repeats mistakes which were made and since solved by the other services.<br />
:* The document focuses on the past (notably with backwards compatibility and use of only GET/POST) not on the future.<br />
:* The document needs a comprehensive editorial review and substantial rewriting for clarity.<br />
<br />
; A conclusion:<br />
<br />
Both simple answers are bad.<br />
<br />
A simple acceptance of the standard would introduce a new set of 'OGC approved' open services. The OGC approval might enable governments to buy a XXXX-new-name-here-XXXX solution instead of a W*S or a S*S solution. The path forwards towards harmonizing the services is unclear. Fixing this document in addition to fixing the W*S services will be a pain.<br />
<br />
Simply rejecting the solution would be bad for the OGC. It would place the OGC in the position of picking winners and losers in the standards business. It would mean that the OGC is stuck on the project of fixing the W*S standards to meet some nebulous future functionality without having any path to get there. It would discourage innovation and progress.<br />
<br />
Is there any third way?<br />
<br />
Well, actually, there is a different way of thinking of the issue. Overall, there appears to be a shared desire for an integrated suite of geospatial services, originally focused on a simple data model, built on the exchange of well defined resources in simple formats including JSON, accessible and usable using the core HTTP verbs, and discoverable through following HTML links and patterns of URL paths. The hope is that such a suite can be designed based on the best expertise of the OGC, can be widely supported by the community, and can be implemented and tested by multiple groups. Neither the proposed document, nor the current services meet this vision. So the work, ultimately, is on improving all the services at the OGC, first to modularize them, then to enable simple implementations, and finally to link those implementations into a functional suite. Since this is the work that is already happening, perhaps the vote is an unfortunate distraction and the productive way forward is merely to redouble the efforts to create the next versions of the standards.<br />
<br />
= Issues with the document =<br />
<br />
''Please don't edit this section - it is now locked to ensure editorial review. You may send comments to Cameron Shorter AT gmail .com''<br />
<br />
Beyond the controversy described above, there are issues with the Geoservices REST API document itself. Even if the standard deserves support, these issues could be considered blockers to the adoption of the current, May 2013, document.<br />
<br />
The critique is incomplete because it quickly falls into a full editorial review of the text, something which takes a lot of time and effort and is beyond the scope and intent of this Open Letter.<br />
<br />
The critique can be found at: http://wiki.osgeo.org/wiki/Geoservices_REST_API_critique.<br />
<br />
Note that some of these critiques hold the document to OGC's current, standards writing guidelines. The OGC has been striving to develop better standards so new standards must meet higher requirements than past standards. The lack of clarity in the proposed document is not substantially worse than many published standards but ought to be resolved in new standards.<br />
<br />
= Further Concerns =<br />
--- DRAFT ____<br />
<br />
''Please add concerns not addressed above as bullet points below. Where appropriate, link to external web pages (such as email achieves). Try to be concise, and try not to repeat concepts which have been covered above, (less words get read by more people). Points you have previously added, which are now covered above should be removed. Words that have been struck out will be removed by Tuesday 14 May.''<br />
<br />
== Political Concerns ==<br />
<br />
* <strike>Adopting the standard will expose the OGC to a strong suspicion of acting as a rubber stamp organization under ESRI weight, and will be detrimental to its recognized position as a reference organization for geospatial standards.</strike><br />
* <strike>It is a dubious practice that a standardization organisation promotes competing standards, without explicitely obsoleting (or at least recommending) some of them. How is a newcomer to the industry supposed to select the appropriate standard if several ones share the same scope : WFS or GeoServices REST API Feature Service, WMS or GeoServices REST API Map Service, etc. ?</strike><br />
<br />
== Commercial Concerns ==<br />
<br />
* <strike>Promoting standards from an existing implementation made by a single vendor leads to an obvious bias in competition.</strike><br />
* <strike>Supporting multiple overlapping standards greatly reduces usability while it increases complexity and cost of development and maintenance.</strike><br />
* <strike>Many SME's have invested in supporting existing OGC standards in their products. They will be forced to choose the standards they support (and can explain), resulting in decreased interoperability, confusion and frustration for clients.</strike><br />
* <strike>Confusing customers with new, overlapping OGC standards will lower the credibility of companies and of OGC, reducing business opportunities.</strike><br />
<br />
== Technical Concerns ==<br />
<br />
* <strike>The Geoservices REST API overlaps in large proportion with existing OGC standards such as WMS, WCS, WFS, WMTS, CSW, with no effort made to reconcile with those standards.</strike><br />
* The standardization of WKT for Spatial reference systems is unfortunately currently quite weak in OGC standards. Geoservices REST API is tied with ESRI's version of WKT, which is not properly specified in the Geoservices REST API documents, and is known to be incompatible with other OGC documents, which will lead to a larger confusion. See the following [http://lists.opengeospatial.org/pipermail/requests/2012-July/000166.html comment] for more details on this issue.<br />
* <strike>The Geoservices REST API is not particularly RESTful - it's a thinly disguised service call, not an address space for RESTful objects that can be operated on.</strike><br />
* At least as far as "imagery" is concerned, OGC standards arguably are substantially more mature, powerful, flexible, and modular then the ESRI "Geoservice REST API" Part 6 (and some design principles suggest that scalability may be hampered as well):<br />
** data model:<br />
*** the ESRI "Geoservice REST API" appears constrained to 2-D imagery, plus optional time stamps. OGC has established a [http://en.wikipedia.org/wiki/Coverage_data unified coverage model] which fully supports n-D spatio-temporal data. It allows use and exchange of coverages between different services, such as [http://en.wikipedia.org/wiki/Web_Coverage_Service WCS], [http://en.wikipedia.org/wiki/Web_Coverage_Processing_Service WCPS], WPS, and SWE.<br />
*** OGC coverages support both regular and irregular grids; the ESRI "Geoservice REST API" supports only regular grids, more specifically: only rectified grids with quadrilateral pixels.<br />
*** the ESRI "Geoservice REST API" lacks support for temporal data; it only offers timestamps, measured in milliseconds; this is inconvenient for users and immediately excludes, e.g., geological dates. OGC has established uniform handling of horizontal, vertical, and temporal coordinate reference systems (CRSs), following a deep consensus process with GIS science and backwards compatible with EPSG. The ESRI "Geoservice REST API" specific way of handling coordinates is not known to support this, thereby excluding appropriate timeseries handling in remote sensing, air traffic, MetOcean, etc.<br />
*** OGC coverages provide a concise, versatile model for supporting different binary formats; the ESRI "Geoservice REST API" supports only very few selected 2-D formats, excluding, e.g., JPEG2000, NetCDF, HDF, etc.<br />
*** the ESRI "Geoservice REST API" lacks a clear model of their data structures, it can be deduced only implicitly from the operation mechanics.<br />
** service model:<br />
*** The ESRI "Geoservice REST API" Part 6 lacks conciseness, thereby opening up ways for implementations that are not interoperable. For developers of alternative implementations this may mean they have to acquire ESRI licenses for finding out the intended behavior.<br />
*** Functionality in the ESRI "Geoservice REST API" appears randomly chosen, with no clear concept visible; this burdens implementers while still leaving holes of functionality. For example, this functionality appears restricted to mapping applications and does not easily extend into other domains.<br />
*** It has been said that the ESRI "Geoservice REST API" can be seen as a "wrapper around OGC W*S" services. This is not true for WCS (and WCPS), at least: the ESRI "Geoservice REST API" Part 6 is too poor in functionality and too different in mechanics to accomplish this.<br />
** In summary, the ESRI "Geoservice REST API" Imaging part is at a technological level where WCS departed from some 5 years ago. Inconciseness of the specification at large will make it difficult for third parties to come up with interoperable implementations. The components making up the ESRI "Geoservice REST API" provide natural blocks assignable to the matching SWGs. As for Part 6 of the ESRI "Geoservice REST API", if to become a standard it needs to be discussed in the WCS.SWG for harmonization, clarification, and improvement.<br />
<br />
== Methodological Concerns ==<br />
<br />
# Ten months after submitting, no public response (nor private to the authors of the comments) has been made to the various comments sent on the OGC Requests mailing list in [[http://lists.opengeospatial.org/pipermail/requests/2012-July/date.html July 2012]] and [[http://lists.opengeospatial.org/pipermail/requests/2012-August/date.html August 2012]] during the 30 day public comments period.<br />
# The Geoservices REST API can not be amended (other than editorial changes in the specification document), because of a requirement of backward compatibility with ESRI implementation. Consequently, the standard is unlikely to improve, or its evolution will be only lead by ESRI.<br />
# OGC standards normally require interoperability experiments and a richer process to ratify a standard such as this one. No explanation has been forthcoming as to why a simplified process is appropriate in this case.<br />
<br />
A response (from Adrian Custer):<br />
<br />
# The OGC is working to release those documents to the public as of 9 May 2013.<br />
# Work on the next version of the document can take any perspective acceptable to those working on the document. (The OGC has no method in place in case two groups want to evolve the document in two different directions.)<br />
# That is not true, the OGC does not require interoperability experiments or some "richer process" for the adoption of a standard; that may be desirable but is not required.<br />
<br />
= Further Reading =<br />
''Please add links to referenced documents, related news stories or blog posts here.''<br />
* Call for comments on GeoServices REST API: http://www.opengeospatial.org/standards/requests/89<br />
* Email archive of OSGeo discussions about GeoServices REST API: http://lists.osgeo.org/pipermail/discuss/2013-May/thread.html<br />
* Adrian Custer's summary of technical issues (and original source of some content in this letter): http://lists.osgeo.org/pipermail/discuss/2013-May/011667.html<br />
* "Is OGC Loosing its way?", letter to OGC Voters, from OGC Interoperability Movement Team Leaders, http://lists.osgeo.org/pipermail/discuss/2013-May/011632.html<br />
<br />
[[Category: OGC]]<br />
[[Category: Standards]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=PgRouting&diff=70710PgRouting2013-05-05T08:32:12Z<p>Dkastl: /* Project Governance */ initial</p>
<hr />
<div>== Basic Project Data ==<br />
*'''Project Name:''' pgRouting<br />
*'''Project Status Condition:''' Stable<br />
*'''Project Web Site:''' http://pgrouting.org<br />
*'''Project Contact:''' Daniel Kastl <project at pgrouting.org><br />
*'''Short Project Description:''' pgRouting adds routing functionality to PostGIS.<br />
<br />
== Project Infrastructure ==<br />
*'''Project Source Code:''' https://github.com/pgrouting/pgrouting<br />
*'''Project Mailing List:''' http://lists.osgeo.org/mailman/listinfo/pgrouting-users<br />
*'''Project Version Control Repository:''' git://github.com/pgRouting/pgrouting.git<br />
*'''Project Bug Tracker:''' https://github.com/pgrouting/pgrouting/issues<br />
*'''Project Feature Request Tracker:''' https://github.com/pgrouting/pgrouting/issues<br />
<br />
== Project Governance ==<br />
*'''Source Code License:''' [http://www.gnu.org/licenses/gpl-2.0.html GNU General Public License, version 2]<br />
*'''Documentation License:''' [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-Share Alike 3.0]<br />
*'''Copyright Assignment Policy:''' All contributions are licensed under the terms of the GNU General Public License, version 2 without explicit assignment<br />
*'''Decision Making Procedure:''' <br />
*'''Coding Standards:''' <br />
*'''Release Procedure:'''<br />
<br />
== Project Deliverables ==<br />
*'''Latest Project Release:'''<br />
<br />
[[Category: OSGeo Labs]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=PgRouting&diff=70709PgRouting2013-05-05T08:26:29Z<p>Dkastl: /* Project Infrastructure */ initial</p>
<hr />
<div>== Basic Project Data ==<br />
*'''Project Name:''' pgRouting<br />
*'''Project Status Condition:''' Stable<br />
*'''Project Web Site:''' http://pgrouting.org<br />
*'''Project Contact:''' Daniel Kastl <project at pgrouting.org><br />
*'''Short Project Description:''' pgRouting adds routing functionality to PostGIS.<br />
<br />
== Project Infrastructure ==<br />
*'''Project Source Code:''' https://github.com/pgrouting/pgrouting<br />
*'''Project Mailing List:''' http://lists.osgeo.org/mailman/listinfo/pgrouting-users<br />
*'''Project Version Control Repository:''' git://github.com/pgRouting/pgrouting.git<br />
*'''Project Bug Tracker:''' https://github.com/pgrouting/pgrouting/issues<br />
*'''Project Feature Request Tracker:''' https://github.com/pgrouting/pgrouting/issues<br />
<br />
== Project Governance ==<br />
*'''Source Code License:'''<br />
*'''Documentation License:'''<br />
*'''Copyright Assignment Policy:'''<br />
*'''Decision Making Procedure:'''<br />
*'''Coding Standards:'''<br />
*'''Release Procedure:'''<br />
<br />
== Project Deliverables ==<br />
*'''Latest Project Release:'''<br />
<br />
[[Category: OSGeo Labs]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=PgRouting&diff=70708PgRouting2013-05-05T08:18:33Z<p>Dkastl: /* Basic Project Data */ initial</p>
<hr />
<div>== Basic Project Data ==<br />
*'''Project Name:''' pgRouting<br />
*'''Project Status Condition:''' Stable<br />
*'''Project Web Site:''' http://pgrouting.org<br />
*'''Project Contact:''' Daniel Kastl <project at pgrouting.org><br />
*'''Short Project Description:''' pgRouting adds routing functionality to PostGIS.<br />
<br />
== Project Infrastructure ==<br />
*'''Project Source Code:'''<br />
*'''Project Mailing List:'''<br />
*'''Project Version Control Repository:'''<br />
*'''Project Bug Tracker:'''<br />
*'''Project Feature Request Tracker:'''<br />
<br />
== Project Governance ==<br />
*'''Source Code License:'''<br />
*'''Documentation License:'''<br />
*'''Copyright Assignment Policy:'''<br />
*'''Decision Making Procedure:'''<br />
*'''Coding Standards:'''<br />
*'''Release Procedure:'''<br />
<br />
== Project Deliverables ==<br />
*'''Latest Project Release:'''<br />
<br />
[[Category: OSGeo Labs]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2013_Ideas&diff=70264Google Summer of Code 2013 Ideas2013-04-08T19:49:05Z<p>Dkastl: /* Guest projects */</p>
<hr />
<div>[[Image:Gsoc-2013-logo-color.jpg|350px|link=http://code.google.com/soc/]] <font size="+3"> @ </font> [[Image:OSGeo_300_127_pixel.png|link=http://www.osgeo.org]]<br />
<br />
-----<br />
* Back to the main OSGeo [[Google Summer of Code 2013]] wiki page.<br />
<br />
* See also ideas from [[Google Summer of Code 2010 Ideas|2010]], [[Google Summer of Code 2011 Ideas|2011]], and [[Google Summer of Code 2012 Ideas|2012]].<br />
-----<br />
<br />
<br />
== OSGeo Google Summer of Code 2013 ==<br />
<br />
The [http://www.osgeo.org Open Source Geospatial Foundation] would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.<br />
<br />
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.<br />
<br />
* '''If you need more information on how to apply you can contact all the mentoring organisations via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])<br />
<br />
* There is a [http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers Google SoC flyer] to look at and post in appropriate places and [http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2013.pdf an OSGeo flavoured one as well].<br />
<br />
* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.<br />
<br />
== Important dates ==<br />
<br />
* [http://www.google-melange.com/gsoc/events/google/gsoc2013 '''The official timeline''']<br />
<br />
<br />
* April 8: Google announces accepted organizations.<br />
: If OSGeo is accepted as an organization for Google Summer of Code, '''start talking to us earlier rather than later.'''<br />
* April 22: '''Student applications open.<br />
: The earlier you start the more probable it is that you will be accepted!'''<br />
: ''There is two way feedback during the application process which really helps you improve and clarify your application before the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''<br />
* May 3: '''Student application deadline.'''<br />
* May 27: Accepted student proposals are announced and Community Bonding Period begins<br />
* June 17: '''Coding begins!'''<br />
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')<br />
* July 29: Mid-term evaluation begins<br />
* September 16-23: '''Pencils down!'''<br />
* September 23-27: Final evaluations<br />
* September 27: Students begin submitting required code samples to Google<br />
* October 1: Final results announced<br />
<br />
<br />
== The ideas pages ==<br />
'''''[Check back often, it's a work in progress]'''''<br />
<br />
<br />
Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:<br />
<br />
=== OSGeo Foundation member projects ===<br />
<br />
[[Image:logo-grass.png|60px|right]]<br />
* [http://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2013 '''GRASS GIS''' 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 wxPython. If you know Python, or want to implement algorithms in C take a look!<br />
<br />
[[Image:logo-qgis.png|60px|right]]<br />
* [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2013 '''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. It is written in C++ and Python.<br />
<br />
[[Image:logo-ossim.png|60px|right]]<br />
* [http://trac.osgeo.org/ossim/wiki/GSoC_2013_Ideas '''OSSIM''' SoC Ideas]: - OSSIM is a powerful suite of geospatial libraries and applications used to process imagery, maps, terrain, and vector data. The software has been under active development since 1996 and is deployed across a number of private, federal and civilian agencies. It is written in C++.<br />
<br />
* [http://trac.osgeo.org/osgeo4w/wiki '''OSGeo4W''']: - OSGeo4W is a binary distribution of a broad set of open source geospatial software for Win32 environments (Windows 7, XP, etc).<br />
[[Image:Logo-osgeo4w-mini.png|60px|right]]<br />
:* ''Idea'': We need to extend support to x64 based platforms to handle larger datasets and circumvent memory restrictions. This is a distribution and packaging project which will involve most/all of OSGeo member projects. (''ed. note: keep in mind that to fulfill GSoC requirements each project must have a majority coding component, so lots of scripting, testing, and Makefiles!'')<br />
<br />
[[Image:logo-gvSIG.png|60px|right]]<br />
* [[GvSIG_GSoC_2013_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.org/web/projects/gvsig-desktop/description2/view?set_language=en Desktop], [http://www.gvsig.org/web/projects/gvsig-mobile/description-2/view?set_language=en PDAs], and [http://gvsigmini.org mobile phones]. The gvSIG project looks for students with Java skills that want to develop new ideas on any of these products.<br />
<br />
[[Image:logo-opticks.png|right]]<br />
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: Opticks is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.<br />
<br />
[[Image:logo-geos.png|60px|right]]<br />
* [http://trac.osgeo.org/geos/wiki/GSoC '''GEOS''' Ideas]: GEOS (Geometry Engine - Open Source) is a C++ port of the JTS Topology Suite (JTS). It includes the OpenGIS Simple Features for SQL spatial predicate functions and spatial operators, as well as specific JTS enhanced topology functions.<br />
<br />
[[Image:logo-geoserver-crop.png|right]]<br />
[[Image:logo-gdal.png|60px|right]]<br />
* [http://live.osgeo.org/en/overview/geoserver_overview.html '''Geoserver'''] is a web server that allows you to serve maps and data from a variety of formats to standard clients such as web browsers and desk top GIS programs. This means that you can store your spatial data in almost any format you prefer but that your users do not need to know anything about GIS data. At the simplest level all they need is a web browser to see your maps exactly as you want. GeoServer is the reference implementation of the Open Geospatial Consortium (OGC) Web Feature Service (WFS) and Web Coverage Service (WCS) standards, as well as a high performance certified compliant Web Map Service (WMS).<br />
:* ''Geoserver will accept one idea, according to the developers' availability. Please contact them to get more information.''<br />
<br />
<!-- moved above for cosmetic reasons [[Image:logo-gdal.png|60px|right]] --><br />
[[Image:logo-postgis.png|60px|right]]<br />
* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: GDAL is a C++ library for reading and writing geospatial data raster and vector formats.<br />
<br />
<!-- moved above for cosmetic reasons [[Image:logo-postgis.png|60px|right]] --><br />
* [http://trac.osgeo.org/postgis/wiki/GoogleSummerCode '''PostGIS''' Ideas]: [http://www.postgis.net PostGIS] spatially enables the popular PostgreSQL object-relational database, allowing it to be used as a back-end database for geographic information systems (GIS) and web-mapping applications.<br />
<br />
<br />
We expect ideas also from [http://live.osgeo.org/en/overview/mapbender_overview.html MapBender], [http://live.osgeo.org/en/overview/zoo-project_overview.html ZOO-Project], [http://live.osgeo.org/en/overview/geomoose_overview.html GeoMOOSE]...<br />
<br />
=== Guest projects ===<br />
<br />
Guest project: <br />
[[Image:Logo-istSOS.png|100px|right]]<br />
* [https://code.google.com/p/istsos/wiki/GSoC_ideas '''istSOS''' Ideas]: [http://code.google.com/p/istsos/ istSOS] (Istituto Scienze della Terra Sensor Observation Service) is an implementation of the Sensor Observation Service (SOS) standard from the Open Geospatial Consortium (OGC). The development of istSOS was started in 2009 in order to provide a simple implementation of the SOS standard for the management, provision and integration of hydro-meteorological data collected in Canton Ticino (Switzerland). istSOS is entirely written in Python.<br />
<br />
[[Image:Pgrouting-logo.png|60px|right]]<br />
* [https://github.com/pgrouting/pgrouting/wiki/GSOC-Ideas '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.<br />
<br />
<br />
Guest students (accepted under OSGeo umbrella):<br />
<br />
[[Image:Logo-mapnik.png|100px|right]]<br />
* [https://github.com/mapnik/mapnik/wiki/GSOC-Ideas '''Mapnik''' Ideas]: [http://mapnik.org/ Mapnik] is a Free Toolkit for developing mapping applications. It’s written in C++ and there are Python bindings to facilitate fast-paced agile development. It can comfortably be used for both desktop and web development, which was something I wanted from the beginning.<br />
<!-- :* ''Mapnik students will be required to apply under OSGeo <strike>or [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2013 OpenStreetMap] umbrella, according to the main topic of their project.</strike>'' (oops, looks like it's just us this time) --><br />
<br />
[[Image:Logo-osm6.png|60px|right]]<br />
* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2013 '''OpenStreetMap''' Ideas]: [http://osm.org/ OSM] is a project aimed squarely at creating and providing free geographic data such as street maps to anyone who wants them. The project was started because most maps you think of as free actually have legal or technical restrictions on their use, holding back people from using them in creative, productive or unexpected ways.<br />
:* ''This year [if we're accepted] OpenStreetMap students will be hosted under OSGeo's GSoC umbrella. Talk to OSM, but apply with us. Begin your proposal description with "OSM: " so we know which way to direct it.''<br />
<br />
[[Image:logo-uDig.png|60px|right]]<br />
* [http://udig.refractions.net/confluence/display/HACK/Summer+of+Code '''uDig''' SoC Ideas]: User-friendly Desktop GIS is a Java application written with the Eclipse RCP framework. The project has a community svn area to host student plug-ins, tutorials cover how to package up a custom application to show off your work.<br />
<br />
== Which project do I choose? ==<br />
<br />
Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.<br />
: View the documents and download the ISO from http://live.osgeo.org<br />
[[File:Osgeolive wordle.png|400px|center]]<br />
<br />
== How to get in contact via mailing lists ==<br />
<br />
Since OSGeo is an umbrella organisation for multiple projects, each project has their own discussion and development mailing lists.<br />
<br />
'''Main OSGeo mailing lists of interest to students:'''<br />
: Please start here, when contacting us for the first time with questions about Google Summer of Code.<br />
<br />
:* OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc)<br />
:* OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)<br />
<br />
Also see the [[Mailing Lists]] page for project specific lists, as well as the longer list at http://lists.osgeo.org.<br />
<br />
<br />
== How to get in contact via IRC ==<br />
<br />
Primary channel:<br />
<br />
* irc://irc.freenode.net/#osgeo (Web based [http://irc.telascience.org/cgi-bin/irc.cgi IRC client], [http://webchat.freenode.net alternative])<br />
<br />
GSoC @ OSGeo inter-project discussions:<br />
<br />
* irc://irc.freenode.net/#osgeo-soc<br />
<br />
Project irc channels:<br />
<br />
* irc://irc.freenode.net/#gdal<br />
* irc://irc.freenode.net/#geoserver<br />
* irc://irc.freenode.net/#geotools<br />
* irc://irc.freenode.net/#grass<br />
* irc://irc.freenode.net/#gvsig<br />
* irc://irc.freenode.net/#mapbuilder<br />
* irc://irc.freenode.net/#mapguide<br />
* irc://irc.freenode.net/#mapnik<br />
* irc://irc.freenode.net/#mapserver<br />
* irc://irc.freenode.net/#openlayers<br />
* irc://irc.freenode.net/#opticks<br />
* irc://irc.freenode.net/#ossimplanet<br />
* irc://irc.freenode.net/#pgrouting-project<br />
* irc://irc.freenode.net/#postgis<br />
* irc://irc.freenode.net/#qgis<br />
* irc://irc.freenode.net/#udig<br />
* irc://irc.oftc.net/#osm-dev<br />
<br />
== Application questions we'll ask you ==<br />
'''''[Provisional]'''''<br />
<br />
* All questions must be answered, ''no exceptions''. Treat this as something between a formal job application and a scholarship application, because that's exactly what it is.<br />
<br />
Name:<br />
<br />
Country:<br />
<br />
School and degree:<br />
<br />
Email:<br />
<br />
Phone:<br />
<br />
OSGeo project(s):<br />
<br />
Title:<br />
(please include the name of the member project as part of<br />
the title, for example: "Gee Whiz Foobar 2001 for QGIS")<br />
<br />
Describe your idea<br />
1. Introduction<br />
2. Background<br />
3. The idea<br />
4. Project plan ('''detailed timeline''': how do you plan to spend your summer?)<br />
5. Future ideas / How can your idea be expanded? <br />
<br />
Explain how your SoC task would benefit the OSGeo member<br />
project and more generally the OSGeo Foundation as a whole:<br />
<br />
Please provide details of general computing experience:<br />
(operating systems you use on a day-to-day basis, languages you<br />
could write a program in, hardware, networking experience, etc.)<br />
<br />
Please provide details of previous GIS experience:<br />
<br />
Please provide details of any previous involvement with<br />
GIS programming and other software programming:<br />
<br />
Please tell us why you are interested in GIS and open<br />
source software:<br />
<br />
Please tell us why you are interested in working for OSGeo<br />
and the software project you have selected:<br />
<br />
Please tell us why you are interested in your specific<br />
coding project:<br />
<br />
Would your application contribute to your ongoing studies/<br />
degree? If so, how?<br />
<br />
Please explain how you intend to continue being an active<br />
member of your project and/or OSGeo AFTER the summer is over:<br />
<br />
Do you understand this is a serious commitment, equivalent<br />
to a full-time paid summer internship or summer job?<br />
<br />
Do you have any known time conflicts during the official coding<br />
period? (June 17 to Sept. 27)<br />
<br />
== What to expect during the summer ==<br />
<br />
* A group of past GSoC students, mentors, and Googlers have prepared this short book just for you:<br />
: [http://google-opensource.blogspot.com/2011/02/flip-bits-not-burgers-student-guide.html Flip bits not Burgers: The Student's Guide to the Summer of Code] -- READ THIS eBOOK<br />
<br />
<br />
=== Be prepared to be in constant communication with your mentors and project ===<br />
<br />
You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to integrate you into the developer community, so you should get involved with them from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you in case of problems, like making sure you get paid.<br />
<br />
University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.<br />
<br />
=== Weekly reports ===<br />
<br />
Yes, every week we expect to see a report posted to the soc@osgeo mailing list that at least answers the following questions:<br />
<br />
# What did you get done this week?<br />
# What do you plan on doing next week?<br />
# Are you blocked on anything?<br />
<br />
These questions BTW are the same as are used in real-work, when developing with the <br />
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process]. ;)<br />
<br />
If you want, feel free to write *more*. But three sentences is the bare minimum. *IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME*, if you don't send this email your mentors will start to get twitchy, and *especially* if they don't get any responses to their emails / don't see you in IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's cool. We have all studied at some point, just tell us about it up front, be honest, and we'll work around it. If you don't know how to proceed and your mentor isn't answering *definitely* tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)<br />
<br />
Last year this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.<br />
<br />
<br />
=== Wiki page and blogs ===<br />
<br />
In addition to weekly reports we require you to maintain a wiki or blog page for your project. You should store your weekly reports there and add other information, like how to compile and test your program. If applicable add screenshots and other nice info.<br />
<br />
Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this.<br />
<br />
We plan to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.<br />
<br />
Final reports from those blogs and wiki pages will be collected into a OSGeoofcode posting about what everyone did during the summer, ensuring you long lasting fame and fortune. (''Or failing that, a bit of public press, a bit of cash from Google, and a lot of gratitude and kudos from us, your peers.'')<br />
<br />
<br />
[Back to [[Google Summer of Code 2013]] @ OSGeo]<br />
[[Category: Google Summer of Code]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=File:Pgrouting-logo.png&diff=70262File:Pgrouting-logo.png2013-04-08T19:46:41Z<p>Dkastl: pgRouting Logo</p>
<hr />
<div>pgRouting Logo</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2012_Ideas&diff=60786Google Summer of Code 2012 Ideas2012-02-20T01:01:08Z<p>Dkastl: /* The ideas pages */ enabled routing for 2012</p>
<hr />
<div>[[Image:Gsoc-2012-logo-color.png|350px|link=http://code.google.com/soc/]] <font size="+3"> @ </font> [[Image:OSGeo_300_127_pixel.png|link=http://www.osgeo.org]]<br />
<br />
-----<br />
* Back to the main OSGeo [[Google Summer of Code 2012]] wiki page.<br />
<br />
* See also ideas from [[Google Summer of Code 2010 Ideas|2010]] and [[Google Summer of Code 2011 Ideas|2011]]<br />
-----<br />
<br />
=OSGeo Google Summer of Code 2012=<br />
<br />
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.<br />
<br />
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.<br />
<br />
'''If you need more information on how to apply you can contact all the mentoring organisations via soc at lists.osgeo.org'''<br />
<br />
* There is a [http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers Google SoC flyer] to look at and post in appropriate places and [http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/ an OSGeo flavoured one as well] (TODO: update to 2012).<br />
<br />
* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.<br />
<br />
=What to expect during the summer?=<br />
<br />
* A group of past GSoC students, mentors, and Googlers have prepared this short book just for you: [http://google-opensource.blogspot.co.nz/2011/02/flip-bits-not-burgers-student-guide.html Flip bits not Burgers: The Student's Guide to the Summer of Code] -- READ THIS eBOOK<br />
<br />
<br />
==Be prepared to be in constant communication with your mentors and project==<br />
<br />
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.<br />
<br />
<br />
==Weekly reports==<br />
Yes, every week we expect to see a report posted to the soc@osgeo mailing list that at least answers the following questions:<br />
# What did you get done this week?<br />
# What do you plan on doing next week?<br />
# Are you blocked on anything?<br />
These questions BTW are the same as are used in real-work, when developing with the <br />
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process]. ;)<br />
<br />
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 ;)<br />
<br />
Last year this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.<br />
<br />
==Wiki page and blogs==<br />
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.<br />
<br />
Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this.<br />
<br />
=Timeline=<br />
<br />
* '''[http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2012/faqs#timeline The official timeline]'''<br />
<br />
<br />
<!-- {{done}} --><br />
* March 16: Google announces accepted organizations. If OSGeo is accepted as an organization for Google Summer of Code, start talking to us earlier rather than later.<br />
* '''March 26''': Student applications open. The earlier you start the more probable it is that you will be accepted! There is two way feedback during the application process which really helps you improve and clarify your application before the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.<br />
* '''April 6''': Student application deadline.<br />
* April 23: Accepted student proposals are announced.<br />
* '''May 21''': Coding begins! (you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. ''This must be reflected in your application timeline'')<br />
* July 13: Mid-term evaluation.<br />
* '''August 13''': Pencils down!<br />
* August 24: Final evaluation deadline<br />
* August 27: Final results announced<br />
* August 31: Students begin submitting required code samples to Google<br />
<br />
= The ideas pages =<br />
<br />
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: <br />
<br />
<!-- * [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. --><br />
<br />
* [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!<br />
<br />
<!-- * [http://www.qgis.org/wiki/Google_Summer_of_Code_2011 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. --><br />
<br />
<!-- * [http://udig.refractions.net/confluence/display/HACK/Summer+of+Code uDig Summer of Code]: 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. --><br />
<br />
<!-- * [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. --><br />
<br />
* [[OpenRouter 2012 SOC Ideas|OpenRouter/pgRouting 2012 SOC Ideas]]: OpenRouter/pgRouting is a couple of projects that are building routing and driving direction libraries and applications that can be integrated with other applications.<br />
<br />
<!-- *OSSIM [http://web.me.com/epiesasha/PlanetSasha/2010Project.html Py-OSSIM]: - ossim-swig-python to generate code to call ossim from python --><br />
<br />
<!-- * [[OSGeo Cartographic Engine#Ideas_for_Summer_of_Code_2010_Project|Cartographic Engine project ideas built on Mapnik]]: Refining much needed high quality hardcopy output tools that encourage collaboration. Built on Mapnik, applications like QGIS, GRASS, MapServer, etc. can output using these features. Focused initially on building specs that support Mapnik as the engine, but that could be applied generally across OSGeo projects as well. --><br />
<br />
<!-- * [http://www.spatialytics.org/google-summer-of-code-2010-ideas/ Spatialytics.org GSoC 2010 Ideas]: Spatialytics.org is the new home of the three open source Geospatial BI projects (GeoKettle, GeoMondrian and SOLAPLayers). Geospatial Business Intelligence (BI) tools, such as spatial ETL (Extract, Transform and Load), geo-analytical dashboards and Spatial On-Line Analytical Processing (SOLAP) allow decision-makers to rapidly analyze large amount of data at different levels of time, geography and detail in order to make better decisions. --><br />
<br />
<!-- *<strike>MapWindow GIS</strike>: '''MapWindow will not participate in the Summer of Code 2011'''. [http://www.mapwindow.org MapWindow] is a free, extensible, geographic information system (GIS) that can be used as an alternative desktop GIS, to distribute data to others, to develop and distribute custom spatial data analyses, written in .NET (C++, C#, VB.NET). If you're a talented VB.Net, C#, or C++ programmer, you could be the perfect fit to work on this project. We have a couple of ideas that could be done over the summer; feel free to suggest your own ideas or plug-ins as well. --><br />
<br />
<!-- * [[MapServer 2011 SOC Ideas|MapServer GSoC Ideas]]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web. --><br />
<br />
<!-- * [[Live GIS Disc GSoC 2011|OSGeo Live]] is a stack of 35+ of the best GeoSpatial Open Source packages bundled as a LiveDVD and Virtual Machine on top an Xubuntu linux ditribution. There are opportunities to address packaging and cross project quality control through application of systematic testing processes. Through this project, developers will gain a broad understanding of the full GeoSpatial Open Source stack. --><br />
<br />
<!-- * [[GvSIG GSoC 2011 Ideas|gvSIG]] is the free GIS project developed by the gvSIG Association. gvSIG is at this time a group of software developments for [http://www.gvsig.org/web/projects/gvsig-desktop/description2/view?set_language=en Desktop],[http://www.gvsig.org/web/projects/gvsig-mobile/description-2/view?set_language=en PDAs] and [http://gvsigmini.org mobile phones]. --><br />
<br />
<!-- * [http://geoserver.org/display/GEOS/Summer+of+Code+2011 GeoServer] is an open source software server written in Java that allows users to share and edit geospatial data. Designed for interoperability, it publishes data from any major spatial data source using open standards. --><br />
<br />
<!-- * [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code Opticks Ideas]: Opticks is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do. --><br />
<br />
<!-- * [http://trac.osgeo.org/postgis/wiki/WKTRasterGSoC PostGIS raster Ideas] PostGIS raster is the raster side of PostGIS. It allows to store, manipulate and do analysis of raster data in the PostgreSQL/PostGIS spatial database.--><br />
<br />
= Application Template =<br />
<br />
(All questions must be answered)<br />
<br />
Name:<br />
<br />
Country:<br />
<br />
School and degree:<br />
<br />
Email:<br />
<br />
Phone:<br />
<br />
OSGeo project(s):<br />
<br />
Title:<br />
(please include the name of the member project as part of<br />
the title, for example: "Gee Whiz Foobar 2001 for QGIS")<br />
<br />
Describe your idea<br />
1. Introduction<br />
2. Background<br />
3. The idea<br />
4. Project plan (detailed timeline: how do you plan to spend your summer?)<br />
5. Future ideas / How can your idea be expanded? <br />
<br />
Explain how your SoC task would benefit the OSGeo member<br />
project and more generally the OSGeo Foundation as a whole:<br />
<br />
Please provide details of general computing experience:<br />
(operating systems you use on a day-to-day basis, languages you<br />
could write a program in, hardware, networking experience, etc.)<br />
<br />
Please provide details of previous GIS experience:<br />
<br />
Please provide details of any previous involvement with<br />
GIS programming and other software programming:<br />
<br />
Please tell us why you are interested in GIS and open<br />
source software:<br />
<br />
Please tell us why you are interested in working for OSGeo<br />
and the software project you have selected:<br />
<br />
Please tell us why you are interested in your specific<br />
coding project:<br />
<br />
Would your application contribute to your ongoing studies/<br />
degree? If so, how?<br />
<br />
Please explain how you intend to continue being an active<br />
member of your project and/or OSGeo AFTER the summer is over:<br />
<br />
Do you understand this is a serious commitment, equivalent<br />
to a full-time paid summer internship or summer job?<br />
<br />
= What is the main public mailing list for your organization? =<br />
Since OSGeo is an umbrella organisation for multiple projects, each project has their own discussion and development mailing lists.<br />
<br />
'''Main OSGeo mailing lists of interest to students.'''<br />
<br />
Please start here, when contacting us for the first time with questions about Google Summer of Code.<br />
<br />
* OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc)<br />
* OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)<br />
<br />
Also see the [[Mailing Lists]] page for project specific lists.<br />
<br />
<br />
= What is the main IRC channel for your organization? =<br />
<br />
irc://irc.freenode.net/#osgeo (Web based [http://irc.telascience.org/cgi-bin/irc.cgi IRC client], [http://webchat.freenode.net alternative)<br />
<br />
Project irc channels:<br />
<br />
* irc://irc.freenode.net/#gdal<br />
* irc://irc.freenode.net/#geoserver<br />
* irc://irc.freenode.net/#geotools<br />
* irc://irc.freenode.net/#grass<br />
* irc://irc.freenode.net/#gvsig<br />
* irc://irc.freenode.net/#mapbuilder<br />
* irc://irc.freenode.net/#mapguide<br />
* irc://irc.freenode.net/#mapnik<br />
* irc://irc.freenode.net/#mapserver<br />
* irc://irc.freenode.net/#openlayers<br />
* irc://irc.freenode.net/#opticks<br />
* irc://irc.freenode.net/#ossimplanet<br />
* irc://irc.freenode.net/#pgrouting-project<br />
* irc://irc.freenode.net/#postgis<br />
* irc://irc.freenode.net/#qgis<br />
* irc://irc.freenode.net/#udig<br />
<br />
<br />
<br />
[Back to [[Google Summer of Code 2012]] @ OSGeo]<br />
<br />
<br />
[[Category: Google Summer of Code]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=OpenRouter_2012_SOC_Ideas&diff=60785OpenRouter 2012 SOC Ideas2012-02-20T01:00:59Z<p>Dkastl: initial commit</p>
<hr />
<div>* Back to the main OSGeo [[Google Summer of Code 2012]] wiki page. <br />
* Back to the main OSGeo [[Google Summer of Code 2012 Ideas]] wiki page.<br />
<br />
= OpenRouter/pgRouting 2012 SOC Ideas =<br />
<br />
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/pgRouting. Our current efforts are based on the following projects: <br />
<br />
* [http://www.pgrouting.org/ pgRouting]. This routing library provides routing functionality to PostGIS/PostgreSQL.<br />
* [http://opengraphrouter.sourceforge.net/ OpenGraphRouter]. This project is a C++ library and tools to build a commercial grade routing engine.<br />
<br />
You can find the source code, tutorials, the project mailing list and various other information at the links above. <br />
<br />
To give you an idea about possible SoC projects, here are some suggestions: <br />
<br />
== pgRouting related ideas ==<br />
<br />
Read a list of possible improvements on the pgRouting project website <br />
<br />
* http://www.pgrouting.org/rfc/index.html<br />
* https://github.com/pgRouting/website/issues<br />
<br />
See the project ideas of the last year summer of code: <br />
<br />
* [[OpenRouter_2010_SOC_Ideas|pgRouting 2010 SOC Ideas]]<br />
* [[OpenRouter_2011_SOC_Ideas|pgRouting 2011 SOC Ideas]]<br />
<br />
== OpenGraphRouter related ideas ==<br />
<br />
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. <br />
<br />
See the project ideas of the last year summer of code: <br />
<br />
* [[OpenRouter_2010_SOC_Ideas|OpenRouter 2011 SOC Ideas]]<br />
<br />
== Routing for Android ==<br />
<br />
Port OpenRouter, or other suitable routing library (e.g. gosmore, navit) to Android mobile platform (Java or NDK). Possible mentor or co-mentor: Jaak Laineste (jaak (at) nutiteq (dot) com, developer of http://www.nutiteq.com/android-mapping-api-sdk<br />
<br />
== Lots of other options ==<br />
<br />
There are a lot of other possibilities that we would be happy to discuss with any students interested. Best you contact us on the pgRouting mailing list:<br />
<br />
* http://lists.osgeo.org/mailman/listinfo/pgrouting-dev<br />
<br />
= Mentor Candidates =<br />
<br />
The following individuals are potentially willing to serve as OpenRouter/pgRouting mentors or co-mentors. <br />
<br />
* Daniel Kastl daniel.kastl (at) georepublic (dot) de<br />
* Stephen Woodbridge woodbri (at) swoodbridge (dot) com <br />
<br />
[[Category:Google_Summer_of_Code]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2011_Code_Sprint&diff=57321FOSS4G 2011 Code Sprint2011-09-15T04:05:14Z<p>Dkastl: /* Additional Interested People */</p>
<hr />
<div>== Code Sprint - what's that? ==<br />
<br />
[[Image:Code-sprint-foss4g2010.jpg|thumb|400px|Code-sprint-foss4g2010.jpg]] A code sprint is about getting a group together to work on Open Source software, sitting around a table and sharing ideas. It's not just about writing code, as you know a project has many needs including documentation, testing, and providing feedback. What a better way to give feedback and give back to the project that you love than to spend a day with the project's developers. There are roles needed to be filled, no matter what your expertise. <br />
<br />
With such a short timeframe (one day) you should probably use this page to set a specific goal for your project. But don't worry, if all you get done is actually sitting at the same table with the project's developers and talking about the next release, that is also great&nbsp;:) <br />
<br />
== Venue ==<br />
<br />
*Date: '''Saturday September 17th, 2011''' (the day after the conference). <br />
*Time: '''9am-5pm'''&nbsp; ([http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&month=9&day=17&hour=15&min=0&sec=0 timeandate])&nbsp; <br />
*'''Where:''' [http://www.tivoli.org/tivoli/ Tivoli Student Union building] (a former brewery), Auraria Campus<br />
<br />
[[Image:Tivoli-logo.jpg|150px|Tivoli-logo.jpg]] <br />
<br />
Tivoli Student Union<br />
900 Auraria Parkway<br />
Denver, CO<br />
'''[http://www.openstreetmap.org/?lat=39.745249&lon=-105.005806&zoom=18&layers=M OSM map]''' - '''[http://g.co/maps/c9eb Google map ]''' - '''[http://maps.google.com/maps?q=tivoli,+denver,+co&hl=en&ll=39.7464,-105.001415&spn=0.002401,0.006866&sll=37.0625,-95.677068&sspn=40.409448,79.013672&vpsrc=0&t=h&z=18&layer=c&cbll=39.7464,-105.001415&panoid=DZVzTs0PjLhWerTJvFchhA&cbp=12,251.13,,0,-2.25 street view (distant tower in center)]'''<br />
<br />
*'''Rooms: (each room has a 60-70 person capacity)''' <br />
**room 440/540 (bilevel) <br />
**room 640<br />
<br />
== What to Bring ==<br />
<br />
*power bars (only outlets for 30 computers exist)<br />
<br />
== How to get there from the Sheraton ==<br />
<br />
The easiest way to get there from the Sheraton is to catch the free shuttle bus along 16th Street to Larimer, then it's about a half mile walk from there (7-10 minutes) - just take a left on Larimer and keep going straight into the campus. More detail to come shortly on how to get to the exact rooms etc. <br />
<br />
== Sponsor ==<br />
<br />
Please! contact organizers: Rafael Moreno, or [[Jeff McKenna]] <br />
<br />
== Questions/Comments/Ideas ==<br />
<br />
*ask on the foss4g2011 mailing list ([http://lists.osgeo.org/mailman/listinfo/foss4g2011 subscribe])<br />
<br />
== Additional Interested People ==<br />
<br />
The following people are potentially interested in participating in sprinting activities though have not yet established a Workgroup. <br />
<br />
*name:project<br />
<br />
*[[Mike Adair]] <br />
*[[User:Olt|Oliver Tonnhofer]] I like to work on tiling stuff (MapProxy) or Python geo APIs (Shapely, imposm).<br />
*Morten Lindegaard<br />
<br />
= Workgroups =<br />
<br />
To participate, copy a project skeleton and start a section below for your project. <br />
<br />
== Project-name ==<br />
<br />
'''Attending:''' <br />
<br />
*user <br />
*user<br />
<br />
'''Goals:''' <br />
<br />
*your goals<br />
<br />
<br><br />
<br />
== Potlatch2 I18N/L10N ==<br />
<br />
'''Attending:''' <br />
<br />
*[[User:Miurahr|Hiroshi Miura]] <br />
*<br />
<br />
'''Goals:''' <br />
<br />
*I18N/L10N complete<br />
*Japanese translations<br />
<br />
<br><br />
<br />
== GeoExt ==<br />
<br />
'''Attending:''' <br />
<br />
*[[User:Rdewit|Roald de Wit]] <br />
*[[User:Mpriour|Matt Priour]] <br />
*...<br />
<br />
'''Goals:''' <br />
<br />
*Getting GeoExt to work with ExtJS4<br />
<br />
== MapQuery ==<br />
<br />
'''Attending:''' <br />
<br />
*[[User:Vmische|Volker Mische]] <br />
*[[User:Stvn|Steven M. Ottens]] <br />
*[[User:H0st1le|Justin Penka]]<br />
<br />
'''Goals:''' <br />
<br />
*Making MapQUery more awesome <br />
*Talk to OpenLayers 3 people about the future<br />
<br />
== PostGIS ==<br />
<br />
'''Attending:''' <br />
<br />
*Paul Ramsey <br />
*Pierre Racine <br />
*David Bitner <br />
*Brian Hamlin <br />
*Bborie Park <br />
*Leo Hsu <br />
*Regina Obe <br />
*Olivier Courtin <br />
*you?<br />
<br />
'''Goals:''' <br />
<br />
*Close bugs and triage for 2.0 release<br />
<br />
== Opticks ==<br />
<br />
'''Attending:''' <br />
<br />
*Kip Streithorst <br />
*Trevor Clarke <br />
*Michael Considine<br />
<br />
'''Goals:''' <br />
<br />
*Enhance scripting support. See [http://opticks.org/confluence/x/6IBl this page] for more information. <br />
*TBD<br />
<br />
'''Possible:''' <br />
<br />
*Work with OSSIM developers to apply OSSIM patches developed by the Opticks developers. <br />
*Co-registration/image-to-image registration tool to replace Data Fusion <br />
*Open source the Opticks unit tests <br />
*Misc small enhancements and bug fixes <br />
*Add georectification and orthorectification <br />
*Prototype an OpenGL 2.1 based rendering pipeline <br />
*Fix AEB installation to support auto-elevation, no need to start-up app with admin privs <br />
*automatically restart Opticks to complete installation and uninstallation <br />
*replace band math with raster math <br />
*Prototype a multithreaded raster algorithm library <br />
*Prototype am OpenCL/CUDA raster algorithm library<br />
<br />
'''Collaborate:''' <br />
<br />
*OSSIM<br />
<br />
== Mapnik ==<br />
<br />
I ([[User:Springmeyer|Dane Springmeyer]]) can't make the code sprint (leaving the night of the 16th), so catch me during the conference to chat Mapnik coding. <br />
<br />
== OSGeo edu ==<br />
<br />
'''Attending:''' <br />
<br />
*Ari Jolma <br />
*[[User:Wildintellect|Alex Mandel]]<br />
*[[User:Danielkastl|Daniel Kastl]]<br />
<br />
'''Goals:''' <br />
<br />
Possible things to do: <br />
<br />
*Set up a repository for joint development of edu materials and kick-start a few projects <br />
*Gather/organize materials for Desktop GIS or Web GIS workbooks <br />
*Investigate Multi-lingual CMS options<br />
<br />
== MapServer ==<br />
<br />
'''Attending:''' <br />
<br />
*Michael Smith <br />
*[[Jeff McKenna]] <br />
*[[Thomas Bonfort]] <br />
*[[User:Schpidi|Stephan Meissl]] <br />
*[[User:Fschindler|Fabian Schindler]] <br />
*[[User:Dmorissette|Daniel Morissette]] <br />
*[[User:Lagerratrobe|Roger Andre]] <br />
*[[User:Timheuer|Tim-Hinnerk Heuer]] <br />
*[[User:hammj|Jeff Hamm]]<br />
easing MapServer upgrade process (from 5 to 6 or possibly beyond) with XML/XSLT transformation. Please view&nbsp;[https://docs.google.com/document/d/1M1GFhgJdoB7_RDOCEmXf1GUg-fKtHTgzqmVh6lM-S8w/edit?hl=en_US docs.google.com/document/d/1M1GFhgJdoB7_RDOCEmXf1GUg-fKtHTgzqmVh6lM-S8w/edit]&nbsp;for details.<br />
*[[User:Panzel|Phil Anzel]]<br />
== libLAS / PDAL ==<br />
<br />
'''Attending:''' <br />
<br />
*Michael Smith <br />
*Howard butler<br />
*mpg<br />
<br />
== GeoMOOSE ==<br />
<br />
'''Attending:''' <br />
<br />
*Brian Fischer <br />
*Bob Basques <br />
*Jim Klassen <br />
*Eli Adam <br />
*Dan "Ducky" Little <br />
*Brent Fraser <br />
*you?<br />
<br />
'''Goals:''' <br />
<br />
*Testing and bug fixes for 2.6 release <br />
*Documentation<br />
<br />
== ZOO-Project ==<br />
<br />
'''Attending:''' <br />
<br />
*Nicolas Bozon <br />
*[[User:Djay|Gérald Fenoy]]<br />
*Luca Delucchi<br />
<br />
<br><br />
<br />
== uDig ==<br />
<br />
'''Attending:''' <br />
<br />
*[[User:Jive|Jody Garnett]] <br />
*[[User:Kengu|Kenneth Gulbrandsøy]] (IRC)<br />
<br />
'''Goals:''' <br />
<br />
*TBD<br />
<br />
'''Possible:''' <br />
<br />
*roll out CDO and a bit of QA on EMF goodness <br />
*migrate user guide to help plugin (since Eclipse has a Wiki Editor that supports textile) <br />
*refactor to *eu.udig* and make a verison release <br />
*GeoTools as OSGi (no more net.refractions.udig.libs) - see GeoTools below as this would require collaborative effort<br />
<br />
== GeoTools ==<br />
<br />
'''Attending:''' <br />
<br />
*[[User:Jive|Jody Garnett]]<br />
<br />
'''Goals:''' <br />
<br />
*TBD<br />
<br />
'''Possible:''' <br />
<br />
*Implement Query/Join for more than just JDBC-NG code <br />
*Get OSGi bundle information sorted (collaborate with downstream applications ) <br />
*Set up new developers <br />
*Major Bug stomp <br />
*Technical Debt (FunctioName details; Remove old Filter code from test cases etc...)<br />
<br />
'''Collaboration:''' <br />
<br />
*uDig: Collaborate on OSGi rollout (ie Equinox testing) <br />
*GeoServer: Collaborate on OSGi rollout (ie Spring testing) <br />
*Zoo-Project: collaborate on WPS Client testing?<br />
<br />
== 52North-WPS ==<br />
<br />
'''Attending:''' <br />
<br />
*Bastian Schäffer <br />
*Benjamin Pross<br />
<br />
'''Goals:''' <br />
<br />
*Open Disucssion about technical aspects <br />
*Open Disucssion about use cases<br />
<br />
== GRASS GIS ==<br />
<br />
'''Attending:''' <br />
<br />
*Luca Delucchi<br />
<br />
'''Goals:''' <br />
<br />
*Testing GRASS 7 scripts <br />
*Closing some Python bugs<br />
*Italian translation <br />
<br />
== GeoHex ==<br />
<br />
GeoHex is a hexagonal geo-coding system created by sa2sa.<br />
https://sites.google.com/site/geohexdocs/<br />
<br />
'''Attending:''' <br />
<br />
*[[User:Hal_sk|Hal Seki]] <br />
<br />
'''Goals:''' <br />
<br />
*Implement geohex-gem version 3.<br />
<br />
'''Possible:''' <br />
<br />
*Implement other language libraries.<br />
*Make a cool demo app using geohex.<br />
<br />
<br />
<br><br />
<br />
<br />
[[Category:FOSS4G2011]] [[Category:FOSS4G]] [[Category:Code_Sprints]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2011_Code_Sprint&diff=57320FOSS4G 2011 Code Sprint2011-09-15T04:04:54Z<p>Dkastl: /* OSGeo edu */</p>
<hr />
<div>== Code Sprint - what's that? ==<br />
<br />
[[Image:Code-sprint-foss4g2010.jpg|thumb|400px|Code-sprint-foss4g2010.jpg]] A code sprint is about getting a group together to work on Open Source software, sitting around a table and sharing ideas. It's not just about writing code, as you know a project has many needs including documentation, testing, and providing feedback. What a better way to give feedback and give back to the project that you love than to spend a day with the project's developers. There are roles needed to be filled, no matter what your expertise. <br />
<br />
With such a short timeframe (one day) you should probably use this page to set a specific goal for your project. But don't worry, if all you get done is actually sitting at the same table with the project's developers and talking about the next release, that is also great&nbsp;:) <br />
<br />
== Venue ==<br />
<br />
*Date: '''Saturday September 17th, 2011''' (the day after the conference). <br />
*Time: '''9am-5pm'''&nbsp; ([http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&month=9&day=17&hour=15&min=0&sec=0 timeandate])&nbsp; <br />
*'''Where:''' [http://www.tivoli.org/tivoli/ Tivoli Student Union building] (a former brewery), Auraria Campus<br />
<br />
[[Image:Tivoli-logo.jpg|150px|Tivoli-logo.jpg]] <br />
<br />
Tivoli Student Union<br />
900 Auraria Parkway<br />
Denver, CO<br />
'''[http://www.openstreetmap.org/?lat=39.745249&lon=-105.005806&zoom=18&layers=M OSM map]''' - '''[http://g.co/maps/c9eb Google map ]''' - '''[http://maps.google.com/maps?q=tivoli,+denver,+co&hl=en&ll=39.7464,-105.001415&spn=0.002401,0.006866&sll=37.0625,-95.677068&sspn=40.409448,79.013672&vpsrc=0&t=h&z=18&layer=c&cbll=39.7464,-105.001415&panoid=DZVzTs0PjLhWerTJvFchhA&cbp=12,251.13,,0,-2.25 street view (distant tower in center)]'''<br />
<br />
*'''Rooms: (each room has a 60-70 person capacity)''' <br />
**room 440/540 (bilevel) <br />
**room 640<br />
<br />
== What to Bring ==<br />
<br />
*power bars (only outlets for 30 computers exist)<br />
<br />
== How to get there from the Sheraton ==<br />
<br />
The easiest way to get there from the Sheraton is to catch the free shuttle bus along 16th Street to Larimer, then it's about a half mile walk from there (7-10 minutes) - just take a left on Larimer and keep going straight into the campus. More detail to come shortly on how to get to the exact rooms etc. <br />
<br />
== Sponsor ==<br />
<br />
Please! contact organizers: Rafael Moreno, or [[Jeff McKenna]] <br />
<br />
== Questions/Comments/Ideas ==<br />
<br />
*ask on the foss4g2011 mailing list ([http://lists.osgeo.org/mailman/listinfo/foss4g2011 subscribe])<br />
<br />
== Additional Interested People ==<br />
<br />
The following people are potentially interested in participating in sprinting activities though have not yet established a Workgroup. <br />
<br />
*name:project<br />
<br />
*[[Daniel Kastl]] <br />
*Haruyuki Seki <br />
*[[Mike Adair]] <br />
*[[User:Olt|Oliver Tonnhofer]] I like to work on tiling stuff (MapProxy) or Python geo APIs (Shapely, imposm).<br />
*Morten Lindegaard<br />
<br />
= Workgroups =<br />
<br />
To participate, copy a project skeleton and start a section below for your project. <br />
<br />
== Project-name ==<br />
<br />
'''Attending:''' <br />
<br />
*user <br />
*user<br />
<br />
'''Goals:''' <br />
<br />
*your goals<br />
<br />
<br><br />
<br />
== Potlatch2 I18N/L10N ==<br />
<br />
'''Attending:''' <br />
<br />
*[[User:Miurahr|Hiroshi Miura]] <br />
*<br />
<br />
'''Goals:''' <br />
<br />
*I18N/L10N complete<br />
*Japanese translations<br />
<br />
<br><br />
<br />
== GeoExt ==<br />
<br />
'''Attending:''' <br />
<br />
*[[User:Rdewit|Roald de Wit]] <br />
*[[User:Mpriour|Matt Priour]] <br />
*...<br />
<br />
'''Goals:''' <br />
<br />
*Getting GeoExt to work with ExtJS4<br />
<br />
== MapQuery ==<br />
<br />
'''Attending:''' <br />
<br />
*[[User:Vmische|Volker Mische]] <br />
*[[User:Stvn|Steven M. Ottens]] <br />
*[[User:H0st1le|Justin Penka]]<br />
<br />
'''Goals:''' <br />
<br />
*Making MapQUery more awesome <br />
*Talk to OpenLayers 3 people about the future<br />
<br />
== PostGIS ==<br />
<br />
'''Attending:''' <br />
<br />
*Paul Ramsey <br />
*Pierre Racine <br />
*David Bitner <br />
*Brian Hamlin <br />
*Bborie Park <br />
*Leo Hsu <br />
*Regina Obe <br />
*Olivier Courtin <br />
*you?<br />
<br />
'''Goals:''' <br />
<br />
*Close bugs and triage for 2.0 release<br />
<br />
== Opticks ==<br />
<br />
'''Attending:''' <br />
<br />
*Kip Streithorst <br />
*Trevor Clarke <br />
*Michael Considine<br />
<br />
'''Goals:''' <br />
<br />
*Enhance scripting support. See [http://opticks.org/confluence/x/6IBl this page] for more information. <br />
*TBD<br />
<br />
'''Possible:''' <br />
<br />
*Work with OSSIM developers to apply OSSIM patches developed by the Opticks developers. <br />
*Co-registration/image-to-image registration tool to replace Data Fusion <br />
*Open source the Opticks unit tests <br />
*Misc small enhancements and bug fixes <br />
*Add georectification and orthorectification <br />
*Prototype an OpenGL 2.1 based rendering pipeline <br />
*Fix AEB installation to support auto-elevation, no need to start-up app with admin privs <br />
*automatically restart Opticks to complete installation and uninstallation <br />
*replace band math with raster math <br />
*Prototype a multithreaded raster algorithm library <br />
*Prototype am OpenCL/CUDA raster algorithm library<br />
<br />
'''Collaborate:''' <br />
<br />
*OSSIM<br />
<br />
== Mapnik ==<br />
<br />
I ([[User:Springmeyer|Dane Springmeyer]]) can't make the code sprint (leaving the night of the 16th), so catch me during the conference to chat Mapnik coding. <br />
<br />
== OSGeo edu ==<br />
<br />
'''Attending:''' <br />
<br />
*Ari Jolma <br />
*[[User:Wildintellect|Alex Mandel]]<br />
*[[User:Danielkastl|Daniel Kastl]]<br />
<br />
'''Goals:''' <br />
<br />
Possible things to do: <br />
<br />
*Set up a repository for joint development of edu materials and kick-start a few projects <br />
*Gather/organize materials for Desktop GIS or Web GIS workbooks <br />
*Investigate Multi-lingual CMS options<br />
<br />
== MapServer ==<br />
<br />
'''Attending:''' <br />
<br />
*Michael Smith <br />
*[[Jeff McKenna]] <br />
*[[Thomas Bonfort]] <br />
*[[User:Schpidi|Stephan Meissl]] <br />
*[[User:Fschindler|Fabian Schindler]] <br />
*[[User:Dmorissette|Daniel Morissette]] <br />
*[[User:Lagerratrobe|Roger Andre]] <br />
*[[User:Timheuer|Tim-Hinnerk Heuer]] <br />
*[[User:hammj|Jeff Hamm]]<br />
easing MapServer upgrade process (from 5 to 6 or possibly beyond) with XML/XSLT transformation. Please view&nbsp;[https://docs.google.com/document/d/1M1GFhgJdoB7_RDOCEmXf1GUg-fKtHTgzqmVh6lM-S8w/edit?hl=en_US docs.google.com/document/d/1M1GFhgJdoB7_RDOCEmXf1GUg-fKtHTgzqmVh6lM-S8w/edit]&nbsp;for details.<br />
*[[User:Panzel|Phil Anzel]]<br />
== libLAS / PDAL ==<br />
<br />
'''Attending:''' <br />
<br />
*Michael Smith <br />
*Howard butler<br />
*mpg<br />
<br />
== GeoMOOSE ==<br />
<br />
'''Attending:''' <br />
<br />
*Brian Fischer <br />
*Bob Basques <br />
*Jim Klassen <br />
*Eli Adam <br />
*Dan "Ducky" Little <br />
*Brent Fraser <br />
*you?<br />
<br />
'''Goals:''' <br />
<br />
*Testing and bug fixes for 2.6 release <br />
*Documentation<br />
<br />
== ZOO-Project ==<br />
<br />
'''Attending:''' <br />
<br />
*Nicolas Bozon <br />
*[[User:Djay|Gérald Fenoy]]<br />
*Luca Delucchi<br />
<br />
<br><br />
<br />
== uDig ==<br />
<br />
'''Attending:''' <br />
<br />
*[[User:Jive|Jody Garnett]] <br />
*[[User:Kengu|Kenneth Gulbrandsøy]] (IRC)<br />
<br />
'''Goals:''' <br />
<br />
*TBD<br />
<br />
'''Possible:''' <br />
<br />
*roll out CDO and a bit of QA on EMF goodness <br />
*migrate user guide to help plugin (since Eclipse has a Wiki Editor that supports textile) <br />
*refactor to *eu.udig* and make a verison release <br />
*GeoTools as OSGi (no more net.refractions.udig.libs) - see GeoTools below as this would require collaborative effort<br />
<br />
== GeoTools ==<br />
<br />
'''Attending:''' <br />
<br />
*[[User:Jive|Jody Garnett]]<br />
<br />
'''Goals:''' <br />
<br />
*TBD<br />
<br />
'''Possible:''' <br />
<br />
*Implement Query/Join for more than just JDBC-NG code <br />
*Get OSGi bundle information sorted (collaborate with downstream applications ) <br />
*Set up new developers <br />
*Major Bug stomp <br />
*Technical Debt (FunctioName details; Remove old Filter code from test cases etc...)<br />
<br />
'''Collaboration:''' <br />
<br />
*uDig: Collaborate on OSGi rollout (ie Equinox testing) <br />
*GeoServer: Collaborate on OSGi rollout (ie Spring testing) <br />
*Zoo-Project: collaborate on WPS Client testing?<br />
<br />
== 52North-WPS ==<br />
<br />
'''Attending:''' <br />
<br />
*Bastian Schäffer <br />
*Benjamin Pross<br />
<br />
'''Goals:''' <br />
<br />
*Open Disucssion about technical aspects <br />
*Open Disucssion about use cases<br />
<br />
== GRASS GIS ==<br />
<br />
'''Attending:''' <br />
<br />
*Luca Delucchi<br />
<br />
'''Goals:''' <br />
<br />
*Testing GRASS 7 scripts <br />
*Closing some Python bugs<br />
*Italian translation <br />
<br />
== GeoHex ==<br />
<br />
GeoHex is a hexagonal geo-coding system created by sa2sa.<br />
https://sites.google.com/site/geohexdocs/<br />
<br />
'''Attending:''' <br />
<br />
*[[User:Hal_sk|Hal Seki]] <br />
<br />
'''Goals:''' <br />
<br />
*Implement geohex-gem version 3.<br />
<br />
'''Possible:''' <br />
<br />
*Implement other language libraries.<br />
*Make a cool demo app using geohex.<br />
<br />
<br />
<br><br />
<br />
<br />
[[Category:FOSS4G2011]] [[Category:FOSS4G]] [[Category:Code_Sprints]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=FOSS4G2011_OSGeo_Booth&diff=57214FOSS4G2011 OSGeo Booth2011-09-12T14:02:08Z<p>Dkastl: /* Signup Schedule */</p>
<hr />
<div>Placeholder for organising the OSGeo Booth at [[FOSS4G 2011]], similar to previous year: [[FOSS4G2009 OSGeo Booth]].<br />
<br />
'''Event Contact: Tyler Mitchell...'''<br />
<br />
== Schedule ==<br />
Official schedule on FOSS4G site [http://2011.foss4g.org/content/exhibit-hours-move-inout-schedule posted here]. All hours are flexible and not considered mandatory. Wednesday evening is the main time to target. Exhibit hall is integrated into the venue, so is never really "closed". <br />
<br />
Summary of schedule is:<br />
<br />
{|class=wikitable border="1"<br />
! Day !! Hours !! <br />
|-<br />
| Tues Sep 13th || 1-5pm || '''Move in/set up''' during this time<br />
|-<br />
| Wed Sep 14th || 9:30am-6pm || Regular hours, sessions running, etc.<br />
|-<br />
| || 6-8pm || '''Exhibitor Reception'''<br />
|-<br />
| Thurs Sep 15th || 9:30am-6pm || Regular hours<br />
|-<br />
| Fri Sep 16th || 9:30am-1pm || Regular hours<br />
|-<br />
| || 1-2:30pm || '''Move out'''<br />
|}<br />
<br />
== Volunteers ==<br />
Sign up for an hour or so here:<br />
* [[Arnulf Christl]] will be at the booth for 2h each day. Once we have several volunteers we should set up a time table to better coordinate.<br />
* [[Robert Hollingsworth]] I'm available for booth time on all exhibit days. Would like to see how exhibit schedule intersects (specific) presentations and other activities when setting times.<br />
* mpg will be attending and would be happy to do some booth duty<br />
* Raj Singh will help man the booth and will also have some OGC material available.<br />
* [http://wiki.osgeo.org/wiki/User:Epifanio Massimo Di Stefano] I'll be at the Sheraton starting from monday at noon, i can help spending 1h per day or more according on the needs.<br />
* ''please add yourself''<br />
<br />
== Signup Schedule ==<br />
<br />
{|class=wikitable border="1"<br />
! Day !! Hours !! !! Booth Team (two each slot)...<br />
|-<br />
| Tues Sep 13th || 1-5pm || Set up - half an hour || [[User:wildintellect|Alex]], Robert<br />
|-<br />
| Wed Sep 14th || 9:30-11:30am || Regular hours || ...<br />
|-<br />
| || 11:30am-2pm || Regular hours || ...<br />
|-<br />
| || 2-4pm || Regular hours || ...<br />
|-<br />
| || 4-6pm || Regular hours || ...<br />
|-<br />
| || 6-7pm (1 hour slot) || '''Exhibitor reception''' || [[Arnulf]]<br />
|-<br />
| || 7-8pm (1 hour slot) || '''Exhibitor reception''' || ...<br />
|-<br />
| Thu Sep 15th || 9:30-11:30am || Regular hours || [[user:Danielkastl|Daniel]]<br />
|-<br />
| || 11:30am-2pm || Regular hours || ...<br />
|-<br />
| || 2-4pm || Regular hours || [[Arnulf]]<br />
|-<br />
| || 4-6pm || Regular hours || ...<br />
|-<br />
| Fri Sep 16th || 9:30-11:30am || Regular hours || ...<br />
|-<br />
| || 11:30-1pm || Last session || ...<br />
|-<br />
| || 1-2:30pm || '''Move out''' || ...<br />
|}<br />
<br />
== Equipment ==<br />
What kind of equipment should be available? How large is the booth footprint? Will internet taps be available?<br />
<br />
Basic Booth Includes:<br />
8’x10’ exhibit space<br />
Pipe and drape, 8’ back and 3’ sides<br />
1 table<br />
2 chairs<br />
Wireless internet<br />
2 booth personnel passes<br />
<br />
* OSGeo booth will be double-width - so 8x20' with two tables, 4 chairs.<br />
<br />
* Volunteers should bring their own laptop if possible. Maybe have a larger desktop monitor there too. Or projector?<br />
* Pop-up Banner: Robert Hollingsworth bringing banner<br />
* Consider adding 1 "discussion" pedestal table and chairs?<br />
* Monitor rental?<br />
<br />
== Handouts ==<br />
What handouts will be available, who/where will they be printed?<br />
* Brochures, sponsorship postcards, business info cards - Tyler/Robert shipping to GITA, will be available at event registration<br />
* Poster showing sponsors! - to be printed<br />
* ...<br />
<br />
== Presentations ==<br />
What kinds of live demonstrations or recorded examples can be played at the booth? Where can they be downloaded from or who can run them?<br />
* If there are multiple booth volunteers, therefore multiple laptops, might simplify by having canned demos/videos, manual demos, and associated data living on a server somewhere.<br />
* OSGeo Live - Everyone is getting a DVD or USB in their bag, so either boot from media or run in a Virtual Machine.<br />
<br />
=== Self-Running ===<br />
'''Review in case of updates or additions'''<br />
<br />
* [http://download.osgeo.org/ossim/Movies/ OSSIMPlanet video with sound] (181MB)<br />
* [http://grass.osgeo.org/grass_movie_CERL_1987/grass_movie_CERL_1987.mov GRASS historical Video from '87] - '''William Shatner''' narrates (60MB)<br />
* [http://www.youtube.com/watch?v=_ZOQSn5tyqQ Italian OSGeo chapter youtube video] Can we get a full res copy of this?<br />
* [http://www.youtube.com/watch?v=EJqF6_80GkM gvSIG OpenMoko youtube vid]. High res copy?<br />
* [http://www.youtube.com/watch?v=1-ymz0LUB0s gvSIG Day's 11 Video] (not too techie, but nice) <s>[http://www.youtube.com/watch?v=hA1jRtm3F1M gvSIG Days '07 Video]</s>.<br />
<br />
== Other Considerations ==<br />
<br />
* Good reading: Running [http://fromtheinsidelookingin.blogspot.com/2008/10/conference-booths.html Conference Booths]<br />
* [[Operate OSGeo Booth]]<br />
<br />
[[Category: Marketing]]<br />
[[Category: Events]]<br />
[[Category: FOSS4G2011]]<br />
[[Category: FOSS4G]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2011_Breakout_Sessions&diff=56986FOSS4G 2011 Breakout Sessions2011-09-04T03:34:08Z<p>Dkastl: /* Proposed Topics */ mobile GIS + added headlines</p>
<hr />
<div>= Introduction =<br />
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).<br />
<br />
Breakout Sessions are unstructured timeslots where people can self-organize themselves to discuss topics of interest.<br />
<br />
'''Room allocation to be determined'''<br />
<br />
== Organising Contact ==<br />
<br />
== Timeslots Available ==<br />
<br />
Wednesday 5:30pm to 6:30pm and 7:00pm to 8:00pm<br />
<br />
= Room Assignments =<br />
<br />
== Rooms Available ==<br />
<br />
= Proposed Topics =<br />
<br />
== GeoMoose == <br />
<br />
*Proposed Topics <br />
**Overview <br />
**GeoMoose 2.6 <br />
**Ideas for CodeSprint <br />
**Meet devlopers and learn how you can help. <br />
*Attending: <br />
**Bob Basques (City of Saint Paul) <br />
**Dan Little (GeoMoose) <br />
**Jim Klasen (SharedGeo) <br />
**Brian Fischer (Houston Engineering)<br />
<br />
== Tiling == <br />
<br />
*Proposed Topics <br />
**standardised sqlite schema for tile caches <br />
**TMS/WMTS evolutions: <br />
***Tile merging (i.e. equivalent of WMS LAYERS=baselayer,overlaylayer) <br />
***TMS multiple grids per tileset <br />
***WMTS multiple url endpoints (eg tile1.domain.tld, tile2.domain.tld...): is this still needed now that browsers allow many more connections per server? <br />
**add yours... <br />
*Attending: <br />
**[[User:Tbonfort]] <br />
**[[User:Olt|Oliver Tonnhofer (Omniscale, MapProxy)]] <br />
**[[User:Stvn|Steven M. Ottens]] <br />
**[[User:Lagerratrobe|Roger Andre (Tableau Software, Seattle)]] <br />
**[[User:Springmeyer|Dane Springmeyer (Development Seed)]]<br />
<br />
== GeoNode == <br />
<br />
*Proposed topics: <br />
**Brief overview <br />
**Get involved with the community! <br />
**Meet developers and institutional partners <br />
***Opportunities for work around the world, especially in South America and Indonesia <br />
***Positions available at the World Bank and OpenGeo <br />
**[http://geonode.org/2011/08/geonode-at-foss4g/ Join us for drinks afterwards!] <br />
*Attending: <br />
**Rolando Peñate (OpenGeo) <br />
**David Winslow (OpenGeo) <br />
**Robert Soden (World Bank) <br />
**Ariel Nuñez (World Bank) <br />
**Seb Benthall (UC Berkeley) <br />
**Ben Lewis(Harvard University) <br />
**Matt Bertrand (Harvard University) <br />
**Sachindra Singh (SOPAC) <br />
**[[User:Ortelius|Jeffrey Johnson (OpenGeo)]] <br />
**Jubal Harpster (SpatialDev) <br />
**[[User:Ebwolf|Eric Wolf (USGS, CU-Boulder)]] <br />
**[[User:Wildintellect|Alex Mandel (UC Davis)]]<br />
<br />
== Python == <br />
<br />
*Scheduling: let's do this one in the 5:30-6:30 slot and tiling afterwards? <br />
*Proposed topics: <br />
**High fives <br />
**Extension modules, Pyrex, Cython, ctypes <br />
**Python 3 <br />
**PyPy <br />
**Packaging and distributions <br />
*Attending: <br />
**Sean Gillies (NYU, Shapely and friends) <br />
**[[User:Ebwolf|Eric Wolf (USGS, CU-Boulder)]] <br />
**Michael Weisman (Urban Mapping) <br />
**Derek Hohls (CSIR, South Africa) <br />
**[[User:Dandye|Dan Dye (WeoGeo)]] <br />
**[[User:Davidfawcett|David Fawcett (MPCA)]] <br />
**[[User:Wildintellect|Alex Mandel (UC Davis)]] <br />
**[[User:Hobu|Howard Butler (Hobu, Inc.)]] <br />
**[[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. <br />
**Marc Pfister (nothing to see here) <br />
**[[User:Lagerratrobe|Roger Andre (Tableau Software, Seattle)]] <br />
**Thomas Emge (Esri)<br />
<br />
== Opengeoportal == <br />
<br />
http://opengeoportal.org/ <br />
<br />
*Proposed topics: governance models, federated searching and coordinating code development <br />
*Attending: <br />
**Stephen McDonald (Tufts) <br />
**Patrick Florance (Tufts) <br />
**Chris Barnett (Tufts) <br />
**David Siegel (Harvard) <br />
**Lisa Sweeney (MIT) <br />
**Garey Mills (Berkeley) <br />
**John Ridener (Berkeley) <br />
**Patricia Carbajales (Stanford) <br />
**Renzo Sanchez-Silva (Stanford)<br />
<br />
== Spatial Data InfraStructure (SDI) ==<br />
<br />
*Scheduling: 7pm - 8pm. Get started with these topics then go get some food/drinks together. <br />
*Proposed topics: data sharing and discovery, metadata, web services, and portals. <br />
*Attending: <br />
**Christine White (Esri) <br />
**Andy Gup (Esri)<br />
<br />
== Mobile GIS ==<br />
<br />
*Proposed Topics <br />
**General discussion about development of mobile mapping/GIS apps <br />
**"OpenLayers-like" SDK for Android (Android GIS) <br />
**add yours... <br />
*Attending: <br />
**[[User:Danielkastl|Daniel Kastl (Georepublic)]] <br />
**[[User:Hal sk|Haruyuki Seki (Georepublic)]] <br />
**Jaak Laineste (Nutiteq)<br />
<br />
== Add yours below ==<br />
<br />
*Add yours below...<br />
<br />
[[Category:FOSS4G]] [[Category:FOSS4G2011]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2011_Workshop_Installed_Software&diff=56538FOSS4G 2011 Workshop Installed Software2011-08-16T01:18:34Z<p>Dkastl: added w06</p>
<hr />
<div>This page describes the software installed on the Master machine to be used for workshops. Uploaded files exist on the machine at ''C:\workshop-uploads\''<br />
<br />
== Base Software ==<br />
<br />
- Windows XP Service Pack 3<br />
<br />
- Firefox 5.0.1<br />
<br />
- Firebug 1.8.1<br />
<br />
- Internet Explorer 8<br />
<br />
- Filezilla 3.5.0<br />
<br />
- Notepad++ 5.9<br />
<br />
- Adobe Reader 10.1.0<br />
<br />
- Textpad 5.4.2<br />
<br />
- 7-zip 9.20<br />
<br />
- OpenOffice 3.3.0<br />
<br />
- VirtualBox 4.1.0<br />
<br />
- Google Chrome 13.0.782.112<br />
<br />
- Java JDK 1.7.0<br />
<br />
== w01 ==<br />
<br />
- VirtualBox 4.1 Oracle VM VirtualBox Extension Pack<br />
<br />
== w02 ==<br />
<br />
- OSGeo4W (Desktop install)<br />
<br />
== w03 ==<br />
<br />
- installed visual studio 2010 c# express<br />
<br />
== w04 ==<br />
<br />
- VirtualBox with the OSGEOLive VM installed.<br />
<br />
== w06 ==<br />
<br />
- VirtualBox with the OSGEOLive VM installed.<br />
<br />
== w07 ==<br />
<br />
- created VirtualBox machine with 'mapfish_workshop.vdi'<br />
<br />
== w08 ==<br />
<br />
- Google Earth 6.0.3<br />
<br />
== w09 == <br />
<br />
- ''''Geomajas_Workshop_2011.vbox' crashes when loading with VirtualBox 4.1.0'''<br />
<br />
== w10 ==<br />
<br />
- OpenGeo Suite Enterprise Edition 2.4.3<br />
<br />
== w11 ==<br />
<br />
- Using a live DVD - nothing to install<br />
<br />
== w12 == <br />
<br />
using open office and a virtual box - nothing to be done<br />
<br />
== w13 ==<br />
<br />
- shortcut to Notepad2 on desktop<br />
<br />
- gx_workshop folder installed<br />
<br />
== w14 ==<br />
<br />
- Created a nodejs and polymaps vbox image (COMPLETE)<br />
<br />
== w15 ==<br />
<br />
- MS4W (MapServer 6.2-dev, Apache 2.2.19)<br />
<br />
== w16 ==<br />
<br />
- QGIS 1.7.0<br />
<br />
- North Carolina, South Dakota, and Alaska datasets loaded for QGIS 1.7.0<br />
<br />
- ColorPic 4.1<br />
<br />
- XML Copy Editor 1.2.0.6<br />
<br />
- Inkscape-0.48.1-2<br />
<br />
- PixelWindow<br />
<br />
== w17 == <br />
<br />
-- '''' EMAIL THE PRESENTER ABOUT NEEDING A VM or links to qt-designer and openlayers plugin for qgis''''<br />
<br />
- VirtualBox with the OSGEOLive 5.0 VM is fine (Pirmin Kalberer, Presenter)<br />
<br />
== w18 ==<br />
<br />
- created new VirtualBox machine with 'qgis-foss4g11-1004.vdi'<br />
<br />
== w19 ==<br />
<br />
- imported 'mapnik-foss4g-2011v2.ova' into VirtualBox<br />
<br />
== w20 == <br />
<br />
- using the opengeo suite nothing to be done<br />
<br />
== w21 ==<br />
<br />
- created VirtualBox machine with 'osgeo-live-vm-i2maps.vmdk'<br />
<br />
== w23 ==<br />
<br />
- workshop materials available at: C:\workshop-uploads\w23\data\GeoNode-Workshop-Materials\<br />
<br />
== w24 == <br />
<br />
- installed Putty on the desktop as per Sophia's request (COMPLETE)<br />
<br />
[[Category:FOSS4G2011]]<br />
[[Category:FOSS4G]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2010_Workshops&diff=56164FOSS4G 2010 Workshops2011-07-26T07:04:36Z<p>Dkastl: /* On-line manuals */</p>
<hr />
<div>Back to [[FOSS4G 2010]]<br />
<br />
<br />
== Introduction ==<br />
Workshops are 3-hour sessions in a PC classroom, and Tutorials are 90-minute sessions in a conference room.<br />
The FOSS4G 2010 Workshop Committee is responsible for the organization of both Workshops and Tutorials.<br />
<br />
<br />
== FOSS4G 2010 Workshop Commitee ==<br />
<br />
We need people with experience organizing conference workshops at other GFOSS events. Local (Barcelona & Spain) members are welcome.<br />
If you are willing to help organizing FOSS4G Workshops and Tutorials, please add yourself to the members list below, and subscribe to<br />
the mail list.<br />
<br />
<br />
=== Workshop Committee Members ===<br />
<br />
* [[Oscar Fonts]] IRC username: oscarfonts<br />
* [[Jeff McKenna]] IRC username: jmckenna<br />
* Alvaro Anguix, collaborator<br />
* Mario Carrera, collaborator<br />
<br />
<br />
=== Communication ===<br />
<br />
* Main discussion mail list: [http://lists.osgeo.org/mailman/listinfo/conference-workshops conference-workshops].<br />
* [[FOSS4G_2010_Workshops_meetings|Periodical IRC meetings]].<br />
<br />
<br />
== Workshop and Tutorial Selection ==<br />
<br />
[http://2010.foss4g.org/organization.php FOSS4G 2010 Organization Committee] will evaluate workshop and tutorial proposals attending to these criteria:<br />
<br />
# Meets conference mandate:<br />
## Matches with the themes of the conference<br />
## Makes use of software that is both "free" and "open source"<br />
# Submission's technical requirements can be met by the conference facilities<br />
# Demonstrates practical applications<br />
# Expected level of attendee interest in the workshop topic<br />
# A plus for proposals addressing the special interest topics stated in [[FOSS4G_2010_Press_Release_3#FOSS4G_2010_Call_for_Workshops_and_Tutorials|the Call]]<br />
# Likelyhood of a quality workshop:<br />
## Expertise of the workshop presenters in the workshop subject matter<br />
## Presenters personal experience presenting workshops at other conferences<br />
## Successful workshop presented at prior FOSS4G/GFOSS conferences<br />
<br />
== Workshop Venue ==<br />
<br />
Workshops will be hold in the Barcelona School of Computer Science ([http://www.fib.upc.edu/en.htm FIB]), at [http://www.openstreetmap.org/?lat=41.38854&lon=2.112316&zoom=18&layers=B000FTF Barcelona Campus Nord], buildings B5 and C6 ([http://www.fib.upc.edu/en/centre/on.html address]). <br />
<br />
All classrooms have screen and projector for instructors.<br />
<br />
Software installation is preferred on Windows XP native Operating System.<br />
<br />
If linux is required, we have a vmware SUSE 11.1 image. <br />
<br />
<br />
=== B5 building classrooms ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Classroom <br />
! # Computers <br />
! PC hardware<br />
|-<br />
| B5.S101 <br />
| 21+1 <br />
| Intel Core 2 Duo E8500 3.1 Ghz. 4GB RAM. Monitor HP L1950g TFT 19". ASUS EAH3450 Series 1GB (512MB), compatible ATI Radeon HD 34xx. DVD-ROM.<br />
|-<br />
| B5.S201 <br />
| 21+1 <br />
| Intel Core 2 Duo E8500 3.1 Ghz. 4GB RAM. Monitor HP L1950g TFT 19". ASUS EAH3450 Series 1GB (512MB), compatible ATI Radeon HD 34xx. DVD-ROM.<br />
|-<br />
| B5.S202 <br />
| 21+1 <br />
| Intel Core 2 Duo E8500 3.1 Ghz. 4GB RAM. Monitor HP L1950g TFT 19". ASUS EAH3450 Series 1GB (512MB), compatible ATI Radeon HD 34xx. DVD-ROM.<br />
|}<br />
<br />
=== C6 building classrooms ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Classroom <br />
! # Computers <br />
! PC hardware<br />
|-<br />
| C6.S302 <br />
| 24+1 <br />
| Intel Core 2 Duo 6320 1.86 Ghz. 2GB RAM. Monitor CRT 17". Nvidia Geforce 6200. DVD-ROM.<br />
|-<br />
| C6.S306 <br />
| 20+1 <br />
| Intel Core 2 Duo E8400 3.00 Ghz. 2GB RAM. Monitor HP L1750 TFT 17". ATI Radeon X1300. DVD-ROM.<br />
|-<br />
| C6.S308 <br />
| 20+1 <br />
| Intel Core 2 Duo E8400 3.00 Ghz. 2GB RAM. Monitor HP L1750 TFT 17". ATI Radeon X1300. DVD-ROM.<br />
|-<br />
| C6.S309 <br />
| 20+1 <br />
| Intel Core 2 Duo E8500 3.1 Ghz. 4GB RAM. Monitor HP L1950g TFT 19". ASUS EAH3450 Series 1GB (512MB), compatible ATI Radeon HD 34xx. DVD-ROM.<br />
|}<br />
<br />
== Schedule ==<br />
<br />
=== Workshops ===<br />
<br />
<div style="margin:5px 5px 0px 0px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#f8f8ff;"><br />
<br />
{| class="wikitable"<br />
! Classroom !! Capacity !! Session 1 (Mon 6 Sep 15-18h) !! Session 2 (Tue 7 Sep 9-12h)<br />
|-<br />
| B5.S101 || 42<br />
||''' W1 - Web mapping with GeoServer'''<br />
''Andrea Aime, Mike Pumphrey (OpenGeo)''<br />
|| '''W8 - Getting started with MapServer'''<br />
''Tyler Mitchell (OSGeo), Jeff McKenna (Gateway Geomatics), Perry Nacionales (University of Minnesota)''<br />
|-<br />
| B5.S201 || 42<br />
|| '''W2 - gvSIG 1.9 user workshop'''<br />
''Jorge Sanz (Prodevelop - gvSIG Association), José Vicente Higón (Software Colaborativo - gvSIG Association), Victoria Agazzi (Prodevelop - gvSIG Association)''<br />
|| '''W9 - Quantum GIS and PostGIS: Solving spatial problems and creating web-based analysis tools'''<br />
''Paul Wickman (Northstar Geographics)''<br />
|-<br />
| B5.S202 || 42<br />
|| '''W3 - Setting up an OpenStreetMap rendering toolchain'''<br />
''Iván Sánchez Ortega (OpenStreetMap España), Dane Springmeyer (Mapnik)''<br />
|| '''W10 - FOSS4G routing with pgRouting tools, OpenStreetMap road data and GeoExt'''<br />
''Daniel Kastl (Georepublic), Frédéric Junod (Camptocamp)''<br />
|-<br />
| C6.S302 || 48<br />
|| '''W4 - Introduction to PostGIS'''<br />
''Paul Ramsey (OpenGeo), Mark Cave-Ayland (Sirius)''<br />
|| '''W11 - Working with OpenLayers'''<br />
''Tim Schaub, Charles David Winslow (OpenGeo)''<br />
|-<br />
| C6.S306 || 40<br />
|| '''W5 - Introduction to the Mapbender geoportal framewework'''<br />
''Astrid Emde, Christoph Baudson (WhereGroup)''<br />
|| '''W12 - GeoNetwork for dummies, or how to setup an SDI in 3 hours'''<br />
''Jeroen Ticheler, Jose Garcia, Heikki Doeleman (GeoCat)''<br />
|-<br />
| C6.S308 || 40<br />
|| '''W6 - Solid web mapping with Python'''<br />
''Éric Lemoine, Bruno Binet (Camptocamp)''<br />
|| '''W13 - Geospatial for Java'''<br />
''Jody Garnett (LISAsoft), Justin Deoliveira (OpenGeo)''<br />
|-<br />
| C6.S309 || 40<br />
|| '''W7 - Practical introduction to ZOO, the powerful WPS platform'''<br />
''Gérald Fenoy (GeoLabs), Nicolas Bozon (3LIZ)''<br />
|| '''W14 - Practical introduction to GRASS'''<br />
''Paolo Zatelli, Clara Tattoni, Marco Ciolli (Univeristy of Trento)''<br />
|-<br />
|}<br />
<br />
</div><br />
<br />
<br />
=== Tutorials ===<br />
Tutorials are 1.5 hour sessions simultaneous to conference talks, in the main conference venue.<br />
<br />
<div style="margin:5px 5px 0px 0px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#f8f8ff;"><br />
<br />
The tutorials this year will be:<br />
<br />
{| class="wikitable"<br />
! Room !! Date&Time !! Tutorial<br />
|-<br />
| Sala 12 || Sept 08 12:00<br />
|| T-01 '''gvSIG Mobile and Mini tutorial'''<br />
''Javier Carrasco, Alberto Romeu (Prodevelop)''<br />
|-<br />
| Sala 11 || Sept 07 16:30<br />
|| T-02 '''PyWPS'''<br />
''Luca Casagrande (Universit&agrave; degli Studi di Perugia), Jorge de Jesus (Plymouth Marine Laboratory) ''<br />
|-<br />
| Sala 12 || Sept 08 14:30<br />
|| T-03 '''Building web based GIS applications with GeoEXT'''<br />
''Pierre Giraud (Camptocamp), Andreas Hocevar (OpenGeo), Yves Jacolin (Camptocamp)''<br />
|-<br />
|-<br />
| Sala 11 || Sept 08 16:30<br />
|| T-04 '''Mastering advanced GeoNetwork'''<br />
''Jeroen Ticheler, Jose Garcia, Heikki Doeleman (GeoCat)''<br />
|-<br />
|-<br />
| Sala 12 || Sept 09 09:00<br />
|| T-05 '''Hands-on introduction to Mapguide Open Source'''<br />
''Gordon Luckett (Arrow Geomatics)''<br />
|-<br />
|-<br />
| Sala 12 || Sept 09 11:00<br />
|| T-06 '''First steps with MapFish'''<br />
''Pierre Mauduit, Antoine Abt (Camptocamp France)''<br />
|-<br />
|-<br />
| Sala 12 || Sept 09 14:00<br />
|| T-07 '''A hands-on introduction to spatial ETL with Geokettle'''<br />
''Thierry Badard (Spatialytics)''<br />
|-<br />
|-<br />
| Sala 11 || Sept 08 12:00<br />
|| T-08 '''How to generate billions of tiles using distributed cloud-computing'''<br />
''Oliver Christen, Cedric Moullet, François Van Der Biest (Camptocamp)''<br />
|-<br />
|-<br />
| Sala 11 || Sept 09 09:00<br />
|| T-10 '''SDI best practices with Geonode'''<br />
''Sebastian Benthall (OpenGeo), Stuart Gill (World Bank)''<br />
|-<br />
|-<br />
| Sala 11 || Sept 08 14:30<br />
|| T-11 '''Standardized geoprocessing with 52°North open source software'''<br />
''Bastian Schaeffer (52°North)''<br />
|-<br />
|-<br />
| Sala 11 || Sept 09 14:00<br />
|| T-12 '''Sensor Web Enablement - Integrating sensor data into Spatial Data Infrastructures'''<br />
''Simon Jirka (52° North), Arne Bröring (University of Münster - Institute für Geoinformatics), Eike Hinderk Jürrens (52° North)''<br />
|-<br />
|-<br />
| Sala 11 || Sept 09 11:00<br />
|| T-13 '''Conquering complex application schemas (INSPIRE Data Themes, GeoSciML, ...) with deegree 3 web services'''<br />
''Markus Schneider (lat/lon GmbH )''<br />
|-<br />
|}<br />
</div><br />
<br />
== Requirements: Software, hardware, geodata ==<br />
<br />
=== Workshops ===<br />
<br />
Workshop classrooms come with native Windows XP computers. Required software will be installed on Windows XP and tested on mid July. Alternatively, an Open Source Virtual Machine can be provided.<br />
<br />
{| class="wikitable"<br />
!width="75px"| Room !!width="40px"| Code !!width="30%"| Title !!width="60%"| Software needs<br />
|-<br />
| B5.S101<br />
|| W1<br />
|| Web Mapping with GeoServer<br />
|| You supply the laptops, we supply the software and data.<br />
|-<br />
| B5.S101<br />
|| W8<br />
|| Getting Started With MapServer<br />
|| No additional material is required. Optional: bring your own datasets to load into your web mapping application. Intermediate/advance questions will be accommodated if time permits.<br />
|-<br />
| B5.S201<br />
|| W2<br />
|| gvSIG 1.9 user workshop<br />
|| the workshop will run on the OSGeo LiveDVD so we suppose we don't need hard and soft additional.<br />
|-<br />
| B5.S201<br />
|| W9<br />
|| Quantum GIS and PostGIS: Solving Spatial Problems and Creating Web-Based Analysis Tools<br />
|| "Quantum GIS v1.4.0 Enceladus" or newer, installed on workshop computers or available on the FOSS4G LiveDVD. Please use Windows "Standalone" version, not the "OSGeo4W" installer version. Internet access to the instructor's PostGIS and WMS/WFS server.<br />
|-<br />
| B5.S202<br />
|| W3<br />
|| Setting up an OpenStreetMap rendering toolchain<br />
|| Hardware: One computer per person, plus overhead projector. Standard internet connection. Nothing out of the ordinary. Software: Already installed in the computers: PostGIS, Mapnik, Mapnik support scripts, Apache2 web server, and mod_tile. Computers *must* run Linux in order for Apache+mod_tile to work. Some other workshops may use PostGIS and Apache, so it should be coordinated. PHPPGAdmin would be a plus. Available somewhere in the workshop CDs: OpenLayers, plus some sets of geodata (global shorelines, plus a small excerpt of OpenStreetMap data). Total size of this data should be around or less than 100 MB. The workshop tutor will provide all materials prior to the workshop. All software in the computers should be tested beforehand, so it is desirable to have a disk image or install CD the tutor can try out ahead of time. Atendees should not bring anything special. All the needed software and data should be readily available in the computers, plus a CD (or pendrive, or similar device).<br />
|-<br />
| B5.S202<br />
|| W10<br />
|| FOSS4G routing with pgRouting tools, OpenStreetMap road data and GeoExt<br />
|| -<br />
|-<br />
| C6.S302<br />
|| W4<br />
|| Introduction to PostGIS<br />
|| Windows XP computers.<br />
|-<br />
| C6.S302<br />
|| W11<br />
|| Working with OpenLayers<br />
|| Participants will complete exercises on a PC (any OS) that is running a web server (e.g. Apache). Participants will need to edit text files with an editor and view examples in a browser. The workshop also requires GeoServer and Postgres w/ PostGIS running. We can provide software and data to be installed in advance of the workshop. In previous workshops, GeoServer has been installed and running, PostGIS configured with workshop data, and Apache configured to proxy GeoServer on port 80 and provide an alias to the workshop document root. We can provide documentation on setting all this up and can help if workshop machines are available before the workshop date. So, requirements are - * PostGIS (configured with data) * GeoServer (running on port 8080 or other) * Apache (configured to proxy GeoServer on port 80 and with alias to workshop document root) * Text editor * Web browser (Firefox recommended).<br />
|-<br />
| C6.S306<br />
|| W5<br />
|| Introduction to the Mapbender Geoportal Framwework<br />
|| The workshop will run completely on the Mapbender Portal provided by OSGeo, no software will be installed during the course all that is needed is a web terminal. Attendees who want to work with their own copy of the software should either install it on a server that is available via internet during the workshop or on their own notebook. To the experienced geoportal operator the installation is straight forward, all information can be found on the Mapbender web site http://www.mapbender.org. If you want to install you own copy but are new to either GIS, web technology, mapping, OGC standards or any combination thereof it is recommended to start the installation well in advance to the workshop as it involves a web server, database, PHP, Mapbender internet accessibility. You will get all the help that you need to set up the system and get it to run properly on the http://www.mapbender.org/index.php/Mapbender_Mailing_Lists. <br />
|-<br />
| C6.S306<br />
|| W12<br />
|| GeoNetwork for dummies, or how to setup an SDI in 3 hours<br />
|| Instructions and CD-ROM can be downloaded from the [[FOSS4G 2010 Workshops#On-line manuals | On-line manuals]] section. CD-ROM and instructions were brought by workshop organizer.<br />
|-<br />
| C6.S308<br />
|| W6<br />
|| Solid Web Mapping with Python<br />
|| Linux or Windows machine with Python 2.5 or 2.6 installed. Linux is preferred.<br />
|-<br />
| C6.S308<br />
|| W13<br />
|| Geospatial for Java<br />
|| Windows, any version of Java, Students will have choice of Eclipse or NetBeans IDE.<br />
|-<br />
| B5.S101<br />
|| W7<br />
|| Practical Introduction to ZOO, the Powerful WPS Platform<br />
|| computer and ZOO-CD (ZOO-Binaries, GDAL/OGR library and dependencies).<br />
|-<br />
| B5.S101<br />
|| W14<br />
|| Practical Introduction to GRASS<br />
|| For the workshop we need: - GRASS (one of the 6.4 series, 6.4.0RC5 is currently available); - the standard North Carolina GRASS demo data set, the "smaller simpler subset (47MB)" (http://grass.osgeo.org/sampledata/north_carolina/nc_basic_spm.tar.gz) is sufficient; - our HTML tutorial; - our PDF file containing the introductory slides for the workshop. The last years we used our own live DVDs, especially tailored for the Conferences (see for example the 2009 DVD here: http://www.ing.unitn.it/~grass/software/FOSS4G2009_GRASS_beginners_DVD.html), but we can provide our tutorial as a Debian and Ubuntu package, so that it can be included in the OSGEO Live DVD. Since this is a beginners' workshop, it is fundamental that GRASS' version in use matches the one used in the workshop material, so that all the details correspond. Therefore, if the OSGEO Live DVD is used we need to know which GRASS version will be included at least a month in advance, to review all the material. No special hardware is required, maps in the dataset are quite small, therefore a fairly modern Pc will do. No network connection is required, unless you want the attendees to download the tutorial and the dataset. It is possible to use attendees' laptop (some of the attendees have used their own Pc last year in Sydney), but we must be reasonably sure they have a working GRASS installation. Again, the GRASS version can be critical. Last year I have helped some of them to setup their machine via email before the workshop. The use of a live DVD on a Pc provided by the organization is probably the best choice for most of the attendees, since they are not required to setup GRASS before the workshop but they can take the DVD home and re-run the workshop. They can also use the DVD as an installer.<br />
|-<br />
|}<br />
<br />
=== Tutorials ===<br />
<br />
For tutorials, it is recommended to use the LiveDVD that will be distributed to all delegates.<br />
Instructors are encouraged to join the [http://lists.osgeo.org/mailman/listinfo/live-demo LiveDVD list] and participate in release testing. <br />
<br />
<br />
== Instructors ==<br />
<br />
Workhsop & tutorial instructors will receive credit for registration for "the Conference". See details in the<br />
[[FOSS4G_2010_Discounts#Workshop_Instructors|Discounts page]].<br />
<br />
<br />
=== Welcome Lunch for Workshop Instructors & Volunteers ===<br />
<br />
All Workshop Instructors and Volunteers are invited to a ''Welcome Lunch'' near the Workshop Venue: [http://www.openstreetmap.org/?mlat=41.390649&mlon=2.113446&zoom=17&layers=M Casa Cantabria], Monday Sept. 6, 1PM.<br />
<br />
If you want to come, please add yourself to this list BEFORE monday, so we can make the reservation in the restaurant:<br />
<br />
* Oscar Fonts (LOC).<br />
* Càrol Puig (LOC).<br />
* Pedro-Juan Ferrer, OSGeo-es LO, Volunteer.<br />
* Bruno Binet, Camptocamp, W6<br />
* Eric Lemoine, Camptocamp, W6<br />
* Frédéric Junod, Camptocamp, W10<br />
* Justin Deoliveira, OpenGeo, W13<br />
* Jody Garnett, LisaSoft, W13<br />
* Chris Holmes, OpenGeo, W01<br />
* Tim Schaub, OpenGeo, W11<br />
* David Winslow, OpenGeo, W11<br />
* Paul Ramsey, OpenGeo, W04<br />
* Jeff McKenna, W8<br />
* Jorge Sanz, gvSIG Association, W2<br />
* Jose Vicente Higón, gvSIG Association, W2<br />
* Marco Ciolli, Clara Tattoni, Paolo Zatelli, Pietro Zambelli, W14<br />
* Gérald Fenoy, GeoLabs, W07<br />
* Nicolas Bozon, 3LIZ, W07<br />
* Astrid Emde, Christoph Baudson, Toni Pignataro W5<br />
* Daniel Kastl, Georepublic, W10 (if the plane has no delay)<br />
* Mark Cave-Ayland, Sirius, W04<br />
* Mike Pumphrey, OpenGeo, W01<br />
* Tyler Mitchell, OSGeo, W8<br />
* Andrea Aime, OpenGeo, W01<br />
<br />
== Calendar ==<br />
<br />
* <strike>Jan 15, Opening Call for Workshops/Tutorials</strike> <br />
* <strike>Jan 30, Closing Call for Workshops/Tutorials </strike> <br />
* <strike>Feb 1-15, Workshop/Tutorial selection process</strike><br />
* <strike>Feb 16, Notification of acceptance for workshops/tutorials</strike><br />
* <strike>Feb 22, Registration for workshops and tutorials opens</strike><br />
* <strike>Jul 15 (aprox), Workshop software installation & testing @ classroom PCs.</strike><br />
* <strike>Aug 25, Manuals sent to printer shop.</strike><br />
* <strike>Aug 31, Printed copies ready.</strike><br />
* <strike>Sep 1, Workshops late software installs (v. gr. OSGeo-Live 4.0.1 VM).</strike><br />
* <strike>Sep 6 9:00 - 11:00 Workshop environment testing by instructors.</strike><br />
* <strike>Sep 6 13:00 - 14:55 Workshops REGISTRATION DESK opening hours.</strike><br />
* <strike>Sep 6 15:00 - 18:00 WORKSHOPS 1st SESSION: W1 to W7.</strike><br />
* <strike>Sep 7 8:00 - 8:55 Workshops REGISTRATION DESK opening hours.</strike><br />
* <strike>Sep 7 9:00-12:00 WORKSHOPS 2nd SESSION: W8 to W14.</strike><br />
* <strike>Sep 7-9, FOSS4G TUTORIALS (see schedule above).</strike><br />
* 2nd half Sept., Wrap-up: Evaluations, lessons learned, on-line materials.<br />
<br />
== On-line manuals ==<br />
<br />
Do you want your Workshop materials to be linked in the official web?<br />
Indicate YES or NO next to your workshop.<br />
Or, if you prefer that we link to your own hosted version, add the URL.<br />
<br />
* W1 Geoserver: http://workshops.opengeo.org/geoserver-intro/<br />
* W2 gvSIG: http://tinyurl.com/gvsig-foss4g10<br />
* W3 OSM: http://dbsgeo.com/foss4g2010/<br />
* W4 PostGIS: http://workshops.opengeo.org/postgis-intro/<br />
* W5 Mapbender: 3 PDF documents at: http://www.mapbender.org/FOSS4G_2010_Workshop_W5_-_Introduction_to_the_Mapbender_geoportal_framework#Workshop_documents<br />
* W6 Python: (PDF) and http://www.mapfish.org/doc/tutorials/python-workshop/<br />
* W7 ZOO Project: http://zoo-project.org/trac/wiki/ZooWorkshop2010/Content<br />
* W8 MapServer: (Full MS4W package, including docs) http://www.gatewaygeomatics.com/dl/mapserver-workshop/ms101_ms4w_foss4g2010.zip<br />
* W10 pgRouting: http://workshop.pgrouting.org<br />
* W11 OpenLayers: http://workshops.opengeo.org/openlayers-intro/<br />
* W12 GeoNetwork: [https://eos.geocat.net/download/workshops/foss4g2010/instructions.pdf Instructions] (PDF) - [https://eos.geocat.net/download/workshops/foss4g2010/gn260.zip ISO image of CD-ROM] (620MB) <br />
* W13 Java: http://docs.geotools.org/latest/tutorials/<br />
* W14 GRASS: (PDF)<br />
<br />
PDFs available at http://geoportal.dlsi.uji.es/fonts/foss4g/manuals/<br />
<br />
== Announcements ==<br />
* [[FOSS4G_2010_Press_Release_3|Call for Workshops and Tutorials (press release 3)]].<br />
* [[FOSS4G_2010_Press_Release_5|Workshops ready for inscriptions (press release 5)]].<br />
<br />
<br />
[[Category:FOSS4G2010]]<br />
[[Category:FOSS4G]]</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2011_Code_Sprint&diff=56139FOSS4G 2011 Code Sprint2011-07-24T05:10:54Z<p>Dkastl: /* Additional Interested People */</p>
<hr />
<div>== Code Sprint - what's that? ==<br />
<br />
[[Image:Code-sprint-foss4g2010.jpg|thumb|400px|FOSS4G 2010 code sprint, in Barcelona]]<br />
A code sprint is about getting a group together to work on Open Source software, sitting around a table and sharing ideas. It's not just about writing code, as you know a project has many needs including documentation, testing, and providing feedback. What a better way to give feedback and give back to the project that you love than to spend a day with the project's developers. There are roles needed to be filled, no matter what your expertise.<br />
<br />
With such a short timeframe (one day) you should probably use this page to set a specific goal for your project. But don't worry, if all you get done is actually sitting at the same table with the project's developers and talking about the next release, that is also great :)<br />
<br />
== Venue ==<br />
<br />
For map and more details see <br />
<br />
*Date: '''Saturday September 17th, 2011''' (the day after the conference). <br />
*Time: '''9am-5pm'''&nbsp; ([http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&month=9&day=17&hour=15&min=0&sec=0 timeandate])&nbsp; <br />
*'''Where:''' [http://www.tivoli.org/tivoli/ Tivoli Student Union building] (a former brewery), Auraria Campus<br />
[[Image:Tivoli-logo.jpg|150px]]<br />
<br />
Tivoli Student Union<br />
900 Auraria Parkway<br />
Denver, CO<br />
'''[http://www.openstreetmap.org/?lat=39.745249&lon=-105.005806&zoom=18&layers=M OSM map]'''<br />
<br />
*'''Rooms: (each room has a 60-70 person capacity)''' <br />
** room 440/540 (bilevel)<br />
** room 640<br />
<br />
== What to Bring ==<br />
<br />
* power bars (only outlets for 30 computers exist)<br />
<br />
== How to get there from the Sheraton ==<br />
<br />
The easiest way to get there from the Sheraton is to catch the free shuttle bus along 16th Street to Larimer, then it's about a half mile walk from there (7-10 minutes) - just take a left on Larimer and keep going straight into the campus. More detail to come shortly on how to get to the exact rooms etc.<br />
<br />
== Sponsor ==<br />
<br />
Please! contact organizers: Rafael Moreno, or [[Jeff McKenna]]<br />
<br />
== Questions/Comments/Ideas ==<br />
<br />
* ask on the foss4g2011 mailing list ([http://lists.osgeo.org/mailman/listinfo/foss4g2011 subscribe])<br />
<br />
== Additional Interested People ==<br />
<br />
The following people are potentially interested in participating in sprinting activities though have not yet established a Workgroup. <br />
<br />
* name:project<br />
<br />
* [[Daniel Kastl]]<br />
* Haruyuki Seki<br />
<br />
= Workgroups =<br />
<br />
To participate, copy a project skeleton and start a section below for your project. <br />
<br />
== Project-name ==<br />
<br />
'''Attending:''' <br />
<br />
* user<br />
* user<br />
<br />
'''Goals:''' <br />
<br />
* your goals<br />
<br />
== MapQuery ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:Vmische|Volker Mische]]<br />
* user<br />
<br />
'''Goals:''' <br />
<br />
* Making MapQUery more awesome<br />
* Talk to OpenLayers 3 people about the future<br />
<br />
== PostGIS ==<br />
<br />
'''Attending:''' <br />
<br />
* Paul Ramsey<br />
* Pierre Racine<br />
* you?<br />
<br />
'''Goals:''' <br />
<br />
* Close bugs and triage for 2.0 release<br />
<br />
== Opticks ==<br />
<br />
'''Attending:''' <br />
<br />
* Kip Streithorst<br />
* Trevor Clarke<br />
* Michael Considine<br />
<br />
'''Goals:''' <br />
<br />
* TBD<br />
<br />
== Mapnik ==<br />
<br />
I ([[User:springmeyer|Dane Springmeyer]]) can't make the code sprint (leaving the night of the 16th),<br />
so catch me during the conference to chat Mapnik coding.<br />
<br />
== OSGeo edu ==<br />
<br />
'''Attending:''' <br />
<br />
* Ari Jolma<br />
<br />
'''Goals:'''<br />
<br />
Possible things to do:<br />
<br />
* Set up a repository for joint development of edu materials and kick-start a few projects<br />
<br />
== MapServer ==<br />
<br />
'''Attending:''' <br />
<br />
* Michael Smith<br />
* [[Jeff McKenna]]<br />
* [[Thomas Bonfort]]<br />
* [[User:Schpidi|Stephan Meissl]]<br />
* [[User:fschindler|Fabian Schindler]]<br />
* [[User:Dmorissette|Daniel Morissette]]<br />
<br />
== libLAS / PDAL ==<br />
<br />
'''Attending:''' <br />
<br />
* Michael Smith<br />
<br />
== uDig ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:Jive|Jody Garnett]]<br />
<br />
'''Goals:''' <br />
<br />
* TBD<br />
<br />
'''Possible:'''<br />
<br />
* roll out CDO and a bit of QA on EMF goodness<br />
* migrate user guide to help plugin (since Eclipse has a Wiki Editor that supports textile)<br />
* refactor to *eu.udig* and make a verison release<br />
* GeoTools as OSGi (no more net.refractions.udig.libs) - see GeoTools below as this would require collaborative effort<br />
<br />
== GeoTools ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:Jive|Jody Garnett]]<br />
<br />
'''Goals:''' <br />
<br />
* TBD<br />
<br />
'''Possible:'''<br />
<br />
* Implement Query/Join for more than just JDBC-NG code<br />
* Get OSGi bundle information sorted (collaborate with downstream applications )<br />
* Set up new developers<br />
* Major Bug stomp <br />
* Technical Debt (FunctioName details; Remove old Filter code from test cases etc...)<br />
<br />
'''Collaboration:'''<br />
<br />
* uDig: Collaborate on OSGi rollout (ie Equinox testing)<br />
* GeoServer: Collaborate on OSGi rollout (ie Spring testing)<br />
* Zoo-Project: collaborate on WPS Client testing?</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=Talk:Live_GIS_Translate&diff=55849Talk:Live GIS Translate2011-06-30T14:13:16Z<p>Dkastl: /* de quickstart translations */</p>
<hr />
<div>== de quickstart translations ==<br />
; application status sheet<br />
* https://spreadsheets.google.com/ccc?key=0AlRFyY1XenjJdFRDbjFyWHg1MlNTRm10QXk0UWEzWlE&hl=en_GB&authkey=CPTB6uIE#gid=30<br />
<br />
'''fett''' -> erledigt<br />
<br />
* '''52nSOS_quickstart.rst''' -> projekt<br />
* 52nWPS_quickstart.rst -> projekt<br />
* atlasstyler_quickstart.rst -> projekt stefan<br />
* '''deegree_quickstart.rst''' -> projekt latlon<br />
* gdal_quickstart.rst -> astrid<br />
* geokettle_quickstart.rst <br />
* geomajas_quickstart.rst -> dominik<br />
* geonetwork_quickstart.rst -> david <br />
* geopublisher_quickstart.rst -> projekt stefan<br />
* geoserver_quickstart.rst -> frank<br />
* gmt_quickstart.rst<br />
* gpsdrive_quickstart.rst<br />
* grass_quickstart.rst -> otto<br />
* gvsig_quickstart.rst ruth<br />
* internationalisation_quickstart.rst<br />
* kosmo_quickstart.rst <br />
* '''mapbender_quickstart.rst''' -> astrid<br />
* mapfish_quickstart.rst -> dominik<br />
* mapguide_quickstart.rst <br />
* mapnik_quickstart.rst -> dominik<br />
* '''mapproxy_quickstart.rst''' -> dominik<br />
* mapserver_quickstart.rst -> otto <br />
* maptiler_quickstart.rst<br />
* marble_quickstart.rst<br />
* mb-system_quickstart.rst<br />
* opencpn_quickstart.rst<br />
* openjump_quickstart.rst<br />
* openlayers_quickstart.rst --> dominik<br />
* osgearth_quickstart.rst -> pirmin<br />
* osgeolive_install_quickstart.rst -> thomas<br />
* osgeolive_quickstart.rst -> thomas<br />
* osm_quickstart.rst<br />
* ossim_quickstart.rst -> otto<br />
* otb_quickstart.rst<br />
* '''pgrouting_quickstart.rst''' -> daniel<br />
* postgis_quickstart.rst -> astrid<br />
* prune_quickstart.rst<br />
* '''qgis_mapserver_quickstart.rst ''' -> primin<br />
* qgis_quickstart.rst -> pirmin <br />
* rasdaman_quickstart.rst -> projekt<br />
* R_quickstart.rst -> otto<br />
* saga_quickstart.rst -> otto<br />
* '''sahana_quickstart.rst''' -> daniel<br />
* '''spatialite_quickstart.rst''' -> daniel<br />
* tiny_ows -> primin<br />
* udig_quickstart.rst -> frank<br />
* usb_quickstart.rst -> thomas<br />
* '''ushahidi_quickstart.rst''' -> daniel<br />
* viking_quickstart.rst<br />
* virtualbox_quickstart.rst -> otto<br />
* '''zoo-project_quickstart.rst''' -> daniel<br />
* zygrib_quickstart.rst</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=Talk:Live_GIS_Translate&diff=55848Talk:Live GIS Translate2011-06-30T13:50:27Z<p>Dkastl: /* de quickstart translations */</p>
<hr />
<div>== de quickstart translations ==<br />
; application status sheet<br />
* https://spreadsheets.google.com/ccc?key=0AlRFyY1XenjJdFRDbjFyWHg1MlNTRm10QXk0UWEzWlE&hl=en_GB&authkey=CPTB6uIE#gid=30<br />
<br />
'''fett''' -> erledigt<br />
<br />
* '''52nSOS_quickstart.rst''' -> projekt<br />
* 52nWPS_quickstart.rst -> projekt<br />
* atlasstyler_quickstart.rst -> projekt stefan<br />
* '''deegree_quickstart.rst''' -> projekt latlon<br />
* gdal_quickstart.rst -> astrid<br />
* geokettle_quickstart.rst <br />
* geomajas_quickstart.rst -> dominik<br />
* geonetwork_quickstart.rst -> david <br />
* geopublisher_quickstart.rst -> projekt stefan<br />
* geoserver_quickstart.rst -> frank<br />
* gmt_quickstart.rst<br />
* gpsdrive_quickstart.rst<br />
* grass_quickstart.rst -> otto<br />
* gvsig_quickstart.rst ruth<br />
* internationalisation_quickstart.rst<br />
* kosmo_quickstart.rst <br />
* '''mapbender_quickstart.rst''' -> astrid<br />
* mapfish_quickstart.rst -> dominik<br />
* mapguide_quickstart.rst <br />
* mapnik_quickstart.rst -> dominik<br />
* '''mapproxy_quickstart.rst''' -> dominik<br />
* mapserver_quickstart.rst -> otto <br />
* maptiler_quickstart.rst<br />
* marble_quickstart.rst<br />
* mb-system_quickstart.rst<br />
* opencpn_quickstart.rst<br />
* openjump_quickstart.rst<br />
* openlayers_quickstart.rst --> dominik<br />
* osgearth_quickstart.rst -> pirmin<br />
* osgeolive_install_quickstart.rst -> thomas<br />
* osgeolive_quickstart.rst -> thomas<br />
* osm_quickstart.rst<br />
* ossim_quickstart.rst -> otto<br />
* otb_quickstart.rst<br />
* '''pgrouting_quickstart.rst''' -> daniel<br />
* postgis_quickstart.rst -> astrid<br />
* prune_quickstart.rst<br />
* '''qgis_mapserver_quickstart.rst ''' -> primin<br />
* qgis_quickstart.rst -> pirmin <br />
* rasdaman_quickstart.rst -> projekt<br />
* R_quickstart.rst -> otto<br />
* saga_quickstart.rst -> otto<br />
* sahana_quickstart.rst -> daniel<br />
* '''spatialite_quickstart.rst''' -> daniel<br />
* tiny_ows -> primin<br />
* udig_quickstart.rst -> frank<br />
* usb_quickstart.rst -> thomas<br />
* '''ushahidi_quickstart.rst''' -> daniel<br />
* viking_quickstart.rst<br />
* virtualbox_quickstart.rst -> otto<br />
* '''zoo-project_quickstart.rst''' -> daniel<br />
* zygrib_quickstart.rst</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=Talk:Live_GIS_Translate&diff=55847Talk:Live GIS Translate2011-06-30T13:21:21Z<p>Dkastl: /* de quickstart translations */</p>
<hr />
<div>== de quickstart translations ==<br />
; application status sheet<br />
* https://spreadsheets.google.com/ccc?key=0AlRFyY1XenjJdFRDbjFyWHg1MlNTRm10QXk0UWEzWlE&hl=en_GB&authkey=CPTB6uIE#gid=30<br />
<br />
'''fett''' -> erledigt<br />
<br />
* '''52nSOS_quickstart.rst''' -> projekt<br />
* 52nWPS_quickstart.rst -> projekt<br />
* atlasstyler_quickstart.rst -> projekt stefan<br />
* '''deegree_quickstart.rst''' -> projekt latlon<br />
* gdal_quickstart.rst -> astrid<br />
* geokettle_quickstart.rst <br />
* geomajas_quickstart.rst -> dominik<br />
* geonetwork_quickstart.rst -> david <br />
* geopublisher_quickstart.rst -> projekt stefan<br />
* geoserver_quickstart.rst -> frank<br />
* gmt_quickstart.rst<br />
* gpsdrive_quickstart.rst<br />
* grass_quickstart.rst -> otto<br />
* gvsig_quickstart.rst ruth<br />
* internationalisation_quickstart.rst<br />
* kosmo_quickstart.rst <br />
* '''mapbender_quickstart.rst''' -> astrid<br />
* mapfish_quickstart.rst -> dominik<br />
* mapguide_quickstart.rst <br />
* mapnik_quickstart.rst -> dominik<br />
* '''mapproxy_quickstart.rst''' -> dominik<br />
* mapserver_quickstart.rst -> otto <br />
* maptiler_quickstart.rst<br />
* marble_quickstart.rst<br />
* mb-system_quickstart.rst<br />
* opencpn_quickstart.rst<br />
* openjump_quickstart.rst<br />
* openlayers_quickstart.rst --> dominik<br />
* osgearth_quickstart.rst -> pirmin<br />
* osgeolive_install_quickstart.rst -> thomas<br />
* osgeolive_quickstart.rst -> thomas<br />
* osm_quickstart.rst<br />
* ossim_quickstart.rst -> otto<br />
* otb_quickstart.rst<br />
* '''pgrouting_quickstart.rst''' -> daniel<br />
* postgis_quickstart.rst -> astrid<br />
* prune_quickstart.rst<br />
* '''qgis_mapserver_quickstart.rst ''' -> primin<br />
* qgis_quickstart.rst -> pirmin <br />
* rasdaman_quickstart.rst -> projekt<br />
* R_quickstart.rst -> otto<br />
* saga_quickstart.rst -> otto<br />
* sahana_quickstart.rst -> daniel<br />
* '''spatialite_quickstart.rst''' -> daniel<br />
* tiny_ows -> primin<br />
* udig_quickstart.rst -> frank<br />
* usb_quickstart.rst -> thomas<br />
* ushahidi_quickstart.rst -> daniel<br />
* viking_quickstart.rst<br />
* virtualbox_quickstart.rst -> otto<br />
* '''zoo-project_quickstart.rst''' -> daniel<br />
* zygrib_quickstart.rst</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=Talk:Live_GIS_Translate&diff=55846Talk:Live GIS Translate2011-06-30T13:09:29Z<p>Dkastl: /* de quickstart translations */</p>
<hr />
<div>== de quickstart translations ==<br />
; application status sheet<br />
* https://spreadsheets.google.com/ccc?key=0AlRFyY1XenjJdFRDbjFyWHg1MlNTRm10QXk0UWEzWlE&hl=en_GB&authkey=CPTB6uIE#gid=30<br />
<br />
'''fett''' -> erledigt<br />
<br />
* '''52nSOS_quickstart.rst''' -> projekt<br />
* 52nWPS_quickstart.rst -> projekt<br />
* atlasstyler_quickstart.rst -> projekt stefan<br />
* '''deegree_quickstart.rst''' -> projekt latlon<br />
* gdal_quickstart.rst -> astrid<br />
* geokettle_quickstart.rst <br />
* geomajas_quickstart.rst -> dominik<br />
* geonetwork_quickstart.rst -> david <br />
* geopublisher_quickstart.rst -> projekt stefan<br />
* geoserver_quickstart.rst -> frank<br />
* gmt_quickstart.rst<br />
* gpsdrive_quickstart.rst<br />
* grass_quickstart.rst -> otto<br />
* gvsig_quickstart.rst ruth<br />
* internationalisation_quickstart.rst<br />
* kosmo_quickstart.rst <br />
* '''mapbender_quickstart.rst''' -> astrid<br />
* mapfish_quickstart.rst -> dominik<br />
* mapguide_quickstart.rst <br />
* mapnik_quickstart.rst -> dominik<br />
* '''mapproxy_quickstart.rst''' -> dominik<br />
* mapserver_quickstart.rst -> otto <br />
* maptiler_quickstart.rst<br />
* marble_quickstart.rst<br />
* mb-system_quickstart.rst<br />
* opencpn_quickstart.rst<br />
* openjump_quickstart.rst<br />
* openlayers_quickstart.rst --> dominik<br />
* osgearth_quickstart.rst -> pirmin<br />
* osgeolive_install_quickstart.rst -> thomas<br />
* osgeolive_quickstart.rst -> thomas<br />
* osm_quickstart.rst<br />
* ossim_quickstart.rst -> otto<br />
* otb_quickstart.rst<br />
* '''pgrouting_quickstart.rst''' -> daniel<br />
* postgis_quickstart.rst -> astrid<br />
* prune_quickstart.rst<br />
* '''qgis_mapserver_quickstart.rst ''' -> primin<br />
* qgis_quickstart.rst -> pirmin <br />
* rasdaman_quickstart.rst -> projekt<br />
* R_quickstart.rst -> otto<br />
* saga_quickstart.rst -> otto<br />
* sahana_quickstart.rst -> daniel<br />
* spatialite_quickstart.rst -> daniel<br />
* tiny_ows -> primin<br />
* udig_quickstart.rst -> frank<br />
* usb_quickstart.rst -> thomas<br />
* ushahidi_quickstart.rst -> daniel<br />
* viking_quickstart.rst<br />
* virtualbox_quickstart.rst -> otto<br />
* '''zoo-project_quickstart.rst''' -> daniel<br />
* zygrib_quickstart.rst</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=Talk:Live_GIS_Translate&diff=55836Talk:Live GIS Translate2011-06-30T07:38:48Z<p>Dkastl: /* de quickstart translations */</p>
<hr />
<div>== de quickstart translations ==<br />
; application status sheet<br />
* https://spreadsheets.google.com/ccc?key=0AlRFyY1XenjJdFRDbjFyWHg1MlNTRm10QXk0UWEzWlE&hl=en_GB&authkey=CPTB6uIE#gid=30<br />
<br />
'''fett''' -> erledigt<br />
<br />
* '''52nSOS_quickstart.rst''' -> projekt<br />
* 52nWPS_quickstart.rst -> projekt<br />
* atlasstyler_quickstart.rst -> projekt stefan<br />
* '''deegree_quickstart.rst''' -> projekt latlon<br />
* gdal_quickstart.rst -> astrid<br />
* geokettle_quickstart.rst <br />
* geomajas_quickstart.rst -> dominik<br />
* geonetwork_quickstart.rst -> david <br />
* geopublisher_quickstart.rst -> projekt stefan<br />
* geoserver_quickstart.rst -> frank<br />
* gmt_quickstart.rst<br />
* gpsdrive_quickstart.rst<br />
* grass_quickstart.rst -> otto<br />
* gvsig_quickstart.rst ruth<br />
* internationalisation_quickstart.rst<br />
* kosmo_quickstart.rst <br />
* '''mapbender_quickstart.rst''' -> astrid<br />
* mapfish_quickstart.rst -> dominik<br />
* mapguide_quickstart.rst <br />
* mapnik_quickstart.rst -> dominik<br />
* '''mapproxy_quickstart.rst''' -> dominik<br />
* mapserver_quickstart.rst -> otto <br />
* maptiler_quickstart.rst<br />
* marble_quickstart.rst<br />
* mb-system_quickstart.rst<br />
* opencpn_quickstart.rst<br />
* openjump_quickstart.rst<br />
* openlayers_quickstart.rst --> dominik<br />
* osgearth_quickstart.rst -> pirmin<br />
* osgeolive_install_quickstart.rst -> thomas<br />
* osgeolive_quickstart.rst -> thomas<br />
* osm_quickstart.rst<br />
* ossim_quickstart.rst -> otto<br />
* otb_quickstart.rst<br />
* '''pgrouting_quickstart.rst''' -> daniel<br />
* postgis_quickstart.rst -> astrid<br />
* prune_quickstart.rst<br />
* '''qgis_mapserver_quickstart.rst ''' -> primin<br />
* qgis_quickstart.rst -> pirmin <br />
* rasdaman_quickstart.rst -> projekt<br />
* R_quickstart.rst -> otto<br />
* saga_quickstart.rst -> otto<br />
* sahana_quickstart.rst -> daniel<br />
* spatialite_quickstart.rst -> daniel<br />
* tiny_ows -> primin<br />
* udig_quickstart.rst -> frank<br />
* usb_quickstart.rst -> thomas<br />
* ushahidi_quickstart.rst -> daniel<br />
* viking_quickstart.rst<br />
* virtualbox_quickstart.rst -> otto<br />
* zoo-project_quickstart.rst -> daniel<br />
* zygrib_quickstart.rst</div>Dkastlhttps://wiki.osgeo.org/w/index.php?title=Talk:Live_GIS_Translate&diff=55833Talk:Live GIS Translate2011-06-30T07:15:54Z<p>Dkastl: /* de quickstart translations */</p>
<hr />
<div>== de quickstart translations ==<br />
; application status sheet<br />
* https://spreadsheets.google.com/ccc?key=0AlRFyY1XenjJdFRDbjFyWHg1MlNTRm10QXk0UWEzWlE&hl=en_GB&authkey=CPTB6uIE#gid=30<br />
<br />
'''fett''' -> erledigt<br />
<br />
* '''52nSOS_quickstart.rst''' -> projekt<br />
* 52nWPS_quickstart.rst -> projekt<br />
* atlasstyler_quickstart.rst -> projekt stefan<br />
* '''deegree_quickstart.rst''' -> projekt latlon<br />
* gdal_quickstart.rst -> astrid<br />
* geokettle_quickstart.rst <br />
* geomajas_quickstart.rst<br />
* geonetwork_quickstart.rst -> david <br />
* geopublisher_quickstart.rst -> projekt stefan<br />
* geoserver_quickstart.rst -> frank<br />
* gmt_quickstart.rst<br />
* gpsdrive_quickstart.rst<br />
* grass_quickstart.rst -> otto<br />
* gvsig_quickstart.rst ruth<br />
* internationalisation_quickstart.rst<br />
* kosmo_quickstart.rst <br />
* '''mapbender_quickstart.rst''' -> astrid<br />
* mapfish_quickstart.rst<br />
* mapguide_quickstart.rst <br />
* mapnik_quickstart.rst<br />
* '''mapproxy_quickstart.rst''' -> dominik<br />
* mapserver_quickstart.rst -> otto <br />
* maptiler_quickstart.rst<br />
* marble_quickstart.rst<br />
* mb-system_quickstart.rst<br />
* opencpn_quickstart.rst<br />
* openjump_quickstart.rst<br />
* openlayers_quickstart.rst --> dominik<br />
* osgearth_quickstart.rst -> pirmin<br />
* osgeolive_install_quickstart.rst<br />
* osgeolive_quickstart.rst<br />
* osm_quickstart.rst<br />
* ossim_quickstart.rst -> otto<br />
* otb_quickstart.rst<br />
* pgrouting_quickstart.rst -> daniel<br />
* postgis_quickstart.rst -> astrid<br />
* prune_quickstart.rst<br />
* '''qgis_mapserver_quickstart.rst ''' -> primin<br />
* qgis_quickstart.rst -> pirmin <br />
* rasdaman_quickstart.rst -> projekt<br />
* R_quickstart.rst -> otto<br />
* saga_quickstart.rst -> otto<br />
* sahana_quickstart.rst -> daniel<br />
* spatialite_quickstart.rst -> daniel<br />
* tiny_ows -> primin<br />
* udig_quickstart.rst -> frank<br />
* usb_quickstart.rst<br />
* ushahidi_quickstart.rst -> daniel<br />
* viking_quickstart.rst<br />
* virtualbox_quickstart.rst -> otto<br />
* zoo-project_quickstart.rst -> daniel<br />
* zygrib_quickstart.rst</div>Dkastl