nyuuzyou/wikis huggingface dataset:
Reglamento de funcionamiento de OSGeo-es

= Reglamento de los miembros =
== Miembros del capítulo ==
=== Derechos ===
=== Deberes ===
=== Altas y bajas ===
== Miembros con Derecho a Voto ==
=== Derechos ===
=== Deberes ===
=== Altas y bajas ===
== Consejo de Dirección ==
=== Derechos ===
=== Deberes ===
=== Altas y bajas ===
* Duración
== Procesos electorales ==
=== Chief Returning Officer ===
= Reuniones =
== Planificación ==
== Herramienas ==
== Actas ==
= Comités =
Los comités, al igual que en OSGeo, son el centro de trabajo del capítulo. Esto significa que a través de ellos debe articularse toda la dinámica de las diferentes actividades que queramos acometer. Por esta razón es importante disponer de unas reglas mínimas que describan los procesos más importantes que regularán el funcionamiento de los mismos.
 NOTA: Hay que revisar las guías generales de OSGeo (Committee Guidelines) para completar y mejorar estas reglas y normas.
== Creación ==
Un comité se podrá crear a partir de una discusión en las listas, el proceso (propuesto) es:
* Discusión en las listas de la conveniencia del comité
* Un Miembro de OSGeo-es debe hacerse responsable del mismo, al menos para arrancarlo
** Preferiblemente no será un miembro de OSGeo-es CD para evitar que el Consejo acabe llevando la carga de trabajo de los comités.
* Se crea una página en el wiki con los contenidos mínimos solicitados
* Se incluye la aprobación oficial del comité en la siguiente reunión programada del OSGeo-es CD
* Se elige una primera lista de miembros y se pueden iniciar las actividades
== Responsabilidades y roles ==
=== Roles ===
;Responsable del comité
: Debe ser un miembro de OSGeo-es. No es necesario que sea un MDV porque este nivel de membresía sólo afecta al poder de votación. En OSGeo.org los responsables de comité son finalmente vicepresidentes de la fundación, pero esto no aplica de momento a OSGeo-es
;Miembro del comité
: Debe ser un miembro de OSGeo-es.
=== Responsabilidades ===
Del responsable:
* Coordinar las actividades del comité, especialmente la correcta documentación en el wiki y la gestión de reuniones.
* El responsable será el contacto oficial entre el Comité y el Consejo Director.
Del miembro del comité (incluido el responsable):
* Participar en el comité de forma activa.
* Participar en las votaciones cuando sea necesario.
== Toma de decisiones ==
* El comité tiene autonomía para tomar las decisiones que estime oportuno, dentro de su ámbito de actuación
* Ante cualquier conflicto que no se pueda resolver internamente, el responsable deberá acudir al OSGeo-es CD
* TODO Política de votaciones por determinar
== Información mínima a mantener ==
La información mínima que el comité debe disponer para arrancar sus actividades es:
* Responsable
* Lista de miembros
* Nombre
* Misión
* Objetivos principales
* Registro de reuniones
** Actas
* Lista de actividades en marcha
Se ha creado una plantilla para la creación de la página de inicio del comité.
Category:Board-es
Regles wiki fr

Retour
=Règles du wiki Francophone=
Voici quelques indications pour éditer les pages de ce wiki :
Règles de nommage des pages du wiki :
* les noms des pages doivent se terminer par _fr
* éventuellement débutant du nom de la section (projet, etc.) par exemple : data_creation_fr, soft_traduc_journal2_fr
* Ajouter ceci à la fin de la page afin de créer un index des pages de la représentation francophone :
[ [Category: Local chapter francophone] ] (enlever les espaces entre les crochets)
* Suivre l'évolution du wiki : http://wiki.osgeo.org/index.php?title=Special:Recentchanges&hideminor=1&feed=rss
Remeras OSGeo-es

