OSGeo - User contributions [en]

FOSS4G-Europe 2020 Code Sprint

2020-01-03T07:33:40Z

Wiki-Peteris: Peteris moved page FOSS4G-Europe 2020 Code Sprint to FOSS4G-Europe 2020 Community Sprint: Recommendation to change code to community

#REDIRECT [[FOSS4G-Europe 2020 Community Sprint]]

FOSS4G-Europe 2020 Community Sprint

2020-01-03T07:33:40Z

Wiki-Peteris: Peteris moved page FOSS4G-Europe 2020 Code Sprint to FOSS4G-Europe 2020 Community Sprint: Recommendation to change code to community

== Community Sprint ==

As usual in FOSS4G conferences, we also are following the OSGeo tradition of hosting a Community Sprint right after [https://europe.foss4g.org/2020 FOSS4G Europe 2020].

Participation is free of charge and anyone involved or interested in getting involved in OSGeo community projects is welcome.

You can choose to contribute to one or more projects. There’s always something to do – translate, document, give feedback, discuss, and test. All activities are very important for projects! Conference registration is not required for participation in code sprint.

=== When ===
The community sprint will be held on Friday 17.07.2020 and on Saturday 18.07.2020.

=== Where ===

Vidzeme University (Valmiera, Latvia)
* Vidzemes Augstskola, Cēsu street 4 or Tērbatas street 10, Valmiera
* https://va.lv/en

== Registered Attendees ==
The code sprint is free of charge but we kindly ask you to write down your name for better planning

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|No
!width="250"|Name
!width="250"|Email
!width="250"|Projects
!width="250"|Friday
!width="250"|Saturday
!width="30"|vegetarian food
|-
|1 || [[User:userid|User Name]] || e-mail@e-mail.com || Foo Bar || x || x ||
|+
|}

== Workgroups ==

=== Project-name ===
To participate, copy this project skeleton and start a section below for your project.

'''Attending:'''
*user
*user

'''Goals:'''
*your goals

== Event Organization ==

