OSGeo - User contributions [en]

LIDAR Format Letter

2015-04-17T12:08:27Z

Wiki-Nachouve: /* Signed */

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

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

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

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

# Suchith Anand, Geo for All, committed to Open Principles in Geo Education and Policy.
# Martin Isenburg, founder of [http://rapidlasso.com rapidlasso GmbH] and creator of [http://rapidlasso.com/LASzip LASzip], [http://rapidlasso.com/LAStools LAStools], and [http://rapidlasso.com/PulseWaves PulseWaves].
# Cameron Shorter, GeoSpatial Director at [http://lisasoft.com LISAsoft]. Core contributor and coordinator of [http://live.osgeo.org OSGeo-Live]. Contributor to numerous OGC testbeds, technical lead on a range of previous Australian and New Zealand Open Government initiatives.
# Stefan Keller, founder and director of [http://www.hsr.ch/geometalab Geometa Lab]; Professor 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.
# [http://www.geodatawiz.com/armin-schmidt Armin Schmidt], Chief Developer at [http://www.GeodataWIZ.com GeodataWIZ Ltd] and Chairman of [http://www.archprospection.org ISAP], committed to better science through Open Data.
# [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.
# [http://pt.linkedin.com/pub/jorge-rocha/1b/560/499 Jorge Gustavo Rocha], Professor, Computer Science Department, University of Minho, Portugal, committed to better science through [http://www.gistam.org/EventChairs.aspx?y=2016 Open Data].
# [http://people.eecs.ku.edu/~miller/ Jim Miller], University of Kansas, Professor, Computer Science. Open standards for data exchange are essential for education and research.
# [http://www.linkedin.com/pub/brandt-melick/22/869/261 Brandt Melick], Information Technology Department Director, Springfield Oregon USA. The need to promote open solutions is paramount.
# Alex Paza Makini, National University Solomon Islands, Natural Resources and Applied Science. Committed to open data standards for education and research, and everything beyond.
# Jorg M. Hacker, Professor, Director/Chief Scientist of [http://www.airborneresearchaustralia.com Airborne Research Australia], Flinders University, Adelaide, Australia. Open formats have always been a great benefit to airborne LiDAR.
# 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, Boulder Creek, CA [http://www.savetheredwoods.org/redwoods/coast-redwoods/ Countdown to the Last Coast Redwood]. 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
# [http://www.linkedin.com/in/clquintanilla 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 [http://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.
# [http://www.roccatello.com Eduard Roccatello], [http://www.3dgis.it 3DGIS], 3DGIS CTO and co-Founder
# [[User:moovida|Andrea Antonello]], [http://www.hydrologis.com HydroloGIS], OSGeo Charter member, Open Source GIS developer, HydroloGIS co-founder.
# [http://www.associazionegfoss.it Stefano Campus], President of [http://www.associazionegfoss.it GFOSS.it] Association (Associazione Italiana per l'Informazione Geografica Libera), Italian Local Chapter of OSGeo Foundation.
# [http://wiki.osgeo.org/wiki/User:Madi Margherita Di Leo], OSGeo Charter Member
# [http://wiki.osgeo.org/wiki/User:Sacosta Sergio Acosta y Lara], OSGeo Charter Member
# [http://wiki.osgeo.org/wiki/User:Maximdubinin Maxim Dubinin], CEO at NextGIS, OSGeo Charter Member. Another 'standard' proprietary format? No, thank you.
# [[User:Steko|Stefano Costa]], Soprintendenza Archeologia della Liguria, Ministero dei Beni e delle Attività Culturali e del Turismo, Italy
# [http://www.geog.illinois.edu/people/jgrn Jonathan Greenberg], Assistant Professor, [http://publish.illinois.edu/jgrn/ GEARS Laboratory], Department of Geography and Geographic Information Science, University of Illinois at Urbana-Champaign.
# Bob Basques, Saint Paul, Mn., GIS Systems Developer for the City of Saint Paul Public Works, Technical Director for SharedGeo.
# [http://wiki.osgeo.org/wiki/User:Maning Maning Sambale], OSGeo Charter Member
# [http://wiki.osgeo.org/wiki/User:Pcav Paolo Cavallini], QGIS PSC
# [http://wiki.osgeo.org/wiki/User:Nbozon Nicolas Bozon], [http://zoo-project.org ZOO-Project PSC], OSGeo Charter Member
# [http://www.linkedin.com/in/ruslanrainis Ruslan Rainis], Professor, Director, [http://www.research.usm.my/default.asp?tag=36 Centre for Research Initiatives in Liberal Arts & Social Sciences](CRI-LASS). Open GeoInformation for a Sustainable Tomorrow and the Bottom Billions.
# [[User:Silli|Silvia Franceschi]], [http://www.hydrologis.com HydroloGIS], OSGeo Charter member, Environmental Engineer Open Source GIS power user, HydroloGIS co-founder.
# Oscar Martinez Rubi [http://esciencecenter.nl Netherlands eScience Center] eScience engineer.
# Werner Macho, QGIS team member. Committed to open data standards for education and research.
# Giuseppe Patti, Geologist and Freelance Geospatial Advisor, GFOSS supporter.
# [http://wiki.osgeo.org/wiki/User:Drappo Daniel Rappo], Professor, University of Applied Sciences and Arts Western Switzerland, School of Business and Engineering Vaud.
# [[User:nachouve|Juan Ignacio Varela]], Freelance Geospatial Advisor and OSGeo Local Chapter Member.

