OSGeo - User contributions [en]

OSGeo Code Sprint 2018

2018-02-09T09:05:37Z

Wiki-Elpaso: /* Participants */

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

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

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

;Gold Sponsors

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

; Silver Sponsors

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

; Bronze Sponsors

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

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

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

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

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

== Purpose ==

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

== Dates and Times ==

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

== Other Events from January to March 2018 ==

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

== Location ==

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

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

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

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

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

== Schedule ==
* tbd

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

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

== Social ideas ==

== Participants ==

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

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

== Communication ==

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

== Photos ==

== Costs ==

Participants should plan for the following costs:

* Travel to Bonn
* Accommodation for x nights

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

== Financial ==

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

== Individual preparation ==

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

== Sponsoring ==

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

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

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

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

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

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

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

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

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

Thank you very much!

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

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

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

Google Summer of Code 2016 Administrative

2016-03-29T12:52:36Z

Wiki-Elpaso: /* Mentors */

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

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

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

== GSoC general information ==

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

== Contacts ==

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

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

== Mentors ==

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

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#D7E3D1; font-size:95%; empty-cells:show;"
|width=30px|'''Number'''
|width=100px|'''Name'''
|width=100px|'''Surname'''
|width=100px|'''Nickname (IRC)'''
|width=250px|'''email'''
|'''Software community'''
|'''Idea(s) you are available to mentor'''
|-
|1
|Margherita
|Di Leo
|madi
|diregola AT gmail DOT com
|admin at OSGeo
|Idea I would like to mentor
|-
|2
|Alexander
|Bruy
|alexbruy
|alexander.bruy AT gmail.com
|QGIS
|
|-
|3
|Victor
|Olaya
|volaya
|volayaf AT gmail DOT com
|QGIS
|
|-
|4
|Daniel
|Kastl
|dkastl
|daniel AT georepublic DOT de
|pgRouting
|
|-
|5
|Massimiliano
|Cannata
|maxi
|massimiliano.cannata AT gmail DOT com
|istSOS
|
|-
|6
|Milan
|Antonovic
|milan
|milan.antonovic AT gmail DOT com
|istSOS
|
|-
|7
|Jachym
|Cepicky
|jachym
|jachym.cepicky AT gmail
|PyWPS
|
|-
|8
|Andrea
|Antonello
|moovida
|andrea.antonello AT gmail DOT com
|JGrasstools, gvSIG, Geopaparazzi
|
|-
|9
|Rashad
|Kanavath
|rashadkm
|rashadkm AT gmail DOT com
|GRASS GIS, OSSIM, GDAL
|
|-
|10
|Cameron
|Shorter
|CameronShorter
|cameronDOTs h o r ter AT gmail com
|OSGeo-Live
|
|-
|11
|Stephen
|Woodbridge
|woodbri
|woodbri AT swoodbridge DOT com
|pgRouting
|
|-
|12
|Vicky
|Vergara
|cvvergara
|vicky AT georepublic DOT de
|pgRouting
|
|-
|13
|Dmitry
|Baryshnikov
|bishop
|bishop.dev AT gmail.com
|GDAL
|
|-
|14
|Luca
|Delucchi
|lucadelu
|lucadeluge AT gmail.com
|GRASS GIS
|
|-
|15
|Anna
|Petrasova
|
|kratochanna AT gmail.com
|GRASS GIS
|
|-
|16
|Stefan
|Steiniger
|
|sstein AT geo.uzh.ch
|OneBusAway, OpenTripPlanner, OpenJUMP
|for OneBusAway see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here]
|-
|17
|Sean
|Barbeau
|
|barbeau AT cutr.usf.edu
|OneBusAway, OpenTripPlanner
|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
|-
|18
|Riccardo
|Rigon
|abouthydrology
|rccrd.rgn AT gmail DOT com
|JGrasstools, gvSIG, Geopaparazzi
|
|-
|19
|Vaclav
|Petras
|
|wenzeslaus AT gmail.com
|GRASS GIS
|
|-
|20
|Oliver
|May
|
|oliver AT dfc DOT be
|Geomajas, leaflet, openlayers, geoserver, geotools
|
|-
|21
|Even
|Rouault
|
|even dot rouault AT spatialys dot com
|GDAL
|
|-
|22
|Alexandre
|Dubé
|
|adube AT mapgears dot com
|OL3-Google-Maps
|
|-
|23
|Moritz
|Lennert
|
|mlennert AT club dot worldonline dot be
|GRASS GIS
|
|-
|24
|Roberto
|Marzocchi
|
|roberto dot marzocchi AT gmail dot com dot
|GRASS GIS
|
|-
|25
|Brian M
|Hamlin
|darkblue_b
|maplabs AT light42 DOT com
|SciPy geospatial stack, PostGIS, gdal 2.0
|
|-
|26
|Jessica
|Lapointe
|
|jlapointe AT mapgears dot com
|OL3-Google-Maps
|
|-
|27
|Gérald
|Fenoy
|djay
|gerald.fenoy AT geolabs.fr
|ZOO-Project
|
|-
|28
|Massimo
|Di Stefano
|epifanio
|epiesasha AT me DOT com
|GRASS GIS
| webgrass
|-
|29
|Patrick
|Hogan
|
|patrick.hogan AT nasa DOT gov
|NASA World Wind
|
|-
|30
|Oscar
|Kramer
|
|oscarkramer AT yahoo DOT com
|OSSIM
|
|-
|31
|Jakub
|Balhar
|
|jakub AT balhar DOT net
|NASA World Wind
|
|-
|32
|Jonas
|Eberle
|
|jonas.eberle AT gmx DOT de
|PyWPS
|
|-
|33
|Martin
|Landa
|
|landa.martin AT gmail DOT com
|GRASS GIS
|
|-
|34
|Rob
|Emanuele
|lossyrob
|rdemanuele AT gmail DOT com
|GDAL
|
|-
|35
|Anita
|Graser
|
|anitagraser AT gmx DOT at
|QGIS
|
|-
|36
|Giustino
|Tonon
|
|giustino.tonon AT unibz DOT it
|JGrasstools
|
|-
|37
|Alessandro
|Pasotti
|
|apasotti AT gmail DOT com
|QGIS
|QGIS Symbology Repository
|-
|}

