OSGeo - User contributions [en]

QGIS 2017 3rd User Conference and Developer Meeting budget

2017-04-11T21:12:50Z

Wiki-LeneFischer: Created page with "== QGIS 3rd User Conference and Developer Meeting budget == === Developer and User budget === * Most developers will pay travel expenses. Accommodation and food provided. *..."

== QGIS 3rd User Conference and Developer Meeting budget ==
=== Developer and User budget ===

* Most developers will pay travel expenses. Accommodation and food provided.
* Developers from distant countries will have the possibility to get travel payed.
* Users pays 120 $ for conference and initial workshops. This amount will cover the expenses for the Developers accommodation and food.
* Users pays for the extra workshops – this amount will cover the extra workshops expenses.

=== Financials ===
* Profit: We hope to get a ‘break even’ budget
* Request: We ask OSGEO to sponsor 3500 $ to this event - if budget fails, and there are too few money we hope OSGEO will cover 1500 $ in risk.

Basic Information
• Audience: 100-150 people are expected. 50 developers and 100 users
• Region: World wide event (location is Denmark)
• Projects: QGIS
• August 2.-11. 2017
• Primary Venue: Workshops, conference and hackfest
=== Budget in US $ ===
'''Expences '''
{| class="wikitable"
|-
! !! Price !! No. !! Total
|-
| Registration || 20 || 100 || 2000
|-
| Accomodation 60 pers. 8 days || 30 || 480 || 14400
|-
| Food || 20 || 480 || 9600
|-
| Workshops || || || 6000
|-
| Travel expences || || || 9000
|-
| Video recording || || || 2500
|-
| Total || || || 43500
|}

'''Income'''
{| class="wikitable"
|-
! !! Price !! No. !! Total
|-
| Workshops || 100 || 150 || 15000
|-
| Conference || 100 || 100 || 10000
|-
| Sponsor confirmed || || || 3500
|-
| Sponsor OSGEO || |||| 3500
|-
| Sponsor expected || 1500 || 7 || 10500
|-
| Total || || || 44000
|}

UnitedNations Committee

2016-09-10T12:48:19Z

Wiki-LeneFischer:

== Background ==
The OSGeo Board of Directors met with the UN GIS team at FOSS4G in Seoul, Korea in September 2015. The UN GIS team is very interested in having OSGeo "at the table". Mr. Kyoung-Soo Eom, chief of the UN Geospatial Information Section, has invited OSGeo to be part of a working group on Geospatial Information and Services for Disasters to support the UN migration to Open Source Geospatial software solutions.

===UN Open GIS initiative===
"... it is to identify and develop an Open Source GIS bundle that meets the requirements of UN operations, taking full advantage of the expertise of mission partners (partner nations, technology contributing countries, international organizations, academia, NGO’s, private sector). The strategic approach shall be developed with best and shared principles, standards and ownership, in a prioritized manner that addresses capability gaps and needs without duplicating efforts of other Member States or entities. The UN OpenGIS Initiative strategy shall collaboratively and cooperatively develop, validate, assess, migrate, and implement sound technical capabilities with all the appropriate documentation and training that in the end provides a united effort to improve the effectiveness and efficiency of utilizing Open Source GIS around the world."

== Goals ==

* Support the UN's member states and committees through:
** OSGeo's service providers
** the GeoForAll network
* Emphasize to the UN and its members the benefits of the stable OSGeo stack of projects
* Establish communication between the UN-GIS team and the OSGeo community.
* Foster the outreach activities of OSGeo

== Communication ==

* a new "UN" mailing list has been created, please subscribe at https://lists.osgeo.org/mailman/listinfo/un and add your name to the list of this committee members at the end of this page.

== Activities ==

===October 2015===
* OSGeo has formally expressed interest in joining the [[UN-GGIM-Working-Group]] on Geospatial Information and Services for Disasters
** this was discussed at OSGeo's [[Board_Meeting_2015-10-15]]
** the UN is looking for feedback on the working group's [http://wiki.osgeo.org/wiki/UN-GGIM-Working-Group#Draft_terms_of_reference_.28TOR.29 TOR draft]

===March 2016===
* OSGeo participated to a UNopenGIS initiative (Brindisi, Italy, 5-10th March 2016) meeting and where formally incorporated in the UN Open GIS initiative as member of the initiative technical committee.
* Call for "UN Training Material". The Material available here: https://wiki.osgeo.org/wiki/UNTraining

===April 2016===
* Birth of "Spiral 2: Capacity Building" Working Group under the direction of Maria Antonia Brovelli (OSGeo), Diego Gonzales Ferreiro (UN) and Juan Curtado (US South Command).
* Decision (taking into account UN exigencies) to start the training with QGIS, PostGIS, Geonode, Geoserver, OpenLayers
* Call for volunteers within GeoForAll for revising available tutorials related to QGIS, PostGIS, GeoNode, Geoserver, OpenLayers

