nyuuzyou/wikis huggingface dataset:
OSGeo y el Capítulo Hispanohablante en las 5as jornadas gvSIG

Category:Marketing en OSGeo-es
Se pretende presentar la fundación y el capítulo durante las 5as Jornadas gvSIG
* Autores (de momento): Jorge Sanz, Pedro-Juan Ferrer
La Open Source Geospatial Foundation (OSGeo[1]) es una fundación sin ánimo de lucro que pretende servir de paraguas para la comunidad de software libre geoespacial (FOSS4G). Esta fundación aúna en un foro común a los mejores proyectos FOSS4G, dotando de infraestructura colaborativa a muchos de ellos. La fundación además dispone de comités para la promoción de los datos libres[2] y para la promoción del FOSS4G en la educación[3]. 
Como fundación de intención claramente internacional, tiene como uno de sus principales objetivos la difusión del software en todo el mundo y en todos los idiomas. Para conseguir este objetivo (especialmente el relacionado con los idiomas) se han ido creando divisiones que actúan de forma local para un ámbito geográfico o lingüístico, son los llamados capítulos locales[4]. 
En este contexto hace ya más de dos años se creó un Capítulo Local para trabajar en el ámbito del idioma español, conocido como Capítulo Local de OSGeo para la comunidad hispano­hablante u OSGeo Spanish[5]. Este capítulo, articulado sobre todo a través de una lista de correo[6] y el wiki de OSGeo ha ido evolucionando y creciendo con relativo éxito. Actualmente la lista de correo del capítulo dispone de más de 300 inscritos. 
En esta comunicación se presentará la fundación: su funcionamiento, estructura y formas de participación así como el trabajo realizado en el ámbito del capítulo hispanohablante: como la participación en eventos, apoyo a la traducción de software y documentación, etc.
===Referencias===
# Web principal de la Fundación: http://www.osgeo.org 
# Comité para los datos libres de OSGeo: http://wiki.osgeo.org/wiki/Public_Geospatial_Data_Committee
# Comité para la educación de OSGeo: http://wiki.osgeo.org/wiki/Education_and_Curriculum_Committee 
# Los capítulos locales de OSGeo: http://wiki.osgeo.org/wiki/Local_Chapters
# OSGeo Spanish: http://es.osgeo.org
# Lista de correo: http://lists.osgeo.org/mailman/listinfo/spanish
OSL

