OSGeo - User contributions [en]

Google Summer of Code

2015-02-20T13:03:28Z

Wiki-HamishBowman: Redirected page to Google Summer of Code 2015

#REDIRECT [[Google Summer of Code 2015]]

Live GIS Disc Press Release 54

2014-08-24T03:34:10Z

Wiki-HamishBowman: /* About OSGeo-Live */

= OSGeo-Live 8.0 Released =

25 August 2014

Version 8.0 of the [http://live.osgeo.org OSGeo-Live GIS software collection] has been released, featuring over 50 open source, standards compliant geospatial applications.

==Release Highlights==

; Lubuntu 14.04.1 LTS
: We have moved from Xubuntu to the lighter Lubuntu base operating system, which starts up faster, requires less RAM, and uses less disk space, making it a better choice for running in a Virtual Machine or from a LiveDVD.
: We have upgraded to the latest 14.04.1 stable Long Term Support (LTS) release. LTS releases are put out every 2 years by Ubuntu.

; Debian packaging
: We have steadily been moving more of our projects to .deb packaging, which makes it easier to install programs on debian based systems such as OSGeo-Live, and allows application of post-release fixes if required.

; Applications
: 34 geospatial programs have been updated to newer versions.

==About OSGeo-Live==
OSGeo-Live is a self-contained bootable DVD, USB flash drive and Virtual Machine, pre-installed with robust open source geospatial software, which can be trialled without installing anything. It includes:

* Over 50 quality geospatial Open Source applications installed and pre-configured
* Free world maps and sample datasets
* Project Overview and step-by-step Quickstart for each application
* Lightning presentation of all applications, along with speaker's script
* Overviews of key OGC standards
* Translations to multiple languages

Homepage: http://live.osgeo.org

Download details: http://live.osgeo.org/en/download.html

Post release glitches collected here: http://wiki.osgeo.org/wiki/Live_GIS_Disc/Errata/8.0

== Credits ==

Over 180 people have directly helped with OSGeo-Live packaging, documenting and translating, and thousands have been involved in building the packaged software.

Developers, packagers, documenters and translators include:

Activity Workshop, Agustin Diez, Aikaterini Kapsampeli, Alan Beccati, Alan Boudreault, Alessandro Furieri, Alexander Bruy, Alexander Kleshnin, Alexander Muriy, Alexandre Dube, Alexey Ardyakov, Alex Mandel, Amy Gao, Andrea Antonello, Andrea Yanza, Andrey Syrokomskiy, Andry Rustanto, Angelos Tzotsos, Anna Munoz, Antonio Falciano, Anton Novichikhin, Anton Patrushev, Argyros Argyridis, Ariel Nunez, Assumpcio Termens, Astrid Emde, Barry Rowlingson, Benjamin Pross, Brian Hamlin, Bruno Binet, Bu Kun, Cameron Shorter, Christophe Tufféry, Christos Iossifidis, Cristhian Pin, Damian Wojslaw, Dane Springmeyer, Daniel Kastl, Danilo Bretschneider, Daria Svidzinska, David Mateos, Denis Rykov, Diego Gonzalez, Diego Migliavacca, Dimitar Misev, Dmitry Baryshnikov, Dominik Helle, Edgar Soldin, Eike Hinderk Jürrens, Elena Mezzini, Eric Lemoine, Erika Pillu, Estela Llorente, Etienne Delay, Etienne Dube, Evgeny Nikulin, Fran Boon, Francois Prunayre, Frank Gasdorf, Frank Warmerdam, Friedjoff Trautwein, Gavin Treadgold, Giuseppe Calamita, Grald Fenoy, Grigory Rozhentsov, Guy Griffiths, Hamish Bowman, Haruyuki Seki, Henry Addo, Hernan Olivera, Hirofumi Hayashi, Howard Butler, Hyeyeong Choe, Ian Edwards, Ian Turton, Ilya Filippov, Jackie Ng, Jan Drewnak, Jane Lewis, Javier Rodrigo, Javier Sanchez, Jesus Gomez, Jim Klassen, Jing Wang, Jinsongdi Yu, Jody Garnett, Johan Van de Wauw, John Bryant, Jorge Arevalo, Jorge Sanz, Jose Antonio Canalejo, Jose Vicente Higon, Judit Mays, Klokan Petr Pridal, Ko Nagase, Kristof Lange, kuzkok, Lance McKee, Lars Lingner, Luca Delucchi, Lucia Sanjaime, Mage Whopper, Manuel Grizonnet, Marc-Andre Barbeau, Marco Curreli, Marco Puppin, Marc Torres, Margherita Di Leo, Maria Vakalopoulou, Mario Andino, Mark Leslie, Massimo Di Stefano, Matthias Streulens, Mauricio Miranda, Mauricio Pazos, Maxim Dubinin, Michael Michaud, Michael Owonibi, Micha Silver, Mike Adair, Milena Nowotarska, M Iqnaul Haq Siregar, Nacho Varela, Nadiia Gorash, Nathaniel V. Kelso, Ned Horning, Nobusuke Iwasaki, Oliver Tonnhofer, Oscar Fonts, Otto Dassau, Pasquale Di Donato, Patric Hafner, Paul Meems, Pavel, Pedro-Juan Ferrer, Pirmin Kalberer, Raf Roset, Regina Obe, Ricardo Pinho, Roald de Wit, Roberta Fagandini, Roberto Antolin, Roger Veciana, Ruth Schoenbuchner, Samuel Mesa, Scott Penrose, Sergey Grachev, Sergio Banos, Simon Cropper, Simon Pigot, Stefan A. Tzeggai, Stefan Hansen, Stefan Steiniger, Stephan Meissl, Steve Lime, Takayuki Nuimura, Thierry Badard, Thomas Baschetti, Thomas Gratier, Tom Kralidis, Toshikazu Seto, Trevor Wekel, Valenty Gonzalez, Vera, Xianfeng Song, Yoichi Kayama, Zhengfan Lin

==Sponsoring organisations==

* [http://www.osgeo.org The Open Source Geospatial Foundation] provides development & hosting infrastructure for OSGeo-Live and many of the included applications.
* [http://www.lisasoft.com LISAsoft] provides sustaining resources and staff toward management and packaging.
* [http://ice.ucdavis.edu Information Center for the Environment (ICE)] at the University of California, Davis provides hardware resources and development support.
* [http://www.ntua.gr Remote Sensing Laboratory at the National Technical University of Athens], provides hardware resources and development support.
* The [http://wiki.debian.org/DebianGis DebianGIS] and [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] teams provide and quality-assure many of the core packages.

[[Category: Live-demo]]

Live GIS Disc FAQ

2014-08-24T02:46:47Z

Wiki-HamishBowman: /* Hardware Drivers */

''For the public good and for your own future reference please record any FAQs here, even if you can only supply the '''Q'''''

== Getting help ==

* '''''Q''''': How can I find the answer to a question which isn't here?
* '''''A''''': Use the search tool in the [http://news.gmane.org/gmane.comp.gis.osgeo.livedemo mailing list archives], or put it here and wait for someone else to fill in the '''''A:'''''.

See also [[Live GIS Disc/Errata/8.0]]

== Usage ==

=== Getting started ===

* '''''Q''''': What's the live user's name and password?
* '''''A''''': user/user. See the passwords.txt file on the desktop for application specific database user/passwords.

== Hardware Drivers ==

* '''''Q''''': How do I get my Wifi working?
* '''''A''''': Due to licensing issues a number of proprietary firmwares can not be included on the disc, you must download them yourself. We don't have the right to redistrubute them.

:* You will probably need a wired network connection to download the drivers.

Start button → Preferences → Aditional Drivers

It will search for available drivers ... this will take a little while.

Select the driver if you wish, and hit "Apply Changes". If you do not have a working network connection this will likely fail without telling you why.

* After the drivers are installed you can look in /var/cache/apt/archives/ for the deb packages, copy them over to another USB drive, then upon a fresh boot copy them back there and use 'apt-get' to install them. If you mount the other USB drive and the OSGeoLive USB drive on another computer, you can even copy these files into a directory in the Live's USB. These will then be available in the (for example) /cdrom/extra_debs directory. You could even stash a little script in there to install it all automatically.

== Customizing ==

* '''''Q''''': How do I set the drive volume name on the live USB drive?
* '''''A''''': From a Linux computer, plug it in and mount it, then:
# limited to 11 single byte characters
IMAGE_NAME=OSGeoLive80

# find devivce and mount name
# for me it is /dev/sdd1 and /media/0FB5-AA29
df -h

# unmount it
umount /media/0FB5-AA29

# check the label
mlabel -i /dev/sdd1 -s ::

# set the label
mlabel -i /dev/sdd1 ::"$IMAGE_NAME"

== Administration ==

* '''''Q''''': What's the root password?
* '''''A''''': There isn't one. To run commands as root type <tt>`sudo <command>`</tt> in a terminal. To become root type <tt>`sudo - su`</tt>. Enter the user's password when prompted.

* '''''Q''''': How do I get my dual monitors to span instead of mirror with xUbuntu?
* '''''A''''': Go to the Applications → Settings menu and use the <tt>`arandr`</tt> program to drag them apart, then click the tick/check button to apply (once you start the program it's pretty obvious, the program name on the other hand is not so obvious :) For the OSGeo 5.5 Live DVD and earlier you'll have to install it yourself via Synaptic or the Ubuntu Software Center.
: [http://screenshots.debian.net/screenshots/a/arandr/2238_large.png ARandR screenshot]

* '''''Q''''': How do I ssh into the Live Disc?
* '''''A''''': You must first install the openssh-server package:
sudo apt-get install openssh-server

[https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1015348 Because of a bug in Ubuntu 12.04] you may also need to run:
sudo initctl reload-configuration
sudo service ssh restart

: '''Important''': If enabling remote login access you really should change the user account's default password with the <tt>passwd</tt> command.

== Building the disc ==

* '''''Q''''': How do I roll my own version of the disc?
* '''''A''''': See the [[Live GIS Build]] wiki page

* '''''Q''''': This app is great! How do I install it on my Ubuntu system without installing everything else?
* '''''A''''': All the install scripts can be found in the ~/gisvm/bin/ directory on the disc.

[[Category: Live-demo]]

Live GIS Disc FAQ

2014-08-24T01:49:09Z

Wiki-HamishBowman: /* Hardware Drivers */

''For the public good and for your own future reference please record any FAQs here, even if you can only supply the '''Q'''''

== Getting help ==

* '''''Q''''': How can I find the answer to a question which isn't here?
* '''''A''''': Use the search tool in the [http://news.gmane.org/gmane.comp.gis.osgeo.livedemo mailing list archives], or put it here and wait for someone else to fill in the '''''A:'''''.

See also [[Live GIS Disc/Errata/8.0]]

== Usage ==

=== Getting started ===

* '''''Q''''': What's the live user's name and password?
* '''''A''''': user/user. See the passwords.txt file on the desktop for application specific database user/passwords.

== Hardware Drivers ==

* '''''Q''''': How do I get my Wifi working?
* '''''A''''': Due to licensing issues a number of proprietary firmwares can not be included on the disc, you must download them yourself. We don't have the right to redistrubute them.

:* You will probably need a wired network connection to download the drivers.

Start button → Preferences → Aditional Drivers

It will search for available drivers ... this will take a little while.

Select the driver if you wish, and hit "Apply Changes". If you do not have a working network connection this will likely fail without telling you why.

== Customizing ==

* '''''Q''''': How do I set the drive volume name on the live USB drive?
* '''''A''''': From a Linux computer, plug it in and mount it, then:
# limited to 11 single byte characters
IMAGE_NAME=OSGeoLive80

# find devivce and mount name
# for me it is /dev/sdd1 and /media/0FB5-AA29
df -h

# unmount it
umount /media/0FB5-AA29

# check the label
mlabel -i /dev/sdd1 -s ::

# set the label
mlabel -i /dev/sdd1 ::"$IMAGE_NAME"

== Administration ==

* '''''Q''''': What's the root password?
* '''''A''''': There isn't one. To run commands as root type <tt>`sudo <command>`</tt> in a terminal. To become root type <tt>`sudo - su`</tt>. Enter the user's password when prompted.

* '''''Q''''': How do I get my dual monitors to span instead of mirror with xUbuntu?
* '''''A''''': Go to the Applications → Settings menu and use the <tt>`arandr`</tt> program to drag them apart, then click the tick/check button to apply (once you start the program it's pretty obvious, the program name on the other hand is not so obvious :) For the OSGeo 5.5 Live DVD and earlier you'll have to install it yourself via Synaptic or the Ubuntu Software Center.
: [http://screenshots.debian.net/screenshots/a/arandr/2238_large.png ARandR screenshot]

* '''''Q''''': How do I ssh into the Live Disc?
* '''''A''''': You must first install the openssh-server package:
sudo apt-get install openssh-server

[https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1015348 Because of a bug in Ubuntu 12.04] you may also need to run:
sudo initctl reload-configuration
sudo service ssh restart

: '''Important''': If enabling remote login access you really should change the user account's default password with the <tt>passwd</tt> command.

== Building the disc ==

* '''''Q''''': How do I roll my own version of the disc?
* '''''A''''': See the [[Live GIS Build]] wiki page

* '''''Q''''': This app is great! How do I install it on my Ubuntu system without installing everything else?
* '''''A''''': All the install scripts can be found in the ~/gisvm/bin/ directory on the disc.

[[Category: Live-demo]]

Live GIS Disc FAQ

2014-08-24T01:36:08Z

Wiki-HamishBowman: /* Hardware Drivers */

''For the public good and for your own future reference please record any FAQs here, even if you can only supply the '''Q'''''

== Getting help ==

* '''''Q''''': How can I find the answer to a question which isn't here?
* '''''A''''': Use the search tool in the [http://news.gmane.org/gmane.comp.gis.osgeo.livedemo mailing list archives], or put it here and wait for someone else to fill in the '''''A:'''''.

See also [[Live GIS Disc/Errata/8.0]]

== Usage ==

=== Getting started ===

* '''''Q''''': What's the live user's name and password?
* '''''A''''': user/user. See the passwords.txt file on the desktop for application specific database user/passwords.

== Hardware Drivers ==

* '''''Q''''': How do I get my Wifi working?
* '''''A''''': Due to legal and licensing issues a number of proprietary firmwares can not be included on the disc, you must download them yourself. We don't have the right to redistrubute them.

:* You will probably need a wired network connection to download the drivers.

Start button → Preferences → Aditional Drivers

It will search for available drivers ... this will take a little while.

Select the driver if you wish, and hit "Apply Changes". If you do not have a working network connection this will likely fail without telling you why.

== Customizing ==

* '''''Q''''': How do I set the drive volume name on the live USB drive?
* '''''A''''': From a Linux computer, plug it in and mount it, then:
# limited to 11 single byte characters
IMAGE_NAME=OSGeoLive80

# find devivce and mount name
# for me it is /dev/sdd1 and /media/0FB5-AA29
df -h

# unmount it
umount /media/0FB5-AA29

# check the label
mlabel -i /dev/sdd1 -s ::

# set the label
mlabel -i /dev/sdd1 ::"$IMAGE_NAME"

== Administration ==

* '''''Q''''': What's the root password?
* '''''A''''': There isn't one. To run commands as root type <tt>`sudo <command>`</tt> in a terminal. To become root type <tt>`sudo - su`</tt>. Enter the user's password when prompted.

* '''''Q''''': How do I get my dual monitors to span instead of mirror with xUbuntu?
* '''''A''''': Go to the Applications → Settings menu and use the <tt>`arandr`</tt> program to drag them apart, then click the tick/check button to apply (once you start the program it's pretty obvious, the program name on the other hand is not so obvious :) For the OSGeo 5.5 Live DVD and earlier you'll have to install it yourself via Synaptic or the Ubuntu Software Center.
: [http://screenshots.debian.net/screenshots/a/arandr/2238_large.png ARandR screenshot]

* '''''Q''''': How do I ssh into the Live Disc?
* '''''A''''': You must first install the openssh-server package:
sudo apt-get install openssh-server

[https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1015348 Because of a bug in Ubuntu 12.04] you may also need to run:
sudo initctl reload-configuration
sudo service ssh restart

: '''Important''': If enabling remote login access you really should change the user account's default password with the <tt>passwd</tt> command.

== Building the disc ==

* '''''Q''''': How do I roll my own version of the disc?
* '''''A''''': See the [[Live GIS Build]] wiki page

* '''''Q''''': This app is great! How do I install it on my Ubuntu system without installing everything else?
* '''''A''''': All the install scripts can be found in the ~/gisvm/bin/ directory on the disc.

[[Category: Live-demo]]

Live GIS Disc FAQ

2014-08-24T01:35:10Z

Wiki-HamishBowman: /* Hardware Drivers */

''For the public good and for your own future reference please record any FAQs here, even if you can only supply the '''Q'''''

== Getting help ==

* '''''Q''''': How can I find the answer to a question which isn't here?
* '''''A''''': Use the search tool in the [http://news.gmane.org/gmane.comp.gis.osgeo.livedemo mailing list archives], or put it here and wait for someone else to fill in the '''''A:'''''.

See also [[Live GIS Disc/Errata/8.0]]

== Usage ==

=== Getting started ===

* '''''Q''''': What's the live user's name and password?
* '''''A''''': user/user. See the passwords.txt file on the desktop for application specific database user/passwords.

== Hardware Drivers ==

* '''''Q''''': How do I get my Wifi working?
* '''''A''''': Due to legal and licensing issues a number of proprietary firmwares can not be included on the disc, you must download them yourself. We don't have the right to redistrubute them.

:* You will probably need a wired network connection to download the drivers.

Start button → Preferences → Aditional Drivers

It will search for available drivers ... this will take a little while.

Select the driver if you wish, and hit "apply". If you do not have a working network connection this will likely fail without telling you why.

== Customizing ==

* '''''Q''''': How do I set the drive volume name on the live USB drive?
* '''''A''''': From a Linux computer, plug it in and mount it, then:
# limited to 11 single byte characters
IMAGE_NAME=OSGeoLive80

# find devivce and mount name
# for me it is /dev/sdd1 and /media/0FB5-AA29
df -h

# unmount it
umount /media/0FB5-AA29

# check the label
mlabel -i /dev/sdd1 -s ::

# set the label
mlabel -i /dev/sdd1 ::"$IMAGE_NAME"

== Administration ==

* '''''Q''''': What's the root password?
* '''''A''''': There isn't one. To run commands as root type <tt>`sudo <command>`</tt> in a terminal. To become root type <tt>`sudo - su`</tt>. Enter the user's password when prompted.

* '''''Q''''': How do I get my dual monitors to span instead of mirror with xUbuntu?
* '''''A''''': Go to the Applications → Settings menu and use the <tt>`arandr`</tt> program to drag them apart, then click the tick/check button to apply (once you start the program it's pretty obvious, the program name on the other hand is not so obvious :) For the OSGeo 5.5 Live DVD and earlier you'll have to install it yourself via Synaptic or the Ubuntu Software Center.
: [http://screenshots.debian.net/screenshots/a/arandr/2238_large.png ARandR screenshot]

* '''''Q''''': How do I ssh into the Live Disc?
* '''''A''''': You must first install the openssh-server package:
sudo apt-get install openssh-server

[https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1015348 Because of a bug in Ubuntu 12.04] you may also need to run:
sudo initctl reload-configuration
sudo service ssh restart

: '''Important''': If enabling remote login access you really should change the user account's default password with the <tt>passwd</tt> command.

== Building the disc ==

* '''''Q''''': How do I roll my own version of the disc?
* '''''A''''': See the [[Live GIS Build]] wiki page

* '''''Q''''': This app is great! How do I install it on my Ubuntu system without installing everything else?
* '''''A''''': All the install scripts can be found in the ~/gisvm/bin/ directory on the disc.

[[Category: Live-demo]]

Live GIS Disc FAQ

2014-08-24T01:34:15Z

Wiki-HamishBowman: wifi

''For the public good and for your own future reference please record any FAQs here, even if you can only supply the '''Q'''''

== Getting help ==

* '''''Q''''': How can I find the answer to a question which isn't here?
* '''''A''''': Use the search tool in the [http://news.gmane.org/gmane.comp.gis.osgeo.livedemo mailing list archives], or put it here and wait for someone else to fill in the '''''A:'''''.

See also [[Live GIS Disc/Errata/8.0]]

== Usage ==

=== Getting started ===

* '''''Q''''': What's the live user's name and password?
* '''''A''''': user/user. See the passwords.txt file on the desktop for application specific database user/passwords.

== Hardware Drivers ==

* '''''Q''''': How do I get my Wifi working?
* '''''A''''': Due to legal and licensing issues a number of proprietary firmwares can not be included on the disc, you must download them yourself. We don't have the right to redistrubute them.

You will probably need a wired network connection to do download the drivers.

Start button → Preferences → Aditional Drivers

It will search for available drivers ... this will take a little while.

Select the driver if you wish, and hit "apply". If you do not have a working network connection this will likely fail without telling you why.

== Customizing ==

* '''''Q''''': How do I set the drive volume name on the live USB drive?
* '''''A''''': From a Linux computer, plug it in and mount it, then:
# limited to 11 single byte characters
IMAGE_NAME=OSGeoLive80

# find devivce and mount name
# for me it is /dev/sdd1 and /media/0FB5-AA29
df -h

# unmount it
umount /media/0FB5-AA29

# check the label
mlabel -i /dev/sdd1 -s ::

# set the label
mlabel -i /dev/sdd1 ::"$IMAGE_NAME"

== Administration ==

* '''''Q''''': What's the root password?
* '''''A''''': There isn't one. To run commands as root type <tt>`sudo <command>`</tt> in a terminal. To become root type <tt>`sudo - su`</tt>. Enter the user's password when prompted.

* '''''Q''''': How do I get my dual monitors to span instead of mirror with xUbuntu?
* '''''A''''': Go to the Applications → Settings menu and use the <tt>`arandr`</tt> program to drag them apart, then click the tick/check button to apply (once you start the program it's pretty obvious, the program name on the other hand is not so obvious :) For the OSGeo 5.5 Live DVD and earlier you'll have to install it yourself via Synaptic or the Ubuntu Software Center.
: [http://screenshots.debian.net/screenshots/a/arandr/2238_large.png ARandR screenshot]

* '''''Q''''': How do I ssh into the Live Disc?
* '''''A''''': You must first install the openssh-server package:
sudo apt-get install openssh-server

[https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1015348 Because of a bug in Ubuntu 12.04] you may also need to run:
sudo initctl reload-configuration
sudo service ssh restart

: '''Important''': If enabling remote login access you really should change the user account's default password with the <tt>passwd</tt> command.

== Building the disc ==

* '''''Q''''': How do I roll my own version of the disc?
* '''''A''''': See the [[Live GIS Build]] wiki page

* '''''Q''''': This app is great! How do I install it on my Ubuntu system without installing everything else?
* '''''A''''': All the install scripts can be found in the ~/gisvm/bin/ directory on the disc.

[[Category: Live-demo]]

Live GIS Disc FAQ

2014-08-24T00:44:42Z

Wiki-HamishBowman: usb label

''For the public good and for your own future reference please record any FAQs here, even if you can only supply the '''Q'''''

== Getting help ==

* '''''Q''''': How can I find the answer to a question which isn't here?
* '''''A''''': Use the search tool in the [http://news.gmane.org/gmane.comp.gis.osgeo.livedemo mailing list archives], or put it here and wait for someone else to fill in the '''''A:'''''.

See also [[Live GIS Disc/Errata/8.0]]

== Usage ==

=== Getting started ===

* '''''Q''''': What's the live user's name and password?
* '''''A''''': user/user. See the passwords.txt file on the desktop for application specific database user/passwords.

== Customizing ==

* '''''Q''''': How do I set the drive volume name on the live USB drive?
* '''''A''''': From a Linux computer, plug it in and mount it, then:
# limited to 11 single byte characters
IMAGE_NAME=OSGeoLive80

# find devivce and mount name
# for me it is /dev/sdd1 and /media/0FB5-AA29
df -h

# unmount it
umount /media/0FB5-AA29

# check the label
mlabel -i /dev/sdd1 -s ::

# set the label
mlabel -i /dev/sdd1 ::"$IMAGE_NAME"

== Administration ==

* '''''Q''''': What's the root password?
* '''''A''''': There isn't one. To run commands as root type <tt>`sudo <command>`</tt> in a terminal. To become root type <tt>`sudo - su`</tt>. Enter the user's password when prompted.

* '''''Q''''': How do I get my dual monitors to span instead of mirror with xUbuntu?
* '''''A''''': Go to the Applications → Settings menu and use the <tt>`arandr`</tt> program to drag them apart, then click the tick/check button to apply (once you start the program it's pretty obvious, the program name on the other hand is not so obvious :) For the OSGeo 5.5 Live DVD and earlier you'll have to install it yourself via Synaptic or the Ubuntu Software Center.
: [http://screenshots.debian.net/screenshots/a/arandr/2238_large.png ARandR screenshot]

* '''''Q''''': How do I ssh into the Live Disc?
* '''''A''''': You must first install the openssh-server package:
sudo apt-get install openssh-server

[https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1015348 Because of a bug in Ubuntu 12.04] you may also need to run:
sudo initctl reload-configuration
sudo service ssh restart

: '''Important''': If enabling remote login access you really should change the user account's default password with the <tt>passwd</tt> command.

== Building the disc ==

* '''''Q''''': How do I roll my own version of the disc?
* '''''A''''': See the [[Live GIS Build]] wiki page

* '''''Q''''': This app is great! How do I install it on my Ubuntu system without installing everything else?
* '''''A''''': All the install scripts can be found in the ~/gisvm/bin/ directory on the disc.

[[Category: Live-demo]]

Live GIS Disc FAQ

2014-08-23T09:12:21Z

Wiki-HamishBowman: /* Getting help */

Live GIS Disc FAQ

2014-08-23T09:12:11Z

Wiki-HamishBowman: /* Getting help */

Live GIS Disc Testing

2014-08-23T09:10:52Z

Wiki-HamishBowman: + errata 8.0

'''Depecated''': This page is not used any more. Instead we make use of Project Quickstarts for testing.

''This page describes how to test each application installed on the [[Live GIS Disc]]. Application test steps describe how an Ubuntu user who is unfamiliar an application can try it out and confirm that everything has been installed correctly within 5 minutes. Test Results document when the application was last verified to be working.''

''This page is maintained at: http://wiki.osgeo.org/wiki/Live_GIS_Disc_Testing and copied onto each release of the LiveDVD.''

* [[Live GIS Disc/Errata/4.0.0]]
* [[Live GIS Disc/Errata/8.0]]

= Package testing matrix =

{| class="wikitable sortable" border="1" style="text-align:center"
|+ Package testing status 
|-
! Package Name
! Latest Tested Against
! Result
! Notes
|-
| [[#Boot and Installer|Boot and Installer]]
| 4.0rc6
|   {{issues}}  
|
|-
| [[#atlasstyler|atlasstyler]]
| 4.0rc9
| {{issues}}
|
|-
| [[#deegree|deegree]]
| 4.0rc6
| {{issues}}
|
|-
| [[#geopublisher|geopublisher]]
| 4.0rc6
| {{issues}}
|
|-
| [[#geoserver|geoserver]]
| 4.0rc6
| {{issues}}
|
|-
| [[#gvSIG|gvSIG]]
| 4.0rc6
| {{issues}}
|
|-
| [[#gdal / ogr|GDAL / OGR]]
| 4.0rc9
| {{pass}}
|
|-
| [[#geomajas|geomajas]]
| 4.0rc9
| {{pass}}
|
|-
| [[#geonetwork|geonetwork]]
| 4.0rc6
| {{issues}}
|
|-
| [[#gpsdrive|gpsdrive]]
| 4.0rc9
| {{pass}}
|
|-
| [[#geokettle|geokettle]]
| 4.0rc6
| {{pass}}
|
|-
| [[#gmt|gmt]]
| 4.0rc9
| {{fail}}
|
|-
| [[#grass|GRASS]]
| 4.0rc9
| {{issues}}
|
|-
| [[#kosmo|kosmo]]
| 4.0rc6
| {{pass}}
|
|-
| [[#mapnik|mapnik]]
| 4.0rc6
| {{pass}}
|
|-
| [[#maptiler|maptiler]]
| 4.0rc9
| {{pass}}
|
|-
| [[#marble|marble]]
| 4.0rc9
| {{pass}}
|
|-
| [[#mapfish|mapfish]]
| 4.0rc6
| {{issues}}
|
|-
| [[#MapGuide Open Source|MapGuide]]
| 4.0rc6
| {{issues}}
|
|-
| [[#Mapbender|Mapbender]]
|  ? 8 Aug 2010
| {{pass}}
|
|-
| [[#mb-system|mb-system]]
| 4.0rc9
| {{fail}}
|
|-
| [[#mapserver|mapserver]]
| 4.0rc6
| {{pass}}
|
|-
| [[#octave|octave]]
| 4.0rc9
| ''disabled''
|
|-
| [[#opencpn|opencpn]]
| 4.0rc9
| {{pass}}
|
|-
| [[#osm|osm]]
| 4.0rc9
| {{pass}}
|
|-
| [[#ossim|ossim]]
| 4.0rc9
| {{pass}}
|
|-
| [[#osgearth|osgearth]]
| 4.0rc9
| {{issues}}
|
|-
| [[#openjump|openjump]]
| 4.0rc9
| {{pass}}
|
|-
| [[#postgis|postgis]]
| 4.0rc9
| {{pass}}
|
|-
| [[#pgRouting|pgRouting]]
| 4.0rc6
| {{Pass}}
|
|-
| [[#qgis|qgis]]
| 4.0rc9
| {{issues}}
|
|-
| [[#QGIS Mapserver|QGIS Mapserver]]
| 4.0rc6
| {{Pass}}
|
|-
| [[#R|R]]
| 4.0rc9
| {{issues}}
|
|-
| [[#SAGA|SAGA]]
| 4.0rc6
| {{Pass}}
|
|-
| [[#Sahana|Sahana]]
| 4.0rc9
| {{pass}}
|
|-
| [[#spatialite|spatialite]]
| 4.0rc6
| {{issues}}
|
|-
| [[#udig|uDig]]
| 4.0rc9
| {{pass}}
|
|-
| [[#Ushahidi|Ushahidi]]
| 4.0rc9
| {{pass}}
|
|-
| [[#Viking|Viking]]
| 4.0rc9
| {{pass}}
|
|-
| [[#ZOO Project|ZOO Project]]
| 4.0rc9
| {{issues}}
|
|-
| [[#zyGrib|zyGrib]]
| 4.0rc9
| {{pass}}
|
|-
| [[#main documentation|main documentation]]
| 4.0rc6
| {{issues}}
|
|-
| [[#Windows Installers|Windows Installers]]
|
| ''none''
|
|-
| [[#Mac Installers|Mac Installers]]
|
| ''none''
|
|-
| DVD burn (full)
| 4.0rc9
| {{pass}}
|
|-
| DVD burn (mini)
|
| ''none''
|
|-
| USB stick install (full)
| 4.0rc9
| ''mixed''
|
|-
| USB stick install (mini)
|
| ''none''
|
|-
| VM:VirtualBox
| 4.0rc9
| {{pass}} ?
|
|-
| VM:VMWare
|
| ''none''
|
|-
| VM:Qemu + KVM
| 4.0rc9
| {{issues}}
|
|}

 


= Template =

;Tests written for
:.package. [version], osgeo-live [version]
;Test Description last updated
:.date.

== Steps ==

''Ideally, steps will mimic the Quick Start documentation, so both can be tested at once. Otherwise, use following:''

#.action.

:Verify that ...

#Eg: From menu, select GeoSpatial->Application->Start

:Eg: Verify that a browser opens at url: http://localhost:... and shows the application start page.

#Update the wiki with test results (after these test steps)

----

== Results from .date. ==

:Run by: FirstName LastName
:System: VMWare Player, 2Gig RAM, on ubuntu 9.0 base
:Version: distribution version: eg: osgeo-live 4.0 rc6
:Results: <nowiki> {{Pass}}, Pass with {{Issues}}, {{Fail}} </nowiki> (use curly-bracket template)

#link to bug reports

----

;Add more test results below, most recent results at the top

 

= Boot and Installer =

== Steps ==

''Ideally, steps will reference Quick Start documentation, otherwise use following:''

*. Straight up Live DVD Disk
*. Installer (into a VM if that is easier to clean up after)
*. Testing is performed offline

:Verify that ...

*. You arrive at the desktop
*. Help opens
*. Firefox opens up

*Update the wiki with test results (after these test steps)

----

== Results from August 6th ==

:Run by: Jody Garnett
:System: Thinkpad T43, 2 GB, on live dvd
:System: Macbook Pro, 4 GB, on live dvd
:System: VirtualBox, 1 GB, 30GB HD image, on windows 7
:Version: distribution version: eg: osgeo-live 4.0 rc6
:Results: Pass with issues

Bootloader

*. shows version 3.0
*. think pad boots fine
*. mac needed to hit ENTER to get to the initial boot loading screen

Installer

*. tried with vitural box vm
*. install says "Arramagong live"
*. obviously installing will allow you to enter a user name; will this break applications expecting "user" ?
*. my install failed; not enough space on the device. Need instructions indicating how much space is needed

Desktop

*. think pad displays fine
*. macbook pro - test OSGeo LIVE DVD Barcelona is cut off (and this one has higher resolution than many laptops)
*. virtual box - could not adjust the screen resolution beyond the initial 800x600, instructions for open-vm-tools were fine, oh wait it wants a reboot - of a live dvd?
*. never did get virtual box to have a different screen resolution even after adding the open-vm-tools

Suggestions from IRC:

*. change background to not have text
*. text at bottom of desktop being cut off is probably a function of screen aspect ratio
*. indicate that "user" is the password in a box or make it more visible (good idea jasonbirch)

*link to bug reports

----

== Results from August 7th, 2010 ==

:Run by: Angelos Tzotsos
:System: VirtualBox 3.2, 1Gig RAM, on OpenSUSE 11.2
:Version: osgeo-live 4.0 rc6
:Results: Pass with issues

*The DVD has label Arramagong Live 3.0
*User name is asked for installation, but after first boot, automatic login can be selected.
*Had to install vbox-additions in order to change screen resolution.

----

= deegree =

;Tests written for
:deegree 2.3 , osgeo-live 4.0

Steps: Run the QuickStart.

== Results from August 6th ==

Switch to running Quick Start over previous 3.0 test steps. Things working as expected.

:Run by: Cameron Shorter
:System: Virtual Box on Ubuntu
:Version: distribution version: eg: osgeo-live 4.0 rc6
:Results: Pass

== Results from August 6th ==

:Run by: Jody Garnett
:System: Thinkpad, 2 GB ram, live dvd
:Version: distribution version: eg: osgeo-live 4.0 rc6
:Results: Pass with test script issues

*start deegree not on desktop; has been moved \u2026 into Web Services
*running start deegree opens firefox; firefox is in offline mode and can't browse http://localhost:8081/
*services are there
*test WMS, test WFS or test WCS links are not there
*generic client works
*deegree logo tries to take me to the website (and I am not online); I would like to return to the initial start page?
*deegree iPortal does not exist
*super hard to tell if the service stopped

----

== Results from August 7th, 2010 ==

:Run by: Angelos Tzotsos
:System: VirtualBox 3.2, 1Gig RAM, on OpenSUSE 11.2
:Version: osgeo-live 4.0 rc6
:Results: Pass with issues

*Firefox starts before Tomcat + deegree are up, throwing a "not found" page. The user needs to refresh.
*iPortal: When changing from Utah theme to Salt Lake City theme, the overview window is not redrawn.

----

= atlasstyler =

# Go to Geospatial ‣ Desktop GIS ‣ AtlasStyler.
# Use the import buttons to either add ESRI Shapefiles oder PostGIS datasources to your project.
# Click the tool-icon in the layer legend and select style. The main AtlasStyler dialog will open. While you change the style, the ‘automatic preview’ option at the bottom will render your changes on the fly.

== Results from August 6th, 2010 ==

:Run by: Jody Garnett
:System: Thinkpad T43, 2Gig RAM, on live dvd
:Version: osgeo-live 4.0 rc6
:Results: Atlas styler fail

* Application is in "Education > Atlasstyler" (Not Science > Atlas Styler)
* Quickstart is not specific enough; it is more a link to other docs
* Application "window" is messed up; the window tilebar is folded up under the desktop bar; you can resise the window; but not move it.
* Tried with natural_earth countries, a warning was provided that it would use the default style, progress bar is taking a long time
* Oh wait the tutorials link to their website (I am offline); but the styling layers with SLD tutorials in french and english are actually included on the disk (verified both links work)
* The application never came back to me; and the window issue result in a fail
* darn I was looking forward to this one
* figured out a workaround; clicking on task bar and asking the application to maximiz finally lets me get at the window tilebar
* Whew was able to use "ps -ef | grep java" and "kill" to shut it down

== Results from August 19th, 2010 ==

:Run by: H Bowman
:System: Qemu+KVM on Debian/lenny amd64 host
:Version: osgeo-live 4.0 rc9
:Results: {{issues}}
* worked fine for me with natural_earth countries, I had to lock the mouse within the VM window (ctrl-alt in Qemu-KVM) so I could alt-left-click-drag the Style window up enough to get at the Ok green check button in the bottom right. Otherwise very nice.

----

= geopublisher =

Run quickstart:

*. http://download.osgeo.org/livedvd/4.0-rc6/osgeolive-docs/quickstart/geopublisher_quickstart.html

*Go to applications->education-> and open Geopublishing documentation
**Verify that the green page from file:///usr/share/doc/geopublishing/index.html open in a browser
*Scroll to the bottom and click the demo atlas.
*Unzip it do your Desktop
*Go to applications->education-> and start Geopublisher
*Load the atlas.gpa from your Desktop/ChartDemoAtlas
**Verify that Geopublisher load the atlas. You should see a triparted GUI with a map-pool, data-pool and menu area.
*Select File->Export and follow the wizard..
**export online and offline version of the atlas to a ''new directory'' Desktop/ChartAtlasExported
**When the export has finished, click the "open folder" button
**Close Geopublisher
*Go into the Desktop/ChartAtlasExported/DISK folder and run ''start.sh''
**Verify that an atlas opens
**Verify that you see a "Charts available" button at the top right
**Verify that clicking selecting the chart opens a chart window

Let that be the basic testing for Geopublisher now.

----

== Results from August 6th, 2010 ==

:Run by: Jody Garnett
:System: Thinkpad T43, 2Gig RAM, on live dvd
:Version: osgeo-live 4.0 rc6
:Results: GeoPublisher pass with issues

*. Application > Education (not Science)
*. You could just have the demo atlas link in the quickstart?
*. I need a bit more advice no unzipping the demo atlas (firefox opened archive manager; but I think a picture is needed for those new to linux)
*. Open Folder button did not work
*. It is running and is very pretty

= geoserver =

Run quickstart: - http://download.osgeo.org/livedvd/4.0-rc6/osgeolive-docs/quickstart/geoserver_quickstart.html

Previous test definition:

*Select the "Start GeoServer" icon.
*Wait ~ 60 seconds for GeoServer to start.

:Verify the GeoServer web page opens at http://localhost:8082/geoserver/web

*In the firefox browser, click on "Layer Preview", wait ~ 30 secs

:Verify you get a list of map layers

*Select the 'OpenLayers' link on one of the layers (say the TOPP:States)

:Verify you should see a web page with sample data in an interactive map

----

== Results from August 6th,2010 ==

:Run by: Jody garnett
:System: Thinkpad T43, 2Gig RAM, on live dvd
:Version: osgeo-live 4.0 rc6
:Results: Pass with issues

*Quickstart document is not rendering correct; images rescale and text is pushed out of the way
*Start GeoServer icon is not specific; it is in Web Services now; or in the Education menu (sigh!)
*Nice progress bar as it starts up (who did that?)
*Helpful having the start page link in the docs; but that new little progress bar opened the page for me
*Suffers from the same "Firefox is in offline mode" error and cannot see local host (sent to email list)
*No need to login if all you are doing is showing the layer preview
*Warning is about the read-only file system; the live dvd provides this; so is this warning needed?
*the directory needs to be /home/user/data/natural_earth (since the live dvd user name is "user" )
*So adding a layer was fine; the sectino for adding the style to the layer is empty

----

== Results from August 7th, 2010 ==

:Run by: Angelos Tzotsos
:System: VirtualBox 3.2, 1Gig RAM, on OpenSUSE 11.2
:Version: osgeo-live 4.0 rc6
:Results: Pass

*Embeded GeoWebCache WMS TMS document throws an error.
*Quickstart: the path to find the data is /usr/lib/geoserver-2.0.2/data_dir/data instead of /usr/lib/geotools-2.0.2/data_dir/data

----

= gvSIG =

*Go to applications->education and start gvSIG

:Verify that gvSIG starts correctly

*Create a new view and add some shapefiles from <tt>/usr/local/share/mapserver/demos/itasca/data</tt>

:Verify that the shapefiles are correctly added to the view

*Create a new view and add any of the two TIFF files from <tt>/usr/local/share/mapserver/demos/itasca/data</tt>

:Verify that the raster files are correctly loaded to the view

*If you have Internet access, try to add a WMS layer from the combo list (i.e. the NASA JPL server)

:Verify that a WMS layer can be accessed

*Open the sample project included in the LiveDVD at <tt>/usr/local/share/gisvm/app-data/gvsig/sample-project.gvp</tt>

:Verify the project loads all the data and layouts configured are available.

*You can also try to access any of the other data available from the LiveDVD like the PostGIS Data, or WxS services by the map servers configured

:This tests are related with the correct functioning of the other software installed on the LiveDVD

*Update the wiki with test results (after these test steps)

----

== Results from 6 Aug 2010 ==

:Run by: Christian Willmes
:System: Virtualbox 3.2, 2048MB RAM, on Ubuntu 10.4
:Version: distribution version: OSGeoLive-v4-rc6.7z
:Results: pass with path issues to sample project

*Programm runs fine, but on opening the sample project from <tt>/usr/local/share/gisvm/app-data/gvsig/sample-project.gvp</tt>, a file not found / Invalid path to "/home/user/data/openjump/data/departement22.shp" and the same message to a lot of other files in that directory comes up.

= gdal / ogr =

;Steps
: 

*Open a terminal

ogrinfo --formats
gdalinfo --formats

ogrinfo data/natural_earth/10m_ocean.shp
gdalinfo /usr/share/osgearth/data/terrain/mt_rainier_90m.tif

== Results from August 7th, 2010 ==

:Run by: Angelos Tzotsos
:System: VirtualBox 3.2, 1Gig RAM, on OpenSUSE 11.2
:Version: osgeo-live 4.0 rc6
:Results: Pass

== Results from 2010-08-18 ==

:Run by: H Bowman
:System: Live DVD booted from ISO in a Qemu-KVM VM on Debian/Lenny amd64
:Version: osgeo-live 4.0 rc9
:Results: {{pass}}

----

 

= geomajas =

*Click desktop icon "Browser Clients" → "Start Geomajas" which will start the Geomajas startup script. This will in turn start up a Tomcat server.

:Verify that Firefox opens a new tab at the page http://localhost:3420/showcase/

* ''Test instructions are out of date'' ...
<strike>
*Click on the "Start demo!" link for the Attributes & Features demo.

:Verify that a sample demo page has opened with an application, showing the provinces of Belgium.

*Doubleclick on one of the rows in the attribute table bottom right.

:Verify that a floating window appears, showing the rows' contents in more detail.
</strike>

*Click on the desktop icon "Browser Clients" → "Stop Geomajas".

:Verify that the Tomcat server that runs Geomajas has stopped.
:*This can be done by refreshing the page. Firefox should give a warning that it is unable to connect.

== Results from 9 March 2010 ==

:Run by: Pieter De Graef
:System: Virtualbox, ~512MB RAM, on Windows XP
:Version: distribution version: osgeo-live-3.0rc2
:Results: Pass

== Results from 6 Aug 2010 ==

:Run by: Christian Willmes
:System: Virtualbox 3.2, 2048MB RAM, on Ubuntu 10.4
:Version: distribution version: OSGeoLive-v4-rc6.7z
:Results: fail

*After starting 'start Geomajas' in the Browser Clients folder Firefox opens URL "http://localhost:3420/showcase/", which is a 404 Page delivered by Jetty.

== Results from August 8th, 2010 ==

:Run by: Angelos Tzotsos
:System: VirtualBox 3.2, 1Gig RAM, on OpenSUSE 11.2
:Version: osgeo-live 4.0 rc6
:Results: Fail

*The link http://localhost:3420/geomajas-tutorial/applications/tutorial/html/ does not work after start-up

== Results from 19 Aug 2010 ==

:Run by: H Bowman
:System: Qemu+KVM on a Debian/Lenny amd64 host
:Version: distribution version: osgeo-live-3.0rc9
:Results: {{Pass}}
* Test instructions are all out of date, but playing around with the showcase/ all seems to work ok.

= geonetwork =

*Click icon "Start Geonetwork" - wait until the server intializes (see load graph in the upper right hand corner)
*open FireFox http://localhost:8880
*you should see a list of active URLs, choose /geonetwork
*Search for "river"

:Verify a list of metadata records are returned

== Results from 10 August 2010 ==

:Run by: Cameron Shorter
:System: VirtualBox, 2Gig RAM, on ubuntu 10.04 base
:Version: osgeo-live 4.0 rc6
:Results: Pass with issues

*GeoNetwork doesn't have a script which opens up a web browser (like GeoServer)
*GeoNetwork still calls the old Project Description file.

== Results from August 8th, 2010 ==

:Run by: Angelos Tzotsos
:System: VirtualBox 3.2, 1Gig RAM, on OpenSUSE 11.2
:Version: osgeo-live 4.0 rc6
:Results: Pass

----

= gpsdrive =

*(''copied from install_gpsdrive.sh'')
*More details in the [http://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/descriptions/gpsdrive_description.html on-disc help page]

=== Testing ===

==== If no GPS is plugged in ====

*Double click on the GpsDrive desktop icon
*You should see a map of downtown Barcelona, after about 10 seconds a waypoint marker for the Convention Centre should appear.
*Set the map scale to 1:150,000 either by dragging the slider at the bottom or by using the +,- buttons (not magnifying glass). After a moment you should see all 3 FOSS4G 2010 venues.
*Enter Explore Mode by pressing the "e" key or in the Map Control button.
*Use the arrow keys or left mouse button to move off screen.
*Try clicking on the Workshop venue and mouse-wheel to zoom in on it
*Right click to set destination and leave Explore Mode

*Click on the "Find" button on the left
*Set "maximum distance" to 1.0 km
*Click the POI-Types drop down menu and select ''Food \u2192 Restaurant \u2192 Restaurant''
*Click the ''Find'' button in the top right
*Click on the nearest restaurant, and "Select Target" in the bottom right
*Make your way there and enjoy a nice meal

===== Downloading maps =====

*Change the scale setting to 1:1,000,000 you should see the limits of the PostGIS/Mapnik/OpenStreetMaps road database for the conference area.
*Click the "Map Control" button on the left hand side, and turn off Mapnik Mode.

:You should now see a continental image

*Enter Explore Mode again ("e") and left click on an island in the Med
*In the top-left menu, pick ''Options \u2192 Map \u2192 Download''
**Map source: NASA LANDSAT, Scale: 1:500,000, [Download Map]
**When download is complete click [ok] then change the preferred scale slider to 1:500,000
**This will be of more use in remote areas.
*Explore to the coast, click on an airport, headland, or some other conspicuous feature. You might want to use the magnifying glass buttons to zoom in on it better. Use a right click set the target on some other conspicuous feature nearby then demagnify back out.
*Options -> Map -> Download
**Map source: OpenStreetMap, Scale: 1:40,000, left-click on map to center the green preview over your target and what looks like a populated area.
**[Download Map]
**When download is complete click [ok] then change the preferred scale slider to 1:40,000 and you should see a road map. This will be more interesting in built up areas.

===== Overlay a GPX track ===== 

*If you have a GPX track file lying around ...
*Options -> Import -> GPX track
*Hidden folders are hidden in the file picker, but just start typing ~/.gpsdrive and hit enter. You should then see the tracks/ directory and be able to load 
*A red trace should appear  

==== If a GPS is plugged in ====

*Make sure gpsd is running by starting "xgps" from the command line.
*The program will automatically detect gpsd and jump to your current position. This should bring up a continental map as you won't have any map tiles downloaded for your area yet. (you may want to switch out of ''Mapnik Mode'' in the ''Map Control'' window)
*See the above "Downloading Maps" section to get some local tiles.
*If you have a local GPX track of some roads try loading that and making sure everything lines up, as detailed in the above "Overlay a GPX track" section.

That's it.

== Results from Aug 2010 ==

:Run by: Cameron Shorter
:System: Virtual Box on Ubuntu 10.04
:Version: osgeo-live 4.0 rc6
:Results: Pass

== Results from 18 Aug 2010 ==

:Run by: H Bowman
:System: Qemu-KVM on Debian Lenny
:Version: osgeo-live 4.0 rc9
:Results: {{pass}}

= geokettle =

;Tests written for
:geokettle 3.2.0-20090609, osgeo-live 4.0-rc6
;Test Description last updated
:August 8th, 2010

;Steps

*Launch GeoKettle.

:Verify you get a window prompting you to select a repository.

*On the "Select a repository" dialog, choose "No repository".

:Verify the GeoKettle application is opened.

*Close any startup tips dialog.
*Select File-> Open
*Select <tt>/opt/geokettle/samples/transformations/geokettle/intersection.ktr</tt>

:Verify you see the "intersection" transformation in the work area, with a big yellow comment box and some step icons.

*Run the transformation in preview mode
**Select Transformation menu -> Preview
**Choose the "Intersecting rows" step (to view the rows that are outputted by that step)
**then click on Quick Launch.

:Verify you see the result in the "Examine preview data" dialog (two rows with four columns: GEOM1_ID, geom1, GEOM2_ID, geom2. The geom1 and geom2 fields should contain MULTIPOLYGON WKT geometries).

----

== Results from August 8th, 2010 ==

:Run by: Thierry Badard
:System: VirtualBox 3.1, 2Gig RAM, on ubuntu 10.04 base
:Version: osgeo-live 4.0 rc6
:Results: Pass

= gmt =

There are 29 example jobs built in, and a script to run them all:

*Open a terminal

cp -r /usr/share/doc/gmt-examples/examples/ gmt-examples
cd gmt-examples/
./do_examples.sh

[whiz .. bang .. whirl]

View results using ghostscript in the ex*/*ps directories

Eg:

gs ex02/example_02.ps

 

== Results from 2010-08-06 ==

:Run by: Cameron Shorter
:System: Live DVD booted from ISO in a VM, 512Meg RAM
:Version: osgeo-live 4.0 rc6
:Results: Pass (fixed test steps)

 

== Results from 2010-08-18 ==

:Run by: H Bowman
:System: Live DVD booted from ISO in a Qemu-KVM VM on Debian/Lenny
:Version: osgeo-live 4.0 rc9
:Results: {{fail}} (trac #627)

= grass =

*Double click on the GRASS desktop icon

:Verify you see a slick "Welcome to GRASS" GUI

*Select Spearfish60 for location, User1 for mapset
*Click on [Start Grass]
*In the Layer Manager GUI window add a raster layer
**On the toolbar click the icon with a + and a checkerboard
**On map to be displayed pull down the list and select elevation.dem
*from the PERMANENT mapset and click [ok]
*In the Layer Manager GUI window add a vector layer
**On the toolbar click the icon with a + and a "V" line
**For input map name pull down the list and select roads from the PERMANENT mapset and click [ok]
*Over in the Map Display window toolbar click on the eyeball icon to render

:Verify you see the maps displayed

;See also

*http://trac.osgeo.org/grass/wiki/HowToTestGrass6

:(North Carolina dataset is already installed in grassdata/)

*More details in the [http://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/descriptions/grass_description.html on-disc help page]
*http://grass.osgeo.org/grass64/manuals/html64_user/helptext.html

----

== Results from 2010-08-06 ==

:Run by: Myles Kenihan
:System: Live DVD, Base System Mac Mini 2.0 Dual Core 2Gig RAM
:Version: osgeo-live 4.0 rc6
:Results: Pass

== Results from 2010-08-18 ==

:Run by: H Bowman
:System: Live DVD booted from ISO in a Qemu-KVM VM on Debian/Lenny
:Version: osgeo-live 4.0 rc9
:Results: {{issues}} (OpenGL NVIZ wonky in a VM)

= kosmo =

;Tests written for
:Kosmo Desktop 2.0, osgeo-live 4.0
: 
;Test Description last updated
:August 10th, 2010

;Steps
;Theming layer with PostGIS backend 

*Select ''Desktop GIS > Kosmo'' from the desktop in order to start Kosmo Desktop 
*In the welcome dialog, select the option "''With a new view''" inside the "''Create a new project''" panel and click ''Ok'' 
*In the "''Spatial Reference System selection''" dialog, press the "..." button in order to select the view SRS
*Select "EPSG" as Type
*Enter 4236 in the textfield and click "Search" button; select the CRS given and click the ''Ok ''button
*Click Ok again to set EPSG:4236 as the current view projection 
*In the main menu "''View''", select the option "''Load Dataset...''"
*Select as Format -> "''Database''" (at the top-left corner) and "''PostGIS''" as database type
*Enter '''Database Name''': ''osm_local'' '''''User Name''''Password''': ''user ''and click the "Connect" button 
*Scroll down, check the box to the left of '''public.planet_osm_roads''' and click the ''Ok ''button
*Select the 'planet_osm_roads' layer at left under 'Working' and click the checkbox to make it visible
*Right-click on the 'planet_osm_roads' layer and choose ''Simbology > Change Styles...''
*Select the "''Colour Theming''" tab; click the "''Enable colour theming''" checkbox
*Choose Attribute => ''highway ''and click the Ok button to apply the changes 
*You should see the local OSM roads coloured by attribute in the map 

''' '''

'''Shapefile and image loading''' 

*Select ''Desktop GIS > Kosmo ''from the desktop in order to start Kosmo - Desktop 
*In the welcome dialog, select the option "''With a new view''" inside the "''Create a new project''" panel and click Ok 
*Repeat the steps described in the test "Layer Theme with PostGIS backend" to select the task projection 
*In the main menu "''View''", select the option "''Load Dataset...''" 
*Select as Format -> "''Image file''" and navigate to ''/home/user/data/natural_earth/'' (or ''data/natural_earth/'' if it starts at the home/user directory) 
*Select the directory "HYP_50M_SR_W" in order to load all the tiffs inside it as a mosaic and press the Ok button 
*Select the HYP_50M_SR_W layer at left under 'Working' and click the checkbox to make it visible 
*Select as Format -> "''Shapefile''" 
*Select the "10m_populated_places_simple.shp" and "10m_ocean.shp" files and press the Ok button in order to load them 
*Check that both shapefiles have been loaded on the layer tree at the left. Make them visible by clicking on the checkbox of each one

 

----

== Results from 2010-08-10 ==

:Run by: Sergio Baños 
:System: VMBox Player, 4Gig RAM, on Windows Vista 
:Version: distribution version: osgeo-live 4.0 rc6
:Results: Pass

 

= mapnik =

see file:///usr/local/share/livedvd-docs/doc/mapnik_description.html Mapnik Description

*http://live.osgeo.org/doc/mapnik_description.html

:''--this may be 6 months old, try the on-disk quickstart instead --HB''

== Results from 2010-08-06 ==

:Run by: Cameron Shorter
:System: Live DVD, in VirtualBox Virtual Machine
:Version: osgeo-live 4.0 rc6
:Results: Pass

= maptiler =

*you need an GeoTIFF or other raster geodata to test the functionality.
: For example <tt>/usr/local/share/maptiler/utm.tif</tt>


*start MapTiler: click on Geospatial → Spatial tools → "MapTiler"
*in the MapTiler application select on the first page "Google Maps compatible" tiles and click "Continue"
*in the second page of wizard add the tiff, it should be <tt>/usr/local/share/maptiler/utm.tif</tt> and click "Continue"
*continue trough all other steps in the wizard (default options are fine) and then start "Render"
*when the rendering is finished you will see a link to the directory with tiles, click to open it (it opens in Firefox as a directory)
*open the "googlemaps.html", you should see a black&white overlay displayed on top of Google Maps hybrid layer. You can also open "openlayers.html" to see another presentation of the results.

:Verify that ...

*MapTiler application starts without problems when clicked on the icon
*When you press on "Render" applications starts the processing and does not report any error.

Alternative "real" geodata for testing are for example [http://www.archive.org/details/maps_usgs USGS maps] or [http://www.charts.noaa.gov/InteractiveCatalog/nrnc.shtml NOAA RNCs].

Another way to try it:

#Start MapTiler by clicking the icon on the Desktop
#Load in the second step example raster GEODATA (with georeference/srs)
#Go through all the steps with 'Next' up to the Render
#Once the render is finished you can click in the GUI to open a folder with tiles. When you open googlemaps.html or openlayers.html then you see your geodata warped to the overlay of popular interactive web maps as Google Maps.

The map tiles are displayed directly from your disk. To publish the map to Internet just upload the folder with tiles to any webserver or Amazon S3"

== Results from 2010-08-19 ==

:Run by: H Bowman
:System: Qemu+KVM on Debian/Lenny amd64 host
:Version: osgeo-live 4.0 rc9
:Results: {{Pass}}
* updated test instructs to reference on-disc geotiff source

----

= marble =

*Click on the desktop icon
*If you have used Google Earth before you should be able to figure this one out without much difficulty.
*In the Settings menu select full-screen mode
*Explore ...
*In the bottom-left corner of the program window there is a subtle tab called "Map View". Click on it.
*Select another map (e.g. 'Precipitation (July)')
*Explore some more ...

== Results from 2010-08-06 ==

:Run by: Myles Kenihan
:System: Live DVD, Base System Mac Mini 2.0 Dual Core 2Gig RAM
:Version: osgeo-live 4.0 rc6
:Results: Pass

== Results from 2010-08-18 ==

:Run by: H Bowman
:System: Live DVD booted from ISO in a Qemu-KVM VM on Debian/Lenny
:Version: osgeo-live 4.0 rc9
:Results: {{pass}}

= mapfish =

;Steps
: 

*Make sure you have a working internet connection
*Double click on the Mapfish icon on the desktop

:Verify that a browser opens after a few seconds showing a map of the southwestern pacific

*Click the magnifying glass just under the word "Map" at the top of the map.
*Zoom in on Sydney
*Explore

----

== Results from August 8th, 2010 ==

:Run by: Angelos Tzotsos
:System: VirtualBox 3.2, 1Gig RAM, on OpenSUSE 11.2
:Version: osgeo-live 4.0 rc6
:Results: Pass with issues

*Mapfish start-up script fails to start.
*Cameron Shorter: I can reproduce this problem when starting up with the Disc is not connected to the internet, and Firefox is in Offline mode. It starts up fine when connected to the internet.

= MapGuide Open Source =

;Tests written for
:MapGuide Open Source 2.2.0, LiveDVD 4.0
;Test Description last updated
:June 26, 2010
;Steps

*Start LiveDVD and log in as "user"

:Verify presence of "Start MapGuide", "Stop MapGuide", and "MapGuide Maestro" desktop icons

*Double click "Start MapGuide" desktop icon and enter "user" password if prompted

:Verify that "Starting MapGuide" and "Starting Apache" messages appear

*Open a browser window to http://localhost:8008/mapguide/phpviewersample/ajaxviewersample.php

:Verify that a map is displayed in the center of the screen with a layer legend to the left of the map and an application "Overview" pane to the right of the map.

*Zoom into street level detail and click the pointer icon. Select a parcel.

:Verify that a parcel is selected in blue.

*On the right hand side of the page, click "Tasks" then "Buffer". Set the distance to 20 meters and click "Done"

:Verify that a red buffer zone appears around the parcel.

*Close the browser and double click the "MapGuide Maestro" desktop icon. Login to "http://localhost:8008/mapguide/mapagent/mapagent.fcgi" as user "Administrator" and password "admin".

:Verify that the tree view contains "Samples/Sheboygan".

*Update the wiki with test results (after these test steps)

----

== Results from August 5, 2010 ==

:Run by: Trevor Wekel
:System: VMware ESX 4.1, 16GB RAM
:Version: LiveDVD 4.0 RC 6
:Results: Pass with minor issue - the project overview is missing. Cameron has already fixed it.

*link to bug reports

== Results from 6 Aug 2010 ==

:Run by: Christian Willmes
:System: Virtualbox 3.2, 2048MB RAM, on Ubuntu 10.4
:Version: distribution version: OSGeoLive-v4-rc6.7z
:Results: pass with minor issue

*The MapGuide Maestro points to the URL without the 8008 port after localhost, which results in an error, if the user does not fix this in the URL himself.

= Mapbender =

;Tests written for
:Mapbender 2.6.1, OSGeo LiveDVD 4.0
;Test Description last updated
:5. July 2010
;Steps

*make sure that you have a working internet connection
*make sure that your Apache and PostgreSQL is running

*double click on the Mapbender icon on the desktop or browse to http://localhost/mapbender/

:Verify that a browser opens after a few seconds showing the Mapbender login-page

*login with user root / password root

:Verify that the list of the available applications appears

*choose application named "gui" with a click on the name

:verify that the application "gui" opens and that you see a Mapbender application with the demis-world WMS, a germany WMS and a mapbender-user WMS

*Update the wiki with test results (after these test steps)

----

== Results from 5.7.2010 ==

:Run by: Astrid Emde
:System: VirtualBox, 2Gig RAM, on ubuntu 8.10
:Version: Mapbender 2.6.1, just ran ./install_postgis.sh and ./install_mapbender.sh
:Results: Fail

*I ran ./install_postgis.sh and ./install_mapbender.sh - When I started Mapbender the ALIAS was not created. After restart the Mapbender could be used without problem, login succeded

;Result

*next test will be run with the osgeolive 4.0 rc

----

== test results from 23.7.2010 ==

:Run by: Marc Manns
:System: VirtualBox, 2Gig RAM, on ubuntu 8.10
:Version: OSGeoLIve beta2 Mapbender 2.6.1
:Results: Pass with issues

*create user/group
*create application
*register new WMS
*customize tree
*add WMSFromFilteredList
*change language in [Mapbender.conf] to german

*suggestion: There is a password.txt at the desktop. I think, we should add our root/root authentication to it. -> '''done --[[User:Astrid Emde|astroide]] 09:28, 23 July 2010 (UTC) '''

;Result

*the Mapbender applications handling worked fine

----

== test results from 8.8.2010 ==

:Run by: Astrid Emde
:System: VirtualBox, 2Gig RAM, on ubuntu 8.10
:Version: OSGeoLIve rc6 Mapbender 2.6.2
:Results: Passed

*create gui
*create application
*register new WMS
*print

;Result

*the Mapbender applications handling worked fine

----

;Add more test results below, most recent results at the top

 

= mb-system =

*Open a terminal

cd /usr/local/mbsystem/examples/

List summary information about the contents of some bathymetric data files:

cd mbinfo/
./mbinfo.cmd

Grid some sample data and then view it:

cd ../mbm_plot/
./mbm_plot_5.cmd

# which creates this script:
./mbm_plot_test5.cmd

You should now see a nice plot of the seafloor off Baja California.

*(this also acts as a test of the GMT plotting package)

== Results from 2010-08-06 ==

:Run by: Myles Kenihan
:System: Live DVD, Base System Mac Mini 2.0 Dual Core 2Gig RAM
:Version: osgeo-live 4.0 rc6
:Results: Pass

== Results from 2010-08-18 ==

:Run by: H Bowman
:System: Live DVD booted from ISO in a Qemu-KVM VM on Debian/Lenny
:Version: osgeo-live 4.0 rc9
:Results: {{fail}} (trac #627)

= mapserver =

;Tests written for
:MapServer 5.6.3, OSGeo LiveDVD 4.0
;Test Description last updated
:30 June 2010
;Steps

*Select the "MapServer" icon.
*Wait a few seconds for FireFox to start.

:Verify the MapServer web page opens at <tt>file:///usr/local/share/livedvd-docs/doc/mapserver_description.html</tt>

*In the firefox browser, scroll down to "MapServer Demo" section and click on "Itasca".

:Select "Basic Application" and click on "Initialize".
:Verify you get a map.

*Select the "Query multiple features" tool on the right of the page and click somewhere on the map.

:Verify you get a list of features.

*'''THE GMAP DEMO HAS BEEN REMOVE IN 4.0 ALPHA4, IT IS NOT YET COMPATIBLE WITH PHP 5.3''' <strike>Return to the the initial MapServer web page, <tt>file:///usr/local/share/livedvd-docs/doc/mapserver_description.html</tt> , scroll down to "MapServer Demo" section and click on "GMap".</strike>

:<strike>Verify you get a map and a legend with icons rendered.</strike>

*Return to the the initial MapServer web page, <tt>file:///usr/local/share/livedvd-docs/doc/mapserver_description.html</tt> on the initial MapServer web page, scroll down to "MapServer Documentation" section.

:Verify that the documentation version is appropriate versus the MapServer version.

----

== Results from 2010-08-06 ==

:Run by: Myles Kenihan
:System: Live DVD, Base System Mac Mini 2.0 Dual Core 2Gig RAM
:Version: osgeo-live 4.0 rc6
:Results: Pass with issues

*All good, documentation link needs to be updated ( says 5.4.2 instead of 5.6, ) but docs themselves seem up to date

== Results from 2010-08-06 ==

:Run by: Daniel Morissette
:System: Live DVD on Acer AST180 desktop (AMD Athlon X2 64, 3GB RAM)
:Version: osgeo-live 4.0 rc6
:Results: Pass with issues

*Itasca demo (and mapserv 5.6.5) work fine
*Problems in mapserver_description.html
**Need to remove "GMap" demo link (since GMap itself has been removed)
**Need to update Documentation link to read "MapServer 5.6 Documentation" or even better: "MapServer Documentation" (with no version number so we don't need to update it in the future)
**The main page of the MapServer 5.6 Docs that's on the DVD is from 5.6.3, and the OSM map in that page does not work: the link to the tiles point to a dead server. This is a known issue and the current version of the docs on the MapServer website (v5.6.5) have the map disabled... so it may be a good idea to grab the latest version of the 5.6 docs for the DVD.

----

== Results from August 7th, 2010 ==

:Run by: Angelos Tzotsos
:System: VirtualBox 3.2, 1Gig RAM, on OpenSUSE 11.2
:Version: osgeo-live 4.0 rc6
:Results: Pass

*"GMap" demo link needs to be removed

----

= octave =

*Open a terminal
*Start program by typing "<tt>octave</tt>" at the prompt

% Which way to Barcelona from Sydney?
sydney = [-33.8750 151.2005]
barcelona = [41+23/60 2+11/60]

dirn = azimuth(sydney, barcelona);
deg_symb = 176;
disp(['Heading: ' num2str(dirn) deg_symb])

% How far's the trip? (roughly!)
system('proj -le')
wgs84_a = 6378137.0  % major radius of the Earth, in meters
dist_deg = distance(sydney, barcelona)
dist_meters = pi * wgs84_a * (dist_deg / 360.0)
disp(['Distance: ' num2str(dist_meters / 1000) ' km'])

Type "exit" to quit.

== Results from 2010-08-06 ==

:Run by: Myles Kenihan
:System: Live DVD, Base System Mac Mini 2.0 Dual Core 2Gig RAM
:Version: osgeo-live 4.0 rc6
:Results: Pass

== Results from 2010-08-18 ==

:Run by: H Bowman
:Version: osgeo-live 4.0 rc9
:Results: '''''Script disabled to save space on the DVD'''''

= opencpn =

;Activate data

*Open a terminal
*Type "<tt>opencpn_noaa_agreement.sh</tt>" at the prompt

;Run program

(assuming your GPS is not plugged in and <tt>gpsd</tt> is not running)

*Double click the OpenCPN icon on the desktop or type "opencpn" at a terminal
**on startup it asks where to find the charts. in the preferences window click in the ''Charts'' tab, click on the charts directory, click on [Add Selection], and tick "Force Full Database Rebuild" at the bottom.
*Left-click recenters the view
*Left-click-drag pans the view
*Mouse-wheel zooms in/out
*The blue bars in the bottom show previews of overlapping raster maps and clicking on them switches to them. The green buttons switch to vectorial charts.
*Right click on the map canvas to get a menu, select "Go to here".
*At this point if you have your auto-pilot interfaced GPS plugged in you should feel your boat/airplane change course. If not, you'll see a red arrow and the destination target blinking anyway but will have make your own arrangements for getting there.

;More details in the [http://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/descriptions/opencpn_description.html on-disc help page]
:and specifically the [http://opencpn.cvs.sourceforge.net/viewvc/*checkout*/opencpn/opencpn/data/doc/tips.html#Getting_Started Getting Started] help page.

== Results from 2010-08-06 ==

:Run by: Myles Kenihan
:System: Live DVD, Base System Mac Mini 2.0 Dual Core 2Gig RAM
:Version: osgeo-live 4.0 rc6
:Results: Pass

== Results from 2010-08-18 ==

:Run by: H Bowman
:System: Live DVD booted from ISO in a Qemu-KVM VM on Debian/Lenny amd64
:Version: osgeo-live 4.0 rc9
:Results: {{pass}}

= osm =

;JOSM

*File \u2192 Open \u2192 /home/user/data/osm/feature_city.osm.bz2
*Left-click drag a box around some data
*Type "<tt>3</tt>" to zoom to the box.
*Rinse and repeat
*Mouse wheel to zoom in further
*Right-click drag to pan
*Click on a road to see some info

;Merkaartor

*Start it up from the ''Navigation and Maps'' menu
*Click the "Download" button at the top left
*Zoom in on ''Mataro'' just to the north of Barcelona (or anywhere) until one zoom level past where you can read the street names, and click [ok] to start the download

:(download map: ''Left-click-drag to pan, mouse wheel to zoom'')

*After it finishes, click on "Download more"

*Click on a road, see its attributes come up
*now it's ''Right-click-drag to pan, mouse wheel to zoom''
*In the Layers list in the top-left right-click on "Map - None" and select "Yahoo!"
*Click the little box to the left of "Map - Yahoo!" to enable the eyeball
*Behold the satellite image underlay

;Osmarender

*Open up Merkaartor again
*When satellite image comes up, click the "Download More" button
*Once the streets come up do ''File \u2192 Export \u2192 OSM (XML)''
*Select "All visible", filename ~/test.osm
*Quit Merkaartor
*Open a terminal, then:

osmarender test.osm

:[''whiz-bang-whirl'']

*After some time it should finish leaving a test.svg file behind
*Open the test.svg file in Inkscape or Firefox to view

inkscape test.svg

*In inkscape it's middle-click-drag to pan, "+" key to zoom in
*In Firefox use Ctrl-+ to zoom in

;Gosmore

*Open a terminal
*Import data with:

bzip2 -dc /usr/local/share/osm/Barcelona.osm.bz2 | gosmore rebuild

*Click on the "-" in the bottom-right of the map canvas until you see the city, then left click to center on downtown, mouse wheel up to zoom in
*That's about it!

== Results from 2010-08-06 ==

:Run by: Myles Kenihan
:System: Live DVD, Base System Mac Mini 2.0 Dual Core 2Gig RAM
:Version: osgeo-live 4.0 rc6
:Results: Pass with issues

*Map didn't render to scale where I could find any roads. Probably because I'm not connected to network. Apps loaded up fine though

:''-- which app are you talking about? net connection should not be needed as we supply data in Barcelona.osm. for Merkaartor you need to un-bzip2 it first, see the quickstart for details. --HB''

*Cameron Shorter: I ran Merkaartor with network connected, and the application was able to download date, and confirmed that when running Merkaartor offline, there was an error, the download of date timed out.

:''-- ... you can't download without somewhere to download from. De-bzip2 the sample data and play with that instead. --HB''

 

== Results from 2010-08-18 ==

:Run by: H Bowman
:System: Live DVD booted from ISO in a Qemu-KVM VM on Debian/Lenny amd64
:Version: osgeo-live 4.0 rc9
:Results: {{pass}}

= ossim =

;Tests written for
:ossim 1.8, osgeo-live 4.0
;Test Description last updated
:2010-08-08

*Run the steps in the quickstart guide
: http://download.osgeo.org/livedvd/4.0-rc7/osgeolive-docs/quickstart/ossim_quickstart.html

Remark: OssimPlanet requires OpenGL support, which might not be available on virtualized environments.

*''Script replaced in 4.0rc8.''

<strike></strike>

== <strike>Results from 2010-08-06</strike> ==

:<strike>Run by: Myles Kenihan</strike>
:<strike>System: Live DVD, Base System Mac Mini 2.0 Dual Core 2Gig RAM</strike>
:<strike>Version: osgeo-live 4.0 rc6</strike>
:<strike>Results: Pass with issues</strike>

*Data is stored in /home/user/ossim. It should be in /home/user/data/ossim directory.

*<strike>The toolbar on ImageLinker flickers as if the toolbar is scrolling up/down/up/down as fast as it can. Possibly due to running in a small window 600x800.</strike>

== <strike>Results from 2010-08-04</strike> ==

:<strike>Run by: Pirmin Kalberer</strike>
:<strike>System: KVM</strike>
:<strike>Version: osgeo-live 4.0 rc6</strike>
:<strike>Results: Pass</strike>

 

== Results from 2010-08-19 ==

:Run by: H Bowman
:System: Qemu+KVM on amd64 Debian/Lenny, physical boot from LiveDVD burn
:Version: osgeo-live 4.0 rc9
:Results: {{Pass}}
* OssimPlanet did not work on VM, as expected, as OpenGL is no-go. Worked fine from physical DVD boot though.

 

----

= osgearth =

;Tests written for
:osgearth 1.3, osgeo-live 4.0
;Test Description last updated
:2010-08-08

*Run the steps in the quickstart guide '''''[LINK PLEASE]'''''
: http://download.osgeo.org/livedvd/4.0-rc7/osgeolive-docs/quickstart/osgearth_quickstart.html

;Result

You should see a globe with different overlays. Remark: OpenGL support is required, which might not be available on virtualized environments.

 

== Results from 2010-08-06 ==

:Run by: Myles Kenihan
:System: Live DVD, Base System Mac Mini 2.0 Dual Core 2Gig RAM
:Version: osgeo-live 4.0 rc6
:Results: Fail

*command failed. Directory share/osgearth/maps/ does not exist
*Cameron Shorter: The following error message occurred:

> osgeoearth_simple 50 50 900 700
[osgEarth::TMS] Error reading TileMap and no overrides set
[osgEarth::MapLayer] Could not initialize TileSource for layer

== Results from 2010-08-04 ==

:Run by: Pirmin Kalberer
:System: KVM
:Version: osgeo-live 4.0 rc6
:Results: Pass

== Results from 2010-08-19 ==

:Run by: H Bowman
:System: Qemu-KVM with X tunneled over ssh; physical LiveDVD
:Version: osgeo-live 4.0 rc9
:Results: {{issues}}
* KVM doesn't like OpenGL, so no luck there. Quickstart should mention that it may not like VMs.
* On the LiveDVD burn it was good though, but of course a network connection was needed which should be mentioned in the quickstart
* A *.desktop file should be written for the simple Blue Marble example to help get folks started/help exposure. (bundle next to Marble)
* All in all, a very nice app!

= openjump =

;Layer Theme with PostGIS backend

*Open OpenJUMP
*under the File menu select 'Open...'
*select Data Store Layer
*on the Connection line, click on the database icon (far right)
*click on Add
*enter '''Name''': osm_local '''Server''': localhost '''Port''': 5432 '''Instance''': osm_local '''User''': user '''Password''': user
*click OK; click OK in the parent dialog box; you should be back in the Data Store Layer dialog
*from the Dataset: menu choose 'planet_osm_roads'; click Finish
*select the planet_osm_roads layer at left under 'Working'
*click on the Palette Icon in the menu bar
*select the 'Colour Theming' tab; click 'Enable colour theming' checkbox
*choose Attribute → admin_level
*choose a colour theme (e.g. Pastel 2 from Colorbrewer); click 'OK' to dismiss the dialog
*you should see the roads in various colours

== Results from 2010-08-06 ==

:Run by: Myles Kenihan
:System: Live DVD, Base System Mac Mini 2.0 Dual Core 2Gig RAM
:Version: osgeo-live 4.0 rc6
:Results: Fail

*Open Jump started but database 'medford' doesn't exist

:''--test is out of date; run "psql -l" to list current installed PostGIS databases. --HB''

== Results from 2010-08-19 ==

:Run by: H Bowman
:System: Qemu+KVM, on debian/lenny amd64 host
:Version: osgeo-live 4.0 rc9
:Results: {{pass}}
* (testing method updated to not use OSM db instead of medford)

= postgis =

;Spatial Query with the Graphical Query Builder helper

*Open PGAdmin III from the Development menu
*double-click on 'local'
*under Databases, double-click on <tt>natural_earth</tt>
*open 'schemas'
*open 'public'
*select 'Tables', click on the 'Execute SQL' Icon above (it has a pencil in it)
*expand the window and click on 'Graphical Query Builder'
*open 'Schemas', double-click on 'public'
*''instructs out of date''
<strike>
*click and drag 'medford_wards' to the work area on the right
*click and drag 'jacksonco_schools' to the work area on the right
*choose 'jacksonco_schools' name, address, city and students
*choose 'medford_wards' council_me (meaning council members)
*click and drag from the_geom in 'medford_wards' to the_geom in 'jacksonco_schools' (you should see a solid line form with an '=' in it)
*click on the 'SQL Editor' tab above, to navigate away from the Graphical Query Builder
*edit the WHERE line to say

ST_Contains( medford_wards.the_geom, jacksonco_schools.the_geom )

*add an additional line

ORDER BY medford_wards.council_me, jacksonco_schools.students DESC;

*the entire query ends with one semicolon ';'
*click on the 'execute query' icon above (a green triangle pointing to the right) you should see a list of council districts, schools, school sizes and the names of council members for each district as a result
</strike>
== Results from 2010-08-06 ==

:Run by: Myles Kenihan
:System: Live DVD, Base System Mac Mini 2.0 Dual Core 2Gig RAM
:Version: osgeo-live 4.0 rc6
:Results: Pass with issues

*database 'medford' doesn't exist

:''--test docs are out of date. run "psql -l" to list currently installed databases. --HB''
:Cameron Shorter: test steps need to be updated to use naturalearth dataset, but otherwise this application is working fine.

== Results from 2010-08-19 ==

:Run by: H Bowman
:System: Qemu+KVM on Debian/Lenny amd64 host
:Version: osgeo-live 4.0 rc9
:Results: {{Pass}}
*database 'medford' used in test instructions doesn't exist, but plenty of evidence that all is ok via GpsDrive live rendering, QGIS browsing, etc.

= pgRouting =

*Follow pgRouting Quick Start documentation, and confirm you get results described.

:'''''[link please]'''''

== Results from 2010-08-06 ==

:Run by: Myles Kenihan
:System: Live DVD, Base System Mac Mini 2.0 Dual Core 2Gig RAM
:Version: osgeo-live 4.0 rc6
:Results: Pass

= qgis =

== open GeoTiff ==

*Layer \u2192 Add raster layer
*Select /home/user/data/natural_earth/HYP_50M_SR_W/HYP_50M_SR_W.tif
*click [Open] and a world map should arrive
*zoom, pan, etc

== open Shapefile ==

*Layer \u2192 Add vector layer
*Select [Browse] then /home/user/data/natural_earth/10m_land.shp
*click [Open] and a world map should arrive
*click the arrow with a blue "i" button (top middle) for query tool
*click on a feature to identify it

*cleanup: File \u2192 New Project, then [discard]

== open PostGIS data I ==

*From the menu: Layer \u2192 Add PostGIS Layer ...
*PostgreSQL Connections: [New]

Name: natural_earth
Host: localhost
Database: natural_earth
Port: 5432
SSL Mode: allow
username: user
password: user

*[Test Connect] should show success
*click [ok]
*click [connect], a list of layers should appear
*select 10m rivers, lakes, and land layers
*click [Add]
*view selected data, drag 10m_land to bottom of layer list so it does not obscure other layers

*cleanup: File \u2192 New Project, then [discard]

== open PostGIS data II ==

:(''run the PostGIS test first so that the osm_barcelona DB exists!''; if not, just set the database name as "osm_local" which is already there)

*From the menu: Layer \u2192 Add PostGIS Layer ...
*PostgreSQL Connections: [New]

Name: ________ "OpenStreetMap Import"
Database: ____ "osm_barcelona"

*Click on [Test Connect], with luck you will get a message that the connection to the database was successful.
*Click [Ok] to close the New Database window.
*Click on [Connect] in the top left of the Add PostGIS Table window. You should see a listing of tables come up.
*Click on all of the table names to highlight them.
*Click on [Add] at the bottom.
*After some moments you should see the data displayed in the main map canvas.
*Zoom, pan, query as you like. Drag layer names up and down in the left-pane list to change their position in the stack.

This should at least prove to you that the database is correctly populated and running.

 

== open OSM data ==

*Plugins \u2192 Manage plugins
*in the filter at the top type "openst"
*tick the OSM plugin and click [ok], a set of new buttons should appear

*In a terminal shell you'll have to uncompress the .osm file

cp data/osm/feature_city.osm.bz2 local.osm.bz2
bzip2 -d local.osm.bz2

*Plugins \u2192 OpenStreetMap \u2192 Load OSM from file
*Select the ~/local.osm file
*Tick all boxes and click [ok], layers should appear in layer list on left
*Right click on a layer in the layer list and Zoom to layer extent
*zoom, pan, etc.
*In the top-left of the right pane depress the blue-i Info button, move mouse over map

*cleanup: File \u2192 New Project, [discard]

 

== Test the GRASS plugin ==

*Plugins \u2192 Manage plugins
*in the filter at the top type "grass"
*tick the GRASS plugin and click [ok], a set of new buttons should appear
*Plugins \u2192 GRASS \u2192 Open Mapset

gisdbase: /home/user/grassdata
location: spearfish60
mapset: user1

*Plugins \u2192 GRASS \u2192 Open GRASS tools

 

*Config \u2192 g.region.multiple.raster

:mapname: elevation.dem [run]

*Raster \u2192 Surface Management \u2192 Generate surface \u2192 r.surf.fractal
*[Run]



;QGIS bug
:wants user to own the PERMANENT mapset even if it isn't open! :-(

 --- 

#click "Add GRASS raster layer" button, select "elevation" map
#click "Add GRASS raster layer" button, select "elevation_shade" map
#click right mouse button in legend on "elevation_shade" map, move transparency to 40%
#click "Add GRASS vector layer" button, select "roadsmajor" map, select layer "1-line" (level 1 is the topological level), OK



== Results from 2010-08-06 ==

:Run by: Myles Kenihan
:System: Live DVD, Base System Mac Mini 2.0 Dual Core 2Gig RAM
:Version: osgeo-live 4.0 rc6
:Results: Fail

*Problem with settings, says database medford does not exist

:''test docs are out of date. run "psql -l" to list currently installed PostGIS databases. --HB''

== Results from August 8th, 2010 ==

:Run by: Angelos Tzotsos
:System: VirtualBox 3.2, 1Gig RAM, on OpenSUSE 11.2
:Version: osgeo-live 4.0 rc6
:Results: Pass with issues

*The GRASS plugin could not load the data from the /hom/user/grassdata folder

== Results from 2010-08-18 ==

:Run by: H Bowman
:System: Live DVD booted from ISO in a Qemu-KVM VM on Debian/Lenny amd64
:Version: osgeo-live 4.0 rc9
:Results: {{issues}} (GRASS plugin is broken)

= QGIS Mapserver =

;Tests written for
:QGIS Mapserver 1.0, osgeo-live 4.0
;Test Description last updated
:2010-08-08

== Steps ==

*Start ''QGIS Mapserver'' from ''Web Services''

:Verify that a browser opens and shows a world map

----

== Results from 2010-08-04 ==

:Run by: Pirmin Kalberer
:System: KVM
:Version: osgeo-live 4.0 rc6
:Results: Pass

= R =

*double click on the R Icon
*at the command line, type demo(graphics) and hit return
*follow the prompt and watch the target window for examples

''If it is possible please add steps here to test the included geostats packages, they are both more interesting and more likely to have problems in the build. tx''

:''e.g. something with r-cran-maps(.deb), gstat, sp, rgdal, or spgrass6 ?''

#Load a library
library(sp)
#list the demos available
demo()
#Run the demo from the sp package
#This will step you through several examples of code and the resulting plots
demo(gallery)

 Some examples to try here:

:http://r-spatial.sourceforge.net/xtra/xtra.RHnw.html

== Results from 2010-08-06 ==

:Run by: Myles Kenihan
:System: Live DVD, Base System Mac Mini 2.0 Dual Core 2Gig RAM
:Version: osgeo-live 4.0 rc6
:Results: Pass

== Results from 2010-08-18 ==

:Run by: H Bowman
:System: Live DVD booted from ISO in a Qemu-KVM VM on Debian/Lenny amd64
:Version: osgeo-live 4.0 rc9
:Results: {{pass}}

= SAGA =

;Tests written for
:OSGeo LiveDVD 4.0

*Start the program
*Check if no errors occur during initialisation (messages text)
*Run the steps in the quickstart guide

As an extra test, you could check whether saga_cmd works: run SAGA_MLB=/usr/lib/saga saga_cmd from a terminal. The list of modules should be given. There should be 45 modules.

== Results from 2010-08-05 ==

:Run by: Johan VandeWauw
:System: Virtualbox, 700Mb RAM, on xubuntu 10.4 base
:Version: distribution version: eg: osgeo-live 4.0 rc6
:Results: Pass

= Sahana =

;Tests written for
:OSGeo LiveDVD 4.0

;Steps

*The '''4.0rc6''' release installer broke. Please rerun the gisvm/trunk/install_sahana.sh script as root before testing.

*follow the steps in the [http://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/descriptions/sahana_description.html '''on-disc help page''']

----

== Results from 2010-08-06 ==

:Run by: Myles Kenihan
:System: Live DVD, Base System Mac Mini 2.0 Dual Core 2Gig RAM
:Version: osgeo-live 4.0 rc6
:Results: Fail

*Didn't have permission to run Sahana even when running under SUDO

:''--see above comment: it's not there because the installer failed. (now fixed) --HB''

== Results from 2010-08-18 ==

:Run by: H Bowman
:System: Live DVD booted from ISO in a Qemu-KVM VM on Debian/Lenny amd64
:Version: osgeo-live 4.0 rc9
:Results: {{pass}}

= spatialite =

;Tests written for
:spatialite 2.4, osgeo-live 4.0
;Test Description last updated
:2010-08-08

*Run the steps in the quickstart guide

== Results from 2010-08-06 ==

:Run by: Myles Kenihan
:System: Live DVD, Mac Mini 2.0 Dual Core, 2Gig RAM
:Version: osgeo-live 4.0 rc6
:Results: Pass with issues

*should read user/data/spatialite/regions.sqlite
*sql query doesn't work with 'order by' qualifier

= udig =

;Steps

*open UDig

:Verify you see a Welcome screen

*Close the Welcome display. (Note if you don't close this display, then you can't load layers later on)
*from the Layer menu, choose "Add..."
*Choose '''Files''' from /home/user/data/udig-data/data-v1_2/
*select bc_border.shp
*you may also select others, for example all shp files starting with bc_
*click OK

:Verify you see Canadian British Columbia data

----

== Results from 2010-08-06 ==

:Run by: Myles Kenihan
:System: Live DVD, Base system Mac Mini 2.0 Dual Core 2Gig RAM
:Version: osgeo-live 4.0 rc6
:Results: Fail

*uDig opened but test data directory was not present

Raised issues:

*http://trac.osgeo.org/osgeo/ticket/621 fix symbolic link so udig-data is available
*http://trac.osgeo.org/osgeo/ticket/622 fails to show geoserver wms

== Results from 2010-08-06 ==

:Run by: H Bowman
:System: Qemu+KVM, host amd64 debian/lenny
:Version: osgeo-live 4.0 rc9
:Results: {{pass}}
* fixed path in test instructs

= Ushahidi =

;Tests written for
:OSGeo LiveDVD 4.0

;Steps

*follow the steps in the [http://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/descriptions/ushahidi_description.html '''on-disc help page''']

----

;Add more test results below, most recent results at the top

 

== Results from 2010-08-06 ==

:Run by: Myles Kenihan
:System: Live DVD, Base System Mac Mini 2.0 Dual Core, 2Gig RAM
:Version: osgeo-live 4.0 rc6
:Results: Pass

== Results from 2010-08-18 ==

:Run by: H Bowman
:System: Live DVD booted from ISO in a Qemu-KVM VM on Debian/Lenny amd64
:Version: osgeo-live 4.0 rc9
:Results: {{pass}}

= Viking =

;Tests written for
:OSGeo LiveDVD 4.0
;Steps

*Start it up from the ''Navigation and Maps'' menu
*If you have a GPX file handy, File \u2192 Open
*Layers \u2192 New Map Layer
*pick OpenStreetMaps (Mapnik), [ok]
*On the ''Layer Name'' list on the left side, right click on "Map" and ''Download Onscreen Maps''
*It should start to download street maps of lower Manhattan
*Select ''Tools \u2192 Ruler'' from the menu
*Click on the Brooklyn Bridge, then on Battery Park to get a distance and heading

== Results from 2010-08-06 ==

:Run by: Myles Kenihan
:System: Live DVD, Base System Mac Mini 2.0 Dual Core 2 Gig RAM
:Version: Osgeo-live 4.0 rc6
:Results: <s>Fail</s>

*Viking opened but with no gpx 'handy' I could not verify that it worked

:''--that's not really a fail. --HB''

== Results from 2010-08-18 ==

:Run by: H Bowman
:System: Live DVD booted from ISO in a Qemu-KVM VM on Debian/Lenny amd64
:Version: osgeo-live 4.0 rc9
:Results: {{pass}}

= ZOO Project =

;Tests written for
:.ZOO Project. 1.0.0, OSGeo LiveDVD 4.0
;Steps

*make sure that your Apache and GeoServer are running

:<tt>Web Services \u2192 Start GeoServer</tt> (takes a few moments)

*Click on "ZOO Project" icon from the bottom of the Web Services geospatial menu to have firefox load the Spatialtools demo page
*select a feature from the displayed states then click on a spatialtools button to get the RawDataOutput result of processing displayed on the map

== Results from 2010-08-03 ==

:Run by: Gérald Fenoy
:System: VMWare Fusion, instance with 2Gig RAM and 2CPU
:Version: distribution version: osgeo-live 4.0 rc6
:Results: Pass

== Results from 2010-08-03 ==

:Run by: Johan VandeWauw
:System: Virtualbox, instance with 700Mb RAM
:Version: distribution version: osgeo-live 4.0 rc6
:Results: Pass after manual install - *if* geoserver started

== Results from 2010-08-18 ==

:Run by: H Bowman
:System: Live DVD booted from ISO in a Qemu-KVM VM on Debian/Lenny amd64
:Version: osgeo-live 4.0 rc9
:Results: {{issues}} (would be nice if it launched geoserver for you)

= zyGrib =

;Tests written for
:OSGeo LiveDVD 4.0
;Steps

*click the magnifying glass 1:1 button on the toolbar to go to the world map
*left-click drag a box over Europe
*click the [] zoom button to the left of the 1:1 zoom button to zoom in to that box
*click the power plug button on the right to check the server status
*left-click drag an area of interest again
*''File \u2192 Download GRIB''
*click the [Download GRIB file] button in the lower-left, and save it.
*You should now see a weather map
*In the ''Data'' menu you can select different maps to look at (e.g. "cloud cover")
*Click the rocketship button on the right end of the toolbar to see a 5 day animation of the forecast. Set speed, Play, etc.

== Results from 2010-08-06 ==

:Run by: Myles Kenihan
:System: Live DVD, Base System Mac Mini 2.0 Dual Core 2Gig RAM
:Version: Osgeo-live 4.0 rc6
:Results: Pass with issues

*Could not connect to network so power plug failed. Could not retrieve network data

== Results from 2010-08-18 ==

:Run by: H Bowman
:System: Live DVD booted from ISO in a Qemu-KVM VM on Debian/Lenny amd64
:Version: osgeo-live 4.0 rc9
:Results: {{pass}}

= main documentation =

;Steps

*Open Help by selecting he help icon (a yellow sign with a wombat)

:Verify that the firefox web browser opens at file:///usr/local/share/livedvd-docs/index.thml
:Verify that the browser opens with "Home", "Contents", "Contact and Support", "Tests", "Sponsors" tabs.

*Click on the above tabs.

:Verify the respective pages are opened.

*Open the "Contents" tab

:Verify that each project is mentioned.
:Verify that the project version numbers matches version numbers here: http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB
:Verify that when clicking on each project title, a description page is opened.

*Install a link checker

sudo apt-get install linkchecker

*Run the linkchecker against the installed docs:

linkchecker /usr/local/share/livedvd-docs/index.html 2>&1 | tee /var/log/osgeo-live/linkchecker.log

:Verify there are not errors in the log file

----

== Results from 2010-08-06 ==

:Run by: Myles Kenihan
:System: Live DVD, Base System Mac Mini 2.0 dual core, 2Gig RAM
:Version: osgeo-live 4.0 rc6
:Results: Pass with issues

 

*The following project listings had issues
*52 degree North Web Processing Service not present in contents
*Geopublisher should be listed as version 1.5 in contents ( it's 1.4 )
*Geoserver 2.0.1 should read 2.0.2
*Mapbender not present in contents
*Octave mapping tools not present in contents

:''--disabled on purpose. --HB''

*Open Jump 1.3 should read 1.3.1
*R Geostatistics 2.10.1 should read 2.11.1
*SAFA GIS not present in contents
*uDIG 1.2rc1 should read 1.2rc3
*Zoo Project not present in contents

The apt-get command failed because I was not connected to a network ( I'm not supposed to be connected to a network, apparently ) and also I was asked for a SUDO password which is not provided.

:''--sudo password now in welcome message --HB''

The linkchecker could thus not be run as I was unable to acquire it

----

= Windows Installers =

;Steps

*From a windows computer, or Virtual Machine, insert the LiveDVD.
*Go to the WindowsInstallers directory on the LiveDVD

:Verify the installers are the same version number as the rest of the DVD, as listed at http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB

*For each WindowsInstaller, run the installer, using all defaults

:Verify the application installs without errors

*If sufficient time, Open up the application and run the test steps above for the application.

----

== Results from 2010-08-19 ==

:Run by: H Bowman
:System: Burned full DVD and Qemu-KVM
:Version: 4.0rc9
:Results: {{issues}}
:: /usr/local/share/ symlinks for both Mac and Windows installers are broken because /cdrom is a real file and not a symlink to /media/cdrom. Otherwise they seem to be correctly in place in the root dir of the DVD. This seems to be an Ubuntu 10.04 thing, only solution is to link to /cdrom instead of /media/cdrom in the install script.

 

= Mac Installers =

;Steps

*From a Mac, or Virtual Machine, insert the LiveDVD.
*Go to the MacInstallers directory on the LiveDVD

:Verify the installers are the same version number as the rest of the DVD, as listed at http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB

*For each MacInstaller, run the installer, using all defaults

:Verify the application installs without errors

*If sufficient time, Open up the application and run the test steps above for the application.

----

== Results from 2010-08-06 ==

:Run by: Myles Kenihan
:System: Booted from Disk. Base System Mac Mini 2.0 Dual Core, 2 Gig RAM
:Version: Arramagong Live GIS 3.0
:Results: Pass with issues

Could not run directly from OSX Snow Leopard. Had to change system settings to boot from disk which worked fine.

= Media tests =

== DVD testing ==

Steps:

*Download full 4.3gb ISO
*Burn to a DVD
*Boot and play

Results:

=== Results from 2010-08-19 ===
* Run by: H Bowman
* System: Quad-core PC amd64 4gb RAM
* Version: 4.0rc9
* Results: {{Pass}} (First one came out as a coaster, second one was ok)

== USB testing ==

Steps:

*Install a OSGeo Live image onto a USB as per: http://wiki.osgeo.org/wiki/Live_GIS_Disc_Quick_Start#Install_to_a_Live_USB_Stick
*Boot the USB. Verify you can log into the OSGeo-Live Desktop
*Open up one of the applications (preferably different to other USB testers), and verify it works fine as per test steps above.
*Note any errors below. ('''''Please state what size USB stick you used (4gb, 8gb, etc.) and how much free space was left for user files (`df -h`)''''')

Results:

*Test 1: First Last

:Computer: Apple Mac ...
:Version: osgeo-live 4.0rc7
:Results: Pass, Fail, Pass with Issues
:Issues: note here.

*Test 2:

:Computer: Gateway (Centrino) pretty old
:Version: osgeo-live 4.0rc9
:Results: Pass with Issues
:Issues: hanging with "boot:" prompt, "live" and "debug" boot option end up with black screen, but "xforcevesa" works very well and resolution fits perfectly.

*Test 3:

:Computer: Acer Timeline
:Version: osgeo-live 4.0rc9
:Results: Pass
:Issues: no issues

*Test 4: Adrià Mercader

:Computer: Dell Inspiron 1564 (Intel i5)
:Version: osgeo-live 4.0rc9
:Results: Pass
:Issues: No issues

*Test 5: Jody Garnett

:Computer: Thinkpad T43
:Version: osgeo-live 4.0rc9
:Results: Pass
:Issues: No issues (hold down F12 to get the bootlist to choose the usb)
:Comment: Wow the experience is so much better - we have to do this :-)

*Test 6: Jody Garnett

:Computer: Macbook Pro
:Version: osgeo-live 4.0rc9
:Results: Fail
:Issues: Unable to boot from usb, not formatted correctly for mac to boot from
:Comment: Internet workarund says to use the DVD to boot the USB

*Test 7: H Bowman

:Computer: 4gb USB drive with full 4.3gb ISO
:Version: osgeo-live 4.0rc9
:Results: {{Fail}}
:Issues: When formated as FAT32 the avail size of the USB goes down to 3.7gb.
:Comment: Make startup disk: "''This device is not large enough to hold the image''"
:: still unknown if Installers would be copied over too.

== VM testing ==

Steps:

*Download full or mini ISO
*Create a VM (''exact method will depend on the VM software used, [[Live GIS Build#Mounting_a_Virtual_Image|see elsewhere in this wiki]]'')
*Boot and play

Results:

=== VirtualBox ===

* ''Brian wrote:'' " running rc9 physical DVD in vbox to type this note"

=== VMWare ===

*-

=== Qemu + KVM ===

*Test version 4.0rc9
*Tested by: H Bowman
*{{issues}}
*Host: Debian/Stable (Lenny) with qemu-kvm 0.12.3+dfsg-4~bpo50+2 from backports.org
*Started with:

kvm -cdrom osgeolive-4.0rc9.iso -m 1024 -cpu phenom

:- All seems to be working, except for <tt>/usr/local/share/*Installers</tt> symlinks, which are broken because /cdrom is a real dir and not a symlink to /media/cdrom. See also <tt>/etc/mtab</tt> vs. <tt>/etc/fstab</tt>.



[[Category:Live-demo]]

Live GIS Disc/Errata/8.0

2014-08-23T07:38:35Z

Wiki-HamishBowman: /* Instructions for changing language and keyboard layout */

= Problems which have come to light after the 8.0 image went to press =

Many of these problems will be fixed in our code repository now, and eligible to go into a possible 8.0.1 release.
Fixes given below can be applied by hand; USB-drive and Virtual-machine users will only have to do it once, DVD users will have to re-do it every time they boot. "''Sorry for the inconvenience''."

* New bugs may be reported and known bugs viewed on the [http://trac.osgeo.org/osgeo/query?status=assigned&status=new&status=reopened&component=LiveDVD&order=priority&col=id&col=summary&col=component&col=milestone&col=status&col=type&col=priority&milestone=OSGeoLive8.0&type=defect OSGeo Trac system].

== Instructions for changing language and keyboard layout ==

;Problem:
The instructions for changing the language and keyboard layout in the desktop-login welcome message are somewhat out of date.

;Solution:
The instructions found in the main Help page are up to date, use them instead.

== GeoNode ==

;Problem:
Layers do not properly load.

;Solution:
In discussion.

== GMT and MB-System ==

;Problem:
GMT in Ubuntu 14.04 has a bug reading the coastline files causing the <tt>pscoast</tt> program to crash or never complete.

;Solution:
In discussion.

== GRASS GIS IPython Examples ==

;Problem
Using the Processing (SEXTANTE) Toolbox in QGIS breaks GRASS's startup history file, which causes the IPython examples to fail.

;Solution
Users will have to start GRASS and reset the main GIS Database path to <tt>/home/user/grassdata</tt>, then start in a GRASS session and exit from it again. The new startup history file is saved upon exiting from the GRASS terminal session.

== OpenJUMP ==

;Problem:
Fails to start on systems with more than 4GB of RAM.

;Solution:
Edit the /usr/bin/openjump startup script and comment out JAVA_MAXMEM= on line 185.

== uDig ==

;Problem:
The program crashes the first time you run it.

;Solution:
Just try again, after that it works ok.

== Other ==

(''minor issues'')

* Mapfish database exists in QGIS's list of Postgres databases, but is not available.
* The 52nSOS database in QGIS's list of Postgres databases is actually "52nsos", all lower case. You can fix that with the <tt>[Edit]</tt> button.

[[Category: Live-demo]]

Live GIS Disc/Errata/8.0

2014-08-23T07:38:14Z

Wiki-HamishBowman: /* Instructions for changing language and keyboard layout */

= Problems which have come to light after the 8.0 image went to press =

Many of these problems will be fixed in our code repository now, and eligible to go into a possible 8.0.1 release.
Fixes given below can be applied by hand; USB-drive and Virtual-machine users will only have to do it once, DVD users will have to re-do it every time they boot. "''Sorry for the inconvenience''."

* New bugs may be reported and known bugs viewed on the [http://trac.osgeo.org/osgeo/query?status=assigned&status=new&status=reopened&component=LiveDVD&order=priority&col=id&col=summary&col=component&col=milestone&col=status&col=type&col=priority&milestone=OSGeoLive8.0&type=defect OSGeo Trac system].

== Instructions for changing language and keyboard layout ==

;Problem:
The instructions for changing the language and keyboard layout in the welcome message are somewhat out of date.

;Solution:
The instructions found in the main Help page are up to date, use them instead.

== GeoNode ==

;Problem:
Layers do not properly load.

;Solution:
In discussion.

== GMT and MB-System ==

;Problem:
GMT in Ubuntu 14.04 has a bug reading the coastline files causing the <tt>pscoast</tt> program to crash or never complete.

;Solution:
In discussion.

== GRASS GIS IPython Examples ==

;Problem
Using the Processing (SEXTANTE) Toolbox in QGIS breaks GRASS's startup history file, which causes the IPython examples to fail.

;Solution
Users will have to start GRASS and reset the main GIS Database path to <tt>/home/user/grassdata</tt>, then start in a GRASS session and exit from it again. The new startup history file is saved upon exiting from the GRASS terminal session.

== OpenJUMP ==

;Problem:
Fails to start on systems with more than 4GB of RAM.

;Solution:
Edit the /usr/bin/openjump startup script and comment out JAVA_MAXMEM= on line 185.

== uDig ==

;Problem:
The program crashes the first time you run it.

;Solution:
Just try again, after that it works ok.

== Other ==

(''minor issues'')

* Mapfish database exists in QGIS's list of Postgres databases, but is not available.
* The 52nSOS database in QGIS's list of Postgres databases is actually "52nsos", all lower case. You can fix that with the <tt>[Edit]</tt> button.

[[Category: Live-demo]]

Live GIS Disc/Errata/8.0

2014-08-23T07:38:06Z

Wiki-HamishBowman: ch lang

= Problems which have come to light after the 8.0 image went to press =

Many of these problems will be fixed in our code repository now, and eligible to go into a possible 8.0.1 release.
Fixes given below can be applied by hand; USB-drive and Virtual-machine users will only have to do it once, DVD users will have to re-do it every time they boot. "''Sorry for the inconvenience''."

* New bugs may be reported and known bugs viewed on the [http://trac.osgeo.org/osgeo/query?status=assigned&status=new&status=reopened&component=LiveDVD&order=priority&col=id&col=summary&col=component&col=milestone&col=status&col=type&col=priority&milestone=OSGeoLive8.0&type=defect OSGeo Trac system].

== Instructions for changing language and keyboard layout ==

;Problem:
The instructions for changing the language and keyboard layout in the welcome message are somewhat out of date.

;Solution:
The instructions found in the main Help page are up to date, use them instead.

== GeoNode ==

;Problem:
Layers do not properly load.

;Solution:
In discussion.

== GMT and MB-System ==

;Problem:
GMT in Ubuntu 14.04 has a bug reading the coastline files causing the <tt>pscoast</tt> program to crash or never complete.

;Solution:
In discussion.

== GRASS GIS IPython Examples ==

;Problem
Using the Processing (SEXTANTE) Toolbox in QGIS breaks GRASS's startup history file, which causes the IPython examples to fail.

;Solution
Users will have to start GRASS and reset the main GIS Database path to <tt>/home/user/grassdata</tt>, then start in a GRASS session and exit from it again. The new startup history file is saved upon exiting from the GRASS terminal session.

== OpenJUMP ==

;Problem:
Fails to start on systems with more than 4GB of RAM.

;Solution:
Edit the /usr/bin/openjump startup script and comment out JAVA_MAXMEM= on line 185.

== uDig ==

;Problem:
The program crashes the first time you run it.

;Solution:
Just try again, after that it works ok.

== Other ==

(''minor issues'')

* Mapfish database exists in QGIS's list of Postgres databases, but is not available.
* The 52nSOS database in QGIS's list of Postgres databases is actually "52nsos", all lower case. You can fix that with the <tt>[Edit]</tt> button.

[[Category: Live-demo]]

Live GIS Disc/Errata/8.0

2014-08-23T07:33:54Z

Wiki-HamishBowman: /* GeoNode */

= Problems which have come to light after the 8.0 image went to press =

Many of these problems will be fixed in our code repository now, and eligible to go into a possible 8.0.1 release.
Fixes given below can be applied by hand; USB-drive and Virtual-machine users will only have to do it once, DVD users will have to re-do it every time they boot. "''Sorry for the inconvenience''."

* New bugs may be reported and known bugs viewed on the [http://trac.osgeo.org/osgeo/query?status=assigned&status=new&status=reopened&component=LiveDVD&order=priority&col=id&col=summary&col=component&col=milestone&col=status&col=type&col=priority&milestone=OSGeoLive8.0&type=defect OSGeo Trac system].

== GeoNode ==

;Problem:
Layers do not properly load.

;Solution:
In discussion.

== GMT and MB-System ==

;Problem:
GMT in Ubuntu 14.04 has a bug reading the coastline files causing the <tt>pscoast</tt> program to crash or never complete.

;Solution:
In discussion.

== GRASS GIS IPython Examples ==

;Problem
Using the Processing (SEXTANTE) Toolbox in QGIS breaks GRASS's startup history file, which causes the IPython examples to fail.

;Solution
Users will have to start GRASS and reset the main GIS Database path to <tt>/home/user/grassdata</tt>, then start in a GRASS session and exit from it again. The new startup history file is saved upon exiting from the GRASS terminal session.

== OpenJUMP ==

;Problem:
Fails to start on systems with more than 4GB of RAM.

;Solution:
Edit the /usr/bin/openjump startup script and comment out JAVA_MAXMEM= on line 185.

== uDig ==

;Problem:
The program crashes the first time you run it.

;Solution:
Just try again, after that it works ok.

== Other ==

(''minor issues'')

* Mapfish database exists in QGIS's list of Postgres databases, but is not available.
* The 52nSOS database in QGIS's list of Postgres databases is actually "52nsos", all lower case. You can fix that with the <tt>[Edit]</tt> button.

[[Category: Live-demo]]

Live GIS Disc/Errata/8.0

2014-08-23T07:33:21Z

Wiki-HamishBowman: /* GRASS GIS IPython Examples */

= Problems which have come to light after the 8.0 image went to press =

Many of these problems will be fixed in our code repository now, and eligible to go into a possible 8.0.1 release.
Fixes given below can be applied by hand; USB-drive and Virtual-machine users will only have to do it once, DVD users will have to re-do it every time they boot. "''Sorry for the inconvenience''."

* New bugs may be reported and known bugs viewed on the [http://trac.osgeo.org/osgeo/query?status=assigned&status=new&status=reopened&component=LiveDVD&order=priority&col=id&col=summary&col=component&col=milestone&col=status&col=type&col=priority&milestone=OSGeoLive8.0&type=defect OSGeo Trac system].

== GeoNode ==

;Problem:
Layers do not properly load.

;Solution:
In discussion.

== GMT and MB-System ==

;Problem:
GMT in Ubuntu 14.04 has a bug reading the coastline files causing the <tt>pscoast</tt> program to crash or never complete.

;Solution:
In discussion.

== GRASS GIS IPython Examples ==

;Problem
Using the Processing (SEXTANTE) Toolbox in QGIS breaks GRASS's startup history file, which causes the IPython examples to fail.

;Solution
Users will have to start GRASS and reset the main GIS Database path to <tt>/home/user/grassdata</tt>, then start in a GRASS session and exit from it again. The new startup history file is saved upon exiting from the GRASS terminal session.

== OpenJUMP ==

;Problem:
Fails to start on systems with more than 4GB of RAM.

;Solution:
Edit the /usr/bin/openjump startup script and comment out JAVA_MAXMEM= on line 185.

== uDig ==

;Problem:
The program crashes the first time you run it.

;Solution:
Just try again, after that it works ok.

== Other ==

(''minor issues'')

* Mapfish database exists in QGIS's list of Postgres databases, but is not available.
* The 52nSOS database in QGIS's list of Postgres databases is actually "52nsos", all lower case. You can fix that with the <tt>[Edit]</tt> button.

[[Category: Live-demo]]

Live GIS Disc/Errata/8.0

2014-08-23T07:32:16Z

Wiki-HamishBowman: /* OpenJUMP */

= Problems which have come to light after the 8.0 image went to press =

Many of these problems will be fixed in our code repository now, and eligible to go into a possible 8.0.1 release.
Fixes given below can be applied by hand; USB-drive and Virtual-machine users will only have to do it once, DVD users will have to re-do it every time they boot. "''Sorry for the inconvenience''."

* New bugs may be reported and known bugs viewed on the [http://trac.osgeo.org/osgeo/query?status=assigned&status=new&status=reopened&component=LiveDVD&order=priority&col=id&col=summary&col=component&col=milestone&col=status&col=type&col=priority&milestone=OSGeoLive8.0&type=defect OSGeo Trac system].

== GeoNode ==

;Problem:
Layers do not properly load.

;Solution:
In discussion.

== GMT and MB-System ==

;Problem:
GMT in Ubuntu 14.04 has a bug reading the coastline files causing the <tt>pscoast</tt> program to crash or never complete.

;Solution:
In discussion.

== GRASS GIS IPython Examples ==

Using the Processing (SEXTANTE) Toolbox in QGIS breaks GRASS's startup history file, which causes the IPython examples to fail. Users will have to start GRASS and reset the main GIS Database path to <tt>/home/user/grassdata</tt>, then start in a GRASS session and exit from it again. The new startup history file is saved upon exiting from the GRASS terminal session.

== OpenJUMP ==

;Problem:
Fails to start on systems with more than 4GB of RAM.

;Solution:
Edit the /usr/bin/openjump startup script and comment out JAVA_MAXMEM= on line 185.

== uDig ==

;Problem:
The program crashes the first time you run it.

;Solution:
Just try again, after that it works ok.

== Other ==

(''minor issues'')

* Mapfish database exists in QGIS's list of Postgres databases, but is not available.
* The 52nSOS database in QGIS's list of Postgres databases is actually "52nsos", all lower case. You can fix that with the <tt>[Edit]</tt> button.

[[Category: Live-demo]]

Live GIS Disc/Errata/8.0

2014-08-23T07:31:44Z

Wiki-HamishBowman: /* GRASS GIS IPython Examples */

= Problems which have come to light after the 8.0 image went to press =

Many of these problems will be fixed in our code repository now, and eligible to go into a possible 8.0.1 release.
Fixes given below can be applied by hand; USB-drive and Virtual-machine users will only have to do it once, DVD users will have to re-do it every time they boot. "''Sorry for the inconvenience''."

* New bugs may be reported and known bugs viewed on the [http://trac.osgeo.org/osgeo/query?status=assigned&status=new&status=reopened&component=LiveDVD&order=priority&col=id&col=summary&col=component&col=milestone&col=status&col=type&col=priority&milestone=OSGeoLive8.0&type=defect OSGeo Trac system].

== GeoNode ==

;Problem:
Layers do not properly load.

;Solution:
In discussion.

== GMT and MB-System ==

;Problem:
GMT in Ubuntu 14.04 has a bug reading the coastline files causing the <tt>pscoast</tt> program to crash or never complete.

;Solution:
In discussion.

== GRASS GIS IPython Examples ==

Using the Processing (SEXTANTE) Toolbox in QGIS breaks GRASS's startup history file, which causes the IPython examples to fail. Users will have to start GRASS and reset the main GIS Database path to <tt>/home/user/grassdata</tt>, then start in a GRASS session and exit from it again. The new startup history file is saved upon exiting from the GRASS terminal session.

== OpenJUMP ==

;Problem:
Fails to start on systems with more than 4GB of RAM.

;Solution:
Edit the /usr/bin/openjump startup script and comment out the JAVA_MAXMEM= on line 185.

== uDig ==

;Problem:
The program crashes the first time you run it.

;Solution:
Just try again, after that it works ok.

== Other ==

(''minor issues'')

* Mapfish database exists in QGIS's list of Postgres databases, but is not available.
* The 52nSOS database in QGIS's list of Postgres databases is actually "52nsos", all lower case. You can fix that with the <tt>[Edit]</tt> button.

[[Category: Live-demo]]

Live GIS Disc/Errata/8.0

2014-08-23T07:31:17Z

Wiki-HamishBowman: /* GRASS GIS IPython Examples */

= Problems which have come to light after the 8.0 image went to press =

Many of these problems will be fixed in our code repository now, and eligible to go into a possible 8.0.1 release.
Fixes given below can be applied by hand; USB-drive and Virtual-machine users will only have to do it once, DVD users will have to re-do it every time they boot. "''Sorry for the inconvenience''."

* New bugs may be reported and known bugs viewed on the [http://trac.osgeo.org/osgeo/query?status=assigned&status=new&status=reopened&component=LiveDVD&order=priority&col=id&col=summary&col=component&col=milestone&col=status&col=type&col=priority&milestone=OSGeoLive8.0&type=defect OSGeo Trac system].

== GeoNode ==

;Problem:
Layers do not properly load.

;Solution:
In discussion.

== GMT and MB-System ==

;Problem:
GMT in Ubuntu 14.04 has a bug reading the coastline files causing the <tt>pscoast</tt> program to crash or never complete.

;Solution:
In discussion.

== GRASS GIS IPython Examples ==

Using the Processing (SEXTANTE) Toolbox in QGIS breaks GRASS's startup history file, which causes the IPython examples to fail. Users will have to start GRASS and reset the GIS Database path to <tt>/home/user/grassdata</tt>, then start in a GRASS session and exit from it again. The new startup history file is saved upon exiting from the GRASS terminal session.

== OpenJUMP ==

;Problem:
Fails to start on systems with more than 4GB of RAM.

;Solution:
Edit the /usr/bin/openjump startup script and comment out the JAVA_MAXMEM= on line 185.

== uDig ==

;Problem:
The program crashes the first time you run it.

;Solution:
Just try again, after that it works ok.

== Other ==

(''minor issues'')

* Mapfish database exists in QGIS's list of Postgres databases, but is not available.
* The 52nSOS database in QGIS's list of Postgres databases is actually "52nsos", all lower case. You can fix that with the <tt>[Edit]</tt> button.

[[Category: Live-demo]]

Live GIS Disc/Errata/8.0

2014-08-23T07:30:55Z

Wiki-HamishBowman: qgis toolbox breakage

= Problems which have come to light after the 8.0 image went to press =

Many of these problems will be fixed in our code repository now, and eligible to go into a possible 8.0.1 release.
Fixes given below can be applied by hand; USB-drive and Virtual-machine users will only have to do it once, DVD users will have to re-do it every time they boot. "''Sorry for the inconvenience''."

* New bugs may be reported and known bugs viewed on the [http://trac.osgeo.org/osgeo/query?status=assigned&status=new&status=reopened&component=LiveDVD&order=priority&col=id&col=summary&col=component&col=milestone&col=status&col=type&col=priority&milestone=OSGeoLive8.0&type=defect OSGeo Trac system].

== GeoNode ==

;Problem:
Layers do not properly load.

;Solution:
In discussion.

== GMT and MB-System ==

;Problem:
GMT in Ubuntu 14.04 has a bug reading the coastline files causing the <tt>pscoast</tt> program to crash or never complete.

;Solution:
In discussion.

== GRASS GIS IPython Examples ==

Using the Processing (SEXTANTE) Toolbox in QGIS breaks GRASS's startup history, file which causes the IPython examples to fail. Users will have to start GRASS and reset the GIS Database path to <tt>/home/user/grassdata</tt>, then start in a GRASS session and exit from it again. The new startup history file is saved upon exiting from the GRASS terminal session.

== OpenJUMP ==

;Problem:
Fails to start on systems with more than 4GB of RAM.

;Solution:
Edit the /usr/bin/openjump startup script and comment out the JAVA_MAXMEM= on line 185.

== uDig ==

;Problem:
The program crashes the first time you run it.

;Solution:
Just try again, after that it works ok.

== Other ==

(''minor issues'')

* Mapfish database exists in QGIS's list of Postgres databases, but is not available.
* The 52nSOS database in QGIS's list of Postgres databases is actually "52nsos", all lower case. You can fix that with the <tt>[Edit]</tt> button.

[[Category: Live-demo]]

Live GIS Disc/Errata/8.0

2014-08-23T07:26:27Z

Wiki-HamishBowman: /* OpenJUMP */

Live GIS Disc/Errata/8.0

2014-08-23T07:24:15Z

Wiki-HamishBowman: /* Problems which have come to light after the 8.0 image went to press */

Live GIS Disc/Errata/8.0

2014-08-23T07:14:00Z

Wiki-HamishBowman: openjump

= Problems which have come to light after the 8.0 image went to press =

These will be fixed in our code repository now, and in a possible 8.0.1 release.
Fixes given below can be applied by hand; USB-drive and Virtual-machine users will only have to do it once, DVD users will have to re-do it every time they boot. "''Sorry for the inconvenience''."

* New bugs may be reported and known bugs viewed on the [http://trac.osgeo.org/osgeo/query?status=assigned&status=new&status=reopened&component=LiveDVD&order=priority&col=id&col=summary&col=component&col=milestone&col=status&col=type&col=priority&milestone=OSGeoLive8.0&type=defect OSGeo Trac system].

== GeoNode ==

;Problem:
Layers do not properly load.

;Solution:
In discussion.

== GMT and MB-System ==

;Problem:
GMT in Ubuntu 14.04 has a bug reading the coastline files causing the <tt>pscoast</tt> program to crash or never complete.

;Solution:
In discussion.

== OpenJUMP ==

;Problem:
Fails to start on systems with more than 4GB of RAM.

;Solution:
Edit the /usr/bin/openjump startup script and comment out the JAVA_MAXMEM line.

== uDig ==

;Problem:
The program crashes the first time you run it.

;Solution:
Just try again, after that it works ok.

== Other ==

(''minor issues'')

* Mapfish database exists in QGIS's list of Postgres databases, but is not available.
* The 52nSOS database in QGIS's list of Postgres databases is actually "52nsos", all lower case. You can fix that with the <tt>[Edit]</tt> button.

[[Category: Live-demo]]

Live GIS Disc/Errata/8.0

2014-08-23T07:12:50Z

Wiki-HamishBowman: /* Other */ 52nsos

= Problems which have come to light after the 8.0 image went to press =

These will be fixed in our code repository now, and in a possible 8.0.1 release.
Fixes given below can be applied by hand; USB-drive and Virtual-machine users will only have to do it once, DVD users will have to re-do it every time they boot. "''Sorry for the inconvenience''."

* New bugs may be reported and known bugs viewed on the [http://trac.osgeo.org/osgeo/query?status=assigned&status=new&status=reopened&component=LiveDVD&order=priority&col=id&col=summary&col=component&col=milestone&col=status&col=type&col=priority&milestone=OSGeoLive8.0&type=defect OSGeo Trac system].

== GeoNode ==

;Problem:
Layers do not properly load.

;Solution:
In discussion.

== GMT and MB-System ==

;Problem:
GMT in Ubuntu 14.04 has a bug reading the coastline files causing the <tt>pscoast</tt> program to crash or never complete.

;Solution:
In discussion.

== uDig ==

;Problem:
The program crashes the first time you run it.

;Solution:
Just try again, after that it works ok.

== Other ==

(''minor issues'')

* Mapfish database exists in QGIS's list of Postgres databases, but is not available.
* The 52nSOS database in QGIS's list of Postgres databases is actually "52nsos", all lower case. You can fix that with the <tt>[Edit]</tt> button.

[[Category: Live-demo]]

Live GIS Disc Press Release 54

2014-08-23T07:07:10Z

Wiki-HamishBowman: /* Sponsoring organisations */ wikilink fix

= OSGeo-Live 8.0 Released =

25 August 2014

Version 8.0 of the [http://live.osgeo.org OSGeo-Live GIS software collection] has been released, featuring over 50 open source, standards compliant geospatial applications.

==Release Highlights==

; Lubuntu 14.04 LTS
: We have moved from Xubuntu to the lighter Lubuntu base operating system, which starts up faster, requires less RAM, and uses less disk space, making it a better choice for running in a Virtual Machine or from a LiveDVD.
: We have upgraded to the latest 14.04 stable Long Term Support (LTS) release. LTS releases are put out every 3 years by Ubuntu.

; Debian packaging
: We have steadily been moving more of our projects to .deb packaging, which makes the projects easier to install both on OSGeo-Live and into other Debian based systems. This also allows us to push out important post-release fixes if they are needed.

; Applications
: 34 geospatial programs have been updated to newer versions.

==About OSGeo-Live==
OSGeo-Live is a self-contained bootable DVD, USB flash drive and Virtual Machine based upon Ubuntu Linux. It is pre-configured and ready to use, with a wide variety of robust open source geospatial software. It includes:

* Over 50 quality geospatial Open Source applications installed and pre-configured
* Free world maps and sample datasets
* Project Overview and step-by-step Quickstart for each application
* Lightning presentation of all applications, along with speaker's script
* Overviews of key OGC standards
* Translations to multiple languages

http://live.osgeo.org

== Credits ==

Over 180 people have directly helped with OSGeo-Live packaging, documenting and translating, and thousands have been involved in building the packaged software.

Developers, packagers, documenters and translators include:

Activity Workshop, Agustin Diez, Aikaterini Kapsampeli, Alan Beccati, Alan Boudreault, Alessandro Furieri, Alexander Bruy, Alexander Kleshnin, Alexander Muriy, Alexandre Dube, Alexey Ardyakov, Alex Mandel, Amy Gao, Andrea Antonello, Andrea Yanza, Andrey Syrokomskiy, Andry Rustanto, Angelos Tzotsos, Anna Munoz, Antonio Falciano, Anton Novichikhin, Anton Patrushev, Argyros Argyridis, Ariel Nunez, Assumpcio Termens, Astrid Emde, Barry Rowlingson, Benjamin Pross, Brian Hamlin, Bruno Binet, Bu Kun, Cameron Shorter, Christophe Tufféry, Christos Iossifidis, Cristhian Pin, Damian Wojslaw, Dane Springmeyer, Daniel Kastl, Danilo Bretschneider, Daria Svidzinska, David Mateos, Denis Rykov, Diego Gonzalez, Diego Migliavacca, Dimitar Misev, Dmitry Baryshnikov, Dominik Helle, Edgar Soldin, Eike Hinderk Jürrens, Elena Mezzini, Eric Lemoine, Erika Pillu, Estela Llorente, Etienne Delay, Etienne Dube, Evgeny Nikulin, Fran Boon, Francois Prunayre, Frank Gasdorf, Frank Warmerdam, Friedjoff Trautwein, Gavin Treadgold, Giuseppe Calamita, Grald Fenoy, Grigory Rozhentsov, Guy Griffiths, Hamish Bowman, Haruyuki Seki, Henry Addo, Hernan Olivera, Hirofumi Hayashi, Howard Butler, Hyeyeong Choe, Ian Edwards, Ian Turton, Ilya Filippov, Jackie Ng, Jan Drewnak, Jane Lewis, Javier Rodrigo, Javier Sanchez, Jesus Gomez, Jim Klassen, Jing Wang, Jinsongdi Yu, Jody Garnett, Johan Van de Wauw, John Bryant, Jorge Arevalo, Jorge Sanz, Jose Antonio Canalejo, Jose Vicente Higon, Judit Mays, Klokan Petr Pridal, Ko Nagase, Kristof Lange, kuzkok, Lance McKee, Lars Lingner, Luca Delucchi, Lucia Sanjaime, Mage Whopper, Manuel Grizonnet, Marc-Andre Barbeau, Marco Curreli, Marco Puppin, Marc Torres, Margherita Di Leo, Maria Vakalopoulou, Mario Andino, Mark Leslie, Massimo Di Stefano, Matthias Streulens, Mauricio Miranda, Mauricio Pazos, Maxim Dubinin, Michael Michaud, Michael Owonibi, Micha Silver, Mike Adair, Milena Nowotarska, M Iqnaul Haq Siregar, Nacho Varela, Nadiia Gorash, Nathaniel V. Kelso, Ned Horning, Nobusuke Iwasaki, Oliver Tonnhofer, Oscar Fonts, Otto Dassau, Pasquale Di Donato, Patric Hafner, Paul Meems, Pavel, Pedro-Juan Ferrer, Pirmin Kalberer, Raf Roset, Regina Obe, Ricardo Pinho, Roald de Wit, Roberta Fagandini, Roberto Antolin, Roger Veciana, Ruth Schoenbuchner, Samuel Mesa, Scott Penrose, Sergey Grachev, Sergio Banos, Simon Cropper, Simon Pigot, Stefan A. Tzeggai, Stefan Hansen, Stefan Steiniger, Stephan Meissl, Steve Lime, Takayuki Nuimura, Thierry Badard, Thomas Baschetti, Thomas Gratier, Tom Kralidis, Toshikazu Seto, Trevor Wekel, Valenty Gonzalez, Vera, Xianfeng Song, Yoichi Kayama, Zhengfan Lin

==Sponsoring organisations==

* [http://www.osgeo.org The Open Source Geospatial Foundation] provides development & hosting infrastructure for OSGeo-Live and many of the included applications.
* [http://www.lisasoft.com LISAsoft] provides sustaining resources and staff toward management and packaging.
* [http://ice.ucdavis.edu Information Center for the Environment (ICE)] at the University of California, Davis provides hardware resources and development support.
* [http://www.ntua.gr Remote Sensing Laboratory at the National Technical University of Athens], provides hardware resources and development support.
* The [http://wiki.debian.org/DebianGis DebianGIS] and [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] teams provide and quality-assure many of the core packages.

[[Category: Live-demo]]

Live GIS Disc Press Release 54

2014-08-23T07:06:10Z

Wiki-HamishBowman: /* About OSGeo-Live */ comma overuse

= OSGeo-Live 8.0 Released =

25 August 2014

Version 8.0 of the [http://live.osgeo.org OSGeo-Live GIS software collection] has been released, featuring over 50 open source, standards compliant geospatial applications.

==Release Highlights==

; Lubuntu 14.04 LTS
: We have moved from Xubuntu to the lighter Lubuntu base operating system, which starts up faster, requires less RAM, and uses less disk space, making it a better choice for running in a Virtual Machine or from a LiveDVD.
: We have upgraded to the latest 14.04 stable Long Term Support (LTS) release. LTS releases are put out every 3 years by Ubuntu.

; Debian packaging
: We have steadily been moving more of our projects to .deb packaging, which makes the projects easier to install both on OSGeo-Live and into other Debian based systems. This also allows us to push out important post-release fixes if they are needed.

; Applications
: 34 geospatial programs have been updated to newer versions.

==About OSGeo-Live==
OSGeo-Live is a self-contained bootable DVD, USB flash drive and Virtual Machine based upon Ubuntu Linux. It is pre-configured and ready to use, with a wide variety of robust open source geospatial software. It includes:

* Over 50 quality geospatial Open Source applications installed and pre-configured
* Free world maps and sample datasets
* Project Overview and step-by-step Quickstart for each application
* Lightning presentation of all applications, along with speaker's script
* Overviews of key OGC standards
* Translations to multiple languages

http://live.osgeo.org

== Credits ==

Over 180 people have directly helped with OSGeo-Live packaging, documenting and translating, and thousands have been involved in building the packaged software.

Developers, packagers, documenters and translators include:

Activity Workshop, Agustin Diez, Aikaterini Kapsampeli, Alan Beccati, Alan Boudreault, Alessandro Furieri, Alexander Bruy, Alexander Kleshnin, Alexander Muriy, Alexandre Dube, Alexey Ardyakov, Alex Mandel, Amy Gao, Andrea Antonello, Andrea Yanza, Andrey Syrokomskiy, Andry Rustanto, Angelos Tzotsos, Anna Munoz, Antonio Falciano, Anton Novichikhin, Anton Patrushev, Argyros Argyridis, Ariel Nunez, Assumpcio Termens, Astrid Emde, Barry Rowlingson, Benjamin Pross, Brian Hamlin, Bruno Binet, Bu Kun, Cameron Shorter, Christophe Tufféry, Christos Iossifidis, Cristhian Pin, Damian Wojslaw, Dane Springmeyer, Daniel Kastl, Danilo Bretschneider, Daria Svidzinska, David Mateos, Denis Rykov, Diego Gonzalez, Diego Migliavacca, Dimitar Misev, Dmitry Baryshnikov, Dominik Helle, Edgar Soldin, Eike Hinderk Jürrens, Elena Mezzini, Eric Lemoine, Erika Pillu, Estela Llorente, Etienne Delay, Etienne Dube, Evgeny Nikulin, Fran Boon, Francois Prunayre, Frank Gasdorf, Frank Warmerdam, Friedjoff Trautwein, Gavin Treadgold, Giuseppe Calamita, Grald Fenoy, Grigory Rozhentsov, Guy Griffiths, Hamish Bowman, Haruyuki Seki, Henry Addo, Hernan Olivera, Hirofumi Hayashi, Howard Butler, Hyeyeong Choe, Ian Edwards, Ian Turton, Ilya Filippov, Jackie Ng, Jan Drewnak, Jane Lewis, Javier Rodrigo, Javier Sanchez, Jesus Gomez, Jim Klassen, Jing Wang, Jinsongdi Yu, Jody Garnett, Johan Van de Wauw, John Bryant, Jorge Arevalo, Jorge Sanz, Jose Antonio Canalejo, Jose Vicente Higon, Judit Mays, Klokan Petr Pridal, Ko Nagase, Kristof Lange, kuzkok, Lance McKee, Lars Lingner, Luca Delucchi, Lucia Sanjaime, Mage Whopper, Manuel Grizonnet, Marc-Andre Barbeau, Marco Curreli, Marco Puppin, Marc Torres, Margherita Di Leo, Maria Vakalopoulou, Mario Andino, Mark Leslie, Massimo Di Stefano, Matthias Streulens, Mauricio Miranda, Mauricio Pazos, Maxim Dubinin, Michael Michaud, Michael Owonibi, Micha Silver, Mike Adair, Milena Nowotarska, M Iqnaul Haq Siregar, Nacho Varela, Nadiia Gorash, Nathaniel V. Kelso, Ned Horning, Nobusuke Iwasaki, Oliver Tonnhofer, Oscar Fonts, Otto Dassau, Pasquale Di Donato, Patric Hafner, Paul Meems, Pavel, Pedro-Juan Ferrer, Pirmin Kalberer, Raf Roset, Regina Obe, Ricardo Pinho, Roald de Wit, Roberta Fagandini, Roberto Antolin, Roger Veciana, Ruth Schoenbuchner, Samuel Mesa, Scott Penrose, Sergey Grachev, Sergio Banos, Simon Cropper, Simon Pigot, Stefan A. Tzeggai, Stefan Hansen, Stefan Steiniger, Stephan Meissl, Steve Lime, Takayuki Nuimura, Thierry Badard, Thomas Baschetti, Thomas Gratier, Tom Kralidis, Toshikazu Seto, Trevor Wekel, Valenty Gonzalez, Vera, Xianfeng Song, Yoichi Kayama, Zhengfan Lin

==Sponsoring organisations==

* [http://www.osgeo.org The Open Source Geospatial Foundation] provides development & hosting infrastructure for OSGeo-Live and many of the included applications.
* [http://www.lisasoft.com LISAsoft] provides sustaining resources and staff toward management and packaging.
* [http://ice.ucdavis.edu Information Center for the Environment (ICE)] at the University of California, Davis provides hardware resources and development support.
* http://www.ntua.gr Remote Sensing Laboratory at the National Technical University of Athens], provides hardware resources and development support.
* The [http://wiki.debian.org/DebianGis DebianGIS] and [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] teams provide and quality-assure many of the core packages.

[[Category: Live-demo]]

Live GIS Disc Press Release 54

2014-08-23T07:04:26Z

Wiki-HamishBowman: /* Release Highlights */ deb ppa benefits

= OSGeo-Live 8.0 Released =

25 August 2014

Version 8.0 of the [http://live.osgeo.org OSGeo-Live GIS software collection] has been released, featuring over 50 open source, standards compliant geospatial applications.

==Release Highlights==

; Lubuntu 14.04 LTS
: We have moved from Xubuntu to the lighter Lubuntu base operating system, which starts up faster, requires less RAM, and uses less disk space, making it a better choice for running in a Virtual Machine or from a LiveDVD.
: We have upgraded to the latest 14.04 stable Long Term Support (LTS) release. LTS releases are put out every 3 years by Ubuntu.

; Debian packaging
: We have steadily been moving more of our projects to .deb packaging, which makes the projects easier to install both on OSGeo-Live and into other Debian based systems. This also allows us to push out important post-release fixes if they are needed.

; Applications
: 34 geospatial programs have been updated to newer versions.

==About OSGeo-Live==
OSGeo-Live is a self-contained bootable DVD, USB flash drive and Virtual Machine based upon Ubuntu Linux. It is pre-configured and ready to use, with a wide variety of robust open source geospatial software. It includes:

* Over 50 quality geospatial Open Source applications installed and pre-configured
* Free world maps and sample datasets
* Project Overview, and step-by-step Quickstart for each application
* Lightning presentation of all applications, along with speaker's script
* Overviews of key OGC standards
* Translations to multiple languages

http://live.osgeo.org

== Credits ==

Over 180 people have directly helped with OSGeo-Live packaging, documenting and translating, and thousands have been involved in building the packaged software.

Developers, packagers, documenters and translators include:

Activity Workshop, Agustin Diez, Aikaterini Kapsampeli, Alan Beccati, Alan Boudreault, Alessandro Furieri, Alexander Bruy, Alexander Kleshnin, Alexander Muriy, Alexandre Dube, Alexey Ardyakov, Alex Mandel, Amy Gao, Andrea Antonello, Andrea Yanza, Andrey Syrokomskiy, Andry Rustanto, Angelos Tzotsos, Anna Munoz, Antonio Falciano, Anton Novichikhin, Anton Patrushev, Argyros Argyridis, Ariel Nunez, Assumpcio Termens, Astrid Emde, Barry Rowlingson, Benjamin Pross, Brian Hamlin, Bruno Binet, Bu Kun, Cameron Shorter, Christophe Tufféry, Christos Iossifidis, Cristhian Pin, Damian Wojslaw, Dane Springmeyer, Daniel Kastl, Danilo Bretschneider, Daria Svidzinska, David Mateos, Denis Rykov, Diego Gonzalez, Diego Migliavacca, Dimitar Misev, Dmitry Baryshnikov, Dominik Helle, Edgar Soldin, Eike Hinderk Jürrens, Elena Mezzini, Eric Lemoine, Erika Pillu, Estela Llorente, Etienne Delay, Etienne Dube, Evgeny Nikulin, Fran Boon, Francois Prunayre, Frank Gasdorf, Frank Warmerdam, Friedjoff Trautwein, Gavin Treadgold, Giuseppe Calamita, Grald Fenoy, Grigory Rozhentsov, Guy Griffiths, Hamish Bowman, Haruyuki Seki, Henry Addo, Hernan Olivera, Hirofumi Hayashi, Howard Butler, Hyeyeong Choe, Ian Edwards, Ian Turton, Ilya Filippov, Jackie Ng, Jan Drewnak, Jane Lewis, Javier Rodrigo, Javier Sanchez, Jesus Gomez, Jim Klassen, Jing Wang, Jinsongdi Yu, Jody Garnett, Johan Van de Wauw, John Bryant, Jorge Arevalo, Jorge Sanz, Jose Antonio Canalejo, Jose Vicente Higon, Judit Mays, Klokan Petr Pridal, Ko Nagase, Kristof Lange, kuzkok, Lance McKee, Lars Lingner, Luca Delucchi, Lucia Sanjaime, Mage Whopper, Manuel Grizonnet, Marc-Andre Barbeau, Marco Curreli, Marco Puppin, Marc Torres, Margherita Di Leo, Maria Vakalopoulou, Mario Andino, Mark Leslie, Massimo Di Stefano, Matthias Streulens, Mauricio Miranda, Mauricio Pazos, Maxim Dubinin, Michael Michaud, Michael Owonibi, Micha Silver, Mike Adair, Milena Nowotarska, M Iqnaul Haq Siregar, Nacho Varela, Nadiia Gorash, Nathaniel V. Kelso, Ned Horning, Nobusuke Iwasaki, Oliver Tonnhofer, Oscar Fonts, Otto Dassau, Pasquale Di Donato, Patric Hafner, Paul Meems, Pavel, Pedro-Juan Ferrer, Pirmin Kalberer, Raf Roset, Regina Obe, Ricardo Pinho, Roald de Wit, Roberta Fagandini, Roberto Antolin, Roger Veciana, Ruth Schoenbuchner, Samuel Mesa, Scott Penrose, Sergey Grachev, Sergio Banos, Simon Cropper, Simon Pigot, Stefan A. Tzeggai, Stefan Hansen, Stefan Steiniger, Stephan Meissl, Steve Lime, Takayuki Nuimura, Thierry Badard, Thomas Baschetti, Thomas Gratier, Tom Kralidis, Toshikazu Seto, Trevor Wekel, Valenty Gonzalez, Vera, Xianfeng Song, Yoichi Kayama, Zhengfan Lin

==Sponsoring organisations==

* [http://www.osgeo.org The Open Source Geospatial Foundation] provides development & hosting infrastructure for OSGeo-Live and many of the included applications.
* [http://www.lisasoft.com LISAsoft] provides sustaining resources and staff toward management and packaging.
* [http://ice.ucdavis.edu Information Center for the Environment (ICE)] at the University of California, Davis provides hardware resources and development support.
* http://www.ntua.gr Remote Sensing Laboratory at the National Technical University of Athens], provides hardware resources and development support.
* The [http://wiki.debian.org/DebianGis DebianGIS] and [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] teams provide and quality-assure many of the core packages.

[[Category: Live-demo]]

Live GIS Disc/Errata/8.0

2014-08-22T03:16:47Z

Wiki-HamishBowman: /* Other */

= Problems which have come to light after the 8.0 image went to press =

These will be fixed in our code repository now, and in a possible 8.0.1 release.
Fixes given below can be applied by hand; USB-drive and Virtual-machine users will only have to do it once, DVD users will have to re-do it every time they boot. "''Sorry for the inconvenience''."

* New bugs may be reported and known bugs viewed on the [http://trac.osgeo.org/osgeo/query?status=assigned&status=new&status=reopened&component=LiveDVD&order=priority&col=id&col=summary&col=component&col=milestone&col=status&col=type&col=priority&milestone=OSGeoLive8.0&type=defect OSGeo Trac system].

== GeoNode ==

;Problem:
Layers do not properly load.

;Solution:
In discussion.

== GMT and MB-System ==

;Problem:
GMT in Ubuntu 14.04 has a bug reading the coastline files causing the <tt>pscoast</tt> program to crash or never complete.

;Solution:
In discussion.

== uDig ==

;Problem:
The program crashes the first time you run it.

;Solution:
Just try again, after that it works ok.

== Other ==

(''minor issues'')

* Mapfish database exists in QGIS's list of Postgres databases, but is not available.

[[Category: Live-demo]]

Live GIS Disc/Errata/8.0

2014-08-22T03:16:03Z

Wiki-HamishBowman:

= Problems which have come to light after the 8.0 image went to press =

These will be fixed in our code repository now, and in a possible 8.0.1 release.
Fixes given below can be applied by hand; USB-drive and Virtual-machine users will only have to do it once, DVD users will have to re-do it every time they boot. "''Sorry for the inconvenience''."

* New bugs may be reported and known bugs viewed on the [http://trac.osgeo.org/osgeo/query?status=assigned&status=new&status=reopened&component=LiveDVD&order=priority&col=id&col=summary&col=component&col=milestone&col=status&col=type&col=priority&milestone=OSGeoLive8.0&type=defect OSGeo Trac system].

== GeoNode ==

;Problem:
Layers do not properly load.

;Solution:
In discussion.

== GMT and MB-System ==

;Problem:
GMT in Ubuntu 14.04 has a bug reading the coastline files causing the <tt>pscoast</tt> program to crash or never complete.

;Solution:
In discussion.

== uDig ==

;Problem:
The program crashes the first time you run it.

;Solution:
Just try again, after that it works ok.

== Other ==

(''minor issues'')

* Mapfish database exists in QGIS's list of Postres databases, but is not available.

[[Category: Live-demo]]

Live GIS Disc/Errata/8.0

2014-08-22T03:15:33Z

Wiki-HamishBowman: /* Other */

= Problems which have come to light after the 8.0 image went to press =

These will be fixed in our code repository now, and in a possible 8.0.1 release.
Fixes given below can be applied by hand; USB-drive and Virtual-machine users will only have to do it once, DVD users will have to re-do it every time they boot. "''Sorry for the inconvenience''."

* New bugs may be reported and known bugs viewed on the [http://trac.osgeo.org/osgeo/query?status=assigned&status=new&status=reopened&component=LiveDVD&order=priority&col=id&col=summary&col=component&col=milestone&col=status&col=type&col=priority&milestone=OSGeoLive8.0&type=defect OSGeo Trac system].

== GeoNode ==

;Problem:
Layers do not properly load.

;Solution:
In discussion.

== GMT and MB-System ==

;Problem:
GMT in Ubuntu 14.04 has a bug reading the coastline files causing the <tt>pscoast</tt> program to crash or never complete.

;Solution:
In discussion.

== uDig ==

;Problem:
The program crashes the first time you run it.

;Solution:
Just try again, after that it works ok.

== Other ==

(''minor issues'')

* Mapfish database exists in QGIS's list of Postres databases, but is not available.

[[Category: Live-demo]]

Live GIS Disc/Errata/8.0

2014-08-22T03:14:30Z

Wiki-HamishBowman: +trac link

= Problems which have come to light after the 8.0 image went to press =

These will be fixed in our code repository now, and in a possible 8.0.1 release.
Fixes given below can be applied by hand; USB-drive and Virtual-machine users will only have to do it once, DVD users will have to re-do it every time they boot. "''Sorry for the inconvenience''."

* New bugs may be reported and known bugs viewed on the [http://trac.osgeo.org/osgeo/query?status=assigned&status=new&status=reopened&component=LiveDVD&order=priority&col=id&col=summary&col=component&col=milestone&col=status&col=type&col=priority&milestone=OSGeoLive8.0&type=defect OSGeo Trac system].

== GeoNode ==

;Problem:
Layers do not properly load.

;Solution:
In discussion.

== GMT and MB-System ==

;Problem:
GMT in Ubuntu 14.04 has a bug reading the coastline files causing the <tt>pscoast</tt> program to crash or never complete.

;Solution:
In discussion.

== uDig ==

;Problem:
The program crashes the first time you run it.

;Solution:
Just try again, after that it works ok.

== Other ==

(''minor issues'')

* Mapfish database exists in QGIS's list of Postres databases, but is not available.

Live GIS Disc/Errata/8.0

2014-08-22T03:12:12Z

Wiki-HamishBowman: init

Live GIS Disc

2014-07-27T03:55:48Z

Wiki-HamishBowman: /* Google Summer of Code */ minor link cosmetic

= About OSGeo-Live =

[[File:Osgeolive wordle.png|center|link=http://live.osgeo.org|750px]]

[http://live.osgeo.org OSGeo Live] provides bootable ISO-Images and [http://en.wikipedia.org/wiki/Virtual_machine Virtual Machines] which allow users to try out fully-operational versions of popular Free Geospatial Software without the need to install a thing.

We do this in large part by maintaining automated build scripts which collect many [[OSGeo]] programs and sample data-sets together, and then combine them to form the Live disc or VM itself. By tweaking these scripts, users are free to make their own custom distributions, for example localized in their own language and with local map data.

= Key Links =
== Quick Start ==
* [[Live GIS Disc Quick Start]]

== How to add a project to OSGeoLive ==
* [[Live GIS Add Project]]
* [[Live_GIS_Disc_Apply|Questions to answer when requesting to add an application to OSGeo-Live]]

== Including OSGeo-Live at your event ==
[http://live.osgeo.org OSGeo Live] provides a DVD, USB and a Virtual Machine which allow users to try out fully-operational versions of popular Free Geospatial Software without the need to install a thing. It also includes documentation and a comprehensive presentation.

This is the process to follow if you wish to make use of OSGeo-Live at your conference, workshop or similar event.

; Tell Us
: Add your event to our [[Live GIS History]] page and tell us how you would like to use OSGeo-Live on our [http://lists.osgeo.org/mailman/listinfo/live-demo email list] (or email [http://wiki.osgeo.org/wiki/OSGeo_Advocate#Cameron_Shorter Cameron Shorter] directly). Hearing how OSGeo-Live is used motivates us to keep going, and we plan releases around upcoming events.
; Presentation
: Conference attendees appreciate the [http://live.osgeo.org/en/presentation/index.html OSGeo-Live Lightning Overview], which explains the breadth of OSGeo software, abstract [http://live.osgeo.org/en/presentation/abstract.txt here]. It is often presented by one of the conference organisors, or keynote speakers. You may wish to find a suitable speaker from the [[OSGeo Advocate]] list. The presentation may be given as is, or modified to align with time constraints, presenter's interest, or conference focus. (For prior variants, see [[Live GIS Presentation]].)
; Handing out DVDs or USBs
: OSGeo-Live DVDs and/or USBs are often handed out to all conference delegates, or a smaller number handed out from an OSGeo booth. DVDs are cheaper (around $2 per copy), but USBs provide a better experience as they are faster to boot up and run. You will need to:
:# Work out how to pay for the USBs/DVDs. Usually the price is factored into event budgets. This means you will require commitment from the event Organisors. However you may find an external sponsor, or for smaller print runs, you might find volunteers to print from their computers.
:# Source a local printer, preferably local. Printers typically require 2 weeks to do the print run, although they often will turn around faster if you pay more money.
:# Printing DVDs: The printer will require an [http://live.osgeo.org/en/download.html ISO image], and artwork for the DVD face and DVD sleeve. You may make use of existing [https://svn.osgeo.org/osgeo/livedvd/artwork/sleeve/ artwork] or create your own.
:# Printing USBs: A 4 Gig USB is required for [http://live.osgeo.org/en/download.html osgeo-live-mini] (8 Gig if you wish the full image with windows and mac installers). The process for installing USBs is described [http://live.osgeo.org/en/quickstart/usb_quickstart.html here]. Note that it is important to ask the printer if they can create '''bootable''' USBs. (We have found that many printers are not familiar with the process). It is prudent to [http://live.osgeo.org/en/quickstart/osgeolive_quickstart.html check] the first USB that is printed before printing the rest. You can also print a logo on the USB.
; Workshops
: For workshops, we recommend using OSGeo-Live from a [http://live.osgeo.org/en/quickstart/virtualization_quickstart.html Virtual Machine] or from a USB. Note that some computers can't boot from a USB. OSGeo-Live on a DVD is slow and as such is not recommended for workshops. However it is wise to have a few spare DVDs in case one of your computers can't boot from the USB. Note that OSGeo-Live we have heard some issues when running on Apple Macs, so if using Macs, please test first.
; Poster
: We have a [http://wiki.osgeo.org/wiki/Live_GIS_Disc#Poster Poster] which is useful for hanging on a wall of a conference booth.

== Build Process ==
* [[Live GIS Build]] instructions

== Package List ==
* [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB#gid=13 Package List]
* [[Live_GIS_Disc_Packages#Package_wishlist|Future/wishlist]]

== Documentation ==
[[Live_GIS_Add_Project#Documentation]]

Stable release: http://live.osgeo.org

Nightly build: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/index.html

== Translate ==
* [[Live GIS Translate]] - translate process.
* Docs ready to translate are marked "Final" in our [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 status spreadsheet].
* [http://adhoc.osgeo.osuosl.org/livedvd/translation_status.html Translation Status]

== Artwork ==
You can find the artwork sleeves, background images, booklet at:
* http://trac.osgeo.org/osgeo/browser/livedvd/artwork/

;Version 4.5:
* http://trac.osgeo.org/osgeo/browser/livedvd/artwork/backgrounds/4.5
* http://trac.osgeo.org/osgeo/browser/livedvd/artwork/sleeve/4.5

== Review ==

* [[Live GIS Review]]
* [[Live_GIS_Add_Project#Quickstart_Review_Checklist|Quickstart Review]]

== Presentation ==

[[ Live GIS Presentation ]]

== Poster ==

[[ Live GIS Poster ]]

== Workshops with OSGeoLive ==

[[ Workshops with OSGeoLive ]]

== Schedule ==
* [http://spreadsheets.google.com/ccc?key=tMRaCwabv7SiIG3moHEfMrQ&hl=en_GB Live GIS Disc Schedule]

== Contact Us ==
* Mailing List: http://lists.osgeo.org/mailman/listinfo/live-demo
: The mailing list is [http://news.gmane.org/gmane.comp.gis.osgeo.livedemo archived at Gmane] and [http://osgeo-org.1560.n6.nabble.com/OSGeo-FOSS4G-LiveDVD-f3777350.html Nabble]
* IRC: irc://irc.freenode.net#osgeolive - [http://irclogs.geoapt.com/osgeolive/ Logs]
** You can log into IRC from: http://webchat.freenode.net/ Enter a nickname, and set channel=osgeolive
** As of April 2014, we are meeting weekly on IRC, Thursday afternoon in the Americas, Thursday evening in Europe, Friday morning in Australia/New Zealand: http://www.timeanddate.com/worldclock/meetingdetails.html?hour=20&min=30&sec=0&p1=179&p2=189&p3=224&p4=22&p5=240&p6=196&p7=215
* [[Live_GIS_Disc_Meeting_Minutes|Meeting Minutes]]

== Downloads ==

Latest Stable Release: http://live.osgeo.org/en/download.html

Latest Development Release: http://aiolos.survey.ntua.gr/gisvm/dev/

Older Releases: http://download.osgeo.org/livedvd

== Issue Tracker==
Our issue tracker is [http://trac.osgeo.org/osgeo/query?group=status&component=LiveDVD&order=priority hosted at OSGeo's Trac system], and you will need to create an [http://www.osgeo.org/osgeo_userid OSGeo UserId] before you can login and edit issues. To distinguish the LiveDVD project from other OSGeo projects, use the following conventions:
; Component field
: Set to `<tt>LiveDVD</tt>`
; Keywords:
: Version: Set to base release version: eg: 5.0, 5.5 (not 5.5rc1)
: Application: Set to application with issue (use lower case): eg: "geoserver"

; [https://trac.osgeo.org/osgeo/report/10 List of open tickets]

* [https://trac.osgeo.org/osgeo/report/11 Just those concerning the upcoming release]
* [https://trac.osgeo.org/osgeo/query?status=closed&group=type&order=priority&component=LiveDVD List of tickets already fixed]

== OSGeo User Id ==
* Create an OSGeo id: http://www.osgeo.org/osgeo_userid , which is required to edit the wiki, commit to svn and create an issue in the issue tracker.

== Subversion ==

; Repository: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk and [http://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk web view]
* On Linux systems: access Subversion using:
svn checkout https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk

* On MS Windows systems, install [http://tortoisesvn.tigris.org/ Tortoise Subversion], which extends Windows Explorer to include subversion commands.

; Commit access
:To get commit access, you need to create yourself an [http://www.osgeo.org/osgeo_userid osgeo user id], then join our [http://lists.osgeo.org/mailman/listinfo/live-demo email list] and ask to be given access to subversion. In this email, you will also need to confirm that you will comply with our license guidelines. Write something like:

:''"Hi all, I'd like to contribute XXX to OSGeo-Live. Could I please get access to subversion. My osgeo-user id is: YYYY.''

: ''I confirm that my contributions to OSGeo-Live will be compatible with the OSGeo-Live license guidelines at the time of contribution."''

: The licenses used for the OSGeo-Live build scripts and documentation are:
:* ''Creative Commons Attribution-ShareAlike 3.0 Unported License for Quickstarts''
:* ''Creative Commons Attribution 3.0 Unported License for Project Overviews''
:* ''LGPL version >=2.1 for the install scripts''
:* ''One of the OSI approved Open Source licenses for installed applications''
:* ''Public domain, CC-By-SA, and Open Data Commons Open Database License (ODbL) for data''

:A project admin will then add you to the [https://www.osgeo.org/cgi-bin/auth/ldap_group.py?group=osgeo osgeo] user group.

;Add your name to contributors list
:The first thing you should do to test your svn install is to add your name the [http://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/doc/contributors.csv code contributors] or [http://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/doc/translators.csv translators] list(s):

cd trunk/doc

# to edit a file
svn update contributors.csv translators.csv

# Coders and creators of new content: edit contributors.csv
# please add your Name, Email, Country and Osgeo_id to the list, separated by comma
# - Order alphabetical by first name,
# - remove punctuation from email addresses to stop harvesting for junk mail

# optionally check to see what has changed.
svn diff contributors.csv

# check the file back into subversion
svn commit contributors.csv

# Translators: edit translators.csv
# same as above, but the order of columns is:
# Language, i18n code, Name, Country, Email, Osgeo_id
# - Order alphabetically by language, then by first name
# - remove punctuation from email addresses to stop harvesting for junk mail

Working with files:

# to add a file
cd <dir>

# create a file
svn add <file>
svn propset svn:mime-type <mime.type> <file>
svn commit <file>

# to move or rename a file
# *** please use instead of 'svn add' + 'svn rm', otherwise the
# development history gets lost and database space is wasted ***
svn move <old filename> <new filename>
svn commit <file>

* A script to automatically set the svn props can be found [https://svn.osgeo.org/grass/grass-addons/tools/module_svn_propset.sh here]. More SVN hints [https://trac.osgeo.org/grass/wiki/HowToSVN here].
* On MS Windows this can be made easy using [http://tortoisesvn.tigris.org/ Tortoise SVN] which plugs directly into Windows Explorer.

== FAQ ==
* [[Live GIS Disc FAQ]]

== Press Releases ==
* [[FOSS4G 2009 Press Releases]]
** 27 August 2009, [[FOSS4G 2009 Press Release 28]] - Simple steps to get your project on the FOSS4G Live DVD
** 6 September 2009, [[FOSS4G 2009 Press Release 29]] - What Windows installers should be on the FOSS4G Live DVD + Live DVD Status.
** 3 October 2009, [http://cameronshorter.blogspot.com/2009/10/arramgong-gis-live-dvd-off-to-printers.html] '''Arramagong GIS Live DVD - off to printers'''
** 16 October 2009, [[FOSS4G 2009 Press Release 35]] - LiveDVD/VM on click2try [[FOSS4G 2009 Press Release 35 Cover|Cover Email]]
* 16 December 2009, [[Live GIS Disc Press Release 1]] - Defining the next LiveDVD/VM
* 14 January 2009, [[Live GIS Disc Press Release 2]] - 3 weeks to Live DVD 3.0 feature freeze
* 24 March 2010, [[Live GIS Disc Press Release 4]] - LiveDVD project joins Google Summer of Code
* 31 March 2010, [[Live GIS Disc Press Release 3]] - '''Arramagong Live DVD 3.0 released'''
* 10 June 2010, [[Live GIS Disc Press Release 5]] - Building OSGeo Live DVD for FOSS4G 2010
* 27 June 2010, [[Live GIS Disc Press Release 6]] - 1 week till OSGeoLive Feature Freeze
* 21 July 2010, [[Live GIS Disc Press Release 7]] - OGC and OSGeo collaborate on documentation
* 3 August 2010, [[Live GIS Disc Press Release 8]] - 1 week to test the OSGeo-Live DVD
* 13 August 2010, [[Live GIS Disc Press Release 9]] - Testing OSGeo-Live on the USB
* 3 September 2010, [[Live GIS Disc Press Release 10]] - '''Video & DVD for OSGeoLive 4.0, the best GeoSpatial''' OpenSource
* 23 November 2010, [[Live GIS Disc Press Release 11]] - Goals and schedule for OSGeo-Live 4.5
* 11 December 2010, [[Live GIS Disc Press Release 12]] - Contact application contacts
* 14 January 2011, [[Live GIS Disc Press Release 13]] - Last call for projects to be included on OSGeo-Live 4.5
* 13 February 2011, [[Live GIS Disc Press Release 14]] - Two weeks to translate Project Overviews
* 13 February 2011, [[Live GIS Disc Press Release 15]] - Two weeks to write Quick Starts
* 25 February 2011, [[Live GIS Disc Press Release 16]] - OSGeo-Live 4.5 ready for testing
* 28 March 2011, [[Live GIS Disc Press Release 17]] - '''OSGeo-Live 4.5 released'''
* 8 May 2011, [[Live GIS Disc Press Release 18]] - Call for interest in OSGeo-Live 5.0
* 4 June 2011, [[Live GIS Disc Press Release 19]] - Last call for new projects wishing to be included on OSGeo-Live
* 17 June 2011, [http://cameronshorter.blogspot.com/2011/06/memoirs-of-cat-herder-coordinating.html Memoirs of a Cat Herder - Coordinating OSGeo-Live volunteers]
* 9 July 2011, [[Live GIS Disc Press Release 20]] - One week to update of OSGeo-Live English Overviews and Quickstarts
* 18 July 2011, [http://cameronshorter.blogspot.com/2011/07/project-overviews-quickstarts-for-new.html Project Overviews & Quickstarts for New Zealand's SDI Cookbook]
* 2 August 2011, [[Live GIS Disc Press Release 21]] - Calling for OSGeo-Live Testers
* 30 August 2011, [[Live GIS Disc Press Release 22]] - '''OSGeo-Live 5.0 released'''
* 1 November 2011, [[Live GIS Disc Press Release 23]] - Call for interest in OSGeo-Live 5.5
* 17 December 2011, [[Live GIS Disc Press Release 24]] - What version of applications should we be installing on OSGeo-Live 5.5?
* 16 January 2012, [[Live GIS Disc Press Release 25]] - Update OSGeo-Live 5.5 docs & installer
* 1 March 2012, [[Live GIS Disc Press Release 26]] - '''OSGeo-Live 5.5 released'''
* 30 April 2012, [[Live GIS Disc Press Release 27]] - Starting build cycle for OSGeo-Live 6.0
* 2 August 2012, [[Live GIS Disc Press Release 28]] - All OSGeo-Live java applications now working with OpenJDK 7
* 20 August 2012, [[Live GIS Disc Press Release 29]] - '''OSGeo-Live 6.0 released'''
* 31 October 2012, [[Live GIS Disc Press Release 30]] - Starting build cycle for OSGeo-Live 6.5
* 9 November 2012, [[Live GIS Disc Press Release 31]] - What version of applications should we be installing on OSGeo-Live 6.5?
* 3 December 2012, [[Live GIS Disc Press Release 33]] - One week to tell us to include your app on OSGeo-Live 6.5
* 18 December 2012, [[Live GIS Disc Press Release 34]] - Update OSGeo-Live Project Overviews and Quickstarts
* 18 January 2013, [[Live GIS Disc Press Release 32]] - Targeting OSGeo-Live Quickstarts for OSGeo-Live 6.5
* 20 January 2013, [[Live GIS Disc Press Release 35]] - OSGeo-Live Project Overview deadline in 3 days
* 24 January 2013, [[Live GIS Disc Press Release 36]] - Two weeks to translate OSGeo-Live Documentation
* 26 January 2013, [[Live GIS Disc Press Release 37]] - OSGeolive Quickstart Hackaton Weekend
* 18 February 2013, [[Live GIS Disc Press Release 39]] - OSGeolive Quickstart Hackaton - Results
* 20 February 2013, [[Live GIS Disc Press Release 38]] - '''OSGeo-Live 6.5 released'''
* 16 May 2013, [[Live GIS Disc Press Release 40]] - Starting build cycle for OSGeo-Live 7.0
* 19 July 2013, [[Live GIS Disc Press Release 41]] - Update OSGeo-Live Project Overviews and Quickstarts
* 23 August 2013, [[Live GIS Disc Press Release 42]] - Final OSGeo-Live testing sprint this weekend
* 30 August 2013, [[Live GIS Disc Press Release 43]] - '''OSGeo-Live 7.0 released'''
* 20 December 2014, [[Live GIS Disc Press Release 44]] - Starting build cycle for OSGeo-Live 7.9
* 27 January 2014, [[Live GIS Disc Press Release 45]] - Update OSGeo-Live Project Overviews and Quickstarts
* 14 February 2014, [[Live GIS Disc Press Release 46]] - Final OSGeo-Live 7.9 testing sprint - call to action
* 19 February 2014, [[Live GIS Disc Press Release 47]] - Two weeks to translate OSGeo-Live Documentation
* 12 March 2014, [[Live GIS Disc Press Release 48]] - '''OSGeo-Live 7.9 released'''
* 14 April 2014, [[Live GIS Disc Press Release 49]] - OSGeo-Live and Heartbleed vulnerability
* 4 May 2014, [[Live GIS Disc Press Release 50]] - Starting build cycle for OSGeo-Live 8.0
* 11 August 2014, [[Live GIS Disc Press Release 51]] - OSGeo-Live at FOSS4G-Europe Code Sprint
* 28 July 2014, [[Live GIS Disc Press Release 52]] - OSGeo-Live Testing and updating Project Overviews and Quickstarts

== History ==
[[Live GIS History]]

== Project Metrics ==
* Metrics from Ohloh: https://www.ohloh.net/p/OSGeo-Live
* OSGeo Live Translation Stats: http://adhoc.osgeo.osuosl.org/livedvd/lang_stats.html

== Google Summer of Code ==
* [[Live GIS GSoC 2014]]

= Use Cases =

There are multiple use cases for this product:

* '''Demo DVD''' that can be handed out at conferences. This will contain a wide variety of applications, preconfigured with some sample data and containing introductory tutorials. It should be able to function completely offline, at least within the scope of the tutorials, and should provide an introduction to many products. This is very much a Live DVD, and as such should be conservative with regards to size (it will be run from RAM).
* '''Education DVD''' This seems to be a more involved version than the Demo DVD, including more involved material, including train-the-trainer style material. This is targeted at those who will be teaching others, be it in workshops or university classes/labs. My expectation (mleslie: feel free to correct me) is that this is more likely to be installed on machines and used as a teaching resource, as opposed to a toy to play with, as with the Demo DVD. This will require material developed through the [[Category:Education|Education initiative]].
* '''Workstation Install DVD''' This need was seen in Cape Town, where the bandwidth seems to be a very limiting factor. Using the DVD to install either a complete OS, a set of packages to an existing Linux, or Windows installers completely offline is of great value in the developing world. Would it be of greater value to lose the Edu or demo material and put in complete application documentation?

= Links to related projects =
* [http://wiki.debian.org/DebianGis DebianGIS]. We encourage projects to package applications into Debian, which in turn is incorporated into Ubuntu.
* [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS]
* [http://wiki.osgeo.org/wiki/Enterprise_Linux_GIS Enterprise Linux GIS] packages as RPMs for redhat based systems.
* [http://www.gisvm.com/ GISVM home page] (GIS Virtual Machine by [[Ricardo Pinho]])
* [http://wiki.debian.org/DebianGis/LiveImages DebianGIS Live Image]
: [http://svn.debian.org/viewsvn/pkg-grass/packages/debian-gis/ Build scripts in DebianGIS's SVN]
* [http://livecd.ominiverdi.org/index.php?page=LiveCD&toc=livecd Omniverdi LiveCD project]
* [http://grass.osgeo.org/download/cdrom.php List of live CDs from the GRASS download site]
* [http://wiki.gfoss.it/index.php/LiveDVD-GFOSS.it Gfoss.it live DVD ]
* [http://www.archaeogeek.com/portable-gis.html Portable GIS] - Zero-install GIS for MS Windows on a USB stick
* [http://www.poseidonlinux.org/ Poseidon Linux]
* [http://www.fossgis.de/projekte_gislive.html GISLive] - LiveDVD project from [http://www.fossgis.de FOSSGIS e.V.] (German language)

= Links to Build tool options =
* The [http://packages.debian.org/sid/live-helper live-helper] package - [http://wiki.debian.org/DebianLive DebianLive home page]
* [http://www.debuntu.org/how-to-customize-your-ubuntu-live-cd Debian\Ubuntu Tricks]
* [https://help.ubuntu.com/community/LiveCDCustomization Ubuntu Help Way]

[[Category: Software Stack]]
[[Category: Live-demo]]

Live GIS Disc Press Release 45

2014-07-27T03:54:26Z

Wiki-HamishBowman: revert to correct content

=Update OSGeo-Live Project Overviews and Quickstarts=

26 January 2014

Now that we have a feature freeze for OSGeo-Live 7.9, could all OSGeo-Live projects please ensure their Project Overviews and Quickstarts [0] are up to date. This should be quite painless for most.

# Update the version number in your Project Overview (if changed).
# Possibly mention a new feature or two.
# Re-run the Quickstart and ensure each step is still valid, and screenshots match the implementation.
# Update status of the Project Overview and Quickstart to "7.9draft" in our status sheet. [1]

== Schedule ==

* 14 February 2014 English docs complete
* 28 February 2014 Translations complete
* 7 March 2014 OSGeo-Live sent to the printers

[0] https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/

[1] https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13

Live GIS Disc Press Release 52

2014-07-27T03:52:27Z

Wiki-HamishBowman: I will do the desktop screenshots once menu is done

= OSGeo-Live UAT in one week: Application testing and documentation update is needed =

28 July 2014

In this OSGeo-Live 8.0 development cycle we have seen major upgrades: moving to the light weight Lubuntu distribution, moving to a new Long Time Support release (LTS), and moving even more applications to make use of Debian packaging. It should be our best distribution yet. But this has impacted our schedule, as the Ubuntu LTS has only become stable within the last week, and we need help in order to deliver OSGeo-Live to [http://2014.foss4g.org FOSS4G-PDX] with our usual high level of quality and reliability.

In particular, we need help:
# Testing to verify everything works in this new system and fixing bugs
# Updating version number in your Project Overview (if changed), and possibly mention a new feature or two.
# Re-running the Quickstart and ensure each step is still valid, and screenshots match the implementation.
# Updating status of the Project Overview and Quickstart to "8.0draft" in our status sheet. [1]

Due to our tight timelines, we might need to hide applications which we can't get stablised, tested, or docs updated in time. Please check our current list of open issues [2][3] to verify that your project is working as expected.

== Schedule ==

* 27 July 2014 Alpha4 released [3]. Please verify all applications work and fix bugs
* 03 August 2014 Beta1 released - start taking screen shots with new background
* 07 August 2014 Community Testing Sprint (UAT)
* 07 August 2014 English docs complete
* 14 August 2014 Translations complete
* 17 August 2014 OSGeo-Live sent to the printers

[1] https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13

[2] http://trac.osgeo.org/osgeo/report/10

[3] http://lists.osgeo.org/pipermail/live-demo/2014-July/009274.html

[[Category: Live-demo]]

Live GIS Disc Press Release 52

2014-07-27T03:51:45Z

Wiki-HamishBowman: fix press release page

= OSGeo-Live UAT in one week: Application testing and documentation update is needed =

28 July 2014

In this OSGeo-Live 8.0 development cycle we have seen major upgrades: moving to the light weight Lubuntu distribution, moving to a new Long Time Support release (LTS), and moving even more applications to make use of Debian packaging. It should be our best distribution yet. But this has impacted our schedule, as the Ubuntu LTS has only become stable within the last week, and we need help in order to deliver OSGeo-Live to [http://2014.foss4g.org FOSS4G-PDX] with our usual high level of quality and reliability.

In particular, we need help:
# Getting screen shots with the new Lubuntu desktop (after beta1 release)
# Testing to verify everything works in this new system and fixing bugs
# Updating version number in your Project Overview (if changed), and possibly mention a new feature or two.
# Re-running the Quickstart and ensure each step is still valid, and screenshots match the implementation.
# Updating status of the Project Overview and Quickstart to "8.0draft" in our status sheet. [1]

Due to our tight timelines, we might need to hide applications which we can't get stablised, tested, or docs updated in time. Please check our current list of open issues [2][3] to verify that your project is working as expected.

== Schedule ==

* 27 July 2014 Alpha4 released [3]. Please verify all applications work and fix bugs
* 03 August 2014 Beta1 released - start taking screen shots with new background
* 07 August 2014 Community Testing Sprint (UAT)
* 07 August 2014 English docs complete
* 14 August 2014 Translations complete
* 17 August 2014 OSGeo-Live sent to the printers

[1] https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13

[2] http://trac.osgeo.org/osgeo/report/10

[3] http://lists.osgeo.org/pipermail/live-demo/2014-July/009274.html

[[Category: Live-demo]]

Live GIS Add Project

2014-05-10T08:38:07Z

Wiki-HamishBowman: /* Packaging Python */

== What gets into OSGeoLive? ==

We have an emphasis of quality, and we are space constrained on OSGeoLive and so are selective about what is included.

Priority for selecting OSGeoLive projects to package is:
# OSGeo Projects
# OSGeo Projects in incubation
# Stable GeoSpatial Open Source Software being presented in workshops, tutorials, or presentations at FOSS4G
# Other Stable GeoSpatial Open Source Software with established project communities and a wide user base
# It will be ready for the next release in accordance with our [https://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdE1SYUN3YWJ2N1NpSUczbW9IRWZNclE&hl=en_GB schedule]

== Application Questions ==

Projects need to provide:
* Project Champion
: Someone who will liaise between the OSGeoLive team and the project and ensures the application remains up to date on OSGeoLive.
* A base [[#Install_Script]] for installing onto an Ubuntu Linux based system.
* [[#Documentation]] in line with OSGeoLive templates
* Someone who will run and verify the applications works in development releases
* [http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB Project Status] to be maintained.

If you think you can cover all these criteria for your project, then send an email to the [http://lists.osgeo.org/mailman/listinfo/live-demo OSGeoLive email list] asking if your project is appropriate. When emailing the list, please address the questions in the [[Live_GIS_Disc_Apply]] form.

== Which version to use? ==

* Stable, always! LiveGIS users are usually seeing OSGeo newbies and will be turned off by any software bugs.

== Install Script ==
Each project is to write a shell script which installs and configures your stable application into the OSGeoLive Xubuntu.

All install scripts for building the LiveGIS disc shall be licensed as LGPL.

When finished, ask the OSGeoLive team to reference your script from ''main.sh''.

Scripts are stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/

The script may be as simple as:
[https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_mapserver.sh install_mapserver.sh], which just
apt-get install mapserver

Projects that haven't been packaged for Ubuntu yet are slightly more complicated:

The uDig package is a good example: [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_udig.sh install_udig.sh]

* 3rd Party Repositories: Create an <app>.list file with your repository in sources.list.d/ in the svn, in your script copy the file to the local machine like
cp -f ../sources.list/ubuntugis.list /etc/apt/sources.list.d/

don't forget to add the repository key like so
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 68436DDF

== Packaging conventions ==

* '''sudo''': Assume the script is to be executed as root. This means that sudo is only needed if you need to execute a command as e.g. the database user.
: This means that ~/ refers to the directory /home/root/, so you should use ~user/ to reference /home/user/.
: Preferred method is to put the <tt>USER_NAME</tt> and <tt>USER_HOME</tt> variables at the top, so these can be easily changed in all scripts if needed.
USER_NAME="user"
USER_HOME="/home/$USER_NAME"
cp package_readme.txt "$USER_HOME"

* '''Called twice''': Assume that the script will be executed multiple times, (as people may re-run the install process to get it right).
: Make sure that nothing is corrupted if the script runs a second time.

* '''No Prompts''': Try not to have any interactive steps which prompt the user for an answer, as we want the scripts to be run automatically. In particular, try running the script a second time, and see if you get prompted to overwrite files.

* '''/tmp''': Copy all downloads into /tmp/build_<package>/
: Don't delete the /tmp/build_<package> directory afterwards. If the script is re-run, then time and bandwidth is saved by not having to download large files again. Do not do code checkouts or place temporary files in the starting build directory, which is ./bin/ in the live disc's SVN tree. See the "BUILD_DIR" environment variable used in a number of scripts if you later have to refer back to the ../app-conf/ or ../app-data/ relative paths in the live disc's SVN tree.

* '''Icons''': Where appropriate, create an icon on the desktop which loads the application. The file should be called <packagename>.desktop and placed in /home/user/Desktop/ for further processing. The icons will be sorted and the Geospatial menu will be auto-generated from here.
: Install <packagename>.png icon files to the /usr/share/icons/ directory.
: see <tt>install_qgis.sh</tt> for an example

* '''Browser bookmarks:''' If the application is launched from the browser, then include the application in Firefox bookmarks.
: (Todo: How do we do this?)

* '''wget''': When downloading large files using wget, use the "-c" continue command, as it will not re-download files if they already exist, and will continue if one is partially downloaded:
wget -c package.tar.gz
: Do not use -c if there is a chance the file of that name will change on the server. Add "<tt>--progress=dot:mega</tt>" to the wget command line if the file is at all large.
: Tiny files should use wget's -nv (non-verbose) flag.
: In a similar manner, use "<tt>--quiet</tt>" when calling '''qsql'''.

* '''mkdir''': Use -p (create parents too) option when creating a directory, as it doesn't complain about creating the directory a second time.
mkdir -p <dir>

* '''Binary files''': Do not put large (>5mb) binary files into the SVN repository without asking first. Due to SVN's preservation of history, once they are added they can never be removed, and forever-more clog up the backend database. Subversion is designed to be a ''source code management'' tool, not a data warehouse. There is space for large static data files (e.g. sample data) at http://download.osgeo.org/livedvd/data/. Just ask on the mailing list if you'd like to house something there.

= Packaging considerations =

The criteria used to select applications for the LiveGIS follow.

== Technical limitations ==
=== Space considerations ===
* DVD: approx 4.2gb compressed
* USB stick: For a 4gb persistent USB stick with some room left over for user-workspace, 3.2-3.5gb compressed. (This pretty much works out to the DVD version minus the preloaded Mac and Windows installers)
* Virtual Machines: theoretically unlimited, but in practice 20gb uncompressed

So smaller apps (<30mb) of lesser priority may easily slip in under the ire radar, but an external project that wants to use a 25% of the available disc space would be the first to be compromised away.

=== Memory considerations ===
Both Virtual Machines, and a LiveDVD images are likely to be constrained by limited memory. So to reduce memory usage. Disk image size is not of major concern, as we can just distribute less data.

The following principles should be followed.
* Do not start applications upon power up. (Ie, don't start deamons, allow users to start them instead).
* Set up examples which, by default, don't depend on other applications. Less applications open, means less memory. Ie, Have GeoServer access a shapefile instead of PostGIS.
* Try to avoid scenarios which write data to disk, as disk space in the Live DVD is stored in RAM, and is not cleared afterward.

File permissions and filesystem user IDs can get garbled during the ISO build process. Therefore a special method is used to ensure that data files which must be read-write can be accessed.

To install a writable data directory or files, change its group to "users" and set the file(s) as group-writable:

adduser $USER_NAME users
chmod -R g+w /usr/local/share/<packagename>/data/
chown -R root.users /usr/local/share/<packagename>/data/

and symlink into the user's home directory if necessary.

Setting files to have universal write permission is strongly discouraged. '''Do not use "''chmod 777 -R''".'''

=== Shared resources ===

The disc is a busy place, so we must all play nice and take care not step on each others toes.

==== Changes to the base system ====

Please don't customize any system level infrastructure which other projects may be relying on.
Often there is an /etc/$foo.d/ directory for you to put config additions into. Always put non-.deb packaged custom things in /usr/local not /usr!

==== Port numbers ====

To avoid overlaps and conflicts with other packages, please avoid putting web services on common port numbers like 8000 or 8080. Choose a random port between 8000 and 8080, search through the whole documentation for this port number (e.g. "grep -R 8042 doc bin") and only use this number if it isn't mentioned anywhere else. Then add your new port number to your quick guide so that others will find it.

Rasdaman is using ports 7001 (dispatcher), 7002, 7003, etc. (worker processes). The number of workers is fixed in the etc/rasmgr.conf file, at least one is required.

= Directory Structure =

# '''/tmp''' Temporary files (e.g., downloaded archives) go into /tmp. Please create a separate folder for your project.
# '''/usr/lib''' application are usually installed into /usr/lib
# '''/usr/bin''' things that get executed by the user such as startup scripts or links to them should go into /usr/bin
# '''/etc/init.d''' startup/shutdown scripts for services (e.g., postgres, apache, tomcat) are stored in /etc/init.d
# '''/usr/local/share''' sample data and documentation goes into /usr/local/share
# '''/etc''' config files are stored in /etc
# '''/home/user''' user specific config files or working directories can go into <tt>/home/user/</tt>. However, keep files in /home/user as small as possible as this folder is loaded into memory in the Live DVD. Symlinks into /usr/local can be useful here.

* ''You are strongly encouraged to use '''/usr/local/''' and '''/var/local/''' for storing non-packaged content.''

== .deb Packaging ==
Currently many packages are installed from bash scripts. The major release goal for the next versions of the Osgeo live DVD is to make sure that all programs can be installed from debian packages.

This offers many advantages: packages can be uninstalled and updated to newer versions without having to build the complete live dvd. This also makes testing more easy: one can just update to the last live dvd rather than having to install all software.
Ideally, applications should be packaged in [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] or [http://wiki.debian.org/DebianGis DebianGIS] repositories, or in a Launchpad PPA (e.g. available from the UbuntuGIS repository). This would mean that any ubuntu or debian user can profit from the packaging works for the osgeo live dvd.

Even though packaging can be overwhelming at first, it eventually boils down to creating a few files in a debian subdirectory from a place where the sources of your application are. A quick and easy way to generate a template is by running dh_make (from the dh-make package) in the directory where your sources are.
This will create the necessary files to build a package which you will have to edit before packaging for real.

Many tutorials exist on the web that can assist building debian packages, so I will not repeat all of them here.
https://wiki.debian.org/IntroDebianPackaging provides a good start.

If you are new to debian packaging probably the best you can do is ask on the mailing lists of [http://lists.osgeo.org/mailman/listinfo/ubuntu UbuntuGIS] or [https://lists.debian.org/debian-gis/ DebianGIS] whether someone can provide a template to start your own package.

=== Packaging Python ===

Instead of using "<tt>pip</tt>", "<tt>easy_install</tt>" or other Python installation methods it is preferred to install the <tt>''python-pkgname''</tt> package if it exists. By integrating the python libraries into the dpkg system-files database we can quickly find files and make sure that there are not two different versions from two different sources competing and conflicting. Fortunately it is very easy to create a .deb from projects on Pypi.

* First check that the software is not already on the disc with "dpkg -S ''name''" and "locate ''name''".

* Next check if it exists as a package, just not currently installed. For example:
apt-cache search fiona

* If needed, install the packaging tools:
sudo apt-get install python-stdeb build-essential python-all-dev

* Run ''<tt>pypi-install</tt>'' to download, build, and install the .deb. For example:
sudo pypi-install Fiona

Add the "--keep" command line option to retain a copy of the .deb and .changes file in a subdirectory of /tmp, e.g. for upload to UbuntuGIS's repository.

See also [http://article.gmane.org/gmane.comp.gis.osgeo.livedemo/7466/ this mailing list thread] with further details on manually packaging using the same tools.

== Example Datasets ==
In order to reduce disk space, and to provide consistency between projects, we strongly encourage all projects to make use of the common datasets packaged on OSGeo-Live by the [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_gisdata.sh install_gisdata.sh] script.

All datasets should be installed into /usr/local/share/data, or if installed elsewhere, there should be a symbolic link into /usr/local/share/data. Data should not be installed in the /home/user directory, as I understand that data in the HOME directory is copied into RAM. (TBD find confirmation of this).

There is a symbolic link from /home/user/data to /usr/local/share/data to make it easy to find from a user's home directory. (Documentation should reference /home/user/data/... ).

Datasets are also available via http://localhost/data/ and http://live.osgeo.org/data/ (which is a symbolic link from /var/www/data to /usr/local/share/data).

=== Natural Earth ===
The [http://www.naturalearthdata.com/ Natural Earth] dataset is the preferred dataset for all examples.

* [http://www.naturalearthdata.com/downloads/10m-cultural-vectors/ 1:10m Simple Populated Places]. Shapefiles are in /user/data/natural_earth/* and have also been loaded into PostGIS.
** admin_0_countries
** admin_1_states_provinces
** geography_marine_polys
** geography_regions_elevated_points
** geography_regions_polys
** lakes
** land
** ocean
** populated_places_simple
** rivers_lake_centerlines
** urban_areas

* Raster basemap -- Cross Blended Hypso with Shaded Relief and Water 1:50 million, stored in /user/data/natural_earth/HYP_50M_SR_W/*

=== OpenStreetMap ===
OpenStreetMap data is loaded into /usr/local/share/data/osm/feature_city.osm

=== North Carolina ===
The [http://www.grassbook.org/data_menu3rd.php OSGeo-Geodata collection of geotiffs and shapefiles for Wake County] (North Carolina) has been tentatively added for the 5.0 release.

The [http://www.grassbook.org/ncexternal/nc_datalist.html North Carolina layers] can be found in /usr/local/share/data/north_carolina/ (symlinked to ~/data/north_carolina)

=== Others ===
If you need another type of data for your examples, please discuss this with us.

== Documentation ==
OSGeo-Live documentation is published at:
;On OSGeo-Live: http://localhost/ which is stored in /var/www/
;Stable release: http://live.osgeo.org
;Nightly build: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/index.html

=== Application Overview ===

The [[Marketing_Artefacts#Application_Overview|Application Overview]] is a one page marketing page targeted at a someone considering using GeoSpatial Open Source, who may be a GeoSpatial User, a Technical person without much geospatial expertise, or manager with limited GeoSpatial or technical experience. Published Overviews are linked from here: http://live.osgeo.org/en/overview/overview.html

The source Overviews are written in [http://sphinx.pocoo.org/rest.html RST wiki format] and built using sphinx. Source documents are to be stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/overview/en/<application>_overview.rst . They should follow the structure and style of the reference Overview, which has lots of helpful comments, at https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/overview/postgis_overview.rst

The Overviews are currently published as [http://live.osgeo.org/overview/overview.html HTML pages]. In future we intend to also create 1 page PDFs, (to hand out as a flier at conferences, and as a page in the OSGeo Book of projects), and as Word/OpenOffice (to be cut and pasted into project proposals and articles which usually use these formats).

Overviews also require:
* an image for the application, usually a screen shot or collage of screen shots, as per [[#Screen_Shot|Screen Shot]] ('''don't use GIF format, please use PNG instead''').
* A project logo as per [[#Logo]] ('''don't use GIF format, please use PNG instead''').

Try printing the html page from the browser, and ensure that the page is less than one page long. (The less words you write, the more people will read your documentation.)

Once finished, note your project's overview status="draft" in the OSGeo-Live project status at: http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB#gid=5 and email live-demo@lists.osgeo.org noting your documentation is ready for review. Once reviewed, the status is moved to "complete" and is ready for translation.

=== Application Quick Start ===
The [[Marketing_Artefacts#Application_Quick_Start|Application Quick Start]] defines detailed steps, with screen shots, for a new user to run one of the application's core functions. It should be able to be run in 5 to 10 minutes.

Try to make use of a friendly, conversational writing style, similar to the way a tutor would talk a class through an example. The quickstarts for [http://live.osgeo.org/en/quickstart/R_quickstart.html R] and [http://live.osgeo.org/en/quickstart/geoserver_quickstart.html GeoServer] do this very well.

Source documentation is written in [http://sphinx.pocoo.org/rest.html RST wiki format], is built using sphinx, and is stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/quickstart/<application>_quickstart.rst

The reference quickstart, which includes structure guidelines and with tips on how to fill in the quickstart is here:
https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/quickstart/udig_quickstart.rst
and is published here: http://live.osgeo.org/en/quickstart/udig_quickstart.html

In order to reduce disk space, and maintain consistency between applications, we request that all examples make use of the common [[#Example_Datasets]]. If the datasets don't cover your requirements, discuss this with us and we may add another suitable common dataset.

Applications are expected to include screen shots for each major step in the quickstart, as per [[#Screen_Shot|Screen Shot]].

Once finished, note your project's quickstart status="draft" in the OSGeo-Live project status at: http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB#gid=5 and email live-demo@lists.osgeo.org noting your documentation is ready for review. Once reviewed, the status is moved to "complete" and is ready for translation.

==== Quickstart Review Checklist ====

* Review latest Quickstart docs at: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/overview/overview.html
* Run with latest OSGeo-Live Development Release. Download from: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Downloads
* ''Before starting, notify others that you have started reviewing by setting "Quickstart reviewed by:" to "Started:<your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If you feel confident [http://wiki.osgeo.org/wiki/Live_GIS_Add_Project#Documentation updating the .rst documentation], then feel free to correct simple errors that you find, and commit back to subversion. (you will need [http://wiki.osgeo.org/wiki/Live_GIS_Disc#Subversion subversion access]).
* Otherwise, report problems in our [http://wiki.osgeo.org/wiki/Live_GIS_Disc#Issue_Tracker Issue Tracker] with keywords: ''docs 6.5 <application>'', component: ''LiveDVD'', milestone:

;Someone experienced with the project:
* Is the quickstart applicable for the version of the application installed on OSGeo-Live?
* If sample data is used, is it one of the OSGeo-Live datasets?
* Is there a screenshot for each step?
* Where appropriate, have screenshots been labeled (usually with numbers) to link them back to the documentation?
* ''Once finished, update Quickstart status to "6.5 Draft" and "Quickstart reviewed by:" to "osgeolive-version <your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If not already included, add the editor's name to the top of the .rst file:
:Author: Your Name
;QA Tester:
* Has the quickstart been run from start to finish?
* How long did the quickstart take to run? (Should be between 5 and 15 minutes)
* Has every step been explained in the quickstart?
* ''Once finished, update Quickstart status to "6.5 Reviewed" and "Quickstart reviewed by:" to "osgeolive-version <your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If not already included, add the testers name to the top of the .rst file:
:Reviewer: Your Name

;Reviewer for readability and consistency:
* Would the quickstart be understandable for a novice? Are all technical terms and acronyms explained?
* Is the language clear, and concise?
* Does the first paragraph explain what this Quickstart is going to cover?
* Are there steps for one scenario?
* Does the quickstart include "Things to try" and/or "What next" sections?
* ''Once finished, update Quickstart status to "6.5 Final" and "Quickstart reviewed by:" to "osgeolive-version <your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If not already included, add the reviewer's name to the top of the .rst file:
:Reviewer: Your Name

=== Logo ===
The Project's logo is used in the headers of documentation (like Project Overviews, QuickStarts, Powerpoint presentations etc, and as icons on the OSGeo-Live Desktop. Hence there are a few different requirements for the logo.

;Header logo:
:* Stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/images/project_logos
:* Filename should be "logo-<projectname>.png" (apparently PNG is required for PDF docs)
:* Should have a transparent background (not white)
:* Preferably stored in size 125x125 pixels (for use in Project Overview and QuickStarts)
:* For PNGs ''please'' run a program like [http://packages.ubuntu.com/pngcrush pngcrush] or [http://packages.ubuntu.com/optipng optipng] to reduce the size of the image without degrading quality. Here's an example using <tt>optipng</tt>:
optipng -o5 image.png
:* Preferably also available as SVG, stored as "logo-<projectname>.svg"

;Desktop logo:
:We are still to define the requirements for creating a desktop logo. They will likely include:
:* A 32x32-pixel XPM icon for use by the Debian menus
:* A 48x48-pixel PNG icon for use by freedesktop.org menus

=== Screen Shot ===
Project overviews include an image, which is usually a screen shot, or collage of screen shorts. Quickstarts include screen shots for each significant step.
* Screen shots can be taken using [http://shutter-project.org/ Shutter] (on linux) or [http://getgreenshot.org/ Greenshot] (on windows).
* Screen shots should be taken from a 1024x768 display, and should be created in PNG format. (Apparently PNG is required for PDF documentation.)
* Images are to be stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/images/screenshots/1024x768
* For Quickstarts, consider marking up the image to explain the current steps. Eg: Add circled numbers: 1, 2, 3 or draw an oval around buttons being described. This is very easy to do using the "Edit" tab in the Shutter program, which provides these drawing icons to add. Tutorials augmented with detailed and pertinent images make it easy for the reader to follow what is going on. Extra time spent on an image pays off big in comprehension (you need more than just a course screen dump). Lines, numbering, highlights, boxes and annotations all help direct a user's focus to those areas which are important.
* Screenshots with large areas of constant color (menus, etc.) should be in PNG format, screenshots containing large areas of imagery (satellite images, shaded relief DEMs, etc.) should be in JPEG format.
* For PNGs ''please'' run a program like [http://packages.ubuntu.com/pngcrush pngcrush] to reduce the size of the image without degrading quality.

=== Extra Documentation ===
Some projects link to extra documentation, stored as PDFs or similar, or alternatively provide example applications. These should be referenced in documentation via a relative link such than it can viewed from:
http://localhost/<application>/... or http://live.osgeo.org/<application>/...

This should typically be achieved by creating a symbolic link from /var/www/<application> to /usr/local/share/doc/<application>

== Publishing Documentation ==

The following web service is useful for checking [http://docutils.sourceforge.net/rst.html reST] formatting: http://rst.ninjs.org/

For a more comprehensive test, set up the reST processor, sphinx:
: (''you will have to have [http://sphinx.pocoo.org/ Sphinx 0.6.4 or greater] installed, it's in the'' <tt>python-sphinx</tt> ''Debian package'')

sudo apt-get install python-sphinx

cd osgeo/livedvd/gisvm/trunk/doc/
make html

You can then view the results in:
osgeo/livedvd/gisvm/trunk/doc/_build/*.html

= Translations =
For details on how to translate, refer to [[Live GIS Translate]]

[[Category: Live-demo]]

Live GIS Add Project

2014-05-10T08:37:28Z

Wiki-HamishBowman: /* Packaging Python */

== What gets into OSGeoLive? ==

We have an emphasis of quality, and we are space constrained on OSGeoLive and so are selective about what is included.

Priority for selecting OSGeoLive projects to package is:
# OSGeo Projects
# OSGeo Projects in incubation
# Stable GeoSpatial Open Source Software being presented in workshops, tutorials, or presentations at FOSS4G
# Other Stable GeoSpatial Open Source Software with established project communities and a wide user base
# It will be ready for the next release in accordance with our [https://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdE1SYUN3YWJ2N1NpSUczbW9IRWZNclE&hl=en_GB schedule]

== Application Questions ==

Projects need to provide:
* Project Champion
: Someone who will liaise between the OSGeoLive team and the project and ensures the application remains up to date on OSGeoLive.
* A base [[#Install_Script]] for installing onto an Ubuntu Linux based system.
* [[#Documentation]] in line with OSGeoLive templates
* Someone who will run and verify the applications works in development releases
* [http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB Project Status] to be maintained.

If you think you can cover all these criteria for your project, then send an email to the [http://lists.osgeo.org/mailman/listinfo/live-demo OSGeoLive email list] asking if your project is appropriate. When emailing the list, please address the questions in the [[Live_GIS_Disc_Apply]] form.

== Which version to use? ==

* Stable, always! LiveGIS users are usually seeing OSGeo newbies and will be turned off by any software bugs.

== Install Script ==
Each project is to write a shell script which installs and configures your stable application into the OSGeoLive Xubuntu.

All install scripts for building the LiveGIS disc shall be licensed as LGPL.

When finished, ask the OSGeoLive team to reference your script from ''main.sh''.

Scripts are stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/

The script may be as simple as:
[https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_mapserver.sh install_mapserver.sh], which just
apt-get install mapserver

Projects that haven't been packaged for Ubuntu yet are slightly more complicated:

The uDig package is a good example: [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_udig.sh install_udig.sh]

* 3rd Party Repositories: Create an <app>.list file with your repository in sources.list.d/ in the svn, in your script copy the file to the local machine like
cp -f ../sources.list/ubuntugis.list /etc/apt/sources.list.d/

don't forget to add the repository key like so
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 68436DDF

== Packaging conventions ==

* '''sudo''': Assume the script is to be executed as root. This means that sudo is only needed if you need to execute a command as e.g. the database user.
: This means that ~/ refers to the directory /home/root/, so you should use ~user/ to reference /home/user/.
: Preferred method is to put the <tt>USER_NAME</tt> and <tt>USER_HOME</tt> variables at the top, so these can be easily changed in all scripts if needed.
USER_NAME="user"
USER_HOME="/home/$USER_NAME"
cp package_readme.txt "$USER_HOME"

* '''Called twice''': Assume that the script will be executed multiple times, (as people may re-run the install process to get it right).
: Make sure that nothing is corrupted if the script runs a second time.

* '''No Prompts''': Try not to have any interactive steps which prompt the user for an answer, as we want the scripts to be run automatically. In particular, try running the script a second time, and see if you get prompted to overwrite files.

* '''/tmp''': Copy all downloads into /tmp/build_<package>/
: Don't delete the /tmp/build_<package> directory afterwards. If the script is re-run, then time and bandwidth is saved by not having to download large files again. Do not do code checkouts or place temporary files in the starting build directory, which is ./bin/ in the live disc's SVN tree. See the "BUILD_DIR" environment variable used in a number of scripts if you later have to refer back to the ../app-conf/ or ../app-data/ relative paths in the live disc's SVN tree.

* '''Icons''': Where appropriate, create an icon on the desktop which loads the application. The file should be called <packagename>.desktop and placed in /home/user/Desktop/ for further processing. The icons will be sorted and the Geospatial menu will be auto-generated from here.
: Install <packagename>.png icon files to the /usr/share/icons/ directory.
: see <tt>install_qgis.sh</tt> for an example

* '''Browser bookmarks:''' If the application is launched from the browser, then include the application in Firefox bookmarks.
: (Todo: How do we do this?)

* '''wget''': When downloading large files using wget, use the "-c" continue command, as it will not re-download files if they already exist, and will continue if one is partially downloaded:
wget -c package.tar.gz
: Do not use -c if there is a chance the file of that name will change on the server. Add "<tt>--progress=dot:mega</tt>" to the wget command line if the file is at all large.
: Tiny files should use wget's -nv (non-verbose) flag.
: In a similar manner, use "<tt>--quiet</tt>" when calling '''qsql'''.

* '''mkdir''': Use -p (create parents too) option when creating a directory, as it doesn't complain about creating the directory a second time.
mkdir -p <dir>

* '''Binary files''': Do not put large (>5mb) binary files into the SVN repository without asking first. Due to SVN's preservation of history, once they are added they can never be removed, and forever-more clog up the backend database. Subversion is designed to be a ''source code management'' tool, not a data warehouse. There is space for large static data files (e.g. sample data) at http://download.osgeo.org/livedvd/data/. Just ask on the mailing list if you'd like to house something there.

= Packaging considerations =

The criteria used to select applications for the LiveGIS follow.

== Technical limitations ==
=== Space considerations ===
* DVD: approx 4.2gb compressed
* USB stick: For a 4gb persistent USB stick with some room left over for user-workspace, 3.2-3.5gb compressed. (This pretty much works out to the DVD version minus the preloaded Mac and Windows installers)
* Virtual Machines: theoretically unlimited, but in practice 20gb uncompressed

So smaller apps (<30mb) of lesser priority may easily slip in under the ire radar, but an external project that wants to use a 25% of the available disc space would be the first to be compromised away.

=== Memory considerations ===
Both Virtual Machines, and a LiveDVD images are likely to be constrained by limited memory. So to reduce memory usage. Disk image size is not of major concern, as we can just distribute less data.

The following principles should be followed.
* Do not start applications upon power up. (Ie, don't start deamons, allow users to start them instead).
* Set up examples which, by default, don't depend on other applications. Less applications open, means less memory. Ie, Have GeoServer access a shapefile instead of PostGIS.
* Try to avoid scenarios which write data to disk, as disk space in the Live DVD is stored in RAM, and is not cleared afterward.

File permissions and filesystem user IDs can get garbled during the ISO build process. Therefore a special method is used to ensure that data files which must be read-write can be accessed.

To install a writable data directory or files, change its group to "users" and set the file(s) as group-writable:

adduser $USER_NAME users
chmod -R g+w /usr/local/share/<packagename>/data/
chown -R root.users /usr/local/share/<packagename>/data/

and symlink into the user's home directory if necessary.

Setting files to have universal write permission is strongly discouraged. '''Do not use "''chmod 777 -R''".'''

=== Shared resources ===

The disc is a busy place, so we must all play nice and take care not step on each others toes.

==== Changes to the base system ====

Please don't customize any system level infrastructure which other projects may be relying on.
Often there is an /etc/$foo.d/ directory for you to put config additions into. Always put non-.deb packaged custom things in /usr/local not /usr!

==== Port numbers ====

To avoid overlaps and conflicts with other packages, please avoid putting web services on common port numbers like 8000 or 8080. Choose a random port between 8000 and 8080, search through the whole documentation for this port number (e.g. "grep -R 8042 doc bin") and only use this number if it isn't mentioned anywhere else. Then add your new port number to your quick guide so that others will find it.

Rasdaman is using ports 7001 (dispatcher), 7002, 7003, etc. (worker processes). The number of workers is fixed in the etc/rasmgr.conf file, at least one is required.

= Directory Structure =

# '''/tmp''' Temporary files (e.g., downloaded archives) go into /tmp. Please create a separate folder for your project.
# '''/usr/lib''' application are usually installed into /usr/lib
# '''/usr/bin''' things that get executed by the user such as startup scripts or links to them should go into /usr/bin
# '''/etc/init.d''' startup/shutdown scripts for services (e.g., postgres, apache, tomcat) are stored in /etc/init.d
# '''/usr/local/share''' sample data and documentation goes into /usr/local/share
# '''/etc''' config files are stored in /etc
# '''/home/user''' user specific config files or working directories can go into <tt>/home/user/</tt>. However, keep files in /home/user as small as possible as this folder is loaded into memory in the Live DVD. Symlinks into /usr/local can be useful here.

* ''You are strongly encouraged to use '''/usr/local/''' and '''/var/local/''' for storing non-packaged content.''

== .deb Packaging ==
Currently many packages are installed from bash scripts. The major release goal for the next versions of the Osgeo live DVD is to make sure that all programs can be installed from debian packages.

This offers many advantages: packages can be uninstalled and updated to newer versions without having to build the complete live dvd. This also makes testing more easy: one can just update to the last live dvd rather than having to install all software.
Ideally, applications should be packaged in [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] or [http://wiki.debian.org/DebianGis DebianGIS] repositories, or in a Launchpad PPA (e.g. available from the UbuntuGIS repository). This would mean that any ubuntu or debian user can profit from the packaging works for the osgeo live dvd.

Even though packaging can be overwhelming at first, it eventually boils down to creating a few files in a debian subdirectory from a place where the sources of your application are. A quick and easy way to generate a template is by running dh_make (from the dh-make package) in the directory where your sources are.
This will create the necessary files to build a package which you will have to edit before packaging for real.

Many tutorials exist on the web that can assist building debian packages, so I will not repeat all of them here.
https://wiki.debian.org/IntroDebianPackaging provides a good start.

If you are new to debian packaging probably the best you can do is ask on the mailing lists of [http://lists.osgeo.org/mailman/listinfo/ubuntu UbuntuGIS] or [https://lists.debian.org/debian-gis/ DebianGIS] whether someone can provide a template to start your own package.

=== Packaging Python ===

Instead of using "<tt>pip</tt>", "<tt>easy_install</tt>" or other Python installation methods it is preferred to install the <tt>''python-pkgname''</tt> package if it exists. By integrating the python libraries into the dpkg system-files database we can quickly find files and make sure that there are not two different versions from two different sources competing and conflicting. Fortunately it is very easy to create a .deb from projects on Pypi.

* First check that the software is not already on the disc with "dpkg -S ''name''" and "locate ''name''".

* Next check if it exists, for example:
apt-cache search fiona

* If needed, install the packaging tools:
sudo apt-get install python-stdeb build-essential python-all-dev

* Run ''<tt>pypi-install</tt>'' to download, build, and install the .deb. For example:
sudo pypi-install Fiona

Add the "--keep" command line option to retain a copy of the .deb and .changes file in a subdirectory of /tmp, e.g. for upload to UbuntuGIS's repository.

See also [http://article.gmane.org/gmane.comp.gis.osgeo.livedemo/7466/ this mailing list thread] with further details on manually packaging using the same tools.

== Example Datasets ==
In order to reduce disk space, and to provide consistency between projects, we strongly encourage all projects to make use of the common datasets packaged on OSGeo-Live by the [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_gisdata.sh install_gisdata.sh] script.

All datasets should be installed into /usr/local/share/data, or if installed elsewhere, there should be a symbolic link into /usr/local/share/data. Data should not be installed in the /home/user directory, as I understand that data in the HOME directory is copied into RAM. (TBD find confirmation of this).

There is a symbolic link from /home/user/data to /usr/local/share/data to make it easy to find from a user's home directory. (Documentation should reference /home/user/data/... ).

Datasets are also available via http://localhost/data/ and http://live.osgeo.org/data/ (which is a symbolic link from /var/www/data to /usr/local/share/data).

=== Natural Earth ===
The [http://www.naturalearthdata.com/ Natural Earth] dataset is the preferred dataset for all examples.

* [http://www.naturalearthdata.com/downloads/10m-cultural-vectors/ 1:10m Simple Populated Places]. Shapefiles are in /user/data/natural_earth/* and have also been loaded into PostGIS.
** admin_0_countries
** admin_1_states_provinces
** geography_marine_polys
** geography_regions_elevated_points
** geography_regions_polys
** lakes
** land
** ocean
** populated_places_simple
** rivers_lake_centerlines
** urban_areas

* Raster basemap -- Cross Blended Hypso with Shaded Relief and Water 1:50 million, stored in /user/data/natural_earth/HYP_50M_SR_W/*

=== OpenStreetMap ===
OpenStreetMap data is loaded into /usr/local/share/data/osm/feature_city.osm

=== North Carolina ===
The [http://www.grassbook.org/data_menu3rd.php OSGeo-Geodata collection of geotiffs and shapefiles for Wake County] (North Carolina) has been tentatively added for the 5.0 release.

The [http://www.grassbook.org/ncexternal/nc_datalist.html North Carolina layers] can be found in /usr/local/share/data/north_carolina/ (symlinked to ~/data/north_carolina)

=== Others ===
If you need another type of data for your examples, please discuss this with us.

== Documentation ==
OSGeo-Live documentation is published at:
;On OSGeo-Live: http://localhost/ which is stored in /var/www/
;Stable release: http://live.osgeo.org
;Nightly build: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/index.html

=== Application Overview ===

The [[Marketing_Artefacts#Application_Overview|Application Overview]] is a one page marketing page targeted at a someone considering using GeoSpatial Open Source, who may be a GeoSpatial User, a Technical person without much geospatial expertise, or manager with limited GeoSpatial or technical experience. Published Overviews are linked from here: http://live.osgeo.org/en/overview/overview.html

The source Overviews are written in [http://sphinx.pocoo.org/rest.html RST wiki format] and built using sphinx. Source documents are to be stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/overview/en/<application>_overview.rst . They should follow the structure and style of the reference Overview, which has lots of helpful comments, at https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/overview/postgis_overview.rst

The Overviews are currently published as [http://live.osgeo.org/overview/overview.html HTML pages]. In future we intend to also create 1 page PDFs, (to hand out as a flier at conferences, and as a page in the OSGeo Book of projects), and as Word/OpenOffice (to be cut and pasted into project proposals and articles which usually use these formats).

Overviews also require:
* an image for the application, usually a screen shot or collage of screen shots, as per [[#Screen_Shot|Screen Shot]] ('''don't use GIF format, please use PNG instead''').
* A project logo as per [[#Logo]] ('''don't use GIF format, please use PNG instead''').

Try printing the html page from the browser, and ensure that the page is less than one page long. (The less words you write, the more people will read your documentation.)

Once finished, note your project's overview status="draft" in the OSGeo-Live project status at: http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB#gid=5 and email live-demo@lists.osgeo.org noting your documentation is ready for review. Once reviewed, the status is moved to "complete" and is ready for translation.

=== Application Quick Start ===
The [[Marketing_Artefacts#Application_Quick_Start|Application Quick Start]] defines detailed steps, with screen shots, for a new user to run one of the application's core functions. It should be able to be run in 5 to 10 minutes.

Try to make use of a friendly, conversational writing style, similar to the way a tutor would talk a class through an example. The quickstarts for [http://live.osgeo.org/en/quickstart/R_quickstart.html R] and [http://live.osgeo.org/en/quickstart/geoserver_quickstart.html GeoServer] do this very well.

Source documentation is written in [http://sphinx.pocoo.org/rest.html RST wiki format], is built using sphinx, and is stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/quickstart/<application>_quickstart.rst

The reference quickstart, which includes structure guidelines and with tips on how to fill in the quickstart is here:
https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/quickstart/udig_quickstart.rst
and is published here: http://live.osgeo.org/en/quickstart/udig_quickstart.html

In order to reduce disk space, and maintain consistency between applications, we request that all examples make use of the common [[#Example_Datasets]]. If the datasets don't cover your requirements, discuss this with us and we may add another suitable common dataset.

Applications are expected to include screen shots for each major step in the quickstart, as per [[#Screen_Shot|Screen Shot]].

Once finished, note your project's quickstart status="draft" in the OSGeo-Live project status at: http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB#gid=5 and email live-demo@lists.osgeo.org noting your documentation is ready for review. Once reviewed, the status is moved to "complete" and is ready for translation.

==== Quickstart Review Checklist ====

* Review latest Quickstart docs at: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/overview/overview.html
* Run with latest OSGeo-Live Development Release. Download from: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Downloads
* ''Before starting, notify others that you have started reviewing by setting "Quickstart reviewed by:" to "Started:<your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If you feel confident [http://wiki.osgeo.org/wiki/Live_GIS_Add_Project#Documentation updating the .rst documentation], then feel free to correct simple errors that you find, and commit back to subversion. (you will need [http://wiki.osgeo.org/wiki/Live_GIS_Disc#Subversion subversion access]).
* Otherwise, report problems in our [http://wiki.osgeo.org/wiki/Live_GIS_Disc#Issue_Tracker Issue Tracker] with keywords: ''docs 6.5 <application>'', component: ''LiveDVD'', milestone:

;Someone experienced with the project:
* Is the quickstart applicable for the version of the application installed on OSGeo-Live?
* If sample data is used, is it one of the OSGeo-Live datasets?
* Is there a screenshot for each step?
* Where appropriate, have screenshots been labeled (usually with numbers) to link them back to the documentation?
* ''Once finished, update Quickstart status to "6.5 Draft" and "Quickstart reviewed by:" to "osgeolive-version <your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If not already included, add the editor's name to the top of the .rst file:
:Author: Your Name
;QA Tester:
* Has the quickstart been run from start to finish?
* How long did the quickstart take to run? (Should be between 5 and 15 minutes)
* Has every step been explained in the quickstart?
* ''Once finished, update Quickstart status to "6.5 Reviewed" and "Quickstart reviewed by:" to "osgeolive-version <your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If not already included, add the testers name to the top of the .rst file:
:Reviewer: Your Name

;Reviewer for readability and consistency:
* Would the quickstart be understandable for a novice? Are all technical terms and acronyms explained?
* Is the language clear, and concise?
* Does the first paragraph explain what this Quickstart is going to cover?
* Are there steps for one scenario?
* Does the quickstart include "Things to try" and/or "What next" sections?
* ''Once finished, update Quickstart status to "6.5 Final" and "Quickstart reviewed by:" to "osgeolive-version <your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If not already included, add the reviewer's name to the top of the .rst file:
:Reviewer: Your Name

=== Logo ===
The Project's logo is used in the headers of documentation (like Project Overviews, QuickStarts, Powerpoint presentations etc, and as icons on the OSGeo-Live Desktop. Hence there are a few different requirements for the logo.

;Header logo:
:* Stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/images/project_logos
:* Filename should be "logo-<projectname>.png" (apparently PNG is required for PDF docs)
:* Should have a transparent background (not white)
:* Preferably stored in size 125x125 pixels (for use in Project Overview and QuickStarts)
:* For PNGs ''please'' run a program like [http://packages.ubuntu.com/pngcrush pngcrush] or [http://packages.ubuntu.com/optipng optipng] to reduce the size of the image without degrading quality. Here's an example using <tt>optipng</tt>:
optipng -o5 image.png
:* Preferably also available as SVG, stored as "logo-<projectname>.svg"

;Desktop logo:
:We are still to define the requirements for creating a desktop logo. They will likely include:
:* A 32x32-pixel XPM icon for use by the Debian menus
:* A 48x48-pixel PNG icon for use by freedesktop.org menus

=== Screen Shot ===
Project overviews include an image, which is usually a screen shot, or collage of screen shorts. Quickstarts include screen shots for each significant step.
* Screen shots can be taken using [http://shutter-project.org/ Shutter] (on linux) or [http://getgreenshot.org/ Greenshot] (on windows).
* Screen shots should be taken from a 1024x768 display, and should be created in PNG format. (Apparently PNG is required for PDF documentation.)
* Images are to be stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/images/screenshots/1024x768
* For Quickstarts, consider marking up the image to explain the current steps. Eg: Add circled numbers: 1, 2, 3 or draw an oval around buttons being described. This is very easy to do using the "Edit" tab in the Shutter program, which provides these drawing icons to add. Tutorials augmented with detailed and pertinent images make it easy for the reader to follow what is going on. Extra time spent on an image pays off big in comprehension (you need more than just a course screen dump). Lines, numbering, highlights, boxes and annotations all help direct a user's focus to those areas which are important.
* Screenshots with large areas of constant color (menus, etc.) should be in PNG format, screenshots containing large areas of imagery (satellite images, shaded relief DEMs, etc.) should be in JPEG format.
* For PNGs ''please'' run a program like [http://packages.ubuntu.com/pngcrush pngcrush] to reduce the size of the image without degrading quality.

=== Extra Documentation ===
Some projects link to extra documentation, stored as PDFs or similar, or alternatively provide example applications. These should be referenced in documentation via a relative link such than it can viewed from:
http://localhost/<application>/... or http://live.osgeo.org/<application>/...

This should typically be achieved by creating a symbolic link from /var/www/<application> to /usr/local/share/doc/<application>

== Publishing Documentation ==

The following web service is useful for checking [http://docutils.sourceforge.net/rst.html reST] formatting: http://rst.ninjs.org/

For a more comprehensive test, set up the reST processor, sphinx:
: (''you will have to have [http://sphinx.pocoo.org/ Sphinx 0.6.4 or greater] installed, it's in the'' <tt>python-sphinx</tt> ''Debian package'')

sudo apt-get install python-sphinx

cd osgeo/livedvd/gisvm/trunk/doc/
make html

You can then view the results in:
osgeo/livedvd/gisvm/trunk/doc/_build/*.html

= Translations =
For details on how to translate, refer to [[Live GIS Translate]]

[[Category: Live-demo]]

Live GIS Add Project

2014-05-10T08:35:04Z

Wiki-HamishBowman: /* Packaging Python */ sp.

== What gets into OSGeoLive? ==

We have an emphasis of quality, and we are space constrained on OSGeoLive and so are selective about what is included.

Priority for selecting OSGeoLive projects to package is:
# OSGeo Projects
# OSGeo Projects in incubation
# Stable GeoSpatial Open Source Software being presented in workshops, tutorials, or presentations at FOSS4G
# Other Stable GeoSpatial Open Source Software with established project communities and a wide user base
# It will be ready for the next release in accordance with our [https://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdE1SYUN3YWJ2N1NpSUczbW9IRWZNclE&hl=en_GB schedule]

== Application Questions ==

Projects need to provide:
* Project Champion
: Someone who will liaise between the OSGeoLive team and the project and ensures the application remains up to date on OSGeoLive.
* A base [[#Install_Script]] for installing onto an Ubuntu Linux based system.
* [[#Documentation]] in line with OSGeoLive templates
* Someone who will run and verify the applications works in development releases
* [http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB Project Status] to be maintained.

If you think you can cover all these criteria for your project, then send an email to the [http://lists.osgeo.org/mailman/listinfo/live-demo OSGeoLive email list] asking if your project is appropriate. When emailing the list, please address the questions in the [[Live_GIS_Disc_Apply]] form.

== Which version to use? ==

* Stable, always! LiveGIS users are usually seeing OSGeo newbies and will be turned off by any software bugs.

== Install Script ==
Each project is to write a shell script which installs and configures your stable application into the OSGeoLive Xubuntu.

All install scripts for building the LiveGIS disc shall be licensed as LGPL.

When finished, ask the OSGeoLive team to reference your script from ''main.sh''.

Scripts are stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/

The script may be as simple as:
[https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_mapserver.sh install_mapserver.sh], which just
apt-get install mapserver

Projects that haven't been packaged for Ubuntu yet are slightly more complicated:

The uDig package is a good example: [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_udig.sh install_udig.sh]

* 3rd Party Repositories: Create an <app>.list file with your repository in sources.list.d/ in the svn, in your script copy the file to the local machine like
cp -f ../sources.list/ubuntugis.list /etc/apt/sources.list.d/

don't forget to add the repository key like so
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 68436DDF

== Packaging conventions ==

* '''sudo''': Assume the script is to be executed as root. This means that sudo is only needed if you need to execute a command as e.g. the database user.
: This means that ~/ refers to the directory /home/root/, so you should use ~user/ to reference /home/user/.
: Preferred method is to put the <tt>USER_NAME</tt> and <tt>USER_HOME</tt> variables at the top, so these can be easily changed in all scripts if needed.
USER_NAME="user"
USER_HOME="/home/$USER_NAME"
cp package_readme.txt "$USER_HOME"

* '''Called twice''': Assume that the script will be executed multiple times, (as people may re-run the install process to get it right).
: Make sure that nothing is corrupted if the script runs a second time.

* '''No Prompts''': Try not to have any interactive steps which prompt the user for an answer, as we want the scripts to be run automatically. In particular, try running the script a second time, and see if you get prompted to overwrite files.

* '''/tmp''': Copy all downloads into /tmp/build_<package>/
: Don't delete the /tmp/build_<package> directory afterwards. If the script is re-run, then time and bandwidth is saved by not having to download large files again. Do not do code checkouts or place temporary files in the starting build directory, which is ./bin/ in the live disc's SVN tree. See the "BUILD_DIR" environment variable used in a number of scripts if you later have to refer back to the ../app-conf/ or ../app-data/ relative paths in the live disc's SVN tree.

* '''Icons''': Where appropriate, create an icon on the desktop which loads the application. The file should be called <packagename>.desktop and placed in /home/user/Desktop/ for further processing. The icons will be sorted and the Geospatial menu will be auto-generated from here.
: Install <packagename>.png icon files to the /usr/share/icons/ directory.
: see <tt>install_qgis.sh</tt> for an example

* '''Browser bookmarks:''' If the application is launched from the browser, then include the application in Firefox bookmarks.
: (Todo: How do we do this?)

* '''wget''': When downloading large files using wget, use the "-c" continue command, as it will not re-download files if they already exist, and will continue if one is partially downloaded:
wget -c package.tar.gz
: Do not use -c if there is a chance the file of that name will change on the server. Add "<tt>--progress=dot:mega</tt>" to the wget command line if the file is at all large.
: Tiny files should use wget's -nv (non-verbose) flag.
: In a similar manner, use "<tt>--quiet</tt>" when calling '''qsql'''.

* '''mkdir''': Use -p (create parents too) option when creating a directory, as it doesn't complain about creating the directory a second time.
mkdir -p <dir>

* '''Binary files''': Do not put large (>5mb) binary files into the SVN repository without asking first. Due to SVN's preservation of history, once they are added they can never be removed, and forever-more clog up the backend database. Subversion is designed to be a ''source code management'' tool, not a data warehouse. There is space for large static data files (e.g. sample data) at http://download.osgeo.org/livedvd/data/. Just ask on the mailing list if you'd like to house something there.

= Packaging considerations =

The criteria used to select applications for the LiveGIS follow.

== Technical limitations ==
=== Space considerations ===
* DVD: approx 4.2gb compressed
* USB stick: For a 4gb persistent USB stick with some room left over for user-workspace, 3.2-3.5gb compressed. (This pretty much works out to the DVD version minus the preloaded Mac and Windows installers)
* Virtual Machines: theoretically unlimited, but in practice 20gb uncompressed

So smaller apps (<30mb) of lesser priority may easily slip in under the ire radar, but an external project that wants to use a 25% of the available disc space would be the first to be compromised away.

=== Memory considerations ===
Both Virtual Machines, and a LiveDVD images are likely to be constrained by limited memory. So to reduce memory usage. Disk image size is not of major concern, as we can just distribute less data.

The following principles should be followed.
* Do not start applications upon power up. (Ie, don't start deamons, allow users to start them instead).
* Set up examples which, by default, don't depend on other applications. Less applications open, means less memory. Ie, Have GeoServer access a shapefile instead of PostGIS.
* Try to avoid scenarios which write data to disk, as disk space in the Live DVD is stored in RAM, and is not cleared afterward.

File permissions and filesystem user IDs can get garbled during the ISO build process. Therefore a special method is used to ensure that data files which must be read-write can be accessed.

To install a writable data directory or files, change its group to "users" and set the file(s) as group-writable:

adduser $USER_NAME users
chmod -R g+w /usr/local/share/<packagename>/data/
chown -R root.users /usr/local/share/<packagename>/data/

and symlink into the user's home directory if necessary.

Setting files to have universal write permission is strongly discouraged. '''Do not use "''chmod 777 -R''".'''

=== Shared resources ===

The disc is a busy place, so we must all play nice and take care not step on each others toes.

==== Changes to the base system ====

Please don't customize any system level infrastructure which other projects may be relying on.
Often there is an /etc/$foo.d/ directory for you to put config additions into. Always put non-.deb packaged custom things in /usr/local not /usr!

==== Port numbers ====

To avoid overlaps and conflicts with other packages, please avoid putting web services on common port numbers like 8000 or 8080. Choose a random port between 8000 and 8080, search through the whole documentation for this port number (e.g. "grep -R 8042 doc bin") and only use this number if it isn't mentioned anywhere else. Then add your new port number to your quick guide so that others will find it.

Rasdaman is using ports 7001 (dispatcher), 7002, 7003, etc. (worker processes). The number of workers is fixed in the etc/rasmgr.conf file, at least one is required.

= Directory Structure =

# '''/tmp''' Temporary files (e.g., downloaded archives) go into /tmp. Please create a separate folder for your project.
# '''/usr/lib''' application are usually installed into /usr/lib
# '''/usr/bin''' things that get executed by the user such as startup scripts or links to them should go into /usr/bin
# '''/etc/init.d''' startup/shutdown scripts for services (e.g., postgres, apache, tomcat) are stored in /etc/init.d
# '''/usr/local/share''' sample data and documentation goes into /usr/local/share
# '''/etc''' config files are stored in /etc
# '''/home/user''' user specific config files or working directories can go into <tt>/home/user/</tt>. However, keep files in /home/user as small as possible as this folder is loaded into memory in the Live DVD. Symlinks into /usr/local can be useful here.

* ''You are strongly encouraged to use '''/usr/local/''' and '''/var/local/''' for storing non-packaged content.''

== .deb Packaging ==
Currently many packages are installed from bash scripts. The major release goal for the next versions of the Osgeo live DVD is to make sure that all programs can be installed from debian packages.

This offers many advantages: packages can be uninstalled and updated to newer versions without having to build the complete live dvd. This also makes testing more easy: one can just update to the last live dvd rather than having to install all software.
Ideally, applications should be packaged in [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] or [http://wiki.debian.org/DebianGis DebianGIS] repositories, or in a Launchpad PPA (e.g. available from the UbuntuGIS repository). This would mean that any ubuntu or debian user can profit from the packaging works for the osgeo live dvd.

Even though packaging can be overwhelming at first, it eventually boils down to creating a few files in a debian subdirectory from a place where the sources of your application are. A quick and easy way to generate a template is by running dh_make (from the dh-make package) in the directory where your sources are.
This will create the necessary files to build a package which you will have to edit before packaging for real.

Many tutorials exist on the web that can assist building debian packages, so I will not repeat all of them here.
https://wiki.debian.org/IntroDebianPackaging provides a good start.

If you are new to debian packaging probably the best you can do is ask on the mailing lists of [http://lists.osgeo.org/mailman/listinfo/ubuntu UbuntuGIS] or [https://lists.debian.org/debian-gis/ DebianGIS] whether someone can provide a template to start your own package.

=== Packaging Python ===

Instead of using "<tt>pip</tt>", "<tt>easy_install</tt>" or other Python installation methods it is preferred to install the <tt>''python-pkgname''</tt> package if it exists. By integrating the python libraries into the dpkg system-files database we can quickly find files and make sure that there are not two different versions from two different sources competing and conflicting. Fortunately it is very easy to create a .deb from projects on Pypi.

* First check that the software is not already on the disc with "dpkg -S ''name''" and "locate ''name''".

* If needed, install the packaging tools:
sudo apt-get install python-stdeb build-essential python-all-dev

* Run ''<tt>pypi-install</tt>'' to download, build, and install the .deb. For example:
sudo pypi-install Fiona

Add the "--keep" command line option to retain a copy of the .deb and .changes file in a subdirectory of /tmp, e.g. for upload to UbuntuGIS's repository.

See also [http://article.gmane.org/gmane.comp.gis.osgeo.livedemo/7466/ this mailing list thread] with further details on manually packaging using the same tools.

== Example Datasets ==
In order to reduce disk space, and to provide consistency between projects, we strongly encourage all projects to make use of the common datasets packaged on OSGeo-Live by the [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_gisdata.sh install_gisdata.sh] script.

All datasets should be installed into /usr/local/share/data, or if installed elsewhere, there should be a symbolic link into /usr/local/share/data. Data should not be installed in the /home/user directory, as I understand that data in the HOME directory is copied into RAM. (TBD find confirmation of this).

There is a symbolic link from /home/user/data to /usr/local/share/data to make it easy to find from a user's home directory. (Documentation should reference /home/user/data/... ).

Datasets are also available via http://localhost/data/ and http://live.osgeo.org/data/ (which is a symbolic link from /var/www/data to /usr/local/share/data).

=== Natural Earth ===
The [http://www.naturalearthdata.com/ Natural Earth] dataset is the preferred dataset for all examples.

* [http://www.naturalearthdata.com/downloads/10m-cultural-vectors/ 1:10m Simple Populated Places]. Shapefiles are in /user/data/natural_earth/* and have also been loaded into PostGIS.
** admin_0_countries
** admin_1_states_provinces
** geography_marine_polys
** geography_regions_elevated_points
** geography_regions_polys
** lakes
** land
** ocean
** populated_places_simple
** rivers_lake_centerlines
** urban_areas

* Raster basemap -- Cross Blended Hypso with Shaded Relief and Water 1:50 million, stored in /user/data/natural_earth/HYP_50M_SR_W/*

=== OpenStreetMap ===
OpenStreetMap data is loaded into /usr/local/share/data/osm/feature_city.osm

=== North Carolina ===
The [http://www.grassbook.org/data_menu3rd.php OSGeo-Geodata collection of geotiffs and shapefiles for Wake County] (North Carolina) has been tentatively added for the 5.0 release.

The [http://www.grassbook.org/ncexternal/nc_datalist.html North Carolina layers] can be found in /usr/local/share/data/north_carolina/ (symlinked to ~/data/north_carolina)

=== Others ===
If you need another type of data for your examples, please discuss this with us.

== Documentation ==
OSGeo-Live documentation is published at:
;On OSGeo-Live: http://localhost/ which is stored in /var/www/
;Stable release: http://live.osgeo.org
;Nightly build: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/index.html

=== Application Overview ===

The [[Marketing_Artefacts#Application_Overview|Application Overview]] is a one page marketing page targeted at a someone considering using GeoSpatial Open Source, who may be a GeoSpatial User, a Technical person without much geospatial expertise, or manager with limited GeoSpatial or technical experience. Published Overviews are linked from here: http://live.osgeo.org/en/overview/overview.html

The source Overviews are written in [http://sphinx.pocoo.org/rest.html RST wiki format] and built using sphinx. Source documents are to be stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/overview/en/<application>_overview.rst . They should follow the structure and style of the reference Overview, which has lots of helpful comments, at https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/overview/postgis_overview.rst

The Overviews are currently published as [http://live.osgeo.org/overview/overview.html HTML pages]. In future we intend to also create 1 page PDFs, (to hand out as a flier at conferences, and as a page in the OSGeo Book of projects), and as Word/OpenOffice (to be cut and pasted into project proposals and articles which usually use these formats).

Overviews also require:
* an image for the application, usually a screen shot or collage of screen shots, as per [[#Screen_Shot|Screen Shot]] ('''don't use GIF format, please use PNG instead''').
* A project logo as per [[#Logo]] ('''don't use GIF format, please use PNG instead''').

Try printing the html page from the browser, and ensure that the page is less than one page long. (The less words you write, the more people will read your documentation.)

Once finished, note your project's overview status="draft" in the OSGeo-Live project status at: http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB#gid=5 and email live-demo@lists.osgeo.org noting your documentation is ready for review. Once reviewed, the status is moved to "complete" and is ready for translation.

=== Application Quick Start ===
The [[Marketing_Artefacts#Application_Quick_Start|Application Quick Start]] defines detailed steps, with screen shots, for a new user to run one of the application's core functions. It should be able to be run in 5 to 10 minutes.

Try to make use of a friendly, conversational writing style, similar to the way a tutor would talk a class through an example. The quickstarts for [http://live.osgeo.org/en/quickstart/R_quickstart.html R] and [http://live.osgeo.org/en/quickstart/geoserver_quickstart.html GeoServer] do this very well.

Source documentation is written in [http://sphinx.pocoo.org/rest.html RST wiki format], is built using sphinx, and is stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/quickstart/<application>_quickstart.rst

The reference quickstart, which includes structure guidelines and with tips on how to fill in the quickstart is here:
https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/quickstart/udig_quickstart.rst
and is published here: http://live.osgeo.org/en/quickstart/udig_quickstart.html

In order to reduce disk space, and maintain consistency between applications, we request that all examples make use of the common [[#Example_Datasets]]. If the datasets don't cover your requirements, discuss this with us and we may add another suitable common dataset.

Applications are expected to include screen shots for each major step in the quickstart, as per [[#Screen_Shot|Screen Shot]].

Once finished, note your project's quickstart status="draft" in the OSGeo-Live project status at: http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB#gid=5 and email live-demo@lists.osgeo.org noting your documentation is ready for review. Once reviewed, the status is moved to "complete" and is ready for translation.

==== Quickstart Review Checklist ====

* Review latest Quickstart docs at: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/overview/overview.html
* Run with latest OSGeo-Live Development Release. Download from: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Downloads
* ''Before starting, notify others that you have started reviewing by setting "Quickstart reviewed by:" to "Started:<your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If you feel confident [http://wiki.osgeo.org/wiki/Live_GIS_Add_Project#Documentation updating the .rst documentation], then feel free to correct simple errors that you find, and commit back to subversion. (you will need [http://wiki.osgeo.org/wiki/Live_GIS_Disc#Subversion subversion access]).
* Otherwise, report problems in our [http://wiki.osgeo.org/wiki/Live_GIS_Disc#Issue_Tracker Issue Tracker] with keywords: ''docs 6.5 <application>'', component: ''LiveDVD'', milestone:

;Someone experienced with the project:
* Is the quickstart applicable for the version of the application installed on OSGeo-Live?
* If sample data is used, is it one of the OSGeo-Live datasets?
* Is there a screenshot for each step?
* Where appropriate, have screenshots been labeled (usually with numbers) to link them back to the documentation?
* ''Once finished, update Quickstart status to "6.5 Draft" and "Quickstart reviewed by:" to "osgeolive-version <your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If not already included, add the editor's name to the top of the .rst file:
:Author: Your Name
;QA Tester:
* Has the quickstart been run from start to finish?
* How long did the quickstart take to run? (Should be between 5 and 15 minutes)
* Has every step been explained in the quickstart?
* ''Once finished, update Quickstart status to "6.5 Reviewed" and "Quickstart reviewed by:" to "osgeolive-version <your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If not already included, add the testers name to the top of the .rst file:
:Reviewer: Your Name

;Reviewer for readability and consistency:
* Would the quickstart be understandable for a novice? Are all technical terms and acronyms explained?
* Is the language clear, and concise?
* Does the first paragraph explain what this Quickstart is going to cover?
* Are there steps for one scenario?
* Does the quickstart include "Things to try" and/or "What next" sections?
* ''Once finished, update Quickstart status to "6.5 Final" and "Quickstart reviewed by:" to "osgeolive-version <your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If not already included, add the reviewer's name to the top of the .rst file:
:Reviewer: Your Name

=== Logo ===
The Project's logo is used in the headers of documentation (like Project Overviews, QuickStarts, Powerpoint presentations etc, and as icons on the OSGeo-Live Desktop. Hence there are a few different requirements for the logo.

;Header logo:
:* Stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/images/project_logos
:* Filename should be "logo-<projectname>.png" (apparently PNG is required for PDF docs)
:* Should have a transparent background (not white)
:* Preferably stored in size 125x125 pixels (for use in Project Overview and QuickStarts)
:* For PNGs ''please'' run a program like [http://packages.ubuntu.com/pngcrush pngcrush] or [http://packages.ubuntu.com/optipng optipng] to reduce the size of the image without degrading quality. Here's an example using <tt>optipng</tt>:
optipng -o5 image.png
:* Preferably also available as SVG, stored as "logo-<projectname>.svg"

;Desktop logo:
:We are still to define the requirements for creating a desktop logo. They will likely include:
:* A 32x32-pixel XPM icon for use by the Debian menus
:* A 48x48-pixel PNG icon for use by freedesktop.org menus

=== Screen Shot ===
Project overviews include an image, which is usually a screen shot, or collage of screen shorts. Quickstarts include screen shots for each significant step.
* Screen shots can be taken using [http://shutter-project.org/ Shutter] (on linux) or [http://getgreenshot.org/ Greenshot] (on windows).
* Screen shots should be taken from a 1024x768 display, and should be created in PNG format. (Apparently PNG is required for PDF documentation.)
* Images are to be stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/images/screenshots/1024x768
* For Quickstarts, consider marking up the image to explain the current steps. Eg: Add circled numbers: 1, 2, 3 or draw an oval around buttons being described. This is very easy to do using the "Edit" tab in the Shutter program, which provides these drawing icons to add. Tutorials augmented with detailed and pertinent images make it easy for the reader to follow what is going on. Extra time spent on an image pays off big in comprehension (you need more than just a course screen dump). Lines, numbering, highlights, boxes and annotations all help direct a user's focus to those areas which are important.
* Screenshots with large areas of constant color (menus, etc.) should be in PNG format, screenshots containing large areas of imagery (satellite images, shaded relief DEMs, etc.) should be in JPEG format.
* For PNGs ''please'' run a program like [http://packages.ubuntu.com/pngcrush pngcrush] to reduce the size of the image without degrading quality.

=== Extra Documentation ===
Some projects link to extra documentation, stored as PDFs or similar, or alternatively provide example applications. These should be referenced in documentation via a relative link such than it can viewed from:
http://localhost/<application>/... or http://live.osgeo.org/<application>/...

This should typically be achieved by creating a symbolic link from /var/www/<application> to /usr/local/share/doc/<application>

== Publishing Documentation ==

The following web service is useful for checking [http://docutils.sourceforge.net/rst.html reST] formatting: http://rst.ninjs.org/

For a more comprehensive test, set up the reST processor, sphinx:
: (''you will have to have [http://sphinx.pocoo.org/ Sphinx 0.6.4 or greater] installed, it's in the'' <tt>python-sphinx</tt> ''Debian package'')

sudo apt-get install python-sphinx

cd osgeo/livedvd/gisvm/trunk/doc/
make html

You can then view the results in:
osgeo/livedvd/gisvm/trunk/doc/_build/*.html

= Translations =
For details on how to translate, refer to [[Live GIS Translate]]

[[Category: Live-demo]]

Live GIS Add Project

2014-05-10T08:33:26Z

Wiki-HamishBowman: /* Packaging Python */

== What gets into OSGeoLive? ==

We have an emphasis of quality, and we are space constrained on OSGeoLive and so are selective about what is included.

Priority for selecting OSGeoLive projects to package is:
# OSGeo Projects
# OSGeo Projects in incubation
# Stable GeoSpatial Open Source Software being presented in workshops, tutorials, or presentations at FOSS4G
# Other Stable GeoSpatial Open Source Software with established project communities and a wide user base
# It will be ready for the next release in accordance with our [https://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdE1SYUN3YWJ2N1NpSUczbW9IRWZNclE&hl=en_GB schedule]

== Application Questions ==

Projects need to provide:
* Project Champion
: Someone who will liaise between the OSGeoLive team and the project and ensures the application remains up to date on OSGeoLive.
* A base [[#Install_Script]] for installing onto an Ubuntu Linux based system.
* [[#Documentation]] in line with OSGeoLive templates
* Someone who will run and verify the applications works in development releases
* [http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB Project Status] to be maintained.

If you think you can cover all these criteria for your project, then send an email to the [http://lists.osgeo.org/mailman/listinfo/live-demo OSGeoLive email list] asking if your project is appropriate. When emailing the list, please address the questions in the [[Live_GIS_Disc_Apply]] form.

== Which version to use? ==

* Stable, always! LiveGIS users are usually seeing OSGeo newbies and will be turned off by any software bugs.

== Install Script ==
Each project is to write a shell script which installs and configures your stable application into the OSGeoLive Xubuntu.

All install scripts for building the LiveGIS disc shall be licensed as LGPL.

When finished, ask the OSGeoLive team to reference your script from ''main.sh''.

Scripts are stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/

The script may be as simple as:
[https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_mapserver.sh install_mapserver.sh], which just
apt-get install mapserver

Projects that haven't been packaged for Ubuntu yet are slightly more complicated:

The uDig package is a good example: [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_udig.sh install_udig.sh]

* 3rd Party Repositories: Create an <app>.list file with your repository in sources.list.d/ in the svn, in your script copy the file to the local machine like
cp -f ../sources.list/ubuntugis.list /etc/apt/sources.list.d/

don't forget to add the repository key like so
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 68436DDF

== Packaging conventions ==

* '''sudo''': Assume the script is to be executed as root. This means that sudo is only needed if you need to execute a command as e.g. the database user.
: This means that ~/ refers to the directory /home/root/, so you should use ~user/ to reference /home/user/.
: Preferred method is to put the <tt>USER_NAME</tt> and <tt>USER_HOME</tt> variables at the top, so these can be easily changed in all scripts if needed.
USER_NAME="user"
USER_HOME="/home/$USER_NAME"
cp package_readme.txt "$USER_HOME"

* '''Called twice''': Assume that the script will be executed multiple times, (as people may re-run the install process to get it right).
: Make sure that nothing is corrupted if the script runs a second time.

* '''No Prompts''': Try not to have any interactive steps which prompt the user for an answer, as we want the scripts to be run automatically. In particular, try running the script a second time, and see if you get prompted to overwrite files.

* '''/tmp''': Copy all downloads into /tmp/build_<package>/
: Don't delete the /tmp/build_<package> directory afterwards. If the script is re-run, then time and bandwidth is saved by not having to download large files again. Do not do code checkouts or place temporary files in the starting build directory, which is ./bin/ in the live disc's SVN tree. See the "BUILD_DIR" environment variable used in a number of scripts if you later have to refer back to the ../app-conf/ or ../app-data/ relative paths in the live disc's SVN tree.

* '''Icons''': Where appropriate, create an icon on the desktop which loads the application. The file should be called <packagename>.desktop and placed in /home/user/Desktop/ for further processing. The icons will be sorted and the Geospatial menu will be auto-generated from here.
: Install <packagename>.png icon files to the /usr/share/icons/ directory.
: see <tt>install_qgis.sh</tt> for an example

* '''Browser bookmarks:''' If the application is launched from the browser, then include the application in Firefox bookmarks.
: (Todo: How do we do this?)

* '''wget''': When downloading large files using wget, use the "-c" continue command, as it will not re-download files if they already exist, and will continue if one is partially downloaded:
wget -c package.tar.gz
: Do not use -c if there is a chance the file of that name will change on the server. Add "<tt>--progress=dot:mega</tt>" to the wget command line if the file is at all large.
: Tiny files should use wget's -nv (non-verbose) flag.
: In a similar manner, use "<tt>--quiet</tt>" when calling '''qsql'''.

* '''mkdir''': Use -p (create parents too) option when creating a directory, as it doesn't complain about creating the directory a second time.
mkdir -p <dir>

* '''Binary files''': Do not put large (>5mb) binary files into the SVN repository without asking first. Due to SVN's preservation of history, once they are added they can never be removed, and forever-more clog up the backend database. Subversion is designed to be a ''source code management'' tool, not a data warehouse. There is space for large static data files (e.g. sample data) at http://download.osgeo.org/livedvd/data/. Just ask on the mailing list if you'd like to house something there.

= Packaging considerations =

The criteria used to select applications for the LiveGIS follow.

== Technical limitations ==
=== Space considerations ===
* DVD: approx 4.2gb compressed
* USB stick: For a 4gb persistent USB stick with some room left over for user-workspace, 3.2-3.5gb compressed. (This pretty much works out to the DVD version minus the preloaded Mac and Windows installers)
* Virtual Machines: theoretically unlimited, but in practice 20gb uncompressed

So smaller apps (<30mb) of lesser priority may easily slip in under the ire radar, but an external project that wants to use a 25% of the available disc space would be the first to be compromised away.

=== Memory considerations ===
Both Virtual Machines, and a LiveDVD images are likely to be constrained by limited memory. So to reduce memory usage. Disk image size is not of major concern, as we can just distribute less data.

The following principles should be followed.
* Do not start applications upon power up. (Ie, don't start deamons, allow users to start them instead).
* Set up examples which, by default, don't depend on other applications. Less applications open, means less memory. Ie, Have GeoServer access a shapefile instead of PostGIS.
* Try to avoid scenarios which write data to disk, as disk space in the Live DVD is stored in RAM, and is not cleared afterward.

File permissions and filesystem user IDs can get garbled during the ISO build process. Therefore a special method is used to ensure that data files which must be read-write can be accessed.

To install a writable data directory or files, change its group to "users" and set the file(s) as group-writable:

adduser $USER_NAME users
chmod -R g+w /usr/local/share/<packagename>/data/
chown -R root.users /usr/local/share/<packagename>/data/

and symlink into the user's home directory if necessary.

Setting files to have universal write permission is strongly discouraged. '''Do not use "''chmod 777 -R''".'''

=== Shared resources ===

The disc is a busy place, so we must all play nice and take care not step on each others toes.

==== Changes to the base system ====

Please don't customize any system level infrastructure which other projects may be relying on.
Often there is an /etc/$foo.d/ directory for you to put config additions into. Always put non-.deb packaged custom things in /usr/local not /usr!

==== Port numbers ====

To avoid overlaps and conflicts with other packages, please avoid putting web services on common port numbers like 8000 or 8080. Choose a random port between 8000 and 8080, search through the whole documentation for this port number (e.g. "grep -R 8042 doc bin") and only use this number if it isn't mentioned anywhere else. Then add your new port number to your quick guide so that others will find it.

Rasdaman is using ports 7001 (dispatcher), 7002, 7003, etc. (worker processes). The number of workers is fixed in the etc/rasmgr.conf file, at least one is required.

= Directory Structure =

# '''/tmp''' Temporary files (e.g., downloaded archives) go into /tmp. Please create a separate folder for your project.
# '''/usr/lib''' application are usually installed into /usr/lib
# '''/usr/bin''' things that get executed by the user such as startup scripts or links to them should go into /usr/bin
# '''/etc/init.d''' startup/shutdown scripts for services (e.g., postgres, apache, tomcat) are stored in /etc/init.d
# '''/usr/local/share''' sample data and documentation goes into /usr/local/share
# '''/etc''' config files are stored in /etc
# '''/home/user''' user specific config files or working directories can go into <tt>/home/user/</tt>. However, keep files in /home/user as small as possible as this folder is loaded into memory in the Live DVD. Symlinks into /usr/local can be useful here.

* ''You are strongly encouraged to use '''/usr/local/''' and '''/var/local/''' for storing non-packaged content.''

== .deb Packaging ==
Currently many packages are installed from bash scripts. The major release goal for the next versions of the Osgeo live DVD is to make sure that all programs can be installed from debian packages.

This offers many advantages: packages can be uninstalled and updated to newer versions without having to build the complete live dvd. This also makes testing more easy: one can just update to the last live dvd rather than having to install all software.
Ideally, applications should be packaged in [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] or [http://wiki.debian.org/DebianGis DebianGIS] repositories, or in a Launchpad PPA (e.g. available from the UbuntuGIS repository). This would mean that any ubuntu or debian user can profit from the packaging works for the osgeo live dvd.

Even though packaging can be overwhelming at first, it eventually boils down to creating a few files in a debian subdirectory from a place where the sources of your application are. A quick and easy way to generate a template is by running dh_make (from the dh-make package) in the directory where your sources are.
This will create the necessary files to build a package which you will have to edit before packaging for real.

Many tutorials exist on the web that can assist building debian packages, so I will not repeat all of them here.
https://wiki.debian.org/IntroDebianPackaging provides a good start.

If you are new to debian packaging probably the best you can do is ask on the mailing lists of [http://lists.osgeo.org/mailman/listinfo/ubuntu UbuntuGIS] or [https://lists.debian.org/debian-gis/ DebianGIS] whether someone can provide a template to start your own package.

=== Packaging Python ===

Instead of using "<tt>pip</tt>", "<tt>easy_install</tt>" or other Python installation methods it is prefered to install the <tt>''python-pkgname''</tt> package if it exists. By integrating the python libraries into the dpkg system-files database we can quickly find files and make sure that there are not two different versions from two different sources competing and conflicting. Fortunately it is very easy to create a .deb from projects on Pypi.

* First check that the software is not already on the disc with "dpkg -S ''name''" and "locate ''name''".

* If needed, install the packaging tools:
sudo apt-get install python-stdeb build-essential python-all-dev

* Run ''<tt>pypi-install</tt>'' to download, build, and install the .deb. For example:
sudo pypi-install Fiona

Add the "--keep" command line option to retain a copy of the .deb and .changes file in a subdirectory of /tmp, e.g. for upload to UbuntuGIS's repository.

See also [http://article.gmane.org/gmane.comp.gis.osgeo.livedemo/7466/ this mailing list thread] with further details on manually packaging using the same tools.

== Example Datasets ==
In order to reduce disk space, and to provide consistency between projects, we strongly encourage all projects to make use of the common datasets packaged on OSGeo-Live by the [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_gisdata.sh install_gisdata.sh] script.

All datasets should be installed into /usr/local/share/data, or if installed elsewhere, there should be a symbolic link into /usr/local/share/data. Data should not be installed in the /home/user directory, as I understand that data in the HOME directory is copied into RAM. (TBD find confirmation of this).

There is a symbolic link from /home/user/data to /usr/local/share/data to make it easy to find from a user's home directory. (Documentation should reference /home/user/data/... ).

Datasets are also available via http://localhost/data/ and http://live.osgeo.org/data/ (which is a symbolic link from /var/www/data to /usr/local/share/data).

=== Natural Earth ===
The [http://www.naturalearthdata.com/ Natural Earth] dataset is the preferred dataset for all examples.

* [http://www.naturalearthdata.com/downloads/10m-cultural-vectors/ 1:10m Simple Populated Places]. Shapefiles are in /user/data/natural_earth/* and have also been loaded into PostGIS.
** admin_0_countries
** admin_1_states_provinces
** geography_marine_polys
** geography_regions_elevated_points
** geography_regions_polys
** lakes
** land
** ocean
** populated_places_simple
** rivers_lake_centerlines
** urban_areas

* Raster basemap -- Cross Blended Hypso with Shaded Relief and Water 1:50 million, stored in /user/data/natural_earth/HYP_50M_SR_W/*

=== OpenStreetMap ===
OpenStreetMap data is loaded into /usr/local/share/data/osm/feature_city.osm

=== North Carolina ===
The [http://www.grassbook.org/data_menu3rd.php OSGeo-Geodata collection of geotiffs and shapefiles for Wake County] (North Carolina) has been tentatively added for the 5.0 release.

The [http://www.grassbook.org/ncexternal/nc_datalist.html North Carolina layers] can be found in /usr/local/share/data/north_carolina/ (symlinked to ~/data/north_carolina)

=== Others ===
If you need another type of data for your examples, please discuss this with us.

== Documentation ==
OSGeo-Live documentation is published at:
;On OSGeo-Live: http://localhost/ which is stored in /var/www/
;Stable release: http://live.osgeo.org
;Nightly build: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/index.html

=== Application Overview ===

The [[Marketing_Artefacts#Application_Overview|Application Overview]] is a one page marketing page targeted at a someone considering using GeoSpatial Open Source, who may be a GeoSpatial User, a Technical person without much geospatial expertise, or manager with limited GeoSpatial or technical experience. Published Overviews are linked from here: http://live.osgeo.org/en/overview/overview.html

The source Overviews are written in [http://sphinx.pocoo.org/rest.html RST wiki format] and built using sphinx. Source documents are to be stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/overview/en/<application>_overview.rst . They should follow the structure and style of the reference Overview, which has lots of helpful comments, at https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/overview/postgis_overview.rst

The Overviews are currently published as [http://live.osgeo.org/overview/overview.html HTML pages]. In future we intend to also create 1 page PDFs, (to hand out as a flier at conferences, and as a page in the OSGeo Book of projects), and as Word/OpenOffice (to be cut and pasted into project proposals and articles which usually use these formats).

Overviews also require:
* an image for the application, usually a screen shot or collage of screen shots, as per [[#Screen_Shot|Screen Shot]] ('''don't use GIF format, please use PNG instead''').
* A project logo as per [[#Logo]] ('''don't use GIF format, please use PNG instead''').

Try printing the html page from the browser, and ensure that the page is less than one page long. (The less words you write, the more people will read your documentation.)

Once finished, note your project's overview status="draft" in the OSGeo-Live project status at: http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB#gid=5 and email live-demo@lists.osgeo.org noting your documentation is ready for review. Once reviewed, the status is moved to "complete" and is ready for translation.

=== Application Quick Start ===
The [[Marketing_Artefacts#Application_Quick_Start|Application Quick Start]] defines detailed steps, with screen shots, for a new user to run one of the application's core functions. It should be able to be run in 5 to 10 minutes.

Try to make use of a friendly, conversational writing style, similar to the way a tutor would talk a class through an example. The quickstarts for [http://live.osgeo.org/en/quickstart/R_quickstart.html R] and [http://live.osgeo.org/en/quickstart/geoserver_quickstart.html GeoServer] do this very well.

Source documentation is written in [http://sphinx.pocoo.org/rest.html RST wiki format], is built using sphinx, and is stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/quickstart/<application>_quickstart.rst

The reference quickstart, which includes structure guidelines and with tips on how to fill in the quickstart is here:
https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/quickstart/udig_quickstart.rst
and is published here: http://live.osgeo.org/en/quickstart/udig_quickstart.html

In order to reduce disk space, and maintain consistency between applications, we request that all examples make use of the common [[#Example_Datasets]]. If the datasets don't cover your requirements, discuss this with us and we may add another suitable common dataset.

Applications are expected to include screen shots for each major step in the quickstart, as per [[#Screen_Shot|Screen Shot]].

Once finished, note your project's quickstart status="draft" in the OSGeo-Live project status at: http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB#gid=5 and email live-demo@lists.osgeo.org noting your documentation is ready for review. Once reviewed, the status is moved to "complete" and is ready for translation.

==== Quickstart Review Checklist ====

* Review latest Quickstart docs at: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/overview/overview.html
* Run with latest OSGeo-Live Development Release. Download from: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Downloads
* ''Before starting, notify others that you have started reviewing by setting "Quickstart reviewed by:" to "Started:<your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If you feel confident [http://wiki.osgeo.org/wiki/Live_GIS_Add_Project#Documentation updating the .rst documentation], then feel free to correct simple errors that you find, and commit back to subversion. (you will need [http://wiki.osgeo.org/wiki/Live_GIS_Disc#Subversion subversion access]).
* Otherwise, report problems in our [http://wiki.osgeo.org/wiki/Live_GIS_Disc#Issue_Tracker Issue Tracker] with keywords: ''docs 6.5 <application>'', component: ''LiveDVD'', milestone:

;Someone experienced with the project:
* Is the quickstart applicable for the version of the application installed on OSGeo-Live?
* If sample data is used, is it one of the OSGeo-Live datasets?
* Is there a screenshot for each step?
* Where appropriate, have screenshots been labeled (usually with numbers) to link them back to the documentation?
* ''Once finished, update Quickstart status to "6.5 Draft" and "Quickstart reviewed by:" to "osgeolive-version <your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If not already included, add the editor's name to the top of the .rst file:
:Author: Your Name
;QA Tester:
* Has the quickstart been run from start to finish?
* How long did the quickstart take to run? (Should be between 5 and 15 minutes)
* Has every step been explained in the quickstart?
* ''Once finished, update Quickstart status to "6.5 Reviewed" and "Quickstart reviewed by:" to "osgeolive-version <your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If not already included, add the testers name to the top of the .rst file:
:Reviewer: Your Name

;Reviewer for readability and consistency:
* Would the quickstart be understandable for a novice? Are all technical terms and acronyms explained?
* Is the language clear, and concise?
* Does the first paragraph explain what this Quickstart is going to cover?
* Are there steps for one scenario?
* Does the quickstart include "Things to try" and/or "What next" sections?
* ''Once finished, update Quickstart status to "6.5 Final" and "Quickstart reviewed by:" to "osgeolive-version <your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If not already included, add the reviewer's name to the top of the .rst file:
:Reviewer: Your Name

=== Logo ===
The Project's logo is used in the headers of documentation (like Project Overviews, QuickStarts, Powerpoint presentations etc, and as icons on the OSGeo-Live Desktop. Hence there are a few different requirements for the logo.

;Header logo:
:* Stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/images/project_logos
:* Filename should be "logo-<projectname>.png" (apparently PNG is required for PDF docs)
:* Should have a transparent background (not white)
:* Preferably stored in size 125x125 pixels (for use in Project Overview and QuickStarts)
:* For PNGs ''please'' run a program like [http://packages.ubuntu.com/pngcrush pngcrush] or [http://packages.ubuntu.com/optipng optipng] to reduce the size of the image without degrading quality. Here's an example using <tt>optipng</tt>:
optipng -o5 image.png
:* Preferably also available as SVG, stored as "logo-<projectname>.svg"

;Desktop logo:
:We are still to define the requirements for creating a desktop logo. They will likely include:
:* A 32x32-pixel XPM icon for use by the Debian menus
:* A 48x48-pixel PNG icon for use by freedesktop.org menus

=== Screen Shot ===
Project overviews include an image, which is usually a screen shot, or collage of screen shorts. Quickstarts include screen shots for each significant step.
* Screen shots can be taken using [http://shutter-project.org/ Shutter] (on linux) or [http://getgreenshot.org/ Greenshot] (on windows).
* Screen shots should be taken from a 1024x768 display, and should be created in PNG format. (Apparently PNG is required for PDF documentation.)
* Images are to be stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/images/screenshots/1024x768
* For Quickstarts, consider marking up the image to explain the current steps. Eg: Add circled numbers: 1, 2, 3 or draw an oval around buttons being described. This is very easy to do using the "Edit" tab in the Shutter program, which provides these drawing icons to add. Tutorials augmented with detailed and pertinent images make it easy for the reader to follow what is going on. Extra time spent on an image pays off big in comprehension (you need more than just a course screen dump). Lines, numbering, highlights, boxes and annotations all help direct a user's focus to those areas which are important.
* Screenshots with large areas of constant color (menus, etc.) should be in PNG format, screenshots containing large areas of imagery (satellite images, shaded relief DEMs, etc.) should be in JPEG format.
* For PNGs ''please'' run a program like [http://packages.ubuntu.com/pngcrush pngcrush] to reduce the size of the image without degrading quality.

=== Extra Documentation ===
Some projects link to extra documentation, stored as PDFs or similar, or alternatively provide example applications. These should be referenced in documentation via a relative link such than it can viewed from:
http://localhost/<application>/... or http://live.osgeo.org/<application>/...

This should typically be achieved by creating a symbolic link from /var/www/<application> to /usr/local/share/doc/<application>

== Publishing Documentation ==

The following web service is useful for checking [http://docutils.sourceforge.net/rst.html reST] formatting: http://rst.ninjs.org/

For a more comprehensive test, set up the reST processor, sphinx:
: (''you will have to have [http://sphinx.pocoo.org/ Sphinx 0.6.4 or greater] installed, it's in the'' <tt>python-sphinx</tt> ''Debian package'')

sudo apt-get install python-sphinx

cd osgeo/livedvd/gisvm/trunk/doc/
make html

You can then view the results in:
osgeo/livedvd/gisvm/trunk/doc/_build/*.html

= Translations =
For details on how to translate, refer to [[Live GIS Translate]]

[[Category: Live-demo]]

Live GIS Add Project

2014-05-10T08:30:52Z

Wiki-HamishBowman: /* .deb Packaging */ pypkg

== What gets into OSGeoLive? ==

We have an emphasis of quality, and we are space constrained on OSGeoLive and so are selective about what is included.

Priority for selecting OSGeoLive projects to package is:
# OSGeo Projects
# OSGeo Projects in incubation
# Stable GeoSpatial Open Source Software being presented in workshops, tutorials, or presentations at FOSS4G
# Other Stable GeoSpatial Open Source Software with established project communities and a wide user base
# It will be ready for the next release in accordance with our [https://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdE1SYUN3YWJ2N1NpSUczbW9IRWZNclE&hl=en_GB schedule]

== Application Questions ==

Projects need to provide:
* Project Champion
: Someone who will liaise between the OSGeoLive team and the project and ensures the application remains up to date on OSGeoLive.
* A base [[#Install_Script]] for installing onto an Ubuntu Linux based system.
* [[#Documentation]] in line with OSGeoLive templates
* Someone who will run and verify the applications works in development releases
* [http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB Project Status] to be maintained.

If you think you can cover all these criteria for your project, then send an email to the [http://lists.osgeo.org/mailman/listinfo/live-demo OSGeoLive email list] asking if your project is appropriate. When emailing the list, please address the questions in the [[Live_GIS_Disc_Apply]] form.

== Which version to use? ==

* Stable, always! LiveGIS users are usually seeing OSGeo newbies and will be turned off by any software bugs.

== Install Script ==
Each project is to write a shell script which installs and configures your stable application into the OSGeoLive Xubuntu.

All install scripts for building the LiveGIS disc shall be licensed as LGPL.

When finished, ask the OSGeoLive team to reference your script from ''main.sh''.

Scripts are stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/

The script may be as simple as:
[https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_mapserver.sh install_mapserver.sh], which just
apt-get install mapserver

Projects that haven't been packaged for Ubuntu yet are slightly more complicated:

The uDig package is a good example: [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_udig.sh install_udig.sh]

* 3rd Party Repositories: Create an <app>.list file with your repository in sources.list.d/ in the svn, in your script copy the file to the local machine like
cp -f ../sources.list/ubuntugis.list /etc/apt/sources.list.d/

don't forget to add the repository key like so
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 68436DDF

== Packaging conventions ==

* '''sudo''': Assume the script is to be executed as root. This means that sudo is only needed if you need to execute a command as e.g. the database user.
: This means that ~/ refers to the directory /home/root/, so you should use ~user/ to reference /home/user/.
: Preferred method is to put the <tt>USER_NAME</tt> and <tt>USER_HOME</tt> variables at the top, so these can be easily changed in all scripts if needed.
USER_NAME="user"
USER_HOME="/home/$USER_NAME"
cp package_readme.txt "$USER_HOME"

* '''Called twice''': Assume that the script will be executed multiple times, (as people may re-run the install process to get it right).
: Make sure that nothing is corrupted if the script runs a second time.

* '''No Prompts''': Try not to have any interactive steps which prompt the user for an answer, as we want the scripts to be run automatically. In particular, try running the script a second time, and see if you get prompted to overwrite files.

* '''/tmp''': Copy all downloads into /tmp/build_<package>/
: Don't delete the /tmp/build_<package> directory afterwards. If the script is re-run, then time and bandwidth is saved by not having to download large files again. Do not do code checkouts or place temporary files in the starting build directory, which is ./bin/ in the live disc's SVN tree. See the "BUILD_DIR" environment variable used in a number of scripts if you later have to refer back to the ../app-conf/ or ../app-data/ relative paths in the live disc's SVN tree.

* '''Icons''': Where appropriate, create an icon on the desktop which loads the application. The file should be called <packagename>.desktop and placed in /home/user/Desktop/ for further processing. The icons will be sorted and the Geospatial menu will be auto-generated from here.
: Install <packagename>.png icon files to the /usr/share/icons/ directory.
: see <tt>install_qgis.sh</tt> for an example

* '''Browser bookmarks:''' If the application is launched from the browser, then include the application in Firefox bookmarks.
: (Todo: How do we do this?)

* '''wget''': When downloading large files using wget, use the "-c" continue command, as it will not re-download files if they already exist, and will continue if one is partially downloaded:
wget -c package.tar.gz
: Do not use -c if there is a chance the file of that name will change on the server. Add "<tt>--progress=dot:mega</tt>" to the wget command line if the file is at all large.
: Tiny files should use wget's -nv (non-verbose) flag.
: In a similar manner, use "<tt>--quiet</tt>" when calling '''qsql'''.

* '''mkdir''': Use -p (create parents too) option when creating a directory, as it doesn't complain about creating the directory a second time.
mkdir -p <dir>

* '''Binary files''': Do not put large (>5mb) binary files into the SVN repository without asking first. Due to SVN's preservation of history, once they are added they can never be removed, and forever-more clog up the backend database. Subversion is designed to be a ''source code management'' tool, not a data warehouse. There is space for large static data files (e.g. sample data) at http://download.osgeo.org/livedvd/data/. Just ask on the mailing list if you'd like to house something there.

= Packaging considerations =

The criteria used to select applications for the LiveGIS follow.

== Technical limitations ==
=== Space considerations ===
* DVD: approx 4.2gb compressed
* USB stick: For a 4gb persistent USB stick with some room left over for user-workspace, 3.2-3.5gb compressed. (This pretty much works out to the DVD version minus the preloaded Mac and Windows installers)
* Virtual Machines: theoretically unlimited, but in practice 20gb uncompressed

So smaller apps (<30mb) of lesser priority may easily slip in under the ire radar, but an external project that wants to use a 25% of the available disc space would be the first to be compromised away.

=== Memory considerations ===
Both Virtual Machines, and a LiveDVD images are likely to be constrained by limited memory. So to reduce memory usage. Disk image size is not of major concern, as we can just distribute less data.

The following principles should be followed.
* Do not start applications upon power up. (Ie, don't start deamons, allow users to start them instead).
* Set up examples which, by default, don't depend on other applications. Less applications open, means less memory. Ie, Have GeoServer access a shapefile instead of PostGIS.
* Try to avoid scenarios which write data to disk, as disk space in the Live DVD is stored in RAM, and is not cleared afterward.

File permissions and filesystem user IDs can get garbled during the ISO build process. Therefore a special method is used to ensure that data files which must be read-write can be accessed.

To install a writable data directory or files, change its group to "users" and set the file(s) as group-writable:

adduser $USER_NAME users
chmod -R g+w /usr/local/share/<packagename>/data/
chown -R root.users /usr/local/share/<packagename>/data/

and symlink into the user's home directory if necessary.

Setting files to have universal write permission is strongly discouraged. '''Do not use "''chmod 777 -R''".'''

=== Shared resources ===

The disc is a busy place, so we must all play nice and take care not step on each others toes.

==== Changes to the base system ====

Please don't customize any system level infrastructure which other projects may be relying on.
Often there is an /etc/$foo.d/ directory for you to put config additions into. Always put non-.deb packaged custom things in /usr/local not /usr!

==== Port numbers ====

To avoid overlaps and conflicts with other packages, please avoid putting web services on common port numbers like 8000 or 8080. Choose a random port between 8000 and 8080, search through the whole documentation for this port number (e.g. "grep -R 8042 doc bin") and only use this number if it isn't mentioned anywhere else. Then add your new port number to your quick guide so that others will find it.

Rasdaman is using ports 7001 (dispatcher), 7002, 7003, etc. (worker processes). The number of workers is fixed in the etc/rasmgr.conf file, at least one is required.

= Directory Structure =

# '''/tmp''' Temporary files (e.g., downloaded archives) go into /tmp. Please create a separate folder for your project.
# '''/usr/lib''' application are usually installed into /usr/lib
# '''/usr/bin''' things that get executed by the user such as startup scripts or links to them should go into /usr/bin
# '''/etc/init.d''' startup/shutdown scripts for services (e.g., postgres, apache, tomcat) are stored in /etc/init.d
# '''/usr/local/share''' sample data and documentation goes into /usr/local/share
# '''/etc''' config files are stored in /etc
# '''/home/user''' user specific config files or working directories can go into <tt>/home/user/</tt>. However, keep files in /home/user as small as possible as this folder is loaded into memory in the Live DVD. Symlinks into /usr/local can be useful here.

* ''You are strongly encouraged to use '''/usr/local/''' and '''/var/local/''' for storing non-packaged content.''

== .deb Packaging ==
Currently many packages are installed from bash scripts. The major release goal for the next versions of the Osgeo live DVD is to make sure that all programs can be installed from debian packages.

This offers many advantages: packages can be uninstalled and updated to newer versions without having to build the complete live dvd. This also makes testing more easy: one can just update to the last live dvd rather than having to install all software.
Ideally, applications should be packaged in [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] or [http://wiki.debian.org/DebianGis DebianGIS] repositories, or in a Launchpad PPA (e.g. available from the UbuntuGIS repository). This would mean that any ubuntu or debian user can profit from the packaging works for the osgeo live dvd.

Even though packaging can be overwhelming at first, it eventually boils down to creating a few files in a debian subdirectory from a place where the sources of your application are. A quick and easy way to generate a template is by running dh_make (from the dh-make package) in the directory where your sources are.
This will create the necessary files to build a package which you will have to edit before packaging for real.

Many tutorials exist on the web that can assist building debian packages, so I will not repeat all of them here.
https://wiki.debian.org/IntroDebianPackaging provides a good start.

If you are new to debian packaging probably the best you can do is ask on the mailing lists of [http://lists.osgeo.org/mailman/listinfo/ubuntu UbuntuGIS] or [https://lists.debian.org/debian-gis/ DebianGIS] whether someone can provide a template to start your own package.

=== Packaging Python ===

Instead of using "<tt>pip</tt>" or other Python installation methods it is prefered to install the <tt>python-pkgname</tt> package if it exists. By integrating the python libraries into the dpkg system-files database we can quickly find files and make sure that there are not two different versions from two different sources competing and conflicting. Fortunately it is very easy to create a .deb from projects on Pypi.

* First check that the software is not already on the disc with "dpkg -S name" and "locate name".

* If needed, install the packaging tools:
sudo apt-get install python-stdeb build-essential python-all-dev

* Run <tt>pypi-install</tt> to download, build, and install the .deb. For example:
sudo pypi-install Fiona

Add the "--keep" command line option to retain a copy of the .deb and .changes file in a subdirectory of /tmp, e.g. for upload to UbuntuGIS's repository.

== Example Datasets ==
In order to reduce disk space, and to provide consistency between projects, we strongly encourage all projects to make use of the common datasets packaged on OSGeo-Live by the [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_gisdata.sh install_gisdata.sh] script.

All datasets should be installed into /usr/local/share/data, or if installed elsewhere, there should be a symbolic link into /usr/local/share/data. Data should not be installed in the /home/user directory, as I understand that data in the HOME directory is copied into RAM. (TBD find confirmation of this).

There is a symbolic link from /home/user/data to /usr/local/share/data to make it easy to find from a user's home directory. (Documentation should reference /home/user/data/... ).

Datasets are also available via http://localhost/data/ and http://live.osgeo.org/data/ (which is a symbolic link from /var/www/data to /usr/local/share/data).

=== Natural Earth ===
The [http://www.naturalearthdata.com/ Natural Earth] dataset is the preferred dataset for all examples.

* [http://www.naturalearthdata.com/downloads/10m-cultural-vectors/ 1:10m Simple Populated Places]. Shapefiles are in /user/data/natural_earth/* and have also been loaded into PostGIS.
** admin_0_countries
** admin_1_states_provinces
** geography_marine_polys
** geography_regions_elevated_points
** geography_regions_polys
** lakes
** land
** ocean
** populated_places_simple
** rivers_lake_centerlines
** urban_areas

* Raster basemap -- Cross Blended Hypso with Shaded Relief and Water 1:50 million, stored in /user/data/natural_earth/HYP_50M_SR_W/*

=== OpenStreetMap ===
OpenStreetMap data is loaded into /usr/local/share/data/osm/feature_city.osm

=== North Carolina ===
The [http://www.grassbook.org/data_menu3rd.php OSGeo-Geodata collection of geotiffs and shapefiles for Wake County] (North Carolina) has been tentatively added for the 5.0 release.

The [http://www.grassbook.org/ncexternal/nc_datalist.html North Carolina layers] can be found in /usr/local/share/data/north_carolina/ (symlinked to ~/data/north_carolina)

=== Others ===
If you need another type of data for your examples, please discuss this with us.

== Documentation ==
OSGeo-Live documentation is published at:
;On OSGeo-Live: http://localhost/ which is stored in /var/www/
;Stable release: http://live.osgeo.org
;Nightly build: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/index.html

=== Application Overview ===

The [[Marketing_Artefacts#Application_Overview|Application Overview]] is a one page marketing page targeted at a someone considering using GeoSpatial Open Source, who may be a GeoSpatial User, a Technical person without much geospatial expertise, or manager with limited GeoSpatial or technical experience. Published Overviews are linked from here: http://live.osgeo.org/en/overview/overview.html

The source Overviews are written in [http://sphinx.pocoo.org/rest.html RST wiki format] and built using sphinx. Source documents are to be stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/overview/en/<application>_overview.rst . They should follow the structure and style of the reference Overview, which has lots of helpful comments, at https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/overview/postgis_overview.rst

The Overviews are currently published as [http://live.osgeo.org/overview/overview.html HTML pages]. In future we intend to also create 1 page PDFs, (to hand out as a flier at conferences, and as a page in the OSGeo Book of projects), and as Word/OpenOffice (to be cut and pasted into project proposals and articles which usually use these formats).

Overviews also require:
* an image for the application, usually a screen shot or collage of screen shots, as per [[#Screen_Shot|Screen Shot]] ('''don't use GIF format, please use PNG instead''').
* A project logo as per [[#Logo]] ('''don't use GIF format, please use PNG instead''').

Try printing the html page from the browser, and ensure that the page is less than one page long. (The less words you write, the more people will read your documentation.)

Once finished, note your project's overview status="draft" in the OSGeo-Live project status at: http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB#gid=5 and email live-demo@lists.osgeo.org noting your documentation is ready for review. Once reviewed, the status is moved to "complete" and is ready for translation.

=== Application Quick Start ===
The [[Marketing_Artefacts#Application_Quick_Start|Application Quick Start]] defines detailed steps, with screen shots, for a new user to run one of the application's core functions. It should be able to be run in 5 to 10 minutes.

Try to make use of a friendly, conversational writing style, similar to the way a tutor would talk a class through an example. The quickstarts for [http://live.osgeo.org/en/quickstart/R_quickstart.html R] and [http://live.osgeo.org/en/quickstart/geoserver_quickstart.html GeoServer] do this very well.

Source documentation is written in [http://sphinx.pocoo.org/rest.html RST wiki format], is built using sphinx, and is stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/quickstart/<application>_quickstart.rst

The reference quickstart, which includes structure guidelines and with tips on how to fill in the quickstart is here:
https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/quickstart/udig_quickstart.rst
and is published here: http://live.osgeo.org/en/quickstart/udig_quickstart.html

In order to reduce disk space, and maintain consistency between applications, we request that all examples make use of the common [[#Example_Datasets]]. If the datasets don't cover your requirements, discuss this with us and we may add another suitable common dataset.

Applications are expected to include screen shots for each major step in the quickstart, as per [[#Screen_Shot|Screen Shot]].

Once finished, note your project's quickstart status="draft" in the OSGeo-Live project status at: http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB#gid=5 and email live-demo@lists.osgeo.org noting your documentation is ready for review. Once reviewed, the status is moved to "complete" and is ready for translation.

==== Quickstart Review Checklist ====

* Review latest Quickstart docs at: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/overview/overview.html
* Run with latest OSGeo-Live Development Release. Download from: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Downloads
* ''Before starting, notify others that you have started reviewing by setting "Quickstart reviewed by:" to "Started:<your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If you feel confident [http://wiki.osgeo.org/wiki/Live_GIS_Add_Project#Documentation updating the .rst documentation], then feel free to correct simple errors that you find, and commit back to subversion. (you will need [http://wiki.osgeo.org/wiki/Live_GIS_Disc#Subversion subversion access]).
* Otherwise, report problems in our [http://wiki.osgeo.org/wiki/Live_GIS_Disc#Issue_Tracker Issue Tracker] with keywords: ''docs 6.5 <application>'', component: ''LiveDVD'', milestone:

;Someone experienced with the project:
* Is the quickstart applicable for the version of the application installed on OSGeo-Live?
* If sample data is used, is it one of the OSGeo-Live datasets?
* Is there a screenshot for each step?
* Where appropriate, have screenshots been labeled (usually with numbers) to link them back to the documentation?
* ''Once finished, update Quickstart status to "6.5 Draft" and "Quickstart reviewed by:" to "osgeolive-version <your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If not already included, add the editor's name to the top of the .rst file:
:Author: Your Name
;QA Tester:
* Has the quickstart been run from start to finish?
* How long did the quickstart take to run? (Should be between 5 and 15 minutes)
* Has every step been explained in the quickstart?
* ''Once finished, update Quickstart status to "6.5 Reviewed" and "Quickstart reviewed by:" to "osgeolive-version <your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If not already included, add the testers name to the top of the .rst file:
:Reviewer: Your Name

;Reviewer for readability and consistency:
* Would the quickstart be understandable for a novice? Are all technical terms and acronyms explained?
* Is the language clear, and concise?
* Does the first paragraph explain what this Quickstart is going to cover?
* Are there steps for one scenario?
* Does the quickstart include "Things to try" and/or "What next" sections?
* ''Once finished, update Quickstart status to "6.5 Final" and "Quickstart reviewed by:" to "osgeolive-version <your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If not already included, add the reviewer's name to the top of the .rst file:
:Reviewer: Your Name

=== Logo ===
The Project's logo is used in the headers of documentation (like Project Overviews, QuickStarts, Powerpoint presentations etc, and as icons on the OSGeo-Live Desktop. Hence there are a few different requirements for the logo.

;Header logo:
:* Stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/images/project_logos
:* Filename should be "logo-<projectname>.png" (apparently PNG is required for PDF docs)
:* Should have a transparent background (not white)
:* Preferably stored in size 125x125 pixels (for use in Project Overview and QuickStarts)
:* For PNGs ''please'' run a program like [http://packages.ubuntu.com/pngcrush pngcrush] or [http://packages.ubuntu.com/optipng optipng] to reduce the size of the image without degrading quality. Here's an example using <tt>optipng</tt>:
optipng -o5 image.png
:* Preferably also available as SVG, stored as "logo-<projectname>.svg"

;Desktop logo:
:We are still to define the requirements for creating a desktop logo. They will likely include:
:* A 32x32-pixel XPM icon for use by the Debian menus
:* A 48x48-pixel PNG icon for use by freedesktop.org menus

=== Screen Shot ===
Project overviews include an image, which is usually a screen shot, or collage of screen shorts. Quickstarts include screen shots for each significant step.
* Screen shots can be taken using [http://shutter-project.org/ Shutter] (on linux) or [http://getgreenshot.org/ Greenshot] (on windows).
* Screen shots should be taken from a 1024x768 display, and should be created in PNG format. (Apparently PNG is required for PDF documentation.)
* Images are to be stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/images/screenshots/1024x768
* For Quickstarts, consider marking up the image to explain the current steps. Eg: Add circled numbers: 1, 2, 3 or draw an oval around buttons being described. This is very easy to do using the "Edit" tab in the Shutter program, which provides these drawing icons to add. Tutorials augmented with detailed and pertinent images make it easy for the reader to follow what is going on. Extra time spent on an image pays off big in comprehension (you need more than just a course screen dump). Lines, numbering, highlights, boxes and annotations all help direct a user's focus to those areas which are important.
* Screenshots with large areas of constant color (menus, etc.) should be in PNG format, screenshots containing large areas of imagery (satellite images, shaded relief DEMs, etc.) should be in JPEG format.
* For PNGs ''please'' run a program like [http://packages.ubuntu.com/pngcrush pngcrush] to reduce the size of the image without degrading quality.

=== Extra Documentation ===
Some projects link to extra documentation, stored as PDFs or similar, or alternatively provide example applications. These should be referenced in documentation via a relative link such than it can viewed from:
http://localhost/<application>/... or http://live.osgeo.org/<application>/...

This should typically be achieved by creating a symbolic link from /var/www/<application> to /usr/local/share/doc/<application>

== Publishing Documentation ==

The following web service is useful for checking [http://docutils.sourceforge.net/rst.html reST] formatting: http://rst.ninjs.org/

For a more comprehensive test, set up the reST processor, sphinx:
: (''you will have to have [http://sphinx.pocoo.org/ Sphinx 0.6.4 or greater] installed, it's in the'' <tt>python-sphinx</tt> ''Debian package'')

sudo apt-get install python-sphinx

cd osgeo/livedvd/gisvm/trunk/doc/
make html

You can then view the results in:
osgeo/livedvd/gisvm/trunk/doc/_build/*.html

= Translations =
For details on how to translate, refer to [[Live GIS Translate]]

[[Category: Live-demo]]

Live GIS Add Project

2014-05-10T02:40:28Z

Wiki-HamishBowman: /* .deb Packaging */ wiki link fix

== What gets into OSGeoLive? ==

We have an emphasis of quality, and we are space constrained on OSGeoLive and so are selective about what is included.

Priority for selecting OSGeoLive projects to package is:
# OSGeo Projects
# OSGeo Projects in incubation
# Stable GeoSpatial Open Source Software being presented in workshops, tutorials, or presentations at FOSS4G
# Other Stable GeoSpatial Open Source Software with established project communities and a wide user base
# It will be ready for the next release in accordance with our [https://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdE1SYUN3YWJ2N1NpSUczbW9IRWZNclE&hl=en_GB schedule]

== Application Questions ==

Projects need to provide:
* Project Champion
: Someone who will liaise between the OSGeoLive team and the project and ensures the application remains up to date on OSGeoLive.
* A base [[#Install_Script]] for installing onto an Ubuntu Linux based system.
* [[#Documentation]] in line with OSGeoLive templates
* Someone who will run and verify the applications works in development releases
* [http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB Project Status] to be maintained.

If you think you can cover all these criteria for your project, then send an email to the [http://lists.osgeo.org/mailman/listinfo/live-demo OSGeoLive email list] asking if your project is appropriate. When emailing the list, please address the questions in the [[Live_GIS_Disc_Apply]] form.

== Which version to use? ==

* Stable, always! LiveGIS users are usually seeing OSGeo newbies and will be turned off by any software bugs.

== Install Script ==
Each project is to write a shell script which installs and configures your stable application into the OSGeoLive Xubuntu.

All install scripts for building the LiveGIS disc shall be licensed as LGPL.

When finished, ask the OSGeoLive team to reference your script from ''main.sh''.

Scripts are stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/

The script may be as simple as:
[https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_mapserver.sh install_mapserver.sh], which just
apt-get install mapserver

Projects that haven't been packaged for Ubuntu yet are slightly more complicated:

The uDig package is a good example: [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_udig.sh install_udig.sh]

* 3rd Party Repositories: Create an <app>.list file with your repository in sources.list.d/ in the svn, in your script copy the file to the local machine like
cp -f ../sources.list/ubuntugis.list /etc/apt/sources.list.d/

don't forget to add the repository key like so
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 68436DDF

== Packaging conventions ==

* '''sudo''': Assume the script is to be executed as root. This means that sudo is only needed if you need to execute a command as e.g. the database user.
: This means that ~/ refers to the directory /home/root/, so you should use ~user/ to reference /home/user/.
: Preferred method is to put the <tt>USER_NAME</tt> and <tt>USER_HOME</tt> variables at the top, so these can be easily changed in all scripts if needed.
USER_NAME="user"
USER_HOME="/home/$USER_NAME"
cp package_readme.txt "$USER_HOME"

* '''Called twice''': Assume that the script will be executed multiple times, (as people may re-run the install process to get it right).
: Make sure that nothing is corrupted if the script runs a second time.

* '''No Prompts''': Try not to have any interactive steps which prompt the user for an answer, as we want the scripts to be run automatically. In particular, try running the script a second time, and see if you get prompted to overwrite files.

* '''/tmp''': Copy all downloads into /tmp/build_<package>/
: Don't delete the /tmp/build_<package> directory afterwards. If the script is re-run, then time and bandwidth is saved by not having to download large files again. Do not do code checkouts or place temporary files in the starting build directory, which is ./bin/ in the live disc's SVN tree. See the "BUILD_DIR" environment variable used in a number of scripts if you later have to refer back to the ../app-conf/ or ../app-data/ relative paths in the live disc's SVN tree.

* '''Icons''': Where appropriate, create an icon on the desktop which loads the application. The file should be called <packagename>.desktop and placed in /home/user/Desktop/ for further processing. The icons will be sorted and the Geospatial menu will be auto-generated from here.
: Install <packagename>.png icon files to the /usr/share/icons/ directory.
: see <tt>install_qgis.sh</tt> for an example

* '''Browser bookmarks:''' If the application is launched from the browser, then include the application in Firefox bookmarks.
: (Todo: How do we do this?)

* '''wget''': When downloading large files using wget, use the "-c" continue command, as it will not re-download files if they already exist, and will continue if one is partially downloaded:
wget -c package.tar.gz
: Do not use -c if there is a chance the file of that name will change on the server. Add "<tt>--progress=dot:mega</tt>" to the wget command line if the file is at all large.
: Tiny files should use wget's -nv (non-verbose) flag.
: In a similar manner, use "<tt>--quiet</tt>" when calling '''qsql'''.

* '''mkdir''': Use -p (create parents too) option when creating a directory, as it doesn't complain about creating the directory a second time.
mkdir -p <dir>

* '''Binary files''': Do not put large (>5mb) binary files into the SVN repository without asking first. Due to SVN's preservation of history, once they are added they can never be removed, and forever-more clog up the backend database. Subversion is designed to be a ''source code management'' tool, not a data warehouse. There is space for large static data files (e.g. sample data) at http://download.osgeo.org/livedvd/data/. Just ask on the mailing list if you'd like to house something there.

= Packaging considerations =

The criteria used to select applications for the LiveGIS follow.

== Technical limitations ==
=== Space considerations ===
* DVD: approx 4.2gb compressed
* USB stick: For a 4gb persistent USB stick with some room left over for user-workspace, 3.2-3.5gb compressed. (This pretty much works out to the DVD version minus the preloaded Mac and Windows installers)
* Virtual Machines: theoretically unlimited, but in practice 20gb uncompressed

So smaller apps (<30mb) of lesser priority may easily slip in under the ire radar, but an external project that wants to use a 25% of the available disc space would be the first to be compromised away.

=== Memory considerations ===
Both Virtual Machines, and a LiveDVD images are likely to be constrained by limited memory. So to reduce memory usage. Disk image size is not of major concern, as we can just distribute less data.

The following principles should be followed.
* Do not start applications upon power up. (Ie, don't start deamons, allow users to start them instead).
* Set up examples which, by default, don't depend on other applications. Less applications open, means less memory. Ie, Have GeoServer access a shapefile instead of PostGIS.
* Try to avoid scenarios which write data to disk, as disk space in the Live DVD is stored in RAM, and is not cleared afterward.

File permissions and filesystem user IDs can get garbled during the ISO build process. Therefore a special method is used to ensure that data files which must be read-write can be accessed.

To install a writable data directory or files, change its group to "users" and set the file(s) as group-writable:

adduser $USER_NAME users
chmod -R g+w /usr/local/share/<packagename>/data/
chown -R root.users /usr/local/share/<packagename>/data/

and symlink into the user's home directory if necessary.

Setting files to have universal write permission is strongly discouraged. '''Do not use "''chmod 777 -R''".'''

=== Shared resources ===

The disc is a busy place, so we must all play nice and take care not step on each others toes.

==== Changes to the base system ====

Please don't customize any system level infrastructure which other projects may be relying on.
Often there is an /etc/$foo.d/ directory for you to put config additions into. Always put non-.deb packaged custom things in /usr/local not /usr!

==== Port numbers ====

To avoid overlaps and conflicts with other packages, please avoid putting web services on common port numbers like 8000 or 8080. Choose a random port between 8000 and 8080, search through the whole documentation for this port number (e.g. "grep -R 8042 doc bin") and only use this number if it isn't mentioned anywhere else. Then add your new port number to your quick guide so that others will find it.

Rasdaman is using ports 7001 (dispatcher), 7002, 7003, etc. (worker processes). The number of workers is fixed in the etc/rasmgr.conf file, at least one is required.

= Directory Structure =

# '''/tmp''' Temporary files (e.g., downloaded archives) go into /tmp. Please create a separate folder for your project.
# '''/usr/lib''' application are usually installed into /usr/lib
# '''/usr/bin''' things that get executed by the user such as startup scripts or links to them should go into /usr/bin
# '''/etc/init.d''' startup/shutdown scripts for services (e.g., postgres, apache, tomcat) are stored in /etc/init.d
# '''/usr/local/share''' sample data and documentation goes into /usr/local/share
# '''/etc''' config files are stored in /etc
# '''/home/user''' user specific config files or working directories can go into <tt>/home/user/</tt>. However, keep files in /home/user as small as possible as this folder is loaded into memory in the Live DVD. Symlinks into /usr/local can be useful here.

* ''You are strongly encouraged to use '''/usr/local/''' and '''/var/local/''' for storing non-packaged content.''

== .deb Packaging ==
Currently many packages are installed from bash scripts. The major release goal for the next versions of the Osgeo live DVD is to make sure that all programs can be installed from debian packages.

This offers many advantages: packages can be uninstalled and updated to newer versions without having to build the complete live dvd. This also makes testing more easy: one can just update to the last live dvd rather than having to install all software.
Ideally, applications should be packaged in [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] or [http://wiki.debian.org/DebianGis DebianGIS] repositories, or in a Launchpad PPA (e.g. available from the UbuntuGIS repository). This would mean that any ubuntu or debian user can profit from the packaging works for the osgeo live dvd.

Even though packaging can be overwhelming at first, it eventually boils down to creating a few files in a debian subdirectory from a place where the sources of your application are. A quick and easy way to generate a template is by running dh_make (from the dh-make package) in the directory where your sources are.
This will create the necessary files to build a package which you will have to edit before packaging for real.

Many tutorials exist on the web that can assist building debian packages, so I will not repeat all of them here.
https://wiki.debian.org/IntroDebianPackaging provides a good start.

If you are new to debian packaging probably the best you can do is ask on the mailing lists of [http://lists.osgeo.org/mailman/listinfo/ubuntu UbuntuGIS] or [https://lists.debian.org/debian-gis/ DebianGIS] whether someone can provide a template to start your own package.

== Example Datasets ==
In order to reduce disk space, and to provide consistency between projects, we strongly encourage all projects to make use of the common datasets packaged on OSGeo-Live by the [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_gisdata.sh install_gisdata.sh] script.

All datasets should be installed into /usr/local/share/data, or if installed elsewhere, there should be a symbolic link into /usr/local/share/data. Data should not be installed in the /home/user directory, as I understand that data in the HOME directory is copied into RAM. (TBD find confirmation of this).

There is a symbolic link from /home/user/data to /usr/local/share/data to make it easy to find from a user's home directory. (Documentation should reference /home/user/data/... ).

Datasets are also available via http://localhost/data/ and http://live.osgeo.org/data/ (which is a symbolic link from /var/www/data to /usr/local/share/data).

=== Natural Earth ===
The [http://www.naturalearthdata.com/ Natural Earth] dataset is the preferred dataset for all examples.

* [http://www.naturalearthdata.com/downloads/10m-cultural-vectors/ 1:10m Simple Populated Places]. Shapefiles are in /user/data/natural_earth/* and have also been loaded into PostGIS.
** admin_0_countries
** admin_1_states_provinces
** geography_marine_polys
** geography_regions_elevated_points
** geography_regions_polys
** lakes
** land
** ocean
** populated_places_simple
** rivers_lake_centerlines
** urban_areas

* Raster basemap -- Cross Blended Hypso with Shaded Relief and Water 1:50 million, stored in /user/data/natural_earth/HYP_50M_SR_W/*

=== OpenStreetMap ===
OpenStreetMap data is loaded into /usr/local/share/data/osm/feature_city.osm

=== North Carolina ===
The [http://www.grassbook.org/data_menu3rd.php OSGeo-Geodata collection of geotiffs and shapefiles for Wake County] (North Carolina) has been tentatively added for the 5.0 release.

The [http://www.grassbook.org/ncexternal/nc_datalist.html North Carolina layers] can be found in /usr/local/share/data/north_carolina/ (symlinked to ~/data/north_carolina)

=== Others ===
If you need another type of data for your examples, please discuss this with us.

== Documentation ==
OSGeo-Live documentation is published at:
;On OSGeo-Live: http://localhost/ which is stored in /var/www/
;Stable release: http://live.osgeo.org
;Nightly build: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/index.html

=== Application Overview ===

The [[Marketing_Artefacts#Application_Overview|Application Overview]] is a one page marketing page targeted at a someone considering using GeoSpatial Open Source, who may be a GeoSpatial User, a Technical person without much geospatial expertise, or manager with limited GeoSpatial or technical experience. Published Overviews are linked from here: http://live.osgeo.org/en/overview/overview.html

The source Overviews are written in [http://sphinx.pocoo.org/rest.html RST wiki format] and built using sphinx. Source documents are to be stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/overview/en/<application>_overview.rst . They should follow the structure and style of the reference Overview, which has lots of helpful comments, at https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/overview/postgis_overview.rst

The Overviews are currently published as [http://live.osgeo.org/overview/overview.html HTML pages]. In future we intend to also create 1 page PDFs, (to hand out as a flier at conferences, and as a page in the OSGeo Book of projects), and as Word/OpenOffice (to be cut and pasted into project proposals and articles which usually use these formats).

Overviews also require:
* an image for the application, usually a screen shot or collage of screen shots, as per [[#Screen_Shot|Screen Shot]] ('''don't use GIF format, please use PNG instead''').
* A project logo as per [[#Logo]] ('''don't use GIF format, please use PNG instead''').

Try printing the html page from the browser, and ensure that the page is less than one page long. (The less words you write, the more people will read your documentation.)

Once finished, note your project's overview status="draft" in the OSGeo-Live project status at: http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB#gid=5 and email live-demo@lists.osgeo.org noting your documentation is ready for review. Once reviewed, the status is moved to "complete" and is ready for translation.

=== Application Quick Start ===
The [[Marketing_Artefacts#Application_Quick_Start|Application Quick Start]] defines detailed steps, with screen shots, for a new user to run one of the application's core functions. It should be able to be run in 5 to 10 minutes.

Try to make use of a friendly, conversational writing style, similar to the way a tutor would talk a class through an example. The quickstarts for [http://live.osgeo.org/en/quickstart/R_quickstart.html R] and [http://live.osgeo.org/en/quickstart/geoserver_quickstart.html GeoServer] do this very well.

Source documentation is written in [http://sphinx.pocoo.org/rest.html RST wiki format], is built using sphinx, and is stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/quickstart/<application>_quickstart.rst

The reference quickstart, which includes structure guidelines and with tips on how to fill in the quickstart is here:
https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/quickstart/udig_quickstart.rst
and is published here: http://live.osgeo.org/en/quickstart/udig_quickstart.html

In order to reduce disk space, and maintain consistency between applications, we request that all examples make use of the common [[#Example_Datasets]]. If the datasets don't cover your requirements, discuss this with us and we may add another suitable common dataset.

Applications are expected to include screen shots for each major step in the quickstart, as per [[#Screen_Shot|Screen Shot]].

Once finished, note your project's quickstart status="draft" in the OSGeo-Live project status at: http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB#gid=5 and email live-demo@lists.osgeo.org noting your documentation is ready for review. Once reviewed, the status is moved to "complete" and is ready for translation.

==== Quickstart Review Checklist ====

* Review latest Quickstart docs at: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/overview/overview.html
* Run with latest OSGeo-Live Development Release. Download from: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Downloads
* ''Before starting, notify others that you have started reviewing by setting "Quickstart reviewed by:" to "Started:<your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If you feel confident [http://wiki.osgeo.org/wiki/Live_GIS_Add_Project#Documentation updating the .rst documentation], then feel free to correct simple errors that you find, and commit back to subversion. (you will need [http://wiki.osgeo.org/wiki/Live_GIS_Disc#Subversion subversion access]).
* Otherwise, report problems in our [http://wiki.osgeo.org/wiki/Live_GIS_Disc#Issue_Tracker Issue Tracker] with keywords: ''docs 6.5 <application>'', component: ''LiveDVD'', milestone:

;Someone experienced with the project:
* Is the quickstart applicable for the version of the application installed on OSGeo-Live?
* If sample data is used, is it one of the OSGeo-Live datasets?
* Is there a screenshot for each step?
* Where appropriate, have screenshots been labeled (usually with numbers) to link them back to the documentation?
* ''Once finished, update Quickstart status to "6.5 Draft" and "Quickstart reviewed by:" to "osgeolive-version <your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If not already included, add the editor's name to the top of the .rst file:
:Author: Your Name
;QA Tester:
* Has the quickstart been run from start to finish?
* How long did the quickstart take to run? (Should be between 5 and 15 minutes)
* Has every step been explained in the quickstart?
* ''Once finished, update Quickstart status to "6.5 Reviewed" and "Quickstart reviewed by:" to "osgeolive-version <your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If not already included, add the testers name to the top of the .rst file:
:Reviewer: Your Name

;Reviewer for readability and consistency:
* Would the quickstart be understandable for a novice? Are all technical terms and acronyms explained?
* Is the language clear, and concise?
* Does the first paragraph explain what this Quickstart is going to cover?
* Are there steps for one scenario?
* Does the quickstart include "Things to try" and/or "What next" sections?
* ''Once finished, update Quickstart status to "6.5 Final" and "Quickstart reviewed by:" to "osgeolive-version <your name>" in [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 Status Spreadsheet].''
* If not already included, add the reviewer's name to the top of the .rst file:
:Reviewer: Your Name

=== Logo ===
The Project's logo is used in the headers of documentation (like Project Overviews, QuickStarts, Powerpoint presentations etc, and as icons on the OSGeo-Live Desktop. Hence there are a few different requirements for the logo.

;Header logo:
:* Stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/images/project_logos
:* Filename should be "logo-<projectname>.png" (apparently PNG is required for PDF docs)
:* Should have a transparent background (not white)
:* Preferably stored in size 125x125 pixels (for use in Project Overview and QuickStarts)
:* For PNGs ''please'' run a program like [http://packages.ubuntu.com/pngcrush pngcrush] or [http://packages.ubuntu.com/optipng optipng] to reduce the size of the image without degrading quality. Here's an example using <tt>optipng</tt>:
optipng -o5 image.png
:* Preferably also available as SVG, stored as "logo-<projectname>.svg"

;Desktop logo:
:We are still to define the requirements for creating a desktop logo. They will likely include:
:* A 32x32-pixel XPM icon for use by the Debian menus
:* A 48x48-pixel PNG icon for use by freedesktop.org menus

=== Screen Shot ===
Project overviews include an image, which is usually a screen shot, or collage of screen shorts. Quickstarts include screen shots for each significant step.
* Screen shots can be taken using [http://shutter-project.org/ Shutter] (on linux) or [http://getgreenshot.org/ Greenshot] (on windows).
* Screen shots should be taken from a 1024x768 display, and should be created in PNG format. (Apparently PNG is required for PDF documentation.)
* Images are to be stored here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/images/screenshots/1024x768
* For Quickstarts, consider marking up the image to explain the current steps. Eg: Add circled numbers: 1, 2, 3 or draw an oval around buttons being described. This is very easy to do using the "Edit" tab in the Shutter program, which provides these drawing icons to add. Tutorials augmented with detailed and pertinent images make it easy for the reader to follow what is going on. Extra time spent on an image pays off big in comprehension (you need more than just a course screen dump). Lines, numbering, highlights, boxes and annotations all help direct a user's focus to those areas which are important.
* Screenshots with large areas of constant color (menus, etc.) should be in PNG format, screenshots containing large areas of imagery (satellite images, shaded relief DEMs, etc.) should be in JPEG format.
* For PNGs ''please'' run a program like [http://packages.ubuntu.com/pngcrush pngcrush] to reduce the size of the image without degrading quality.

=== Extra Documentation ===
Some projects link to extra documentation, stored as PDFs or similar, or alternatively provide example applications. These should be referenced in documentation via a relative link such than it can viewed from:
http://localhost/<application>/... or http://live.osgeo.org/<application>/...

This should typically be achieved by creating a symbolic link from /var/www/<application> to /usr/local/share/doc/<application>

== Publishing Documentation ==

The following web service is useful for checking [http://docutils.sourceforge.net/rst.html reST] formatting: http://rst.ninjs.org/

For a more comprehensive test, set up the reST processor, sphinx:
: (''you will have to have [http://sphinx.pocoo.org/ Sphinx 0.6.4 or greater] installed, it's in the'' <tt>python-sphinx</tt> ''Debian package'')

sudo apt-get install python-sphinx

cd osgeo/livedvd/gisvm/trunk/doc/
make html

You can then view the results in:
osgeo/livedvd/gisvm/trunk/doc/_build/*.html

= Translations =
For details on how to translate, refer to [[Live GIS Translate]]

[[Category: Live-demo]]

AdhocVM

2014-04-25T09:55:30Z

Wiki-HamishBowman: /* Existing services hosted on the Ad-hoc VM: */ +oam

The Adhoc VM is a virtual machine minimally administered by [[SAC]], hosted on osgeo4 at OSU OSL and used for adhoc, and development activities related to OSGeo projects.

It differs from the Projects VM primarily in that:

* sudo access is granted less restrictively.
* greater risks to system operations are acceptable, as critical services are not run here.

The VM is reachable by ssh at adhoc.osgeo.osuosl.org. Anyone in the https://www.osgeo.org/cgi-bin/auth/ldap_shell.py has ssh access, and anyone in this group can add new people via the link. Sudo access can be provided by existing sudoer's by adding folks to the sudoers group in /etc/group.

For the most part SAC is providing no backup, or detailed administration for this server beyond some security patches, and ldap setup. It is up to the users of the VM to detail their use here, and to cooperate so as to avoid stepping on each others toes. It is a good idea to segregate activities into directories under /osgeo named after projects or users.

== Existing services hosted on the Ad-hoc VM: ==

{|class=wikitable border=1
! site
! path
! contact
! comments
|-
|mapbenderadhoc.osgeo.org
|/osgeo/mapbender
|astrid_emde, banjo, kmq
| still under discussion - have a look at [[Mapbender at AdhocVM]]
|-
|demo.mapserver.org
|/osgeo/mapserver
|jmckenna
| have a look at [[MapServer at AdhocVM]]
|-
|adhoc.osgeo.osuosl.org/livedvd/
|/osgeo/livedvd
|hamish, wildintellect, camerons
|daily cron job for nightly sphinx builds of LiveDVD documentation 
|-
|adhoc.osgeo.osuosl.org/grass/
|/osgeo/grass
|hamish, neteler
|Cron job demo plotting of recent earthquakes using GRASS batch job.
|-
|demo.pycsw.org
|/osgeo/demo.pycsw.org
| kalxas, tomkralidis
|CSW Server demos (running http://github.com/geopython/demo.pycsw.org)
|-
| oam.osgeo.org, docs.oam.osgeo.org
| /osgeo/oam
| crschmidt
| OpenAerialMap
|-
|''foo.osgeo.org''
|''/osgeo/project_name''
|''your osgeo_id here''
|''services running etc''
|-
|}

=== OS ===

''(command: <tt>lsb_release -a</tt>)''

* Distributor ID: Debian
* Description: Debian GNU/Linux 6.0.9 (squeeze)
* Release: 6.0.9
* Codename: squeeze

=== Apache ===

Each service is handled through a VirtualHost, configured in ''/etc/apache2/sites-available/''

==== ChangeLog ====

* The Sphinx 1.0.8 package from debian-backports has been installed.
: ''an old manually installed version 1.0.4 is still on disk at /usr/lib/python2.5/site-packages/''

[[Category:Infrastructure]]

AdhocVM

2014-04-25T09:35:12Z

Wiki-HamishBowman: /* OS */ updated

The Adhoc VM is a virtual machine minimally administered by [[SAC]], hosted on osgeo4 at OSU OSL and used for adhoc, and development activities related to OSGeo projects.

It differs from the Projects VM primarily in that:

* sudo access is granted less restrictively.
* greater risks to system operations are acceptable, as critical services are not run here.

The VM is reachable by ssh at adhoc.osgeo.osuosl.org. Anyone in the https://www.osgeo.org/cgi-bin/auth/ldap_shell.py has ssh access, and anyone in this group can add new people via the link. Sudo access can be provided by existing sudoer's by adding folks to the sudoers group in /etc/group.

For the most part SAC is providing no backup, or detailed administration for this server beyond some security patches, and ldap setup. It is up to the users of the VM to detail their use here, and to cooperate so as to avoid stepping on each others toes. It is a good idea to segregate activities into directories under /osgeo named after projects or users.

== Existing services hosted on the Ad-hoc VM: ==

{|class=wikitable border=1
! site
! path
! contact
! comments
|-
|mapbenderadhoc.osgeo.org
|/osgeo/mapbender
|astrid_emde, banjo, kmq
| still under discussion - have a look at [[Mapbender at AdhocVM]]
|-
|demo.mapserver.org
|/osgeo/mapserver
|jmckenna
| have a look at [[MapServer at AdhocVM]]
|-
|adhoc.osgeo.osuosl.org/livedvd/
|/osgeo/livedvd
|hamish, wildintellect, camerons
|daily cron job for nightly sphinx builds of LiveDVD documentation 
|-
|adhoc.osgeo.osuosl.org/grass/
|/osgeo/grass
|hamish, neteler
|Cron job demo plotting of recent earthquakes using GRASS batch job.
|-
|demo.pycsw.org
|/osgeo/demo.pycsw.org
| kalxas, tomkralidis
|CSW Server demos (running http://github.com/geopython/demo.pycsw.org)
|-
|''foo.osgeo.org''
|''/osgeo/project_name''
|''your osgeo_id here''
|''services running etc''
|-
|}

=== OS ===

''(command: <tt>lsb_release -a</tt>)''

* Distributor ID: Debian
* Description: Debian GNU/Linux 6.0.9 (squeeze)
* Release: 6.0.9
* Codename: squeeze

=== Apache ===

Each service is handled through a VirtualHost, configured in ''/etc/apache2/sites-available/''

==== ChangeLog ====

* The Sphinx 1.0.8 package from debian-backports has been installed.
: ''an old manually installed version 1.0.4 is still on disk at /usr/lib/python2.5/site-packages/''

[[Category:Infrastructure]]

AdhocVM

2014-04-25T09:32:52Z

Wiki-HamishBowman: grass earthquake demo status

The Adhoc VM is a virtual machine minimally administered by [[SAC]], hosted on osgeo4 at OSU OSL and used for adhoc, and development activities related to OSGeo projects.

It differs from the Projects VM primarily in that:

* sudo access is granted less restrictively.
* greater risks to system operations are acceptable, as critical services are not run here.

The VM is reachable by ssh at adhoc.osgeo.osuosl.org. Anyone in the https://www.osgeo.org/cgi-bin/auth/ldap_shell.py has ssh access, and anyone in this group can add new people via the link. Sudo access can be provided by existing sudoer's by adding folks to the sudoers group in /etc/group.

For the most part SAC is providing no backup, or detailed administration for this server beyond some security patches, and ldap setup. It is up to the users of the VM to detail their use here, and to cooperate so as to avoid stepping on each others toes. It is a good idea to segregate activities into directories under /osgeo named after projects or users.

== Existing services hosted on the Ad-hoc VM: ==

{|class=wikitable border=1
! site
! path
! contact
! comments
|-
|mapbenderadhoc.osgeo.org
|/osgeo/mapbender
|astrid_emde, banjo, kmq
| still under discussion - have a look at [[Mapbender at AdhocVM]]
|-
|demo.mapserver.org
|/osgeo/mapserver
|jmckenna
| have a look at [[MapServer at AdhocVM]]
|-
|adhoc.osgeo.osuosl.org/livedvd/
|/osgeo/livedvd
|hamish, wildintellect, camerons
|daily cron job for nightly sphinx builds of LiveDVD documentation 
|-
|adhoc.osgeo.osuosl.org/grass/
|/osgeo/grass
|hamish, neteler
|Cron job demo plotting of recent earthquakes using GRASS batch job.
|-
|demo.pycsw.org
|/osgeo/demo.pycsw.org
| kalxas, tomkralidis
|CSW Server demos (running http://github.com/geopython/demo.pycsw.org)
|-
|''foo.osgeo.org''
|''/osgeo/project_name''
|''your osgeo_id here''
|''services running etc''
|-
|}

=== OS ===

''(command: <tt>lsb_release -a</tt>)''

* Distributor ID: Debian
* Description: Debian GNU/Linux 6.0.3 (squeeze)
* Release: 6.0.3
* Codename: squeeze

=== Apache ===

Each service is handled through a VirtualHost, configured in ''/etc/apache2/sites-available/''

==== ChangeLog ====

* The Sphinx 1.0.8 package from debian-backports has been installed.
: ''an old manually installed version 1.0.4 is still on disk at /usr/lib/python2.5/site-packages/''

[[Category:Infrastructure]]

Google Summer of Code 2014 Ideas

2014-03-15T02:07:50Z

Wiki-HamishBowman: /* Guest projects */

[[Image:GoogleSummer_2014logo.jpg|300px|link=http://code.google.com/soc/]] @ [[Image:OSGeo_300_127_pixel.png|link=http://www.osgeo.org]]

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

* See also ideas from [[2007_SoC_Merged_Ideas|2007]], [[2008_SoC_Merged_Ideas|2008]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[Google Summer of Code 2010 Ideas|2010]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2012 Ideas|2012]], and [[Google Summer of Code 2013 Ideas|2013]].
-----

== OSGeo Google Summer of Code 2014 ==

The [http://www.osgeo.org 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.

* '''Students: If you need more information on how to apply you can contact all the mentoring organisations via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])

* 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 and [http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2014.pdf an OSGeo flavoured one as well].

* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.

* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google Summer of Code 2014]] wiki page.

== Important dates ==

* [http://www.google-melange.com/gsoc/events/google/gsoc2014 '''The official timeline''']


* February 24: Google announces accepted organizations. {{done}}

: Please start talking to the dev communities you are interested in ''now''.
* March 10: Student applications open.
: 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 the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''
* March 21: Student application deadline.
* April 21: '''Accepted student proposals are announced and Community Bonding Period begins.'''
* May 19: '''Coding begins!'''
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')
* June 23: Mid-term evaluation begins
* August 11-18: '''Pencils down!'''
* August 18-22: Final evaluations
* August 22: Students begin submitting required code samples to Google
* August 25: Final results announced

== The ideas pages ==
'''''[Check back often, it's a work in progress]'''''

Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:

=== OSGeo Foundation member projects ===

* ''More coming soon: Get started talking to your favorite project's development team today!''

[[Image:logo-grass.png|60px|right]]
* [https://trac.osgeo.org/grass/wiki/GSoC/2014 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look!

[[Image:logo-qgis.png|60px|right]]
* [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2014 '''QGIS''' SoC Ideas]: [http://www.qgis.org 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. It is written in C++ and Python.

[[Image:logo-gdal.png|60px|right]]

* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: [http://www.gdal.org GDAL] is a C++ library for reading and writing geospatial data raster and vector formats.



[[Image:logo-gvSIG.png|60px|right]]
* [[GvSIG_GSoC_2014_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project 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]. The gvSIG project looks for students with Java skills that want to develop new ideas on any of these products.

[[Image:logo-opticks.png|right]]
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: [http://opticks.org/ Opticks] is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.

[[Image:Osgeolive_60px.png|right]]
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2014 '''OSGeo-Live''' Ideas]: [http://live.osgeo.org OSGeo-Live] packages over 50 of the best geospatial open source projects, preconfigured with data, quickstarts and project overviews. We have packaging and automated build projects. ([[#Which_project_do_I_choose.3F|See below]])

[[Image:logo-postgis.png|60px|right]]
* [http://trac.osgeo.org/postgis/wiki/GoogleSummerCode '''PostGIS''' Ideas]: [http://postgis.net PostGIS] spatially enables the popular PostgreSQL object-relational database, allowing it to be used as a back-end database for geographic information systems (GIS) and web-mapping applications.

[[Image:logo-ossim.png|90px|right]]
* [https://trac.osgeo.org/ossim/wiki/GSoC_2014 '''OSSIM''' SoC Ideas]: [http://trac.osgeo.org/ossim/wiki OSSIM] Open Source Software Image Map (OSSIM) is a high performance engine for remote sensing, image processing, geographical information systems and photogrammetry. The software has been under active development since 1996 and is deployed across a number of private, federal and civilian agencies. It is written in C++.

[[Image:Logo_OTB.png|60px|right]]
* [http://wiki.orfeo-toolbox.org/index.php/GSOC_2014 '''OTB''' SoC Ideas]: [http://www.orfeo-toolbox.org ORFEO ToolBox] (OTB) is an open source library for remote sensing image processing.Targeted algorithms for high resolution optical images (Pleiades, SPOT, QuickBird, WorldView, Landsat, Ikonos), hyperspectral sensors (Hyperion) or SAR (TerraSarX, ERS, Palsar) are available. The software has been under active development since 2006 and is written in C++ and it includes also side projects also open source with GUI like Monteverdi. OTB has recently started the incubation process into OSGeo.

  



=== Guest projects ===

Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact Hamish, Anne and Dustan.

[[Image:Logo-osm6.png|60px|right]]
* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2014/Project_Ideas '''OpenStreetMap''' Ideas]: [http://osm.org/ OSM] is a project aimed squarely at creating and providing free geographic data such as street maps to anyone who wants them. The project was started because most maps you think of as free actually have legal or technical restrictions on their use, holding back people from using them in creative, productive or unexpected ways.
:* ''This year OpenStreetMap students will again be hosted under OSGeo's GSoC umbrella. Talk to OSM, but apply with us. Begin your proposal description with "OSM: " so we know which way to direct it.''

[[Image:Pgrouting-logo.png|60px|right]]

* [https://github.com/pgrouting/pgrouting/wiki/GSOC-Ideas '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.

[[Image:Pywps-logo.png|60px|right]]

* [https://github.com/jachym/pywps-4/wiki/GSOC-2014-ideas '''PyWPS''' Ideas]: [http://pywps.wald.intevation.org PyWPS] is server implementation of OGC WPS standard on server side using Python programming language. Currently, [http://github.com/jachym/pywps-4/ new version of PyWPS] is being done, were we would like to implement several new attractive features.

* [https://sourceforge.net/p/istsos/wiki/GSoC_ideas_2014/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] [[Image:Logo-istSOS.png|100px|right]] (Istituto Scienze della Terra Sensor Observation Service) is an implementation of the Sensor Observation Service (SOS) standard from the Open Geospatial Consortium (OGC). The development of istSOS was started in 2009 in order to provide a simple implementation of the SOS standard for the management, provision and integration of hydro-meteorological data collected in Canton Ticino (Switzerland). istSOS is entirely written in Python.

[[Image:logo-uDig.png|60px|right]]
* [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-Ideas-2014 '''JGrasstools''' and '''uDig''' SoC Ideas]: User-friendly Desktop GIS ([http://udig.github.io/ uDig]) 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.



[[Image:Logo-cartaro.png|60px|right]]
* [https://groups.drupal.org/node/407408 '''Cartaro''' Ideas]: [http://cartaro.org Cartaro] provides geospatial functionality and web services within the Drupal Content Management System (CMS). It is builds upon robust Open Source components: the PostGIS database, GeoServer and GeoWebCache web services, OpenLayers maps in the browser, all managed from within the powerful Drupal CMS.

[[Image:Geonode logo.png|60px|right]]
* [https://github.com/GeoNode/geonode/wiki/Google-Summer-of-Code-Ideas-2014 '''GeoNode''' Ideas]: [http://geonode.org/ GeoNode] is an Open Source Geospatial Content Management System: a web-based application and platform for developing Geospatial Information Systems (GIS) and for deploying spatial data infrastructures (SDI). It is designed to be easily extended and modified, and can be integrated into existing platforms. Written with the Python Django web application, it is based on other great Open Source components such as PostGIS, GeoServer, OpenLayers and GeoExplorer.

[[Image:neo4j-spatial_64.png|right]]
* [https://github.com/neo4j/GSoC/wiki '''Neo4j Spatial''' Ideas]: [https://github.com/neo4j/spatial Neo4j Spatial] is an Open Source library extending the popular [http://neo4j.org Neo4j Graph Database] with a number of features for GIS enabling your data model. It embeds and relies on JTS and GeoTools, and provides the ability to store your domain model in many internal formats, and has utilities for import and export of Shapefiles and OpenStreetMap data. We've received contributions from GSoC projects in 2010, 2011 and 2012.

[[Image:Logo-cartoDB.png|70px|right]]
* [https://github.com/CartoDB/cartodb/wiki/GoogleSummerCode '''CartoDB Ideas''']: [http://cartodb.com/develop CartoDB] is a cloud based mapping, analysis and visualization engine that lets users build spatial applications for both mobile and the web. Students will need to be able to use PHP and PostgreSQL.





== Which project do I choose? ==

Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.
: View the documents and download the ISO from http://live.osgeo.org
[[File:Osgeolive wordle.png|400px|center]]

== How to get in contact via mailing lists ==

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, as well as the longer list at http://lists.osgeo.org.

== How to get in contact via IRC ==

Primary channel:

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

GSoC @ OSGeo inter-project discussions:

* irc://irc.freenode.net/#osgeo-soc

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/#mapguide
* irc://irc.freenode.net/#mapnik
* irc://irc.freenode.net/#mapserver
* irc://irc.freenode.net/#openlayers
* irc://irc.freenode.net/#opticks
* irc://irc.freenode.net/#osgeolive
* irc://irc.freenode.net/#ossimplanet
* irc://irc.freenode.net/#pgrouting-project
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#qgis
* irc://irc.freenode.net/#udig
* irc://irc.oftc.net/#osm-dev

== Application questions we'll ask you ==
'''''[Provisional]'''''

* All questions must be answered, ''no exceptions''. Treat this as something between a formal job application and a scholarship application, because that's exactly what it is.

Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

Title:
(please include the name of the member project as part of
the title, for example: "Gee Whiz Foobar 2001 for QGIS")

Describe your idea
1. Introduction
2. Background
3. The idea
4. Project plan ('''detailed timeline''': how do you plan to spend your summer?)
5. Future ideas / How can your idea be expanded?

Explain how your SoC task would benefit the OSGeo member
project and more generally the OSGeo Foundation as a whole:

Please provide details of general computing experience:
(operating systems you use on a day-to-day basis, languages you
could write a program in, hardware, networking experience, etc.)

Please provide details of previous GIS experience:

Please provide details of any previous involvement with
GIS programming and other software programming:

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

Please tell us why you are interested in working for OSGeo
and the software project you have selected:

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

Would your application contribute to your ongoing studies/
degree? If so, how?

Please explain how you intend to continue being an active
member of your project and/or OSGeo AFTER the summer is over:

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

Do you have any known time conflicts during the official coding
period? (May 19 to August 18)

== What to expect during the summer ==

* A group of past GSoC students, mentors, and Googlers have prepared this short book just for you:
: [http://google-opensource.blogspot.com/2011/02/flip-bits-not-burgers-student-guide.html Flip bits not Burgers: The Student's Guide to the Summer of Code] -- READ THIS eBOOK

=== 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 integrate you into the developer community, so you should get involved with them 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, like making sure you get paid.

University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.

=== 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 up front, be honest, and we'll work around it. 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 require 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.

We plan to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.

Final reports from those blogs and wiki pages will be collected into a OSGeoofcode posting about what everyone did during the summer, ensuring you long lasting fame and fortune. (''Or failing that, a bit of public press, a bit of cash from Google, and a lot of gratitude and kudos from us, your peers.'')

[Back to [[Google Summer of Code 2014]] @ OSGeo]
[[Category: Google Summer of Code]]

Google Summer of Code 2014 Ideas

2014-03-15T02:07:20Z

Wiki-HamishBowman: /* Guest projects */

[[Image:GoogleSummer_2014logo.jpg|300px|link=http://code.google.com/soc/]] @ [[Image:OSGeo_300_127_pixel.png|link=http://www.osgeo.org]]

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

* See also ideas from [[2007_SoC_Merged_Ideas|2007]], [[2008_SoC_Merged_Ideas|2008]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[Google Summer of Code 2010 Ideas|2010]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2012 Ideas|2012]], and [[Google Summer of Code 2013 Ideas|2013]].
-----

== OSGeo Google Summer of Code 2014 ==

The [http://www.osgeo.org 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.

* '''Students: If you need more information on how to apply you can contact all the mentoring organisations via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])

* 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 and [http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2014.pdf an OSGeo flavoured one as well].

* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.

* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google Summer of Code 2014]] wiki page.

== Important dates ==

* [http://www.google-melange.com/gsoc/events/google/gsoc2014 '''The official timeline''']


* February 24: Google announces accepted organizations. {{done}}

: Please start talking to the dev communities you are interested in ''now''.
* March 10: Student applications open.
: 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 the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''
* March 21: Student application deadline.
* April 21: '''Accepted student proposals are announced and Community Bonding Period begins.'''
* May 19: '''Coding begins!'''
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')
* June 23: Mid-term evaluation begins
* August 11-18: '''Pencils down!'''
* August 18-22: Final evaluations
* August 22: Students begin submitting required code samples to Google
* August 25: Final results announced

== The ideas pages ==
'''''[Check back often, it's a work in progress]'''''

Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:

=== OSGeo Foundation member projects ===

* ''More coming soon: Get started talking to your favorite project's development team today!''

[[Image:logo-grass.png|60px|right]]
* [https://trac.osgeo.org/grass/wiki/GSoC/2014 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look!

[[Image:logo-qgis.png|60px|right]]
* [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2014 '''QGIS''' SoC Ideas]: [http://www.qgis.org 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. It is written in C++ and Python.

[[Image:logo-gdal.png|60px|right]]

* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: [http://www.gdal.org GDAL] is a C++ library for reading and writing geospatial data raster and vector formats.



[[Image:logo-gvSIG.png|60px|right]]
* [[GvSIG_GSoC_2014_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project 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]. The gvSIG project looks for students with Java skills that want to develop new ideas on any of these products.

[[Image:logo-opticks.png|right]]
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: [http://opticks.org/ Opticks] is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.

[[Image:Osgeolive_60px.png|right]]
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2014 '''OSGeo-Live''' Ideas]: [http://live.osgeo.org OSGeo-Live] packages over 50 of the best geospatial open source projects, preconfigured with data, quickstarts and project overviews. We have packaging and automated build projects. ([[#Which_project_do_I_choose.3F|See below]])

[[Image:logo-postgis.png|60px|right]]
* [http://trac.osgeo.org/postgis/wiki/GoogleSummerCode '''PostGIS''' Ideas]: [http://postgis.net PostGIS] spatially enables the popular PostgreSQL object-relational database, allowing it to be used as a back-end database for geographic information systems (GIS) and web-mapping applications.

[[Image:logo-ossim.png|90px|right]]
* [https://trac.osgeo.org/ossim/wiki/GSoC_2014 '''OSSIM''' SoC Ideas]: [http://trac.osgeo.org/ossim/wiki OSSIM] Open Source Software Image Map (OSSIM) is a high performance engine for remote sensing, image processing, geographical information systems and photogrammetry. The software has been under active development since 1996 and is deployed across a number of private, federal and civilian agencies. It is written in C++.

[[Image:Logo_OTB.png|60px|right]]
* [http://wiki.orfeo-toolbox.org/index.php/GSOC_2014 '''OTB''' SoC Ideas]: [http://www.orfeo-toolbox.org ORFEO ToolBox] (OTB) is an open source library for remote sensing image processing.Targeted algorithms for high resolution optical images (Pleiades, SPOT, QuickBird, WorldView, Landsat, Ikonos), hyperspectral sensors (Hyperion) or SAR (TerraSarX, ERS, Palsar) are available. The software has been under active development since 2006 and is written in C++ and it includes also side projects also open source with GUI like Monteverdi. OTB has recently started the incubation process into OSGeo.

  



=== Guest projects ===

Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact Hamish, Anne and Dustan.

[[Image:Logo-osm6.png|60px|right]]
* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2014/Project_Ideas '''OpenStreetMap''' Ideas]: [http://osm.org/ OSM] is a project aimed squarely at creating and providing free geographic data such as street maps to anyone who wants them. The project was started because most maps you think of as free actually have legal or technical restrictions on their use, holding back people from using them in creative, productive or unexpected ways.
:* ''This year OpenStreetMap students will again be hosted under OSGeo's GSoC umbrella. Talk to OSM, but apply with us. Begin your proposal description with "OSM: " so we know which way to direct it.''

[[Image:Pgrouting-logo.png|60px|right]]

* [https://github.com/pgrouting/pgrouting/wiki/GSOC-Ideas '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.

[[Image:Pywps-logo.png|60px|right]]

* [https://github.com/jachym/pywps-4/wiki/GSOC-2014-ideas '''PyWPS''' Ideas]: [http://pywps.wald.intevation.org PyWPS] is server implementation of OGC WPS standard on server side using Python programming language. Currently, [http://github.com/jachym/pywps-4/ new version of PyWPS] is being done, were we would like to implement several new attractive features.

* [https://sourceforge.net/p/istsos/wiki/GSoC_ideas_2014/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] [[Image:Logo-istSOS.png|100px|right]] (Istituto Scienze della Terra Sensor Observation Service) is an implementation of the Sensor Observation Service (SOS) standard from the Open Geospatial Consortium (OGC). The development of istSOS was started in 2009 in order to provide a simple implementation of the SOS standard for the management, provision and integration of hydro-meteorological data collected in Canton Ticino (Switzerland). istSOS is entirely written in Python.

[[Image:logo-uDig.png|60px|right]]
* [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-Ideas-2014 '''JGrasstools''' and '''uDig''' SoC Ideas]: User-friendly Desktop GIS ([http://udig.github.io/ uDig]) 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.



[[Image:Logo-cartaro.png|60px|right]]
* [https://groups.drupal.org/node/407408 '''Cartaro''' Ideas]: [http://cartaro.org Cartaro] provides geospatial functionality and web services within the Drupal Content Management System (CMS). It is builds upon robust Open Source components: the PostGIS database, GeoServer and GeoWebCache web services, OpenLayers maps in the browser, all managed from within the powerful Drupal CMS.

[[Image:Geonode logo.png|60px|right]]
* [https://github.com/GeoNode/geonode/wiki/Google-Summer-of-Code-Ideas-2014 '''GeoNode''' Ideas]: [http://geonode.org/ GeoNode] is an Open Source Geospatial Content Management System: a web-based application and platform for developing Geospatial Information Systems (GIS) and for deploying spatial data infrastructures (SDI). It is designed to be easily extended and modified, and can be integrated into existing platforms. Written with the Python Django web application, it is based on other great Open Source components such as PostGIS, GeoServer, OpenLayers and GeoExplorer.

[[Image:neo4j-spatial_64.png|right]]
* [https://github.com/neo4j/GSoC/wiki '''Neo4j Spatial''' Ideas]: [https://github.com/neo4j/spatial Neo4j Spatial] is an Open Source library extending the popular [http://neo4j.org Neo4j Graph Database] with a number of features for GIS enabling your data model. It embeds and relies on JTS and GeoTools, and provides the ability to store your domain model in many internal formats, and has utilities for import and export of Shapefiles and OpenStreetMap data. We've received contributions from GSoC projects in 2010, 2011 and 2012.

[[Image:Logo-cartoDB.png|70px|right]]
* [https://github.com/CartoDB/cartodb/wiki/GoogleSummerCode '''CartoDB Ideas''']: [http://cartodb.com/develop CartoDB] is a cloud based mapping, analysis and visualization engine that lets users build spatial applications for both mobile and the web. Student will need to be able to use PHP and PostgreSQL.





== Which project do I choose? ==

Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.
: View the documents and download the ISO from http://live.osgeo.org
[[File:Osgeolive wordle.png|400px|center]]

== How to get in contact via mailing lists ==

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, as well as the longer list at http://lists.osgeo.org.

== How to get in contact via IRC ==

Primary channel:

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

GSoC @ OSGeo inter-project discussions:

* irc://irc.freenode.net/#osgeo-soc

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/#mapguide
* irc://irc.freenode.net/#mapnik
* irc://irc.freenode.net/#mapserver
* irc://irc.freenode.net/#openlayers
* irc://irc.freenode.net/#opticks
* irc://irc.freenode.net/#osgeolive
* irc://irc.freenode.net/#ossimplanet
* irc://irc.freenode.net/#pgrouting-project
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#qgis
* irc://irc.freenode.net/#udig
* irc://irc.oftc.net/#osm-dev

== Application questions we'll ask you ==
'''''[Provisional]'''''

* All questions must be answered, ''no exceptions''. Treat this as something between a formal job application and a scholarship application, because that's exactly what it is.

Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

Title:
(please include the name of the member project as part of
the title, for example: "Gee Whiz Foobar 2001 for QGIS")

Describe your idea
1. Introduction
2. Background
3. The idea
4. Project plan ('''detailed timeline''': how do you plan to spend your summer?)
5. Future ideas / How can your idea be expanded?

Explain how your SoC task would benefit the OSGeo member
project and more generally the OSGeo Foundation as a whole:

Please provide details of general computing experience:
(operating systems you use on a day-to-day basis, languages you
could write a program in, hardware, networking experience, etc.)

Please provide details of previous GIS experience:

Please provide details of any previous involvement with
GIS programming and other software programming:

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

Please tell us why you are interested in working for OSGeo
and the software project you have selected:

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

Would your application contribute to your ongoing studies/
degree? If so, how?

Please explain how you intend to continue being an active
member of your project and/or OSGeo AFTER the summer is over:

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

Do you have any known time conflicts during the official coding
period? (May 19 to August 18)

== What to expect during the summer ==

* A group of past GSoC students, mentors, and Googlers have prepared this short book just for you:
: [http://google-opensource.blogspot.com/2011/02/flip-bits-not-burgers-student-guide.html Flip bits not Burgers: The Student's Guide to the Summer of Code] -- READ THIS eBOOK

=== 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 integrate you into the developer community, so you should get involved with them 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, like making sure you get paid.

University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.

=== 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 up front, be honest, and we'll work around it. 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 require 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.

We plan to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.

Final reports from those blogs and wiki pages will be collected into a OSGeoofcode posting about what everyone did during the summer, ensuring you long lasting fame and fortune. (''Or failing that, a bit of public press, a bit of cash from Google, and a lot of gratitude and kudos from us, your peers.'')

[Back to [[Google Summer of Code 2014]] @ OSGeo]
[[Category: Google Summer of Code]]

Google Summer of Code 2014 Ideas

2014-03-15T02:05:50Z

Wiki-HamishBowman: /* Guest projects */

[[Image:GoogleSummer_2014logo.jpg|300px|link=http://code.google.com/soc/]] @ [[Image:OSGeo_300_127_pixel.png|link=http://www.osgeo.org]]

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

* See also ideas from [[2007_SoC_Merged_Ideas|2007]], [[2008_SoC_Merged_Ideas|2008]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[Google Summer of Code 2010 Ideas|2010]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2012 Ideas|2012]], and [[Google Summer of Code 2013 Ideas|2013]].
-----

== OSGeo Google Summer of Code 2014 ==

The [http://www.osgeo.org 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.

* '''Students: If you need more information on how to apply you can contact all the mentoring organisations via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])

* 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 and [http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2014.pdf an OSGeo flavoured one as well].

* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.

* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google Summer of Code 2014]] wiki page.

== Important dates ==

* [http://www.google-melange.com/gsoc/events/google/gsoc2014 '''The official timeline''']


* February 24: Google announces accepted organizations. {{done}}

: Please start talking to the dev communities you are interested in ''now''.
* March 10: Student applications open.
: 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 the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''
* March 21: Student application deadline.
* April 21: '''Accepted student proposals are announced and Community Bonding Period begins.'''
* May 19: '''Coding begins!'''
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')
* June 23: Mid-term evaluation begins
* August 11-18: '''Pencils down!'''
* August 18-22: Final evaluations
* August 22: Students begin submitting required code samples to Google
* August 25: Final results announced

== The ideas pages ==
'''''[Check back often, it's a work in progress]'''''

Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:

=== OSGeo Foundation member projects ===

* ''More coming soon: Get started talking to your favorite project's development team today!''

[[Image:logo-grass.png|60px|right]]
* [https://trac.osgeo.org/grass/wiki/GSoC/2014 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look!

[[Image:logo-qgis.png|60px|right]]
* [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2014 '''QGIS''' SoC Ideas]: [http://www.qgis.org 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. It is written in C++ and Python.

[[Image:logo-gdal.png|60px|right]]

* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: [http://www.gdal.org GDAL] is a C++ library for reading and writing geospatial data raster and vector formats.



[[Image:logo-gvSIG.png|60px|right]]
* [[GvSIG_GSoC_2014_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project 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]. The gvSIG project looks for students with Java skills that want to develop new ideas on any of these products.

[[Image:logo-opticks.png|right]]
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: [http://opticks.org/ Opticks] is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.

[[Image:Osgeolive_60px.png|right]]
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2014 '''OSGeo-Live''' Ideas]: [http://live.osgeo.org OSGeo-Live] packages over 50 of the best geospatial open source projects, preconfigured with data, quickstarts and project overviews. We have packaging and automated build projects. ([[#Which_project_do_I_choose.3F|See below]])

[[Image:logo-postgis.png|60px|right]]
* [http://trac.osgeo.org/postgis/wiki/GoogleSummerCode '''PostGIS''' Ideas]: [http://postgis.net PostGIS] spatially enables the popular PostgreSQL object-relational database, allowing it to be used as a back-end database for geographic information systems (GIS) and web-mapping applications.

[[Image:logo-ossim.png|90px|right]]
* [https://trac.osgeo.org/ossim/wiki/GSoC_2014 '''OSSIM''' SoC Ideas]: [http://trac.osgeo.org/ossim/wiki OSSIM] Open Source Software Image Map (OSSIM) is a high performance engine for remote sensing, image processing, geographical information systems and photogrammetry. The software has been under active development since 1996 and is deployed across a number of private, federal and civilian agencies. It is written in C++.

[[Image:Logo_OTB.png|60px|right]]
* [http://wiki.orfeo-toolbox.org/index.php/GSOC_2014 '''OTB''' SoC Ideas]: [http://www.orfeo-toolbox.org ORFEO ToolBox] (OTB) is an open source library for remote sensing image processing.Targeted algorithms for high resolution optical images (Pleiades, SPOT, QuickBird, WorldView, Landsat, Ikonos), hyperspectral sensors (Hyperion) or SAR (TerraSarX, ERS, Palsar) are available. The software has been under active development since 2006 and is written in C++ and it includes also side projects also open source with GUI like Monteverdi. OTB has recently started the incubation process into OSGeo.

  



=== Guest projects ===

Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact Hamish, Anne and Dustan.

[[Image:Logo-osm6.png|60px|right]]
* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2014/Project_Ideas '''OpenStreetMap''' Ideas]: [http://osm.org/ OSM] is a project aimed squarely at creating and providing free geographic data such as street maps to anyone who wants them. The project was started because most maps you think of as free actually have legal or technical restrictions on their use, holding back people from using them in creative, productive or unexpected ways.
:* ''This year OpenStreetMap students will again be hosted under OSGeo's GSoC umbrella. Talk to OSM, but apply with us. Begin your proposal description with "OSM: " so we know which way to direct it.''

[[Image:Pgrouting-logo.png|60px|right]]

* [https://github.com/pgrouting/pgrouting/wiki/GSOC-Ideas '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.

[[Image:Pywps-logo.png|60px|right]]

* [https://github.com/jachym/pywps-4/wiki/GSOC-2014-ideas '''PyWPS''' Ideas]: [http://pywps.wald.intevation.org PyWPS] is server implementation of OGC WPS standard on server side using Python programming language. Currently, [http://github.com/jachym/pywps-4/ new version of PyWPS] is being done, were we would like to implement several new attractive features.

* [https://sourceforge.net/p/istsos/wiki/GSoC_ideas_2014/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] [[Image:Logo-istSOS.png|100px|right]] (Istituto Scienze della Terra Sensor Observation Service) is an implementation of the Sensor Observation Service (SOS) standard from the Open Geospatial Consortium (OGC). The development of istSOS was started in 2009 in order to provide a simple implementation of the SOS standard for the management, provision and integration of hydro-meteorological data collected in Canton Ticino (Switzerland). istSOS is entirely written in Python.

[[Image:logo-uDig.png|60px|right]]
* [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-Ideas-2014 '''JGrasstools''' and '''uDig''' SoC Ideas]: User-friendly Desktop GIS ([http://udig.github.io/ uDig]) 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.



[[Image:Logo-cartaro.png|60px|right]]
* [https://groups.drupal.org/node/407408 '''Cartaro''' Ideas]: [http://cartaro.org Cartaro] provides geospatial functionality and web services within the Drupal Content Management System (CMS). It is builds upon robust Open Source components: the PostGIS database, GeoServer and GeoWebCache web services, OpenLayers maps in the browser, all managed from within the powerful Drupal CMS.

[[Image:Geonode logo.png|60px|right]]
* [https://github.com/GeoNode/geonode/wiki/Google-Summer-of-Code-Ideas-2014 '''GeoNode''' Ideas]: [http://geonode.org/ GeoNode] is an Open Source Geospatial Content Management System: a web-based application and platform for developing Geospatial Information Systems (GIS) and for deploying spatial data infrastructures (SDI). It is designed to be easily extended and modified, and can be integrated into existing platforms. Written with the Python Django web application, it is based on other great Open Source components such as PostGIS, GeoServer, OpenLayers and GeoExplorer.

[[Image:neo4j-spatial_64.png|right]]
* [https://github.com/neo4j/GSoC/wiki '''Neo4j Spatial''' Ideas]: [https://github.com/neo4j/spatial Neo4j Spatial] is an Open Source library extending the popular [http://neo4j.org Neo4j Graph Database] with a number of features for GIS enabling your data model. It embeds and relies on JTS and GeoTools, and provides the ability to store your domain model in many internal formats, and has utilities for import and export of Shapefiles and OpenStreetMap data. We've received contributions from GSoC projects in 2010, 2011 and 2012.

[[Image:Logo-cartoDB.png|70px|right]]
* [https://github.com/CartoDB/cartodb/wiki/GoogleSummerCode '''CartoDB Ideas''']: [http://cartodb.com/develop CartoDB] is a cloud based mapping, analysis and visualization engine that lets users build spatial applications for both mobile and the web.





== Which project do I choose? ==

Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.
: View the documents and download the ISO from http://live.osgeo.org
[[File:Osgeolive wordle.png|400px|center]]

== How to get in contact via mailing lists ==

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, as well as the longer list at http://lists.osgeo.org.

== How to get in contact via IRC ==

Primary channel:

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

GSoC @ OSGeo inter-project discussions:

* irc://irc.freenode.net/#osgeo-soc

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/#mapguide
* irc://irc.freenode.net/#mapnik
* irc://irc.freenode.net/#mapserver
* irc://irc.freenode.net/#openlayers
* irc://irc.freenode.net/#opticks
* irc://irc.freenode.net/#osgeolive
* irc://irc.freenode.net/#ossimplanet
* irc://irc.freenode.net/#pgrouting-project
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#qgis
* irc://irc.freenode.net/#udig
* irc://irc.oftc.net/#osm-dev

== Application questions we'll ask you ==
'''''[Provisional]'''''

* All questions must be answered, ''no exceptions''. Treat this as something between a formal job application and a scholarship application, because that's exactly what it is.

Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

Title:
(please include the name of the member project as part of
the title, for example: "Gee Whiz Foobar 2001 for QGIS")

Describe your idea
1. Introduction
2. Background
3. The idea
4. Project plan ('''detailed timeline''': how do you plan to spend your summer?)
5. Future ideas / How can your idea be expanded?

Explain how your SoC task would benefit the OSGeo member
project and more generally the OSGeo Foundation as a whole:

Please provide details of general computing experience:
(operating systems you use on a day-to-day basis, languages you
could write a program in, hardware, networking experience, etc.)

Please provide details of previous GIS experience:

Please provide details of any previous involvement with
GIS programming and other software programming:

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

Please tell us why you are interested in working for OSGeo
and the software project you have selected:

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

Would your application contribute to your ongoing studies/
degree? If so, how?

Please explain how you intend to continue being an active
member of your project and/or OSGeo AFTER the summer is over:

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

Do you have any known time conflicts during the official coding
period? (May 19 to August 18)

== What to expect during the summer ==

* A group of past GSoC students, mentors, and Googlers have prepared this short book just for you:
: [http://google-opensource.blogspot.com/2011/02/flip-bits-not-burgers-student-guide.html Flip bits not Burgers: The Student's Guide to the Summer of Code] -- READ THIS eBOOK

=== 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 integrate you into the developer community, so you should get involved with them 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, like making sure you get paid.

University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.

=== 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 up front, be honest, and we'll work around it. 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 require 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.

We plan to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.

Final reports from those blogs and wiki pages will be collected into a OSGeoofcode posting about what everyone did during the summer, ensuring you long lasting fame and fortune. (''Or failing that, a bit of public press, a bit of cash from Google, and a lot of gratitude and kudos from us, your peers.'')

[Back to [[Google Summer of Code 2014]] @ OSGeo]
[[Category: Google Summer of Code]]

File:Logo-cartoDB.png

2014-03-15T02:04:19Z

Wiki-HamishBowman: uploaded a new version of "File:Logo-cartoDB.png"

File:Logo-cartoDB.png

2014-03-15T02:03:24Z

Wiki-HamishBowman: uploaded a new version of "File:Logo-cartoDB.png"