===May - June - July 2016 ===
* Revision and discussions about QGIS, PostGIS and GeoNode tutorials. People contributing: Alberta Albertella, Gregory Giuliani,Scott Hatcher,Ivana Ivanova,Thomas Mueller, Rick Smith, Mike Pumphrey, Vivien Deparday, Ariel Núñez ,Paolo Corti,Francesco Stompanato, Dimitris Karakostis, Dilek Emanetoglu, Arun Kumar Muthusamy, Andres Felipe Poveda Sanchez, Stanly Shaji

===August 2016===
* UNopenGIS governance has been defined and OSGeo has been incorporated in it (Massimiliano Cannata and Maria Brovelli are member of the Strategic Board) and more OSGeo members is going to be incorporated in other governing committees.
* A logo contest has been set up and run by OSGeo to brand the initiative (see [[UN_OpenGIS_logo_contest]])

===September 2016===
* The 19th September 2016 the first UN virtual class of Spiral 2 will start their activity with GeoAcademy QGIS.The virtual class will work using the Beep Platform of Politecnico di Milano, as teaching platform. Tutors of this first course will be:
Thomas Mueller, Rick Smith and Youngok Kang. Alberta Albertella will help in accessing and using the platform (for sharing material, upload files, homework, webconference, blog, etc)

Four editions of this course will be issued for a total of 72 GIS experts of Operational Field (Peacekeeping Actions) of UN.
The courses will be:
19 September - 18 October 2016
19 October - 18 November 2016
19 November - 19 December 2016
9 January - 8 February 2017

Volunteers who will be involved are:
Thomas Mueller, Rick Smith, Youngok Kang, Lene Fischer and Kurt Menke.
Volunteers who will be activated if needed:
Darshana Rawal, Ivana Ivanova, Adeymo Ayodele Oba

===November 2016===
* Second UN openGIS initiative workshops will be held in Seoul 7-11 November

== Committee Meetings ==

; Next meeting:
* planned for November 2016, date and time to be decided

; Previous meetings:
* [[UN Meeting 2015-11-17]] 16.00 UTC

== Chairs ==
* [[User:Maxi71|Massimiliano_Cannata]]
* [[User:maria|Maria Antonia Brovelli]]

== Members ==
* [[Jeff McKenna]]
* [[Jochen Albrecht]]
* [[Bob Basques]]
* [[Massimiliano_Cannata]]
* [[User:Ticheler|Jeroen Ticheler]]
* [[Micha Silver]]
* [[User:GodwinYeboah|Godwin Yeboah]]
* [[User:Assefa|Yewondwossen Assefa]]
* [[User:Nikos|Nikos Alexandris]]
* [[User:AndrewTurner|Andrew Turner]]
* [[Venkatesh Raghavan]]
* [[User:Djay|Gérald Fenoy]]
* [[User:Pmooney|Peter MOONEY]]
* [[User:13scoter|Scott Hatcher]]
* [[User:kotzino|Dimitris Kotzinos]]
* [[User:ElaWoloszynska|Ela Wołoszyńska-Wiśniewska]]
* [[User:Jachym|Jachym Cepicky]]
* [[User:endofcap|Sanghee Shin]]
* [[User:Giulianoramat|Giuliano Ramat]]
* [[User:Gregory.giuliani|Gregory Giuliani]]
* [[User:Till Adams|Till Adams]]
* [[Tanya Haddad]]
* [[User:Maria gridw|Maria Andrzejewska]]
* [[User:rburhum|Ragi Y. Burhum (OSGeo - California / OSGeo Perú)]]
* [[User:darkblue_b|Brian M Hamlin]]
* [[User:Danielkastl|Daniel Kastl]]
* [[User:WernerLeyh|Werner Leyh]]
* [[User:Bruce.bannerman|Bruce Bannerman]]
* [[User:Ortelius|Jeffrey Johnson]]
* [[User:pnaciona|Pericles Nacionales]]
* [[User:Novacite|Junyoung Choi]]
* [[User:dirkf|Dirk Frigne]]
* [[User:pierzen|Pierre Béland]]
* [[User:maria|Maria Antonia Brovelli]]
* [[User:Mikel|Mikel Maron]]
* [[User:Rickasmith|Rick Smith]]
* [[User:Serenacoetzee|Serena Coetzee]]
* [[User:LeneFischer|Lene Fischer]]
* ''add your name''

[[Category:UnitedNations]]
[[Category:Committees]]

FOSS4G 2016 Code Sprint

2016-07-21T11:12:04Z

Wiki-LeneFischer: /* Registered Attendees */

== CodeSprint ==

Venue: Bonn, Germany

This year, once again, we are following the old tradition of hosting a codesprint on the FOSS4G. More precisely, we offer a setting so that individual projects can meet for their codesprint. Since projects benefit from each other as well, the codesprint will naturally be held conjointly at one place.
Unfortunately, circumstances have forced us to divide the codesprint timetable-wise.

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

'''The first part''' is scheduled to take place directly before the conference, the second immediately after. The first two and a half days start on Sunday, August 21, 2016 at around noon and are scheduled to end on Tuesday, August 23, 2016 (open end). The '''second part''' starts in the morning of Saturday, August 27, 2016 and ends on Sunday at 12 pm.

[[Image:Basecamp2.png|200px|thumb|right]]
[[Image:Basecamp3.png|200px|thumb|right]]

