https://wiki.osgeo.org/w/api.php?action=feedcontributions&feedformat=atom&user=Wiki-RemanueleOSGeo - User contributions [en]2026-04-14T04:17:25ZUser contributionsMediaWiki 1.35.9https://wiki.osgeo.org/w/index.php?title=FOSS4GNA_Code_Sprint_2018&diff=114477FOSS4GNA Code Sprint 20182018-04-13T22:51:37Z<p>Wiki-Remanuele: /* Participation */</p>
<hr />
<div>[https://2018.foss4g-na.org/ FOSS4G NA 2018] includes a code-sprint as part of Community and Workshop day:<br />
<br />
* Workshops: Your $45 registration includes access to T-REX location, and two workshops: register [https://2018.foss4g-na.org/registration online here]).<br />
* Update: The brand new osgeo-us local chapter has arranged for additional space nearby making the code-sprint free to attend! Thank you so much!<br />
<br />
== Projects Attending == <br />
<br />
(i.e what do you wish/want/plan to work on during the sprint ?)<br />
<br />
GeoTools<br />
* Java Jigsaw prep!<br />
<br />
GeoMesa<br />
* Spark integration<br />
<br />
JTS <br />
* 2.0.0 Roadmap work<br />
<br />
GeoTrellis<br />
* Roadmap discussion<br />
<br />
== Participation ==<br />
<br />
Preparation:<br />
<br />
* Bring your own laptop<br />
* Install GIT and compiler tools, and come with a working development environment<br />
<br />
Please add your name and the projects you are planning to sprint and note the likeliness of your attendance.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="25"|No<br />
!width="250"|Name<br />
!width="100"|Country<br />
!width="250"|Email<br />
!width="250"|Organisation<br />
!width="250"|Projects<br />
!width="200"|Attending<br />
|-<br />
| 1 ||[[Jody Garnett]] <libravatar email="jody.garnett@gmail.com"/> || CA || jody.garnett@gmail.com || OSGeo || GeoTools, JTS || Limited, workshop coordinator<br />
|-<br />
| 2 ||[[Eugene Cheipesh]] <libravatar email="echeipesh@gmail.com"/> || USA || echeipesh@gmail.com || Azavea || GeoTrellis || Full<br />
|-<br />
| 2 ||[[User:remanuele|Rob Emanuele]] <libravatar email="rdemanuele@gmail.com"/> || USA || rdemanuele@gmail.com || Azavea || GeoTrellis, JTS || Full<br />
|}<br />
<br />
[[Category:Code Sprints]]<br />
[[Category:FOSS4GNA]]</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=FOSS4GNA_Code_Sprint_2018&diff=114476FOSS4GNA Code Sprint 20182018-04-13T22:51:23Z<p>Wiki-Remanuele: /* Participation */</p>
<hr />
<div>[https://2018.foss4g-na.org/ FOSS4G NA 2018] includes a code-sprint as part of Community and Workshop day:<br />
<br />
* Workshops: Your $45 registration includes access to T-REX location, and two workshops: register [https://2018.foss4g-na.org/registration online here]).<br />
* Update: The brand new osgeo-us local chapter has arranged for additional space nearby making the code-sprint free to attend! Thank you so much!<br />
<br />
== Projects Attending == <br />
<br />
(i.e what do you wish/want/plan to work on during the sprint ?)<br />
<br />
GeoTools<br />
* Java Jigsaw prep!<br />
<br />
GeoMesa<br />
* Spark integration<br />
<br />
JTS <br />
* 2.0.0 Roadmap work<br />
<br />
GeoTrellis<br />
* Roadmap discussion<br />
<br />
== Participation ==<br />
<br />
Preparation:<br />
<br />
* Bring your own laptop<br />
* Install GIT and compiler tools, and come with a working development environment<br />
<br />
Please add your name and the projects you are planning to sprint and note the likeliness of your attendance.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="25"|No<br />
!width="250"|Name<br />
!width="100"|Country<br />
!width="250"|Email<br />
!width="250"|Organisation<br />
!width="250"|Projects<br />
!width="200"|Attending<br />
|-<br />
| 1 ||[[Jody Garnett]] <libravatar email="jody.garnett@gmail.com"/> || CA || jody.garnett@gmail.com || OSGeo || GeoTools, JTS || Limited, workshop coordinator<br />
|-<br />
| 2 ||[[Eugene Cheipesh]] <libravatar email="echeipesh@gmail.com"/> || USA || echeipesh@gmail.com || Azavea || GeoTrellis || Full<br />
|-<br />
| 2 ||[[User:remanuele|Rob Emanuele]] <libravatar email="rdemanuele@gmail.com"/> || CA || rdemanuele@gmail.com || Azavea || GeoTrellis, JTS || Full<br />
|}<br />
<br />
[[Category:Code Sprints]]<br />
[[Category:FOSS4GNA]]</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=OSGeo_Code_Sprint_2018&diff=112327OSGeo Code Sprint 20182018-01-02T22:21:51Z<p>Wiki-Remanuele: /* Participants */</p>
<hr />
<div>Annual Code Sprint comes to Bonn (Germany) in 2018! <br />
<br />
Powered by [[Image:Osgeo-logo.png|250px|link=http://www.osgeo.org]]<br />
<br />
'''Sponsoring ''' Find out about [[OSGeo_Code_Sprint_2018#Sponsoring |Sponsoring the Event]].<br />
<br />
;Gold Sponsors <br />
<br />
[[File:Logo-FOSSGIS-e.V.png|260px|FOSSGIS e.V.|link=http://www.fossgis.de]]<br />
<br />
; Silver Sponsors <br />
<br />
; Bronze Sponsors <br />
<br />
{| border=0 cellspacing=15 cellpadding=10<br />
|<br />
[[File:Logo-Azavea.png|280px|Azavea|link=http://www.azavea.com/]]<br />
<br><br />
http://www.azavea.com/<br />
|<br />
[[File:WhereGroup_logo_418x110.png|290px|WhereGroup|link=https://www.wheregroup.com/]]<br />
<br><br />
https://www.wheregroup.com/<br />
|<br />
[[File:Logo-EOX.png|120px|EOX IT Services GmbH|link=http://eox.at]]<br />
<br><br />
[http://eox.at http://eox.at] <br />
|}<br />
<br />
In 2018 we once again want to invite you to Bonn to meet for codesprint at Basecamp! ....<br />
<br />
[[Image:FOSS4G_2016_OSGeo_Code_Sprint_indoor_hacking_overview.jpg|400px|thumb|right]]<br />
[[Image:FOSS4G_OSGeo_Code_Sprint_in_Action1.jpg|400px|thumb|right]]<br />
<br />
[[Image:Basecamp5.png|300px|thumb]]<br />
[[Image:Basecamp6.png|300px|thumb]]<br />
[[Image:Basecamp7.png|300px|thumb]]<br />
[[Image:Basecamp1.png|300px|thumb]]<br />
<br />
[[Image:FOSS4G_2016_OSGeo_Code_Sprint_sponsors.jpg|400px]]<br />
<br />
<br />
== Purpose ==<br />
<br />
Bring together project members to make decisions and tackle larger geospatial <br />
problems as in previous years: <br />
* [[Daytona Beach Code Sprint 2017|Daytona_Beach]] (2017)<br />
* [[Paris Code Sprint 2016|Paris]] (2016)<br />
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)<br />
* [[Vienna Code Sprint 2014|Vienna]] (2014)<br />
* [[Boston Code Sprint 2013|Boston]] (2013)<br />
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)<br />
* [[Montreal Code Sprint 2011|Montreal]] (2011)<br />
* [[New York Code Sprint 2010|New York City]] (2010)<br />
* [[Toronto Code Sprint 2009|Toronto]] (2009)<br />
<br />
<br />
== Dates and Times ==<br />
<br />
Dates: <br />
* Sprint: Sunday-Sunday, March 18 to 25, 2018 (8 days - Arrival/Departure Sundays)<br />
<br />
== Other Events from January to March 2018 ==<br />
<br />
* '''OSGeo's 12th birthday Feb 4'''<br />
* FOSDEM 3-4 Feb https://fosdem.org/2018/<br />
* FOSS4G IT 19-22 Feb http://foss4g-it2018.gfoss.it/<br />
* [https://github.com/qgis/QGIS/wiki/DeveloperMeetingMadeira2018 QGis Hackfest] 21-25 Feb, 2018<br />
* FOSSGIS 21-24 March https://www.fossgis-konferenz.de/2018/<br />
* ''please add your event''<br />
<br />
== Location ==<br />
<br />
=== Coding Venue ===<br />
* Venue & Accommodation BaseCamp. <br />
* For more informations: http://www.basecamp-bonn.com/<br />
* [http://www.openstreetmap.org/way/44335958#map=18/50.70763/7.12316| OpenStreetMap]<br />
<br />
<br />
=== Accommodations ===<br />
* we will publish the hotel booking system here soon. This will also enable to book the caravans in base camp. All bookers that use this system will receive a free oublic transport ticket that is valid during your stay.<br />
<br />
=== How to get there ===<br />
* http://alienus.de/basecamp1/en/arrival-bonn-hostel/<br />
* http://www.openstreetmap.org/search?query=raste%201%20bonn#map=18/50.70762/7.12383<br />
<br />
By train<br />
* From Bonn Main station take the U-Trains (Underground platform) 16, 63 or 68. Get off after 6 min at stop Dt. Telekom / Ollenhauerstr. <br />
* http://alienus.de/basecamp1/en/arrival-bonn-hostel/<br />
* http://www.openstreetmap.org/search?query=raste%201%20bonn#map=18/50.70762/7.12383<br />
* [https://www.vrsinfo.de/englisch/the-vrs/vrs-about-us.html online public transport planner]<br />
<br />
By Car<br />
* Coming from the highway A59 Basecamp is located at the end of the highway A562. For navigation systems it is best to type Basecamp's address: "''In der Raste 3, 53129 Bonn''")<br />
<br />
== Schedule ==<br />
* tbd<br />
<br />
== Project Plans ==<br />
(i.e what do you wish/want/plan to work on during the sprint ?)<br />
<br />
* '''GRASS GIS project''': See [https://grasswiki.osgeo.org/wiki/GRASS_Community_Sprint_Bonn_2018 dedicated Wiki page]<br />
* tbd<br />
<br />
== Social ideas ==<br />
<br />
<br />
== Participants ==<br />
<br />
We are planning for attendance of ~50. Please add your name and the projects <br />
you are planning to sprint and note the likeliness of your attendance.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="25"|No<br />
!width="250"|Name<br />
!width="100"|Country<br />
!width="250"|Email<br />
!width="250"|Organisation<br />
!width="250"|Projects<br />
!width="25"|sun<br />
!width="25"|mon<br />
!width="25"|tue<br />
!width="25"|wed<br />
!width="25"|thu<br />
!width="25"|fri<br />
!width="25"|sat<br />
!width="25"|sun<br />
!width="60"|Accommodation<br />
!width="30"|vegetarian food<br />
|-<br />
| 1 ||[[Jeff McKenna]] <libravatar email="jmckenna@gatewaygeomatics.com"/> || CA || jmckenna(at)osgeo.org || OSGeo || MapServer, MS4W, ZOO-Project || x || x || x || x || x || x || x || x || shared accommodation || <br />
|-<br />
| 2 ||[[Howard Butler]] || US || howard@hobu.co || Hobu, Inc. || Proj.4, PDAL, GDAL, Point clouds || || x || x || x || x || x || || || || No thank you.<br />
|-<br />
| 3 ||[[Even Rouault]] || FR || even.rouault(at)spatialys.com || Spatialys || Proj.4, GDAL, MapServer || || x || x || x || x || x || || || BaseCamp if possible ||<br />
|-<br />
| 4 ||[[Markus Neteler]] || DE || neteler(at)osgeo.org || mundialis || GRASS GIS (Proj.4, GDAL, OTB, QGIS) || x || x || x || x || x || x || x || x || || preferably<br />
|-<br />
| 5 ||[[User:Djay|Gérald Fenoy]] || FR || gerald.fenoy(at)geolabs.fr || GeoLabs || MS4W, ZOO-Project || x || x || x || x || x || x || x || x || shared accommodation || <br />
|-<br />
| 6 ||[[User:Schpidi|Stephan Meißl]] || AT || stephan(at)meissl.name || EOX || MapServer, EOxServer || x || x || x || x || x || x || x || x || BaseCamp || <br />
|-<br />
| 7 ||[[User:martinl|Martin Landa]] || CZ || landa.martin(at)gmail.com || CTU in Prague || GRASS GIS (Proj.4, GDAL, PostGIS, QGIS) || x || x || x || x || x || x || x || x || BaseCamp ||<br />
|-<br />
| 8 ||[[User:connormanning|Connor Manning]] || US || connor@hobu.co || Hobu, Inc. || Entwine, Greyhound, PDAL, Point clouds || x || x || x || x || x || x || x || x || ||<br />
|-<br />
| 9 ||Markus Schütz || AT || mschuetz@potree.org|| TU Wien|| Potree, point clouds|| x || x || x || || || || || || || <br />
|-<br />
| 10 ||[[User:Tomkralidis|Tom Kralidis]] || CA || tomkralidis(at)gmail.com || self || pycsw, OWSLib, pygeometa, MapServer, geocatalogo || x || x || x || x || x || || || || tbd || sure <br />
|-<br />
| 11 ||[[User:kalxas|Angelos Tzotsos]] || GR || tzotsos(at)osgeo.org || OSGeo || pycsw, OSGeoLive, GeoNode, UbuntuGIS, geocatalogo, OTB, ZOO-Project || x || x || x || x || x || x || x || x || tbd || probably <br />
|-<br />
| 12 ||[[User:jjesus|Jorge Samuel Mendes de Jesus]] || NL || jorge.dejesus(at)geocat.net || Geocat || pywps || || x || x || x || x || x || x || || tbd || NO! <br />
|-<br />
| 13 ||[[User:ingenieroariel|Ariel Núñez]] || CO || ariel(at)terranodo.io || Terranodo || GeoNode || x || x || x || x || x || x || x || x || tbd || <br />
|-<br />
| 14 ||[[User:Lads|Luís de Sousa]] || PT & NL || luis.de.sousa(at)protonmail.ch || [http://www.isric.org ISRIC] || PyWPS, GRASS || || || x || x || x || x || x || x || BaseCamp || <br />
|-<br />
| 15 ||[[User:Vmische|Volker Mische]] || DE || volker.mische(at)gmail,com || Myself || Noise, CouchDB || x || x || x || x || x || x || x || x || BaseCamp || 50% <br />
|-<br />
| 16 ||[[User:Just|Just van den Broecke]] || NL || justb4(at)gmail,com || Myself || GeoHealthCheck, Stetl || x || x || x || x || x || x || x || x || tbd || - <br />
|-<br />
| 17 ||[[User:Jgrocha|Jorge Gustavo Rocha]] || PT || jgr@geomaster.pt || Geomaster || QGIS, GeoExt 3 || || x || x || x || x || x || 2 x || 2 x || BaseCamp (+ extra bed for the last 2 days for my daughter Rita, if possible) || <br />
|-<br />
| 18 ||[[User:tfr42|Torsten Friebe]] || DE || friebe AT lat-lon DOT de || organization || deegree || x || x || x || x || x || x || x || x || not needed || yes, please<br />
|-<br />
| 19 ||[[User:Stenger|Dirk Stenger]] || DE || stenger AT lat-lon DOT de || organization || deegree || || x || x || x || x || x || || || not needed || <br />
|-<br />
| 20 ||[[User:Lgoltz|Lyn Goltz]] || DE || goltz AT lat-lon DOT de || organization || deegree || || x || x || x || x || x || x || x || not needed || yes<br />
|-<br />
| 21 ||[[User:remanuele|Rob Emanuele]] || US || remanuele@azavea.com ||Azavea || PDAL, GDAL, Point clouds, GeoTrellis, LocationTech || || x || x || x || x || x || || || || <br />
|-<br />
| 22 || Grigory Pomadchin || RU || gr.pomadchin AT gmail DOT com || Azavea || PDAL, GDAL, Point clouds, GeoTrellis || || x || x || x || x || x || || || || <br />
|-<br />
| 23 ||[[User:tomvantilburg|Tom van Tilburg]] || NL || tom.van.tilburg@geodan.nl || geodan || Pointcloud || x || x || x || x || x || x || x || x || tbd || x|-<br />
|-<br />
| 24 ||[[User:chambbj|Brad Chambers]] || US || bradley.chambers@digitalglobe.com || Radiant Solutions || PDAL, Point Clouds || || x || x || x || x || x || || || TBD || No thanks!<br />
|-<br />
| 25 || Eugene Cheipesh || USA || echeipesh AT azavea DOT com || Azavea || LocationTech, JTS, JAI Replacement || || x || x || x || x || x || || || || <br />
<br />
|-<br />
| # ||[[User:your osgeo profile|Your name]] || DE || email || organization || project || x || x || x || x || x || x || x || x || x || x|-<br />
|}<br />
<br />
== Communication ==<br />
<br />
* Please join the mailing list: http://lists.osgeo.org/mailman/listinfo/tosprint<br />
* IRC chat during the event: #tosprint Server: irc.freenode.net<br />
* Twitter: #TOSprint ( https://twitter.com/search?q=tosprint )<br />
<br />
== Photos ==<br />
<br />
== Costs ==<br />
<br />
Participants should plan for the following costs:<br />
<br />
* Travel to Bonn<br />
* Accommodation for x nights <br />
<br />
All other costs - food, outings and entertainment - should/will be covered by the sponsors<br />
<br />
<br />
<br />
== Financial == <br />
<br />
'''Detailed budget'''<br />
* [[Bonn_Code_Sprint_2018_:_Budget|Budget]]<br />
<br />
== Individual preparation ==<br />
<br />
* Bring your own laptop<br />
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:Schuko_plug_and_socket.png Germany]). See also http://www.power-plugs-sockets.com/<br />
* Install GIT and compiler tools, and come with a working development environment<br />
<br />
== Sponsoring ==<br />
<br />
The Open Source Geospatial Foundation (OSGeo) has a long tradition of organizing code sprints for developers of Open Source GIS software.<br />
(https://wiki.osgeo.org/wiki/Category:Code_Sprints).<br />
<br />
Simultaneously with the [https://www.fossgis-konferenz.de/2018/ FOSSGIS Conference 2018 in Bonn] an international code sprint of the OSGeo will take place from 19 to 25 March 2018.<br />
We expect about 80 developers from all over the world to come from various [http://www.osgeo.org/] projects. Whether desktop application, geospatial library, metadata catalog or web mapping: be sure to find products in the list that you use. Thus, the Code Sprint is also an opportunity for your developers to meet with the core developers of the projects, get a deeper insight into the software and participate in the development.<br />
<br />
The code sprint will take place at [http://www.basecamp-bonn.de/ BaseCamp] in Bonn. During the [http://www.foss4g2016.org/home.html FOSS4G 2016] in Bonn we have already organized a code sprint at this location, in which about 100 developers worked on the open source projects every day. (https://wiki.osgeo.org/wiki/FOSS4G_2016_Code_Sprint)<br />
<br />
In addition to the costs of providing the technical infrastructure, the cost of food and drinks for the developers is the main cost. A buffet at lunchtime and drinks during the whole day are intended.<br />
<br />
So far, the code sprint is already sponsored by [http://www.osgeo.org/ OSGeo] and [https://www.fossgis.de/ FOSSGIS e. V.].<br />
<br />
In order to cover the costs, we would be very pleased about further sponsors!<br />
<br />
What we offer:<br />
* Your logo on top of the [http://osgeo.getinteractive.nl/events/osgeo-code-sprint-2018/ websites of the Code Sprint] [https://wiki.osgeo.org/wiki/OSGeo_Code_Sprint_2018 1] as well as on all official documents around the Code Sprint<br />
* Mention in all code sprint related mails<br />
* Our undying gratitude, which comes in handy when you least expect it (Remember that feature you wanted...)<br />
<br />
Our sponsorship levels:<br />
* Gold: >= 2500 USD<br />
* Silver: 1500 USD<br />
* Bronze: 750 USD<br />
<br />
So...<br />
* get your company talking to the top developers of the scene!<br />
* enable your GIS developers to take advantage of this opportunity, there is no better opportunity to learn!<br />
* support the software you use - you benefit immediately.<br />
<br />
Thank you very much!<br />
<br />
Contact: To sponsor, please contact codesprint@osgeo.org directly.<br />
<br />
<br />
== Event Owner ==<br />
* [[User:Astrid_Emde|Astrid Emde]]<br />
* Uli Rothstein<br />
* Carmen Tawalika<br />
* [[User:Olr|Oliver Rudzick]]<br />
* Mirko Blinn<br />
<br />
; Supported by<br />
* [[User:Lucadelu|Luca Delucchi]]<br />
[[Category:Code Sprints]]<br />
[[Category:C Tribe Code Sprint]]</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=OSGeo_Code_Sprint_2018&diff=112326OSGeo Code Sprint 20182018-01-02T22:21:27Z<p>Wiki-Remanuele: /* Participants */</p>
<hr />
<div>Annual Code Sprint comes to Bonn (Germany) in 2018! <br />
<br />
Powered by [[Image:Osgeo-logo.png|250px|link=http://www.osgeo.org]]<br />
<br />
'''Sponsoring ''' Find out about [[OSGeo_Code_Sprint_2018#Sponsoring |Sponsoring the Event]].<br />
<br />
;Gold Sponsors <br />
<br />
[[File:Logo-FOSSGIS-e.V.png|260px|FOSSGIS e.V.|link=http://www.fossgis.de]]<br />
<br />
; Silver Sponsors <br />
<br />
; Bronze Sponsors <br />
<br />
{| border=0 cellspacing=15 cellpadding=10<br />
|<br />
[[File:Logo-Azavea.png|280px|Azavea|link=http://www.azavea.com/]]<br />
<br><br />
http://www.azavea.com/<br />
|<br />
[[File:WhereGroup_logo_418x110.png|290px|WhereGroup|link=https://www.wheregroup.com/]]<br />
<br><br />
https://www.wheregroup.com/<br />
|<br />
[[File:Logo-EOX.png|120px|EOX IT Services GmbH|link=http://eox.at]]<br />
<br><br />
[http://eox.at http://eox.at] <br />
|}<br />
<br />
In 2018 we once again want to invite you to Bonn to meet for codesprint at Basecamp! ....<br />
<br />
[[Image:FOSS4G_2016_OSGeo_Code_Sprint_indoor_hacking_overview.jpg|400px|thumb|right]]<br />
[[Image:FOSS4G_OSGeo_Code_Sprint_in_Action1.jpg|400px|thumb|right]]<br />
<br />
[[Image:Basecamp5.png|300px|thumb]]<br />
[[Image:Basecamp6.png|300px|thumb]]<br />
[[Image:Basecamp7.png|300px|thumb]]<br />
[[Image:Basecamp1.png|300px|thumb]]<br />
<br />
[[Image:FOSS4G_2016_OSGeo_Code_Sprint_sponsors.jpg|400px]]<br />
<br />
<br />
== Purpose ==<br />
<br />
Bring together project members to make decisions and tackle larger geospatial <br />
problems as in previous years: <br />
* [[Daytona Beach Code Sprint 2017|Daytona_Beach]] (2017)<br />
* [[Paris Code Sprint 2016|Paris]] (2016)<br />
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)<br />
* [[Vienna Code Sprint 2014|Vienna]] (2014)<br />
* [[Boston Code Sprint 2013|Boston]] (2013)<br />
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)<br />
* [[Montreal Code Sprint 2011|Montreal]] (2011)<br />
* [[New York Code Sprint 2010|New York City]] (2010)<br />
* [[Toronto Code Sprint 2009|Toronto]] (2009)<br />
<br />
<br />
== Dates and Times ==<br />
<br />
Dates: <br />
* Sprint: Sunday-Sunday, March 18 to 25, 2018 (8 days - Arrival/Departure Sundays)<br />
<br />
== Other Events from January to March 2018 ==<br />
<br />
* '''OSGeo's 12th birthday Feb 4'''<br />
* FOSDEM 3-4 Feb https://fosdem.org/2018/<br />
* FOSS4G IT 19-22 Feb http://foss4g-it2018.gfoss.it/<br />
* [https://github.com/qgis/QGIS/wiki/DeveloperMeetingMadeira2018 QGis Hackfest] 21-25 Feb, 2018<br />
* FOSSGIS 21-24 March https://www.fossgis-konferenz.de/2018/<br />
* ''please add your event''<br />
<br />
== Location ==<br />
<br />
=== Coding Venue ===<br />
* Venue & Accommodation BaseCamp. <br />
* For more informations: http://www.basecamp-bonn.com/<br />
* [http://www.openstreetmap.org/way/44335958#map=18/50.70763/7.12316| OpenStreetMap]<br />
<br />
<br />
=== Accommodations ===<br />
* we will publish the hotel booking system here soon. This will also enable to book the caravans in base camp. All bookers that use this system will receive a free oublic transport ticket that is valid during your stay.<br />
<br />
=== How to get there ===<br />
* http://alienus.de/basecamp1/en/arrival-bonn-hostel/<br />
* http://www.openstreetmap.org/search?query=raste%201%20bonn#map=18/50.70762/7.12383<br />
<br />
By train<br />
* From Bonn Main station take the U-Trains (Underground platform) 16, 63 or 68. Get off after 6 min at stop Dt. Telekom / Ollenhauerstr. <br />
* http://alienus.de/basecamp1/en/arrival-bonn-hostel/<br />
* http://www.openstreetmap.org/search?query=raste%201%20bonn#map=18/50.70762/7.12383<br />
* [https://www.vrsinfo.de/englisch/the-vrs/vrs-about-us.html online public transport planner]<br />
<br />
By Car<br />
* Coming from the highway A59 Basecamp is located at the end of the highway A562. For navigation systems it is best to type Basecamp's address: "''In der Raste 3, 53129 Bonn''")<br />
<br />
== Schedule ==<br />
* tbd<br />
<br />
== Project Plans ==<br />
(i.e what do you wish/want/plan to work on during the sprint ?)<br />
<br />
* '''GRASS GIS project''': See [https://grasswiki.osgeo.org/wiki/GRASS_Community_Sprint_Bonn_2018 dedicated Wiki page]<br />
* tbd<br />
<br />
== Social ideas ==<br />
<br />
<br />
== Participants ==<br />
<br />
We are planning for attendance of ~50. Please add your name and the projects <br />
you are planning to sprint and note the likeliness of your attendance.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="25"|No<br />
!width="250"|Name<br />
!width="100"|Country<br />
!width="250"|Email<br />
!width="250"|Organisation<br />
!width="250"|Projects<br />
!width="25"|sun<br />
!width="25"|mon<br />
!width="25"|tue<br />
!width="25"|wed<br />
!width="25"|thu<br />
!width="25"|fri<br />
!width="25"|sat<br />
!width="25"|sun<br />
!width="60"|Accommodation<br />
!width="30"|vegetarian food<br />
|-<br />
| 1 ||[[Jeff McKenna]] <libravatar email="jmckenna@gatewaygeomatics.com"/> || CA || jmckenna(at)osgeo.org || OSGeo || MapServer, MS4W, ZOO-Project || x || x || x || x || x || x || x || x || shared accommodation || <br />
|-<br />
| 2 ||[[Howard Butler]] || US || howard@hobu.co || Hobu, Inc. || Proj.4, PDAL, GDAL, Point clouds || || x || x || x || x || x || || || || No thank you.<br />
|-<br />
| 3 ||[[Even Rouault]] || FR || even.rouault(at)spatialys.com || Spatialys || Proj.4, GDAL, MapServer || || x || x || x || x || x || || || BaseCamp if possible ||<br />
|-<br />
| 4 ||[[Markus Neteler]] || DE || neteler(at)osgeo.org || mundialis || GRASS GIS (Proj.4, GDAL, OTB, QGIS) || x || x || x || x || x || x || x || x || || preferably<br />
|-<br />
| 5 ||[[User:Djay|Gérald Fenoy]] || FR || gerald.fenoy(at)geolabs.fr || GeoLabs || MS4W, ZOO-Project || x || x || x || x || x || x || x || x || shared accommodation || <br />
|-<br />
| 6 ||[[User:Schpidi|Stephan Meißl]] || AT || stephan(at)meissl.name || EOX || MapServer, EOxServer || x || x || x || x || x || x || x || x || BaseCamp || <br />
|-<br />
| 7 ||[[User:martinl|Martin Landa]] || CZ || landa.martin(at)gmail.com || CTU in Prague || GRASS GIS (Proj.4, GDAL, PostGIS, QGIS) || x || x || x || x || x || x || x || x || BaseCamp ||<br />
|-<br />
| 8 ||[[User:connormanning|Connor Manning]] || US || connor@hobu.co || Hobu, Inc. || Entwine, Greyhound, PDAL, Point clouds || x || x || x || x || x || x || x || x || ||<br />
|-<br />
| 9 ||Markus Schütz || AT || mschuetz@potree.org|| TU Wien|| Potree, point clouds|| x || x || x || || || || || || || <br />
|-<br />
| 10 ||[[User:Tomkralidis|Tom Kralidis]] || CA || tomkralidis(at)gmail.com || self || pycsw, OWSLib, pygeometa, MapServer, geocatalogo || x || x || x || x || x || || || || tbd || sure <br />
|-<br />
| 11 ||[[User:kalxas|Angelos Tzotsos]] || GR || tzotsos(at)osgeo.org || OSGeo || pycsw, OSGeoLive, GeoNode, UbuntuGIS, geocatalogo, OTB, ZOO-Project || x || x || x || x || x || x || x || x || tbd || probably <br />
|-<br />
| 12 ||[[User:jjesus|Jorge Samuel Mendes de Jesus]] || NL || jorge.dejesus(at)geocat.net || Geocat || pywps || || x || x || x || x || x || x || || tbd || NO! <br />
|-<br />
| 13 ||[[User:ingenieroariel|Ariel Núñez]] || CO || ariel(at)terranodo.io || Terranodo || GeoNode || x || x || x || x || x || x || x || x || tbd || <br />
|-<br />
| 14 ||[[User:Lads|Luís de Sousa]] || PT & NL || luis.de.sousa(at)protonmail.ch || [http://www.isric.org ISRIC] || PyWPS, GRASS || || || x || x || x || x || x || x || BaseCamp || <br />
|-<br />
| 15 ||[[User:Vmische|Volker Mische]] || DE || volker.mische(at)gmail,com || Myself || Noise, CouchDB || x || x || x || x || x || x || x || x || BaseCamp || 50% <br />
|-<br />
| 16 ||[[User:Just|Just van den Broecke]] || NL || justb4(at)gmail,com || Myself || GeoHealthCheck, Stetl || x || x || x || x || x || x || x || x || tbd || - <br />
|-<br />
| 17 ||[[User:Jgrocha|Jorge Gustavo Rocha]] || PT || jgr@geomaster.pt || Geomaster || QGIS, GeoExt 3 || || x || x || x || x || x || 2 x || 2 x || BaseCamp (+ extra bed for the last 2 days for my daughter Rita, if possible) || <br />
|-<br />
| 18 ||[[User:tfr42|Torsten Friebe]] || DE || friebe AT lat-lon DOT de || organization || deegree || x || x || x || x || x || x || x || x || not needed || yes, please<br />
|-<br />
| 19 ||[[User:Stenger|Dirk Stenger]] || DE || stenger AT lat-lon DOT de || organization || deegree || || x || x || x || x || x || || || not needed || <br />
|-<br />
| 20 ||[[User:Lgoltz|Lyn Goltz]] || DE || goltz AT lat-lon DOT de || organization || deegree || || x || x || x || x || x || x || x || not needed || yes<br />
|-<br />
| 21 ||[[User:remanuele|Rob Emanuele]] || US || remanuele@azavea.com ||Azavea || PDAL, GDAL, Point clouds, GeoTrellis, LocationTech || || x || x || x || x || x || || || || <br />
|-<br />
| 22 || Grigory Pomadchin || RU || gr.pomadchin AT gmail DOT com || Azavea || PDAL, GDAL, Point clouds, GeoTrellis || || x || x || x || x || x || || || || <br />
|-<br />
| 23 ||[[User:tomvantilburg|Tom van Tilburg]] || NL || tom.van.tilburg@geodan.nl || geodan || Pointcloud || x || x || x || x || x || x || x || x || tbd || x|-<br />
|-<br />
| # ||[[User:chambbj|Brad Chambers]] || US || bradley.chambers@digitalglobe.com || Radiant Solutions || PDAL, Point Clouds || || x || x || x || x || x || || || TBD || No thanks!<br />
|-<br />
| 22 || Eugene Cheipesh || USA || echeipesh AT azavea DOT com || Azavea || LocationTech, JTS, JAI Replacement || || x || x || x || x || x || || || || <br />
<br />
|-<br />
| # ||[[User:your osgeo profile|Your name]] || DE || email || organization || project || x || x || x || x || x || x || x || x || x || x|-<br />
|}<br />
<br />
== Communication ==<br />
<br />
* Please join the mailing list: http://lists.osgeo.org/mailman/listinfo/tosprint<br />
* IRC chat during the event: #tosprint Server: irc.freenode.net<br />
* Twitter: #TOSprint ( https://twitter.com/search?q=tosprint )<br />
<br />
== Photos ==<br />
<br />
== Costs ==<br />
<br />
Participants should plan for the following costs:<br />
<br />
* Travel to Bonn<br />
* Accommodation for x nights <br />
<br />
All other costs - food, outings and entertainment - should/will be covered by the sponsors<br />
<br />
<br />
<br />
== Financial == <br />
<br />
'''Detailed budget'''<br />
* [[Bonn_Code_Sprint_2018_:_Budget|Budget]]<br />
<br />
== Individual preparation ==<br />
<br />
* Bring your own laptop<br />
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:Schuko_plug_and_socket.png Germany]). See also http://www.power-plugs-sockets.com/<br />
* Install GIT and compiler tools, and come with a working development environment<br />
<br />
== Sponsoring ==<br />
<br />
The Open Source Geospatial Foundation (OSGeo) has a long tradition of organizing code sprints for developers of Open Source GIS software.<br />
(https://wiki.osgeo.org/wiki/Category:Code_Sprints).<br />
<br />
Simultaneously with the [https://www.fossgis-konferenz.de/2018/ FOSSGIS Conference 2018 in Bonn] an international code sprint of the OSGeo will take place from 19 to 25 March 2018.<br />
We expect about 80 developers from all over the world to come from various [http://www.osgeo.org/] projects. Whether desktop application, geospatial library, metadata catalog or web mapping: be sure to find products in the list that you use. Thus, the Code Sprint is also an opportunity for your developers to meet with the core developers of the projects, get a deeper insight into the software and participate in the development.<br />
<br />
The code sprint will take place at [http://www.basecamp-bonn.de/ BaseCamp] in Bonn. During the [http://www.foss4g2016.org/home.html FOSS4G 2016] in Bonn we have already organized a code sprint at this location, in which about 100 developers worked on the open source projects every day. (https://wiki.osgeo.org/wiki/FOSS4G_2016_Code_Sprint)<br />
<br />
In addition to the costs of providing the technical infrastructure, the cost of food and drinks for the developers is the main cost. A buffet at lunchtime and drinks during the whole day are intended.<br />
<br />
So far, the code sprint is already sponsored by [http://www.osgeo.org/ OSGeo] and [https://www.fossgis.de/ FOSSGIS e. V.].<br />
<br />
In order to cover the costs, we would be very pleased about further sponsors!<br />
<br />
What we offer:<br />
* Your logo on top of the [http://osgeo.getinteractive.nl/events/osgeo-code-sprint-2018/ websites of the Code Sprint] [https://wiki.osgeo.org/wiki/OSGeo_Code_Sprint_2018 1] as well as on all official documents around the Code Sprint<br />
* Mention in all code sprint related mails<br />
* Our undying gratitude, which comes in handy when you least expect it (Remember that feature you wanted...)<br />
<br />
Our sponsorship levels:<br />
* Gold: >= 2500 USD<br />
* Silver: 1500 USD<br />
* Bronze: 750 USD<br />
<br />
So...<br />
* get your company talking to the top developers of the scene!<br />
* enable your GIS developers to take advantage of this opportunity, there is no better opportunity to learn!<br />
* support the software you use - you benefit immediately.<br />
<br />
Thank you very much!<br />
<br />
Contact: To sponsor, please contact codesprint@osgeo.org directly.<br />
<br />
<br />
== Event Owner ==<br />
* [[User:Astrid_Emde|Astrid Emde]]<br />
* Uli Rothstein<br />
* Carmen Tawalika<br />
* [[User:Olr|Oliver Rudzick]]<br />
* Mirko Blinn<br />
<br />
; Supported by<br />
* [[User:Lucadelu|Luca Delucchi]]<br />
[[Category:Code Sprints]]<br />
[[Category:C Tribe Code Sprint]]</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=OSGeo_Code_Sprint_2018&diff=111617OSGeo Code Sprint 20182017-12-09T23:11:43Z<p>Wiki-Remanuele: /* Participants */</p>
<hr />
<div>Annual Code Sprint comes to Bonn (Germany) in 2018!<br />
<br />
Powered by <br />
<br />
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]<br />
<br />
; Sponsors <br />
Find out about [[OSGeo_Code_Sprint_2018#Sponsoring |Sponsoring the Event]].<br />
<br />
;Gold Sponsors <br />
<br />
; Silver Sponsors <br />
<br />
; Bronze Sponsors <br />
<br />
{| border=0 cellspacing=15 cellpadding=10<br />
|<br />
[[File:Logo-Azavea.png|280px|Azavea|link=http://www.azavea.com/]]<br />
<br><br />
http://www.azavea.com/<br />
|<br />
[[File:WhereGroup_logo_418x110.png|290px|WhereGroup|link=https://www.wheregroup.com/]]<br />
<br><br />
https://www.wheregroup.com/<br />
|<br />
<br />
|}<br />
<br />
<br />
In 2018 we once again want to invite you to Bonn to meet for codesprint at Basecamp! ....<br />
<br />
[[Image:FOSS4G_2016_OSGeo_Code_Sprint_indoor_hacking_overview.jpg|400px|thumb|right]]<br />
[[Image:FOSS4G_OSGeo_Code_Sprint_in_Action1.jpg|400px|thumb|right]]<br />
<br />
[[Image:Basecamp5.png|300px|thumb]]<br />
[[Image:Basecamp6.png|300px|thumb]]<br />
[[Image:Basecamp7.png|300px|thumb]]<br />
[[Image:Basecamp1.png|300px|thumb]]<br />
<br />
[[Image:FOSS4G_2016_OSGeo_Code_Sprint_sponsors.jpg|400px]]<br />
<br />
<br />
== Purpose ==<br />
<br />
Bring together project members to make decisions and tackle larger geospatial <br />
problems as in previous years: <br />
* [[Daytona Beach Code Sprint 2017|Daytona_Beach]] (2017)<br />
* [[Paris Code Sprint 2016|Paris]] (2016)<br />
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)<br />
* [[Vienna Code Sprint 2014|Vienna]] (2014)<br />
* [[Boston Code Sprint 2013|Boston]] (2013)<br />
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)<br />
* [[Montreal Code Sprint 2011|Montreal]] (2011)<br />
* [[New York Code Sprint 2010|New York City]] (2010)<br />
* [[Toronto Code Sprint 2009|Toronto]] (2009)<br />
<br />
<br />
== Dates and Times ==<br />
<br />
Dates: <br />
* Sprint: Sunday-Sunday, March 18 to 25, 2018 (8 days - Arrival/Departure Sundays)<br />
<br />
== Other Events from January to March 2018 ==<br />
<br />
* '''OSGeo's 12th birthday Feb 4'''<br />
* FOSDEM 3-4 Feb https://fosdem.org/2018/<br />
* FOSS4G IT 19-22 Feb http://foss4g-it2018.gfoss.it/<br />
* [https://github.com/qgis/QGIS/wiki/DeveloperMeetingMadeira2018 QGis Hackfest] 21-25 Feb, 2018<br />
* FOSSGIS 21-24 March https://www.fossgis-konferenz.de/2018/<br />
* ''please add your event''<br />
<br />
== Location ==<br />
<br />
=== Coding Venue ===<br />
* Venue & Accommodation BaseCamp. <br />
* For more informations: http://www.basecamp-bonn.com/<br />
* [http://www.openstreetmap.org/way/44335958#map=18/50.70763/7.12316| OpenStreetMap]<br />
<br />
<br />
=== Accommodations ===<br />
* Nearby Hotel: Bonnox http://www.bonnox.de/en/<br />
* Max Hotel cheap and in the center<br />
<br />
=== How to get there ===<br />
* http://alienus.de/basecamp1/en/arrival-bonn-hostel/<br />
* http://www.openstreetmap.org/search?query=raste%201%20bonn#map=18/50.70762/7.12383<br />
<br />
By train<br />
* From Bonn Main station take the U-Trains (Underground platform) 16, 63 or 68. Get off after 6 min at stop Dt. Telekom / Ollenhauerstr. <br />
* http://alienus.de/basecamp1/en/arrival-bonn-hostel/<br />
* http://www.openstreetmap.org/search?query=raste%201%20bonn#map=18/50.70762/7.12383<br />
* [https://www.vrsinfo.de/englisch/the-vrs/vrs-about-us.html online public transport planner]<br />
<br />
By Car<br />
* Coming from the highway A59 Basecamp is located at the end of the highway A562. For navigation systems it is best to type Basecamp's address: "''In der Raste 3, 53129 Bonn''")<br />
<br />
== Schedule ==<br />
* tbd<br />
<br />
== Project Plans ==<br />
(i.e what do you wish/want/plan to work on during the sprint ?)<br />
<br />
* '''GRASS GIS project''': See [https://grasswiki.osgeo.org/wiki/GRASS_Community_Sprint_Bonn_2018 dedicated Wiki page]<br />
* tbd<br />
<br />
== Social ideas ==<br />
<br />
<br />
== Participants ==<br />
<br />
We are planning for attendance of ~50. Please add your name and the projects <br />
you are planning to sprint and note the likeliness of your attendance.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="25"|No<br />
!width="250"|Name<br />
!width="100"|Country<br />
!width="250"|Email<br />
!width="250"|Organisation<br />
!width="250"|Projects<br />
!width="25"|sun<br />
!width="25"|mon<br />
!width="25"|tue<br />
!width="25"|wed<br />
!width="25"|thu<br />
!width="25"|fri<br />
!width="25"|sat<br />
!width="25"|sun<br />
!width="60"|Accommodation<br />
!width="30"|vegetarian food<br />
|-<br />
| 1 ||[[Jeff McKenna]] <libravatar email="jmckenna@gatewaygeomatics.com"/> || CA || jmckenna(at)osgeo.org || OSGeo || MapServer, MS4W, ZOO-Project || x || x || x || x || x || x || x || x || shared accommodation || <br />
|-<br />
| 2 ||[[Howard Butler]] || US || howard@hobu.co || Hobu, Inc. || Proj.4, PDAL, GDAL, Point clouds || || x || x || x || x || x || || || || No thank you.<br />
|-<br />
| 3 ||[[Even Rouault]] || FR || even.rouault(at)spatialys.com || Spatialys || Proj.4, GDAL, MapServer || || x || x || x || x || x || || || BaseCamp if possible ||<br />
|-<br />
| 4 ||[[Markus Neteler]] || DE || neteler(at)osgeo.org || mundialis || GRASS GIS (Proj.4, GDAL, OTB, QGIS) || x || x || x || x || x || x || x || x || || preferably<br />
|-<br />
| 5 ||[[User:Djay|Gérald Fenoy]] || FR || gerald.fenoy(at)geolabs.fr || GeoLabs || MS4W, ZOO-Project || x || x || x || x || x || x || x || x || shared accommodation || <br />
|-<br />
| 6 ||[[User:Schpidi|Stephan Meißl]] || AT || stephan(at)meissl.name || EOX || MapServer, EOxServer || x || x || x || x || x || x || x || x || BaseCamp || <br />
|-<br />
| 7 ||[[User:martinl|Martin Landa]] || CZ || landa.martin(at)gmail.com || CTU in Prague || GRASS GIS (Proj.4, GDAL, PostGIS, QGIS) || x || x || x || x || x || x || x || x || BaseCamp ||<br />
|-<br />
| 8 ||[[User:connormanning|Connor Manning]] || US || connor@hobu.co || Hobu, Inc. || Entwine, Greyhound, PDAL, Point clouds || x || x || x || x || x || x || x || x || ||<br />
|-<br />
| 9 ||Markus Schütz (probably) || AT || mschuetz@potree.org|| TU Wien|| Potree, point clouds|| || x || x || x || x || x || || || || <br />
|-<br />
| 10 ||[[User:Tomkralidis|Tom Kralidis]] || CA || tomkralidis(at)gmail.com || self || pycsw, OWSLib, pygeometa, MapServer, geocatalogo || x || x || x || x || x || || || || tbd || sure <br />
|-<br />
| 11 ||[[User:kalxas|Angelos Tzotsos]] || GR || tzotsos(at)osgeo.org || OSGeo || pycsw, OSGeoLive, GeoNode, UbuntuGIS, geocatalogo, OTB, ZOO-Project || x || x || x || x || x || x || x || x || tbd || probably <br />
|-<br />
| 12 ||[[User:jjesus|Jorge Samuel Mendes de Jesus]] || NL || jorge.dejesus(at)geocat.net || Geocat || pywps || || x || x || x || x || x || x || || tbd || NO! <br />
|-<br />
| 13 ||[[User:ingenieroariel|Ariel Núñez]] || CO || ariel(at)terranodo.io || Terranodo || GeoNode || x || x || x || x || x || x || x || x || tbd || <br />
|-<br />
| 14 ||[[User:Lads|Luís de Sousa]] || PT & NL || luis.de.sousa(at)protonmail.ch || [http://www.isric.org ISRIC] || PyWPS, GRASS || || || x || x || x || x || x || x || BaseCamp || <br />
|-<br />
| 15 ||[[User:Vmische|Volker Mische]] || DE || volker.mische(at)gmail,com || Myself || Noise, CouchDB || x || x || x || x || x || x || x || x || BaseCamp || 50% <br />
|-<br />
| 16 ||[[User:Just|Just van den Broecke]] || NL || justb4(at)gmail,com || Myself || GeoHealthCheck, Stetl || x || x || x || x || x || x || x || x || tbd || - <br />
|-<br />
| 17 ||[[User:Jgrocha|Jorge Gustavo Rocha]] || PT || jgr@geomaster.pt || Geomaster || QGIS, GeoExt 3 || || x || x || x || x || x || 2 x || 2 x || BaseCamp (+ extra bed for the last 2 days for my daughter Rita, if possible) || <br />
|-<br />
| 18 ||[[User:tfr42|Torsten Friebe]] || DE || friebe AT lat-lon DOT de || organization || deegree || x || x || x || x || x || x || x || x || not needed || yes, please<br />
|-<br />
| 19 ||[[User:Stenger|Dirk Stenger]] || DE || stenger AT lat-lon DOT de || organization || deegree || || x || x || x || x || x || || || not needed || <br />
|-<br />
| 20 ||[[User:Lgoltz|Lyn Goltz]] || DE || goltz AT lat-lon DOT de || organization || deegree || || x || x || x || x || x || x || x || not needed || yes<br />
|-<br />
| 21 ||[[User:remanuele|Rob Emanuele]] || US || remanuele@azavea.com ||Azavea || PDAL, GDAL, Point clouds, GeoTrellis, LocationTech || || x || x || x || x || x || || || || <br />
|-<br />
| 22 || Grigory Pomadchin || RU || gr.pomadchin AT gmail DOT com || Azavea || PDAL, GDAL, Point clouds, GeoTrellis || || x || x || x || x || x || || || || <br />
|-<br />
| # ||[[User:your osgeo profile|Your name]] || DE || email || organization || project || x || x || x || x || x || x || x || x || x || x|-<br />
|}<br />
<br />
== Communication ==<br />
<br />
* Please join the mailing list: http://lists.osgeo.org/mailman/listinfo/tosprint<br />
* IRC chat during the event: #tosprint Server: irc.freenode.net<br />
* Twitter: #TOSprint ( https://twitter.com/search?q=tosprint )<br />
<br />
== Photos ==<br />
<br />
== Costs ==<br />
<br />
Participants should plan for the following costs:<br />
<br />
* Travel to Bonn<br />
* Accommodation for x nights <br />
<br />
All other costs - food, outings and entertainment - should/will be covered by the sponsors<br />
<br />
<br />
<br />
== Financial == <br />
<br />
'''Detailed budget'''<br />
* [[Bonn_Code_Sprint_2018_:_Budget|Budget]]<br />
<br />
== Individual preparation ==<br />
<br />
* Bring your own laptop<br />
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:Schuko_plug_and_socket.png Germany]). See also http://www.power-plugs-sockets.com/<br />
* Install GIT and compiler tools, and come with a working development environment<br />
<br />
== Sponsoring ==<br />
<br />
The Open Source Geospatial Foundation (OSGeo) has a long tradition of organizing code sprints for developers of Open Source GIS software.<br />
(https://wiki.osgeo.org/wiki/Category:Code_Sprints).<br />
<br />
Simultaneously with the [https://www.fossgis-konferenz.de/2018/ FOSSGIS Conference 2018 in Bonn] an international code sprint of the OSGeo will take place from 19 to 25 March 2018.<br />
We expect about 80 developers from all over the world to come from various [http://www.osgeo.org/] projects. Whether desktop application, geospatial library, metadata catalog or web mapping: be sure to find products in the list that you use. Thus, the Code Sprint is also an opportunity for your developers to meet with the core developers of the projects, get a deeper insight into the software and participate in the development.<br />
<br />
The code sprint will take place at [http://www.basecamp-bonn.de/ BaseCamp] in Bonn. During the [http://www.foss4g2016.org/home.html FOSS4G 2016] in Bonn we have already organized a code sprint at this location, in which about 100 developers worked on the open source projects every day. (https://wiki.osgeo.org/wiki/FOSS4G_2016_Code_Sprint)<br />
<br />
In addition to the costs of providing the technical infrastructure, the cost of food and drinks for the developers is the main cost. A buffet at lunchtime and drinks during the whole day are intended.<br />
<br />
So far, the code sprint is already sponsored by [http://www.osgeo.org/ OSGeo] and [https://www.fossgis.de/ FOSSGIS e. V.].<br />
<br />
In order to cover the costs, we would be very pleased about further sponsors!<br />
<br />
What we offer:<br />
* Your logo on top of the [http://osgeo.getinteractive.nl/events/osgeo-code-sprint-2018/ websites of the Code Sprint] [https://wiki.osgeo.org/wiki/OSGeo_Code_Sprint_2018 1] as well as on all official documents around the Code Sprint<br />
* Mention in all code sprint related mails<br />
* Our undying gratitude, which comes in handy when you least expect it (Remember that feature you wanted...)<br />
<br />
Our sponsorship levels:<br />
* Gold: >= 2500 USD<br />
* Silver: 1500 USD<br />
* Bronze: 750 USD<br />
<br />
So...<br />
* get your company talking to the top developers of the scene!<br />
* enable your GIS developers to take advantage of this opportunity, there is no better opportunity to learn!<br />
* support the software you use - you benefit immediately.<br />
<br />
Thank you very much!<br />
<br />
Contact: To sponsor, please contact astrid_emde@osgeo.org directly.<br />
<br />
<br />
== Event Owner ==<br />
* [[User:Astrid_Emde|Astrid Emde]]<br />
* Uli Rothstein<br />
* Carmen Tawalika<br />
* [[User:Olr|Oliver Rudzick]]<br />
* Mirko Blinn<br />
<br />
; Supported by<br />
* [[User:Lucadelu|Luca Delucchi]]<br />
[[Category:Code Sprints]]<br />
[[Category:C Tribe Code Sprint]]</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=User:Remanuele&diff=108511User:Remanuele2017-08-30T15:23:48Z<p>Wiki-Remanuele: </p>
<hr />
<div>{{OSGeo Member<br />
|Name=Rob Emanuele<br />
|JobTitle=VP of Research<br />
|Company=Azavea<br />
|Country=United States of America <br />
|State=PA<br />
|City=Philadelphia<br />
|Coordinate=39.958714, -75.158391<br />
|LocalChapter=Philadelphia<br />
}}<br />
{{OSGeo Experience<br />
|User=Yes<br />
|Committee=No<br />
|Board=No<br />
|Coder=Yes<br />
|Translate=No<br />
|PSC=No<br />
|ExBoard=No<br />
|Charter=No<br />
|Chair=No<br />
|SolKatz=No<br />
|Committer=Yes<br />
}}<br />
Core dev of [[http://www.geotrellis.io GeoTrellis]].<br />
GDAL, PDAL, JTS, Apache Spark<br />
<br />
Program Chair for FOSS4G NA 2015 & 2016.<br />
<br />
rdemanuele [at] gmail [dot] com<br />
<br />
[[Category: OSGeo Member]]<br />
[[Category:OSGeo_Advocate]]</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=User:Remanuele&diff=108510User:Remanuele2017-08-30T15:22:45Z<p>Wiki-Remanuele: </p>
<hr />
<div>{{OSGeo Member<br />
|Name=Rob Emanuele<br />
|JobTitle=VP of Research<br />
|Company=Azavea<br />
|Country=USA<br />
|State=PA<br />
|City=Philadelphia<br />
|Coordinate=39.958714, -75.158391<br />
|LocalChapter=Philadelphia<br />
}}<br />
{{OSGeo Experience<br />
|User=Yes<br />
|Committee=No<br />
|Board=No<br />
|Coder=Yes<br />
|Translate=No<br />
|PSC=No<br />
|ExBoard=No<br />
|Charter=No<br />
|Chair=No<br />
|SolKatz=No<br />
|Committer=Yes<br />
}}<br />
Core dev of [[http://www.geotrellis.io GeoTrellis]].<br />
GDAL, PDAL, JTS, Apache Spark<br />
<br />
Program Chair for FOSS4G NA 2015 & 2016.<br />
<br />
rdemanuele [at] gmail [dot] com<br />
<br />
[[Category: OSGeo Member]]<br />
[[Category:OSGeo_Advocate]]</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=User:Remanuele&diff=108508User:Remanuele2017-08-30T15:20:03Z<p>Wiki-Remanuele: </p>
<hr />
<div>Core dev of [[http://www.geotrellis.io GeoTrellis]].<br />
GDAL, PDAL, JTS, Apache Spark<br />
<br />
VP of Research at [[http://azavea.com Azavea]].<br />
<br />
Program Chair for FOSS4G NA 2015 & 2016.<br />
<br />
rdemanuele [at] gmail [dot] com<br />
<br />
[[Category: OSGeo Member]]<br />
<br />
{{OSGeo Member<br />
|Name=Rob Emanuele<br />
|Address=Philadelphia, PA, USA<br />
|Coordinate=39.958714, -75.158391<br />
}}<br />
<br />
[[Category:OSGeo_Advocate]]</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2017_Code_Sprint&diff=107786FOSS4G 2017 Code Sprint2017-08-04T15:38:50Z<p>Wiki-Remanuele: /* Registered Attendees */</p>
<hr />
<div>== Code Sprint ==<br />
<br />
Venue: Boston, Massachusetts, United States<br />
<br />
This year, once again, we are following the old tradition of hosting a code sprint right after [http://2017.foss4g.org FOSS4G 2017]. <br />
The code sprint will be held Saturday August 19th, 2017 at District Hall (http://www.districthallboston.org/). <br />
<br />
<br />
Participation in the code sprint is free of charge and all folks currently involved or interested in getting involved in OSGeo community projects are welcome.<br />
<br />
This is open to all who wish to participate in one or more projects. There’s always plenty to do – it’s not all about programming. Translation, documentation, feedback, discussions, and testing are also very important for projects! Registration with the conference is not a prerequisite for participation in code sprint.<br />
<br />
<br />
If you plan to attend, please signup in the table below so we have ample time for planning of snacks and drinks!<br />
<br />
.<br />
<br />
One thing we’d like to ask you: with over 200 participants anticipated, the WLAN capacity will naturally be exhausted at some point. Please be sure to avoid huge on-site downloads of data, as this could impact the work of others. Thank you!<br />
<br />
The Codesprint Organizing Team is looking forward to your coming!<br />
<br />
'''In summary:'''<br />
<br />
===When ===<br />
* Saturday August 19th 9AM - 5PM<br />
<br />
<br />
=== Where===<br />
* Venue & Accommodation: Boston District Hall. (For more information: http://www.districthallboston.org/) [[http://www.openstreetmap.org/#map=19/42.35229/-71.04528| OpenStreetMap]]<br />
<br />
'''Power connector:'''<br />
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] . See also http://www.power-plugs-sockets.com/<br />
<br />
== Registered Attendees ==<br />
<br />
The Code Sprint does not cost any money. For us it makes planning easier if we know who is coming. So please leave your Name.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="30"|No<br />
!width="250"|Name<br />
!width="250"|Email<br />
!width="250"|Projects<br />
!width="60"|Accomodation<br />
!width="30"|vegetarian food<br />
|-<br />
| 1 ||[[User:Robe|Regina Obe]] || lr pcorp us|| [[PostGIS]], [[GDAL]], [[pgRouting]], [[GEOS]] || home || No<br />
|-<br />
| 2 ||[[Leo Hsu]] || lr pcorp us || [[PostGIS]], [[pgRouting]] || home || No<br />
|-<br />
| 3 ||[[User:gsteinmon|Guido Stein]] || gstein@appgeo.com || [[FOSS4G]] || home || No<br />
|-<br />
| 4 ||[[User:wenzeslaus|Vaclav Petras]] || wenzeslaus gmail com || [[GRASS GIS]], PDAL || || No<br />
|-<br />
| 5 ||[[User:Annakrat|Anna Petrasova]] || akratoc gmail com || [[GRASS GIS]] || || No<br />
|-<br />
| 6 ||[[User:Helena|Helena Mitasova]] || hmitaso ncsu edu || [[GRASS GIS]] || || No<br />
|-<br />
| 7 ||[[User:Adamsteer|Adam Steer]] || adam.steer anu edu au || PDAL,PyWPS || || No<br />
|-<br />
| 8 ||[[User:hgryoo|Hyung-Gyu Ryoo]] || hgryoo pnu edu || [[GeoTools]], [[GeoServer]] || || No<br />
|-<br />
| 9 ||[[User:soojin.kim|Soojin Kim]] || soojin.kim pnu edu || [[GeoTools]], [[GeoServer]] || || No<br />
|-<br />
| 10 ||[[User:dbaston|Dan Baston]] || dbaston gmail com || [[PostGIS]], [[GEOS]] || || No<br />
|-<br />
| 11 ||[[User:pwramsey3|Paul Ramsey]] || pramsey cleverelephant ca || [[PostGIS]], [[GEOS]] || || No<br />
|-<br />
| 12 ||[[User:darkblue_b|Brian M Hamlin]] || maplabs -at- light42 || OSGeo Live || || Yes<br />
|-<br />
| 13 ||[[User:ianturton|Ian Turton]] || ian -at- ianturton.com || [[GeoTools]], [[GeoServer]] || || No<br />
|-<br />
| 14 ||[[User:jimk|Jim Klassen]] || jklassen -at- sharedgeo.org || [[GeoMoose]], [[MapServer]] || || No<br />
|-<br />
| 15 ||[[User:Chrismarx|Chris Marx]] || chrismarx -at- gmail.com || [[PostGIS]] || || No<br />
|-<br />
| 16 ||[[User:larss|Lars Schylberg]] || lars.schylberg -at- blixtmail.se || [[MapServer]] - documentation/demo || || No<br />
|-<br />
| 17 ||[[User: Bluemates |Kyoung-Sook Kim]] || ks.kim -at- aist.go.jp || [[PostGIS]], PDAL || || No<br />
|-<br />
| 18 ||[[User:msmitherdc|Michael Smith]] || michael.smith.erdc-at-gmail.com || PDAL,MapServer || || No<br />
|-<br />
| 19 ||[[User:grizonnetm|Manuel Grizonnet]] || manuel.grizonnet-at-cnes.fr || OTB, OSGeo-Live, QGIS || || No<br />
|-<br />
| 20 ||[[User:Lorenblock|Loren Block]] || loren@onxmaps.com || GeoTools || || No<br />
|-<br />
| 21 ||[[Jody Garnett]] || || GeoServer, GeoTools || || <br />
|-<br />
| 22 ||[[Torben Barsballe]] || || GeoServer || || <br />
|-<br />
| 23 ||[[Kevin Smith]] || || GeoServer || || <br />
|-<br />
| 24 ||[[User:ortelius|Jeffrey Johnson]] || jeff@terranodo.io || GeoNode, OSGeo Website || || No<br />
|-<br />
| 25 ||[[User:Cvvergara| Vicky Vergara]] || vicky@georepublic.de || OSGeo Website || IRC || No Food<br />
|-<br />
| 26 ||[[User:yoichi| Yoichi Kayama]] || yoichi.kayama-at-gmail.com || OSGeo-Live, QGIS || || No<br />
|-<br />
| 27 ||[[User:jachym|Jachym Cepicky]] || jachym.cepicky gmail || PyWPS || || No<br />
|-<br />
| 28 ||Micah Wengren || micah.wengren at gmail com || CKAN, pycsw, GeoNode || || <br />
|-<br />
| 29 ||[[User:Stevenfeldman| Steven Feldman]] || shfeldman at gmail.com || Community, OSGeo Website || || Yes<br />
|-<br />
| 30 ||[[User:OSGeoErikPohl| Erik Pohl]] || iotasubscript at gmail.com || [[GRASS GIS]] || || Yes<br />
|-<br />
| 31 ||[[User:remanuele| Rob Emanuele]] || remanuele at azavea.com || GeoTrellis, [[GDAL]], PDAL || || No<br />
|+<br />
|}<br />
<br />
= Workgroups =<br />
<br />
Getting the most of a code sprint takes a lot of prep. Please use this area to decide on a topic, sort out a plan of attack.<br />
<br />
Please keep in mind that the FOSS4G conference is an outreach event. Some of the "new" volunteers are learning about open source for the first time, consider listing some activities (and perhaps having a mentor on hand to facilitate).<br />
<br />
== Website Training ==<br />
<br />
OSGeo website training is available throughout the day, please mark your name down to attend. We ask that a member of each OSGeo committee, local chapter, geoforall lab make plans to attend. Service providers and sponsors are also welcome.<br />
<br />
We will be reviewing both the website publication workflow and the about.yaml structured content used by the project working group.<br />
<br />
'''Attending:''' <br />
Jody Garnett, Jeffrey Johnson<br />
<br />
'''Goals:''' <br />
<br />
Introduce members to the new website, editing workflow, and add to the members map.<br />
<br />
Stop by to create your own personal "osgeo branding" using InkScape.<br />
<br />
Answer any questions projects have on about.yaml use.<br />
<br />
Add to the collection of presentations, videos and tutorial links.<br />
<br />
== PostGIS ==<br />
<br />
Spatial database extender for PostgreSQL<br />
<br />
'''Attending:''' <br />
Regina Obe, Leo Hsu, Dan Baston, Paul Ramsey<br />
<br />
<br />
'''Goals:''' <br />
* Getting ready for PostGIS 2.4.0 release.<br />
* Testing out what we'll be pushing.<br />
* Thoughts on better integration with GDAL and PostGIS. Most notably the sucky support of out of db tables in GDAL.<br />
* Better integration of document translations<br />
<br />
== GRASS GIS ==<br />
<br />
Backend and desktop geospatial analysis tool<br />
<br />
'''Attending:''' Vaclav Petras, Anna Petrasova, Helena Mitasova<br />
<br />
'''Goals:''' Documentation, images for manual pages, and testing for next release. <br />
<br />
== GeoTools ==<br />
<br />
GeoTools is an open source Java library that provides tools for geospatial data.<br />
<br />
'''Attending:''' <br />
<br />
Jody Garnett,<br />
Ian Turton<br />
<br />
'''Goals:''' <br />
<br />
* Java 9 "Service Provider Interface" compatibility<br />
* Service Locator based FactoryRegistery replacement<br />
* Updated factory tutorials to document FactoryRegistry replacement<br />
<br />
'''New to Open Source:''' <br />
<br />
* Help review and improve the geotools function list.<br />
* Come prepaired with [http://docs.geotools.org/latest/userguide/build/index.html geotools build and development environment] and review the [http://docs.geotools.org/latest/userguide/tutorial/function.html function tutorial]. We can help answer any questions if you get stuck.<br />
<br />
== GeoServer ==<br />
<br />
Popular web application for sharing geospatial information, written in Java.<br />
<br />
'''Attending:''' <br />
<br />
Jody Garnett,<br />
Torben Barsballe,<br />
Kevin Smith,<br />
Ian Turton<br />
<br />
'''Goals:''' <br />
<br />
* Coordinate Java 9 upgrade with GeoTools project<br />
<br />
<br />
'''New to Open Source:''' <br />
<br />
* Volunteers assist with any remaining REST API docs ahead of the 2.12 release, come prepaired with a GeoServer installation and your own github id.<br />
* Developers come prepaired with [http://docs.geoserver.org/latest/en/developer/quickstart/index.html build and development environment] we can help answer any questions if you get stuck.<br />
* We will be posting to the [https://lists.osgeo.org/mailman/listinfo/foss4g2017 FOSS4G OSGeo email list] with updates about food and coordination.<br />
<br />
== PyWPS ==<br />
<br />
Python implementation of OGC Web Processing Service server<br />
<br />
'''Attending:''' <br />
<br />
Jachym Cepicky,<br />
...<br />
<br />
'''Goals:''' <br />
<br />
* Incubation sprint<br />
* Logging finalization<br />
<br />
<br />
[[Category:FOSS4G2017]] [[Category:FOSS4G]] [[Category:Code_Sprints]]</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2017_Code_Sprint&diff=107785FOSS4G 2017 Code Sprint2017-08-04T15:38:11Z<p>Wiki-Remanuele: /* Registered Attendees */</p>
<hr />
<div>== Code Sprint ==<br />
<br />
Venue: Boston, Massachusetts, United States<br />
<br />
This year, once again, we are following the old tradition of hosting a code sprint right after [http://2017.foss4g.org FOSS4G 2017]. <br />
The code sprint will be held Saturday August 19th, 2017 at District Hall (http://www.districthallboston.org/). <br />
<br />
<br />
Participation in the code sprint is free of charge and all folks currently involved or interested in getting involved in OSGeo community projects are welcome.<br />
<br />
This is open to all who wish to participate in one or more projects. There’s always plenty to do – it’s not all about programming. Translation, documentation, feedback, discussions, and testing are also very important for projects! Registration with the conference is not a prerequisite for participation in code sprint.<br />
<br />
<br />
If you plan to attend, please signup in the table below so we have ample time for planning of snacks and drinks!<br />
<br />
.<br />
<br />
One thing we’d like to ask you: with over 200 participants anticipated, the WLAN capacity will naturally be exhausted at some point. Please be sure to avoid huge on-site downloads of data, as this could impact the work of others. Thank you!<br />
<br />
The Codesprint Organizing Team is looking forward to your coming!<br />
<br />
'''In summary:'''<br />
<br />
===When ===<br />
* Saturday August 19th 9AM - 5PM<br />
<br />
<br />
=== Where===<br />
* Venue & Accommodation: Boston District Hall. (For more information: http://www.districthallboston.org/) [[http://www.openstreetmap.org/#map=19/42.35229/-71.04528| OpenStreetMap]]<br />
<br />
'''Power connector:'''<br />
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] . See also http://www.power-plugs-sockets.com/<br />
<br />
== Registered Attendees ==<br />
<br />
The Code Sprint does not cost any money. For us it makes planning easier if we know who is coming. So please leave your Name.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="30"|No<br />
!width="250"|Name<br />
!width="250"|Email<br />
!width="250"|Projects<br />
!width="60"|Accomodation<br />
!width="30"|vegetarian food<br />
|-<br />
| 1 ||[[User:Robe|Regina Obe]] || lr pcorp us|| [[PostGIS]], [[GDAL]], [[pgRouting]], [[GEOS]] || home || No<br />
|-<br />
| 2 ||[[Leo Hsu]] || lr pcorp us || [[PostGIS]], [[pgRouting]] || home || No<br />
|-<br />
| 3 ||[[User:gsteinmon|Guido Stein]] || gstein@appgeo.com || [[FOSS4G]] || home || No<br />
|-<br />
| 4 ||[[User:wenzeslaus|Vaclav Petras]] || wenzeslaus gmail com || [[GRASS GIS]], PDAL || || No<br />
|-<br />
| 5 ||[[User:Annakrat|Anna Petrasova]] || akratoc gmail com || [[GRASS GIS]] || || No<br />
|-<br />
| 6 ||[[User:Helena|Helena Mitasova]] || hmitaso ncsu edu || [[GRASS GIS]] || || No<br />
|-<br />
| 7 ||[[User:Adamsteer|Adam Steer]] || adam.steer anu edu au || PDAL,PyWPS || || No<br />
|-<br />
| 8 ||[[User:hgryoo|Hyung-Gyu Ryoo]] || hgryoo pnu edu || [[GeoTools]], [[GeoServer]] || || No<br />
|-<br />
| 9 ||[[User:soojin.kim|Soojin Kim]] || soojin.kim pnu edu || [[GeoTools]], [[GeoServer]] || || No<br />
|-<br />
| 10 ||[[User:dbaston|Dan Baston]] || dbaston gmail com || [[PostGIS]], [[GEOS]] || || No<br />
|-<br />
| 11 ||[[User:pwramsey3|Paul Ramsey]] || pramsey cleverelephant ca || [[PostGIS]], [[GEOS]] || || No<br />
|-<br />
| 12 ||[[User:darkblue_b|Brian M Hamlin]] || maplabs -at- light42 || OSGeo Live || || Yes<br />
|-<br />
| 13 ||[[User:ianturton|Ian Turton]] || ian -at- ianturton.com || [[GeoTools]], [[GeoServer]] || || No<br />
|-<br />
| 14 ||[[User:jimk|Jim Klassen]] || jklassen -at- sharedgeo.org || [[GeoMoose]], [[MapServer]] || || No<br />
|-<br />
| 15 ||[[User:Chrismarx|Chris Marx]] || chrismarx -at- gmail.com || [[PostGIS]] || || No<br />
|-<br />
| 16 ||[[User:larss|Lars Schylberg]] || lars.schylberg -at- blixtmail.se || [[MapServer]] - documentation/demo || || No<br />
|-<br />
| 17 ||[[User: Bluemates |Kyoung-Sook Kim]] || ks.kim -at- aist.go.jp || [[PostGIS]], PDAL || || No<br />
|-<br />
| 18 ||[[User:msmitherdc|Michael Smith]] || michael.smith.erdc-at-gmail.com || PDAL,MapServer || || No<br />
|-<br />
| 19 ||[[User:grizonnetm|Manuel Grizonnet]] || manuel.grizonnet-at-cnes.fr || OTB, OSGeo-Live, QGIS || || No<br />
|-<br />
| 20 ||[[User:Lorenblock|Loren Block]] || loren@onxmaps.com || GeoTools || || No<br />
|-<br />
| 21 ||[[Jody Garnett]] || || GeoServer, GeoTools || || <br />
|-<br />
| 22 ||[[Torben Barsballe]] || || GeoServer || || <br />
|-<br />
| 23 ||[[Kevin Smith]] || || GeoServer || || <br />
|-<br />
| 24 ||[[User:ortelius|Jeffrey Johnson]] || jeff@terranodo.io || GeoNode, OSGeo Website || || No<br />
|-<br />
| 25 ||[[User:Cvvergara| Vicky Vergara]] || vicky@georepublic.de || OSGeo Website || IRC || No Food<br />
|-<br />
| 26 ||[[User:yoichi| Yoichi Kayama]] || yoichi.kayama-at-gmail.com || OSGeo-Live, QGIS || || No<br />
|-<br />
| 27 ||[[User:jachym|Jachym Cepicky]] || jachym.cepicky gmail || PyWPS || || No<br />
|-<br />
| 28 ||Micah Wengren || micah.wengren at gmail com || CKAN, pycsw, GeoNode || || <br />
|-<br />
| 29 ||[[User:Stevenfeldman| Steven Feldman]] || shfeldman at gmail.com || Community, OSGeo Website || || Yes<br />
|-<br />
| 30 ||[[User:OSGeoErikPohl| Erik Pohl]] || iotasubscript at gmail.com || [[GRASS GIS]] || || Yes<br />
|-<br />
| 31 ||[[User:remanuele| Rob Emanuele]] || remanuele at azavea.com || GeoTrellis, [[GDAL]], [[PDAL]] || || No<br />
|+<br />
|}<br />
<br />
= Workgroups =<br />
<br />
Getting the most of a code sprint takes a lot of prep. Please use this area to decide on a topic, sort out a plan of attack.<br />
<br />
Please keep in mind that the FOSS4G conference is an outreach event. Some of the "new" volunteers are learning about open source for the first time, consider listing some activities (and perhaps having a mentor on hand to facilitate).<br />
<br />
== Website Training ==<br />
<br />
OSGeo website training is available throughout the day, please mark your name down to attend. We ask that a member of each OSGeo committee, local chapter, geoforall lab make plans to attend. Service providers and sponsors are also welcome.<br />
<br />
We will be reviewing both the website publication workflow and the about.yaml structured content used by the project working group.<br />
<br />
'''Attending:''' <br />
Jody Garnett, Jeffrey Johnson<br />
<br />
'''Goals:''' <br />
<br />
Introduce members to the new website, editing workflow, and add to the members map.<br />
<br />
Stop by to create your own personal "osgeo branding" using InkScape.<br />
<br />
Answer any questions projects have on about.yaml use.<br />
<br />
Add to the collection of presentations, videos and tutorial links.<br />
<br />
== PostGIS ==<br />
<br />
Spatial database extender for PostgreSQL<br />
<br />
'''Attending:''' <br />
Regina Obe, Leo Hsu, Dan Baston, Paul Ramsey<br />
<br />
<br />
'''Goals:''' <br />
* Getting ready for PostGIS 2.4.0 release.<br />
* Testing out what we'll be pushing.<br />
* Thoughts on better integration with GDAL and PostGIS. Most notably the sucky support of out of db tables in GDAL.<br />
* Better integration of document translations<br />
<br />
== GRASS GIS ==<br />
<br />
Backend and desktop geospatial analysis tool<br />
<br />
'''Attending:''' Vaclav Petras, Anna Petrasova, Helena Mitasova<br />
<br />
'''Goals:''' Documentation, images for manual pages, and testing for next release. <br />
<br />
== GeoTools ==<br />
<br />
GeoTools is an open source Java library that provides tools for geospatial data.<br />
<br />
'''Attending:''' <br />
<br />
Jody Garnett,<br />
Ian Turton<br />
<br />
'''Goals:''' <br />
<br />
* Java 9 "Service Provider Interface" compatibility<br />
* Service Locator based FactoryRegistery replacement<br />
* Updated factory tutorials to document FactoryRegistry replacement<br />
<br />
'''New to Open Source:''' <br />
<br />
* Help review and improve the geotools function list.<br />
* Come prepaired with [http://docs.geotools.org/latest/userguide/build/index.html geotools build and development environment] and review the [http://docs.geotools.org/latest/userguide/tutorial/function.html function tutorial]. We can help answer any questions if you get stuck.<br />
<br />
== GeoServer ==<br />
<br />
Popular web application for sharing geospatial information, written in Java.<br />
<br />
'''Attending:''' <br />
<br />
Jody Garnett,<br />
Torben Barsballe,<br />
Kevin Smith,<br />
Ian Turton<br />
<br />
'''Goals:''' <br />
<br />
* Coordinate Java 9 upgrade with GeoTools project<br />
<br />
<br />
'''New to Open Source:''' <br />
<br />
* Volunteers assist with any remaining REST API docs ahead of the 2.12 release, come prepaired with a GeoServer installation and your own github id.<br />
* Developers come prepaired with [http://docs.geoserver.org/latest/en/developer/quickstart/index.html build and development environment] we can help answer any questions if you get stuck.<br />
* We will be posting to the [https://lists.osgeo.org/mailman/listinfo/foss4g2017 FOSS4G OSGeo email list] with updates about food and coordination.<br />
<br />
== PyWPS ==<br />
<br />
Python implementation of OGC Web Processing Service server<br />
<br />
'''Attending:''' <br />
<br />
Jachym Cepicky,<br />
...<br />
<br />
'''Goals:''' <br />
<br />
* Incubation sprint<br />
* Logging finalization<br />
<br />
<br />
[[Category:FOSS4G2017]] [[Category:FOSS4G]] [[Category:Code_Sprints]]</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2017_Code_Sprint&diff=107784FOSS4G 2017 Code Sprint2017-08-04T15:37:56Z<p>Wiki-Remanuele: /* Registered Attendees */</p>
<hr />
<div>== Code Sprint ==<br />
<br />
Venue: Boston, Massachusetts, United States<br />
<br />
This year, once again, we are following the old tradition of hosting a code sprint right after [http://2017.foss4g.org FOSS4G 2017]. <br />
The code sprint will be held Saturday August 19th, 2017 at District Hall (http://www.districthallboston.org/). <br />
<br />
<br />
Participation in the code sprint is free of charge and all folks currently involved or interested in getting involved in OSGeo community projects are welcome.<br />
<br />
This is open to all who wish to participate in one or more projects. There’s always plenty to do – it’s not all about programming. Translation, documentation, feedback, discussions, and testing are also very important for projects! Registration with the conference is not a prerequisite for participation in code sprint.<br />
<br />
<br />
If you plan to attend, please signup in the table below so we have ample time for planning of snacks and drinks!<br />
<br />
.<br />
<br />
One thing we’d like to ask you: with over 200 participants anticipated, the WLAN capacity will naturally be exhausted at some point. Please be sure to avoid huge on-site downloads of data, as this could impact the work of others. Thank you!<br />
<br />
The Codesprint Organizing Team is looking forward to your coming!<br />
<br />
'''In summary:'''<br />
<br />
===When ===<br />
* Saturday August 19th 9AM - 5PM<br />
<br />
<br />
=== Where===<br />
* Venue & Accommodation: Boston District Hall. (For more information: http://www.districthallboston.org/) [[http://www.openstreetmap.org/#map=19/42.35229/-71.04528| OpenStreetMap]]<br />
<br />
'''Power connector:'''<br />
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] . See also http://www.power-plugs-sockets.com/<br />
<br />
== Registered Attendees ==<br />
<br />
The Code Sprint does not cost any money. For us it makes planning easier if we know who is coming. So please leave your Name.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="30"|No<br />
!width="250"|Name<br />
!width="250"|Email<br />
!width="250"|Projects<br />
!width="60"|Accomodation<br />
!width="30"|vegetarian food<br />
|-<br />
| 1 ||[[User:Robe|Regina Obe]] || lr pcorp us|| [[PostGIS]], [[GDAL]], [[pgRouting]], [[GEOS]] || home || No<br />
|-<br />
| 2 ||[[Leo Hsu]] || lr pcorp us || [[PostGIS]], [[pgRouting]] || home || No<br />
|-<br />
| 3 ||[[User:gsteinmon|Guido Stein]] || gstein@appgeo.com || [[FOSS4G]] || home || No<br />
|-<br />
| 4 ||[[User:wenzeslaus|Vaclav Petras]] || wenzeslaus gmail com || [[GRASS GIS]], PDAL || || No<br />
|-<br />
| 5 ||[[User:Annakrat|Anna Petrasova]] || akratoc gmail com || [[GRASS GIS]] || || No<br />
|-<br />
| 6 ||[[User:Helena|Helena Mitasova]] || hmitaso ncsu edu || [[GRASS GIS]] || || No<br />
|-<br />
| 7 ||[[User:Adamsteer|Adam Steer]] || adam.steer anu edu au || PDAL,PyWPS || || No<br />
|-<br />
| 8 ||[[User:hgryoo|Hyung-Gyu Ryoo]] || hgryoo pnu edu || [[GeoTools]], [[GeoServer]] || || No<br />
|-<br />
| 9 ||[[User:soojin.kim|Soojin Kim]] || soojin.kim pnu edu || [[GeoTools]], [[GeoServer]] || || No<br />
|-<br />
| 10 ||[[User:dbaston|Dan Baston]] || dbaston gmail com || [[PostGIS]], [[GEOS]] || || No<br />
|-<br />
| 11 ||[[User:pwramsey3|Paul Ramsey]] || pramsey cleverelephant ca || [[PostGIS]], [[GEOS]] || || No<br />
|-<br />
| 12 ||[[User:darkblue_b|Brian M Hamlin]] || maplabs -at- light42 || OSGeo Live || || Yes<br />
|-<br />
| 13 ||[[User:ianturton|Ian Turton]] || ian -at- ianturton.com || [[GeoTools]], [[GeoServer]] || || No<br />
|-<br />
| 14 ||[[User:jimk|Jim Klassen]] || jklassen -at- sharedgeo.org || [[GeoMoose]], [[MapServer]] || || No<br />
|-<br />
| 15 ||[[User:Chrismarx|Chris Marx]] || chrismarx -at- gmail.com || [[PostGIS]] || || No<br />
|-<br />
| 16 ||[[User:larss|Lars Schylberg]] || lars.schylberg -at- blixtmail.se || [[MapServer]] - documentation/demo || || No<br />
|-<br />
| 17 ||[[User: Bluemates |Kyoung-Sook Kim]] || ks.kim -at- aist.go.jp || [[PostGIS]], PDAL || || No<br />
|-<br />
| 18 ||[[User:msmitherdc|Michael Smith]] || michael.smith.erdc-at-gmail.com || PDAL,MapServer || || No<br />
|-<br />
| 19 ||[[User:grizonnetm|Manuel Grizonnet]] || manuel.grizonnet-at-cnes.fr || OTB, OSGeo-Live, QGIS || || No<br />
|-<br />
| 20 ||[[User:Lorenblock|Loren Block]] || loren@onxmaps.com || GeoTools || || No<br />
|-<br />
| 21 ||[[Jody Garnett]] || || GeoServer, GeoTools || || <br />
|-<br />
| 22 ||[[Torben Barsballe]] || || GeoServer || || <br />
|-<br />
| 23 ||[[Kevin Smith]] || || GeoServer || || <br />
|-<br />
| 24 ||[[User:ortelius|Jeffrey Johnson]] || jeff@terranodo.io || GeoNode, OSGeo Website || || No<br />
|-<br />
| 25 ||[[User:Cvvergara| Vicky Vergara]] || vicky@georepublic.de || OSGeo Website || IRC || No Food<br />
|-<br />
| 26 ||[[User:yoichi| Yoichi Kayama]] || yoichi.kayama-at-gmail.com || OSGeo-Live, QGIS || || No<br />
|-<br />
| 27 ||[[User:jachym|Jachym Cepicky]] || jachym.cepicky gmail || PyWPS || || No<br />
|-<br />
| 28 ||Micah Wengren || micah.wengren at gmail com || CKAN, pycsw, GeoNode || || <br />
|-<br />
| 29 ||[[User:Stevenfeldman| Steven Feldman]] || shfeldman at gmail.com || Community, OSGeo Website || || Yes<br />
|-<br />
| 30 ||[[User:OSGeoErikPohl| Erik Pohl]] || iotasubscript at gmail.com || [[GRASS GIS]] || || Yes<br />
|-<br />
| 30 ||[[User:remanuele| Rob Emanuele]] || remanuele at azavea.com || GeoTrellis, [[GDAL]], [[PDAL]] || || No<br />
|+<br />
|}<br />
<br />
= Workgroups =<br />
<br />
Getting the most of a code sprint takes a lot of prep. Please use this area to decide on a topic, sort out a plan of attack.<br />
<br />
Please keep in mind that the FOSS4G conference is an outreach event. Some of the "new" volunteers are learning about open source for the first time, consider listing some activities (and perhaps having a mentor on hand to facilitate).<br />
<br />
== Website Training ==<br />
<br />
OSGeo website training is available throughout the day, please mark your name down to attend. We ask that a member of each OSGeo committee, local chapter, geoforall lab make plans to attend. Service providers and sponsors are also welcome.<br />
<br />
We will be reviewing both the website publication workflow and the about.yaml structured content used by the project working group.<br />
<br />
'''Attending:''' <br />
Jody Garnett, Jeffrey Johnson<br />
<br />
'''Goals:''' <br />
<br />
Introduce members to the new website, editing workflow, and add to the members map.<br />
<br />
Stop by to create your own personal "osgeo branding" using InkScape.<br />
<br />
Answer any questions projects have on about.yaml use.<br />
<br />
Add to the collection of presentations, videos and tutorial links.<br />
<br />
== PostGIS ==<br />
<br />
Spatial database extender for PostgreSQL<br />
<br />
'''Attending:''' <br />
Regina Obe, Leo Hsu, Dan Baston, Paul Ramsey<br />
<br />
<br />
'''Goals:''' <br />
* Getting ready for PostGIS 2.4.0 release.<br />
* Testing out what we'll be pushing.<br />
* Thoughts on better integration with GDAL and PostGIS. Most notably the sucky support of out of db tables in GDAL.<br />
* Better integration of document translations<br />
<br />
== GRASS GIS ==<br />
<br />
Backend and desktop geospatial analysis tool<br />
<br />
'''Attending:''' Vaclav Petras, Anna Petrasova, Helena Mitasova<br />
<br />
'''Goals:''' Documentation, images for manual pages, and testing for next release. <br />
<br />
== GeoTools ==<br />
<br />
GeoTools is an open source Java library that provides tools for geospatial data.<br />
<br />
'''Attending:''' <br />
<br />
Jody Garnett,<br />
Ian Turton<br />
<br />
'''Goals:''' <br />
<br />
* Java 9 "Service Provider Interface" compatibility<br />
* Service Locator based FactoryRegistery replacement<br />
* Updated factory tutorials to document FactoryRegistry replacement<br />
<br />
'''New to Open Source:''' <br />
<br />
* Help review and improve the geotools function list.<br />
* Come prepaired with [http://docs.geotools.org/latest/userguide/build/index.html geotools build and development environment] and review the [http://docs.geotools.org/latest/userguide/tutorial/function.html function tutorial]. We can help answer any questions if you get stuck.<br />
<br />
== GeoServer ==<br />
<br />
Popular web application for sharing geospatial information, written in Java.<br />
<br />
'''Attending:''' <br />
<br />
Jody Garnett,<br />
Torben Barsballe,<br />
Kevin Smith,<br />
Ian Turton<br />
<br />
'''Goals:''' <br />
<br />
* Coordinate Java 9 upgrade with GeoTools project<br />
<br />
<br />
'''New to Open Source:''' <br />
<br />
* Volunteers assist with any remaining REST API docs ahead of the 2.12 release, come prepaired with a GeoServer installation and your own github id.<br />
* Developers come prepaired with [http://docs.geoserver.org/latest/en/developer/quickstart/index.html build and development environment] we can help answer any questions if you get stuck.<br />
* We will be posting to the [https://lists.osgeo.org/mailman/listinfo/foss4g2017 FOSS4G OSGeo email list] with updates about food and coordination.<br />
<br />
== PyWPS ==<br />
<br />
Python implementation of OGC Web Processing Service server<br />
<br />
'''Attending:''' <br />
<br />
Jachym Cepicky,<br />
...<br />
<br />
'''Goals:''' <br />
<br />
* Incubation sprint<br />
* Logging finalization<br />
<br />
<br />
[[Category:FOSS4G2017]] [[Category:FOSS4G]] [[Category:Code_Sprints]]</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=User:Remanuele&diff=107783User:Remanuele2017-08-04T15:37:45Z<p>Wiki-Remanuele: </p>
<hr />
<div>Core dev of [[http://www.geotrellis.io GeoTrellis]].<br />
GDAL, PDAL, JTS, Apache Spark<br />
<br />
VP of Research at [[http://azavea.com Azavea]].<br />
<br />
Program Chair for FOSS4G NA 2015 & 2016.<br />
<br />
rdemanuele [at] gmail [dot] com<br />
<br />
[[Category: OSGeo Member]]<br />
<br />
{{OSGeo Member<br />
|Name=Rob Emanuele<br />
|Address=Philadelphia, PA, USA<br />
|Coordinate=39.958714, -75.158391<br />
}}</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=Daytona_Beach_Code_Sprint_2017&diff=104549Daytona Beach Code Sprint 20172017-01-05T17:43:11Z<p>Wiki-Remanuele: /* Participants */</p>
<hr />
<div><br />
=== Gold Sponsors ===<br />
<br />
=== Silver Sponsors ===<br />
<br />
=== Bronze Sponsors ===<br />
<br />
=== Venue Sponsor ===<br />
<br />
<br />
=== Other/in-kind sponsors ===<br />
<br />
{| border=0 cellspacing=15 cellpadding=10<br />
|<br />
[[File:OSGeo_logo.png|260px|OSGeo|link=http://www.osgeo.org/]]<br />
<br><br />
http://www.osgeo.org/<br />
|}<br />
<br />
== Purpose ==<br />
<br />
Bring together project members to make decisions and tackle larger geospatial <br />
problems as in previous years: <br />
<br />
* [[Paris Code Sprint 2016|Paris]] (2016)<br />
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)<br />
* [[Vienna Code Sprint 2014|Vienna]] (2014)<br />
* [[Boston Code Sprint 2013|Boston]] (2013)<br />
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)<br />
* [[Montreal Code Sprint 2011|Montreal]] (2011)<br />
* [[New York Code Sprint 2010|New York City]] (2010)<br />
* [[Toronto Code Sprint 2009|Toronto]] (2009)<br />
<br />
== Other Events from January to March 2017 ==<br />
<br />
* FOSSGIS Hacking event January 20-22<br />
* FOSS4G Asia January 26-29<br />
* '''OSGeo's 11th birthday Feb 4'''<br />
* FOSDEM Feb 4-5<br />
* FOSS4G-IT (Genoa) Feb 8-11<br />
* Daytona 500 NASCAR race Feb 26<br />
* OGC Technical meeting March 7-11<br />
<br />
== Dates and Times ==<br />
<br />
Dates: <br />
* Sprint: Tuesday-Friday, Feb 7 to 10, 2017 (4 days)<br />
* Welcome event: TBD<br />
<br />
== Location ==<br />
<br />
=== Coding Venue ===<br />
* Embry Riddle Aeronautical University, College of Arts & Science building: https://www.openstreetmap.org/way/361201184#map=16/29.1912/-81.0494<br />
* Located 5 minutes from Daytona International Airport (DAB)<br />
<br />
=== Accommodations ===<br />
Several hotels are within walking distance of the venue. Here are a few options:<br />
{|border=1<br />
|-<br />
| '''Hotel Name''' || '''Price Range (USD)''' || '''TripAdvisor Rank''' || '''Distance''' || '''Notes'''<br />
|-<br />
| [http://www.marriott.com/hotels/travel/dabri-residence-inn-daytona-beach-speedway-airport/?pid=corptbta&scid=b661a3c4-9c47-48c8-9e13-75b66089dd79 Marriott Residence Inn] || 115$+ || [https://www.tripadvisor.ca/Hotel_Review-g34172-d596573-Reviews-Residence_Inn_Daytona_Beach_Speedway_Airport-Daytona_Beach_Florida.html #28 of 103] || 1.1 mile || Right next to University Campus<br />
|-<br />
| [https://www.choicehotels.com/florida/daytona-beach/quality-inn-hotels/fl931 Quality Inn Daytona Speedway] || 80-90$ || [https://www.tripadvisor.ca/Hotel_Review-g34172-d240235-Reviews-Quality_Inn_Daytona_Speedway-Daytona_Beach_Florida.html #3 of 103] || 2.4 miles || <br />
|}<br />
<br />
=== Airport options ===<br />
Airports to look at DAB - Daytona Beach International - Connects thru Atlanta on Delta, Charolette NC on American Airlines, and JFK from Jet Blue this might help with connections ideas: http://www.flydaytonafirst.com/schedule.stml<br />
<br />
DAB is super easy in/out 5 minutes away from Embry-Riddle Aeronautical University, actually the college is situated off the runway for the flight school. Here are the other airports that might be cheaper on the surface, but between having to commute another hour plus the extra time dealing with the airports...DAB is probably $200 more to fly in/out of, but you save hours of transportation time and costs. Of course if you are hitting Disney World while you are here or something, then fly out of Orlando or Sanford. Or Kennedy Space Center which is an hour South, you could fly out of Melbourne FL or again Orlando. MCO is the main Orlando airport and probably has the "cheapest flights" because of the volume, but security takes a good bit of time, and typically you need to check in 90 minutes early, and traffic in Orlando can build quickly.<br />
<br />
SFB is about 50 minutes South West and typically has good deals on Allegiant Airlines (no-frills) http://www.orlandosanfordairport.com/<br />
<br />
MCO is about 90 minutes West in Orlando FL<br />
<br />
JAX is about 90 minutes North in Jacksonville FL<br />
<br />
== Schedule ==<br />
<br />
=== Mon Feb 6, 2017 Welcoming Event ===<br />
<br />
=== Tue Feb 7, 2017 - First Sprint Day / Evening ===<br />
<br />
=== Wed Feb 8, 2017 - Second Sprint Day / Evening ===<br />
<br />
=== Thu Feb 9, 2017 - Third Sprint Day / Evening ===<br />
<br />
=== Fri Feb 10, 2017 - Fourth Sprint Day ===<br />
<br />
== Project Plans ==<br />
(i.e what do you wish/want/plan to work on during the sprint ?)<br />
<br />
* <br />
== Social ideas ==<br />
<br />
If you need to take a break, some ideas close to the sprint place:<br />
<br />
== Participants ==<br />
<br />
We are planning for attendance of ~50. Please add your name and the projects <br />
you are planning to sprint and note the likeliness of your attendance.<br />
<br />
{| style="border: solid grey 1px; width:100%" class="sortable"<br />
|+ Participants<br />
|-<br />
| # || Participant || Country || Organization || Arrival || Departure || Project Work on || Attendance / Notes<br />
|-<br />
|1 || [[User:remanuele|Rob Emanuele]] || US || Azavea || first day || last day || PDAL, GDAL || Highly Likely<br />
|-<br />
|2 || [[User:dmorissette|Daniel Morissette]] || CA || Mapgears || first day || last day || MapServer, GDAL/OGR || Booked<br />
|-<br />
|3 || [[User:msmitherdc|Michael Smith]] || US || US Army Corp || first day || last day || MapServer, PDAL || Highly Likely<br />
|-<br />
|4 || [[User:Schpidi|Stephan Meißl]] || AT || EOX || first day || last day || MapServer || Tentative<br />
|-<br />
|5 || [[User:smathermather|Stephen Mather]] || US || Cleveland Metroparks || first day || last day || OpenDroneMap || Highly Likely<br />
|-<br />
|6 || [[User:hobu|Howard Butler]] || US || Hobu Inc || Monday|| Friday morning || PDAL, MapServer, Proj.4, GDAL || Booked<br />
|-<br />
|7 || [[User:tomkralidis|Tom Kralidis]] || CA || self || first day|| Friday afternoon || pycsw, OWSLib, GeoHealthCheck, pygeometa, other geopython, MapServer || Booked<br />
|-<br />
|8 || [[User:pomadchin|Grigory Pomadchin]] || RU || Azavea || first day || last day || PDAL || Highly Likely<br />
|-<br />
|9 || [[User:sdlime|Steve Lime]] || US || self || first day || last day || MapServer || Booked<br />
|-<br />
|#|| your name || country code || org || date || date || project name || Confirmed, tentative, etc <br />
|}<br />
<br />
== Communication ==<br />
<br />
* Please join the mailing list: http://lists.osgeo.org/mailman/listinfo/tosprint<br />
* IRC chat during the event: #tosprint Server: irc.freenode.net<br />
* Twitter: #TOSprint ( https://twitter.com/search?q=tosprint )<br />
<br />
== Photos ==<br />
<br />
== Costs ==<br />
<br />
Participants should plan for the following costs:<br />
<br />
* Travel to Daytona Beach<br />
* Accommodation for four nights (including breakfast)<br />
<br />
All other costs - food, outings and entertainment - should/will be covered by the sponsors<br />
<br />
<br />
== Financial == <br />
<br />
'''Detailed budget'''<br />
* [[Daytona_Beach_Code_Sprint_2017_:_Budget|Budget]]<br />
<br />
== Individual preparation ==<br />
<br />
* Bring your own laptop<br />
* Install GIT and compiler tools, and come with a working development environment<br />
* If your laptop need it, video export adapter to DVI and/or VGA<br />
* Optional: something to take pictures (camera, smartphone, small tablet...)<br />
<br />
== Sponsors ==<br />
<br />
We have three sponsorship levels:<br />
<br />
* Gold: >= 2500 USD<br />
* Silver: 1500 USD<br />
* Bronze: 750 USD<br />
<br />
We encourage sponsors to support nutriment and entertainment for the <br />
sprinters as they work hard and play hard for four or five productive days. <br />
Contributions will be put towards lunch, snacks, and dinner costs for the <br />
sprinters, and potentially bringing in sprinters who might otherwise be unable <br />
to attend. Any surplus at the end of the event will be turned over to OSGeo or <br />
used for a future code sprint.<br />
<br />
Sponsors will receive the following:<br />
<br />
<br />
* Your logo at the top of this page<br />
* Mention in all of our public communication<br />
* Our undying gratitude, which comes in handy when you least expect it (Remember that feature you wanted...) <br />
* And as extra, for Silver and Gold: Kakemono in the event room (if you provide it)<br />
<br />
To sponsor, please contact xxx directly.<br />
<br />
<br />
[[Category:Code Sprints]]<br />
[[Category:C Tribe Code Sprint]]</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=Daytona_Beach_Code_Sprint_2017&diff=104287Daytona Beach Code Sprint 20172016-12-06T21:50:58Z<p>Wiki-Remanuele: /* Participants */</p>
<hr />
<div><br />
=== Gold Sponsors ===<br />
<br />
=== Silver Sponsors ===<br />
<br />
=== Bronze Sponsors ===<br />
<br />
=== Venue Sponsor ===<br />
<br />
<br />
=== Other/in-kind sponsors ===<br />
<br />
{| border=0 cellspacing=15 cellpadding=10<br />
|<br />
[[File:OSGeo_logo.png|260px|OSGeo|link=http://www.osgeo.org/]]<br />
<br><br />
http://www.osgeo.org/<br />
|}<br />
<br />
== Purpose ==<br />
<br />
Bring together project members to make decisions and tackle larger geospatial <br />
problems as in previous years: <br />
<br />
* [[Paris Code Sprint 2016|Paris]] (2016)<br />
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)<br />
* [[Vienna Code Sprint 2014|Vienna]] (2014)<br />
* [[Boston Code Sprint 2013|Boston]] (2013)<br />
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)<br />
* [[Montreal Code Sprint 2011|Montreal]] (2011)<br />
* [[New York Code Sprint 2010|New York City]] (2010)<br />
* [[Toronto Code Sprint 2009|Toronto]] (2009)<br />
<br />
== Other Events from January to March 2017 ==<br />
<br />
* FOSSGIS Hacking event January 20-22<br />
* FOSS4G Asia January 26-29<br />
* '''OSGeo's 11th birthday Feb 4'''<br />
* FOSDEM Feb 4-5<br />
* FOSS4G-IT (Genoa) Feb 8-11<br />
* Daytona 500 NASCAR race Feb 26<br />
* OGC Technical meeting March 7-11<br />
<br />
== Dates and Times ==<br />
<br />
Dates: <br />
* Sprint: Tuesday-Friday, Feb 7 to 10, 2017 (4 days)<br />
* Welcome event: TBD<br />
<br />
== Location ==<br />
<br />
=== Coding Venue ===<br />
* On campus of Dayton State College (https://www.openstreetmap.org/#map=15/29.1953/-81.0537)<br />
* Located 5 minutes from Daytona International Airport (DAB)<br />
<br />
=== Accommodations ===<br />
Several hotels are within walking distance of the venue.<br />
<br />
* TODO: List a few nearby hotels<br />
<br />
=== Airport options ===<br />
Airports to look at DAB - Daytona Beach International - Connects thru Atlanta on Delta, Charolette NC on American Airlines, and JFK from Jet Blue this might help with connections ideas: http://www.flydaytonafirst.com/schedule.stml<br />
<br />
DAB is super easy in/out 5 minutes away from Embry-Riddle Aeronautical University, actually the college is situated off the runway for the flight school. Here are the other airports that might be cheaper on the surface, but between having to commute another hour plus the extra time dealing with the airports...DAB is probably $200 more to fly in/out of, but you save hours of transportation time and costs. Of course if you are hitting Disney World while you are here or something, then fly out of Orlando or Sanford. Or Kennedy Space Center which is an hour South, you could fly out of Melbourne FL or again Orlando. MCO is the main Orlando airport and probably has the "cheapest flights" because of the volume, but security takes a good bit of time, and typically you need to check in 90 minutes early, and traffic in Orlando can build quickly.<br />
<br />
SFB is about 50 minutes South West and typically has good deals on Allegiant Airlines (no-frills) http://www.orlandosanfordairport.com/<br />
<br />
MCO is about 90 minutes West in Orlando FL<br />
<br />
JAX is about 90 minutes North in Jacksonville FL<br />
<br />
== Schedule ==<br />
<br />
=== Mon Feb 6, 2017 Welcoming Event ===<br />
<br />
=== Tue Feb 7, 2017 - First Sprint Day / Evening ===<br />
<br />
=== Wed Feb 8, 2017 - Second Sprint Day / Evening ===<br />
<br />
=== Thu Feb 9, 2017 - Third Sprint Day / Evening ===<br />
<br />
=== Fri Feb 10, 2017 - Fourth Sprint Day ===<br />
<br />
== Project Plans ==<br />
(i.e what do you wish/want/plan to work on during the sprint ?)<br />
<br />
* <br />
== Social ideas ==<br />
<br />
If you need to take a break, some ideas close to the sprint place:<br />
<br />
== Participants ==<br />
<br />
We are planning for attendance of ~50. Please add your name and the projects <br />
you are planning to sprint and note the likeliness of your attendance.<br />
<br />
{| style="border: solid grey 1px; width:100%" class="sortable"<br />
|+ Participants<br />
|-<br />
| # || Participant || Country || Organization || Arrival || Departure || Project Work on || Attendance / Notes<br />
|-<br />
|#|| name || country code || org || date || date || project name || Confirmed, tentative, etc <br />
|-<br />
|1 || [[User:remanuele|Rob Emanuele]] || US || Azavea || first day || last day || PDAL || Highly Likely<br />
|}<br />
<br />
== Communication ==<br />
<br />
* Please join the mailing list: http://lists.osgeo.org/mailman/listinfo/tosprint<br />
* IRC chat during the event: #tosprint Server: irc.freenode.net<br />
* Twitter: #TOSprint ( https://twitter.com/search?q=tosprint )<br />
<br />
== Photos ==<br />
<br />
== Costs ==<br />
<br />
Participants should plan for the following costs:<br />
<br />
* Travel to Daytona Beach<br />
* Accommodation for four nights (including breakfast)<br />
<br />
All other costs - food, outings and entertainment - should/will be covered by the sponsors<br />
<br />
<br />
== Financial == <br />
<br />
'''Detailled budget'''<br />
* [[Daytona_Beach_Code_Sprint_2017_:_Budget|Budget]]<br />
<br />
== Individual preparation ==<br />
<br />
* Bring your own laptop<br />
* Install GIT and compiler tools, and come with a working development environment<br />
* If your laptop need it, video export adapter to DVI and/or VGA<br />
* Optional: something to take pictures (camera, smartphone, small tablet...)<br />
<br />
== Sponsors ==<br />
<br />
We have three sponsorship levels:<br />
<br />
* Gold: >= 2500 USD<br />
* Silver: 1500 USD<br />
* Bronze: 750 USD<br />
<br />
We encourage sponsors to support nutriment and entertainment for the <br />
sprinters as they work hard and play hard for four or five productive days. <br />
Contributions will be put towards lunch, snacks, and dinner costs for the <br />
sprinters, and potentially bringing in sprinters who might otherwise be unable <br />
to attend. Any surplus at the end of the event will be turned over to OSGeo or <br />
used for a future code sprint.<br />
<br />
Sponsors will receive the following:<br />
<br />
<br />
* Your logo at the top of this page<br />
* Mention in all of our public communication<br />
* Our undying gratitude, which comes in handy when you least expect it (Remember that feature you wanted...) <br />
* And as extra, for Silver and Gold: Kakemono in the event room (if you provide it)<br />
<br />
To sponsor, please contact xxx directly.<br />
<br />
<br />
[[Category:Code Sprints]]<br />
[[Category:C Tribe Code Sprint]]</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2016_Code_Sprint&diff=99425FOSS4G 2016 Code Sprint2016-06-15T23:29:10Z<p>Wiki-Remanuele: /* Registered Attendees */</p>
<hr />
<div>== CodeSprint ==<br />
<br />
Venue: Bonn, Germany<br />
<br />
This year, once again, we are following the old tradition of hosting a codesprint on the FOSS4G. More precisely, we offer a setting so that individual projects can meet for their codesprint. Since projects benefit from each other as well, the codesprint will naturally be held conjointly at one place.<br />
Unfortunately, circumstances have forced us to divide the codesprint timetable-wise.<br />
<br />
[[Image:Basecamp5.png|200px|thumb|right]]<br />
[[Image:Basecamp6.png|200px|thumb|right]]<br />
[[Image:Basecamp7.png|200px|thumb|right]]<br />
[[Image:Basecamp1.png|200px|thumb|right]]<br />
<br />
'''The first part''' is scheduled to take place directly before the conference, the second immediately after. The first two and a half days start on Sunday, August 21, 2016 at around noon and are scheduled to end on Tuesday, August 23, 2016 (open end). The '''second part''' starts in the morning of Saturday, August 27, 2016 and ends on Sunday at 12 pm.<br />
<br />
[[Image:Basecamp2.png|200px|thumb|right]]<br />
[[Image:Basecamp3.png|200px|thumb|right]]<br />
<br />
We are happy to have found a really '''awesome location''' for you. Codesprint and accommodations are combined in one hall. Check out http://www.basecamp-bonn.com/ for details about the venue.<br />
Working zones will be created for you in the breakfast area and hallways. There’s the option of finding relatively inexpensive sleeping accommodations in train sleeping cars, camping buses, classic cars and more. Additionally, an outdoor area is available for you to enjoy Bonn’s summer weather in August, while working. Healthy and not-so-healthy catering of drinks and snacks will be provided by us. Participation in codesprint is free of charge. However, overnight stays will have to be reserved and paid for by you.<br />
<br />
[[Image:Basecamp4.png|200px|thumb|right]]<br />
<br />
Another hint: the BaseCamp is within '''walking distance from the conference venue''' (WCCB) and has good access to public transportation – the Icebreaker takes place here, too.<br />
You see, it’s worthwhile booking here!<br />
<br />
As the accommodations are available to all FOSS4G participants, we will make an effort to make advance booking possible for you a few days ahead, to ensure you have the opportunity to sleep on-site and wrap up the evenings jointly. For that, it’s necessary for you to sign up (https://wiki.osgeo.org/wiki/FOSS4G_2016_Code_Sprint) and leave your email address so that we can contact you immediately accomodation booking is available. We need your sign-up for the planning of snacks and drinks, too!<br />
<br />
This is open to all who wish to participate in one or more projects. There’s always plenty to do – it’s not all about programming. Translation, documentation, feedback, discussions, testing – all this is also important for project so everyone is cordially invited to attend the codesprints! Registration with the conference is not a prerequisite for participation in codesprint.<br />
<br />
One thing we’d like to ask you: with an approx. 120 participants anticipated, the WLAN capacity will naturally be exhausted at some point. Please be sure to avoid huge on-site downloads of data, as this could impact the work of others. Thank you!<br />
<br />
The Codesprint Organizing Team is looking forward to your coming!<br />
<br />
'''In summary:'''<br />
<br />
'''When:''' <br />
* Part I: Sun 2016-08-21 12:00 noon - Tue 2016-08-23 (open end)<br />
* Part II: Sat 2016-08-27 - Sun 2016-08-28 12:00 noon<br />
<br />
'''Where:'''<br />
* Venue & Accommodation: BaseCamp. (For more informations: http://www.basecamp-bonn.com/) [[http://www.openstreetmap.org/way/44335958#map=18/50.70763/7.12316| OpenStreetMap]]<br />
* Nearby Hotel: Bonnox (http://www.bonnox.de/en/)<br />
<br />
'''Questions/Comments/Ideas'''<br />
<br />
* If you have questions/comments/ideas please let us know. Send an email to codesprint@foss4g2016.org. You are welcome!<br />
<br />
== Sponsors ==<br />
Thanks to our great sponsors!<br />
<br />
[[File:FOSSGIS_OSGeo_DACH.png]] <br />
<br />
<br />
== Registered Attendees ==<br />
<br />
The Code Sprint does not cost any money. For us it makes planning easier if we know who is coming. So please leave your Name and mark the days you will come.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="30"|No<br />
!width="250"|Name<br />
!width="250"|Email<br />
!width="250"|Projects<br />
!width="30"|sun<br />
!width="30"|mon<br />
!width="30"|tue<br />
!width="30"|sat<br />
!width="30"|sun<br />
!width="60"|Accomodation<br />
!width="30"|vegetarian food<br />
|-<br />
| 1 ||[[User:Astrid Emde|Astrid Emde]] || astrid_emde@osgeo.org || [[Mapbender]] & Organization || x || x || x || x || x || other || x<br />
|-<br />
| 2 ||[[User:rcoup|Rob Coup]] || robert@coup.net.nz || [[GDAL]], [[GeoServer]] || - || x || x || - || - || Basecamp ||<br />
|-<br />
| 3 ||[[User:alfonx|Stefan Tzeggai]] || tzeggai@wikisquare.de || || - || - || x || x || - || Basecamp? ||<br />
|-<br />
| 4 ||[[User:Neteler|Markus Neteler]] || neteler@osgeo.org || [[GRASS GIS]] || x || x || x || x || x || other || x<br />
|-<br />
| 5 ||[[User:pcav|Paolo Cavallini]] || cavallini@faunalia.it || [[QGIS]] || x || x || x || x || x || Basecamp? || <br />
|-<br />
| 6 ||[[User:Pirmin_Kalberer|Pirmin Kalberer]] || pka [ät] sourcepole.ch || [[QGIS]], [[GDAL]] || x || x || x || - || - || Basecamp || <br />
|-<br />
| 7 ||[[User:neumann|Andreas Neumann]] || andreas [ät] qgis.org || [[QGIS]] || x || x || x || x || - || Basecamp ||<br />
|-<br />
| 8 ||[[User:timlinux|Tim Sutton]] || tim [ät] qgis.org || [[QGIS]] || x || x || x || x || - || Basecamp || yes<br />
|-<br />
| 9 ||[[User:Lucadelu|Luca Delucchi]] || lucadeluge @ gmail.com || [[GRASS GIS]] || x || x || x || x || x || Basecamp || <br />
|-<br />
| 10 ||[[User:Schpidi|Stephan Meißl]]||stephan [ät] meissl.name||MapServer, EOxServer||?||?||x||-||-||Basecamp||<br />
|-<br />
| 11 ||[[User:lastools|Martin Isenburg]] || martin near rapidlasso.com || LASzip for LAS 1.4 || x || x || x || x || x || Basecamp ||<br />
|-<br />
| 12 || [[User:jgrocha|Jorge Gustavo Rocha]] || jgr@di.uminho.pt || GeoExt 3 || x || x || x || x || x || Basecamp ||<br />
|-<br />
| 13 || [[User:alexbruy|Alex Bruy]] || alexander.bruy at gmail.com || [[QGIS]] || x || x || x || x || x || Basecamp ||<br />
|-<br />
| 14 || [[User:volaya|Victor Olaya]] || volayaf at gmail.com || [[QGIS]] || x || x || x || x || x || Basecamp ||<br />
|-<br />
| 15 || [[bartvde2|Bart van den Eijnden]] || bartvde at osgis.nl || [[OpenLayers]] || ? || x || x || ? || ? || Basecamp? ||<br />
|-<br />
| 16 || [[User:anitagraser|Anita Graser]] || anitagraser [ät] gmx.at || [[QGIS]] || - || x || x || - || -|| Basecamp ||<br />
|-<br />
| 17 ||[[User:Dmorissette|Daniel Morissette]]||dmorissette at mapgears.com||MapServer, GDAL/OGR||?||?||x||x||?||Basecamp||<br />
|-<br />
| 18 ||[[User:Stranger | Andreas Schmitz]] || hwbllmnn@mailbox.org || Mapbender || || || || || || other ||<br />
|-<br />
| 19 ||[[User:Uli | Uli Rothstein]] || || Mapbender || || || || || || other ||<br />
|-<br />
| 20 ||[[User:Tbonfort|Thomas Bonfort]]||thomas.bonfort@gmail.com||MapServer||?||?||x||x||?||Basecamp||<br />
|-<br />
| 21 || CCC VOC Team || || video || || || || || || Basecamp ||<br />
|-<br />
| 22 || CCC VOC Team|| || video || || || || || || Basecamp ||<br />
|-<br />
| 23 || CCC VOC Team || || video || || || || || || Basecamp ||<br />
|-<br />
| 24 || CCC VOC Team || || video || || || || || || Basecamp ||<br />
|-<br />
| 25 ||CCC VOC Team || || video || || || || || || Basecamp ||<br />
|-<br />
| 26 ||[[User:Martinl|Martin Landa]] || || [[GRASS GIS]], [[GDAL]], [[QGIS]], [[PyWPS]], GIS.lab || x || x || x || x || x|| Basecamp? ||<br />
|-<br />
| 27 ||[[User:jachym|Jáchym Čepický]] || jachym.cepicky at gmail || [[PyWPS]], GIS.lab || x || x || x || x || x|| Basecamp ||<br />
|-<br />
| 28 ||[[User:Jonaseberle|Jonas Eberle]] || jonas.eberle at gmx.de || [[PyWPS]] || x || x || x || x || x || Basecamp/other? ||<br />
|-<br />
| 29 ||[[User:dassau|Otto Dassau]] ||otto at qgis.org || [[QGIS]] || x || x || x || - || - || other || yes<br />
|-<br />
| 30 ||[[User:rouault|Even Rouault]]||even.rouault @ spatialys.com||GDAL, MapServer, QGIS||?||?||x||x||?||Basecamp||<br />
|-<br />
| 31 ||[[User:grizonnetm|Manuel Grizonnet]]||manuel.grizonnet @ cnes.fr||OTB, OSGeo-Live, QGIS||x||x||x||-||-||Basecamp||<br />
|-<br />
| 32 ||[[User:mlennert|Moritz Lennert]]||mlennert at club worldonline be||GRASS GIS||x||x||x||?||?||Other/Basecamp||<br />
|-<br />
| 33 ||Verena Diewald || || Mapbender || || || || || || other ||<br />
|-<br />
| 34 ||Andriy Oblivantsev || || Mapbender || || || || || || other ||<br />
|-<br />
| 35 ||Axel Schaefer || || Mapbender || || || || || || other ||<br />
|-<br />
| 36 || David Patzke || || Mapbender || || || || || || other ||<br />
|-<br />
| 37 || Thekla Wirkus || || Mapbender || || || || || || other ||<br />
|-<br />
| 38 || Charly Toma || || Mapbender || || || || || || other ||<br />
|-<br />
| 39 ||[[User:Lads|Luís de Sousa]] ||luis de sousa @ protonmail ch || [[PyWPS]] || ? || x || x || x || ? || Basecamp? ||<br />
|-<br />
| 40 ||[[User:ajolma|Ari Jolma]]||ari.jolma @ gmail.com||GDAL, MapServer, QGIS||?||?||x||x||?||Beethoven||<br />
|-<br />
| 41 ||[[User:magicgate|Jakob Miksch]]||jakob.miksch [ät] posteo.eu||QGIS||x||?||?||x||x||Basecamp||<br />
|-<br />
| 42 ||[[User:Yjacolin|yjacolin]] ([[User talk:Yjacolin|talk]]) || yves dot jacolin [at] camptocamp.com ||QGIS||x||x||x|| || ||Basecamp?||<br />
|-<br />
| 43 || Arnaud Morvan ||arnaud dot morvan @ camptocamp.com||QGIS||x||x||x|| || ||Basecamp||<br />
|-<br />
| 44 || Stéphane Brunner || stephane dot brunner [at] camptocamp.com || QGIS || x || x || x || || || Basecamp? ||<br />
|-<br />
| 45 || [[User:asgerskovbopetersen|Asger Skovbo Petersen]] || asger ãt septima.dk || QGIS || - || x || x || - || - || Other ||<br />
|-<br />
| 46 ||[[User:Tudorbarascu|Tudor Bărăscu ]] || tudor dot barascu [at] qtibia.ro || [[QGIS]] || x || x || x || x || x || Basecamp? || <br />
|-<br />
| 47 ||[[User:moovida|Andrea Antonello ]] || andrea dot antonello [at] gmail dot com || gvSIG || - || - || x || - || - || other || <br />
|-<br />
| 48 ||[[User:Silli|Silvia Franceschi ]] || silvia dot franceschi [at] gmail dot com || gvSIG || - || - || x || - || - || other || <br />
|-<br />
| 49 || [[User:Guychisholm|Guy Chisholm]] || guy.chisholm at geoplace dot co dot uk || [[GeoServer]], [[OpenLayers]] || x || ? || ? || x || x || Basecamp ||<br />
|-<br />
| 50 || [[User:Remanuele|Rob Emanuele]] || remanuele at azavea dot com || [[GDAL]], [[JTS]], [[Proj4j]], [[GeoTrellis]], [[GeoTools]] || x || x || x || ? || ? || other ||<br />
|}<br />
<br />
= Workgroups =<br />
<br />
== Mapbender ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:Astrid Emde|Astrid Emde]]<br />
* [[User:Stranger | Andreas Schmitz]]<br />
* [[User:Uli | Uli Rothstein]]<br />
* Axel Schaefer<br />
* David Patzke<br />
* Andriy Oblivantsev<br />
* Verena Diewald<br />
* Charly Toma<br />
* Thekla Wirkus<br />
<br />
'''Goals:''' <br />
* modularisation<br />
* tests<br />
* documentation<br />
* & more<br />
<br />
== GRASS GIS ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:Neteler|Markus Neteler]]<br />
* [[User:Lucadelu|Luca Delucchi]]<br />
* [[User:Martinl|Martin Landa]]<br />
* [[User:mlennert|Moritz Lennert]]<br />
<br />
'''Goals:''' <br />
<br />
* planning towards GRASS GIS 8<br />
* integrating GSoC results<br />
<br />
== QGIS ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:pcav|Paolo Cavallini]]<br />
* [[User:Pirmin_Kalberer|Pirmin Kalberer]]<br />
* [[User:neumann|Andreas Neumann]]<br />
* [[User:volaya|Victor Olaya]]<br />
* [[User:alexbruy|Alex Bruy]]<br />
* [[User:anitagraser|Anita Graser]]<br />
* [[User:dassau|Otto Dassau]]<br />
* [[User:Yjacolin|yjacolin]]<br />
* Arnaud Morvan<br />
* [[User:Tudorbarascu|Tudor Bărăscu]]<br />
<br />
'''Goals:''' <br />
<br />
* working on QGIS 3.0<br />
* porting plugins to Python 3<br />
* Working on QWC II<br />
* Working on QGIS Processing framework<br />
* Working on Documentation 2.14/2.16<br />
<br />
== PyWPS ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:jachym|Jachym Cepicky]]<br />
* [[User:Jonaseberle|Jonas Eberle]]<br />
* [[User:Lads|Luís de Sousa]]<br />
<br />
'''Goals:''' <br />
<br />
* What is needed for PyWPS-4<br />
* Discuss new steps<br />
* WPS 2.0.0 start<br />
<br />
== GIS.lab ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:martinl|Martin Landa]]<br />
* [[User:jachym|Jachym Cepicky]]<br />
<br />
'''Goals:''' <br />
<br />
* GIS.lab 1.0<br />
* GIS.lab QGIS Plugin<br />
* new generation of GIS.lab Web Client<br />
* WPS Processing<br />
<br />
== OSGeo-Live ==<br />
<br />
<br />
'''Attending:''' <br />
<br />
*[[User: Astrid Emde]] <br />
* [[User:grizonnetm|Manuel Grizonnet]]<br />
<br />
'''Goals:''' <br />
<br />
* next version<br />
* documentation<br />
* translation<br />
<br />
== GeoMoose ==<br />
<br />
'''Attending:'''<br />
<br />
* [[User:theduckylittle|Dan "Ducky" Little]]<br />
<br />
''Goals:'''<br />
<br />
* 3.0 release! <br />
<br />
== ORFEO ToolBox ==<br />
<br />
'''Attending:'''<br />
<br />
* [[User:grizonnetm|Manuel Grizonnet]]<br />
<br />
''Goals:'''<br />
<br />
* Documentation<br />
* QGIS/OTB compatibility<br />
* Bugs<br />
<br />
== gvSIG ==<br />
<br />
'''Attending:'''<br />
<br />
* [[User:moovida|Andrea Antonello]]<br />
* [[User:Silli|Silvia Franceschi]]<br />
<br />
''Goals:'''<br />
<br />
* Developer Documentation<br />
* JGrasstools integration<br />
* Geopaparazzi integration<br />
* Bug fixes<br />
<br />
== Project-name ==<br />
<br />
To participate, copy this project skeleton and start a section below for your project.<br />
<br />
'''Attending:''' <br />
<br />
*user <br />
*user<br />
<br />
'''Goals:''' <br />
<br />
*your goals<br />
<br />
[[Category:FOSS4G2016]] [[Category:FOSS4G]] [[Category:Code_Sprints]]</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2016_Administrative&diff=97725Google Summer of Code 2016 Administrative2016-03-24T21:58:29Z<p>Wiki-Remanuele: /* 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=250px|'''email'''<br />
|'''Software community'''<br />
|'''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 />
|Idea I would like to mentor<br />
|-<br />
|2<br />
|Alexander<br />
|Bruy <br />
|alexbruy<br />
|alexander.bruy AT gmail.com <br />
|QGIS<br />
|<br />
|-<br />
|3<br />
|Victor<br />
|Olaya <br />
|volaya<br />
|volayaf AT gmail DOT com <br />
|QGIS<br />
|<br />
|-<br />
|4<br />
|Daniel<br />
|Kastl<br />
|dkastl<br />
|daniel AT georepublic DOT de <br />
|pgRouting<br />
|<br />
|-<br />
|5<br />
|Massimiliano<br />
|Cannata<br />
|maxi<br />
|massimiliano.cannata AT gmail DOT com <br />
|istSOS<br />
|<br />
|-<br />
|6<br />
|Milan<br />
|Antonovic<br />
|milan<br />
|milan.antonovic AT gmail DOT com <br />
|istSOS<br />
|<br />
|-<br />
|7<br />
|Jachym<br />
|Cepicky<br />
|jachym<br />
|jachym.cepicky AT gmail <br />
|PyWPS<br />
|<br />
|-<br />
|8<br />
|Andrea<br />
|Antonello<br />
|moovida<br />
|andrea.antonello AT gmail DOT com<br />
|JGrasstools, gvSIG, Geopaparazzi<br />
|<br />
|-<br />
|9<br />
|Rashad<br />
|Kanavath<br />
|rashadkm<br />
|rashadkm AT gmail DOT com<br />
|GRASS GIS, OSSIM, GDAL<br />
|<br />
|-<br />
|10<br />
|Cameron<br />
|Shorter<br />
|CameronShorter<br />
|cameronDOTs h o r ter AT gmail com<br />
|OSGeo-Live<br />
|<br />
|-<br />
|11<br />
|Stephen<br />
|Woodbridge<br />
|woodbri<br />
|woodbri AT swoodbridge DOT com<br />
|pgRouting<br />
|<br />
|-<br />
|12<br />
|Vicky<br />
|Vergara<br />
|cvvergara<br />
|vicky AT georepublic DOT de<br />
|pgRouting<br />
|<br />
|-<br />
|13<br />
|Dmitry<br />
|Baryshnikov<br />
|bishop<br />
|bishop.dev AT gmail.com <br />
|GDAL<br />
|<br />
|-<br />
|14<br />
|Luca<br />
|Delucchi<br />
|lucadelu<br />
|lucadeluge AT gmail.com <br />
|GRASS GIS<br />
|<br />
|-<br />
|15<br />
|Anna<br />
|Petrasova<br />
|<br />
|kratochanna AT gmail.com <br />
|GRASS GIS<br />
|<br />
|-<br />
|16<br />
|Stefan<br />
|Steiniger<br />
|<br />
|sstein AT geo.uzh.ch <br />
|OneBusAway, OpenTripPlanner, OpenJUMP<br />
|for OneBusAway see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here]<br />
|-<br />
|17<br />
|Sean<br />
|Barbeau<br />
|<br />
|barbeau AT cutr.usf.edu<br />
|OneBusAway, OpenTripPlanner<br />
|for OneBusAway see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here], also there are ideas around for OpenTripPlanner Android App, and the GTFS-RT Validator<br />
|-<br />
|18<br />
|Riccardo<br />
|Rigon<br />
|abouthydrology<br />
|rccrd.rgn AT gmail DOT com<br />
|JGrasstools, gvSIG, Geopaparazzi<br />
|<br />
|-<br />
|19<br />
|Vaclav<br />
|Petras<br />
|<br />
|wenzeslaus AT gmail.com <br />
|GRASS GIS<br />
|<br />
|-<br />
|20<br />
|Oliver<br />
|May<br />
|<br />
|oliver AT dfc DOT be<br />
|Geomajas, leaflet, openlayers, geoserver, geotools<br />
|<br />
|-<br />
|21<br />
|Even<br />
|Rouault<br />
|<br />
|even dot rouault AT spatialys dot com<br />
|GDAL<br />
|<br />
|-<br />
|22<br />
|Alexandre<br />
|Dubé<br />
|<br />
|adube AT mapgears dot com<br />
|OL3-Google-Maps<br />
|<br />
|-<br />
|23<br />
|Moritz<br />
|Lennert<br />
|<br />
|mlennert AT club dot worldonline dot be<br />
|GRASS GIS<br />
|<br />
|-<br />
|24<br />
|Roberto<br />
|Marzocchi<br />
|<br />
|roberto dot marzocchi AT gmail dot com dot<br />
|GRASS GIS<br />
|<br />
|-<br />
|25<br />
|Brian M<br />
|Hamlin<br />
|darkblue_b<br />
|maplabs AT light42 DOT com<br />
|SciPy geospatial stack, PostGIS, gdal 2.0<br />
|<br />
|-<br />
|26<br />
|Jessica<br />
|Lapointe<br />
|<br />
|jlapointe AT mapgears dot com<br />
|OL3-Google-Maps<br />
|<br />
|-<br />
|27<br />
|Gérald<br />
|Fenoy<br />
|djay<br />
|gerald.fenoy AT geolabs.fr <br />
|ZOO-Project<br />
|<br />
|-<br />
|28<br />
|Massimo<br />
|Di Stefano<br />
|epifanio<br />
|epiesasha AT me DOT com<br />
|jupyter noytebook, cross projects python based<br />
|<br />
|-<br />
|29<br />
|Patrick<br />
|Hogan<br />
|<br />
|patrick.hogan AT nasa DOT gov<br />
|NASA World Wind<br />
|<br />
|-<br />
|30<br />
|Oscar<br />
|Kramer<br />
|<br />
|oscarkramer AT yahoo DOT com <br />
|OSSIM<br />
|<br />
|-<br />
|31<br />
|Jakub<br />
|Balhar<br />
|<br />
|jakub AT balhar DOT net<br />
|NASA World Wind<br />
|<br />
|-<br />
|32<br />
|Jonas<br />
|Eberle<br />
|<br />
|jonas.eberle AT gmx DOT de<br />
|PyWPS<br />
|<br />
|-<br />
|33<br />
|Martin<br />
|Landa<br />
|<br />
|landa.martin AT gmail DOT com<br />
|GRASS GIS<br />
|<br />
|-<br />
|34<br />
|Rob<br />
|Emanuele<br />
|lossyrob<br />
|rdemanuele AT gmail DOT com<br />
|GDAL<br />
|<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 dev community 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 />
== Tips for mentors ==<br />
<br />
This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.<br />
<br />
=== Good ideas ===<br />
<br />
* Test students before selection. Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand if they are capable.<br />
* Time management tips: Try not to mentor more than one project per year. In any case, you can be primary mentor only for one project. Consider carefully the time that you can allocate on GSoC.<br />
* ...<br />
<br />
=== Bad ideas ===<br />
<br />
* ...<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>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2016_Administrative&diff=97724Google Summer of Code 2016 Administrative2016-03-24T21:58:05Z<p>Wiki-Remanuele: /* 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=250px|'''email'''<br />
|'''Software community'''<br />
|'''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 />
|Idea I would like to mentor<br />
|-<br />
|2<br />
|Alexander<br />
|Bruy <br />
|alexbruy<br />
|alexander.bruy AT gmail.com <br />
|QGIS<br />
|<br />
|-<br />
|3<br />
|Victor<br />
|Olaya <br />
|volaya<br />
|volayaf AT gmail DOT com <br />
|QGIS<br />
|<br />
|-<br />
|4<br />
|Daniel<br />
|Kastl<br />
|dkastl<br />
|daniel AT georepublic DOT de <br />
|pgRouting<br />
|<br />
|-<br />
|5<br />
|Massimiliano<br />
|Cannata<br />
|maxi<br />
|massimiliano.cannata AT gmail DOT com <br />
|istSOS<br />
|<br />
|-<br />
|6<br />
|Milan<br />
|Antonovic<br />
|milan<br />
|milan.antonovic AT gmail DOT com <br />
|istSOS<br />
|<br />
|-<br />
|7<br />
|Jachym<br />
|Cepicky<br />
|jachym<br />
|jachym.cepicky AT gmail <br />
|PyWPS<br />
|<br />
|-<br />
|8<br />
|Andrea<br />
|Antonello<br />
|moovida<br />
|andrea.antonello AT gmail DOT com<br />
|JGrasstools, gvSIG, Geopaparazzi<br />
|<br />
|-<br />
|9<br />
|Rashad<br />
|Kanavath<br />
|rashadkm<br />
|rashadkm AT gmail DOT com<br />
|GRASS GIS, OSSIM, GDAL<br />
|<br />
|-<br />
|10<br />
|Cameron<br />
|Shorter<br />
|CameronShorter<br />
|cameronDOTs h o r ter AT gmail com<br />
|OSGeo-Live<br />
|<br />
|-<br />
|11<br />
|Stephen<br />
|Woodbridge<br />
|woodbri<br />
|woodbri AT swoodbridge DOT com<br />
|pgRouting<br />
|<br />
|-<br />
|12<br />
|Vicky<br />
|Vergara<br />
|cvvergara<br />
|vicky AT georepublic DOT de<br />
|pgRouting<br />
|<br />
|-<br />
|13<br />
|Dmitry<br />
|Baryshnikov<br />
|bishop<br />
|bishop.dev AT gmail.com <br />
|GDAL<br />
|<br />
|-<br />
|14<br />
|Luca<br />
|Delucchi<br />
|lucadelu<br />
|lucadeluge AT gmail.com <br />
|GRASS GIS<br />
|<br />
|-<br />
|15<br />
|Anna<br />
|Petrasova<br />
|<br />
|kratochanna AT gmail.com <br />
|GRASS GIS<br />
|<br />
|-<br />
|16<br />
|Stefan<br />
|Steiniger<br />
|<br />
|sstein AT geo.uzh.ch <br />
|OneBusAway, OpenTripPlanner, OpenJUMP<br />
|for OneBusAway see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here]<br />
|-<br />
|17<br />
|Sean<br />
|Barbeau<br />
|<br />
|barbeau AT cutr.usf.edu<br />
|OneBusAway, OpenTripPlanner<br />
|for OneBusAway see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here], also there are ideas around for OpenTripPlanner Android App, and the GTFS-RT Validator<br />
|-<br />
|18<br />
|Riccardo<br />
|Rigon<br />
|abouthydrology<br />
|rccrd.rgn AT gmail DOT com<br />
|JGrasstools, gvSIG, Geopaparazzi<br />
|<br />
|-<br />
|19<br />
|Vaclav<br />
|Petras<br />
|<br />
|wenzeslaus AT gmail.com <br />
|GRASS GIS<br />
|<br />
|-<br />
|20<br />
|Oliver<br />
|May<br />
|<br />
|oliver AT dfc DOT be<br />
|Geomajas, leaflet, openlayers, geoserver, geotools<br />
|<br />
|-<br />
|21<br />
|Even<br />
|Rouault<br />
|<br />
|even dot rouault AT spatialys dot com<br />
|GDAL<br />
|<br />
|-<br />
|22<br />
|Alexandre<br />
|Dubé<br />
|<br />
|adube AT mapgears dot com<br />
|OL3-Google-Maps<br />
|<br />
|-<br />
|23<br />
|Moritz<br />
|Lennert<br />
|<br />
|mlennert AT club dot worldonline dot be<br />
|GRASS GIS<br />
|<br />
|-<br />
|24<br />
|Roberto<br />
|Marzocchi<br />
|<br />
|roberto dot marzocchi AT gmail dot com dot<br />
|GRASS GIS<br />
|<br />
|-<br />
|25<br />
|Brian M<br />
|Hamlin<br />
|darkblue_b<br />
|maplabs AT light42 DOT com<br />
|SciPy geospatial stack, PostGIS, gdal 2.0<br />
|<br />
|-<br />
|26<br />
|Jessica<br />
|Lapointe<br />
|<br />
|jlapointe AT mapgears dot com<br />
|OL3-Google-Maps<br />
|<br />
|-<br />
|27<br />
|Gérald<br />
|Fenoy<br />
|djay<br />
|gerald.fenoy AT geolabs.fr <br />
|ZOO-Project<br />
|<br />
|-<br />
|28<br />
|Massimo<br />
|Di Stefano<br />
|epifanio<br />
|epiesasha AT me DOT com<br />
|jupyter noytebook, cross projects python based<br />
|<br />
|-<br />
|29<br />
|Patrick<br />
|Hogan<br />
|<br />
|patrick.hogan AT nasa DOT gov<br />
|NASA World Wind<br />
|<br />
|-<br />
|30<br />
|Oscar<br />
|Kramer<br />
|<br />
|oscarkramer AT yahoo DOT com <br />
|OSSIM<br />
|<br />
|-<br />
|31<br />
|Jakub<br />
|Balhar<br />
|<br />
|jakub AT balhar DOT net<br />
|NASA World Wind<br />
|<br />
|-<br />
|32<br />
|Jonas<br />
|Eberle<br />
|<br />
|jonas.eberle AT gmx DOT de<br />
|PyWPS<br />
|<br />
|-<br />
|33<br />
|Martin<br />
|Landa<br />
|<br />
|landa.martin AT gmail DOT com<br />
|GRASS GIS<br />
|<br />
|-<br />
|34<br />
|Rob<br />
|Emanuele<br />
|<br />
|rdemanuele AT gmail DOT com<br />
|GDAL<br />
|<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 dev community 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 />
== Tips for mentors ==<br />
<br />
This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.<br />
<br />
=== Good ideas ===<br />
<br />
* Test students before selection. Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand if they are capable.<br />
* Time management tips: Try not to mentor more than one project per year. In any case, you can be primary mentor only for one project. Consider carefully the time that you can allocate on GSoC.<br />
* ...<br />
<br />
=== Bad ideas ===<br />
<br />
* ...<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>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=Paris_Code_Sprint_2016_:_GDAL_Agenda&diff=96388Paris Code Sprint 2016 : GDAL Agenda2016-02-06T21:20:04Z<p>Wiki-Remanuele: /* Tasks */</p>
<hr />
<div>Discussion and group review topics for the [[Paris Code Sprint 2016]].<br />
<br />
== Tasks ==<br />
<br />
* Extending [https://trac.osgeo.org/gdal/wiki/rfc61_support_for_measured_geometries RFC 61 - Support for measured geometries] :<br />
** Python testing of new methods<br />
** Implementation in drivers that support it : PostGIS (if not already completed), SQLite/Spatialite, FileGDB, OpenFileGDB, GPKG, Oracle. Check that it works with CSV, VRT, MEM<br />
** Check how that works with reprojection. Probably need ogr2ogr hack<br />
<br />
* Breaking cyclic dependency spatialite->postgis->gdal->spatialite that cause [https://lists.debian.org/debian-gis/2016/02/msg00017.html issues in DebianGIS packaging], possibly by [https://lists.debian.org/debian-gis/2016/02/msg00020.html dlopen()'ing spatialite]<br />
<br />
*Improve error handling of libcurl errors and other network errors for vsi* drivers<br />
** See: https://github.com/mapbox/rasterio/issues/538 for discussion<br />
<br />
== Discussions ==</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=Paris_Code_Sprint_2016&diff=89791Paris Code Sprint 20162016-01-13T21:41:03Z<p>Wiki-Remanuele: Added Rob Emanuele</p>
<hr />
<div>''Gold Sponsors'''<br />
<br />
{| border=0 cellspacing=15 cellpadding=10<br />
|<br />
[[File:Logo-Oslandia.png|260px|Oslandia|link=http://www.oslandia.com/]]<br />
<br><br />
http://www.oslandia.com/<br />
|}<br />
<br />
<br />
''Bronze Sponsors'''<br />
<br />
{| border=0 cellspacing=15 cellpadding=10<br />
|<br />
[[File:Logo-rapidlasso.png|260px|RapidLasso|link=http://www.rapidlasso.com/]]<br />
<br><br />
http://www.rapidlasso.com/<br />
|}<br />
<br />
<br />
== Purpose ==<br />
<br />
Bring together project members to make decisions and tackle larger geospatial <br />
problems as in previous years: <br />
<br />
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)<br />
* [[Vienna Code Sprint 2014|Vienna]] (2014)<br />
* [[Boston Code Sprint 2013|Boston]] (2013)<br />
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)<br />
* [[Montreal Code Sprint 2011|Montreal]] (2011)<br />
* [[New York Code Sprint 2010|New York City]] (2010)<br />
* [[Toronto Code Sprint 2009|Toronto]] (2009)<br />
<br />
== Dates and Times ==<br />
<br />
Dates: <br />
* Welcome event: evening of Mon, Feb 22<br />
* Sprint: Tues, Feb 23 - Fri, Feb 26 (4 days)<br />
<br />
== Place ==<br />
* 16bis Boulevard Montmartre, 75009 Paris - Mozilla Foundation <br />
* https://www.openstreetmap.org/node/2883451098<br />
* Metro: Grand Boulevard or Richelieu Drouot<br />
<br />
== Project Plans ==<br />
(i.e what do you wish/want/plan to work on during the sprint ?)<br />
<br />
*<br />
*<br />
<br />
== Participants ==<br />
<br />
We are planning for attendance of ~50. Please add your name and the projects <br />
you are planning to sprint and note the likeliness of your attendance.<br />
<br />
{| style="border: solid grey 1px; width:100%" class="sortable"<br />
|+ Participants<br />
|-<br />
| # || Participant || Country || Arrival || Departure || Project Work on || Attendance / Notes<br />
|-<br />
| 1 || [[User:Olivier.courtin|Olivier Courtin]] || FR || first day || last day || PostgreSQL/PostGIS || Definite <br />
|-<br />
| 2 || [[User:kalxas|Angelos Tzotsos]] || GR || first day || last day || OSGeo-Live, pycsw || Very Likely <br />
|-<br />
| 3 || [[User:Schpidi|Stephan Meissl]] || AT || first day || last day || MapServer || Very Likely <br />
|-<br />
| 4 || [[Jeff McKenna]] || CA || second day || last day || MapServer || Very Likely <br />
|-<br />
| 5 || Markus Schütz || AT || first day || last day || Potree || Interested but unlikely<br />
|-<br />
| 6 || [[User:msmitherdc|Michael Smith]] || US || first day || last day || PDAL / MapServer || Highly likely<br />
|-<br />
| 7|| [[User:hobu|Howard Butler]] || US || first day || last day || PDAL / MapServer || Booked<br />
|-<br />
| 8|| [[User:lucadelu|Luca Delucchi]] || IT || first day || last day || GRASS, OSGeo-Live || Booked<br />
|-<br />
| 9|| [[User:rouault|Even Rouault]] || FR || first day || last day || GDAL, MapServer, Proj.4? || Highly likely<br />
|-<br />
| 10|| [[User:mloskot|Mateusz Łoskot]] || PL || first day || last day || GDAL, PostGIS || Highly likely<br />
|-<br />
| 11|| [[User:dmorissette|Daniel Morissette]] || CA || first day || last day || MapServer, GDAL/OGR || Very likely<br />
|-<br />
| 12|| [[User:ianturton|Ian Turton]]||UK||first day|| last day || GeoTools, GeoServer, GeoNetwork? || likely if any others from Java tribe appear<br />
|-<br />
| 13|| [[User:Aandre|Adrien André]]|| FR ||first day|| last day || GRASS || Very likely<br />
|-<br />
| 14 || Jérémy Gaillard || FR || first day || last day || Cesium buildings || Definite<br />
|-<br />
| 15|| [[User:Tbonfort|Thomas Bonfort]]|| FR ||first day|| last day || MapServer || Very likely<br />
|-<br />
| 16|| [[User:VincentP|Vincent Picavet]] || FR ||first day|| last day || PostGIS/3D viz & streaming || Definite<br />
|-<br />
| 17|| [[User:Mhugo|Hugo Mercier]] || FR ||first day|| last day || PostGIS/SFCGAL || Definite<br />
|-<br />
| 18|| [[User:Vmo|Vincent Mora]] || FR ||first day|| third day || PostGIS/SFCGAL, Cesium building || Definite<br />
|-<br />
| 19|| [[User:Oscarmartinezrubi|Oscar Martinez Rubi]] || SP ||first day|| last day || Potree / PDAL || Definite<br />
|-<br />
| 20|| Maarten van Meersbergen || NL ||first day|| last day || Potree / PDAL || Very likely<br />
|-<br />
| 21|| Andrew Bell || US ||first day|| last day || PDAL || Booked<br />
|-<br />
| 22|| Martin Isenburg || DE ||first day|| last day || LASzip / QGIS || Booked<br />
|-<br />
| 23|| Connor Manning || US ||first day|| last day || PDAL/Potree || Booked<br />
|-<br />
|24|| Victor Poughon||FR||first day||last day||Orfeo-toolbox||Very likely<br />
|-<br />
|25|| Bruno Friedman||CH ||First day||Last day||Mapserver, Postgis, Potree||Definite<br />
|-<br />
|26|| Julien Enselme||FR||First day||Last day||Mapserver, Postgis, Potree||Definite<br />
|-<br />
|27|| Yann Chemin || FR || first day || last day || GRASS || Definite<br />
|-<br />
|28|| [[User:remanuele|Rob Emanuele]] || US || first day || last day || GDAL (https://git.io/vzZQJ) || Likely<br />
|-}<br />
<br />
== Communication ==<br />
<br />
* Please join the mailing list: http://lists.osgeo.org/mailman/listinfo/tosprint<br />
* IRC chat during the event: #tosprint Server: irc.freenode.net<br />
* Twitter: #TOSprint ( https://twitter.com/search?q=tosprint )<br />
<br />
== Costs ==<br />
<br />
Participants should plan for the following costs:<br />
<br />
* Travel to Paris<br />
* Accommodation for four nights (including breakfast)<br />
<br />
All other costs - food, outings and entertainment - should/will be covered by the sponsors<br />
<br />
<br />
== Hotel and co ==<br />
<br />
Center of Paris is indeed quite small, the sprint place quite central, and metro network quite dense.<br /><br />
So no special need to be that close from the sprint place (anywhere else in Paris could also be fine, with less than 30-45' by tube).<br />
<br />
<br />
However, nice hotels, quite close to the sprint place: <br />
* http://www.astotel.com/hotel/hotel-le-34b/overview<br />
* http://www.hotel20prieure.com/<br />
<br />
<br />
A common way to find a discounted room in Paris is to use booking.com<br />
<br />
Paris is also well known to became an AirBNB city. <br /><br />
Could be so a way to share (big) flat, among some sprinters.<br />
<br />
<br />
And there's also hostels, for those who want/need to find a cheaper hosting solution.<br />
* http://www.hostelworld.com/Paris<br />
<br />
== Sponsors ==<br />
<br />
We have three sponsorship levels:<br />
<br />
* Gold: > 2500 €<br />
* Silver: 1500 €<br />
* Bronze: 750 €<br />
<br />
We encourage sponsors to support nutriment and entertainment for the <br />
sprinters as they work hard and play hard for four or five productive days. <br />
Contributions will be put towards lunch, snacks, and dinner costs for the <br />
sprinters, and potentially bringing in sprinters who might otherwise be unable <br />
to attend. Any surplus at the end of the event will be turned over to OSGeo or <br />
used for a future code sprint.<br />
<br />
Sponsors will receive the following honors:<br />
<br />
<br />
* Your logo at the top of this page<br />
* Mention in all of our public communication<br />
* Our undying gratitude, which comes in handy when you least expect it (Remember that feature you wanted...) <br />
* And as extra, for Silver and Gold: Kakemono in the event room (if you provide it)<br />
<br />
To sponsor, please contact Olivier Courtin (olivier dot courtin at oslandia dot com) directly.<br />
<br />
<br />
[[Category:Code Sprints]]<br />
[[Category:C Tribe Code Sprint]]</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=User:Remanuele&diff=88666User:Remanuele2015-11-20T17:19:39Z<p>Wiki-Remanuele: </p>
<hr />
<div>Lead of [[http://www.geotrellis.io GeoTrellis]] library.<br />
<br />
Program Chair for FOSS4G NA 2015 & 2016.<br />
<br />
Developer at [[http://azavea.com Azavea]].<br />
<br />
rdemanuele [at] gmail [dot] com<br />
<br />
[[Category: OSGeo Member]]<br />
<br />
{{OSGeo Member<br />
|Name=Rob Emanuele<br />
|Address=Philadelphia, PA, USA<br />
|Coordinate=39.958714, -75.158391<br />
}}</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=User:Remanuele&diff=88665User:Remanuele2015-11-20T17:19:21Z<p>Wiki-Remanuele: </p>
<hr />
<div>Lead of [[http://www.geotrellis.io GeoTrellis]] library.<br />
<br />
Program Chair for FOSS4G NA 2015 & 2016.<br />
<br />
Developer at [[http://azavea.com Azavea].<br />
<br />
rdemanuele [at] gmail [dot] com<br />
<br />
[[Category: OSGeo Member]]<br />
<br />
{{OSGeo Member<br />
|Name=Rob Emanuele<br />
|Address=Philadelphia, PA, USA<br />
|Coordinate=39.958714, -75.158391<br />
}}</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=User:Remanuele&diff=88664User:Remanuele2015-11-20T17:18:45Z<p>Wiki-Remanuele: </p>
<hr />
<div>{{OSGeo Member<br />
|Name=Rob Emanuele<br />
|Address=Philadelphia, PA, USA<br />
|Coordinate=39.958714, -75.158391<br />
}}<br />
Lead of [[http://www.geotrellis.io GeoTrellis]] library.<br />
<br />
Program Chair for FOSS4G NA 2015 & 2016.<br />
<br />
Developer at [[http://azavea.com Azavea].<br />
<br />
rdemanuele [at] gmail [dot] com<br />
<br />
[[Category: OSGeo Member]]</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=User:Remanuele&diff=88663User:Remanuele2015-11-20T17:18:20Z<p>Wiki-Remanuele: </p>
<hr />
<div>Lead of [[http://www.geotrellis.io GeoTrellis]] library.<br />
Program Chair for FOSS4G NA 2015 & 2016.<br />
Developer at [[http://azavea.com Azavea].<br />
rdemanuele [at] gmail [dot] com<br />
<br />
[[Category: OSGeo Member]]<br />
<br />
{{OSGeo Member<br />
|Name=Rob Emanuele<br />
|Address=Philadelphia, PA, USA<br />
|Coordinate=39.958714, -75.158391<br />
}}</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=LIDAR_Format_Letter&diff=83734LIDAR Format Letter2015-04-21T07:31:32Z<p>Wiki-Remanuele: /* 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], [http://zoo-project.org ZOO-Project PSC], 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 />
# [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 />
<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 Esri's claim at being good "Standards" citizens is questionable]<br />
<br />
=References=<br />
<br />
<references /></div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=LIDAR_Format_Letter&diff=83733LIDAR Format Letter2015-04-21T07:31:05Z<p>Wiki-Remanuele: /* 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], [http://zoo-project.org ZOO-Project PSC], 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 />
# [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 Robert Emanuele], Software Developer, Azavea Inc.<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 Esri's claim at being good "Standards" citizens is questionable]<br />
<br />
=References=<br />
<br />
<references /></div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=LIDAR_Format_Letter&diff=83732LIDAR Format Letter2015-04-21T07:30:20Z<p>Wiki-Remanuele: /* 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], [http://zoo-project.org ZOO-Project PSC], 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 />
# [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 />
# Robert Emanuele, Software Developer, Azavea<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 Esri's claim at being good "Standards" citizens is questionable]<br />
<br />
=References=<br />
<br />
<references /></div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2014_Code_Sprint&diff=79826FOSS4G 2014 Code Sprint2014-09-03T16:07:42Z<p>Wiki-Remanuele: /* Additional Interested People */</p>
<hr />
<div>== Code Sprint - what's that? ==<br />
<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&nbsp;:)<br />
<br />
== Who ==<br />
All participants are welcome and you don't need to register or attend FOSS4G to attend the Code Sprint (registering here on the wiki is appreciated for planning purposes like coffee and food). Some projects will prefer attendees who have previously engaged with the project and already have a working development environment on their computer (i.e. not all project will welcome helping you set up your development environment). <br />
<br />
== Where &amp; When ==<br />
<br />
<br />
The day after the main conference ('''Saturday, September 13th''' 2014) has been set aside for the Code Sprint.<br />
<br />
The sprint will be in the [http://eliotcenterportland.org Eliot Center] ([http://osm.org/go/WIDlUtpOQ-?m=&relation=186579 OSM]) along side [http://wherecamppdx.org WhereCampPDX].<br />
<br />
== What to Bring ==<br />
<br />
<br />
<br />
== How to get there ==<br />
<br />
TBD<br />
<br />
== Sponsor ==<br />
<br />
<br />
<br />
== Questions/Comments/Ideas ==<br />
<br />
*ask on the foss4g2014 mailing list ([http://lists.osgeo.org/mailman/listinfo/foss4g2014 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 />
<br />
* ''Your name: project(s)''<br />
* Jordan Winthrop: Interested in Art, Mapping & Marketing<br />
* Kyle Shannon: GDAL(?)<br />
* James Hiebert: ?<br />
* Alex Mandel: [[SAC]]<br />
* Rob Emanuele: GeoTrellis, GDAL<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 />
== GeoMoose ==<br />
<br />
'''Attending:''' <br />
<br />
* Eli Adam<br />
* Dan 'Ducky' Little<br />
* Bob Basques<br />
* Jim Klassen<br />
<br />
'''Goals:''' <br />
<br />
* 2.7 wrap up.<br />
* Marketing plan - do mores?<br />
<br />
<br><br />
<br />
== GeoNode ==<br />
<br />
'''Attending:''' <br />
<br />
* Ian Schneider<br />
* Ariel Nunez<br />
* Tyler Garner<br />
* Angelos Tzotsos<br />
* Simone Dalmasso<br />
* Paolo Corti<br />
* Tom Kralidis<br />
<br />
'''Goals:''' <br />
<br />
* TBD<br />
<br />
<br><br />
<br />
== GeoServer ==<br />
<br />
'''Attending:''' <br />
<br />
* Jody Garnett<br />
* Andrea Aime<br />
* Mauro Bartolomeoli<br />
* user<br />
<br />
'''Goals:''' <br />
<br />
* Option 1: Update Wicket to a recent version, goal wider browser compatibility. Benefit from a balance of developers and testers.<br />
* Option 2: Update CITE tests. Benefit from collaboration with the CITE TEAM Engine project.<br />
<br />
'''Note'''<br />
* GeoServer will continue sprinting on Sunday at a different venue, [http://blog.geoserver.org/2014/07/25/geoserver-sunday-sprint-foss4g/ (details)]<br />
<br />
<br><br />
<br />
== GRASS GIS ==<br />
<br />
'''Attending:''' <br />
<br />
* Luca Delucchi<br />
* Markus Neteler<br />
* Anna Petrasova<br />
* Vaclav Petras<br />
* ... you (normal and power users welcome, too)<br />
<br />
'''Goals:''' <br />
<br />
* prepare for GRASS GIS 8 ;-)<br />
<br />
== MapServer ==<br />
<br />
'''Attending:''' <br />
<br />
* Michael Smith <br />
* Jeff McKenna<br />
* Steve Lime<br />
* Daniel Morissette<br />
* Thomas Bonfort<br />
<br />
'''Goals:''' <br />
<br />
*7.0 Release Fixes<br />
<br />
<br><br />
<br />
== PostGIS ==<br />
<br />
'''Attending:'''<br />
* Regina Obe<br />
* Leo Hsu<br />
<br />
'''Goals:'''<br />
* Plan out PostGIS 2.2<br />
<br />
<br><br />
<br />
== pycsw ==<br />
<br />
'''Attending:''' <br />
<br />
* Tom Kralidis<br />
* Angelos Tzotsos<br />
* Jeff McKenna (''buzzer sound'')<br />
* Paolo Corti (I have to split with GeoNode)<br />
<br />
'''Goals:''' <br />
<br />
* OSGeo Incubation<br />
* CSW 3.0<br />
* Roadmap<br />
* packaging (UbuntuGIS, DebianGIS)<br />
* i18n of codebase / messages, docs<br />
<br />
<br><br />
<br />
[[Category:FOSS4G2014]] [[Category:FOSS4G]] [[Category:Code_Sprints]]</div>Wiki-Remanuelehttps://wiki.osgeo.org/w/index.php?title=User:Remanuele&diff=78725User:Remanuele2014-07-25T21:39:21Z<p>Wiki-Remanuele: Created user page.</p>
<hr />
<div>Lead of [[http://www.geotrellis.io GeoTrellis]] library.<br />
<br />
rdemanuele [at] gmail [dot] com<br />
<br />
[[Category: OSGeo Member]]<br />
{{#umSetParam: -75.158391|39.958714|Philadelphia, PA, USA|Remanuele|Rob Emanuele}}<br />
{{#umUserMap: Remanuele|510px|256px|12|2|y}}<br />
{{#umAdmin: Remanuele}}</div>Wiki-Remanuele