OSGeo - User contributions [en]

Vienna Code Sprint 2014

2014-02-11T14:17:02Z

Wiki-Wellsp: /* Participants */

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

'''Gold Sponsors'''

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

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

'''Silver Sponsors'''

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

'''Bronze Sponsors'''

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

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

'''Venue Sponsor'''

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

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

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

== Purpose ==

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

== Venue ==

The City of Vienna MA 14 gladly provides the location for the Vienna Code Sprint for up to 60 sprinters in [http://www.wien.gv.at/stadtplan/grafik.aspx?lang=de-AT&bookmark=zHClRv95TUbsTHFEFcAeRO5RphlRnHnkur2pH4Oprw-b-b&bmadr=25723751 their very new office called STAR 22].

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

== Dates and Times ==

March 24-28 2014

Note: March 19-21 FOSSGIS Berlin

Duration: Full week

== Agenda ==

TBD

=== Project Plans ===

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

== Hotel ==

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

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

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

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

=== Hotel Wiener Kindl ===

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

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

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

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

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

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

=== Hotel Hillinger ===

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

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

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

Accepted payment methods: cash or creditcard.

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

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

=== Alternatives ===

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

== Costs ==

Participants should plan for the following costs:

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

== Communication ==

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

== Participants ==

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

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



== Individual Preparation ==

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

== FAQ ==

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

== Social Activities ==

TBD

Ideas
* Skiing: The idea is to find a not too far away place the weekend after the sprint. Please add your name if you're interested: [[User:schpidi|Stephan Meissl]]

Isn't it a bit late for skiing at this time of the year in eastern Austria?
Yes that's probably right but there should be snow left within 2-3 hours drive. Anyway, given the 'high' interest I didn't assign high priority to this ;)

== Budget ==

TBD

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

Vienna Code Sprint 2014

2014-02-11T14:09:14Z

Wiki-Wellsp: /* Hotel Wiener Kindl */

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

'''Gold Sponsors'''

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

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

'''Silver Sponsors'''

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

'''Bronze Sponsors'''

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

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

'''Venue Sponsor'''

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

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

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

== Purpose ==

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

== Venue ==

The City of Vienna MA 14 gladly provides the location for the Vienna Code Sprint for up to 60 sprinters in [http://www.wien.gv.at/stadtplan/grafik.aspx?lang=de-AT&bookmark=zHClRv95TUbsTHFEFcAeRO5RphlRnHnkur2pH4Oprw-b-b&bmadr=25723751 their very new office called STAR 22].

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

== Dates and Times ==

March 24-28 2014

Note: March 19-21 FOSSGIS Berlin

Duration: Full week

== Agenda ==

TBD

=== Project Plans ===

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

== Hotel ==

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

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

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

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

=== Hotel Wiener Kindl ===

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

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

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

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

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

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

=== Hotel Hillinger ===

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

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

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

Accepted payment methods: cash or creditcard.

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

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

=== Alternatives ===

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

== Costs ==

Participants should plan for the following costs:

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

== Communication ==

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

== Participants ==

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

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



== Individual Preparation ==

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

== FAQ ==

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

== Social Activities ==

TBD

Ideas
* Skiing: The idea is to find a not too far away place the weekend after the sprint. Please add your name if you're interested: [[User:schpidi|Stephan Meissl]]

Isn't it a bit late for skiing at this time of the year in eastern Austria?
Yes that's probably right but there should be snow left within 2-3 hours drive. Anyway, given the 'high' interest I didn't assign high priority to this ;)

== Budget ==

TBD

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

Vienna Code Sprint 2014

2014-01-08T16:56:16Z

Wiki-Wellsp: /* Participants */

Geoservices REST API

2013-05-10T19:34:53Z

Wiki-Wellsp: /* Signed */

This wiki page aims to collate community concerns related to the adoption of the "Geoservices REST API" document as a standard of the Open Geospatial Consortium (OGC). The page is being collaboratively edited, targeting completion before the end of May 2013.