We are happy to have found a really '''awesome location''' for you. Codesprint and accommodations are combined in one hall. Check out http://www.basecamp-bonn.com/ for details about the venue.
Working zones will be created for you in the breakfast area and hallways. There’s the option of finding relatively inexpensive sleeping accommodations in train sleeping cars, camping buses, classic cars and more. Additionally, an outdoor area is available for you to enjoy Bonn’s summer weather in August, while working. Healthy and not-so-healthy catering of drinks and snacks will be provided by us. Participation in codesprint is free of charge. However, overnight stays will have to be reserved and paid for by you.

[[Image:Basecamp4.png|200px|thumb|right]]

Another hint: the BaseCamp is within '''walking distance from the conference venue''' (WCCB) and has good access to public transportation – the Icebreaker takes place here, too.
You see, it’s worthwhile booking here!

As the accommodations are available to all FOSS4G participants, we will make an effort to make advance booking possible for you a few days ahead, to ensure you have the opportunity to sleep on-site and wrap up the evenings jointly. For that, it’s necessary for you to sign up (https://wiki.osgeo.org/wiki/FOSS4G_2016_Code_Sprint) and leave your email address so that we can contact you immediately accomodation booking is available. We need your sign-up for the planning of snacks and drinks, too!

This is open to all who wish to participate in one or more projects. There’s always plenty to do – it’s not all about programming. Translation, documentation, feedback, discussions, testing – all this is also important for project so everyone is cordially invited to attend the codesprints! Registration with the conference is not a prerequisite for participation in codesprint.

One thing we’d like to ask you: with an approx. 120 participants anticipated, the WLAN capacity will naturally be exhausted at some point. Please be sure to avoid huge on-site downloads of data, as this could impact the work of others. Thank you!

The Codesprint Organizing Team is looking forward to your coming!

'''In summary:'''

'''When:'''
* Part I: Sun 2016-08-21 12:00 noon - Tue 2016-08-23 (open end)
* Part II: Sat 2016-08-27 - Sun 2016-08-28 12:00 noon

'''Where:'''
* Venue & Accommodation: BaseCamp. (For more informations: http://www.basecamp-bonn.com/) [[http://www.openstreetmap.org/way/44335958#map=18/50.70763/7.12316| OpenStreetMap]]
* Nearby Hotel: Bonnox (http://www.bonnox.de/en/)

'''Questions/Comments/Ideas'''

* If you have questions/comments/ideas please let us know. Send an email to codesprint@foss4g2016.org. You are welcome!

== Sponsors ==
Thanks to our great sponsors!

[[File:FOSSGIS_OSGeo_DACH.png]]

== Registered Attendees ==

The Code Sprint does not cost any money. For us it makes planning easier if we know who is coming. So please leave your Name and mark the days you will come.

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|No
!width="250"|Name
!width="250"|Email
!width="250"|Projects
!width="30"|sun
!width="30"|mon
!width="30"|tue
!width="30"|sat
!width="30"|sun
!width="60"|Accomodation
!width="30"|vegetarian food
|-
| 1 ||[[User:Astrid Emde|Astrid Emde]] || astrid_emde@osgeo.org || [[Mapbender]] & Organization || x || x || x || x || x || other || x
|-
| 2 ||[[User:rcoup|Rob Coup]] || robert@coup.net.nz || [[GDAL]], [[GeoServer]] || - || x || x || - || - || Basecamp ||
|-
| 3 ||[[User:alfonx|Stefan Tzeggai]] || tzeggai@wikisquare.de || || - || - || x || x || - || Basecamp? ||
|-
| 4 ||[[User:Neteler|Markus Neteler]] || neteler@osgeo.org || [[GRASS GIS]] || x || x || x || x || x || other || x
|-
| 5 ||[[User:pcav|Paolo Cavallini]] || cavallini@faunalia.it || [[QGIS]] || x || x || x || x || x || Basecamp? ||
|-
| 6 ||[[User:Pirmin_Kalberer|Pirmin Kalberer]] || pka [ät] sourcepole.ch || [[QGIS]], [[GDAL]] || x || x || x || - || - || Basecamp ||
|-
| 7 ||[[User:neumann|Andreas Neumann]] || andreas [ät] qgis.org || [[QGIS]] || x || x || x || x || - || Basecamp ||
|-
| 8 ||[[User:timlinux|Tim Sutton]] || tim [ät] qgis.org || [[QGIS]] || x || x || x || x || - || Basecamp || yes
|-
| 9 ||[[User:Lucadelu|Luca Delucchi]] || lucadeluge @ gmail.com || [[GRASS GIS]] || x || x || x || x || x || Basecamp ||
|-
| 10 ||[[User:Schpidi|Stephan Meißl]]||stephan [ät] meissl.name||MapServer, EOxServer||?||?||x||-||-||Basecamp||
|-
| 11 ||[[User:lastools|Martin Isenburg]] || martin near rapidlasso.com || LASzip for LAS 1.4 || x || x || x || x || x || Basecamp ||
|-
| 12 || [[User:jgrocha|Jorge Gustavo Rocha]] || jgr@di.uminho.pt || GeoExt 3 || x || x || x || x || x || Basecamp ||
|-
| 13 || [[User:alexbruy|Alex Bruy]] || alexander.bruy at gmail.com || [[QGIS]] || x || x || x || - || - || Basecamp? ||
|-
| 14 || [[User:volaya|Victor Olaya]] || volayaf at gmail.com || [[QGIS]] || x || x || x || - || - || Basecamp? ||
|-
| 15 || [[bartvde2|Bart van den Eijnden]] || bartvde at osgis.nl || [[OpenLayers]] || - || x || x || - || - || Other ||
|-
| 16 || [[User:anitagraser|Anita Graser]] || anitagraser [ät] gmx.at || [[QGIS]] || - || x || x || - || -|| Basecamp ||
|-
| 17 ||[[User:Dmorissette|Daniel Morissette]]||dmorissette at mapgears.com||MapServer, GDAL/OGR||?||?||x||x||?||Basecamp||
|-
| 18 ||[[User:Stranger | Andreas Schmitz]] || hwbllmnn@mailbox.org || Mapbender || || || || || || other ||
|-
| 19 ||[[User:Uli | Uli Rothstein]] || || Mapbender || || || || || || other ||
|-
| 20 ||[[User:Tbonfort|Thomas Bonfort]]||thomas.bonfort@gmail.com||MapServer||?||?||x||x||?||Basecamp||
|-
| 21 ||[[User:Martinl|Martin Landa]] || || [[GRASS GIS]], [[GDAL]], [[QGIS]], [[PyWPS]], GIS.lab || x || x || x || x || x|| Basecamp? ||
|-
| 22 ||[[User:jachym|Jáchym Čepický]] || jachym.cepicky at gmail || [[PyWPS]], GIS.lab || x || x || x || x || x|| Basecamp ||
|-
| 23 ||[[User:Jonaseberle|Jonas Eberle]] || jonas.eberle at gmx.de || [[PyWPS]] || x || x || x || x || x || Basecamp/other? ||
|-
| 24 ||[[User:dassau|Otto Dassau]] ||otto at qgis.org || [[QGIS]] || x || x || x || - || - || other || yes
|-
| 25 ||[[User:rouault|Even Rouault]]||even.rouault @ spatialys.com||GDAL, MapServer, QGIS||-||x||x||x||-||Basecamp||
|-
| 26 ||[[User:grizonnetm|Manuel Grizonnet]]||manuel.grizonnet @ cnes.fr||OTB, OSGeo-Live, QGIS||x||x||x||-||-||Basecamp||
|-
| 27 ||[[User:mlennert|Moritz Lennert]]||mlennert at club worldonline be||GRASS GIS||x||x||x||-||-||Other||
|-
| 28 ||Verena Diewald || || Mapbender || || || || || || other ||
|-
| 29 ||Andriy Oblivantsev || || Mapbender || || || || || || other ||
|-
| 30 ||Axel Schaefer || || Mapbender || || || || || || other ||
|-
| 31 || David Patzke || || Mapbender || || || || || || other ||
|-
| 32 || Thekla Wirkus || || Mapbender || || || || || || other ||
|-
| 33 || Charly Toma || || Mapbender || || || || || || other ||
|-
| 34 ||[[User:Lads|Luís de Sousa]] ||luis de sousa @ protonmail ch || [[PyWPS]] || ? || x || x || x || ? || Basecamp? ||
|-
| 35 ||[[User:ajolma|Ari Jolma]]||ari.jolma @ gm/* Registered Attendees */ ail.com||GDAL, MapServer, QGIS||?||?||x||x||?||Beethoven||
|-
| 36 ||[[User:magicgate|Jakob Miksch]]||jakob.miksch [ät] posteo.eu||OSGeo-Live||x||?||?||x||x||Basecamp||
|-
| 37 ||[[User:Yjacolin|yjacolin]] ([[User talk:Yjacolin|talk]]) || yves dot jacolin [at] camptocamp.com ||QGIS||x||x||x|| || ||Bonnox||
|-
| 38 || Arnaud Morvan ||arnaud dot morvan @ camptocamp.com||QGIS||x||x||x|| || ||Bonnox||
|-
| 39 || Stéphane Brunner || stephane dot brunner [at] camptocamp.com || QGIS || x || x || x || || || Other ||
|-
| 40 || [[User:asgerskovbopetersen|Asger Skovbo Petersen]] || asger ãt septima.dk || QGIS || - || x || x || - || - || Other ||
|-
| 41 ||[[User:Tudorbarascu|Tudor Bărăscu ]] || tudor dot barascu [at] qtibia.ro || [[QGIS]] || x || x || x || x || x || Basecamp? ||
|-
| 42 ||[[User:moovida|Andrea Antonello ]] || andrea dot antonello [at] gmail dot com || gvSIG || - || - || x || - || - || other ||
|-
| 43 ||[[User:Silli|Silvia Franceschi ]] || silvia dot franceschi [at] gmail dot com || gvSIG || - || - || x || - || - || other ||
|-
| 44 || [[User:Guychisholm|Guy Chisholm]] || guy.chisholm at geoplace dot co dot uk || [[GeoServer]], [[OpenLayers]] || x || ? || ? || x || x || Basecamp ||
|-
| 45 || [[User:Remanuele|Rob Emanuele]] || remanuele at azavea dot com || [[GDAL]], [[JTS]], [[Proj4j]], [[GeoTrellis]], [[GeoTools]] || x || x || x || ? || ? || other ||
|-
| 46 || [[User:theduckylittle|Dan Little]] || dan.little at dbspatial dot com || [[GeoMoose]] || - || - || - || x || ? || other ||
|-
| 47 || [[User:IvanSanchez|Iván Sánchez Ortega]] || ivan sanchezortega.es || Leaflet || ? || - || - || ? || ? || TODO ||
|-
| 48 || [[User:Marcjansen|Marc Jansen]] || jansen [at] terrestris [dot] de || [[OpenLayers]] || x || x || x || x || x || Other ||
|-
| 49 || [[User:Thomas Baschetti|Thomas Baschetti]] || || || - || x || x || - || - || other || preferred
|-
| 50 || [[User:JulienSam|Julien-Samuel Lacroix]] || jlacroix at mapgears dot com || [[MapServer]], [[OpenLayers]] || x || x || x || x || - || other ||
|-
| 51 || Rasťo Micanik || rastomicanik at gmail dot com || GIS.lab || x || x || x || x || x|| Basecamp || yes
|-
| 52 || [[User:ianturton|Ian Turton]] || ijturton at gmail dot com || [[GeoTools]], [[GeoServer]] || - || - || x || x || x|| Other || No
|-
| 53 || [[User:aaime|Andrea Aime]] || andrea dot aime at gmail dot com || [[GeoTools]], [[GeoServer]] || x || x || - || - || -|| Other || No
|-
| 54 || [[User:connormanning|Connor Manning]] || connor at hobu dot co || Entwine PDAL || - || - || x || x || x|| Other || No
|-
| 55 || [[User:Tulau|Tuure Laurinolli]] || tuure dot laurinolli at vaisala dot com || [[GeoTools]], [[GeoServer]], [[OpenLayers]] || x || x || x || - || - || Other ||
|-
| 56 || [[User:Tkardi|Tõnis Lärdi]] || tonis.kardi@kemit.ee || || ? || x || x || x || ? || Basecamp ||
|-
| 57 || [[User:Maxi71 | Massimiliano Cannata]] || massimiliano dot cannata at supsi dot ch || [[istSOS]] || - || x || - || - || - || Other ||
|-
| 58 || [[User:mantonovic | Milan Antonovic]] || milan dot antonovic at supsi dot ch || [[istSOS]] || - || x || - || - || - || Other ||
|-
| 59 || Mirko Cardoso || mirko dot cardoso at supsi dot ch || [[istSOS]] || - || x || - || - || - || Other ||
|-
| 60 || Patrick Valsecchi || patrick dot valsecchi at camptocamp dot com || QGIS || x || x || x || || || Other ||
|-
| 61 || || || || x || x || x || || || Other ||
|-
| 62 || [[User:Veroandreo | Veronica Andreo]] || veroandreo@gmail.com || GRASS GIS || - || - || - || x || x || Basecamp ||
|-
| 63 || [[User:ksmith | Kevin Smith]] || smithkm at draconic dot ca || [[GeoServer]], [[GeoWebCache]], [[GeoTools]] || late || wkshp || x || x || x || ||
|-
| 64 || [[User:Ciupava | Anna Zanchetta]] || ciupava[at]gmail[dot]com || GRASS GIS || - || x || x || - || - || Basecamp ||
|-
| 65 || [[User:tbarsballe | Torben Barsballe]] || tbarsballe at boundlessgeo dot com || [[GeoServer]], [[GeoTools]] || - || - || - || x || - || ||
|-
| 66 || Jon Moules || || GeoServer, QGIS || - || ? || ? || x || x || Other || Vegan
|-
| 67 || Torsten Friebe || friebe AT lat-lon DOT de || deegree || x || ? || ? || x || x || Other ||
|-
| 68 || [[User:Borysiasty | Borys Jurgiel]] || info at borysjurgiel dot pl || QGIS || x || x || x || - || - || tbd || preferred
|-
| 69 || [[User:Jive | Jody Garnett]] || jody.garnett@gmail.com || GeoServer, GeoTools, Incubation, uDig || x || ? || ? || x || x || || No
|-
| 70 || [[User:rduivenvoorde | Richard Duivenvoorde]] || richard ta qgis.org || QGIS, GeoServer || x || x || x || - || - || ||
|-
| 71 || [[User:ahocevar | Andreas Hocevar]] || andreas.hocevar ta gmail.com || OpenLayers || - || x || x || - || - || ||
|-
| 72 || [[User:GeoFootballer | Christian Mayer]] || chris ta meggsimum.de || [[GeoExt]], [[OpenLayers]] || - || x || x || x || - || ||
|-
| 73 || [[User:FxKu | Felix Kunde]] || fkunde[at]beuth-hoschschule.de || 3DCityDB, pgMemento || - || x || x || - || - || other ||
|-
| 74 || [[User:Jesus | Jorge S. Mendes de Jesus]] || jorge.mendesdejesus[at]wur.nl || PyWPS || x || x || x || - || - ||BaseCamp || NO
|-
| 75 || [[User:mhugo | Hugo Mercier]] || hugo dot mercier at oslandia dot com || QGIS || ? || x || x || - || - || ? || no preference
|-
| 76 || [[User:sarasafavi | Sara Safavi]] || ssafavi at boundlessgeo dot com || GeoNode || x || x || x || - || - || Other ||
|-
| 77 || [[User:Lars | lars lingner]] || lars at lingner dot eu || MapServer || - || - || - || x || x || Other || no preference
|-
| 78 || [[User:Mkuhn | Matthias Kuhn]] || matthias@opengis.ch || QGIS || x || x || x || - || - || Other || no preference
|-
| 79 || [[User:LeneFischer | Lene Fischer]] || lfi@ign.ku.dk || QGIS || x || x || x || - || - || Other || no preference
|-
| 78 || [[User:bvthomsen3 | Bo Victor Thomsen]] || bvtho@frederikssund.dk || QGIS || x || x || x || - || - || Other || no preference
|-
|}

= Workgroups =

== Mapbender ==

'''Attending:'''

* [[User:Astrid Emde|Astrid Emde]]
* [[User:Stranger | Andreas Schmitz]]
* [[User:Uli | Uli Rothstein]]
* Axel Schaefer
* David Patzke
* Andriy Oblivantsev
* Verena Diewald
* Charly Toma
* Thekla Wirkus

'''Goals:'''
* modularisation
* tests
* documentation
* & more

== GRASS GIS ==

'''Attending:'''

* [[User:Neteler|Markus Neteler]]
* [[User:Lucadelu|Luca Delucchi]]
* [[User:Martinl|Martin Landa]]
* [[User:mlennert|Moritz Lennert]]

'''Goals:'''

* planning towards GRASS GIS 8
* integrating GSoC results

== QGIS ==

'''Attending:'''

* [[User:pcav|Paolo Cavallini]]
* [[User:Pirmin_Kalberer|Pirmin Kalberer]]
* [[User:neumann|Andreas Neumann]]
* [[User:volaya|Victor Olaya]]
* [[User:alexbruy|Alex Bruy]]
* [[User:anitagraser|Anita Graser]]
* [[User:dassau|Otto Dassau]]
* [[User:Yjacolin|yjacolin]]
* Arnaud Morvan
* [[User:Tudorbarascu|Tudor Bărăscu]]
* Stéphane Brunner
* Patrick Valsecchi
* [[User:Borysiasty|Borys Jurgiel]]
* [[User:rduivenvoorde|Richard Duivenvoorde]]
* Hugo Mercier

'''Goals:'''

* working on QGIS 3.0
* porting plugins to Python 3
* Working on QWC II
* Working on QGIS Processing framework
* Working on Documentation (release 2.16, [https://github.com/qgis/QGIS-Documentation/wiki/hackfest_Bonn_2016 discussion])

== PyWPS ==

'''Attending:'''

* [[User:jachym|Jachym Cepicky]]
* [[User:Jonaseberle|Jonas Eberle]]
* [[User:Lads|Luís de Sousa]]

'''Goals:'''

* What is needed for PyWPS-4
* Discuss new steps
* WPS 2.0.0 start

== GIS.lab ==

'''Attending:'''

* [[User:martinl|Martin Landa]]
* [[User:jachym|Jachym Cepicky]]
* Rasťo Mičánik

'''Goals:'''

* GIS.lab 1.0
* GIS.lab QGIS Plugin
* new generation of GIS.lab Web Client
* WPS Processing

== OSGeo-Live ==

'''Attending:'''

*[[User: Astrid Emde]]
* [[User:grizonnetm|Manuel Grizonnet]]

'''Goals:'''

* next version
* documentation
* translation

== GeoMoose ==

'''Attending:'''

* [[User:theduckylittle|Dan "Ducky" Little]]

''Goals:'''

* 3.0 release!

== ORFEO ToolBox ==

'''Attending:'''

* [[User:grizonnetm|Manuel Grizonnet]]

''Goals:'''

* Documentation
* QGIS/OTB compatibility
* Bugs

== gvSIG ==

'''Attending:'''

* [[User:moovida|Andrea Antonello]]
* [[User:Silli|Silvia Franceschi]]

''Goals:'''

* Developer Documentation
* JGrasstools integration
* Geopaparazzi integration
* Bug fixes

== GeoTools/GeoServer ==

Focused on Saturday/Sunday activities, seeking collaboration with QGIS project on SLD export story.

'''Attending:'''

* [[User:ianturton|Ian Turton]]
* [[User:aaime|Andrea Aime]]
* [[User:ksmith|Kevin Smith]]
* [[User:jive|Jody Garnett]]
* [[User:tbarsballe|Torben Barsballe]]
* Tyler Battle
* Gabriel Roland
* Jon Moules

'''Goals:'''

* QGIS SLD Export story
* Bug fixes
* fun!

== istSOS ==

'''Attending:'''

* [[User:Maxi71 | Massimiliano Cannata]]
* [[User:mantonovic | Milan Antonovic]]
* [[User:jive | Jody Garnett]] (Sunday only)
* Mirko Cardoso

'''Goals:'''

* OSGeo Incubation, what's next?

== deegree ==

http://www.deegree.org/

'''Attending:'''

*Torsten Friebe

'''Goals:'''

* Finalize 3.4, bug-fixing, documentation
* improved interface for [http://www.esdi-community.eu/projects/hale HALE]
* prepare official docker image for deegree 3.4

== OpenLayers ==

http://openlayers.org/

'''Attending:'''

* Bart van den Eijnden
* Andreas Hocevar

'''Goals:'''

* Implement restricted extent ([https://github.com/openlayers/ol3/pull/2777 #2777])

[[Category:FOSS4G2016]] [[Category:FOSS4G]] [[Category:Code_Sprints]]

LIDAR Format Letter

2015-04-13T17:57:27Z

Wiki-LeneFischer: /* Signed */

=Open Letter for 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 concern since the fragmentation of the LAS format will lead to reduced 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 sponsors of OGC help to 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 hurdle 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.

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

==Proprietary "Optimized LAS" format from ESRI==
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.

==OGCs efforts so far to enable Open standards in LiDAR ==

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 "Optimized LAS"==

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

: '''Summary:'''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=Value of Standards=

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

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

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

=Further Reading=

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

=References=

<references />

LIDAR Format Letter

2015-04-13T17:52:49Z

Wiki-LeneFischer: /* Signed */

=Open Letter for 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 concern since the fragmentation of the LAS format will lead to reduced 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 sponsors of OGC help to 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 hurdle 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 http://ign.ku.dk/ .

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

==Proprietary "Optimized LAS" format from ESRI==
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.

==OGCs efforts so far to enable Open standards in LiDAR ==

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 "Optimized LAS"==

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

: '''Summary:'''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=Value of Standards=

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

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

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

=Further Reading=

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

=References=

<references />

Board Meeting 2015-04-09

2015-04-08T21:03:41Z

Wiki-LeneFischer: /* Current items */

This board meeting is '''scheduled for the 9th of April 2015''' at [http://www.timeanddate.com/worldclock/fixedtime.html?year=2015&month=4&day=9&hour=15&min=0&sec=0%2015.00UTC 15.00 UTC] through IRC and follow up voting by email.

== Agenda ==

=== Current items ===

Items in italic are recurring at each meeting.

Move items from past meetings, or add new items, at will. Note that the discussion is limited to 1 hour.

* ''roll call''
* ''appoint meeting chair, meeting scribe/secretary''
* ''Review and approve past minutes: [[Board Meeting 2015-03-05]]''
* ''brief treasurer report''
* "Geo for All" Student Awards request for seed funding (4k USD) ([http://wiki.osgeo.org/wiki/Ica-osgeo-isprs_award award wiki])
* An [http://wiki.osgeo.org/wiki/LIDAR_Format_Letter Open Letter] is being drafted requesting OGC/OGC Sponsors/ESRI back Open LiDAR standards. This letter should be ready to present within a week or two, ~ 20 April 2015. Request that the OSGeo Board officially endorse and present this letter once complete (as was done for the [http://wiki.osgeo.org/wiki/Geoservices_REST_API GeoServicesREST API letter]). Contacts: Suchith Anand, Martin Isenburg, Cameron Shorter.
* Proposing a [[Diversity]] statement for the Foundation
* FOSS4G 2015 update
* FOSS4G 2016 update
* Request for funding OSGeo President's travel to enable expanding strategic level initiatives between OSGeo and ICA at ICC 2015 and SDI-Open 2015 ([http://lists.osgeo.org/pipermail/ica-osgeo-labs/2015-April/001447.html GeoforAll request])
* Request for [http://wiki.osgeo.org/wiki/Uva_letter_of_support letter of support] for Jan Hartmann (University of Amsterdam) - Dutch historical GIS based on the first cadastre of the Netherlands (1832)
* Request for Funding QGIS Codesprint/ Developers meeting in Denmark May 2015 - for Lene Fischer (University of Copenhagen)
* add your items here..

=== Items from past meetings ===
* Beginning plans for a 2015 budget (similar to [[OSGeo Budget 2014]])
** Dealing with SAC/systems issues ([[Outstanding SAC Issues 2014]])
* Updating/Recording accurate [http://www.osgeo.org/content/foundation/board_and_officers.html foundation officers]
** Website committee chair not active (according to the chair)
** Geodata committee not actively used (according to the chair)
** Marketing committee without a chair
* Updating/Recording accurate [http://www.osgeo.org/content/chapters/index.html local chapters]
* Agree on 5-level project evaluation as proposed by Cameron [http://lists.osgeo.org/pipermail/board/2014-September/012188.html]
* OSGeo is now a registered 'organization' with OGC, and goal is to have all OSGeo "products"/projects listed [http://www.opengeospatial.org/resource/products there]. (initial [http://osgeo-org.1560.x6.nabble.com/OGC-products-list-td5167501.html discussion] on Projects list)
* [UNASSIGNED] update Officers page (and any others) to reflect pycsw as a graduted OSGeo project
* [Jeff] draft a letter at [[OGC XML Schemas and FOSS4G Software Distribution]]

== Minutes ==

* Attending:
* Presiding:
* Scribing:

Also attended:

=== Assigned Tasks ===

* [UNASSIGNED] task description

=== Motions (to be confirmed by email) ===

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
!Motion
!+1
!0
!-1
!Abstain
!Passed?
!Notes
|-
| Approve past meeting's minutes
| x
| x
| x
| x
| Yes/No
|
|}

=== Full, raw minutes notes ===

IRC Log at http://irclogs.geoapt.com/osgeo/%23osgeo.2015-04-09.log

* 15:00 Meeting starts
* ...
* ...
* 16:10 '''Next meeting time''': date + time [[link to next meeting page]]

[[Category:Board]]
[[Category:Board Meetings 2015]]

Board Meeting 2015-04-09

2015-04-08T20:57:37Z

Wiki-LeneFischer: /* Current items */

This board meeting is '''scheduled for the 9th of April 2015''' at [http://www.timeanddate.com/worldclock/fixedtime.html?year=2015&month=4&day=9&hour=15&min=0&sec=0%2015.00UTC 15.00 UTC] through IRC and follow up voting by email.

== Agenda ==

=== Current items ===

Items in italic are recurring at each meeting.

Move items from past meetings, or add new items, at will. Note that the discussion is limited to 1 hour.

* ''roll call''
* ''appoint meeting chair, meeting scribe/secretary''
* ''Review and approve past minutes: [[Board Meeting 2015-03-05]]''
* ''brief treasurer report''
* "Geo for All" Student Awards request for seed funding (4k USD) ([http://wiki.osgeo.org/wiki/Ica-osgeo-isprs_award award wiki])
* An [http://wiki.osgeo.org/wiki/LIDAR_Format_Letter Open Letter] is being drafted requesting OGC/OGC Sponsors/ESRI back Open LiDAR standards. This letter should be ready to present within a week or two, ~ 20 April 2015. Request that the OSGeo Board officially endorse and present this letter once complete (as was done for the [http://wiki.osgeo.org/wiki/Geoservices_REST_API GeoServicesREST API letter]). Contacts: Suchith Anand, Martin Isenburg, Cameron Shorter.
* Proposing a [[Diversity]] statement for the Foundation
* FOSS4G 2015 update
* FOSS4G 2016 update
* Request for funding OSGeo President's travel to enable expanding strategic level initiatives between OSGeo and ICA at ICC 2015 and SDI-Open 2015 ([http://lists.osgeo.org/pipermail/ica-osgeo-labs/2015-April/001447.html GeoforAll request])
* Request for [http://wiki.osgeo.org/wiki/Uva_letter_of_support letter of support] for Jan Hartmann (University of Amsterdam) - Dutch historical GIS based on the first cadastre of the Netherlands (1832)
* Request for letter of support for Lene Fischer (University of Copenhagen) - For QGIS Codesprint/ Developers meeting in Denmark May 2015
* add your items here..

=== Items from past meetings ===
* Beginning plans for a 2015 budget (similar to [[OSGeo Budget 2014]])
** Dealing with SAC/systems issues ([[Outstanding SAC Issues 2014]])
* Updating/Recording accurate [http://www.osgeo.org/content/foundation/board_and_officers.html foundation officers]
** Website committee chair not active (according to the chair)
** Geodata committee not actively used (according to the chair)
** Marketing committee without a chair
* Updating/Recording accurate [http://www.osgeo.org/content/chapters/index.html local chapters]
* Agree on 5-level project evaluation as proposed by Cameron [http://lists.osgeo.org/pipermail/board/2014-September/012188.html]
* OSGeo is now a registered 'organization' with OGC, and goal is to have all OSGeo "products"/projects listed [http://www.opengeospatial.org/resource/products there]. (initial [http://osgeo-org.1560.x6.nabble.com/OGC-products-list-td5167501.html discussion] on Projects list)
* [UNASSIGNED] update Officers page (and any others) to reflect pycsw as a graduted OSGeo project
* [Jeff] draft a letter at [[OGC XML Schemas and FOSS4G Software Distribution]]

== Minutes ==

* Attending:
* Presiding:
* Scribing:

Also attended:

=== Assigned Tasks ===

* [UNASSIGNED] task description

=== Motions (to be confirmed by email) ===

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
!Motion
!+1
!0
!-1
!Abstain
!Passed?
!Notes
|-
| Approve past meeting's minutes
| x
| x
| x
| x
| Yes/No
|
|}

=== Full, raw minutes notes ===

IRC Log at http://irclogs.geoapt.com/osgeo/%23osgeo.2015-04-09.log

* 15:00 Meeting starts
* ...
* ...
* 16:10 '''Next meeting time''': date + time [[link to next meeting page]]

[[Category:Board]]
[[Category:Board Meetings 2015]]