=Background=
==About LiDAR==

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

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

==LAS Limitations==

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

: LAS format is not without its drawbacks:

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

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

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

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

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

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

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

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

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

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

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

: '''Summary:'''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=Value of Standards=

The importance of Open Standards is described 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 />

Geoservices REST API

2013-05-09T21:51:40Z

Wiki-Nachouve: /* Signed */

This wiki page aims to collate community concerns related to the proposed acceptance of the "Geoservices REST API" becoming an OGC standard. It is being collaboratively edited, targeting completion before the end of May 2013.

= Open Letter to OGC and voting members =

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

May 2013

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

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

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

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

* [[User:camerons|Cameron Shorter]], Geospatial Solutions Director at [http://lisasoft.com LISAsoft], core contributor & coordinator of [http://live.osgeo.org OSGeo-Live]
* [[Mark Lucas]], Founding member and board of directors for OSGeo foundation, Prinicipal Scientist for RadiantBlue Technologies Inc.
* [[User:Woodbri|Stephen Woodbridge]], Director of [http://imaptools.com iMaptools.com], Contributor and/or PSC of [http://mapserver.org Mapserver], [http://pgrouting.org/ pgRouting], [http://www.pagcgeo.org/ PAGC], and [http://www.postgis.org/ PostGIS]
* [[User:rouault|Even Rouault]], Geospatial developer, OSGeo Charter Member, core contributor and PSC member of [http://gdal.org GDAL/OGR], contributor of [http://mapserver.org Mapserver], [http://trac.osgeo.org/proj/ PROJ.4], [http://trac.osgeo.org/geotiff/ libgeotiff], [http://shapelib.maptools.org/ shapelib], [http://www.remotesensing.org/libtiff/ libtiff]
* Gerhard Triebnig, Managing Director at [http://eox.at EOX IT Services GmbH]
* [[User:pcreso|Brent Wood]], Environmental Information Delivery Programme Leader, NIWA, New Zealand. OGC member, Aust/NZ OSGEO chapter member, NZOSS Council member
* [[User:Schpidi|Stephan Meissl]], CTO at [http://eox.at EOX IT Services GmbH], contributor to [http://mapserver.org Mapserver], PSC chair of [http://eoxserver.org EOxServer]
* [[User:ticheler|Jeroen Ticheler]], Director of [http://geocat.net GeoCat], project founder and PSC chair of [http://geonetwork-opensource.org GeoNetwork opensource]
* [[User:Just|Just van den Broecke]], Director at [http://www.justobjects.nl Just Objects], contributor to [http://heron-mc.org Heron Mapping Client], secretary of [http://osgeo.nl OSGeo Dutch Local Chapter], member at [http://www.opengeogroep.nl OpenGeoGroep]
* [[User:milovanderlinden|Milo van der Linden]], member at [http://www.opengeogroep.nl OpenGeoGroep]
* [[User:surveyor|Landon Blake]], GIS Department Manager/Land Surveyor at [http://www.ksninc.com KSN], OSGeo California Chapter Board Representative.
* [[User:dmorissette|Daniel Morissette]], President at [http://mapgears.com/ Mapgears], core contributor and PSC member of [http://mapserver.org Mapserver] and [http://gdal.org GDAL/OGR]. Former OGC TC member and involved in the implementation of several OGC WxS services specs in MapServer.
* [[User:blammo|Bob Basques]], GIS Systems Developer at the City of Saint Paul, MN. [http://gis.ci.stpaul.mn.us Public Works GIS (GISmo)], Technical Director at [http://www.sharedgeo.org SharedGeo], OSGeo Charter Member, OSGeo TCMUG local chapter member, Co-founder and PSC member of [http://www.geomoose.org GeoMoose] project.
* [[User:vehrka|Pedro-Juan Ferrer Matoses]], PM at Omnium Strategic Intelligence, Spain, OSGeo Charter Member, OSGeo Spanish Local Chapter Liaison officer.
* Bevan Rudge, Director Lucion Limited, IT Advisor at Conservation Strategy Fund, Esri client
* [[User:Delawen|María Arias de Reyna]], software engineer at [http://geocat.net GeoCat], Spain, member of OSGeo Spanish Local Chapter.
* [[User:Aghisla|Anne Ghisla]], OSGeo Board Member, Italy, member of OSGeo Italian Local Chapter.
* [[User:Michogar|Micho Garcia]], Freelance and member of [http://geomati.co geomati.co], Spain, member of Spanish Local Chapter
* [[User:Madi|Margherita Di Leo]], OSGeo Charter Member, Italy
* [[Jorge Sanz]], GIS Consultant at [http://www.prodevelop.es Prodevelop], OSGeo Charter Member, OSGeo Spanish Local Chapter Member, Spain
* [[Pablo Sanxiao]], CTO and co-founder at [http://www.icarto.es iCarto], OSGeo Spanish Local Chapter Member, Spain
* [[User:Fsteggink|Frank Steggink]], GIS software developer at [http://www.vicrea.nl Vicrea], The Netherlands, member of the Dutch Local Chapter
* [[User:Olivier.courtin|Olivier Courtin]], [http://www.oslandia.com Oslandia] co-founder, core contributor or/and PSC member of [http://mapserver.org Mapserver] and [http://www.postgis.org/ PostGIS]. OGC TC member.
* [[User:Bolosig|Wladimir Szczerban]], OSGeo Spanish Local Chapter Member, Spain
* [[User:AnitaGraser|Anita Graser]], GIS specialist with AIT Austrian Institute of Technology, OSGeo Charter member and QGIS team member.
* [[User:Vmische|Volker Mische]], geospatial software engineer, creator of GeoCouch
* [[User:Ivansanchez|Iván Sánchez]], OSGeo Spanish Local Chapter Member, head of [http://www.openstreetmap.es OpenStreetMap Spain], [http://osmfoundation.org OpenStreetMap Foundation] member, [http://hot.openstreetmap.org/ Humanitarian OpenStreetMap Team] member, [http://www.idee.es/ Spanish SDI working group] member
* [[User:Gabi|Gabriel Carrión]], Strategy Manager at [http://www.gvsig.com gvSIG association]
* [http://strk.keybit.net Sandro Santilli], OSGeo Charter Member, [http://postgis.net PostGIS] and [http://trac.osgeo.org/geos GEOS] PSC member and core hacker.
* [[User:Javiarch|Javier Diaz]], member of Geoinquietos Bs As [http://wiki.osgeo.org/wiki/Category:Geoinquietos_Buenos_Aires], member of the Organizing Committee FOSS4G Bs As 2013 [http://www.foss4g-ba.org/]
* [[User: JoCook|Jo Cook]], Consultant at [http://isharemaps.com| Astun Technology], former Director of OSGeo, Charter Member, founder of UK Local Chapter, Deputy Chair of [http://2013.foss4g.org| FOSS4G 2013]
* [[User: Fpenarru | Francisco José Peñarrubia]], CTO and co-founder at [http://www.scolab.es SCOLAB]. Members of [http://www.gvsig.com gvSIG Association]
* [[User: Ganesh|Shanmugam Ganeshkumar]], Director of [http://www.geoicon.com GeoICON], member OSGeo Malaysia Chapter
* [[User:Barryrowlingson|Barry Rowlingson]], Senior Researcher, Lancaster University and Software Sustainability Institute Fellow
* [[User: Sfkeller|Stefan Keller]], University of Applied Sciences, Rapperswil (Switzerland), Member of Swiss OSM (SOSM) and QGIS association and of organizing committees of pgConf.DE and FOSSGIS 2013, and member of eCH (e-government standards of Switzerland)
* [[User: AndyBMapMan|Andrew Bailey]], OSGeo member, Astun Technology
* [[User: Sanand|Suchith Anand]], OSGeo Charter member, OSGeo Education member, FOSS4G 2013 LOC member
* [[User: krefftc|Carlos Krefft]], GIS software developer at [http://www.cstars.miami.edu CSTARS - University of Miami], OGC and OSGeo Member.
* [[User:Steko|Stefano Costa]], OSGeo member, GFOSS.it member and former board member, Ministero per i Beni e le Attività Culturali (Italy)
* [[User:pebau|Peter Baumann]], [http://www.jacobs-university.de/lsis Jacobs University], OGC member, WCS.SWG chair, editor of 10+ specs (disclaimer: this is an expression of my personal opinion and not in any way endorsed by OGC)
* [[User:pmbatty|Peter Batty]], CTO of Geospatial Division at [http://www.ubisense.net Ubisense], OSGeo board member, former CTO of [http://intergraph.com Intergraph] and [http://www.gedigitalenergy.com/gis.htm GE Smallworld], Technical Committee member of OGC in its formative years c 1995-97
* [[User: BarendKobben | Barend Köbben]], OSGEO Chartered Member, OSGeo.nl Dutch chapter treasurer, Senior Lecturer at [http://www.itc.nl ITC-University of Twente]
* [[User: pcav | Paolo Cavallini]], [http://www.faunalia.it Faunalia], OSGeo member, GFOSS.it member and former president, QGIS-PSC
* [[User: fthamura| FRans Thamura]], [http://www.osgeo.or.id Indonesia], OSGeo Indonesia, organizer]
* [[User: Endofcap| Sanghee Shin]], Founder and CEO of [http://www.gaia3d.com Gaia3D], OSGeo Charter Member, Representative of [http://www.osgeo.kr OSGeo Korean Chapter], Chairman of Open Source GIS Alliance Korea
* [[User: rentairo| Benni Purwonegoro]],Indonesia, IT-Spatial Engineer @ Geospatial Information Agency .
* [[User: jachym| Jachym Cepicky]], Czech Republic, member of OSGeo Board of Directors
* [[User: cappelaere| Pat Cappelaere]], Vightel Corporation
* [[User: JuergenFischer|Jürgen Fischer]], norBIT GmbH, QGIS core developer
* [[User: Maria|Maria Antonia Brovelli]], OSGeo Charter member, OSGeo Education member, GIS Professor and Vice Rector for the Como Campus at [http://www.polimi.it/en Politecnico di Milano], Italy
* [[User:Nachouve |Nacho Varela]], GIS Consultant, OSGeo Spanish Local Chapter Member, Spain

= Concerns =
--- DRAFT ____

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

== Summary ==
As at May 2013, OGC members have been asked to decide whether to accept the "GeoServices REST API" as an OGC standard. This is a contentious issue, with many people arguing that introduction of the “GeoServices REST API” will have costly, far reaching, negative impacts on interoperability, and significantly tarnish the OGC's reputation as a champion of interoperability.

The key points of contention revolve around the fact that the proposed "GeoServices REST API" does not build upon or extend existing OGC standards, but rather addresses similar requirements using an alternative API. In particular, the overlap and/or duplication of existing standards is widespread: OGC's core standards of WMS, WMTS, WFS, SE/SLD, WCS, CS/W are all duplicated to a significant extent. This defeats the purpose of having standards in the first place.

Duplication of standards will likely result in a combination of the following:
# The cost to application developers, systems integrators, testers and sponsors to support all relevant OGC standards will be substantially increased.
# Consequently, organisations and/or applications may choose to only support one standard, or only support one standard fully.
# Sponsors (such as governments) who require compliance with OGC standards will discover that applications don't communicate together, due to applications supporting different OGC standards that essentially do the same thing.
# This will result in a diminished importance of OGC, as the "OGC standards" stamp of approval will not equate interoperability.
# After a while, in order to solve interoperability issues, a respected international organisation or program will likely take the initiative to mandate one standard as the preferred standard for all agencies to follow. To date, the OGC has provided this leadership.
# One standard taking prominance over the other will likely lead to the other being neglected or deprecated, resulting in many OGC compliant systems becoming legacy systems in the process. This should be considered an undesirable outcome for a standards organisation. Backward compatibility to the existing WxS standards is important in this respect.
# Given backwards compatibility with the ESRI Restful implementation is mandated, this is not an Open Standard, and should not be ratified as if it was.

== Political Concerns ==

* Adopting the standard will expose the OGC to a strong suspicion of acting as a rubber stamp organization under ESRI weight, and will be detrimental to its recognized position as a reference organization for geospatial standards.
* It is a dubious practice that a standardization organisation promotes competing standards, without explicitely obsoleting (or at least recommending) some of them. How is a newcomer to the industry supposed to select the appropriate standard if several ones share the same scope : WFS or GeoServices REST API Feature Service, WMS or GeoServices REST API Map Service, etc. ?

== Commercial Concerns ==

* Promoting standards from an existing implementation made by a single vendor leads to an obvious bias in competition.
* Supporting multiple overlapping standards greatly reduces usability while it increases complexity and cost of development and maintenance.
* Many SME's have invested in supporting existing OGC standards in their products. They will be forced to choose the standards they support (and can explain), resulting in decreased interoperability, confusion and frustration for clients.
* Confusing customers with new, overlapping OGC standards will lower the credibility of companies and of OGC, reducing business opportunities.

== Technical Concerns ==

* The Geoservices REST API overlaps in large proportion with existing OGC standards such as WMS, WCS, WFS, WMTS, CSW, with no effort made to reconcile with those standards.
* The standardization of WKT for Spatial reference systems is unfortunately currently quite weak in OGC standards. Geoservices REST API is tied with ESRI's version of WKT, which is not properly specified in the Geoservices REST API documents, and is known to be incompatible with other OGC documents, which will lead to a larger confusion. See the following [http://lists.opengeospatial.org/pipermail/requests/2012-July/000166.html comment] for more details on this issue.
* The Geoservices REST API is not particularly RESTful - it's a thinly disguised service call, not an address space for RESTful objects that can be operated on.
* At least as far as "imagery" is concerned, OGC standards arguably are substantially more mature, powerful, flexible, and modular then the ESRI "Geoservice REST API" Part 6 (and some design principles suggest that scalability may be hampered as well):
** data model:
*** the ESRI "Geoservice REST API" appears constrained to 2-D imagery, plus optional time stamps. OGC has established a [http://en.wikipedia.org/wiki/Coverage_data unified coverage model] which fully supports n-D spatio-temporal data. It allows use and exchange of coverages between different services, such as [http://en.wikipedia.org/wiki/Web_Coverage_Service WCS], [http://en.wikipedia.org/wiki/Web_Coverage_Processing_Service WCPS], WPS, and SWE.
*** OGC coverages support both regular and irregular grids; the ESRI "Geoservice REST API" supports only regular grids, more specifically: only rectified grids with quadrilateral pixels.
*** the ESRI "Geoservice REST API" lacks support for temporal data; it only offers timestamps, measured in milliseconds; this is inconvenient for users and immediately excludes, e.g., geological dates. OGC has established uniform handling of horizontal, vertical, and temporal coordinate reference systems (CRSs), following a deep consensus process with GIS science and backwards compatible with EPSG. The ESRI "Geoservice REST API" specific way of handling coordinates is not known to support this, thereby excluding appropriate timeseries handling in remote sensing, air traffic, MetOcean, etc.
*** OGC coverages provide a concise, versatile model for supporting different binary formats; the ESRI "Geoservice REST API" supports only very few selected 2-D formats, excluding, e.g., JPEG2000, NetCDF, HDF, etc.
*** the ESRI "Geoservice REST API" lacks a clear model of their data structures, it can be deduced only implicitly from the operation mechanics.
** service model:
*** The ESRI "Geoservice REST API" Part 6 lacks conciseness, thereby opening up ways for implementations that are not interoperable. For developers of alternative implementations this may mean they have to acquire ESRI licenses for finding out the intended behavior.
*** Functionality in the ESRI "Geoservice REST API" appears randomly chosen, with no clear concept visible; this burdens implementers while still leaving holes of functionality. For example, this functionality appears restricted to mapping applications and does not easily extend into other domains.
*** It has been said that the ESRI "Geoservice REST API" can be seen as a "wrapper around OGC W*S" services. This is not true for WCS (and WCPS), at least: the ESRI "Geoservice REST API" Part 6 is too poor in functionality and too different in mechanics to accomplish this.
** In summary, the ESRI "Geoservice REST API" Imaging part is at a technological level where WCS departed from some 5 years ago. Inconciseness of the specification at large will make it difficult for third parties to come up with interoperable implementations. The components making up the ESRI "Geoservice REST API" provide natural blocks assignable to the matching SWGs. As for Part 6 of the ESRI "Geoservice REST API", if to become a standard it needs to be discussed in the WCS.SWG for harmonization, clarification, and improvement.

== Methodological Concerns ==

* No public response (nor private to the authors of the comments) has been made to the various comments sent on the OGC Requests mailing list in [[http://lists.opengeospatial.org/pipermail/requests/2012-July/date.html July 2012]] and [[http://lists.opengeospatial.org/pipermail/requests/2012-August/date.html August 2012]] during the 30 day public comments period.
* The Geoservices REST API can not be amended (other than editorial changes in the specification document), because of a requirement of backward compatibility with ESRI implementation. Consequently, the standard is unlikely to improve, or its evolution will be only lead by ESRI.
* OGC standards normally require interoperability experiments and a richer process to ratify a standard such as this one. No explanation has been forthcoming as to why a simplified process is appropriate in this case.
* ESRI/OGC have specifically [http://lists.osgeo.org/pipermail/discuss/2013-May/011659.html rejected requests] to openly share their justifications document being selectively sent to OGC voters.

= History =

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

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

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

Erratas y correcciones

2010-12-20T23:43:52Z

Wiki-Nachouve:

Si has detectado cualquier problema en el libro susceptible de ser solucionado, anótalo aquí para que quede constancia de ello. Simplemente edita esta página y escribe lo que consideres necesario para describir el problema.

Utiliza los números de línea y página para que sea fácil localizar de localizar. Anota también la fecha de la revisión (la encontraras en la portada del libro), para que sepamos con qué versión del manuscrito trabajas. Por último, pon tu nombre para que podamos reconocer tu colaboración en los créditos del libro.

Por ejemplo:

Juan Gómez: En la página 47, linea 22, donde dice "una capa vectorial de puntos" debería decir "una capa vectorial de polígonos". Revisión del 13 de noviembre de 2010.

-----------------------------

[Añade aquí tus comentarios, debajo del último existente]

Nacho Varela: En la figura 5.17 el barrido usando órdenes de Morton tiene la secuencia 11, 12, 13, ¿24?, 15. Revisión: 15 de diciembre 2010

FOSS4G 2010 Code Sprint

2010-08-25T07:38:11Z

Wiki-Nachouve: /* Geomajas Code Sprint */

[[Category:FOSS4G2010]] [[Category:FOSS4G]] [[Category:Code Sprints]]
== Organizing Contacts ==

*Wladimir Szczerban, Enric Rodellas

== Code Sprint - what's that? ==

A code sprint is usually organized by a group that is using an open source project and wants to see something done. They fly the developers to a single location and feed them for a couple of days with the necessities of the hacking life (internet, caffeine, electricity). The communication that happens from face to face hacking usually lasts the project for a year or more. You see this a lot in projects like Drupal etc...

== Venue ==

For map and more details see

*Date: '''Friday, 10 Sep 2010''' (the day after the conference).
*Time: '''9am-5pm'''  ([http://www.timeanddate.com/worldclock/meetingdetails.html?year=2010&month=9&day=10&hour=7&min=0&sec=0&p1=31 timeandate]) 
*'''Where:''' Citilab-Cornellà
Citilab-Cornellà
Phone: +34 93 551 06 60
Fax: +34 93 551 06 78
[http://en.citilab.eu/home/ web Citilab]
Pl. Can Suris s/n
08940 Cornellà de Llobregat (Barcelona)
*'''Rooms:''' A+B+C
*'''[http://www.openstreetmap.org/?mlat=41.359847&mlon=2.061653&zoom=18&layers=B000FTF online maps]'''

More than 100 attendees are expected!

== Motivation and Direction ==

A day, a code base, and your imagination?

Projects can use the time and venue for organizational discussions, development roadmaps, and group resolution of thorny issues in their code bases.

Is this your First Sprint? Here is some background information to get you started:

*http://www.infrae.com/about/activities/sprintathon/tips
*http://www.onlamp.com/pub/a/python/2006/10/19/running-a-sprint.html
*Example Sprint (from same people who do GeoServer): http://www.openplans.org/projects/bbq-sprint

Visit FOSS4G past experiences: [http://wiki.osgeo.org/wiki/FOSS4G_2009_Code_Sprint 2009], [http://wiki.osgeo.org/wiki/FOSS4G2008_CodeSprint 2008], [http://wiki.osgeo.org/wiki/FOSS4G2007_CodeSprint 2007 ]

== Summary of Workgroups ==

List of Workgroups here, more info follows...

*workgroup 1
*workgroup 2

== Additional Interested People ==

The following people are potentially interested in participating in sprinting activities though have not yet established a Workgroup.

* Frank Warmerdam: GDAL, MapServer, PROJ.4, OSGeo4W
* Ari Jolma: GDAL
* Chaitanya kumar CH: GDAL

= Workgroups =

To participate, copy a project skeleton and start a section below for your project.

== 52°North WPS ==

'''Coordinator:'''

*Bastian Schäffer

'''Attending:'''

*Person 1

'''Goals:'''

* Technical disucssions about 52°North WPS

== Geomajas Code Sprint ==

'''Coordinator:'''

*Pieter De Graef

'''Attending:'''

*Pieter De Graef
*Jan De Moerloose
*Joachim van der Auwera
*Dirk Frigne
*Frank Maes
*Oliver May

'''Goals:'''

* Improving getting started documentation
* Create a GeoJson service, so that an OpenLayers client can make use of a Geomajas server.
* Create a Geomajas DataStore for GeoTools.
* Work toward plug-in graduation (documentation + tests)

== PostGIS ==

'''Attending:'''

* Paul Ramsey
* Olivier Courtin
* Mark Cave-Ayland
* Pierre Racine

'''Goals:'''

* Synchronize fall development goals
* Discuss ISO type extensions
* Discuss official raster integration issues

== GeoJQuery ==

'''Coordinator:'''

* [[User:Vmische | Volker Mische]]

'''Attending:'''

* [[User:Astrid Emde | Astrid Emde]]
* [[User:Testbaudson | Christoph Baudson]]
* [[User:Jacarma | Javi Carrasco]]
* [[Arnulf Christl]]

'''Goals:'''

* getting started
* ...

== gvSIG ==

Someone asked at gvSIG mailing lists ([http://listserv.gva.es/pipermail/gvsig_desarrolladores/2010-August/004697.html 1], [http://listserv.gva.es/pipermail/gvsig_internacional/2010-August/005857.html 2]) about a possible gvSIG code sprint at Barcelona FOSS4G.

'''(Tentative) coordinator:'''

* [[Jorge Sanz]]

'''Attending:'''

* [[User:Amaneiro | Andrés Maneiro]]
* [[User:nachouve | Nacho Varela]]

'''Goals:'''

Not defined yet.

User:Nachouve

2010-08-24T09:32:04Z

Wiki-Nachouve: /* Nacho Varela (Nacho Uve) */

== Nacho Varela (Nacho Uve) ==
<div style="float: right;">
[[Image:NachoUve.jpg|thumb]]
</div>
'''Informatic Engineer'''<br>
GIS Consultor<br>Project Manager - FLOSS Developer <br>

=== Contact ===

:[mailto:nachouve@gmail.com nachouve@gmail.com]

File:NachoUve.jpg

2010-08-24T09:30:18Z

Wiki-Nachouve: Nacho Varela Pic

Nacho Varela Pic

User:Nachouve

2010-08-24T09:28:34Z

Wiki-Nachouve: Created page with '== Nacho Varela (Nacho Uve) == <div style="float: right;"> </div> '''Informatic Engineer'''<br> GIS Consultor<br>Project Manager - FLOSS Developer <br> === Contact === :[m…'

== Nacho Varela (Nacho Uve) ==
<div style="float: right;">

</div>
'''Informatic Engineer'''<br>
GIS Consultor<br>Project Manager - FLOSS Developer <br>

=== Contact ===

:[mailto:nachouve@gmail.com nachouve@gmail.com]

FOSS4G 2010 Code Sprint

2010-08-24T09:05:17Z

Wiki-Nachouve: /* Geomajas Code Sprint */

[[Category:FOSS4G2010]] [[Category:FOSS4G]] [[Category:Code Sprints]]
== Organizing Contacts ==

*Wladimir Szczerban, Enric Rodellas

== Code Sprint - what's that? ==

A code sprint is usually organized by a group that is using an open source project and wants to see something done. They fly the developers to a single location and feed them for a couple of days with the necessities of the hacking life (internet, caffeine, electricity). The communication that happens from face to face hacking usually lasts the project for a year or more. You see this a lot in projects like Drupal etc...

== Venue ==

For map and more details see

*Date: '''Friday, 10 Sep 2010''' (the day after the conference).
*Time: '''9am-5pm'''  ([http://www.timeanddate.com/worldclock/meetingdetails.html?year=2010&month=9&day=10&hour=7&min=0&sec=0&p1=31 timeandate]) 
*'''Where:''' Citilab-Cornellà
Citilab-Cornellà
Phone: +34 93 551 06 60
Fax: +34 93 551 06 78
[http://en.citilab.eu/home/ web Citilab]
Pl. Can Suris s/n
08940 Cornellà de Llobregat (Barcelona)
*'''Rooms:''' A+B+C
*'''[http://www.openstreetmap.org/?mlat=41.359847&mlon=2.061653&zoom=18&layers=B000FTF online maps]'''

More than 100 attendees are expected!

== Motivation and Direction ==

A day, a code base, and your imagination?

Projects can use the time and venue for organizational discussions, development roadmaps, and group resolution of thorny issues in their code bases.

Is this your First Sprint? Here is some background information to get you started:

*http://www.infrae.com/about/activities/sprintathon/tips
*http://www.onlamp.com/pub/a/python/2006/10/19/running-a-sprint.html
*Example Sprint (from same people who do GeoServer): http://www.openplans.org/projects/bbq-sprint

Visit FOSS4G past experiences: [http://wiki.osgeo.org/wiki/FOSS4G_2009_Code_Sprint 2009], [http://wiki.osgeo.org/wiki/FOSS4G2008_CodeSprint 2008], [http://wiki.osgeo.org/wiki/FOSS4G2007_CodeSprint 2007 ]

== Summary of Workgroups ==

List of Workgroups here, more info follows...

*workgroup 1
*workgroup 2

== Additional Interested People ==

The following people are potentially interested in participating in sprinting activities though have not yet established a Workgroup.

* Frank Warmerdam: GDAL, MapServer, PROJ.4, OSGeo4W
* Ari Jolma: GDAL
* Chaitanya kumar CH: GDAL

= Workgroups =

To participate, copy a project skeleton and start a section below for your project.

== 52°North WPS ==

'''Coordinator:'''

*Bastian Schäffer

'''Attending:'''

*Person 1

'''Goals:'''

* Technical disucssions about 52°North WPS

== Geomajas Code Sprint ==

'''Coordinator:'''

*Pieter De Graef

'''Attending:'''

*Pieter De Graef
*Jan De Moerloose
*Joachim van der Auwera
*Dirk Frigne
*Frank Maes
*Oliver May
*[[User:nachouve | Nacho Varela]]

'''Goals:'''

* Improving getting started documentation
* Create a GeoJson service, so that an OpenLayers client can make use of a Geomajas server.
* Create a Geomajas DataStore for GeoTools.

== PostGIS ==

'''Attending:'''

* Paul Ramsey
* Olivier Courtin

'''Goals:'''

* Synchronize fall development goals
* Discuss ISO type extensions
* Discuss official raster integration issues

== GeoJQuery ==

'''Coordinator:'''

* [[User:Vmische | Volker Mische]]

'''Attending:'''

* [[User:Astrid Emde | Astrid Emde]]
* [[User:Testbaudson | Christoph Baudson]]
* [[User:Jacarma | Javi Carrasco]]
* [[Arnulf Christl]]

'''Goals:'''

* getting started
* ...

== gvSIG ==

Someone asked at gvSIG mailing lists ([http://listserv.gva.es/pipermail/gvsig_desarrolladores/2010-August/004697.html 1], [http://listserv.gva.es/pipermail/gvsig_internacional/2010-August/005857.html 2]) about a possible gvSIG code sprint at Barcelona FOSS4G.

'''(Tentative) coordinator:'''

* [[Jorge Sanz]]

'''Attending:'''

* [[User:Amaneiro | Andrés Maneiro]]
* [[User:nachouve | Nacho Varela]]

'''Goals:'''

Not defined yet.

FOSS4G 2010 Code Sprint

2010-08-24T09:04:42Z

Wiki-Nachouve: /* gvSIG */

[[Category:FOSS4G2010]] [[Category:FOSS4G]] [[Category:Code Sprints]]
== Organizing Contacts ==

*Wladimir Szczerban, Enric Rodellas

== Code Sprint - what's that? ==

A code sprint is usually organized by a group that is using an open source project and wants to see something done. They fly the developers to a single location and feed them for a couple of days with the necessities of the hacking life (internet, caffeine, electricity). The communication that happens from face to face hacking usually lasts the project for a year or more. You see this a lot in projects like Drupal etc...

== Venue ==

For map and more details see

*Date: '''Friday, 10 Sep 2010''' (the day after the conference).
*Time: '''9am-5pm'''  ([http://www.timeanddate.com/worldclock/meetingdetails.html?year=2010&month=9&day=10&hour=7&min=0&sec=0&p1=31 timeandate]) 
*'''Where:''' Citilab-Cornellà
Citilab-Cornellà
Phone: +34 93 551 06 60
Fax: +34 93 551 06 78
[http://en.citilab.eu/home/ web Citilab]
Pl. Can Suris s/n
08940 Cornellà de Llobregat (Barcelona)
*'''Rooms:''' A+B+C
*'''[http://www.openstreetmap.org/?mlat=41.359847&mlon=2.061653&zoom=18&layers=B000FTF online maps]'''

More than 100 attendees are expected!

== Motivation and Direction ==

A day, a code base, and your imagination?

Projects can use the time and venue for organizational discussions, development roadmaps, and group resolution of thorny issues in their code bases.

Is this your First Sprint? Here is some background information to get you started:

*http://www.infrae.com/about/activities/sprintathon/tips
*http://www.onlamp.com/pub/a/python/2006/10/19/running-a-sprint.html
*Example Sprint (from same people who do GeoServer): http://www.openplans.org/projects/bbq-sprint

Visit FOSS4G past experiences: [http://wiki.osgeo.org/wiki/FOSS4G_2009_Code_Sprint 2009], [http://wiki.osgeo.org/wiki/FOSS4G2008_CodeSprint 2008], [http://wiki.osgeo.org/wiki/FOSS4G2007_CodeSprint 2007 ]

== Summary of Workgroups ==

List of Workgroups here, more info follows...

*workgroup 1
*workgroup 2

== Additional Interested People ==

The following people are potentially interested in participating in sprinting activities though have not yet established a Workgroup.

* Frank Warmerdam: GDAL, MapServer, PROJ.4, OSGeo4W
* Ari Jolma: GDAL
* Chaitanya kumar CH: GDAL

= Workgroups =

To participate, copy a project skeleton and start a section below for your project.

== 52°North WPS ==

'''Coordinator:'''

*Bastian Schäffer

'''Attending:'''

*Person 1

'''Goals:'''

* Technical disucssions about 52°North WPS

== Geomajas Code Sprint ==

'''Coordinator:'''

*Pieter De Graef

'''Attending:'''

*Pieter De Graef
*Jan De Moerloose
*Joachim van der Auwera
*Dirk Frigne
*Frank Maes
*Oliver May
*Nacho Varela

'''Goals:'''

* Improving getting started documentation
* Create a GeoJson service, so that an OpenLayers client can make use of a Geomajas server.
* Create a Geomajas DataStore for GeoTools.

== PostGIS ==

'''Attending:'''

* Paul Ramsey
* Olivier Courtin

'''Goals:'''

* Synchronize fall development goals
* Discuss ISO type extensions
* Discuss official raster integration issues

== GeoJQuery ==

'''Coordinator:'''

* [[User:Vmische | Volker Mische]]

'''Attending:'''

* [[User:Astrid Emde | Astrid Emde]]
* [[User:Testbaudson | Christoph Baudson]]
* [[User:Jacarma | Javi Carrasco]]
* [[Arnulf Christl]]

'''Goals:'''

* getting started
* ...

== gvSIG ==

Someone asked at gvSIG mailing lists ([http://listserv.gva.es/pipermail/gvsig_desarrolladores/2010-August/004697.html 1], [http://listserv.gva.es/pipermail/gvsig_internacional/2010-August/005857.html 2]) about a possible gvSIG code sprint at Barcelona FOSS4G.

'''(Tentative) coordinator:'''

* [[Jorge Sanz]]

'''Attending:'''

* [[User:Amaneiro | Andrés Maneiro]]
* [[User:nachouve | Nacho Varela]]

'''Goals:'''

Not defined yet.

FOSS4G 2010 Code Sprint

2010-08-24T09:04:04Z

Wiki-Nachouve: /* Geomajas Code Sprint */

[[Category:FOSS4G2010]] [[Category:FOSS4G]] [[Category:Code Sprints]]
== Organizing Contacts ==

*Wladimir Szczerban, Enric Rodellas

== Code Sprint - what's that? ==

A code sprint is usually organized by a group that is using an open source project and wants to see something done. They fly the developers to a single location and feed them for a couple of days with the necessities of the hacking life (internet, caffeine, electricity). The communication that happens from face to face hacking usually lasts the project for a year or more. You see this a lot in projects like Drupal etc...

== Venue ==

For map and more details see

*Date: '''Friday, 10 Sep 2010''' (the day after the conference).
*Time: '''9am-5pm'''  ([http://www.timeanddate.com/worldclock/meetingdetails.html?year=2010&month=9&day=10&hour=7&min=0&sec=0&p1=31 timeandate]) 
*'''Where:''' Citilab-Cornellà
Citilab-Cornellà
Phone: +34 93 551 06 60
Fax: +34 93 551 06 78
[http://en.citilab.eu/home/ web Citilab]
Pl. Can Suris s/n
08940 Cornellà de Llobregat (Barcelona)
*'''Rooms:''' A+B+C
*'''[http://www.openstreetmap.org/?mlat=41.359847&mlon=2.061653&zoom=18&layers=B000FTF online maps]'''

More than 100 attendees are expected!

== Motivation and Direction ==

A day, a code base, and your imagination?

Projects can use the time and venue for organizational discussions, development roadmaps, and group resolution of thorny issues in their code bases.

Is this your First Sprint? Here is some background information to get you started:

*http://www.infrae.com/about/activities/sprintathon/tips
*http://www.onlamp.com/pub/a/python/2006/10/19/running-a-sprint.html
*Example Sprint (from same people who do GeoServer): http://www.openplans.org/projects/bbq-sprint

Visit FOSS4G past experiences: [http://wiki.osgeo.org/wiki/FOSS4G_2009_Code_Sprint 2009], [http://wiki.osgeo.org/wiki/FOSS4G2008_CodeSprint 2008], [http://wiki.osgeo.org/wiki/FOSS4G2007_CodeSprint 2007 ]

== Summary of Workgroups ==

List of Workgroups here, more info follows...

*workgroup 1
*workgroup 2

== Additional Interested People ==

The following people are potentially interested in participating in sprinting activities though have not yet established a Workgroup.

* Frank Warmerdam: GDAL, MapServer, PROJ.4, OSGeo4W
* Ari Jolma: GDAL
* Chaitanya kumar CH: GDAL

= Workgroups =

To participate, copy a project skeleton and start a section below for your project.

== 52°North WPS ==

'''Coordinator:'''

*Bastian Schäffer

'''Attending:'''

*Person 1

'''Goals:'''

* Technical disucssions about 52°North WPS

== Geomajas Code Sprint ==

'''Coordinator:'''

*Pieter De Graef

'''Attending:'''

*Pieter De Graef
*Jan De Moerloose
*Joachim van der Auwera
*Dirk Frigne
*Frank Maes
*Oliver May
*Nacho Varela

'''Goals:'''

* Improving getting started documentation
* Create a GeoJson service, so that an OpenLayers client can make use of a Geomajas server.
* Create a Geomajas DataStore for GeoTools.

== PostGIS ==

'''Attending:'''

* Paul Ramsey
* Olivier Courtin

'''Goals:'''

* Synchronize fall development goals
* Discuss ISO type extensions
* Discuss official raster integration issues

== GeoJQuery ==

'''Coordinator:'''

* [[User:Vmische | Volker Mische]]

'''Attending:'''

* [[User:Astrid Emde | Astrid Emde]]
* [[User:Testbaudson | Christoph Baudson]]
* [[User:Jacarma | Javi Carrasco]]
* [[Arnulf Christl]]

'''Goals:'''

* getting started
* ...

== gvSIG ==

Someone asked at gvSIG mailing lists ([http://listserv.gva.es/pipermail/gvsig_desarrolladores/2010-August/004697.html 1], [http://listserv.gva.es/pipermail/gvsig_internacional/2010-August/005857.html 2]) about a possible gvSIG code sprint at Barcelona FOSS4G.

'''(Tentative) coordinator:'''

* [[Jorge Sanz]]

'''Attending:'''

* [[User:Amaneiro | Andrés Maneiro]]

'''Goals:'''

Not defined yet.