= 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, which 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 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, Prinicipal Scientist for RadiantBlue Technologies Inc.
# [[User:Woodbri|Stephen Woodbridge]], Director of [http://imaptools.com iMaptools.com], Contributor and/or PSC of [http://mapserver.org Mapserver], [http://pgrouting.org/ pgRouting], [http://www.pagcgeo.org/ PAGC], and [http://www.postgis.org/ PostGIS]
# [[User:rouault|Even Rouault]], Geospatial developer, OSGeo Charter Member, core contributor and PSC member of [http://gdal.org GDAL/OGR], contributor of [http://mapserver.org Mapserver], [http://trac.osgeo.org/proj/ PROJ.4], [http://trac.osgeo.org/geotiff/ libgeotiff], [http://shapelib.maptools.org/ shapelib], [http://www.remotesensing.org/libtiff/ libtiff]
# Gerhard Triebnig, Managing Director at [http://eox.at EOX IT Services GmbH]
# [[User:pcreso|Brent Wood]], Environmental Information Delivery Programme Leader, NIWA, New Zealand. OGC member, Aust/NZ OSGEO chapter member, NZOSS Council member
# [[User:Schpidi|Stephan Meissl]], CTO at [http://eox.at EOX IT Services GmbH], contributor to [http://mapserver.org Mapserver], PSC chair of [http://eoxserver.org EOxServer]
# [[User:ticheler|Jeroen Ticheler]], Director of [http://geocat.net GeoCat], project founder and PSC chair of [http://geonetwork-opensource.org GeoNetwork opensource]
# [[User:Just|Just van den Broecke]], Director at [http://www.justobjects.nl Just Objects], contributor to [http://heron-mc.org Heron Mapping Client], secretary of [http://osgeo.nl OSGeo Dutch Local Chapter], member at [http://www.opengeogroep.nl OpenGeoGroep]
# [[User:milovanderlinden|Milo van der Linden]], member at [http://www.opengeogroep.nl OpenGeoGroep]
# [[User:surveyor|Landon Blake]], GIS Department Manager/Land Surveyor at [http://www.ksninc.com KSN], OSGeo California Chapter Board Representative.
# [[User:dmorissette|Daniel Morissette]], President at [http://mapgears.com/ Mapgears], core contributor and PSC member of [http://mapserver.org Mapserver] and [http://gdal.org GDAL/OGR]. Former OGC TC member and involved in the implementation of several OGC WxS services specs in MapServer.
# [[User:blammo|Bob Basques]], GIS Systems Developer at the City of Saint Paul, MN. [http://gis.ci.stpaul.mn.us Public Works GIS (GISmo)], Technical Director at [http://www.sharedgeo.org SharedGeo], OSGeo Charter Member, OSGeo TCMUG local chapter member, Co-founder and PSC member of [http://www.geomoose.org GeoMoose] project.
# [[User:vehrka|Pedro-Juan Ferrer Matoses]], PM at Omnium Strategic Intelligence, Spain, OSGeo Charter Member, OSGeo Spanish Local Chapter Liaison officer.
# Bevan Rudge, Director Lucion Limited, IT Advisor at Conservation Strategy Fund, Esri client
# [[User:Delawen|María Arias de Reyna]], software engineer at [http://geocat.net GeoCat], Spain, member of OSGeo Spanish Local Chapter.
# [[User:Aghisla|Anne Ghisla]], OSGeo Board Member, Italy, member of OSGeo Italian Local Chapter.
# [[User:Michogar|Micho Garcia]], Freelance and member of [http://geomati.co geomati.co], Spain, member of Spanish Local Chapter
# [[User:Madi|Margherita Di Leo]], OSGeo Charter Member, 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

= Summary =

The document titled "GeoServices REST API" is currently, in May 2013, being considered as a standard of the Open Geospatial Consortium (OGC). 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.

The adoption of the document is contentious for a wide variety of reasons including:

* the process through which it was developed,
* the language of 'REST' and 'API' used by the document,
* the names of the standard and of the services which are potentially confusing
* the duplication of these new services with other services standardized by the OGC such as WMS, WFS, WCS, and WPS and with work, by those services, of adopting RESTful designs including URL hierarchies and JSON exchange formats,
* the specific format of JSON messages used, and
* the dominance of the vendor of the single complete implementation in the marketplace.

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 of 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 is a feel 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.

These issues have been answered by the authors of the document who state:

* 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 of some of these services.

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

= Positions on the vote =

The discussion raises a number of issues even beyond those mentioned above. This makes difficult any rational decision by the voting members of the OGC Technical Committee, who will determine adoption or rejection of the vote.

The following is the analysis of positions on the vote, originally from a single person on his own point of view and therefore reaching a conclusion appropriate in particular to him. Obviously the signatories of the letter at the start of this page have reached different conclusions.

; The pros:

:* The OGC should be in the business of developing good standards, not of choosing which standards should be implemented.
:* The proposers of the document want to make a standard and have followed all the rules of the consortium. 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 an author of standards at the OGC, 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 is, de-facto, in the position of recommending the 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 the desire to support this approach by the OGC membership is limited. The lack of collaboration on this version 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 implemetation.
:* 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 rewrite. (see at end)

; The 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. (On that, perhaps they should be allowed to make their own mistakes.) The path forwards towards harmonizing the services is unclear. There is little good will towards the standard on behalf of the membership. 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 a third way?

Well, actually, there is. The natural consequence of either decision is a renewed commitment towards trying to build this thing that we want, an integrated suite of simple services built using simple, well defined resources, accessible and usable using the core HTTP verbs, and discoverable through following links. That's the good way forwards and why to focus work on WMS-Next, WCS JSON bindings, and other modular extensions to OGC services.

= Issues with the document =

Beyond the controversy described above, there are issues with the standard 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.

The critique can be found on the separate [[Geoservices_REST_API_critique]] page.

Note that some of these critiques hold the document to the current, higher standard of the OGC. 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.

= Further Concerns =
--- DRAFT ____

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

== Political Concerns ==

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

== Commercial Concerns ==

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

== Technical Concerns ==

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

== Methodological Concerns ==

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

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 other processes.

= References =
* 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 eloquent, unbiased, concise summary of the technical issues: 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]]