__toc__
Oregon State University's Open Source Lab (OSUOSL) hosts four OSGeo machines.
* OSGeo service users should file a ticket with SAC (http://trac.osgeo.org/osgeo). Under normal conditions only SAC primary administrators should file tickets with OSL. Support tickets are filed by sending emails to support at osuosl.org, please also notify SAC via a trac ticket or mailing list. 
* General Questions from OSGeo SAC can also be discussed on their freenode channel #osuosl .
== General Information on VMs ==
* By default the VMs allow shell access to folks in the LDAP SAC shell access group. Some VMs (ie. qgis.osgeo.org) have their own shell access.
* Selected users are listed in the sudo group in /etc/group for super user access - this can be extended machine by machine as needed by those with permission.
* The VMs also are preconfigured with ssh authorized keys for selected OSGeo primary admins to login directly as root (see /root/.ssh/authorized_keys), avoiding the LDAP requirement - useful if LDAP is misbehaving.
* See SAC:Standard System Setup for details on how to setup a new VM. 
* The VMs also have an osuadmin account used by OSU OSL admins for work.
* All VMs should be listed in the SAC Service Status page under osgeo3 or osgeo4.
== How to Administer Servers ==
There are currently 7 physical servers at OSUOSL (osgeo3- osgeo9). Each has their own web interface requiring OSUOSL OpenVPN access to OSL network in order to access it. osgeo3 - osgeo9 have internal private dns like osgeo3.osuosl.oob etc.
You will find credentials for this in secure container on OSGeo Password store 
There is one for each server e.g. osgeo3.osgeo.osuosl.org for login details for osgeo3 server.
This needs to be written up including information on:
* For day to day use standard public console access, is sufficient as detailed in SAC_Service_Status#Logging_into_Physical_Machines
* Who has access to the physical machines? Only Primary Administrators have physical access and can do hard-reboots in case of major failures.
Such KVM access requires an OSUOSL OpenVPN account
** OSUOSL - Lance is our primary contact (Ramareth on #osuosl)
* Dealing with disk space issues.
* Analysing performance problems.
** 1st stop is to use the monitor instance.
== Opening a ticket ==
If having serious issues with hardware, like the physical host is unreachable even thru the KVM interface.
* Write to 'support at osuosl.org' - only OSGeo SysAdmins should write to support. Other users should put in a trac.osgeo.org/osgeo for general issues
** don't forget to say on which physical machine the VM is (osgeoX, get that from SAC Service Status)
** Example: tracsvn.osgeo.org is on osgeo7
* if urgent, kindly ask in irc://freenode/osuosl
Category:Infrastructure
OSM-RD

=== Problemen ===
Renderen van Nederlandse tiles vereist wat geheugen en schijfruimte. De Nederlandse OpenStreetMap servers zitten wat dat betreft nogal 'vol'. Een insteek om een isgenoeg.nl servertje te regelen voor dit soort gerender, of een loadbalanced high availability cluster, laat ik aan de lezer over. De software om het te realiseren staat hieronder. Importeren moet ook nog wel software voor zijn, maar is mijnsinziens een trivialiteit.
--Skinkie 15:17, 20 December 2011 (PST)
=== Software ===
Voor OpenStreetMap en een project om OSM binnen de muren van de gemeentes te krijgen via een VM die automatisch een stukje OSM selecteert en omzet naar een tile bak, hebben we ook een aanpassing in mod_tile / renderd gemaakt die het mogelijk maakt om 'gewoon' in RD te renderen, volgens het tile schema wat Milo ooit heeft gemaakt.
De code staat hier:
http://kinkrsoftware.nl/contrib/mod_tile/
Voor Cherokee heb ik handler_tile gemaakt die ook automatisch integreert hiermee, maar ik denk dat mod_tile dat technisch ook kan; die code kun je hier vinden:
https://github.com/skinkie/webserver
OSSIM Report 2007

== Key Accomplishments ==
OSSIM has continued to evolve as additional tools, applications and web solutions have been developed with the core C++ library. The key contributors of the project have been working on US Government projects that have been responsible for many of the new tools and capabilities. Most of the recent work has focused on ossimPlanet and OMAR.
ossimPlanet is an accurate 3D global visualization client that emphasizes native file access, navigation and data synchronization between clients and servers, and event driven alerts. This client is being used by several government projects and contractors as well as high end visualization systems located at CALIT2 and the Arizona State University Decision Theater. 
 
 
 Urban Models with ossimPlanet (Washington DC)
 
 Mosaic of Korea with ossimPlanet
OMAR is a web based ossim service that rapidly provides new products to end users.
== Areas for Improvement==
OSSIM is currently in incubation awaiting final graduation. Work is continuing on documenting the wiki and improving the communications from the Program Steering Committee to the developer list.
OSSIM Report 2009

OSSIM 2009 Year in Review 
submitted by Mark Lucas 
The OSSIM project has now been up and running over a decade and continues to rapidly evolve.  The focus of the core OSSIM library is on satellite and aerial image processing and advanced photogrammetry.  Functions in the library essentially take what the camera sees and transforms it into a map.  OSSIM is in use in many international 	language translationground stations and processing centers.  It is often used as part of larger systems such as Opticks and the Orfeo toolbox.  A number corporations and government agencies have integrated OSSIM into their ground station processing solutions.  RadiantBlue Technologies, SPADAC, SAIC, L3-Communications, the Naval Research Labs, the South African Center for Remote Sensing, and the US Department of Defense are just a few examples. 
 
Figure 1.  A historic profile of the source code in the OSSIM repository
The core developers and contributors to the OSSIM project are typically professional software engineers providing commercial and government solutions and engineering students.  At the end of 2009, there are 9 developers with commit permissions in the repository.  OSSIM successfully graduated from OSGeo incubation this year. 
A number of additional libraries, tools, applications, and solutions are included in the OSSIM distribution.  The command line tools are typically used for simple tasks or scripting workflows.  OssimPlanet is an accurate 3D geospatial viewer and collaboration client.  It combines OSSIM and OpenSceneGraph to provide 3D visualization.   ImageLinker is a prototyping / production tool that was originally developed to test the functionality of the OSSIM library.  ImageLinker can construct and manipulate complex "image chains" for complex geospatial products.
As the OSSIM library has matured, the core developers have focused more of their efforts on integrating higher level solutions to government agencies by combining with other open source projects. OMAR is a solution that integrates OSSIM, GDAL, OpenLayers, MapServer, Postgres/Postgis, and GRAILS into a powerful provisioning and processing system for satellite ground stations. The OMAR solution is currently being deployed in various ground stations to rapidly expose and process imagery in archives. At the end of 2009, an OMAR site was established at telascience to support the Haiti relief efforts. Government funding for OMAR development and deployment supports the day to day activities of many of the OSSIM core developers.
The development team is currently looking at the OpenGeo project suite to add a number of new features.
Category: Reports 2009
OTB Code Provenance Review

= Committers =
List of all OTB committers since 2006:
* Amit Kulkarni
* Angelos Tzotsos
* Arnaud Jaen
* Aurelien Bricier
* Caroline Ruffel
* Charles Peyrega
* Chia Aik Song
* Christophe Palmann
* Conrad Bielski
* Cyrille Valladeau
* Daphne Deleflie
* Emmanuel Christophe
* Etienne Bougoin
* Gregoire Mercier
* Guillaume Borrut
* Guillaume Pasero
* Jonathan Guinet
* Jordi Inglada
* Julien Malik
* Julien Michel
* Luc Hermitte
* Manuel Grizonnet
* Mathieu Deltorre
* Mickael Savinaud
* Otmane Lahlou
* Patrick Imbo
* Rashad Kanavath
* Romain Garrigues
* Rosa Ruiloba
* Sebastien Dinot
* Sebastien Harasse
* Stephane Albert
* Thomas Feuvrier
* Tishampati Dhar
* Vincent Poulain
* Yin Tiangang
Actual committers to OTB:
* sdinot (Sébastien Dinot)
* jmalik (Julien Malik)
* msavinaud (Mickaël Savinaud)
* mgrizonnet (Manuel Grizonnet)
* jmichel (Julien Michel)
* gpasero (Guillaume Pasero)
* abricier (Aurélien Bricier)
* jinglada (Jordi Inglada)
* rkanavath (Rashad Kanavath)
* cpalmann (Christophe Palmann)
* salbert (Stéphane Albert)
* lhermitte (Luc Hermitte)
* poughov (Victor Poughon)
An updated list of all contributors to the library is also available in the OTB Software Guide (Chapter 36 - Contributors).
= Outstanding Issues =
There is no outstanding issue regarding OTB code provenance. OTB integrates in one module a dependency to the 6S library (developed by NASA, Maryland University and LOA lab). The software is distribute freely (including the source code) but without explicit license. We've got the agreement from the software authors and we're in the process of formalize this agreement (there is no issue) In the meantime OTB module which use 6S has been deactivated from the Debian package. 
= Included Libraries =
List of third party libraries source code integrated in OTB source tree: 
* 6S
* SiftFast
* Boost (type_traits)
* OssimPLugins
Other OTB dependencies are not included in the source tree.
== Free Libraries ==
* 6S
* SiftFast
* Boost type_traits
* OssimPLugins
== Non-Free Libraries ==
OTB does not include any non-free libraries.
== Code Review ==
Moreover CNES commissioned Black Duck to perform a code review of the library in 2011 which does not highlight issue with 
An extensive code review was done in the frame of the license migration for OTB in 2016/2017(from CeCILL v2 to Apache v2).
Since March 2017, OTB sources are released under Apache v2 (starting with release 6.0). This modification was conduct by the OTB development team and adopted in the following RFC which detail the procedure.
As describe in the RFC, OTB follows Apache foundation guidelines regarding copyright management, headers definition.
OTT OSGEO

Ottawa Chapter
== Executive Members==
Chair: Dave Sampson
Co-Chair: Jeff McKenna
== Meetings ==
 July 20 2006 
 August 31 2006
== Chapter Navigation ==
 Ottawa Chapter Home:
The WIKI Home Page for the Ottawa OSGEO Chapter.
 Chapter Admin: 
Information of interest to the chapter at large concerning meetings, events, charter,etc.
 MapServer: 
Information of interest to local MAPSERVER users (including old OMSUG content)
 GRASS: 
Information of interest to local GRASS users (including old OGUG content)
 MapBuilder:
Information of interest to local MAPBUILDER users
 Local Chapter Directory:
Listing of companies, people, universities and government departments involved with or using OSGeo projects
 Ottawa OSGEO Media Coverage:
Links or snippets of media featuring activities of Ottawa OSGeo from various Sources
OTT OSGEO-meetings-083106

Thurs Aug 31st, 2006<BR>
6pm<BR>
Fox and Feather Pub<BR>
283 Elgin Street (upstairs)<BR>
map
* Approve Mission (below), and select executive (perhaps just a president/chair)
* Presentation on "Coordinate Systems: PROJ.4, EPSG and OGC WKT" by Frank Warmerdam
* Eat, drink and be merry!
Objetivos OSGeo-ES 2011

=== Objetivos OSGeo-ES 2011 ===
Este año, con el fin de generar más actividad en el Capítulo, desde el nuevo Consejo de Dirección, se planteó la idea de definir unos objetivos que centrasen la linea de los esfuerzos ha realizar. 
A lo largo de la vida del Capítulo se han detectado una serie de debilidades en el funcionamiento: 
*Poca implicación de la Comunidad en los organismos de gestión del Capítulo 
*Poca presencia de la Comunidad Latinoamericana 
*Poca actividad del Capítulo en las actividades de la Fundación OSGeo 
*Actividad baja en las iniciativas del Capítulo, Libro SIG, Traducciones, Comites...
Para intentar solucionar alguna de ellas se han definido los siguientes objetivos: 
*Seguir de cerca a los grupos locales e intentar participar en ellos lo máximo posible o al menos que haya gente de OSGeo que participe en ellos
A raíz del surgimiento de las iniciativas locales y su desarrollo como Geoinquietos, se ha definido darles el máximo apoyo y difusión a los mismos, además de participar en ellos, como se ha ido desarrollando hasta ahora. Creemos que el contacto directo con la gente anima a la participación y el desarrollo de la comunidad. 
*Aumentar los eventos no-geo o no-libres en los que tenemos presencia
Ya han existido contactos entre el Capítulo y diferentes organizaciones, pero se marca este año la idea de potenciar esas sinergias. Asi mismo se cree necesaria la presencia del Capítulo en el mayor número de eventos, tanto de temática geo como no, así como del ámbito del software libre o privativo. 
*Incidir en la participación en las actividades del Capítulo y de la Fundación
Durante la vida del Capítulo se han iniciado actividades en las que se reclamaba implicación a los participantes del Capítulo. En muchos casos esta participación ha sido alta, y se quiere incidir en seguir incentivando esta participación, intentando transmitir la necesidad de dedicarle algo de tiempo a las mismas como manera de desarrollar la presencia del Capítulo.
Esperamos la participación de los miembros del Capítulo para poder llevar a buen fin dichos objetivos. Desde el Consejo de Dirección vamos a intentar definir estrategias para la consecución de los mismos. A pesar de la existencia de estos, cualquier iniciativa que surja de manera espontanea será bienvenida y se apoyará como hasta ahora se ha ido haciendo
Category:Español
Official IncCom Documents

This is the list of all official IncCom documents. The documents have been reviewed and approved by the board during the Twelfth Board Meeting on Jun 23, 2006. The stable documents are available in the official documents section at https://incubator.osgeo.org/.
IncCom Document Status
Draft Document (wiki) 	Approved Document	Editors	Status
General Principles of Incubation 	1.0 	
: Daniel Brookshier
: Jody Garnett
: Markus Neteler
: Paul Spencer
: Frank Warmerdam	Reviewed and approved on Jun 23, 2006.
Incubator Application Questionnaire	1.0 	
: Paul Spencer 
: Jo Walsh	Reviewed and approved on Jun 23, 2006.
Project Evaluation Criteria 	1.0 	
: Daniel Brookshier
: Paul Spencer	Reviewed and approved on Jun 23, 2006.
Incubation Mentor Guidelines 	1.1 	
: Paul Spencer 
: Frank Warmerdam	Reviewed and approved on Jun 23, 2006.
Incubation Process 	1.1 	
: Daniel Brookshier
: Markus Neteler
: Paul Spencer	Reviewed and approved on Jun 23, 2006.
Code Provenance Review Process 	1.0 	
: Paul Spencer
: Jo Walsh	Reviewed and approved on Jun 23, 2006.
Project Status Template 	1.1 	
: Cameron Shorter
: Paul Spencer
: Frank Warmerdam	Retired.
Project Graduation Checklist 	2.0 	
: Cameron Shorter
: Paul Spencer
: Frank Warmerdam
: Jody Garnett
: Arnulf Christl	Reviewed and approved, last updated on June 16, 2014.
Project Retiring Process 	1.0 	
: Cameron Shorter	Reviewed and approved on Mar 21, 2010.
Category:Incubation
Official OSGeo Conference Policy

#REDIRECT Archived
Note that this page has now been replaced with a new event policy page
== Description ==
The purpose of this document is to outline rules that must be followed for an OSGeo conference event (meaning any event using the OSGeo name).
== Additional Resources ==
The following are of interest to the conference policy:
* Conference committee homepage
* Board notes regarding Conference policy
== Policy ==
The following guidelines apply to all OSGeo conference events. The terms "conference events" apply to: 1) the annual FOSS4G event, 2) an event hosted by an OSGeo local chapter, 3) a 3rd party event that uses the OSGeo name, and 4) any other event that uses the OSGeo name.
A. Mission -- any event using the OSGeo name must contribute positively to the OSGeo Mission, which is essentially to support the development of open source Geospatial Software, and promote its widespread use.
 