== A Mentor's Responsibilities ==

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

Every student project will also have a '''backup mentor''', this person should come from your 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.

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

== Guides for mentors ==

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

== Tips for mentors ==

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.

=== Good ideas ===

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

=== Bad ideas ===

* ...

== Learn more ==

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

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

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

[[Category: Google Summer of Code]]

LIDAR Format Letter

2015-04-16T09:31:17Z

Wiki-Elpaso:

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

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

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

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

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

=Background=
==About LiDAR==

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

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

==LAS Limitations==

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

: LAS format is not without its drawbacks:

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

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

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

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

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

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

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

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

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

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

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

: '''Summary:'''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=Value of Standards=

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

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

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

=Further Reading=

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

=References=

<references />

LIDAR Format Letter

2015-04-16T09:30:49Z

Wiki-Elpaso:

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

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

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

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

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

=Background=
==About LiDAR==

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

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

==LAS Limitations==

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

: LAS format is not without its drawbacks:

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

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

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

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

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

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

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

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

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

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

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

: '''Summary:'''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=Value of Standards=

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

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

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

=Further Reading=

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

=References=

<references />

Vienna Code Sprint 2014

2014-03-10T07:31:23Z

Wiki-Elpaso: /* Participants */

''OSGeo Code Sprint 2014 official web site: [http://vienna2014.sprint.osgeo.org http://vienna2014.sprint.osgeo.org]. Please contact us if you are interested in our [http://vienna2014.sprint.osgeo.org/sponsoring.html sponsorship opportunities].''

'''Gold Sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-Airborne-Interactive.png|260px|Airborne Interactive Ltd|link=http://www.airborne.aero/]]
 
http://www.airborne.aero/
|
[[File:Logo-Austrospace.png‎|260px|Austrospace|link=http://www.austrospace.at/]]
 
http://www.austrospace.at/
|
[[File:Logo-TYDAC.png‎|260px|TYDAC|link=http://www.tydac.ch]]
 
http://www.tydac.ch
|}

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

'''Silver Sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-ITS-VR.jpg|260px|ITS Vienna Region|link=http://www.anachb.at/mehr]]
 
http://www.anachb.at/mehr
|}

'''Bronze Sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-metaspatial.png|260px|metaspatial Institut|link=http://www.metaspatial.net/en/institute]]
 
[http://metaspatial.net/en/institute http://metaspatial.net/en/institute]
|
[[File:Logo-Oslandia.png|260px|Oslandia|link=http://www.oslandia.com]]
 
[http://www.oslandia.com http://www.oslandia.com]
|
[[File:Logo-rapidlasso.png|260px|rapidlasso|link=http://rapidlasso.com]]
 
[http://rapidlasso.com http://rapidlasso.com]
|}

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-Azavea.jpg‎|260px|Azavea|link=http://www.azavea.com]]
 
http://www.azavea.com
|
[[File:Logo-gfoss.png‎|260px|GFOSS.it|link=http://gfoss.it]]
 
http://gfoss.it
|}

'''Venue Sponsor'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-City-of-Vienna.png|260px|City of Vienna MA 14|link=http://www.wien.gv.at/english/administration/ict/index.html]]
 
[http://www.wien.gv.at/english/administration/ict/index.html http://www.wien.gv.at/]
|}

'''Other/in-kind sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-EOX.png|120px|EOX IT Services GmbH|link=http://eox.at]]
 
[http://eox.at http://eox.at]
|}

== Purpose ==

Get together project members to make decisions and tackle larger geospatial
problems (as done last year at the [[Boston Code Sprint 2013]] and previous
years: [[IslandWood Code Sprint 2012|Island Wood]] (2012),
[[Montreal Code Sprint 2011|Montreal]] (2011),
[[New York Code Sprint 2010|New York City]] (2010), and
[[Toronto Code Sprint 2009|Toronto]] (2009)). This code sprint is targeting
members of the "C Tribe" (e.g., MapServer, QGis, GRASS, GDAL, Proj, PostGIS,
MapGuide, OpenLayers). Other tribes are welcome to join the sprint, of course,
but we hope that "C Tribe" members will give this event special consideration.

== Venue ==

The City of Vienna MA 14 gladly provides the location for the Vienna Code Sprint for up to 60 sprinters in [http://www.wien.gv.at/stadtplan/grafik.aspx?lang=de-AT&bookmark=zHClRv95TUbsTHFEFcAeRO5RphlRnHnkur2pH4Oprw-b-b&bmadr=25723751 their very new office called STAR 22] (see also [http://www.openstreetmap.org/?mlat=48.22910&mlon=16.45660#map=19/48.22910/16.45660 OSM map]).

The venue is not far from the center of Vienna (~25min via train and subway) and can be reached easily from the Vienna airport via train.

== Dates and Times ==

March 24-28 2014

Note: March 19-21 FOSSGIS Berlin

Duration: Full week

== Agenda ==

TBD

=== Project Plans ===

GRASS GIS Agenda: See http://grasswiki.osgeo.org/wiki/GRASS_Community_Sprint_Vienna_2014

== Hotel ==

Two blocks of rooms have been negotiated at the two hotels closest to the sprint venue, [http://www.hillinger.at Hotel Hillinger] ([http://www.openstreetmap.org/#map=19/48.23133/16.45037 map]) and [http://www.wienerkindl.at Hotel Wiener Kindl] ([http://www.openstreetmap.org/#map=19/48.22757/16.45428 map]). Please make your own choice.

The rooms are blocked for the sprint week i.e. 24.-28. March 2014 whereas +/- one day should be no problem.

Please find the lists of available rooms below. If you make a reservation for one of the listed rooms please indicate this by adding your name to the list. Thanks.

Don't hesitate to contact me if you need any assistance.

=== Hotel Wiener Kindl ===

{| style="border: solid grey 1px" class="sortable"
|+ Hotel-Wiener-Kindl
|-
| # Beds || Rate || # Rooms || Reservations || Notes
|-
| 1 || € 65,- || 3 || Martin Isenburg (willing to share room with 2 or 3 beds) ||
|-
| 2 || € 80,- || 6 || (Martin Dobias & Peter Wells), Even Rouault, (Anne and Stefano), (Richard Duivenvoorde (booked, offering to share) ||
|-
| 3 || € 90,- || 2 || ||
|}

The rates include breakfast buffet, sat TV, direct dial telephone, ensuite bathroom with shower, minibar, and free WLAN.

Cancellation policy:
* Free cancellation until 7 days in advance
* 50% fee later

These rooms are blocked until 28.02.2014. Please make your reservation via mail to "wienerkindl@utanet.at" and indicate that you're participating at the "OSGeo Vienna Code Sprint" in order to get a room of the block.

If you really want to save on budget you might consider a room with shared bathroom and sometimes also shared shower. Note that these rooms are available at the hotel as backup rooms but not recommended. You have been warned.

{| style="border: solid grey 1px" class="sortable"
|+ Hotel-Wiener-Kindl-low-budget
|-
| # Beds || Rate || # Rooms || Reservations || Notes
|-
| 1 || € 45,- || 3 || Radim Blazek ||
|-
| 2 || € 50,- || 2 || <add your name> ||
|}

=== Hotel Hillinger ===

'''Note, in case you've seen the previous note, that today I visited the hotel again and hopefully resolved all misunderstandings.'''

