OSGeo - User contributions [en]

User:PedroNGV

2015-08-20T19:57:59Z

Wiki-PedroNGV: Created page with "===Pedro Venâncio=== Pedro Venâncio GIS Analyst and Developer, Câmara Municipal de Pinhel Location: Pinhel, Portugal Pedro works..."

===Pedro Venâncio===

[[File:Pedrongv.png‎|thumb|right|100px|Pedro Venâncio]]

GIS Analyst and Developer, Câmara Municipal de Pinhel

Location: Pinhel, Portugal

Pedro works with Geographic Information Systems and Remote Sensing for about 10 years, and over the last 5, he uses only FOSS4G. He started with the early versions of gvSIG and QGIS, then GRASS, SAGA, GDAL, R, PostgreSQL, PostGIS, MapGuide OS, MapServer, GeoServer, GeoNetwork, ... Apart from FOSS4G, he is also a user and evangelizer of FOSS in general (Linux, LibreOffice, Gimp, ...).

Over the last years, he has participated in several conferences in Portugal in the field of Civil Protection, where he has presented solutions based on FOSS4G. He also gave some workshops in the same area.

Pedro is currently responsible for the Cartography and GIS service of Pinhel Municipality (Portugal), where develops and manages the geographic information solutions (data models, databases, geowebservices, WebGIS, spatial models), using exclusively OSGeo projects.

;OSGeo Experience

[[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]]
[[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]]

:
:* Co-founder of the Portuguese QGIS User Group;
:
:* Co-organizer of the 2nd Portuguese QGIS User meeting (Coimbra, 2014);
:
:* Active member of OSGeo-PT and QGIS-PT mailing lists;
:
:* QGIS tester, bug hunter and reporter;
:
:* Collaborator with Portuguese QGIS User Group in the development of QGIS plugins;