The [https://2020.europe.foss4g.org/about/ VLOC] is the organiser of the community sprint.

For any question you can contact [[User:peteris|Peteris Brūns]] or [[User:Marisn|Māris Nartišs]], the persons in charge of the code sprint.

[[Category:FOSS4G2020]] [[Category:FOSS4G]] [[Category:Code_Sprints]]

FOSS4G-Europe 2020 Community Sprint

2020-01-03T07:32:27Z

Wiki-Peteris: Renamed code to community.

FOSS4G-Europe 2020 Community Sprint

2019-12-16T18:28:24Z

Wiki-Peteris: Codesprints, initail version.

== Code Sprint ==

As usual in FOSS4G conferences, we also are following the OSGeo tradition of hosting a code sprint right after [https://europe.foss4g.org/2020 FOSS4G Europe 2020].

Participation is free of charge and anyone involved or interested in getting involved in OSGeo community projects is welcome.

You can choose to contribute to one or more projects. There’s always something to do – translate, document, give feedback, discuss, and test. All activities are very important for projects! Conference registration is not required for participation in code sprint.

=== When ===
The code sprint will be held Friday 17.07.2020 and Saturday 18.07.2020.

=== Where ===

Vidzeme University (Valmiera, Latvia)
* Vidzemes Augstskola, Cēsu street 4 or Tērbatas street 10, Valmiera
* https://va.lv/en

== Registered Attendees ==
The code sprint is free of charge but we kindly ask you to write down your name for better planning

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|No
!width="250"|Name
!width="250"|Email
!width="250"|Projects
!width="250"|Friday
!width="250"|Saturday
!width="30"|vegetarian food
|-
|1 || [[User:userid|User Name]] || e-mail@e-mail.com || Foo Bar || x || x ||
|+
|}

== Workgroups ==

=== Project-name ===
To participate, copy this project skeleton and start a section below for your project.

'''Attending:'''
*user
*user

'''Goals:'''
*your goals

== Event Organization ==

The [https://2020.europe.foss4g.org/about/ VLOC] is the organiser of the code sprint.

For any question you can contact [[User:peteris|Peteris Brūns]] or [[User:Marisn|Māris Nartišs]], the persons in charge of the code sprint.

[[Category:FOSS4G2020]] [[Category:FOSS4G]] [[Category:Code_Sprints]]

User:Peteris

2019-10-08T20:34:45Z

Wiki-Peteris:

{{OSGeo Member
|Name=Pēteris Brūns
|Company=SIA SunGIS
|Country=Latvia
|City=Valmiera
|Coordinate=57.53805, 25.42292
|Website=https://sungis.lv
|Languages=Latvian; English; Russian;
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=No
|Translate=Yes
|PSC=No
|ExBoard=No
|Charter=No
|Chair=No
|SolKatz=No
|Committer=No
}}
QGIS and GRASS GIS translator to Latvian language.
Member of organisational committee of QuantumGIS developer meeting in Valmiera, 2013.
System architect and analyst, GIS/IT consultant.

;Contact:
: Email: pb@sungis.lv, peteris.bruns@gmail.com
: GitHub: https://github.com/peterisb
: Twitter: https://twitter.com/sungis

User:Peteris

2019-10-08T20:30:34Z

Wiki-Peteris:

QGIS and GRASS GIS translator to Latvian language.
Member of organisational committee of QuantumGIS developer meeting in Valmiera, 2013.

{{OSGeo Member
|Name= Pēteris Brūns
|Country=Latvia
|City=Valmiera
|Coordinate=57.53805, 25.42292
|LocalChapter=
|Company=SIA SunGIS
}}

{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=No
|Translate=Yes
|PSC=No
|ExBoard=No
|Charter=No
|Chair=No
|SolKatz=No
|Committer=No
}}

;Contact:
: Email: pb@sungis.lv, peteris.bruns@gmail.com
: GitHub: https://github.com/peterisb
: Twitter: https://twitter.com/sungis

===Pēteris Brūns===
System architect and analyst, GIS/IT consultant.

Location: Valmiera, Latvia

Conference-Europe-2020

2019-09-30T15:42:21Z

Wiki-Peteris: /* Proposals Submitted */

= Call for venue =

FOSS4G-Europe conference committee invites all interested groups from Europe to ''Call for venue''

<del>The proposals shall be submitted by '''2019-06-30''' to [https://lists.osgeo.org/mailman/listinfo/conference-europe Conference-europe mailing list].</del>

The deadline for proposals shall was extended till '''2019-09-30''' to [https://lists.osgeo.org/mailman/listinfo/conference-europe Conference-europe mailing list].

== Parameters of the propsal ==

* Expect around 400-500 attendees (sofar, the number was between 100+ at FOSS4G-CEE 2012, Prague, to 400 people FOSS4G-Europe, Como). We do not set any upper limit to attendees number - this lies solely at LOC.
* The growing number of participants is not the main scope of the event. We rather prefer modest costs for attendees, therefore co-organising the event with universities might be of good way, how to ''keep the costs lower''.
* Cooperation with universities of course implies careful selection of conference date, which is usually, but not necessary, in the holiday season.
* Although the policy in Europe has changed, we still advice you to make sure, that the venue is covered with stable and relayable WIFI connectivity.
* Communication language is English
* FOSS4G-Europe is usually 3 days conference, with 4 parallel sessions, each talk was arranged for 30 minutes (including discussions)
* Please consider also, that workshops are part of the conference, you shall organize rooms, ideally with computers. The workshops can provide both 4-hours and 8-hours slots.
* You should provide also several rooms during the conference, for BOF meetings
* Usually Code Sprint events are part of the conference - it is preferred, if you could arrange rooms at least after or before the conference itself (about 1-2 days), if you could cover both time frames, it would be appreciated.
* Please, refer [[FOSS4G_Manifesto#FOSS4G_Europe_Manifesto|FOSS4G-Europe Manifesto]] for further details
* There also is [[FOSS4G_Handbook|FOSS4G Handbook]] you might see useful
* We believe, students are our future - please take significant discount for students into your budget proposal

== Position of the Local organisation committee to OSGeo and Conference committee Europe ==

* The [[Conference-Europe#Committee|FOSS4G-Europe Conference committee]] will, after the selection process, "kindly ask" the best venue offer, to host FOSS4G-Europe on behalf of OSGeo-European chapter (in formation)
* There is possibility to negotiate with OSGeo.org for the seeding money for necessary spending under the condition, that the LOC will guarantee at least balanced budget during the final countings. The seeding money shall be negotiated with OSGeo Board of directors
* Program committee shall be delegated from nominees from LOC as well as OSGeo on mutual understanding manner.

== Dates ==

(might be adjusted during the time, adjusted after FOSS4G 2019 Bucharest meeting)

{| class="wikitable"
|-
! Item !! Date
|-
| Start and end of proposal submission. Proposals shall be sent to Conference-Europe mailing list || '''2019-09-30'''
|-
| Selection period. Proposals will be evaluated by FOSS4G-Europe Conference committee || 2019-09-30 - 2019-10-35
|-
| Venue announcement (At FOSS4G) || '''early autumn 2019'''
|-
| Call for papers and workshops || 2020-01 - 2020-04
|-
| Papers and workshops selection period || 2020-04 - 2020-05
|-
| Conference and accompanying events || ?2020-06 - 2020-07?
|}

== Note on Seeding money ==
* [[Conference_Committee|OSGeo Conference Committee]] along with [[Board_of_Directors|OSGeo Board]] can provide LOC with ''seeding money'' necessary for the start
* LOC needs to guarantee, that after final books closing, the seeding money will be returned back to OSGeo
* It is fair to ask for the seeding money and we encourage LOC to do so - with proper reasoning and proposed budget. But the final decision lies solely at the Board.

== Proposals Submitted ==

* Venue proposal from Latvia, Valmiera ( [[Media:FOSS4G_Europe_2020_Valmiera_proposal.pdf|proposal ]] and estimated [[Media:Osgeo-foss4g-eu-2020-valmiera-conference-budget_-_FOSS4G-Europe_2020.pdf|budget]] )

[[Category: FOSS4G]]
[[Category: FOSS4G-Europe]]

File:Osgeo-foss4g-eu-2020-valmiera-conference-budget - FOSS4G-Europe 2020.pdf

2019-09-30T15:35:28Z

Wiki-Peteris: Valmiera FOSS4GE 2020 proposal budget estimations/guestimations. Original document https://docs.google.com/spreadsheets/d/1ij_Zrpj7yG2ENyaCbaHZF4XSLTHoypcAqb7HmrN_frU/edit#gid=1122554603

Valmiera FOSS4GE 2020 proposal budget estimations/guestimations.
Original document https://docs.google.com/spreadsheets/d/1ij_Zrpj7yG2ENyaCbaHZF4XSLTHoypcAqb7HmrN_frU/edit#gid=1122554603

File:FOSS4G Europe 2020 Valmiera proposal.pdf

2019-09-30T15:32:12Z

Wiki-Peteris: Valmiera FOSS4GE 2020 proposal

Valmiera FOSS4GE 2020 proposal

FOSS4G 2019 BirdsOfAFeather

2019-08-29T11:59:30Z

Wiki-Peteris: /* FOSS4G-Europe 2020 */

= Introduction =

Birds of a Feather (BoF) sessions are unstructured timeslots where people can self-organise themselves to discuss topics of interest.

== General Information ==

During the [[FOSS4G 2019]] conference in Bucharest, there will be a number of spaces for people to hold Birds of a Feather sessions.

For reference, an overview of the FOSS4G schedule is available at [https://2019.foss4g.org/schedule/outline/ https://2019.foss4g.org/schedule/outline/].

=== How to organize a BOF ===

BoF sessions are informal gatherings of people around a specific topic. BoF's can be held in: BoF rooms or taken off-site for breakfast, lunch or dinner!

While FOSS4G is provide space, but the setting up a bird-of-feather meetup is done informally using this wiki, twitter, or on site BoF board.

=== Capacities ===

The BoF sessions rooms are available after regular parallel session times (setup theater style) in the InterContinental Hotel.

* Ronda Ballroom (450 people);
* Fortuna Vest (80 people);
* Fortuna Est (80 people);
* Rapsodia Ballroom (220 people);
* Opera (70 people);
* Opereta (40 people);
* Simfonia (30 people);
* Menuet (50 people);
* Hora (45 people);
* Coral (30 people).

We will put a BoF organizing board next to the lounge for on site organization.

== FOSS4G Contact ==

Reach out to https://twitter.com/foss4g on twitter, or mailto:foss4g2019@lists.osgeo.org via email.

= Wednesday 28 August (18:00 - 19:30) =

== Ronda Ballroom (1st floor) ==

=== OSGeo Charter Member ===

* Description: Are you a charter member? Then come to this BoF to talk about what we do as Charter Members!
* Person to contact: Vicky Vergara
Who is coming:
* Vicky Vergara

== Fortuna Est (21st floor) ==

=== OPEN SCIENCE AND NEW TECHNOLOGIES FORUM AT IPSRS 2020 CONGRESS ===

* Description: The BOF is aimed at organizing the OSGeo Forum that will held at the ISPRS Congress 2020 (http://www.isprs2020-nice.com/) in June 2020
* Persons to contact: Maria Antonia Brovelli (maria.brovelli@polimi.it) and Serena Coetzee (serena.coetzee@up.ac.za)

Who is coming:
* Moritz Lennert

== Rapsodia Ballroom (1st floor) ==

=== GeoForAll meeting ===

* Description: The aim of the BOF is to connect with members of GeoForAll labs and other educators.
* Person to contact: Andreea Marin (andreeamarin19@gmail.com) and Victoria Rautenbach (victoria.rautenbach@gmail.com)

Who is coming:
* Cameron Green
* Andreea Marin
* Zoltan Siki

== Opera (2nd floor) ==

=== MapServer ===

* Description: An opportunity for users and devs to get together for a general discussions about MapServer's past, present and future.
* Person to contact: Seth Girvin and Daniel Morissette

Who is coming:
* Seth Girvin
* Daniel Morissette
* Lars Schylberg
* Even Rouault
* Michael Smith
* Mathieu Coudert
* Stephan Meißl
* Add your name

== Opereta (2nd floor)==

=== Catalog ===

* Description:

- Metasearch; what are the expected/agreed best practices to link to OGC services from a Dublin Core metadata record, so metasearch is able to activate add-to-map button? Is it possible to specify a specific layer in the service so metasearch will not display the capabilities-layer-selection.

- OGC API Catalog (AKA Cat 4) in OGC, MetaSearch, pyGeoAPI, GeoNetwork, Geoserver, deegree

- Catalogs typically use OGC services to provide data previews of listed datasets. OGC is creating a batch of new OGC-API standards which will likely impact catalogs. Many catalogs delegate to OpenLayers and JSONIX to communicate to OGC services. To hear is the status of OpenLayers and JSONIX about ideas on new OGC API's

* Person to contact: Tom Kralidis, Paul van Genuchten

Who is coming:
* Paul
* Tom
* Antonio
* Angelos

== Simfonia (2nd floor) ==

=== GRASS GIS new website ===

* Description: Small meeting to discuss about the new GRASS GIS website and plan/split further tasks
* Person to contact: Veronica Andreo (veroandreo@gmail.com)

Who is coming:
* Nicolas Bozon
* Veronica Andreo
* ...

== Menuet (2nd floor) ==

=== OpenMapTiles ===

* Description: Discussion about OpenMapTiles project - meeting of contributors, users and all the people interested.
* Person to contact: Eva Jelinkova

Who is coming:
* Eva Jelinkova
* Dalibor Janak

== Hora (21st floor) ==

===Travel Grant Program participants' session ===

* Description: This session is dedicated to the FOSS4G 2019 TGP participants.
* Person to contact: Olimpia Copăcenaru

Who is coming:
* Olimpia Copăcenaru
* Muhammad Hasan Mustafa
* Rosa Maria Aguilar de Archila
* Katre Kasemägi
* Jordan Steven Bates
* Tanmoy Chakraborty
* Md Reaid Alam
* Madelijn Madelief Bazen
* Akintunde Opeyemi Kuye
* Hamidreza Ostadabbas
* Anthonia Ijeoma Onyeahialam
* Cláudia Morais Viana
* Candan Eylül Kilsedar
* Brenda Ayo
* Ivan Rykin
* Caroline Akoth Otiwa
* Sharon Adhiambo Omoja
* Céline Lorraine Jacquin
* Gladys Adjei
* Anne Akinyi Aol
* Sidorela Uku
* Gorica Bratić
* Stefan Jovanovic
* Besfort Guri
* Vesna Tunguz
* Lukáš Bezrouk
* Ana-Ioana Breaban
* Iuliia Danylenko
* Marko Kažić
* Brunilda Licaj
* Erviola Konomi

== Coralle (2nd floor) ==

=== GeoServer Flock (18:00-19:00) ===

* Description: Meet GeoServer enthusiasts from all backgrounds for stories, discussion, and GeoServer Q&A.
* Person to contact: [[User:Jive|Jody Garnett]]

Who is coming:
* Jody Garnett
* Gert-Jan van der Weijden
* Andrea Aime

=== GeoServer Demos (19:00-19:30) ===

* Description: Got a great GeoServer example? Share and learn ...
* Person to contact: [[User:Jive|Jody Garnett]]

Who is coming:
* Jody Garnett
* Andrea Aime

= Thursday 29 August (18:00 - 19:30) =

== Ronda Ballroom (1st floor) ==

=== OSGeo Members ===

* Description: Are you a member of OSGeo, come and talk about what members do in OSGeo
* Person to contact: Vicky Vergara

Who is coming:
* Vicky Vergara
* Zoltan Siki

== Fortuna Vest (21st floor) ==

=== Open Source Cartography and Mapping (18:00-19:30) ===

* Description: Making open source look good with QGIS, GeoStyler, GeoServer and more ...
* Person to contact: [[User:Jive|Jody Garnett]]

Who is coming:
* Jody Garnett
* Andrea Aime
* <del>[[User:Geejee|Gert-Jan]] (depending on the exact planning of the "FOSS4G-Europe 2020" BoF)</del>

== Fortuna Est (21st floor) ==

=== Add BoF name ===

* Description: Add description
* Person to contact: Add contact person

Who is coming:
* Add your name

== Rapsodia Ballroom (1st floor) ==

=== Women in Geospatial - What skills will matter in FOSS4G? ===

This session highlights different aspects of essential skills in order to build up a successful career in FOSS4G. Besides an inspirational talk from Maria Brovelli, the Queen of FOSS4G, we will have a panel discussion with geospatial experts and FOSS4G enthusiasts discussing essential career skills across the career ladder.

Additionally, some community efforts such as the newly founded [https://twitter.com/geospatialwomen/ Women in Geospatial network] and the [https://twitter.com/GeochicasOSM/ GeoChicasOSM network] are presented.

This session is organised by Women in Geospatial network and we invite everyone to this session (men and women), who would like to join us in discussing different career development paths in the FOSS4G domain.

==== Programme ====
{| class="wikitable"
|-
! Time !! Title !! Presenter
|-
| 18:00-18:05 || Welcome and setting the scene || Julia Wagemann
|-
| 18:05-18:10 || Women in Geospatial || Julia Wagemann
|-
| 18:10-18:15 || GeoChicas OSM || Celine Jacquin
|-
| 18:15-18:30 || '''''"From an old Queen to young Princesses, Frogs and Princes"''''' || Maria Brovelli
|-
| 18:30-19:20 || Panel discussion on '''"Careers in FOSS4G - Which skills will matter?"''''' || Moderator: Joana Kamenova,
Panelists:
* Maria Brovelli
* Athina Trakas
* Astrid Emde
* Laura Mugeha
* Celine Jacquin
* Maria Arias de Reyna
* Maria Bellesteros
|-
| 19:20-19:30 || Q&A and Wrap-up || Julia Wagemann
|}

==== Who is coming ====
* [https://2019.foss4g.org/speakers/julia-wagemann/ Julia Wagemann] (Contact person for this session)
* Malena Libman
* Ilie Codrina
* Maria Brovelli
* Athina Trakas
* Astrid Emde
* Laura Mugeha
* Celine Jacquin
* Maria Arias de Reyna
* Maria Bellesteros
* Joana Kamenova
* Carmen Díez
* Cristina Vrînceanu
* ...

== Opera (2nd floor) ==

=== Mapillary Q&A Session (12:45-14:00) ===

* Description: Mapillary will be available during lunch for all questions on street-level imagery, computer vision, mobile apps, OpenStreetMap integrations and anything else that may interest you.
* Person to contact: Edoardo Neerhut, Christopher Beddow, Ovidiu Voda - All in the Attendify app

Who is coming:
* Add your name

== Opereta (2nd floor) ==

=== FOSS4G-Europe 2020===

* Description: Talk about FOSS4G Europe the next year. Where and who? See also dedicated AM [[AM_FOSS4G2019_Bucharest]]
* Person to contact: [[User:jachym|Jáchym Čepický]] jachym.cepicky@gmail.com

Who is coming:
* [[User:jachym|Jáchym]]
* [[User:Jgrocha|Jorge Gustavo]], Portugal
* [[User:Astrid Emde | Astrid Emde]]
* [[User:Geejee|Gert-Jan van der Weijden]], Netherlands
* [[User:Lads|Luís de Sousa]], Portugal
* [[User:Just|Just van den Broecke]], Netherlands
* [[User:tkardi|Tõnis Kärdi]], Estonia
* [[User:Geogoeroe|Erik Meerburg]], Netherlands
* [[User:Peteris|Pēteris Brūns]], Latvia

== Simfonia (2nd floor) ==

=== Google Code-in ===

* Description: Meetup for Google Code-in mentors and students to discuss challenges and opportunities for the 2019 GCI.
* Person to contact: Victoria Rautenbach (victoria.rautenbach@gmail.com)

Who is coming:
* Cameron Green
* Add your name

== Menuet (2nd floor) ==

=== Deep Learning for Earth Observation ===

* Description:
Deep Learning for EO is already there.
But how can we go further ?

Few leads:
- High Quality Geographical OpenDataSet
- DL for EO Frameworks best practices and convergence
- Reducing CO2 footprint
- EO Data Cube
- Interoperabilty with GIS tools
- [bring your owns]

* Person to contact: Olivier Courtin @o_courtin

Who is coming:
* Olivier Courtin

== Hora (21st floor) ==

=== Add BoF name ===

* Description: Add description
* Person to contact: Add contact person

Who is coming:
* Add your name

== Coral (2nd floor) ==

=== GeoTIFF (.js) ===

* Description: Discussion about remote GeoTIFF exploitation and geotiff.js
* Person to contact: Fabian Schindler (@__fschindler__)

Who is coming:
* Fabian Schindler

[[Category:FOSS4G2019]]

User:Peteris

2019-08-29T11:58:38Z

Wiki-Peteris: Created page with "{{OSGeo Experience |User=Yes |Committee=No |Board=No |Coder=No |Translate=Yes |PSC=No |ExBoard=No |Charter=No |Chair=No |SolKatz=No |Committer=No }} ;Contact: : Email: pb@sun..."

{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=No
|Translate=Yes
|PSC=No
|ExBoard=No
|Charter=No
|Chair=No
|SolKatz=No
|Committer=No
}}

;Contact:
: Email: pb@sungis.lv, peteris.bruns@gmail.com
: GitHub: https://github.com/peterisb
: Twitter: https://twitter.com/sungis

===Pēteris Brūns===
System architect and analyst, GIS/IT consultant.

Location: Valmiera, Latvia

AM FOSS4G2019 Bucharest

2019-07-09T07:26:20Z

Wiki-Peteris: /* participants */

== general ==
The next general meeting among all existing and interested new members will take place at FOSS4G 2019 in Bucharest. We will publish exact date, site and time here soon.

See also: [[Annual General Meeting 2019]]

== participants ==
Please place your name here, if you are interested to participate

* Till Adams (Board FOSS4G Europe)
* Jorge Gustavo Rocha
* Silvia Franceschi
* Peteris Bruns

== Agenda ==
Please add your topics here
* status of FOSS4G Europe
* re-organize goals and tasks
* vote new board
* FOSS4G-Europe 2020

[[Category: Annual General Meeting]]
[[Category: FOSS4G2019]]

Geoservices REST API

2013-05-10T08:15:58Z

Wiki-Peteris: /* 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.

= 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]
* [[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 Crăciunescu]], 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]

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

== Analysis ==
To do, incorporate text from [http://lists.osgeo.org/pipermail/discuss/2013-May/011667.html Adrian Custer's eloquent, unbiased, concise summary of the technical issues].

(If you read nothing else, read this analysis from Adrian).

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