== La idea ==
La idea general fue usar una imagen que refleje la filosofía del software libre sin recaer en el uso de los íconos típicos de la geomática como son los mapas, el planeta, la brújula, etc.
Basado en esto, se trabajó sobre la figura de una especie de paloma, que representa la libertad, pero formada por partes pequeñas que representan la integración y la colaboración.
La marca se usa en el frente de la remera, dando principal protagonismo a la idea formada por la paloma, la url del capítulo y la frase "Geomática Libre", que resumen de alguna manera simple qué hacemos y de qué forma.
En la parte de atrás se muestran los datos referentes a la conferencia, jornada o evento particular. Figuran el país, la ciudad y el año. Además, se agrega un ícono referente al país o lugar, que puede ser simplemente una bandera o tal vez algo más informal o divertido, como en el caso del modelo de Denver 2011 donde se incorporó el escudo del Capitán América.
Finalmente, en la manga aparece el isotipo y la marca original de OSGeo.
== La marca ==
* Sobre fondo negro
* Sobre fondo blanco
== Modelos ==
* Denver 2011
* Girona 2012
* Buenos Aires 2012
== Modelos ==
Los archivos con los modelos originales pueden encontrarse en el repositorio SVN
Category: Marketing en OSGeo-es
RencontreSiglalettre2009