{| style="border: solid grey 1px" class="sortable"
|+ Hotel-Hillinger
|-
| # Beds || Rate || # Rooms || Reservations || Notes
|-
| 2 || € 85,- || 15 are blocked of up to 50 || <add your name> || Most of the rooms have double beds and some twin beds. Ask for your preferred choice.
|-
| 1 || € 65,- || Same as above but single use || <add your name> ||
|-
| 3 || € 105,- || 4 || <add your name> || 2 of the rooms can also be used as 4 bed rooms for € 125,-.
|}

The rates include breakfast buffet, cable and pay-TV, air conditioning, direct dial telephone, ensuite bathroom with bathtub or shower, hairdryer, and free WLAN in the whole hotel. In addition they offer free usage of the climbing hall and fitness center on the other side of the street.

Accepted payment methods: cash or creditcard.

Cancellation policy:
* Free cancellation until 7 days in advance
* 50% fee from 7 to 3 days in advance
* 100% fee later

These rooms are blocked until 15.02.2014. Please make your reservation via mail to "hotel@hillinger.at" and indicate that you're participating at the "OSGeo Vienna Code Sprint" in order to get a room of the block.

=== Alternatives ===

If you don't feel comfortable with both options we recommend to look for alternatives around Kagran ([http://www.openstreetmap.org/#map=15/48.2434/16.4341 map]) which is just a couple of stops away from the venue with the tram and also close to the city center with the subway.

== Costs ==

Participants should plan for the following costs:

* Travel to Vienna
* Accommodation for four nights
* Breakfast and dinner (partly)

== Communication ==

* Please join the mailing list: http://lists.osgeo.org/mailman/listinfo/tosprint
* IRC chat during the event: #tosprint Server: irc.freenode.net

== Participants ==

We are planning for attendance of 50-60 participants. Please add your name and the projects
you are hoping to sprint and note the likeliness of your attendance as well as
any special needs.

