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

'''Gold Sponsors'''

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

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

'''Silver Sponsors'''

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

'''Bronze Sponsors'''

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

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

'''Venue Sponsor'''

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

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

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

== Purpose ==

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

== Venue ==

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

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

'''Directions'''

Convenient route planning for public transportation: http://www.wienerlinien.at/ (both German and English)

From the airport take the train S-Bahn S7 going to Wien Floridsdorf and exit
at Praterstern (~30min). Make sure to avoid the CAT as it doesn't bring you
to Praterstern and I consider it too costly for gaining just 10 minutes.

From Praterstern take the subway U-Bahn U2 going to Seestadt and exit at
Stadlau. Now either take a 15 minutes walk to the venue or take the bus
Autobus 86A going to Breitenleer Straße/Arnikaweg or 87A going to
Hermann-Gebauer-Straße and exit at Genochplatz.

From Praterstern instead of the U2 you can also take the subway U-Bahn U1
particularly when going to the Hotel Hillinger. Take the U1 going to
Leopoldau and exit at Kagran. Now take the tram Straßenbahn 25 going to
Oberdorfstraße or the bus Autobus 26A going to Großenzersdorf and exit at
Polgarstraße for the Hotel Hillinger or continue to Konstanziagasse for the
code sprint venue.

== Dates and Times ==

March 24-28 2014

Note: March 19-21 FOSSGIS Berlin

Duration: Full week

== Agenda ==

=== Sunday Ice Breaker ===

If you're in Vienna already on Sunday you're invited to join us for a small
ice breaker starting from 7pm at Green - Cafe-Wok-Grill-Restaurant which is
located next to the sprint venue. You will see the signs when you enter the
plaza of Star22.

=== Project Plans ===

On Monday we will start 9ish with some sort of "official" opening around 10.

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

<add your agenda>

== Hotel ==

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

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

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

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

=== Hotel Wiener Kindl ===

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

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

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

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

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

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

=== Hotel Hillinger ===

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

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



== Individual Preparation ==