B. Program -- any event using the OSGeo name must have program content that is predominantly related to Open Source geospatial software.
 
C. Value -- any event using the OSGeo name must offer reasonably good "value for money" to paid participants, so as to not reflect poorly on OSGeo.
D. Infrastructure -- any event using the OSGeo name must have a respectable infrastructure (materials, presentation, facilities, and instructors) of good quality so as to not reflect negatively on OSGeo.
E. Acceptance -- any event using the OSGeo name must be approved by OSGeo's Board of Directors. The exact process is as follows:
# event organizer must distribute plan to the osgeo-discuss list for community discussion
# event organizer must distribute a formal plan to the Conference Committee through the conference_dev list
# Conference Committee must vote on the acceptance of the event (abiding by OSGeo's conflict of interest policy)
# if accepted, the Conference Committee recommends the event to OSGeo's Board of Directors, through an email to the board list
# Board of Directors must vote on the recommended event (abiding by OSGeo's conflict of interest policy)
Official OSGeo Event Policy

== Description ==
The purpose of this document is to outline rules that must be followed for an OSGeo event (meaning any event using the OSGeo name).
== Additional Resources ==
The following are of interest to the event policy:
* Conference committee homepage
* Board notes regarding event policy
== OSGeo Event Guidelines ==
The following guidelines apply to all events that use the OSGeo name.
These include:
# the annual FOSS4G event
# an event hosted by an OSGeo local chapter
# Third Party events that uses the OSGeo name
A. Mission -- any event using the OSGeo name must contribute positively to the OSGeo Mission, which is essentially to support the development of open source Geospatial Software, and promote its widespread use.
 