{| style="border: solid grey 1px; width:100%" class="sortable"
|+ Participants
|-
| # || Participant || Country || Arrival || Departure || Accomodation || Work on || Notes
|-
| 1 || [[User:schpidi|Stephan Meissl]] || AT || first day || last day || home || MapServer || Definite - No special needs
|-
| 2 || [[User:ahocevar|Andreas Hocevar]] || AT || first day || last day || family || OpenLayers || Definite - No hotel needed
|-
| 3 || [[User:pwramsey3|Paul Ramsey]] || CA || Mar 23 (AC6164) || Mar 30 (AC9159) || TBD || PostGIS || Booked
|-
| 4 || [[User:msmitherdc|Michael Smith]] || US || Mar 23 (BA0700 || Mar 30 (BA0701) || || PDAL/MapServer || Booked
|-
| 5 || [[Jeff McKenna]] || CA || Mar 26 (AC6158) || Mar 31 (AC6159) || || MapServer, ZOO-Project, pycsw || Booked
|-
| 6 || [[User:Dmorissette|Daniel Morissette]] || CA || Likely Mar 23 || Mar 31 || || MapServer, GDAL/OGR || Booked
|-
| 7 || [[User:hobu|Howard Butler]] || USA || Mar 22 || Mar 29 || || MapServer, GDAL/OGR, PDAL || Booked
|-
| 8 || Olivier Courtin || FR || || || || PostGIS, TinyOWS || Booked
|-
| 9 || [[User:Lucadelu|Luca Delucchi]] || IT || || || || GRASS GIS || Booked
|-
| 10 || [[User:Landa|Martin Landa]] || CZ || || || || GRASS GIS, PostGIS, GDAL/OGR || Very Likely
|-
| 11 || [[User:Tbonfort|Thomas Bonfort]] || FR || Mar 24 midday || Mar 28 || || MapServer || Definite
|-
| 12 || [[User:Szekerest|Tamas Szekeres]] || HU || Mar 24 midday || Mar 28 || Hillinger || MapServer, GDAL/OGR || Definite
|-
| 13 || [[User:Mloskot|Mateusz Loskot]] || || || || || PDAL || Likely
|-
| 14 || [[User:pcav|Paolo Cavallini]] || || || || || QGIS || Very likely
|-
| 15 || [[User:Neteler|Markus Neteler]] || IT || || || || GRASS GIS || Definite - No special needs
|-
| 16 || [[User:kalxas|Angelos Tzotsos]] || GR || Mar 23 (OS0802) || Mar 29 (OS0801) || TBD || OSGeoLive, pycsw/GeoPython/GeoNode, OTB, ZOO-Project || Booked
|-
| 17 || [[User:Aghisla|Anne Ghisla]] || DE || Mar 24 || Mar 28 || Wiener Kindl || GRASS GIS/QGIS/Translations || Definite
|-
| 18 || <strike>[[User:Jachym|Jachym Cepicky]]</strike> || || || || || <strike>PyWPS/GeoPython (OpenLayers)</strike> || <strike>Likely</strike> No :-(
|-
| 19 || [[User:Jesus|Jorge de Jesus]] || || || || || PyWPS/REST/GeoPython || Likely
|-
| 20 || Andreas Trawoeger || || || || || GRASS GIS || Definite - No special needs
|-
| 22 || [[User:pacesm| Martin Paces]] || || || || || EOxServer || Very Likely
|-
| 23 || [[User:fschindler| Fabian Schindler]] || || || || || EOxServer/MapServer || Definite
|-
| 24 || [[User:Djay|Gérald Fenoy]] || FR || Mar 23 (AF1738) || Mar 29 (AF7680) || TBD || MapServer, ZOO-Project || Booked
|-
| 25 || Marco Hugentobler || CH || Mar 24 (OS562) || Mar 28 (OS565) || Hillinger || QGIS || Booked
|-
| 26 || Mathias Walker || CH || Mar 24 (OS562) || Mar 28 (OS565) || Hillinger || QGIS || Booked
|-
| 27 || [[User:Pirmin_Kalberer|Pirmin Kalberer]] || CH ||Mar 24 (OS562) || Mar 28 (OS565) || Hillinger || QGIS, GDAL/OGR || Booked
|-
| 28 || [[User:capooti|Paolo Corti]] || || || || || GeoNode/QGIS || Booked
|-
| 29 || [[Arnulf Christl]] - [[OSGeo]], [[Geo for All]] || DE || || || || Guest ||
|-
| 30 || [[User:rduivenvoorde|Richard Duivenvoorde]] || NL || Mar 24 (KLM1845) || Mar 28 (KLM1848) || Hotel Wiener Kindl || QGIS, context help, vector tools || Booked
|-
| 31 || [[User:timlinux|Tim Sutton]] || || || || || QGIS || likely
|-
| 32 || [[User:mbernasocchi|Marco Bernasocchi]] || CH || || || || QGIS || Very likely
|-
| 33 || [[User:MartinDobias|Martin Dobias]] || SK || Mar 23 20:45 || Mar 28 20:45 || Hotel Wiener Kindl || QGIS || Booked
|-
| 34 || Hugo Mercier || FR || || || || QGIS, SFCGAL, PostGIS || Booked
|-
| 36 || [[User:hellik|Helmut Kudrnovsky]] || AT || || || || GRASS GIS || Likely
|-
| 37 || [[User:lutra|Giovanni Manghi]] || PT/IT || || || || QGIS || Likely
|-
| 38 || [[User:Ginetto|Luigi Pirelli]] || ES/IT ||24(VY8710) 14:30|| 30(VY8711) ||tbd || QGIS || Booked flight
|-
| 39 || [[Milena Nowotarska | Milena Nowotarska]] || PL || || || || GRASS GIS/QGIS || Likely
|-
| 40 || [[User:Madi|Margherita Di Leo]] || IT || 24 h11:50 || 28 h15:15 || [http://arnes-vienna.viennaaustrohotel.com/ Arnes Hotel] || GRASS GIS / INSPIRE || Booked
|-
| 41 || [[User:Macho|Werner Macho]] || AT || || || || QGIS || Likely
|-
| 42 || [[User:Vasile|Vasile Crăciunescu]] || RO || Mar 23 || Mar 28 || Hillinger || GRASS GIS / INSPIRE/ Open GeoData || Booked
|-
| 43 || Radim Blazek || CZ || Mar 24 || Mar 27 || Wiener Kindl || QGIS ||
|-
| 44 || [[User:lastools|Martin Isenburg]] || DE || Mar 24 (LH2324) || Mar 29 || Wiener Kindl || LiDAR in QGIS, LAStools toolbox, light-weight data base || Booked flight
|-
| 45 || [[User:Johanvdw|Johan Van de Wauw]] || BE || || || || SAGA - QGis processing, OSGeo live || Likely, probably not all days
|-
| 46 || [[User:neumann|Andreas Neumann]] || CH || Mar 24 08:30 || Mar 28 18:00 || Hotel Wiener Kindl || QGIS, QGIS Web Client || Booked
|-
| 47 || Denis Rouzaud || CH || tbd || tbd || tbd || QGIS || Very Likely
|-
| 48 || Peter Wells || UK || Mar 23 20:45 || Mar 28 20:45 || Hotel Wiener Kindl || QGIS || Booked
|-
| 49 || [[User:Jef|Jürgen Fischer]] || DE || 24(KLM1845) || 28(KLM1848) || Wiener Kindl || QGIS || booked
|-
| 50 || Yves Jacolin || FR || tbd || tbd || tbd || QGIS || Very Likely
|-
| 51 || Stéphane Brunner || CH || tbd || tbd || tbd || QGIS || Very Likely
|-
| 52 || Arnaud Morvan || FR || tbd || tbd || tbd || QGIS || Very Likely
|-
| 53 || [[User:elpaso|Alessandro Pasotti]] || IT || Mar 24 || Mar 28 || Wiener Kindl || QGIS, QGIS Web Client, QGIS Plugins repo || Booked
|-
| 54 || [[User:Rouault|Even Rouault]] || FR || Mar 24 || Mar 28 || Wiener Kindl || GDAL, MapServer, QGIS? || Booked
|-
| 55 || Rob Emanuele || US || tbd || tbd || tbd || GDAL || Likely
|-
| 56 || Stefano Cavallari || DE || Mar 24 || Mar 28 || Wiener Kindl || GRASS/QGIS, Python || Definite
|-
| 57 || Anita Graser || AT || tbd || tbd || home || QGIS || Definite
|-
| 58 || Kenny Shepard || US || Mar 24 || Mar 28 || AirBnB || GDAL || Booked flight
|-
| 59 || Rafael Krucker || CH || Mar 24 || Mar 28 || budget or youth hostel || QGIS || Booked
|-
| 60 || Tobias Schmitz || CH || Mar 24 || Mar 28 || budget or youth hostel || QGIS || Booked
|-
| 61 || [[User:Dodobas|Dražen Odobašić]] || HR || tbd || tbd || tbd || QGIS || Likely
|-
| 62 || Stepan Turek || CZ || tbd || tbd || tbd || GRASS || Likely
|-
| 63 || [[Borys Jurgiel|Borys Jurgiel]] || PL || tbd || tbd || tbd || QGIS || Likely
|-
| 64 || [[Nikos Alexandris|Nikos Alexandris]] || GR || tbd || tbd || tbd || GRASS GIS || Likely
|-
| 65 ||[[Ratko Vasiljević]] ||HR|| tbd || tbd || tbd || GRASS GIS, QGIS, ILWIS || Likely
|-
| 66 || Georg Ramler || AT || Mar 24 || Mar 27 || || pycsw, QGIS Plugins || Definite - No special needs
|-
| 67 || Jürgen Zornig || AT || Mar 24 || Mar 27 || || pycsw, QGIS Plugins || Definite - No special needs
|-
| 68 || Roberto Angeletti || IT || Mar 24 || Mar 28 || || 3D , QGIS Plugins || Likely
|-
| 69 || Stephan Bösch-Plepelits || AT
| colspan=2 | Mar 26, 28 (mornings) || home || [https://github.com/plepe/pgmapcss pgmapcss] (can it be used for MapServer?) || -
|}



== Individual Preparation ==

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

== FAQ ==

* Is the Vienna Code Sprint just a coding event?
** Yes, a coding and documentation event. It is a working session for people who are already participants in open source projects.
* Will it be possible to present new projects during this event?
** While this is not a presentation-oriented event like FOSS4G, there will be the possibility to have presentations. There are plans to get a dedicated room with beamer.

== Social Activities ==

=== Welcome party ===

In the evening of the first day of the sprint we will invite all sprinters to a big welcome party. More details shall not be revealed yet but we try to make it a memorable event.

=== Guided evening walk - "The City of Vienna at a glance" ===

On Wednesday evening we invite interested participants to a guided evening walk - "The City of Vienna at a glance". An on-site registration will be needed due to a limit number of 25 places.

The downtown tour introduces the imperial city, Vienna´s great history, its unique architecture, and todays life-style.

Meeting in front of St. Stephen´s Cathedral, Vienna’s main 900 years old landmark, we will stroll along Graben and Kohlmarkt, passing former court confectionary Demel and the most exclusive shops in Vienna. Crossing the courtyards of the Imperial Palace "Hofburg" you will hear about the great times of former Austrian monarchy, see where Empress Elizabeth (Sisi) married Emperor Franz Joseph, where the Vienna Boys’ Choir sings mass on Sunday, and where the famous white Lipizzaner stallions of the Spanish Riding School perform. You will enjoy the great view from Heroes Square to some of the magnificent buildings of the famous Ringstraße. We will continue walking towards State Opera and the legendary hotel Sacher and will end the tour at Albertinaplatz.

=== Skiing ===

We will leave Vienna early on Saturday to go to [http://openrouteservice.org/index.php?start=16.4564156,48.2295225&end=13.7795834,47.4114987&pref=Fastest&lang=de&noMotorways=false&noTollways=false Haus im Ennstal] for skiing. In the evening we will visit an [http://www.hauser-kaibling.at/de/events/events2014/open_air_2014.htm open air concert] and return on Sunday.

Please contact [[User:schpidi|Stephan Meissl]] if you're interested.

== Budget ==

TBD

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

Vienna Code Sprint 2014

2014-03-04T11:05:56Z

Wiki-Elpaso: /* Participants */

''OSGeo Code Sprint 2014 official web site: [http://vienna2014.sprint.osgeo.org http://vienna2014.sprint.osgeo.org]. Please contact us if you are interested in our [http://vienna2014.sprint.osgeo.org/sponsoring.html sponsorship opportunities].''

'''Gold Sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-Airborne-Interactive.png|260px|Airborne Interactive Ltd|link=http://www.airborne.aero/]]
 
http://www.airborne.aero/
|
[[File:Logo-Austrospace.png‎|260px|Austrospace|link=http://www.austrospace.at/]]
 
http://www.austrospace.at/
|
[[File:Logo-TYDAC.png‎|260px|TYDAC|link=http://www.tydac.ch]]
 
http://www.tydac.ch
|}

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

'''Silver Sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-ITS-VR.jpg|260px|ITS Vienna Region|link=http://www.anachb.at/mehr]]
 
http://www.anachb.at/mehr
|}

'''Bronze Sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-metaspatial.png|260px|metaspatial Institut|link=http://www.metaspatial.net/en/institute]]
 
[http://metaspatial.net/en/institute http://metaspatial.net/en/institute]
|
[[File:Logo-Oslandia.png|260px|Oslandia|link=http://www.oslandia.com]]
 
[http://www.oslandia.com http://www.oslandia.com]
|
[[File:Logo-rapidlasso.png|260px|rapidlasso|link=http://rapidlasso.com]]
 
[http://rapidlasso.com http://rapidlasso.com]
|}

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-Azavea.jpg‎|260px|Azavea|link=http://www.azavea.com]]
 
http://www.azavea.com
|}

'''Venue Sponsor'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-City-of-Vienna.png|260px|City of Vienna MA 14|link=http://www.wien.gv.at/english/administration/ict/index.html]]
 
[http://www.wien.gv.at/english/administration/ict/index.html http://www.wien.gv.at/]
|}

'''Other/in-kind sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-EOX.png|120px|EOX IT Services GmbH|link=http://eox.at]]
 
[http://eox.at http://eox.at]
|}

== Purpose ==

Get together project members to make decisions and tackle larger geospatial
problems (as done last year at the [[Boston Code Sprint 2013]] and previous
years: [[IslandWood Code Sprint 2012|Island Wood]] (2012),
[[Montreal Code Sprint 2011|Montreal]] (2011),
[[New York Code Sprint 2010|New York City]] (2010), and
[[Toronto Code Sprint 2009|Toronto]] (2009)). This code sprint is targeting
members of the "C Tribe" (e.g., MapServer, QGis, GRASS, GDAL, Proj, PostGIS,
MapGuide, OpenLayers). Other tribes are welcome to join the sprint, of course,
but we hope that "C Tribe" members will give this event special consideration.

== Venue ==

The City of Vienna MA 14 gladly provides the location for the Vienna Code Sprint for up to 60 sprinters in [http://www.wien.gv.at/stadtplan/grafik.aspx?lang=de-AT&bookmark=zHClRv95TUbsTHFEFcAeRO5RphlRnHnkur2pH4Oprw-b-b&bmadr=25723751 their very new office called STAR 22] (see also [http://www.openstreetmap.org/?mlat=48.22910&mlon=16.45660#map=19/48.22910/16.45660 OSM map]).

The venue is not far from the center of Vienna (~25min via train and subway) and can be reached easily from the Vienna airport via train.

== Dates and Times ==

March 24-28 2014

Note: March 19-21 FOSSGIS Berlin

Duration: Full week

== Agenda ==

TBD

=== Project Plans ===

GRASS GIS Agenda: See http://grasswiki.osgeo.org/wiki/GRASS_Community_Sprint_Vienna_2014

== Hotel ==

Two blocks of rooms have been negotiated at the two hotels closest to the sprint venue, [http://www.hillinger.at Hotel Hillinger] ([http://www.openstreetmap.org/#map=19/48.23133/16.45037 map]) and [http://www.wienerkindl.at Hotel Wiener Kindl] ([http://www.openstreetmap.org/#map=19/48.22757/16.45428 map]). Please make your own choice.

The rooms are blocked for the sprint week i.e. 24.-28. March 2014 whereas +/- one day should be no problem.

Please find the lists of available rooms below. If you make a reservation for one of the listed rooms please indicate this by adding your name to the list. Thanks.

Don't hesitate to contact me if you need any assistance.

=== Hotel Wiener Kindl ===

{| style="border: solid grey 1px" class="sortable"
|+ Hotel-Wiener-Kindl
|-
| # Beds || Rate || # Rooms || Reservations || Notes
|-
| 1 || € 65,- || 3 || Martin Isenburg (willing to share room with 2 or 3 beds) ||
|-
| 2 || € 80,- || 6 || (Martin Dobias & Peter Wells), Even Rouault, Dmitry Baryshnikov, (Anne and Stefano) ||
|-
| 3 || € 90,- || 2 || ||
|}

The rates include breakfast buffet, sat TV, direct dial telephone, ensuite bathroom with shower, minibar, and free WLAN.

Cancellation policy:
* Free cancellation until 7 days in advance
* 50% fee later

These rooms are blocked until 28.02.2014. Please make your reservation via mail to "wienerkindl@utanet.at" and indicate that you're participating at the "OSGeo Vienna Code Sprint" in order to get a room of the block.

If you really want to save on budget you might consider a room with shared bathroom and sometimes also shared shower. Note that these rooms are available at the hotel as backup rooms but not recommended. You have been warned.

{| style="border: solid grey 1px" class="sortable"
|+ Hotel-Wiener-Kindl-low-budget
|-
| # Beds || Rate || # Rooms || Reservations || Notes
|-
| 1 || € 45,- || 3 || Radim Blazek ||
|-
| 2 || € 50,- || 2 || <add your name> ||
|}

=== Hotel Hillinger ===

'''Note, in case you've seen the previous note, that today I visited the hotel again and hopefully resolved all misunderstandings.'''

{| style="border: solid grey 1px" class="sortable"
|+ Hotel-Hillinger
|-
| # Beds || Rate || # Rooms || Reservations || Notes
|-
| 2 || € 85,- || 15 are blocked of up to 50 || <add your name> || Most of the rooms have double beds and some twin beds. Ask for your preferred choice.
|-
| 1 || € 65,- || Same as above but single use || <add your name> ||
|-
| 3 || € 105,- || 4 || <add your name> || 2 of the rooms can also be used as 4 bed rooms for € 125,-.
|}

The rates include breakfast buffet, cable and pay-TV, air conditioning, direct dial telephone, ensuite bathroom with bathtub or shower, hairdryer, and free WLAN in the whole hotel. In addition they offer free usage of the climbing hall and fitness center on the other side of the street.

Accepted payment methods: cash or creditcard.

Cancellation policy:
* Free cancellation until 7 days in advance
* 50% fee from 7 to 3 days in advance
* 100% fee later

These rooms are blocked until 15.02.2014. Please make your reservation via mail to "hotel@hillinger.at" and indicate that you're participating at the "OSGeo Vienna Code Sprint" in order to get a room of the block.

=== Alternatives ===

If you don't feel comfortable with both options we recommend to look for alternatives around Kagran ([http://www.openstreetmap.org/#map=15/48.2434/16.4341 map]) which is just a couple of stops away from the venue with the tram and also close to the city center with the subway.

== Costs ==

Participants should plan for the following costs:

* Travel to Vienna
* Accommodation for four nights
* Breakfast and dinner (partly)

== Communication ==

* Please join the mailing list: http://lists.osgeo.org/mailman/listinfo/tosprint
* IRC chat during the event: #tosprint Server: irc.freenode.net

== Participants ==

We are planning for attendance of 50-60 participants. Please add your name and the projects
you are hoping to sprint and note the likeliness of your attendance as well as
any special needs.

{| style="border: solid grey 1px; width:100%" class="sortable"
|+ Participants
|-
| # || Participant || Country || Arrival || Departure || Accomodation || Work on || Notes
|-
| 1 || [[User:schpidi|Stephan Meissl]] || AT || first day || last day || home || MapServer || Definite - No special needs
|-
| 2 || [[User:ahocevar|Andreas Hocevar]] || AT || first day || last day || family || OpenLayers || Definite - No hotel needed
|-
| 3 || [[User:pwramsey3|Paul Ramsey]] || CA || Mar 23 (AC6164) || Mar 30 (AC9159) || TBD || PostGIS || Booked
|-
| 4 || [[User:msmitherdc|Michael Smith]] || || || || || PDAL/MapServer || Very Likely
|-
| 5 || [[Jeff McKenna]] || CA || Mar 26 (AC6158) || Mar 31 (AC6159) || || MapServer, ZOO-Project, pycsw || Booked
|-
| 6 || [[User:Dmorissette|Daniel Morissette]] || CA || Likely Mar 23 || Mar 31 || || MapServer, GDAL/OGR || Booked
|-
| 7 || [[User:hobu|Howard Butler]] || USA || Mar 22 || Mar 29 || || MapServer, GDAL/OGR, PDAL || Booked
|-
| 8 || Olivier Courtin || FR || || || || PostGIS, TinyOWS || Booked
|-
| 9 || [[User:Lucadelu|Luca Delucchi]] || IT || || || || GRASS GIS || Very Likely
|-
| 10 || [[User:Landa|Martin Landa]] || CZ || || || || GRASS GIS, PostGIS, GDAL/OGR || Very Likely
|-
| 11 || [[User:Tbonfort|Thomas Bonfort]] || FR || Mar 24 midday || Mar 28 || || MapServer || Definite
|-
| 12 || [[User:Szekerest|Tamas Szekeres]] || HU || Mar 24 midday || Mar 28 || || MapServer, GDAL/OGR || Definite
|-
| 13 || [[User:Mloskot|Mateusz Loskot]] || || || || || PDAL || Likely
|-
| 14 || [[User:pcav|Paolo Cavallini]] || || || || || QGIS || Very likely
|-
| 15 || [[User:Neteler|Markus Neteler]] || IT || || || || GRASS GIS || Definite - No special needs
|-
| 16 || [[User:kalxas|Angelos Tzotsos]] || GR || Mar 23 (OS0802) || Mar 29 (OS0801) || TBD || OSGeoLive, pycsw/GeoPython/GeoNode, OTB, ZOO-Project || Booked
|-
| 17 || [[User:Aghisla|Anne Ghisla]] || DE || Mar 24 || Mar 28 || Wiener Kindl || GRASS GIS/QGIS/Translations || Definite
|-
| 18 || [[User:Jachym|Jachym Cepicky]] || || || || || PyWPS/GeoPython (OpenLayers) || Likely
|-
| 19 || [[User:Jesus|Jorge de Jesus]] || || || || || PyWPS/REST/GeoPython || Likely
|-
| 20 || Andreas Trawoeger || || || || || GRASS GIS || Definite - No special needs
|-
| 22 || [[User:pacesm| Martin Paces]] || || || || || EOxServer || Very Likely
|-
| 23 || [[User:fschindler| Fabian Schindler]] || || || || || EOxServer/MapServer || Definite
|-
| 24 || [[User:Djay|Gérald Fenoy]] || FR || Mar 23 (AF1738) || Mar 29 (AF7680) || TBD || MapServer, ZOO-Project || Booked
|-
| 25 || Marco Hugentobler || CH || Mar 24 (OS562) || Mar 28 (OS565) || Hillinger || QGIS || Booked
|-
| 26 || Mathias Walker || CH || Mar 24 (OS562) || Mar 28 (OS565) || Hillinger || QGIS || Booked
|-
| 27 || [[User:Pirmin_Kalberer|Pirmin Kalberer]] || CH ||Mar 24 (OS562) || Mar 28 (OS565) || Hillinger || QGIS, GDAL/OGR || Booked
|-
| 28 || [[User:capooti|Paolo Corti]] || || || || || GeoNode/QGIS || Likely
|-
| 29 || [[Arnulf Christl]] - [[OSGeo]], [[Geo for All]] || DE || || || || Guest ||
|-
| 30 || [[User:rduivenvoorde|Richard Duivenvoorde]] || NL || tbd || tbd || tbd || QGIS, context help, vector tools || Very likely
|-
| 31 || [[User:timlinux|Tim Sutton]] || || || || || QGIS || likely
|-
| 32 || [[User:mbernasocchi|Marco Bernasocchi]] || CH || || || || QGIS || Very likely
|-
| 33 || [[User:MartinDobias|Martin Dobias]] || SK || Mar 23 20:45 || Mar 28 20:45 || Hotel Wiener Kindl || QGIS || Booked
|-
| 34 || Hugo Mercier || FR || || || || QGIS, SFCGAL, PostGIS || Booked
|-
| 36 || [[User:hellik|Helmut Kudrnovsky]] || AT || || || || GRASS GIS || Likely
|-
| 37 || [[User:lutra|Giovanni Manghi]] || PT/IT || || || || QGIS || Likely
|-
| 38 || [[User:Ginetto|Luigi Pirelli]] || ES/IT ||24(VY8710) 14:30|| 30(VY8711) ||tbd || QGIS || Booked flight
|-
| 39 || [[Milena Nowotarska | Milena Nowotarska]] || PL || || || || GRASS GIS/QGIS || Likely
|-
| 40 || [[User:Madi|Margherita Di Leo]] || IT || 24 h11:50 || 28 h15:15 || [http://arnes-vienna.viennaaustrohotel.com/ Arnes Hotel] || GRASS GIS / INSPIRE || Booked
|-
| 41 || [[User:Macho|Werner Macho]] || AT || || || || QGIS || Likely
|-
| 42 || [[User:Vasile|Vasile Crăciunescu]] || RO || || || || GRASS GIS / INSPIRE/ Open GeoData || Very Likely
|-
| 43 || Radim Blazek || CZ || Mar 24 || Mar 27 || Wiener Kindl || QGIS ||
|-
| 44 || [[User:lastools|Martin Isenburg]] || DE || Mar 24 (LH2324) || Mar 29 || Wiener Kindl || LiDAR in QGIS, LAStools toolbox, light-weight data base || Booked flight
|-
| 45 || [[User:Johanvdw|Johan Van de Wauw]] || BE || || || || SAGA - QGis processing, OSGeo live || Likely, probably not all days
|-
| 46 || [[User:neumann|Andreas Neumann]] || CH || Mar 24 08:30 || Mar 28 18:00 || Hotel Wiener Kindl || QGIS, QGIS Web Client || Booked
|-
| 47 || Denis Rouzaud || CH || tbd || tbd || tbd || QGIS || Very Likely
|-
| 48 || Peter Wells || UK || Mar 23 20:45 || Mar 28 20:45 || Hotel Wiener Kindl || QGIS || Booked
|-
| 49 || [[User:Jef|Jürgen Fischer]] || DE || 24(KLM1845) || 28(KLM1848) || Wiener Kindl || QGIS || booked
|-
| 50 || Yves Jacolin || FR || tbd || tbd || tbd || QGIS || Very Likely
|-
| 51 || Stéphane Brunner || CH || tbd || tbd || tbd || QGIS || Very Likely
|-
| 52 || Arnaud Morvan || FR || tbd || tbd || tbd || QGIS || Very Likely
|-
| 53 || [[User:elpaso|Alessandro Pasotti]] || IT || tbd || tbd || tbd || QGIS, QGIS Web Client, QGIS Plugins repo || Booked
|-
| 54 || [[User:Rouault|Even Rouault]] || FR || Mar 24 || Mar 28 || Wiener Kindl || GDAL, MapServer, QGIS? || Booked
|-
| 55 || Rob Emanuele || US || tbd || tbd || tbd || GDAL || Likely
|-
| 56 || Stefano Cavallari || DE || Mar 24 || Mar 28 || Wiener Kindl || GRASS/QGIS, Python || Definite
|-
| 57 || Anita Graser || AT || tbd || tbd || home || QGIS || Definite
|-
| 58 || Kenny Shepard || US || Mar 24 || Mar 28 || AirBnB || GDAL || Booked flight
|-
| 59 || Rafael Krucker || CH || Mar 24 || Mar 28 || budget or youth hostel || QGIS || Booked
|-
| 60 || Tobias Schmitz || CH || Mar 24 || Mar 28 || budget or youth hostel || QGIS || Booked
|-
| 61 || [[User:Dodobas|Dražen Odobašić]] || HR || tbd || tbd || tbd || QGIS || Likely
|-
| 62 || Stepan Turek || CZ || tbd || tbd || tbd || GRASS || Likely
|-
| 63 || [[Borys Jurgiel|Borys Jurgiel]] || PL || tbd || tbd || tbd || QGIS || Likely
|-
| 64 || [[Nikos Alexandris|Nikos Alexandris]] || GR || tbd || tbd || tbd || GRASS GIS || Likely
|-
| 65 ||[[Ratko Vasiljević]] ||HR|| tbd || tbd || tbd || GRASS GIS, QGIS, ILWIS || Likely
|-
| 66 ||[[User:Bishop|Dmitry Baryshnikov]] ||RU|| Mar 24 || Mar 28 || Hotel Wiener Kindl|| GDAL/OGR || Likely
|-
| 67 || Georg Ramler || AT || Mar 24 || Mar 27 || || pycsw, QGIS Plugins || Definite - No special needs
|-
| 68 || Jürgen Zornig || AT || Mar 24 || Mar 27 || || pycsw, QGIS Plugins || Definite - No special needs
|-
| 69 || Roberto Angeletti || IT || Mar 24 || Mar 28 || || 3D , QGIS Plugins || Likely
|-
|}



== Individual Preparation ==

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

== FAQ ==

* Is the Vienna Code Sprint just a coding event?
** Yes, a coding and documentation event. It is a working session for people who are already participants in open source projects.
* Will it be possible to present new projects during this event?
** While this is not a presentation-oriented event like FOSS4G, there will be the possibility to have presentations. There are plans to get a dedicated room with beamer.

== Social Activities ==

=== Welcome party ===

In the evening of the first day of the sprint we will invite all sprinters to a big welcome party. More details shall not be revealed yet but we try to make it a memorable event.

=== Guided evening walk - "The City of Vienna at a glance" ===

On Wednesday evening we invite interested participants to a guided evening walk - "The City of Vienna at a glance". An on-site registration will be needed due to a limit number of 25 places.

The downtown tour introduces the imperial city, Vienna´s great history, its unique architecture, and todays life-style.

Meeting in front of St. Stephen´s Cathedral, Vienna’s main 900 years old landmark, we will stroll along Graben and Kohlmarkt, passing former court confectionary Demel and the most exclusive shops in Vienna. Crossing the courtyards of the Imperial Palace "Hofburg" you will hear about the great times of former Austrian monarchy, see where Empress Elizabeth (Sisi) married Emperor Franz Joseph, where the Vienna Boys’ Choir sings mass on Sunday, and where the famous white Lipizzaner stallions of the Spanish Riding School perform. You will enjoy the great view from Heroes Square to some of the magnificent buildings of the famous Ringstraße. We will continue walking towards State Opera and the legendary hotel Sacher and will end the tour at Albertinaplatz.

=== Skiing ===

We will leave Vienna early on Saturday to go to [http://openrouteservice.org/index.php?start=16.4564156,48.2295225&end=13.7795834,47.4114987&pref=Fastest&lang=de&noMotorways=false&noTollways=false Haus im Ennstal] for skiing. In the evening we will visit an [http://www.hauser-kaibling.at/de/events/events2014/open_air_2014.htm open air concert] and return on Sunday.

Please contact [[User:schpidi|Stephan Meissl]] if you're interested.

== Budget ==

TBD

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

Vienna Code Sprint 2014

2014-01-13T09:38:53Z

Wiki-Elpaso:

AJAX WebMapping Project Request

2006-09-08T14:14:08Z

Wiki-Elpaso: /* foss4g2006 conference */

[https://mail.osgeo.org/servlets/SummarizeList?listName=webmap-discuss webmap-discuss list has been set up]

Motion "AJAX WebMapping" mailing list from Cameron Shorter by email:

== Description ==
What could be good is if we set up a ajax-mapping list which has
representatives from all the OS AJAX web mapping projects.

== Aims ==
On it we can discuss ideas on how to implement different functionality
with the long term aim that we develop a set of common libraries that we
all can use.

== OSGeo Projects ==
* mapbuilder
* mapbender
* ka-map (interested)
* worldkit (interested)
* OpenLayers (interested)
* [http://maps.civicactions.net/ CivicMaps] (another possible..)

After adoption (going throughthis incubator) the mailing list "AJAX WebMapping" would be part of the OSGeo project infrastructure (run by CollabNet). Alternatively, it could be set up as a list of an existing project, probably ka.map or MapBuilder, once they moved into osgeo.

==foss4g2006 conference==
At foss4g2006 in Lausanne all interested AJAX webMapping Projects are invited to participate at the conference on wednesday afternoon at 18:00 -> 20:00 (room not known yet).

Projects registering in the attendance list below will be invited to present for 10 minutes (depending on available time) their best features, their lacking features and wich features they would like to share with other projects.

After the presentation we'll start the debate: depending on presentation results we'll try to plan a medium term action to evaluate common needings and a long term action to develop a common framework.

'''Target public''' is intended to be AJAX web mapping '''developers'''.

Attendance:
* '''Ka-Map''' (Paul Spencer, Lorenzo Becchi, Andrea Cappugi)
* '''OpenLayers''' (Schuyler Erle)
* '''MapGuide Open Source''' (Robert Bray)
* '''Mapbuilder''' (Steven Ottens, Michael Adair)
* '''InterMap opensource''' (Stefano Giaccio, Jeroen Ticheler)
* '''MapStorer''' (Alessandro Pasotti)

== Discussion ==

[[Talk:AJAX_WebMapping_Project_Request]]