;Contact:
: Email: pedrongvenancio AT gmail DOT com
: [https://www.facebook.com/pedro.venancio.923 Facebook]
: [https://pt.linkedin.com/in/pedrovenancio LinkedIn]

;Spoken Language(s): Portuguese, Spanish, English

;Profile last updated: 20 August 2015

File:Pedrongv.png

2015-08-20T19:22:02Z

Wiki-PedroNGV:

Geoservices REST API

2013-05-12T23:18:05Z

Wiki-PedroNGV: /* Signed */

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

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

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

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

= Open Letter to OGC and voting members =

''Please don't edit this "Open Letter" statement, comments and discussion should go in the "Further Concerns" section below.''

May 2013

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

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

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

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

# [[User:camerons|Cameron Shorter]], Geospatial Solutions Director at [http://lisasoft.com LISAsoft], core contributor & coordinator of [http://live.osgeo.org OSGeo-Live], OSGeo Board member
# [[Mark Lucas]], Founding member and board of directors for OSGeo foundation, 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
# [[User:alvaro|Alvaro Anguix]], Spain, General Manager at [http://www.gvsig.com gvSIG Association]
# [[Santiago Higuera]], CEO at [http://Mercatorlab.com Mercatorlab], OSGeo Spanish Local Chapter Board Member, Spain
# [[Alan Boudreault]], Developer at [http://mapgears.com/ Mapgears], contributor to [http://mapserver.org Mapserver] and [httpo://gdal.org GDAL/OGR].
# [[User:mikesaunt|Mike Saunt]], UK, Owner at [http://astuntechnology.com Astun Technology Ltd], OSGeo sponsor
# [[User:msmitherdc|Michael Smith]], OSGeo Charter Member, Physical Scientist US Army Corps of Engineers Remote Sensing GIS Center
# [[User:Kalxas|Angelos Tzotsos]], OSGeo Charter Member, Researcher at National Technical University of Athens
# [[User:Kimaidou|Michaël Douchin]], France, GIS consultant & software engineer at [http://3liz.com/ 3liz]
# [[User:PedroVenancio | Pedro Venâncio]], Portugal, GIS Analyst @ Municipality of Pinhel

= Summary =

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

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

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

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

== Criticism and Response ==

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

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

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

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

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

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

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

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

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

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

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

; The cons:

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

; A conclusion:

Both simple answers are bad.

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

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

Is there any third way?

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

= Issues with the document =

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

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

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

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

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

= Further Concerns =
--- DRAFT ____

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

== Political Concerns ==

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

== Commercial Concerns ==

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

== Technical Concerns ==

* <strike>The Geoservices REST API overlaps in large proportion with existing OGC standards such as WMS, WCS, WFS, WMTS, CSW, with no effort made to reconcile with those standards.</strike>
* The standardization of WKT for Spatial reference systems is unfortunately currently quite weak in OGC standards. Geoservices REST API is tied with ESRI's version of WKT, which is not properly specified in the Geoservices REST API documents, and is known to be incompatible with other OGC documents, which will lead to a larger confusion. See the following [http://lists.opengeospatial.org/pipermail/requests/2012-July/000166.html comment] for more details on this issue.
* <strike>The Geoservices REST API is not particularly RESTful - it's a thinly disguised service call, not an address space for RESTful objects that can be operated on.</strike>
* 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 ==

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

A response (from Adrian Custer):

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

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

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

Geoservices REST API

2013-05-12T23:17:03Z

Wiki-PedroNGV: /* Signed */

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

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

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

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

= Open Letter to OGC and voting members =

''Please don't edit this "Open Letter" statement, comments and discussion should go in the "Further Concerns" section below.''

May 2013

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

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

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

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

# [[User:camerons|Cameron Shorter]], Geospatial Solutions Director at [http://lisasoft.com LISAsoft], core contributor & coordinator of [http://live.osgeo.org OSGeo-Live], OSGeo Board member
# [[Mark Lucas]], Founding member and board of directors for OSGeo foundation, 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
# [[User:alvaro|Alvaro Anguix]], Spain, General Manager at [http://www.gvsig.com gvSIG Association]
# [[Santiago Higuera]], CEO at [http://Mercatorlab.com Mercatorlab], OSGeo Spanish Local Chapter Board Member, Spain
# [[Alan Boudreault]], Developer at [http://mapgears.com/ Mapgears], contributor to [http://mapserver.org Mapserver] and [httpo://gdal.org GDAL/OGR].
# [[User:mikesaunt|Mike Saunt]], UK, Owner at [http://astuntechnology.com Astun Technology Ltd], OSGeo sponsor
# [[User:msmitherdc|Michael Smith]], OSGeo Charter Member, Physical Scientist US Army Corps of Engineers Remote Sensing GIS Center
# [[User:Kalxas|Angelos Tzotsos]], OSGeo Charter Member, Researcher at National Technical University of Athens
# [[User:Kimaidou|Michaël Douchin]], France, GIS consultant & software engineer at [http://3liz.com/ 3liz]
# [[User:Pedro Venâncio | Pedro Venâncio]], Portugal, GIS Analyst @ Municipality of Pinhel

= Summary =

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

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

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

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

== Criticism and Response ==

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

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

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

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

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

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

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

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

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

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

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

; The cons:

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

; A conclusion:

Both simple answers are bad.

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

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

Is there any third way?

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

= Issues with the document =

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

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

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

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

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

= Further Concerns =
--- DRAFT ____

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

== Political Concerns ==

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

== Commercial Concerns ==

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

== Technical Concerns ==

* <strike>The Geoservices REST API overlaps in large proportion with existing OGC standards such as WMS, WCS, WFS, WMTS, CSW, with no effort made to reconcile with those standards.</strike>
* The standardization of WKT for Spatial reference systems is unfortunately currently quite weak in OGC standards. Geoservices REST API is tied with ESRI's version of WKT, which is not properly specified in the Geoservices REST API documents, and is known to be incompatible with other OGC documents, which will lead to a larger confusion. See the following [http://lists.opengeospatial.org/pipermail/requests/2012-July/000166.html comment] for more details on this issue.
* <strike>The Geoservices REST API is not particularly RESTful - it's a thinly disguised service call, not an address space for RESTful objects that can be operated on.</strike>
* 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 ==

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

A response (from Adrian Custer):

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

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

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

Geoservices REST API

2013-05-12T23:15:07Z

Wiki-PedroNGV: /* Signed */

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

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

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

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

= Open Letter to OGC and voting members =

''Please don't edit this "Open Letter" statement, comments and discussion should go in the "Further Concerns" section below.''

May 2013

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

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

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

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

# [[User:camerons|Cameron Shorter]], Geospatial Solutions Director at [http://lisasoft.com LISAsoft], core contributor & coordinator of [http://live.osgeo.org OSGeo-Live], OSGeo Board member
# [[Mark Lucas]], Founding member and board of directors for OSGeo foundation, 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
# [[User:alvaro|Alvaro Anguix]], Spain, General Manager at [http://www.gvsig.com gvSIG Association]
# [[Santiago Higuera]], CEO at [http://Mercatorlab.com Mercatorlab], OSGeo Spanish Local Chapter Board Member, Spain
# [[Alan Boudreault]], Developer at [http://mapgears.com/ Mapgears], contributor to [http://mapserver.org Mapserver] and [httpo://gdal.org GDAL/OGR].
# [[User:mikesaunt|Mike Saunt]], UK, Owner at [http://astuntechnology.com Astun Technology Ltd], OSGeo sponsor
# [[User:msmitherdc|Michael Smith]], OSGeo Charter Member, Physical Scientist US Army Corps of Engineers Remote Sensing GIS Center
# [[User:Kalxas|Angelos Tzotsos]], OSGeo Charter Member, Researcher at National Technical University of Athens
# [[User:Kimaidou|Michaël Douchin]], France, GIS consultant & software engineer at [http://3liz.com/ 3liz]
# [[User:Pedro Venâncio | Pedro Venâncio]], Portugal, GIS Analyst, Municipality of Pinhel

= Summary =

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

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

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

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

== Criticism and Response ==

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

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

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

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

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

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

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

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

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

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

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

; The cons:

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

; A conclusion:

Both simple answers are bad.

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

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

Is there any third way?

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

= Issues with the document =

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

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

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

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

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

= Further Concerns =
--- DRAFT ____

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

== Political Concerns ==

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

== Commercial Concerns ==

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

== Technical Concerns ==

* <strike>The Geoservices REST API overlaps in large proportion with existing OGC standards such as WMS, WCS, WFS, WMTS, CSW, with no effort made to reconcile with those standards.</strike>
* The standardization of WKT for Spatial reference systems is unfortunately currently quite weak in OGC standards. Geoservices REST API is tied with ESRI's version of WKT, which is not properly specified in the Geoservices REST API documents, and is known to be incompatible with other OGC documents, which will lead to a larger confusion. See the following [http://lists.opengeospatial.org/pipermail/requests/2012-July/000166.html comment] for more details on this issue.
* <strike>The Geoservices REST API is not particularly RESTful - it's a thinly disguised service call, not an address space for RESTful objects that can be operated on.</strike>
* 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 ==

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

A response (from Adrian Custer):

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

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

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

Ensino / Projectos / Ensino com SASIG

2010-08-26T11:36:43Z

Wiki-PedroNGV: /* Ensino Superior */

==Lista de Casos de Ensino com SASIG==

===Acções de Formação agendadas===

{| border="1"
! Promotor !! Curso!!Software!!Contacto!!Descrição!!Datas!!Local
|-
| Faunália || QGIS/GRASS || QGIS/GRASS || [http://www.faunalia.pt/formacao Faunália] || 28 Horas/4 Dias || 17/18 e 24/25 Setembro || Évora
|-
| Faunália || Programação QGIS/GRASS || QGIS/GRASS || [http://www.faunalia.pt/formacao Faunália] || 16 Horas/2 Dias || 7 e 8 Outubro || Lisboa
|-
| Faunália || QGIS/GRASS || QGIS/GRASS || [http://www.faunalia.pt/formacao Faunália] || 28 Horas/4 Dias || 11 a 14 de Outubro || Lousada
|-
| Faunália || Bases de Dados Geográficas || || [http://www.faunalia.pt/formacao Faunália] || 21 Horas/3 Dias || 27 a 29 Outubro || Lousada
|-
| Faunália || Webmapping || || [http://www.faunalia.pt/formacao Faunália] || 21 Horas/3 Dias || 22 a 24 Novembro || Lousada
|}

=== Ensino Superior ===

{| border="1"
|-
! Instituição
! Curso
! Disciplina
! Contacto/email
! Software
! Descrição/Objectivo
! Observações
! Vantagens
|-
| [http://www.ua.pt/estga/ '''ESTGA-UA''']
| [http://www.ua.pt/estga/PageText.aspx?id=8931 CET em Sistemas de Informação Geográfica]
| [http://www.estga.ua.pt/PageText.aspx?id=8943 '''Plataformas Open Source''']
| [http://wiki.osgeo.org/wiki/Toze_%28Ant%C3%B3nio_Jos%C3%A9_Silva%29 António José Silva]
| Vários*
| Pretende-se dar a conhecer o movimento open source e tirar partido das suas vantagens. São utilizadas em concreto algumas das tecnologias associadas a este movimento, devendo os formandos instalar e manipular uma solução open source integrada: SIG, base de dados e servidor web.
| Este curso encontra-se na primeira edição e ainda está em funcionamento.
| ...
|-
| [http://www.isegi.unl.pt '''ISEGI-UNL''']
| [http://www.isegi.unl.pt/Cursos/Mestrados/CSIG/Default.asp Mestrado em Ciência e Sistemas De Informação Geográfica]
| [http://www.isegi.unl.pt/Cursos/Mestrados/CSIG/Detalhe_Disciplina.asp?iddisc=60020&Obr=0 '''Geospatial Free Open Source Software''']
| [mailto:jgr@isegi.unl.pt Jorge Gustavo Rocha]
| Vários*
| O principal objectivo desta disciplina é a compreensão das propriedades específicas, qualidades e fraquezas do Software Livre e de Código Aberto para SIG, promovendo assim a sua utilização.
|
| ...
|-
| Universidade dos Açores
| Licenciatura em Guias da Natureza
| Espeleologia e Montanhismo
| dinisacores(AT)sapo.pt
| DNRGarmin, Google Earth, FGis
| Desenho de trilhos, trabalhar com dados GPS e informação remota, criar shapefiles, ...
| ...
| Facilidade de aprendizagem. Custo zero ou próximo de zero.
|-
| Universidade dos Açores
| Eng. Civil / Arquitectura
| Ordenamento do Território
| António Moniz / amonizm(AT)gmail.com
| gvSIG
| Introdução aos Sistemas de Informação Geográfica aplicados ao Planeamento e Ordenamento do Território
| ...
| Disponibilidade, Facilidade de Instalação e Uso.
|-
| Faculdade de Ciências da Universidade de Lisboa
| Mestrado em Sistemas de Informação Geográfica - Tecnologias e Aplicações
| Análise Espacial da Informação Geográfica
| [mailto:cmcatita@fc.ul.pt Cristina Catita]
| Spring, Grass, QGIS
| Pretende-se mostrar diferentes aplicações informáticas para a análise espacial de informação geográfica e tirar partido do melhor que cada uma oferece de modo a enriquecer o conhecimento dos alunos nesta área.
| ...
| A possibilidade de desenvolver novos módulos/funções adaptado(a)s às necessidades de cada uma das áreas científicas em que é usado, partindo de uma base já construída para a gestão e visualização de dados geoespaciais.
|-
| '''Univ. Minho'''
| [http://www.uminho.pt/Default.aspx?tabid=8&pageid=1079&lang=pt-PT Mestrado em Património e Turismo Cultural]
| SIG
| [mailto:jgr@di.uminho.pt Jorge Gustavo Rocha]
| [http://geobox.geospot.pt GeoBox]
|
|
|
|-
| '''Univ. Minho'''
| [http://www.uminho.pt/Default.aspx?tabid=8&pageid=337&lang=pt-PT Engenharia Biomédica (Mestrado Integrado)]
| SIG
| [mailto:jgr@di.uminho.pt Jorge Gustavo Rocha]
| [http://geobox.geospot.pt GeoBox]
|
|
|
|-
| '''FLUP'''
| [http://sigarra.up.pt/flup/planos_estudos_geral.formview?p_Pe=646 Mestrado em Sistemas de Informação Geográfica e Ordenamento de Território]
| Programação em SIG
| [mailto:jgr@di.uminho.pt Jorge Gustavo Rocha]
| [http://geobox.geospot.pt GeoBox]
| [http://msigot.blogspot.com Blog]
|
|
|-
| '''Univ. Minho'''
| [http://www.ecum.uminho.pt/Default.aspx?tabid=4&pageid=366&lang=pt-PT Mestrado em Ordenamento e Valorização de Recursos Geológicos]
| SIG
| [mailto:jgr@di.uminho.pt Jorge Gustavo Rocha]
| [http://geobox.geospot.pt GeoBox]
| [http://www.sigaberto.org/geologia/ Blog]
|
|
|-
| '''Instituto Politécnico de Tomar'''
| [http://portal.ipt.pt/portal/portal/posgradSLAP Pós-Graduação em Software Livre Aplicado ao Património]
| Sistemas de Informação Geográfica em Código Aberto
| dgt AT ipt.pt
| QGIS, GRASS, Postgis, Geoserver, R
| [http://portal.ipt.pt/portal/portal/posgradSLAP/objectivos Objectivos ]
|
|
|}

===Acções de Formação realizadas===

{| border="1"
! Instituição !!Curso!!Contacto/email!!Software!!Descrição/Objectivo !!Observações!!Vantagens
|-
|Joaquim Seixas, Formador em Centros de Formação Continua para Professores do Secundário||Aprender Sistemas de Informação Geografica com programas OpenSouce||Joaquim Seixas / mapas(AT)sapo.pt||Quantum GIS, OpenOffice Calc||A Acção de Formação “Aprender Sistemas de Informação Geográfica com programas OpenSource” é orientada para professores de Geografia do Ensino Secundário e tem por principais objectivos:

• Estimular o contacto com novas tecnologias de informação geográfica.

• Ensinar como se constrói mapas temáticos a partir de uma aplicação SIG.

• Obterem competências para desenvolverem materiais didácticos (mapas temáticos) para apresentação em sala de aula.
||A acção de formação em causa, integra-se no plano formação de vários Centros de Formação Continua para Professores do Secundário||As enorme vantagem da acção é levar o OpenSouce SIG para as salas de aula do Ensino Secundário. Ensinando os Professores a trabalhar com este tipo de aplicações. O entusiasmo demonstrado por muitos professores levou muitos a considerarem ensinar o Quantum GIS aos seus discentes, em oficinas temáticas.
|-
|INOVINTER Pólo de Vila Real de Santo António||Unidade de Formação Modular - Sistemas de informação geográfica - construção civil||Nelson Silva / nelson.jgs(AT)gmail.com||Quantum GIS||Catálogo Nacional de Qualificações, referencial de formação do curso de Construção Civil e Engenharia Civil, da saída profissional de Técnico/a de Topografia, com o objectivo de utilizar sistemas de informação geográfica aplicados à topografia||Este módulo foi ministrado para funcionários do ICNB, delegação do Algarve, com qualificação profissional entre o 9º ano e máximo 12º ano||Formandos pretendiam ter acesso a um software passível de utilizarem no seu posto de trabalho e em casa, daí a escolha de open source. Interface amigável para iniciantes (vigilantes da natureza)
|}

[[category: Portugal]]

Links Uteis Portugal

2009-08-21T16:37:21Z

Wiki-PedroNGV: /* Servidores WebGIS */

Página para inserir links úteis e interessantes para a comunidade portuguesa.

== Mailing List ==
*[http://lists.osgeo.org/mailman/listinfo/portugal Lista de correio electrónico do Grupo Local Português do OSGeo]

== Case Studies ==
*[http://osor.eu/case_studies/dutch-use-open-source-for-geoservices-in-public/ Caso de estudo de implementação de SIG aberto na Holanda]
*[http://ec.europa.eu/enterprise/ict/policy/doc/2006-11-20-flossimpact.pdf Impacto Económico do Software Open Source (na Europa)]

== Gis "portáteis" ==

=== USB ===
*[http://www.archaeogeek.com/blog/portable-gis/ Gis "portátil" para levar na "pen" USB. Para Windows.]
*[http://geomatica.como.polimi.it/software/slaxGIS/index.php slaxGIS, distribuição GNU/Linux para ser instalada em uma pen USB.]
*[http://www.faunalia.pt/?q=node/7 GIS on USB Stick. A Debian GNU/Linux installation with many Open Source GIS tools made to run on a USB disk drive.]

=== Distribuições Gnu/Linux - Live CDs com software SIG pre-instalado ===
*[http://www.arc-team.com/archeos/wiki/doku.php The first GNU/Linux distribution for archaeology.]
*[http://www.ing.unitn.it/~grass/software/GRASS_DVDit.html The Italian GRASS DVD. Com também software para Windows.]
*[http://poseidon.furg.br/ Poseidon linux: nasceu a partir da necessidade de ter-se um desktop amigável e completo baseado em software livre para a comunidade acadêmica/científica brasileira.]
*[http://wiki.debian.org/DebianGis/LiveImages Debian GIS Live image]
*[http://wiki.osgeo.org/wiki/Live_GIS_Disc OsGeo Live GIS Disc]
*[http://livecd.ominiverdi.org/index.php?page=LiveCD&toc=livecd Omini Verdi Live CD]
*[ftp://grassimages.ing.unitn.it/pub/GRASS_DVD_FOSS4G2008_workshop.iso FOSS4G 2008 live Workshop DVD]

=== Virtual Machines com software SIG pre-instalado ===
*[http://www.gisvm.com/ Gis Virtual Machine]

== Directórios de Software==

*[http://opensourcegis.org/ Index de Software OpenSource/Free GIS]
*[http://www.freegis.org/database/?cat=0 Freegis]
*[http://wiki.osgeo.org/wiki/Software_para_uma_Workstation Exemplos de Software para uma Workstation]

=== Base de Dados ===

*[http://www.postgresql.org/ PostgreSQL - Página oficial]

*[http://www.postgresql.org.br/ PostgreSQL Brasil - Página oficial]

*[http://postgis.refractions.net/ PostGIS - Página oficial]

*[http://www.gaia-gis.it/ SpatiaLite - Página oficial]

=== Servidor Web ===

==== Apache ====

*[http://httpd.apache.org/ Apache Web Server - Página oficial]

*[http://www.apachefriends.org/en/xampp.html XAMPP - Página oficial]

=== Servidores WebGIS ===

*[http://mapserver.gis.umn.edu/ MapServer - Página oficial]

*[http://mapserver.gis.umn.edu/docs MapServer (Documentação) - Página oficial]

*[http://trac.mapfish.org/trac/mapfish/wiki/Home MapFish - Página oficial]

*[http://geoserver.org/display/GEOS/Welcome GeoServer - Página oficial]

*[http://mapguide.osgeo.org/ MapGuide Open Source - Página oficial]

*[http://geonetwork-opensource.org/ GeoNetwork opensource - Página oficial]

==== ''Front Ends'' para Mapserver e Geoserver ====

*[http://www.pmapper.net/ p.mapper - Página oficial]

*[http://ka-map.maptools.org/ Ka-Map - Página oficial]

*[http://chameleon.maptools.org/ chameleon - Página oficial]

*[http://openlayers.org/ openlayers - Página oficial]

*[http://communitymapbuilder.org/ mapbuilder - Página oficial]

*[http://www.mapbender.org/Main_Page mapbender - Página oficial]

*[http://www.cartoweb.org/ cartoweb - Página oficial]

*[http://fist-mapping.org/ fist-mapping - Página oficial]

==== Edição map files ====

*[http://www.mapstorer.org/ MapStorer (Mapfile editing tool) - Página oficial]

*[http://notepad-plus.sourceforge.net/br/site.htm Notepad++ - Página oficial]

*[http://gianpiero.campanella.googlepages.com/mapfile-highlighting-Notepad-1.3.zip Notepad++ Syntax File for .map Files]

*[http://wiki.osgeo.org/wiki/Notepad%2B%2B_Syntax_File_for_map_Files Instalação de Notepad++ Syntax File for map Files]

=== Aplicações Desktop ===

==== Quantum GIS ====

*[http://www.qgis.org/ Quantum GIS - Página oficial]

*[http://ppa.launchpad.net/qgis/ubuntu/ Ubuntu Hardy Repository --> "deb http://ppa.launchpad.net/qgis/ubuntu hardy main"]

*[http://ppa.launchpad.net/qgis/ubuntu/ Ubuntu Gutsy Repository --> "deb http://ppa.launchpad.net/qgis/ubuntu gutsy main"]

*[http://debian.gfoss.it/README Debian Repository]

==== GRASS ====

*[http://grass.osgeo.org/ GRASS - Página oficial]

*[http://debian.gfoss.it/README Debian Repository]

*[http://les-ejk.cz/ubuntu/ Les-ejk UbuntuGIS repository]

==== gvSIG ====

*[http://www.gvsig.gva.es/ gvSIG - Página oficial]

*[https://gvsig.org/web/ gvSIG - Portal gvSIG]

*[http://www.gvsig.gva.es/index.php?id=listas-distribucion&L=2&K=1&A=&L=0 gvSIG - Mailing Lists]

==== Kosmo ====

*[http://www.opengis.es/ Kosmo - Página oficial]

==== OpenJump ====

*[http://openjump.org/wiki/show/HomePage OpenJump - Página oficial]

==== Sextante ====

*[http://www.sextantegis.com/ Sextante - Página oficial]

*[http://sextantegis.blogspot.com/ Sextante - Blog oficial]

*[http://www.sextantegis.com/video.htm Sextante (Vídeos Tutoriais) - Página oficial]

==== uDig ====

*[http://udig.refractions.net/ uDig - Página oficial]

=== Modelação ===

==== Scape Toad ====

*[http://chorogram.choros.ch/scapetoad/ Scape Toad - Página oficial]

==== openModeller ====

*[http://openmodeller.sourceforge.net/ openModeller - Página oficial]

=== Estatistica ===

==== R ====

*[http://www.r-project.org/ R - Página oficial]

==== CRAN Task View: Analysis of Spatial Data ====

*[http://cran.r-project.org/web/views/Spatial.html CRAN Task View: Analysis of Spatial Data - Página oficial]

==== R Spatial ====

*[http://r-spatial.sourceforge.net/ R Spatial - Página oficial]

*[http://sal.uiuc.edu/csiss/Rgeo/ Spatial Analysis Laboratory (R Spatial Projects) - Página oficial]

=== Detecção Remota ===

==== e-Foto ====

*[http://www.efoto.eng.uerj.br/pt-br:start e-Foto - Página oficial]

==== OSSIM ====

*[http://www.ossim.org//OSSIM/OSSIMHome.html OSSIM - Página oficial]

==== Opticks ====

*[https://opticks.ballforge.net/ Opticks - Página oficial]

==== ORFEO Toolbox (OTB) ====

*[http://www.orfeo-toolbox.org/ ORFEO Toolbox (OTB) - Página oficial]

=== Virtual Machines ===

*[http://www.virtualbox.org/ VirtualBox]

*[http://www.vmware.com/ VMware]

== Documentação não oficial, Manuais e Wiki ==

*[https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS]
*[http://wiki.debian.org/DebianGis DebianGIS]
*[http://www.spatialserver.net/osgis/osgis_functionality.doc Sig Desktop OpenSource, Tabela das funcionalidades]
*[http://www.spatialserver.net/osgis/Desktopgis_overview.doc Sig Desktop OpenSource, Tabela comparativa]
*[http://www.geo.unizh.ch/publications/degen/sstein_foss_desktop_gis_overview.pdf Artigo: An Overview on Current Free and Open Source Desktop GIS Developments]
*[http://www.toddbuchanan.net/thesis_ver.pdf Tese: "COMPARISON OF GEOGRAPHIC INFORMATION SYSTEM SOFTWARE (ARCGIS 9.0 AND GRASS 6.0): IMPLEMENTATION AND CASE STUDY"]
*[http://www.grassbook.org/ The Grass Book]
*[http://www.irri.org/gis/courses/ccQGISforGRASS.pdf Starter Manual to Quantum GIS for GRASS GIS]
*[http://www.novageo.pt/blog/?p=32 Manual de gvSIG em Português Novageo]
*[http://mpa.itc.it/markus/mum3/neteler_grass6_nutshell2005.pdf GRASS 6.0: GRASS 6 in a nutshell]
*[http://mpa.itc.it/markus/mum3/g63_nutshell_v1_1_es.pdf GRASS 6.3: GRASS 6: Una guía de inicio]
*[http://www.igc.usp.br/pessoais/guano/downloads/tutorial_grass6.pdf Introdução à Análise Digital de Terreno com GRASS-GIS]
*[http://www.geo.unipr.it/~clerici/GRASS6.2.pdf GRASS 6.2: Manuale pratico introduttivo]
*[http://www.gdf-hannover.de/dl.php?download=gdf_grass60_v1.2_en.pdf An introduction to the practical use of the Free Geographical Information System GRASS 6.0]
*[http://cemml.carleton.ca/grass_Misc/Introduccion_a_Grass_v.1.1.pdf MANUAL DE GRASS: INTRODUCCIÓN A GRASS]
*[http://download.osgeo.org/grass/grass6_progman_pdf/grass64vectorlib_2008_07_12_refman.pdf GRASS Reference Manual]
*[http://www.lulu.com/content/1076107 PostgreSql Book]
*[http://www.wiley.com/legacy/wileychi/gis/volumes.html Geographic Information Systems and Science - John Wiley & Sons, Ltd]
*[http://wiki.osgeo.org/wiki/SIG:_Gloss%C3%A1rio_Portugu%C3%AAs SIG: Glossário Português]
*[http://www.ossgis.co.cc/ Open Source and GIS world]

== Guias e Dicas ==

*[http://www.bostongis.com/ Boston GIS: Geographic Information Systems Web Mapping OpenGIS and open source Solutions - Página oficial]
*[http://www.personal.psu.edu/cab38/ColorBrewer/ColorBrewer_intro.html ColorBrewer - Selecting Good Color Schemes for Maps]
*[http://www.dpi.inpe.br/livros.php Divisão de Processamento de Imagens - DPI (Livros) - Página oficial]
*[http://www.geom.unimelb.edu.au/gisweb/menu.html Geomatics - Interactive GIS Learning Tool - Página oficial]
*[http://recursos.gabrielortiz.com/ GIS - SIG | Sistemas de Información Geográfica: Recursos y la Mejor Comunidad de Usuarios - Página oficial]
*[http://www.guiaubuntupt.org/ Guia Ubuntu PT - Página oficial]
*[[Instalar Grass e Qgis em Ubuntu 8.04 (com ECW e MrSID)]]
*[[Instalar Grass e Qgis em Ubuntu 8.04 através repositorios]]
*[http://www.postgresonline.com/ Postgres OnLine Journal - Página oficial]

== Divulgação ==
*[http://www.gisdevelopment.net/magazine/global/2007/august/62_1.htm Free GIS desktop and analyses: QuantumGIS, the easy way]
*[http://www.faunalia.pt/downloads/grassflyer.pdf.zip Brochura de GRASS]
*[http://mpa.itc.it/markus/papers/grass_lightening_talk_no_anim.pdf "Growing GRASS" - Lightning talk at FOSS4G 2006]
*[http://mpa.itc.it/markus/grass_movie_video_CERL/ The GRASS story, 1987 Video]
*[[Desmistificar crenças sobre os SIG livres]]

== Dados Geográficos ==

=== Sistemas de Coordenadas de Portugal ===
*[http://wiki.osgeo.org/wiki/Sistemas_de_Coordenadas_de_Portugal Grupo de trabalho: Sistemas de Coordenadas de Portugal para FOSS4G]
=== Servidores WMS (Web Map Service) ===
*[http://mapas.igeo.pt/igp/wms_sig.html WMS dos produtos do Instituto Geográfico Português]
*[http://wms-sites.com/catalog Catálogo de servidores WMS]
*[http://www.skylab-mobilesystems.com/en/wms_serverlist.html Catálogo de servidores WMS]

=== Servidores WFS (Web Feature Service) ===
*[http://mapas.igeo.pt/igp/wfs_sig.html WFS dos produtos do Instituto Geográfico Português]

=== Dados Geo-Espaciais, Ambientais, Fotografias Aéreas ou Satélitares ===
*[http://www.openstreetmap.org/ Openstreetmap]
*[http://www.geotorrent.org/browse.php GeoTorrent.org]
*[http://www.iambiente.pt/atlas/est/index.jsp Agência Portuguesa do Ambiente - Atlas do Ambiente Digital]
*[http://glcf.umiacs.umd.edu/index.shtml ''Global Land Cover Facility'']
*[https://zulu.ssc.nasa.gov/mrsid/ ''World Landsat Mosaic'' 1999/2000]
*[http://www.freegis.org/database/?cat=1 Freegis]

== Outros Links Úteis ==

*[http://www.softwarepublico.gov.br/ Portal do Software Público Brasileiro - Página oficial]

*[http://www.portugal-a-programar.org/forum/index.php Portugal-a-Programar - Página oficial]

*[http://www.icivilengineer.com/Open_Source/ The Civil Engineering Portal (lista de programas Open Source) - Página oficial]

[[category: Portugal]]

PedroNGV

2009-05-23T19:03:24Z

Wiki-PedroNGV: /* Interesses */

== Apresentação ==

* Geólogo
* Mestrando em Sistemas de Informação Geográfica

== Interesses ==
* Geologia Ambiental
* Protecção Civil
* Riscos Naturais
* Planeamento e Ordenamento do Território
* Sistemas de Informação Geográfica
* Detecção Remota
* Bases de Dados
* Software Open Source

http://webx.ubi.pt/~m2468/

[[Category:Portugal]]

PedroNGV

2008-12-30T00:21:43Z

Wiki-PedroNGV: /* Interesses */

PedroNGV

2008-12-30T00:21:08Z

Wiki-PedroNGV: /* Interesses */

== Apresentação ==

* Geólogo
* Mestrando em Sistemas de Informação Geográfica

== Interesses ==
* Geologia Ambiental
* Protecção Civil
* Riscos Naturais
* Planeamento e Ordenamento do Território
* Sistemas de Informação Geográfica
* Detecção Remota
* Bases de Dados
* Software Open Source

http://www.pedrovenancio.pt.vu
http://pngvenancio.googlepages.com

[[Category:Portugal]]

Portugal

2008-10-23T18:06:26Z

Wiki-PedroNGV: /* Lista de Interessados */

==Introdução==
Chegou à página wiki do '''Capítulo Local do Osgeo em Portugal'''.

Este grupo tem como interesse comum a criação duma comunidade portuguesa de interessados em software livre de código aberto para SIG, tentando promover uma rede que permita intercâmbio de experiências e suporte mútuo. Assim, esta página pretende ser um ponto de encontro da comunidade, cartão de visita para os novos colaboradores, assim como um ponto de informação e divulgação do Software Livre no âmbito dos Sistemas de Informação Geográfica.

==Nota Histórica==
As '''II Jornadas de SIG Livre''' que decorreram em Girona (Espanha) em Abril de 2008 permitiram o encontro de vários Portugueses, que descobriram um interesse comum em promover o desenvolvimento do SIG livre em Portugal.
Foi um ponto de encontro que permitiu conhecer o representante da Osgeo e alguns membros do Capítulo local espanhol, que imediatamente aproveitaram para nos lançar o desafio de criar também um grupo em Portugal.
Neste sentido, considerou-se importante conseguir criar uma comunidade, o mais numerosa possível, que pense, discuta, desenvolva, organize, apoie e divulgue as acções levadas a cabo nesta área. Decidiu-se, como primeiras iniciativas, criar uma Mailing List e esta página, o Capítulo Local Português na OSGeo.

Partilhamos a esperança de que existem muitos mais portugueses com os mesmos ideais e com vontade de ajudar nesta tarefa em prol de todos e do desenvolvimento do SIG no nosso país!

==Como participar==
Por favor leia a página sobre [[Portugal#Chapter_Roles|o papel do Capítulo Local]] e as suas [[Portugal#Chapter_Responsibilities|Responsabilidades]] antes de inscrever-se. Para inscrever-se basta criar um login no wiki (link no canto superior direito da página) para poder editar as páginas, e de seguida editar esta página acrescentando o seu nome (basta seguir a lógica dos que já estão na lista).
 Depois de criar o seu login, poderá criar a sua página de utilizador, usando o link <nowiki>"http://wiki.osgeo.org/wiki/login_escolhido"</nowiki> e editando-a. Se na página incluir o marcador <nowiki>[[Category: Portugal]]</nowiki>, será incluído automaticamente na [http://wiki.osgeo.org/wiki/Category:Portugal lista de utilizadores do Capítulo português].
 Mantendo a tradição, pode também incluir as coordenadas LatLon da sua localização na sua página de utilizador.

=== Lista de correio ===
A ferramenta principal para comunicação entre todos os interessados. Inscreva-se a se quiser apresente-se à comunidade. Ideal para se manter a par de novidades do Capítulo e do Software Livre de Código Aberto para SIG!
[[User:ominiverdi|Lorenzo Becchi]] é o actual administrador da lista de correio '''Portugal''' para a OSGeo:

http://lists.osgeo.org/mailman/listinfo/portugal

=== Wiki ===
Este wiki está aberto à participação de todos os interessados. Se não sabe bem como editar veja a [[Help:Contents|Ajuda]].
Será a ferramenta preferencial para organizar actividades do Capítulo.

=== Lista de Interessados ===
(criar página autónoma -> se todos colocarem nas suas páginas o marcador <nowiki>[[Category:Portugal]]</nowiki> a lista fica automaticamente feita na [http://wiki.osgeo.org/wiki/Category:Portugal página de Portugal])

# [[User:ominiverdi|Lorenzo Becchi]]
# [[User:victorferreira|Victor Ferreira]], Arquitecto, Lisboa, Portugal.
# [[User:miguelluaces|Miguel R. Luaces]], Engenheiro Informático, Ferrol, Espanha.
# [[User:fred|Fred (Frédéric Lehodey)]], Algarve Digital, Algarve.
# [[User:martinho|Martinho (José Lourenço)]], Eng. Geólogo, Vila Real, Portugal.
# [[User:jgrocha|Jorge Gustavo Rocha]], Eng. Informático, Braga, Portugal.
# [[User:dfurtado|Danilo Furtado]], Msc. Ciência e Sistemas de Informação Geográfica, Lisboa, Portugal.
# [[User:pduarte|Pedro Duarte]], Sintra, Portugal.
# [[User:mario.gomes|Mário Rui Gomes]], Engenheiro Informático, IST/UTL campus do TagusPark, Oeiras, Portugal.
# [[Miguel Tavares]], Engenheiro Geografo, Câmara Municipal de Águeda, Portugal.
# [[User:lutra|Giovanni Manghi]], Unidade de Biologia da Conservação, Universidade de Évora, Portugal.
# [[User:eloi.ribeiro|Eloi Ribeiro]], Técnico SIG, Valencia, Espanha.
# [[User:vanilla|Vânia Neves]], Unidade de Biologia da Conservação, Universidade de Évora, Portugal.
# [[User:Alchimista|André Barbosa]] , Estudante de Eng. Ambiente, Universidade de Aveiro
# [[User:pmonteiro|Pedro Monteiro]], Instituto Regional de Ordenamento Agrário SA, Mestrando do Msc. Ciência e Sistemas de Informação Geográfica, Ponta Delgada, Portugal.
# [[User:Nelsonjsilva|Nelson Silva]], Técnico SIG, Coimbra, Portugal.
# [[Duarte Carreira]], Cuba (Alentejo!), Portugal.
# [http://wiki.osgeo.org/wiki/User:marlagsan Margarida Laginha San-Payo], Lisboa, Portugal.
# [http://wiki.osgeo.org/wiki/User:Hugo.poeira Hugo Poeira], Lisboa, Portugal.
# [[User:joaopinasouza|João Pina Souza]], Lisboa, Portugal.
# [http://wiki.osgeo.org/wiki/User:Termal12 José Manuel Estêvão], Vila Real, Portugal.
# [[User:Lgseco|Luis Gonçalves Seco]], CICGE, FCUP, Portugal.
# [[User:kavune|Vítor Torres Videira]], UM, Portugal.
# [[User:linovski|Avelino Rego]], UM, Portugal.
# [[User:nsosilva|Nelson Silva]], UM, Portugal.
# [[Toze (António José Silva)]], Engenheiro Geógrafo, Águeda, Portugal.
# [[Jacinto Estima]], Engenheiro Geógrafo, Águeda, Portugal.
# [[User:Gnolasco|Gabriel Nolasco]], Geógrafo, Águeda, Portugal.
# [[User:ruigeo|Rui Manuel Dias]], Geógrafo, Lisboa, Portugal.
# [[User:ncharneca|Nuno Charneca]], Doutorando em Eng. Geográfica e Geoinformática, LNEC, Lisboa, Portugal.
# [[PedroNGV|Pedro Venâncio]], Geólogo, Mestrando em Sistemas de Informação Geográfica, Pinhel, Portugal.
# Inscreva-se na lista aquí

==Actividades (grupos de trabalho)==
Listagem de actividades propostas pelos membros. As propostas deverão vir acompanhadas dos nomes dos membros responsáveis pela actividade.

=== Jornadas de Software Aberto para SIG ===

Estas jornadas decorrerão de 20 a 22 de Outubro de 2008, na Escola Superior de Tecnologia e Gestão de Águeda, em Águeda.

Toda a informação sobre o evento está em [[Jornadas de Software Aberto para SIG]].

Existe também uma breve introdução ao evento em Inglês [[Open Source for GIS Meeting in Portugal]], para dar a conhecer o mesmo a toda a comunidade OSGeo.

=== Difusão em eventos e conferências ===
Listar aqui eventos que possam ser alvos para divulgação das nossas actividades (indicar responsável pela acção).

=== Tradução e Documentação ===
No sentido de reunir trabalhos de documentação realizados, foi criada a página de [[Documentação SIG Pt|Documentação em Português de ferramentas SIG]].

=== Glossário ===
Importante criar um glossário para suportar toda a actividade de tradução, permitindo coerência global de termos utilizados. '''PRIORITÁRIO! EM PREPARAÇÃO'''

[http://wiki.osgeo.org/wiki/SIG:_Gloss%C3%A1rio_Portugu%C3%AAs SIG: Glossário Português]

=== Directório de Software ===
[http://wiki.osgeo.org/wiki/Links_Uteis_Portugal#Direct.C3.B3rios_de_Software Directório de software utilizado em Portugal.]

== Papéis a desempenhar pelo Capítulo (pt) ==
O Open Source já demonstrou ser um ambiente sólido para a construção de software robusto através da colaboração global aberta. A Fundação Software Geoespacial Aberto (OSGeo) foi criada para apoiar e construir software geoespacial da mais alta qualidade.

A meta da OSGeo é promover o uso de projectos OSGeo globalmente através de uma colaboração localizada forte e a presença em diferentes domínios geográficos e linguísticos. Para além de constituir uma voz local forte para a OSGeo, algumas das principais vantagens da presença desta associação local de OSGeo no enriquecimento e melhora das iniciativas geoespaciais globais são:

* Promover apoio e oportunidades de trabalho aos membros através da rede
* Internacionalização e localização de software
* Desenvolver protótipos de aplicações para demonstrar as capacidades do software livre geoespacial a audiências locais ou regionais
* ''Software Packaging'' e ''Customization'' para as necessidades locais e regionais
* Educação, suporte e desenvolvimento de conteúdos de aprendizagem em Português
* Suporte de ''standards'' abertos e acesso aberto a dados geoespaciais da região
* Promover OSGeo e melhorar a sua visibilidade em vários fóruns

Estas actividades complementariam e fortaleceriam os esforços da OSGeo no aumento do conhecimento da disponibilidade de soluções geoespaciais de código aberto estimulando a sua adopção na educação, indústria, governo e organizações sem fins lucrativos em vários domínios geográficos e linguísticos.

== Responsabilidades do Capítulo (pt) ==
OSGeo não distingue entre um grupo geográfico e um linguístico e estimula a organizaçäo autónoma de forma similar aos ''Grupos de Utilizadores'' ou ''Grupos de Interesse Especial'' em outros projectos ''Open Source''. Os ''Grupos de Utilizadores'' ou os ''Grupos de Interesse Especial'' näo representam formalmente a OSGeo mas podem aproveitar alguns dos serviços como a utilzação da Wiki da OSGeo. O ''Capítulo Português'' oferece uma estrutura formal de organizaçäo autónoma baseada numas poucas directrizes enumeradas de seguida:
* O ''Capítulo Português'' representa oficialmente a OSGeo e é formalmente reconhecido como um projecto de OSGeo.
* O ''Capítulo Português'' deve apoiar as missões e objectivos da OSGeo.
* O ''Capítulo Português'' deve manter encontros regulares (pelo menos um anualmente) e proporcionar um relatório anual sobre as actividades do mesmo ao Comité de Direcção da OSGeo.
* O ''Capítulo Português'' não disporá de nenhum compromisso financeiro de ou em nome da OSGeo. Da mesma maneira, a OSGeo não proporcionará nenhum orçamento ao ''Capítulo Português''.
* O ''Capítulo Português'' deve esforçar-se na sua relação com as organizações para conseguir a participação e o suporte para a OSGeo.
* A OSGeo reserva-se o direito de terminar a sua relação com o ''Capítulo Português'' se tiver razões para crer que as actividades do ''Capítulo Português'' säo contrárias ou em detrimento da Missão e Objectivos da OSGeo.

== Vantagens do Capítulo (pt) ==
* É permitido ao ''Capítulo Português'' o uso do logótipo da OSGeo e outros recursos de imagem corporativa para promover a Missão e Objectivos da OSGeo.
* A OSGeo proporcionará a infra-estrutura necessária para promover a comunicação e visibilidade do ''Capítulo Português''. A infra-estrutura inclui uma lista de correio, hospedagem para páginas wiki e serviço de domínio para o ''Capítulo Português''.

== Formação do Capítulo ==

Para formar um capítulo, deverão ser tomados os passos seguintes:
# O "Capítulo OSGeo" deverá auto-organizar-se (por exemplo no wiki OSGeo, via lista de email OSGeo, etc) procurando determinar se existe uma massa crítica de interesse, que justifique um capítulo local.
##'''FEITO''': [http://lists.osgeo.org/mailman/listinfo/portugal Lista de email] e esta página.
# O "Capítulo OSGeo" deverá preparar os objectivos e missão indicando o escopo do capítulo planeado (extensão geográfica ou linguística por exemplo). '''A FAZER'''
# O "Capítulo OSGeo" deverá propor um representante oficial de ligação à direcção da OSGeo. Se aceite pela OSGeo, o representante será um oficial da OSGeo (officer?) '''A FAZER'''
# O "Capítulo OSGeo" deverá submeter uma declaração oficial de interesse em formar um capítulo à direcção da OSGeo, listando os membros iniciais, missão, representante e outra informação de suporte '''A FAZER'''
# A direcção da OSGeo deverá então aprovar uma moção formalizando o capítulo, e designando o oficial de ligação. '''A FAZER'''

Ao considerar a formação de novos capítulos OSGeo, a direcção tomará em consideração alguns assuntos, incluindo:
* O mandato do capítulo (geográfico ou linguístico) conflitua com outros capítulos existentes ou em formação?
* O capítulo parece ter interesse suficiente para justificar criação oficial?
* O capítulo parece ser aberto a inscrição por todos, e representativo da comunidade geográfica ou linguística alvo? (Por exemplo se o alvo fosse incluir todos os falantes de uma certa língua, seria desapropriado ter só inscritos dum só país)

== Ver também ==
[[Links Uteis Portugal]]

[[Category:Portugal]]

[[Category:Local Chapters]]

PedroNGV

2008-10-23T18:04:11Z

Wiki-PedroNGV:

== Apresentação ==

* Geólogo
* Mestrando em Sistemas de Informação Geográfica

== Interesses ==
* Geologia Ambiental
* Protecção Civil
* Riscos Naturais
* Planeamento e Ordenamento do Território
* Sistemas de Informação Geográfica
* Detecção Remota
* Bases de Dados
* Software Open Source

http://pngvenancio.googlepages.com

[[Category:Portugal]]

Portugal

2008-10-23T17:59:41Z

Wiki-PedroNGV: /* Lista de Interessados */

==Introdução==
Chegou à página wiki do '''Capítulo Local do Osgeo em Portugal'''.

Este grupo tem como interesse comum a criação duma comunidade portuguesa de interessados em software livre de código aberto para SIG, tentando promover uma rede que permita intercâmbio de experiências e suporte mútuo. Assim, esta página pretende ser um ponto de encontro da comunidade, cartão de visita para os novos colaboradores, assim como um ponto de informação e divulgação do Software Livre no âmbito dos Sistemas de Informação Geográfica.

==Nota Histórica==
As '''II Jornadas de SIG Livre''' que decorreram em Girona (Espanha) em Abril de 2008 permitiram o encontro de vários Portugueses, que descobriram um interesse comum em promover o desenvolvimento do SIG livre em Portugal.
Foi um ponto de encontro que permitiu conhecer o representante da Osgeo e alguns membros do Capítulo local espanhol, que imediatamente aproveitaram para nos lançar o desafio de criar também um grupo em Portugal.
Neste sentido, considerou-se importante conseguir criar uma comunidade, o mais numerosa possível, que pense, discuta, desenvolva, organize, apoie e divulgue as acções levadas a cabo nesta área. Decidiu-se, como primeiras iniciativas, criar uma Mailing List e esta página, o Capítulo Local Português na OSGeo.

Partilhamos a esperança de que existem muitos mais portugueses com os mesmos ideais e com vontade de ajudar nesta tarefa em prol de todos e do desenvolvimento do SIG no nosso país!

==Como participar==
Por favor leia a página sobre [[Portugal#Chapter_Roles|o papel do Capítulo Local]] e as suas [[Portugal#Chapter_Responsibilities|Responsabilidades]] antes de inscrever-se. Para inscrever-se basta criar um login no wiki (link no canto superior direito da página) para poder editar as páginas, e de seguida editar esta página acrescentando o seu nome (basta seguir a lógica dos que já estão na lista).
 Depois de criar o seu login, poderá criar a sua página de utilizador, usando o link <nowiki>"http://wiki.osgeo.org/wiki/login_escolhido"</nowiki> e editando-a. Se na página incluir o marcador <nowiki>[[Category: Portugal]]</nowiki>, será incluído automaticamente na [http://wiki.osgeo.org/wiki/Category:Portugal lista de utilizadores do Capítulo português].
 Mantendo a tradição, pode também incluir as coordenadas LatLon da sua localização na sua página de utilizador.

=== Lista de correio ===
A ferramenta principal para comunicação entre todos os interessados. Inscreva-se a se quiser apresente-se à comunidade. Ideal para se manter a par de novidades do Capítulo e do Software Livre de Código Aberto para SIG!
[[User:ominiverdi|Lorenzo Becchi]] é o actual administrador da lista de correio '''Portugal''' para a OSGeo:

http://lists.osgeo.org/mailman/listinfo/portugal

=== Wiki ===
Este wiki está aberto à participação de todos os interessados. Se não sabe bem como editar veja a [[Help:Contents|Ajuda]].
Será a ferramenta preferencial para organizar actividades do Capítulo.

=== Lista de Interessados ===
(criar página autónoma -> se todos colocarem nas suas páginas o marcador <nowiki>[[Category:Portugal]]</nowiki> a lista fica automaticamente feita na [http://wiki.osgeo.org/wiki/Category:Portugal página de Portugal])

# [[User:ominiverdi|Lorenzo Becchi]]
# [[User:victorferreira|Victor Ferreira]], Arquitecto, Lisboa, Portugal.
# [[User:miguelluaces|Miguel R. Luaces]], Engenheiro Informático, Ferrol, Espanha.
# [[User:fred|Fred (Frédéric Lehodey)]], Algarve Digital, Algarve.
# [[User:martinho|Martinho (José Lourenço)]], Eng. Geólogo, Vila Real, Portugal.
# [[User:jgrocha|Jorge Gustavo Rocha]], Eng. Informático, Braga, Portugal.
# [[User:dfurtado|Danilo Furtado]], Msc. Ciência e Sistemas de Informação Geográfica, Lisboa, Portugal.
# [[User:pduarte|Pedro Duarte]], Sintra, Portugal.
# [[User:mario.gomes|Mário Rui Gomes]], Engenheiro Informático, IST/UTL campus do TagusPark, Oeiras, Portugal.
# [[Miguel Tavares]], Engenheiro Geografo, Câmara Municipal de Águeda, Portugal.
# [[User:lutra|Giovanni Manghi]], Unidade de Biologia da Conservação, Universidade de Évora, Portugal.
# [[User:eloi.ribeiro|Eloi Ribeiro]], Técnico SIG, Valencia, Espanha.
# [[User:vanilla|Vânia Neves]], Unidade de Biologia da Conservação, Universidade de Évora, Portugal.
#[[User:Alchimista|André Barbosa]] , Estudante de Eng. Ambiente, Universidade de Aveiro
#[[User:pmonteiro|Pedro Monteiro]], Instituto Regional de Ordenamento Agrário SA, Mestrando do Msc. Ciência e Sistemas de Informação Geográfica, Ponta Delgada, Portugal.
#[[User:Nelsonjsilva|Nelson Silva]], Técnico SIG, Coimbra, Portugal.
#[[Duarte Carreira]], Cuba (Alentejo!), Portugal.
#[http://wiki.osgeo.org/wiki/User:marlagsan Margarida Laginha San-Payo], Lisboa, Portugal.
#[http://wiki.osgeo.org/wiki/User:Hugo.poeira Hugo Poeira], Lisboa, Portugal.
# [[User:joaopinasouza|João Pina Souza]], Lisboa, Portugal.
#[http://wiki.osgeo.org/wiki/User:Termal12 José Manuel Estêvão], Vila Real, Portugal.
# [[User:Lgseco|Luis Gonçalves Seco]], CICGE, FCUP, Portugal.
# [[User:kavune|Vítor Torres Videira]], UM, Portugal.
# [[User:linovski|Avelino Rego]], UM, Portugal.
# [[User:nsosilva|Nelson Silva]], UM, Portugal.
# [[Toze (António José Silva)]], Engenheiro Geógrafo, Águeda, Portugal.
# [[Jacinto Estima]], Engenheiro Geógrafo, Águeda, Portugal.
# [[User:Gnolasco|Gabriel Nolasco]], Geógrafo, Águeda, Portugal.
# [[User:ruigeo|Rui Manuel Dias]], Geógrafo, Lisboa, Portugal.
# [[User:ncharneca|Nuno Charneca]], Doutorando em Eng. Geográfica e Geoinformática, LNEC, Lisboa, Portugal.
# [[PedroNGV|Pedro Venâncio]], Geólogo, Mestrando em Sistemas de Informação Geográfica, Pinhel, Portugal.
# Inscreva-se na lista aquí

==Actividades (grupos de trabalho)==
Listagem de actividades propostas pelos membros. As propostas deverão vir acompanhadas dos nomes dos membros responsáveis pela actividade.

=== Jornadas de Software Aberto para SIG ===

Estas jornadas decorrerão de 20 a 22 de Outubro de 2008, na Escola Superior de Tecnologia e Gestão de Águeda, em Águeda.

Toda a informação sobre o evento está em [[Jornadas de Software Aberto para SIG]].

Existe também uma breve introdução ao evento em Inglês [[Open Source for GIS Meeting in Portugal]], para dar a conhecer o mesmo a toda a comunidade OSGeo.

=== Difusão em eventos e conferências ===
Listar aqui eventos que possam ser alvos para divulgação das nossas actividades (indicar responsável pela acção).

=== Tradução e Documentação ===
No sentido de reunir trabalhos de documentação realizados, foi criada a página de [[Documentação SIG Pt|Documentação em Português de ferramentas SIG]].

=== Glossário ===
Importante criar um glossário para suportar toda a actividade de tradução, permitindo coerência global de termos utilizados. '''PRIORITÁRIO! EM PREPARAÇÃO'''

[http://wiki.osgeo.org/wiki/SIG:_Gloss%C3%A1rio_Portugu%C3%AAs SIG: Glossário Português]

=== Directório de Software ===
[http://wiki.osgeo.org/wiki/Links_Uteis_Portugal#Direct.C3.B3rios_de_Software Directório de software utilizado em Portugal.]

== Papéis a desempenhar pelo Capítulo (pt) ==
O Open Source já demonstrou ser um ambiente sólido para a construção de software robusto através da colaboração global aberta. A Fundação Software Geoespacial Aberto (OSGeo) foi criada para apoiar e construir software geoespacial da mais alta qualidade.

A meta da OSGeo é promover o uso de projectos OSGeo globalmente através de uma colaboração localizada forte e a presença em diferentes domínios geográficos e linguísticos. Para além de constituir uma voz local forte para a OSGeo, algumas das principais vantagens da presença desta associação local de OSGeo no enriquecimento e melhora das iniciativas geoespaciais globais são:

* Promover apoio e oportunidades de trabalho aos membros através da rede
* Internacionalização e localização de software
* Desenvolver protótipos de aplicações para demonstrar as capacidades do software livre geoespacial a audiências locais ou regionais
* ''Software Packaging'' e ''Customization'' para as necessidades locais e regionais
* Educação, suporte e desenvolvimento de conteúdos de aprendizagem em Português
* Suporte de ''standards'' abertos e acesso aberto a dados geoespaciais da região
* Promover OSGeo e melhorar a sua visibilidade em vários fóruns

Estas actividades complementariam e fortaleceriam os esforços da OSGeo no aumento do conhecimento da disponibilidade de soluções geoespaciais de código aberto estimulando a sua adopção na educação, indústria, governo e organizações sem fins lucrativos em vários domínios geográficos e linguísticos.

== Responsabilidades do Capítulo (pt) ==
OSGeo não distingue entre um grupo geográfico e um linguístico e estimula a organizaçäo autónoma de forma similar aos ''Grupos de Utilizadores'' ou ''Grupos de Interesse Especial'' em outros projectos ''Open Source''. Os ''Grupos de Utilizadores'' ou os ''Grupos de Interesse Especial'' näo representam formalmente a OSGeo mas podem aproveitar alguns dos serviços como a utilzação da Wiki da OSGeo. O ''Capítulo Português'' oferece uma estrutura formal de organizaçäo autónoma baseada numas poucas directrizes enumeradas de seguida:
* O ''Capítulo Português'' representa oficialmente a OSGeo e é formalmente reconhecido como um projecto de OSGeo.
* O ''Capítulo Português'' deve apoiar as missões e objectivos da OSGeo.
* O ''Capítulo Português'' deve manter encontros regulares (pelo menos um anualmente) e proporcionar um relatório anual sobre as actividades do mesmo ao Comité de Direcção da OSGeo.
* O ''Capítulo Português'' não disporá de nenhum compromisso financeiro de ou em nome da OSGeo. Da mesma maneira, a OSGeo não proporcionará nenhum orçamento ao ''Capítulo Português''.
* O ''Capítulo Português'' deve esforçar-se na sua relação com as organizações para conseguir a participação e o suporte para a OSGeo.
* A OSGeo reserva-se o direito de terminar a sua relação com o ''Capítulo Português'' se tiver razões para crer que as actividades do ''Capítulo Português'' säo contrárias ou em detrimento da Missão e Objectivos da OSGeo.

== Vantagens do Capítulo (pt) ==
* É permitido ao ''Capítulo Português'' o uso do logótipo da OSGeo e outros recursos de imagem corporativa para promover a Missão e Objectivos da OSGeo.
* A OSGeo proporcionará a infra-estrutura necessária para promover a comunicação e visibilidade do ''Capítulo Português''. A infra-estrutura inclui uma lista de correio, hospedagem para páginas wiki e serviço de domínio para o ''Capítulo Português''.

== Formação do Capítulo ==

Para formar um capítulo, deverão ser tomados os passos seguintes:
# O "Capítulo OSGeo" deverá auto-organizar-se (por exemplo no wiki OSGeo, via lista de email OSGeo, etc) procurando determinar se existe uma massa crítica de interesse, que justifique um capítulo local.
##'''FEITO''': [http://lists.osgeo.org/mailman/listinfo/portugal Lista de email] e esta página.
# O "Capítulo OSGeo" deverá preparar os objectivos e missão indicando o escopo do capítulo planeado (extensão geográfica ou linguística por exemplo). '''A FAZER'''
# O "Capítulo OSGeo" deverá propor um representante oficial de ligação à direcção da OSGeo. Se aceite pela OSGeo, o representante será um oficial da OSGeo (officer?) '''A FAZER'''
# O "Capítulo OSGeo" deverá submeter uma declaração oficial de interesse em formar um capítulo à direcção da OSGeo, listando os membros iniciais, missão, representante e outra informação de suporte '''A FAZER'''
# A direcção da OSGeo deverá então aprovar uma moção formalizando o capítulo, e designando o oficial de ligação. '''A FAZER'''

Ao considerar a formação de novos capítulos OSGeo, a direcção tomará em consideração alguns assuntos, incluindo:
* O mandato do capítulo (geográfico ou linguístico) conflitua com outros capítulos existentes ou em formação?
* O capítulo parece ter interesse suficiente para justificar criação oficial?
* O capítulo parece ser aberto a inscrição por todos, e representativo da comunidade geográfica ou linguística alvo? (Por exemplo se o alvo fosse incluir todos os falantes de uma certa língua, seria desapropriado ter só inscritos dum só país)

== Ver também ==
[[Links Uteis Portugal]]

[[Category:Portugal]]

[[Category:Local Chapters]]

Portugal

2008-10-23T17:56:59Z

Wiki-PedroNGV: /* Lista de Interessados */

==Introdução==
Chegou à página wiki do '''Capítulo Local do Osgeo em Portugal'''.

Este grupo tem como interesse comum a criação duma comunidade portuguesa de interessados em software livre de código aberto para SIG, tentando promover uma rede que permita intercâmbio de experiências e suporte mútuo. Assim, esta página pretende ser um ponto de encontro da comunidade, cartão de visita para os novos colaboradores, assim como um ponto de informação e divulgação do Software Livre no âmbito dos Sistemas de Informação Geográfica.

==Nota Histórica==
As '''II Jornadas de SIG Livre''' que decorreram em Girona (Espanha) em Abril de 2008 permitiram o encontro de vários Portugueses, que descobriram um interesse comum em promover o desenvolvimento do SIG livre em Portugal.
Foi um ponto de encontro que permitiu conhecer o representante da Osgeo e alguns membros do Capítulo local espanhol, que imediatamente aproveitaram para nos lançar o desafio de criar também um grupo em Portugal.
Neste sentido, considerou-se importante conseguir criar uma comunidade, o mais numerosa possível, que pense, discuta, desenvolva, organize, apoie e divulgue as acções levadas a cabo nesta área. Decidiu-se, como primeiras iniciativas, criar uma Mailing List e esta página, o Capítulo Local Português na OSGeo.

Partilhamos a esperança de que existem muitos mais portugueses com os mesmos ideais e com vontade de ajudar nesta tarefa em prol de todos e do desenvolvimento do SIG no nosso país!

==Como participar==
Por favor leia a página sobre [[Portugal#Chapter_Roles|o papel do Capítulo Local]] e as suas [[Portugal#Chapter_Responsibilities|Responsabilidades]] antes de inscrever-se. Para inscrever-se basta criar um login no wiki (link no canto superior direito da página) para poder editar as páginas, e de seguida editar esta página acrescentando o seu nome (basta seguir a lógica dos que já estão na lista).
 Depois de criar o seu login, poderá criar a sua página de utilizador, usando o link <nowiki>"http://wiki.osgeo.org/wiki/login_escolhido"</nowiki> e editando-a. Se na página incluir o marcador <nowiki>[[Category: Portugal]]</nowiki>, será incluído automaticamente na [http://wiki.osgeo.org/wiki/Category:Portugal lista de utilizadores do Capítulo português].
 Mantendo a tradição, pode também incluir as coordenadas LatLon da sua localização na sua página de utilizador.

=== Lista de correio ===
A ferramenta principal para comunicação entre todos os interessados. Inscreva-se a se quiser apresente-se à comunidade. Ideal para se manter a par de novidades do Capítulo e do Software Livre de Código Aberto para SIG!
[[User:ominiverdi|Lorenzo Becchi]] é o actual administrador da lista de correio '''Portugal''' para a OSGeo:

http://lists.osgeo.org/mailman/listinfo/portugal

=== Wiki ===
Este wiki está aberto à participação de todos os interessados. Se não sabe bem como editar veja a [[Help:Contents|Ajuda]].
Será a ferramenta preferencial para organizar actividades do Capítulo.

=== Lista de Interessados ===
(criar página autónoma -> se todos colocarem nas suas páginas o marcador <nowiki>[[Category:Portugal]]</nowiki> a lista fica automaticamente feita na [http://wiki.osgeo.org/wiki/Category:Portugal página de Portugal])

# [[User:ominiverdi|Lorenzo Becchi]]
# [[User:victorferreira|Victor Ferreira]], Arquitecto, Lisboa, Portugal.
# [[User:miguelluaces|Miguel R. Luaces]], Engenheiro Informático, Ferrol, Espanha.
# [[User:fred|Fred (Frédéric Lehodey)]], Algarve Digital, Algarve.
# [[User:martinho|Martinho (José Lourenço)]], Eng. Geólogo, Vila Real, Portugal.
# [[User:jgrocha|Jorge Gustavo Rocha]], Eng. Informático, Braga, Portugal.
# [[User:dfurtado|Danilo Furtado]], Msc. Ciência e Sistemas de Informação Geográfica, Lisboa, Portugal.
# [[User:pduarte|Pedro Duarte]], Sintra, Portugal.
# [[User:mario.gomes|Mário Rui Gomes]], Engenheiro Informático, IST/UTL campus do TagusPark, Oeiras, Portugal.
# [[Miguel Tavares]], Engenheiro Geografo, Câmara Municipal de Águeda, Portugal.
# [[User:lutra|Giovanni Manghi]], Unidade de Biologia da Conservação, Universidade de Évora, Portugal.
# [[User:eloi.ribeiro|Eloi Ribeiro]], Técnico SIG, Valencia, Espanha.
# [[User:vanilla|Vânia Neves]], Unidade de Biologia da Conservação, Universidade de Évora, Portugal.
#[[User:Alchimista|André Barbosa]] , Estudante de Eng. Ambiente, Universidade de Aveiro
#[[User:pmonteiro|Pedro Monteiro]], Instituto Regional de Ordenamento Agrário SA, Mestrando do Msc. Ciência e Sistemas de Informação Geográfica, Ponta Delgada, Portugal.
#[[User:Nelsonjsilva|Nelson Silva]], Técnico SIG, Coimbra, Portugal.
#[[Duarte Carreira]], Cuba (Alentejo!), Portugal.
#[http://wiki.osgeo.org/wiki/User:marlagsan Margarida Laginha San-Payo], Lisboa, Portugal.
#[http://wiki.osgeo.org/wiki/User:Hugo.poeira Hugo Poeira], Lisboa, Portugal.
# [[User:joaopinasouza|João Pina Souza]], Lisboa, Portugal.
#[http://wiki.osgeo.org/wiki/User:Termal12 José Manuel Estêvão], Vila Real, Portugal.
# [[User:Lgseco|Luis Gonçalves Seco]], CICGE, FCUP, Portugal.
# [[User:kavune|Vítor Torres Videira]], UM, Portugal.
# [[User:linovski|Avelino Rego]], UM, Portugal.
# [[User:nsosilva|Nelson Silva]], UM, Portugal.
# [[Toze (António José Silva)]], Engenheiro Geógrafo, Águeda, Portugal.
# [[Jacinto Estima]], Engenheiro Geógrafo, Águeda, Portugal.
# [[User:Gnolasco|Gabriel Nolasco]], Geógrafo, Águeda, Portugal.
# [[User:ruigeo|Rui Manuel Dias]], Geógrafo, Lisboa, Portugal.
# [[User:ncharneca|Nuno Charneca]], Doutorando em Eng. Geográfica e Geoinformática, LNEC, Lisboa, Portugal.
# [[User:PedroNGV|Pedro Venâncio]], Geólogo, Mestrando em Sistemas de Informação Geográfica, Pinhel, Portugal.
# Inscreva-se na lista aquí

==Actividades (grupos de trabalho)==
Listagem de actividades propostas pelos membros. As propostas deverão vir acompanhadas dos nomes dos membros responsáveis pela actividade.

=== Jornadas de Software Aberto para SIG ===

Estas jornadas decorrerão de 20 a 22 de Outubro de 2008, na Escola Superior de Tecnologia e Gestão de Águeda, em Águeda.

Toda a informação sobre o evento está em [[Jornadas de Software Aberto para SIG]].

Existe também uma breve introdução ao evento em Inglês [[Open Source for GIS Meeting in Portugal]], para dar a conhecer o mesmo a toda a comunidade OSGeo.

=== Difusão em eventos e conferências ===
Listar aqui eventos que possam ser alvos para divulgação das nossas actividades (indicar responsável pela acção).

=== Tradução e Documentação ===
No sentido de reunir trabalhos de documentação realizados, foi criada a página de [[Documentação SIG Pt|Documentação em Português de ferramentas SIG]].

=== Glossário ===
Importante criar um glossário para suportar toda a actividade de tradução, permitindo coerência global de termos utilizados. '''PRIORITÁRIO! EM PREPARAÇÃO'''

[http://wiki.osgeo.org/wiki/SIG:_Gloss%C3%A1rio_Portugu%C3%AAs SIG: Glossário Português]

=== Directório de Software ===
[http://wiki.osgeo.org/wiki/Links_Uteis_Portugal#Direct.C3.B3rios_de_Software Directório de software utilizado em Portugal.]

== Papéis a desempenhar pelo Capítulo (pt) ==
O Open Source já demonstrou ser um ambiente sólido para a construção de software robusto através da colaboração global aberta. A Fundação Software Geoespacial Aberto (OSGeo) foi criada para apoiar e construir software geoespacial da mais alta qualidade.

A meta da OSGeo é promover o uso de projectos OSGeo globalmente através de uma colaboração localizada forte e a presença em diferentes domínios geográficos e linguísticos. Para além de constituir uma voz local forte para a OSGeo, algumas das principais vantagens da presença desta associação local de OSGeo no enriquecimento e melhora das iniciativas geoespaciais globais são:

* Promover apoio e oportunidades de trabalho aos membros através da rede
* Internacionalização e localização de software
* Desenvolver protótipos de aplicações para demonstrar as capacidades do software livre geoespacial a audiências locais ou regionais
* ''Software Packaging'' e ''Customization'' para as necessidades locais e regionais
* Educação, suporte e desenvolvimento de conteúdos de aprendizagem em Português
* Suporte de ''standards'' abertos e acesso aberto a dados geoespaciais da região
* Promover OSGeo e melhorar a sua visibilidade em vários fóruns

Estas actividades complementariam e fortaleceriam os esforços da OSGeo no aumento do conhecimento da disponibilidade de soluções geoespaciais de código aberto estimulando a sua adopção na educação, indústria, governo e organizações sem fins lucrativos em vários domínios geográficos e linguísticos.

== Responsabilidades do Capítulo (pt) ==
OSGeo não distingue entre um grupo geográfico e um linguístico e estimula a organizaçäo autónoma de forma similar aos ''Grupos de Utilizadores'' ou ''Grupos de Interesse Especial'' em outros projectos ''Open Source''. Os ''Grupos de Utilizadores'' ou os ''Grupos de Interesse Especial'' näo representam formalmente a OSGeo mas podem aproveitar alguns dos serviços como a utilzação da Wiki da OSGeo. O ''Capítulo Português'' oferece uma estrutura formal de organizaçäo autónoma baseada numas poucas directrizes enumeradas de seguida:
* O ''Capítulo Português'' representa oficialmente a OSGeo e é formalmente reconhecido como um projecto de OSGeo.
* O ''Capítulo Português'' deve apoiar as missões e objectivos da OSGeo.
* O ''Capítulo Português'' deve manter encontros regulares (pelo menos um anualmente) e proporcionar um relatório anual sobre as actividades do mesmo ao Comité de Direcção da OSGeo.
* O ''Capítulo Português'' não disporá de nenhum compromisso financeiro de ou em nome da OSGeo. Da mesma maneira, a OSGeo não proporcionará nenhum orçamento ao ''Capítulo Português''.
* O ''Capítulo Português'' deve esforçar-se na sua relação com as organizações para conseguir a participação e o suporte para a OSGeo.
* A OSGeo reserva-se o direito de terminar a sua relação com o ''Capítulo Português'' se tiver razões para crer que as actividades do ''Capítulo Português'' säo contrárias ou em detrimento da Missão e Objectivos da OSGeo.

== Vantagens do Capítulo (pt) ==
* É permitido ao ''Capítulo Português'' o uso do logótipo da OSGeo e outros recursos de imagem corporativa para promover a Missão e Objectivos da OSGeo.
* A OSGeo proporcionará a infra-estrutura necessária para promover a comunicação e visibilidade do ''Capítulo Português''. A infra-estrutura inclui uma lista de correio, hospedagem para páginas wiki e serviço de domínio para o ''Capítulo Português''.

== Formação do Capítulo ==

Para formar um capítulo, deverão ser tomados os passos seguintes:
# O "Capítulo OSGeo" deverá auto-organizar-se (por exemplo no wiki OSGeo, via lista de email OSGeo, etc) procurando determinar se existe uma massa crítica de interesse, que justifique um capítulo local.
##'''FEITO''': [http://lists.osgeo.org/mailman/listinfo/portugal Lista de email] e esta página.
# O "Capítulo OSGeo" deverá preparar os objectivos e missão indicando o escopo do capítulo planeado (extensão geográfica ou linguística por exemplo). '''A FAZER'''
# O "Capítulo OSGeo" deverá propor um representante oficial de ligação à direcção da OSGeo. Se aceite pela OSGeo, o representante será um oficial da OSGeo (officer?) '''A FAZER'''
# O "Capítulo OSGeo" deverá submeter uma declaração oficial de interesse em formar um capítulo à direcção da OSGeo, listando os membros iniciais, missão, representante e outra informação de suporte '''A FAZER'''
# A direcção da OSGeo deverá então aprovar uma moção formalizando o capítulo, e designando o oficial de ligação. '''A FAZER'''

Ao considerar a formação de novos capítulos OSGeo, a direcção tomará em consideração alguns assuntos, incluindo:
* O mandato do capítulo (geográfico ou linguístico) conflitua com outros capítulos existentes ou em formação?
* O capítulo parece ter interesse suficiente para justificar criação oficial?
* O capítulo parece ser aberto a inscrição por todos, e representativo da comunidade geográfica ou linguística alvo? (Por exemplo se o alvo fosse incluir todos os falantes de uma certa língua, seria desapropriado ter só inscritos dum só país)

== Ver também ==
[[Links Uteis Portugal]]

[[Category:Portugal]]

[[Category:Local Chapters]]

PedroNGV

2008-10-23T17:52:31Z

Wiki-PedroNGV:

PedroNGV

2008-10-23T17:45:46Z

Wiki-PedroNGV: New page: Geólogo Mestrando em Sistemas de Informação Geográfica

Geólogo
Mestrando em Sistemas de Informação Geográfica