* Bring your own computer
* Bring [http://en.wikipedia.org/wiki/AC_power_plugs_and_sockets AC power connector adapter] if needed (Austria {{wikipedia|File:Schuko_plug_and_socket.png|CEE 7/4 (German "Schuko")(Type F)}})
* Install git, subversion and the compiler tools, and come with a working development environment if possible

== FAQ ==

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

== Social Activities ==

=== Welcome party ===

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

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

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

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

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

=== Skiing ===

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

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

== Budget ==

TBD

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

Vienna Code Sprint 2014

2013-12-14T15:42:46Z

Wiki-Pcav:

Vienna Code Sprint 2014

2013-09-25T06:47:42Z

Wiki-Pcav: /* Participants */

'''Gold Sponsors'''

TBA

'''Silver Sponsors'''

TBA

'''Bronze Sponsors'''

TBA

'''Venue Sponsor'''

[http://www.wien.gv.at/english/administration/ict/index.html City of Vienna, MA 14] [[Image:Logo-City-of-Vienna.png|400px|City of Vienna MA 14|link=http://www.wien.gv.at/english/administration/ict/index.html]]

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

[http://eox.at EOX] [[Image:Logo-EOX.png|120px|EOX IT Services GmbH|link=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, 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 30 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 (TBD)

== Agenda ==

TBD

== Hotel ==

A hotel block is planned to be negotiated. Details will be provided here.

== Costs ==

Participants should plan for the following costs:

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

== Project Plans ==

TBD

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

# [[User:schpidi|Stephan Meissl]] - MapServer - Definite - No special needs
# [[User:ahocevar|Andreas Hocevar]] - OpenLayers - Definite -
# [[User:pwramsey3|Paul Ramsey]] - PostGIS - Very Likely
# [[User:msmitherdc|Michael Smith]] - PDAL/MapServer - Very Likely
# [[Jeff McKenna]] - MapServer - Very Likely
# [[User:Dmorissette|Daniel Morissette]] - MapServer, GDAL/OGR - Very Likely
# [[User:hobu|Howard Butler]] - MapServer, GDAL/OGR, PDAL - Very Likely
# Olivier Courtin - PostGIS, TinyOWS - Very Likely
# [[User:Lucadelu|Luca Delucchi]] - GRASS GIS - Very Likely
# [[User:Landa|Martin Landa]] - GRASS GIS, PostGIS, GDAL/OGR - Very Likely
# [[User:TBonfort|Thomas Bonfort]] - MapServer - Very Likely
# [[User:Szekerest|Tamas Szekeres]] - MapServer, GDAL/OGR - Very Likely
# [[User:Mloskot|Mateusz Loskot]] - PDAL - Likely
# [[User:pcav|Paolo Cavallini]] - QGIS - Possible

== Individual Preparation ==

* Bring your own computer
* Install 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?
** No, this is not a presentation-oriented event. People will get together in small groups and work on areas of mutual interest within their projects.

== Social Activities ==

TBD

== Sponsors ==

We have three sponsorship levels:

* Gold: €1500+, Silver: €1000, Bronze: €500

We encourage sponsors (€500+) to support nutriment and entertainment for the
sprinters as they work hard and play hard for five productive days.
Contributions will be put towards lunch, snacks, and dinner costs for the
sprinters, and potentially bringing in sprinters who might otherwise be unable
to attend. Any surplus at the end of the event will be turned over to OSGeo or
used for a future code sprint.

Sponsors will receive the following honors:

* Your logo or portrait at the top of this page
* 30-min slot to talk about how you are using FOSS GIS at the sprint
* Get to stare at us during the sprint and voice your input in person
* Our undying gratitude, which comes in handy when you least expect it (Remember that feature you wanted...)

To sponsor, please contact Stephan Meissl (stephan.meissl at eox dot at) directly.

=== 2014 Sponsors ===
==== Gold ====
TBA
==== Silver ====
TBA
==== Bronze ====
* [http://metaspatial.net metaspatial] (unconfirmed)

==== Venue Sponsor ====
City of Vienna MA 14

== Budget ==

TBD

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

User:Pcav

2013-05-17T05:02:07Z

Wiki-Pcav: Created page with "http://faunalia.eu/pc"

http://faunalia.eu/pc

SDI Committee

2013-05-17T05:00:56Z

Wiki-Pcav: /* Members */

<div style="font-size: 12pt; margin: 20px; background-color: #f9f9f9; border: 2px dotted; padding: 10px;">
'''NOTE:''' This wiki page was created based on discussion on the [http://lists.osgeo.org/pipermail/discuss/2013-May/011709.html mailing list]. The OSGeo SDI Committee was not established yet. This wiki page is to be used for the committee's establishing.
</div>

== About ==
A spatial data infrastructure (SDI) is a data infrastructure implementing a framework of geographic data, metadata, users and tools that are interactively connected in order to use spatial data in an efficient and flexible way. [http://en.wikipedia.org/wiki/Spatial_data_infrastructure Wikipedia:SDI]

OSGeo considers the ability of its software projects to implement various SDIs an important feature for organizations around the world.

=== Software components of SDIs ===
Basic software components of SDI are:

* catalogue service
* spatial data service
* processing services
* spatial data repository

* Client software (desktop and web) communicates via standards to those services, which interacts directly with the user. It enables download, display, query, analysis and updating spatial data.

OSGeo projects cover all these software components. Some of them are covered by multiple OSGeo projects.

=== Standards ===
Most SDIs are related to [http://www.opengeospatial.org/standards/is OGC standards] (OGC OWS) as well as [http://www.iso.org/iso/home/standards.htm ISO]. They are all well implemented in OSGeo projects.

=== Current SDIs ===
* [http://en.wikipedia.org/wiki/GEOSS GEOSS] Global Earth Observation System of Systems. 2005-2015
* [http://en.wikipedia.org/wiki/GMES GMES] Global Monitoring for Environment and Security. Should be fully operational during 2014
* [http://en.wikipedia.org/wiki/INSPIRE INSPIRE] Infrastructure for Spatial Information in the European Community. See also [[INSPIRE]]
* [http://en.wikipedia.org/wiki/UNSDI UNSDI] United Nations Spatial Data Infrastructure
* [http://en.wikipedia.org/wiki/National_Spatial_Data_Infrastructure NSDI] National Spatial Data Infrastructure
* [http://cgdi.ca/ CGDI] Canadian Geospatial Data Infrastructure
* ''add more here''

== Goals ==
* Coordinate efforts of development teams
* Help to make OSGeo software stack the best choice for SDIs implementation
* Promote OSGeo software stack, as the best choice for SDIs implementation
* ...

== Methods ==
* Checklists
* Tests
* Reference implementations
* ''Relevant'' case studies

== Communication ==
* Mailing list
* IRC meetings
** how often should meetings occur?

== Members ==
* [[user: jachym | Jáchym Čepický]]
* [[user: tomkralidis | Tom Kralidis]]
* [[user: Stranger | Andreas Schmitz]]
* [[user: kwilcox| Kyle Wilcox]]
* [[user: maxi71 | Massimiliano Cannata]]
* [[user: Vasile | Vasile Crăciunescu]]
* [[user: Mlechner | Marco Lechner]]
* [[user: JoCook | Jo Cook]]
* [[user: Huwer | Rafal Wawer]]
* [[User: Madi | Margherita Di Leo]]
* [[User: aaime | Andrea Aime]]
* [[User: maria | Maria Brovelli]]
* [[User:ticheler | Jeroen Ticheler]]
* [[Arnulf Christl]]
* [[User:pcav | Paolo Cavallini]]

* ''Add your name, if you would like to be active member of the committee''

[[Category:Committees]]

Geoservices REST API

2013-05-09T16:25:01Z

Wiki-Pcav: /* Signed */

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

= Open Letter to OGC and voting members =

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

May 2013

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

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

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

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

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

= Concerns =
--- DRAFT ____

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

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

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

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

== Political Concerns ==

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

== Commercial Concerns ==

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

== Technical Concerns ==

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

== Methodological Concerns ==

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

= History =

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

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

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