B. Program -- any event using the OSGeo name must have program content that is predominantly related to Open Source geospatial software.
 
C. Value -- any event using the OSGeo name should offer "good value" to the event participants, so as not to reflect poorly on OSGeo.
D. Infrastructure -- any event using the OSGeo name should have a high-quality infrastructure (materials, presentation, facilities, and instructors), so as not to reflect poorly on OSGeo.
== OSGeo Third Party Event Guidelines ==
=== Definition of Third Party ===
* Dictionary definition: a person or group besides the two primarily involved in a situation
In some cases a person or group may want to organise an event independently of OSGeo administration, but wishes to use the OSGeo name or brand. This may include companies, consultants or other organisations including OSGeo members and officers. Financial profit itself does not define a third party event and may or may not be involved in a proposal. OSGeo officers participating in the running of a third party event must not purport to be acting as OSGeo officers.
=== Acceptance ===
Third Parties using the OSGeo or FOSS4G name must abide by the above guidelines, as well as being approved by the OSGeo Board of Directors, as follows:
# The event organizer must distribute a formal plan to the general public osgeo-discuss list for community discussion, and to the Conference Committee through the conference_dev list
# The Conference Committee must vote on the acceptance of the event (abiding by OSGeo's conflict of interest policy)
# If accepted, the Conference Committee recommends the event to OSGeo's Board of Directors, through an email to the board list
# Board of Directors must vote on the recommended event (abiding by OSGeo's conflict of interest policy)
# OSGeo will endeavour to make a decision within 1 month of the event organizer distributing the formal plan, as in step 1 above.
# If the proposal is approved, an agreement document is created to describe how the event organizers and OSGeo will relate during the event planning. Event organizers will not operate under the direct administration or control of OSGeo.
# Event organizers may withdraw their proposal at any point in the process and are under no obligation to OSGeo to deliver the event.
Category:Conference Committee