OSGeo - User contributions [en]

FOSS4G 2010 Breakout Sessions

2010-09-03T01:08:39Z

Wiki-Cholmes: /* Java GeoSpatial (GeoTools, GeoServer, uDig, etc...) */

[[Category:FOSS4G]]
[[Category:FOSS4G2010]]

back to [[FOSS4G 2010]]

= Introduction =
During the [http://2010.foss4g.org/ FOSS4G2010 conference] in Barcelona, Spain, there will be conference rooms available for people to hold Breakout Sessions (aka Birds-of-a-Feather).

Breakout Sessions sessions are unstructured timeslots where people can self-organise themselves to discuss topics of interest.

This year, Breakout Sessions sessions will be held on Wednesday 8th September ('''and possibly at other times as well - depending on interest'''). A number of rooms will be available. Most popular sessions will get bigger rooms.

'''Room allocation to be determined'''

==Organising Contact==
* [[Tyler Mitchell]]
* [[Mauricio Miranda]]
* Other volunteers welcome - sign up here!

==Timeslots Available==

At this stage, each room is scheduled for one hour between 18:00 to 19:00.

Remember the Gala Dinner is scheduled at 20:00.

=Room Assignments=
==Rooms Available==

{|class="wikitable" border="1"
! width="150"|Room
! width="400"|Wednesday 08
! width="400"|Contact
|-
| Room 4 (75 pax)
|
|
|-
| Room 5 (250 pax)
|
|
|-
| Room 6 (320 pax)
|
|
|-
| Room 8 (100 pax)
|
|
|-
| Room 11 (78 pax)
|
|
|-
| Room 12 (90 pax)
|
|
|}

= Proposed Topics =

* Add yours below...

==Web Client (OpenLayers/GeoExt)==

The first half of this session will be focused on OpenLayers, and the second half will focus on GeoExt. We can decide on topics at the start of each session, but we'll likely cover ideas for OpenLayers 3.0/GeoExt 1.0, getting more developers involved, and just some general Q/A time.

'''Coming:'''

* Tim Schaub
* Eric Lemoine
* David Jonglez - for the first half, at least
* Florin Iosub
* Xurxo Méndez
* [[Ricardo Pinho|Ricardo Pinho]]
* [[Nuno Guerreiro|Nuno Guerreiro]]
* Hugo Pereira
* [[Just van den Broecke|Just van den Broecke]]
* Sébastien Deleuze
* Richard Greenwood
* Andreas Hocevar

==Spatial Databases BoF==

Relational and non-relational persistence layers, let's get together and talk about interoperability, appropriate use cases, architecture and where we should be moving the spatial persistence state-of-the-art!

'''Coming:'''

* Paul Ramsey (PostGIS)
* Nicklas Avén (PostGIS)
* Brent Wood (NIWA)
* Peter Baumann (Jacobs University / rasdaman)
* Vincent Picavet (Oslandia/PostGIS)
* [[Nuno Guerreiro|Nuno Guerreiro]]
* Olivier Courtin (PostGIS)
* Hugo Pereira
* Volker Mische (CouchDB/GeoCouch)
* [[user:sebastian.ovide|Sebastián Ovide]]

==WPS BoF==

Several presentation on Web Processing selected
for presentation at FOSS4G2010 indicates a growing
interest amongst the communities.

If you are interested please add your names below...

'''Who's coming:'''

* Venkatesh Raghavan
* [[Markus Neteler]]
* [[Daniel Kastl]]
* Maria Brovelli
* [[Ian Turton]]
* [[Gerald Fenoy]]
* Nicolas Bozon
* [[Jody Garnett]]
* [[User:fpenarru | Fran Peñarrubia]]
* [[User:MarkusSchneider | Markus Schneider]]
* Luca Delucchi
* Milan Antonovic
* [[User:Maxi71 | Massimiliano cannata]]
* Luca Casagrande
* [[User:Rajsingh| Raj Singh ]]
* [[User:Jesus|Jorge de Jesus]] (Plymouth Marine Laboratory)
* Bertrand Gervais
* [[User:Schpidi | Stephan Meissl]]
* [[Sebastián Cruz|Sebastián Cruz]]
* Add your name here

==Sensor Web BoF==

The use of Sensor Web implementations has constantly increased during the last years.

If you are interested please add your names below...

'''Who's coming:'''

* Simon Jirka
* Marjorie Robert
* [[User:Maxi71 | Massimiliano cannata]]
* Graeme Mcferren
* Sarawut Ninsawat
* Brent Wood (NIWA)
* Jorge Piera
* Alain Tamayo
* Maria Brovelli
* Add your name here

==Biodiversity/conservation projects and FOSS4G tools==

More and more Open Source is catching on Biodiversity and conservation projects. Most of them are publicly funded so most of the time all the source they develop is Open Source. Aditionally Biodiversity and conservation heavily rely on GIS and they have specific needs. From geospatial niche modeling to species distributions, occurrence catalog, etc, there is a lot to talk about!

If you are interested please add your names below...

'''Coming:'''

* Javier de la Torre (Vizzuality)
* Brent Wood (NIWA)
* [[Markus Neteler]]
* [[User:jesus| Jorge de Jesus]] (Plymouth Marine Laboratory)
* [[User:Aghisla|Anne Ghisla]]
* Add your name here

==Spatial Data Infrastructure==

A birds of a feather session about using open source for spatial data infrastructure. Come discuss implementation strategies, best practices, INSPIRE.

'''Who's coming:'''

* Sebastian Benthall (GeoNode)
* David Winslow (GeoNode)
* Ariel Núñez (GeoNode)
* David Jonglez
* [[Ricardo Pinho|Ricardo Pinho]]
* Hugo Pereira
* Maria Brovelli
* [[Sebastián Cruz|Sebastián Cruz]]
* [[user:sebastian.ovide|Sebastián Ovide]]
* Add your name here

==Virtualization and Cloud Computing BoF==

Virtualization and Cloud Computing is growing fast on the GIS world, let's get together and talk about the use cases and share opinions and suggestions about how can we take the most out of this new technology!

If you are interested please add your name below...

'''Coming:'''
* [[Ricardo Pinho|Ricardo Pinho]]
* Hugo Pereira
* [[Sebastián Cruz|Sebastián Cruz]]
* [[user:sebastian.ovide|Sebastián Ovide]]
* Add your name here

==Spatial OLAP==

Spatial OLAP can be defined as a visual platform built especially to support rapid and easy spatiotemporal analysis and exploration of data following a multidimensional approach comprised of aggregation levels available in cartographic displays as well as in tabular and diagram displays. Let's talk about new improvements combining GIS and BI technologies.

If you are interested please add your name below...

'''Coming:'''
* [[Nuno Guerreiro|Nuno Guerreiro]]
* [[Mauricio Miranda]]
* [[User:Rajsingh| Raj Singh ]]
* Add your name here

==Flex Mapping (Alternatives to HTML)==

Flex is a highly productive, free, open source framework for building expressive web applications that deploy consistently on all major browsers, desktops, and operating systems.
OpenScales is an open source (LGPL) mapping framework written in ActionScript 3 and Flex that allows developers to building Rich Internet Mapping Applications.
There are alternatives to HTML mapping, let's discuss about them...

If you are interested please add your name below...

'''Coming:'''
* Sébastien Deleuze (OpenScales)
* Aurélien Barbier-Accary (OpenScales)
* Simon Lopez (OpenScales)
* Fabio Panettieri
* Marjorie Robert (if the session is planned on tuesday)
* Add your name here

David Jonglez - As discussed previously with other parties, it would be interesting to plan this session in an other time schedule in order to allow a maximum of interested persons already involved in other sessions to participate. What do you think planning this session on tuesday, the 7th evening ? (I'm shure we'll find a place !)

==QGIS user & developer meeting==

Topics:
* What's new in QGIS 1.5
* Interesting plugins
* What's coming in the next QGIS release
* Discussion

If you are interested please add your name below...

'''Coming:'''
* Marco Hugentobler
* [[User:Pirmin_Kalberer| Pirmin Kalberer]]
* Mathias Walker
* [[User:Vasile| Vasile Crăciunescu]]
* [[User:Lmotta| Luiz Motta]]
* Richard Duivenvoorde
* [[User:hdus | Horst Düster]]
* [[User:yoichi | Yoichi Kayama]]

== Java GeoSpatial (GeoTools, GeoServer, uDig, etc...) ==

Topics:

If you are a user or developer in the "Java Tribe" come check out this BOF. You can let the developers know what you like, what you don't like, and what sorts of features and developments you would like to see in the future.

'''Coming:'''

* [[User:jdeolive | Justin Deoliveira]]
* [[User:cholmes | Chris Holmes]]

FOSS4G 2010 Workshops

2010-09-02T22:23:08Z

Wiki-Cholmes: /* Welcome Lunch for Workshop Instructors & Volunteers */

Back to [[FOSS4G 2010]]

== Introduction ==
Workshops are 3-hour sessions in a PC classroom, and Tutorials are 90-minute sessions in a conference room.
The FOSS4G 2010 Workshop Committee is responsible for the organization of both Workshops and Tutorials.

== FOSS4G 2010 Workshop Commitee ==

We need people with experience organizing conference workshops at other GFOSS events. Local (Barcelona & Spain) members are welcome.
If you are willing to help organizing FOSS4G Workshops and Tutorials, please add yourself to the members list below, and subscribe to
the mail list.

=== Workshop Committee Members ===

* [[Oscar Fonts]] IRC username: oscarfonts
* [[Jeff McKenna]] IRC username: jmckenna
* Alvaro Anguix, collaborator
* Mario Carrera, collaborator

=== Communication ===

* Main discussion mail list: [http://lists.osgeo.org/mailman/listinfo/conference-workshops conference-workshops].
* [[FOSS4G_2010_Workshops_meetings|Periodical IRC meetings]].

== Workshop and Tutorial Selection ==

[http://2010.foss4g.org/organization.php FOSS4G 2010 Organization Committee] will evaluate workshop and tutorial proposals attending to these criteria:

# Meets conference mandate:
## Matches with the themes of the conference
## Makes use of software that is both "free" and "open source"
# Submission's technical requirements can be met by the conference facilities
# Demonstrates practical applications
# Expected level of attendee interest in the workshop topic
# A plus for proposals addressing the special interest topics stated in [[FOSS4G_2010_Press_Release_3#FOSS4G_2010_Call_for_Workshops_and_Tutorials|the Call]]
# Likelyhood of a quality workshop:
## Expertise of the workshop presenters in the workshop subject matter
## Presenters personal experience presenting workshops at other conferences
## Successful workshop presented at prior FOSS4G/GFOSS conferences

== Workshop Venue ==

Workshops will be hold in the Barcelona School of Computer Science ([http://www.fib.upc.edu/en.htm FIB]), at [http://www.openstreetmap.org/?lat=41.38854&lon=2.112316&zoom=18&layers=B000FTF Barcelona Campus Nord], buildings B5 and C6 ([http://www.fib.upc.edu/en/centre/on.html address]).

All classrooms have screen and projector for instructors.

Software installation is preferred on Windows XP native Operating System.

If linux is required, we have a vmware SUSE 11.1 image.

=== B5 building classrooms ===

{| class="wikitable"
|-
! Classroom
! # Computers
! PC hardware
|-
| B5.S101
| 21+1
| Intel Core 2 Duo E8500 3.1 Ghz. 4GB RAM. Monitor HP L1950g TFT 19". ASUS EAH3450 Series 1GB (512MB), compatible ATI Radeon HD 34xx. DVD-ROM.
|-
| B5.S201
| 21+1
| Intel Core 2 Duo E8500 3.1 Ghz. 4GB RAM. Monitor HP L1950g TFT 19". ASUS EAH3450 Series 1GB (512MB), compatible ATI Radeon HD 34xx. DVD-ROM.
|-
| B5.S202
| 21+1
| Intel Core 2 Duo E8500 3.1 Ghz. 4GB RAM. Monitor HP L1950g TFT 19". ASUS EAH3450 Series 1GB (512MB), compatible ATI Radeon HD 34xx. DVD-ROM.
|}

=== C6 building classrooms ===

{| class="wikitable"
|-
! Classroom
! # Computers
! PC hardware
|-
| C6.S302
| 24+1
| Intel Core 2 Duo 6320 1.86 Ghz. 2GB RAM. Monitor CRT 17". Nvidia Geforce 6200. DVD-ROM.
|-
| C6.S306
| 20+1
| Intel Core 2 Duo E8400 3.00 Ghz. 2GB RAM. Monitor HP L1750 TFT 17". ATI Radeon X1300. DVD-ROM.
|-
| C6.S308
| 20+1
| Intel Core 2 Duo E8400 3.00 Ghz. 2GB RAM. Monitor HP L1750 TFT 17". ATI Radeon X1300. DVD-ROM.
|-
| C6.S309
| 20+1
| Intel Core 2 Duo E8500 3.1 Ghz. 4GB RAM. Monitor HP L1950g TFT 19". ASUS EAH3450 Series 1GB (512MB), compatible ATI Radeon HD 34xx. DVD-ROM.
|}

== Schedule ==

=== Workshops ===

<div style="margin:5px 5px 0px 0px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#f8f8ff;">

{| class="wikitable"
! Classroom !! Capacity !! Session 1 (Mon 6 Sep 15-18h) !! Session 2 (Tue 7 Sep 9-12h)
|-
| B5.S101 || 42
||''' W1 - Web mapping with GeoServer'''
''Andrea Aime, Mike Pumphrey (OpenGeo)''
|| '''W8 - Getting started with MapServer'''
''Tyler Mitchell (OSGeo), Jeff McKenna (Gateway Geomatics), Perry Nacionales (University of Minnesota)''
|-
| B5.S201 || 42
|| '''W2 - gvSIG 1.9 user workshop'''
''Jorge Sanz (Prodevelop - gvSIG Association), José Vicente Higón (Software Colaborativo - gvSIG Association), Victoria Agazzi (Prodevelop - gvSIG Association)''
|| '''W9 - Quantum GIS and PostGIS: Solving spatial problems and creating web-based analysis tools'''
''Paul Wickman (Northstar Geographics)''
|-
| B5.S202 || 42
|| '''W3 - Setting up an OpenStreetMap rendering toolchain'''
''Iván Sánchez Ortega (OpenStreetMap España), Dane Springmeyer (Mapnik)''
|| '''W10 - FOSS4G routing with pgRouting tools, OpenStreetMap road data and GeoExt'''
''Daniel Kastl (Georepublic), Frédéric Junod (Camptocamp)''
|-
| C6.S302 || 48
|| '''W4 - Introduction to PostGIS'''
''Paul Ramsey (OpenGeo), Mark Cave-Ayland (Sirius)''
|| '''W11 - Working with OpenLayers'''
''Tim Schaub, Charles David Winslow (OpenGeo)''
|-
| C6.S306 || 40
|| '''W5 - Introduction to the Mapbender geoportal framewework'''
''Astrid Emde, Christoph Baudson (WhereGroup)''
|| '''W12 - GeoNetwork for dummies, or how to setup an SDI in 3 hours'''
''Jeroen Ticheler, Jose Garcia, Heikki Doeleman (GeoCat)''
|-
| C6.S308 || 40
|| '''W6 - Solid web mapping with Python'''
''Éric Lemoine, Bruno Binet (Camptocamp)''
|| '''W13 - Geospatial for Java'''
''Jody Garnett (LISAsoft), Justin Deoliveira (OpenGeo)''
|-
| C6.S309 || 40
|| '''W7 - Practical introduction to ZOO, the powerful WPS platform'''
''Gérald Fenoy (GeoLabs), Nicolas Bozon (3LIZ)''
|| '''W14 - Practical introduction to GRASS'''
''Paolo Zatelli, Clara Tattoni, Marco Ciolli (Univeristy of Trento)''
|-
|}

</div>

=== Tutorials ===
Tutorials are 1.5 hour sessions simultaneous to conference talks, in the main conference venue.

<div style="margin:5px 5px 0px 0px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#f8f8ff;">

The tutorials this year will be:

{| class="wikitable"
! Room !! Date&Time !! Tutorial
|-
| Sala 12 || Sept 08 12:00
|| T-01 '''gvSIG Mobile and Mini tutorial'''
''Javier Carrasco, Alberto Romeu (Prodevelop)''
|-
| Sala 11 || Sept 07 16:30
|| T-02 '''PyWPS'''
''Luca Casagrande (Università degli Studi di Perugia), Jorge de Jesus (Plymouth Marine Laboratory) ''
|-
| Sala 12 || Sept 08 14:30
|| T-03 '''Building web based GIS applications with GeoEXT'''
''Pierre Giraud (Camptocamp), Andreas Hocevar (OpenGeo), Yves Jacolin (Camptocamp)''
|-
|-
| Sala 11 || Sept 08 16:30
|| T-04 '''Mastering advanced GeoNetwork'''
''Jeroen Ticheler, Jose Garcia, Heikki Doeleman (GeoCat)''
|-
|-
| Sala 12 || Sept 09 09:00
|| T-05 '''Hands-on introduction to Mapguide Open Source'''
''Gordon Luckett (Arrow Geomatics)''
|-
|-
| Sala 12 || Sept 09 11:00
|| T-06 '''First steps with MapFish'''
''Pierre Mauduit, Antoine Abt (Camptocamp France)''
|-
|-
| Sala 12 || Sept 09 14:00
|| T-07 '''A hands-on introduction to spatial ETL with Geokettle'''
''Thierry Badard (Spatialytics)''
|-
|-
| Sala 11 || Sept 08 12:00
|| T-08 '''How to generate billions of tiles using distributed cloud-computing'''
''Oliver Christen, Cedric Moullet, François Van Der Biest (Camptocamp)''
|-
|-
| Sala 11 || Sept 09 09:00
|| T-10 '''SDI best practices with Geonode'''
''Sebastian Benthall (OpenGeo), Stuart Gill (World Bank)''
|-
|-
| Sala 11 || Sept 08 14:30
|| T-11 '''Standardized geoprocessing with 52°North open source software'''
''Bastian Schaeffer (52°North)''
|-
|-
| Sala 11 || Sept 09 14:00
|| T-12 '''Sensor Web Enablement - Integrating sensor data into Spatial Data Infrastructures'''
''Simon Jirka (52° North), Arne Bröring (University of Münster - Institute für Geoinformatics), Eike Hinderk Jürrens (52° North)''
|-
|-
| Sala 11 || Sept 09 11:00
|| T-13 '''Conquering complex application schemas (INSPIRE Data Themes, GeoSciML, ...) with deegree 3 web services'''
''Markus Schneider (lat/lon GmbH )''
|-
|}
</div>

== Requirements: Software, hardware, geodata ==

=== Workshops ===

Workshop classrooms come with native Windows XP computers. Required software will be installed on Windows XP and tested on mid July. Alternatively, an Open Source Virtual Machine can be provided.

{| class="wikitable"
! Room !! Code !! Title !! Software needs
|-
| B5.S101
|| W1
|| Web Mapping with GeoServer
|| You supply the laptops, we supply the software and data.
|-
| B5.S101
|| W8
|| Getting Started With MapServer
|| No additional material is required. Optional: bring your own datasets to load into your web mapping application. Intermediate/advance questions will be accommodated if time permits.
|-
| B5.S201
|| W2
|| gvSIG 1.9 user workshop
|| the workshop will run on the OSGeo LiveDVD so we suppose we don't need hard and soft additional.
|-
| B5.S201
|| W9
|| Quantum GIS and PostGIS: Solving Spatial Problems and Creating Web-Based Analysis Tools
|| "Quantum GIS v1.4.0 Enceladus" or newer, installed on workshop computers or available on the FOSS4G LiveDVD. Please use Windows "Standalone" version, not the "OSGeo4W" installer version. Internet access to the instructor's PostGIS and WMS/WFS server.
|-
| B5.S202
|| W3
|| Setting up an OpenStreetMap rendering toolchain
|| Hardware: One computer per person, plus overhead projector. Standard internet connection. Nothing out of the ordinary. Software: Already installed in the computers: PostGIS, Mapnik, Mapnik support scripts, Apache2 web server, and mod_tile. Computers *must* run Linux in order for Apache+mod_tile to work. Some other workshops may use PostGIS and Apache, so it should be coordinated. PHPPGAdmin would be a plus. Available somewhere in the workshop CDs: OpenLayers, plus some sets of geodata (global shorelines, plus a small excerpt of OpenStreetMap data). Total size of this data should be around or less than 100 MB. The workshop tutor will provide all materials prior to the workshop. All software in the computers should be tested beforehand, so it is desirable to have a disk image or install CD the tutor can try out ahead of time. Atendees should not bring anything special. All the needed software and data should be readily available in the computers, plus a CD (or pendrive, or similar device).
|-
| B5.S202
|| W10
|| FOSS4G routing with pgRouting tools, OpenStreetMap road data and GeoExt
|| -
|-
| C6.S302
|| W4
|| Introduction to PostGIS
|| Windows XP computers.
|-
| C6.S302
|| W11
|| Working with OpenLayers
|| Participants will complete exercises on a PC (any OS) that is running a web server (e.g. Apache). Participants will need to edit text files with an editor and view examples in a browser. The workshop also requires GeoServer and Postgres w/ PostGIS running. We can provide software and data to be installed in advance of the workshop. In previous workshops, GeoServer has been installed and running, PostGIS configured with workshop data, and Apache configured to proxy GeoServer on port 80 and provide an alias to the workshop document root. We can provide documentation on setting all this up and can help if workshop machines are available before the workshop date. So, requirements are - * PostGIS (configured with data) * GeoServer (running on port 8080 or other) * Apache (configured to proxy GeoServer on port 80 and with alias to workshop document root) * Text editor * Web browser (Firefox recommended).
|-
| C6.S306
|| W5
|| Introduction to the Mapbender Geoportal Framwework
|| The workshop will run completely on the Mapbender Portal provided by OSGeo, no software will be installed during the course all that is needed is a web terminal. Attendees who want to work with their own copy of the software should either install it on a server that is available via internet during the workshop or on their own notebook. To the experienced geoportal operator the installation is straight forward, all information can be found on the Mapbender web site http://www.mapbender.org. If you want to install you own copy but are new to either GIS, web technology, mapping, OGC standards or any combination thereof it is recommended to start the installation well in advance to the workshop as it involves a web server, database, PHP, Mapbender internet accessibility. You will get all the help that you need to set up the system and get it to run properly on the http://www.mapbender.org/index.php/Mapbender_Mailing_Lists.
|-
| C6.S306
|| W12
|| GeoNetwork for dummies, or how to setup an SDI in 3 hours
|| None. CD-ROM and instructions will be brought by workshop organizer.
|-
| C6.S308
|| W6
|| Solid Web Mapping with Python
|| Linux or Windows machine with Python 2.5 or 2.6 installed. Linux is preferred.
|-
| C6.S308
|| W13
|| Geospatial for Java
|| Windows, any version of Java, Students will have choice of Eclipse or NetBeans IDE.
|-
| B5.S101
|| W7
|| Practical Introduction to ZOO, the Powerful WPS Platform
|| computer and ZOO-CD (ZOO-Binaries, GDAL/OGR library and dependencies).
|-
| B5.S101
|| W14
|| Practical Introduction to GRASS
|| For the workshop we need: - GRASS (one of the 6.4 series, 6.4.0RC5 is currently available); - the standard North Carolina GRASS demo data set, the "smaller simpler subset (47MB)" (http://grass.osgeo.org/sampledata/north_carolina/nc_basic_spm.tar.gz) is sufficient; - our HTML tutorial; - our PDF file containing the introductory slides for the workshop. The last years we used our own live DVDs, especially tailored for the Conferences (see for example the 2009 DVD here: http://www.ing.unitn.it/~grass/software/FOSS4G2009_GRASS_beginners_DVD.html), but we can provide our tutorial as a Debian and Ubuntu package, so that it can be included in the OSGEO Live DVD. Since this is a beginners' workshop, it is fundamental that GRASS' version in use matches the one used in the workshop material, so that all the details correspond. Therefore, if the OSGEO Live DVD is used we need to know which GRASS version will be included at least a month in advance, to review all the material. No special hardware is required, maps in the dataset are quite small, therefore a fairly modern Pc will do. No network connection is required, unless you want the attendees to download the tutorial and the dataset. It is possible to use attendees' laptop (some of the attendees have used their own Pc last year in Sydney), but we must be reasonably sure they have a working GRASS installation. Again, the GRASS version can be critical. Last year I have helped some of them to setup their machine via email before the workshop. The use of a live DVD on a Pc provided by the organization is probably the best choice for most of the attendees, since they are not required to setup GRASS before the workshop but they can take the DVD home and re-run the workshop. They can also use the DVD as an installer.
|-
|}

=== Tutorials ===

For tutorials, it is recommended to use the LiveDVD that will be distributed to all delegates.
Instructors are encouraged to join the [http://lists.osgeo.org/mailman/listinfo/live-demo LiveDVD list] and participate in release testing.

== Instructors ==

Workhsop & tutorial instructors will receive credit for registration for "the Conference". See details in the
[[FOSS4G_2010_Discounts#Workshop_Instructors|Discounts page]].

=== Welcome Lunch for Workshop Instructors & Volunteers ===

All Workshop Instructors and Volunteers are invited to a ''Welcome Lunch'' near the Workshop Venue: [http://www.openstreetmap.org/?mlat=41.390649&mlon=2.113446&zoom=17&layers=M Casa Cantabria], Monday Sept. 6, 1PM.

If you want to come, please add yourself to this list BEFORE monday, so we can make the reservation in the restaurant:

* Oscar Fonts (LOC).
* Càrol Puig (LOC).
* Bruno Binet, Camptocamp, W6
* Eric Lemoine, Camptocamp, W6
* Justin Deoliveira, OpenGeo, W13
* Jody Garnett, LisaSoft, W13
* Chris Holmes, OpenGeo, W01

== Calendar ==

* <strike>Jan 15, Opening Call for Workshops/Tutorials</strike>
* <strike>Jan 30, Closing Call for Workshops/Tutorials </strike>
* <strike>Feb 1-15, Workshop/Tutorial selection process</strike>
* <strike>Feb 16, Notification of acceptance for workshops/tutorials</strike>
* <strike>Feb 22, Registration for workshops and tutorials opens</strike>
* <strike>Jul 15 (aprox), Workshop software installation & testing @ classroom PCs.</strike>
* <strike>Aug 25, Manuals sent to printer shop.</strike>
* Aug 31, Printed copies ready.
* Sep 1, Workshops late software installs (v. gr. OSGeo-Live 4.0.1 VM).
* Sep 6 9:00 - 11:00 Workshop environment testing by instructors.
* Sep 6 13:00 - 14:55 Workshops REGISTRATION DESK opening hours.
* Sep 6 15:00 - 18:00 WORKSHOPS 1st SESSION: W1 to W7.
* Sep 7 8:00 - 8:55 Workshops REGISTRATION DESK opening hours.
* Sep 7 9:00-12:00 WORKSHOPS 2nd SESSION: W8 to W14.
* Sep 7-9, FOSS4G TUTORIALS (see schedule above).

== Announcements ==
* [[FOSS4G_2010_Press_Release_3|Call for Workshops and Tutorials (press release 3)]].
* [[FOSS4G_2010_Press_Release_5|Workshops ready for inscriptions (press release 5)]].

[[Category:FOSS4G2010]]
[[Category:FOSS4G]]

Google Summer of Code 2010 Ideas

2010-04-07T18:49:58Z

Wiki-Cholmes: /* The ideas pages */

[[Image:Google_soc_2010_logo.jpg|center|250px]]

* Back to the main OSGeo [[Google Summer of Code 2010]] wiki page.

=OSGeo Google Summer of Code 2010=

The Open Source Geospatial Foundation would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.

These ideas are '''*only*''' to motivate you, and serve as example of the kind of hills we want to charge up. Your own ideas are more than welcomed - they are encouraged. We view you as the next wave of open source leaders; show us what you've got.

'''If you need more information on how to apply you can contact all the mentoring organisations via soc at lists.osgeo.org'''

* There is a [http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers Google SoC flyer] to look at and post in appropriate places.

=What to expect during the summer?=

==Be prepared to be in constant communication with your mentors and project==
You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to intergrate you into the developer community, so you should get involved from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you, in case of problems.

==Weekly reports==
Yes, every week we expect to see a report posted to the soc@osgeo mailing list that at least answers the following questions:
# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?
These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process]. ;)

If you want, feel free to write *more*. But three sentences is the bare minimum. *IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME*, if you don't send this email your mentors will start to get twitchy, and *especially* if they don't get any responses to their emails / don't see you in IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's cool. We have all studied at some point, just tell us about it, be honest. If you don't know how to proceed and your mentor isn't answering *definitely* tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)

Last year this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.

==Wiki page and blogs==
In addition to weekly reports we ask you to maintain a wiki or blog page for your project. You should store your weekly reports there and add other information, like how to compile and test your program. If applicable add screenshots and other nice info.

Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this.

=Timeline=
http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline

* {{done}} March 18th 2010: Google announces accepted organizations. If OSGeo is accepted as an organization for Google Summer of Code, start talking to us earlier rather than later.
* April 9th 2010: Student application deadline. The earlier you start the more probable it is that you will be accepted! There is two way feedback during the application process which really helps you improve and clarify your application before this final deadline.
* April 26th 2010: Accepted student proposals are announced.
* May 24th 2010: Coding begins!
* July 12-16th: Mid-term evaluation.
* August 9th: Pencils down!

= The ideas pages =
Each participating project's list of ideas is here, with a short description of the project and what type of students would be interested in it:

* [http://trac.osgeo.org/gdal/wiki/SummerOfCode GDAL SoC Ideas]: GDAL is the Geographic Data Abstraction Library, a library which provides access to spatial data in all kinds of formats via a uniform API.
* [http://grass.osgeo.org/wiki/GRASS_SoC_Ideas GRASS SoC Ideas]: GRASS GIS is an open source GIS focusing mainly on analysis. It is written as a collection of stand-alone C programs and has a new GUI written in Python. If you know Python, or want to implement algorithms in C take a look!
* [http://www.mapbender.org/GSoC_2010 Mapbender SoC ideas 2010]: Mapbender is a server and client side geographic data management tool, programmed in '''PHP''' and '''JavaScript''', using the '''jQuery''' library.
* [http://www.qgis.org/wiki/Google_Summer_of_Code_2010 Quantum GIS SoC Ideas] Quantum GIS (QGIS) is a user friendly Open Source Geographic Information System (GIS) that runs on Linux, Unix, Mac OSX, and Windows. QGIS supports vector, raster, and database formats.
* [http://udig.refractions.net/confluence/display/HACK/Summer+of+Code uDig Summer of Code]: User-friendly Desktop GIS is a Java application written with the Eclipse RCP framework. The project has a community svn area to host student plug-ins, tutorials cover how to package up a custom application to show off your work.
* [http://sourceforge.net/apps/mediawiki/jump-pilot/index.php?title=OpenJUMP_Google_Summer_Of_Code OpenJUMP/deegree Ideas List]: deegree and OpenJUMP share code derived from the original JUMP. Both programs maintain separate development lists and source code repositories but look for opportunities to collaborate.
* [http://wiki.osgeo.org/wiki/OpenRouter_2010_SOC_Ideas OpenRouter 2010 SOC Ideas]: OpenRouter is a couple of projects that are building routing and driving direction libraries and applications that can be integrated with other applications.
* OSSIM [http://web.me.com/epiesasha/PlanetSasha/2010Project.html Py-OSSIM]: - ossim-swig-python to generate code to call ossim from python
* [[OSGeo_Cartographic_Engine#Ideas_for_Summer_of_Code_2010_Project | Cartographic Engine project ideas built on Mapnik]]: Refining much needed high quality hardcopy output tools that encourage collaboration. Built on Mapnik, applications like QGIS, GRASS, MapServer, etc. can output using these features. Focused initially on building specs that support Mapnik as the engine, but that could be applied generally across OSGeo projects as well.
* [http://www.spatialytics.org/google-summer-of-code-2010-ideas/ Spatialytics.org GSoC 2010 Ideas]: Spatialytics.org is the new home of the three open source Geospatial BI projects (GeoKettle, GeoMondrian and SOLAPLayers). Geospatial Business Intelligence (BI) tools, such as spatial ETL (Extract, Transform and Load), geo-analytical dashboards and Spatial On-Line Analytical Processing (SOLAP) allow decision-makers to rapidly analyze large amount of data at different levels of time, geography and detail in order to make better decisions.
* [http://www.mapwindow.org/wiki/index.php/Google_Summer_of_Code MapWindow GIS SoC Ideas]: MapWindow is a free, extensible, geographic information system (GIS) that can be used as an alternative desktop GIS, to distribute data to others, to develop and distribute custom spatial data analyses, written in .NET (C++, C#, VB.NET). If you're a talented VB.Net, C#, or C++ programmer, you could be the perfect fit to work on this project. We have a couple of ideas that could be done over the summer; feel free to suggest your own ideas or plug-ins as well.
* [[MapServer_2010_SOC_Ideas | MapServer GSoC Ideas]]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.
* [[Live_GIS_Disc_GSoC_2010 | OSGeo Live]] is a stack of 35+ of the best GeoSpatial Open Source packages bundled as a LiveDVD and Virtual Machine on top an Xubuntu linux ditribution. There are opportunities to address packaging and cross project quality control through application of systematic testing processes. Through this project, developers will gain a broad understanding of the full GeoSpatial Open Source stack.
* [[gvSIG GSoC 2010 Ideas|gvSIG]] is the free GIS project developed by the Regional Department of Infrastructures and Transport of the Valencian Government (Spain). gvSIG is at this time a group of software developments for [http://www.gvsig.org/web/projects/gvsig-desktop/description2/view?set_language=en Desktop],[http://www.gvsig.org/web/projects/gvsig-mobile/description-2/view?set_language=en PDAs] and [http://gvsigmini.org mobile phones].
* [http://geoserver.org/display/GEOS/Summer+of+Code+2010 GeoServer] is an open source software server written in Java that allows users to share and edit geospatial data. Designed for interoperability, it publishes data from any major spatial data source using open standards.

=Application Template=
==Contact Information==
* '''Name:'''
* '''Country:'''
* '''School and degree:'''
* '''Email:'''
* '''Phone:'''
* '''OSGeo project(s):'''

==Application==
===Title===
===Introduction===
A summary of your idea. About 300 words is a suitable length
===Background===
Describe how your project relates to your project and OSGeo. Also describe how you came to think of the idea.
===The idea===
Describe your detail in as much detail as you can. Explain what algorithms you intend to use/study (if any). Also describe the business benefit, that is how your idea improves the program it is intended for. Who is your intended target audience (end users?, administrators?, developers?)
===Project plan===
How do you plan to spend your summer? Please include a preliminary week-by-week plan on how you think you can fulfill your project in the time allocated.
===Future ideas / How can your idea be expanded?===
Describe how your idea can be improved and extended, and what the benefits of this extension would be. Perhaps your idea can be used in some other project, or for something else?

==Answer the following questions briefly (about 300 words max)==
===How does your SoC task benefit the OSGeo member project, and more generally the OSGeo Foundation as a whole?===

===Please provide details of previous GIS experience===

===Do you have any previous GIS programming and other software programming experience?===
If you do explain what and when.

===Please provide details of general computing experience===
We are looking for things like operating systems you use on a day-to-day basis, programming languages you could write a program in, hardware, networking experience, etc.

===Please tell us why you are interested in GIS and open source software===

===Please tell us why you are interested in your specific coding project===

===Please tell us why you are interested in working for OSGeo and the software project(s) you have selected===

===Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?===

= What is the main public mailing list for your organization? =
Since OSGeo is an umbrella organisation for multiple projects, each project has their own discussion and development mailing lists.

'''Main OSGeo mailing lists of interest to students.'''

Please start here, when contacting us for the first time with questions about Google Summer of Code.

* OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc)
* OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)

Also see the [[Mailing Lists]] page for project specific lists.

= What is the main IRC channel for your organization? =

irc://irc.freenode.net/#osgeo (Web based [http://irc.telascience.org/cgi-bin/irc.cgi IRC client], [http://webchat.freenode.net alternative)

Project irc channels:

* irc://irc.freenode.net/#gdal
* irc://irc.freenode.net/#geoserver
* irc://irc.freenode.net/#geotools
* irc://irc.freenode.net/#grass
* irc://irc.freenode.net/#gvsig
* irc://irc.freenode.net/#mapbender
* irc://irc.freenode.net/#mapbuilder
* irc://irc.freenode.net/#mapguide
* irc://irc.freenode.net/#mapnik
* irc://irc.freenode.net/#mapserver
* irc://irc.freenode.net/#openlayers
* irc://irc.freenode.net/#ossimplanet
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#qgis
* irc://irc.freenode.net/#udig

[[Category:Google Summer of Code]]

Google Summer of Code 2009 Ideas

2009-03-22T08:22:40Z

Wiki-Cholmes:

[[Image:2009_summer_of_code_logo_final_r3-01.png|center|250px]]

* Back to the main OSGeo [[Google Summer of Code 2009]] wiki page.

=OSGeo Google Summer of Code 2009=
The Open Source Geospatial Foundation would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.

These ideas are '''*only*''' to motivate you, and serve as example of the kind of hills we want to charge up. Your own ideas are more than welcomed - they are encouraged. We view you as the next wave of open source leaders; show us what you've got.

'''If you need more information on how to apply you can contact all the mentoring organisations via soc at lists.osgeo.org'''

* There is a [http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers Google SoC flyer] to look at and post in appropriate places.

=What to expect during the summer?=

==Be prepared to be in constant communication with your mentors and project==
You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to intergrate you into the developer community, so you should get involved from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you, in case of problems.

==Weekly reports==
Yes, every week we expect to see a report that at least answers the following questions:
# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?

If you want, feel free to write *more*. But three sentences is the bare minimum. *IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME*, if you don't send this email your mentors will start to get twitchy, and *especially* if they don't get any responses to their emails / don't see you in IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's cool. We have all studied at some point, just tell us about it, be honest. If you don't know how to proceed and your mentor isn't answering *definitely* tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)

Last year this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.

==Wiki page==
In addition to weekly reports we ask you to maintain a wiki page for your project. You should store your weekly reports there and add other information, like how to compile and test your program. If applicable add screenshots and other nice info.

=Timeline=
http://socghop.appspot.com/document/show/program/google/gsoc2009/faqs#timeline

* March 18th 2009: Google announces accepted organisations. If OSGeo is accepted as an organization for Google Summer of Code, start talking to us earlier rather than later.
* April 3rd 2009: Student application deadline. The earlier you start the more probable it is that you will be accepted!
* April 20th 2009: Accepted student proposals are announced.
* May 23rd 2009: Coding begins!
* July 6th - July 13th: Mid-term evaluation.
* Agust 10th: Pencils down!

= What is the URL for your ideas page? =
Each participating project's list of ideas is here, with a short description of the project and what type of students would be interested in it.

* [http://trac.openlayers.org/wiki/SummerOfCode OpenLayers]: OpenLayers is a Javascript based mapping client, similar to the Javascript used to power Google Maps and other similar mapping websites. Ideas run the full range of math-oriented vector operations to full scale browser-based GIS application development. Good place to look if you're interested in Javascript.
* [http://trac.osgeo.org/gdal/wiki/SummerOfCode GDAL SoC Ideas]: GDAL is the Geographic Data Abstraction Library, a library which provides access to spatial data in all kinds of formats via a uniform API.
* [http://grass.osgeo.org/wiki/GRASS_SoC_Ideas GRASS SoC Ideas]: GRASS GIS is an open source GIS focusing mainly on analysis. It is written as a collection of stand-alone C programs and has a new GUI written in Python. If you know Python, or want to implement algorithms in C take a look!
* [http://www.mapbender.org/GSoC_2009 Mapbender SoC ideas 2009]: Mapbender is a server and client side geographic data management tool.
* [http://wiki.qgis.org/qgiswiki/SummerOfCodeIdeas Quantum GIS SoC Ideas] Quantum GIS (QGIS) is a user friendly Open Source Geographic Information System (GIS) that runs on Linux, Unix, Mac OSX, and Windows. QGIS supports vector, raster, and database formats.
* [[MapServer 2009 SOC Ideas]]
* [http://geosoa.scg.ulaval.ca/en/index.php?module=pagemaster&PAGE_user_op=view_page&PAGE_id=20 Laval University 2009 SoC ideas]: Based on OpenLayers and other relevant software from OSGeo, this project aims at designing and developing a tool to produce rich and interactive geo-analytical dashboards. Such dashboards will serve as a front end for a range of Spatial OLAP technologies to better support decision makers, managers, etc. in making informed decisions.
* [http://geoserver.org/display/GEOS/Summer+of+Code+2009 GeoServer SoC 2009]: GeoServer supports Web Map Server, Web Feature Server and Web Coverage Service protocols. It makes spatial information available in a range of formats from GeoTIFF to KML. The application is Java EE based, making use of Spring to wire everything up. The application supports a plug-in system so student contributions can me distributed as they are ready.
* [http://docs.codehaus.org/display/GEOTOOLS/Summer+of+Code+2009 GeoTools SoC 2009]: GeoTools is a Java toolkit for working with spatial data, it covers everything from bits on disk to rendering. It provides client code for WFS, WMS and supports a range of data sources like shapefile and PostGIS. The library is used by a lot of the Java applications on this page. The library has a plug-in system so students work can be distributed via maven as they are ready.
* [http://udig.refractions.net/confluence/display/HACK/Summer+of+Code uDig SoC 2009]: User-friendly Desktop GIS is a Java application written with the Eclipse RCP framework. The project has a community svn area to host student plug-ins, tutorials cover how to package up a custom application to show off your work.
* [http://openjump.org/wiki/show/Google+Summer+Of+Code+Ideas+List OpenJUMP/deegree Ideas List]: deegree and OpenJUMP share code derived from the original JUMP. Both programs maintain separate development lists and source code repositories but look for opportunities to collaborate.

= What is the main public mailing list for your organization? =
Since OSGeo is an umbrella organisation for multiple projects, each project has their own discussion and development mailing lists.

'''Main OSGeo mailing lists of interest to students.'''

Please start here, when contacting us for the first time with questions about Google Summer of Code.

* OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc)
* OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)

'''Project development lists'''

* GeoServer - geoserver-devel@lists.sourceforge.net ( http://lists.sourceforge.net/lists/listinfo/geoserver-devel )
* GeoTools - geotools-devel@lists.sourceforge.net ( http://lists.sourceforge.net/lists/listinfo/geotools-devel )
* uDig - udig-devel@lists.refractions.net ( http://lists.refractions.net/mailman/listinfo/udig-devel )
* MapGuide - mapguide-internals@lists.osgeo.org ( http://lists.osgeo.org/mailman/listinfo/mapguide-internals )
* OpenJUMP - jump-pilot-devel@lists.sourceforge.net ( http://lists.sourceforge.net/lists/listinfo/jump-pilot-devel )
* MapServer - mapserver-dev@lists.osgeo.org ( http://lists.osgeo.org/mailman/listinfo/mapserver-dev )
* GDAL - gdal-dev@lists.osgeo.org ( http://lists.osgeo.org/mailman/listinfo/gdal-dev )
* PostGIS - postgis-users@postgis.refractions.net ( http://postgis.refractions.net/mailman/listinfo/postgis-users )
* GRASS - grass-dev@lists.osgeo.org ( http://lists.osgeo.org/mailman/listinfo/grass-dev )
* Quantum GIS - qgis-developer@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/qgis-developer)
* Mapbender - mapbender_dev@lists.osgeo.org ( http://lists.osgeo.org/mailman/listinfo/mapbender_dev )
* OpenJUMP - jump-pilot-devel@lists.sourceforge.net (https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel)
* deegree - deegree-devel@lists.sourceforge.net (https://lists.sourceforge.net/lists/listinfo/deegree-devel)
* OpenLayers - dev@openlayers.org (http://openlayers.org/mailman/listinfo/dev)

= What is the main IRC channel for your organization? =

irc://irc.freenode.net/#osgeo (Web based [http://irc.telascience.org/cgi-bin/irc.cgi IRC client])

Project irc channels:

* irc://irc.freenode.net/#geoserver
* irc://irc.freenode.net/#geotools
* irc://irc.freenode.net/#udig
* irc://irc.freenode.net/#mapbuilder
* irc://irc.freenode.net/#mapguide
* irc://irc.freenode.net/#mapserver
* irc://irc.freenode.net/#openlayers
* irc://irc.freenode.net/#gdal
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#grass
* irc://irc.freenode.net/#qgis
* irc://irc.freenode.net/#mapbender

[[Category:Google Summer of Code]]

OSGeo en Informatica 2009

2008-10-11T20:17:32Z

Wiki-Cholmes:

Aquí se coordina la participación de OSGeo [[Spanish]] en [[Informatica 2009]].

==Nota de prensa para listas, blogs, etc==

===Español===
''OSGeo-es participará en la convención «Informática 2009» en La Habana, Cuba''

Del 9 al 14 de Febrero sesionará en La Habana la XIII Feria y Convención Internacional Informática 2009[1]. En el marco de estas jornadas tendrá lugar el VI Congreso Internacional de Geomática[2], donde el Capítulo local de OSGeo para la Comunidad Hispano-hablante (OSGeo-es[3]) estará presente con el objetivo de promocionar el software libre para la geomática (FOSS4G), fomentar la implementación de estándares abiertos y la interoperabilidad basada en estándares y promover el acceso libre a los datos.

El Capítulo local de OSGeo para la Comunidad Hispano-hablante invita a participar el Lunes 9 de Febrero, en el Palacio de las Convenciones, en una jornada de talleres y demostraciones prácticas[4] desarrollados por varios de los miembros de su Consejo Director. Estos talleres pretenden brindar una panorámica del estado del arte de las principales tecnologías FOSS4G a la vez que sirven como pretexto para reunir a usuarios y desarrolladores de las comunidades de Latinoamérica y el resto del Mundo.

Igualmente OSGeo tendrá participación con ponencias para presentar el capítulo local y la fundación, así como presentaciones de otros proyectos FOSS4G en los que participan los miembros del Consejo Director. Así mismo se realizará una mesa redonda sobre software libre en el marco del congreso.

El VI Congreso Internacional de Geomática reunirá además, un numeroso grupo de especialistas de alto nivel técnico profesional que abordarán varias temáticas relacionadas con la informática de las ciencias de la Tierra. Para obtener información detallada sobre inscripciones y envío de contribuciones por favor consultar el sitio de los organizadores. El plazo de admisión de trabajos vence el 30 de Octubre de 2008.

===Français===
''OSGeo-es participera à la convention «Informatique 2009» à La Havane, Cuba''

Du 9 au 14 février sera réalisé à La Havane la XIII Convention Internationale et Foire Informatique 2009[1]. Dans le cadre de cette conférence aura lieu le VI Congrès International de Géomatique[2], où la section locale de OSGeo de la Communauté hispanophone (OSGeo-es[3]) será présent dans le but de promouvoir le logiciel libre pour géomatique (FOSS4G), de promouvoir la implémentation de normes ouvertes et l'interopérabilité basée sur des standards et de promouvoir le libre accès aux données.

La Section Locale de la Communauté hispanophone OSGeo les invite à participer le lundi 9 février au Palais des Conventions à une journée d'ateliers et de démonstrations pratiques[4] développés par plusieurs membres de son conseil d'administration. Ces ateliers cherchent à offrir un panorama de l'état des technologies principales FOSS4G en même temps qui servent de prétexte pour rassembler les utilisateurs et les développeurs des communautés en Amérique latine et dans le reste du monde.

OSGeo également participera avec présentations pour faire connaître la Section Locale et de la Fondation, ainsi que la présentation d'autres projets FOSS4G auxquels participent des membres du Comité Directeur. Aussi, sera réalisé une table ronde sur le thème des logiciels libres dans le cadre du congrès.

Le sixieme Congrès International des Sciences Géomatiques réunira outre, un grand groupe de spécialistes de haut niveau technique professionnel qui aborderont quelques doctrines relatives aux technologies de l'information pour les sciences de la Terre. Pour obtenir une information détaillée sur des inscriptions et l'envoi de contributions s'il vous plaît consulter le site Web des organisateurs. La date limite pour la réception des travaux prend fin le Octobre 30, 2008.
===English===
''OSGeo-es will take part in the congress «Informática 2009» in La Havana, Cuba''

On February 9-14, 2009 the 13th "Feria y Convención Internacional Informática 2009"[1] will take place in Havana. At the VI Internacional Congress of Geomatics [2], part of the greater congress, the Spanish Language Local Chapter of OSGeo (OSGeo-es [3]) will attend to promote the Free Software for Geomatics (FOSS4G), foster the implementation of Open Standards and their usage for interoperability and promote the access to Free Geo-data.

The Spanish Language Local Chapter of OSGeo invites everybody to participate, Monday Feb. 9 2009, in the Convention Palace (Palacio de las Convenciones), in a day of workshops and practical demonstrations [4] prepared by some of the members of its community. These workshops promise to offer an overview of FOSS4G state of the art technologies and to let users, developers and Latin-American communities meet the international one.

OSGeo and OSGeo-es will be introduced in a dedicated session. A round table on Free Software for Geomatics will be organized too.

The VI Geomatics International Congress will join together a group of high level specialist who will address several issues on IT and Earth Sciences.
For further information and to submit your talk or workshop proposal, please visit the web site of the event [2].
Call for Papers deadline is set on Oct. 30, 2008.

===Italiano===
''OSGeo-es parteciperà al convegno "Informática 2009" che si terrá a La Avana, Cuba''

Dal 9 al 14 Febraio 2009 si terrá a la Avana la XIII Feria y Convención Internacional Informática 2009 [1]. Nell'ambito di questo evento si terrà il VI Congresso Internazionale di Geomatica [2], dove il Capitolo Locale di Lingua Spagnola di OSGeo (OSgeo-es [3]) sarà presente con l'obbiettivo di promuovere il Software Libero per la Geomatica (FOSS4G). stimolare l'utilizzo di standard aperti e promuovere l'accesso ai dai geo-spaziali liberi.

OSGeo-es invita a partecipare lunedì 9 Febbraio 2009, nel Palacio de las Convenciones, ad una giornata di Workshop e dimostrazioni pratiche [4], preparate dagli membri della Comunità. Questi workshop cercheranno di offrire una panoramica dello stato dell'arte de le principali tecnologie FOSS4G e allo stesso tempo serviranno per far incontrare gli sviluppatori con i membri della comunità latino-americana.

La fondazione di OSGeo verrá presentata insieme al suo capitolo locale insieme a vari progetti FOSS4G. Nell'ambito del congresso verrá anche realizzata una tavola rotonda sul software libero.

Il VI Congresso Internazionale di Geomatica riunirà un numeroso gruppo di tecnici specializzati nelle varie tematiche relative all'informatica e alle scienze della terra. Per avere informazioni più dettagliate sulle modalità di iscrizione ed invio dei contributi si consiglia di visitare il sito dell'organizzazione [2].

Il termine ultimo per la presentazione delle proposte e' il 30 ottobre 2008.

[1] http://www.informaticahabana.com/ 
[2] http://www.informaticahabana.com/?q=es/listeventos_es&e=13&id=es&ci=1 
[3] http://wiki.osgeo.org/wiki/Spanish 
[4] http://wiki.osgeo.org/wiki/OSGeo_en_Informatica_2009

==Temáticas==

El evento tratará, entre [http://www.informaticahabana.com/?q=es/listeventos_es&e=13&id=es&ci=1 otras] la temática del '''Software de código abierto en tecnología geoespacial.'''

== Talleres ==

* Los resúmenes de los talleres deben estar listos y en la wiki el
2008-10-31 para poder ser revisados.

* Procesamiento y transformación de datos
** Responsable [[User:Vehrka|Pedro-Juan Ferrer Matoses]]

* Servidores OWS: Servicios OGC con Mapserver
** Responsable [[User:elpbatista|Jorge L. Batista]]

* Cientes ligeros: OWS con Openlayers
** Responsable [[User:ominiverdi|Lorenzo Becchi]]

* Clientes pesados: OWS con gvSIG y gvSIG mobile
** Responsable [[User:Jsanz|Jorge Gaspar Sanz]]

*Desarrollo de plugins para QGIS usando Python ''(añadido recientemente)''
** Responsable [[User:FranciscoPalm|Francisco Palm]]

== Ponencias propuestas ==
* OSGeo y el Capítulo Local para la Comunidad Hispano-hablante [[OSGeo_en_4th_gvSIG_Conference#OSGeo_y_el_Cap.C3.ADtulo_Local_para_la_Comunidad_Hispano-hablante | resumen]] (conferencia magistral)
* Panorama actual del ecosistema de Software Libre para SIG ([http://www.sigte.udg.es/jornadassiglibre/uploads/file/Ponencias/A5.odt artículo])
* pyWPS, una implementación de WPS
* Presentación de gvSIG Mobile ¿demostración práctica?
* Presentación del estado del proyecto gvSIG
* Presentación de OpenLayers
* Presentación de Ka-Map

== Otras actividades ==

* Póster del Panorama del Software Libre para GIS (con la colaboración del [http://cartolab.udc.es/index.html CartoLab] (Universidad de A Courña).
* Mesa Redonda (panel) Implementación de un SIG Libre... proyectos significativos y casos de uso ¿?
* La Iniciativa OpenStreetMap: ¿Fiesta del mapa?
* Presentación del LiveCD ¿taller?

== Logística ==

* Alojamiento
* Transporte
* ...

[[Category:Español]]
[[Category:Events]]

2008 Google SoC Application

2008-03-11T18:24:59Z

Wiki-Cholmes:

==What is your Organization's Name?==
OSGeo - Open Source Geospatial Foundation

==What is your Organization's Homepage?==
http://www.osgeo.org/

==Describe your organization.==
OSGeo is an incorporated not-for-profit organization serving as an umbrella organization for the Open Source Geospatial community in general, and 14 projects in particular.

==Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating?==
We hope to get more students involved in open source geospatial development to grow the development community, and to advance particular projects. Additionally we hope to spread the word of open source GIS in the universities.

==Did your organization participate in previous GSoC years? If so, please summarize your involvement and the successes and failures of your student projects. (optional)==

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report.

OSGeo was formed in early 2006 and hadn't participated in GSoC before 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators are involved in this years OSGeo GSoC effort.

==If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)? (optional)==

==What license does your project use?==
Different projects operate under a variety of OSI approved licenses, mainly GPL, LGPL, and MIT/X.

==URL for your ideas page==
http://wiki.osgeo.org/wiki/Google_Summer_of_Code

==What is the main development mailing list for your organization?==

OSGeo Wide - discuss@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/discuss details])

OSGeo SoC Mentors and Students - soc@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/soc details])

'''Project lists'''

* GeoServer - geoserver-devel@lists.sourceforge.net ( [http://lists.sourceforge.net/lists/listinfo/geoserver-devel details] )
* GeoTools - geotools-devel@lists.sourceforge.net ( [http://lists.sourceforge.net/lists/listinfo/geotools-devel details] )
* uDig - udig-devel@lists.refractions.net ( [http://lists.refractions.net/mailman/listinfo/udig-devel details] )
* MapGuide - mapguide-internals@lists.osgeo.org ( [http://lists.osgeo.org/mailman/listinfo/mapguide-internals details] )
* OpenJUMP - jump-pilot-devel@lists.sourceforge.net ( [http://lists.sourceforge.net/lists/listinfo/jump-pilot-devel details] )
* MapServer - mapserver-dev@lists.umn.edu ( [http://mapserver.gis.umn.edu/community/mailinglists/mapserver-dev/ details] )
* GDAL - gdal-dev@lists.maptools.org ( [http://lists.maptools.org/
* PostGIS - postgis-users@postgis.refractions.net ( [http://postgis.refractions.net/mailman/listinfo/postgis-users details] )
* GRASS - grass-dev@grass.itc.it ( [http://grass.itc.it/mailman/listinfo/grass-dev details] )
* Mapbender - mapbender_dev@lists.osgeo.org ( [http://lists.osgeo.org/mailman/listinfo/mapbender_dev details] )

==Where is the main IRC channel for your organization?==
irc://irc.freenode.net/#osgeo

'''Project irc channels:'''
* irc://irc.freenode.net/#geoserver
* irc://irc.freenode.net/#geotools
* irc://irc.freenode.net/#udig
* irc://irc.freenode.net/#mapbuilder
* irc://irc.freenode.net/#mapguide
* irc://irc.freenode.net/#mapserver
* irc://irc.freenode.net/#openlayers
* irc://irc.freenode.net/#gdal
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#grass
* irc://irc.freenode.net/#mapbender

==Does your organization have an application template you would like to see students use? If so, please provide it now. (optional)==

==Who will be your backup organization administrator? Please enter their Google Account address. We will email them to confirm, your organization will not become active until they respond. (optional)==
Frank Warmerdam (2007 administrator) - fwarmerdam at gmail.com

==About Your Mentors==
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
Mentors are selected by project steering comittees based on their reputation as skilled developers, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process.

===Who will your mentors be? Please enter their Google Account address separated by commas. If your organization is accepted we will email each mentor to invite them to take part. (optional)===
* fwarmerdam []gmail.com (Frank Warmerdam) - GDAL, MapServer
* wolf[]bergenheim.net (Wolf Bergenheim) - GRASS
* crschmidt []gmail.com (Christopher Schmidt) - OpenLayers
* euzuro []gmail.com (Erik Uzureau) - OpenLayers
* tim.schaub []gmail.com (Tim Schaub) - OpenLayers
* eric.c2c []gmail.com (Eric Lemoine) - OpenLayers
* bluecarto []gmail.com (Pierre Giraud) - OpenLayers
* shemange []gmail.com (Gary Sherman) - QGIS
* ottens []gmail.com (Steven Ottens) - Mapbuilder, OpenLayers
* dmorissette []gmail.com (Daniel Morissette) - MapServer, GDAL
* hobu.inc []gmail.com (Howard Butler) - MapServer, GDAL
* thomas.bonfort []gmail.com (Thomas Bonfort) - MapServer
* mloskot [] gmail.com (Mateusz Loskot) - GDAL
* assefay []gmail.com (Yewondwossen Assefa) - MapServer
* woodbri []swoodbridge.com (Stephen Woodbridge) - MapServer
* astrid_emde []osgeo.org - Mapbender
* marko.samson []gmail.com - Mapbender
* christoph.baudson []wheregroup.com - Mapbender
* uli []osgeo.org - Mapbender
* arkepp []gmail.com (Arne Kepp)- GeoServer / GeoTools / GeoWebcache
* andrea.aime []gmail.com (Andrea Aime) - GeoServer / GeoTools
* cdwindslow []gmail.com - (David Winslow) GeoServer / GeoTools
* sbenthall []gmail.com - (Seb Benthall) OpenLayers
* jody.garnett []gmail.com - (Jody Garnett) GeoTools

==About The Program==
===What is your plan for dealing with disappearing students?===
'''Plan A:'''

In order to minimize the likelyhood of disappearing students we will ensure that the OSGeo administrative contact and the mentor have full contact information (email, home phone, etc) so that we can keep in touch with them.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require weekly progress reports, participation on public IRC channels and mailing lists will all help ensure ongoing commitment to the work.

'''Plan B:'''

Leveraging Open Source software from the OSGeo stack, coupled with high-accuracy data sources, volunteers from the open source community will process the data, including student metadata, and the results will be used for the targeting instructions for high-powered space-based lasers. Results of this will be displayed on a large video wall, which will prove that the student really has disappeared, and should act as a deterrent to future student disappearances.

http://www.jasonbirch.com/files/space_lasers.jpg
([http://ossim.telascience.org/ossimdata/nhv/DSCF0129.JPG resized from] )

===What is your plan for dealing with disappearing mentors?===
Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period.

===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
The steps taken depend on the individual projects, as example last year GeoTools project has asked for weekly attendence at IRC meetings or status email.

Further more the mentors are encouraged to actively involve the students in the community, but having the student interact with the mentor throught the community channels rather then directly.

Other possibilities include:
# Having potential students work with their potential mentor to prepare a brief plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the appropriate OSGeo or project-specific mailing list when they have reached a milestone, giving a brief description of the work completed to that date.
# Selecting students that have shown interest previously in the geospatial field.

===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===
The steps taken depend on the individual projects, as example last year GeoTools project asked that students act as a "module maintainer" for their work. This role has an expected level of support associated with it.

Apart from that, we are relying on the open development process and the appreciation that students will receive for implementing these needed features to provide positive feedback for the students. The projects will be encouraging the students to take ownership of their work, and to contribute in other areas they may be interested in. In some cases students may also have opportunities for future contract work if they make a good impression on community members.

2008 Google SoC Application

2008-03-11T18:05:23Z

Wiki-Cholmes: /* Who will your mentors be? Please enter their Google Account address separated by commas. If your organization is accepted we will email each mentor to invite them to take part. (optional) */

==What is your Organization's Name?==
OSGeo - Open Source Geospatial Foundation

==What is your Organization's Homepage?==
http://www.osgeo.org/

==Describe your organization.==
OSGeo is an incorporated not-for-profit organization serving as an umbrella organization for the Open Source Geospatial community in general, and 14 projects in particular.

==Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating?==
We hope to get more students involved in open source geospatial development to grow the development community, and to advance particular projects. Additionally we hope to spread the word of open source GIS in the universities.

==Did your organization participate in previous GSoC years? If so, please summarize your involvement and the successes and failures of your student projects. (optional)==

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report.

OSGeo was formed in early 2006 and hadn't participated in GSoC before 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators are involved in this years OSGeo GSoC effort.

==If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)? (optional)==

==What license does your project use?==
Different projects operate under a variety of OSI approved licenses, mainly GPL, LGPL, and MIT/X.

==URL for your ideas page==
http://wiki.osgeo.org/wiki/Google_Summer_of_Code

==What is the main development mailing list for your organization?==

OSGeo Wide - discuss@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/discuss details])

OSGeo SoC Mentors and Students - soc@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/soc details])

'''Project lists'''

* GeoServer - geoserver-devel@lists.sourceforge.net ( [http://lists.sourceforge.net/lists/listinfo/geoserver-devel details] )
* GeoTools - geotools-devel@lists.sourceforge.net ( [http://lists.sourceforge.net/lists/listinfo/geotools-devel details] )
* uDig - udig-devel@lists.refractions.net ( [http://lists.refractions.net/mailman/listinfo/udig-devel details] )
* MapGuide - mapguide-internals@lists.osgeo.org ( [http://lists.osgeo.org/mailman/listinfo/mapguide-internals details] )
* OpenJUMP - jump-pilot-devel@lists.sourceforge.net ( [http://lists.sourceforge.net/lists/listinfo/jump-pilot-devel details] )
* MapServer - mapserver-dev@lists.umn.edu ( [http://mapserver.gis.umn.edu/community/mailinglists/mapserver-dev/ details] )
* GDAL - gdal-dev@lists.maptools.org ( [http://lists.maptools.org/
* PostGIS - postgis-users@postgis.refractions.net ( [http://postgis.refractions.net/mailman/listinfo/postgis-users details] )
* GRASS - grass-dev@grass.itc.it ( [http://grass.itc.it/mailman/listinfo/grass-dev details] )
* Mapbender - mapbender_dev@lists.osgeo.org ( [http://lists.osgeo.org/mailman/listinfo/mapbender_dev details] )

==Where is the main IRC channel for your organization?==
irc://irc.freenode.net/#osgeo

'''Project irc channels:'''
* irc://irc.freenode.net/#geoserver
* irc://irc.freenode.net/#geotools
* irc://irc.freenode.net/#udig
* irc://irc.freenode.net/#mapbuilder
* irc://irc.freenode.net/#mapguide
* irc://irc.freenode.net/#mapserver
* irc://irc.freenode.net/#openlayers
* irc://irc.freenode.net/#gdal
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#grass
* irc://irc.freenode.net/#mapbender

==Does your organization have an application template you would like to see students use? If so, please provide it now. (optional)==

==Who will be your backup organization administrator? Please enter their Google Account address. We will email them to confirm, your organization will not become active until they respond. (optional)==
Frank Warmerdam (2007 administrator) - fwarmerdam at gmail.com

==About Your Mentors==
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
Mentors are selected by project steering comittees based on their reputation as skilled developers, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process.

===Who will your mentors be? Please enter their Google Account address separated by commas. If your organization is accepted we will email each mentor to invite them to take part. (optional)===
* fwarmerdam []gmail.com (Frank Warmerdam) - GDAL, MapServer
* wolf[]bergenheim.net (Wolf Bergenheim) - GRASS
* crschmidt []gmail.com (Christopher Schmidt) - OpenLayers
* euzuro []gmail.com (Erik Uzureau) - OpenLayers
* tim.schaub []gmail.com (Tim Schaub) - OpenLayers
* eric.c2c []gmail.com (Eric Lemoine) - OpenLayers
* bluecarto []gmail.com (Pierre Giraud) - OpenLayers
* shemange []gmail.com (Gary Sherman) - QGIS
* ottens []gmail.com (Steven Ottens) - Mapbuilder, OpenLayers
* dmorissette []gmail.com (Daniel Morissette) - MapServer, GDAL
* hobu.inc []gmail.com (Howard Butler) - MapServer, GDAL
* thomas.bonfort []gmail.com (Thomas Bonfort) - MapServer
* mloskot [] gmail.com (Mateusz Loskot) - GDAL
* assefay []gmail.com (Yewondwossen Assefa) - MapServer
* woodbri []swoodbridge.com (Stephen Woodbridge) - MapServer
* astrid_emde []osgeo.org - Mapbender
* marko.samson []gmail.com - Mapbender
* christoph.baudson []wheregroup.com - Mapbender
* uli []osgeo.org - Mapbender
* arkepp []gmail.com (Arne Kepp)- GeoServer / GeoTools / GeoWebcache
* andrea.aime []gmail.com (Andrea Aime) - GeoServer / GeoTools
* cdwindslow []gmail.com - (David Winslow) GeoServer / GeoTools
* sbenthall []gmail.com - (Seb Benthall) OpenLayers

==About The Program==
===What is your plan for dealing with disappearing students?===
'''Plan A:'''

In order to minimize the likelyhood of disappearing students we will ensure that the OSGeo administrative contact and the mentor have full contact information (email, home phone, etc) so that we can keep in touch with them.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require weekly progress reports, participation on public IRC channels and mailing lists will all help ensure ongoing commitment to the work.

'''Plan B:'''

Leveraging Open Source software from the OSGeo stack, coupled with high-accuracy data sources, volunteers from the open source community will process the data, including student metadata, and the results will be used for the targeting instructions for high-powered space-based lasers. Results of this will be displayed on a large video wall, which will prove that the student really has disappeared, and should act as a deterrent to future student disappearances.

http://www.jasonbirch.com/files/space_lasers.jpg
([http://ossim.telascience.org/ossimdata/nhv/DSCF0129.JPG resized from] )

===What is your plan for dealing with disappearing mentors?===
Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period.

===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
The steps taken depend on the individual projects, as example last year GeoTools project has asked for weekly attendence at IRC meetings or status email.

Further more the mentors are encouraged to actively involve the students in the community, but having the student interact with the mentor throught the community channels rather then directly.

Other possibilities include:
# Having potential students work with their potential mentor to prepare a brief plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the appropriate OSGeo or project-specific mailing list when they have reached a milestone, giving a brief description of the work completed to that date.
# Selecting students that have shown interest previously in the geospatial field.

===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===
The steps taken depend on the individual projects, as example last year GeoTools project asked that students act as a "module maintainer" for their work. This role has an expected level of support associated with it.

Apart from that, we are relying on the open development process and the appreciation that students will receive for implementing these needed features to provide positive feedback for the students. The projects will be encouraging the students to take ownership of their work, and to contribute in other areas they may be interested in. In some cases students may also have opportunities for future contract work if they make a good impression on community members.

Google Summer of Code 2008 Administrative

2008-03-07T20:10:47Z

Wiki-Cholmes:

Central page for administering OSGeo participation in Google Summer of Code 2008.

= Background =

* Wolf Bergenheim will act as Administrative contact, with support from Frank Warmerdam.
* Google documentation on the program is at: http://code.google.com/support/bin/topic.py?topic=10442
* There is also a Google Wiki page about the program: http://code.google.com/p/google-summer-of-code/wiki/WikiStart
* Last years GSoC submission: http://code.google.com/soc/2007/osgeo/about.html
* Last years GSoC page: [[Google Summer of Code 2007]]
* Mentoring HOWTO: http://primates.ximian.com/~federico/docs/summer-of-code-mentoring-howto/index.html
* Advice for Mentors from the Google Wiki: http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors

= Timeline =

* March 3rd: Project applications will be accepted
* March 24th: Student applications

= Project Ideas Lists =

Please link project specific proposed projects here:

* [[Chisimba SoC Ideas]]
* [http://trac.osgeo.org/gdal/wiki/SummerOfCode GDAL SoC Ideas]
* [http://grass.gdf-hannover.de/wiki/GRASS_SoC_Ideas GRASS SoC Ideas]
* [http://www.mapbender.org/GSoC_2008 Mapbender SoC ideas 2008]
* [http://trac.openlayers.org/wiki/SummerOfCode OpenLayers SoC Ideas]
* [http://wiki.qgis.org/qgiswiki/SummerOfCodeIdeas Quantum GIS SoC Ideas]
* [[MapServer 2008 SOC Ideas]]
* [http://geosoa.scg.ulaval.ca/en/index.php?module=pagemaster&PAGE_user_op=view_page&PAGE_id=16 Laval University/CamptoCamp 2008 SoC ideas]
* [http://geoserver.org/display/GEOS/Summer+of+Code+2008 GeoServer SoC 2008]

'''these need updating!'''

* [http://docs.codehaus.org/display/GEOSDEV/GeoServer+Summer+of+Code+Ideas GeoServer SoC Ideas]
* [http://docs.codehaus.org/display/GEOTOOLS/Google+Summer+of+Code GeoTools Soc Ideas]
* [http://trac.osgeo.org/mapguide/wiki/GoogleSoC2007 MapGuide Soc Ideas]
* [[PostGIS SoC Ideas 2007|PostGIS SoC Ideas]]
* [http://udig.refractions.net/confluence/display/HACK/Summer+of+Code+2007 User-friendly Desktop Internet GIS SoC Ideas]
* [[OpenJUMP 2007 SOC Ideas]]

The "Student Landing Page" is [[2008 SoC Merged Ideas]].

= Documents =

'''These pages also need updating!'''

* OSGeo [[2007 Google SoC Application]]
* [[SoC Application Rankings by Project]]

= Project Milestones =
[[2008 Google SoC Project Milestones]]

= Project Pages =
Each accepted Soc Project should be listed here, and the page should be updated with information about the progress of the project.

Board Meeting 2008 01 11

2008-01-03T15:49:28Z

Wiki-Cholmes:

This board meeting has been scheduled for the 11th of January at 16:00 UTC ([http://www.timeanddate.com/worldclock/fixedtime.html?month=1&day=11&year=2008&hour=16&min=0&sec=0 fixedtime]), by phone and IRC ([irc://irc.freenode.net/#osgeo #osgeo]) at the same time.

Communication will use the new [[Conference Call]] facilities.

== Agenda ==

* Appoint meeting secretary
* Review and approve [[Thirty First Board Meeting]] minutes.
* Review [[SPD Prioritization]] proposal for highlighting sponsors and contributors (FrankW/ArnulfC to prepare).
* Review who needs to be an officer of the foundation ([http://www.osgeo.org/content/foundation/incorporation/bylaws.html bylaws - see ARTICLE V Officers])
* FOSS4G 2008 contracting and budget status review.
* Approve hosting the Fusion project on OSGeo infrastructure (already approved by SAC).
* Consider streamlining non-OSGeo project hosting procedure.
* Discuss feasibility of the quite speculative [[Data Project Incubation]] idea (JoW)
* Review and hopefully approve GeoTools/OSGeo contributors agreement, see [http://docs.codehaus.org/download/attachments/9765352/010-GtCopyright-HJM_version_FINAL.odt draft] and [http://docs.codehaus.org/display/GEOTOOLS/Geotools+Legal+Review info page] (cholmes)

[[Category: Board]]

Board Meeting FOSS4G2007

2007-09-23T14:41:09Z

Wiki-Cholmes:

The OSGeo Board of Directors will meet in a face-to-face meeting prior to the [[FOSS4G2007]] conference event. Space is limited to accomodate the board only. General OSGeo meeting / discussion will be possible during [[AGM_2007|Annual General Meeting]] the following day.

= Venue =
* '''When''': Sunday, September 23rd, 9am - 5pm
* '''Where''': Harbour Towers Meeting Room - 203
* Breakfast, lunch and morning/afternoon foods and beverages will be provided

= Agenda =

These are suggested items and not a final agenda.

* Review and Update of OSGeo Priorities
* Budget Preparation for 2008
* Financial management / treasurer discussion ('''Ken Tamura available for call in, scheduled for 11am''')
* Review of sponsorship programme - who the sponsors are, who could be approached, what seem to be their expectations of value in return
* 2008 Conference program, local conferences
* Possibility of and conditions around support fund for OSGeo members to get to conferences
* Whether and how well the current committee structure is working to coordinate Foundation activities
* Report from ED and overview of following year position
* Sustainable Funding
** Review of Current Model
** Discuss Conference Driven Model
** Discuss Certification Driven Model
* Revisit and better define membership roles
* Francophone Local Chapter to present [[OSGeo_proposal_for_Francophone_Local_Chapter | their proposal]] to form officially ('''Vincent Picavet & Yves Jacolin scheduled to come at 4pm''')
* Legal situation with GeoTools in particular, access to legal support generally.
'''Please contribute.'''

= Who =
Who is planning to attend...
* [[User:tmitchell|Tyler Mitchell]]
* [[User:Davemac|Dave McIlhagga]]
* [[User:Warmerda| Frank Warmerdam]]
* [[User:pwramsey3|Paul Ramsey]]
** Subject to conference needs...
* [[User:Arnulf Christl|Arnulf Christl]]
* [[User:robertbray|Bob Bray]]
* [[User:JoWalsh|Jo Walsh]]
* [[User:ticheler| Jeroen Ticheler]]
* [[User:cholmes|Chris Holmes]]

Who is planning to virtually attend (given there is Voip possible)...
* [[User:Neteler|Markus Neteler]]
* ...

[[Category:FOSS4G2007]]
[[Category:Board]]

Board Meeting FOSS4G2007

2007-09-23T14:40:19Z

Wiki-Cholmes:

The OSGeo Board of Directors will meet in a face-to-face meeting prior to the [[FOSS4G2007]] conference event. Space is limited to accomodate the board only. General OSGeo meeting / discussion will be possible during [[AGM_2007|Annual General Meeting]] the following day.

= Venue =
* '''When''': Sunday, September 23rd, 9am - 5pm
* '''Where''': Harbour Towers Meeting Room - 203
* Breakfast, lunch and morning/afternoon foods and beverages will be provided

= Agenda =

These are suggested items and not a final agenda.

* Review and Update of OSGeo Priorities
* Budget Preparation for 2008
* Financial management / treasurer discussion ('''Ken Tamura available for call in, scheduled for 11am''')
* Review of sponsorship programme - who the sponsors are, who could be approached, what seem to be their expectations of value in return
* 2008 Conference program, local conferences
* Possibility of and conditions around support fund for OSGeo members to get to conferences
* Whether and how well the current committee structure is working to coordinate Foundation activities
* Report from ED and overview of following year position
* Sustainable Funding
** Review of Current Model
** Discuss Conference Driven Model
** Discuss Certification Driven Model
* Revisit and better define membership roles
* Francophone Local Chapter to present [[OSGeo_proposal_for_Francophone_Local_Chapter | their proposal]] to form officially ('''Vincent Picavet & Yves Jacolin scheduled to come at 4pm''')
* Legal situation with GeoTools in particular, access to legal support generally.
'''Please contribute.'''

= Who =
Who is planning to attend...
* [[User:tmitchell|Tyler Mitchell]]
* [[User:Davemac|Dave McIlhagga]]
* [[User:Warmerda| Frank Warmerdam]]
* [[User:pwramsey3|Paul Ramsey]]
** Subject to conference needs...
* [[User:Arnulf Christl|Arnulf Christl]]
* [[User:robertbray|Bob Bray]]
* [[User:JoWalsh|Jo Walsh]]
* [[User:ticheler| Jeroen Ticheler]]

Who is planning to virtually attend (given there is Voip possible)...
* [[User:Neteler|Markus Neteler]]
* ...

[[Category:FOSS4G2007]]
[[Category:Board]]

GSDI

2007-06-12T17:55:34Z

Wiki-Cholmes:

From the [http://gsdi.org/ GSDI] Website:
: ''The [http://gsdi.org/ Global Spatial Data Infrastructure Association] is an inclusive organization of organizations, agencies, firms, and individuals from around the world. The purpose of the organization is to promote international cooperation and collaboration in support of local, national and international spatial data infrastructure developments that will allow nations to better address social, economic, and environmental issues of pressing importance.''

== GSDI 10 Conference ==
The GSDI Association organizes the [http://gsdi.org/gsdi10/ International Conference for Spatial Data Infrastructure 2007]. OSGeo will submit [http://gsdi.org/gsdi10/workshops.html proposals for Workshop] sessions to demonstrate the FOSS SDI stack. Please help to put together a comprehensive proramm, submission deadline is June 1st.

There is interest from several projects:
* [[GeoNetwork]] opensource
* [[GeoServer]]
* [[Mapbender]]
* gvSIG (will request OSGeo entry soon)
* ''please add more only if you can contribute''

OSGeo can highlight the whole software stack and present how it interoperates plus explain FOSS advantages beyond the obvious.

=== Workshop Proposal ===
This page contains content and contributors to the emerging GSDI Workshop.

; Contact and Confirmation
: Professor Harlan Onsrud, Interim Executive Director
: Global Spatial Data Infrastructure Association (GSDI)

1. Proposed Workshop Title
: '''Getting Started with Free and Open Source Software for SDIs'''

2. Organizer/Contact Person (name, title, address, country, phone, fax, e-mail)
: Open Source Geospatial Foundation
: [[User:Arnulf Christl | Arnulf Christl]] Board Member, (event owner)
:
: Siemensstr. 8
: 53111, Bonn
: Germany

3. Workshop Description and Goals (250 words or less suitable for posting on the web. Please include in the description if the session will involve lecture, hands-on exercises, group exercises, etc. and whether any take-home materials will be supplied and indicate whether participants should bring a laptop computer or anything else to the workshop.)

: The workshop will introduce some of the latest advances in open source tools for SDI development. The Open Source Geospatial Foundation (OSGeo) is a central resource for geospatial projects with open licenses and collaborative development models. This workshop will mostly center on gvSIG, GeoServer, MapBuilder and GeoNetwork Open Source. It will include a lecture and an introduction to installing, configuring, and using the tools for SDI, focusing on WMS, WFS WCS and Catalog 2.0 OGC standards. The workshop will walk through building the basics of a functioning open source SDI. Different Open Source GeoSpatial packages for SDI will also be discussed. The first half will be more structured, with discussion of what constitutes an 'OpenSDI', the advantages of a truly open SDI, and an introduction to the tools that can be used to build it today. The second half will consist of demonstrations of the software in action and case studies from around the world. The workshop will conclude with a question and answer session about real issues building SDI's on open source software. The presenters are experienced open source community members with a wealth of knowledge. A laptop is recommended, but not required. All software demonstrated will be available on a CD for participants to take home.

4. Workshop Topics in First Session (90 Minutes)
: This workshop gives an introduction to the 'OpenSDI' concept and the Open Source Geospatial Foundation. After that OSGeo SDI software projects will be discussed, including an overview of features, programming languages used, interfaces, standards and cross project activities. Demonstrations of the projects in action will also be shown. All projects have in common that they are licensed as Free and Open Source Software and are operated with an open governance model. The second part of the first session will focus on how to participate in the processes of these projects and how to find out which level of involvement gives best return on investment.

5. If needed, Workshop Topics in Second Session (90 Minutes)
: The second session will focus on putting the individual projects in to an SDI setting, showing how they work together to publish, find and bind diverse geospatial information in a working Spatial Data Infrastructure. In addition to showing the projects in action we will also discuss several case studies from around the world where the shift to open source software has not only been cost effective but has helped to build better SDI's than commercial vendors.

6. Tentative Workshop Instructors/Speakers (list name, title, affiliation - these do not have to be confirmed at this time)
* [[User:Arnulf Christl | Arnulf Christl]], OSGeo, [[Mapbender]], WhereGroup
* Christ Holmes, The Open Planning Project, [[GeoServer]]
* Jeroen Ticheler, FAO, [[GeoNetwork]] opensource
* Salvador Bayarri, IVER, gvSIG Project

7. Intended Audience (technicians, managers, policymakers, introductory, advanced, etc.) and any required skills or interests they should possess
* Policymakers
* Managers
* Technicians
* Introductory

8. Indicate Preferred Room and Size: e.g. prefer computer lab with 40 person capacity, prefer classroom style with tables and 80 person capacity
* Prefer classroom style, as large as possible.

=== Letter from the Organizers ===
Workshops this time will be offered under a slightly different
arrangement that we hope will attract strong attendance. We are
requesting workshop proposals by the end of this month so that people
registering for the conference will be able to sign up for specific
workshops in advance. In this manner instructors will know the number of
people attending their workshops and have the contact information for
their participants in advance.

We highly encourage you to submit a workshop proposal. For reference,
the description of the workshop you presented in Santiago in 2006 may be
found at http://www.gsdi.org/gsdiconf/gsdi9/english/09_Act_Work_Sched.htm.
Submit your proposal on or before 1 June 2007 to onsrud@gsdi.org with a
copy to astevens@gsdi.org. If you submit, you should have a decision by
the evaluation committee in early June.

[[Category:Events]]

GeoTools Contribution Steps

2007-05-16T18:28:25Z

Wiki-Cholmes:

The GeoTools project has had some push back on contributor agreements, looking for a bit more from the board. They have proposed this plan:

Review the Fiduciary Agreement proposed by the Geotools project and plan steps to obtain a final draft:
** Core geotools contributors want to make OSGeo the legal guardian of the code base by granting OSGeo a full copyright over our submissions. As part of this process, OSGeo and geotools need to agree on a legal document transferring copyright from individual geotools contributors to OSGeo. The agenda item requires the Board review the latest draft document and plan the steps required to obtain a final draft acceptable to the OSGeo board.
** The proposed draft is presented at the bottom of the [http://docs.codehaus.org/display/GEOTOOLS/Incubation+for+acceptance+to+OSGeo this page] on the Geotools web site.
** The draft is inspired mostly from the Free Software Foundation, Europe's FLA.
** The draft does not consider patents and hence does not force contributors to assert that they are not knowingly including patented code. Frank felt that such language did not belong in a Copyright assignment. The omission makes the document more precise for copyright assignment but lessens its utility as a guarantor of the suitability for use of the code by the future licensees of OSGeo.
** The paragraph in section IV stipulating that OSGeo commit to keep the code "free" has been left to the Board to write. Previous discussion mentioned this guarantee might be provided by reference to the OSGeo charter. We hope that the language could stipulate that any change in license would be undertaken according to the wishes of the active Project management committee.
** This version does not contain the request for legal support from contributors in the event of a dispute which was present in the original OSGeo draft. It could if this were felt by the board to be important.
** Someone will have to sign on behalf of OSGeo.
** Questions should be addressed to the geotools developer's list <nowiki>geotools-devel@lists.sourceforge.net</nowiki>
** Thanks and sorry to expose everyone to yet even more legalese.

Board Meeting 2007 05 18

2007-05-16T18:27:42Z

Wiki-Cholmes:

'''Not actually scheduled yet!'''

This board meeting has been tentatively scheduled for the 18th of May at 16:00 UTC ([http://www.timeanddate.com/worldclock/fixedtime.html?month=5&day=18&year=2007&hour=16&min=0&sec=0 fixedtime]), by phone and IRC ([irc://irc.freenode.net/#osgeo #osgeo]) at the same time.

Communication will use the new [[Conference Call]] facilities.

== Agenda ==

* Appoint meeting secretary
* Review and approve [[Twenty Sixth Board Meeting]] minutes
* Discuss timing of a FOSS4G OSGeo face-to-face meeting, if we want one.
* Approve Arnulf as new VisCom Chair.
* Review Financial Report.
* [[GeoTools Contribution Steps]]
* Revise [http://wiki.osgeo.org/index.php?title=OSGeo_FAQ&diff=13249&oldid=5281 the FAQ about proprietary software]. -- Jo
* Revisit [[What's Working]] and [[What's Not Working]] -- Arnulf
* Revisit [[Board tasks]] and consider to eiter drop this page altogether (and do ti via Tarc?) or appoint page maintainer -- Arnulf

SoC Application Rankings by Project 2007

2007-03-30T19:57:25Z

Wiki-Cholmes:

This page segregates SoC applications by project, so that projects can rate their applications in priority order.

= GDAL =

# [http://code.google.com/soc/osgeo/app.html?csaid=KBsNH0VHUiINNx0kFAZQWi1LOxwJSVMBUiJUaRJQSQoDUnRVbRJX%0A A Synthetic Aperture RADAR Processor using GDAL] - Philippe Vachon
# [http://code.google.com/soc/osgeo/app.html?csaid=Mx8LGApfcyYIORoIXQheXntSaEZdRg1UB3sEYRJVSlMEVQ%3D%3D%0A GDAL Raster Driver for PNG/JPG Tile Structure + gdal2tiles utility] - Petr Prindal
# [http://code.google.com/soc/osgeo/app.html?csaid=Ml0LEQJxRzMKMhJKHQ5FCXYEbxBSEg4ECSBSOUMBQAlV%0A GDAL: KML read support for the existing driver] - Jens Oberender
# [http://code.google.com/soc/osgeo/app.html?csaid=NhwTEgBxSzEENV0AFlEJVSQHa0JVSlFVVyBVYUYBQg%3D%3D%0A OGC WMS GDAL driver] - Adam Nowacki
# [http://code.google.com/soc/osgeo/app.html?csaid=Ml0LEQJxRzMKMhJKHQ5FCXYEahZdQQkACXkDbRdRRAgC%0A GDAL: Driver for GeoRSS] - Jens Oberender

= GRASS =

# [http://code.google.com/soc/osgeo/app.html?csaid=OgYKFwpdUgECNRINH0VSXCxfYBcCQw9UBCdfPhdUFlJTUXI%3D%0A GRASS Modules for line generalization and smoothing] - Daniel Bundala
# [http://code.google.com/soc/osgeo/app.html?csaid=OgYKFwpdUgECNRINH0VSXCxfYBUHRVoEVnVfYRJdQw0GUiI%3D%0A GRASS Global Least Cost Path Module] - Daniel Bundala
# [http://code.google.com/soc/osgeo/app.html?csaid=OhwGERJBXDYAKgAkFAZQWi1LOxwJSVMBUCBQbUQASQ9UBCIEYRcH%0A A new simulation/optimization algorithm for least cost path] - Bobby Powers
# [http://code.google.com/soc/osgeo/app.html?csaid=NhoPHAdYUCwMNBYKEitWXiAMNF0HHAYLCycAOhBSQV0LBCJTYBJUFl8%3D%0A Line generalization module for GRASS] - Milena Nikolic
# [http://code.google.com/soc/osgeo/app.html?csaid=NR4FHw9QUCoAKjMDHgpYX28GNx5eRF4DUHFTO0NeEQ1XBCIDPhE%3D%0A Shortest path in free (vector) space avoiding obstacles module in GRASS] - Maximilian Maldacker

= Java =

Mentors avaialble from GeoTools, GeoServer and uDIg communities.
{| border=1
! Proposal
! Student
! GeoTools
! GeoServer
! uDig
|-
| [http://code.google.com/soc/osgeo/app.html?csaid=MF0OFhFUWAEGPR0QAR5cHSIfYksCEl0HCnQEYhcCQVtQUCJV%0A UDig Sensor Observation Service Client]
| Jan Jezek
| x
| -
| X
|-
| [http://code.google.com/soc/osgeo/app.html?csaid=NBoIGhlEWnNTGBQJEgJdHSIKNUlcRl8GUHQEOklSQQlTViIDOg%3D%3D%0A Implementation of An Interactive GeoRSS tool in uDig]
| Rui Li
| X
| -
| X
|-
| [http://code.google.com/soc/osgeo/app.html?csaid=OxsWGhhFXDENPV0WHB5CQC4LGBQJEgJdHSIKNUlcEg8HAHBRO0kFRVgJBiQHaA%3D%3D%0A Caching data in uDig]
| Christophe ROUSSON
| X
| x
| x
|-
| [http://code.google.com/soc/osgeo/app.html?csaid=OxsWGhgfRCkMLB0BCitWXiAMNF0HHAYLCnFTaRcGRw4LVnRRYRYAFwo%3D%0A JTileCache]
| Christopher Whitney
| x
| X
| -
|-
| [http://code.google.com/soc/osgeo/app.html?csaid=PBIKCkV2Vi4xNxwIACtWXiAMNF0HHAYLCyRSaUQFR1oLC3ZSYUZdElI%3D%0A Plugins for multidimensional raster data sources]
| Daniele Romagnoli
| X
| x
| x
|-
| [http://code.google.com/soc/osgeo/app.html?csaid=MF0OFhFUWAEGPR0QAR5cHSIfYksCEQgJAXkGYkcHRF5VCndd%0A New Transformation Algorithms for GeoTools and uDig]
| Jan Jezek
| X
| x
| x
|-
| [http://code.google.com/soc/osgeo/app.html?csaid=MF0OFhFUWAEGPR0QAR5cHSIfYksCEQgJAXkGYkcHRF5VCndd%0 GeoServer Style Editor]
| Anthony Manfredi
| x
| X
| x
|-
}

= PostGIS =

# [http://code.google.com/soc/osgeo/app.html?csaid=KxwIHEVdWi8lPx4FGgcfUC4IYkQGElhSBXAHYkNWF1JVCnYE%0A Coverage model and operations for PostGIS] - Xing Lin
# [http://code.google.com/soc/osgeo/app.html?csaid=IRYHEhlDWi0JNzMDHgpYX28GNx5eRl1QUHZQbxVeElwIBnFSOxc%3D%0A Materialized Views with Geometric Support] - Eduin Yezid Carrillo Vega

Protocol for requesting letter of support

2007-01-09T21:39:17Z

Wiki-Cholmes:

'''Draft guidelines regarding requests for OSGeo support of a proposed project'''

This document proposes a set of guidelines than can be used by the OSGeo community to request explicit support, in the form of a letter of support, for a proposed activity. This represents some initial ideas to be used as a starting point with the expectation that changes will be made. The intent is to have a standard set of guidelines that are easy to implement.

Given the likelihood that multiple members of the OSGeo community will request support for a single solicitation a balance should be reached between providing sufficient information so an informed decision to support or not support the proposed work can be made and to maintain sufficient confidentiality so that a competitive edge can be maintained by the requestor.

All letters of support should be archived on the OSGeo web site for access by the OSGeo community.

The process involves 4 steps: submission, comment, decision, and notification.
# To start the process, a request for support should be submitted to the OSGeo discuss mailing list. In the request sufficient information should be provided about the proposal’s goals and deliverables with explicit reference to why OSGeo support is being requested.
# During a period of 3 days (72 hours) the OSGeo community will have an opportunity to respond with comments indicating why OSGeo should or should not explicitly support the project. If more information is required that should be stated during this review period.
# After this 3-day review period the OSGeo board will discuss the request at their next scheduled meeting. If no meeting is scheduled by the time the letter of support is due then one should let the board know and they can vote over email or potentially meet sooner. One board member should be assigned the task of organizing the initial request and all replies concerning that request so this information can be distributed to board members in advance of the meeting. After discussing feedback received from the discuss mailing list the board will make one of the following decisions:
## Request additional information
## Approve the request
## Deny the request
# The requestor will be notified of the board’s decision within 24 hours of the start of the board meeting. If the request is approved the board will write the letter and deliver it. If additional information is requested the board will notify the requestor and the OSGeo community via the discuss mailing list and the review process begins again. If the request is denied a notice of denial will be sent to the requestor via-email. This notice will include the justification for denying the request.

'''Question:'''
Should it be mentioned that board members wishing to comment should do so via the discuss mailing list or is it okay for them to have the option of limiting their feedback to the board meeting?

OpenTechnologyConference Mar2007

2006-12-06T15:44:13Z

Wiki-Cholmes:

=Open Technology Development - Realizing the Vision=
Working title. We are currently working with the AFEI to organize a two day conference in Washington DC, 14, 15 March at the Hyatt. The 14th will be focused on the Open Technology Development effort within the federal government. The 15th will focus on open source geospatial capabilities and support for those technologies. The Open Source Geospatial Foundation will guide the planning and agenda for that day.

== 14 Mar - Open Technology and the Federal Government ==

=== Keynote Speakers ===

=== Panels ===

=== Presentations ===

== 15 Mar - Open Source Geospatial Software and the Government ==
The goal this day of the conference is to educate the attending government decision makers and contractors that open source geospatial technologies are mature and supportable. These technologies and open source practices would provide substantial benefits to government programs and projects. The collaborative technology development methodologies employed by open source geospatial projects can be accessed through collaboration with the Open Source Geospatial Foundation.

Potential speakers:
Tyler Mitchell
Gary Lang
Mark Lucas
Dave McIlhagga
Canadian Government Speaker (DM)
Large Data JCTD
Al Kelly - Ilabs
Jim Long - NGA
Chris Holmes

=== Keynote Speakers ===

=== Panels ===

=== Presentations ===

=== Marketing ===
This is an opportunity to communicate the benefits of OSGeo and Open Technologies to government agencies and contractors. Perhaps the key message is that these technologies are mature and supportable through existing organizations and companies.

====Why should you attend?====
Learn about the latest trends in bringing open technologies solutions into government systems and acquisitions. A special focus will demonstrate open source geospatial solutions and their supporting organizations and companies. Open source software and open systems have revolutionized how complex architectures are implemented. The collaboration, tools, and technologies used in open source systems provide agile technology paths that are critical in our ever changing environment. This conference will educate the participants on open technology initiatives and open source software solutions that are backed with commercial support.

====Who should attend?====
Decision makers, systems integrators and technologists from contractors and government that are interested in how to improve government solutions through the use of open architectures and open source software. The conference will focus on the efforts of the Open Technology Development Initiative within the Department of Defense with a special focus on advanced open source geospatial technologies from the Open Source Geospatial Foundation.

[[Category:Events]]

OSGeo at FOSS4G2006

2006-08-30T16:39:35Z

Wiki-Cholmes:

= General =
* FOSS4G 2006 - Open Source Geospatial Communities JOINT CONFERENCE - September 12-15 2006, Lausanne, Switzerland. This conference will unite the MapServer, GRASS, EOGEO, and other Open Source communities at an international venue.
* See http://www.foss4g2006.org/

== To Do ==
* What is to be done?
* Will OSGeo have booth space, or do we need to ask the organisers about it?
* Will we want to distrib brochures, flyers if so how to produce them.
* Do people who are attending not have t-shirts and how can they get them.
* Do we want a demo CD to hand out, during presentations if nothing else
* Demofest, to we want to clump togehter, or stange interoptability between products?
* Theme, do we want to have a point?

== OSGeo related talks and sessions ==

=== Workshops ===

* Several [http://www.foss4g2006.org/conferenceTimeTable.py?confId=1&showDate=all&showSession=all&detailLevel=contribution&viewMode=parallel workshops] are running

Presenter: Paul Spencer, DM Solutions Group,Robert Bray, Autodesk; Zak James, DM Solutions Group
Title of Presentation: MapGuide Open Source Users Workshop
Date/Time: Tuesday, 12 September, 09:00 – 12:30
Location: Amphipole (Pol 189)

Presenter: Robert Bray, Autodesk
Title of Presentation: Advanced MapGuide Open Source Development
Date/Time: Tuesday, 12 September, 14:00 – 17:30
Location: Amphipole (Pol 189)

Presenter: Arnulf Christl, CCGIS
Title of Presentation: Mapbender Workshop
Date/Time: Tuesday, 12 September, 14:00 – 18:15
Location: Amphipole (Pol 189)

=== BOFs ===
When and where?

* ''Binary Distribution Builders'' by FrankW (submitted)
* ''Public Geodata BOF'' by Jo (submitted)
* ''Towards a Web Map Tiling Standard'' by Schuyler
* ''Education committee BoF '' proposed by Ari (will happen Tuesday at 18.00, meet at GRASS workshop)
* ''GeoTools is 10 years old'', Birthday BOF
* ''ka-map/openLayers merging discussions'' by Lorenzo Becchi (will happen Wednesday, 18:00-20:00)(more [http://wiki.osgeo.org/index.php/AJAX_WebMapping_Project_Request#foss4g2006_conference])
* ''Perl BoF'' proposed by Ari (Thursday lunch?)
* ''Mobile GIS reloaded'' proposed by Silke Reimer, Tim Bowden and Mateusz Loskot

=== Keynotes ===

* Frank Warmerdam
* Gary Lang
Presenter: Gary Lang
Title of Presentation: Welcome & Opening Conference Plenary
Date/Time: Wednesday, 13 September, 10:45 – 11:30
Location: Amphimax
Abstract:. Welcome & Opening Conference Plenary

=== Talk Presentations ===

* Jo is doing a talk "Have a Nice Metadata" about the work the [[Geodata Committee]] has been doing on simplest-useful-thing metadata models and exchange interfaces
* Chris is doing 'Architecting Participation for GeoSpatial Data', touching on geodata committee topics
* Justin is doing a talk on 'GeoServer: a platform for open web services', which will certainly touch on some GeoTools topics.
* '''Please add your talk title / topic here - there must be dozens, right?'''

=== Breakout session ideas ===
* Geospatial Metadata Syndication - see [[Simple Catalog Interface]]
* Tiling WMS, some talk of GeoServer and uDig implementation of GetTile

== People planning to attend ==
The OSGeo booth will be a place where most OSGeo folks will go to at one time or another. Ideally we have full coverage of every project by a representative of that project at all times at the booth. To get things organized just a bit we need to have some people at the booth at all times. Please add yourself to the list, even if it is for one morning or evening only so that we can get an overview where it might be critical. Most traffic will be during the breaks and there will be lots of time to chat with others also hangin out at the booth during all those boring sessions going on. So please feel free to drop by.

For questions, contact Arnulf Christl (mailto:arnulf@osgeo.org) or Tina Mena, tina.mena@autodesk.com.

=== Staff Plan ===
{| border=1
! Day of week !! Monday!!Tuesday!!evening!!Wednesday!!evening!!Thursday!!evening!!Friday!!pack in
|-
! Date || 09.12 || 09.13 || || 09.14 || || 09.15 || || 09.16 ||
|-
! Time || 15:00-|| 7:30- ||-18:00 || 7:30- ||-18:00 || 7:30- || -18:00|| 7:30- || -16:00
|-
! Todo ||setup || booth ||booth ||booth || booth ||booth || booth || booth || pack in
|-
! Arnulf Christl (VisCom) || X || o || o || X || X || X || X || X || X
|-
! Steve Lime (MapServer) || || || || o || o || o || o || o ||
|-
! Jody Garnett (GeoTools) || || || || o || o || o || o || o ||
|-
! Jo Walsh (Geodata) || || || || || o || || o || ||
|-
! Puneet Kishor (Education) || || || o || || o || o || || o ||
|-
! Uli Rothstein (Mapbender) || || || || X || o || X || o || X || X
|-
! Astrid Emde (Mapbender, Edu) || || || || o || X || o || X || o ||
|-
! Michaela Schneeberger (MapGuideOS)|| || X || X || o || X || o || X || o ||
|-
! Frank Warmerdam (GDAL/OGR) || || || || o || o || o || o || o ||
|-
! Perry Nacionales (MapServer, other) || x || o || || o || || o || o || o ||
|-
! Chris Holmes (GeoTools) || || x || || o || || x || || ||
|-
! Brent Owens (GeoTools) || || || || || x || o || o || x ||
|-
! Justin Deoliveira (GeoTools) || || x || || o || x || || o || ||
|-
! Add your name (project) || || o || o || o || o || o || o || o ||
|-
! Responsible staff (X) || 1 || 1 || 1 || 2 || 3 || 2 || 3 || 2 || 2
|}
; Legend
:'''X''' = will be there all time
:'''x''' = will be there most of the time
:'''o''' = will be there during the breaks

[[Category:Events]]

WMS Tile Caching

2006-08-20T18:29:34Z

Wiki-Cholmes:

== Goal ==

The goal of a '''WMS Tile Caching''' proposal, perhaps ''WMS-C'' for short, is to find a way to optimize the delivery of map imagery across the Internet. The proposal needs to offer ideally some means by which map clients can fetch tiles from existing servers, in such a way that the images can be cached on the server, or at an intermediate location, or even be completely pre-generated, if desired. Further, the proposal needs to offer a way of advertising that a cached tile set is available for a given layer from a particular WMS or WMS proxy. The proposal should leverage the existing investment in OGC-compliant WMS servers on the 'Net.

The two main questions to be addressed are:
# How does a server advertise its cacheable image tiles?
# How does a client request possibly cached image tiles?

== Proposal ==

=== WMS-C as WMS Profile ===

One approach to take might be to define ''WMS-C'' (as in ''Web Mapping Service - Cached'') as a constrained profile of [http://www.opengeospatial.org/docs/01-068r2.pdf OGC WMS] that permits servers to optimize their image generation, and allows tiles to be cached at intermediate points. A WMS-C service would likely only deliver images for bounding boxes aligned to a given rectangular origin and grid, and only at particular scale levels.

The basic idea is that, unlike with WMS, two different requests for a given WMS-C tile should form the exact same HTTP GET request. This invites several constraints on WMS ''GetMap'' requests:

# Minimal query string arguments (i.e. no optional arguments permitted, versus §7.2)
# Fixed query string argument ordering and case (versus §6.4.1; q.v. also §7.2.2, Table 8)
# Fixed range of possible bounding boxes, computed from the WMS-C profile parameters
# Fixed precision on bounding box values (clarifying §6.5.6)
# Fixed tile size in pixels
# Fixed layer name and/or layer name ordering
# Fixed styling
# Fixed output format

Some means of identifying these constraints programmatically on a per-server basis, a la ''GetCapabilities'' might be desirable. From the table below, it appears that minimum/maximum scale (and scale quantization factor, which should probably never be other than 2) are the only suggested tiling regime parameters that would be difficult to directly express in a WMS GetCapabilities document. Is there some existing way to add custom parameters to a GetCapabilities declaration?

Note that the ''LAYERS'', ''STYLES'', ''SRS'', ''HEIGHT'', ''WIDTH'', and ''FORMAT'' arguments to a ''GetMap'' request would become fixed for a particular WMS-C tiled layer, but the WMS specification would still require the inclusion of these arguments in every WMS-C request (§ 7.2).

A WMS-C proxy or server should be free to return an exception or a redirect, if it receives a WMS request that is not WMS-C compliant, or involves a bounding box that does not correspond to a single tile in the cache.

=== Calculating Valid Tile Extents for a Given Request ===

WMS tile caching implies fixed scale or zoom levels. Typically, each valid scale level would be half that of the next larger scale. It would be worth writing reference code to help developers figure out which tiles they need to load to cover a given bounding box at a given scale.

=== Possible Tile Scheme Parameters ===

{| cellpadding="5" cellspacing="1" border="1"
| '''Parameter''' || '''Default value''' || '''Specifiable in WMS GetCapabilities?'''
|-
| "This service suppports tiling." || ''none'' || ''<KeywordList>'' contains the string 'tiled', perhaps? (§7.1.4.5.3)
|-
| Projection || EPSG:4326 || ''<SRS>''
|-
| Maximal extent || (-180,-90,180,90) || ''<BoundingBox>'' (§7.1.4.5.7)
|-
| Number of horizontal and vertical tiles at the maximal extent || ''none'' || Could be implied by ''<ScaleHint>'' (§7.1.4.5.8, but note that the format is weakly specified)... Alternately, could use ''<DataURL>'' (§7.1.4.5.14)
|-
| Tile size in pixels || some power of 2 || <Layer> attribute ''fixedWidth'', ''fixedHeight'' (§7.1.4.6)
|-
| Minimum scale || ''none'' || ''<ScaleHint>'' or ''<DataURL>'' (see note, above)
|-
| Scale quantization factor || 2 || ''<DataURL>''
|}

----

== Other Considerations ==

* Would non-rectangular tessellations yield more efficient results? If so, which tessellations to consider? Also, are the processing and bandwidth advantages of a non-rectangular tessellation outweighed by the potential implementation complexity?
* Norm Vine rightly points out that a tile request basically boils (or should boil down to) Layer + Zoom Level + Row + Column. Can we define an even simpler method for requesting tiles from servers in the know? How are those capabilities advertised, if not shoehorned into WMS? Note that WorldWind basically already has a mechanism for this. Their tiling requests basically look like:

http://domain.tld/service?L=0&X=1&Y=2
* Like all caching schemes, WMS-C caches would need to be cognizant of expiration. Easy with using the proper HTTP headers. There is a wide range of freshness/staleness, with OpenStreetMap being highly volatile, and Landsat being pretty stable (until the ice caps melt ;).
* Several people (particularly Paul Spencer and Chris Schmidt) have argued that a separate ''GetTile'' request should be used. This topic probably warrants discussion.

== Distributed Caching ==

* A WMS-C standard would permit tile caching through [http://www.coralcdn.org/ Coral]. However, the World Wind community's experience has been that using Coral to serve tiles results in frustratingly high latency.
* Alternately, one could do (distributed) [[Distributed Tile Caching|peer-to-peer tile caching]] optimized specifically for geographic space, which might still suffer the latency issues associated with P2P networks.

== Existing Tiling Schemes ==

* Mikel Maron's description of [http://lists.eogeo.org/pipermail/tiling/2006-March/000017.html OnEarth's LandSat tiling scheme]
* World Wind's LandSat tiling scheme: [http://www.ceteranet.com/nww-tile-struct.pdf PDF], [http://www.worldwindcentral.com/wiki/Making_Layers wiki]
* World Wind ''QuadTileSet'' [http://rafb.net/paste/results/S3I8Zr92.html sample description], [http://forum.worldwind.arc.nasa.gov/lofiversion/index.php?t2965.html forum discussion], [http://rafb.net/paste/results/z2dQKa54.html sample PHP code] to fetch WW tiles for a given WMS GetMap request
* osgPlanet's C++ code for [http://www.remotesensing.org/cgi-bin/cvsweb.cgi/osgPlanet/src/osgPlanet/osgPlanetGridUtility.cpp?rev=HEAD;content-type=text%2Fx-cvsweb-markup tiling the Earth]
* WorldWind Example code for tiling the Earth (needs Proj.4 and GDAL libraries)[http://download.worldwindcentral.com/dstile-0.2.tar.gz DSTile and Tilepack]
* OnEarth's code for intercepting WW requests and converting into WMS requests and caching them [http://www.twobeds.com/upload/userfiles/adamhill/lucians%20code%20-%20cache_1_1.gz?PHPSESSID=f485cf3fd66cd30ad7a4f814a127d2cb from Lucian Plesa]
* Casey Chestnut explains Microsoft Virtual Earth's tiling scheme + code to experiment with the URL's [http://www.brains-n-brawn.com/veWorldWind/]
* GeoOdyssey's [http://www.geodyssey.com/tileshare/index.html TileShare scheme]
* Chuck Stein's [http://www.geongrid.org/workshops/geonvis2005/Presentations/ChuckStein/GeoFusion.ppt GeoFusion presentation] from GEON (warning: PowerPoint)
* [http://globe.sintef.no/documentation/projection.html The Finite Nearly-Conformal Normal Cylindrical Projection] (Aasgaard's map projection)

Note: WW and OnEarth's schemes are pretty much identical, the WW client just allows you to specify arbitrary tile sizes, coverages and number of levels to accomodate a given client.

== Related Projects ==

* [http://www.ossim.org/osgPlanet.html osgPlanet]
* [http://worldwind.arc.nasa.gov/ NASA WorldWind] ([http://www.worldwindcentral.com/wiki/Main_page wiki])
* [http://worldkit.org/ worldKit]
* [http://mapbuilder.sf.net/ Community MapBuilder]
* [http://ka-map.maptools.org/ ka-Map!]
* [http://openlayers.org/ OpenLayers]
* other AJAX map clients, presumably

== Interested Parties ==

''Note:'' Interested parties should join the existing low-volume [http://lists.eogeo.org/mailman/listinfo/tiling EOGEO mailing list] dedicated to this topic.

* [[User:SchuylerErle|Schuyler Erle]]
* [[User"Adoyle"|Allan Doyle]]
* [[user"Nhv"|Norman Vine]]
* [[user"Joshli"|Josh Lieberman]]
* [[user"Adamhill"|Adam Hill]]
* [[user"bitner"|David Bitner]]
* [[user:Mikel|Mikel Maron]]
* [[user:mpg|Michael P. Gerlek]]
* [[user:stvn|Steven M. Ottens]]
* [[user:Pagameba|Paul Spencer]]
* [[user:hallkbrdz|Bryan Hall]]
* [[user:tschaub|Tim Schaub]]
* [[user:dmorissette|Daniel Morissette]]
* [[user:dpatton|Dave Patton]]
* [[user:cholmes|Chris Holmes]]
* ''add yourself''

Supporting Spatial Databases

2006-07-31T18:20:35Z

Wiki-Cholmes:

This page is an attempt to survey spatial SQL storage and query support in open source databases.

What functions are people really using?

=== cholmes braindump on spatial databases ===

Sorry for the unclean format, hopefully someone else can come along and extract stuff out.

First, I think it's worthwhile to support the whole simple features for sql specification. I'm a bit biased, since GeoServer makes extensive use of the full set of operations. But it's really nice to have the power and to be sure it's accurate. The other reason I'm for the full power is that David Blasby came up with a really easy way to implement it, see [http://docs.codehaus.org/display/GEOS/SpatialDBBox Spatial DB in a Box]. It uses [JTS http://vividsolutions.com/jts/main.htm] to do all the 'hard' spatial operations, the crazy touches and intersects, in a very robust and accurate way. So if it's plugged in to spatial types, you basically get most of the simple features for sql specification for free. Note that it can compile to see using GCJ, David did experiments with PostGresql, and found that it would actually perform faster than postgis, and was much more maintainable than the hand coding of GEOS. The other thing needed for any spatial db is spatial indexing. This is required, or else queries on any table that's not a joke take way too long. Generally GIS guys aren't so interested in implementing the indexing, what's first needed is a GiST, which someone can slap an R-tree implementation to, and use that as the spatial index (I may have messed up some of the terminology, I'm mostly just replicating what Dave's braindumped to me - really, just read his spatial db in a box stuff, lots of valuable insights, on how the original architect of PostGIS would do it better the second time around).

==== MySQL ====

MySQL actually has decent spatial support, but without the last 20% it's relegated to close to useless. Very few people seriously use MySQL as a spatial backend. The problem is it does everything against the envelopes. So it can't be counted on to be accurate. It's sorta like an index against characters that when you ask for F* occasionally gives you one that starts with a G. It's not a huge deal, but if there's an alternative that gets it right, then you go with it.

The other big limitation is that the spatial support is only against the MyISAM tables, which don't offer full ACID compliance (afaik), and I think may be even flakier with spatial stuff. Like they just can't be trusted with transactions, and thus for many who actually manage spatial data are close to worthless. It'd be cool to see a compiled spatial db in a box against mysql, and certainly possible. Or they could go and use GEOS (the disadvantage in my biased mind being that it forked from JTS awhile ago, and relies on updating by hand, whereas compiling straight from JTS allows you to pick up all their fixes. But GEOS seems to have some critical mass behind it, though no one seems incredibly happy with it, and it seems to be in a limbo between just totally forking and optimizing or trying to stay up with hand ports of JTS)

==== Derby ====
This is the spatial DB I'd love to see. Super small, acid compliant, pure java. They need a GiST, and a couple of other improvements David [http://docs.codehaus.org/display/GEOS/SpatialDerby outlines]. He's already done probably 95% of the work.

==== Others ====
It'd be great to see SQL Lite support spatial stuff, could make use of GEOS or a compiled spatial db in a box. There's also HSQL and a few other small open source DBs. It'd be really great to have a very light weight embeddable spatial database. I know we'd love it for GeoServer, and indeed it could perhaps be a replacement for ESRI's personal Geo database, but with none of their limits. But I'd say it needs to fully support Simple features for SQL, and perhaps an additional small subset of operations, to be useful.

== References ==

* [http://postgis.refractions.net/docs/ch06.html#id2526109 OGC SQL Functions] (at refractions)
* [http://postgis.refractions.net/docs/ch06.html#id2527996 PostGIS Extensions]
* [http://portal.opengeospatial.org/files/index.php?artifact_id=829&version=2 OGC Simple Features for SQL] (pdf)
* [http://docs.codehaus.org/display/GEOS/SpatialDBBox Spatial DB in a Box]

Geodata Licensing Working Group

2006-07-20T15:31:34Z

Wiki-Cholmes:

This is a project started by the [[Public Geospatial Data Committee]]

The right to reuse and redistribute publically accessible bodies of data needs to be clear. This group can help provide guidelines for public geodata licensing, both of community-contributed and state-collected bodies of data.

== Focus ==

* Provision of clear guidelines for licenses, and the implications of their uses, for people contributing data to geospatial web / GSDI efforts.
* Potential work on a draft LPGL license to complement the draft [http://cemml.carleton.ca:8080/OGUG/pgl/ PGL].

[[Image:Cc_license_smaller.png]]

== Participants ==

* [[User:JoWalsh|Jo Walsh]]
* [[User:SchuylerErle|Schuyler Erle]]
* [[User:Pnaciona|Perry Nacionales]] (Jo and Schuyler need company :)
* [[User:dF|Daniel FAIVRE]]
* [[User:fbiasi|Frank Biasi]]
* [[User:cholmes|Chries Holmes]]
* ''your name here''

== Existing and related projects ==

* [http://geodatacommons.umaine.edu/ Geodata Commons]
* [http://www.okfn.org/wiki/OpenKnowledgeDefinition Open Knowledge Definition] survey of open license stances, a superset of this effort.

== Geodata Licenses ==

=== Public Geodata Licence ===

* original [http://sig.cwriter.org/index.php/PGL Public Geodata License] (French/English)
* [http://cemml.carleton.ca:8080/OGUG/pgl Group PGL-Canada]

=== Canadian Unrestricted Use Licence ===
* [http://www.geobase.ca/geobase/en/licence.jsp Geobase Unrestricted Use Licence Agreement] - BSD style license
* [http://www.cits.rncan.gc.ca/cit/servlet/CIT/site_id=01&page_id=1-021-001-007.html same license at Natural Resources Canada]

=== Creative Commons ===

* [http://creativecommons.org/ Creative Commons] is not a data-specific license, but Open

[[Image:Osm_license_small.png]]

== References ==

* [http://cemml.carleton.ca:8080/OGUG/pgl/ Public Geodata License] - [http://sig.cwriter.org/index.php/PGL French version, and cooperative website for license writing]
* [http://wiki.openstreetmap.org/index.php/Legal_FAQ OpenStreetmap Legal FAQ]
* [http://www.spatial.maine.edu/geodatacommons/PubCommonsSNGL.pdf Public Commons of Geographic Data - Research and Development Challenges (PDF)] - discusses IP issues
* [http://fermat.nap.edu/catalog/11079.html Licensing Geographic Data and Services] - book with some sample PDFs - cf [http://www.nap.edu/books/0309092671/html/213.htm Section 3, Chapter 9]
* [http://sciencecommons.org/data The Science Commons Data project] - explores ways to assure broad access to scientific data

== See Also ==

* [[Geodata Packaging Working Group]]
* [[Geodata Discovery Working Group]]

Public Geospatial Data Committee

2006-07-02T16:25:57Z

Wiki-Cholmes:

== Mission and Approach ==

See [[Public Geospatial Data Project]]

== Current Committee members ==

* [[User:JoWalsh|Jo Walsh]] (chair)
* [[User:cmbarton|Michael Barton]]
* [[User:bitner|David Bitner (irc:bitner)]]
* [[User:Neteler|Markus Neteler]]
* [[User:Adoyle|Allan Doyle]]
* [[User:Pnaciona|Pericles (Perry) Nacionales]]
* [[User:SchuylerErle|Schuyler Erle]]
* [[User:Arnulf_Christl|Arnulf Christl]]
* [[User:jmckenna|Jeff McKenna]]
* [[User:putler|Dan Putler]]
* [[User:nhv|Norman Vine]]

== Committee Website and Discussion List ==

* http://geodata.osgeo.org
* discussion: [https://geodata.osgeo.org/servlets/ProjectMailingListList geodata@geodata.osgeo.org]

== Task ==

Add basic description and references to the http://geodata.osgeo.org/ site

== Documents ==

* [[Public Geospatial Data Project]]
* [[Geodata Repository]]

== Meeting Agenda and Minutes ==

Meeting in IRC #osgeo channel (irc.freenode.net)

* [[Geodata_Committee_Meeting_20060322 | First meeting]], 1500 UTC 22 March, 2006 ([http://www.timeanddate.com/worldclock/fixedtime.html?month=3&day=22&year=2006&hour=16&min=0&sec=0&p1=215 fixed time around the world])
* [[Geodata_Committee_Meeting_20060329 | Second Meeting]], 1500 UTC 29 March, 2006 ([http://www.timeanddate.com/worldclock/fixedtime.html?month=3&day=29&year=2006&hour=16&min=0&sec=0&p1=215 fixed time around the world])
* [[Geodata_Committee_Meeting_20060406 | Third Meeting]], moved! 1600 UTC 6 April, 2006 ([http://www.timeanddate.com/worldclock/fixedtime.html?month=4&day=06&year=2006&hour=17&min=0&sec=0&p1=215 fixed time around the world])
* [[Geodata_Committee_Meeting_20060420 | Fourth Meeting]], 1600 UTC 20 April, 2006 ([http://www.timeanddate.com/worldclock/fixedtime.html?month=4&day=20&year=2006&hour=17&min=0&sec=0&p1=215 fixed time around the world])
* [[Geodata_Committee_Chat_20060511 | Fifth Meeting]], 1600 UTC 11 May, 2006 ([http://www.timeanddate.com/worldclock/fixedtime.html?month=5&day=11&year=2006&hour=16&min=0&sec=0 fixed time])
* [[Geodata_Committee_Sixth_Meeting | Sixth Meeting]] 1500 UTC 30th June 2006 ([http://timeanddate.com/worldclock/fixedtime.html?month=6&day=29&year=2006&hour=15&min=0&sec=0&p1=0 fixed time])

== Milestones ==

Milestones will be developed by the working groups.

== Working Groups ==

* [[Geodata Discovery Working Group]]
* [[Geodata Packaging Working Group]]
* [[Geodata Licensing Working Group]]

== Outreach ==

* [http://www.publicgeodata.org/Open_Letter Open Letter regarding the INSPIRE Directive] signed (3/2006)

=== Responses, References , Press ===
* http://www.heise.de/newsticker/meldung/71921 (Heise is a commercial enterprise publishing around IT. They operate a /.-like forum in German language

Public Geospatial Data Committee

2006-07-02T16:25:42Z

Wiki-Cholmes:

== Mission and Approach ==

See [[Public Geospatial Data Project]]

== Current Committee members ==

* [[User:JoWalsh|Jo Walsh]] (chair)
* [[User:cmbarton|Michael Barton]]
* [[User:bitner|David Bitner (irc:bitner)]]
* [[User:Neteler|Markus Neteler]]
* [[User:Adoyle|Allan Doyle]]
* [[User:Pnaciona|Pericles (Perry) Nacionales]]
* [[User:SchuylerErle|Schuyler Erle]]
* [[User:Arnulf_Christl|Arnulf Christl]]
* [[User:jmckenna|Jeff McKenna]]
* [[User:putler|Dan Putler]]
* [[User:nhv|Norman Vine]]
* [[User:cholmes|Chris Holmes]

== Committee Website and Discussion List ==

* http://geodata.osgeo.org
* discussion: [https://geodata.osgeo.org/servlets/ProjectMailingListList geodata@geodata.osgeo.org]

== Task ==

Add basic description and references to the http://geodata.osgeo.org/ site

== Documents ==

* [[Public Geospatial Data Project]]
* [[Geodata Repository]]

== Meeting Agenda and Minutes ==

Meeting in IRC #osgeo channel (irc.freenode.net)

* [[Geodata_Committee_Meeting_20060322 | First meeting]], 1500 UTC 22 March, 2006 ([http://www.timeanddate.com/worldclock/fixedtime.html?month=3&day=22&year=2006&hour=16&min=0&sec=0&p1=215 fixed time around the world])
* [[Geodata_Committee_Meeting_20060329 | Second Meeting]], 1500 UTC 29 March, 2006 ([http://www.timeanddate.com/worldclock/fixedtime.html?month=3&day=29&year=2006&hour=16&min=0&sec=0&p1=215 fixed time around the world])
* [[Geodata_Committee_Meeting_20060406 | Third Meeting]], moved! 1600 UTC 6 April, 2006 ([http://www.timeanddate.com/worldclock/fixedtime.html?month=4&day=06&year=2006&hour=17&min=0&sec=0&p1=215 fixed time around the world])
* [[Geodata_Committee_Meeting_20060420 | Fourth Meeting]], 1600 UTC 20 April, 2006 ([http://www.timeanddate.com/worldclock/fixedtime.html?month=4&day=20&year=2006&hour=17&min=0&sec=0&p1=215 fixed time around the world])
* [[Geodata_Committee_Chat_20060511 | Fifth Meeting]], 1600 UTC 11 May, 2006 ([http://www.timeanddate.com/worldclock/fixedtime.html?month=5&day=11&year=2006&hour=16&min=0&sec=0 fixed time])
* [[Geodata_Committee_Sixth_Meeting | Sixth Meeting]] 1500 UTC 30th June 2006 ([http://timeanddate.com/worldclock/fixedtime.html?month=6&day=29&year=2006&hour=15&min=0&sec=0&p1=0 fixed time])

== Milestones ==

Milestones will be developed by the working groups.

== Working Groups ==

* [[Geodata Discovery Working Group]]
* [[Geodata Packaging Working Group]]
* [[Geodata Licensing Working Group]]

== Outreach ==

* [http://www.publicgeodata.org/Open_Letter Open Letter regarding the INSPIRE Directive] signed (3/2006)

=== Responses, References , Press ===
* http://www.heise.de/newsticker/meldung/71921 (Heise is a commercial enterprise publishing around IT. They operate a /.-like forum in German language

Face to Face Meeting Summer 2006

2006-05-27T03:19:07Z

Wiki-Cholmes:

== Meeting ==

The board has been discussing the idea of getting people together for a face-to-face meeting to establish, and work on, priorities. A meetup / workshop needs clear goals. If we could set them, this could be a really useful occasion.

=== When and Where ===

June 11th and 12th at the Autodesk San Rafael offices.

This is just preceeding the Where 2.0 conference June 13/14 in San Jose which is relatively nearby. (According to Google, San Rafael to San Jose is 67 miles / 74 minutes.)

=== Attendees ===

Board members and committee members of VisCom, WebCom and the Fundraising committees are encouraged to attend.
* Frank Warmerdam will attend.
* mpg will attend (VisCom)
* Arnulf Christl will attend
* Jo Walsh will attend
* Dave McIlhagga will attend - likely arrive Sunday AM
* Gary Lang will attend
* Tyler Mitchell will attend (also from VisCom)
* Mark Lucas will attend
* Chris Holmes will attend
* ''please add availability for other people''

=== Goals ===
For a one- or two- day meeting there need to be clear goals identifiable.

==== WebCom ====
* OSGeo Web style established.
* Project style guidelines.
* Content plan completed.

==== Board ====
* Briefing by Mark Lucas on open source related activities within DOD.
* Develop a 2005/2006 budget.
* General strategy discussions.
* Discuss the stated priorities and how we meet them
* Make sure that the VisCom is as focused on promoting OSGeo projects as it is OSGeo itself, (if not more?)
* Try to reach consensus on new projects to admit to incubation.
* Discuss ideas for starting cross-collaboration between projects

==== VisCom ====
* Prepare conference presentation materials (for Where 2.0, and more general use).
* General strategy discussions.
* Outreach strategy

==== FunCom ====
* Develop sponsorship model
* Identify sources of income

=== Lodging and Travel ===
* See Itineraries section below for other attendee arrival times/places
* What hotels are near to venue?
** Embassy Suites is next door to Autodesk HQ. Use Autodesk Corporate rate of $119.
** [http://www.embassysuites.com/en/es/hotels/index.jhtml?ctyhocn=SFORFES Embassy Suites]
* Best way to get from SFO to San Rafael?
** From SFO to Central San Rafael Transit Center by Marin Airporter [http://www.marinairporter.com/schedules_sfo_to_marin.html Marin Airporter Service] (approx. 50 minutes) for $17
** Then take taxi from Central San Rafael Transit Center to Embassy Suites (5-10 minutes) approx. $10
** Meet up at SFO or SJC to share rental (see Itineraries below)
* Best way to get from San Rafael to San Jose at end of meeting? Share a bus/van?

=== Itineraries ===

Possibly futile attempt at collaborative scheduling as follows:

'''Saturday, June 10 (day before meeting)'''

* 5:00 pm - mpg arrives SJC
* 5:30 pm - mpg drives to San Rafael ''(space available, will rent large car if needed)''
* 5:00 pm - TM arrives SFO ''would like to catch/share ride to San Rafael''
* 12:15 pm - cholmes arrives OAK, spends day with friends.

'''Sunday, June 11 (1st meeting day)'''
* morning - cholmes is looking for a ride to San Rafael from SF area
* 11:00 pm - mlucas arrives SFO, rents car, drives to San Rafael

'''Monday, June 12 (2nd meeting day)'''

* evening - mpg drives to Where 2.0 ''(space available, will rent large car if needed)''
* evening - mlucas drives to Where 2.0 " "
* evening - cholmes rides with one of the above to Where 2.0

'''Tuesday, June 13 (day after meeting)'''
* Where 2.0

'''Wednesday, Jun 14
* Where 2.0
* evening - mlucas drives to SFO to catch a 10pm flight

Face to Face Meeting Summer 2006

2006-05-26T18:52:22Z

Wiki-Cholmes:

== Meeting ==

The board has been discussing the idea of getting people together for a face-to-face meeting to establish, and work on, priorities. A meetup / workshop needs clear goals. If we could set them, this could be a really useful occasion.

=== When and Where ===

June 11th and 12th at the Autodesk San Rafael offices.

This is just preceeding the Where 2.0 conference June 13/14 in San Jose which is relatively nearby. (According to Google, San Rafael to San Jose is 67 miles / 74 minutes.)

=== Attendees ===

Board members and committee members of VisCom, WebCom and the Fundraising committees are encouraged to attend.
* Frank Warmerdam will attend.
* mpg will attend (VisCom)
* Arnulf Christl will attend
* Jo Walsh will attend
* Dave McIlhagga will attend - likely arrive Sunday AM
* Gary Lang will attend
* Tyler Mitchell will attend (also from VisCom)
* Mark Lucas will attend
* ''please add availability for other people''

=== Goals ===
For a one- or two- day meeting there need to be clear goals identifiable.

==== WebCom ====
* OSGeo Web style established.
* Project style guidelines.
* Content plan completed.

==== Board ====
* Briefing by Mark Lucas on open source related activities within DOD.
* Develop a 2005/2006 budget.
* General strategy discussions.
* Discuss the stated priorities and how we meet them
* Make sure that the VisCom is as focused on promoting OSGeo projects as it is OSGeo itself, (if not more?)
* Try to reach consensus on new projects to admit to incubation.
* Discuss ideas for starting cross-collaboration between projects

==== VisCom ====
* Prepare conference presentation materials (for Where 2.0, and more general use).
* General strategy discussions.
* Outreach strategy

==== FunCom ====
* Develop sponsorship model
* Identify sources of income

=== Lodging and Travel ===
* See Itineraries section below for other attendee arrival times/places
* What hotels are near to venue?
** Embassy Suites is next door to Autodesk HQ. Use Autodesk Corporate rate of $119.
** [http://www.embassysuites.com/en/es/hotels/index.jhtml?ctyhocn=SFORFES Embassy Suites]
* Best way to get from SFO to San Rafael?
** From SFO to Central San Rafael Transit Center by Marin Airporter [http://www.marinairporter.com/schedules_sfo_to_marin.html Marin Airporter Service] (approx. 50 minutes) for $17
** Then take taxi from Central San Rafael Transit Center to Embassy Suites (5-10 minutes) approx. $10
** Meet up at SFO or SJC to share rental (see Itineraries below)
* Best way to get from San Rafael to San Jose at end of meeting? Share a bus/van?

=== Itineraries ===

Possibly futile attempt at collaborative scheduling as follows:

'''Saturday, June 10 (day before meeting)'''

* 5:00 pm - mpg arrives SJC
* 5:30 pm - mpg drives to San Rafael ''(space available, will rent large car if needed)''
* 5:00 pm - TM arrives SFO ''would like to catch/share ride to San Rafael''
* 12:15 pm - cholmes arrives OAK, spends day with friends.

'''Sunday, June 11 (1st meeting day)'''
* morning - cholmes is looking for a ride to San Rafael from SF area
* 11:00 pm - mlucas arrives SFO, rents car, drives to San Rafael

'''Monday, June 12 (2nd meeting day)'''

* evening - mpg drives to Where 2.0 ''(space available, will rent large car if needed)''
* evening - mlucas drives to Where 2.0 " "
* evening - cholmes rides with one of the above to Where 2.0

'''Tuesday, June 13 (day after meeting)'''
* Where 2.0

'''Wednesday, Jun 14
* Where 2.0
* evening - mlucas drives to SFO to catch a 10pm flight

Where 2.0 2006

2006-05-24T16:13:02Z

Wiki-Cholmes:

''' Look for plenty of OSGeo visibility and participation at Where 2.0.'''

''' Join us at the booth, the Birds of a Feather gathering, or Developer Roundtable!'''

== Speakers ==
Several people from OSGeo (and some non-OSGeo) are doing presentations at the conference.
* Chris Holmes: [http://conferences.oreillynet.com/cs/where2006/view/e_sess/9403 Lightning Talk on Geoserver]
* Gary Lang: [http://conferences.oreillynet.com/cs/where2006/view/e_sess/9390 "Opening” the Possibilities: API’s and Open Source Code]
* Frank Warmerdam: [http://conferences.oreillynet.com/cs/where2006/view/e_sess/9404 GDAL]
* Dylan Beaudette: [http://conferences.oreillynet.com/cs/where2006/view/e_sess/9344 GRASS]
* Schuyler Erle: [http://conferences.oreillynet.com/cs/where2006/view/e_sess/9310 Schuyler will likely do some OSGeo open geodata stuff]
* Frank Warmerdam [http://conferences.oreillynet.com/cs/where2006/view/e_sess/9389 OSGeo Foundation Intro]
* ''More to come''

== Booth Area ==
A 10 foot x 10 foot OSGeo booth area will be available for use by OSGeo members and projects, on Tuesday June 13.

* Two 6’ draped counters (20 linear feet)
* 2 counter height stools
* 8’ high draped backwall to hang banner
* High speed Internet connection
* Electrical connection for two computers

If you are planning to attend the event and would like to participate and represent your project, ADD YOUR NAME AND PROJECT below by May 31.

* Tyler Mitchell, OSGeo in general
* Dave McIlhagga, OSGeo in general
* Jo Walsh, OSGeo in general
* Pete Southwood or Arnab Ganguly, MapGuide Open Source
* mpg, OSGeo in general (Tuesday only)
* Arnulf Christl, OSGeo in detail, Mapbender
* Chris Holmes, OSGeo (and GeoServer).
* Add your name and project here

Booth staffing and scheduling will be determined once interested participants are known.

'''Exhibit Move-in Hours:'''

Monday, June 12, 2:00 pm – 6:00 pm

Tuesday, June 13, 7:00 am – 10:00 am

'''Exhibit Show Hours: '''
Tuesday, June 13, 10:00 am – 7:30 pm

(Actual open time: 10-11, 12-2, 3-4:30, 6-7:30 reception)

'''Exhibit Move-out Hours:'''

Tuesday, June 13, 7:00 pm – 10:00 pm

== Birds of a Feather Gathering ==
An informal gathering of the open source geospatial community will occur at:

* Tuesday, June 13
* now at 8:30 pm - 9:30 pm
* Location: Plaza Room

Tyler is now running the BOF.

The "agenda" will be something like this:

* Welcome (BOF Host)

* "What is OSGeo?" (5-10 mins) (Speaker 1)

* "An OSGeo Project" (5 mins) (Speaker 2)

* "An OSGeo Project" (5 mins) (Speaker 3)

* "An OSGeo Project" (5 mins) (Speaker 4)

* open discussion (remainder of time, until wee small hours)

The actual agenda will firm up closer to the time, when we get a better feel for who is going to be presenting what on the main stage, e.g. we don't want to repeat a "What is OSGeo" talk -- and who is actually going to be at the conference.

Preference for "Project" speakers will be those who don't get main-stage airtime. Also, note that I'm explicitly including the "Edu" and "OpenData" groups as projects.

== Press Event: Developer Roundtable ==

Section got too big -- moved to separate page: [[OSGeo at Where PressEvent]]

== Pre-Conference Messaging ==
OSGeo has the opportunity to email conference attendees who have opted in to receive communications regarding the event. The conference organizers at O'Reilly will provide a list 7-10 days prior to the conference. Chris Holmes has volunteered to craft a message promoting OSGeo activities at Where 2.0 and invite others to join us.

== Advert ==
Look for a one page ad promoting OSGeo in the conference program. It is a minimalist design, as our resources are limited here. We will reuse this as a flyer promoting OSGeo.

Where 2.0 2006

2006-05-16T17:52:08Z

Wiki-Cholmes:

Look for plenty of OSGeo visibility and participation at Where 2.0. Join us at booth area, the Birds of a Feather gathering, or Developer Roundtable.

== Speakers ==
Chris Holmes, Frank Warmerdam and Gary Lang will have speaking opportunities. Schuyler will do a bit of OSGeo, and a guy from GRASS is there as well:
* [http://conferences.oreillynet.com/cs/where2006/view/e_sess/9403 Lightning Talk on Geoserver]
* [http://conferences.oreillynet.com/cs/where2006/view/e_sess/9390 "Opening” the Possibilities: API’s and Open Source Code]
* [http://conferences.oreillynet.com/cs/where2006/view/e_sess/9404 GDAL]
* [http://conferences.oreillynet.com/cs/where2006/view/e_sess/9344 GRASS]
* [http://conferences.oreillynet.com/cs/where2006/view/e_sess/9310 Schuyler will likely do some OSGeo open geodata stuff]
* [http://conferences.oreillynet.com/cs/where2006/view/e_sess/9389 OSGeo Foundation Intro]

== Booth Area ==
An OSGeo booth area will be available for use by OSGeo members and projects.

* Two 6’ draped counters (20 linear feet)
* 2 counter height stools
* 8’ high draped backwall to hang banner
* High speed Internet connection
* Electrical connection for two computers

If you are planning to attend the event and would like to participate and represent your project, ADD YOUR NAME AND PROJECT below by May 31.

* Add your name and project here
* Add your name and project here

Booth staffing and scheduling will be determined once interested participants are known.

== Birds of a Feather Gathering ==
An informal gathering of the open source geospatial community will occur at:

* Tuesday, June 13
* 7:30 pm - 8:30 pm
* Location: Plaza Room

Chris Holmes and Michael Gerlek are coordinating this event.

The "agenda" will be something like this:

* Welcome (BOF Host)

* "What is OSGeo?" (5-10 mins) (Speaker 1)

* "An OSGeo Project" (5 mins) (Speaker 2)

* "An OSGeo Project" (5 mins) (Speaker 3)

* "An OSGeo Project" (5 mins) (Speaker 4)

* open discussion (remainder of time, until wee small hours)

The actual agenda will firm up closer to the time, when we get a better feel for who is going to be presenting what on the main stage, e.g. we don't want to repeat a "What is OSGeo" talk -- and who is actually going to be at the conference.

Preference for "Project" speakers will be those who don't get main-stage airtime. Also, note that I'm explicitly including the "Edu" and "OpenData" groups as projects.

I, or someone like me, will be the BOF Host.

== Developer Roundtable ==
An informal gathering of the open source geospatial community will occur at:

* Wednesday, June 14
* Time: During Lunchtime - we are investigating getting lunch catered.
* Location: TBD
* Participants: 4-6 developers. Members of the press will be invited. Room capacity is 20 people.

This will follow the keynotes on Wednesday morning so this is nice timing. There is nothing going on during this lunch hour and there is no exhibit hall during this time.

Michael Gerlek is coordinating this event, but may not be able to attend. We are looking for an on-site volunteer to help host and execute this event.

Suggested agenda:

* moderator introduces 4 panel members

* moderator introduces theme
** I'm thinking of something readily consumable by the press and suitable for sound-bites along the lines of "What is Driving Open Source Adoption in GIS Today?" (alternatives welcome)
** I'm inclined to not make it too technical, as in addition to the usual GIS media there may well be mainstream tech press there from Big Media like San Jose Merc, WSJ, or NYT

* each panel member gives a 1-2 minute (no more!) opening

* <much active discussion ensues>
** this is where the press gets to ask questions
** moderator gently aids in keeping discussion alive, as needed
** moderator may interject preplanned, leading questions like
*** "So just how many copies of MapServer were downloaded last year?"
*** "Is it true that both ESRI and Google Earth wouldn't exist today without GDAL?" ''(tee-hee)''

* at the end of the session, each panel member gets a 1 minute wrap-up

Possible Participants:

* Moderator
** '''who would be best for this?'''

* Dave McIlhagga - President & CEO of DM Solutions
** voice for: corporate provider of open source solutions (small team division)
** (confirmed)

* '''SUGGESTION:''' Frank Warmerdam - President of OSGeo and GDAL Lead
** voice for: OSGeo Foundation
** voice for: developer community

* '''SUGGESTION:''' Gary Lang - (title?) of Autodesk
** voice for: corporate provider of open source solutions (large team division), corporate acceptance and transition)''
** voice for: mainstream/close-source corporate acceptance of and transition to open source

* Speaker 4
** voice for: developer community? open data? open source in general? ...?
** '''suggestions?'''

== Pre-Conference Messaging ==
OSGeo has the opportunity to email conference attendees who have opted in to receive communications regarding the event. The conference organizers at O'Reilly will provide a list 7-10 days prior to the conference. Chris Holmes has volunteered to craft a message promoting OSGeo activities at Where 2.0 and invite others to join us.

== Advert ==
Look for a one page ad promoting OSGeo in the conference program. It will likely be a minimalist design, as our resources are limited here.

Where 2.0 2006

2006-05-16T17:51:13Z

Wiki-Cholmes:

Look for plenty of OSGeo visibility and participation at Where 2.0. Join us at booth area, the Birds of a Feather gathering, or Developer Roundtable.

== Speakers ==
Chris Holmes and Gary Lang will have speaking opportunities:
* [http://conferences.oreillynet.com/cs/where2006/view/e_sess/9403 Lightning Talk on Geoserver]
* [http://conferences.oreillynet.com/cs/where2006/view/e_sess/9390 "Opening” the Possibilities: API’s and Open Source Code]
* [http://conferences.oreillynet.com/cs/where2006/view/e_sess/9404 GDAL]
* [http://conferences.oreillynet.com/cs/where2006/view/e_sess/9344 GRASS]
* [http://conferences.oreillynet.com/cs/where2006/view/e_sess/9310 Schuyler will likely do some OSGeo open geodata stuff]
* [http://conferences.oreillynet.com/cs/where2006/view/e_sess/9389 OSGeo Foundation Intro]

== Booth Area ==
An OSGeo booth area will be available for use by OSGeo members and projects.

* Two 6’ draped counters (20 linear feet)
* 2 counter height stools
* 8’ high draped backwall to hang banner
* High speed Internet connection
* Electrical connection for two computers

If you are planning to attend the event and would like to participate and represent your project, ADD YOUR NAME AND PROJECT below by May 31.

* Add your name and project here
* Add your name and project here

Booth staffing and scheduling will be determined once interested participants are known.

== Birds of a Feather Gathering ==
An informal gathering of the open source geospatial community will occur at:

* Tuesday, June 13
* 7:30 pm - 8:30 pm
* Location: Plaza Room

Chris Holmes and Michael Gerlek are coordinating this event.

The "agenda" will be something like this:

* Welcome (BOF Host)

* "What is OSGeo?" (5-10 mins) (Speaker 1)

* "An OSGeo Project" (5 mins) (Speaker 2)

* "An OSGeo Project" (5 mins) (Speaker 3)

* "An OSGeo Project" (5 mins) (Speaker 4)

* open discussion (remainder of time, until wee small hours)

The actual agenda will firm up closer to the time, when we get a better feel for who is going to be presenting what on the main stage, e.g. we don't want to repeat a "What is OSGeo" talk -- and who is actually going to be at the conference.

Preference for "Project" speakers will be those who don't get main-stage airtime. Also, note that I'm explicitly including the "Edu" and "OpenData" groups as projects.

I, or someone like me, will be the BOF Host.

== Developer Roundtable ==
An informal gathering of the open source geospatial community will occur at:

* Wednesday, June 14
* Time: During Lunchtime - we are investigating getting lunch catered.
* Location: TBD
* Participants: 4-6 developers. Members of the press will be invited. Room capacity is 20 people.

This will follow the keynotes on Wednesday morning so this is nice timing. There is nothing going on during this lunch hour and there is no exhibit hall during this time.

Michael Gerlek is coordinating this event, but may not be able to attend. We are looking for an on-site volunteer to help host and execute this event.

Suggested agenda:

* moderator introduces 4 panel members

* moderator introduces theme
** I'm thinking of something readily consumable by the press and suitable for sound-bites along the lines of "What is Driving Open Source Adoption in GIS Today?" (alternatives welcome)
** I'm inclined to not make it too technical, as in addition to the usual GIS media there may well be mainstream tech press there from Big Media like San Jose Merc, WSJ, or NYT

* each panel member gives a 1-2 minute (no more!) opening

* <much active discussion ensues>
** this is where the press gets to ask questions
** moderator gently aids in keeping discussion alive, as needed
** moderator may interject preplanned, leading questions like
*** "So just how many copies of MapServer were downloaded last year?"
*** "Is it true that both ESRI and Google Earth wouldn't exist today without GDAL?" ''(tee-hee)''

* at the end of the session, each panel member gets a 1 minute wrap-up

Possible Participants:

* Moderator
** '''who would be best for this?'''

* Dave McIlhagga - President & CEO of DM Solutions
** voice for: corporate provider of open source solutions (small team division)
** (confirmed)

* '''SUGGESTION:''' Frank Warmerdam - President of OSGeo and GDAL Lead
** voice for: OSGeo Foundation
** voice for: developer community

* '''SUGGESTION:''' Gary Lang - (title?) of Autodesk
** voice for: corporate provider of open source solutions (large team division), corporate acceptance and transition)''
** voice for: mainstream/close-source corporate acceptance of and transition to open source

* Speaker 4
** voice for: developer community? open data? open source in general? ...?
** '''suggestions?'''

== Pre-Conference Messaging ==
OSGeo has the opportunity to email conference attendees who have opted in to receive communications regarding the event. The conference organizers at O'Reilly will provide a list 7-10 days prior to the conference. Chris Holmes has volunteered to craft a message promoting OSGeo activities at Where 2.0 and invite others to join us.

== Advert ==
Look for a one page ad promoting OSGeo in the conference program. It will likely be a minimalist design, as our resources are limited here.

Response to RFI for US Gov GeoSpatial

2006-05-05T19:51:07Z

Wiki-Cholmes:

== Introduction ==

This is a wiki version of the questions we need to answer for the RFI. Please feel free to start answering questions, and to edit the existing stuff, even without asking. It's all versioned, so we can roll back if a new change that we don't like is in. Be sure to read the full RFI, that has more about what they're looking for, at: http://www.estrategy.gov/lineofbusiness/docs/geospatial_rfi.doc

Right now we have four people who've thrown their hats in to work on this, feel free to add your name.

# Chris Holmes (interspersed time till start of may)
# Ned Horning (little time this week, start of may)
# Dave McIlhagga (start of may)
# Mike Davis (interspersed as workload permits)
# Bob Basques (as workload permits)
# Kevin Yam

==== Notes to use ====
Just ran across this, which may be helpful as a citation of sorts: http://www.linuxdevices.com/news/NS2542131185.html
It's about a report 'examining open standards, open source software, and "open innovation." The report concludes that openness should be promoted as a matter of public policy, in order to foster innovation and economic growth in the U.S. and world economies.'

[[Bibliography of OS and Geo information]]

==== Notes on submission ====

Submission of RFI Responses
Responses to the RFI must be submitted by e-mail to GSA by 5:00 p.m. EDT, May 5th, 2006. In responding to the RFI, please use the template labeled Part II: RFI Questionnaire. This template is also available at the following URL: http://www.whitehouse.gov/omb/egov/c-6-8-glob.html. Place your responses in-line in the document, retaining the question number and question text before each answer. Your e-mail should be clearly marked in the subject line with reference to RFI-GSV06PD00089 and your organization. You are required to include a point of contact for your organization. E-mail your response in Word (version 2000 or higher) to geospatial@gsa.gov. Please do not include marketing materials with your response at this time and ensure that any sensitive or protected information is marked as such. The government will ensure this information is not released externally. The overarching objective for this RFI is information gathering and not development of possible government acquisition of products or services.

* So someone's going to have to paste from this wiki back in to the original document, and email it in.

==== More notes ====
Place any additional notes about our information here...

Note that we don't have to respond to every question. The RFI says 'If you choose not to respond to a question, indicate “no response” and identify the rationale.' One can bypass a whole section (e.g. the scenarios, to which no-one has made a response here);
"Please respond to the appropriate Sections based on your experience"

The RFI urges this consideration of its goals, in responses:

''Respondents must factor key public values as defined by the NSDI into each response whenever applicable. Key public values include:''

* ''Privacy and security of citizens’ personal data and accuracy of statistical information on people, both in raw form and in derived information products''
* ''Access for all citizens to spatial data, information, and interpretive products, in accordance with OMB Circular A-130''
* ''Protection of proprietary interests related to licensed information and data''
* ''Interoperability of Federal information systems to enable the drawing of resources from multiple Federal agencies and their partners''

== RFI Questionnaire Section 1: Respondent Information ==

''Please provide the following information about your organization.''
''Responding Organization Name:'' Open Source GeoSpatial Foundation

''Are you responding as a:

''User organization from experience coordinating the use of geographic information or optimizing related spatial data activities''

''Vendor or consultant from experience providing products or services to help other organizations coordinate the use of geographic information or optimize related spatial data activities''

''Both''

Both

''Type of organization (e.g. Federal agency, non-profit, state, private):'' Non-Profit

''Contact information (provide a point of contact, phone number and e-mail address):''
Primary contact:
Chris Holmes, 212-219-6062, cholmes@openplans.org

Secondary contact:
Ned Horning, 212-313-7947, horning@amnh.org

== ''Lifecycle Activities'' ==
''The Office of Management and Budget (OMB) Circular A-161 provides direction for Federal agencies that produce, maintain, or use spatial data either directly or indirectly in the fulfillment of their respective missions. OMB Circular A-16, Section 8 describes Federal agency responsibilities and reporting requirements for collecting, using, or disseminating geographic information or carrying out related spatial data activities. These activities are identified as lifecycle activities for the purposes of this RFI.''

''Please answer the following questions from the perspective of an overall solution and approach for coordinating the use of geographic information and/or optimizing related spatial data activities. Lifecycle activities are being defined as (1) acquire, (2) process, (3) distribute, (4) use, 5) maintain, and (6) preserve spatial data. Be sure to include innovative practices, the applicability of these practices to Government and any relevant past experience.''

''2.2.1 In which data themes of national importance is there opportunity for increased effectiveness, efficiency, and cost savings potential across the Federal Government, and what is the recommended transition approach? OMB Circular A-16 framework data themes and other data themes of national significance are (1) geodetic control, (2) orthoimagery, (3) elevation and bathymetry, (4) transportation, (5) hydrography, (6) cadastral, and (7) governmental units.''

'''no response? rationale?'''

''2.2.2 What are the critical change management issues and best practices for successful transition to and full implementation of common solutions?''

Promotion and adoption of open standards for the collection, storage, access, and processing of geographic data is fundamental to the development of best-practise common solutions. Common implementation of standard protocols (for exchange) and formats (for storage and distribution) of geographic data are can greatly simplify future transitions.

A recently released report by the Digital Connections Council of the Committee for Economic Development, “Open Standards, Open Source, and Open Innovation: Harnessing the Benefits of Openness” (http://www.ced.org/projects/ecom.shtml#open) highlights the interoperability benefits gained from adopting open standards.

However, the presence of standards alone is not sufficient. The Open GeoSpatial Consortium (OGC) has made great strides in developing a set of standards, which precisely define a solution for interoperability of geographic data and systems. Yet uptake has been slow, as few outside of the standards writers see compelling reason to implement common solutions. Additionally, there are often large investments needed to adopt a standard. Investments may take the form of an upgrade to current software, developing or acquiring new software, or investing significant time in getting an open source solution running.

In transition to a common solution, these concerns can be addressed by:

- providing proof of best practise in ease of implementation of open standards for geographic data
- providing proof of value and return on investment in doing so

In order to encourage uptake, data providers need some compelling reason to transition a common solution. While the OGC community passed by promotion of their standards to write newer, more niche ones geared towards higher overhead uses, Google Earth came along with a compelling, user friendly environment with lots of available data. Far more organizations are making their data available as KML, the Google Earth standard, than have set up a Web Map Service interface. With WMS one tends to only replicate functionality that was already available, albeit in a more open way.

A compelling example of the power of interoperability is needed to render a new investment attractive to stakeholders; an open standards based solution cannot be merely a requirement demanded from above. The essence this is "bottom up" rather than "top down" approach is exemplified by the World Wide Web. Participation in the was not a question of being obliged to implement HTML and HTTP standards to share one's information; not doing so, one would be "missing the boat". If the Geospatial Web is perceived as something that is working now, and can be as compelling as the World Wide Web, it is naturally to everyone's advantage to implement common solutions.

The impact of potentially large infrastructure investment needed to adopt a standard, can be greatly minimized by available user friendly open source implementations of the open standards. This allows organizations to 'try out' new open standards without having to heavily invest in new infrastructure, the advantages of which are unknowable.

This is in no way exclusive of proprietary implementations of open standards, and most proprietary vendors that we've talked to welcome the availability of open source implementations.

After an initial evaluation phase of the standard itself, using the open source software, most organizations will complete a full evaluation of available solutions, and many times proprietary solutions will fit them best. Open standards and common solutions also benefit from many implementations; the more data that is available, the more compelling an environment. For vendors of proprietary software, 'a rising tide raises all boats', even if many people choose open source solutions. To go back to the World Wide Web analogy; though the open source Apache Web Server has a majority of the web server market, the proprietary vendors all have much greater sales as a result of the fact that more organisations are offering their online via standard protocols and formats; an outcome which Apache enabled by greatly lowering the barrier to entry.

Additionally, open source solutions will easily operate alongside legacy systems, so that an entirely new investment is not needed to transition over a whole infrastructure. Open source can run side by side with proprietary solutions, with open source implementing the new open standards. Stakeholders can maintain their regular workflows and transition to a more common solution in time. The open nature of the code means that even if a certain legacy system is not already available to be integrated, it is relatively easy to modify the open code to work with the legacy code. This mitigates the risk of transition to common solutions by allowing the transition to be iterative, incrementally adding small pieces along the way, instead of requiring a massive upheaval.

''2.2.3 What cultural impediments and training issues are paramount at which stages of the transition? What are the solutions to them?''

Although the United States is a global leader in providing public access to data, the process of collecting and maintaining, storing and processing these data are open. Historically, this has been the case because vendors providing these services use proprietary methods with the intent of gaining a competitive edge over their competition. This approach is rooted in traditional intellectual property protection ideals and can result in incompatibility between data sets, and high costs to the government. This mindset is a significant cultural impediment to achieving common solutions for working with geospatial data and can be overcome by developing open data and software standards and promoting the benefits of this approach to the business community and government organizations.

Cultural Issues
<ul>
<li>Data Ownership vs. Data Stewardship</li>
<li>Drawing Centric vs. Data Centric (especially in CADD shops)</li>
<li>Public vs Private (or percieved to be Private).</li>
<li>Data format preferences still exist that may not coincide with the greater good.</li>
</ul>

Training Issues
<ul>
<li>Cost of use, training materials derived from open source packages vs proprietary packages.</li>
<li>Simple is better, if something is easier to use, it's more likely to be used.</li>
<li>Proprietary vs OpenSource</li>
</ul>

''2.2.4 From your experience, please describe the cost/benefit of coordinating the use of geographic information or optimizing NSDI components and related spatial data activities across all sectors and levels of government.''

Many current activities rely on a string of participants to manage a Geographic Information System. A system needs to allow individual data owners to update and maintain their respective datasets with the least amount of percieved extra work. If the process is precieved by the data owners to be additional effort on their part, it's much less likely to take hold as a standard. The process needs to be as painless as possible for the Data Steward in order for a system to be self sustaining.

Publication by Data Owners requires a few basic needs be met, such as:
<ul>
<li>Move publication and maintenance of data as close as possible to the data owners/creators.</li>
<li>Owners/creators are also responsible for appropriate metadata for their respective datasets. This aids in data discovery mechanisms for the end users.</li>
<li>Responsibly for upkeep and timeliness of data should be traceable to the owners/creators by average users of the data.</li>
<li>User Feedback systems need to be in place for relaying of errors and/or omissions back to the data owners.</li>
</ul>

''2.2.5 What are the top three critical factors for successfully coordinating the use of geographic information or optimizing related spatial data activities?''
<ul>
<li>Data interoperability – It is important that data can be used in all anticipated situations. This means it must be possible to combine it with other data and it must be usable within a broad range of available systems.</li>
<li>Accessibility – This includes physical access to data layers and the ability to work with those data in available usable systems (for example a GIS with trained personnel.)</li>
<li>Data Currency – Data currency must be within the requirements of the intended application.</li>
</ul>

''2.2.6 What are the top three risks in coordinating the use of geographic information or optimizing related spatial data activities? How do you mitigate these risks?''
<ul>
<li>Data Accuracy</li>
<li>Data Availability</li>
<li>Data Compatibility</li>
</ul>
The three biggest risks when building business practices based on shared geospatial information reflect the critical factors mentioned in 2.2.5. For shared systems to work, each proponent must be willing and able to meet a certain standard level of service that ensures the reliability and consistancy of the data provided. These data must be available in a format that is accessible to the end user regardless of software package or vendor.

''2.2.7 What are the key performance indicators related to coordinating the use of geographic information or optimizing related spatial data activities? What metrics can be obtained to measure performance and how?''

While data accuracy can be a difficult metric to measure shared spatial data by, it is probably the most important factor when relying on such data for business processes.

Easier to measure is the level of consistancy maintained by shared spatial data. Data that follows an established standard (ie. SDSFIE) [''reference?''] can be graded based on how well it follows and implements said standard.

Another important metric for coordinating use geographic data is the length of time required for changes made by the data steward to be reflected in the shared dataset. Minimizing this refresh time is critical if the shared datasets are to be considered an authoritative source of information.

''2.2.8 How do you retain the advantages of competition while reaping the benefits of geospatial coordination and optimization?''

Advantages of competition are perceived to be improved innovation (producing a better product) and reduced cost to the consumer. By developing and using open standards innovation is improved because of the size and diversity of the community developing the standards. Cost is also reduced because once the standards and clearly defined metrics of success are in place, the cost of entry for product development is reduced. To strengthen competition it helps if companies can compete on a level playing field that is promoted through the use of open standards.

''2.2.9 How do you ensure and manage ongoing innovation in geospatial coordination and optimization?''

The most effective way to ensure continued innovation is to promote and adopt open standards for the creation/collection, storage, access, and processing of geospatial data. This includes contributing to the development of open source geospatial software that supports and promotes common standards.

It is in the data users’ and producers’ interest to have interoperable solutions and the most effective way to accomplish this is to include them in the process of developing standards and software. The benefits of using open methods are becoming well publicized (for example see: http://www.amso.army.mil/cc-tteam/PMG_04_MOSA.pdf). [''quote?'']

To further benefit from current open approaches it is necessary to fund research and development for improved interoperability and access. Research should also be conducted on innovative open approaches for creating and maintaining geospatial data layers in an open environment. The potential of openness in the geospatial sector is great but funded research is needed to expedite the realization of these benefits.

''2.2.10 What are the incentives and disincentives for participation in geospatial coordination and optimization as a collaboration partner, a customer and as a service provider?''

'''no response? rationale?'''

''2.2.11 How do you achieve and sustain senior management involvement and commitment to coordinating the use of geographic information or optimizing related spatial data activities?''

Sustained commitment from senior management within an organization can be assured in two ways:
<ul><li>Funding</li><li>Mission</li></ul>
Tying funding to an entity's ability to create, maintain, and distribute geospatial information is the most immediate way to ensure the interest of senior management. For long term success, the organization must evolve to embrace the geospatial data lifecycle as a key component of its mission.

[''more detail..?'']

''2.2.12 What governance model do you use or would you recommend for coordinating the use of geographic information or optimizing related spatial data activities?''

A refined and clear cut governance model for coordinating the use of geographic information and related activities does not yet exist. As with developing standards, this should be developed using an open process. The success of the World Wide Web, the open source software movement, and online initiatives like Wikipedia, point to the success of what Benkler calls 'commons-based peer production' in Coase's Penguin (http://www.yale.edu/yalelj/112/BenklerWEB.pdf). The prerequisite of such activities is that the work is made available under an open access license (thus a commons), that a community of peers can collaborate on to improve. Value is built by coordination of a diverse group of individuals and institutions, located in many different places, to do an iterative set of tasks.

There is potentially much to be applied to the geospatial domain, looking to a bottom up process that is oriented towards users instead of a top down process dominated by producers. Ultimately most agencies are also potential consumers of geospatial information, and so a focus on the user needs should work for all. Since geospatial information is so diverse, and comes with varying quality of metadata, a top down coordination mechanism will likely crumble under its own weight. Instead open access should be a prerequisite, and that access should be simplified, not requiring lots of expensive software or training. It should be accessible online, for quick connection and integration in to other applications. If enough value is released in to an open environment, then potential users can contribute to the coordination and optimization of spatial data. The open source movement and commons-based peer production leaves it to users to figure out what tasks of coordination and use they are most effective at, instead of leaving it to a narrow choice of available employees. Just as some users of Amazon are excited to write reviews of thousands of books, so too there may be potential users of geospatial data who are motivated to write metadata and classify the quality, scale, year, and domain of available geospatial data. Instead of a culture of fear around putting out data without the accompanying metadata, producers should be able to release their data in to an open environment that can actually assist with the classification and additional information needed by other users.

The governance model for commons based peer production can not be dictated in advance, as it is different across domains and individuals involved. But those that have met success, after an iterative bootstrap period of figuring out the appropriate model, have changed their respective domains. If access is truly open, not just in license but in real availability, then it becomes possible to leverage the joint efforts of all users to coordinate a process that no single agency could do alone. The open source software community, wikipedia, the world wide web, and smaller communities like slashdot, clickworkers, and others, all point to the real world success of such processes. Beyond mere metadata Open Street Map (http://openstreetmap.org) starts to show the potential of coordinating the creation and maintenance of actual geographic data.

''2.2.13 What is the best approach for assembling and using multiple data sets from diverse fields where scale, units of analysis and data types differ?''
The key to working with diverse data is interoperability; this can be best achieved through the use of open standards for data and software. Open source geospatial software offerings have a proven track record for often being the first to implement geospatial standards developed by the Open Geospatial Consortium (OGC). 
The inability to read a particular file format is often the factor preventing access to a particular data set. This can occur for several reasons but two common problems are an insufficient capability of a software program to read a particular file format or the inability to read a proprietary file format using incompatible software. Adopting open standards and open source software can alleviate both of these problems. Having a community of individuals and organizations build on open source software libraries can help strengthen the ability of software packages to handle a wide variety of format. A good example of this is the open source Geospatial Data Abstraction Library (GDAL) and OGR which are raster (GDAL) and vector (OGR) translator libraries. Building on open source libraries provides excellent resources for open source and proprietary software developers alike. 

''2.2.14 What geospatial cross-cutting services, best practices, interoperable technologies, and data standards exist but are not necessarily coordinated or optimized by the Federal government?''

'''no response? rationale? '''

''2.2.15 What key issues and challenges must be considered when geospatial lifecycle activities occur in a foreign country that may or may not share borders with the US? What solutions do you propose to overcome these issues and challenges?''

''' no response? rationale?'''

== ''Scenarios'' ==

=== Scenario 1 - Emergency Response: ===
''The U.S. is experiencing an “Incident of National Significance”, as defined by Homeland Security Presidential Directive 5 (HSPD-5) that has required activation of the National Response Plan (NRP). The NRP provides a framework for the coordination of Federal, state, local, private, volunteer, and Non-Governmental organizations to work together in real time to respond effectively. Under the NRP, significant Federal geospatial data and assets are mobilized and made available to the responding homeland security (HLS) community. However, significant geospatial data and assets are available at the state and local level that are not immediately available to responding Federal Departments and agencies.''

''2.3.1 Please describe the types of non-Federal geospatial data that are available at the state and local government level, as well as from private utilities and other entities that might improve the effectiveness of the NRP.''

''In your response please address any issues regarding licensing of data, the need for information sharing agreements and similar impediments to other than full and open sharing of geospatial data within the HLS community.''

''2.3.2 What activities need to be undertaken during the Preparedness phase of the emergency lifecycle to assure emergency managements are aware of the potential of geospatial data and assets to support emergency response?''

''2.3.3 What activities need to be undertaken during the Preparedness phase of the emergency lifecycle to assure that geospatial technology subject matter experts and data stewards are aware of the emergency response requirement and standard operating procedures?''

''2.3.4 During response to an Incident of National Significance, what needs to be done to assure geospatial data and assets are made available to all participants in the NRP?''
''In particular, please identify issues that must be addressed to assure state and local geospatial data and assets can be made readily available to all participants in the response?''

''2.3.5 What activities to coordinate geospatial data and assets for emergency management applications are you aware of?''

''2.3.6 What activities do you suggest be undertaken to coordinate the use of geographic information or optimize related spatial data activities for emergency management?''

''2.3.7 Geospatial data can also play a critical role in performing analyses to support pre-disaster mitigation plan development and implementation as well as support of recovery operations. Please describe key aspects of the use of geospatial data and assets for pre-disaster mitigation and recovery.''

''2.3.8 What are the key components – organizational, training, business, and technical (including fixed and mobile technology) – that establish an environment that is ready to respond (preparedness), able to respond (incident management), capable of supporting pre-disaster mitigation and post-disaster recovery analysis, and provides enhancements or lessons learned for future event management?''

=== Scenario 2 - Long Term Research Scenario: ===

''The U.S. perceives societal benefit in performing long-term research. Research is being conducted in numerous social and physical science fields such as demographics, public infrastructure, climatology, health care, economics, and crime, etc.''

''2.3.9 How can we enable the use of geospatial assets, including both structured and unstructured data (e.g. statistical, geographic, imagery, narrative, etc.) and services for the types of research described in scenario 2?''

''2.3.10 How can the use of geospatial data, technologies and spatial data analysis be leveraged in this scenario?''

''2.3.11 What are the key components – organizational, training, business, and technical – that establish an environment that is capable of leveraging geospatial data and assets to achieve research objectives?''

=== Scenario 3 - Administration and Resources Management: ===

''Federal agencies and other organizations, both individually and collectively, manage billions of dollars of resources that traditionally have not exploited geospatial assets. This encompasses human resources, facilities, supplies, and finance (including grants, contracts, and intramural resources). In the grants management arena, Federal agencies are often required by OMB and Congress to assess and report on the efficiency, effectiveness and return on investment of multiple grant programs and other expenditures made annually to meet mission goals and provide service to citizens.''
''2.3.12 How can we establish the effective and efficient use of geo-referenced or geo-enabled data and assets across organizations, for the types of activities described in scenario 3?''

''2.3.13 How can the use of geospatial data, assets and spatial data analysis be leveraged in scenario 3?''

''2.3.14 What are the key components – organizational, training, business, and technical – that establish an environment that is capable of leveraging geospatial assets to achieve operational administrative and resource management objectives?''

=== Additional Information ===
''Please feel free to provide additional information, beyond the questions found in Section 2.2 and 2.3 that you feel should be considered to meet the goals and objectives of the Geospatial Line of Business.''

Response to RFI for US Gov GeoSpatial

2006-05-05T15:44:44Z

Wiki-Cholmes: fix from commercial -> proprietary

== Introduction ==

This is a wiki version of the questions we need to answer for the RFI. Please feel free to start answering questions, and to edit the existing stuff, even without asking. It's all versioned, so we can roll back if a new change that we don't like is in. Be sure to read the full RFI, that has more about what they're looking for, at: http://www.estrategy.gov/lineofbusiness/docs/geospatial_rfi.doc

Right now we have four people who've thrown their hats in to work on this, feel free to add your name.

# Chris Holmes (interspersed time till start of may)
# Ned Horning (little time this week, start of may)
# Dave McIlhagga (start of may)
# Mike Davis (interspersed as workload permits)
# Bob Basques (as workload permits)
# Kevin Yam

==== Notes to use ====
Just ran across this, which may be helpful as a citation of sorts: http://www.linuxdevices.com/news/NS2542131185.html
It's about a report 'examining open standards, open source software, and "open innovation." The report concludes that openness should be promoted as a matter of public policy, in order to foster innovation and economic growth in the U.S. and world economies.'

[[Bibliography of OS and Geo information]]

==== Notes on submission ====

Submission of RFI Responses
Responses to the RFI must be submitted by e-mail to GSA by 5:00 p.m. EDT, May 5th, 2006. In responding to the RFI, please use the template labeled Part II: RFI Questionnaire. This template is also available at the following URL: http://www.whitehouse.gov/omb/egov/c-6-8-glob.html. Place your responses in-line in the document, retaining the question number and question text before each answer. Your e-mail should be clearly marked in the subject line with reference to RFI-GSV06PD00089 and your organization. You are required to include a point of contact for your organization. E-mail your response in Word (version 2000 or higher) to geospatial@gsa.gov. Please do not include marketing materials with your response at this time and ensure that any sensitive or protected information is marked as such. The government will ensure this information is not released externally. The overarching objective for this RFI is information gathering and not development of possible government acquisition of products or services.

* So someone's going to have to paste from this wiki back in to the original document, and email it in.

==== More notes ====
Place any additional notes about our information here...

Note that we don't have to respond to every question. The RFI says 'If you choose not to respond to a question, indicate “no response” and identify the rationale.' One can bypass a whole section (e.g. the scenarios, to which no-one has made a response here);
"Please respond to the appropriate Sections based on your experience"

The RFI urges this consideration of its goals, in responses:

''Respondents must factor key public values as defined by the NSDI into each response whenever applicable. Key public values include:''

* ''Privacy and security of citizens’ personal data and accuracy of statistical information on people, both in raw form and in derived information products''
* ''Access for all citizens to spatial data, information, and interpretive products, in accordance with OMB Circular A-130''
* ''Protection of proprietary interests related to licensed information and data''
* ''Interoperability of Federal information systems to enable the drawing of resources from multiple Federal agencies and their partners''

== RFI Questionnaire Section 1: Respondent Information ==

''Please provide the following information about your organization.''
''Responding Organization Name:'' Open Source GeoSpatial Foundation

''Are you responding as a:

''User organization from experience coordinating the use of geographic information or optimizing related spatial data activities''

''Vendor or consultant from experience providing products or services to help other organizations coordinate the use of geographic information or optimize related spatial data activities''

''Both''

Both

''Type of organization (e.g. Federal agency, non-profit, state, private):'' Non-Profit

''Contact information (provide a point of contact, phone number and e-mail address):''
* whoever sends it in could naturally be their contact

== ''Lifecycle Activities'' ==
''The Office of Management and Budget (OMB) Circular A-161 provides direction for Federal agencies that produce, maintain, or use spatial data either directly or indirectly in the fulfillment of their respective missions. OMB Circular A-16, Section 8 describes Federal agency responsibilities and reporting requirements for collecting, using, or disseminating geographic information or carrying out related spatial data activities. These activities are identified as lifecycle activities for the purposes of this RFI.''

''Please answer the following questions from the perspective of an overall solution and approach for coordinating the use of geographic information and/or optimizing related spatial data activities. Lifecycle activities are being defined as (1) acquire, (2) process, (3) distribute, (4) use, 5) maintain, and (6) preserve spatial data. Be sure to include innovative practices, the applicability of these practices to Government and any relevant past experience.''

''2.2.1 In which data themes of national importance is there opportunity for increased effectiveness, efficiency, and cost savings potential across the Federal Government, and what is the recommended transition approach? OMB Circular A-16 framework data themes and other data themes of national significance are (1) geodetic control, (2) orthoimagery, (3) elevation and bathymetry, (4) transportation, (5) hydrography, (6) cadastral, and (7) governmental units.''

'''no response? rationale?'''

''2.2.2 What are the critical change management issues and best practices for successful transition to and full implementation of common solutions?''

Promotion and adoption of open standards for the collection, storage, access, and processing of geographic data is fundamental to the development of best-practise common solutions. Common implementation of standard protocols (for exchange) and formats (for storage and distribution) of geographic data are can greatly simplify future transitions.

A recently released report by the Digital Connections Council of the Committee for Economic Development, “Open Standards, Open Source, and Open Innovation: Harnessing the Benefits of Openness” (http://www.ced.org/projects/ecom.shtml#open) highlights the interoperability benefits gained from adopting open standards.

However, the presence of standards alone is not sufficient. The Open GeoSpatial Consortium (OGC) has made great strides in developing a set of standards, which precisely define a solution for interoperability of geographic data and systems. Yet uptake has been slow, as few outside of the standards writers see compelling reason to implement common solutions. Additionally, there are often large investments needed to adopt a standard. Investments may take the form of an upgrade to current software, developing or acquiring new software, or investing significant time in getting an open source solution running.

In transition to a common solution, these concerns can be addressed by:

- providing proof of best practise in ease of implementation of open standards for geographic data
- providing proof of value and return on investment in doing so

In order to encourage uptake, data providers need some compelling reason to transition a common solution. While the OGC community passed by promotion of their standards to write newer, more niche ones geared towards higher overhead uses, Google Earth came along with a compelling, user friendly environment with lots of available data. Far more organizations are making their data available as KML, the Google Earth standard, than have set up a Web Map Service interface. With WMS one tends to only replicate functionality that was already available, albeit in a more open way.

A compelling example of the power of interoperability is needed to render a new investment attractive to stakeholders; an open standards based solution cannot be merely a requirement demanded from above. The essence this is "bottom up" rather than "top down" approach is exemplified by the World Wide Web. Participation in the was not a question of being obliged to implement HTML and HTTP standards to share one's information; not doing so, one would be "missing the boat". If the Geospatial Web is perceived as something that is working now, and can be as compelling as the World Wide Web, it is naturally to everyone's advantage to implement common solutions.

The impact of potentially large infrastructure investment needed to adopt a standard, can be greatly minimized by available user friendly open source implementations of the open standards. This allows organizations to 'try out' new open standards without having to heavily invest in new infrastructure, the advantages of which are unknowable.

This is in no way exclusive of proprietary implementations of open standards, and most proprietary vendors that we've talked to welcome the availability of open source implementations.

After an initial evaluation phase of the standard itself, using the open source software, most organizations will complete a full evaluation of available solutions, and many times proprietary solutions will fit them best. Open standards and common solutions also benefit from many implementations; the more data that is available, the more compelling an environment. For vendors of proprietary software, 'a rising tide raises all boats', even if many people choose open source solutions. To go back to the World Wide Web analogy; though the open source Apache Web Server has a majority of the web server market, the proprietary vendors all have much greater sales as a result of the fact that more organisations are offering their online via standard protocols and formats; an outcome which Apache enabled by greatly lowering the barrier to entry.

Additionally, open source solutions will easily operate alongside legacy systems, so that an entirely new investment is not needed to transition over a whole infrastructure. Open source can run side by side with proprietary solutions, with open source implementing the new open standards. Stakeholders can maintain their regular workflows and transition to a more common solution in time. The open nature of the code means that even if a certain legacy system is not already available to be integrated, it is relatively easy to modify the open code to work with the legacy code. This mitigates the risk of transition to common solutions by allowing the transition to be iterative, incrementally adding small pieces along the way, instead of requiring a massive upheaval.

''2.2.3 What cultural impediments and training issues are paramount at which stages of the transition? What are the solutions to them?''

Although the United States is a global leader in providing public access to data, the process of collecting and maintaining, storing and processing these data are open. Historically, this has been the case because vendors providing these services use proprietary methods with the intent of gaining a competitive edge over their competition. This approach is rooted in traditional intellectual property protection ideals and can result in incompatibility between data sets, and high costs to the government. This mindset is a significant cultural impediment to achieving common solutions for working with geospatial data and can be overcome by developing open data and software standards and promoting the benefits of this approach to the business community and government organizations.

Cultural Issues
<ul>
<li>Data Ownership vs. Data Stewardship</li>
<li>Drawing Centric vs. Data Centric (especially in CADD shops)</li>
<li>Public vs Private (or percieved to be Private).</li>
<li>Data format preferences still exist that may not coincide with the greater good.</li>
</ul>

Training Issues
<ul>
<li>Cost of use, training materials derived from open source packages vs proprietary packages.</li>
<li>Simple is better, if something is easier to use, it's more likely to be used.</li>
<li>Proprietary vs OpenSource</li>
</ul>

''2.2.4 From your experience, please describe the cost/benefit of coordinating the use of geographic information or optimizing NSDI components and related spatial data activities across all sectors and levels of government.''

Many current activities rely on a string of participants to manage a Geographic Information System. A system needs to allow individual data owners to update and maintain their respective datasets with the least amount of percieved extra work. If the process is precieved by the data owners to be additional effort on their part, it's much less likely to take hold as a standard. The process needs to be as painless as possible for the Data Steward in order for a system to be self sustaining.

Publication by Data Owners requires a few basic needs be met, such as:
<ul>
<li>Move publication and maintenance of data as close as possible to the data owners/creators.</li>
<li>Owners/creators are also responsible for appropriate metadata for their respective datasets. This aids in data discovery mechanisms for the end users.</li>
<li>Responsibly for upkeep and timeliness of data should be traceable to the owners/creators by average users of the data.</li>
<li>User Feedback systems need to be in place for relaying of errors and/or omissions back to the data owners.</li>
</ul>

''2.2.5 What are the top three critical factors for successfully coordinating the use of geographic information or optimizing related spatial data activities?''
<ul>
<li>Data interoperability – It is important that data can be used in all anticipated situations. This means it must be possible to combine it with other data and it must be usable within a broad range of available systems.</li>
<li>Accessibility – This includes physical access to data layers and the ability to work with those data in available usable systems (for example a GIS with trained personnel.)</li>
<li>Data Currency – Data currency must be within the requirements of the intended application.</li>
</ul>

''2.2.6 What are the top three risks in coordinating the use of geographic information or optimizing related spatial data activities? How do you mitigate these risks?''
<ul>
<li>Data Accuracy</li>
<li>Data Availability</li>
<li>Data Compatibility</li>
</ul>
The three biggest risks when building business practices based on shared geospatial information reflect the critical factors mentioned in 2.2.5. For shared systems to work, each proponent must be willing and able to meet a certain standard level of service that ensures the reliability and consistancy of the data provided. These data must be available in a format that is accessible to the end user regardless of software package or vendor.

''2.2.7 What are the key performance indicators related to coordinating the use of geographic information or optimizing related spatial data activities? What metrics can be obtained to measure performance and how?''

While data accuracy can be a difficult metric to measure shared spatial data by, it is probably the most important factor when relying on such data for business processes.

Easier to measure is the level of consistancy maintained by shared spatial data. Data that follows an established standard (ie. SDSFIE) [''reference?''] can be graded based on how well it follows and implements said standard.

Another important metric for coordinating use geographic data is the length of time required for changes made by the data steward to be reflected in the shared dataset. Minimizing this refresh time is critical if the shared datasets are to be considered an authoritative source of information.

''2.2.8 How do you retain the advantages of competition while reaping the benefits of geospatial coordination and optimization?''

Advantages of competition are perceived to be improved innovation (producing a better product) and reduced cost to the consumer. By developing and using open standards innovation is improved because of the size and diversity of the community developing the standards. Cost is also reduced because once the standards and clearly defined metrics of success are in place, the cost of entry for product development is reduced. To strengthen competition it helps if companies can compete on a level playing field that is promoted through the use of open standards.

''2.2.9 How do you ensure and manage ongoing innovation in geospatial coordination and optimization?''

The most effective way to ensure continued innovation is to promote and adopt open standards for the creation/collection, storage, access, and processing of geospatial data. This includes contributing to the development of open source geospatial software that supports and promotes common standards.

It is in the data users’ and producers’ interest to have interoperable solutions and the most effective way to accomplish this is to include them in the process of developing standards and software. The benefits of using open methods are becoming well publicized (for example see: http://www.amso.army.mil/cc-tteam/PMG_04_MOSA.pdf). [''quote?'']

To further benefit from current open approaches it is necessary to fund research and development for improved interoperability and access. Research should also be conducted on innovative open approaches for creating and maintaining geospatial data layers in an open environment. The potential of openness in the geospatial sector is great but funded research is needed to expedite the realization of these benefits.

''2.2.10 What are the incentives and disincentives for participation in geospatial coordination and optimization as a collaboration partner, a customer and as a service provider?''

'''no response? rationale?'''

''2.2.11 How do you achieve and sustain senior management involvement and commitment to coordinating the use of geographic information or optimizing related spatial data activities?''

Sustained commitment from senior management within an organization can be assured in two ways:
<ul><li>Funding</li><li>Mission</li></ul>
Tying funding to an entity's ability to create, maintain, and distribute geospatial information is the most immediate way to ensure the interest of senior management. For long term success, the organization must evolve to embrace the geospatial data lifecycle as a key component of its mission.

[''more detail..?'']

''2.2.12 What governance model do you use or would you recommend for coordinating the use of geographic information or optimizing related spatial data activities?''

A refined and clear cut governance model for coordinating the use of geographic
information and related activities does not yet exist. As with developing standards, this should be developed using an open process. There is a wealth of information related to governance models that can be drawn from the open source software community. The open source software community is thriving by leveraging the expertise and interests from a diverse group of individuals and a similar model can be used to benefit from, and better coordinate, the use of geographic information and to optimize related spatial data activities. 

''2.2.13 What is the best approach for assembling and using multiple data sets from diverse fields where scale, units of analysis and data types differ?''
The key to working with diverse data is interoperability; this can be best achieved through the use of open standards for data and software. Open source geospatial software offerings have a proven track record for often being the first to implement geospatial standards developed by the Open Geospatial Consortium (OGC). 
The inability to read a particular file format is often the factor preventing access to a particular data set. This can occur for several reasons but two common problems are an insufficient capability of a software program to read a particular file format or the inability to read a proprietary file format using incompatible software. Adopting open standards and open source software can alleviate both of these problems. Having a community of individuals and organizations build on open source software libraries can help strengthen the ability of software packages to handle a wide variety of format. A good example of this is the open source Geospatial Data Abstraction Library (GDAL) and OGR which are raster (GDAL) and vector (OGR) translator libraries. Building on open source libraries provides excellent resources for open source and proprietary software developers alike. 

''2.2.14 What geospatial cross-cutting services, best practices, interoperable technologies, and data standards exist but are not necessarily coordinated or optimized by the Federal government?''

'''no response? rationale? '''

''2.2.15 What key issues and challenges must be considered when geospatial lifecycle activities occur in a foreign country that may or may not share borders with the US? What solutions do you propose to overcome these issues and challenges?''

''' no response? rationale?'''

== ''Scenarios'' ==

=== Scenario 1 - Emergency Response: ===
''The U.S. is experiencing an “Incident of National Significance”, as defined by Homeland Security Presidential Directive 5 (HSPD-5) that has required activation of the National Response Plan (NRP). The NRP provides a framework for the coordination of Federal, state, local, private, volunteer, and Non-Governmental organizations to work together in real time to respond effectively. Under the NRP, significant Federal geospatial data and assets are mobilized and made available to the responding homeland security (HLS) community. However, significant geospatial data and assets are available at the state and local level that are not immediately available to responding Federal Departments and agencies.''

''2.3.1 Please describe the types of non-Federal geospatial data that are available at the state and local government level, as well as from private utilities and other entities that might improve the effectiveness of the NRP.''

''In your response please address any issues regarding licensing of data, the need for information sharing agreements and similar impediments to other than full and open sharing of geospatial data within the HLS community.''

''2.3.2 What activities need to be undertaken during the Preparedness phase of the emergency lifecycle to assure emergency managements are aware of the potential of geospatial data and assets to support emergency response?''

''2.3.3 What activities need to be undertaken during the Preparedness phase of the emergency lifecycle to assure that geospatial technology subject matter experts and data stewards are aware of the emergency response requirement and standard operating procedures?''

''2.3.4 During response to an Incident of National Significance, what needs to be done to assure geospatial data and assets are made available to all participants in the NRP?''
''In particular, please identify issues that must be addressed to assure state and local geospatial data and assets can be made readily available to all participants in the response?''

''2.3.5 What activities to coordinate geospatial data and assets for emergency management applications are you aware of?''

''2.3.6 What activities do you suggest be undertaken to coordinate the use of geographic information or optimize related spatial data activities for emergency management?''

''2.3.7 Geospatial data can also play a critical role in performing analyses to support pre-disaster mitigation plan development and implementation as well as support of recovery operations. Please describe key aspects of the use of geospatial data and assets for pre-disaster mitigation and recovery.''

''2.3.8 What are the key components – organizational, training, business, and technical (including fixed and mobile technology) – that establish an environment that is ready to respond (preparedness), able to respond (incident management), capable of supporting pre-disaster mitigation and post-disaster recovery analysis, and provides enhancements or lessons learned for future event management?''

=== Scenario 2 - Long Term Research Scenario: ===

''The U.S. perceives societal benefit in performing long-term research. Research is being conducted in numerous social and physical science fields such as demographics, public infrastructure, climatology, health care, economics, and crime, etc.''

''2.3.9 How can we enable the use of geospatial assets, including both structured and unstructured data (e.g. statistical, geographic, imagery, narrative, etc.) and services for the types of research described in scenario 2?''

''2.3.10 How can the use of geospatial data, technologies and spatial data analysis be leveraged in this scenario?''

''2.3.11 What are the key components – organizational, training, business, and technical – that establish an environment that is capable of leveraging geospatial data and assets to achieve research objectives?''

=== Scenario 3 - Administration and Resources Management: ===

''Federal agencies and other organizations, both individually and collectively, manage billions of dollars of resources that traditionally have not exploited geospatial assets. This encompasses human resources, facilities, supplies, and finance (including grants, contracts, and intramural resources). In the grants management arena, Federal agencies are often required by OMB and Congress to assess and report on the efficiency, effectiveness and return on investment of multiple grant programs and other expenditures made annually to meet mission goals and provide service to citizens.''
''2.3.12 How can we establish the effective and efficient use of geo-referenced or geo-enabled data and assets across organizations, for the types of activities described in scenario 3?''

''2.3.13 How can the use of geospatial data, assets and spatial data analysis be leveraged in scenario 3?''

''2.3.14 What are the key components – organizational, training, business, and technical – that establish an environment that is capable of leveraging geospatial assets to achieve operational administrative and resource management objectives?''

=== Additional Information ===
''Please feel free to provide additional information, beyond the questions found in Section 2.2 and 2.3 that you feel should be considered to meet the goals and objectives of the Geospatial Line of Business.''

Response to RFI for US Gov GeoSpatial

2006-05-03T19:25:08Z

Wiki-Cholmes: formatting of scenario's 2 and 3

== Introduction ==

This is a wiki version of the questions we need to answer for the RFI. Please feel free to start answering questions, and to edit the existing stuff, even without asking. It's all versioned, so we can roll back if a new change that we don't like is in. Be sure to read the full RFI, that has more about what they're looking for, at: http://www.estrategy.gov/lineofbusiness/docs/geospatial_rfi.doc

Right now we have four people who've thrown their hats in to work on this, feel free to add your name.

# Chris Holmes (interspersed time till start of may)
# Ned Horning (little time this week, start of may)
# Dave McIlhagga (start of may)
# Mike Davis (interspersed as workload permits)
# Bob Basques (as workload permits)
#

==== Notes to use ====
Just ran across this, which may be helpful as a citation of sorts: http://www.linuxdevices.com/news/NS2542131185.html
It's about a report 'examining open standards, open source software, and "open innovation." The report concludes that openness should be promoted as a matter of public policy, in order to foster innovation and economic growth in the U.S. and world economies.'

[[Bibliography of OS and Geo information]]

==== Notes on submission ====

Submission of RFI Responses
Responses to the RFI must be submitted by e-mail to GSA by 5:00 p.m. EDT, May 5th, 2006. In responding to the RFI, please use the template labeled Part II: RFI Questionnaire. This template is also available at the following URL: http://www.whitehouse.gov/omb/egov/c-6-8-glob.html. Place your responses in-line in the document, retaining the question number and question text before each answer. Your e-mail should be clearly marked in the subject line with reference to RFI-GSV06PD00089 and your organization. You are required to include a point of contact for your organization. E-mail your response in Word (version 2000 or higher) to geospatial@gsa.gov. Please do not include marketing materials with your response at this time and ensure that any sensitive or protected information is marked as such. The government will ensure this information is not released externally. The overarching objective for this RFI is information gathering and not development of possible government acquisition of products or services.

* So someone's going to have to paste from this wiki back in to the original document, and email it in.

==== More notes ====
Place any additional notes about our information here...

Note that we don't have to respond to every question. The RFI says 'If you choose not to respond to a question, indicate “no response” and identify the rationale.'

== RFI Questionnaire Section 1: Respondent Information ==

''Please provide the following information about your organization.''
''Responding Organization Name:'' Open Source GeoSpatial Foundation

''Are you responding as a:

''User organization from experience coordinating the use of geographic information or optimizing related spatial data activities''

''Vendor or consultant from experience providing products or services to help other organizations coordinate the use of geographic information or optimize related spatial data activities''

''Both''

Both

''Type of organization (e.g. Federal agency, non-profit, state, private):'' Non-Profit

''Contact information (provide a point of contact, phone number and e-mail address):''

== ''Lifecycle Activities'' ==
''The Office of Management and Budget (OMB) Circular A-161 provides direction for Federal agencies that produce, maintain, or use spatial data either directly or indirectly in the fulfillment of their respective missions. OMB Circular A-16, Section 8 describes Federal agency responsibilities and reporting requirements for collecting, using, or disseminating geographic information or carrying out related spatial data activities. These activities are identified as lifecycle activities for the purposes of this RFI.''

''Please answer the following questions from the perspective of an overall solution and approach for coordinating the use of geographic information and/or optimizing related spatial data activities. Lifecycle activities are being defined as (1) acquire, (2) process, (3) distribute, (4) use, 5) maintain, and (6) preserve spatial data. Be sure to include innovative practices, the applicability of these practices to Government and any relevant past experience.''

''2.2.1 In which data themes of national importance is there opportunity for increased effectiveness, efficiency, and cost savings potential across the Federal Government, and what is the recommended transition approach? OMB Circular A-16 framework data themes and other data themes of national significance are (1) geodetic control, (2) orthoimagery, (3) elevation and bathymetry, (4) transportation, (5) hydrography, (6) cadastral, and (7) governmental units.''

''2.2.2 What are the critical change management issues and best practices for successful transition to and full implementation of common solutions?''

A fundamental change management issue is to promote and adapt open standards for the collection (protocols), storage (file formats, media, and metadata), access, and processing of geographic data. A recently released report by the Digital Connections Council of the Committee for Economic Development, “Open Standards, Open Source, and Open Innovation: Harnessing the Benefits of Openness” (http://www.ced.org/projects/ecom.shtml#open) highlights the benefits from adapting open standards. This report found that openness can be used effectively to build standards that in turn can be used to enhance interoperability.

But standards alone are not a cure all. The Open GeoSpatial Consortium (OGC) has made great strides in developing a solid set of standards, which precisely defines a common solution that would go quite far towards true interoperability. But uptake has been slow, as few outside of the standards writers see compelling reason to upgrade, while they also see a large investment needed to adopt a standard - in the form of an upgrade to their current software, an entirely new piece of software, or significant time investment to get an open source solution running.

Both of these issues can be improved upon, which would greatly increase the chances of common solutions. The first is to provide some compelling reason to transition a current solution. While the OGC community passed by promotion of their standards to write newer, more niche ones geared towards higher overhead uses, Google Earth came along with a compelling, user friendly environment with lots of available data. Far more organizations are making their data available as KML, the Google Earth standard, than have set up a WMS, since with it they can visualize their data in ways they couldn't before. With WMS one tends to only replicate functionality that was already available, albeit in a more open way. What is needed is a compelling example of the power of interoperability, so that a new investment is attractive to stakeholders, and not merely a requirement demanded from above. The essence of this is a top down versus bottom up approach. The bottom up approach is exemplified by the World Wide Web, where it became so compelling and so important that it was not a question of implementing some html and http standard to share one's information, but instead a question of just missing the boat. If the GeoSpatial Web becomes as compelling as the World Wide Web, in potential if not initially in actual content, then common solutions will naturally be implemented as it is to everyone's advantage. But that potential must be able to be immediately percieved, something must be working now, or uptake will always be felt to be enforced from above.

The second issue, of large investment needed to adopt a standard, can be greatly minimized by available user friendly open source implementations of the open standards. This is in no way exclusive to proprietary implementations of open standards, and most proprietary vendors that we've talked to welcome the availability of open source implementations. The main reason for this is that it allows organizations to 'try out' new open standards with out having to fully invest with out knowing if it does bring them any advantage. After an initial evaluation phase of the standard itself, using the open source software, most organizations will complete a full evaluation of available solutions, and many times proprietary solutions will fit them best. Open standards and common solutions also benefit from many implementations, since there is more available data, making a more compelling environment. So for proprietary vendors, 'a rising tide raises all boats', even if many people choose open source solutions, the overall 'GeoSpatial Web' becomes more compelling the more people are on it. To go back to the World Wide Web, though the open source Apache Web Server has a majority of the web server market, the proprietary vendors all have much greater sales as a result of the fact that most everyone is online, which Apache enabled by greatly lowering the barrier to entry.

Additionally, open source solutions will easily operate alongside legacy systems, so that an entirely new investment is not needed to transition over a whole infrastructure. Open Source can run side by side proprietary solutions, with open source implementing the new open standards, while allowing users to keep their regular work flows and transition to a more common solution in time. The open nature of the code means that even if a certain legacy system is not already available to be integrated, it is relatively easy to modify the open code to work with the legacy code. This mitigates the risk of transition to common solutions by allowing the transition to be iterative, with everything working along the way, instead of requiring a massive upheaval.

''2.2.3 What cultural impediments and training issues are paramount at which stages of the transition? What are the solutions to them?''

Although the United States is a global leader in providing public access to data the process of collecting/creating, storing and processing these data are less open largely because vendors providing these services use secret and proprietary methods with the intent of gaining a competitive edge over their competition. This approach is rooted in traditional intellectual property protection ideals and can result in incompatibly and high costs to the government. This mindset is a significant cultural impediment to achieving common solutions for working with geospatial data and can be overcome by developing open data and software standards and promoting the benefits of this approach to the business community and government organizations.

Cultural Issues
<ul>
<li>Data Ownership vs. Data Stewardship</li>
<li>Drawing Centric vs. Data Centric (especially in CADD shops)</li>
<li>Public vs Private (or percieved to be Private).</li>
<li>Data format preferences still exist that may not coincide with the greater good.</li>
</ul>

Training Issues
<ul>
<li>Cost of use, training materials derived from open source packages vs commercial packages.</li>
<li>Simple is better, if something is easier to use, it's more likely to be used.</li>
<li>Commercial vs OpenSource</li>
</ul>

''2.2.4 From your experience, please describe the cost/benefit of coordinating the use of geographic information or optimizing NSDI components and related spatial data activities across all sectors and levels of government.''

Many current systems rely on a string of partcipants to manage a Geographic Information system. A System needs to allow individual data owners to update and maintain their respective datasets with the least amount of percieved extra work. If the process is precieved by the data owners to be additional effort on their part, it's much less likely to take hold as a standard. The process needs to be as painless as possible for the Data Steward in order for a system to be self sustaining.

Publication by Data Owners requires a few basic needs be met, such as:
<ul>
<li>Move publication and maintenance of data as close as possible to the data owners/creators.</li>
<li>Owners/creators are also responsible for approriate metadata for their respective datasets. This aids in data discovery mechanisms for the end users.</li>
<li>Responsibly for upkeep and timeliness of data should be tracable to the owners/creators by the average users.</li>
<li>User Feedback systems need to be in place for relaying of errors and/or omissions back to the data owners.</li>
</ul>

''2.2.5 What are the top three critical factors for successfully coordinating the use of geographic information or optimizing related spatial data activities?''
<ul>
<li>Data Consistency</li>
<li>Ease of Access</li>
<li>Data Currency</li>
</ul>

My list is Different . . .(actaully, might be dependant on individual GIS Functions, don't you think?)
<ul>
<li>Enabling Data Owners to Publish and Maintain their own Data</li>
<li>Data Currency</li>
<li>Ease of Use (Systems and Data)</li>
</ul>

There may be room here to describe more than one list based on different functionalities or Tasks. A list could be made for each of: Data, Systems, Access, Currency, Ease of Use, etc.

''2.2.6 What are the top three risks in coordinating the use of geographic information or optimizing related spatial data activities? How do you mitigate these risks?''
<ul>
<li>Data Accuracy</li>
<li>Data Availability</li>
<li>Data Compatability</li>
</ul>
The three biggest risks when building business practices based on shared geospatial information reflect the critical factors mentioned in 2.2.5. For shared systems to work, each proponent must be willing and able to meet a certain standard level of service that ensures the reliability and consistancy of the data provided. These data must be available in a format that is accessable to the end user regardless of software package or vendor.

''2.2.7 What are the key performance indicators related to coordinating the use of geographic information or optimizing related spatial data activities? What metrics can be obtained to measure performance and how?''
While data accuracy can be a difficult metric to measure shared spatial data by, it is probably the most important factor when relying on such data for business processes.

Easier to measure is the level of consistancy maintained by shared spatial data. Data that follows an established standard (ie. SDSFIE) can be graded based on how well it follows and implements said standard.

Another important metric for shared spatial data is the length of time required for changes made by the data steward to be reflected in the shared dataset. Minimizing this refresh time is critical if the shared datasets are to be considered an authoritative source of information.

''2.2.8 How do you retain the advantages of competition while reaping the benefits of geospatial coordination and optimization?''
Advantages of competition are perceived to be improved innovation (producing a better product) and reduced cost to the consumer. By developing and using open standards innovation is improved because of the size and diversity of the community developing the standards. Cost is also reduced because once the standards and clearly defined metrics of success are in place the cost of entry to begin developing products is reduced. Competition is important but to strengthen competition it helps if companies can compete on a level playing field that is promoted through the use of open standards.

''2.2.9 How do you ensure and manage ongoing innovation in geospatial coordination and optimization?''
The most effective way to ensure continued innovation with regard to geospatial coordination and optimization is to promote and adopt open standards for the creation/collection, storage, access, and processing of geospatial data. This includes contributing to the development of open source geospatial software. It is in the data users’ and producers’ interest to have interoperable solutions and the most effective way to accomplish this is to include them in the process of developing standards and software. The benefits of using open methods are becoming well publicized (could use a citation here). To further benefit from current open approaches it is necessary to fund research to further develop open geospatial-focused standards for improved interoperability and access. Research should also be conducted on innovative open approaches for creating and maintaining geospatial data layers in an open environment. The potential of openness in the geospatial sector is great but funded research is needed to expedite the realization of these benefits.

''2.2.10 What are the incentives and disincentives for participation in geospatial coordination and optimization as a collaboration partner, a customer and as a service provider?''

''2.2.11 How do you achieve and sustain senior management involvement and commitment to coordinating the use of geographic information or optimizing related spatial data activities?''

Display all Geographic Data in bright shinny colors... Kidding
Sustained commitment from senior management within an organization can be assured in two ways:
<ul><li>Funding</li><li>Mission</li></ul>
Tying funding to an entities' ability to create, maintain, and distribute geospatial information is the most immediate way to ensure the interest of senior management. For long term success, the organization must evolve to embrace the geospatial data lifecycle as a key component of its mission.

''2.2.12 What governance model do you use or would you recommend for coordinating the use of geographic information or optimizing related spatial data activities?''
A refined and clear cut governance model for coordinating the use of geographic information and related activities does not exist but as with developing standards this should be developed using an open process. There is a wealth of information related to governance models that can be drawn from the open source software community. The open source software community is thriving by leveraging the expertise and interests from a diverse group of individuals and a similar model can be used to benefit from and better coordinate the use of geographic information and to optimize related spatial data activities. 

''2.2.13 What is the best approach for assembling and using multiple data sets from diverse fields where scale, units of analysis and data types differ?''
The key to working with diverse data is interoperability and this can be best achieved through the use of open standards for data and software. Open source geospatial software offerings have a proven track record for often being the first to implement geospatial standards developed by the Open Geospatial Consortium (OGC). 
The inability to read a particular file format is often the factor preventing access to a particular data set. This can occur for several reasons but two common problems are an insufficient capability of a software program to read a particular file format or the inability to read a proprietary file format using incompatible software. Adopting open standards and open source software can alleviate both of these problems. Having a community of individuals and organizations build on open source software libraries can help strengthen the ability of software packages to handle a wide variety of format. A good example of this is the open source Geospatial Data Abstraction Library (GDAL) and OGR which are raster (GDAL) and vector (OGR) translator libraries. Building on open source libraries provides excellent resources for open source and proprietary software developers alike. 

''2.2.14 What geospatial cross-cutting services, best practices, interoperable technologies, and data standards exist but are not necessarily coordinated or optimized by the Federal government?''

''2.2.15 What key issues and challenges must be considered when geospatial lifecycle activities occur in a foreign country that may or may not share borders with the US? What solutions do you propose to overcome these issues and challenges?''

== ''Scenarios'' ==

=== Scenario 1 - Emergency Response: ===
''The U.S. is experiencing an “Incident of National Significance”, as defined by Homeland Security Presidential Directive 5 (HSPD-5) that has required activation of the National Response Plan (NRP). The NRP provides a framework for the coordination of Federal, state, local, private, volunteer, and Non-Governmental organizations to work together in real time to respond effectively. Under the NRP, significant Federal geospatial data and assets are mobilized and made available to the responding homeland security (HLS) community. However, significant geospatial data and assets are available at the state and local level that are not immediately available to responding Federal Departments and agencies.''

''2.3.1 Please describe the types of non-Federal geospatial data that are available at the state and local government level, as well as from private utilities and other entities that might improve the effectiveness of the NRP.''

''In your response please address any issues regarding licensing of data, the need for information sharing agreements and similar impediments to other than full and open sharing of geospatial data within the HLS community.''

''2.3.2 What activities need to be undertaken during the Preparedness phase of the emergency lifecycle to assure emergency managements are aware of the potential of geospatial data and assets to support emergency response?''

''2.3.3 What activities need to be undertaken during the Preparedness phase of the emergency lifecycle to assure that geospatial technology subject matter experts and data stewards are aware of the emergency response requirement and standard operating procedures?''

''2.3.4 During response to an Incident of National Significance, what needs to be done to assure geospatial data and assets are made available to all participants in the NRP?''
''In particular, please identify issues that must be addressed to assure state and local geospatial data and assets can be made readily available to all participants in the response?''

''2.3.5 What activities to coordinate geospatial data and assets for emergency management applications are you aware of?''

''2.3.6 What activities do you suggest be undertaken to coordinate the use of geographic information or optimize related spatial data activities for emergency management?''

''2.3.7 Geospatial data can also play a critical role in performing analyses to support pre-disaster mitigation plan development and implementation as well as support of recovery operations. Please describe key aspects of the use of geospatial data and assets for pre-disaster mitigation and recovery.''

''2.3.8 What are the key components – organizational, training, business, and technical (including fixed and mobile technology) – that establish an environment that is ready to respond (preparedness), able to respond (incident management), capable of supporting pre-disaster mitigation and post-disaster recovery analysis, and provides enhancements or lessons learned for future event management?''

=== Scenario 2 - Long Term Research Scenario: ===

''The U.S. perceives societal benefit in performing long-term research. Research is being conducted in numerous social and physical science fields such as demographics, public infrastructure, climatology, health care, economics, and crime, etc.''

''2.3.9 How can we enable the use of geospatial assets, including both structured and unstructured data (e.g. statistical, geographic, imagery, narrative, etc.) and services for the types of research described in scenario 2?''

''2.3.10 How can the use of geospatial data, technologies and spatial data analysis be leveraged in this scenario?''

''2.3.11 What are the key components – organizational, training, business, and technical – that establish an environment that is capable of leveraging geospatial data and assets to achieve research objectives?''

=== Scenario 3 - Administration and Resources Management: ===

''Federal agencies and other organizations, both individually and collectively, manage billions of dollars of resources that traditionally have not exploited geospatial assets. This encompasses human resources, facilities, supplies, and finance (including grants, contracts, and intramural resources). In the grants management arena, Federal agencies are often required by OMB and Congress to assess and report on the efficiency, effectiveness and return on investment of multiple grant programs and other expenditures made annually to meet mission goals and provide service to citizens.''
''2.3.12 How can we establish the effective and efficient use of geo-referenced or geo-enabled data and assets across organizations, for the types of activities described in scenario 3?''

''2.3.13 How can the use of geospatial data, assets and spatial data analysis be leveraged in scenario 3?''

''2.3.14 What are the key components – organizational, training, business, and technical – that establish an environment that is capable of leveraging geospatial assets to achieve operational administrative and resource management objectives?''

=== Additional Information ===
''Please feel free to provide additional information, beyond the questions found in Section 2.2 and 2.3 that you feel should be considered to meet the goals and objectives of the Geospatial Line of Business.''

Response to RFI for US Gov GeoSpatial

2006-05-03T17:17:38Z

Wiki-Cholmes:

== Introduction ==

This is a wiki version of the questions we need to answer for the RFI. Please feel free to start answering questions, and to edit the existing stuff, even without asking. It's all versioned, so we can roll back if a new change that we don't like is in. Be sure to read the full RFI, that has more about what they're looking for, at: http://www.estrategy.gov/lineofbusiness/docs/geospatial_rfi.doc

Right now we have four people who've thrown their hats in to work on this, feel free to add your name.

# Chris Holmes (interspersed time till start of may)
# Ned Horning (little time this week, start of may)
# Dave McIlhagga (start of may)
# Mike Davis (interspersed as workload permits)
# Bob Basques (as workload permits)
#

==== Notes to use ====
Just ran across this, which may be helpful as a citation of sorts: http://www.linuxdevices.com/news/NS2542131185.html
It's about a report 'examining open standards, open source software, and "open innovation." The report concludes that openness should be promoted as a matter of public policy, in order to foster innovation and economic growth in the U.S. and world economies.'

[[Bibliography of OS and Geo information]]

==== Notes on submission ====

Submission of RFI Responses
Responses to the RFI must be submitted by e-mail to GSA by 5:00 p.m. EDT, May 5th, 2006. In responding to the RFI, please use the template labeled Part II: RFI Questionnaire. This template is also available at the following URL: http://www.whitehouse.gov/omb/egov/c-6-8-glob.html. Place your responses in-line in the document, retaining the question number and question text before each answer. Your e-mail should be clearly marked in the subject line with reference to RFI-GSV06PD00089 and your organization. You are required to include a point of contact for your organization. E-mail your response in Word (version 2000 or higher) to geospatial@gsa.gov. Please do not include marketing materials with your response at this time and ensure that any sensitive or protected information is marked as such. The government will ensure this information is not released externally. The overarching objective for this RFI is information gathering and not development of possible government acquisition of products or services.

* So someone's going to have to paste from this wiki back in to the original document, and email it in.

==== More notes ====
Place any additional notes about our information here...

Note that we don't have to respond to every question. The RFI says 'If you choose not to respond to a question, indicate “no response” and identify the rationale.'

== RFI Questionnaire Section 1: Respondent Information ==

''Please provide the following information about your organization.''
''Responding Organization Name:'' Open Source GeoSpatial Foundation

''Are you responding as a:

''User organization from experience coordinating the use of geographic information or optimizing related spatial data activities''

''Vendor or consultant from experience providing products or services to help other organizations coordinate the use of geographic information or optimize related spatial data activities''

''Both''

Both

''Type of organization (e.g. Federal agency, non-profit, state, private):'' Non-Profit

''Contact information (provide a point of contact, phone number and e-mail address):''

== ''Lifecycle Activities'' ==
''The Office of Management and Budget (OMB) Circular A-161 provides direction for Federal agencies that produce, maintain, or use spatial data either directly or indirectly in the fulfillment of their respective missions. OMB Circular A-16, Section 8 describes Federal agency responsibilities and reporting requirements for collecting, using, or disseminating geographic information or carrying out related spatial data activities. These activities are identified as lifecycle activities for the purposes of this RFI.''

''Please answer the following questions from the perspective of an overall solution and approach for coordinating the use of geographic information and/or optimizing related spatial data activities. Lifecycle activities are being defined as (1) acquire, (2) process, (3) distribute, (4) use, 5) maintain, and (6) preserve spatial data. Be sure to include innovative practices, the applicability of these practices to Government and any relevant past experience.''

''2.2.1 In which data themes of national importance is there opportunity for increased effectiveness, efficiency, and cost savings potential across the Federal Government, and what is the recommended transition approach? OMB Circular A-16 framework data themes and other data themes of national significance are (1) geodetic control, (2) orthoimagery, (3) elevation and bathymetry, (4) transportation, (5) hydrography, (6) cadastral, and (7) governmental units.''

''2.2.2 What are the critical change management issues and best practices for successful transition to and full implementation of common solutions?''

A fundamental change management issue is to promote and adapt open standards for the collection (protocols), storage (file formats, media, and metadata), access, and processing of geographic data. A recently released report by the Digital Connections Council of the Committee for Economic Development, “Open Standards, Open Source, and Open Innovation: Harnessing the Benefits of Openness” (http://www.ced.org/projects/ecom.shtml#open) highlights the benefits from adapting open standards. This report found that openness can be used effectively to build standards that in turn can be used to enhance interoperability.

But standards alone are not a cure all. The Open GeoSpatial Consortium (OGC) has made great strides in developing a solid set of standards, which precisely defines a common solution that would go quite far towards true interoperability. But uptake has been slow, as few outside of the standards writers see compelling reason to upgrade, while they also see a large investment needed to adopt a standard - in the form of an upgrade to their current software, an entirely new piece of software, or significant time investment to get an open source solution running.

Both of these issues can be improved upon, which would greatly increase the chances of common solutions. The first is to provide some compelling reason to transition a current solution. While the OGC community passed by promotion of their standards to write newer, more niche ones geared towards higher overhead uses, Google Earth came along with a compelling, user friendly environment with lots of available data. Far more organizations are making their data available as KML, the Google Earth standard, than have set up a WMS, since with it they can visualize their data in ways they couldn't before. With WMS one tends to only replicate functionality that was already available, albeit in a more open way. What is needed is a compelling example of the power of interoperability, so that a new investment is attractive to stakeholders, and not merely a requirement demanded from above. The essence of this is a top down versus bottom up approach. The bottom up approach is exemplified by the World Wide Web, where it became so compelling and so important that it was not a question of implementing some html and http standard to share one's information, but instead a question of just missing the boat. If the GeoSpatial Web becomes as compelling as the World Wide Web, in potential if not initially in actual content, then common solutions will naturally be implemented as it is to everyone's advantage. But that potential must be able to be immediately percieved, something must be working now, or uptake will always be felt to be enforced from above.

The second issue, of large investment needed to adopt a standard, can be greatly minimized by available user friendly open source implementations of the open standards. This is in no way exclusive to proprietary implementations of open standards, and most proprietary vendors that we've talked to welcome the availability of open source implementations. The main reason for this is that it allows organizations to 'try out' new open standards with out having to fully invest with out knowing if it does bring them any advantage. After an initial evaluation phase of the standard itself, using the open source software, most organizations will complete a full evaluation of available solutions, and many times proprietary solutions will fit them best. Open standards and common solutions also benefit from many implementations, since there is more available data, making a more compelling environment. So for proprietary vendors, 'a rising tide raises all boats', even if many people choose open source solutions, the overall 'GeoSpatial Web' becomes more compelling the more people are on it. To go back to the World Wide Web, though the open source Apache Web Server has a majority of the web server market, the proprietary vendors all have much greater sales as a result of the fact that most everyone is online, which Apache enabled by greatly lowering the barrier to entry.

Additionally, open source solutions will easily operate alongside legacy systems, so that an entirely new investment is not needed to transition over a whole infrastructure. Open Source can run side by side proprietary solutions, with open source implementing the new open standards, while allowing users to keep their regular work flows and transition to a more common solution in time. The open nature of the code means that even if a certain legacy system is not already available to be integrated, it is relatively easy to modify the open code to work with the legacy code. This mitigates the risk of transition to common solutions by allowing the transition to be iterative, with everything working along the way, instead of requiring a massive upheaval.

''2.2.3 What cultural impediments and training issues are paramount at which stages of the transition? What are the solutions to them?''

Although the United States is a global leader in providing public access to data the process of collecting/creating, storing and processing these data are less open largely because vendors providing these services use secret and proprietary methods with the intent of gaining a competitive edge over their competition. This approach is rooted in traditional intellectual property protection ideals and can result in incompatibly and high costs to the government. This mindset is a significant cultural impediment to achieving common solutions for working with geospatial data and can be overcome by developing open data and software standards and promoting the benefits of this approach to the business community and government organizations.

Cultural Issues
<ul>
<li>Data Ownership vs. Data Stewardship</li>
<li>Drawing Centric vs. Data Centric (especially in CADD shops)</li>
<li>Public vs Private (or percieved to be Private).</li>
<li>Data format preferences still exist that may not coincide with the greater good.</li>
</ul>

Training Issues
<ul>
<li>Cost of use, training materials derived from open source packages vs commercial packages.</li>
<li>Simple is better, if something is easier to use, it's more likely to be used.</li>
<li>Commercial vs OpenSource</li>
</ul>

''2.2.4 From your experience, please describe the cost/benefit of coordinating the use of geographic information or optimizing NSDI components and related spatial data activities across all sectors and levels of government.''

Many current systems rely on a string of partcipants to manage a Geographic Information system. A System needs to allow individual data owners to update and maintain their respective datasets with the least amount of percieved extra work. If the process is precieved by the data owners to be additional effort on their part, it's much less likely to take hold as a standard. The process needs to be as painless as possible for the Data Steward in order for a system to be self sustaining.

Publication by Data Owners requires a few basic needs be met, such as:
<ul>
<li>Move publication and maintenance of data as close as possible to the data owners/creators.</li>
<li>Owners/creators are also responsible for approriate metadata for their respective datasets. This aids in data discovery mechanisms for the end users.</li>
<li>Responsibly for upkeep and timeliness of data should be tracable to the owners/creators by the average users.</li>
<li>User Feedback systems need to be in place for relaying of errors and/or omissions back to the data owners.</li>
</ul>

''2.2.5 What are the top three critical factors for successfully coordinating the use of geographic information or optimizing related spatial data activities?''
<ul>
<li>Data Consistency</li>
<li>Ease of Access</li>
<li>Data Currency</li>
</ul>

My list is Different . . .(actaully, might be dependant on individual GIS Functions, don't you think?)
<ul>
<li>Enabling Data Owners to Publish and Maintain their own Data</li>
<li>Data Currency</li>
<li>Ease of Use (Systems and Data)</li>
</ul>

There may be room here to describe more than one list based on different functionalities or Tasks. A list could be made for each of: Data, Systems, Access, Currency, Ease of Use, etc.

''2.2.6 What are the top three risks in coordinating the use of geographic information or optimizing related spatial data activities? How do you mitigate these risks?''
<ul>
<li>Data Accuracy</li>
<li>Data Availability</li>
<li>Data Compatability</li>
</ul>
The three biggest risks when building business practices based on shared geospatial information reflect the critical factors mentioned in 2.2.5. For shared systems to work, each proponent must be willing and able to meet a certain standard level of service that ensures the reliability and consistancy of the data provided. These data must be available in a format that is accessable to the end user regardless of software package or vendor.

''2.2.7 What are the key performance indicators related to coordinating the use of geographic information or optimizing related spatial data activities? What metrics can be obtained to measure performance and how?''
While data accuracy can be a difficult metric to measure shared spatial data by, it is probably the most important factor when relying on such data for business processes.

Easier to measure is the level of consistancy maintained by shared spatial data. Data that follows an established standard (ie. SDSFIE) can be graded based on how well it follows and implements said standard.

Another important metric for shared spatial data is the length of time required for changes made by the data steward to be reflected in the shared dataset. Minimizing this refresh time is critical if the shared datasets are to be considered an authoritative source of information.

''2.2.8 How do you retain the advantages of competition while reaping the benefits of geospatial coordination and optimization?''
Advantages of competition are perceived to be improved innovation (producing a better product) and reduced cost to the consumer. By developing and using open standards innovation is improved because of the size and diversity of the community developing the standards. Cost is also reduced because once the standards and clearly defined metrics of success are in place the cost of entry to begin developing products is reduced. Competition is important but to strengthen competition it helps if companies can compete on a level playing field that is promoted through the use of open standards.

''2.2.9 How do you ensure and manage ongoing innovation in geospatial coordination and optimization?''
The most effective way to ensure continued innovation with regard to geospatial coordination and optimization is to promote and adopt open standards for the creation/collection, storage, access, and processing of geospatial data. This includes contributing to the development of open source geospatial software. It is in the data users’ and producers’ interest to have interoperable solutions and the most effective way to accomplish this is to include them in the process of developing standards and software. The benefits of using open methods are becoming well publicized (could use a citation here). To further benefit from current open approaches it is necessary to fund research to further develop open geospatial-focused standards for improved interoperability and access. Research should also be conducted on innovative open approaches for creating and maintaining geospatial data layers in an open environment. The potential of openness in the geospatial sector is great but funded research is needed to expedite the realization of these benefits.

''2.2.10 What are the incentives and disincentives for participation in geospatial coordination and optimization as a collaboration partner, a customer and as a service provider?''

''2.2.11 How do you achieve and sustain senior management involvement and commitment to coordinating the use of geographic information or optimizing related spatial data activities?''

Display all Geographic Data in bright shinny colors... Kidding
Sustained commitment from senior management within an organization can be assured in two ways:
<ul><li>Funding</li><li>Mission</li></ul>
Tying funding to an entities' ability to create, maintain, and distribute geospatial information is the most immediate way to ensure the interest of senior management. For long term success, the organization must evolve to embrace the geospatial data lifecycle as a key component of its mission.

''2.2.12 What governance model do you use or would you recommend for coordinating the use of geographic information or optimizing related spatial data activities?''
A refined and clear cut governance model for coordinating the use of geographic information and related activities does not exist but as with developing standards this should be developed using an open process. There is a wealth of information related to governance models that can be drawn from the open source software community. The open source software community is thriving by leveraging the expertise and interests from a diverse group of individuals and a similar model can be used to benefit from and better coordinate the use of geographic information and to optimize related spatial data activities. 

''2.2.13 What is the best approach for assembling and using multiple data sets from diverse fields where scale, units of analysis and data types differ?''
The key to working with diverse data is interoperability and this can be best achieved through the use of open standards for data and software. Open source geospatial software offerings have a proven track record for often being the first to implement geospatial standards developed by the Open Geospatial Consortium (OGC). 
The inability to read a particular file format is often the factor preventing access to a particular data set. This can occur for several reasons but two common problems are an insufficient capability of a software program to read a particular file format or the inability to read a proprietary file format using incompatible software. Adopting open standards and open source software can alleviate both of these problems. Having a community of individuals and organizations build on open source software libraries can help strengthen the ability of software packages to handle a wide variety of format. A good example of this is the open source Geospatial Data Abstraction Library (GDAL) and OGR which are raster (GDAL) and vector (OGR) translator libraries. Building on open source libraries provides excellent resources for open source and proprietary software developers alike. 

''2.2.14 What geospatial cross-cutting services, best practices, interoperable technologies, and data standards exist but are not necessarily coordinated or optimized by the Federal government?''

''2.2.15 What key issues and challenges must be considered when geospatial lifecycle activities occur in a foreign country that may or may not share borders with the US? What solutions do you propose to overcome these issues and challenges?''

== ''Scenarios'' ==

=== Scenario 1 - Emergency Response: ===
''The U.S. is experiencing an “Incident of National Significance”, as defined by Homeland Security Presidential Directive 5 (HSPD-5) that has required activation of the National Response Plan (NRP). The NRP provides a framework for the coordination of Federal, state, local, private, volunteer, and Non-Governmental organizations to work together in real time to respond effectively. Under the NRP, significant Federal geospatial data and assets are mobilized and made available to the responding homeland security (HLS) community. However, significant geospatial data and assets are available at the state and local level that are not immediately available to responding Federal Departments and agencies.''

''2.3.1 Please describe the types of non-Federal geospatial data that are available at the state and local government level, as well as from private utilities and other entities that might improve the effectiveness of the NRP.''

''In your response please address any issues regarding licensing of data, the need for information sharing agreements and similar impediments to other than full and open sharing of geospatial data within the HLS community.''

''2.3.2 What activities need to be undertaken during the Preparedness phase of the emergency lifecycle to assure emergency managements are aware of the potential of geospatial data and assets to support emergency response?''

''2.3.3 What activities need to be undertaken during the Preparedness phase of the emergency lifecycle to assure that geospatial technology subject matter experts and data stewards are aware of the emergency response requirement and standard operating procedures?''

''2.3.4 During response to an Incident of National Significance, what needs to be done to assure geospatial data and assets are made available to all participants in the NRP?''
''In particular, please identify issues that must be addressed to assure state and local geospatial data and assets can be made readily available to all participants in the response?''

''2.3.5 What activities to coordinate geospatial data and assets for emergency management applications are you aware of?''

''2.3.6 What activities do you suggest be undertaken to coordinate the use of geographic information or optimize related spatial data activities for emergency management?''

''2.3.7 Geospatial data can also play a critical role in performing analyses to support pre-disaster mitigation plan development and implementation as well as support of recovery operations. Please describe key aspects of the use of geospatial data and assets for pre-disaster mitigation and recovery.''

''2.3.8 What are the key components – organizational, training, business, and technical (including fixed and mobile technology) – that establish an environment that is ready to respond (preparedness), able to respond (incident management), capable of supporting pre-disaster mitigation and post-disaster recovery analysis, and provides enhancements or lessons learned for future event management?''

=== Scenario 2 - Long Term Research Scenario: ===

''The U.S. perceives societal benefit in performing long-term research. Research is being conducted in numerous social and physical science fields such as demographics, public infrastructure, climatology, health care, economics, and crime, etc.''

''2.3.9 How can we enable the use of geospatial assets, including both structured and unstructured data (e.g. statistical, geographic, imagery, narrative, etc.) and services for the types of research described in scenario 2?''
''2.3.10 How can the use of geospatial data, technologies and spatial data analysis be leveraged in this scenario?''
''2.3.11 What are the key components – organizational, training, business, and technical – that establish an environment that is capable of leveraging geospatial data and assets to achieve research objectives?''

=== Scenario 3 - Administration and Resources Management: ===

''Federal agencies and other organizations, both individually and collectively, manage billions of dollars of resources that traditionally have not exploited geospatial assets. This encompasses human resources, facilities, supplies, and finance (including grants, contracts, and intramural resources). In the grants management arena, Federal agencies are often required by OMB and Congress to assess and report on the efficiency, effectiveness and return on investment of multiple grant programs and other expenditures made annually to meet mission goals and provide service to citizens.''
''2.3.12 How can we establish the effective and efficient use of geo-referenced or geo-enabled data and assets across organizations, for the types of activities described in scenario 3?''
''2.3.13 How can the use of geospatial data, assets and spatial data analysis be leveraged in scenario 3?''
''2.3.14 What are the key components – organizational, training, business, and technical – that establish an environment that is capable of leveraging geospatial assets to achieve operational administrative and resource management objectives?''

=== Additional Information ===
''Please feel free to provide additional information, beyond the questions found in Section 2.2 and 2.3 that you feel should be considered to meet the goals and objectives of the Geospatial Line of Business.''

Response to RFI for US Gov GeoSpatial

2006-05-01T22:38:16Z

Wiki-Cholmes:

Bibliography of OS and Geo information

2006-05-01T19:18:55Z

Wiki-Cholmes:

This is starting as the bibliography for a journal paper I started writing on applying open source principles to the geospatial arena. It never really finished, but it made me cite a bunch of stuff. I'll paste it all in here. Feel free to add new sources in, and to remove stuff that's not directly relevant. Hopefully it can make it easier for us to all write papers in the future.

=== References ===

Abbate, J. (1999) Inventing the Internet MIT Press, Cambridge, MA

Bar, F. and Riis, A.M. (2000) Tapping user-driven innovation: A new rationale for universal service. The Information Society, 16(2): 99-108.

Benkler, Y. (2002) Coase’s Penguin, or, Linux and The Nature of the Firm The Yale Law Journal [Vol. 112].
Bernard, L., Craglia, M., Gould, M., Kuhn, W. (2005) Towards an SDI Research Agenda In: Proceedings of the 11 EC-GIS Workshop, Sardinia, May 30-June 1, 2005.

Bleeker, J. A Design Approach for the Geospatial Web, 2005 O'Reilly Network [http://www.oreillynet.com/pub/a/network/2005/06/07/geospatialweb.html]

Bozman, J., Gillen, A., Kolodgy, C., Kusnetzky, D., Perry, R., and Shian D. (2002) Windows 2000 Versus Linux in Enterprise Computing: An IDC White Paper 2002. [http://download.microsoft.com/download/d/b/8/db8543a5-1e19-42e6-b0e3-d17ae2c2a9d2/IDC20TCO20Paper.pdf]

bridges.org (2004) Straight from the Source: Perspectives from the African Free and Open Source Software Movement. A bridges.org essay in collaboration with Tactical Technology Collective. [http://www.tacticaltech.org/files/straight_from_the_source_may04.pdf]

Brox, C., Y. Bishr, et al. (2002) Towards a geospatial data infrastructure for North Rhine Westphalia Computers, Environment and Urban Systems 26 19-37

Câmara, G. (?) Frameworks for Sustainability of GIS and Earth Observation Technologies in Developing Countries http://www.dpi.inpe.br/gilberto/present/codata_talk_camara.pdf (This was from his website, not sure if it was a talk or what...)

Castells, M., (2005) Innovation, Information Technology and the Culture of Freedom, speech at World Social Forum in Porto Alegre, 2005. [http://openflows.org/article.pl?sid=05/01/31/2028221]

Ciborra, C. U., Braa, K., Cordella, A., Dahlbom, B., Failla, A., Hanseth, O., Hepso, V., Ljungberg, J., Monteiro, E., and Simon, K. A. (2000) From control to drift: the dynamics of corporate information infrastructures. Oxford University Press, Oxford.

Dalle, J. and N. Jullien (2001) “Libre” Software: Turning Fads into Institutions, Research Policy, vol. 32, No. 1, pp. 1-11. [http://opensource.mit.edu/papers/Libre-Software.pdf]

Edney, M. H. (1991) Strategies for maintaining the democratic nature of geographic information systems. Papers and Proceedings of the Applied Geography Conferences 14, 100-108.

Georgiadou, Y., S. Puri, S. Sahay (2004), Towards a Research Agenda to Guide the Implementation of Spatial Data Infrastructures – A Case Study from India. Submitted to: International Journal of GIS, August 9, 2004 (Yola gave me this paper in Cairo, not sure if it got published.)

Groot, R. and J. McLaughlin (2000) Introduction. In: Geospatial Data Infrastructure – Concepts, Cases and Good Practice. Groot, R. and J. McLaughlin (eds.). Oxford University Press, Oxford.

Hanseth, O., and Aanestad, M., (2003) Bootstrapping networks, communities and infrastructures: on the evolution of ICT solutions in healthcare. Methods of Information in Medicine, 42, 385–391.

Hanseth, O., and Monteiro, E., (2004) Understanding information infrastructure(forthcoming book), manuscript available on [http://heim.ifi.uio.no/~oleha/ Publications/].

Hanseth, O and K Lyytinen (2005). Theorizing about the design of Information Infrastructures: design kernel theories and principles. Position Paper presented at Research Workshop on Cross-learning between Spatial Data Infrastructures and Information Infrastructures March 31 and April 1, 2005 at ITC, the Netherlands.

Harvey, David. (1989) The Condition of Postmodernity. Basil Blackwell, Oxford.

Heeks, R. (2002) Failure, Success and Improvisation of Information Systems Projects in Developing Countries, Institute for Development Policy and Management, University of Manchester, Manchester.[http://www.man.ac.uk/idpm/idpm_dp.htm#devinf_wp]

INSPIRE 2003. http://www.ec-gis.org/inspire/principles_en.html

Jambo Open Office website - http://www.o.ne.tz/pressrelease_en.php

Larsen, M.H., Holck, J., and Pedersen, M.K. (2004) The Challenges of Open Source Software in IT: Enterprise Architecture versus Total Cost of Ownership, [http://w3.msi.vxu.se/users/per/IRIS27/iris27-1135.pdf]

Lerner, J. and J. Tirole (2002) Some Simple Economics of Open Source, 50 J. INDUS. ECON. 197, 212-23.

Lessig, L. (2003) Open Source Baselines: Compared to What?, Government Policy toward Open Source Software, edited by Robert W. Hahn, AEI-Brookings Joint Center, Washington, DC. [http://www.aei.brookings.org/publications/abstract.php?pid=296]

Liebhold, M. The GeoSpatial Web: A Call to Action, 2005 O'Reilly Network [http://www.oreillynet.com/pub/a/network/2005/05/10/geospatialweb.html]

Leiner, B. M., (1997) V. G. Cerf, D. D. Clark, R. E. Kahn, L. Kleinrock, D. C. Lynch, J. Postel, L. G. Roberts, and S. Wolff: A Brief History of the Internet. http://info.isoc.org/internet-his-tory/brief.htm. Leiner et al. Brief history of the internet. (find citations on the internet)

Maguire, D. and P. A. Longley (2005). The emergence of geoportals and their role in spatial data infrastructures, Computers Environment and Urban Systems, 29, 3-14.

Masser, I. (2005) Some Priorities for SDI Related Research. In: Proceedings of the FIG Working Week and GSDI 8: From Pharaohs to Geinformatics, Cairo, 16-21 April 2005. FIG, Frederiksberg.

Gunnar M. and K-E Johnsen (2002): The One Map Project. Proceedings paper, GML Dev Days, Vancouver, July 2002.

NASA Clickworkers Project, available at <http://clickworkers.arc.nasa.gov/top>

NASA, Clickworkers Results: Crater Marking Activity. [http://clickworkers.arc.nasa.gov/documents/crater-marking.pdf].

National Research Council (2004), Down to Earth: Geographic Information for Sustainable Development in Africa Committee on the Geographic Foundation for Agenda 21, National Academy Press ( I'm not sure how to cite this. It's this national research council book thing that I got online, from the nap.edu)

Onsrud, H.J. and G. Rushton, ed. (1995) Sharing Geographic Information Systems. Center for Urban Policy Research, New Brunswick, New Jersey.

Onsrud, H. Camara, G., Campbell, J., and Sharad, N. (2004) Public Commons of Geographic Data: Research and Development Challenges. III International Conference on Geographical Information Science (GIScience 2004). Washington, 2004.

Pickles, J. (1991) Geography, GIS, and the surveillant society. Papers and Proceedings of Applied Geography Conferences 14: 80-91.

Pickles, J. ed. (1995). Ground Truth: The social implications of geographic information systems. Guilford, New York.

Rajabifard, A., I.P. Williamson, P. Holland and G. Johnstone (2000) From Local to Global SDI initiatives: a pyramid of building blocks. In: Proceedings of the 4th GSDI Conference. GSDIm Cape Town, South Africa. [http://www.gsdi.org/docs2000/capetown/abbas.rtf]

Rajabifard, A., Feeney, M. and Williamson I.P. (2001) Future Directions for the Development of Spatial Data Infrastructure. Journal of the International Institute for Aerospace Survey and Earth Sciences (ITC), The Netherlands. (Submitted)

Raymond, E.S. (1999) The Cathedral and the Bazaar, 1st Edition, O'Reilly and Associates, Sebastopol,. [ http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/]

Reichardt, M. (2005) GSDI Depends on Widespread Adoption of OGC Standards In: Proceedings of the FIG Working Week and GSDI 8: From Pharaohs to Geinformatics, Cairo, 16-21 April 2005. FIG, Frederiksberg.

Rocha, G. J. (2005) Geowiki – Enabling Collaborative Maintenance of Spatial Data, In: Proceedings of the FIG Working Week and GSDI 8: From Pharaohs to Geinformatics, Cairo, 16-21 April 2005. FIG, Frederiksberg.

Rolland, K. H., and Monteiro, E. (2002) Balancing the local and the global in infrastructural information systems. The Information Society, 18, 87–100.

Russell, B. (2003) Headmap Manifesto http://www.headmap.org

Not sure how to cite magazines:
Schonfeld, E. (2005) 'Where Google's Maps Will Take Us' Business 2.0, August 5, 2005 http://www.business2.com/b2/web/articles/0,17863,1088995,00.html

Terdiman, D. (2005) 'Hey google map this', in Wired magazine, May 16, 2005 http://www.wired.com/news/culture/0,1284,67514,00.html?tw=wn_tophead_1

Timmermans, S. and M. Berg, (1997) “Standardization in action: achieving local universality through medical protocols”, In Social studies of science, 27:273-305.

Sandvig, C. (forthcoming) Shaping Infrastructure and Innovation on the Internet: The End-to-End Network that Isn't to be in: Guston, D. and D Sarewitz. (eds.) forthcoming. Shaping Science and Technology Policy: The Next Generation of Research. University of Wisconsin Press, Madison.

Stallman, R. (2001) "The Free Software Definition,".[http://www.fsf.org/philosophy/free-sw.html]

von Hippel, E. (1988). The sources of innovation. Oxford University Press, Oxford.

von Hippel, E. (2005) Democratizing Innovation, MIT Press, Cambridge, Massachusetts.

von Hippel, E., and G. von Krogh. 2003. Open Source Software and the “Private-Collective” Innovation Model: Issues for Organization Science. Organization Science 14(2): 209–223.

Walsham, G. (1993) Interpreting information systems in organizations, John Wiley & Sons, Chichester.

Weber, S. (2004) Open Source Software in Developing Economies [http://www.ssrc.org/programs/itic/publications/ITST_materials/webernote2.pdf]

Weber, S. (2004) The Success of Open Source, Harvard University Press, Cambridge, Massachusetts.

Weber, S. Is the Open Source Software Process Sui Generis to Software, or a More General Way of Organizing the Production of Complex Knowledge Products?
[http://www.ssrc.org/programs/itic/publications/ITST_materials/webernote1.pdf]

Weerawarana, S. and Weeratunga, J. (2004) Open Source in Developing Countries SIDA, Sweden. [http://www.sida.se/Sida/jsp/polopoly.jsp?d=1265&a=23955]

Wikipedia, the Free Encyclopedia, available at <http://www.wikipedia.org>

Wytzisk, A. and A. Sliwinski (2004) Quo Vadis SDI? In: Proceedings of the 7th AGILE Conference on GI Science. Heraklion, 2004. 43-49.

Response to RFI for US Gov GeoSpatial

2006-05-01T19:12:02Z

Wiki-Cholmes:

Response to RFI for US Gov GeoSpatial

2006-05-01T17:56:15Z

Wiki-Cholmes:

Response to RFI for US Gov GeoSpatial

2006-05-01T17:55:01Z

Wiki-Cholmes:

Response to RFI for US Gov GeoSpatial

2006-05-01T17:52:23Z

Wiki-Cholmes:

Board Meeting 2006 04 28

2006-04-28T15:18:22Z

Wiki-Cholmes:

The 8th board meeting is planned for Friday, April 28, 2006 at 15:00 UTC ([http://www.timeanddate.com/worldclock/fixedtime.html?month=4&day=28&year=2006&hour=15&min=0&sec=0 fixedtime]), by phone and IRC (#osgeo) at the same time.

From Skype call : +99038275318640

To use a regular phone:
From the US: call # 1-419-753-7120 (free, long distance costs apply).
From the UK: call # 0870-119-2350 (10p/minute).

Your Conference Room Number is: 5318640.

== Agenda ==

* Appoint meeting chairperson and secretary.
* Review and approve [http://wiki.osgeo.org/index.php/Seventh_Board_Meeting#Minutes prior meeting minutes]
* Discuss and adopt [[Committee Chair Guidelines]]
* Discuss appearance at Where 2.0, get back to Nat.
* Discuss request from Humaninet
* Get a date/place for face to face OSGeo meeting?

== Minutes ==

Second VisCom Meeting

2006-04-27T15:55:09Z

Wiki-Cholmes:

=== Date and Time ===
April 27th, 2006, at 15:00 UTC ([http://www.timeanddate.com/worldclock/fixedtime.html?month=4&day=27&year=2006&hour=15&min=0&sec=0 worldclock link]) (8:00am PST)

The meeting will take place on IRC at [irc://irc.freenode.net/#osgeo #osgeo].

== Agenda ==
* Officially vote on committee membership (list still shows 'Potential Members')
* Process for press releases
* Press release topics to push and interval
* Developing a contact list for promotions (news organizations and related web sites)
* Evaluate osgeo.org web site stats
* Work out [[VisComTODO]]
* Discuss Slogans
* Start discussion on OSGeo/Project promotion potential
* mpg suggests we fork off three subteams:
** one for "marketing operations/logistics" - manages formal Marketing dept things like brochures, logos, press releases, contact lists, etc
** one for "conferences" - responsible for tracking what shows are happening, and coordinating what (if any) presence OSGeo will have there
** one for "library" - permanent archive of high-quality OSGeo-related content, e.g. slide sets about us, slides about our member projects, workshops, etc, etc, all to be used and recycled by members and the public ''(if library idea deemed worthy, mpg will humbly nominate himself for the "librarian" role)''
** one for "outreach" - chartered with responsibility of "getting the word out" to specific communities, corporate and otherwise
* mpg would like to see a (possibly informal) charter for VisCom, as he (and others?) are a little confused about the roles of VisCom versus WebCom
* confirmed we have a slot open for us at GeoWeb 2006; current default is to have mpg present
* cholmes report on Where 2.0 slots.
* ''please add your topics''

Response to RFI for US Gov GeoSpatial

2006-04-20T22:13:44Z

Wiki-Cholmes: added link to original rfi

Response to RFI for US Gov GeoSpatial

2006-04-20T02:20:58Z

Wiki-Cholmes:

Response to RFI for US Gov GeoSpatial

2006-04-17T21:09:45Z

Wiki-Cholmes: Getting started

Main Page

2006-04-17T20:52:42Z

Wiki-Cholmes:

== Introduction to the Open Source Geospatial Foundation Wiki ==
This is the community Wiki of the [http://www.osgeo.org/ Open Source Geospatial Foundation]. Please refer to the official web site at http://www.osgeo.org/ for stable documents and policies. This Wiki is the place where documents can be created collaboratively (ie. adoption processes, user hints, suggestions, committee notes, etc.). All web pages that are adopted as official documents will be moved to a CVS or SVN and subsequently appear at the [http://www.osgeo.org/ OSGeo] web site, which is the only official place for documents.

If you're wondering about how to dive in to OSGeo, what it's all about and how to get involved, see [[Getting Started]].

== OSGeo Structure ==

* [https://www.osgeo.org/content/foundation/about.html "About the Foundation"] (official officers, charter docs, etc)
* [[All Members]] -- add information about yourself
* [[Roadmap]]
* [[Mailing Lists]]

== Committees and Working Groups ==
* [[Board of Directors]] (official) - [[Board tasks]]
* [[Website Committee]] (official) - [[WebComTODO|Current WebCom tasks]]
* [[Fundraising]] Committee (official)
* [[IncCom Wiki|Incubation Committee]] (official) - [[IncubatorTODO|Current IncCom tasks]]
* [[Promotion and Visibility Committee]] (official) - [[VisComTODO|Current VisCom tasks]]
* [[Public Geospatial Data Committee]] (official; maybe needs a catchier name)
* [[Education and Curriculum Committee]] (official)
* [[Certification Committee]] (not official) - ''initial ideas stage!''

For a list of scheduled or regularly scheduled meetings of the Board Committees and Working Groups refer to the [[Foundation Calendar]].

== Current Proposals and Documents in Editing Process ==
* [[Talk:Proposed_Press_Release | Translations of Press Release]]
* [[Proposed Project Submission Process]]
* [[Like Minded Regional Organizations]]
* [[International Outreach]]
* [[OSGeo Mission]]
* [[Fundraising]]
* [[Proposed Membership Rules]]
* [[Potential Nominees for Next Membership Election]]
* [[Distribution Special Interest Groups]]
* [[Response to RFI for US Gov GeoSpatial]]

== Project requests ==
* [[Volunteers Needed]]
* [[AJAX WebMapping Project Request]]
* [[Programming Languages Project]]
* [[Cpanel Installer]]
* [[Languages maps for webs]]
* [[Maps gallery]]

== Project Tools ==
[[ OSGeo.org Project Tool FAQ]]

== Useful Notes ==
* [[Getting Started]] will help you to find about.
* [[How to Edit]] this Wiki.
* [[How to keep Track]] of what is going on in the Wiki.
* [[OSGEO:Protected page guidelines|Protected page guidelines]]

-----
[[OSGEO:About|Wiki Site Disclaimer]]

Location Intelligence 2006

2006-04-07T22:38:57Z

Wiki-Cholmes:

[http://www.locationintelligence.net/conference/ Location Intelligence] is an annual conference put on by [http://directionsmag.org Directions Magazine]. The [http://www.locationintelligence.net/agenda/ agenda] had a higher portion of OSGeo activities than previous years, as Directions is one of the bigger champions of Open Source Geospatial. There was a panel entitled 'Why Should the CXO Care About Open Source Geospatial Products?' which Gary Lang, Dave McIlhagga, and Chris Holmes sat on, in addition to Brian Timoney, who none of us had met but who complemented our points nicely.

The best [http://www.allpointsblog.com/archives/1322-Quotes-of-the-Conference.html quote] was from Gary, on a question posed to the panel: "The barriers to adoption of open source technology in geospatial are mental."

Chris Holmes also gave a [http://docs.codehaus.org/display/GEOS/Location+Intelligence+Presentation Presentation on ever-increasing ROI], available for everyone to reuse (including nice animations for you to 'borrow'). Both the panel and the [http://www.locationintelligence.net/presentations/#lipp-Chris%20Holmes presentation] were positively recieved.

As for notes from the attendees:

* Gary says:

'Many people came up to us afterwards and said how enlightening the OS panel discussion was. Of possible interest: I think we went a ways towards convincing other companies like Autodesk that maybe, just maybe, they should be moving some of their work out into open source as well. I had two conversations tonight that gave me hope that the wheels are spinning at those companies.

As long as the OSGeo continues to be seen in the current light, many things are possible.'

* Dave says

'I share Gary's feelings on this. Having done many outreach discussions re. Open source over the years -- being able to point others in the industry to a real 'entity' in OSGeo is a huge step forward.

Once we get our act together re. Outreach materials (and we will!) This message will only get better and more powerful.

Interesting event -- a significant number of companies represented here who are adopting or are in serious consideration about open source. Some big players you might not expect. Message is key right now to win over those standing on the ledge wondering if they should jump.'

* Chris concurs, he's writing this. It was a step forward, was very nice to have a single entity to point people at. Many were open to the message, are starting to get their heads around it all. This was definitely a business oriented crowd, and the thoughts were oriented more around mashups, but I only see open source becoming more and more important. Lots of good feedback from a number of individuals.

Location Intelligence 2006

2006-04-07T22:07:59Z

Wiki-Cholmes:

[http://www.locationintelligence.net/conference/ Location Intelligence] is an annual conference put on by [http://directionsmag.org Directions Magazine]. The [http://www.locationintelligence.net/agenda/ agenda] had a higher portion of OSGeo activities than previous years, as Directions is one of the bigger champions of Open Source Geospatial. There was a panel entitled 'Why Should the CXO Care About Open Source Geospatial Products?' which Gary Lang, Dave McIlhagga, and Chris Holmes sat on, in addition to Brian Timoney, who none of us had met but who complemented our points nicely.

The best [http://www.allpointsblog.com/archives/1322-Quotes-of-the-Conference.html quote] was from Gary, on a question posed to the panel: "The barriers to adoption of open source technology in geospatial are mental."

Chris Holmes also gave a [[Presentation on ever-increasing ROI]], available for everyone to reuse (including nice animations for you to 'borrow'). Both the panel and the [http://www.locationintelligence.net/presentations/#lipp-Chris%20Holmes presentation] were positively recieved.

As for notes from the attendees:

* Gary says:

'Many people came up to us afterwards and said how enlightening the OS panel discussion was. Of possible interest: I think we went a ways towards convincing other companies like Autodesk that maybe, just maybe, they should be moving some of their work out into open source as well. I had two conversations tonight that gave me hope that the wheels are spinning at those companies.

As long as the OSGeo continues to be seen in the current light, many things are possible.'

* Dave says

'I share Gary's feelings on this. Having done many outreach discussions re. Open source over the years -- being able to point others in the industry to a real 'entity' in OSGeo is a huge step forward.

Once we get our act together re. Outreach materials (and we will!) This message will only get better and more powerful.

Interesting event -- a significant number of companies represented here who are adopting or are in serious consideration about open source. Some big players you might not expect. Message is key right now to win over those standing on the ledge wondering if they should jump.'

* Chris concurs, he's writing this. It was a step forward, was very nice to have a single entity to point people at. Many were open to the message, are starting to get their heads around it all. This was definitely a business oriented crowd, and the thoughts were oriented more around mashups, but I only see open source becoming more and more important. Lots of good feedback from a number of individuals.

Promotion and Visibility Committee

2006-04-07T21:47:17Z

Wiki-Cholmes:

''('''NOTE:''' The following is all for discussion purposes, and not firmly established yet)''

The Promotion Committee will help produce input to be published by the [[Web Site Committee Motion|Web Site Committee]]. Publishing, controlling and adoption as stable documents is probably done by the latter.

To spread word and build a strong recognition of the Open Source Geospatial Foundation, foundation projects and the use of open source in geospatial applications in general every major event should be covered professionally. Smaller events and local conventions in many cases already get covered by associated members (friends of the foundation).

== Committee Website ==
The official committee web site is https://visibilitycommittee.osgeo.org/. For the time being it seems as if this Wiki is more flexible. Once stable documents are available they will move to the official committee web site.

== Tasks ==
Several levels of activity should be addressed to support advertising the OSGeo Foundation depending on the character of the event to take place.
* Web site linking [[Website Committee]]
* Create and provide paperwork (ads, flyers, posters, information brochures)
* Giveaways (focused on larger events with special OS affinity)
* [[Operate OSGeo Booth]] (large events)

Our scratchpad is currently located at the [[VisComTODO]] page.

== Committee Members ==

Potential Members:
* Jason Birch (jasonbirch@osgeo.org)
* [[User:Arnulf Christl | Arnulf Christl]] (Chair)
* Michael Gerlek (mpg@osgeo.org)
* Dave McIlhagga (dmcilhagga@dmsolutions.ca)
* Tyler Mitchell (pending)
* Markus Neteler (pending)
* Sean Sternfeldt (Sean.Sternfeldt@autodesk.com)
* Mark Lucas (mlucas17@mac.com)

== Linking ==
Links to the OSGeo Foundation web site should be related to the primary context of fostering Free and Open Source Software projects, availability of [[Public Geospatial Data Project]] and [[Free Geospatial Data]]. Both [[International Outreach]] and [[Like Minded Regional Organizations]] will establish an efficient network.

== Press Releases ==

Due to the possibility of a Slashdot affect, CollabNet operations needs to be notified 24 hours in advance of press releases whenever possible. Please email Daniel Brookshier and Michael Lavoie at the following addresses as soon as you have an aproximate time and date: dbrookshier@collab.net, mlavoie@collab.net

First [https://www.osgeo.org/content/news/news_archive/open_source_geospatial_foundation_initial_press_release.html Press Release] published 6 March 2006

== Presentations ==
Presentations, promotion and dissemination of the OSGeo Foundation principles and ideas:
* Give talks and [[Presentations]] at conferences
* Hold workshops at conventions
* [[Operate OSGeo Booth]] at exhibitions, conventions, user meetings

=== Presentation Material ===
A central document directory should feature [[Presentations]] about the OSGeo. Presentations should eventually be managed in the SVN repository of the Promotion and Visibility Project. Externals who need to get the FOSSGIS idea across can use material from this repository to build their own presentations. The material will be appropriately licensed with a free non-software license (e.g., Creative Commons licenses).

At a later stage Posters, Give Aways, Flyers, live-CD, etc. can be added (see also [[Fundraising]]).

=== Formats, Copyright, License of Documents ===
The preferred format would probably be HTML, making it easy to create links and make it searchable using the OSGeo (CN) infrastructure. (Initial discussion and collaborative editing can be done in the Wiki). Please refrain from creating PPTs, PDFs or other closed formats while OpenDocument format will be appropriate for slides. Presentations would preferably be licensed as GNU FDL, CC (or appropriate alternative) to ensure that they are freely available (please use the discussion page registered at the top of this page).

== Sticker, Caps, Promotion Stuff ==
We will want to think up some stuff to give away. This could be mugs, caps, t-shirts, etc. Probably will have to wait until the logo is done. Some slogan (slogans?) (all by [http://weblogs.java.net/blog/jive/archive/2006/02/_open_source_ge.html Jody Garnett]):
* Built on OSGeo
* OSGeo - Think way outside the box
* OSGeo: It's a Spheroid get over it

== Timetable ==
A timetable should be set up showing where OSGeo members talk, meet or give presentations. This timetable should be managed in an online planner (can CN provide for this?) and in professional map services using the OSGeo technology.

=== Future events with OSGeo Project and Foundation presence ===

==== 2006 ====
* [[FOSSGIS 2006]] conference - German language Free and Open Source Software GIS conference - 29-30 March 2006 (Bonn, Germany)
* [[Location Intelligence]], April 3-5, 2006 (San Francisco, California)
* [http://www.gita.org/events/annual/29/index.html GITA's Annual Conference 29], April 23-26, 2006 (Tampa Bay, Florida)
* [[LinuxTag 2006]] - 3-6 May 2006 (Wiesbaden, Germany) forerunner to [[Operate OSGeo Booth]]
* [http://conferences.oreilly.com/where/ Where 2.0], 13-14 June 2006, (San Jose, California)
* [http://www.geoplace.com/ GeoTec], June 18-20, 2006 (Ottawa, Ontario, Canada)
* [[AGIT 2006]] GIS convention, conference and exhibition - 5-7 July 2006 (Salzburg, Austria)
* [http://www.geoweb.org GeoWeb 2006], 24-28 July 2006 (Vancouver BC, Canada)
* [http://www.foss4g2006.org/ FOSS4G conference], 12-15 September 2006 (Lausanne, Switzerland)
* [http://www.intergeo.de/englisch/page/main/index.php Intergeo 2006] 10-12 October 2006 (Munich, Germany)
* [http://www.gsdi9.cl/index.html GSDI9] 6-10 November 2006 (Santiago, Chile)

==== 2007 ====
* [http://gislab.dirap.unipa.it/grass_meeting/grass_meeting.htm 8. Italian GRASS Users Meeting] 14-16 February 2007, Palermo, Italy

=== Event Archive ===

Promotion and Visibility Committee

2006-04-07T21:47:00Z

Wiki-Cholmes:

''('''NOTE:''' The following is all for discussion purposes, and not firmly established yet)''

The Promotion Committee will help produce input to be published by the [[Web Site Committee Motion|Web Site Committee]]. Publishing, controlling and adoption as stable documents is probably done by the latter.

To spread word and build a strong recognition of the Open Source Geospatial Foundation, foundation projects and the use of open source in geospatial applications in general every major event should be covered professionally. Smaller events and local conventions in many cases already get covered by associated members (friends of the foundation).

== Committee Website ==
The official committee web site is https://visibilitycommittee.osgeo.org/. For the time being it seems as if this Wiki is more flexible. Once stable documents are available they will move to the official committee web site.

== Tasks ==
Several levels of activity should be addressed to support advertising the OSGeo Foundation depending on the character of the event to take place.
* Web site linking [[Website Committee]]
* Create and provide paperwork (ads, flyers, posters, information brochures)
* Giveaways (focused on larger events with special OS affinity)
* [[Operate OSGeo Booth]] (large events)

Our scratchpad is currently located at the [[VisComTODO]] page.

== Committee Members ==

Potential Members:
* Jason Birch (jasonbirch@osgeo.org)
* [[User:Arnulf Christl | Arnulf Christl]] (Chair)
* Michael Gerlek (mpg@osgeo.org)
* Dave McIlhagga (dmcilhagga@dmsolutions.ca)
* Tyler Mitchell (pending)
* Markus Neteler (pending)
* Sean Sternfeldt (Sean.Sternfeldt@autodesk.com)
* Mark Lucas (mlucas17@mac.com)

== Linking ==
Links to the OSGeo Foundation web site should be related to the primary context of fostering Free and Open Source Software projects, availability of [[Public Geospatial Data Project]] and [[Free Geospatial Data]]. Both [[International Outreach]] and [[Like Minded Regional Organizations]] will establish an efficient network.

== Press Releases ==

Due to the possibility of a Slashdot affect, CollabNet operations needs to be notified 24 hours in advance of press releases whenever possible. Please email Daniel Brookshier and Michael Lavoie at the following addresses as soon as you have an aproximate time and date: dbrookshier@collab.net, mlavoie@collab.net

First [https://www.osgeo.org/content/news/news_archive/open_source_geospatial_foundation_initial_press_release.html Press Release] published 6 March 2006

== Presentations ==
Presentations, promotion and dissemination of the OSGeo Foundation principles and ideas:
* Give talks and [[Presentations]] at conferences
* Hold workshops at conventions
* [[Operate OSGeo Booth]] at exhibitions, conventions, user meetings

=== Presentation Material ===
A central document directory should feature [[Presentations]] about the OSGeo. Presentations should eventually be managed in the SVN repository of the Promotion and Visibility Project. Externals who need to get the FOSSGIS idea across can use material from this repository to build their own presentations. The material will be appropriately licensed with a free non-software license (e.g., Creative Commons licenses).

At a later stage Posters, Give Aways, Flyers, live-CD, etc. can be added (see also [[Fundraising]]).

=== Formats, Copyright, License of Documents ===
The preferred format would probably be HTML, making it easy to create links and make it searchable using the OSGeo (CN) infrastructure. (Initial discussion and collaborative editing can be done in the Wiki). Please refrain from creating PPTs, PDFs or other closed formats while OpenDocument format will be appropriate for slides. Presentations would preferably be licensed as GNU FDL, CC (or appropriate alternative) to ensure that they are freely available (please use the discussion page registered at the top of this page).

== Sticker, Caps, Promotion Stuff ==
We will want to think up some stuff to give away. This could be mugs, caps, t-shirts, etc. Probably will have to wait until the logo is done. Some slogan (slogans?) (all by [http://weblogs.java.net/blog/jive/archive/2006/02/_open_source_ge.html Jody Garnett]):
* Built on OSGeo
* OSGeo - Think way outside the box
* OSGeo: It's a Spheroid get over it

== Timetable ==
A timetable should be set up showing where OSGeo members talk, meet or give presentations. This timetable should be managed in an online planner (can CN provide for this?) and in professional map services using the OSGeo technology.

=== Future events with OSGeo Project and Foundation presence ===

==== 2006 ====
* [[FOSSGIS 2006]] conference - German language Free and Open Source Software GIS conference - 29-30 March 2006 (Bonn, Germany)
* [Location Intelligence], April 3-5, 2006 (San Francisco, California)
* [http://www.gita.org/events/annual/29/index.html GITA's Annual Conference 29], April 23-26, 2006 (Tampa Bay, Florida)
* [[LinuxTag 2006]] - 3-6 May 2006 (Wiesbaden, Germany) forerunner to [[Operate OSGeo Booth]]
* [http://conferences.oreilly.com/where/ Where 2.0], 13-14 June 2006, (San Jose, California)
* [http://www.geoplace.com/ GeoTec], June 18-20, 2006 (Ottawa, Ontario, Canada)
* [[AGIT 2006]] GIS convention, conference and exhibition - 5-7 July 2006 (Salzburg, Austria)
* [http://www.geoweb.org GeoWeb 2006], 24-28 July 2006 (Vancouver BC, Canada)
* [http://www.foss4g2006.org/ FOSS4G conference], 12-15 September 2006 (Lausanne, Switzerland)
* [http://www.intergeo.de/englisch/page/main/index.php Intergeo 2006] 10-12 October 2006 (Munich, Germany)
* [http://www.gsdi9.cl/index.html GSDI9] 6-10 November 2006 (Santiago, Chile)

==== 2007 ====
* [http://gislab.dirap.unipa.it/grass_meeting/grass_meeting.htm 8. Italian GRASS Users Meeting] 14-16 February 2007, Palermo, Italy

=== Event Archive ===

Requesting an Area Mailing List

2006-03-31T23:35:23Z

Wiki-Cholmes:

OSGeo hopes to support a variety of area and language specific groups.

The first way we do this is by providing 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 you would like a local list, just email [[User:DBrookshier Daniel Brookshier]], who can create a list at mail.osgeo.org

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.

International Outreach

2006-03-31T16:34:41Z

Wiki-Cholmes:

At it's formation, the Open Source Geospatial Foundation agreed it was important that it be very international, and represent and weld together open source geospatial activities around the globe.
What is less clear is how to make this happen in practical terms. In order to provide a venue for more detailed discussion of international outreach, a mailing list (international-discuss at osgeo.org) has been created.

Some topics it might try and address are:
* organizing translation of documents such as press releases, and osgeo.org web pages.
* identifying [[Like Minded Regional Organizations]], and making recommendations on how OSGeo ought to relate to them.
* creating non-english mailing lists and local news pages.
* recommending to the board what formal committees, projects or other mechanisms ought to be created
* supporting translation of software packages.
* publicizing projects, conferences and other activities

For the time being (February 2006) international-discuss is just a discussion list for a broad topic area, and not formally designated as a committee with members, a chair and reporting responsibility to the board.

If a local area group is interested in having a local discuss list, please see [[Requesting an Area Mailing List]].

To subscribe send mail to international-discuss-subscribe at osgeo.org.

== See also ==

[[Promotion and Visibility Committee]]