= Rencontre SIG la Lettre =
-- En attente de confirmation --
== Présentation ==
Avec le soutien de l’Ecole Nationale des Sciences Géographiques de Marne-la-Vallée, les rencontres de SIG La Lettre vont désormais permettre aux géomaticiens de se retrouver une fois par an pour partager leurs expériences et effectuer une veille technologique intense.
Les avantages des Rencontres de SIG La Lettre :
3 cycles de conférences en parallèle sur la base de sujets sélectionnés par un comité de programme rassemblant des personnalités du monde de la géomatique, de façon à coller au plus près à l’actualité du moment.
La capitalisation sur un média d’information reconnu et sur une longue expérience dans le domaine des conférences. 
[source : http://www.sig-la-lettre.com/?Rencontres-de-SIG-la-Lettre-2009-a-ENSCG]
== Proposition ==
# disponibilité d'un espace de 36 m², avec l'opportunité de réunir 6 stands 
# une salle de conférence toute équipée (capacité de minimum 50 personnes), et la possibilité de proposer un cycle de conférences en toute liberté
# surfaces + mobilier + électricité + connexion Internet
== Organisation/planning ==
== Stands ==
== Conférences ==
== Marketing ==
Category:Past Events
Category: Local chapter francophone
Rendez-vous OSGeo-qc 2012

Dans le cadre de l'évènement VisionGéomatique 2012, le chapitre Québecois de l'OSGeo est fière d'organiser son deuxième rendez-vous les 17 et 18 octobre 2012. Informations ici
Pendant les 2 jours du colloque, une salle sera réservée à des présentations liées aux logiciels libres et open source.
=== Volontaires pour être modérateur de présentations dans la salle OSGeo-qc ===
Le travail de modérateur est très simple:
* Présenter le conférencier
* Indiquer au conférencier lorsqu'il ne reste que 5 minutes
* S'assurer que les présentations commencent et se terminent à l'heure prévue
* Coordonner et animer la période de questions
* Poser une ou deux questions pour stimuler la conversation si nécessaire
Note: Une brève réunion des modérateurs aura lieu mercredi matin le 17 octobre à 7h30, rendez-vous au comptoir d'inscription dans le hall de l'hôtel
Cases horaires à combler:
* Mercredi 10h00 à 12h00: Alan Boudreault
* Mercredi 13h45 à 14h45: Julien-Samuel Lacroix
* Mercredi 15h00 à 16h00: Marc-André Goderre
* Jeudi 10h30 à 12h00: Nicolas Delffon
* Jeudi 13h45 à 14h45: Pierre Racine
* Jeudi 15h00 à 16h00: Mathieu Lahaye
=== Volontaires pour être présent au kiosque OSGeo-qc ===
OSGeo-qc disposera d'un kiosque dans le salon des exposants. Il est nécessaire d'avoir une ou deux personnes disponibles pour informer le public sur les initiatives, les avantages, les logiciels et la philosophie libre et open source.
* Mercredi matin: Jean-Denis Giguère, 
* Mercredi midi: Yoann Perrot, 
* Mercredi pause: Yoann Perrot, 
* Mercredi fin de journée: Jean-Denis Giguère, 
* Jeudi matin: Jean-Denis Giguère, 
* Jeudi midi: , 
* Jeudi pause: , 
* Jeudi fin de journée: ,
Rendez-vous OSGeo Quebec 2010 - Covoiturage

Cette page vise à mettre en contact les participants au Rendez-vous OSGeo Quebec 2010 intéressés à faire du co-voiturage à l'aller vers Saguenay, et/ou au retour de Saguenay vers la ville de départ/retour. 
SVP indiquez si vous offrez ou recherchez une place, ainsi que les points de départ/retour et les dates de voyage prévues. 
== Offres de co-voiturage ==
Nom 	contact/email 	Ville de départ/retour	Nbre Places	Date de départ	Heure de départ	Date de retour
Christian Jauvin	cjauvin@gmail.com 	Montréal 	3 	lundi 14 	vers 15h00 	17
Frédéric Hubert 	frederic.hubert@gmail.com	Québec 	3 	lundi 14 	vers 18h00 	17
== Demandes de co-voiturage ==
Nom 	contact/email 	Ville de départ/retour	Date de départ	Date de retour
Delffon Nicolas 	nicolasdelffon@gmail.com (514-524-8617) 	Montréal 	15/06/2010 	17/06/2010
HALBOUT Hervé 	hhalbout@hc-sig.fr (+33607982765) 	Montréal (très tôt ?) 	15/06/2010 	pas encore défini
Jean-Denis Giguère	j-d.giguere@usherbrooke.ca (819-345-4708)	R (Montréal) 	 	17/06/2010 (après 20h00) ou 18/06/2010
 
----
Revenir à la page de la Journée OSGeo-qc Juin 2010 
Category:Quebec Category:Canada
Representational State Transfer

Representational State Transfer is also known as REST and RESTful.
There is an ongoing discussion in the standards world whether to adopt SOAP as the unique interoperable binding. Because this decision might be detrimental to RESTful design approaches the discussion sometimes turns into a fight between SOAP or REST as if the two could be compared. But they cannot as one is a technology and the other a design approach. It is possible to implement RESTful services using SOAP bindings and the current version of the WSDL standard has explicitly been modified to allow for RESTful implementations. 
== Introduction ==
From Wikipedia: http://en.wikipedia.org/wiki/REST
Representational State Transfer (REST) is a style of software architecture for distributed hypermedia systems such as the World Wide Web. The term was introduced in the doctoral dissertation in 2000 by Roy Fielding,[1], one of the principal authors of the Hypertext Transfer Protocol (HTTP) specification, and has come into widespread use in the networking community.
REST strictly refers to a collection of network architecture principles that outline how resources are defined and addressed. The term is often used in a looser sense to describe any simple interface that transmits domain-specific data over HTTP without an additional messaging layer such as SOAP or session tracking via HTTP cookies. These two meanings can conflict as well as overlap.
== Further Reading ==
* http://blog.geobliki.com/articles/2007/08/06/a-wfs-basic-as-a-geo-atom-store by Patrice Cappelaere 
Leonard Richardson, Sam Ruby: RESTful Web Services, Sebastopol, 2007
* ISBN 10: 0-596-52926-0
* ISBN 13: 9780596529260
Excellent introduction to the RESTful architecture. Must-read for web mapping developers.
Commentary by OSGeo members:
* http://crschmidt.net/blog/archives/275/what-rest-is-really-about/ - Chris Schmidt
* http://geotips.blogspot.com/2007/08/rest-without-resources.html - Paul Ramsey
== Testing and Experimenting ==
=== FeatureServer ===
http://featureserver.org/ with OpenLayers by MetaCarta
=== Mapbender ===
The Mapbender project was urged by some customers to look into implementing SOAP bindings for OGC standards because some industries communicated that this is the only way to implement security required for Digital Restrictions Management for geodata. During the developer meeting in May 2007 it was discussed that this can be done once there is funding available and that the project should also look into RESTful approaches. Further information of any results will be made available on the project pages: http://www.mapbender.org/index.php/SOAP_vs_REST
Category: Standards
Requesting an Area Mailing List

OSGeo supports a variety of area and language specific groups. The first way we do this is by starting a new Page linked from Local Chapters. OSGeo can provide hosting for mailing lists of interested groups. OSGeo does not seek to work against already organized local lists and groups, instead OSGeo just acts as a resource for any new group, or any group looking for new hosting. 
If groups would like to make use of more OSGeo resources, such as web hosting, task tracking, svn, and more, then please raise the issue on the international discuss list, check the International Outreach page.
Research infrastructure

== Research Infrastructure Activities ==
=== Scope ===
This page collects all acitvities within OSGeo, which are related to research infrastructure (RI).
OSGeo activities related to RI currently include internal discussions within Committees and Projects, official agreements with external parties (e.g. MOUs) and reach out activities.
=== Definition Research Infrastructure (RI) ===
Research infrastructure topics are currently adressed using by different terms, including E-Research and others (to be extended).
=== RI Stakeholders ===
Stakeholders in RI-related topics include (but are not limited) to:
* funding agencies (e.g. NSF, European Union, Foundations), 
* publishers/editors (e.g. Science, Nature, Copernicus), 
* data repository manager (e.g. PANGAEA, NASA, etc.)
* data community (e.g. RDA, FORCE11, etc.)
* data/publishing infrastructure
* journal workflow vendors
* librarians
* researcher/scientists (ranging from early career to end-of career).
=== RI paradigms ===
==== Bad Science ====
The term bad science stands for the inceasing number of failings of the classical scientific exchange via scholarly articles, which result from ignoring the changes induced to the scientific work environment by the computer age (especially publication and preservation of research data and research code as part of the scientific process) 
===== Ressources =====
* Bad Science vs. Open Science
* Data Sharing and Management Snafu in 3 Short Acts (video)
* Reference case: Editorial Retraction by Science due to loss of primary research data (Link via DOI tombstone page)
* Shining light into the black box: Publication and citation of scientific software code
==== Open Science ====
Open Science definition by Wikipedia
==== Data Science ====
Data Science definifiton by Wikipedia
==== FAIR (Findable|Accessible|Interoperable|Reproducible) ====
FORCE11 FAIR data principles
=== RI-related activities by OSGeo Projects ===
==== GRASS ====
* Discussion on PSC level about software citation
=== RI-related activities by OSGeo Committees ===
==== GeoForAll ====
* RDA GI interest group (Input from Suchith needed)
==== Open Geoscience ====
===== Science Organisations =====
====== American Geophysical Union (AGU) ======
* Enabling FAIR Data project by AGU: Input as stakeholder
====== European Geoscience Union (EGU) ======
* GA Workshops (Input from Maxi needed)
* GA Splinter Meetings
** 2013
** 2012
* GA Townhall Events
** 2017
** 2016
** 2015
** 2014
=== other RI-related OSGeo activities ===
==== MOU ====
MOU overview page
==== Chapters ====
===== European Chapter =====
* tbd
==== Conferences ====
* FOSS4G Europe 2015 (Como): Dedicated track on library sciences
* FOSS4G Asia 2017 Keynote by Maxi Cannata
* DI4R conference, Brussels Nov 2017 (pster presentation: details needed)
=== Other Stakeholders ===
* British Research Software Engineer Association (RSE)
Response to INSPIRE Discovery and View Draft

This page is meant for collecting feedback about the above draft legal rules for European SDI participants, to be submitted through the FOSS SDIC. We can only send one spreadsheet document on behalf of the SDIC, so either please provide text or a link here if you want your comments to be included.
When adding commentary please mark your contributions with Article or Annex number (e.g. 8.2.3) and paragraph number if necessary, that would help a lot.
* http://inspire.jrc.it/reports/ImplementingRules/network/D3.7_Draft_IR_Discovery_and_View_Services_v2.0.pdf Implementing Rules for Discovery and View Services
* FOSS SDIC
* Response to INSPIRE Network Services Architecture (this document is referenced in this IR and is short so is worth reading first.)
== Responses ==
{| border="1" valign="top"
|Clause/ Subclause||Paragraph/ Figure/ Table||Type comment||Comment||Proposed change
|-
| 6, Protocol bindings || para 1 || G || "One of the requirements specified in the D3.5 Network Services Architecture document is the use of SOAP bindings for all INSPIRE services." This is incorrect. D3.5 does not mandate SOAP, simply offers arguments in its favour and solicits reports and comments from the spatial data user community.||Change "one of the requirements specified" to a less definite wording, or omit this section until the Architecture is actually complete.
|-
| 6 Protocol bindings || para 1|| G || "In the D3.5 Network Services Architecture document it is proposed to implement INSPIRE services as web services, as defined by W3C in http://www.w3c.org/TR/ws-arch/." The URL given is not a W3C Recommendation and explicitly states that it is a Working Group Note which "...does not imply endorsement by the W3C Membership" and also states that "It is inappropriate to cite this document as other than work in progress." At this time in 2003 as today, there was much disagreement about the definition of Web Services. A respected geospatial market analyst wrote at the time that "Today, four organizations - Liberty Alliance, OASIS, W3C and WS- I - are vying to preside over the Web standards process, each with different goals" (see http://www.directionsmag.com/printer.php?article_id=455) and this Working Group Note is one of several competing "definitions" written by members of industry consortia at that time. ||This URL should be removed from citation or it should be made clear that it is a non-binding draft without agreement from the w3c membership.
|-
| 6 Protocol bindings ||para 2|| G ||"Therefore, for INSPIRE Services SOAP bindings are mandatory". This claim is based on two assertions: 1. that the D3.5 Architecture document requires SOAP, and 2. that the W3C organisation defines web services as having SOAP bindings, and neither of these assertions are grounded. ||The mandatory SOAP bindings clause, possibly this entire section of the draft, should be reworded or removed.
|-
extra comments in spreadsheets:
* sent via FOSS SDIC
* sent via CEN
Ressource technique Quebec

= Mapserver =
== Tutoriel ==
*Une marche à suivre pour créer un premier WMS avec la BDGA
*Banc d'essai comparatif ECW, MrSID, JPG2000, TIF
== Mapfile ==
* BDGA(La Base de données géographiques et administratives du Québec 1 / 1 000 000)
* BDTA(La Base de données topographiques et administratives 1 / 250 000)
* BDAT(La Base de données pour l'aménagement du territoire 1 / 100 000)
* BDTQ(La Base de données topographiques du Québec 1 / 20 000)
 
= TileCache =
*TileCache est un projet OpenSource qui prend rapidement de l'ampleur avec la popularité grandissante de OpenLayers. Ce tutoriel facilitera la vie a ceux qui sont intéressés à se familiariser avec ce projet.
= GDAL =
*Documents pour orthophotographie
TODO...
Revenir à la page d'accueil du chapitre québécois.
Category: Quebec
Category: Canada
Category: Local chapter francophone
Ressources documentaires québécoises

== Objectif de cette page ==
Cette page vise à rassembler un ensemble de ressources documentaires propres aux utilisateurs québécois. Les ressources d'intérêt plus général seront partagées avec le chapitre Francophone ou avec la représentation canadienne afin de ne pas dupliquer les efforts. Vous y trouverez néanmoins :
* Une page présentant des cas concrets dans les administrations publiques et organismes privés du Québec.
* Un article dans le bulletin du gouvernement provincial sur l'état de la géomatique libre au Québec a été publié à l'automne 2007, il est disponible ici.
*Des ressources techniques propre au contexte québécois
* ...
Revenir à la page d'accueil du chapitre québécois.
Category: Quebec
Category: Canada
Category: Local chapter francophone
Resultados del Tutorial ISSTOCAM WebGIS

This page shows some screenshots of the results of a 6 day WebGIS workshop at the IODE Project Office (UNESCO/IOC) in Oostende, Belgium. Paticipants came from Ecuador, Colombia, Peru, Chile, online resources from Brazil and a special guest from Belgium. During the course the page Sudamerica was created and some of the participants left their traces in this Wiki. Contact them or hack the correpsonding page if you are interested to further this local chapter, workgroup, page of interrest or whatever it will turn out to be.
== Used Software ==
During the course a lot of software has been installed some of which is explicitlz mentioned here including the reason why it was included.
== Installation Instructions ==
If you want to try out the OSGeo SDI Stack read the Instrucciones de Instalación Course WebGIS Español. 
=== FOSS Geospatial Software ===
* MapServer
* GDAL/OGR
* GeoServer
* PostGIS
* Mapbender
* QuantumGIS
=== System Software ===
* Apache http Server
* PostgreSQL
== Used Data Sets ==
The attendees of the course brought a broad set of data including arid zones of south america, water quality stations, topographic maps, rivers as linestrings, etc. 
* Colombia Direccion General Maritima DIMAR; Instituto de Investigaciones Marinas y Costeras INVEMAR
* Chile Servicio Hidrografico y Oceanografico de la Armada; CAZALAC
* Brazil (servicio WMS demo de la Universidade do Vale do Itajai
* Belgium Continental Shelf VLIZ as special guest
* Perú Direccion de Hidrografía y Navegación DHN
== Screenshot of Bathimetric data off the Brazilian Coast ==
This screenshot shows several WMS services, one with bathymetric data off the Brazilian coast. Check Sudamerica for the corresponding WMS GetCapabilities URL.
== Screenshot of Arid Zones in Sudamerica ==
The data comes as shape files and has been added to a MapServer as WMS and WFS. For usability reasons later WFS was also added using GeoServer.
== Screenshot of Microbiological quality of the water of Colombia ==
The data comes as shape files and has been added to a MapServer as WMS and WFS. For usability reasons later WFS was also added using GeoServer.
thumb|center|700px|Microbiotic Water Quality in Colombia
== Pantalla de las Zonas Aridas de Colombia ==
Los datos son capturados desde una base de datos en postgreSQL con la ayuda de Mapserver como WMS y WFS.
== Pantalla de las Zonas Aridas del Peru ==
Los datos son capturados desde una base de datos en PostgreSQL / PostGIS con la ayuda de MapServer como WMS y WFS.
=== Notas de clase ===
* Instalación de Mapbender
== Pantalla de las Zonas Aridas del Ecuador ==
Los datos son capturados desde una base de datos en PostgreSQL / PostGIS con la ayuda de MapServer como WMS y WFS.
Image:Ecuador.JPG
== Tsunami Warning System in the Indian Ocean ==
An overview of the Tsunami Warning System in the Indian Ocean using WMS and WFS. Data is stored in a MSSQL database and rendered by MapServer using an OVF map-file (this simulates a geometry coming from two lat and lon coordinate column). The information window pops up using the usemap module in MapBender.
Image:Indianocean.JPG