OSGeo - User contributions [en]

Geoservices REST API

2013-06-04T22:13:00Z

Wiki-Hdus: /* Signed */

This page aims to collate community concerns related to the adoption of the "Geoservices REST API" document as a standard of the [http://www.opengeospatial.org/ Open Geospatial Consortium (OGC)]. The page has been collaboratively edited, and delivered by the board of the [http://osgeo.org OSGeo Foundation (OSGeo)] to the OGC and OGC voting members on Friday 17 May 2013.

The version of the document delivered can be found here: http://wiki.osgeo.org/index.php?title=Geoservices_REST_API&oldid=71311

= Cover Letter from the OSGeo Board =

The board of the [http://osgeo.org Open Source Geospatial Foundation] (OSGeo) is presenting this letter to the OGC. The letter highlights concerns about the "GeoServices REST API" from many people within the OSGeo community. As always, if there is anything the OSGeo board can do to help, then please let us know.

Signed: Jeff McKenna (OSGeo president),
Peter Batty,
Jáchym Čepický,
Michael Gerlek,
Anne Ghisla,
Mark Lucas,
Daniel Morissette,
Cameron Shorter,
Frank Warmerdam

= Open Letter to OGC and voting members =

May 2013

We, the undersigned, have concerns that approving the "Geoservices REST API" as an OGC standard, will 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. These concerns are described below.

== Signed ==

# [[User:camerons|Cameron Shorter]], Geospatial Solutions Director at [http://lisasoft.com LISAsoft], core contributor & coordinator of [http://live.osgeo.org OSGeo-Live], OSGeo Board member
# [[Mark Lucas]], Founding member and board of directors for OSGeo foundation, Principal 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], OSGeo Board member, 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 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, Post-doctoral researcher at the European Commission, JRC, 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
# [[User:vasile |Vasile Craciunescu]], OSGeo Charter member, OSGeo Romania Local Chapter Leader, Researcher at Romanian National Meteorological Administration, Romania
# [[User:badaveil |Abbas Abdul Wahab]], Asst. Director, Federal Department of Town & Country Planning, Peninsular Malaysia
# [[User:rbraam | Roy Braam]], Software Engineer @ [http://www.b3partners.nl | B3Partners]
# [[User:peteris | Peteris Bruns]], Latvia, GIS Consultant & Software Engineer @ [http://www.sungis.lv | SunGIS]
# [[User:Lutra | Giovanni Manghi]], Portugal, [http://www.faunalia.pt Faunalia], OSGeo member, OSGeo-Portugal
# [[User:Hfpmartins | Hugo Martins]], UK, [http://www.lutraconsulting.co.uk Lutra Consulting], WebGIS Developer, OSGeo-Portugal Member
# [[User:Sabb | Saber Razmjooei]], UK, [http://www.lutraconsulting.co.uk Lutra Consulting], Co-Founder
# [[User:Wellsp | Peter Wells]], UK, [http://www.lutraconsulting.co.uk Lutra Consulting], Co-Founder
# [[User:SGijzen | Sidney Gijzen]], The Netherlands, Researcher GIS @ [http://www.wageningenur.nl/en/Expertise-Services/Research-Institutes/alterra.htm Alterra, Wageningen UR]
# [[User:mfidelman | Miles Fidelman]], US, Principal, Protocol Technologies Group, LLC
# [[User:punkish | Puneet Kishor]], OSGeo Charter Member; [http://www.geology.wisc.edu Geology, Univ. of Wisconsin-Madison]; [http://creativecommons.org/staff#puneetkishor Creative Commons]
# [[User:Toze | António José Silva]], Portugal, GIS Consultant, OSGeo-Portugal Member
# [[User:AndreMano | AndreMano]], Portugal, Natural History Society - GIS Department, OSGeo-Portugal Member
# [[User:maurimiranda|Mauricio Miranda]], Argentina, OSGeo Charter Member, OSGeo Spanish Local Chapter Board Member
# [[User:pmachado|Paulo Machado]], Portugal, Software Engineer @ PT Inovação
# [[User:alvaro|Alvaro Anguix]], Spain, General Manager at [http://www.gvsig.com gvSIG Association]
# [[Santiago Higuera]], CEO at [http://Mercatorlab.com Mercatorlab], OSGeo Spanish Local Chapter Board Member, Spain
# [[Alan Boudreault]], Developer at [http://mapgears.com/ Mapgears], contributor to [http://mapserver.org Mapserver] and [http://gdal.org GDAL/OGR].
# [[User:mikesaunt|Mike Saunt]], UK, Owner at [http://astuntechnology.com Astun Technology Ltd], OSGeo sponsor
# [[User:msmitherdc|Michael Smith]], OSGeo Charter Member, Physical Scientist US Army Corps of Engineers Remote Sensing GIS Center
# [[User:Kalxas|Angelos Tzotsos]], OSGeo Charter Member, Researcher at National Technical University of Athens
# [[User:Kimaidou|Michaël Douchin]], France, GIS consultant & software engineer at [http://3liz.com/ 3liz]
# [[User:PedroVenancio | Pedro Venâncio]], Portugal, GIS Analyst @ Municipality of Pinhel
# [[User:Jgrocha|Jorge Gustavo Rocha]], Portugal, GIS Professor at Universidade do Minho
# [[User:Danielkastl| Daniel Kastl]], Japan, [http://georepublic.info Georepublic], Founder
# [[Diodata|John Callahan]], US, Research Scientist and GIS/Remote Sensing Specialist, University of Delaware
# [[User:kjkalyan|Kalyan Janakiraman]], Senior Systems Analyst, Business Development Services, NSW Land and Property Information, Sydney, Australia
# [[User:goliadranger|Phillip Davis]], Director, National Geospatial Technology Center of Excellence, Texas, USA
# [[User:simonp|Simon Pigot]], contributor to and PSC member of [http://geonetwork-opensource.org GeoNetwork opensource] (speaking for myself, not an official view of my employer)
# [[User:jbryant|John Bryant]], Consultant, Mammoth Mapping, Dawson City, Canada and GIS/DB Admin, Jupiter Mines, Perth, Australia
# [[ChIossif|Christos Iossifides]], Remote Sensing Instructor, Laboratory Teaching Staff, Remote Sensing Instructor and Researcher, National Technical University of Athens
# [[User:tbowden|Tim Bowden]], Spatial Consultant, Perth, Australia
# [[User:Lucadelu|Luca Delucchi]], GIS Technician, Trento, Italy
# [[User:bartvde|Bart van den Eijnden]], GIS software developer, Utrecht, Netherlands
# [[User:eyedol|Henry Addo]], Software Developer at Ushahidi [http://ushahidi.com], contributor of [http://live.osgeo.org OSGeo-Live]
# [[User:iacovellas|Stefano Iacovella]], GIS consultant & software engineer, Rome, Italy
# [[User:Mtoonen| Meine Toonen]], Software Engineer @ [http://www.b3partners.nl B3Partners], The Netherlands
# [[User:arneke| Arne Kepp]], Software Engineer, Oslo, Norway
# [[User:Pirmin_Kalberer| Pirmin Kalberer]], Managing director [http://sourcepole.com/ Sourcepole], [http://fossgis.de FOSSGIS] member, Contributor of [http://gdal.org GDAL/OGR], [http://qgis.org QGIS], [http://mapfish.org/ Mapfish], [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS], [http://live.osgeo.org OSGeo-Live], Switzerland
# [[User:hdus| Dr. Horst Düster]], Managing director [http://sourcepole.com/ Sourcepole], [http://fossgis.de FOSSGIS] member, QGIS Project Treasurer and Contributor of [http://qgis.org QGIS], Zürich, Switzerland
# [[Richard_Duivenvoorde| Richard Duivenvoorde]], Managing director & software developer [http://www.webmapper.net/ Webmapper], QGIS community member
# [[User:stevenfeldman|Steven Feldman]], Principal at [http://knowwhereconslting.co.uk KnowWhere Consulting] and Chair of the LOC for [http://2013.foss4g.org/ FOSS4G 2013]
# [[Edward_Mac_Gillavry| Edward Mac Gillavry]], Managing director & software developer [http://www.webmapper.net/ Webmapper]
# [[User:maximdubinin| Maxim Dubinin]], CEO at [http://www.nextgis.org/ NextGIS], head of [http://gis-lab.info GIS-Lab.info]
# [[User:flavour| Fran Boon]], PMC Chair at [http://sahanafoundation.org/ Sahana Foundation], CTO of [http://aidiq.com AidIQ]
# [[User:Ian| Ian Edwards]], Chair [http://www.osgeo.org/uk OSGeo:UK]
# [[User:Bishop|Dmitriy Baryshnikov]] Developer at [http://www.nextgis.org/ NextGIS], [http://gdal.org GDAL/OGR] committer, [http://wxgis.googlecode.com wxGIS] developer, [http://gis-lab.info GIS-Lab.info] community member
# [[User:cvanlith| Chris van Lith]], Director [http://www.b3partners.nl B3Partners], member of [http://www.opengeogroep.nl OpenGeoGroep]
# [[User:VincentP| Vincent Picavet]], co-founder of [http://www.oslandia.com Oslandia], founding member and treasurer of OSGeo-FR
# [[User:Stefan_A._Tzeggai| Stefan A. Tzeggai]], creator of [http://www.geopublishing.org/AtlasStyler AtlasStyler SLD editor], founder of [http://www.empirica-systeme.de empirica systeme gmbh]
# [[User:Rdewit| Roald de Wit]], Geospatial Software Engineer, Melbourne, Australia
# [[User:grizonnetm| Manuel Grizonnet]], working at the [http://www.cnes.fr/ French Space Agency], [http://www.orfeo-toolbox.org/otb/ ORFEO ToolBox library] developer
# [[User:RdeMoritoru| Toru Mori]], President & CEO, [http://www.orkney.co.jp Orkney, Inc.], Yokohama, Japan, Representative of OSGeo Japan Chapter, OSGeo Charter Member
# [[User:MarkusSchneider2|Markus Schneider]], TMC chair of the [http://www.deegree.org deegree project], CEO of [http://www.occamlabs.de Occam Labs]
# [[User:elena|Elena Mezzini]], Remote Sensing and GIS Technician, GFOSS.it member, Bologna, Italy
# [[User:Alexbruy|Alexander Bruy]], [http://nextgis.org NextGIS], QGIS core developer
# [[User:Dfurtado | Danilo Furtado]], Portugal, OSGeo member, OSGeo-Portugal
# [[User:Stranger | Andreas Schmitz]], Germany, deegree core developer and TMC member, CTO of [http://www.occamlabs.de Occam Labs]
# [[User:Olt | Oliver Tonnhofer]], Germany, [http://mapproxy.org MapProxy] core developer, founder & CTO of [http://www.omniscale.com Omniscale]
# [[User:Thomas_Baschetti | Thomas Baschetti]], Germany, Freelancer, Mapbender PSC Member, [http://fossgis.de FOSSGIS] member
# [[User:IanMayo | Ian Mayo]], GeoSpatial developer, UK
# [[User:imincik | Ivan Mincik]], CEO of [http://www.gista.sk GISTA s.r.o.], Slovakia
# [[User:edmar.moretti | Edmar Moretti]], Software developer, [http://www.i3geo.com i3GEO] core developer, Brazil
# [[User:Moreira | Diego Moreira]], GIS Analyst, Contributor of [http://qgis.org QGIS], Brazil
# [[User:Ginetto | Luigi Pirelli]], Freelance Analyst/Programmer, co-founder of Italian OSGEO Local Chapter [http://www.gfoss.it GFOSS.it], Italy
# [[User:kyle | Kyle Shannon]] Software Developer, contributor of [http://gdal.org GDAL/OGR], United States
# [[User:DMateos | David Mateos]], worker member at [http://www.terrativa.net Terrativa S. Coop.] and OSGeo Spanish Local Chapter Member, Spain
# [[Luis Franco]], researcher and GIS analyst at the University of Santiago de Compostela, Spain
# [[User:groldan | Gabriel Roldan]], Software Developer, Argentina, OSGeo Charter Member, OSGeo Spanish Local Chapter Member
# [[User:kotzino | Dimitris Kotzinos]], OSGEO Charter Member, OSGEO Greek Chapter founder, Assistant Professor TEI of Serres, Greece
# [[User:Perriger|Stefan Steiniger]], owner of [http://www.geosteiniger.cl GEO Steiniger Ltda.], contributor to [http://openjump.org OpenJUMP GIS] and [http://www.opentripplanner.org OpenTripPlanner] and author of several FOSS4G overview articles, Canada/Chile
# [[User:Iwasaki | Nobusuke Iwasaki]], Senior Researcher, National Institute for Agro-Environmental Sciences, Tsukuba, Japan, OSGeo Japan Chapter Board Member
# [[User:Johnson | Ross Johnson]], Land Information Officer, City of Ryde Council and NSW Committee member of Surveying & Spatial Sciences Institute (SSSI)
# [[User:kumaran |Kumaran Narayanaswamy]], CEO & Managing Director of kCube Consultancy Services Pvt Ltd India.[http://www.kcubeconsulting.com], Member of India OSGeo Chapter.
# [[User:luis |Luis Fernando Bueno]], Professor at Federal University of Rondonia, researcher and GIS analyst, Brazil.
# [[User:MapperBob |Bob Bruce, FEC, P.Eng.]], Geomatics Engineer, Winnipeg, Manitoba, Canada.
# [[User:mlennert|Moritz Lennert]], Researcher in geography at the [http://www.ulb.ac.be/ Free University of Brussels (ULB)], [http://grass.osgeo.org GRASS-PSC]
# [[User:Ianturton|Ian Turton]], Software developer and open standards advocate, [http://geotools.org GeoTools-PSC]
# [[User:Djay|Gérald Fenoy]], OSGeo Charter member, Founder and CEO of GeoLabs SARL, France
# [[User:bitner|David Bitner]], OSGeo Charter member, OSGeo VP for Geodata, OSGeo Twin Cities Chapter, [http://sahanafoundation.org Sahana Software Foundation] Board of Directors, [http://www.metrogis.org MetroGIS] Coordinating Committee Chair, owner [http://dbspatial.com dbSpatial]
# [[User:Peter Loewe|Peter Löwe]], OSGeo Charter member, Senior Researcher at Deutsches GeoForschungsZentrum GFZ, General Manager GISIX.com
# [[User:gfleming|Gavin Fleming]], OSGeo Charter member, owner of AfriSpatial.
# [[User:FrankM|Frank Maes]], GeoICT professional, Head Operations at [http://www.geosparc.com Geosparc], Contributor & community member of [http://www.geomajas.org Geomajas], OSGeo member
# [[User:epifanio|Massimo Di Stefano]] , OSGeo Charter Member, Italy, founder-member of OSGeo Italian Local Chapter.

= Summary =

The OGC candidate standard titled "GeoServices REST API" is currently, in May 2013, being considered to be approved as an Open Geospatial Consortium (OGC) standard. The vote to accept the document as a standard is unusually contentious. The controversy is the cause of this open letter.

The candidate standard was previously released for public comment and can be found [http://www.opengeospatial.org/standards/requests/89 on the request for public comment page] (though public comment has been closed for now).

The candidate standard attempts to standardize a suite of web services such as a service which provides map images, a service which provides geospatial feature data, and a service which performs geospatial processing. The candidate standard focuses on interactions via a defined hierarchy of URLs and using predominantly a particular set of JSON schemas for the exchange of geospatial data.

== Criticism and Response ==

The '''criticism''' of the adoption of this particular document as an OGC Standard includes a wide variety of reasons such as:

* the OGC's process through which the document was developed which is thought to lack sufficient flexibility to respond to input from various stakeholders,
* the focus of the document on 'REST' and 'API' which is seen as not matching the ideas others have for these concepts,
* the names of the standard and of the services which are seen as potentially confusing,
* the functionality of the new services which are considered to duplicate that of existing services already standardized by the OGC such as WMS, WFS, WCS, and WPS,
* the addition of a new set of services based on new URL patterns and new JSON exchange formats which is seen as duplicating the efforts of other working groups bringing similar ideas to the updates of existing OGC services,
* the re-introduction in the new services of previously resolved interoperability issues which is seen as failing to build on the existing knowledge and experience,
* the use of the particular JSON schemas which are seen as having little industry acceptance and are incompatible with other widely used schemas, and
* the lack of implementation diversity which is thought to give the vendor of the one complete implementation an unusual commercial advantage on top of the vendor's already dominant position in the domain.

These issues have potential impacts on the use of 'Open Standards' by governments and companies, on the interoperability of software interacting with standards compliant OGC services, on the costs to developers and users of standards compliant software, on the understanding of 'Open Standards' by the public at large, and, possibly, on the reputation of the OGC as a champion of interoperability.

In particular there are concerns by some that adoption of the standard 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 prominence 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.

In '''response''' to these issues, the authors of the Geoservices REST API document have stated that:

* the process of the OGC has been followed completely,
* the specification actually is RESTful and does define an API,
* the name, due to the controversy, is open for modification
* the OGC does not forbid duplication of service functionality, already has duplication between the W*S and the S*S (sensor) family of standards, should not block progress in the name of 'one true way', and harmonization between the services can be considered in the future,
* the JSON format exists and functions, and
* there are alternative implementations for some of these services.

The authors also stress that the existence of a large user base shows the service is useful, and that the standardization of the services at the OGC may encourage new implementations.

The SWG has published two documents in response to various comments.
* [https://portal.opengeospatial.org/files/?artifact_id=54048 OGC 12-646 Response to RFC Comments] presents the responses from the Standards Working Group to the comments received from the public during the public Request for Comments (RFC).
* [https://portal.opengeospatial.org/files/?artifact_id=54049 OGC 13-031r1 Response to 'no' votes] presents the responses from the Standards Working Group to the reasons given by the organizations voting _no_ during the adoption vote.

Both are available through the links above, or via the [http://www.opengeospatial.org/projects/groups/gservrestswg public page] of the Standards Working Group.

= Positions on the vote =

The discussion raises a number of issues, many based upon complex technical concepts and implications. This makes it difficult for voting OGC members considering whether to support (or not) the "Geoservices REST API" as a standard. The following provides one analysis of the positions on the vote, aimed to simplify and summarize key points. However, it does not necessarily represent the opinions held by all signatories above.

; The pros for accepting the "Geoservices REST API" document as an OGC standard:

:* The OGC should be in the business of developing good standards, not in choosing which standards should be implemented.
:* The proposers of the document want to make a standard and have followed all the rules of the OGC. The work of any such group of members deserves serious, good faith consideration.
:* The need for an integrated suite of services using simple data, which is addressed (partially) by the document, is real. The proposed document is pushing the OGC on this issue.
:* The proposed document could be useful to a number of people.
:* The proposed document is not significantly more broken than the existing standards of the OGC. As one author of standards [http://lists.osgeo.org/pipermail/discuss/2013-May/011667.html notes]:
:''"I know how totally impossible it is to write a good standard, so the weaknesses in the existing document seem more acceptable."''

; The cons:

:* The OGC actually is, whether it should be or not, in the position of recommending interoperable standards for geospatial services. The proposed document is not good enough, has implementations dominated by one vendor's server implementation, and not publicly supported enough, to be considered at the same level as existing standards.
:* Adopting a standard implies a desire to maintain the standard, but OGC's desire to support this approach has been questioned by some. In particular, the lack of collaboration and willingness to accept recommendations from the community on this version of the "Geoservices REST API" document bodes ill for the future.
:* The overlap in functionality between the proposed services and the existing services, notably with the ongoing work to modularize the existing services, is almost 100 percent. However, compatibility is low.
:* There is already a published document: http://www.esri.com/library/whitepapers/pdfs/geoservices-rest-spec.pdf so there is no need for the document to be adopted as an OGC Standard merely for interoperability with the ESRI implementation.
:* The document, as a new, separate effort, repeats mistakes which were made and since solved by the other services.
:* The document focuses on the past (notably with backwards compatibility and use of only GET/POST) not on the future.
:* The document needs a comprehensive editorial review and substantial rewriting for clarity.

; A conclusion:

Both simple answers are bad.

A simple acceptance of the standard would introduce a new set of 'OGC approved' open services. The OGC approval might enable governments to buy a XXXX-new-name-here-XXXX solution instead of a W*S or a S*S solution. The path forwards towards harmonizing the services is unclear. Fixing this document in addition to fixing the W*S services will be a pain.

Simply rejecting the solution would be bad for the OGC. It would place the OGC in the position of picking winners and losers in the standards business. It would mean that the OGC is stuck on the project of fixing the W*S standards to meet some nebulous future functionality without having any path to get there. It would discourage innovation and progress.

Is there any third way?

Well, actually, there is a different way of thinking of the issue. Overall, there appears to be a shared desire for an integrated suite of geospatial services, originally focused on a simple data model, built on the exchange of well defined resources in simple formats including JSON, accessible and usable using the core HTTP verbs, and discoverable through following HTML links and patterns of URL paths. The hope is that such a suite can be designed based on the best expertise of the OGC, can be widely supported by the community, and can be implemented and tested by multiple groups. Neither the proposed document, nor the current services meet this vision. So the work, ultimately, is on improving all the services at the OGC, first to modularize them, then to enable simple implementations, and finally to link those implementations into a functional suite. Since this is the work that is already happening, perhaps the vote is an unfortunate distraction and the productive way forward is merely to redouble the efforts to create the next versions of the standards.

= Issues with the document =

Beyond the controversy described above, there are issues with the Geoservices REST API document itself. Even if the standard deserves support, these issues could be considered blockers to the adoption of the current, May 2013, document.

The critique is incomplete because it quickly falls into a full editorial review of the text, something which takes a lot of time and effort and is beyond the scope and intent of this Open Letter.

The critique can be found at: http://wiki.osgeo.org/wiki/Geoservices_REST_API_critique.

Note that some of these critiques hold the document to OGC's current, standards writing guidelines. The OGC has been striving to develop better standards so new standards must meet higher requirements than past standards. The lack of clarity in the proposed document is not substantially worse than many published standards but ought to be resolved in new standards.

= Further Concerns =

== Technical Concerns ==

* see [http://wiki.osgeo.org/wiki/Geoservices_REST_API_critique#The_Technical_Approach this discussion] for detailed arguments why OGC WCS is superior to the "GeoServices REST API" Part 6. It concludes:
: ''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 ==

* The Geoservices REST API can not be amended (other than editorial changes in the specification document), because of a requirement for backward compatibility with the ESRI implementation. This has limited improvements in this version of the candidate specification.

= Further Reading =
* Cameron Shorter's [http://lisasoft.com/blog/will-ogc%E2%80%99s-standards-meet-government-purchasing-guidelines Will OGC’s standards meet government purchasing guidelines?]
* Email archive of OSGeo discussions about GeoServices REST API: http://lists.osgeo.org/pipermail/discuss/2013-May/thread.html
* Adrian Custer's summary of technical issues (and original source of some content in this letter): http://lists.osgeo.org/pipermail/discuss/2013-May/011667.html
* "Is OGC Loosing its way?", letter to OGC Voters, from OGC Interoperability Movement Team Leaders, http://lists.osgeo.org/pipermail/discuss/2013-May/011632.html

* Call for comments on GeoServices REST API: http://www.opengeospatial.org/standards/requests/89
* Responses from the Standards Working Group to the comments received from the public during the public Request for Comments (RFC): [[file:OGC_12-642_GeoServices_REST_API_-_RFC_Comments_Response.pdf|OGC 12-646 Response to RFC Comments]]
* Responses from the Standards Working Group to the reasons given by the organizations voting _no_ during the adoption vote: [[file:OGC_13-031r1_GeoServices_REST_API_-_Response_to_no_votes_r1.pdf|OGC 13-031r1 Response to 'no' votes]]

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

Geoservices REST API

2013-05-13T07:26:45Z

Wiki-Hdus: /* Signed */

This wiki page aims to collate community concerns related to the adoption of the "Geoservices REST API" document as a standard of the [http://www.opengeospatial.org/ Open Geospatial Consortium (OGC)]. The page is being collaboratively edited, targeting completion by Wednesday 15 May 2013, after which it will be delivered by the board of the [http://osgeo.org OSGeo Foundation (OSGeo)] to the OGC and OGC voting members.

= Cover Letter from the OSGeo Board =
''Please don't edit this "Cover Letter" statement, which has been approved by the OSGeo Board.''

The board of the [http://osgeo.org Open Source Geospatial Foundation] (OSGeo) is presenting this letter to the OGC. It highlights concerns about the "GeoServices REST API" from many people within the OSGeo community. As always, if there is anything the OSGeo board can do to help, then please let us know.

Signed: Jeff McKenna (OSGeo president),
Peter Batty,
Jáchym Čepický,
Michael Gerlek,
Anne Ghisla,
Mark Lucas,
Daniel Morissette,
Cameron Shorter,
Frank Warmerdam

= Open Letter to OGC and voting members =

''Please don't edit this "Open Letter" statement, comments and discussion should go in the "Further Concerns" section 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], OSGeo Board member
# [[Mark Lucas]], Founding member and board of directors for OSGeo foundation, Principal 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, Post-doctoral researcher at the European Commission, JRC, 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
# [[User:vasile |Vasile Craciunescu]], OSGeo Charter member, OSGeo Romania Local Chapter Leader, Researcher at Romanian National Meteorological Administration, Romania
# [[User:badaveil |Abbas Abdul Wahab]], Asst. Director, Federal Department of Town & Country Planning, Peninsular Malaysia
# [[User:rbraam | Roy Braam]], Software Engineer @ [http://www.b3partners.nl | B3Partners]
# [[User:peteris | Peteris Bruns]], Latvia, GIS Consultant & Software Engineer @ [http://www.sungis.lv | SunGIS]
# [[User:Lutra | Giovanni Manghi]], Portugal, [http://www.faunalia.pt Faunalia], OSGeo member, OSGeo-Portugal
# [[User:Hfpmartins | Hugo Martins]], UK, [http://www.lutraconsulting.co.uk Lutra Consulting], WebGIS Developer, OSGeo-Portugal Member
# [[User:Sabb | Saber Razmjooei]], UK, [http://www.lutraconsulting.co.uk Lutra Consulting], Co-Founder
# [[User:Wellsp | Peter Wells]], UK, [http://www.lutraconsulting.co.uk Lutra Consulting], Co-Founder
# [[User:SGijzen | Sidney Gijzen]], The Netherlands, Researcher GIS @ [http://www.wageningenur.nl/en/Expertise-Services/Research-Institutes/alterra.htm Alterra, Wageningen UR]
# [[User:mfidelman | Miles Fidelman]], US, Principal, Protocol Technologies Group, LLC
# [[User:punkish | Puneet Kishor]], OSGeo Charter Member; [http://www.geology.wisc.edu Geology, Univ. of Wisconsin-Madison]; [http://creativecommons.org/staff#puneetkishor Creative Commons]
# [[User:Toze | António José Silva]], Portugal, GIS Consultant, OSGeo-Portugal Member
# [[User:AndreMano | AndreMano]], Portugal, Natural History Society - GIS Department, OSGeo-Portugal Member
# [[User:maurimiranda|Mauricio Miranda]], Argentina, OSGeo Charter Member, OSGeo Spanish Local Chapter Board Member
# [[User:pmachado|Paulo Machado]], Portugal, Software Engineer @ PT Inovação
# [[User:alvaro|Alvaro Anguix]], Spain, General Manager at [http://www.gvsig.com gvSIG Association]
# [[Santiago Higuera]], CEO at [http://Mercatorlab.com Mercatorlab], OSGeo Spanish Local Chapter Board Member, Spain
# [[Alan Boudreault]], Developer at [http://mapgears.com/ Mapgears], contributor to [http://mapserver.org Mapserver] and [httpo://gdal.org GDAL/OGR].
# [[User:mikesaunt|Mike Saunt]], UK, Owner at [http://astuntechnology.com Astun Technology Ltd], OSGeo sponsor
# [[User:msmitherdc|Michael Smith]], OSGeo Charter Member, Physical Scientist US Army Corps of Engineers Remote Sensing GIS Center
# [[User:Kalxas|Angelos Tzotsos]], OSGeo Charter Member, Researcher at National Technical University of Athens
# [[User:Kimaidou|Michaël Douchin]], France, GIS consultant & software engineer at [http://3liz.com/ 3liz]
# [[User:PedroVenancio | Pedro Venâncio]], Portugal, GIS Analyst @ Municipality of Pinhel
# [[User:Jgrocha|Jorge Gustavo Rocha]], Portugal, GIS Professor at Universidade do Minho
# [[User:Danielkastl| Daniel Kastl]], Japan, [http://georepublic.info Georepublic], Founder
# [[Diodata|John Callahan]], US, Research Scientist and GIS/Remote Sensing Specialist, University of Delaware
# [[User:kjkalyan|Kalyan Janakiraman]], Senior Systems Analyst, Business Development Services, NSW Land and Property Information, Sydney, Australia
# [[User:goliadranger|Phillip Davis]], Director, National Geospatial Technology Center of Excellence, Texas, USA
# [[User:simonp|Simon Pigot]], contributor to and PSC member of [http://geonetwork-opensource.org GeoNetwork opensource] (speaking for myself, not an official view of my employer)
# [[User:jbryant|John Bryant]], Consultant, Mammoth Mapping, Dawson City, Canada and GIS/DB Admin, Jupiter Mines, Perth, Australia
# [[ChIossif|Christos Iossifides]], Remote Sensing Instructor, Laboratory Teaching Staff, Remote Sensing Instructor and Researcher, National Technical University of Athens
# [[User:tbowden|Tim Bowden]], Spatial Consultant, Perth, Australia
# [[User:Lucadelu|Luca Delucchi]], GIS Technician, Trento, Italy
# [[User:bartvdenl|Bart van den Eijnden]], GIS software developer, Utrecht, Netherlands
# [[User:eyedol|Henry Addo]], Software Developer at Ushahidi [http://ushahidi.com], contributor of [http://live.osgeo.org OSGeo-Live]
# [[User:iacovellas|Stefano Iacovella]], GIS consultant & software engineer, Rome, Italy
# [[User:Mtoonen| Meine Toonen]], Software Engineer @ [http://www.b3partners.nl B3Partners], The Netherlands
# [[User:arneke| Arne Kepp]], Software Engineer, Oslo, Norway
# [[User:Pirmin_Kalberer| Pirmin Kalberer]], Managing director [http://sourcepole.com/ Sourcepole], [http://fossgis.de FOSSGIS] member, Contributor of [http://gdal.org GDAL/OGR], [http://qgis.org QGIS], [http://mapfish.org/ Mapfish], [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS], [http://live.osgeo.org OSGeo-Live], Switzerland
# [[User:hdus| Dr. Horst Düster]], Managing director [http://sourcepole.com/ Sourcepole], [http://fossgis.de FOSSGIS] member, Treasurer QGIS Project [http://qgis.org QGIS], Zürich, Switzerland

= Summary =

''Please don't edit this section - it is now locked to ensure editorial review. You may send comments to Cameron Shorter AT gmail .com''

The document titled "GeoServices REST API" is currently, in May 2013, being considered to be included as one of the Open Geospatial Consortium (OGC) standards. The vote to accept the document as a standard is unusually contentious; the controversy is the cause of this page.

The document was previously released for public comment and can be found [http://www.opengeospatial.org/standards/requests/89 on the request for public comment page] (though public comment has been closed for now).

The document attempts to standardize a suite of web services such as a service which provides map images, a service which provides geospatial feature data, and a service which performs geospatial processing. The standard focuses on interactions via a defined hierarchy of URLs and using predominantly a particular set of JSON schemas for the exchange of geospatial data.

== Criticism and Response ==

The adoption of the document as an OGC Standard is contentious for a wide variety of reasons including:

* the process through which the document was developed which is thought to lack sufficient flexibility to respond to input from various stakeholders,
* the focus of the document on 'REST' and 'API' which is seen as not matching the ideas others have for these concepts,
* the names of the standard and of the services which are seen as potentially confusing,
* the functionality of the new services which are considered to duplicate that of existing services already standardized by the OGC such as WMS, WFS, WCS, and WPS,
* the addition of a new set of services based on new URL patterns and new JSON exchange formats which is seen as duplicating the efforts of other working groups bringing similar ideas to the updates of existing OGC services,
* the re-introduction in the new services of previously resolved interoperability issues which is seen as failing to build on the existing knowledge and experience,
* the use of the particular JSON schemas which are seen as having little industry acceptance and are incompatible with other widely used schemas, and
* the lack of implementation diversity which is thought to give the vendor of the one complete implementation an unusual commercial advantage on top of the vendor's already dominant position in the domain.

These issues have potential impacts on the use of 'Open Standards' by governments and companies, on the interoperability of software interacting with standards compliant OGC services, on the costs to developers and users of standards compliant software, on the understanding of 'Open Standards' by the public at large, and, possibly, on the reputation of the OGC as a champion of interoperability.

In particular there are concerns by some that adoption of the standard 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.

In response to these issues, the authors of the Geoservices REST API document have stated that:

* the process of the OGC has been followed completely,
* the specification actually is RESTful and does define an API,
* the name, due to the controversy, may be open for modification
* the OGC does not forbid duplication of service functionality, already has duplication between the W*S and the S*S (sensor) family of standards, should not block progress in the name of 'one true way', and harmonization between the services can be considered in the future,
* the JSON format exists and functions, and
* there are alternative implementations for some of these services.

The authors also stress that the existence of a large user base shows the service is useful, and that the standardization of the services at the OGC may encourage new implementations.

= Positions on the vote =
''Please don't edit this section - it is now locked to ensure editorial review. You may send comments to Cameron Shorter AT gmail .com''

The discussion raises a number of issues, many based upon complex technical concepts and implications. This makes it difficult for voting OGC members considering whether to support "Geoservices REST API" as a standard. The following provides one analysis of the positions on the vote, aimed to simplify and summarize key points. However, it does not necessarily represent the opinions held by all signatories above.

; The pros for accepting the "Geoservices REST API" document as an OGC standard:

:* The OGC should be in the business of developing good standards, not in choosing which standards should be implemented.
:* The proposers of the document want to make a standard and have followed all the rules of the OGC. The work of any such group of members deserves serious, good faith consideration.
:* The need for an integrated suite of services using simple data, which is addressed (partially) by the document, is real. The proposed document is pushing the OGC on this issue.
:* The proposed document could be useful to a number of people.
:* The proposed document is not significantly more broken than the existing standards of the OGC. As one author of standards [http://lists.osgeo.org/pipermail/discuss/2013-May/011667.html notes]:
:''"I know how totally impossible it is to write a good standard, so the weaknesses in the existing document seem more acceptable."''

; The cons:

:* The OGC actually is, whether it should be or not, in the position of recommending interoperable standards for geospatial services. The proposed document is not good enough, not widely enough implemented, and not publicly supported enough, to be considered at the same level as existing standards.
:* Adopting a standard implies a desire to maintain the standard, but OGC's desire to support this approach has been questioned by some. In particular, the lack of collaboration and willingness to accept recommendations from the community on this version of the "Geoservices REST API" document bodes ill for the future.
:* The overlap in functionality between the proposed services and the existing services, notably with the ongoing work to modularize the existing services, is almost 100 percent. However, compatibility is low.
:* There is already a published document: http://www.esri.com/library/whitepapers/pdfs/geoservices-rest-spec.pdf so there is no need for the document to be adopted as an OGC Standard merely for interoperability with the ESRI implementation.
:* The document, as a new, separate effort, repeats mistakes which were made and since solved by the other services.
:* The document focuses on the past (notably with backwards compatibility and use of only GET/POST) not on the future.
:* The document needs a comprehensive editorial review and substantial rewriting for clarity.

; A conclusion:

Both simple answers are bad.

A simple acceptance of the standard would introduce a new set of 'OGC approved' open services. The OGC approval might enable governments to buy a XXXX-new-name-here-XXXX solution instead of a W*S or a S*S solution. The path forwards towards harmonizing the services is unclear. Fixing this document in addition to fixing the W*S services will be a pain.

Simply rejecting the solution would be bad for the OGC. It would place the OGC in the position of picking winners and losers in the standards business. It would mean that the OGC is stuck on the project of fixing the W*S standards to meet some nebulous future functionality without having any path to get there. It would discourage innovation and progress.

Is there any third way?

Well, actually, there is a different way of thinking of the issue. Overall, there appears to be a shared desire for an integrated suite of geospatial services, originally focused on a simple data model, built on the exchange of well defined resources in simple formats including JSON, accessible and usable using the core HTTP verbs, and discoverable through following HTML links and patterns of URL paths. The hope is that such a suite can be designed based on the best expertise of the OGC, can be widely supported by the community, and can be implemented and tested by multiple groups. Neither the proposed document, nor the current services meet this vision. So the work, ultimately, is on improving all the services at the OGC, first to modularize them, then to enable simple implementations, and finally to link those implementations into a functional suite. Since this is the work that is already happening, perhaps the vote is an unfortunate distraction and the productive way forward is merely to redouble the efforts to create the next versions of the standards.

= Issues with the document =

''Please don't edit this section - it is now locked to ensure editorial review. You may send comments to Cameron Shorter AT gmail .com''

Beyond the controversy described above, there are issues with the Geoservices REST API document itself. Even if the standard deserves support, these issues could be considered blockers to the adoption of the current, May 2013, document.

The critique is incomplete because it quickly falls into a full editorial review of the text, something which takes a lot of time and effort and is beyond the scope and intent of this Open Letter.

The critique can be found at: http://wiki.osgeo.org/wiki/Geoservices_REST_API_critique.

Note that some of these critiques hold the document to OGC's current, standards writing guidelines. The OGC has been striving to develop better standards so new standards must meet higher requirements than past standards. The lack of clarity in the proposed document is not substantially worse than many published standards but ought to be resolved in new standards.

= Further Concerns =
--- DRAFT ____

''Please add concerns not addressed above as bullet points below. Where appropriate, link to external web pages (such as email achieves). Try to be concise, and try not to repeat concepts which have been covered above, (less words get read by more people). Points you have previously added, which are now covered above should be removed. Words that have been struck out will be removed by Tuesday 14 May.''

== Political Concerns ==

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

== Commercial Concerns ==

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

== Technical Concerns ==

* <strike>The Geoservices REST API overlaps in large proportion with existing OGC standards such as WMS, WCS, WFS, WMTS, CSW, with no effort made to reconcile with those standards.</strike>
* 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.
* <strike>The Geoservices REST API is not particularly RESTful - it's a thinly disguised service call, not an address space for RESTful objects that can be operated on.</strike>
* see [http://wiki.osgeo.org/wiki/Geoservices_REST_API_critique#The_Technical_Approach this discussion] for detailed arguments why OGC WCS is superior to the "GeoServices REST API" Part 6. It concludes: ''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 ==

# Ten months after submitting, no public response (nor private to the authors of the comments) has been made to the various comments sent on the OGC Requests mailing list in [[http://lists.opengeospatial.org/pipermail/requests/2012-July/date.html July 2012]] and [[http://lists.opengeospatial.org/pipermail/requests/2012-August/date.html August 2012]] during the 30 day public comments period.
# 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.

A response (from Adrian Custer):

# The OGC is working to release those documents to the public as of 9 May 2013.
# Work on the next version of the document can take any perspective acceptable to those working on the document. (The OGC has no method in place in case two groups want to evolve the document in two different directions.)
# That is not true, the OGC does not require interoperability experiments or some "richer process" for the adoption of a standard; that may be desirable but is not required.

= Further Reading =
''Please add links to referenced documents, related news stories or blog posts here.''
* Call for comments on GeoServices REST API: http://www.opengeospatial.org/standards/requests/89
* Email archive of OSGeo discussions about GeoServices REST API: http://lists.osgeo.org/pipermail/discuss/2013-May/thread.html
* Adrian Custer's summary of technical issues (and original source of some content in this letter): http://lists.osgeo.org/pipermail/discuss/2013-May/011667.html
* "Is OGC Loosing its way?", letter to OGC Voters, from OGC Interoperability Movement Team Leaders, http://lists.osgeo.org/pipermail/discuss/2013-May/011632.html

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

Geoservices REST API

2013-05-13T07:25:53Z

Wiki-Hdus: /* Signed */

This wiki page aims to collate community concerns related to the adoption of the "Geoservices REST API" document as a standard of the [http://www.opengeospatial.org/ Open Geospatial Consortium (OGC)]. The page is being collaboratively edited, targeting completion by Wednesday 15 May 2013, after which it will be delivered by the board of the [http://osgeo.org OSGeo Foundation (OSGeo)] to the OGC and OGC voting members.

= Cover Letter from the OSGeo Board =
''Please don't edit this "Cover Letter" statement, which has been approved by the OSGeo Board.''

The board of the [http://osgeo.org Open Source Geospatial Foundation] (OSGeo) is presenting this letter to the OGC. It highlights concerns about the "GeoServices REST API" from many people within the OSGeo community. As always, if there is anything the OSGeo board can do to help, then please let us know.

Signed: Jeff McKenna (OSGeo president),
Peter Batty,
Jáchym Čepický,
Michael Gerlek,
Anne Ghisla,
Mark Lucas,
Daniel Morissette,
Cameron Shorter,
Frank Warmerdam

= Open Letter to OGC and voting members =

''Please don't edit this "Open Letter" statement, comments and discussion should go in the "Further Concerns" section 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], OSGeo Board member
# [[Mark Lucas]], Founding member and board of directors for OSGeo foundation, Principal 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, Post-doctoral researcher at the European Commission, JRC, 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
# [[User:vasile |Vasile Craciunescu]], OSGeo Charter member, OSGeo Romania Local Chapter Leader, Researcher at Romanian National Meteorological Administration, Romania
# [[User:badaveil |Abbas Abdul Wahab]], Asst. Director, Federal Department of Town & Country Planning, Peninsular Malaysia
# [[User:rbraam | Roy Braam]], Software Engineer @ [http://www.b3partners.nl | B3Partners]
# [[User:peteris | Peteris Bruns]], Latvia, GIS Consultant & Software Engineer @ [http://www.sungis.lv | SunGIS]
# [[User:Lutra | Giovanni Manghi]], Portugal, [http://www.faunalia.pt Faunalia], OSGeo member, OSGeo-Portugal
# [[User:Hfpmartins | Hugo Martins]], UK, [http://www.lutraconsulting.co.uk Lutra Consulting], WebGIS Developer, OSGeo-Portugal Member
# [[User:Sabb | Saber Razmjooei]], UK, [http://www.lutraconsulting.co.uk Lutra Consulting], Co-Founder
# [[User:Wellsp | Peter Wells]], UK, [http://www.lutraconsulting.co.uk Lutra Consulting], Co-Founder
# [[User:SGijzen | Sidney Gijzen]], The Netherlands, Researcher GIS @ [http://www.wageningenur.nl/en/Expertise-Services/Research-Institutes/alterra.htm Alterra, Wageningen UR]
# [[User:mfidelman | Miles Fidelman]], US, Principal, Protocol Technologies Group, LLC
# [[User:punkish | Puneet Kishor]], OSGeo Charter Member; [http://www.geology.wisc.edu Geology, Univ. of Wisconsin-Madison]; [http://creativecommons.org/staff#puneetkishor Creative Commons]
# [[User:Toze | António José Silva]], Portugal, GIS Consultant, OSGeo-Portugal Member
# [[User:AndreMano | AndreMano]], Portugal, Natural History Society - GIS Department, OSGeo-Portugal Member
# [[User:maurimiranda|Mauricio Miranda]], Argentina, OSGeo Charter Member, OSGeo Spanish Local Chapter Board Member
# [[User:pmachado|Paulo Machado]], Portugal, Software Engineer @ PT Inovação
# [[User:alvaro|Alvaro Anguix]], Spain, General Manager at [http://www.gvsig.com gvSIG Association]
# [[Santiago Higuera]], CEO at [http://Mercatorlab.com Mercatorlab], OSGeo Spanish Local Chapter Board Member, Spain
# [[Alan Boudreault]], Developer at [http://mapgears.com/ Mapgears], contributor to [http://mapserver.org Mapserver] and [httpo://gdal.org GDAL/OGR].
# [[User:mikesaunt|Mike Saunt]], UK, Owner at [http://astuntechnology.com Astun Technology Ltd], OSGeo sponsor
# [[User:msmitherdc|Michael Smith]], OSGeo Charter Member, Physical Scientist US Army Corps of Engineers Remote Sensing GIS Center
# [[User:Kalxas|Angelos Tzotsos]], OSGeo Charter Member, Researcher at National Technical University of Athens
# [[User:Kimaidou|Michaël Douchin]], France, GIS consultant & software engineer at [http://3liz.com/ 3liz]
# [[User:PedroVenancio | Pedro Venâncio]], Portugal, GIS Analyst @ Municipality of Pinhel
# [[User:Jgrocha|Jorge Gustavo Rocha]], Portugal, GIS Professor at Universidade do Minho
# [[User:Danielkastl| Daniel Kastl]], Japan, [http://georepublic.info Georepublic], Founder
# [[Diodata|John Callahan]], US, Research Scientist and GIS/Remote Sensing Specialist, University of Delaware
# [[User:kjkalyan|Kalyan Janakiraman]], Senior Systems Analyst, Business Development Services, NSW Land and Property Information, Sydney, Australia
# [[User:goliadranger|Phillip Davis]], Director, National Geospatial Technology Center of Excellence, Texas, USA
# [[User:simonp|Simon Pigot]], contributor to and PSC member of [http://geonetwork-opensource.org GeoNetwork opensource] (speaking for myself, not an official view of my employer)
# [[User:jbryant|John Bryant]], Consultant, Mammoth Mapping, Dawson City, Canada and GIS/DB Admin, Jupiter Mines, Perth, Australia
# [[ChIossif|Christos Iossifides]], Remote Sensing Instructor, Laboratory Teaching Staff, Remote Sensing Instructor and Researcher, National Technical University of Athens
# [[User:tbowden|Tim Bowden]], Spatial Consultant, Perth, Australia
# [[User:Lucadelu|Luca Delucchi]], GIS Technician, Trento, Italy
# [[User:bartvdenl|Bart van den Eijnden]], GIS software developer, Utrecht, Netherlands
# [[User:eyedol|Henry Addo]], Software Developer at Ushahidi [http://ushahidi.com], contributor of [http://live.osgeo.org OSGeo-Live]
# [[User:iacovellas|Stefano Iacovella]], GIS consultant & software engineer, Rome, Italy
# [[User:Mtoonen| Meine Toonen]], Software Engineer @ [http://www.b3partners.nl B3Partners], The Netherlands
# [[User:arneke| Arne Kepp]], Software Engineer, Oslo, Norway
# [[User:Pirmin_Kalberer| Pirmin Kalberer]], Managing director [http://sourcepole.com/ Sourcepole], [http://fossgis.de FOSSGIS] member, Contributor of [http://gdal.org GDAL/OGR], [http://qgis.org QGIS], [http://mapfish.org/ Mapfish], [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS], [http://live.osgeo.org OSGeo-Live], Switzerland
# [[User:hdus| Dr. Horst Düster]], Managing director [http://sourcepole.com/ Sourcepole], [http://fossgis.de FOSSGIS] member, Treasurer QGIS Project [http://qgis.org QGIS] Switzerland

= Summary =

''Please don't edit this section - it is now locked to ensure editorial review. You may send comments to Cameron Shorter AT gmail .com''

The document titled "GeoServices REST API" is currently, in May 2013, being considered to be included as one of the Open Geospatial Consortium (OGC) standards. The vote to accept the document as a standard is unusually contentious; the controversy is the cause of this page.

The document was previously released for public comment and can be found [http://www.opengeospatial.org/standards/requests/89 on the request for public comment page] (though public comment has been closed for now).

The document attempts to standardize a suite of web services such as a service which provides map images, a service which provides geospatial feature data, and a service which performs geospatial processing. The standard focuses on interactions via a defined hierarchy of URLs and using predominantly a particular set of JSON schemas for the exchange of geospatial data.

== Criticism and Response ==

The adoption of the document as an OGC Standard is contentious for a wide variety of reasons including:

* the process through which the document was developed which is thought to lack sufficient flexibility to respond to input from various stakeholders,
* the focus of the document on 'REST' and 'API' which is seen as not matching the ideas others have for these concepts,
* the names of the standard and of the services which are seen as potentially confusing,
* the functionality of the new services which are considered to duplicate that of existing services already standardized by the OGC such as WMS, WFS, WCS, and WPS,
* the addition of a new set of services based on new URL patterns and new JSON exchange formats which is seen as duplicating the efforts of other working groups bringing similar ideas to the updates of existing OGC services,
* the re-introduction in the new services of previously resolved interoperability issues which is seen as failing to build on the existing knowledge and experience,
* the use of the particular JSON schemas which are seen as having little industry acceptance and are incompatible with other widely used schemas, and
* the lack of implementation diversity which is thought to give the vendor of the one complete implementation an unusual commercial advantage on top of the vendor's already dominant position in the domain.

These issues have potential impacts on the use of 'Open Standards' by governments and companies, on the interoperability of software interacting with standards compliant OGC services, on the costs to developers and users of standards compliant software, on the understanding of 'Open Standards' by the public at large, and, possibly, on the reputation of the OGC as a champion of interoperability.

In particular there are concerns by some that adoption of the standard 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.

In response to these issues, the authors of the Geoservices REST API document have stated that:

* the process of the OGC has been followed completely,
* the specification actually is RESTful and does define an API,
* the name, due to the controversy, may be open for modification
* the OGC does not forbid duplication of service functionality, already has duplication between the W*S and the S*S (sensor) family of standards, should not block progress in the name of 'one true way', and harmonization between the services can be considered in the future,
* the JSON format exists and functions, and
* there are alternative implementations for some of these services.

The authors also stress that the existence of a large user base shows the service is useful, and that the standardization of the services at the OGC may encourage new implementations.

= Positions on the vote =
''Please don't edit this section - it is now locked to ensure editorial review. You may send comments to Cameron Shorter AT gmail .com''

The discussion raises a number of issues, many based upon complex technical concepts and implications. This makes it difficult for voting OGC members considering whether to support "Geoservices REST API" as a standard. The following provides one analysis of the positions on the vote, aimed to simplify and summarize key points. However, it does not necessarily represent the opinions held by all signatories above.

; The pros for accepting the "Geoservices REST API" document as an OGC standard:

:* The OGC should be in the business of developing good standards, not in choosing which standards should be implemented.
:* The proposers of the document want to make a standard and have followed all the rules of the OGC. The work of any such group of members deserves serious, good faith consideration.
:* The need for an integrated suite of services using simple data, which is addressed (partially) by the document, is real. The proposed document is pushing the OGC on this issue.
:* The proposed document could be useful to a number of people.
:* The proposed document is not significantly more broken than the existing standards of the OGC. As one author of standards [http://lists.osgeo.org/pipermail/discuss/2013-May/011667.html notes]:
:''"I know how totally impossible it is to write a good standard, so the weaknesses in the existing document seem more acceptable."''

; The cons:

:* The OGC actually is, whether it should be or not, in the position of recommending interoperable standards for geospatial services. The proposed document is not good enough, not widely enough implemented, and not publicly supported enough, to be considered at the same level as existing standards.
:* Adopting a standard implies a desire to maintain the standard, but OGC's desire to support this approach has been questioned by some. In particular, the lack of collaboration and willingness to accept recommendations from the community on this version of the "Geoservices REST API" document bodes ill for the future.
:* The overlap in functionality between the proposed services and the existing services, notably with the ongoing work to modularize the existing services, is almost 100 percent. However, compatibility is low.
:* There is already a published document: http://www.esri.com/library/whitepapers/pdfs/geoservices-rest-spec.pdf so there is no need for the document to be adopted as an OGC Standard merely for interoperability with the ESRI implementation.
:* The document, as a new, separate effort, repeats mistakes which were made and since solved by the other services.
:* The document focuses on the past (notably with backwards compatibility and use of only GET/POST) not on the future.
:* The document needs a comprehensive editorial review and substantial rewriting for clarity.

; A conclusion:

Both simple answers are bad.

A simple acceptance of the standard would introduce a new set of 'OGC approved' open services. The OGC approval might enable governments to buy a XXXX-new-name-here-XXXX solution instead of a W*S or a S*S solution. The path forwards towards harmonizing the services is unclear. Fixing this document in addition to fixing the W*S services will be a pain.

Simply rejecting the solution would be bad for the OGC. It would place the OGC in the position of picking winners and losers in the standards business. It would mean that the OGC is stuck on the project of fixing the W*S standards to meet some nebulous future functionality without having any path to get there. It would discourage innovation and progress.

Is there any third way?

Well, actually, there is a different way of thinking of the issue. Overall, there appears to be a shared desire for an integrated suite of geospatial services, originally focused on a simple data model, built on the exchange of well defined resources in simple formats including JSON, accessible and usable using the core HTTP verbs, and discoverable through following HTML links and patterns of URL paths. The hope is that such a suite can be designed based on the best expertise of the OGC, can be widely supported by the community, and can be implemented and tested by multiple groups. Neither the proposed document, nor the current services meet this vision. So the work, ultimately, is on improving all the services at the OGC, first to modularize them, then to enable simple implementations, and finally to link those implementations into a functional suite. Since this is the work that is already happening, perhaps the vote is an unfortunate distraction and the productive way forward is merely to redouble the efforts to create the next versions of the standards.

= Issues with the document =

''Please don't edit this section - it is now locked to ensure editorial review. You may send comments to Cameron Shorter AT gmail .com''

Beyond the controversy described above, there are issues with the Geoservices REST API document itself. Even if the standard deserves support, these issues could be considered blockers to the adoption of the current, May 2013, document.

The critique is incomplete because it quickly falls into a full editorial review of the text, something which takes a lot of time and effort and is beyond the scope and intent of this Open Letter.

The critique can be found at: http://wiki.osgeo.org/wiki/Geoservices_REST_API_critique.

Note that some of these critiques hold the document to OGC's current, standards writing guidelines. The OGC has been striving to develop better standards so new standards must meet higher requirements than past standards. The lack of clarity in the proposed document is not substantially worse than many published standards but ought to be resolved in new standards.

= Further Concerns =
--- DRAFT ____

''Please add concerns not addressed above as bullet points below. Where appropriate, link to external web pages (such as email achieves). Try to be concise, and try not to repeat concepts which have been covered above, (less words get read by more people). Points you have previously added, which are now covered above should be removed. Words that have been struck out will be removed by Tuesday 14 May.''

== Political Concerns ==

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

== Commercial Concerns ==

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

== Technical Concerns ==

* <strike>The Geoservices REST API overlaps in large proportion with existing OGC standards such as WMS, WCS, WFS, WMTS, CSW, with no effort made to reconcile with those standards.</strike>
* 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.
* <strike>The Geoservices REST API is not particularly RESTful - it's a thinly disguised service call, not an address space for RESTful objects that can be operated on.</strike>
* see [http://wiki.osgeo.org/wiki/Geoservices_REST_API_critique#The_Technical_Approach this discussion] for detailed arguments why OGC WCS is superior to the "GeoServices REST API" Part 6. It concludes: ''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 ==

# Ten months after submitting, no public response (nor private to the authors of the comments) has been made to the various comments sent on the OGC Requests mailing list in [[http://lists.opengeospatial.org/pipermail/requests/2012-July/date.html July 2012]] and [[http://lists.opengeospatial.org/pipermail/requests/2012-August/date.html August 2012]] during the 30 day public comments period.
# 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.

A response (from Adrian Custer):

# The OGC is working to release those documents to the public as of 9 May 2013.
# Work on the next version of the document can take any perspective acceptable to those working on the document. (The OGC has no method in place in case two groups want to evolve the document in two different directions.)
# That is not true, the OGC does not require interoperability experiments or some "richer process" for the adoption of a standard; that may be desirable but is not required.

= Further Reading =
''Please add links to referenced documents, related news stories or blog posts here.''
* Call for comments on GeoServices REST API: http://www.opengeospatial.org/standards/requests/89
* Email archive of OSGeo discussions about GeoServices REST API: http://lists.osgeo.org/pipermail/discuss/2013-May/thread.html
* Adrian Custer's summary of technical issues (and original source of some content in this letter): http://lists.osgeo.org/pipermail/discuss/2013-May/011667.html
* "Is OGC Loosing its way?", letter to OGC Voters, from OGC Interoperability Movement Team Leaders, http://lists.osgeo.org/pipermail/discuss/2013-May/011632.html

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

User:Hdus

2010-09-02T17:54:50Z

Wiki-Hdus: /* Open Source Geospatial project involvements */

Dr. Horst Düster 

Solothurn / Switzerland

horst dot duester at kappasys dot ch 
http://www.kappasys.ch

== Open Source Geospatial project involvements ==

* [http://www.sogis.ch SO!GIS]: Responsible for the 100% FOSSGIS stack of the state of Solothurn with more than 3500 clients since 2001.
* [http://qgis.org/ QGIS]: Plugin contributions: [http://www.kappasys.ch/qgis/plugins.xml Geoprocessing, WPS-Client, PostGIS Query Editor].
* [http://www.kappasys.ch/pgtools/cleangeometry/cleanGeometry.sql cleanGeometry.sql]: PgSQL-Function to remove self-intersections from PostGIS LINESTRING and POLYGON geometries.
* [http://www.kappasys.ch/pgtools/pghistory/index.html PostGIS Historisation]: Two approaches for historisation of PostGIS data.
* PgVersion: PostGIS-Versioning System for concurrent editing of PostGIS-Layers (coming soon)

User:Hdus

2010-09-02T17:27:36Z

Wiki-Hdus: /* Open Source Geospatial project involvements */

Dr. Horst Düster 

Solothurn / Switzerland

horst dot duester at kappasys dot ch 
http://www.kappasys.ch

== Open Source Geospatial project involvements ==

* [http://www.sogis.ch SO!GIS]: Responsible for the 100% FOSSGIS stack of the state of Solothurn with more than 3500 clients since 2001.
* [http://qgis.org/ QGIS]: Plugin contributions: Geoprocessing, WPS-Client, PostGIS Query Editor.
* [http://www.kappasys.ch/pgtools/cleangeometry/cleanGeometry.sql cleanGeometry.sql]: PgSQL-Function to remove self-intersections from PostGIS LINESTRING and POLYGON geometries.
* [http://www.kappasys.ch/pgtools/pghistory/index.html PostGIS Historisation]: Two approaches for historisation of PostGIS data.
* PgVersion: PostGIS-Versioning System for concurrent editing of PostGIS-Layers (coming soon)

User:Hdus

2010-09-02T17:09:43Z

Wiki-Hdus:

Dr. Horst Düster 

Solothurn / Switzerland

horst dot duester at kappasys dot ch 
http://www.kappasys.ch

== Open Source Geospatial project involvements ==

* [http://www.sogis.ch SO!GIS]: Responsible for the 100% FOSSGIS stack of the state of Solothurn with more than 3500 clients since 2001.
* [http://qgis.org/ QGIS]: Plugin contributions: Geoprocessing, WPS-Client, PostGIS Query Editor.
* [http://www.kappasys.ch/pgtools/cleangeometry/cleanGeometry.sql cleanGeometry.sql]: PgSQL-Function to remove self-intersections from PostGIS LINESTRING and POLYGON geometries.
* PgVersion: PostGIS-Versioning System for concurrent editing of PostGIS-Layers (coming soon)

FOSS4G 2010 Breakout Sessions

2010-09-02T17:08:43Z

Wiki-Hdus: /* QGIS user & developer meeting */

[[Category:FOSS4G]]
[[Category:FOSS4G2010]]

back to [[FOSS4G 2010]]

= Introduction =
During the [http://2010.foss4g.org/ FOSS4G2010 conference] in Barcelona, Spain, there will be conference rooms available for people to hold Breakout Sessions (aka Birds-of-a-Feather).

Breakout Sessions sessions are unstructured timeslots where people can self-organise themselves to discuss topics of interest.

This year, Breakout Sessions sessions will be held on Wednesday 8th September ('''and possibly at other times as well - depending on interest'''). A number of rooms will be available. Most popular sessions will get bigger rooms.

'''Room allocation to be determined'''

==Organising Contact==
* [[Tyler Mitchell]]
* [[Mauricio Miranda]]
* Other volunteers welcome - sign up here!

==Timeslots Available==

At this stage, each room is scheduled for one hour between 18:00 to 19:00.

Remember the Gala Dinner is scheduled at 20:00.

=Room Assignments=
==Rooms Available==

{|class="wikitable" border="1"
! width="150"|Room
! width="400"|Wednesday 08
! width="400"|Contact
|-
| Room 4 (75 pax)
|
|
|-
| Room 5 (250 pax)
|
|
|-
| Room 6 (320 pax)
|
|
|-
| Room 8 (100 pax)
|
|
|-
| Room 11 (78 pax)
|
|
|-
| Room 12 (90 pax)
|
|
|}

= Proposed Topics =

* Add yours below...

==Web Client (OpenLayers/GeoExt)==

The first half of this session will be focused on OpenLayers, and the second half will focus on GeoExt. We can decide on topics at the start of each session, but we'll likely cover ideas for OpenLayers 3.0/GeoExt 1.0, getting more developers involved, and just some general Q/A time.

'''Coming:'''

* Tim Schaub
* Eric Lemoine
* David Jonglez - for the first half, at least
* Florin Iosub
* Xurxo Méndez
* [[Ricardo Pinho|Ricardo Pinho]]
* [[Nuno Guerreiro|Nuno Guerreiro]]
* Hugo Pereira
* [[Just van den Broecke|Just van den Broecke]]
* Sébastien Deleuze
* Richard Greenwood
* Andreas Hocevar

==Spatial Databases BoF==

Relational and non-relational persistence layers, let's get together and talk about interoperability, appropriate use cases, architecture and where we should be moving the spatial persistence state-of-the-art!

'''Coming:'''

* Paul Ramsey (PostGIS)
* Nicklas Avén (PostGIS)
* Brent Wood (NIWA)
* Peter Baumann (Jacobs University / rasdaman)
* Vincent Picavet (Oslandia/PostGIS)
* [[Nuno Guerreiro|Nuno Guerreiro]]
* Olivier Courtin (PostGIS)
* Hugo Pereira
* Volker Mische (CouchDB/GeoCouch)
* [[user:sebastian.ovide|Sebastián Ovide]]

==WPS BoF==

Several presentation on Web Processing selected
for presentation at FOSS4G2010 indicates a growing
interest amongst the communities.

If you are interested please add your names below...

'''Who's coming:'''

* Venkatesh Raghavan
* [[Markus Neteler]]
* [[Daniel Kastl]]
* Maria Brovelli
* [[Ian Turton]]
* [[Gerald Fenoy]]
* Nicolas Bozon
* [[Jody Garnett]]
* [[User:fpenarru | Fran Peñarrubia]]
* [[User:MarkusSchneider | Markus Schneider]]
* Luca Delucchi
* Milan Antonovic
* [[User:Maxi71 | Massimiliano cannata]]
* Luca Casagrande
* [[User:Rajsingh| Raj Singh ]]
* [[User:Jesus|Jorge de Jesus]] (Plymouth Marine Laboratory)
* Bertrand Gervais
* [[User:Schpidi | Stephan Meissl]]
* [[Sebastián Cruz|Sebastián Cruz]]
* Add your name here

==Sensor Web BoF==

The use of Sensor Web implementations has constantly increased during the last years.

If you are interested please add your names below...

'''Who's coming:'''

* Simon Jirka
* Marjorie Robert
* [[User:Maxi71 | Massimiliano cannata]]
* Graeme Mcferren
* Sarawut Ninsawat
* Brent Wood (NIWA)
* Jorge Piera
* Alain Tamayo
* Maria Brovelli
* Add your name here

==Biodiversity/conservation projects and FOSS4G tools==

More and more Open Source is catching on Biodiversity and conservation projects. Most of them are publicly funded so most of the time all the source they develop is Open Source. Aditionally Biodiversity and conservation heavily rely on GIS and they have specific needs. From geospatial niche modeling to species distributions, occurrence catalog, etc, there is a lot to talk about!

If you are interested please add your names below...

'''Coming:'''

* Javier de la Torre (Vizzuality)
* Brent Wood (NIWA)
* [[Markus Neteler]]
* [[User:jesus| Jorge de Jesus]] (Plymouth Marine Laboratory)
* [[User:Aghisla|Anne Ghisla]]
* Add your name here

==Spatial Data Infrastructure==

A birds of a feather session about using open source for spatial data infrastructure. Come discuss implementation strategies, best practices, INSPIRE.

'''Who's coming:'''

* Sebastian Benthall (GeoNode)
* David Winslow (GeoNode)
* Ariel Núñez (GeoNode)
* David Jonglez
* [[Ricardo Pinho|Ricardo Pinho]]
* Hugo Pereira
* Maria Brovelli
* [[Sebastián Cruz|Sebastián Cruz]]
* [[user:sebastian.ovide|Sebastián Ovide]]
* Add your name here

==Virtualization and Cloud Computing BoF==

Virtualization and Cloud Computing is growing fast on the GIS world, let's get together and talk about the use cases and share opinions and suggestions about how can we take the most out of this new technology!

If you are interested please add your name below...

'''Coming:'''
* [[Ricardo Pinho|Ricardo Pinho]]
* Hugo Pereira
* [[Sebastián Cruz|Sebastián Cruz]]
* [[user:sebastian.ovide|Sebastián Ovide]]
* Add your name here

==Spatial OLAP==

Spatial OLAP can be defined as a visual platform built especially to support rapid and easy spatiotemporal analysis and exploration of data following a multidimensional approach comprised of aggregation levels available in cartographic displays as well as in tabular and diagram displays. Let's talk about new improvements combining GIS and BI technologies.

If you are interested please add your name below...

'''Coming:'''
* [[Nuno Guerreiro|Nuno Guerreiro]]
* [[Mauricio Miranda]]
* [[User:Rajsingh| Raj Singh ]]
* Add your name here

==Flex Mapping (Alternatives to HTML)==

Flex is a highly productive, free, open source framework for building expressive web applications that deploy consistently on all major browsers, desktops, and operating systems.
OpenScales is an open source (LGPL) mapping framework written in ActionScript 3 and Flex that allows developers to building Rich Internet Mapping Applications.
There are alternatives to HTML mapping, let's discuss about them...

If you are interested please add your name below...

'''Coming:'''
* Sébastien Deleuze (OpenScales)
* Aurélien Barbier-Accary (OpenScales)
* Simon Lopez (OpenScales)
* Fabio Panettieri
* Marjorie Robert (if the session is planned on tuesday)
* Add your name here

David Jonglez - As discussed previously with other parties, it would be interesting to plan this session in an other time schedule in order to allow a maximum of interested persons already involved in other sessions to participate. What do you think planning this session on tuesday, the 7th evening ? (I'm shure we'll find a place !)

==QGIS user & developer meeting==

Topics:
* What's new in QGIS 1.5
* Interesting plugins
* What's coming in the next QGIS release
* Discussion

If you are interested please add your name below...

'''Coming:'''
* Marco Hugentobler
* [[User:Pirmin_Kalberer| Pirmin Kalberer]]
* Mathias Walker
* [[User:Vasile| Vasile Crăciunescu]]
* [[User:Lmotta| Luiz Motta]]
* Richard Duivenvoorde
* [[User:hdus | Horst Düster]]

User:Hdus

2010-09-02T17:07:21Z

Wiki-Hdus:

Dr. Horst Düster 

Solothurn / Switzerland

horst.duester@kappasys.ch 
http://www.kappasys.ch

== Open Source Geospatial project involvements ==

* [http://www.sogis.ch SO!GIS]: Responsible for the 100% FOSSGIS stack of the state of Solothurn with more than 3500 clients since 2001.
* [http://qgis.org/ QGIS]: Plugin contributions: Geoprocessing, WPS-Client, PostGIS Query Editor.
* [http://www.kappasys.ch/pgtools/cleangeometry/cleanGeometry.sql cleanGeometry.sql]: PgSQL-Function to remove self-intersections from PostGIS LINESTRING and POLYGON geometries.
* PgVersion: PostGIS-Versioning System for concurrent editing of PostGIS-Layers (coming soon)

FOSS4G 2010 Breakout Sessions

2010-09-02T16:42:57Z

Wiki-Hdus: /* QGIS user & developer meeting */

FOSS4G2008 LightningTalks

2008-09-08T07:58:37Z

Wiki-Hdus: /* 5 Dr. Horst Düster : Building a FOSS geospatial solution for a Swiss state */

Back to [[FOSS4G2008]]...

= Introduction =
Eight speakers, five minutes each, [http://www.foss4g2008.org/plenaries/#lightning Lightning Talks] will be presented to the full conference attendance, and should be fast paced, visual, and entertaining. Please note we reserve the right to juggle the order of talks listed below to align better with topics etc.

= Proposed Speakers =

If you would like to give a lightning talk, or would like to put forward someone to give a talk, please provide adequate contact details here:

* '''Name, affiliation, email, proposed topic'''
*
*

= Confirmed Speakers =

(speaking order to be confirmed)

== 1 Steven Ottens ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 2 Speaker: OSGeo4W ==
* Frank Warmerdam (or Jeff McKenna)
* Position / person title
* One sentence bio
* A brief introduction to [http://trac.osgeo.org/osgeo4w OSGeo4W], the "OSGeo Windows Software Stack", including a call for users and packagers.
* URL to head shot

== 3 Dr Manie Brynard: Serving global geological data using Mapserver ==
* Dr Manie Brynard, Council for Geoscience mbrynard <at> geoscience.org.za:
* One sentence bio GIS Specialist and Senior Geologist at the Council for Geoscience for 12 years
* As a contribution to the global initiative to present global geology on a Google-earth like the CGS has applied MapServer to serve countrywide geological data as a WMS.
* URL to head shot

== 4 Speaker: Geospatial at the United Nations ==
* T. Suha Ulgen (Mr.) ulgen at un.org
* Coordinator - UN Geographic Information Working Group Secretariat (UNGIWG)
* Introduction to the United Nations Geographic Information Working Group (UNGIWG), the UN Spatial Data Infrastructure (UNSDI) and UN's FOSS4G initiatives.
* URL to head shot

== 5 Dr. Horst Düster : Building a FOSS geospatial solution for a Swiss state ==
* Dr. Horst Düster - Departement of Geoinformation State of Solothurn (Horst.Duester AT bd.so.ch)
* GIS - Coodinator and CGO at Public Authority since 13 Years
* A short overview on history of the FOSS geospatial infrastructure in Solothurn
* [http://www.sogis1.so.ch/sogis/dl/foss4g/hdus.jpg] URL to head shot

== 6 Paul Scott : Chisimba and Ubuntu GIS ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 7 Speaker: Talk Title ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 8 Speaker: Talk Title ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

FOSS4G2008 LightningTalks

2008-09-02T18:05:36Z

Wiki-Hdus: /* 5 Dr. Horst Düster : Building a FOSS geospatial solution for a Swiss canton */

Back to [[FOSS4G2008]]...

= Introduction =
Eight speakers, five minutes each, [http://www.foss4g2008.org/plenaries/#lightning Lightning Talks] will be presented to the full conference attendance, and should be fast paced, visual, and entertaining. Please note we reserve the right to juggle the order of talks listed below to align better with topics etc.

= Proposed Speakers =

If you would like to give a lightning talk, or would like to put forward someone to give a talk, please provide adequate contact details here:

* '''Name, affiliation, email, proposed topic'''
*
*

= Confirmed Speakers =

(speaking order to be confirmed)

== 1 Steven Ottens ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 2 Speaker: OSGeo4W ==
* Frank Warmerdam (or Jeff McKenna)
* Position / person title
* One sentence bio
* A brief introduction to [http://trac.osgeo.org/osgeo4w OSGeo4W], the "OSGeo Windows Software Stack", including a call for users and packagers.
* URL to head shot

== 3 Dr Manie Brynard: Serving global geological data using Mapserver ==
* Dr Manie Brynard, Council for Geoscience mbrynard <at> geoscience.org.za:
* One sentence bio GIS Specialist and Senior Geologist at the Council for Geoscience for 12 years
* As a contribution to the global initiative to present global geology on a Google-earth like the CGS has applied MapServer to serve countrywide geological data as a WMS.
* URL to head shot

== 4 Speaker: Geospatial at the United Nations ==
* T. Suha Ulgen (Mr.) ulgen at un.org
* Coordinator - UN Geographic Information Working Group Secretariat (UNGIWG)
* Introduction to the United Nations Geographic Information Working Group (UNGIWG), the UN Spatial Data Infrastructure (UNSDI) and UN's FOSS4G initiatives.
* URL to head shot

== 5 Dr. Horst Düster : Building a FOSS geospatial solution for a Swiss state ==
* Dr. Horst Düster - Departement of Geoinformation State of Solothurn (Horst.Duester AT bd.so.ch)
* GIS - Coodinator and CGO at Public Authority since 13 Years
* A short overview on history of the FOSS geospatial infrastructure in Solothurn
* [http://www.sogis1.so.ch/sogis/dl/foss4g/hdus.gif] URL to head shot

== 6 Paul Scott : Chisimba and Ubuntu GIS ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 7 Speaker: Talk Title ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 8 Speaker: Talk Title ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

FOSS4G2008 LightningTalks

2008-09-02T15:01:18Z

Wiki-Hdus: /* 5 Dr. Horst Düster : Building a FOSS geospatial solution for a Swiss canton */

Back to [[FOSS4G2008]]...

= Introduction =
Eight speakers, five minutes each, [http://www.foss4g2008.org/plenaries/#lightning Lightning Talks] will be presented to the full conference attendance, and should be fast paced, visual, and entertaining. Please note we reserve the right to juggle the order of talks listed below to align better with topics etc.

= Proposed Speakers =

If you would like to give a lightning talk, or would like to put forward someone to give a talk, please provide adequate contact details here:

* '''Name, affiliation, email, proposed topic'''
*
*

= Confirmed Speakers =

(speaking order to be confirmed)

== 1 Steven Ottens ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 2 Speaker: OSGeo4W ==
* Frank Warmerdam (or Jeff McKenna)
* Position / person title
* One sentence bio
* A brief introduction to [http://trac.osgeo.org/osgeo4w OSGeo4W], the "OSGeo Windows Software Stack", including a call for users and packagers.
* URL to head shot

== 3 Dr Manie Brynard: Serving global geological data using Mapserver ==
* Dr Manie Brynard, Council for Geoscience mbrynard <at> geoscience.org.za:
* One sentence bio GIS Specialist and Senior Geologist at the Council for Geoscience for 12 years
* As a contribution to the global initiative to present global geology on a Google-earth like the CGS has applied MapServer to serve countrywide geological data as a WMS.
* URL to head shot

== 4 Speaker: Geospatial at the United Nations ==
* T. Suha Ulgen (Mr.) ulgen at un.org
* Coordinator - UN Geographic Information Working Group Secretariat (UNGIWG)
* Introduction to the United Nations Geographic Information Working Group (UNGIWG), the UN Spatial Data Infrastructure (UNSDI) and UN's FOSS4G initiatives.
* URL to head shot

== 5 Dr. Horst Düster : Building a FOSS geospatial solution for a Swiss canton ==
* Dr. Horst Düster - Departement of Geoinformation Kanton Solothurn (Horst.Duester AT bd.so.ch)
* GIS - Coodinator and Senior CGO at Public Authority since 13 Years
* A brief overview on history and architecture of the FOSS geospatial infrastructure in Solothurn
* [http://www.sogis1.so.ch/sogis/dl/foss4g/hdus.gif] URL to head shot

== 6 Paul Scott : Chisimba and Ubuntu GIS ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 7 Speaker: Talk Title ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 8 Speaker: Talk Title ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

FOSS4G2008 LightningTalks

2008-09-02T15:00:39Z

Wiki-Hdus: /* 5 Dr. Horst Düster : Building a FOSS geospatial solution for a Swiss canton */

Back to [[FOSS4G2008]]...

= Introduction =
Eight speakers, five minutes each, [http://www.foss4g2008.org/plenaries/#lightning Lightning Talks] will be presented to the full conference attendance, and should be fast paced, visual, and entertaining. Please note we reserve the right to juggle the order of talks listed below to align better with topics etc.

= Proposed Speakers =

If you would like to give a lightning talk, or would like to put forward someone to give a talk, please provide adequate contact details here:

* '''Name, affiliation, email, proposed topic'''
*
*

= Confirmed Speakers =

(speaking order to be confirmed)

== 1 Steven Ottens ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 2 Speaker: OSGeo4W ==
* Frank Warmerdam (or Jeff McKenna)
* Position / person title
* One sentence bio
* A brief introduction to [http://trac.osgeo.org/osgeo4w OSGeo4W], the "OSGeo Windows Software Stack", including a call for users and packagers.
* URL to head shot

== 3 Dr Manie Brynard: Serving global geological data using Mapserver ==
* Dr Manie Brynard, Council for Geoscience mbrynard <at> geoscience.org.za:
* One sentence bio GIS Specialist and Senior Geologist at the Council for Geoscience for 12 years
* As a contribution to the global initiative to present global geology on a Google-earth like the CGS has applied MapServer to serve countrywide geological data as a WMS.
* URL to head shot

== 4 Speaker: Geospatial at the United Nations ==
* T. Suha Ulgen (Mr.) ulgen at un.org
* Coordinator - UN Geographic Information Working Group Secretariat (UNGIWG)
* Introduction to the United Nations Geographic Information Working Group (UNGIWG), the UN Spatial Data Infrastructure (UNSDI) and UN's FOSS4G initiatives.
* URL to head shot

== 5 Dr. Horst Düster : Building a FOSS geospatial solution for a Swiss canton ==
* Dr. Horst Düster - Departement of Geoinformation Kanton Solothurn (Horst.Duester AT bd.so.ch)
* GIS - Coodinator and Senior CGO at Public Authory since 13 Years
* A brief overview on history and architecture of the FOSS geospatial infrastructure in Solothurn
* [http://www.sogis1.so.ch/sogis/dl/foss4g/hdus.gif] URL to head shot

== 6 Paul Scott : Chisimba and Ubuntu GIS ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 7 Speaker: Talk Title ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 8 Speaker: Talk Title ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

FOSS4G2008 LightningTalks

2008-09-02T14:57:01Z

Wiki-Hdus: /* 5 Dr. Horst Düster : Building a FOSS geospatial solution for a Swiss canton */

Back to [[FOSS4G2008]]...

= Introduction =
Eight speakers, five minutes each, [http://www.foss4g2008.org/plenaries/#lightning Lightning Talks] will be presented to the full conference attendance, and should be fast paced, visual, and entertaining. Please note we reserve the right to juggle the order of talks listed below to align better with topics etc.

= Proposed Speakers =

If you would like to give a lightning talk, or would like to put forward someone to give a talk, please provide adequate contact details here:

* '''Name, affiliation, email, proposed topic'''
*
*

= Confirmed Speakers =

(speaking order to be confirmed)

== 1 Steven Ottens ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 2 Speaker: OSGeo4W ==
* Frank Warmerdam (or Jeff McKenna)
* Position / person title
* One sentence bio
* A brief introduction to [http://trac.osgeo.org/osgeo4w OSGeo4W], the "OSGeo Windows Software Stack", including a call for users and packagers.
* URL to head shot

== 3 Dr Manie Brynard: Serving global geological data using Mapserver ==
* Dr Manie Brynard, Council for Geoscience mbrynard <at> geoscience.org.za:
* One sentence bio GIS Specialist and Senior Geologist at the Council for Geoscience for 12 years
* As a contribution to the global initiative to present global geology on a Google-earth like the CGS has applied MapServer to serve countrywide geological data as a WMS.
* URL to head shot

== 4 Speaker: Geospatial at the United Nations ==
* T. Suha Ulgen (Mr.) ulgen at un.org
* Coordinator - UN Geographic Information Working Group Secretariat (UNGIWG)
* Introduction to the United Nations Geographic Information Working Group (UNGIWG), the UN Spatial Data Infrastructure (UNSDI) and UN's FOSS4G initiatives.
* URL to head shot

== 5 Dr. Horst Düster : Building a FOSS geospatial solution for a Swiss canton ==
* Dr. Horst Düster - Departement of Geoinformation Kanton Solothurn (Horst.Duester AT bd.so.ch)
* GIS - Coodinator and Senior CGO at Public Authory since 13 Years
* Overview on history and architecture of the FOSS geospatial infrastructure in Solothurn
* [http://www.sogis1.so.ch/sogis/dl/foss4g/hdus.gif] URL to head shot

== 6 Paul Scott : Chisimba and Ubuntu GIS ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 7 Speaker: Talk Title ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 8 Speaker: Talk Title ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

FOSS4G2008 LightningTalks

2008-09-02T14:54:56Z

Wiki-Hdus: /* 5 Dr. Horst Düster : Building a FOSS geospatial solution for a Swiss canton */

Back to [[FOSS4G2008]]...

= Introduction =
Eight speakers, five minutes each, [http://www.foss4g2008.org/plenaries/#lightning Lightning Talks] will be presented to the full conference attendance, and should be fast paced, visual, and entertaining. Please note we reserve the right to juggle the order of talks listed below to align better with topics etc.

= Proposed Speakers =

If you would like to give a lightning talk, or would like to put forward someone to give a talk, please provide adequate contact details here:

* '''Name, affiliation, email, proposed topic'''
*
*

= Confirmed Speakers =

(speaking order to be confirmed)

== 1 Steven Ottens ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 2 Speaker: OSGeo4W ==
* Frank Warmerdam (or Jeff McKenna)
* Position / person title
* One sentence bio
* A brief introduction to [http://trac.osgeo.org/osgeo4w OSGeo4W], the "OSGeo Windows Software Stack", including a call for users and packagers.
* URL to head shot

== 3 Dr Manie Brynard: Serving global geological data using Mapserver ==
* Dr Manie Brynard, Council for Geoscience mbrynard <at> geoscience.org.za:
* One sentence bio GIS Specialist and Senior Geologist at the Council for Geoscience for 12 years
* As a contribution to the global initiative to present global geology on a Google-earth like the CGS has applied MapServer to serve countrywide geological data as a WMS.
* URL to head shot

== 4 Speaker: Geospatial at the United Nations ==
* T. Suha Ulgen (Mr.) ulgen at un.org
* Coordinator - UN Geographic Information Working Group Secretariat (UNGIWG)
* Introduction to the United Nations Geographic Information Working Group (UNGIWG), the UN Spatial Data Infrastructure (UNSDI) and UN's FOSS4G initiatives.
* URL to head shot

== 5 Dr. Horst Düster : Building a FOSS geospatial solution for a Swiss canton ==
* Dr. Horst Düster - Departement of Geoinformation Kanton Solothurn (Horst.Duester AT bd.so.ch)
* GIS - Coodinator and Senior CGO at Public Authory since 13 Years
* Overview on history and architecture of the FOSS geospatial infrastructure in Solothurn
* [http://www.sogis1.so.ch/sogis/dl/foss4g/hdus.gif] Image

== 6 Paul Scott : Chisimba and Ubuntu GIS ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 7 Speaker: Talk Title ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 8 Speaker: Talk Title ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

FOSS4G2008 LightningTalks

2008-09-02T14:50:06Z

Wiki-Hdus: /* 5 Dr. Horst Düster : Building a FOSS geospatial solution for a Swiss canton */

Back to [[FOSS4G2008]]...

= Introduction =
Eight speakers, five minutes each, [http://www.foss4g2008.org/plenaries/#lightning Lightning Talks] will be presented to the full conference attendance, and should be fast paced, visual, and entertaining. Please note we reserve the right to juggle the order of talks listed below to align better with topics etc.

= Proposed Speakers =

If you would like to give a lightning talk, or would like to put forward someone to give a talk, please provide adequate contact details here:

* '''Name, affiliation, email, proposed topic'''
*
*

= Confirmed Speakers =

(speaking order to be confirmed)

== 1 Steven Ottens ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 2 Speaker: OSGeo4W ==
* Frank Warmerdam (or Jeff McKenna)
* Position / person title
* One sentence bio
* A brief introduction to [http://trac.osgeo.org/osgeo4w OSGeo4W], the "OSGeo Windows Software Stack", including a call for users and packagers.
* URL to head shot

== 3 Dr Manie Brynard: Serving global geological data using Mapserver ==
* Dr Manie Brynard, Council for Geoscience mbrynard <at> geoscience.org.za:
* One sentence bio GIS Specialist and Senior Geologist at the Council for Geoscience for 12 years
* As a contribution to the global initiative to present global geology on a Google-earth like the CGS has applied MapServer to serve countrywide geological data as a WMS.
* URL to head shot

== 4 Speaker: Geospatial at the United Nations ==
* T. Suha Ulgen (Mr.) ulgen at un.org
* Coordinator - UN Geographic Information Working Group Secretariat (UNGIWG)
* Introduction to the United Nations Geographic Information Working Group (UNGIWG), the UN Spatial Data Infrastructure (UNSDI) and UN's FOSS4G initiatives.
* URL to head shot

== 5 Dr. Horst Düster : Building a FOSS geospatial solution for a Swiss canton ==
* Dr. Horst Düster - Departement of Geoinformation Kanton Solothurn (Horst.Duester AT bd.so.ch)
* GIS - Coodinator and Senior CGO at Public Authory since 13 Years
* Overview on history and architecture of the FOSS geospatial infrastructure in Solothurn
* URL to head shot

== 6 Paul Scott : Chisimba and Ubuntu GIS ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 7 Speaker: Talk Title ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 8 Speaker: Talk Title ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

FOSS4G2008 LightningTalks

2008-09-02T14:45:02Z

Wiki-Hdus: /* 5 Dr. Horst Düster : Building a FOSS geospatial solution for a Swiss canton */

Back to [[FOSS4G2008]]...

= Introduction =
Eight speakers, five minutes each, [http://www.foss4g2008.org/plenaries/#lightning Lightning Talks] will be presented to the full conference attendance, and should be fast paced, visual, and entertaining. Please note we reserve the right to juggle the order of talks listed below to align better with topics etc.

= Proposed Speakers =

If you would like to give a lightning talk, or would like to put forward someone to give a talk, please provide adequate contact details here:

* '''Name, affiliation, email, proposed topic'''
*
*

= Confirmed Speakers =

(speaking order to be confirmed)

== 1 Steven Ottens ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 2 Speaker: OSGeo4W ==
* Frank Warmerdam (or Jeff McKenna)
* Position / person title
* One sentence bio
* A brief introduction to [http://trac.osgeo.org/osgeo4w OSGeo4W], the "OSGeo Windows Software Stack", including a call for users and packagers.
* URL to head shot

== 3 Dr Manie Brynard: Serving global geological data using Mapserver ==
* Dr Manie Brynard, Council for Geoscience mbrynard <at> geoscience.org.za:
* One sentence bio GIS Specialist and Senior Geologist at the Council for Geoscience for 12 years
* As a contribution to the global initiative to present global geology on a Google-earth like the CGS has applied MapServer to serve countrywide geological data as a WMS.
* URL to head shot

== 4 Speaker: Geospatial at the United Nations ==
* T. Suha Ulgen (Mr.) ulgen at un.org
* Coordinator - UN Geographic Information Working Group Secretariat (UNGIWG)
* Introduction to the United Nations Geographic Information Working Group (UNGIWG), the UN Spatial Data Infrastructure (UNSDI) and UN's FOSS4G initiatives.
* URL to head shot

== 5 Dr. Horst Düster : Building a FOSS geospatial solution for a Swiss canton ==
* Dr. Horst Düster - Departement of Geoinformation Kanton Solothurn (Horst.Duester AT bd.so.ch)
* One sentence bio
* Overview on history and architecture of the FOSS geospatial infrastructure in Solothurn
* URL to head shot

== 6 Paul Scott : Chisimba and Ubuntu GIS ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 7 Speaker: Talk Title ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 8 Speaker: Talk Title ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

FOSS4G2008 LightningTalks

2008-09-02T06:43:38Z

Wiki-Hdus: /* 5 Dr. Horst Düster : Building a FOSS geospatial solution for a Swiss canton */

Back to [[FOSS4G2008]]...

= Introduction =
Eight speakers, five minutes each, [http://www.foss4g2008.org/plenaries/#lightning Lightning Talks] will be presented to the full conference attendance, and should be fast paced, visual, and entertaining. Please note we reserve the right to juggle the order of talks listed below to align better with topics etc.

= Proposed Speakers =

If you would like to give a lightning talk, or would like to put forward someone to give a talk, please provide adequate contact details here:

* '''Name, affiliation, email, proposed topic'''
*
*

= Confirmed Speakers =

(speaking order to be confirmed)

== 1 Steven Ottens ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 2 Speaker: OSGeo4W ==
* Frank Warmerdam (or Jeff McKenna)
* Position / person title
* One sentence bio
* A brief introduction to [http://trac.osgeo.org/osgeo4w OSGeo4W], the "OSGeo Windows Software Stack", including a call for users and packagers.
* URL to head shot

== 3 Dr Manie Brynard: Serving global geological data using Mapserver ==
* Dr Manie Brynard, Council for Geoscience mbrynard <at> geoscience.org.za:
* One sentence bio GIS Specialist and Senior Geologist at the Council for Geoscience for 12 years
* As a contribution to the global initiative to present global geology on a Google-earth like the CGS has applied MapServer to serve countrywide geological data as a WMS.
* URL to head shot

== 4 Speaker: Geospatial at the United Nations ==
* T. Suha Ulgen (Mr.) ulgen at un.org
* Coordinator - UN Geographic Information Working Group Secretariat (UNGIWG)
* Introduction to the United Nations Geographic Information Working Group (UNGIWG), the UN Spatial Data Infrastructure (UNSDI) and UN's FOSS4G initiatives.
* URL to head shot

== 5 Dr. Horst Düster : Building a FOSS geospatial solution for a Swiss canton ==
* Dr. Horst Düster - Departement of Geoinformation Kanton Solothurn (Horst.Duester AT bd.so.ch)
* One sentence bio
* One sentence talk summary
* URL to head shot

== 6 Paul Scott : Chisimba and Ubuntu GIS ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 7 Speaker: Talk Title ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 8 Speaker: Talk Title ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

FOSS4G2008 LightningTalks

2008-09-02T06:32:13Z

Wiki-Hdus: /* 5 Dr. Horst Düster : Building a FOSS geospatial solution for a Swiss municipality (title subject to revision) */

Back to [[FOSS4G2008]]...

= Introduction =
Eight speakers, five minutes each, [http://www.foss4g2008.org/plenaries/#lightning Lightning Talks] will be presented to the full conference attendance, and should be fast paced, visual, and entertaining. Please note we reserve the right to juggle the order of talks listed below to align better with topics etc.

= Proposed Speakers =

If you would like to give a lightning talk, or would like to put forward someone to give a talk, please provide adequate contact details here:

* '''Name, affiliation, email, proposed topic'''
*
*

= Confirmed Speakers =

(speaking order to be confirmed)

== 1 Steven Ottens ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 2 Speaker: OSGeo4W ==
* Frank Warmerdam (or Jeff McKenna)
* Position / person title
* One sentence bio
* A brief introduction to [http://trac.osgeo.org/osgeo4w OSGeo4W], the "OSGeo Windows Software Stack", including a call for users and packagers.
* URL to head shot

== 3 Dr Manie Brynard: Serving global geological data using Mapserver ==
* Dr Manie Brynard, Council for Geoscience mbrynard <at> geoscience.org.za:
* One sentence bio GIS Specialist and Senior Geologist at the Council for Geoscience for 12 years
* As a contribution to the global initiative to present global geology on a Google-earth like the CGS has applied MapServer to serve countrywide geological data as a WMS.
* URL to head shot

== 4 Speaker: Geospatial at the United Nations ==
* T. Suha Ulgen (Mr.) ulgen at un.org
* Coordinator - UN Geographic Information Working Group Secretariat (UNGIWG)
* Introduction to the United Nations Geographic Information Working Group (UNGIWG), the UN Spatial Data Infrastructure (UNSDI) and UN's FOSS4G initiatives.
* URL to head shot

== 5 Dr. Horst Düster : Building a FOSS geospatial solution for a Swiss canton ==
* Dr. Horst Düster - Kanton Solothurn (Horst.Duester AT bd.so.ch)
* One sentence bio
* One sentence talk summary
* URL to head shot

== 6 Paul Scott : Chisimba and Ubuntu GIS ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 7 Speaker: Talk Title ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

== 8 Speaker: Talk Title ==
* Position / person title
* One sentence bio
* One sentence talk summary
* URL to head shot

User:Hdus

2008-04-07T15:42:55Z

Wiki-Hdus: New page: Dr. Horst Düster GIS-Koordinator, Stv. Amtschef Kanton Solothurn Bau- und Justizdepartement Amt für Geoinformation SO!GIS Koordination Rötistrasse 4 CH-45...

Dr. Horst Düster 
GIS-Koordinator, Stv. Amtschef

Kanton Solothurn 
Bau- und Justizdepartement 
Amt für Geoinformation 
SO!GIS Koordination 
Rötistrasse 4 
CH-4501 Solothurn 

Telefon ++41(0)32 627 25 32 
Telefax ++41(0)32 627 22 14

horst.duester@bd.so.ch 
http://www.sogis.ch

D-A-CH

2008-04-07T15:38:38Z

Wiki-Hdus: /* Mitgliederliste */

''This is the start page of the German Local Chapter as per [[Local Chapter Guidelines]]''

''Das ist die deutschsprachige Einstiegsseite zur OSGeo Foundation, die zu einer regionalen Gruppe werden könnte wie sie in den [[Local Chapter Guidelines]] beschrieben wird.

== Presse ==

Artikel über die OSGeo (erschienen in der "GIS-Zeitschrift für Geoinformatik", 11/07, S.38-41)

[http://wiki.osgeo.org/images/c/c6/GIS_OSGeo.pdf Download]

== Einführung ==
Bitte tragen Sie sich in die [[Deutsch#Mitgliederliste | Mitgliederliste]] ein, wenn Sie Interesse an einem deutschsprachigen [[Local Chapters]] haben. Der Eintrag ist freiwillig, dieses Wiki und alle enthaltenen Informationen sind öffentlich sichtbar. Die Kommunikation erfolgt über die [http://lists.osgeo.org/mailman/listinfo/viscom-discuss-de Mailing-Liste discuss-de] ([http://lists.osgeo.org/pipermail/viscom-discuss-de/ Archiv]) oder dieses Wiki.
Eingeladen an dem deutschsprachigen Local Chapter mitzuwirken sind ausdrücklich alle Interessierten, völlig unabhängig davon ob Anwender oder Entwickler, völlig unabhängig davon ob erfahren im Umgang mit OS-GIS-Software oder "Neuling". Die OSGeo lebt von der Beteiligung jedes Einzelnen, jeder Beitrag ist willkommen.

== Unser Name ==
Wir brauchen einen offiziellen Namen für die deutschsprachige Gruppe der OSGe, Vorschläge:
* OSGeo DACH

Der Begriff der "Foundation" lässt sich ebenfalls nicht gut [http://dict.leo.org/ende?lp=ende&lang=de&searchLoc=0&cmpType=relaxed&sectHdr=on&spellToler=on&search=Foundation&relink=on direkt übersetzen], in vielen Dokumenten ist deshalb von der "OSGeo Foundation" zu lesen, was allerdings gegen die Vorgaben zur Nutzung des OSGeo Logo und Markennamen geht.

== Rechtsform, Konto ==
Die OSGeo Foundation ist als non-profit Firma in Delaware, USA gegründet worden. Dort gibt es auch ein Konto und wird das Budget verwaltet. Für formale Arbeiten und als zentrale Anlaufstelle für Fragen rund um die OSGeo wurde Tyler Mitchell als Executive Director angestellt, seine Stelle wird auch aus diesem Budget finanziert. Unabhängig davon werden wir nationale Konten benötigen, da die Transferkosten und der Aufwand, Geld über internationale Grenzen zu transportieren, nach wie vor unsinnig ist.

In Deutschland gibt es bereits ein Netzwerk und Organisation für die Förderung Freier Software. Die GAV e.V. (GRASS Anwender-Vereinigung) ist eine formale Organisation der Rechtsform "eingetragener Verein", die bereits seit 1999 die gleichen Ziele verfolgt wie die OSGeo. Der GAV und OSGeo sind im Gespräch, wie eine Kooperation gestaltet werden kann. Eine erste, pragmatische Kooperation betrifft die Überschüsse der letzten FOSSGIS-Konferenzen, die das Organisationsteam zweckgebunden an den GAV e.V. gespendet hat. Bei Konferenzen und zu Marketing-Zwecken der OSGeo auf Messen im deutschsprachigen Raum konnte dieser Überschuß bereits sinnvoll genutzt werden, z.B. um den Druck von Informationsmaterial zu finanzieren.
* [http://www.grass-verein.de/ GAV] (GRASS Anwender-Vereinigung e.V.)
* [http://www.fossgis.de FOSSGIS.de] (Organisationsteam der FOSSGIS-Konferenzen)

== Ziele ==
Die Ziele der deutschsprachigen OSGeo Arbeitsgruppe entwickeln sich durch die Beiträge der Mitglieder. Eine erste Orientierung geben die [[Local Chapter Guidelines | Richtlinien für lokale Gruppen]], einzelne Schwerpunkte werden sich im Laufe der Arbeit herauskristallisieren.
* Bereitstellung eines Netzwerkes für die Mitglieder, ggf. mit Job-Börse.
* Organisation der jährlichen deutschsprachigen Konferenz (siehe [[FOSSGIS 2006]])
* Kontaktstelle für neue Mitglieder und Sponsoren
* Führung eines Regionalbüros mit Konto, Telefon, Ansprechpartner
* Übersetzung von Dokumenten, Inhalten, Webseiten und Lokalisierung von Software (Anpassung an örtliche Besonderheiten)
* Lösungen im deutschsprachigen Raum bewerben
* Erstellung von regionalisierten Software-Paketen
* Training, Support und Entwicklung von e-Learning Inhalten in deutscher Sprache
* Förderung von offenen Standards und freien Zugang zu räumlichen Daten im deutschsprachigen Umfeld.
* Förderung der OSGeo Foundation durch Präsentationen, Informationsveranstaltungen, Messestände, etc.

== Komitees ==

An dieser Stelle folgen nach und nach die Komitees der deutschsprachigen OSGeo Gemeinschaft. Fühlen Sie sich frei selber ein Komitee zu gründen oder sich einem bestehenden anzuschließen.

* [[Komitee für Bildung und Dokumentationserstellung | Komitee für Bildung und Dokumentationserstellung]]

== Kommunikation ==
Die Kommunikaiton läuft über dieses Wiki, Mailing Listen, Webseite und natürlich das persönliche Gespräch auf Messen, Konferenzen und Anwendertreffen. Das neue OSGeo Portal bietet eine einfache Möglichkeit zur Übersetzung ins Deutsche. Falls Sie bei der Übersetzung gerne helfen möchten wenden Sie sich bitte an die Translation Group des [[WebCom | Website Committee]].

== Steuerung ==
Die deutschprachige Gruppe der OSGeo ist noch informell. Beteiligen Sie sich an der Gestaltung, indem Sie sich einbringen. Entscheidungen werden wie bei Open Source üblich per Email an die Mailing Liste geschickt und diskutiert. Beschlussfähige Vorschläge werden von einem Mitglied vorgeschlagen und von einem zweiten Mitglied unterstützt.

=== Wahl ===
Die Wahl erfolgt über Ablehung, Zustimmung oder Gleichgültigkeit:
-1 = Veto, Ablehung
-0 = nicht einverstanden, beugt sich aber der Mehrheit
0 = trägt die Entscheidung der anderen mit, kann aber nicht beurteilen, ob sie gut ist (zu wenig Information, keine Zeit sich zu informieren, etc.)
+0 = unterstützt den Antrag passiv, kann aber nicht aktiv zum Thema beisteuern
+1 = Zustimmung, unterstützt den Antrag voll und arbeitet auch mit

=== Veto ===
Wer mit -1 wählt legt ein Veto ein. Damit das Veto angenommen werden kann muss es innerhalb der Wahlfrist begründet und am besten gleich mit einem Alternativvorschlag eingebracht werden.

=== Unterstützung ===
Wer mit +1 wählt muss auch bereit sein aktiv mit der Lösung mitzumachen. Sonst gibt es zu viele faule Beobachter und zu wenige Arbeiter.

=== Veto überstimmen ===
Ein Veto kann überstimmt werden
* durch eine absolute Mehrheit der Mitglieder
* oder wenn mindestens vier Mitglieder mit einer +1 wählen.

Alle Ergebnis können immer angefochten werden (bis uns was besseres einfällt).

== Offizieller Status und Dokumente ==
Die OSGeo Foundation ist eine rechtliche Organisation die aus mittlerweile 59 Mitgliedern und 9 Direktoren besteht. Alle offiziellen Projekte und Dokumente müssen von dem Direktorium abgenommen werden bevor sie offiziellen Status erreichen. Offizielle Dokumente werden in den statischen Dokumenten-Ordner auf osgeo.org hinterlegt und werden dadurch "Official Policy" der OSGeo Foundation. Sobald die Mitgliederliste 10 bis 15 Einträge hat, die sich aktiv einbringen wollen, können wir einen Antrag auf einen eigenen Projektbereich mit Dokumentenordner, SVN, Webseite, etc. und offiziellem Status beantragen.

Die Sammlung deutschsprachiger Dokumente ist der Migration zum Opfer gefallen, wird aber nach und nach wieder aufgebaut. Falls Sie selbst Dokumente beisteuern können wenden Sie dich bitte an das [[Promotion and Visibility Committee]].
* [[Intern: Entwurf Artikel GIS BUSINESS | ]]

== Weitere Wiki-Seiten zu regionalen (''local'') Themen und Veranstaltungen ==
* [http://wiki.osgeo.org/index.php/Deutsch/NAS Entwicklung freier NAS-Schnittstelle]
* [http://wiki.osgeo.org/index.php/LinuxTag_2007 LinuxTag 2007]
* [[AGIT_2007]]
* [[Intergeo_2007]]
* [[FOSSGIS 2008]]

== Mitgliederliste ==
* [[User:Arnulf Christl | Arnulf Christl]]
* [[User:Ofreier | Olaf Freier]] ([http://www.hinte-messe.de/ Hinte GmbH])
* [[User:Peter Stamm | Peter Stamm]]
* [[User:Schmitz | Sebastian Schmitz]]
* [[User:Astrid Emde | Astrid Emde]]
* [[User:Uli Rothstein | Uli Rothstein]]
* [[User:Sven Boehme | Sven Boehme]]
* [[User:Garand | Michel Garand]]
* [[User:christoph | Christoph Baudson]]
* [[User:dietmar | Dietmar Fleischhauer]]
* [[User:Georgloesel | Georg Lösel]]
* [[User:Olaf Knopp | Olaf Knopp]]
* [[User:Torsten Brassat | Torsten Brassat]]
* [[User:Jtmapmedia | Jörg Thomsen]]
* [[User:Silke Reimer | Silke Reimer]]
* [[User:Till Adams | Till Adams]]
* [[User:Athina Trakas | Athina Trakas]]
* [[User:mlechner | Marco Lechner]]
* [[User:maltehm | Malte Halbey-Martin]]
* [[User:Kai Behncke | Kai Behncke]]
* [[User:Cplass | Christian Plass]]
* [[User:Thomas Kastler | Thomas Kastler]]
* [[User:Constanze Tschritter | Constanze Tschritter]]
* [[User:Marko Samson | Marko Samson]]
* [[User:Markus Weißmann | Markus Weißmann]]
* [[User:Robert.Dettmann | Robert Dettmann]] ([http://www.creata-software.de/ creaTa Software GmbH])
* [[User:Verena Diewald | Verena Diewald]]
* [[User:sholl | Stephan Holl]]
* [[User:GEppelt | Gunter Eppelt]]
* [[User:Sholler | Sebastian Holler]]
* [[User:Thomas Baschetti | Thomas Baschetti]]
* [[User:Peter Loewe| Peter Löwe]]
* [[User:Peter_panther| Florian Thürkow]]
* [[User:Fjbehr| Dr. Franz-Josef Behr]]
* [[User:crischan| Christian Wygoda (FH Eberswalde)]]
* [[User:Uwe.Seidel| Uwe Seidel (http://www.seicontec.net)]]
* [[User:Khoffmann | Karsten Hoffmann]]
* [[User:Schpidi | Stephan Meißl]]
* [[User:rnuske | Robert Nuske]]
* [[User:gritibaenz | Adrian Matter]]
* [[User:Martin Hüben | Martin Hüben]]
* [[User:Simon Appelt | Simon Appelt]]
* [[User:Liechtm | Matthias Liechti]]
* [[User:hporath | Holger Porath]]
* [[User:Pirmin_Kalberer | Pirmin Kalberer]]
* [[User:gerhard | Gerhard Schrotter]]
* [[User:Simon Schneider | Simon Schneider]]
* Ladzinski
* [[User:Neumann | Andreas Neumann]]
* [[User: hdus | Dr. Horst Düster]]
* Bitte tragen Sie sich hier mit Link auf Ihren OSGeo-Wiki Account ein.

[[Category:Local Chapters]]

OSGeo Cartographic Engine

2008-04-04T06:35:55Z

Wiki-Hdus: /* Interested people */

== Motivation ==

There are plans about new cartographic tools (map composer) for QGIS, as well as for GRASS. We suggest to develop a joint library for the various functions which could be shared across GRASS, QGIS and other projects with bindings to Qt, Python etc. The GUI part will be done within the individual software projects.

== Functionality ==

Shared functions may include

* break for classes (various algorithms)
* histogram analysis
* color ramps
* RGB and possibly CYMK support (aka color transformations) etc.
* ... (add here)

== Programming Language ==

* C? C++?

== Existing code to be recycled ==

There will be code in GRASS, QGIS, the Python Cartographic Library (http://zcologia.org/cartography) and other sources which could be integrated (check license compatibility).

== License ==

It is proposed to license the OSGeo Cartographic Library under LGPL. The license needs to be GPL compliant.

== Interested people ==

* [[User:Neteler|Markus Neteler]]
* Horst Düster

OSGeo Cartographic Engine

2008-04-04T06:35:07Z

Wiki-Hdus: /* Interested people */

FOSS4G2007 CodeSprint

2007-09-10T10:02:03Z

Wiki-Hdus: /* Attending */

Back to [[FOSS4G2007]]...

== Organizing Contacts ==

* [[User:Jive | Jody Garnett]]

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

== Motivation and Direction ==

A day, a code base, and your imagination?

On the Friday after the conference, a [http://www.foss4g2007.org/code_sprint/ big room] with internet connectivity, lots of tables and flip charts will be arranged. 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

To participate, start a section below for your project.

== GeoTools ==

=== Attending ===

* Andrea Aime
* [[User:Jdeolive | Justin Deoliveira]]
* [[User:Jive | Jody Garnett]]
* [[User:Chorner | Cory Horner]]

=== Goals ===

We are going to to do a cross project code sprint (with GeoServer and uDig developers) focused on changing the internals over to the new Feature model. If we run across any old Filter code we will take care of it as well. The "old" Feature interface will still be available for client code to use - this sprint is just focused on updating (and testing the heck out of) our internals.

=== Preparation ===

We need *good* code examples of how to do the following before we start: Use SimpleFeatureTypeBuilder, use SimpleFeatureBuilder. It may also help to have a big old class diagram of the Feature model.

We expect each developer to have a working build of trunk, have read the interfaces for SimpleFeature and the above code examples.

=== Out of Scope ===

There are lots of things that are going to have to follow out of scope for this sprint. I am going to bring attention to the following explicitly. *Performance* (the implementation of SimpleFeature available here is for the transition period only - optimize on your own time after we have updated the codebase to handle it). *Javadocs* - much of the javadocs will be out of date by the time we are done, type a sentence and move on.

During the code sprint you will be tempted - when you run into any good ideas on these topics simply fire an email off to the devel list and we will revisit it later.

== GRASS ==

=== Attending ===

=== Goals ===

* Hack session

== GDAL Bug Squash ==

Details at: http://trac.osgeo.org/gdal/wiki/BugSquash2007

== GeoNetwork / Metadata Madness ==

=== Goals ===

Building crawler/harvester/aggregator applications on top of the GeoNetwork metadata catalog network and similar interfaces. Plugging client stuff like gvSIG and uDig into it.

=== Attending ===

* [[User:JoWalsh|Jo Walsh]]
* [[User:Fxp|François Prunayre]]

== OpenLayers ==

=== Attending ===

* [[User:crschmidt|Christopher Schmidt]]
* [[User:aaronr|Aaron Racicot]]
* [[User:tschaub|Tim Schaub]]
* [[User:euzuro|Erik Uzureau]]
* [[User:ominiverdi|Lorenzo Becchi]]
* [[User:SchuylerErle|Schuyler Erle]]
* [[User:pagameba|Paul Spencer]]
* [[User:pgiraud|Pierre Giraud]]

=== Goals ===
Hack, hack, hack. I think this will be OpenLayers 2.6 or 2.7?

Some specific ideas:
* OL Context/WMC+ - read/write support for and OWS Context style doc
* SLD support - edit/read/write
* Renderer Optimizations
** consider attributing geometry components with a minResolution below which the renderer doesn't deal with them
** clipping - svg supports clipping, we need to consider clipping or another method of dealing with geometries that extend beyond the renderer bounds
** add <canvas> renderer
* integrate emanual's animated zooming stuff

== QGIS ==
=== Attending ===
* [[User:Gsherman|Gary Sherman]]
* [[User:Aaronr|Aaron Racicot]]
* [[User:spacedman|Barry Rowlingson]]

=== Goals ===
Here are some goals/wishes/ideas for the code sprint:

1. I would love to get some traction on expanding the "Tim Tutorials" into a more generic and robust framework for stand alone apps. Focusing on the Python bindings would be my preference. (Aaron Racicot)

2. Build an ''all-in-one'' data browser:
* Display a tree of all QGIS supported types, including PostGIS and WMS
* Support drag and drop from the browser to the QGIS map canvas
* Include file/layer management tools

3. I would prefer a discussion in which direction symbolisation should go. (Horst Düster)

== SWIG Bindings ==

SWIG bindings are increasingly used and could be used by many projects. GDAL uses them, and this sprint will focus in GDAL's (new generation) bindings but more general discussion, goal setting, and talk on integration is very much hoped for.

=== Attending ===

* [[User:ajolma|Ari Jolma]]
* [[User:szekerest|Tamas Szekeres]]

=== Goals ===

* present a short introduction to SWIG (AJ: I'll prepare this)
* develop a vision of how we integrate tools and create common look and feel high-level programming interfaces with SWIG bindings

Specifically for GDAL (from Tamas Szekeres' email):

* harmonize the typemap usage between the various bindings (and update the README.typemaps accordingly)
* determine which of the gdal/ogr features should be added to (or perhaps removed from) the SWIG interface.
* look over the possibilities to automate the creation of the code-comment-documentation for the various languages.
* construct the expected object model diagram to follow by the various languages (and publish the model itself)
* discuss the language specific issues and the expected treatments.

== Udig / JGrass ==

Cross project code sprint with the JGrass and uDig projects.

=== Attending ===

* [[User:Moovida | Andrea Antonello]]
* [[User:jeichar | Jesse Eichar]]
* [[User:silli | Silvia Franceschi]]
* [[User:Jive | Jody Garnett]]

=== Goals ===
Currently these are proposals we are working on selecting a subset of these goals.

{| border="1"
|-
! Topic
! Description
|-
| Animation Framework
| If we could code up an example animation (say a point moving over a road network), then it becomes much easier for newcommers to work on fleshing this out. We could come up with a list of topics as the meeting draws nearer and decide on site as to which we wanted to tackle.
|-
| Debug uDig Trunk
| uDig trunk was moved to GeoTools trunk some time ago but the changes were major and many bugs still exist. Styling for example still doesn't work
|-
| Simple Feature
| GeoTools is doing a cross project code sprint and will need a uDig developer to update our trunk to SimpleFeature
|-
| Better GRASS compatibility
| better GRASS compatibility through JGrass
|-
| Wizard and DND
| Separate catalog wizards and Drag and Drop code to simplify both problems
|-
| Rendering
| Rendering has been in need of an overhaul for quite some time. Lets fix it
|-
| Remove Cruft
| Lets comb the code base and get rid of some of the ugly/unused
|-
| 3D visualization
| let's talk a bit about 3D, jogl, jirr and other nasty things and udig
|-
| Italian translation of uDig
| I know this is rather utopic, but you never know :)
|-
| Definition of a portable workspace
| UDig should have the possibility to export the workspace, either automagically or even by just moving a folder from one user to the other. It's about relative paths, about copying data eventually into the workspace and things like that. I believe this is a critical problem for usability. Should remember to isolate username/password information as well.
|}

==== Voting (scale 1-5)====
{| border="1"
|-
! ID
! Voter
! Voter
! Voter
! Voter
! Voter
|-
| Animation Framework
| 1
| 4
| 4
| 1
| 4
|-
| Debug uDig Trunk
| 1
| 1
| 0
| 4
| 4
|-
| Simple Feature
| 2
|
|
|
| 2
|-
| Better GRASS compatibility
| 3
| 5
| 5
| 2
| 0
|-
| Wizard and DND
| 4
| 3
| 0
| 4
| 3
|-
| Rendering
| 4
| 3
| 5
| 4
| 4
|-
| Remove Cruft
| 4
| 3
| 0
| 3
| 4
|-
| 3D visualization
| 5
| 5
| 5
| 4
| 4
|-
| Italian translation
| 2.5
| 3
| 5
| x
| 0
|-
| Portable workspace
| 4
| 5
| 5
| 4
| 1
|}

== French translation ==
Contact: [[User:Yjacolin|Yjacolin]]
=== Attending ===
See [[OSGeo_fr_FOSS4G_2007_fr#Traduction_sprint|Translation sprint (in french)]]
=== Goals ===
Translate a documentation into french. The document has to be defined, some exemple : qgis, openlayers, OSGeo website, GRASS, MapBuilder, MapLab, OSGeo Journal Vol. 2, etc.

[[Category:Events]]
[[Category:FOSS4G2007]]
[[Category:FOSS4G]]

FOSS4G2007 CodeSprint

2007-08-07T09:06:58Z

Wiki-Hdus: /* Attending */

FOSS4G2007 CodeSprint

2007-08-07T09:06:14Z

Wiki-Hdus: /* Goals */