OSGeo - User contributions [en]

Joint OGC OSGeo ASF Sprint 2021

2021-02-12T16:22:27Z

Wiki-Epifanio: /* Participants */

== Purpose ==
Document/track/coordinate FOSS4G project participation at the virtual [https://github.com/opengeospatial/joint-ogc-osgeo-asf-sprint-2021 Joint OGC OSGeo ASF Code Sprint 2021]. The virtual event will run on 17/18/19 February 2021. The sprint will begin at 07:00am EST on the first day, and end at 05:30pm EST on the last day.

== Event Details ==

All information, logistics for participants is coordinated at https://github.com/opengeospatial/joint-ogc-osgeo-asf-sprint-2021

There is an OGC registration page (https://portal.ogc.org/public_ogc/register/20210217_code_sprint.php) if you wish to be invited to kick-off meetings.

== Participants ==
{| class="wikitable"
|-
! No !! Name !! Country !! Email !! Organization !! Project(s) || Standard (s)
|-
| 1 || Tom Kralidis || Canada || tomkralidis at gmail.com || Meteorological Service of Canada || pygeoapi, pycsw, OWSLib and the Geopython stack || ogc-api-records
|-
| 2 || Angelos Tzotsos || Greece || tzotsos at gmail.com || OSGeo || OSGeoLive, pycsw, pygeoapi, GeoNode, OWSLib ||
|-
| 3 || Steve Lime || USA/MN || sdlime at gmail.com || MNIT Services || MapServer || OGCAPI support
|-
| 4 || Astrid Emde || Germany || astrid_emde at osgeo.org || OSGeo || OSGeoLive, OSGeo ||
|-
| 5 || Andrea Aime || Italy || andrea.aime at gmail.com || GeoSolutions || GeoServer || ogc-api-features
|-
| 6 || Jody Garnett || Canada|| jody.garnett at gmail.com || GeoCat || GeoServer || ogc-api-features
|-
| 7 || Paul van Genuchten || NL|| genuchten at yahoo.com || GeoCat || GeoNetwork / pygeoapi || ogc-api-features
|-
| 8 || Just van den Broecke || NL|| justb4 at gmail.com || Just Objects || pygeoapi, stetl, GeoHealthCheck and the GeoPython stack || ogc-api-features
|-
| 9 || Peter Rushforth || Canada || peter.rushforth at gmail.com || Natural Resources Canada || GeoServer || Map Markup Language
|-
| 10 || Ahmad Ayubi || Canada || ahmad.ayubi at canada.ca || Natural Resources Canada || GeoServer MapML Community Module Viewer || Map Markup Language
|-
| 11 || Massimo Di Stefano || Norway || massimods at met.no || Norwegian Meteorological Institute || pycsw || CSW
|}

== Updates ==

[[Category:Code Sprints]]
[[Category:OGC]]

Google Summer of Code Recommendations for Students

2017-03-10T10:12:05Z

Wiki-Epifanio: /* RTFM */

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://summerofcode.withgoogle.com/]] @ 
[[Image:OSGeo_300_127_pixel.png|300px|link=http://www.osgeo.org]]
</center>

-----
* Back to the main OSGeo [[Google Summer of Code 2017]] wiki page.
* Check out the [[Google_Summer_of_Code_2017_Ideas | Ideas web page]] or propose your own!

-----

== How to get in contact with your potential mentors ==

Since OSGeo is an umbrella organisation for multiple project communities, each community has their own discussion and development [[Mailing Lists]].

'''OSGeo mailing lists of interest for GSoC 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)
:* The dedicated dev mailing list of the software you intend to develop for (Browse http://lists.osgeo.org)

* To contact OSGeo's GSoC admin team directly:
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]

== How to increase your chances of being selected ==

If you put yourself in the shoes of the mentor that should select the student, you'll immediately realize that there are some behaviours that are usually rewarded. Here's some examples.

=== Be proactive ===

* Mentors are more likely to select students that openly discuss the existing ideas and / or propose their own. It is a '''bad idea''' to just submit your idea only in the Google web site without discussing it, because it won't be noticed. Mentors and developers discuss ideas mostly in [[Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_mailing_lists | mailing lists]].
* It is a '''bad idea''' just listing your programming skills and waiting for the mentors to guide you towards next steps. Mentors reward students that show genuine interest in the projects they are willing to develop, propose improvements on their own and make pertinent questions. Remember that it is up to you, and not to the mentor, decide the software you want to work on and the idea to develop. It is not the mentor's job to do that for you.
* It is a '''good idea''' to engage the individual dev lists and find a community that you are interested in working with and start building a relationship with that community. It is the community that decides which of the candidates they want to back, based on the value of the project, and whether or not they think the student will be successful.

=== Demonstrate your skills ===

Consider that mentors are being contacted by several students that apply for the same project. A way to show that you are the best candidate, is to demonstrate that you are familiar with the software and you can code. How? Browse the bug tracker, fix some bugs and propose your patch in mailing list, and/or ask mentors to challenge you! Moreover, bug fixes are a great way to get familiar with the code.

=== Demonstrate your intention to stay ===

Students that are likely to disappear after GSoC are less likely to be selected. This is because there is no point in developing something that won't be maintained. And moreover, one scope of GSoC is to bring new developers to the community.

=== [http://xkcd.com/293/ RTFM] ===

Read the relevant information about GSoC in the wiki / web pages before asking. Most FAQs have been answered already!
* OSGeo Wiki pages related to GSoC can be browsed from [http://wiki.osgeo.org/wiki/Category:Google_Summer_of_Code Category:Google Summer of Code].
* [https://developers.google.com/open-source/gsoc/resources/ Full documentation about GSoC on official website].
* [https://developers.google.com/open-source/gsoc/faq FAQ from GSoC web site].
* [https://summerofcode.withgoogle.com/rules/ GOOGLE SUMMER OF CODE 2017 PROGRAM RULES].
* A group of past GSoC students, mentors, and Googlers have prepared this short book just for you: [https://flossmanuals.net/GSoCStudentGuide/ The Student's Guide to the Summer of Code]
* If you are new to OSGeo, take the time to familiarize with the [http://www.osgeo.org/content/foundation/about.html Open Source Geospatial Foundation]

== Application instructions ==

We welcome students to contact relevant developer communities within OSGeo umbrella before submitting their application into GSoC official website. If in doubt for which project(s) to contact, send the mail to both soc and discuss mailing lists.
We recommend browsing past years' ideas pages, to look for ready-to-use projects, and to get an idea of the expected amount of work for a valid GSoC proposal.
Developers will then assist students in filling the proposal template (see below) and will prepare a small coding test (programming exercise or bug fix). See [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities] to understand a successfull teamwork and interplay of project, mentors and students.

-----

=== Template ===

==== 1. Contact details ====
* Name and surname:
* Nickname:
* Country:
* Email:
* Phone (we will not call you, unless you will become unreachable by email/IM for more than a week without warning):
* Public repository/ies:
* Personal blog (optional):
* Twitter/Identica/LinkedIn/others:

==== 2. Your idea ====
* OSGeo or guest software:
* Title: (please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")
* Brief description of the idea. e.g. "My project will focus on xxx".
* The state of the software BEFORE your GSoC. For example, if you want to make a GUI, you can say: "In the software XYZ, when I want to use the tool xxx, I have to manually edit the file yyy. "
* The addition that your project will bring to the software. In the same example: "With the GUI that I intend to create, it will be possible to use the tool xxx via graphical user interface".
* Future developments. How can your project be expanded or maintained after GSoC is over.

==== 3. Timeline ====
* Now split your project idea in smaller tasks. Quantify the time you think each task needs. Finally, draw a detailed project plan (timeline) including the dates covering all period of GSoC. Don’t forget to include also the days in which you don’t plan to code, because of exams, holidays etc.
* 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?

==== 4. Studies ====
* What is your School and degree?
* Would your application contribute to your ongoing studies/degree? If so, how?

==== 5. Programming and GIS ====
* Computing experience: operating systems you use on a daily basis, known programming languages, hardware, ecc.
* GIS experience as a user:
* GIS programming and other software programming:

==== 6. GSoC participation ====
* Have you participated to GSoC before?
* How many times, which year, which project?
* Have you applied but were not selected? When?
* Have you submitted/will you submit another proposal for GSoC 2016 to a different org?

== What to expect after application ==

Now that you have submitted your application, it's time for you to set up your development environment and get familiar with the code of the software you want to develop for. Ask the developers to test you with a small coding task, or browse the bug tracker and submit a patch for a bug.

=== Bonding period ===

Bonding period does not mean relax. During bonding period, you are supposed to do all preparation in order to be able to start coding immediately the first week of actual coding period. These activities entail:
* set up your dev environment: compile the source code, etc;
* getting familiar with the source code, the dev documentation, programming manual and all the material that your mentors suggest;
* scratching and pseudocoding your project;
* set up your repository, familiarize with version control systems such as git / svn etc;
* set up your wiki page, where you will describe your project and keep track of your weekly progresses;
* get in touch with the community: introduce yourself in soc and dev mailing list, introduce your project and receive feedback.

== What to expect during the summer ==

=== Be prepared to be in constant communication with your mentors and project ===

You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to 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 ===

Every week, by Sunday, we expect to see a report posted to the soc@osgeo and the developer mailing list of your project, 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.

Please explicitly mention your project in the subject and in the introduction to the e-mail.

'''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 on IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's OK. 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 ;)

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

=== Code repository and documentation ===

Publishing your progress online and publicly is a GSoC requirement. Therefore, all students have to decide, before GSoC coding period starts, where to publish the code they will write. We ask students to give the link to the public repository in the first weekly report.

The possibilities are:
* get a sandbox in your software project's repository (your mentor will tell you how to get write access)
* work on a branch of the main code repository (for centralized versioning systems like SVN)
* work on a fork of the code repository (for DCVS like Mercurial and Git)
* work on an independent codebase (if you are developing a plugin or some other extra functionality that is not yet part of main codebase)

Your mentor is the best guide regarding this choice. Please discuss it as soon as possible, and learn how to use the related version control tool well before GSoC coding starts.

Documentation of your code is important! Don't leave all documentation writing to the last weeks of GSoC. It makes sense to outline it at the beginning of coding period, then refine it while you code. It is an important support to coding, as it is a mirror of the overall plan for the summer, and an essential source of information for who will use your code.

=== 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. Alternatives may be code repositories with wiki/blog functionality like [https://github.com/ GitHub], [https://about.gitlab.com/ GitLab] or [https://bitbucket.org/ Bitbucket].

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 OSGeo-of-code 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.'')

== How to get in contact via IRC ==

Primary channel:

* irc://irc.freenode.net/#osgeo (Web based [http://webchat.freenode.net IRC client]) 

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
* https://gitter.im/pgRouting/pgrouting
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#qgis
* irc://irc.freenode.net/#udig
* irc://irc.freenode.net/#geonode

[[Category: Google Summer of Code]]

Google Summer of Code Recommendations for Students

2017-03-10T10:10:50Z

Wiki-Epifanio: /* RTFM */

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://summerofcode.withgoogle.com/]] @ 
[[Image:OSGeo_300_127_pixel.png|300px|link=http://www.osgeo.org]]
</center>

-----
* Back to the main OSGeo [[Google Summer of Code 2017]] wiki page.
* Check out the [[Google_Summer_of_Code_2017_Ideas | Ideas web page]] or propose your own!

-----

== How to get in contact with your potential mentors ==

Since OSGeo is an umbrella organisation for multiple project communities, each community has their own discussion and development [[Mailing Lists]].

'''OSGeo mailing lists of interest for GSoC 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)
:* The dedicated dev mailing list of the software you intend to develop for (Browse http://lists.osgeo.org)

* To contact OSGeo's GSoC admin team directly:
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]

== How to increase your chances of being selected ==

If you put yourself in the shoes of the mentor that should select the student, you'll immediately realize that there are some behaviours that are usually rewarded. Here's some examples.

=== Be proactive ===

* Mentors are more likely to select students that openly discuss the existing ideas and / or propose their own. It is a '''bad idea''' to just submit your idea only in the Google web site without discussing it, because it won't be noticed. Mentors and developers discuss ideas mostly in [[Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_mailing_lists | mailing lists]].
* It is a '''bad idea''' just listing your programming skills and waiting for the mentors to guide you towards next steps. Mentors reward students that show genuine interest in the projects they are willing to develop, propose improvements on their own and make pertinent questions. Remember that it is up to you, and not to the mentor, decide the software you want to work on and the idea to develop. It is not the mentor's job to do that for you.
* It is a '''good idea''' to engage the individual dev lists and find a community that you are interested in working with and start building a relationship with that community. It is the community that decides which of the candidates they want to back, based on the value of the project, and whether or not they think the student will be successful.

=== Demonstrate your skills ===

Consider that mentors are being contacted by several students that apply for the same project. A way to show that you are the best candidate, is to demonstrate that you are familiar with the software and you can code. How? Browse the bug tracker, fix some bugs and propose your patch in mailing list, and/or ask mentors to challenge you! Moreover, bug fixes are a great way to get familiar with the code.

=== Demonstrate your intention to stay ===

Students that are likely to disappear after GSoC are less likely to be selected. This is because there is no point in developing something that won't be maintained. And moreover, one scope of GSoC is to bring new developers to the community.

=== [http://xkcd.com/293/ RTFM] ===

Read the relevant information about GSoC in the wiki / web pages before asking. Most FAQs have been answered already!
* OSGeo Wiki pages related to GSoC can be browsed from [http://wiki.osgeo.org/wiki/Category:Google_Summer_of_Code Category:Google Summer of Code].
* [https://developers.google.com/open-source/gsoc/resources/ Full documentation about GSoC on official website].
* [https://summerofcode.withgoogle.com/rules/ GSoC Rules]
* [https://developers.google.com/open-source/gsoc/faq FAQ from GSoC web site].
* A group of past GSoC students, mentors, and Googlers have prepared this short book just for you: [https://flossmanuals.net/GSoCStudentGuide/ The Student's Guide to the Summer of Code]
* If you are new to OSGeo, take the time to familiarize with the [http://www.osgeo.org/content/foundation/about.html Open Source Geospatial Foundation]

== Application instructions ==

We welcome students to contact relevant developer communities within OSGeo umbrella before submitting their application into GSoC official website. If in doubt for which project(s) to contact, send the mail to both soc and discuss mailing lists.
We recommend browsing past years' ideas pages, to look for ready-to-use projects, and to get an idea of the expected amount of work for a valid GSoC proposal.
Developers will then assist students in filling the proposal template (see below) and will prepare a small coding test (programming exercise or bug fix). See [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities] to understand a successfull teamwork and interplay of project, mentors and students.

-----

=== Template ===

==== 1. Contact details ====
* Name and surname:
* Nickname:
* Country:
* Email:
* Phone (we will not call you, unless you will become unreachable by email/IM for more than a week without warning):
* Public repository/ies:
* Personal blog (optional):
* Twitter/Identica/LinkedIn/others:

==== 2. Your idea ====
* OSGeo or guest software:
* Title: (please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")
* Brief description of the idea. e.g. "My project will focus on xxx".
* The state of the software BEFORE your GSoC. For example, if you want to make a GUI, you can say: "In the software XYZ, when I want to use the tool xxx, I have to manually edit the file yyy. "
* The addition that your project will bring to the software. In the same example: "With the GUI that I intend to create, it will be possible to use the tool xxx via graphical user interface".
* Future developments. How can your project be expanded or maintained after GSoC is over.

==== 3. Timeline ====
* Now split your project idea in smaller tasks. Quantify the time you think each task needs. Finally, draw a detailed project plan (timeline) including the dates covering all period of GSoC. Don’t forget to include also the days in which you don’t plan to code, because of exams, holidays etc.
* 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?

==== 4. Studies ====
* What is your School and degree?
* Would your application contribute to your ongoing studies/degree? If so, how?

==== 5. Programming and GIS ====
* Computing experience: operating systems you use on a daily basis, known programming languages, hardware, ecc.
* GIS experience as a user:
* GIS programming and other software programming:

==== 6. GSoC participation ====
* Have you participated to GSoC before?
* How many times, which year, which project?
* Have you applied but were not selected? When?
* Have you submitted/will you submit another proposal for GSoC 2016 to a different org?

== What to expect after application ==

Now that you have submitted your application, it's time for you to set up your development environment and get familiar with the code of the software you want to develop for. Ask the developers to test you with a small coding task, or browse the bug tracker and submit a patch for a bug.

=== Bonding period ===

Bonding period does not mean relax. During bonding period, you are supposed to do all preparation in order to be able to start coding immediately the first week of actual coding period. These activities entail:
* set up your dev environment: compile the source code, etc;
* getting familiar with the source code, the dev documentation, programming manual and all the material that your mentors suggest;
* scratching and pseudocoding your project;
* set up your repository, familiarize with version control systems such as git / svn etc;
* set up your wiki page, where you will describe your project and keep track of your weekly progresses;
* get in touch with the community: introduce yourself in soc and dev mailing list, introduce your project and receive feedback.

== What to expect during the summer ==

=== Be prepared to be in constant communication with your mentors and project ===

You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to 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 ===

Every week, by Sunday, we expect to see a report posted to the soc@osgeo and the developer mailing list of your project, 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.

Please explicitly mention your project in the subject and in the introduction to the e-mail.

'''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 on IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's OK. 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 ;)

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

=== Code repository and documentation ===

Publishing your progress online and publicly is a GSoC requirement. Therefore, all students have to decide, before GSoC coding period starts, where to publish the code they will write. We ask students to give the link to the public repository in the first weekly report.

The possibilities are:
* get a sandbox in your software project's repository (your mentor will tell you how to get write access)
* work on a branch of the main code repository (for centralized versioning systems like SVN)
* work on a fork of the code repository (for DCVS like Mercurial and Git)
* work on an independent codebase (if you are developing a plugin or some other extra functionality that is not yet part of main codebase)

Your mentor is the best guide regarding this choice. Please discuss it as soon as possible, and learn how to use the related version control tool well before GSoC coding starts.

Documentation of your code is important! Don't leave all documentation writing to the last weeks of GSoC. It makes sense to outline it at the beginning of coding period, then refine it while you code. It is an important support to coding, as it is a mirror of the overall plan for the summer, and an essential source of information for who will use your code.

=== 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. Alternatives may be code repositories with wiki/blog functionality like [https://github.com/ GitHub], [https://about.gitlab.com/ GitLab] or [https://bitbucket.org/ Bitbucket].

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 OSGeo-of-code 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.'')

== How to get in contact via IRC ==

Primary channel:

* irc://irc.freenode.net/#osgeo (Web based [http://webchat.freenode.net IRC client]) 

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
* https://gitter.im/pgRouting/pgrouting
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#qgis
* irc://irc.freenode.net/#udig
* irc://irc.freenode.net/#geonode

[[Category: Google Summer of Code]]

GitServiceRequirement

2016-09-01T08:55:39Z

Wiki-Epifanio:

Requirements for a Git service offered by OSGeo, useful to evaluate possible solutions (see [[GitInfrastructureComparison]])

Please add your name to the ones that are important to you, and add more items if needed.

# '''Sign in using OSGeo Userid'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Autonomously create and manage teams'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Autonomously create and manage repositories'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Create private repositories (for software vulnerability testing, etc.)'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:Tomkralidis|tomkralidis]] ([[User talk:Tomkralidis|tomkralidis]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Import tickets from Trac'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Import tickets from Redmine'''
# '''Comment tickets via email'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:34, 27 April 2016 (PDT)
# '''Comment/close tickets via commit log'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:34, 27 April 2016 (PDT)
# '''SVN->GIT sync - (Mirroring existing SVN repository)''' see:[https://trac.osgeo.org/osgeo/ticket/1654 /ticket/1654]
## --[[User:Epifanio|epifanio]] ([[User talk:Epifanio|talk]]) 04:49, 01 September 2016 (PDT)
Add a new item if your requirement is missing

[[Category:Infrastructure]]

GitServiceRequirement

2016-09-01T08:53:31Z

Wiki-Epifanio:

Requirements for a Git service offered by OSGeo, useful to evaluate possible solutions (see [[GitInfrastructureComparison]])

Please add your name to the ones that are important to you, and add more items if needed.

# '''Sign in using OSGeo Userid'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Autonomously create and manage teams'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Autonomously create and manage repositories'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Create private repositories (for software vulnerability testing, etc.)'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:Tomkralidis|tomkralidis]] ([[User talk:Tomkralidis|tomkralidis]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Import tickets from Trac'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Import tickets from Redmine'''
# '''Comment tickets via email'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:34, 27 April 2016 (PDT)
# '''Comment/close tickets via commit log'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:34, 27 April 2016 (PDT)
# '''SVN->GIT sync - (Mirroring existing SVN repository)'''
## --[[User:Epifanio|epifanio]] ([[User talk:Epifanio|talk]]) 04:49, 01 September 2016 (PDT)
Add a new item if your requirement is missing

[[Category:Infrastructure]]

GitServiceRequirement

2016-09-01T08:52:58Z

Wiki-Epifanio:

Requirements for a Git service offered by OSGeo, useful to evaluate possible solutions (see [[GitInfrastructureComparison]])

Please add your name to the ones that are important to you, and add more items if needed.

# '''Sign in using OSGeo Userid'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Autonomously create and manage teams'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Autonomously create and manage repositories'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Create private repositories (for software vulnerability testing, etc.)'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:Tomkralidis|tomkralidis]] ([[User talk:Tomkralidis|tomkralidis]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Import tickets from Trac'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Import tickets from Redmine'''
# '''Comment tickets via email'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:34, 27 April 2016 (PDT)
# '''Comment/close tickets via commit log'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:34, 27 April 2016 (PDT)
# "SVN->GIT sync - (Mirroring existing SVN repository)"
## --[[User:Epifanio|epifanio]] ([[User talk:Epifanio|talk]]) 04:49, 01 September 2016 (PDT)
Add a new item if your requirement is missing

[[Category:Infrastructure]]

GitServiceRequirement

2016-09-01T08:51:40Z

Wiki-Epifanio:

Requirements for a Git service offered by OSGeo, useful to evaluate possible solutions (see [[GitInfrastructureComparison]])

Please add your name to the ones that are important to you, and add more items if needed.

# '''Sign in using OSGeo Userid'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Autonomously create and manage teams'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Autonomously create and manage repositories'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Create private repositories (for software vulnerability testing, etc.)'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:Tomkralidis|tomkralidis]] ([[User talk:Tomkralidis|tomkralidis]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Import tickets from Trac'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Import tickets from Redmine'''
# '''Comment tickets via email'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:34, 27 April 2016 (PDT)
# '''Comment/close tickets via commit log'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:34, 27 April 2016 (PDT)
# "SVN->GIT sync - (Mirroring existing SVN repository)"
## --[[User:Epifanio|epifanio]] - 04:49, 01 September 2016 (PDT)
Add a new item if your requirement is missing

[[Category:Infrastructure]]

GitServiceRequirement

2016-09-01T08:49:56Z

Wiki-Epifanio:

Requirements for a Git service offered by OSGeo, useful to evaluate possible solutions (see [[GitInfrastructureComparison]])

Please add your name to the ones that are important to you, and add more items if needed.

# '''Sign in using OSGeo Userid'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Autonomously create and manage teams'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Autonomously create and manage repositories'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Create private repositories (for software vulnerability testing, etc.)'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:Tomkralidis|tomkralidis]] ([[User talk:Tomkralidis|tomkralidis]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Import tickets from Trac'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Import tickets from Redmine'''
# '''Comment tickets via email'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:34, 27 April 2016 (PDT)
# '''Comment/close tickets via commit log'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:34, 27 April 2016 (PDT)
# "SVN->GIT sync - (Mirroring existing SVN repository)"
## --[[User:Epifanio|epifanio]] ([[User talk:Epifanio|epifanio]]) 04:49, 01 September 2016 (PDT)
Add a new item if your requirement is missing

[[Category:Infrastructure]]

GitServiceRequirement

2016-09-01T08:49:20Z

Wiki-Epifanio:

Requirements for a Git service offered by OSGeo, useful to evaluate possible solutions (see [[GitInfrastructureComparison]])

Please add your name to the ones that are important to you, and add more items if needed.

# '''Sign in using OSGeo Userid'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Autonomously create and manage teams'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Autonomously create and manage repositories'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Create private repositories (for software vulnerability testing, etc.)'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:Tomkralidis|tomkralidis]] ([[User talk:Tomkralidis|tomkralidis]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Import tickets from Trac'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:01, 27 April 2016 (PDT)
## --[[User:kalxas|kalxas]] ([[User talk:kalxas|kalxas]]) 12:00, 06 June 2016 (UTC)
# '''Import tickets from Redmine'''
# '''Comment tickets via email'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:34, 27 April 2016 (PDT)
# '''Comment/close tickets via commit log'''
## --[[User:Strk|strk]] ([[User talk:Strk|talk]]) 06:34, 27 April 2016 (PDT)
# "SVN->GIT sync - (Mirroring existing SVN repository)"
## --[[User:Eifanio|epifanio]] ([[User talk:Epifanio|epifanio]]) 04:49, 01 September 2016 (PDT)
Add a new item if your requirement is missing

[[Category:Infrastructure]]

User:Epifanio

2016-05-27T07:12:08Z

Wiki-Epifanio:

{{OSGeo Member
|Name=Massimo Di Stefano
|Address=Eboli, Salerno, Italy
|Country=Italy
|City=Eboli
|Coordinate=40.61694, 15.05639
|LocalChapter=GFOSS.it
|Email=epiesasha@me.com
|InstantMessaging=Skype : epifaniox;
|Website=http://ccom.unh.edu/user/distefano
|Photo=Epi.png
|Info=Massimo Di Stefano, graduated from "Università degli Studi di Napoli "Parthenope"" (Naples, IT) with a Master's Degree in Environmental Science, specializing in Marine Ecosystem. Massimo is now pursuing his Ph.D. at CCOM-JHC in Oceanography. A founding member of [http://gfoss.it/drupal/ GFOSS.it], the Italian community of users and developers of Geographic Free/Open-Source Software (GFOSS) and charter member of OSGeo, Massimo has spent more than 10 years developing Geographical Free and Open Source Software, with current development activities in [http://grass.osgeo.org/ GRASS], [http://trac.osgeo.org/ossim OSSIM], [http://www.qgis.org/en/site/ QGIS] and [http://live.osgeo.org/en/index.html OSGeo Live] projects. For the past four years, Massimo worked as Research Assistant III at the Woods Hole Oceanographic Institute (WHOI) for the HABCAM project, and as Software Engineer on staff at the Tetherless World Constellation (RPI) on the ECO-OP project.
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=Yes
|Translate=No
|PSC=No
|ExBoard=No
|Charter=Yes
|Chair=No
|SolKatz=No
|Committer=No
}}
{{OSGeo Member FormEdit}}
__NOTOC__
=== [http://tw.rpi.edu/web/person/MassimoDiStefano | Massimo Di Stefano] ===
[[File:Epi.png|thumb|right|100px|Massimo Di Stefano]]

Massimo Di Stefano, graduated from "Università degli Studi di Napoli "Parthenope"" (Naples, IT) with a Master's Degree in Environmental Science, specializing in Marine Ecosystem. Massimo is now pursuing his Ph.D. at CCOM-JHC in Oceanography. A founding member of [http://gfoss.it/drupal/ GFOSS.it], the Italian community of users and developers of Geographic Free/Open-Source Software (GFOSS) and charter member of OSGeo, Massimo has spent more than 10 years developing Geographical Free and Open Source Software, with current development activities in [http://grass.osgeo.org/ GRASS], [http://trac.osgeo.org/ossim OSSIM], [http://www.qgis.org/en/site/ QGIS] and [http://live.osgeo.org/en/index.html OSGeo Live] projects. For the past four years, Massimo worked as Research Assistant III at the Woods Hole Oceanographic Institute (WHOI) for the HABCAM project, and as Software Engineer on staff at the Tetherless World Constellation (RPI) on the ECO-OP project.

;OSGeo Experience [[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]] [[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]] [[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]]

* PhD Candidate in Oceanography at Center for Coastal and Ocean Mapping CCOM - University of New Hampshire
* Software Engineer at [http://tw.rpi.edu/web/person/MassimoDiStefano RPI] (Renssellaer Polytechnic Institute)
* Guest Investigator at [http://www.whoi.edu/profile.do?id=mdistefano WHOI] (Woods Hole Oceanographic Institution)
* GIS Team member of [http://www.geofemengineering.it GeofemEngineering]
* Cartography and Geodesy Specialist
* Member of the [http://www.ossim.org OSSIM] Dev-Team
* Promoting Free Software
* [http://www.ossim.org Ossim],[http://grass.itc.it/ Grass], and [http://www.qgis.org/ Qgis] development
* [http://www.gfoss.it gfoss.it] Founder
* [http://trac.osgeo.org/ossim/wiki/GoogleSummerOfCode OSGEO-Google Summer Of Code]
* [[italiano | Italian OSGeo Board]] Member
* Italian Osgeo Liason Officer ([[italiano]])
* [http://live.osgeo.org/en/index.html OSGeo-Live] contributor
* Translating the OSGeo [http://www.osgeo.org official site] into Italian

'''Contact'''

: [mailto:epiesasha@me.com epiesasha@me.com]
: IRC : '''epifanio'''
: Skype : '''epifaniox'''

; Location 1
: [http://stable.toolserver.org/geohack/geohack.php?params=41_31_27.12_N_70_40_11.28_W 41°31′27.12″N 70°40′11.28″W]
: Woods Hole, Massachussetts, USA

; Location 2
: [http://stable.toolserver.org/geohack/geohack.php?params=40_37_01_N_15_03_23_E 40°37′1″N 15°3′23″E]
: Eboli, Salerno, Italy

; UTC (GMT) offset 1
: Standard time zone: UTC/GMT -5 hours ([http://www.timeanddate.com/worldclock/city.html?n=43 details])
: Daylight saving time: +1 hour (northern hemisphere summer time)

; UTC (GMT) offset 2
: Standard time zone: UTC/GMT +1 hour ([http://www.timeanddate.com/worldclock/city.html?n=215 details])
: Daylight saving time: +1 hour (northern hemisphere summer time)

[http://24timezones.com/usa_time/ma_barnstable/woods_hole.htm time-zone-spec]

; Web logs and more
: http://web.me.com/epiesasha/PlanetSasha/Project.html

-->

[[Category:OSGeo Advocate]]

UNTraining

2016-04-15T17:17:42Z

Wiki-Epifanio: /* Open Source Geospatial Notebooks */

'''Welcome to the UN training page'''

GeoForAll is supporting UN in their migration to geospatial open source applications. In this page we list the training material available for some products that UN will use. Please add your training material here, putting also the reference to all data used in such a way that everybody in using your material can be autonomous.

== QGIS ==

* Official manual + training manual: http://docs.qgis.org - Point of contact: QGIS Project Steering Committee

*'''FOSS4G GeoAcademy Curriculum''' - 35 hands-on labs written primarily for QGIS with some cross over with GRASS and Inkscape. Labs are aligned to the Geospatial Technology Competency Model. Development was sponsored by a Department of Labor Grant and is released under Creative Commons Attribute 3.0 Unported license. All labs currently written for QGIS 2.8, but we are about to release labs for QGIS 2.14. In addition to labs, lecture material is also developed and being uploaded. All lab instructions and data are [http://spatialquerylab.com/foss4g-academy-curriculum/ available online on our lab website].
**'''Link to material''': http://spatialquerylab.com/foss4g-academy-curriculum/
**'''Lab''': Spatial {Query} Lab - http://www.spatialquerylab.com
**'''Point of Contact''': Rick Smith - Richard.Smith@tamucc.edu
**'''Mailing Address''': 6300 Ocean Dr., Unit 5868, Corpus Christi, TX 78412-5868, USA

Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact

== gvSIG ==

gvSIG is a powerful, user-friendly and interoperable GIS. It is easy to work in a variety of formats, vector and raster files, databases and remote services. There are always available all kinds of tools to analyze and manage geographic information.

gvSIG Desktop is designed to be an easily extensible solution, allowing thus continually improving the software application and developing tailor made solutions. It is open source software, GNU / GPL license, this makes its free use, distribution, study and improvement. gvSIG Desktop integrates NASA World Wind, so it allows to work with 3D Views.

gvSIG Online is an Open Source solution for Spatial Data Infrastructures. It is an integral platform for the Spatial Data Infrastructure (SDI) implementation, 100% open source software. A fast and powerful solution for start up the infrastructure necessary to manage spatial data in an organization in an efficient way.

*Website: http://www.gvsig.com
** [http://www.gvsig.com/en/diffusion/educational-material?p_p_id=122_INSTANCE_A9eo37KAqtxs&p_p_lifecycle=0&p_p_state=normal&p_p_mode=view&p_p_col_id=column-2&p_p_col_count=1&p_r_p_564233524_resetCur=true&p_r_p_564233524_categoryId=25973 Educational material in English]
** [http://web.gvsig-training.com/index.php/en/quienes-somos-2/noticias-2/145-the-free-mooc-cycle-gvsig-for-users Free MOOC cycle "gvSIG for Users"]
** '''Point of Contact''': Mario Carrera - mcarrera [at] gvsig.com
* [https://www.youtube.com/user/gvsig gvSIG Youtube Channel]

== GRASS GIS ==

Geographic Resources Analysis Support System, commonly referred to as GRASS GIS, is a Geographic Information System (GIS) used for data management, image processing, graphics production, spatial modelling, and visualization of many types of data. URL: https://grass.osgeo.org

*'''NCSU Geospatial Analysis and Modeling course''' - 13 hands-on labs exercises used at North Carolina State University for teaching geospatial analysis and modeling with focus on terrain analysis, continuous surfaces, interpolation, geomorphometry, hydrology and erosion. We tested the exercises with GRASS GIS 7.0 and we update the material with every new release and academic semester. The material is released under Creative Commons Attribution-ShareAlike 4.0 International license (CC BY-SA 4.0) and the material is [https://github.com/ncsu-osgeorel/geospatial-modeling-course developed openly]. The course also includes software-independent lectures which are available online as recorded videos and presentations slides.
**'''Link to material''': http://ncsu-osgeorel.github.io/geospatial-modeling-course/grass/
**'''Lab''': NCSU OSGeoREL - https://geospatial.ncsu.edu/osgeorel
**'''Point of Contact''': Helena Mitasova - hmitaso@ncsu.edu
**'''Mailing Address''': 2800 Faucette Drive, North Carolina State University, Raleigh, NC 27695-8208, USA
*'''Workshop on urban growth modeling with FUTURES''' - A day long tutorial on GRASS GIS and urban growth modeling using the FUTURES model tested with GRASS GIS 7.0. The material is dual licensed under Creative Commons Attribution-ShareAlike 4.0 International license (CC BY-SA 4.0) and GNU Free Documentation License 1.2.
**'''Link to material''': https://grasswiki.osgeo.org/wiki/Workshop_on_urban_growth_modeling_with_FUTURES
**'''Lab''': NCSU OSGeoREL - https://geospatial.ncsu.edu/osgeorel
**'''Point of Contact''': Anna Petrasova - akratoc@ncsu.edu
**'''Mailing Address''': 2800 Faucette Drive, North Carolina State University, Raleigh, NC 27695-8208, USA

== GeoServer ==

GeoServer is an open source server for sharing geospatial data. Designed for interoperability, it publishes data from any major spatial data source using open standards.

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://workshops.boundlessgeo.com/geoserver-intro/ Introduction to GeoServer]
**'''Link to Material''': [http://workshops.boundlessgeo.com/suiteintro/ Introduction to Suite]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

*'''GeoSolutions Workshops''': [http://www.geo-solutions.it Website]
** '''Link to Material''': [http://geoserver.geo-solutions.it/edu/en/ GeoServer general training, four days worth of training material, from the first steps to production deploy setups, performance optimization and the like]
** '''Link to Material''': [http://geoserver.geo-solutions.it/multidim/en/ Spatio-temporal data handling with GeoServer]
** '''Link to Material''': [http://geoserver.geo-solutions.it/complexfeatures/ Complex features support and mapping with Hale]
** '''Point of Contact''': Andrea Aime - [mailto:andrea.aime@geo-solutions.it andrea.aime@geo-solutions.it]

*'''GeoServer Users Guide''': [http://docs.geoserver.org/latest/en/user/ Website]
**'''Link to Material''': [http://docs.geoserver.org/latest/en/user/extensions/css/workshop/index.html CSS styling workshop]
**'''Point of Contact''': Mike Pumphrey - [mailto:mike@boundlessgeo.com mike@boundlessgeo.com]

== OpenLayers ==

OpenLayers is a high-performance, feature-packed library for all your mapping needs.

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://workshops.boundlessgeo.com/openlayers3/ Introduction to OpenLayers]
**'''Link to Material''': [http://workshops.boundlessgeo.com/suiteintro/ Introduction to Suite]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

== PostgreSQL ==

Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact

== PostGIS ==

PostGIS is a spatial database extender for PostgreSQL object-relational database. It adds support for geographic objects allowing location queries to be run in SQL.

*''' University of Colorado Denver FOSS4G Lab''': [http://geospatial.ucdenver.edu/foss4g/ CU Denver FOSS4G Lab]
**'''PostgreSQL-PostGIS Tutorial Series''' Series of 7 tutorials covering the basics of PostGIS for spatial data handling and analysis.
**'''Link to material''': [http://geospatial.ucdenver.edu/foss4g/training/tutorials PostgreSQL-PostGIS Tutorials]
**'''Point of Contact''': Rafael Moreno - Rafael.Moreno@ucdenver.edu

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://workshops.boundlessgeo.com/postgis-intro/ Introduction to PostGIS]
**'''Link to Material''': [http://workshops.boundlessgeo.com/suiteintro/ Introduction to Suite]
**'''Link to Material''': [http://workshops.boundlessgeo.com/postgis-spatialdbtips/ Spatial Database Tips & Tricks]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

== GeoGig ==

GeoGig is an open source tool that draws inspiration from Git, but adapts its core concepts to handle distributed versioning of geospatial data.

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://geogig.org/workshop/ GeoGig Workshop]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

== GeoNode ==

GeoNode is a web-based application and platform for developing geospatial information systems (GIS) and for deploying spatial data infrastructures (SDI).

**'''Email List''': [http://lists.osgeo.org/mailman/listinfo/geonode-users geonode-users] and [http://lists.osgeo.org/mailman/listinfo/geonode-dev geonode-dev]
* Website: http://geonode.org
** Demo: http://demo.geonode.org
**'''Link to material''': http://docs.geonode.org/en/latest/index.html
**'''Point of Contact''': Vivien Deparday - [mailto:vdeparday@worldbank.org vdeparday@worldbank.org], Ariel Núñez - [mailto:ingenieroariel@gmail.com ingenieroariel@gmail.com], Paolo Corti - [mailto:pcorti@fas.harvard.edu pcorti@fas.harvard.edu]

== Rasdaman ==

*'''[http://www.rasdaman.org rasdaman]'''
**'''Big Geo Data Lab''' - Spatio-temporal sensor, image, simulation, and statistics data of unlimited size are served rapidly by rasdaman ("raster data manager"). As a multiparallel, distributed analytics engine, rasdaman achieves unparalleled service flexibility, scalability, and performance. Being OGC [http://en.wikipedia.org/wiki/Web_Coverage_Processing_Service WCPS] and [http://en.wikipedia.org/wiki/Web_Coverage_Service WCS] Core Reference Implementation, rasdaman enables access, subsetting, and processing on the fly using open standards interfaces. The WCS suite is a central cornerstone for SDIs: a large, growing number of open-source and proprietary tools supports it (MapServer, GeoServer, OpenLayers, QGIS, ESRI ArcGIS, ...) and the OGC standards are under adoption by ISO (as forthcoming 19123-2) and INSPIRE ("Coverage Download Service"). Significant training material is available already, and is being augmented continuously:
**'''Link to material''': [http://rasdaman.org/wiki/Workshops OGC Big Geo Data standards and rasdaman workshops] | [http://standards.rasdaman.com/ hands-on lab on Big Data Standards] | [http://kahlua.eecs.jacobs-university.de/~lsis/Big-Earth-Data_the-ARTE-Movie/index.php Big Earth Data] (53min TV documentary)
**'''Point of Contact''': Peter Baumann - baumann@rasdaman.com

== OSGeo-Live ==

OSGeo-Live contains 50 of the best geospatial applications, pre-installed with datasets, along with project overviews and 10 to 15 minute quickstarts for each application and ~ 45 minute presentation of them all. The documentation provides an excellent high level overview of the breadth of geospatial open source applications. It is also used as a plaform for many open source geospatial workshops.

* Project Overviews and Quickstarts: http://live.osgeo.org/en/overview/overview.html
* Presentation: http://live.osgeo.org/en/presentation/index.html#/
* Contact: Cameron Shorter <cam e r onDoTs hort erA T g mai l.com>

*'''Bringing GEOSS services into practice'''
The "Bringing GEOSS services into practice" workshop aims at teaching how to configure, use and deploy a set of open source software (PostGIS, GeoServer, GeoNetwork, PyWPS, QGIS) to set up a spatial data infrastructure (SDI). Trainees will learn how to publish and share data and metadata using OGC and ISO standards and how to register services into the Global Earth Observation System of Systems (GEOSS).

Website: http://www.geossintopractice.org

Lab: GeoForAll - ISE, University of Geneva: http://www.unige.ch/tigers/fr/autres-reseaux/geoforall/

Contact: Gregory Giuliani <gregory.giuliani AT unige.ch>

== GeoMOOSE ==

GeoMOOSE is a Web Client JavaScript Framework for displaying distributed cartographic data. GeoMOOSE has a number of strengths including modularity, configurability, and delivers a number of core functionalities in its packages. GeoMOOSE is also very light weight for servers making it easy to handle a large number of users, with a large number of layers, and a large number of services without stressing a server.

The GeoMOOSE core is written using JavaScript and HTML. It is entirely possible to run GeoMOOSE with nothing more than a basic web server (Nginx, Apache, IIS). But besides the basic client core, GeoMOOSE also comes prepackaged with a number of built in services written in PHP. These services add the ability to perform drill-down identify operations, selection operations, and search data sets. If you have existing scripts that perform similar functions, GeoMOOSE can be tuned to work with those services, no matter which language they were written in.

* Website: http://www.geomoose.org
** Online Demo: http://demo.geomoose.org/master/
** Package download (includes operating demo with sample data): http://geomoose.org/download.html
** GeoMOOSE is also compatible with MS4W.
** Link to material: Training materials are included in the download package as an operating demo.
*** Workshop materials: http://www.geomoose.org/downloads/workshops/foss4gna-2013/
**** NOTE: Newer version will be available by May 15th, 2016
*** The OSGeo Live page for GeoMOOSE includes the Overview and Quickstart:
**** http://live.osgeo.org/en/quickstart/geomoose_quickstart.html
**** http://live.osgeo.org/en/overview/geomoose_overview.html
** Contact: Bob Basques <bbasques AT sharedgeo.org>

== GET-IT ==

'''GET-IT''' - Geoinformation Enabling ToolkIT starterkit, supports researchers and professional in the creation of autonomous, distributed nodes of a Spatial Data Infrastructure and uploading research results in the form of maps/observations (and related metadata). GET-It supports domain researchers and professional in the creation of OGC standard services like WMS, WFS, WCS, CSW, and SOS. GET-It is based on GeoNode, contains pyCSW, 52° North SOS Server, Geoserver, PostgreSQL, PostGIS, OpenLayers and also contains EDI, a general purpose, customizable, template-driven metadata editor. The suite is the first open-source collaborative effort toward the integration of traditional geographic information with observational data.

*'''GET-IT Website''': http://www.get-it.it/
**'''EDI Website''': http://edidemo.get-it.it/
**'''Docs''': http://getit.readthedocs.org/en/latest/
**'''Demo''': http://demo2.get-it.it/
**'''Code''': https://github.com/SP7-Ritmare/starterkit
**'''Lab''': 103 IREA-CNR - http://www.irea.cnr.it/
**'''Point of Contact''': Alessandro Oggioni - oggioni.a@irea.cnr.it

==Open Source Geospatial Notebooks==
'''OSGeo-Notebooks''' - Development of interactive educational material in the form of geospatial notebooks based on the [http://jupyter.org/ Jupyter project].
This project is in active development, do not hesitate to contact me If interested in the integration of existing educational materials in the form of interactive notebooks.

* '''Code:''' https://github.com/epifanio/OSGeospatial-Notebooks
* '''Point of Contact:''' Massimo Di Stefano <epiesasha@me.com>

UNTraining

2016-04-15T16:41:14Z

Wiki-Epifanio: /* Open Source Geospatial Notebooks */

'''Welcome to the UN training page'''

GeoForAll is supporting UN in their migration to geospatial open source applications. In this page we list the training material available for some products that UN will use. Please add your training material here, putting also the reference to all data used in such a way that everybody in using your material can be autonomous.

== QGIS ==

* Official manual + training manual: http://docs.qgis.org - Point of contact: QGIS Project Steering Committee

*'''FOSS4G GeoAcademy Curriculum''' - 35 hands-on labs written primarily for QGIS with some cross over with GRASS and Inkscape. Labs are aligned to the Geospatial Technology Competency Model. Development was sponsored by a Department of Labor Grant and is released under Creative Commons Attribute 3.0 Unported license. All labs currently written for QGIS 2.8, but we are about to release labs for QGIS 2.14. In addition to labs, lecture material is also developed and being uploaded. All lab instructions and data are [http://spatialquerylab.com/foss4g-academy-curriculum/ available online on our lab website].
**'''Link to material''': http://spatialquerylab.com/foss4g-academy-curriculum/
**'''Lab''': Spatial {Query} Lab - http://www.spatialquerylab.com
**'''Point of Contact''': Rick Smith - Richard.Smith@tamucc.edu
**'''Mailing Address''': 6300 Ocean Dr., Unit 5868, Corpus Christi, TX 78412-5868, USA

Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact

== gvSIG ==

gvSIG is a powerful, user-friendly and interoperable GIS. It is easy to work in a variety of formats, vector and raster files, databases and remote services. There are always available all kinds of tools to analyze and manage geographic information.

gvSIG Desktop is designed to be an easily extensible solution, allowing thus continually improving the software application and developing tailor made solutions. It is open source software, GNU / GPL license, this makes its free use, distribution, study and improvement. gvSIG Desktop integrates NASA World Wind, so it allows to work with 3D Views.

gvSIG Online is an Open Source solution for Spatial Data Infrastructures. It is an integral platform for the Spatial Data Infrastructure (SDI) implementation, 100% open source software. A fast and powerful solution for start up the infrastructure necessary to manage spatial data in an organization in an efficient way.

*Website: http://www.gvsig.com
** [http://www.gvsig.com/en/diffusion/educational-material?p_p_id=122_INSTANCE_A9eo37KAqtxs&p_p_lifecycle=0&p_p_state=normal&p_p_mode=view&p_p_col_id=column-2&p_p_col_count=1&p_r_p_564233524_resetCur=true&p_r_p_564233524_categoryId=25973 Educational material in English]
** [http://web.gvsig-training.com/index.php/en/quienes-somos-2/noticias-2/145-the-free-mooc-cycle-gvsig-for-users Free MOOC cycle "gvSIG for Users"]
** '''Point of Contact''': Mario Carrera - mcarrera [at] gvsig.com
* [https://www.youtube.com/user/gvsig gvSIG Youtube Channel]

== GRASS GIS ==

Geographic Resources Analysis Support System, commonly referred to as GRASS GIS, is a Geographic Information System (GIS) used for data management, image processing, graphics production, spatial modelling, and visualization of many types of data. URL: https://grass.osgeo.org

*'''NCSU Geospatial Analysis and Modeling course''' - 13 hands-on labs exercises used at North Carolina State University for teaching geospatial analysis and modeling with focus on terrain analysis, continuous surfaces, interpolation, geomorphometry, hydrology and erosion. We tested the exercises with GRASS GIS 7.0 and we update the material with every new release and academic semester. The material is released under Creative Commons Attribution-ShareAlike 4.0 International license (CC BY-SA 4.0) and the material is [https://github.com/ncsu-osgeorel/geospatial-modeling-course developed openly]. The course also includes software-independent lectures which are available online as recorded videos and presentations slides.
**'''Link to material''': http://ncsu-osgeorel.github.io/geospatial-modeling-course/grass/
**'''Lab''': NCSU OSGeoREL - https://geospatial.ncsu.edu/osgeorel
**'''Point of Contact''': Helena Mitasova - hmitaso@ncsu.edu
**'''Mailing Address''': 2800 Faucette Drive, North Carolina State University, Raleigh, NC 27695-8208, USA
*'''Workshop on urban growth modeling with FUTURES''' - A day long tutorial on GRASS GIS and urban growth modeling using the FUTURES model tested with GRASS GIS 7.0. The material is dual licensed under Creative Commons Attribution-ShareAlike 4.0 International license (CC BY-SA 4.0) and GNU Free Documentation License 1.2.
**'''Link to material''': https://grasswiki.osgeo.org/wiki/Workshop_on_urban_growth_modeling_with_FUTURES
**'''Lab''': NCSU OSGeoREL - https://geospatial.ncsu.edu/osgeorel
**'''Point of Contact''': Anna Petrasova - akratoc@ncsu.edu
**'''Mailing Address''': 2800 Faucette Drive, North Carolina State University, Raleigh, NC 27695-8208, USA

== GeoServer ==

GeoServer is an open source server for sharing geospatial data. Designed for interoperability, it publishes data from any major spatial data source using open standards.

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://workshops.boundlessgeo.com/geoserver-intro/ Introduction to GeoServer]
**'''Link to Material''': [http://workshops.boundlessgeo.com/suiteintro/ Introduction to Suite]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

*'''GeoSolutions Workshops''': [http://www.geo-solutions.it Website]
** '''Link to Material''': [http://geoserver.geo-solutions.it/edu/en/ GeoServer general training, four days worth of training material, from the first steps to production deploy setups, performance optimization and the like]
** '''Link to Material''': [http://geoserver.geo-solutions.it/multidim/en/ Spatio-temporal data handling with GeoServer]
** '''Link to Material''': [http://geoserver.geo-solutions.it/complexfeatures/ Complex features support and mapping with Hale]
** '''Point of Contact''': Andrea Aime - [mailto:andrea.aime@geo-solutions.it andrea.aime@geo-solutions.it]

*'''GeoServer Users Guide''': [http://docs.geoserver.org/latest/en/user/ Website]
**'''Link to Material''': [http://docs.geoserver.org/latest/en/user/extensions/css/workshop/index.html CSS styling workshop]
**'''Point of Contact''': Mike Pumphrey - [mailto:mike@boundlessgeo.com mike@boundlessgeo.com]

== OpenLayers ==

OpenLayers is a high-performance, feature-packed library for all your mapping needs.

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://workshops.boundlessgeo.com/openlayers3/ Introduction to OpenLayers]
**'''Link to Material''': [http://workshops.boundlessgeo.com/suiteintro/ Introduction to Suite]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

== PostgreSQL ==

Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact

== PostGIS ==

PostGIS is a spatial database extender for PostgreSQL object-relational database. It adds support for geographic objects allowing location queries to be run in SQL.

*''' University of Colorado Denver FOSS4G Lab''': [http://geospatial.ucdenver.edu/foss4g/ CU Denver FOSS4G Lab]
**'''PostgreSQL-PostGIS Tutorial Series''' Series of 7 tutorials covering the basics of PostGIS for spatial data handling and analysis.
**'''Link to material''': [http://geospatial.ucdenver.edu/foss4g/training/tutorials PostgreSQL-PostGIS Tutorials]
**'''Point of Contact''': Rafael Moreno - Rafael.Moreno@ucdenver.edu

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://workshops.boundlessgeo.com/postgis-intro/ Introduction to PostGIS]
**'''Link to Material''': [http://workshops.boundlessgeo.com/suiteintro/ Introduction to Suite]
**'''Link to Material''': [http://workshops.boundlessgeo.com/postgis-spatialdbtips/ Spatial Database Tips & Tricks]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

== GeoGig ==

GeoGig is an open source tool that draws inspiration from Git, but adapts its core concepts to handle distributed versioning of geospatial data.

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://geogig.org/workshop/ GeoGig Workshop]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

== GeoNode ==

GeoNode is a web-based application and platform for developing geospatial information systems (GIS) and for deploying spatial data infrastructures (SDI).

**'''Email List''': [http://lists.osgeo.org/mailman/listinfo/geonode-users geonode-users] and [http://lists.osgeo.org/mailman/listinfo/geonode-dev geonode-dev]
* Website: http://geonode.org
** Demo: http://demo.geonode.org
**'''Link to material''': http://docs.geonode.org/en/latest/index.html
**'''Point of Contact''': Vivien Deparday - [mailto:vdeparday@worldbank.org vdeparday@worldbank.org], Ariel Núñez - [mailto:ingenieroariel@gmail.com ingenieroariel@gmail.com], Paolo Corti - [mailto:pcorti@fas.harvard.edu pcorti@fas.harvard.edu]

== Rasdaman ==

*'''[http://www.rasdaman.org rasdaman]'''
**'''Big Geo Data Lab''' - Spatio-temporal sensor, image, simulation, and statistics data of unlimited size are served rapidly by rasdaman ("raster data manager"). As a multiparallel, distributed analytics engine, rasdaman achieves unparalleled service flexibility, scalability, and performance. Being OGC [http://en.wikipedia.org/wiki/Web_Coverage_Processing_Service WCPS] and [http://en.wikipedia.org/wiki/Web_Coverage_Service WCS] Core Reference Implementation, rasdaman enables access, subsetting, and processing on the fly using open standards interfaces. The WCS suite is a central cornerstone for SDIs: a large, growing number of open-source and proprietary tools supports it (MapServer, GeoServer, OpenLayers, QGIS, ESRI ArcGIS, ...) and the OGC standards are under adoption by ISO (as forthcoming 19123-2) and INSPIRE ("Coverage Download Service"). Significant training material is available already, and is being augmented continuously:
**'''Link to material''': [http://rasdaman.org/wiki/Workshops OGC Big Geo Data standards and rasdaman workshops] | [http://standards.rasdaman.com/ hands-on lab on Big Data Standards] | [http://kahlua.eecs.jacobs-university.de/~lsis/Big-Earth-Data_the-ARTE-Movie/index.php Big Earth Data] (53min TV documentary)
**'''Point of Contact''': Peter Baumann - baumann@rasdaman.com

== OSGeo-Live ==

OSGeo-Live contains 50 of the best geospatial applications, pre-installed with datasets, along with project overviews and 10 to 15 minute quickstarts for each application and ~ 45 minute presentation of them all. The documentation provides an excellent high level overview of the breadth of geospatial open source applications. It is also used as a plaform for many open source geospatial workshops.

* Project Overviews and Quickstarts: http://live.osgeo.org/en/overview/overview.html
* Presentation: http://live.osgeo.org/en/presentation/index.html#/
* Contact: Cameron Shorter <cam e r onDoTs hort erA T g mai l.com>

*'''Bringing GEOSS services into practice'''
The "Bringing GEOSS services into practice" workshop aims at teaching how to configure, use and deploy a set of open source software (PostGIS, GeoServer, GeoNetwork, PyWPS, QGIS) to set up a spatial data infrastructure (SDI). Trainees will learn how to publish and share data and metadata using OGC and ISO standards and how to register services into the Global Earth Observation System of Systems (GEOSS).

Website: http://www.geossintopractice.org

Lab: GeoForAll - ISE, University of Geneva: http://www.unige.ch/tigers/fr/autres-reseaux/geoforall/

Contact: Gregory Giuliani <gregory.giuliani AT unige.ch>

== GeoMOOSE ==

GeoMOOSE is a Web Client JavaScript Framework for displaying distributed cartographic data. GeoMOOSE has a number of strengths including modularity, configurability, and delivers a number of core functionalities in its packages. GeoMOOSE is also very light weight for servers making it easy to handle a large number of users, with a large number of layers, and a large number of services without stressing a server.

The GeoMOOSE core is written using JavaScript and HTML. It is entirely possible to run GeoMOOSE with nothing more than a basic web server (Nginx, Apache, IIS). But besides the basic client core, GeoMOOSE also comes prepackaged with a number of built in services written in PHP. These services add the ability to perform drill-down identify operations, selection operations, and search data sets. If you have existing scripts that perform similar functions, GeoMOOSE can be tuned to work with those services, no matter which language they were written in.

* Website: http://www.geomoose.org
** Online Demo: http://demo.geomoose.org/master/
** Package download (includes operating demo with sample data): http://geomoose.org/download.html
** GeoMOOSE is also compatible with MS4W.
** Link to material: Training materials are included in the download package as an operating demo.
*** Workshop materials: http://www.geomoose.org/downloads/workshops/foss4gna-2013/
**** NOTE: Newer version will be available by May 15th, 2016
*** The OSGeo Live page for GeoMOOSE includes the Overview and Quickstart:
**** http://live.osgeo.org/en/quickstart/geomoose_quickstart.html
**** http://live.osgeo.org/en/overview/geomoose_overview.html
** Contact: Bob Basques <bbasques AT sharedgeo.org>

== GET-IT ==

'''GET-IT''' - Geoinformation Enabling ToolkIT starterkit, supports researchers and professional in the creation of autonomous, distributed nodes of a Spatial Data Infrastructure and uploading research results in the form of maps/observations (and related metadata). GET-It supports domain researchers and professional in the creation of OGC standard services like WMS, WFS, WCS, CSW, and SOS. GET-It is based on GeoNode, contains pyCSW, 52° North SOS Server, Geoserver, PostgreSQL, PostGIS, OpenLayers and also contains EDI, a general purpose, customizable, template-driven metadata editor. The suite is the first open-source collaborative effort toward the integration of traditional geographic information with observational data.

*'''GET-IT Website''': http://www.get-it.it/
**'''EDI Website''': http://edidemo.get-it.it/
**'''Docs''': http://getit.readthedocs.org/en/latest/
**'''Demo''': http://demo2.get-it.it/
**'''Code''': https://github.com/SP7-Ritmare/starterkit
**'''Lab''': 103 IREA-CNR - http://www.irea.cnr.it/
**'''Point of Contact''': Alessandro Oggioni - oggioni.a@irea.cnr.it

==Open Source Geospatial Notebooks==
'''OSGeo-Notebooks''' - Development of interactive educational material in the form of geospatial notebooks based on the [http://jupyter.org/ Jupyter project].
This project is in active development (work in progress :) ), do not hesitate to contact me If interested in the integration of existing educational materials in the form of interactive notebooks.

* '''Code:''' https://github.com/epifanio/OSGeospatial-Notebooks
* '''Point of Contact:''' Massimo Di Stefano <epiesasha@me.com>

UNTraining

2016-04-15T16:40:29Z

Wiki-Epifanio: /* Open Source Geospatial Notebooks */

'''Welcome to the UN training page'''

GeoForAll is supporting UN in their migration to geospatial open source applications. In this page we list the training material available for some products that UN will use. Please add your training material here, putting also the reference to all data used in such a way that everybody in using your material can be autonomous.

== QGIS ==

* Official manual + training manual: http://docs.qgis.org - Point of contact: QGIS Project Steering Committee

*'''FOSS4G GeoAcademy Curriculum''' - 35 hands-on labs written primarily for QGIS with some cross over with GRASS and Inkscape. Labs are aligned to the Geospatial Technology Competency Model. Development was sponsored by a Department of Labor Grant and is released under Creative Commons Attribute 3.0 Unported license. All labs currently written for QGIS 2.8, but we are about to release labs for QGIS 2.14. In addition to labs, lecture material is also developed and being uploaded. All lab instructions and data are [http://spatialquerylab.com/foss4g-academy-curriculum/ available online on our lab website].
**'''Link to material''': http://spatialquerylab.com/foss4g-academy-curriculum/
**'''Lab''': Spatial {Query} Lab - http://www.spatialquerylab.com
**'''Point of Contact''': Rick Smith - Richard.Smith@tamucc.edu
**'''Mailing Address''': 6300 Ocean Dr., Unit 5868, Corpus Christi, TX 78412-5868, USA

Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact

== gvSIG ==

gvSIG is a powerful, user-friendly and interoperable GIS. It is easy to work in a variety of formats, vector and raster files, databases and remote services. There are always available all kinds of tools to analyze and manage geographic information.

gvSIG Desktop is designed to be an easily extensible solution, allowing thus continually improving the software application and developing tailor made solutions. It is open source software, GNU / GPL license, this makes its free use, distribution, study and improvement. gvSIG Desktop integrates NASA World Wind, so it allows to work with 3D Views.

gvSIG Online is an Open Source solution for Spatial Data Infrastructures. It is an integral platform for the Spatial Data Infrastructure (SDI) implementation, 100% open source software. A fast and powerful solution for start up the infrastructure necessary to manage spatial data in an organization in an efficient way.

*Website: http://www.gvsig.com
** [http://www.gvsig.com/en/diffusion/educational-material?p_p_id=122_INSTANCE_A9eo37KAqtxs&p_p_lifecycle=0&p_p_state=normal&p_p_mode=view&p_p_col_id=column-2&p_p_col_count=1&p_r_p_564233524_resetCur=true&p_r_p_564233524_categoryId=25973 Educational material in English]
** [http://web.gvsig-training.com/index.php/en/quienes-somos-2/noticias-2/145-the-free-mooc-cycle-gvsig-for-users Free MOOC cycle "gvSIG for Users"]
** '''Point of Contact''': Mario Carrera - mcarrera [at] gvsig.com
* [https://www.youtube.com/user/gvsig gvSIG Youtube Channel]

== GRASS GIS ==

Geographic Resources Analysis Support System, commonly referred to as GRASS GIS, is a Geographic Information System (GIS) used for data management, image processing, graphics production, spatial modelling, and visualization of many types of data. URL: https://grass.osgeo.org

*'''NCSU Geospatial Analysis and Modeling course''' - 13 hands-on labs exercises used at North Carolina State University for teaching geospatial analysis and modeling with focus on terrain analysis, continuous surfaces, interpolation, geomorphometry, hydrology and erosion. We tested the exercises with GRASS GIS 7.0 and we update the material with every new release and academic semester. The material is released under Creative Commons Attribution-ShareAlike 4.0 International license (CC BY-SA 4.0) and the material is [https://github.com/ncsu-osgeorel/geospatial-modeling-course developed openly]. The course also includes software-independent lectures which are available online as recorded videos and presentations slides.
**'''Link to material''': http://ncsu-osgeorel.github.io/geospatial-modeling-course/grass/
**'''Lab''': NCSU OSGeoREL - https://geospatial.ncsu.edu/osgeorel
**'''Point of Contact''': Helena Mitasova - hmitaso@ncsu.edu
**'''Mailing Address''': 2800 Faucette Drive, North Carolina State University, Raleigh, NC 27695-8208, USA
*'''Workshop on urban growth modeling with FUTURES''' - A day long tutorial on GRASS GIS and urban growth modeling using the FUTURES model tested with GRASS GIS 7.0. The material is dual licensed under Creative Commons Attribution-ShareAlike 4.0 International license (CC BY-SA 4.0) and GNU Free Documentation License 1.2.
**'''Link to material''': https://grasswiki.osgeo.org/wiki/Workshop_on_urban_growth_modeling_with_FUTURES
**'''Lab''': NCSU OSGeoREL - https://geospatial.ncsu.edu/osgeorel
**'''Point of Contact''': Anna Petrasova - akratoc@ncsu.edu
**'''Mailing Address''': 2800 Faucette Drive, North Carolina State University, Raleigh, NC 27695-8208, USA

== GeoServer ==

GeoServer is an open source server for sharing geospatial data. Designed for interoperability, it publishes data from any major spatial data source using open standards.

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://workshops.boundlessgeo.com/geoserver-intro/ Introduction to GeoServer]
**'''Link to Material''': [http://workshops.boundlessgeo.com/suiteintro/ Introduction to Suite]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

*'''GeoSolutions Workshops''': [http://www.geo-solutions.it Website]
** '''Link to Material''': [http://geoserver.geo-solutions.it/edu/en/ GeoServer general training, four days worth of training material, from the first steps to production deploy setups, performance optimization and the like]
** '''Link to Material''': [http://geoserver.geo-solutions.it/multidim/en/ Spatio-temporal data handling with GeoServer]
** '''Link to Material''': [http://geoserver.geo-solutions.it/complexfeatures/ Complex features support and mapping with Hale]
** '''Point of Contact''': Andrea Aime - [mailto:andrea.aime@geo-solutions.it andrea.aime@geo-solutions.it]

*'''GeoServer Users Guide''': [http://docs.geoserver.org/latest/en/user/ Website]
**'''Link to Material''': [http://docs.geoserver.org/latest/en/user/extensions/css/workshop/index.html CSS styling workshop]
**'''Point of Contact''': Mike Pumphrey - [mailto:mike@boundlessgeo.com mike@boundlessgeo.com]

== OpenLayers ==

OpenLayers is a high-performance, feature-packed library for all your mapping needs.

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://workshops.boundlessgeo.com/openlayers3/ Introduction to OpenLayers]
**'''Link to Material''': [http://workshops.boundlessgeo.com/suiteintro/ Introduction to Suite]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

== PostgreSQL ==

Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact

== PostGIS ==

PostGIS is a spatial database extender for PostgreSQL object-relational database. It adds support for geographic objects allowing location queries to be run in SQL.

*''' University of Colorado Denver FOSS4G Lab''': [http://geospatial.ucdenver.edu/foss4g/ CU Denver FOSS4G Lab]
**'''PostgreSQL-PostGIS Tutorial Series''' Series of 7 tutorials covering the basics of PostGIS for spatial data handling and analysis.
**'''Link to material''': [http://geospatial.ucdenver.edu/foss4g/training/tutorials PostgreSQL-PostGIS Tutorials]
**'''Point of Contact''': Rafael Moreno - Rafael.Moreno@ucdenver.edu

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://workshops.boundlessgeo.com/postgis-intro/ Introduction to PostGIS]
**'''Link to Material''': [http://workshops.boundlessgeo.com/suiteintro/ Introduction to Suite]
**'''Link to Material''': [http://workshops.boundlessgeo.com/postgis-spatialdbtips/ Spatial Database Tips & Tricks]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

== GeoGig ==

GeoGig is an open source tool that draws inspiration from Git, but adapts its core concepts to handle distributed versioning of geospatial data.

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://geogig.org/workshop/ GeoGig Workshop]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

== GeoNode ==

GeoNode is a web-based application and platform for developing geospatial information systems (GIS) and for deploying spatial data infrastructures (SDI).

**'''Email List''': [http://lists.osgeo.org/mailman/listinfo/geonode-users geonode-users] and [http://lists.osgeo.org/mailman/listinfo/geonode-dev geonode-dev]
* Website: http://geonode.org
** Demo: http://demo.geonode.org
**'''Link to material''': http://docs.geonode.org/en/latest/index.html
**'''Point of Contact''': Vivien Deparday - [mailto:vdeparday@worldbank.org vdeparday@worldbank.org], Ariel Núñez - [mailto:ingenieroariel@gmail.com ingenieroariel@gmail.com], Paolo Corti - [mailto:pcorti@fas.harvard.edu pcorti@fas.harvard.edu]

== Rasdaman ==

*'''[http://www.rasdaman.org rasdaman]'''
**'''Big Geo Data Lab''' - Spatio-temporal sensor, image, simulation, and statistics data of unlimited size are served rapidly by rasdaman ("raster data manager"). As a multiparallel, distributed analytics engine, rasdaman achieves unparalleled service flexibility, scalability, and performance. Being OGC [http://en.wikipedia.org/wiki/Web_Coverage_Processing_Service WCPS] and [http://en.wikipedia.org/wiki/Web_Coverage_Service WCS] Core Reference Implementation, rasdaman enables access, subsetting, and processing on the fly using open standards interfaces. The WCS suite is a central cornerstone for SDIs: a large, growing number of open-source and proprietary tools supports it (MapServer, GeoServer, OpenLayers, QGIS, ESRI ArcGIS, ...) and the OGC standards are under adoption by ISO (as forthcoming 19123-2) and INSPIRE ("Coverage Download Service"). Significant training material is available already, and is being augmented continuously:
**'''Link to material''': [http://rasdaman.org/wiki/Workshops OGC Big Geo Data standards and rasdaman workshops] | [http://standards.rasdaman.com/ hands-on lab on Big Data Standards] | [http://kahlua.eecs.jacobs-university.de/~lsis/Big-Earth-Data_the-ARTE-Movie/index.php Big Earth Data] (53min TV documentary)
**'''Point of Contact''': Peter Baumann - baumann@rasdaman.com

== OSGeo-Live ==

OSGeo-Live contains 50 of the best geospatial applications, pre-installed with datasets, along with project overviews and 10 to 15 minute quickstarts for each application and ~ 45 minute presentation of them all. The documentation provides an excellent high level overview of the breadth of geospatial open source applications. It is also used as a plaform for many open source geospatial workshops.

* Project Overviews and Quickstarts: http://live.osgeo.org/en/overview/overview.html
* Presentation: http://live.osgeo.org/en/presentation/index.html#/
* Contact: Cameron Shorter <cam e r onDoTs hort erA T g mai l.com>

*'''Bringing GEOSS services into practice'''
The "Bringing GEOSS services into practice" workshop aims at teaching how to configure, use and deploy a set of open source software (PostGIS, GeoServer, GeoNetwork, PyWPS, QGIS) to set up a spatial data infrastructure (SDI). Trainees will learn how to publish and share data and metadata using OGC and ISO standards and how to register services into the Global Earth Observation System of Systems (GEOSS).

Website: http://www.geossintopractice.org

Lab: GeoForAll - ISE, University of Geneva: http://www.unige.ch/tigers/fr/autres-reseaux/geoforall/

Contact: Gregory Giuliani <gregory.giuliani AT unige.ch>

== GeoMOOSE ==

GeoMOOSE is a Web Client JavaScript Framework for displaying distributed cartographic data. GeoMOOSE has a number of strengths including modularity, configurability, and delivers a number of core functionalities in its packages. GeoMOOSE is also very light weight for servers making it easy to handle a large number of users, with a large number of layers, and a large number of services without stressing a server.

The GeoMOOSE core is written using JavaScript and HTML. It is entirely possible to run GeoMOOSE with nothing more than a basic web server (Nginx, Apache, IIS). But besides the basic client core, GeoMOOSE also comes prepackaged with a number of built in services written in PHP. These services add the ability to perform drill-down identify operations, selection operations, and search data sets. If you have existing scripts that perform similar functions, GeoMOOSE can be tuned to work with those services, no matter which language they were written in.

* Website: http://www.geomoose.org
** Online Demo: http://demo.geomoose.org/master/
** Package download (includes operating demo with sample data): http://geomoose.org/download.html
** GeoMOOSE is also compatible with MS4W.
** Link to material: Training materials are included in the download package as an operating demo.
*** Workshop materials: http://www.geomoose.org/downloads/workshops/foss4gna-2013/
**** NOTE: Newer version will be available by May 15th, 2016
*** The OSGeo Live page for GeoMOOSE includes the Overview and Quickstart:
**** http://live.osgeo.org/en/quickstart/geomoose_quickstart.html
**** http://live.osgeo.org/en/overview/geomoose_overview.html
** Contact: Bob Basques <bbasques AT sharedgeo.org>

== GET-IT ==

'''GET-IT''' - Geoinformation Enabling ToolkIT starterkit, supports researchers and professional in the creation of autonomous, distributed nodes of a Spatial Data Infrastructure and uploading research results in the form of maps/observations (and related metadata). GET-It supports domain researchers and professional in the creation of OGC standard services like WMS, WFS, WCS, CSW, and SOS. GET-It is based on GeoNode, contains pyCSW, 52° North SOS Server, Geoserver, PostgreSQL, PostGIS, OpenLayers and also contains EDI, a general purpose, customizable, template-driven metadata editor. The suite is the first open-source collaborative effort toward the integration of traditional geographic information with observational data.

*'''GET-IT Website''': http://www.get-it.it/
**'''EDI Website''': http://edidemo.get-it.it/
**'''Docs''': http://getit.readthedocs.org/en/latest/
**'''Demo''': http://demo2.get-it.it/
**'''Code''': https://github.com/SP7-Ritmare/starterkit
**'''Lab''': 103 IREA-CNR - http://www.irea.cnr.it/
**'''Point of Contact''': Alessandro Oggioni - oggioni.a@irea.cnr.it

==Open Source Geospatial Notebooks==
'''OSGeo-Notebooks''' - Development of interactive educational material in the form of geospatial notebooks based on the [http://jupyter.org/ Jupyter project].
This project is in active development (work in progress :) ), do not hesitate to contact me If interested in the integration of existing educational materials in the form of interactive notebooks.

* '''Code repository: [https://github.com/epifanio/OSGeospatial-Notebooks Open Source Geospatial Notebooks]'''
* '''Point of Contact:''' Massimo Di Stefano <epiesasha@me.com>

UNTraining

2016-04-15T16:40:08Z

Wiki-Epifanio: /* Open Source Geospatial Notebooks */

'''Welcome to the UN training page'''

GeoForAll is supporting UN in their migration to geospatial open source applications. In this page we list the training material available for some products that UN will use. Please add your training material here, putting also the reference to all data used in such a way that everybody in using your material can be autonomous.

== QGIS ==

* Official manual + training manual: http://docs.qgis.org - Point of contact: QGIS Project Steering Committee

*'''FOSS4G GeoAcademy Curriculum''' - 35 hands-on labs written primarily for QGIS with some cross over with GRASS and Inkscape. Labs are aligned to the Geospatial Technology Competency Model. Development was sponsored by a Department of Labor Grant and is released under Creative Commons Attribute 3.0 Unported license. All labs currently written for QGIS 2.8, but we are about to release labs for QGIS 2.14. In addition to labs, lecture material is also developed and being uploaded. All lab instructions and data are [http://spatialquerylab.com/foss4g-academy-curriculum/ available online on our lab website].
**'''Link to material''': http://spatialquerylab.com/foss4g-academy-curriculum/
**'''Lab''': Spatial {Query} Lab - http://www.spatialquerylab.com
**'''Point of Contact''': Rick Smith - Richard.Smith@tamucc.edu
**'''Mailing Address''': 6300 Ocean Dr., Unit 5868, Corpus Christi, TX 78412-5868, USA

Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact

== gvSIG ==

gvSIG is a powerful, user-friendly and interoperable GIS. It is easy to work in a variety of formats, vector and raster files, databases and remote services. There are always available all kinds of tools to analyze and manage geographic information.

gvSIG Desktop is designed to be an easily extensible solution, allowing thus continually improving the software application and developing tailor made solutions. It is open source software, GNU / GPL license, this makes its free use, distribution, study and improvement. gvSIG Desktop integrates NASA World Wind, so it allows to work with 3D Views.

gvSIG Online is an Open Source solution for Spatial Data Infrastructures. It is an integral platform for the Spatial Data Infrastructure (SDI) implementation, 100% open source software. A fast and powerful solution for start up the infrastructure necessary to manage spatial data in an organization in an efficient way.

*Website: http://www.gvsig.com
** [http://www.gvsig.com/en/diffusion/educational-material?p_p_id=122_INSTANCE_A9eo37KAqtxs&p_p_lifecycle=0&p_p_state=normal&p_p_mode=view&p_p_col_id=column-2&p_p_col_count=1&p_r_p_564233524_resetCur=true&p_r_p_564233524_categoryId=25973 Educational material in English]
** [http://web.gvsig-training.com/index.php/en/quienes-somos-2/noticias-2/145-the-free-mooc-cycle-gvsig-for-users Free MOOC cycle "gvSIG for Users"]
** '''Point of Contact''': Mario Carrera - mcarrera [at] gvsig.com
* [https://www.youtube.com/user/gvsig gvSIG Youtube Channel]

== GRASS GIS ==

Geographic Resources Analysis Support System, commonly referred to as GRASS GIS, is a Geographic Information System (GIS) used for data management, image processing, graphics production, spatial modelling, and visualization of many types of data. URL: https://grass.osgeo.org

*'''NCSU Geospatial Analysis and Modeling course''' - 13 hands-on labs exercises used at North Carolina State University for teaching geospatial analysis and modeling with focus on terrain analysis, continuous surfaces, interpolation, geomorphometry, hydrology and erosion. We tested the exercises with GRASS GIS 7.0 and we update the material with every new release and academic semester. The material is released under Creative Commons Attribution-ShareAlike 4.0 International license (CC BY-SA 4.0) and the material is [https://github.com/ncsu-osgeorel/geospatial-modeling-course developed openly]. The course also includes software-independent lectures which are available online as recorded videos and presentations slides.
**'''Link to material''': http://ncsu-osgeorel.github.io/geospatial-modeling-course/grass/
**'''Lab''': NCSU OSGeoREL - https://geospatial.ncsu.edu/osgeorel
**'''Point of Contact''': Helena Mitasova - hmitaso@ncsu.edu
**'''Mailing Address''': 2800 Faucette Drive, North Carolina State University, Raleigh, NC 27695-8208, USA
*'''Workshop on urban growth modeling with FUTURES''' - A day long tutorial on GRASS GIS and urban growth modeling using the FUTURES model tested with GRASS GIS 7.0. The material is dual licensed under Creative Commons Attribution-ShareAlike 4.0 International license (CC BY-SA 4.0) and GNU Free Documentation License 1.2.
**'''Link to material''': https://grasswiki.osgeo.org/wiki/Workshop_on_urban_growth_modeling_with_FUTURES
**'''Lab''': NCSU OSGeoREL - https://geospatial.ncsu.edu/osgeorel
**'''Point of Contact''': Anna Petrasova - akratoc@ncsu.edu
**'''Mailing Address''': 2800 Faucette Drive, North Carolina State University, Raleigh, NC 27695-8208, USA

== GeoServer ==

GeoServer is an open source server for sharing geospatial data. Designed for interoperability, it publishes data from any major spatial data source using open standards.

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://workshops.boundlessgeo.com/geoserver-intro/ Introduction to GeoServer]
**'''Link to Material''': [http://workshops.boundlessgeo.com/suiteintro/ Introduction to Suite]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

*'''GeoSolutions Workshops''': [http://www.geo-solutions.it Website]
** '''Link to Material''': [http://geoserver.geo-solutions.it/edu/en/ GeoServer general training, four days worth of training material, from the first steps to production deploy setups, performance optimization and the like]
** '''Link to Material''': [http://geoserver.geo-solutions.it/multidim/en/ Spatio-temporal data handling with GeoServer]
** '''Link to Material''': [http://geoserver.geo-solutions.it/complexfeatures/ Complex features support and mapping with Hale]
** '''Point of Contact''': Andrea Aime - [mailto:andrea.aime@geo-solutions.it andrea.aime@geo-solutions.it]

*'''GeoServer Users Guide''': [http://docs.geoserver.org/latest/en/user/ Website]
**'''Link to Material''': [http://docs.geoserver.org/latest/en/user/extensions/css/workshop/index.html CSS styling workshop]
**'''Point of Contact''': Mike Pumphrey - [mailto:mike@boundlessgeo.com mike@boundlessgeo.com]

== OpenLayers ==

OpenLayers is a high-performance, feature-packed library for all your mapping needs.

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://workshops.boundlessgeo.com/openlayers3/ Introduction to OpenLayers]
**'''Link to Material''': [http://workshops.boundlessgeo.com/suiteintro/ Introduction to Suite]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

== PostgreSQL ==

Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact

== PostGIS ==

PostGIS is a spatial database extender for PostgreSQL object-relational database. It adds support for geographic objects allowing location queries to be run in SQL.

*''' University of Colorado Denver FOSS4G Lab''': [http://geospatial.ucdenver.edu/foss4g/ CU Denver FOSS4G Lab]
**'''PostgreSQL-PostGIS Tutorial Series''' Series of 7 tutorials covering the basics of PostGIS for spatial data handling and analysis.
**'''Link to material''': [http://geospatial.ucdenver.edu/foss4g/training/tutorials PostgreSQL-PostGIS Tutorials]
**'''Point of Contact''': Rafael Moreno - Rafael.Moreno@ucdenver.edu

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://workshops.boundlessgeo.com/postgis-intro/ Introduction to PostGIS]
**'''Link to Material''': [http://workshops.boundlessgeo.com/suiteintro/ Introduction to Suite]
**'''Link to Material''': [http://workshops.boundlessgeo.com/postgis-spatialdbtips/ Spatial Database Tips & Tricks]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

== GeoGig ==

GeoGig is an open source tool that draws inspiration from Git, but adapts its core concepts to handle distributed versioning of geospatial data.

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://geogig.org/workshop/ GeoGig Workshop]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

== GeoNode ==

GeoNode is a web-based application and platform for developing geospatial information systems (GIS) and for deploying spatial data infrastructures (SDI).

**'''Email List''': [http://lists.osgeo.org/mailman/listinfo/geonode-users geonode-users] and [http://lists.osgeo.org/mailman/listinfo/geonode-dev geonode-dev]
* Website: http://geonode.org
** Demo: http://demo.geonode.org
**'''Link to material''': http://docs.geonode.org/en/latest/index.html
**'''Point of Contact''': Vivien Deparday - [mailto:vdeparday@worldbank.org vdeparday@worldbank.org], Ariel Núñez - [mailto:ingenieroariel@gmail.com ingenieroariel@gmail.com], Paolo Corti - [mailto:pcorti@fas.harvard.edu pcorti@fas.harvard.edu]

== Rasdaman ==

*'''[http://www.rasdaman.org rasdaman]'''
**'''Big Geo Data Lab''' - Spatio-temporal sensor, image, simulation, and statistics data of unlimited size are served rapidly by rasdaman ("raster data manager"). As a multiparallel, distributed analytics engine, rasdaman achieves unparalleled service flexibility, scalability, and performance. Being OGC [http://en.wikipedia.org/wiki/Web_Coverage_Processing_Service WCPS] and [http://en.wikipedia.org/wiki/Web_Coverage_Service WCS] Core Reference Implementation, rasdaman enables access, subsetting, and processing on the fly using open standards interfaces. The WCS suite is a central cornerstone for SDIs: a large, growing number of open-source and proprietary tools supports it (MapServer, GeoServer, OpenLayers, QGIS, ESRI ArcGIS, ...) and the OGC standards are under adoption by ISO (as forthcoming 19123-2) and INSPIRE ("Coverage Download Service"). Significant training material is available already, and is being augmented continuously:
**'''Link to material''': [http://rasdaman.org/wiki/Workshops OGC Big Geo Data standards and rasdaman workshops] | [http://standards.rasdaman.com/ hands-on lab on Big Data Standards] | [http://kahlua.eecs.jacobs-university.de/~lsis/Big-Earth-Data_the-ARTE-Movie/index.php Big Earth Data] (53min TV documentary)
**'''Point of Contact''': Peter Baumann - baumann@rasdaman.com

== OSGeo-Live ==

OSGeo-Live contains 50 of the best geospatial applications, pre-installed with datasets, along with project overviews and 10 to 15 minute quickstarts for each application and ~ 45 minute presentation of them all. The documentation provides an excellent high level overview of the breadth of geospatial open source applications. It is also used as a plaform for many open source geospatial workshops.

* Project Overviews and Quickstarts: http://live.osgeo.org/en/overview/overview.html
* Presentation: http://live.osgeo.org/en/presentation/index.html#/
* Contact: Cameron Shorter <cam e r onDoTs hort erA T g mai l.com>

*'''Bringing GEOSS services into practice'''
The "Bringing GEOSS services into practice" workshop aims at teaching how to configure, use and deploy a set of open source software (PostGIS, GeoServer, GeoNetwork, PyWPS, QGIS) to set up a spatial data infrastructure (SDI). Trainees will learn how to publish and share data and metadata using OGC and ISO standards and how to register services into the Global Earth Observation System of Systems (GEOSS).

Website: http://www.geossintopractice.org

Lab: GeoForAll - ISE, University of Geneva: http://www.unige.ch/tigers/fr/autres-reseaux/geoforall/

Contact: Gregory Giuliani <gregory.giuliani AT unige.ch>

== GeoMOOSE ==

GeoMOOSE is a Web Client JavaScript Framework for displaying distributed cartographic data. GeoMOOSE has a number of strengths including modularity, configurability, and delivers a number of core functionalities in its packages. GeoMOOSE is also very light weight for servers making it easy to handle a large number of users, with a large number of layers, and a large number of services without stressing a server.

The GeoMOOSE core is written using JavaScript and HTML. It is entirely possible to run GeoMOOSE with nothing more than a basic web server (Nginx, Apache, IIS). But besides the basic client core, GeoMOOSE also comes prepackaged with a number of built in services written in PHP. These services add the ability to perform drill-down identify operations, selection operations, and search data sets. If you have existing scripts that perform similar functions, GeoMOOSE can be tuned to work with those services, no matter which language they were written in.

* Website: http://www.geomoose.org
** Online Demo: http://demo.geomoose.org/master/
** Package download (includes operating demo with sample data): http://geomoose.org/download.html
** GeoMOOSE is also compatible with MS4W.
** Link to material: Training materials are included in the download package as an operating demo.
*** Workshop materials: http://www.geomoose.org/downloads/workshops/foss4gna-2013/
**** NOTE: Newer version will be available by May 15th, 2016
*** The OSGeo Live page for GeoMOOSE includes the Overview and Quickstart:
**** http://live.osgeo.org/en/quickstart/geomoose_quickstart.html
**** http://live.osgeo.org/en/overview/geomoose_overview.html
** Contact: Bob Basques <bbasques AT sharedgeo.org>

== GET-IT ==

'''GET-IT''' - Geoinformation Enabling ToolkIT starterkit, supports researchers and professional in the creation of autonomous, distributed nodes of a Spatial Data Infrastructure and uploading research results in the form of maps/observations (and related metadata). GET-It supports domain researchers and professional in the creation of OGC standard services like WMS, WFS, WCS, CSW, and SOS. GET-It is based on GeoNode, contains pyCSW, 52° North SOS Server, Geoserver, PostgreSQL, PostGIS, OpenLayers and also contains EDI, a general purpose, customizable, template-driven metadata editor. The suite is the first open-source collaborative effort toward the integration of traditional geographic information with observational data.

*'''GET-IT Website''': http://www.get-it.it/
**'''EDI Website''': http://edidemo.get-it.it/
**'''Docs''': http://getit.readthedocs.org/en/latest/
**'''Demo''': http://demo2.get-it.it/
**'''Code''': https://github.com/SP7-Ritmare/starterkit
**'''Lab''': 103 IREA-CNR - http://www.irea.cnr.it/
**'''Point of Contact''': Alessandro Oggioni - oggioni.a@irea.cnr.it

==Open Source Geospatial Notebooks==
'''OSGeo-Notebooks''' - Development of interactive educational material in the form of geospatial notebooks based on the [http://jupyter.org/ Jupyter project].
This project is in active development (work in progress :) ), do not hesitate to contact me If interested in the integration of existing educational materials in the form of interactive notebooks.

* '''Code repository: [https://github.com/epifanio/OSGeospatial-Notebooks Open Source Geospatial Notebooks]'''
* '''Contact:''' Massimo Di Stefano <epiesasha@me.com>

UNTraining

2016-04-15T16:39:15Z

Wiki-Epifanio: /* Open Source Geospatial Notebooks */

'''Welcome to the UN training page'''

GeoForAll is supporting UN in their migration to geospatial open source applications. In this page we list the training material available for some products that UN will use. Please add your training material here, putting also the reference to all data used in such a way that everybody in using your material can be autonomous.

== QGIS ==

* Official manual + training manual: http://docs.qgis.org - Point of contact: QGIS Project Steering Committee

*'''FOSS4G GeoAcademy Curriculum''' - 35 hands-on labs written primarily for QGIS with some cross over with GRASS and Inkscape. Labs are aligned to the Geospatial Technology Competency Model. Development was sponsored by a Department of Labor Grant and is released under Creative Commons Attribute 3.0 Unported license. All labs currently written for QGIS 2.8, but we are about to release labs for QGIS 2.14. In addition to labs, lecture material is also developed and being uploaded. All lab instructions and data are [http://spatialquerylab.com/foss4g-academy-curriculum/ available online on our lab website].
**'''Link to material''': http://spatialquerylab.com/foss4g-academy-curriculum/
**'''Lab''': Spatial {Query} Lab - http://www.spatialquerylab.com
**'''Point of Contact''': Rick Smith - Richard.Smith@tamucc.edu
**'''Mailing Address''': 6300 Ocean Dr., Unit 5868, Corpus Christi, TX 78412-5868, USA

Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact

== gvSIG ==

gvSIG is a powerful, user-friendly and interoperable GIS. It is easy to work in a variety of formats, vector and raster files, databases and remote services. There are always available all kinds of tools to analyze and manage geographic information.

gvSIG Desktop is designed to be an easily extensible solution, allowing thus continually improving the software application and developing tailor made solutions. It is open source software, GNU / GPL license, this makes its free use, distribution, study and improvement. gvSIG Desktop integrates NASA World Wind, so it allows to work with 3D Views.

gvSIG Online is an Open Source solution for Spatial Data Infrastructures. It is an integral platform for the Spatial Data Infrastructure (SDI) implementation, 100% open source software. A fast and powerful solution for start up the infrastructure necessary to manage spatial data in an organization in an efficient way.

*Website: http://www.gvsig.com
** [http://www.gvsig.com/en/diffusion/educational-material?p_p_id=122_INSTANCE_A9eo37KAqtxs&p_p_lifecycle=0&p_p_state=normal&p_p_mode=view&p_p_col_id=column-2&p_p_col_count=1&p_r_p_564233524_resetCur=true&p_r_p_564233524_categoryId=25973 Educational material in English]
** [http://web.gvsig-training.com/index.php/en/quienes-somos-2/noticias-2/145-the-free-mooc-cycle-gvsig-for-users Free MOOC cycle "gvSIG for Users"]
** '''Point of Contact''': Mario Carrera - mcarrera [at] gvsig.com
* [https://www.youtube.com/user/gvsig gvSIG Youtube Channel]

== GRASS GIS ==

Geographic Resources Analysis Support System, commonly referred to as GRASS GIS, is a Geographic Information System (GIS) used for data management, image processing, graphics production, spatial modelling, and visualization of many types of data. URL: https://grass.osgeo.org

*'''NCSU Geospatial Analysis and Modeling course''' - 13 hands-on labs exercises used at North Carolina State University for teaching geospatial analysis and modeling with focus on terrain analysis, continuous surfaces, interpolation, geomorphometry, hydrology and erosion. We tested the exercises with GRASS GIS 7.0 and we update the material with every new release and academic semester. The material is released under Creative Commons Attribution-ShareAlike 4.0 International license (CC BY-SA 4.0) and the material is [https://github.com/ncsu-osgeorel/geospatial-modeling-course developed openly]. The course also includes software-independent lectures which are available online as recorded videos and presentations slides.
**'''Link to material''': http://ncsu-osgeorel.github.io/geospatial-modeling-course/grass/
**'''Lab''': NCSU OSGeoREL - https://geospatial.ncsu.edu/osgeorel
**'''Point of Contact''': Helena Mitasova - hmitaso@ncsu.edu
**'''Mailing Address''': 2800 Faucette Drive, North Carolina State University, Raleigh, NC 27695-8208, USA
*'''Workshop on urban growth modeling with FUTURES''' - A day long tutorial on GRASS GIS and urban growth modeling using the FUTURES model tested with GRASS GIS 7.0. The material is dual licensed under Creative Commons Attribution-ShareAlike 4.0 International license (CC BY-SA 4.0) and GNU Free Documentation License 1.2.
**'''Link to material''': https://grasswiki.osgeo.org/wiki/Workshop_on_urban_growth_modeling_with_FUTURES
**'''Lab''': NCSU OSGeoREL - https://geospatial.ncsu.edu/osgeorel
**'''Point of Contact''': Anna Petrasova - akratoc@ncsu.edu
**'''Mailing Address''': 2800 Faucette Drive, North Carolina State University, Raleigh, NC 27695-8208, USA

== GeoServer ==

GeoServer is an open source server for sharing geospatial data. Designed for interoperability, it publishes data from any major spatial data source using open standards.

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://workshops.boundlessgeo.com/geoserver-intro/ Introduction to GeoServer]
**'''Link to Material''': [http://workshops.boundlessgeo.com/suiteintro/ Introduction to Suite]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

*'''GeoSolutions Workshops''': [http://www.geo-solutions.it Website]
** '''Link to Material''': [http://geoserver.geo-solutions.it/edu/en/ GeoServer general training, four days worth of training material, from the first steps to production deploy setups, performance optimization and the like]
** '''Link to Material''': [http://geoserver.geo-solutions.it/multidim/en/ Spatio-temporal data handling with GeoServer]
** '''Link to Material''': [http://geoserver.geo-solutions.it/complexfeatures/ Complex features support and mapping with Hale]
** '''Point of Contact''': Andrea Aime - [mailto:andrea.aime@geo-solutions.it andrea.aime@geo-solutions.it]

*'''GeoServer Users Guide''': [http://docs.geoserver.org/latest/en/user/ Website]
**'''Link to Material''': [http://docs.geoserver.org/latest/en/user/extensions/css/workshop/index.html CSS styling workshop]
**'''Point of Contact''': Mike Pumphrey - [mailto:mike@boundlessgeo.com mike@boundlessgeo.com]

== OpenLayers ==

OpenLayers is a high-performance, feature-packed library for all your mapping needs.

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://workshops.boundlessgeo.com/openlayers3/ Introduction to OpenLayers]
**'''Link to Material''': [http://workshops.boundlessgeo.com/suiteintro/ Introduction to Suite]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

== PostgreSQL ==

Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact

== PostGIS ==

PostGIS is a spatial database extender for PostgreSQL object-relational database. It adds support for geographic objects allowing location queries to be run in SQL.

*''' University of Colorado Denver FOSS4G Lab''': [http://geospatial.ucdenver.edu/foss4g/ CU Denver FOSS4G Lab]
**'''PostgreSQL-PostGIS Tutorial Series''' Series of 7 tutorials covering the basics of PostGIS for spatial data handling and analysis.
**'''Link to material''': [http://geospatial.ucdenver.edu/foss4g/training/tutorials PostgreSQL-PostGIS Tutorials]
**'''Point of Contact''': Rafael Moreno - Rafael.Moreno@ucdenver.edu

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://workshops.boundlessgeo.com/postgis-intro/ Introduction to PostGIS]
**'''Link to Material''': [http://workshops.boundlessgeo.com/suiteintro/ Introduction to Suite]
**'''Link to Material''': [http://workshops.boundlessgeo.com/postgis-spatialdbtips/ Spatial Database Tips & Tricks]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

== GeoGig ==

GeoGig is an open source tool that draws inspiration from Git, but adapts its core concepts to handle distributed versioning of geospatial data.

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://geogig.org/workshop/ GeoGig Workshop]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

== GeoNode ==

GeoNode is a web-based application and platform for developing geospatial information systems (GIS) and for deploying spatial data infrastructures (SDI).

**'''Email List''': [http://lists.osgeo.org/mailman/listinfo/geonode-users geonode-users] and [http://lists.osgeo.org/mailman/listinfo/geonode-dev geonode-dev]
* Website: http://geonode.org
** Demo: http://demo.geonode.org
**'''Link to material''': http://docs.geonode.org/en/latest/index.html
**'''Point of Contact''': Vivien Deparday - [mailto:vdeparday@worldbank.org vdeparday@worldbank.org], Ariel Núñez - [mailto:ingenieroariel@gmail.com ingenieroariel@gmail.com], Paolo Corti - [mailto:pcorti@fas.harvard.edu pcorti@fas.harvard.edu]

== Rasdaman ==

*'''[http://www.rasdaman.org rasdaman]'''
**'''Big Geo Data Lab''' - Spatio-temporal sensor, image, simulation, and statistics data of unlimited size are served rapidly by rasdaman ("raster data manager"). As a multiparallel, distributed analytics engine, rasdaman achieves unparalleled service flexibility, scalability, and performance. Being OGC [http://en.wikipedia.org/wiki/Web_Coverage_Processing_Service WCPS] and [http://en.wikipedia.org/wiki/Web_Coverage_Service WCS] Core Reference Implementation, rasdaman enables access, subsetting, and processing on the fly using open standards interfaces. The WCS suite is a central cornerstone for SDIs: a large, growing number of open-source and proprietary tools supports it (MapServer, GeoServer, OpenLayers, QGIS, ESRI ArcGIS, ...) and the OGC standards are under adoption by ISO (as forthcoming 19123-2) and INSPIRE ("Coverage Download Service"). Significant training material is available already, and is being augmented continuously:
**'''Link to material''': [http://rasdaman.org/wiki/Workshops OGC Big Geo Data standards and rasdaman workshops] | [http://standards.rasdaman.com/ hands-on lab on Big Data Standards] | [http://kahlua.eecs.jacobs-university.de/~lsis/Big-Earth-Data_the-ARTE-Movie/index.php Big Earth Data] (53min TV documentary)
**'''Point of Contact''': Peter Baumann - baumann@rasdaman.com

== OSGeo-Live ==

OSGeo-Live contains 50 of the best geospatial applications, pre-installed with datasets, along with project overviews and 10 to 15 minute quickstarts for each application and ~ 45 minute presentation of them all. The documentation provides an excellent high level overview of the breadth of geospatial open source applications. It is also used as a plaform for many open source geospatial workshops.

* Project Overviews and Quickstarts: http://live.osgeo.org/en/overview/overview.html
* Presentation: http://live.osgeo.org/en/presentation/index.html#/
* Contact: Cameron Shorter <cam e r onDoTs hort erA T g mai l.com>

*'''Bringing GEOSS services into practice'''
The "Bringing GEOSS services into practice" workshop aims at teaching how to configure, use and deploy a set of open source software (PostGIS, GeoServer, GeoNetwork, PyWPS, QGIS) to set up a spatial data infrastructure (SDI). Trainees will learn how to publish and share data and metadata using OGC and ISO standards and how to register services into the Global Earth Observation System of Systems (GEOSS).

Website: http://www.geossintopractice.org

Lab: GeoForAll - ISE, University of Geneva: http://www.unige.ch/tigers/fr/autres-reseaux/geoforall/

Contact: Gregory Giuliani <gregory.giuliani AT unige.ch>

== GeoMOOSE ==

GeoMOOSE is a Web Client JavaScript Framework for displaying distributed cartographic data. GeoMOOSE has a number of strengths including modularity, configurability, and delivers a number of core functionalities in its packages. GeoMOOSE is also very light weight for servers making it easy to handle a large number of users, with a large number of layers, and a large number of services without stressing a server.

The GeoMOOSE core is written using JavaScript and HTML. It is entirely possible to run GeoMOOSE with nothing more than a basic web server (Nginx, Apache, IIS). But besides the basic client core, GeoMOOSE also comes prepackaged with a number of built in services written in PHP. These services add the ability to perform drill-down identify operations, selection operations, and search data sets. If you have existing scripts that perform similar functions, GeoMOOSE can be tuned to work with those services, no matter which language they were written in.

* Website: http://www.geomoose.org
** Online Demo: http://demo.geomoose.org/master/
** Package download (includes operating demo with sample data): http://geomoose.org/download.html
** GeoMOOSE is also compatible with MS4W.
** Link to material: Training materials are included in the download package as an operating demo.
*** Workshop materials: http://www.geomoose.org/downloads/workshops/foss4gna-2013/
**** NOTE: Newer version will be available by May 15th, 2016
*** The OSGeo Live page for GeoMOOSE includes the Overview and Quickstart:
**** http://live.osgeo.org/en/quickstart/geomoose_quickstart.html
**** http://live.osgeo.org/en/overview/geomoose_overview.html
** Contact: Bob Basques <bbasques AT sharedgeo.org>

== GET-IT ==

'''GET-IT''' - Geoinformation Enabling ToolkIT starterkit, supports researchers and professional in the creation of autonomous, distributed nodes of a Spatial Data Infrastructure and uploading research results in the form of maps/observations (and related metadata). GET-It supports domain researchers and professional in the creation of OGC standard services like WMS, WFS, WCS, CSW, and SOS. GET-It is based on GeoNode, contains pyCSW, 52° North SOS Server, Geoserver, PostgreSQL, PostGIS, OpenLayers and also contains EDI, a general purpose, customizable, template-driven metadata editor. The suite is the first open-source collaborative effort toward the integration of traditional geographic information with observational data.

*'''GET-IT Website''': http://www.get-it.it/
**'''EDI Website''': http://edidemo.get-it.it/
**'''Docs''': http://getit.readthedocs.org/en/latest/
**'''Demo''': http://demo2.get-it.it/
**'''Code''': https://github.com/SP7-Ritmare/starterkit
**'''Lab''': 103 IREA-CNR - http://www.irea.cnr.it/
**'''Point of Contact''': Alessandro Oggioni - oggioni.a@irea.cnr.it

==Open Source Geospatial Notebooks==
'''OSGeo-Notebooks''' - Development of interactive educational material in the form of geospatial notebooks based on the [http://jupyter.org/ Jupyter project].
This project is in active development (work in progress :) ), do not hesitate to contact me If interested in the integration of existing educational materials in the form of interactive notebooks.

* '''[https://github.com/epifanio/OSGeospatial-Notebooks Open Source Geospatial Notebooks]'''
** Contact: Massimo Di Stefano <epiesasha@me.com>

UNTraining

2016-04-15T16:29:38Z

Wiki-Epifanio:

'''Welcome to the UN training page'''

GeoForAll is supporting UN in their migration to geospatial open source applications. In this page we list the training material available for some products that UN will use. Please add your training material here, putting also the reference to all data used in such a way that everybody in using your material can be autonomous.

== QGIS ==

* Official manual + training manual: http://docs.qgis.org - Point of contact: QGIS Project Steering Committee

*'''FOSS4G GeoAcademy Curriculum''' - 35 hands-on labs written primarily for QGIS with some cross over with GRASS and Inkscape. Labs are aligned to the Geospatial Technology Competency Model. Development was sponsored by a Department of Labor Grant and is released under Creative Commons Attribute 3.0 Unported license. All labs currently written for QGIS 2.8, but we are about to release labs for QGIS 2.14. In addition to labs, lecture material is also developed and being uploaded. All lab instructions and data are [http://spatialquerylab.com/foss4g-academy-curriculum/ available online on our lab website].
**'''Link to material''': http://spatialquerylab.com/foss4g-academy-curriculum/
**'''Lab''': Spatial {Query} Lab - http://www.spatialquerylab.com
**'''Point of Contact''': Rick Smith - Richard.Smith@tamucc.edu
**'''Mailing Address''': 6300 Ocean Dr., Unit 5868, Corpus Christi, TX 78412-5868, USA

Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact

== gvSIG ==

gvSIG is a powerful, user-friendly and interoperable GIS. It is easy to work in a variety of formats, vector and raster files, databases and remote services. There are always available all kinds of tools to analyze and manage geographic information.

gvSIG Desktop is designed to be an easily extensible solution, allowing thus continually improving the software application and developing tailor made solutions. It is open source software, GNU / GPL license, this makes its free use, distribution, study and improvement. gvSIG Desktop integrates NASA World Wind, so it allows to work with 3D Views.

gvSIG Online is an Open Source solution for Spatial Data Infrastructures. It is an integral platform for the Spatial Data Infrastructure (SDI) implementation, 100% open source software. A fast and powerful solution for start up the infrastructure necessary to manage spatial data in an organization in an efficient way.

*Website: http://www.gvsig.com
** [http://www.gvsig.com/en/diffusion/educational-material?p_p_id=122_INSTANCE_A9eo37KAqtxs&p_p_lifecycle=0&p_p_state=normal&p_p_mode=view&p_p_col_id=column-2&p_p_col_count=1&p_r_p_564233524_resetCur=true&p_r_p_564233524_categoryId=25973 Educational material in English]
** [http://web.gvsig-training.com/index.php/en/quienes-somos-2/noticias-2/145-the-free-mooc-cycle-gvsig-for-users Free MOOC cycle "gvSIG for Users"]
** '''Point of Contact''': Mario Carrera - mcarrera [at] gvsig.com
* [https://www.youtube.com/user/gvsig gvSIG Youtube Channel]

== GRASS GIS ==

Geographic Resources Analysis Support System, commonly referred to as GRASS GIS, is a Geographic Information System (GIS) used for data management, image processing, graphics production, spatial modelling, and visualization of many types of data. URL: https://grass.osgeo.org

*'''NCSU Geospatial Analysis and Modeling course''' - 13 hands-on labs exercises used at North Carolina State University for teaching geospatial analysis and modeling with focus on terrain analysis, continuous surfaces, interpolation, geomorphometry, hydrology and erosion. We tested the exercises with GRASS GIS 7.0 and we update the material with every new release and academic semester. The material is released under Creative Commons Attribution-ShareAlike 4.0 International license (CC BY-SA 4.0) and the material is [https://github.com/ncsu-osgeorel/geospatial-modeling-course developed openly]. The course also includes software-independent lectures which are available online as recorded videos and presentations slides.
**'''Link to material''': http://ncsu-osgeorel.github.io/geospatial-modeling-course/grass/
**'''Lab''': NCSU OSGeoREL - https://geospatial.ncsu.edu/osgeorel
**'''Point of Contact''': Helena Mitasova - hmitaso@ncsu.edu
**'''Mailing Address''': 2800 Faucette Drive, North Carolina State University, Raleigh, NC 27695-8208, USA
*'''Workshop on urban growth modeling with FUTURES''' - A day long tutorial on GRASS GIS and urban growth modeling using the FUTURES model tested with GRASS GIS 7.0. The material is dual licensed under Creative Commons Attribution-ShareAlike 4.0 International license (CC BY-SA 4.0) and GNU Free Documentation License 1.2.
**'''Link to material''': https://grasswiki.osgeo.org/wiki/Workshop_on_urban_growth_modeling_with_FUTURES
**'''Lab''': NCSU OSGeoREL - https://geospatial.ncsu.edu/osgeorel
**'''Point of Contact''': Anna Petrasova - akratoc@ncsu.edu
**'''Mailing Address''': 2800 Faucette Drive, North Carolina State University, Raleigh, NC 27695-8208, USA

== GeoServer ==

GeoServer is an open source server for sharing geospatial data. Designed for interoperability, it publishes data from any major spatial data source using open standards.

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://workshops.boundlessgeo.com/geoserver-intro/ Introduction to GeoServer]
**'''Link to Material''': [http://workshops.boundlessgeo.com/suiteintro/ Introduction to Suite]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

*'''GeoSolutions Workshops''': [http://www.geo-solutions.it Website]
** '''Link to Material''': [http://geoserver.geo-solutions.it/edu/en/ GeoServer general training, four days worth of training material, from the first steps to production deploy setups, performance optimization and the like]
** '''Link to Material''': [http://geoserver.geo-solutions.it/multidim/en/ Spatio-temporal data handling with GeoServer]
** '''Link to Material''': [http://geoserver.geo-solutions.it/complexfeatures/ Complex features support and mapping with Hale]
** '''Point of Contact''': Andrea Aime - [mailto:andrea.aime@geo-solutions.it andrea.aime@geo-solutions.it]

*'''GeoServer Users Guide''': [http://docs.geoserver.org/latest/en/user/ Website]
**'''Link to Material''': [http://docs.geoserver.org/latest/en/user/extensions/css/workshop/index.html CSS styling workshop]
**'''Point of Contact''': Mike Pumphrey - [mailto:mike@boundlessgeo.com mike@boundlessgeo.com]

== OpenLayers ==

OpenLayers is a high-performance, feature-packed library for all your mapping needs.

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://workshops.boundlessgeo.com/openlayers3/ Introduction to OpenLayers]
**'''Link to Material''': [http://workshops.boundlessgeo.com/suiteintro/ Introduction to Suite]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

== PostgreSQL ==

Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact

== PostGIS ==

PostGIS is a spatial database extender for PostgreSQL object-relational database. It adds support for geographic objects allowing location queries to be run in SQL.

*''' University of Colorado Denver FOSS4G Lab''': [http://geospatial.ucdenver.edu/foss4g/ CU Denver FOSS4G Lab]
**'''PostgreSQL-PostGIS Tutorial Series''' Series of 7 tutorials covering the basics of PostGIS for spatial data handling and analysis.
**'''Link to material''': [http://geospatial.ucdenver.edu/foss4g/training/tutorials PostgreSQL-PostGIS Tutorials]
**'''Point of Contact''': Rafael Moreno - Rafael.Moreno@ucdenver.edu

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://workshops.boundlessgeo.com/postgis-intro/ Introduction to PostGIS]
**'''Link to Material''': [http://workshops.boundlessgeo.com/suiteintro/ Introduction to Suite]
**'''Link to Material''': [http://workshops.boundlessgeo.com/postgis-spatialdbtips/ Spatial Database Tips & Tricks]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

== GeoGig ==

GeoGig is an open source tool that draws inspiration from Git, but adapts its core concepts to handle distributed versioning of geospatial data.

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://geogig.org/workshop/ GeoGig Workshop]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

== GeoNode ==

GeoNode is a web-based application and platform for developing geospatial information systems (GIS) and for deploying spatial data infrastructures (SDI).

**'''Email List''': [http://lists.osgeo.org/mailman/listinfo/geonode-users geonode-users] and [http://lists.osgeo.org/mailman/listinfo/geonode-dev geonode-dev]
* Website: http://geonode.org
** Demo: http://demo.geonode.org
**'''Link to material''': http://docs.geonode.org/en/latest/index.html
**'''Point of Contact''': Vivien Deparday - [mailto:vdeparday@worldbank.org vdeparday@worldbank.org], Ariel Núñez - [mailto:ingenieroariel@gmail.com ingenieroariel@gmail.com], Paolo Corti - [mailto:pcorti@fas.harvard.edu pcorti@fas.harvard.edu]

== Rasdaman ==

*'''[http://www.rasdaman.org rasdaman]'''
**'''Big Geo Data Lab''' - Spatio-temporal sensor, image, simulation, and statistics data of unlimited size are served rapidly by rasdaman ("raster data manager"). As a multiparallel, distributed analytics engine, rasdaman achieves unparalleled service flexibility, scalability, and performance. Being OGC [http://en.wikipedia.org/wiki/Web_Coverage_Processing_Service WCPS] and [http://en.wikipedia.org/wiki/Web_Coverage_Service WCS] Core Reference Implementation, rasdaman enables access, subsetting, and processing on the fly using open standards interfaces. The WCS suite is a central cornerstone for SDIs: a large, growing number of open-source and proprietary tools supports it (MapServer, GeoServer, OpenLayers, QGIS, ESRI ArcGIS, ...) and the OGC standards are under adoption by ISO (as forthcoming 19123-2) and INSPIRE ("Coverage Download Service"). Significant training material is available already, and is being augmented continuously:
**'''Link to material''': [http://rasdaman.org/wiki/Workshops OGC Big Geo Data standards and rasdaman workshops] | [http://standards.rasdaman.com/ hands-on lab on Big Data Standards] | [http://kahlua.eecs.jacobs-university.de/~lsis/Big-Earth-Data_the-ARTE-Movie/index.php Big Earth Data] (53min TV documentary)
**'''Point of Contact''': Peter Baumann - baumann@rasdaman.com

== OSGeo-Live ==

OSGeo-Live contains 50 of the best geospatial applications, pre-installed with datasets, along with project overviews and 10 to 15 minute quickstarts for each application and ~ 45 minute presentation of them all. The documentation provides an excellent high level overview of the breadth of geospatial open source applications. It is also used as a plaform for many open source geospatial workshops.

* Project Overviews and Quickstarts: http://live.osgeo.org/en/overview/overview.html
* Presentation: http://live.osgeo.org/en/presentation/index.html#/
* Contact: Cameron Shorter <cam e r onDoTs hort erA T g mai l.com>

*'''Bringing GEOSS services into practice'''
The "Bringing GEOSS services into practice" workshop aims at teaching how to configure, use and deploy a set of open source software (PostGIS, GeoServer, GeoNetwork, PyWPS, QGIS) to set up a spatial data infrastructure (SDI). Trainees will learn how to publish and share data and metadata using OGC and ISO standards and how to register services into the Global Earth Observation System of Systems (GEOSS).

Website: http://www.geossintopractice.org

Lab: GeoForAll - ISE, University of Geneva: http://www.unige.ch/tigers/fr/autres-reseaux/geoforall/

Contact: Gregory Giuliani <gregory.giuliani AT unige.ch>

== GeoMOOSE ==

GeoMOOSE is a Web Client JavaScript Framework for displaying distributed cartographic data. GeoMOOSE has a number of strengths including modularity, configurability, and delivers a number of core functionalities in its packages. GeoMOOSE is also very light weight for servers making it easy to handle a large number of users, with a large number of layers, and a large number of services without stressing a server.

The GeoMOOSE core is written using JavaScript and HTML. It is entirely possible to run GeoMOOSE with nothing more than a basic web server (Nginx, Apache, IIS). But besides the basic client core, GeoMOOSE also comes prepackaged with a number of built in services written in PHP. These services add the ability to perform drill-down identify operations, selection operations, and search data sets. If you have existing scripts that perform similar functions, GeoMOOSE can be tuned to work with those services, no matter which language they were written in.

* Website: http://www.geomoose.org
** Online Demo: http://demo.geomoose.org/master/
** Package download (includes operating demo with sample data): http://geomoose.org/download.html
** GeoMOOSE is also compatible with MS4W.
** Link to material: Training materials are included in the download package as an operating demo.
*** Workshop materials: http://www.geomoose.org/downloads/workshops/foss4gna-2013/
**** NOTE: Newer version will be available by May 15th, 2016
*** The OSGeo Live page for GeoMOOSE includes the Overview and Quickstart:
**** http://live.osgeo.org/en/quickstart/geomoose_quickstart.html
**** http://live.osgeo.org/en/overview/geomoose_overview.html
** Contact: Bob Basques <bbasques AT sharedgeo.org>

== GET-IT ==

'''GET-IT''' - Geoinformation Enabling ToolkIT starterkit, supports researchers and professional in the creation of autonomous, distributed nodes of a Spatial Data Infrastructure and uploading research results in the form of maps/observations (and related metadata). GET-It supports domain researchers and professional in the creation of OGC standard services like WMS, WFS, WCS, CSW, and SOS. GET-It is based on GeoNode, contains pyCSW, 52° North SOS Server, Geoserver, PostgreSQL, PostGIS, OpenLayers and also contains EDI, a general purpose, customizable, template-driven metadata editor. The suite is the first open-source collaborative effort toward the integration of traditional geographic information with observational data.

*'''GET-IT Website''': http://www.get-it.it/
**'''EDI Website''': http://edidemo.get-it.it/
**'''Docs''': http://getit.readthedocs.org/en/latest/
**'''Demo''': http://demo2.get-it.it/
**'''Code''': https://github.com/SP7-Ritmare/starterkit
**'''Lab''': 103 IREA-CNR - http://www.irea.cnr.it/
**'''Point of Contact''': Alessandro Oggioni - oggioni.a@irea.cnr.it

==Open Source Geospatial Notebooks==
'''OSGeo-Notebooks''' - Development of interactive educational material in the form of geospatial notebooks based on the [http://jupyter.org/ Jupyter project].
This project is in active development (work in progress :) ), do not hesitate to contact me If interested in the integration of existing educational materials in the form of interactive notebooks.

* [https://github.com/epifanio/OSGeospatial-Notebooks Open Source Geospatial Notebooks]
** Contact: Massimo Di Stefano <epiesasha@me.com>

UNTraining

2016-04-14T00:06:48Z

Wiki-Epifanio: /* OSGeo-Live */

'''Welcome to the UN training page'''

GeoForAll is supporting UN in their migration to geospatial open source applications. In this page we list the training material available for some products that UN will use. Please add your training material here, putting also the reference to all data used in such a way that everybody in using your material can be autonomous.

== QGIS ==

* Official manual + training manual: http://docs.qgis.org - Point of contact: QGIS Project Steering Committee

*'''FOSS4G GeoAcademy Curriculum''' - 35 hands-on labs written primarily for QGIS with some cross over with GRASS and Inkscape. Labs are aligned to the Geospatial Technology Competency Model. Development was sponsored by a Department of Labor Grant and is released under Creative Commons Attribute 3.0 Unported license. All labs currently written for QGIS 2.8, but we are about to release labs for QGIS 2.14. In addition to labs, lecture material is also developed and being uploaded. All lab instructions and data are [http://spatialquerylab.com/foss4g-academy-curriculum/ available online on our lab website].
**'''Link to material''': http://spatialquerylab.com/foss4g-academy-curriculum/
**'''Lab''': Spatial {Query} Lab - http://www.spatialquerylab.com
**'''Point of Contact''': Rick Smith - Richard.Smith@tamucc.edu
**'''Mailing Address''': 6300 Ocean Dr., Unit 5868, Corpus Christi, TX 78412-5868, USA

Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact

== gvSIG ==

gvSIG is a powerful, user-friendly and interoperable GIS. It is easy to work in a variety of formats, vector and raster files, databases and remote services. There are always available all kinds of tools to analyze and manage geographic information.

gvSIG Desktop is designed to be an easily extensible solution, allowing thus continually improving the software application and developing tailor made solutions. It is open source software, GNU / GPL license, this makes its free use, distribution, study and improvement. gvSIG Desktop integrates NASA World Wind, so it allows to work with 3D Views.

gvSIG Online is an Open Source solution for Spatial Data Infrastructures. It is an integral platform for the Spatial Data Infrastructure (SDI) implementation, 100% open source software. A fast and powerful solution for start up the infrastructure necessary to manage spatial data in an organization in an efficient way.

*Website: http://www.gvsig.com
** [http://www.gvsig.com/en/diffusion/educational-material?p_p_id=122_INSTANCE_A9eo37KAqtxs&p_p_lifecycle=0&p_p_state=normal&p_p_mode=view&p_p_col_id=column-2&p_p_col_count=1&p_r_p_564233524_resetCur=true&p_r_p_564233524_categoryId=25973 Educational material in English]
** [http://web.gvsig-training.com/index.php/en/quienes-somos-2/noticias-2/145-the-free-mooc-cycle-gvsig-for-users Free MOOC cycle "gvSIG for Users"]
** '''Point of Contact''': Mario Carrera - mcarrera [at] gvsig.com
* [https://www.youtube.com/user/gvsig gvSIG Youtube Channel]

== GRASS GIS ==

*'''NCSU Geospatial Analysis and Modeling course''' - 13 hands-on labs exercises used at North Carolina State University for teaching geospatial analysis and modeling with focus on terrain analysis, continuous surfaces, interpolation, geomorphometry, hydrology and erosion. We tested the exercises with GRASS GIS 7.0 and we update the material with every new release and academic semester. The material is released under Creative Commons Attribution-ShareAlike 4.0 International license (CC BY-SA 4.0) and the material is [https://github.com/ncsu-osgeorel/geospatial-modeling-course developed openly]. The course also includes software-independent lectures which are available online as recorded videos and presentations slides.
**'''Link to material''': http://ncsu-osgeorel.github.io/geospatial-modeling-course/grass/
**'''Lab''': NCSU OSGeoREL - https://geospatial.ncsu.edu/osgeorel
**'''Point of Contact''': Helena Mitasova - hmitaso@ncsu.edu
**'''Mailing Address''': 2800 Faucette Drive, North Carolina State University, Raleigh, NC 27695-8208, USA
*'''Workshop on urban growth modeling with FUTURES''' - A day long tutorial on GRASS GIS and urban growth modeling using the FUTURES model tested with GRASS GIS 7.0. The material is dual licensed under Creative Commons Attribution-ShareAlike 4.0 International license (CC BY-SA 4.0) and GNU Free Documentation License 1.2.
**'''Link to material''': https://grasswiki.osgeo.org/wiki/Workshop_on_urban_growth_modeling_with_FUTURES
**'''Lab''': NCSU OSGeoREL - https://geospatial.ncsu.edu/osgeorel
**'''Point of Contact''': Anna Petrasova - akratoc@ncsu.edu
**'''Mailing Address''': 2800 Faucette Drive, North Carolina State University, Raleigh, NC 27695-8208, USA

== GeoServer ==

GeoServer is an open source server for sharing geospatial data. Designed for interoperability, it publishes data from any major spatial data source using open standards.

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://workshops.boundlessgeo.com/geoserver-intro/ Introduction to GeoServer]
**'''Link to Material''': [http://workshops.boundlessgeo.com/suiteintro/ Introduction to Suite]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

*'''GeoSolutions Workshops''': [http://www.geo-solutions.it Website]
** '''Link to Material''': [http://geoserver.geo-solutions.it/edu/en/ GeoServer general training, four days worth of training material, from the first steps to production deploy setups, performance optimization and the like]
** '''Link to Material''': [http://geoserver.geo-solutions.it/multidim/en/ Spatio-temporal data handling with GeoServer]
** '''Link to Material''': [http://geoserver.geo-solutions.it/complexfeatures/ Complex features support and mapping with Hale]
** '''Point of Contact''': Andrea Aime - [mailto:andrea.aime@geo-solutions.it andrea.aime@geo-solutions.it]

*'''GeoServer Users Guide''': [http://docs.geoserver.org/latest/en/user/ Website]
**'''Link to Material''': [http://docs.geoserver.org/latest/en/user/extensions/css/workshop/index.html CSS styling workshop]
**'''Point of Contact''': Mike Pumphrey - [mailto:mike@boundlessgeo.com mike@boundlessgeo.com]

== OpenLayers ==

OpenLayers is a high-performance, feature-packed library for all your mapping needs.

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://workshops.boundlessgeo.com/openlayers3/ Introduction to OpenLayers]
**'''Link to Material''': [http://workshops.boundlessgeo.com/suiteintro/ Introduction to Suite]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

== PostgreSQL ==

Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact

== PostGIS ==

PostGIS is a spatial database extender for PostgreSQL object-relational database. It adds support for geographic objects allowing location queries to be run in SQL.

*''' University of Colorado Denver FOSS4G Lab''': [http://geospatial.ucdenver.edu/foss4g/ CU Denver FOSS4G Lab]
**'''PostgreSQL-PostGIS Tutorial Series''' Series of 7 tutorials covering the basics of PostGIS for spatial data handling and analysis.
**'''Link to material''': [http://geospatial.ucdenver.edu/foss4g/training/tutorials PostgreSQL-PostGIS Tutorials]
**'''Point of Contact''': Rafael Moreno - Rafael.Moreno@ucdenver.edu

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://workshops.boundlessgeo.com/postgis-intro/ Introduction to PostGIS]
**'''Link to Material''': [http://workshops.boundlessgeo.com/suiteintro/ Introduction to Suite]
**'''Link to Material''': [http://workshops.boundlessgeo.com/postgis-spatialdbtips/ Spatial Database Tips & Tricks]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

== GeoGig ==

GeoGig is an open source tool that draws inspiration from Git, but adapts its core concepts to handle distributed versioning of geospatial data.

*'''Boundless Workshops''': [http://www.boundlessgeo.com/ Website]
**'''Link to Material''': [http://geogig.org/workshop/ GeoGig Workshop]
**'''Point of Contact''': Anthony Calamito - [mailto:acalamito@boundlessgeo.com acalamito@boundlessgeo.com]

== GeoNode ==

GeoNode is a web-based application and platform for developing geospatial information systems (GIS) and for deploying spatial data infrastructures (SDI).

**'''Email List''': [http://lists.osgeo.org/mailman/listinfo/geonode-users geonode-users] and [http://lists.osgeo.org/mailman/listinfo/geonode-dev geonode-dev]
* Website: http://geonode.org
** Demo: http://demo.geonode.org
**'''Link to material''': http://docs.geonode.org/en/latest/index.html
**'''Point of Contact''': Vivien Deparday - [mailto:vdeparday@worldbank.org vdeparday@worldbank.org], Ariel Núñez - [mailto:ingenieroariel@gmail.com ingenieroariel@gmail.com], Paolo Corti - [mailto:pcorti@fas.harvard.edu pcorti@fas.harvard.edu]

== Rasdaman ==

*'''[http://www.rasdaman.org rasdaman]'''
**'''Big Geo Data Lab''' - Spatio-temporal sensor, image, simulation, and statistics data of unlimited size are served rapidly by rasdaman ("raster data manager"). As a multiparallel, distributed analytics engine, rasdaman achieves unparalleled service flexibility, scalability, and performance. Being OGC [http://en.wikipedia.org/wiki/Web_Coverage_Processing_Service WCPS] and [http://en.wikipedia.org/wiki/Web_Coverage_Service WCS] Core Reference Implementation, rasdaman enables access, subsetting, and processing on the fly using open standards interfaces. The WCS suite is a central cornerstone for SDIs: a large, growing number of open-source and proprietary tools supports it (MapServer, GeoServer, OpenLayers, QGIS, ESRI ArcGIS, ...) and the OGC standards are under adoption by ISO (as forthcoming 19123-2) and INSPIRE ("Coverage Download Service"). Significant training material is available already, and is being augmented continuously:
**'''Link to material''': [http://rasdaman.org/wiki/Workshops OGC Big Geo Data standards and rasdaman workshops] | [http://standards.rasdaman.com/ hands-on lab on Big Data Standards] | [http://kahlua.eecs.jacobs-university.de/~lsis/Big-Earth-Data_the-ARTE-Movie/index.php Big Earth Data] (53min TV documentary)
**'''Point of Contact''': Peter Baumann - baumann@rasdaman.com

== OSGeo-Live ==

OSGeo-Live contains 50 of the best geospatial applications, pre-installed with datasets, along with project overviews and 10 to 15 minute quickstarts for each application. The documentation provides an excellent high level overview of the breadth of geospatial open source applications. It is also used as a plaform for many open source geospatial workshops.

* Website: http://live.osgeo.org
** Contact: Cameron Shorter <cam e r onDoTs hort erA T g mai l.com>

*'''Open Source Geospatial Notebooks:'''
A set of [http://jupyter.org/ jupyter notebook] that demonstrate the Open Source Geospatial Tools capabilities on OSGeo-live.
* [http://live.osgeo.org/en/overview/jupyter_overview.html overview]
* [http://live.osgeo.org/en/quickstart/jupyter_quickstart.html quickstart]
* [https://github.com/OSGeo/OSGeoLive-Notebooks github repository]
** Contact: Massimo Di Stefano <epiesasha@me.com>

*'''Bringing GEOSS services into practice'''
The "Bringing GEOSS services into practice" workshop aims at teaching how to configure, use and deploy a set of open source software (PostGIS, GeoServer, GeoNetwork, PyWPS, QGIS) to set up a spatial data infrastructure (SDI). Trainees will learn how to publish and share data and metadata using OGC and ISO standards and how to register services into the Global Earth Observation System of Systems (GEOSS).

Website: http://www.geossintopractice.org

Lab: GeoForAll - ISE, University of Geneva: http://www.unige.ch/tigers/fr/autres-reseaux/geoforall/

Contact: Gregory Giuliani <gregory.giuliani AT unige.ch>

== GeoMOOSE ==

GeoMOOSE is a Web Client JavaScript Framework for displaying distributed cartographic data. GeoMOOSE has a number of strengths including modularity, configurability, and delivers a number of core functionalities in its packages. GeoMOOSE is also very light weight for servers making it easy to handle a large number of users, with a large number of layers, and a large number of services without stressing a server.

The GeoMOOSE core is written using JavaScript and HTML. It is entirely possible to run GeoMOOSE with nothing more than a basic web server (Nginx, Apache, IIS). But besides the basic client core, GeoMOOSE also comes prepackaged with a number of built in services written in PHP. These services add the ability to perform drill-down identify operations, selection operations, and search data sets. If you have existing scripts that perform similar functions, GeoMOOSE can be tuned to work with those services, no matter which language they were written in.

* Website: http://www.geomoose.org
** Online Demo: http://demo.geomoose.org/master/
** Package download (includes operating demo with sample data): http://geomoose.org/download.html
** GeoMOOSE is also compatible with MS4W.
** Link to material: Training materials are included in the download package as an operating demo.
*** Workshop materials: http://www.geomoose.org/downloads/workshops/foss4gna-2013/
**** NOTE: Newer version will be available by May 15th, 2016
*** The OSGeo Live page for GeoMOOSE includes the Overview and Quickstart:
**** http://live.osgeo.org/en/quickstart/geomoose_quickstart.html
**** http://live.osgeo.org/en/overview/geomoose_overview.html
** Contact: Bob Basques <bbasques AT sharedgeo.org>

== GET-IT ==

'''GET-IT''' - Geoinformation Enabling ToolkIT starterkit, supports researchers and professional in the creation of autonomous, distributed nodes of a Spatial Data Infrastructure and uploading research results in the form of maps/observations (and related metadata). GET-It supports domain researchers and professional in the creation of OGC standard services like WMS, WFS, WCS, CSW, and SOS. GET-It is based on GeoNode, contains pyCSW, 52° North SOS Server, Geoserver, PostgreSQL, PostGIS, OpenLayers and also contains EDI, a general purpose, customizable, template-driven metadata editor. The suite is the first open-source collaborative effort toward the integration of traditional geographic information with observational data.

*'''GET-IT Website''': http://www.get-it.it/
**'''EDI Website''': http://edidemo.get-it.it/
**'''Docs''': http://getit.readthedocs.org/en/latest/
**'''Demo''': http://demo2.get-it.it/
**'''Code''': https://github.com/SP7-Ritmare/starterkit
**'''Lab''': 103 IREA-CNR - http://www.irea.cnr.it/
**'''Point of Contact''': Alessandro Oggioni - oggioni.a@irea.cnr.it

Google Summer of Code 2016 Administrative

2016-03-26T14:40:26Z

Wiki-Epifanio: /* Mentors */

<center>
[[Image:GSoC2016Logo.jpg|500px|link=https://summerofcode.withgoogle.com/]] @ [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]
</center>

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

This is the central page for OSGeo administrative information in Google Summer of Code 2016.

== GSoC general information ==

* [https://developers.google.com/open-source/gsoc/timeline The official timeline]
* [https://developers.google.com/open-source/gsoc/resources/ Google's FAQ on the program]
* [https://summerofcode.withgoogle.com/ Official 2016 GSoC site]

== Contacts ==

* [[User:Madi|Margherita Di Leo]] acts as Administrative contact, with support from [[User:Aghisla|Anne Ghisla]]. Feel free to email us with any questions, we're here to help mentor the mentors as much as anything else!

* Would-be mentors and students: you are invited to sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailing list] right away. The list is the central communication channel for mentors, students and administrators. It is used for general GSoC announcements, specific OSGeo announcements, and for clarification about the program. As soon as you subscribe it, you are encouraged to introduce yourself and your role. We look forward to hear from you!

== Mentors ==

If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please add your name, email, OSGeo/guest software and the projects you're interested in mentoring here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#D7E3D1; font-size:95%; empty-cells:show;"
|width=30px|'''Number'''
|width=100px|'''Name'''
|width=100px|'''Surname'''
|width=100px|'''Nickname (IRC)'''
|width=250px|'''email'''
|'''Software community'''
|'''Idea(s) you are available to mentor'''
|-
|1
|Margherita
|Di Leo
|madi
|diregola AT gmail DOT com
|admin at OSGeo
|Idea I would like to mentor
|-
|2
|Alexander
|Bruy
|alexbruy
|alexander.bruy AT gmail.com
|QGIS
|
|-
|3
|Victor
|Olaya
|volaya
|volayaf AT gmail DOT com
|QGIS
|
|-
|4
|Daniel
|Kastl
|dkastl
|daniel AT georepublic DOT de
|pgRouting
|
|-
|5
|Massimiliano
|Cannata
|maxi
|massimiliano.cannata AT gmail DOT com
|istSOS
|
|-
|6
|Milan
|Antonovic
|milan
|milan.antonovic AT gmail DOT com
|istSOS
|
|-
|7
|Jachym
|Cepicky
|jachym
|jachym.cepicky AT gmail
|PyWPS
|
|-
|8
|Andrea
|Antonello
|moovida
|andrea.antonello AT gmail DOT com
|JGrasstools, gvSIG, Geopaparazzi
|
|-
|9
|Rashad
|Kanavath
|rashadkm
|rashadkm AT gmail DOT com
|GRASS GIS, OSSIM, GDAL
|
|-
|10
|Cameron
|Shorter
|CameronShorter
|cameronDOTs h o r ter AT gmail com
|OSGeo-Live
|
|-
|11
|Stephen
|Woodbridge
|woodbri
|woodbri AT swoodbridge DOT com
|pgRouting
|
|-
|12
|Vicky
|Vergara
|cvvergara
|vicky AT georepublic DOT de
|pgRouting
|
|-
|13
|Dmitry
|Baryshnikov
|bishop
|bishop.dev AT gmail.com
|GDAL
|
|-
|14
|Luca
|Delucchi
|lucadelu
|lucadeluge AT gmail.com
|GRASS GIS
|
|-
|15
|Anna
|Petrasova
|
|kratochanna AT gmail.com
|GRASS GIS
|
|-
|16
|Stefan
|Steiniger
|
|sstein AT geo.uzh.ch
|OneBusAway, OpenTripPlanner, OpenJUMP
|for OneBusAway see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here]
|-
|17
|Sean
|Barbeau
|
|barbeau AT cutr.usf.edu
|OneBusAway, OpenTripPlanner
|for OneBusAway see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here], also there are ideas around for OpenTripPlanner Android App, and the GTFS-RT Validator
|-
|18
|Riccardo
|Rigon
|abouthydrology
|rccrd.rgn AT gmail DOT com
|JGrasstools, gvSIG, Geopaparazzi
|
|-
|19
|Vaclav
|Petras
|
|wenzeslaus AT gmail.com
|GRASS GIS
|
|-
|20
|Oliver
|May
|
|oliver AT dfc DOT be
|Geomajas, leaflet, openlayers, geoserver, geotools
|
|-
|21
|Even
|Rouault
|
|even dot rouault AT spatialys dot com
|GDAL
|
|-
|22
|Alexandre
|Dubé
|
|adube AT mapgears dot com
|OL3-Google-Maps
|
|-
|23
|Moritz
|Lennert
|
|mlennert AT club dot worldonline dot be
|GRASS GIS
|
|-
|24
|Roberto
|Marzocchi
|
|roberto dot marzocchi AT gmail dot com dot
|GRASS GIS
|
|-
|25
|Brian M
|Hamlin
|darkblue_b
|maplabs AT light42 DOT com
|SciPy geospatial stack, PostGIS, gdal 2.0
|
|-
|26
|Jessica
|Lapointe
|
|jlapointe AT mapgears dot com
|OL3-Google-Maps
|
|-
|27
|Gérald
|Fenoy
|djay
|gerald.fenoy AT geolabs.fr
|ZOO-Project
|
|-
|28
|Massimo
|Di Stefano
|epifanio
|epiesasha AT me DOT com
|GRASS GIS
| webgrass
|-
|29
|Patrick
|Hogan
|
|patrick.hogan AT nasa DOT gov
|NASA World Wind
|
|-
|30
|Oscar
|Kramer
|
|oscarkramer AT yahoo DOT com
|OSSIM
|
|-
|31
|Jakub
|Balhar
|
|jakub AT balhar DOT net
|NASA World Wind
|
|-
|32
|Jonas
|Eberle
|
|jonas.eberle AT gmx DOT de
|PyWPS
|
|-
|33
|Martin
|Landa
|
|landa.martin AT gmail DOT com
|GRASS GIS
|
|-
|34
|Rob
|Emanuele
|lossyrob
|rdemanuele AT gmail DOT com
|GDAL
|
|-
|}

== A Mentor's Responsibilities ==

Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.

Every student project will also have a '''backup mentor''', this person should come from your dev community and should at minimum keep up to date with the student's weekly developments. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.

You '''must''' be available at some time during the '''midterm and final evaluation period'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filed within these dates.

== Guides for mentors ==

* [http://en.flossmanuals.net/GSoCMentoring/ The GSoC Mentoring Guide] - A must. Do get all useful info and tips from many years of experience from GSoC mentors.
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]

== Tips for mentors ==

This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.

=== Good ideas ===

* Test students before selection. Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand if they are capable.
* Time management tips: Try not to mentor more than one project per year. In any case, you can be primary mentor only for one project. Consider carefully the time that you can allocate on GSoC.
* ...

=== Bad ideas ===

* ...

== Learn more ==

* Previous years SoC involvement: [http://code.google.com/soc/2008/osgeo/about.html 2008], [http://www.google-melange.com/gsoc/org/google/gsoc2009/osgeo 2009], [http://www.google-melange.com/gsoc/org/google/gsoc2010/osgeo 2010], [http://www.google-melange.com/gsoc/org/google/gsoc2011/osgeo 2011], [http://www.google-melange.com/gsoc/org/google/gsoc2012/osgeo 2012], [http://www.google-melange.com/gsoc/org/google/gsoc2013/osgeo 2013], [https://www.google-melange.com/gsoc/org2/google/gsoc2015/osgeo 2015]

* OSGeo GSoC wiki pages: [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2009|2009]], [[Google Summer of Code 2010|2010]], [[Google Summer of Code 2011|2011]], [[Google Summer of Code 2012|2012]], [[Google Summer of Code 2013|2013]], [[Google Summer of Code 2014|2014]], [[Google Summer of Code 2015|2015]]

* OSGeo Applications: [[Google SoC Application 2009|2009]], [[Google SoC Application 2010|2010]], [[Google Summer of Code Application 2011|2011]], [[Google Summer of Code Application 2012|2012]], [[Google Summer of Code Application 2013|2013]], [[Google Summer of Code Application 2014|2014]], [[Google Summer of Code Application 2015|2015]], [[Google Summer of Code Application 2016|2016]]

[[Category: Google Summer of Code]]

Google Summer of Code 2016 Administrative

2016-03-26T14:39:47Z

Wiki-Epifanio: /* Mentors */

<center>
[[Image:GSoC2016Logo.jpg|500px|link=https://summerofcode.withgoogle.com/]] @ [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]
</center>

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

This is the central page for OSGeo administrative information in Google Summer of Code 2016.

== GSoC general information ==

* [https://developers.google.com/open-source/gsoc/timeline The official timeline]
* [https://developers.google.com/open-source/gsoc/resources/ Google's FAQ on the program]
* [https://summerofcode.withgoogle.com/ Official 2016 GSoC site]

== Contacts ==

* [[User:Madi|Margherita Di Leo]] acts as Administrative contact, with support from [[User:Aghisla|Anne Ghisla]]. Feel free to email us with any questions, we're here to help mentor the mentors as much as anything else!

* Would-be mentors and students: you are invited to sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailing list] right away. The list is the central communication channel for mentors, students and administrators. It is used for general GSoC announcements, specific OSGeo announcements, and for clarification about the program. As soon as you subscribe it, you are encouraged to introduce yourself and your role. We look forward to hear from you!

== Mentors ==

If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please add your name, email, OSGeo/guest software and the projects you're interested in mentoring here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#D7E3D1; font-size:95%; empty-cells:show;"
|width=30px|'''Number'''
|width=100px|'''Name'''
|width=100px|'''Surname'''
|width=100px|'''Nickname (IRC)'''
|width=250px|'''email'''
|'''Software community'''
|'''Idea(s) you are available to mentor'''
|-
|1
|Margherita
|Di Leo
|madi
|diregola AT gmail DOT com
|admin at OSGeo
|Idea I would like to mentor
|-
|2
|Alexander
|Bruy
|alexbruy
|alexander.bruy AT gmail.com
|QGIS
|
|-
|3
|Victor
|Olaya
|volaya
|volayaf AT gmail DOT com
|QGIS
|
|-
|4
|Daniel
|Kastl
|dkastl
|daniel AT georepublic DOT de
|pgRouting
|
|-
|5
|Massimiliano
|Cannata
|maxi
|massimiliano.cannata AT gmail DOT com
|istSOS
|
|-
|6
|Milan
|Antonovic
|milan
|milan.antonovic AT gmail DOT com
|istSOS
|
|-
|7
|Jachym
|Cepicky
|jachym
|jachym.cepicky AT gmail
|PyWPS
|
|-
|8
|Andrea
|Antonello
|moovida
|andrea.antonello AT gmail DOT com
|JGrasstools, gvSIG, Geopaparazzi
|
|-
|9
|Rashad
|Kanavath
|rashadkm
|rashadkm AT gmail DOT com
|GRASS GIS, OSSIM, GDAL
|
|-
|10
|Cameron
|Shorter
|CameronShorter
|cameronDOTs h o r ter AT gmail com
|OSGeo-Live
|
|-
|11
|Stephen
|Woodbridge
|woodbri
|woodbri AT swoodbridge DOT com
|pgRouting
|
|-
|12
|Vicky
|Vergara
|cvvergara
|vicky AT georepublic DOT de
|pgRouting
|
|-
|13
|Dmitry
|Baryshnikov
|bishop
|bishop.dev AT gmail.com
|GDAL
|
|-
|14
|Luca
|Delucchi
|lucadelu
|lucadeluge AT gmail.com
|GRASS GIS
|
|-
|15
|Anna
|Petrasova
|
|kratochanna AT gmail.com
|GRASS GIS
|
|-
|16
|Stefan
|Steiniger
|
|sstein AT geo.uzh.ch
|OneBusAway, OpenTripPlanner, OpenJUMP
|for OneBusAway see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here]
|-
|17
|Sean
|Barbeau
|
|barbeau AT cutr.usf.edu
|OneBusAway, OpenTripPlanner
|for OneBusAway see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here], also there are ideas around for OpenTripPlanner Android App, and the GTFS-RT Validator
|-
|18
|Riccardo
|Rigon
|abouthydrology
|rccrd.rgn AT gmail DOT com
|JGrasstools, gvSIG, Geopaparazzi
|
|-
|19
|Vaclav
|Petras
|
|wenzeslaus AT gmail.com
|GRASS GIS
|
|-
|20
|Oliver
|May
|
|oliver AT dfc DOT be
|Geomajas, leaflet, openlayers, geoserver, geotools
|
|-
|21
|Even
|Rouault
|
|even dot rouault AT spatialys dot com
|GDAL
|
|-
|22
|Alexandre
|Dubé
|
|adube AT mapgears dot com
|OL3-Google-Maps
|
|-
|23
|Moritz
|Lennert
|
|mlennert AT club dot worldonline dot be
|GRASS GIS
|
|-
|24
|Roberto
|Marzocchi
|
|roberto dot marzocchi AT gmail dot com dot
|GRASS GIS
|
|-
|25
|Brian M
|Hamlin
|darkblue_b
|maplabs AT light42 DOT com
|SciPy geospatial stack, PostGIS, gdal 2.0
|
|-
|26
|Jessica
|Lapointe
|
|jlapointe AT mapgears dot com
|OL3-Google-Maps
|
|-
|27
|Gérald
|Fenoy
|djay
|gerald.fenoy AT geolabs.fr
|ZOO-Project
|
|-
|28
|Massimo
|Di Stefano
|epifanio
|epiesasha AT me DOT com
|GRASS GIS,
|
|-
|29
|Patrick
|Hogan
|
|patrick.hogan AT nasa DOT gov
|NASA World Wind
|
|-
|30
|Oscar
|Kramer
|
|oscarkramer AT yahoo DOT com
|OSSIM
|
|-
|31
|Jakub
|Balhar
|
|jakub AT balhar DOT net
|NASA World Wind
|
|-
|32
|Jonas
|Eberle
|
|jonas.eberle AT gmx DOT de
|PyWPS
|
|-
|33
|Martin
|Landa
|
|landa.martin AT gmail DOT com
|GRASS GIS
|
|-
|34
|Rob
|Emanuele
|lossyrob
|rdemanuele AT gmail DOT com
|GDAL
|
|-
|}

== A Mentor's Responsibilities ==

Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.

Every student project will also have a '''backup mentor''', this person should come from your dev community and should at minimum keep up to date with the student's weekly developments. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.

You '''must''' be available at some time during the '''midterm and final evaluation period'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filed within these dates.

== Guides for mentors ==

* [http://en.flossmanuals.net/GSoCMentoring/ The GSoC Mentoring Guide] - A must. Do get all useful info and tips from many years of experience from GSoC mentors.
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]

== Tips for mentors ==

This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.

=== Good ideas ===

* Test students before selection. Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand if they are capable.
* Time management tips: Try not to mentor more than one project per year. In any case, you can be primary mentor only for one project. Consider carefully the time that you can allocate on GSoC.
* ...

=== Bad ideas ===

* ...

== Learn more ==

* Previous years SoC involvement: [http://code.google.com/soc/2008/osgeo/about.html 2008], [http://www.google-melange.com/gsoc/org/google/gsoc2009/osgeo 2009], [http://www.google-melange.com/gsoc/org/google/gsoc2010/osgeo 2010], [http://www.google-melange.com/gsoc/org/google/gsoc2011/osgeo 2011], [http://www.google-melange.com/gsoc/org/google/gsoc2012/osgeo 2012], [http://www.google-melange.com/gsoc/org/google/gsoc2013/osgeo 2013], [https://www.google-melange.com/gsoc/org2/google/gsoc2015/osgeo 2015]

* OSGeo GSoC wiki pages: [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2009|2009]], [[Google Summer of Code 2010|2010]], [[Google Summer of Code 2011|2011]], [[Google Summer of Code 2012|2012]], [[Google Summer of Code 2013|2013]], [[Google Summer of Code 2014|2014]], [[Google Summer of Code 2015|2015]]

* OSGeo Applications: [[Google SoC Application 2009|2009]], [[Google SoC Application 2010|2010]], [[Google Summer of Code Application 2011|2011]], [[Google Summer of Code Application 2012|2012]], [[Google Summer of Code Application 2013|2013]], [[Google Summer of Code Application 2014|2014]], [[Google Summer of Code Application 2015|2015]], [[Google Summer of Code Application 2016|2016]]

[[Category: Google Summer of Code]]

Google Summer of Code 2016 Administrative

2016-03-26T14:39:06Z

Wiki-Epifanio: /* Mentors */

<center>
[[Image:GSoC2016Logo.jpg|500px|link=https://summerofcode.withgoogle.com/]] @ [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]
</center>

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

This is the central page for OSGeo administrative information in Google Summer of Code 2016.

== GSoC general information ==

* [https://developers.google.com/open-source/gsoc/timeline The official timeline]
* [https://developers.google.com/open-source/gsoc/resources/ Google's FAQ on the program]
* [https://summerofcode.withgoogle.com/ Official 2016 GSoC site]

== Contacts ==

* [[User:Madi|Margherita Di Leo]] acts as Administrative contact, with support from [[User:Aghisla|Anne Ghisla]]. Feel free to email us with any questions, we're here to help mentor the mentors as much as anything else!

* Would-be mentors and students: you are invited to sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailing list] right away. The list is the central communication channel for mentors, students and administrators. It is used for general GSoC announcements, specific OSGeo announcements, and for clarification about the program. As soon as you subscribe it, you are encouraged to introduce yourself and your role. We look forward to hear from you!

== Mentors ==

If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please add your name, email, OSGeo/guest software and the projects you're interested in mentoring here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#D7E3D1; font-size:95%; empty-cells:show;"
|width=30px|'''Number'''
|width=100px|'''Name'''
|width=100px|'''Surname'''
|width=100px|'''Nickname (IRC)'''
|width=250px|'''email'''
|'''Software community'''
|'''Idea(s) you are available to mentor'''
|-
|1
|Margherita
|Di Leo
|madi
|diregola AT gmail DOT com
|admin at OSGeo
|Idea I would like to mentor
|-
|2
|Alexander
|Bruy
|alexbruy
|alexander.bruy AT gmail.com
|QGIS
|
|-
|3
|Victor
|Olaya
|volaya
|volayaf AT gmail DOT com
|QGIS
|
|-
|4
|Daniel
|Kastl
|dkastl
|daniel AT georepublic DOT de
|pgRouting
|
|-
|5
|Massimiliano
|Cannata
|maxi
|massimiliano.cannata AT gmail DOT com
|istSOS
|
|-
|6
|Milan
|Antonovic
|milan
|milan.antonovic AT gmail DOT com
|istSOS
|
|-
|7
|Jachym
|Cepicky
|jachym
|jachym.cepicky AT gmail
|PyWPS
|
|-
|8
|Andrea
|Antonello
|moovida
|andrea.antonello AT gmail DOT com
|JGrasstools, gvSIG, Geopaparazzi
|
|-
|9
|Rashad
|Kanavath
|rashadkm
|rashadkm AT gmail DOT com
|GRASS GIS, OSSIM, GDAL
|
|-
|10
|Cameron
|Shorter
|CameronShorter
|cameronDOTs h o r ter AT gmail com
|OSGeo-Live
|
|-
|11
|Stephen
|Woodbridge
|woodbri
|woodbri AT swoodbridge DOT com
|pgRouting
|
|-
|12
|Vicky
|Vergara
|cvvergara
|vicky AT georepublic DOT de
|pgRouting
|
|-
|13
|Dmitry
|Baryshnikov
|bishop
|bishop.dev AT gmail.com
|GDAL
|
|-
|14
|Luca
|Delucchi
|lucadelu
|lucadeluge AT gmail.com
|GRASS GIS
|
|-
|15
|Anna
|Petrasova
|
|kratochanna AT gmail.com
|GRASS GIS
|
|-
|16
|Stefan
|Steiniger
|
|sstein AT geo.uzh.ch
|OneBusAway, OpenTripPlanner, OpenJUMP
|for OneBusAway see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here]
|-
|17
|Sean
|Barbeau
|
|barbeau AT cutr.usf.edu
|OneBusAway, OpenTripPlanner
|for OneBusAway see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here], also there are ideas around for OpenTripPlanner Android App, and the GTFS-RT Validator
|-
|18
|Riccardo
|Rigon
|abouthydrology
|rccrd.rgn AT gmail DOT com
|JGrasstools, gvSIG, Geopaparazzi
|
|-
|19
|Vaclav
|Petras
|
|wenzeslaus AT gmail.com
|GRASS GIS
|
|-
|20
|Oliver
|May
|
|oliver AT dfc DOT be
|Geomajas, leaflet, openlayers, geoserver, geotools
|
|-
|21
|Even
|Rouault
|
|even dot rouault AT spatialys dot com
|GDAL
|
|-
|22
|Alexandre
|Dubé
|
|adube AT mapgears dot com
|OL3-Google-Maps
|
|-
|23
|Moritz
|Lennert
|
|mlennert AT club dot worldonline dot be
|GRASS GIS
|
|-
|24
|Roberto
|Marzocchi
|
|roberto dot marzocchi AT gmail dot com dot
|GRASS GIS
|
|-
|25
|Brian M
|Hamlin
|darkblue_b
|maplabs AT light42 DOT com
|SciPy geospatial stack, PostGIS, gdal 2.0
|
|-
|26
|Jessica
|Lapointe
|
|jlapointe AT mapgears dot com
|OL3-Google-Maps
|
|-
|27
|Gérald
|Fenoy
|djay
|gerald.fenoy AT geolabs.fr
|ZOO-Project
|
|-
|28
|Massimo
|Di Stefano
|epifanio
|epiesasha AT me DOT com
|GRASS GIS, webgrass, jupyter noytebook,
|
|-
|29
|Patrick
|Hogan
|
|patrick.hogan AT nasa DOT gov
|NASA World Wind
|
|-
|30
|Oscar
|Kramer
|
|oscarkramer AT yahoo DOT com
|OSSIM
|
|-
|31
|Jakub
|Balhar
|
|jakub AT balhar DOT net
|NASA World Wind
|
|-
|32
|Jonas
|Eberle
|
|jonas.eberle AT gmx DOT de
|PyWPS
|
|-
|33
|Martin
|Landa
|
|landa.martin AT gmail DOT com
|GRASS GIS
|
|-
|34
|Rob
|Emanuele
|lossyrob
|rdemanuele AT gmail DOT com
|GDAL
|
|-
|}

== A Mentor's Responsibilities ==

Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.

Every student project will also have a '''backup mentor''', this person should come from your dev community and should at minimum keep up to date with the student's weekly developments. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.

You '''must''' be available at some time during the '''midterm and final evaluation period'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filed within these dates.

== Guides for mentors ==

* [http://en.flossmanuals.net/GSoCMentoring/ The GSoC Mentoring Guide] - A must. Do get all useful info and tips from many years of experience from GSoC mentors.
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]

== Tips for mentors ==

This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.

=== Good ideas ===

* Test students before selection. Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand if they are capable.
* Time management tips: Try not to mentor more than one project per year. In any case, you can be primary mentor only for one project. Consider carefully the time that you can allocate on GSoC.
* ...

=== Bad ideas ===

* ...

== Learn more ==

* Previous years SoC involvement: [http://code.google.com/soc/2008/osgeo/about.html 2008], [http://www.google-melange.com/gsoc/org/google/gsoc2009/osgeo 2009], [http://www.google-melange.com/gsoc/org/google/gsoc2010/osgeo 2010], [http://www.google-melange.com/gsoc/org/google/gsoc2011/osgeo 2011], [http://www.google-melange.com/gsoc/org/google/gsoc2012/osgeo 2012], [http://www.google-melange.com/gsoc/org/google/gsoc2013/osgeo 2013], [https://www.google-melange.com/gsoc/org2/google/gsoc2015/osgeo 2015]

* OSGeo GSoC wiki pages: [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2009|2009]], [[Google Summer of Code 2010|2010]], [[Google Summer of Code 2011|2011]], [[Google Summer of Code 2012|2012]], [[Google Summer of Code 2013|2013]], [[Google Summer of Code 2014|2014]], [[Google Summer of Code 2015|2015]]

* OSGeo Applications: [[Google SoC Application 2009|2009]], [[Google SoC Application 2010|2010]], [[Google Summer of Code Application 2011|2011]], [[Google Summer of Code Application 2012|2012]], [[Google Summer of Code Application 2013|2013]], [[Google Summer of Code Application 2014|2014]], [[Google Summer of Code Application 2015|2015]], [[Google Summer of Code Application 2016|2016]]

[[Category: Google Summer of Code]]

Google Summer of Code 2016 Administrative

2016-03-20T09:26:37Z

Wiki-Epifanio: /* Mentors */

<center>
[[Image:GSoC2016Logo.jpg|500px|link=https://summerofcode.withgoogle.com/]] @ [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]
</center>

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

This is the central page for OSGeo administrative information in Google Summer of Code 2016.

== GSoC general information ==

* [https://developers.google.com/open-source/gsoc/timeline The official timeline]
* [https://developers.google.com/open-source/gsoc/resources/ Google's FAQ on the program]
* [https://summerofcode.withgoogle.com/ Official 2016 GSoC site]

== Contacts ==

* [[User:Madi|Margherita Di Leo]] acts as Administrative contact, with support from [[User:Aghisla|Anne Ghisla]]. Feel free to email us with any questions, we're here to help mentor the mentors as much as anything else!

* Would-be mentors and students: you are invited to sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailing list] right away. The list is the central communication channel for mentors, students and administrators. It is used for general GSoC announcements, specific OSGeo announcements, and for clarification about the program. As soon as you subscribe it, you are encouraged to introduce yourself and your role. We look forward to hear from you!

== Mentors ==

If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please add your name, email, OSGeo/guest software and the projects you're interested in mentoring here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#D7E3D1; font-size:95%; empty-cells:show;"
|width=30px|'''Number'''
|width=100px|'''Name'''
|width=100px|'''Surname'''
|width=100px|'''Nickname (IRC)'''
|width=250px|'''email'''
|'''Software community'''
|'''Idea(s) you are available to mentor'''
|-
|1
|Margherita
|Di Leo
|madi
|diregola AT gmail DOT com
|admin at OSGeo
|Idea I would like to mentor
|-
|2
|Alexander
|Bruy
|alexbruy
|alexander.bruy AT gmail.com
|QGIS
|
|-
|3
|Victor
|Olaya
|volaya
|volayaf AT gmail DOT com
|QGIS
|
|-
|4
|Daniel
|Kastl
|dkastl
|daniel AT georepublic DOT de
|pgRouting
|
|-
|5
|Massimiliano
|Cannata
|maxi
|massimiliano.cannata AT gmail DOT com
|istSOS
|
|-
|6
|Milan
|Antonovic
|milan
|milan.antonovic AT gmail DOT com
|istSOS
|
|-
|7
|Jachym
|Cepicky
|jachym
|jachym.cepicky AT gmail
|PyWPS
|
|-
|8
|Andrea
|Antonello
|moovida
|andrea.antonello AT gmail DOT com
|JGrasstools, gvSIG, Geopaparazzi
|
|-
|-
|9
|Rashad
|Kanavath
|rashadkm
|rashadkm AT gmail DOT com
|GRASS GIS, OSSIM, GDAL
|
|-
|10
|Cameron
|Shorter
|CameronShorter
|cameronDOTs h o r ter AT gmail com
|OSGeo-Live
|
|-
|11
|Stephen
|Woodbridge
|woodbri
|woodbri AT swoodbridge DOT com
|pgRouting
|
|-
|12
|Vicky
|Vergara
|cvvergara
|vicky AT georepublic DOT de
|pgRouting
|
|-
|13
|Dmitry
|Baryshnikov
|bishop
|bishop.dev AT gmail.com
|GDAL
|
|-
|14
|Luca
|Delucchi
|lucadelu
|lucadeluge AT gmail.com
|GRASS GIS
|
|-
|15
|Anna
|Petrasova
|
|kratochanna AT gmail.com
|GRASS GIS
|
|-
|16
|Stefan
|Steiniger
|
|sstein AT geo.uzh.ch
|OneBusAway, OpenTripPlanner, OpenJUMP
|for OneBusAway see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here]
|-
|17
|Sean
|Barbeau
|
|barbeau AT cutr.usf.edu
|OneBusAway, OpenTripPlanner
|for OneBusAway see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here], also there are ideas around for OpenTripPlanner Android App, and the GTFS-RT Validator
|-
|18
|Riccardo
|Rigon
|abouthydrology
|rccrd.rgn AT gmail DOT com
|JGrasstools, gvSIG, Geopaparazzi
|
|-
|19
|Vaclav
|Petras
|
|wenzeslaus AT gmail.com
|GRASS GIS
|
|-
|20
|Oliver
|May
|
|oliver AT dfc DOT be
|Geomajas, leaflet, openlayers, geoserver, geotools
|
|-
|21
|Even
|Rouault
|
|even dot rouault AT spatialys dot com
|GDAL
|
|-
|22
|Alexandre
|Dubé
|
|adube AT mapgears dot com
|OL3-Google-Maps
|
|
|-
|23
|Moritz
|Lennert
|
|mlennert AT club dot worldonline dot be
|GRASS GIS
|-
|24
|Roberto
|Marzocchi
|
|roberto dot marzocchi AT gmail dot com dot
|GRASS GIS
|
|-
|25
|Brian M
|Hamlin
|darkblue_b
|maplabs AT light42 DOT com
|SciPy geospatial stack, PostGIS, gdal 2.0
|
|-
|26
|Jessica
|Lapointe
|
|jlapointe AT mapgears dot com
|OL3-Google-Maps
|
|-
|27
|Gérald
|Fenoy
|djay
|gerald.fenoy AT geolabs.fr
|ZOO-Project
|-
|28
|Massimo
|Di Stefano
|epifanio
|epiesasha AT me DOT com
|jupyter noytebook, cross projects python based
|
|
|
|}

== A Mentor's Responsibilities ==

Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find :). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.

Every student project will also have a '''backup mentor''', this person should come from your programming team and should at minimum keep up to date with the student's weekly developments. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.

You '''must''' be available at some time during the '''midterm and final evaluation period'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filed within these dates.

== Guides for mentors ==

* [http://en.flossmanuals.net/GSoCMentoring/ The GSoC Mentoring Guide] - A must. Do get all useful info and tips from many years of experience from GSoC mentors.
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]

== Tips for mentors ==

This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.

=== Good ideas ===

* Test students before selection. Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand if they are capable.
* Be patient.

=== Bad ideas ===

== Learn more ==

* Previous years SoC involvement: [http://code.google.com/soc/2008/osgeo/about.html 2008], [http://www.google-melange.com/gsoc/org/google/gsoc2009/osgeo 2009], [http://www.google-melange.com/gsoc/org/google/gsoc2010/osgeo 2010], [http://www.google-melange.com/gsoc/org/google/gsoc2011/osgeo 2011], [http://www.google-melange.com/gsoc/org/google/gsoc2012/osgeo 2012], [http://www.google-melange.com/gsoc/org/google/gsoc2013/osgeo 2013], [https://www.google-melange.com/gsoc/org2/google/gsoc2015/osgeo 2015]

* OSGeo GSoC wiki pages: [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2009|2009]], [[Google Summer of Code 2010|2010]], [[Google Summer of Code 2011|2011]], [[Google Summer of Code 2012|2012]], [[Google Summer of Code 2013|2013]], [[Google Summer of Code 2014|2014]], [[Google Summer of Code 2015|2015]]

* OSGeo Applications: [[Google SoC Application 2009|2009]], [[Google SoC Application 2010|2010]], [[Google Summer of Code Application 2011|2011]], [[Google Summer of Code Application 2012|2012]], [[Google Summer of Code Application 2013|2013]], [[Google Summer of Code Application 2014|2014]], [[Google Summer of Code Application 2015|2015]], [[Google Summer of Code Application 2016|2016]]

[[Category: Google Summer of Code]]

Live GIS Add Project

2016-03-15T09:28:08Z

Wiki-Epifanio: /* Notebooks */

== 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 Lubuntu.

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

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

Ideally, your application will already be packaged as a .deb file, probably in UbuntuGIS. Then the main part of the script uses apt-get, such as
[https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_mapserver.sh install_mapserver.sh], which is primarily
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

The script should create an icon for desktop and menu. See section under: #### install desktop icon #### in [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_qgis.sh install_qgis.sh].

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

== 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/<project>
# '''/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.
# '''/var/www/html'''. This is the directory references. For user specific documentation, a symbolic link from this directory/<project> can point to /usr/local/share/<project>

* ''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]]

= Notebooks =

OSGeo-Live provides a set of digital notebooks to explore several open source solution for geospatial data analysis, with the aim of bridging together the several software libraries already installed on the OSGeo-live to perform complex geo-data-science workflows. The notebooks are developed in the [http://jupyter.org/ Jupyter] environments which is heavily based on the [http://ipython.org/notebook.html IPython notebook] project, are written id different languages (bash, python, R) and are organized in a series of "topic-oriented" geospatial notebooks.

Astatic HTML rendering of the notebooks shipped within the OSGeo-Live is available at: [http://nbviewer.jupyter.org/github/OSGeo/OSGeoLive-Notebooks/blob/master/index.ipynb OSGeoLive-Notebooks]

== Notebook-Guidelines ==

The intended use of the notebooks on the OSGeo-live is to include rich descriptive narrative to a data processing workflow, including the possibilities to interact with data through a nicely done interactive widget system and finally enabling the printing of publication-ready reports (see latex inline rendering and pdf export).

On the OSGeo-live, we are aiming to use the same [[Live_GIS_Add_Project#Example_Datasets|Example_Datasets]] among projects this way different software projects can be more easily compared, say for their usage complexity or for output quality/performance comparison.

Notebooks shipped within the OSGeo-live must:

* be the result of original work specifically designed to run on the OSGeo-live
* describe a workflow related to geospatial data analysis where code and software documentation are merged together by a rich descriptive narrative.
* use dataset already present on the OSGeo-live dis (Notebooks developer are free to generate novel data i.e.: from querying available database or using using numerical tools to generate synthetic dataset)
* avoid the use of network resources to allow offline use (alert the user otherwise)
* when applicable use hyperlinks to the official project documentation (i.e.: if use a GRASS GIS command, the notebook developer is invited to ad add reference to the official documentation available on the OSGeo-Live)

[[Category: Live-demo]]

Live GIS Add Project

2016-03-15T09:25:37Z

Wiki-Epifanio: /* Notebooks */

== 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 Lubuntu.

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

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

Ideally, your application will already be packaged as a .deb file, probably in UbuntuGIS. Then the main part of the script uses apt-get, such as
[https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_mapserver.sh install_mapserver.sh], which is primarily
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

The script should create an icon for desktop and menu. See section under: #### install desktop icon #### in [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_qgis.sh install_qgis.sh].

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

== 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/<project>
# '''/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.
# '''/var/www/html'''. This is the directory references. For user specific documentation, a symbolic link from this directory/<project> can point to /usr/local/share/<project>

* ''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]]

= Notebooks =

OSGeo-Live provides a set of digital notebooks to explore several open source solution for geospatial data analysis, with the aim of bridging together the several software libraries already installed on the OSGeo-live to perform complex geo-data-science workflows. The notebooks are developed in the [http://jupyter.org/ Jupyter] environments which is heavily based on the [http://ipython.org/notebook.html IPython notebook] project, are written id different languages (bash, python, R) and are organized in a series of "topic-oriented" geospatial notebooks.

== Notebook-Guidelines ==

The intended use of the notebooks on the OSGeo-live is to include rich descriptive narrative to a data processing workflow, including the possibilities to interact with data through a nicely done interactive widget system and finally enabling the printing of publication-ready reports (see latex inline rendering and pdf export).

On the OSGeo-live, we are aiming to use the same [[Live_GIS_Add_Project#Example_Datasets|Example_Datasets]] among projects this way different software projects can be more easily compared, say for their usage complexity or for output quality/performance comparison.

Notebooks shipped within the OSGeo-live must:

* be the result of original work specifically designed to run on the OSGeo-live
* describe a workflow related to geospatial data analysis where code and software documentation are merged together by a rich descriptive narrative.
* use dataset already present on the OSGeo-live dis (Notebooks developer are free to generate novel data i.e.: from querying available database or using using numerical tools to generate synthetic dataset)
* avoid the use of network resources to allow offline use (alert the user otherwise)
* when applicable use hyperlinks to the official project documentation (i.e.: if use a GRASS GIS command, the notebook developer is invited to ad add reference to the official documentation available on the OSGeo-Live)

[[Category: Live-demo]]

Live GIS Add Project

2016-03-15T09:22:06Z

Wiki-Epifanio:

== 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 Lubuntu.

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

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

Ideally, your application will already be packaged as a .deb file, probably in UbuntuGIS. Then the main part of the script uses apt-get, such as
[https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_mapserver.sh install_mapserver.sh], which is primarily
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

The script should create an icon for desktop and menu. See section under: #### install desktop icon #### in [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_qgis.sh install_qgis.sh].

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

== 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/<project>
# '''/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.
# '''/var/www/html'''. This is the directory references. For user specific documentation, a symbolic link from this directory/<project> can point to /usr/local/share/<project>

* ''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]]

= Notebooks =

Starting with OSGeo-Live 9.0 a set of digital notebooks to explore several open source solution for geospatial data analysis, with the aim of bridging together the several software libraries already installed on the OSGeo-live to perform complex geo-data-science workflows. The notebooks are developed in the Jupyter notebook server environments which is heavily based on the IPython project, are written id different languages (bash, python, R) and are organized in a series of "topic-oriented" geospatial notebooks.

== Notebook-Guidelines ==

The intended use of the notebooks on the OSGeo-live is to include rich descriptive narrative to a data processing workflow, including the possibilities to interact with data through a nicely done interactive widget system and finally enabling the printing of publication-ready reports (see latex inline rendering and pdf export).

On the OSGeo-live, we are aiming to use the same [[Live_GIS_Add_Project#Example_Datasets|Example_Datasets]] among projects this way different software projects can be more easily compared, say for their usage complexity or for output quality/performance comparison.

Notebooks shipped within the OSGeo-live must:

* be the result of original work specifically designed to run on the OSGeo-live
* describe a workflow related to geospatial data analysis where code and software documentation are merged together by a rich descriptive narrative.
* use dataset already present on the OSGeo-live dis (Notebooks developer are free to generate novel data i.e.: from querying available database or using using numerical tools to generate synthetic dataset)
* avoid the use of network resources to allow offline use (alert the user otherwise)
* when applicable use hyperlinks to the official project documentation (i.e.: if use a GRASS GIS command, the notebook developer is invited to ad add reference to the official documentation available on the OSGeo-Live)

[[Category: Live-demo]]

Live GIS Add Project

2016-03-15T09:21:33Z

Wiki-Epifanio:

== 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 Lubuntu.

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

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

Ideally, your application will already be packaged as a .deb file, probably in UbuntuGIS. Then the main part of the script uses apt-get, such as
[https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_mapserver.sh install_mapserver.sh], which is primarily
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

The script should create an icon for desktop and menu. See section under: #### install desktop icon #### in [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_qgis.sh install_qgis.sh].

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

== 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/<project>
# '''/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.
# '''/var/www/html'''. This is the directory references. For user specific documentation, a symbolic link from this directory/<project> can point to /usr/local/share/<project>

* ''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]]

== Notebooks ==

Starting with OSGeo-Live 9.0 a set of digital notebooks to explore several open source solution for geospatial data analysis, with the aim of bridging together the several software libraries already installed on the OSGeo-live to perform complex geo-data-science workflows. The notebooks are developed in the Jupyter notebook server environments which is heavily based on the IPython project, are written id different languages (bash, python, R) and are organized in a series of "topic-oriented" geospatial notebooks.

=== Notebook-Guidelines ===

The intended use of the notebooks on the OSGeo-live is to include rich descriptive narrative to a data processing workflow, including the possibilities to interact with data through a nicely done interactive widget system and finally enabling the printing of publication-ready reports (see latex inline rendering and pdf export).

On the OSGeo-live, we are aiming to use the same [[Live_GIS_Add_Project#Example_Datasets|Example_Datasets]] among projects this way different software projects can be more easily compared, say for their usage complexity or for output quality/performance comparison.

Notebooks shipped within the OSGeo-live must:

* be the result of original work specifically designed to run on the OSGeo-live
* describe a workflow related to geospatial data analysis where code and software documentation are merged together by a rich descriptive narrative.
* use dataset already present on the OSGeo-live dis (Notebooks developer are free to generate novel data i.e.: from querying available database or using using numerical tools to generate synthetic dataset)
* avoid the use of network resources to allow offline use (alert the user otherwise)
* when applicable use hyperlinks to the official project documentation (i.e.: if use a GRASS GIS command, the notebook developer is invited to ad add reference to the official documentation available on the OSGeo-Live)

[[Category: Live-demo]]

Live GIS Add Project

2016-03-15T09:01:57Z

Wiki-Epifanio: /* Notebook-Guidelines */

== 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 Lubuntu.

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

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

Ideally, your application will already be packaged as a .deb file, probably in UbuntuGIS. Then the main part of the script uses apt-get, such as
[https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_mapserver.sh install_mapserver.sh], which is primarily
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

The script should create an icon for desktop and menu. See section under: #### install desktop icon #### in [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_qgis.sh install_qgis.sh].

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

== 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/<project>
# '''/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.
# '''/var/www/html'''. This is the directory references. For user specific documentation, a symbolic link from this directory/<project> can point to /usr/local/share/<project>

* ''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>

== Notebooks ==

Starting with OSGeo-Live 9.0 a set of digital notebooks to explore several open source solution for geospatial data analysis, with the aim of bridging together the several software libraries already installed on the OSGeo-live to perform complex geo-data-science workflows. The notebooks are developed in the Jupyter notebook server environments which is heavily based on the IPython project, are written id different languages (bash, python, R) and are organized in a series of "topic-oriented" geospatial notebooks.

=== Notebook-Guidelines ===

The intended use of the notebooks on the OSGeo-live is to include rich descriptive narrative to a data processing workflow, including the possibilities to interact with data through a nicely done interactive widget system and finally enabling the printing of publication-ready reports (see latex inline rendering and pdf export).

On the OSGeo-live, we are aiming to use the same [[Live_GIS_Add_Project#Example_Datasets|Example_Datasets]] among projects this way different software projects can be more easily compared, say for their usage complexity or for output quality/performance comparison.

Notebooks shipped within the OSGeo-live must:

* be the result of original work specifically designed to run on the OSGeo-live
* describe a workflow related to geospatial data analysis where code and software documentation are merged together by a rich descriptive narrative.
* use dataset already present on the OSGeo-live dis (Notebooks developer are free to generate novel data i.e.: from querying available database or using using numerical tools to generate synthetic dataset)
* avoid the use of network resources to allow offline use (alert the user otherwise)
* when applicable use hyperlinks to the official project documentation (i.e.: if use a GRASS GIS command, the notebook developer is invited to ad add reference to the official documentation available on the OSGeo-Live)

== 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

2016-03-15T08:59:18Z

Wiki-Epifanio: /* Notebook-Guidelines */

== 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 Lubuntu.

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

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

Ideally, your application will already be packaged as a .deb file, probably in UbuntuGIS. Then the main part of the script uses apt-get, such as
[https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_mapserver.sh install_mapserver.sh], which is primarily
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

The script should create an icon for desktop and menu. See section under: #### install desktop icon #### in [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_qgis.sh install_qgis.sh].

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

== 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/<project>
# '''/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.
# '''/var/www/html'''. This is the directory references. For user specific documentation, a symbolic link from this directory/<project> can point to /usr/local/share/<project>

* ''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>

== Notebooks ==

Starting with OSGeo-Live 9.0 a set of digital notebooks to explore several open source solution for geospatial data analysis, with the aim of bridging together the several software libraries already installed on the OSGeo-live to perform complex geo-data-science workflows. The notebooks are developed in the Jupyter notebook server environments which is heavily based on the IPython project, are written id different languages (bash, python, R) and are organized in a series of "topic-oriented" geospatial notebooks.

=== Notebook-Guidelines ===

The intended use of the notebooks on the OSGeo-live is to include rich descriptive narrative to a data processing workflow, including the possibilities to interact with data through a nicely done interactive widget system and finally enabling the printing of publication-ready reports (see latex inline rendering and pdf export).

On the OSGeo-live, we are aiming to use the same `common dataset` among projects this way different software projects can be more easily compared, say for their usage complexity or for output quality/performance comparison.

Notebooks shipped within the OSGeo-live must:

* be the result of original work specifically designed to run on the OSGeo-live
* describe a workflow related to geospatial data analysis where code and software documentation are merged together by a rich descriptive narrative.
* use dataset already present on the OSGeo-live dis (Notebooks developer are free to generate novel data i.e.: from querying available database or using using numerical tools to generate synthetic dataset)
* avoid the use of network resources to allow offline use (alert the user otherwise)
* when applicable use hyperlinks to the official project documentation (i.e.: if use a GRASS GIS command, the notebook developer is invited to ad add reference to the official documentation available on the OSGeo-Live)

== 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

2016-03-15T08:58:03Z

Wiki-Epifanio: /* Notebooks */

== 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 Lubuntu.

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

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

Ideally, your application will already be packaged as a .deb file, probably in UbuntuGIS. Then the main part of the script uses apt-get, such as
[https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_mapserver.sh install_mapserver.sh], which is primarily
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

The script should create an icon for desktop and menu. See section under: #### install desktop icon #### in [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_qgis.sh install_qgis.sh].

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

== 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/<project>
# '''/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.
# '''/var/www/html'''. This is the directory references. For user specific documentation, a symbolic link from this directory/<project> can point to /usr/local/share/<project>

* ''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>

== Notebooks ==

Starting with OSGeo-Live 9.0 a set of digital notebooks to explore several open source solution for geospatial data analysis, with the aim of bridging together the several software libraries already installed on the OSGeo-live to perform complex geo-data-science workflows. The notebooks are developed in the Jupyter notebook server environments which is heavily based on the IPython project, are written id different languages (bash, python, R) and are organized in a series of "topic-oriented" geospatial notebooks.

== Notebook-Guidelines ==

The intended use of the notebooks on the OSGeo-live is to include rich descriptive narrative to a data processing workflow, including the possibilities to interact with data through a nicely done interactive widget system and finally enabling the printing of publication-ready reports (see latex inline rendering and pdf export).

On the OSGeo-live, we are aiming to use the same `common dataset` among projects this way different software projects can be more easily compared, say for their usage complexity or for output quality/performance comparison.

Notebooks shipped within the OSGeo-live must:

* be the result of original work specifically designed to run on the OSGeo-live
* describe a workflow related to geospatial data analysis where code and software documentation are merged together by a rich descriptive narrative.
* use dataset already present on the OSGeo-live dis (Notebooks developer are free to generate novel data i.e.: from querying available database or using using numerical tools to generate synthetic dataset)
* avoid the use of network resources to allow offline use (alert the user otherwise)
* when applicable use hyperlinks to the official project documentation (i.e.: if use a GRASS GIS command, the notebook developer is invited to ad add reference to the official documentation available on the OSGeo-Live)

== 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 Disc

2016-03-15T08:32:21Z

Wiki-Epifanio: /* Documentation */

= 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

== Want to help? ==
We love volunteers, and would love to hear from you if you would like to help out. Best place to start is to introduce yourself on our [https://wiki.osgeo.org/wiki/Live_GIS_Disc#Contact_Us email list], maybe mention how you'd like to get involved. Here are some ideas about things that you might want to help with:
; Translations: Know another language? Why not join our team of translators:
: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Translate

; Testing:
; Quickstarts:
; Debian Packaging:

== 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

== Notebooks ==
[[Live_GIS_Add_Project#Notebooks]]

[http://nbviewer.jupyter.org/github/OSGeo/OSGeoLive-Notebooks/blob/master/index.ipynb In development Notebooks]

== 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 December 2015, 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=19&min=0&sec=0&p1=179&p2=189&p3=224&p4=22&p5=240&p6=196&p7=215
* [[Live_GIS_Disc_Meeting_Minutes|Meeting Minutes]]
* Twitter [https://twitter.com/osgeolive @osgeolive]

== 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.

== Git migration ==

; Repositories (to be moved to OSGeo infrastructure soon): https://github.com/OSGeo/OSGeoLive and https://github.com/OSGeo/OSGeoLive-doc
* Since Git is a distributed versioning system, it is very convenient for each developer/contributor to have a personal public copy of the "official" repository (also known as fork).

* Web hosting services like GitLab or GitHub provide this option if you visit the main code repository and press the button "Fork". This way the developer can make changes to a personal isolated repository. Then one can ask the rest of the developers to review the code and merge accordingly through a "pull request".

* After forking the official repositories, your working repositories are: https://github.com/your_id/OSGeoLive and https://github.com/your_id/OSGeoLive-doc

* On Linux systems get the source code locally using:
git clone https://github.com/your_id/OSGeoLive

* In order to be able to get and send changes to your public repository, you need to link your local copy to your public copy. This is done automatically for you when you "git clone". The repository that you cloned from has the alias "origin".

* In order to be able to get changes that others do to the main repository, you need to manually link to that using:
git remote add upstream https://github.com/OSGeo/OSGeoLive

* On MS Windows systems, install [https://code.google.com/p/tortoisegit/ TortoiseGit], which extends Windows Explorer to include git commands.

* The first thing you should do when you install Git is to set your user name and e-mail address.
git config --global user.name "John Doe"
git config --global user.email johndoe@example.com

; Commit access
:On the git world, you don't need commit access to the main repository in order to contribute. You just work on your own fork and ask maintainers to merge your code through "pull requests". Before you contribute to the project for the first time, you will 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. 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''

;Add your name to contributors list
:The first thing you should do to test your git setup is to add your name to the [https://github.com/OSGeo/OSGeoLive-doc/blob/master/contributors.csv code contributors] or [https://github.com/OSGeo/OSGeoLive-doc/blob/master/translators.csv translators] list(s):

cd OSGeoLive-doc

# Pull any updates from upstream project (master is the equivalent of subversion trunk)
git pull upstream master

# 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.
git diff contributors.csv

# add the changes into stage area
git add contributors.csv

# commit changes locally
git commit -m "Added [my name] to contributors"

# send the changes to your public repository
git push origin master

At this point you can let others know that you have some changes that you want to merge, so you can use the button "Pull Request" on GitLab or GitHub. Or you can continue until you feel ready to share your code :)

# 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
git add <file>
git commit -m "commit message"
git push origin master

# 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 ***
git mv <old filename> <new filename>
git commit -m "commit message"
git push origin master

Last step: pull request

In order to merge your work with the main repository, you have to make a pull request.

You can do it by logging on your github account and go to the branch you changed. Click on the New pull request green button. The changes you made previously while appear.

You can review and comment your request before submitting. To submit, click on the Create pull request green button. Then, you're done ! Good job !

More information about Github pull request here: https://help.github.com/articles/using-pull-requests/

<strike>
== 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.
</strike>

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

==Code of Conduct==
Within the OSGeo-Live community we act respectfully toward others in line with the [http://www.osgeo.org/code_of_conduct OSGeo Code of Conduct].

== 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 July 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
* 8 August 2014, [[Live GIS Disc Press Release 53]] - Final OSGeo-Live 8.0 testing sprint
* 25 August 2014, [[Live GIS Disc Press Release 54]] - '''OSGeo-Live 8.0 released'''
* 10 November 2014, [[Live GIS Disc Press Release 55]] - Starting build cycle for OSGeo-Live 8.5
* 1 February 2015, [[Live GIS Disc Press Release 56]] - One week to translate OSGeo-Live 8.5 Documentation
* 2 February 2015, [[Live GIS Disc Press Release 57]] - Final OSGeo-Live 8.5 testing sprint
* 22 February 2015, [[Live GIS Disc Press Release 58]] - '''OSGeo-Live 8.5 released'''
* 19 May 2015, [[Live GIS Disc Press Release 59]] - Starting build cycle for OSGeo-Live 9.0
* 27 August 2015, [[Live GIS Disc Press Release 60]] - Final OSGeo-Live 9.0 testing sprint
* 10 September 2015, [[Live GIS Disc Press Release 61]] - '''OSGeo-Live 9.0 released'''
* 23 November 2015, [[Live GIS Disc Press Release 62]] - Starting build cycle for OSGeo-Live 9.5
* 01 February 2016, [[Live GIS Disc Press Release 63]] - OSGeo-Live metrics going public in next release
* 03 February 2016, [[Live GIS Disc Press Release 64]] - Projects being considered to be retired from OSGeo-Live
* 07 March 2016, [[Live GIS Disc Press Release 65]] - OSGeo-Live 9.5 - Call for testers and translators

=== Twitter ===
We also announce press releases on twitter.

* Major Builds
* Calls for Testing
* Calls for Translation
* Retweets of events featuring OSGeo-Live

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

== Testimonials ==
[[Live GIS Testimonials]]

== 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]]
* [[Live GIS GSoC 2015]]
* [https://github.com/hotosm/HOT-Project-Ideas/issues/15 Cross project OSGeo-Live and HOT in GSoC 2015]

== OSGeo Incubation ==

* [[ Live GIS Incubation Graduation Checklist ]]

= 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)
* [http://imincik.github.io/gis-lab/ GIS.lab] - Automatic deployment of GIS infrastructure

= 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 Add Project

2016-03-15T08:31:51Z

Wiki-Epifanio: /* Documentation */

== 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 Lubuntu.

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

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

Ideally, your application will already be packaged as a .deb file, probably in UbuntuGIS. Then the main part of the script uses apt-get, such as
[https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_mapserver.sh install_mapserver.sh], which is primarily
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

The script should create an icon for desktop and menu. See section under: #### install desktop icon #### in [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_qgis.sh install_qgis.sh].

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

== 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/<project>
# '''/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.
# '''/var/www/html'''. This is the directory references. For user specific documentation, a symbolic link from this directory/<project> can point to /usr/local/share/<project>

* ''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>

== Notebooks ==

== 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 GSoC 2016

2016-02-20T16:20:40Z

Wiki-Epifanio: /* OSGeo-Live Dashboard */

= OSGeo-Live Google Summer of Code ideas 2015 =

OSGeo-Live is a self-contained bootable DVD, USB thumb drive or Virtual Machine based on Lubuntu, that allows you to try a wide variety of open source geospatial software without installing anything. It is composed entirely of free software, allowing it to be freely distributed, duplicated and passed around. It provides pre-configured applications for a range of geospatial use cases, including storage, publishing, viewing, analysis and manipulation of data. It also contains sample datasets and documentation.
=Integration of geospatial OSS in educational notebooks=

==OSGeo-Live Dashboard==

This GSoC 2016 Idea will focus on the development of interactive web application (dashboards) where the user will learn how to build interactive web-based widgets to execute common task in geospatial data processing. The series of "interactive dashboards" will make use of the data already available on the OSGeo-Live as well as web-based resources, making wide use of the OGC standard protocol to access the dataset. The working environment will be based on the jupyter-notebook which enable fast prototyping of both analytical methods as well as GUI components.
Such dashboard will teach how to “bind” together, code and GUI using basic example workflow. It can be considered a cross-project idea where geospatial tools (installed on OSGeo-Live) and data (already on OSGeo-Live) are used to build interactive web-application to visualize and interact with the data-source and with data-products. The results will be a set of reusable-code to build interactive web applications.

== Student ==
*

== Willing to Mentor ==
* Massimo Di Stefano (@epifanio GitHub id)
* Cameron Shorter (@camerons GitHub id)

[[Category: Live-demo]]

Google Summer of Code 2015 Results

2015-12-15T13:35:40Z

Wiki-Epifanio:

<center>
[[Image:GoogleSummer_2015logo.jpg|200px|link=http://code.google.com/soc/]] @ [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]
</center>

OSGeo participated in Google Summer of Code 2015 with 13 projects, all successful:

* GDAL - Faza Mahamood: [https://github.com/fazam/gdal/tree/gdalinfo Integration of GDAL utilities into GDAL core library]

* GRASS GIS - Matej Krejci: [https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata Improved Metadata for GRASS GIS]

* gvSIG - Eva Rodríguez: [https://redmine.gvsig.net/redmine/projects/gvsig-networkanalysis/wiki Port Network Analysis Extension to gvSIG 2.x branch]

* istSOS - Luca Ambrosini: [http://sourceforge.net/p/istsos/wiki/GSoC_2015_scalability/ Scalability for Big data processing for istSOS]

* JGRASSTOOLS - Silvia Franceschi: [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-2015 Development of a simple 1D hydraulic model for JGRASSTOOLS]

* MapServer - Samuel Lapointe: [https://github.com/mapgears/scribeui/wiki/Google-Summer-of-Code-2015 Add productivity tools to MapServer's ScribeUI]

* Opticks - Tom Van den Eynde: [http://drizzle-for-opticks-gsoc2015.blogspot.be/ Image Enhancement/Background Suppression for Opticks]

* OTP - Nipuna Gunathilake: [https://github.com/CUTR-at-USF/gtfs-realtime-validator/wiki GTFS-Realtime validation tool for Open Trip Planner]

* OSGeo-Live - Massimo Di Stefano: [https://github.com/epifanio/OSGeoNotebooks Integration of geospatial OSS in educational notebooks]

* OSSIM - Martina Di Rita: [https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery OSSIM tool for DSM generation using tri-stereo and SAR imagery]

* pgRouting - Sarthak Agarwal: [https://github.com/pgRouting/pgrouting/wiki/GSoC-2015-Sarthak-Agarwal New osm2pgrouting import tool to import OpenStreetMap (OSM) data in pgRouting]

* PyWPS - Calin Ciociu: [https://github.com/jachym/pywps-4/wiki/GSoC-2015 REST interface for PyWPS 4]

* QGIS - Marcus Santos: [https://qgisgsoc2015.wordpress.com/ QGIS - Multithread support on QGIS Processing toolbox]

== Description of the projects ==

=== Example: software XYZ - title of my GSoC project ===
Student1 (picture)
* Mentors: Mentor1; Mentor2; OtherMentors?
* Brief description of the idea. e.g. "[[link|My project]] focused on xxx".
* The state of the project as it was BEFORE your GSoC. For example, if you made a GUI, you can say: "In the software XYZ, when I wanted to use the tool xxx, I had to manually edit the file yyy. "
* The addition that your project brought to the software. In the same example: "With the GUI that I created, now it is possible to use the tool xxx via graphical user interface".
* Add all the links (hopefully permanent) to access the relevant code and documentation for the user to get started with testing your application. "Please test my [[code-repository|code]] following instructions [[some-link|here]]".
* [[Link_to_image|Slide]] The slide / image should serve to show the main elements of your project. It could be a flow chart, a screenshot, both, or whatever you think could serve for the scope. Remember: the aim is to showcase your project to people that are not necessarily familiar with the software.

=== GDAL - Integration of GDAL utilities into GDAL core library ===
Faza Mahamood ([https://drive.google.com/file/d/0B9gY4JeBmoKVZ2REcjcwVnl1Nk0/view?usp=sharing Picture])
* Mentor: Even Rouault
* There is a need for calling GDAL utilities from code without involving system calls, to be able to work on in-memory datasets and use progress/cancellation callback functions.
* Before, inorder to use any functionalities of GDAL utilities in a program, the developer had to use system calls. Even then, the developer cannot work with in memory datasets.
* Now, the developers can easily have all the functionalities of GDAL utilities through dedicated functions which are part of GDAL core library. There is no system call involved and it works on in-memory datasets.
* Project: https://trac.osgeo.org/gdal/wiki/rfc59.1_utilities_as_a_library

=== GRASS GIS - Improved Metadata for GRASS GIS ===
Matej Krejci ([http://tinyurl.com/pp69bwd Picture])
* Mentors: Martin Landa, Angelos Tzotsos, Luca Delucchi
* Description: The first aim was to improve current package by adding a new functionality for extend metadata handling. The second goal was to implement module for interaction with metadata catalogue services (CSW).
* State of the project before GSoC: In 2014 during GSoC I have developed new GRASS GIS metadata management support based on ISO-INSPIRE. This package needed extension to meet the users requirements. In addition package for CSW searching was missing.
* Addition to the project: New module g.gui.cswbrowser based on graphical interface allows managing csw connections, setting filter and searching, browsing results and adding services to GRASS GIS have been implemented. For g.gui.metadata have been added support: exporting metadata reports to pdf, storing themes of metadata in SQL backend, publishing metadata to CSW and metadata support for Temporal datasets.
* Slide: https://grasswiki.osgeo.org/w/images/Find1.png

Links:
* Project: https://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support
* Development page 2015: https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata
* source SVN: http://svn.osgeo.org/grass/grass-addons/grass7/gui/wxpython/wx.metadata/

=== gvSIG - Port Network Analysis Extension to gvSIG 2.x branch ===

=== istSOS - Scalability for Big data processing for istSOS ===

Ambrosini Luca ([https://www.dropbox.com/sc/z3twbb6zicslvy2/AAC43ZE3JYy_JCAiLEGoOstIa Picture])

* Mentors: Massimiliano Cannata, Milan Antonovic

* Brief description of the idea : istSOS is essentially a data collector, it wasn't ready for BigData, the idea was to implement data replication to improve security, online time and performance.

* The state of the project before GSOS : All data were hosted on a single postgres db, and there wasn't a tool that helps finding this implementation limits.

* The addition that your project brought to the software : We adapted the source code to work with replications, we set up a middleware that balances query among multiple database server, and we realized a benchmarking tool to test system response time and its scaling .

* Gsoc Reports : https://sourceforge.net/p/istsos/wiki/GSoC_2015_scalability/

* Slide http://i.imgur.com/EACzyxf.png

=== JGrassTools - Development of a simplified 1D hydraulics model ===
Silvia Franceschi ([https://sites.google.com/a/hydrologis.com/home/_/rsrc/1348641375730/silviafranceschi/silli.jpg?height=320&width=234 Picture])
* Mentors: Andrea Antonello, Riccardo Rigon
* Description: The module developed during this GSoC2015 is SaintGeo, a simple 1D hydraulic model based on the equations of Saint Venant.
* State of the project before GSoC: There was an original implementation of the model in C language done during a master thesis by Angelo Zacchia and Riccardo Rigon. I did the porting in the JGrassTools library of the model together with the implementation of the code for reading and writing GIS layers as input and outputs.
* Addition to the project: The new model bases on GIS input layers instead of text files and has a graphical interface, directly provided by the integration in the JGrassTools library to specify the inputs and outputs files.
* Slide: https://github.com/moovida/jgrasstools/wiki/gsoqc2015imgs/a_profile_qin_monte_laterali_in_out10.png

Links:
* Project: http://www.jgrasstools.org
* Development page 2015: https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-2015
* Source: https://github.com/moovida/jgrasstools/tree/master/hortonmachine/src/main/java/org/jgrasstools/hortonmachine/modules/hydrogeomorphology/saintgeo

=== Mapserver - Add productivity tools to MapServer's ScribeUI ===
Samuel Lapointe ([https://goo.gl/photos/LbSwPeMrCG5V2K9t8 Picture])
* Mentors: Daniel Morissette; Jessica Lapointe
* Description: The goal of the project was to improve the error detection system, add the ability to export and import maps and add a way to generate a set of classes from data.
* State of the project before GSoC: When I wanted to debug a map that didn’t work, I had to check the generated Mapserver file to find the error. To create classes from a set of data, I had to analyse the data and create the classes using bounds I had manually calculated, and the only way to export a map was to use Git.
* Addition to the project: Now, I can see most syntax errors directly in the editor’s interface, I can use a menu to generate classes for a layer and I can export or import maps to share them with other users.
* Slide: https://drive.google.com/file/d/0B686XfUqwP1LMm5GaVV0ckZ1b2c/view?usp=sharing

Links:
* Project page: https://github.com/mapgears/scribeui
* Getting started: https://github.com/mapgears/scribeui/wiki/Getting-started-with-ScribeUI
* Demo: http://demo.scribeui.org/

=== Opticks – Image Enhancement/Background Suppression ===
Tom Van den Eynde ([https://goo.gl/photos/DKwS7Fq4ZWEmHfR46 Picture])
* Mentors: Trevor Clarke
* Brief description of the idea: The goal of the project was to implement the image enhancement algorithm Drizzle for both image and video input.
* The state of the project as it was before GSoC: In Opticks, when I wanted to use a low resolution image I had to resort to other software to first improve the quality or reduce the noise interference.
* The addition to the software: With the addition of the Drizzle algorithm, Opticks can enhance and improve the interpretability of images. Now, even low resolution or heavily noise polluted images can be used for various remote sensing applications.
* Slide: https://goo.gl/photos/szt3RW3X93v2ccZi9

Links:
* Project: https://www.google-melange.com/gsoc/project/details/google/gsoc2015/tomvde/5733935958982656
* Blog: http://drizzle-for-opticks-gsoc2015.blogspot.be/
* Repository: https://github.com/Tom-VdE/Drizzle-plugin
* Instructions: https://github.com/Tom-VdE/Drizzle-plugin/blob/master/README.md

=== OTP - GTFS-Realtime validation tool for Open Trip Planner ===

=== Osgeo-Live - Integration of geospatial OSS in educational notebooks ===
Massimo Di Stefano ([http://tw.rpi.edu/media/latest/Massimo_Di_Stefano.jpg Picture])
* '''Mentors: Cameron Shorter, Rich Signell, Angelos Tzotsos'''
* '''Brief description of the idea:'''This GSoC 2015 Idea will focus on the development of a cross-projects python library with the aim of bridging together the several software libraries already installed on the live through the use of the Jupyter notebook server in a series of "topic-oriented" geospatial notebooks.
* '''The state of the project as it was BEFORE this GSoC:''' before this GSoC there was no jupyter-notebook installed and very limited set of example based on the IPython-notebook.
* '''Addition to the software:''' After GSOC 2015 an installer for the jupyter-notebook has ben developed (enabling multiple kernels [py2, py3, R, Bash, Julia]) and a series of geospatial notebooks to show the usage of several project like GDAL, OSSIM, GRASS has been added. The project also included the building on Debian packages for the jupyter single user ecosystem and the collaborative development of widget for interactive visualization of geospatial data from a notebook ([https://github.com/epifanio/CesiumWidget CesiumWidget])
'''Relevant links:'''
* GSoC Proposal: https://wiki.osgeo.org/wiki/Live_GIS_GSoC_2015
* Weekly reports: https://github.com/epifanio/IPython_notebooks/tree/master/OSGeo-live/osgeolive-gsoc-2015/Report
* Repository: https://github.com/epifanio/OSGeoNotebooks
* Demo [http://mybinder.org/repo/epifanio/CesiumWidget CesiumWidget], [http://epinux.com/cesium-720p.mp4 video]
* [[Link_to_image|Slide]]

=== OSSIM - Tool for DSM generation using tri-stereo optical imagery ===
Martina Di Rita (You can find a [https://www.dropbox.com/s/59dfmpz8kwapmsf/2015-12-03%2015.54.15.jpg?dl=0 picture of me])
* '''Mentors:''' Oscar Kramer, David Burken
* '''Brief description of the idea:''' the work has been based on a previous GSoC project through which a tool, named DATE, for Digital Surface Model (DSM) generation from optical stereo-pair was developed within OSSIM framework. The idea was to improve and update DATE in order to generate DSMs from tri-stereo optical imagery and fix some bugs in the DSMs generation processing chain. DATE key features include the use of computer vision algorithms in order to improve the processing efficiency and make the DSMs generation process fully automatic.
* '''The state of the project as it was BEFORE this GSoC:''' before this GSoC it was not possible to process tri-stereo imagery and there was still some problem in finding the right quasi-epipolar geometry in the stereo version in order to compute a proper Disparity Map.
* '''Addition to the software:''' with DATE plug-in it is now possible to generate DSMs within OSSIM framework starting from stereo and tri-stereo satellite optical imagery. Furthermore, from the stereo processing side, I added an image preprocess filtering and I found a better solution for the quasi-epipolar geometry achievement.
'''Relevant links:'''
* GSoC Proposal: https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015/martidi/5717271485874176
* Weekly reports: https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery
* Please test my code in https://github.com/martidi/opencv_dsm/tree/master following the instructions in README.md file

* [[Link_to_image|Slide]] The slide / image should serve to show the main elements of your project. It could be a flow chart, a screenshot, both, or whatever you think could serve for the scope. Remember: the aim is to showcase your project to people that are not necessarily familiar with the software.

=== pgRouting - New osm2pgrouting import tool to import OpenStreetMap (OSM) data in pgRouting ===
Sarthak Agarwal
* Mentors: Daniel Kastl, Vicky Vergara
* Brief description of the idea: The idea for this year GSOC project was to update the existing osm2pgRouting tool which helps users to import open source osm data into pgRouting database tables.
* The state of the project as it was BEFORE this GSoC: Before the gsoc project the tool lack support for boost library and the code was to be refactored and commented. The code was not documented and the tool on a whole needed documentation(WIKI pages)
* Addition to the software: After GSOC 2015 support for boost library such as boost.program_options and boost.geometry has been added to the software. Now user can give options in any order while running the software and boost will do the parsing. The code was not commented and refactored, which was updated. Several wiki pages are added to better understand the tags used for routing present in osm data and all the attributes related to those tags. The link to the wiki page can be found below.

Links:
* [https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015/sarthak0415/5629499534213120 GSoC Proposal]
* [https://github.com/pgRouting/pgrouting/wiki/GSoC-2015-Sarthak-Agarwal Weekly reports]
* [https://github.com/sarthak-0415/pgrouting/tree/sarthak-0415 Repository]

=== PyWPS-4 – REST Interface ===
Calin Cristian Nicolae Ciociu ([http://i.imgur.com/WglCPnz.jpg Picture])
* Mentors: Jachym Cepicky, Luís de Sousa
* Brief description of the idea: My project added the ability to use a REST interface to control, add, remove processes and change configuration of PyWPS-4 instances.
* The state of the project as it was before GSoC: We had to create/delete the processes by accessing the storage of the server which required a restart of the server every time something got changed.
* The addition to the software: With the addition of the REST interface I wrote everyone who needs to update, delete, or add new processes and change configuration can do so without accessing the server.
* Slide: http://i.imgur.com/oYAHsgQ.png

Links:
* Project: http://www.google-melange.com/gsoc/project/details/google/gsoc2015/noctalin/5717271485874176
* Repository: https://github.com/jachym/pywps-4
* Instructions: https://github.com/PyWPS/pywps-4-demo/blob/master/README.rst

=== QGIS - Multithread Support on Processing Toolboxt ===
Marcus Santos ([https://media.licdn.com/media/AAEAAQAAAAAAAATOAAAAJDA1Y2M0MWQ0LTMyYjMtNDlhMi05OWM3LWIxMDQ5YWM1ZTk2MA.jpg Picture])
* Mentors: Victor Olaya, Alexander Bruy
* Description: This project consisted on making the QGIS Processing toolbox multi-threaded, allowing to have non blocking analysis/geoprocessing jobs, prevent crashes (when a QGIS module crashes for some reason) and also improve the user experience.
* The state of the project GSoC: Before the multithreading support, the user was only able to run one analysis at a time and there was no option to cancel the algorithm execution.
* The addition to the project: With multithreading support the user is allowed to cancel long geoprocessing jobs and also run several algorithms at the same time.
* Slide: https://www.dropbox.com/s/fmaxf97jkmf2cy1/slide.png?dl=0

Links:
* Project page: https://qgisgsoc2015.wordpress.com
* Repository: https://github.com/mvcsantos/QGIS
* Demo: https://www.youtube.com/watch?v=V-CJCnKw89U

[[Category:Google Summer of Code]]

Google Summer of Code 2015 Results

2015-12-05T21:09:38Z

Wiki-Epifanio:

<center>
[[Image:GoogleSummer_2015logo.jpg|200px|link=http://code.google.com/soc/]] @ [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]
</center>

OSGeo participated in Google Summer of Code 2015 with 13 projects, all successful:

* GDAL - Faza Mahamood: [https://github.com/fazam/gdal/tree/gdalinfo Integration of GDAL utilities into GDAL core library]

* GRASS GIS - Matej Krejci: [https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata Improved Metadata for GRASS GIS]

* gvSIG - Eva Rodríguez: [https://redmine.gvsig.net/redmine/projects/gvsig-networkanalysis/wiki Port Network Analysis Extension to gvSIG 2.x branch]

* istSOS - Luca Ambrosini: [http://sourceforge.net/p/istsos/wiki/GSoC_2015_scalability/ Scalability for Big data processing for istSOS]

* JGRASSTOOLS - Silvia Franceschi: [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-2015 Development of a simple 1D hydraulic model for JGRASSTOOLS]

* MapServer - Samuel Lapointe: [https://github.com/mapgears/scribeui/wiki/Google-Summer-of-Code-2015 Add productivity tools to MapServer's ScribeUI]

* Opticks - Tom Van den Eynde: [http://drizzle-for-opticks-gsoc2015.blogspot.be/ Image Enhancement/Background Suppression for Opticks]

* OTP - Nipuna Gunathilake: [https://github.com/CUTR-at-USF/gtfs-realtime-validator/wiki GTFS-Realtime validation tool for Open Trip Planner]

* OSGeo-Live - Massimo Di Stefano: [https://github.com/epifanio/GSOC2015 Integration of geospatial OSS in educational notebooks]

* OSSIM - Martina Di Rita: [https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery OSSIM tool for DSM generation using tri-stereo and SAR imagery]

* pgRouting - Sarthak Agarwal: [https://github.com/pgRouting/pgrouting/wiki/GSoC-2015-Sarthak-Agarwal New osm2pgrouting import tool to import OpenStreetMap (OSM) data in pgRouting]

* PyWPS - Calin Ciociu: [https://github.com/jachym/pywps-4/wiki/GSoC-2015 REST interface for PyWPS 4]

* QGIS - Marcus Santos: [https://qgisgsoc2015.wordpress.com/ QGIS - Multithread support on QGIS Processing toolbox]

== Description of the projects ==

=== Example: software XYZ - title of my GSoC project ===
Student1 (picture)
* Mentors: Mentor1; Mentor2; OtherMentors?
* Brief description of the idea. e.g. "[[link|My project]] focused on xxx".
* The state of the project as it was BEFORE your GSoC. For example, if you made a GUI, you can say: "In the software XYZ, when I wanted to use the tool xxx, I had to manually edit the file yyy. "
* The addition that your project brought to the software. In the same example: "With the GUI that I created, now it is possible to use the tool xxx via graphical user interface".
* Add all the links (hopefully permanent) to access the relevant code and documentation for the user to get started with testing your application. "Please test my [[code-repository|code]] following instructions [[some-link|here]]".
* [[Link_to_image|Slide]] The slide / image should serve to show the main elements of your project. It could be a flow chart, a screenshot, both, or whatever you think could serve for the scope. Remember: the aim is to showcase your project to people that are not necessarily familiar with the software.

=== GDAL - Integration of GDAL utilities into GDAL core library ===
Faza Mahamood ([https://drive.google.com/file/d/0B9gY4JeBmoKVZ2REcjcwVnl1Nk0/view?usp=sharing Picture])
* Mentor: Even Rouault
* There is a need for calling GDAL utilities from code without involving system calls, to be able to work on in-memory datasets and use progress/cancellation callback functions.
* Before, inorder to use any functionalities of GDAL utilities in a program, the developer had to use system calls. Even then, the developer cannot work with in memory datasets.
* Now, the developers can easily have all the functionalities of GDAL utilities through dedicated functions which are part of GDAL core library. There is no system call involved and it works on in-memory datasets.
* Project: https://trac.osgeo.org/gdal/wiki/rfc59.1_utilities_as_a_library

=== GRASS GIS - Improved Metadata for GRASS GIS ===
Matej Krejci ([http://tinyurl.com/pp69bwd Picture])
* Mentors: Martin Landa, Angelos Tzotsos, Luca Delucchi
* Description: The first aim was to improve current package by adding a new functionality for extend metadata handling. The second goal was to implement module for interaction with metadata catalogue services (CSW).
* State of the project before GSoC: In 2014 during GSoC I have developed new GRASS GIS metadata management support based on ISO-INSPIRE. This package needed extension to meet the users requirements. In addition package for CSW searching was missing.
* Addition to the project: New module g.gui.cswbrowser based on graphical interface allows managing csw connections, setting filter and searching, browsing results and adding services to GRASS GIS have been implemented. For g.gui.metadata have been added support: exporting metadata reports to pdf, storing themes of metadata in SQL backend, publishing metadata to CSW and metadata support for Temporal datasets.
* Slide: https://grasswiki.osgeo.org/w/images/Find1.png

Links:
* Project: https://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support
* Development page 2015: https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata
* source SVN: http://svn.osgeo.org/grass/grass-addons/grass7/gui/wxpython/wx.metadata/

=== gvSIG - Port Network Analysis Extension to gvSIG 2.x branch ===

=== istSOS - Scalability for Big data processing for istSOS ===

Ambrosini Luca ([https://www.dropbox.com/sc/z3twbb6zicslvy2/AAC43ZE3JYy_JCAiLEGoOstIa Picture])

* Mentors: Massimiliano Cannata, Milan Antonovic

* Brief description of the idea : istSOS is essentially a data collector, it wasn't ready for BigData, the idea was to implement data replication to improve security, online time and performance.

* The state of the project before GSOS : All data were hosted on a single postgres db, and there wasn't a tool that helps finding this implementation limits.

* The addition that your project brought to the software : We adapted the source code to work with replications, we set up a middleware that balances query among multiple database server, and we realized a benchmarking tool to test system response time and its scaling .

* Gsoc Reports : https://sourceforge.net/p/istsos/wiki/GSoC_2015_scalability/

* Slide http://i.imgur.com/EACzyxf.png

=== JGrassTools - Development of a simplified 1D hydraulics model ===
Silvia Franceschi ([https://sites.google.com/a/hydrologis.com/home/_/rsrc/1348641375730/silviafranceschi/silli.jpg?height=320&width=234 Picture])
* Mentors: Andrea Antonello, Riccardo Rigon
* Description: The module developed during this GSoC2015 is SaintGeo, a simple 1D hydraulic model based on the equations of Saint Venant.
* State of the project before GSoC: There was an original implementation of the model in C language done during a master thesis by Angelo Zacchia and Riccardo Rigon. I did the porting in the JGrassTools library of the model together with the implementation of the code for reading and writing GIS layers as input and outputs.
* Addition to the project: The new model bases on GIS input layers instead of text files and has a graphical interface, directly provided by the integration in the JGrassTools library to specify the inputs and outputs files.
* Slide: https://github.com/moovida/jgrasstools/wiki/gsoqc2015imgs/a_profile_qin_monte_laterali_in_out10.png

Links:
* Project: http://www.jgrasstools.org
* Development page 2015: https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-2015
* Source: https://github.com/moovida/jgrasstools/tree/master/hortonmachine/src/main/java/org/jgrasstools/hortonmachine/modules/hydrogeomorphology/saintgeo

=== Mapserver - Add productivity tools to MapServer's ScribeUI ===
Samuel Lapointe ([https://goo.gl/photos/LbSwPeMrCG5V2K9t8 Picture])
* Mentors: Daniel Morissette; Jessica Lapointe
* Description: The goal of the project was to improve the error detection system, add the ability to export and import maps and add a way to generate a set of classes from data.
* State of the project before GSoC: When I wanted to debug a map that didn’t work, I had to check the generated Mapserver file to find the error. To create classes from a set of data, I had to analyse the data and create the classes using bounds I had manually calculated, and the only way to export a map was to use Git.
* Addition to the project: Now, I can see most syntax errors directly in the editor’s interface, I can use a menu to generate classes for a layer and I can export or import maps to share them with other users.
* Slide: https://drive.google.com/file/d/0B686XfUqwP1LMm5GaVV0ckZ1b2c/view?usp=sharing

Links:
* Project page: https://github.com/mapgears/scribeui
* Getting started: https://github.com/mapgears/scribeui/wiki/Getting-started-with-ScribeUI
* Demo: http://demo.scribeui.org/

=== Opticks – Image Enhancement/Background Suppression ===
Tom Van den Eynde ([https://goo.gl/photos/DKwS7Fq4ZWEmHfR46 Picture])
* Mentors: Trevor Clarke
* Brief description of the idea: The goal of the project was to implement the image enhancement algorithm Drizzle for both image and video input.
* The state of the project as it was before GSoC: In Opticks, when I wanted to use a low resolution image I had to resort to other software to first improve the quality or reduce the noise interference.
* The addition to the software: With the addition of the Drizzle algorithm, Opticks can enhance and improve the interpretability of images. Now, even low resolution or heavily noise polluted images can be used for various remote sensing applications.
* Slide: https://goo.gl/photos/szt3RW3X93v2ccZi9

Links:
* Project: https://www.google-melange.com/gsoc/project/details/google/gsoc2015/tomvde/5733935958982656
* Blog: http://drizzle-for-opticks-gsoc2015.blogspot.be/
* Repository: https://github.com/Tom-VdE/Drizzle-plugin
* Instructions: https://github.com/Tom-VdE/Drizzle-plugin/blob/master/README.md

=== OTP - GTFS-Realtime validation tool for Open Trip Planner ===

=== Osgeo-Live - Integration of geospatial OSS in educational notebooks ===
Massimo Di Stefano ([http://tw.rpi.edu/media/latest/Massimo_Di_Stefano.jpg Picture])
* '''Mentors: Cameron Shorter, Rich Signell, Angelos Tzotsos'''
* '''Brief description of the idea:'''This GSoC 2015 Idea will focus on the development of a cross-projects python library with the aim of bridging together the several software libraries already installed on the live through the use of the Jupyter notebook server in a series of "topic-oriented" geospatial notebooks.
* '''The state of the project as it was BEFORE this GSoC:''' before this GSoC there was no jupyter-notebook installed and very limited set of example based on the IPython-notebook.
* '''Addition to the software:''' After GSOC 2015 an installer for the jupyter-notebook has ben developed (enabling multiple kernels [py2, py3, R, Bash, Julia]) and a series of geospatial notebooks to show the usage of several project like GDAL, OSSIM, GRASS has been added. The project also included the building on Debian packages for the jupyter single user ecosystem and the collaborative development of widget for interactive visualization of geospatial data from a notebook ([https://github.com/epifanio/CesiumWidget CesiumWidget])
'''Relevant links:'''
* GSoC Proposal: https://wiki.osgeo.org/wiki/Live_GIS_GSoC_2015
* Weekly reports: https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery
* Repository: https://github.com/epifanio/GSOC2015
* Demo [http://mybinder.org/repo/epifanio/CesiumWidget CesiumWidget], [http://epinux.com/cesium-720p.mp4 video]
* [[Link_to_image|Slide]]

=== OSSIM - Tool for DSM generation using tri-stereo optical imagery ===
Martina Di Rita (You can find a [https://www.dropbox.com/s/59dfmpz8kwapmsf/2015-12-03%2015.54.15.jpg?dl=0 picture of me])
* '''Mentors:''' Oscar Kramer, David Burken
* '''Brief description of the idea:''' the work has been based on a previous GSoC project through which a tool, named DATE, for Digital Surface Model (DSM) generation from optical stereo-pair was developed within OSSIM framework. The idea was to improve and update DATE in order to generate DSMs from tri-stereo optical imagery and fix some bugs in the DSMs generation processing chain. DATE key features include the use of computer vision algorithms in order to improve the processing efficiency and make the DSMs generation process fully automatic.
* '''The state of the project as it was BEFORE this GSoC:''' before this GSoC it was not possible to process tri-stereo imagery and there was still some problem in finding the right quasi-epipolar geometry in the stereo version in order to compute a proper Disparity Map.
* '''Addition to the software:''' with DATE plug-in it is now possible to generate DSMs within OSSIM framework starting from stereo and tri-stereo satellite optical imagery. Furthermore, from the stereo processing side, I added an image preprocess filtering and I found a better solution for the quasi-epipolar geometry achievement.
'''Relevant links:'''
* GSoC Proposal: https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015/martidi/5717271485874176
* Weekly reports: https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery
* Please test my code in https://github.com/martidi/opencv_dsm/tree/master following the instructions in README.md file

* [[Link_to_image|Slide]] The slide / image should serve to show the main elements of your project. It could be a flow chart, a screenshot, both, or whatever you think could serve for the scope. Remember: the aim is to showcase your project to people that are not necessarily familiar with the software.

=== pgRouting ===

=== PyWPS-4 – REST Interface ===
Calin Cristian Nicolae Ciociu ([http://i.imgur.com/WglCPnz.jpg Picture])
* Mentors: Jachym Cepicky, Luís de Sousa
* Brief description of the idea: My project added the ability to use a REST interface to control, add, remove processes and change configuration of PyWPS-4 instances.
* The state of the project as it was before GSoC: We had to create/delete the processes by accessing the storage of the server which required a restart of the server every time something got changed.
* The addition to the software: With the addition of the REST interface I wrote everyone who needs to update, delete, or add new processes and change configuration can do so without accessing the server.
* Slide: http://i.imgur.com/oYAHsgQ.png

Links:
* Project: http://www.google-melange.com/gsoc/project/details/google/gsoc2015/noctalin/5717271485874176
* Repository: https://github.com/jachym/pywps-4
* Instructions: https://github.com/PyWPS/pywps-4-demo/blob/master/README.rst

=== QGIS - Multithread Support on Processing Toolboxt ===
Marcus Santos ([https://media.licdn.com/media/AAEAAQAAAAAAAATOAAAAJDA1Y2M0MWQ0LTMyYjMtNDlhMi05OWM3LWIxMDQ5YWM1ZTk2MA.jpg Picture])
* Mentors: Victor Olaya, Alexander Bruy
* Description: This project consisted on making the QGIS Processing toolbox multi-threaded, allowing to have non blocking analysis/geoprocessing jobs, prevent crashes (when a QGIS module crashes for some reason) and also improve the user experience.
* The state of the project GSoC: Before the multithreading support, the user was only able to run one analysis at a time and there was no option to cancel the algorithm execution.
* The addition to the project: With multithreading support the user is allowed to cancel long geoprocessing jobs and also run several algorithms at the same time.
* Slide: https://www.dropbox.com/s/fmaxf97jkmf2cy1/slide.png?dl=0

Links:
* Project page: https://qgisgsoc2015.wordpress.com
* Repository: https://github.com/mvcsantos/QGIS
* Demo: https://www.youtube.com/watch?v=V-CJCnKw89U

[[Category:Google Summer of Code]]

Google Summer of Code 2015 Results

2015-12-04T20:04:05Z

Wiki-Epifanio:

<center>
[[Image:GoogleSummer_2015logo.jpg|200px|link=http://code.google.com/soc/]] @ [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]
</center>

OSGeo participated in Google Summer of Code 2015 with 13 projects, all successful:

* GDAL - Faza Mahamood: [https://github.com/fazam/gdal/tree/gdalinfo Integration of GDAL utilities into GDAL core library]

* GRASS GIS - Matej Krejci: [https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata Improved Metadata for GRASS GIS]

* gvSIG - Eva Rodríguez: [https://redmine.gvsig.net/redmine/projects/gvsig-networkanalysis/wiki Port Network Analysis Extension to gvSIG 2.x branch]

* istSOS - Luca Ambrosini: [http://sourceforge.net/p/istsos/wiki/GSoC_2015_scalability/ Scalability for Big data processing for istSOS]

* JGRASSTOOLS - Silvia Franceschi: [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-2015 Development of a simple 1D hydraulic model for JGRASSTOOLS]

* MapServer - Samuel Lapointe: [https://github.com/mapgears/scribeui/wiki/Google-Summer-of-Code-2015 Add productivity tools to MapServer's ScribeUI]

* Opticks - Tom Van den Eynde: [http://drizzle-for-opticks-gsoc2015.blogspot.be/ Image Enhancement/Background Suppression for Opticks]

* OTP - Nipuna Gunathilake: [https://github.com/CUTR-at-USF/gtfs-realtime-validator/wiki GTFS-Realtime validation tool for Open Trip Planner]

* OSGeo-Live - Massimo Di Stefano: [https://github.com/epifanio/GSOC2015 Integration of geospatial OSS in educational notebooks]

* OSSIM - Martina Di Rita: [https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery OSSIM tool for DSM generation using tri-stereo and SAR imagery]

* pgRouting - Sarthak Agarwal: [https://github.com/pgRouting/pgrouting/wiki/GSoC-2015-Sarthak-Agarwal New osm2pgrouting import tool to import OpenStreetMap (OSM) data in pgRouting]

* PyWPS - Calin Ciociu: [https://github.com/jachym/pywps-4/wiki/GSoC-2015 REST interface for PyWPS 4]

* QGIS - Marcus Santos: [https://qgisgsoc2015.wordpress.com/ QGIS - Multithread support on QGIS Processing toolbox]

== Description of the projects ==

=== Example: software XYZ - title of my GSoC project ===
Student1 (picture)
* Mentors: Mentor1; Mentor2; OtherMentors?
* Brief description of the idea. e.g. "[[link|My project]] focused on xxx".
* The state of the project as it was BEFORE your GSoC. For example, if you made a GUI, you can say: "In the software XYZ, when I wanted to use the tool xxx, I had to manually edit the file yyy. "
* The addition that your project brought to the software. In the same example: "With the GUI that I created, now it is possible to use the tool xxx via graphical user interface".
* Add all the links (hopefully permanent) to access the relevant code and documentation for the user to get started with testing your application. "Please test my [[code-repository|code]] following instructions [[some-link|here]]".
* [[Link_to_image|Slide]] The slide / image should serve to show the main elements of your project. It could be a flow chart, a screenshot, both, or whatever you think could serve for the scope. Remember: the aim is to showcase your project to people that are not necessarily familiar with the software.

=== GDAL - Integration of GDAL utilities into GDAL core library ===
Faza Mahamood ([https://drive.google.com/file/d/0B9gY4JeBmoKVZ2REcjcwVnl1Nk0/view?usp=sharing Picture])
* Mentor: Even Rouault
* There is a need for calling GDAL utilities from code without involving system calls, to be able to work on in-memory datasets and use progress/cancellation callback functions.
* Before, inorder to use any functionalities of GDAL utilities in a program, the developer had to use system calls. Even then, the developer cannot work with in memory datasets.
* Now, the developers can easily have all the functionalities of GDAL utilities through dedicated functions which are part of GDAL core library. There is no system call involved and it works on in-memory datasets.
* Project: https://trac.osgeo.org/gdal/wiki/rfc59.1_utilities_as_a_library

=== GRASS GIS - Improved Metadata for GRASS GIS ===
Matej Krejci ([http://tinyurl.com/pp69bwd Picture])
* Mentors: Martin Landa, Angelos Tzotsos, Luca Delucchi
* Description: The first aim was to improve current package by adding a new functionality for extend metadata handling. The second goal was to implement module for interaction with metadata catalogue services (CSW).
* State of the project before GSoC: In 2014 during GSoC I have developed new GRASS GIS metadata management support based on ISO-INSPIRE. This package needed extension to meet the users requirements. In addition package for CSW searching was missing.
* Addition to the project: New module g.gui.cswbrowser based on graphical interface allows managing csw connections, setting filter and searching, browsing results and adding services to GRASS GIS have been implemented. For g.gui.metadata have been added support: exporting metadata reports to pdf, storing themes of metadata in SQL backend, publishing metadata to CSW and metadata support for Temporal datasets.
* Slide: https://grasswiki.osgeo.org/w/images/Find1.png

Links:
* Project: https://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support
* Development page 2015: https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata
* source SVN: http://svn.osgeo.org/grass/grass-addons/grass7/gui/wxpython/wx.metadata/

=== gvSIG - Port Network Analysis Extension to gvSIG 2.x branch ===

=== istSOS - Scalability for Big data processing for istSOS ===

Ambrosini Luca ([https://www.dropbox.com/sc/z3twbb6zicslvy2/AAC43ZE3JYy_JCAiLEGoOstIa Picture])

* Mentors: Massimiliano Cannata, Milan Antonovic

* Brief description of the idea : istSOS is essentially a data collector, it wasn't ready for BigData, the idea was to implement data replication to improve security, online time and performance.

* The state of the project before GSOS : All data were hosted on a single postgres db, and there wasn't a tool that helps finding this implementation limits.

* The addition that your project brought to the software : We adapted the source code to work with replications, we set up a middleware that balances query among multiple database server, and we realized a benchmarking tool to test system response time and its scaling .

* Gsoc Reports : https://sourceforge.net/p/istsos/wiki/GSoC_2015_scalability/

* Slide http://i.imgur.com/EACzyxf.png

=== JGrassTools - Development of a simplified 1D hydraulics model ===
Silvia Franceschi ([https://sites.google.com/a/hydrologis.com/home/_/rsrc/1348641375730/silviafranceschi/silli.jpg?height=320&width=234 Picture])
* Mentors: Andrea Antonello, Riccardo Rigon
* Description: The module developed during this GSoC2015 is SaintGeo, a simple 1D hydraulic model based on the equations of Saint Venant.
* State of the project before GSoC: There was an original implementation of the model in C language done during a master thesis by Angelo Zacchia and Riccardo Rigon. I did the porting in the JGrassTools library of the model together with the implementation of the code for reading and writing GIS layers as input and outputs.
* Addition to the project: The new model bases on GIS input layers instead of text files and has a graphical interface, directly provided by the integration in the JGrassTools library to specify the inputs and outputs files.
* Slide: https://github.com/moovida/jgrasstools/wiki/gsoqc2015imgs/a_profile_qin_monte_laterali_in_out10.png

Links:
* Project: http://www.jgrasstools.org
* Development page 2015: https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-2015
* Source: https://github.com/moovida/jgrasstools/tree/master/hortonmachine/src/main/java/org/jgrasstools/hortonmachine/modules/hydrogeomorphology/saintgeo

=== Mapserver - Add productivity tools to MapServer's ScribeUI ===
Samuel Lapointe ([https://goo.gl/photos/LbSwPeMrCG5V2K9t8 Picture])
* Mentors: Daniel Morissette; Jessica Lapointe
* Description: The goal of the project was to improve the error detection system, add the ability to export and import maps and add a way to generate a set of classes from data.
* State of the project before GSoC: When I wanted to debug a map that didn’t work, I had to check the generated Mapserver file to find the error. To create classes from a set of data, I had to analyse the data and create the classes using bounds I had manually calculated, and the only way to export a map was to use Git.
* Addition to the project: Now, I can see most syntax errors directly in the editor’s interface, I can use a menu to generate classes for a layer and I can export or import maps to share them with other users.
* Slide: https://drive.google.com/file/d/0B686XfUqwP1LMm5GaVV0ckZ1b2c/view?usp=sharing

Links:
* Project page: https://github.com/mapgears/scribeui
* Getting started: https://github.com/mapgears/scribeui/wiki/Getting-started-with-ScribeUI
* Demo: http://demo.scribeui.org/

=== Opticks – Image Enhancement/Background Suppression ===
Tom Van den Eynde ([https://goo.gl/photos/DKwS7Fq4ZWEmHfR46 Picture])
* Mentors: Trevor Clarke
* Brief description of the idea: The goal of the project was to implement the image enhancement algorithm Drizzle for both image and video input.
* The state of the project as it was before GSoC: In Opticks, when I wanted to use a low resolution image I had to resort to other software to first improve the quality or reduce the noise interference.
* The addition to the software: With the addition of the Drizzle algorithm, Opticks can enhance and improve the interpretability of images. Now, even low resolution or heavily noise polluted images can be used for various remote sensing applications.
* Slide: https://goo.gl/photos/szt3RW3X93v2ccZi9

Links:
* Project: https://www.google-melange.com/gsoc/project/details/google/gsoc2015/tomvde/5733935958982656
* Blog: http://drizzle-for-opticks-gsoc2015.blogspot.be/
* Repository: https://github.com/Tom-VdE/Drizzle-plugin
* Instructions: https://github.com/Tom-VdE/Drizzle-plugin/blob/master/README.md

=== OTP - GTFS-Realtime validation tool for Open Trip Planner ===

=== Osgeo-Live - Integration of geospatial OSS in educational notebooks ===

=== OSSIM - Tool for DSM generation using tri-stereo optical imagery ===
Martina Di Rita (You can find a [https://www.dropbox.com/s/59dfmpz8kwapmsf/2015-12-03%2015.54.15.jpg?dl=0 picture of me])
* '''Mentors:''' Oscar Kramer, David Burken
* '''Brief description of the idea:''' the work has been based on a previous GSoC project through which a tool, named DATE, for Digital Surface Model (DSM) generation from optical stereo-pair was developed within OSSIM framework. The idea was to improve and update DATE in order to generate DSMs from tri-stereo optical imagery and fix some bugs in the DSMs generation processing chain. DATE key features include the use of computer vision algorithms in order to improve the processing efficiency and make the DSMs generation process fully automatic.
* '''The state of the project as it was BEFORE this GSoC:''' before this GSoC it was not possible to process tri-stereo imagery and there was still some problem in finding the right quasi-epipolar geometry in the stereo version in order to compute a proper Disparity Map.
* '''Addition to the software:''' with DATE plug-in it is now possible to generate DSMs within OSSIM framework starting from stereo and tri-stereo satellite optical imagery. Furthermore, from the stereo processing side, I added an image preprocess filtering and I found a better solution for the quasi-epipolar geometry achievement.
'''Relevant links:'''
* GSoC Proposal: https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015/martidi/5717271485874176
* Weekly reports: https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery
* Please test my code in https://github.com/martidi/opencv_dsm/tree/master following the instructions in README.md file

* [[Link_to_image|Slide]] The slide / image should serve to show the main elements of your project. It could be a flow chart, a screenshot, both, or whatever you think could serve for the scope. Remember: the aim is to showcase your project to people that are not necessarily familiar with the software.

=== pgRouting ===

=== PyWPS-4 – REST Interface ===
Calin Cristian Nicolae Ciociu ([http://i.imgur.com/WglCPnz.jpg Picture])
* Mentors: Jachym Cepicky, Luís de Sousa
* Brief description of the idea: My project added the ability to use a REST interface to control, add, remove processes and change configuration of PyWPS-4 instances.
* The state of the project as it was before GSoC: We had to create/delete the processes by accessing the storage of the server which required a restart of the server every time something got changed.
* The addition to the software: With the addition of the REST interface I wrote everyone who needs to update, delete, or add new processes and change configuration can do so without accessing the server.
* Slide: http://i.imgur.com/oYAHsgQ.png

Links:
* Project: http://www.google-melange.com/gsoc/project/details/google/gsoc2015/noctalin/5717271485874176
* Repository: https://github.com/jachym/pywps-4
* Instructions: https://github.com/PyWPS/pywps-4-demo/blob/master/README.rst

=== QGIS - Multithread Support on Processing Toolboxt ===
Marcus Santos ([https://media.licdn.com/media/AAEAAQAAAAAAAATOAAAAJDA1Y2M0MWQ0LTMyYjMtNDlhMi05OWM3LWIxMDQ5YWM1ZTk2MA.jpg Picture])
* Mentors: Victor Olaya, Alexander Bruy
* Description: This project consisted on making the QGIS Processing toolbox multi-threaded, allowing to have non blocking analysis/geoprocessing jobs, prevent crashes (when a QGIS module crashes for some reason) and also improve the user experience.
* The state of the project GSoC: Before the multithreading support, the user was only able to run one analysis at a time and there was no option to cancel the algorithm execution.
* The addition to the project: With multithreading support the user is allowed to cancel long geoprocessing jobs and also run several algorithms at the same time.
* Slide: https://www.dropbox.com/s/fmaxf97jkmf2cy1/slide.png?dl=0

Links:
* Project page: https://qgisgsoc2015.wordpress.com
* Repository: https://github.com/mvcsantos/QGIS
* Demo: https://www.youtube.com/watch?v=V-CJCnKw89U

=== OSGeo-Live - TIntegration of geospatial OSS in educational notebooks ===
Massimo Di Stefano ([http://tw.rpi.edu/media/latest/Massimo_Di_Stefano.jpg Picture])
* '''Mentors: Cameron Shorter, Rich Signell, Angelos Tzotsos'''
* '''Brief description of the idea:'''This GSoC 2015 Idea will focus on the development of a cross-projects python library with the aim of bridging together the several software libraries already installed on the live through the use of the Jupyter notebook server in a series of "topic-oriented" geospatial notebooks.
* '''The state of the project as it was BEFORE this GSoC:''' before this GSoC there was no jupyter-notebook installed and very limited set of example based on the IPython-notebook.
* '''Addition to the software:''' After GSOC 2015 an installer for the jupyter-notebook has ben developed (enabling multiple kernels [py2, py3, R, Bash, Julia]) and a series of geospatial notebooks to show the usage of several project like GDAL, OSSIM, GRASS has been added. The project also included the building on Debian packages for the jupyter single user ecosystem and the collaborative development of widget for interactive visualization of geospatial data from a notebook ([https://github.com/epifanio/CesiumWidget CesiumWidget])
'''Relevant links:'''
* GSoC Proposal: https://wiki.osgeo.org/wiki/Live_GIS_GSoC_2015
* Weekly reports: https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery
* Repository: https://github.com/epifanio/GSOC2015
* Demo http://epinux.com/cesium-720p.mp4
* [[Link_to_image|Slide]]

[[Category:Google Summer of Code]]

Google Summer of Code 2015 Results

2015-12-04T20:02:52Z

Wiki-Epifanio:

<center>
[[Image:GoogleSummer_2015logo.jpg|200px|link=http://code.google.com/soc/]] @ [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]
</center>

OSGeo participated in Google Summer of Code 2015 with 13 projects, all successful:

* GDAL - Faza Mahamood: [https://github.com/fazam/gdal/tree/gdalinfo Integration of GDAL utilities into GDAL core library]

* GRASS GIS - Matej Krejci: [https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata Improved Metadata for GRASS GIS]

* gvSIG - Eva Rodríguez: [https://redmine.gvsig.net/redmine/projects/gvsig-networkanalysis/wiki Port Network Analysis Extension to gvSIG 2.x branch]

* istSOS - Luca Ambrosini: [http://sourceforge.net/p/istsos/wiki/GSoC_2015_scalability/ Scalability for Big data processing for istSOS]

* JGRASSTOOLS - Silvia Franceschi: [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-2015 Development of a simple 1D hydraulic model for JGRASSTOOLS]

* MapServer - Samuel Lapointe: [https://github.com/mapgears/scribeui/wiki/Google-Summer-of-Code-2015 Add productivity tools to MapServer's ScribeUI]

* Opticks - Tom Van den Eynde: [http://drizzle-for-opticks-gsoc2015.blogspot.be/ Image Enhancement/Background Suppression for Opticks]

* OTP - Nipuna Gunathilake: [https://github.com/CUTR-at-USF/gtfs-realtime-validator/wiki GTFS-Realtime validation tool for Open Trip Planner]

* OSGeo-Live - Massimo Di Stefano: [https://github.com/epifanio/IPython_notebooks/blob/master/OSGeo-live/osgeolive-gsoc-2015/Report/Weekly%20report%2013.ipynb Integration of geospatial OSS in educational notebooks]

* OSSIM - Martina Di Rita: [https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery OSSIM tool for DSM generation using tri-stereo and SAR imagery]

* pgRouting - Sarthak Agarwal: [https://github.com/pgRouting/pgrouting/wiki/GSoC-2015-Sarthak-Agarwal New osm2pgrouting import tool to import OpenStreetMap (OSM) data in pgRouting]

* PyWPS - Calin Ciociu: [https://github.com/jachym/pywps-4/wiki/GSoC-2015 REST interface for PyWPS 4]

* QGIS - Marcus Santos: [https://qgisgsoc2015.wordpress.com/ QGIS - Multithread support on QGIS Processing toolbox]

== Description of the projects ==

=== Example: software XYZ - title of my GSoC project ===
Student1 (picture)
* Mentors: Mentor1; Mentor2; OtherMentors?
* Brief description of the idea. e.g. "[[link|My project]] focused on xxx".
* The state of the project as it was BEFORE your GSoC. For example, if you made a GUI, you can say: "In the software XYZ, when I wanted to use the tool xxx, I had to manually edit the file yyy. "
* The addition that your project brought to the software. In the same example: "With the GUI that I created, now it is possible to use the tool xxx via graphical user interface".
* Add all the links (hopefully permanent) to access the relevant code and documentation for the user to get started with testing your application. "Please test my [[code-repository|code]] following instructions [[some-link|here]]".
* [[Link_to_image|Slide]] The slide / image should serve to show the main elements of your project. It could be a flow chart, a screenshot, both, or whatever you think could serve for the scope. Remember: the aim is to showcase your project to people that are not necessarily familiar with the software.

=== GDAL - Integration of GDAL utilities into GDAL core library ===
Faza Mahamood ([https://drive.google.com/file/d/0B9gY4JeBmoKVZ2REcjcwVnl1Nk0/view?usp=sharing Picture])
* Mentor: Even Rouault
* There is a need for calling GDAL utilities from code without involving system calls, to be able to work on in-memory datasets and use progress/cancellation callback functions.
* Before, inorder to use any functionalities of GDAL utilities in a program, the developer had to use system calls. Even then, the developer cannot work with in memory datasets.
* Now, the developers can easily have all the functionalities of GDAL utilities through dedicated functions which are part of GDAL core library. There is no system call involved and it works on in-memory datasets.
* Project: https://trac.osgeo.org/gdal/wiki/rfc59.1_utilities_as_a_library

=== GRASS GIS - Improved Metadata for GRASS GIS ===
Matej Krejci ([http://tinyurl.com/pp69bwd Picture])
* Mentors: Martin Landa, Angelos Tzotsos, Luca Delucchi
* Description: The first aim was to improve current package by adding a new functionality for extend metadata handling. The second goal was to implement module for interaction with metadata catalogue services (CSW).
* State of the project before GSoC: In 2014 during GSoC I have developed new GRASS GIS metadata management support based on ISO-INSPIRE. This package needed extension to meet the users requirements. In addition package for CSW searching was missing.
* Addition to the project: New module g.gui.cswbrowser based on graphical interface allows managing csw connections, setting filter and searching, browsing results and adding services to GRASS GIS have been implemented. For g.gui.metadata have been added support: exporting metadata reports to pdf, storing themes of metadata in SQL backend, publishing metadata to CSW and metadata support for Temporal datasets.
* Slide: https://grasswiki.osgeo.org/w/images/Find1.png

Links:
* Project: https://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support
* Development page 2015: https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata
* source SVN: http://svn.osgeo.org/grass/grass-addons/grass7/gui/wxpython/wx.metadata/

=== gvSIG - Port Network Analysis Extension to gvSIG 2.x branch ===

=== istSOS - Scalability for Big data processing for istSOS ===

Ambrosini Luca ([https://www.dropbox.com/sc/z3twbb6zicslvy2/AAC43ZE3JYy_JCAiLEGoOstIa Picture])

* Mentors: Massimiliano Cannata, Milan Antonovic

* Brief description of the idea : istSOS is essentially a data collector, it wasn't ready for BigData, the idea was to implement data replication to improve security, online time and performance.

* The state of the project before GSOS : All data were hosted on a single postgres db, and there wasn't a tool that helps finding this implementation limits.

* The addition that your project brought to the software : We adapted the source code to work with replications, we set up a middleware that balances query among multiple database server, and we realized a benchmarking tool to test system response time and its scaling .

* Gsoc Reports : https://sourceforge.net/p/istsos/wiki/GSoC_2015_scalability/

* Slide http://i.imgur.com/EACzyxf.png

=== JGrassTools - Development of a simplified 1D hydraulics model ===
Silvia Franceschi ([https://sites.google.com/a/hydrologis.com/home/_/rsrc/1348641375730/silviafranceschi/silli.jpg?height=320&width=234 Picture])
* Mentors: Andrea Antonello, Riccardo Rigon
* Description: The module developed during this GSoC2015 is SaintGeo, a simple 1D hydraulic model based on the equations of Saint Venant.
* State of the project before GSoC: There was an original implementation of the model in C language done during a master thesis by Angelo Zacchia and Riccardo Rigon. I did the porting in the JGrassTools library of the model together with the implementation of the code for reading and writing GIS layers as input and outputs.
* Addition to the project: The new model bases on GIS input layers instead of text files and has a graphical interface, directly provided by the integration in the JGrassTools library to specify the inputs and outputs files.
* Slide: https://github.com/moovida/jgrasstools/wiki/gsoqc2015imgs/a_profile_qin_monte_laterali_in_out10.png

Links:
* Project: http://www.jgrasstools.org
* Development page 2015: https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-2015
* Source: https://github.com/moovida/jgrasstools/tree/master/hortonmachine/src/main/java/org/jgrasstools/hortonmachine/modules/hydrogeomorphology/saintgeo

=== Mapserver - Add productivity tools to MapServer's ScribeUI ===
Samuel Lapointe ([https://goo.gl/photos/LbSwPeMrCG5V2K9t8 Picture])
* Mentors: Daniel Morissette; Jessica Lapointe
* Description: The goal of the project was to improve the error detection system, add the ability to export and import maps and add a way to generate a set of classes from data.
* State of the project before GSoC: When I wanted to debug a map that didn’t work, I had to check the generated Mapserver file to find the error. To create classes from a set of data, I had to analyse the data and create the classes using bounds I had manually calculated, and the only way to export a map was to use Git.
* Addition to the project: Now, I can see most syntax errors directly in the editor’s interface, I can use a menu to generate classes for a layer and I can export or import maps to share them with other users.
* Slide: https://drive.google.com/file/d/0B686XfUqwP1LMm5GaVV0ckZ1b2c/view?usp=sharing

Links:
* Project page: https://github.com/mapgears/scribeui
* Getting started: https://github.com/mapgears/scribeui/wiki/Getting-started-with-ScribeUI
* Demo: http://demo.scribeui.org/

=== Opticks – Image Enhancement/Background Suppression ===
Tom Van den Eynde ([https://goo.gl/photos/DKwS7Fq4ZWEmHfR46 Picture])
* Mentors: Trevor Clarke
* Brief description of the idea: The goal of the project was to implement the image enhancement algorithm Drizzle for both image and video input.
* The state of the project as it was before GSoC: In Opticks, when I wanted to use a low resolution image I had to resort to other software to first improve the quality or reduce the noise interference.
* The addition to the software: With the addition of the Drizzle algorithm, Opticks can enhance and improve the interpretability of images. Now, even low resolution or heavily noise polluted images can be used for various remote sensing applications.
* Slide: https://goo.gl/photos/szt3RW3X93v2ccZi9

Links:
* Project: https://www.google-melange.com/gsoc/project/details/google/gsoc2015/tomvde/5733935958982656
* Blog: http://drizzle-for-opticks-gsoc2015.blogspot.be/
* Repository: https://github.com/Tom-VdE/Drizzle-plugin
* Instructions: https://github.com/Tom-VdE/Drizzle-plugin/blob/master/README.md

=== OTP - GTFS-Realtime validation tool for Open Trip Planner ===

=== Osgeo-Live - Integration of geospatial OSS in educational notebooks ===

=== OSSIM - Tool for DSM generation using tri-stereo optical imagery ===
Martina Di Rita (You can find a [https://www.dropbox.com/s/59dfmpz8kwapmsf/2015-12-03%2015.54.15.jpg?dl=0 picture of me])
* '''Mentors:''' Oscar Kramer, David Burken
* '''Brief description of the idea:''' the work has been based on a previous GSoC project through which a tool, named DATE, for Digital Surface Model (DSM) generation from optical stereo-pair was developed within OSSIM framework. The idea was to improve and update DATE in order to generate DSMs from tri-stereo optical imagery and fix some bugs in the DSMs generation processing chain. DATE key features include the use of computer vision algorithms in order to improve the processing efficiency and make the DSMs generation process fully automatic.
* '''The state of the project as it was BEFORE this GSoC:''' before this GSoC it was not possible to process tri-stereo imagery and there was still some problem in finding the right quasi-epipolar geometry in the stereo version in order to compute a proper Disparity Map.
* '''Addition to the software:''' with DATE plug-in it is now possible to generate DSMs within OSSIM framework starting from stereo and tri-stereo satellite optical imagery. Furthermore, from the stereo processing side, I added an image preprocess filtering and I found a better solution for the quasi-epipolar geometry achievement.
'''Relevant links:'''
* GSoC Proposal: https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015/martidi/5717271485874176
* Weekly reports: https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery
* Please test my code in https://github.com/martidi/opencv_dsm/tree/master following the instructions in README.md file

* [[Link_to_image|Slide]] The slide / image should serve to show the main elements of your project. It could be a flow chart, a screenshot, both, or whatever you think could serve for the scope. Remember: the aim is to showcase your project to people that are not necessarily familiar with the software.

=== pgRouting ===

=== PyWPS-4 – REST Interface ===
Calin Cristian Nicolae Ciociu ([http://i.imgur.com/WglCPnz.jpg Picture])
* Mentors: Jachym Cepicky, Luís de Sousa
* Brief description of the idea: My project added the ability to use a REST interface to control, add, remove processes and change configuration of PyWPS-4 instances.
* The state of the project as it was before GSoC: We had to create/delete the processes by accessing the storage of the server which required a restart of the server every time something got changed.
* The addition to the software: With the addition of the REST interface I wrote everyone who needs to update, delete, or add new processes and change configuration can do so without accessing the server.
* Slide: http://i.imgur.com/oYAHsgQ.png

Links:
* Project: http://www.google-melange.com/gsoc/project/details/google/gsoc2015/noctalin/5717271485874176
* Repository: https://github.com/jachym/pywps-4
* Instructions: https://github.com/PyWPS/pywps-4-demo/blob/master/README.rst

=== QGIS - Multithread Support on Processing Toolboxt ===
Marcus Santos ([https://media.licdn.com/media/AAEAAQAAAAAAAATOAAAAJDA1Y2M0MWQ0LTMyYjMtNDlhMi05OWM3LWIxMDQ5YWM1ZTk2MA.jpg Picture])
* Mentors: Victor Olaya, Alexander Bruy
* Description: This project consisted on making the QGIS Processing toolbox multi-threaded, allowing to have non blocking analysis/geoprocessing jobs, prevent crashes (when a QGIS module crashes for some reason) and also improve the user experience.
* The state of the project GSoC: Before the multithreading support, the user was only able to run one analysis at a time and there was no option to cancel the algorithm execution.
* The addition to the project: With multithreading support the user is allowed to cancel long geoprocessing jobs and also run several algorithms at the same time.
* Slide: https://www.dropbox.com/s/fmaxf97jkmf2cy1/slide.png?dl=0

Links:
* Project page: https://qgisgsoc2015.wordpress.com
* Repository: https://github.com/mvcsantos/QGIS
* Demo: https://www.youtube.com/watch?v=V-CJCnKw89U

=== OSGeo-Live - TIntegration of geospatial OSS in educational notebooks ===
Massimo Di Stefano ([http://tw.rpi.edu/media/latest/Massimo_Di_Stefano.jpg Picture])
* '''Mentors: Cameron Shorter, Rich Signell, Angelos Tzotsos'''
* '''Brief description of the idea:'''This GSoC 2015 Idea will focus on the development of a cross-projects python library with the aim of bridging together the several software libraries already installed on the live through the use of the Jupyter notebook server in a series of "topic-oriented" geospatial notebooks.
* '''The state of the project as it was BEFORE this GSoC:''' before this GSoC there was no jupyter-notebook installed and very limited set of example based on the IPython-notebook.
* '''Addition to the software:''' After GSOC 2015 an installer for the jupyter-notebook has ben developed (enabling multiple kernels [py2, py3, R, Bash, Julia]) and a series of geospatial notebooks to show the usage of several project like GDAL, OSSIM, GRASS has been added. The project also included the building on Debian packages for the jupyter single user ecosystem and the collaborative development of widget for interactive visualization of geospatial data from a notebook ([https://github.com/epifanio/CesiumWidget CesiumWidget])
'''Relevant links:'''
* GSoC Proposal: https://wiki.osgeo.org/wiki/Live_GIS_GSoC_2015
* Weekly reports: https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery
* Repository: https://github.com/epifanio/GSOC2015
* Demo http://epinux.com/cesium-720p.mp4
* [[Link_to_image|Slide]]

[[Category:Google Summer of Code]]

FOSS4G Europe 2015 GeoForAll Agenda

2015-07-15T10:19:52Z

Wiki-Epifanio: /* 3. GeoForAll Europe Meeting */

GeoForAll FOSS4G Como meetings, tentative agendas and who will be there. Please add your name to the sessions if you plan to attend, and feel free to add agenda items if you have something you want discussed. -- email me (cschweik AT Pubpol.umass.edu) if you have questions or concerns.

== 1. GeoForAll pre-conference meeting ==

When: Tuesday July 14th, 8:30-11:30 am

Where: 14 Via Natta. Note: The building is in the city centre of Como (not in the main campus where the conference will take place). See here http://www.openstreetmap.org/?mlat=45.808829&mlon=9.083251#map=18/45.80883/9.08325&layers=N
On the wall outside the building is a sign that says 'Politecnico Di Milano' and 14 is written above the doorway. Go through the door and there is a small security room. There will be signs saying 'GeoForAll' posted somewhere near this station. The meeting room is in the upstairs. I (Charlie) will be there at 8am getting set up. Give yourself time to find this building (there are nice cafes all along the roads leading to it so you can pick up your morning coffee! We will start right at 8:30 am!

Agenda:

1.'''Welcome and quick introductions''' (Suchith, Charlie) 8:30-8:45
- Need scribe volunteer

2. '''GeoForAll lab membership issues''' (Helena leads the discussion here) - 8:45-9:30 (Ideally faster than this)
* 2a.Quick update on the current Lab membership list [1] - inactive ones? What do we still need to do to get the list updated?
* 2b.We want this list to reflect active labs. '''What criteria do we use for lab removal and can this be documented? Annual procedure for keeping this list updated? Can we do this here in Como and get the list updated'''?
* 2c.Lab membership questions (9:30-10:00)
**i.Our current membership criteria text is here: http://wiki.osgeo.org/wiki/Geoforall_criteria
**ii.What kind of organization can be called a ‘lab’? Can firms, gov agencies, nonprofits also be ‘Labs’? (based on the discussion so far it appears that YES, ask everybody to put the type of organization into notes)
**iii.Currently our membership table has some non-universities [1]. Discuss the issue of firms or agendies as labs or 'partners'.
**iv.Discuss the idea of GeoForAll lab membership expansion to K-12 schools.
**v. Regional mailing lists-keep or delete? There is enough support for keeping them.
*summary of key recommendations or action items to report in the BOF 1 on Thursday.

3. '''Certification issues''' (Phil Davis leads) (10:00-10:30)
* 3a. Phil opens with 5 minute summary/status
* 3b. Tanzeel Khan presents his findings on 'An OS Certification Model.' 10 minutes
* 3c. Discussion
* 3d. summary of key recommendations or action items to report in the BOF 1 on Thursday

4. '''OSGeo and GeoForAll educational committee''' -- What is their relationship? Same or different entities? (10:30-10:45)
* We need to update the OSGeo Education page [8]. Who would like to help this week?

5. '''Educational content curation strategies''' (Charlie leads) (10:45-11:15)
* How can we get past simple emailing information about educational material we have developed?
* Current options
** Go back to our earlier educational metada inventory system [2, 3]
** Use Rick Smith's GeoAcademy GitHub system [4]
** Work with Suchith to get the ELOGeo system back up and operational. Suchith mentioned that it was built using the UK Open Educational Resource system Jorum [5]
** Investigate the use of the Drupal-based OpenABM system (if grant funding comes in). See [6]. Charlie has a conference call with their team tomorrow.
** Consider utilizing one of the existing Open Educational Repository systems such as Rice U CNX [7], Carnegie Mellon Open Learning Initiative, or the Open Education Consortium [7]
* Short term strategy? Longer term strategy?
* summary of key recommendations or action items to report in the BOF 1 on Thursday

6. '''Lightning round update on grant-getting efforts''' (Charlie leads) (11:15-11:25)
*a.Charlie - NSF RCN
*b.Antoni - H2020 efforts
*c.Suchith - AgriGIS?
*d. Maria - Italy US opportunity

7.'''Decide on agenda item priorities for BOF 1 report back''' (11:25-11:30)

[1] http://wiki.osgeo.org/wiki/Edu_current_initiatives#sortable_table_id_0

[2] http://www.osgeo.org/educational_content

[3] https://www.osgeo.org/node/add/edu-content

[4] https://github.com/FOSS4GAcademy

[5] http://www.jorum.ac.uk/

[6] https://www.openabm.org/

[7] http://www.oeconsortium.org/

[8] http://www.osgeo.org/education

Attending? Add your name below.

* Charlie Schweik, USA
* Maria, Italy
* Dimitris Kotzinos
* [[User:Helena|Helena Mitasova]]
* [[User:Darsvid|Daria Svidzinska]]
* [[User:Wenzeslaus|Vaclav Petras]]
* [[User:Fjbehr|Franz-Josef Behr]]
* [[User:Aperezn|Antoni Perez-Navarro]]
* [[User:Dirkf|Dirk Frigne]]
* [http://www.linkedin.com/in/ronfortunato Ron Fortunato]
* Suchith Anand (attending by Skype - sanand1976)
* Mario Miler
* others?

== 2. GeoForAll BOF meeting #1 ==

When: Thursday July 16th, 8:00-9:00 AM

Where: room VS9, Valleggio building

Agenda:

* Report back and discussion of items from our pre-conference meeting (see above).
* Other new discussion items from the Group
* Preparation and ideas for Seoul conference

Attending? Add your name to the BOF signup list [http://wiki.osgeo.org/wiki/FOSS4G_Europe_2015_BirdsOfAFeather#GeoForAll_BOF here]

== 3. GeoForAll Europe Meeting ==

When: Thursday July 16th, 5:30

Where: room 3.5 at Politecnico di Milano

(This is a good idea... any other regions have a group attending and want
to meet up?)

Agenda:
* collaborations between the European and US labs, students exchange and funding opportunities

Attending? Add your name below.

* Charlie Schweik, USA
* Maria, Italy
* [[User:Aghisla|Anne]], Italy/Germany
* Dimitris Kotzinos
* Ela Wołoszyńska-Wiśniewska, Poland
* Helena Mitasova
* [[User:Darsvid|Daria Svidzinska]], Ukraine
* [[User:Fjbehr|Franz-Josef Behr]]
* [[User:Aperezn|Antoni Perez-Navarro]]
* Nadia Panchaud, Switzerland
* Suchith Anand (attending by Skype)
* [[User:epifanio|Massimo Di Stefano]]
* others?

== 4. GeoForAll Bird's of a Feather 2 ==

When: Friday July 17th, 12:00-13:00

Where: room 3.6, Castelnuovo building

Agenda:
* 30 minute discussion of GeoForAll and connections with primary, seconday, high schools (Ela helps lead)
** Who is doing what (responsibilities)?
** Can we build a network of teachers and schools? And how to start?
** Can we ask the teachers/students of the network via a questionnaire?
** What can we do to make our tools better and useful to every teacher and child? (i.e. translation, new tools, new ideas, applications based on the age, etc)
* 30 minutes on people reporting on their next steps and planning for Seoul -- who is going? Organizing there?

Attending? Add your name to the BOF signup list [http://wiki.osgeo.org/wiki/FOSS4G_Europe_2015_BirdsOfAFeather#GeoForAll_BOF_2 here]

== 5. GeoForAll Grant Sprint ==

When: Saturday July 18th - 8:30-11:30

Where: Hall of Via Natta building

Agenda:

* US NSF Smart City proposal (Charlie Schweik, others with GeoForAll city analytics group)
* Hopefully some discussion by European participants on another grant effort to support GeoForAll efforts (anyone working on this? add your name and topic)

Attending? Add your name below.
* Charlie Schweik, USA
* Maria, Italy
* Dimitris Kotzinos
* [[User:Darsvid|Daria Svidzinska]], Ukraine
* [[User:Wenzeslaus|Vaclav Petras]]
* [[User:Aperezn|Antoni Perez-Navarro]]
* Suchith Anand (attending by Skype)
* others?

== TOPICS NOT ON THE CURRENT AGENDA BUT NEED TO BE DISCUSSED ==

Add any ideas here please.

Questions? Contact Charlie Schweik - cschweik AT pubpol DOT UMass DOT edu

FOSS4G Europe 2015 BirdsOfAFeather

2015-07-15T10:17:03Z

Wiki-Epifanio: /* GeoForAll BOF 2 */

= Introduction =
Birds of a Feather (BoF) sessions are unstructured timeslots where people can self-organise themselves to discuss topics of interest.

== General Information ==
During the [http://europe.foss4g.org/2015/ FOSS4G Europe 2015] conference in Como, Italy, there will be a number of spaces for people to hold Birds of a Feather sessions.

 
The 1-hour time blocks outlined below are just general guidelines. Adjust as needed. For reference, an overview of the FOSS4G schedule is available at [http://europe.foss4g.org/2015/Program http://europe.foss4g.org/2015/Program].

 
=== Rooms ===
We have available the three rooms of the conference (VS9, V08, V2.12) from 8 am up to 8 pm.
Therefore the BOFs can be there when there are not sessions.

=== Capacities ===
* Room VS9: 236
* Room V08: 98
* Room V2.12: 93
 

==FOSS4G Contact==
* conference-europe(at)lists.osgeo.org
 

== Wednesday ==

=== Room VS9 ===

{| class="wikitable" border="1"
|-
! Timeslot !! Topic/Group !! Description !! Contact
|-
| 08:00-09:00 || || ||
|-
| 13:00-14:00 || || ||
|}

 

=== Room V08 ===

{| class="wikitable" border="1"
|-
! Timeslot !! Topic/Group !! Description !! Contact
|-
| 08:00-09:00 || || ||
|-
| 13:00-14:00 || FOSS4G 2016 || Planning meeting || [[Till Adams]]
|}

 

=== Room V2.12 ===

{| class="wikitable" border="1"
|-
! Timeslot !! Topic/Group !! Description !! Contact
|-
| 08:00-09:00 || || ||
|-
| 13:00-14:00 || || ||
|}

 

== Thursday ==

=== Room VS9 ===

{| class="wikitable" border="1"
|-
! Timeslot !! Topic/Group !! Description !! Contact
|-
| 08:00-09:00 || GeoForAll || Discussions about open education || JM
|-
| 13:00-14:00 || Launching a European Geoscience Union (EGU) Interest Group || A meeting place for OSGeo interested in EGU/AGU. Discussion: OSGeo related research/activities in the EGU Divisions, stakeholders, current links between OSGeo and EGU/AGU, how to move on || Peter Löwe
|-
| 18:00-19:15 || Osgeo Europe / OSGeo Membership / OSGeo Industry || Discussion: OSGeo Europe as a legal entity, OSGeo membership discussion and how OSGeo relates to the geo-ict industry || Dirk Frigne
|}

 

=== Room V08 ===

{| class="wikitable" border="1"
|-
! Timeslot !! Topic/Group !! Description !! Contact
|-
| 08:00-09:00 || || ||
|-
| 13:00-14:00 || OSM editing time || Insert into OSM data collected during OSM Mapping Party || Luca Delucchi / Peter Mooney
|-
| 18:00-19:15 || || ||
|}

 

=== Room V2.12 ===

{| class="wikitable" border="1"
|-
! Timeslot !! Topic/Group !! Description !! Contact
|-
| 08:00-09:00 || || ||
|-
| 13:00-14:00 || || ||
|-
| 18:00-19:15 || || ||
|}

 
 

== Friday ==

=== Room VS9 ===

{| class="wikitable" border="1"
|-
! Timeslot !! Topic/Group !! Description !! Contact
|-
| 08:00-09:00 || || ||
|-
| 13:00-14:00 || || ||
|-
| 18:00-19:15 || H2020 || Discuss topics and possibilities to apply for an H2020 project || aperezn at uoc dot edu
|}

 

=== Room V08 ===

{| class="wikitable" border="1"
|-
! Timeslot !! Topic/Group !! Description !! Contact
|-
| 08:00-09:00 || || ||
|-
| 13:00-14:00 || || ||
|-
| 18:00-19:15 || OSGeo Board meeting || Board face-to-face meeting || JM
|}

 

=== Room V2.12 ===

{| class="wikitable" border="1"
|-
! Timeslot !! Topic/Group !! Description !! Contact
|-
| 08:00-09:00 || || ||
|-
| 13:00-14:00 || || ||
|-
| 18:00-19:15 || || ||
|}

 
 

== FOSS4G 2016 Planning BOF ==

* Description: Planning for the 2016 conference that will be held in Bonn, Germany
* When/Where: Wednesday 15th of July, 13h-14h, '''Room V08'''
* Topics:
** Marketing & PR activities (Gert-Jan)
** Sponsorship (Arnulf) (Do we need Media sponsors?)
** FOSS4G-EU 2016? (Till, @all)
** Timetable (Till)
** Relation FOSSGIS <-> OSGEO (Till, Jeff)
** Academic Track (FJ)

Who is coming:
* [[Jeff McKenna]]
* [[Till Adams]]
* [[Arnulf Christl]]
* [[user:Geejee|Gert-Jan van der Weijden]]
* [[User:Fjbehr|Franz-Josef Behr]]
* [[User:Endofcap|Sanghee Shin]]
* [[User:Astrid Emde|Astrid Emde]]
* [[User:Peter_Loewe|Peter Löwe]]
* [[User:Dirkf|Dirk Frigne]]
* [[User:jachym|Jachym Cepicky]]
* [[User:kotzino|Dimitris Kotzinos]]

== GeoForAll BOF ==

* Description: Discussions about open education. Sharing within the OSGeo, ICA, and ISPRS communities. http://www.geoforall.org/
* When/Where: Thursday 16th of July, 08:00-09:00, '''Room VS9'''
* More info: [http://wiki.osgeo.org/wiki/FOSS4G_Europe_2015_GeoForAll_Agenda Agenda]

Who is coming:
* [[Jeff McKenna]]
* Phillip Davis
* [[Arnulf Christl]]
* Lene Fischer
* [[Charlie Schweik]]
* [[User:Siki|Zoltan Siki]]
* [[BarendKobben]]
* [[User:kotzino|Dimitris Kotzinos]]
* Ela Wołoszyńska-Wiśniewska
* [[Helena Mitasova]]
* [[Martin Landa]]
* [[User:Imincik|Ivan Minčík]]
* [[User:Darsvid|Daria Svidzinska]]
* [[User:Wenzeslaus|Vaclav Petras]]
* [[User:Fjbehr|Franz-Josef Behr]]
* [[User:Aperezn|Antoni Perez-Navarro]]
* [[User:Aghisla|Anne aka aghisla]]
* [[Georg Gartner]]
* [[User:Lucadelu|Luca Delucchi]]
* [http://www.linkedin.com/in/ronfortunato Ron Fortunato]
* Maria Brovelli
* Suchith Anand (attending by Skype - sanand1976)
* [[User:Dirkf|Dirk Frigne]]
* [[User:Mmiler|Mario Miler]]
* [[User:epifanio|Massimo Di Stefano]]

== GeoForAll BOF 2 ==

* Description: Open session to plan our collective activities after reflecting on the conference experiences.
* When/Where: Friday July 17th, 12:00-13:00 '''Room 3.6'''
* More info: [http://wiki.osgeo.org/wiki/FOSS4G_Europe_2015_GeoForAll_Agenda Agenda]

Who is coming:
* [[Charlie Schweik]]
* [[BarendKobben]]
* [http://wiki.osgeo.org/wiki/User:kotzino Dimitris Kotzinos]
* Ela Wołoszyńska-Wiśniewska
* [[Helena Mitasova]]
* [[User:Darsvid|Daria Svidzinska]]
* [[User:Aperezn|Antoni Perez-Navarro]]
* [[User:Lucadelu|Luca Delucchi]]
* Suchith Anand (attending by skype - sanand1976)
* [[User:epifanio|Massimo Di Stefano]]

== OSM editing time ==

* Description: Insert into OSM data collected during OSM Mapping Party
* When/Where: Thursday 16th of July, 13:00-14:00 '''Room V08'''
* More info: [http://wiki.openstreetmap.org/wiki/Como_foss4ge_2015 OpenStreetMap wiki page]

Who is coming:

* [[User:Lucadelu|Luca Delucchi]]
* [[User:Pmooney|Peter Mooney]]

== European Geoscience Union (EGU) Interest Group BoF ==

* Description: A meeting place for OSGeo people interested in EGU/AGU. Discussion: OSGeo related research/activities in the EGU Divisions, stakeholders, current links between OSGeo and EGU/AGU, how to move on

* When/Where: Thursday 16th of July,, 13:00-14:00 hours, '''room VS9'''
* [[FOSS4G Europe 2015 EGU Interest Group BOF Agenda|Agenda]]

Who is coming:
* [[User:Peter_Loewe|Peter Löwe]]
* [[Jeff McKenna]]
* [[User:Maxi71| Massimiiano Cannata]]
* [[User:Madi| Margherita Di Leo]]

== OSGeo Europe BOF ==

* Description: Follow up of the conversation started at FOSS4G Europe 2014 about Osgeo Europe / OSGeo Membership / OSGeo Industry
* When/Where: Thursday 16th of July, 18:00-19:15 hours, '''room VS9'''
* More info: [[FOSS4G Europe 2015 OSGeo Europe BOF Agenda|Agenda]]

Who is coming:
* [[User:Dirkf|Dirk Frigne]]
* [[User:ecosyd|Kari Salovaara]]
* [[Jeff McKenna]]
* [[User:OliverMay|Oliver May]]
* [[User:Geejee|Gert-Jan van der Weijden]]
* [[User:Neteler|Markus Neteler]]
* [[User:jachym|Jáchym Čepický]]
* [[Till Adams]]
* [[User:kotzino|Dimitris Kotzinos]]
* [[User:Peter_Loewe|Peter Löwe]]

== Your BOF Name Here ==

* Description:
* When/Where:

Who is coming:
*
*

----

* See [[FOSS4G_2009_BirdsOfAFeather|FOSS4G 2009 Birds of a Feather]] for inspiration!

[[Category:FOSS4G]]
[[Category:FOSS4G-Europe]]

FOSS4G Europe 2015 BirdsOfAFeather

2015-07-15T10:15:25Z

Wiki-Epifanio: /* GeoForAll BOF */

= Introduction =
Birds of a Feather (BoF) sessions are unstructured timeslots where people can self-organise themselves to discuss topics of interest.

== General Information ==
During the [http://europe.foss4g.org/2015/ FOSS4G Europe 2015] conference in Como, Italy, there will be a number of spaces for people to hold Birds of a Feather sessions.

 
The 1-hour time blocks outlined below are just general guidelines. Adjust as needed. For reference, an overview of the FOSS4G schedule is available at [http://europe.foss4g.org/2015/Program http://europe.foss4g.org/2015/Program].

 
=== Rooms ===
We have available the three rooms of the conference (VS9, V08, V2.12) from 8 am up to 8 pm.
Therefore the BOFs can be there when there are not sessions.

=== Capacities ===
* Room VS9: 236
* Room V08: 98
* Room V2.12: 93
 

==FOSS4G Contact==
* conference-europe(at)lists.osgeo.org
 

== Wednesday ==

=== Room VS9 ===

{| class="wikitable" border="1"
|-
! Timeslot !! Topic/Group !! Description !! Contact
|-
| 08:00-09:00 || || ||
|-
| 13:00-14:00 || || ||
|}

 

=== Room V08 ===

{| class="wikitable" border="1"
|-
! Timeslot !! Topic/Group !! Description !! Contact
|-
| 08:00-09:00 || || ||
|-
| 13:00-14:00 || FOSS4G 2016 || Planning meeting || [[Till Adams]]
|}

 

=== Room V2.12 ===

{| class="wikitable" border="1"
|-
! Timeslot !! Topic/Group !! Description !! Contact
|-
| 08:00-09:00 || || ||
|-
| 13:00-14:00 || || ||
|}

 

== Thursday ==

=== Room VS9 ===

{| class="wikitable" border="1"
|-
! Timeslot !! Topic/Group !! Description !! Contact
|-
| 08:00-09:00 || GeoForAll || Discussions about open education || JM
|-
| 13:00-14:00 || Launching a European Geoscience Union (EGU) Interest Group || A meeting place for OSGeo interested in EGU/AGU. Discussion: OSGeo related research/activities in the EGU Divisions, stakeholders, current links between OSGeo and EGU/AGU, how to move on || Peter Löwe
|-
| 18:00-19:15 || Osgeo Europe / OSGeo Membership / OSGeo Industry || Discussion: OSGeo Europe as a legal entity, OSGeo membership discussion and how OSGeo relates to the geo-ict industry || Dirk Frigne
|}

 

=== Room V08 ===

{| class="wikitable" border="1"
|-
! Timeslot !! Topic/Group !! Description !! Contact
|-
| 08:00-09:00 || || ||
|-
| 13:00-14:00 || OSM editing time || Insert into OSM data collected during OSM Mapping Party || Luca Delucchi / Peter Mooney
|-
| 18:00-19:15 || || ||
|}

 

=== Room V2.12 ===

{| class="wikitable" border="1"
|-
! Timeslot !! Topic/Group !! Description !! Contact
|-
| 08:00-09:00 || || ||
|-
| 13:00-14:00 || || ||
|-
| 18:00-19:15 || || ||
|}

 
 

== Friday ==

=== Room VS9 ===

{| class="wikitable" border="1"
|-
! Timeslot !! Topic/Group !! Description !! Contact
|-
| 08:00-09:00 || || ||
|-
| 13:00-14:00 || || ||
|-
| 18:00-19:15 || H2020 || Discuss topics and possibilities to apply for an H2020 project || aperezn at uoc dot edu
|}

 

=== Room V08 ===

{| class="wikitable" border="1"
|-
! Timeslot !! Topic/Group !! Description !! Contact
|-
| 08:00-09:00 || || ||
|-
| 13:00-14:00 || || ||
|-
| 18:00-19:15 || OSGeo Board meeting || Board face-to-face meeting || JM
|}

 

=== Room V2.12 ===

{| class="wikitable" border="1"
|-
! Timeslot !! Topic/Group !! Description !! Contact
|-
| 08:00-09:00 || || ||
|-
| 13:00-14:00 || || ||
|-
| 18:00-19:15 || || ||
|}

 
 

== FOSS4G 2016 Planning BOF ==

* Description: Planning for the 2016 conference that will be held in Bonn, Germany
* When/Where: Wednesday 15th of July, 13h-14h, '''Room V08'''
* Topics:
** Marketing & PR activities (Gert-Jan)
** Sponsorship (Arnulf) (Do we need Media sponsors?)
** FOSS4G-EU 2016? (Till, @all)
** Timetable (Till)
** Relation FOSSGIS <-> OSGEO (Till, Jeff)
** Academic Track (FJ)

Who is coming:
* [[Jeff McKenna]]
* [[Till Adams]]
* [[Arnulf Christl]]
* [[user:Geejee|Gert-Jan van der Weijden]]
* [[User:Fjbehr|Franz-Josef Behr]]
* [[User:Endofcap|Sanghee Shin]]
* [[User:Astrid Emde|Astrid Emde]]
* [[User:Peter_Loewe|Peter Löwe]]
* [[User:Dirkf|Dirk Frigne]]
* [[User:jachym|Jachym Cepicky]]
* [[User:kotzino|Dimitris Kotzinos]]

== GeoForAll BOF ==

* Description: Discussions about open education. Sharing within the OSGeo, ICA, and ISPRS communities. http://www.geoforall.org/
* When/Where: Thursday 16th of July, 08:00-09:00, '''Room VS9'''
* More info: [http://wiki.osgeo.org/wiki/FOSS4G_Europe_2015_GeoForAll_Agenda Agenda]

Who is coming:
* [[Jeff McKenna]]
* Phillip Davis
* [[Arnulf Christl]]
* Lene Fischer
* [[Charlie Schweik]]
* [[User:Siki|Zoltan Siki]]
* [[BarendKobben]]
* [[User:kotzino|Dimitris Kotzinos]]
* Ela Wołoszyńska-Wiśniewska
* [[Helena Mitasova]]
* [[Martin Landa]]
* [[User:Imincik|Ivan Minčík]]
* [[User:Darsvid|Daria Svidzinska]]
* [[User:Wenzeslaus|Vaclav Petras]]
* [[User:Fjbehr|Franz-Josef Behr]]
* [[User:Aperezn|Antoni Perez-Navarro]]
* [[User:Aghisla|Anne aka aghisla]]
* [[Georg Gartner]]
* [[User:Lucadelu|Luca Delucchi]]
* [http://www.linkedin.com/in/ronfortunato Ron Fortunato]
* Maria Brovelli
* Suchith Anand (attending by Skype - sanand1976)
* [[User:Dirkf|Dirk Frigne]]
* [[User:Mmiler|Mario Miler]]
* [[User:epifanio|Massimo Di Stefano]]

== GeoForAll BOF 2 ==

* Description: Open session to plan our collective activities after reflecting on the conference experiences.
* When/Where: Friday July 17th, 12:00-13:00 '''Room 3.6'''
* More info: [http://wiki.osgeo.org/wiki/FOSS4G_Europe_2015_GeoForAll_Agenda Agenda]

Who is coming:
* [[Charlie Schweik]]
* [[BarendKobben]]
* [http://wiki.osgeo.org/wiki/User:kotzino Dimitris Kotzinos]
* Ela Wołoszyńska-Wiśniewska
* [[Helena Mitasova]]
* [[User:Darsvid|Daria Svidzinska]]
* [[User:Aperezn|Antoni Perez-Navarro]]
* [[User:Lucadelu|Luca Delucchi]]
* Suchith Anand (attending by skype - sanand1976)

== OSM editing time ==

* Description: Insert into OSM data collected during OSM Mapping Party
* When/Where: Thursday 16th of July, 13:00-14:00 '''Room V08'''
* More info: [http://wiki.openstreetmap.org/wiki/Como_foss4ge_2015 OpenStreetMap wiki page]

Who is coming:

* [[User:Lucadelu|Luca Delucchi]]
* [[User:Pmooney|Peter Mooney]]

== European Geoscience Union (EGU) Interest Group BoF ==

* Description: A meeting place for OSGeo people interested in EGU/AGU. Discussion: OSGeo related research/activities in the EGU Divisions, stakeholders, current links between OSGeo and EGU/AGU, how to move on

* When/Where: Thursday 16th of July,, 13:00-14:00 hours, '''room VS9'''
* [[FOSS4G Europe 2015 EGU Interest Group BOF Agenda|Agenda]]

Who is coming:
* [[User:Peter_Loewe|Peter Löwe]]
* [[Jeff McKenna]]
* [[User:Maxi71| Massimiiano Cannata]]
* [[User:Madi| Margherita Di Leo]]

== OSGeo Europe BOF ==

* Description: Follow up of the conversation started at FOSS4G Europe 2014 about Osgeo Europe / OSGeo Membership / OSGeo Industry
* When/Where: Thursday 16th of July, 18:00-19:15 hours, '''room VS9'''
* More info: [[FOSS4G Europe 2015 OSGeo Europe BOF Agenda|Agenda]]

Who is coming:
* [[User:Dirkf|Dirk Frigne]]
* [[User:ecosyd|Kari Salovaara]]
* [[Jeff McKenna]]
* [[User:OliverMay|Oliver May]]
* [[User:Geejee|Gert-Jan van der Weijden]]
* [[User:Neteler|Markus Neteler]]
* [[User:jachym|Jáchym Čepický]]
* [[Till Adams]]
* [[User:kotzino|Dimitris Kotzinos]]
* [[User:Peter_Loewe|Peter Löwe]]

== Your BOF Name Here ==

* Description:
* When/Where:

Who is coming:
*
*

----

* See [[FOSS4G_2009_BirdsOfAFeather|FOSS4G 2009 Birds of a Feather]] for inspiration!

[[Category:FOSS4G]]
[[Category:FOSS4G-Europe]]

User:Epifanio

2015-04-18T22:43:27Z

Wiki-Epifanio: /* | Massimo Di Stefano */

__NOTOC__
=== [http://tw.rpi.edu/web/person/MassimoDiStefano | Massimo Di Stefano] ===
[[File:Epi.png|thumb|right|100px|Massimo Di Stefano]]

Massimo Di Stefano, graduated from "Università degli Studi di Napoli "Parthenope"" (Naples, IT) with a Master's Degree in Environmental Science, specializing in Marine Ecosystem. Massimo is now pursuing his Ph.D. at CCOM-JHC in Oceanography. A founding member of [http://gfoss.it/drupal/ GFOSS.it], the Italian community of users and developers of Geographic Free/Open-Source Software (GFOSS) and charter member of OSGeo, Massimo has spent more than 10 years developing Geographical Free and Open Source Software, with current development activities in [http://grass.osgeo.org/ GRASS], [http://trac.osgeo.org/ossim OSSIM], [http://www.qgis.org/en/site/ QGIS] and [http://live.osgeo.org/en/index.html OSGeo Live] projects. For the past four years, Massimo worked as Research Assistant III at the Woods Hole Oceanographic Institute (WHOI) for the HABCAM project, and as Software Engineer on staff at the Tetherless World Constellation (RPI) on the ECO-OP project.

;OSGeo Experience [[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]] [[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]] [[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]]

* PhD Candidate in Oceanography at Center for Coastal and Ocean Mapping CCOM - University of New Hampshire
* Software Engineer at [http://tw.rpi.edu/web/person/MassimoDiStefano RPI] (Renssellaer Polytechnic Institute)
* Guest Investigator at [http://www.whoi.edu/profile.do?id=mdistefano WHOI] (Woods Hole Oceanographic Institution)
* GIS Team member of [http://www.geofemengineering.it GeofemEngineering]
* Cartography and Geodesy Specialist
* Member of the [http://www.ossim.org OSSIM] Dev-Team
* Promoting Free Software
* [http://www.ossim.org Ossim],[http://grass.itc.it/ Grass], and [http://www.qgis.org/ Qgis] development
* [http://www.gfoss.it gfoss.it] Founder
* [http://trac.osgeo.org/ossim/wiki/GoogleSummerOfCode OSGEO-Google Summer Of Code]
* [[italiano | Italian OSGeo Board]] Member
* Italian Osgeo Liason Officer ([[italiano]])
* [http://live.osgeo.org/en/index.html OSGeo-Live] contributor
* Translating the OSGeo [http://www.osgeo.org official site] into Italian

'''Contact'''

: [mailto:epiesasha@me.com epiesasha@me.com]
: IRC : '''epifanio'''
: Skype : '''epifaniox'''

User:Epifanio

2015-04-18T22:39:23Z

Wiki-Epifanio: /* | Massimo Di Stefano */

__NOTOC__
=== [http://tw.rpi.edu/web/person/MassimoDiStefano | Massimo Di Stefano] ===
[[File:Epi.png|thumb|right|100px|Massimo Di Stefano]]

Massimo Di Stefano, graduated from "Università degli Studi di Napoli "Parthenope"" (Naples, IT) with a Master's Degree in Environmental Science, specializing in Marine Ecosystem. Massimo is now pursuing his Ph.D. at CCOM-JHC in Oceanography. A founding member of [http://gfoss.it/drupal/] (GFOSS.it), the Italian community of users and developers of Geographic Free/Open-Source Software (GFOSS) and charter member of OSGeo, Massimo has spent more than 10 years developing Geographical Free and Open Source Software, with current development activities in [http://grass.osgeo.org/] (GRASS), [http://trac.osgeo.org/ossim/](OSSIM), [http://www.qgis.org/en/site/] (QGIS) and [http://live.osgeo.org/en/index.html] (OSGeo Live) projects. For the past four years, Massimo worked as Research Assistant III at the Woods Hole Oceanographic Institute (WHOI) for the HABCAM project, and as Software Engineer on staff at the Tetherless World Constellation (RPI) on the ECO-OP project.

;OSGeo Experience [[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]] [[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]] [[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]]

* Software Engineer at [http://tw.rpi.edu/web/person/MassimoDiStefano RPI] (Renssellaer Polytechnic Institute)
* Guest Investigator at [http://www.whoi.edu/profile.do?id=mdistefano WHOI] (Woods Hole Oceanographic Institution)
* GIS Team member of [http://www.geofemengineering.it GeofemEngineering]
* Cartography and Geodesy Specialist
* Member of the [http://www.ossim.org OSSIM] Dev-Team
* Promoting Free Software
* [http://www.ossim.org Ossim],[http://grass.itc.it/ Grass], and [http://www.qgis.org/ Qgis] development
* [http://www.gfoss.it gfoss.it] Founder
* [http://trac.osgeo.org/ossim/wiki/GoogleSummerOfCode OSGEO-Google Summer Of Code]
* [[italiano | Italian OSGeo Board]] Member
* Italian Osgeo Liason Officer ([[italiano]])
* [http://live.osgeo.org/en/index.html OSGeo-Live] contributor
* Translating the OSGeo [http://www.osgeo.org official site] into Italian

'''Contact'''

: [mailto:epiesasha@me.com epiesasha@me.com]
: IRC : '''epifanio'''
: Skype : '''epifaniox'''

User:Epifanio

2015-04-18T22:38:32Z

Wiki-Epifanio: /* | Massimo Di Stefano */

__NOTOC__
=== [http://tw.rpi.edu/web/person/MassimoDiStefano | Massimo Di Stefano] ===
[[File:Epi.png|thumb|right|100px|Massimo Di Stefano]]

Massimo Di Stefano, graduated from "Università degli Studi di Napoli "Parthenope"" (Naples, IT) with a Master's Degree in Environmental Science, specializing in Marine Ecosystem. Massimo is now pursuing his Ph.D. at CCOM-JHC in Oceanography. A founding member of [http://gfoss.it/drupal/](GFOSS.it), the Italian community of users and developers of Geographic Free/Open-Source Software (GFOSS) and charter member of OSGeo, Massimo has spent more than 10 years developing Geographical Free and Open Source Software, with current development activities in [http://grass.osgeo.org/](GRASS), [http://trac.osgeo.org/ossim/](OSSIM), [http://www.qgis.org/en/site/](QGIS) and [http://live.osgeo.org/en/index.html](OSGeo Live) projects. For the past four years, Massimo worked as Research Assistant III at the Woods Hole Oceanographic Institute (WHOI) for the HABCAM project, and as Software Engineer on staff at the Tetherless World Constellation (RPI) on the ECO-OP project.

;OSGeo Experience [[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]] [[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]] [[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]]

* Software Engineer at [http://tw.rpi.edu/web/person/MassimoDiStefano RPI] (Renssellaer Polytechnic Institute)
* Guest Investigator at [http://www.whoi.edu/profile.do?id=mdistefano WHOI] (Woods Hole Oceanographic Institution)
* GIS Team member of [http://www.geofemengineering.it GeofemEngineering]
* Cartography and Geodesy Specialist
* Member of the [http://www.ossim.org OSSIM] Dev-Team
* Promoting Free Software
* [http://www.ossim.org Ossim],[http://grass.itc.it/ Grass], and [http://www.qgis.org/ Qgis] development
* [http://www.gfoss.it gfoss.it] Founder
* [http://trac.osgeo.org/ossim/wiki/GoogleSummerOfCode OSGEO-Google Summer Of Code]
* [[italiano | Italian OSGeo Board]] Member
* Italian Osgeo Liason Officer ([[italiano]])
* [http://live.osgeo.org/en/index.html OSGeo-Live] contributor
* Translating the OSGeo [http://www.osgeo.org official site] into Italian

'''Contact'''

: [mailto:epiesasha@me.com epiesasha@me.com]
: IRC : '''epifanio'''
: Skype : '''epifaniox'''

LIDAR Format Letter

2015-04-18T22:33:44Z

Wiki-Epifanio: /* Signed */

=Open Letter of the Need for Open Standards in LiDAR=
April 2015.

We, the undersigned, are concerned that the current interoperability between LiDAR applications, through use of the open "LAS" format, is being threatened by ESRI's introduction and promotion of an alternative "Optimized LAS" '''''proprietary format.''''' This is of grave concern given that fragmentation of the LAS format will reduce interoperability between applications and organisations, and introduce vendor lock-in.

We request that:
# The OGC initiate the formalisation of an open standard for storing LiDAR data, and that OGC sponsors help prioritise the development of this open LiDAR standard.
# ESRI support the OGC in their [http://www.opengeospatial.org/ogc/vision mission] "to advance the development and use of international standards and supporting services that promote geospatial interoperability." In particular, ESRI join the OGC in consolidating an Open Standard for use of LiDAR data. This might include proposing ESRI's "Optimized LAS" as an Open Standard to remove any technical or legal hurdles in use of "Optimized LAS" as an Open Standard. A simple test to determine if "Optimized LAS" can be used as an Open Standard would be if "Optimized LAS" can legally be implemented by Open Source software such as libLAS or LASzip.
# Users and sponsors of LiDAR data, publicly state their preference for the use of an open LiDAR format over proprietary when selecting software and services.
# The custodians of the open LAS format [http://www.asprs.org/LD-Division/LAS-Working-Group.html LAS Working Group (LWG)], who are part of [http://www.asprs.org/ American Society for Photogrammetry and Remote Sensing (ASPRS)], request the term "LAS" not to be included in the name of a proprietary format, as it makes such a proprietary format appear to be an approved derivative of LAS.

=Signed=
Name, Affiliation(s), Optional comment on interest in Open LiDAR format

# Suchith Anand, Geo for All, committed to Open Principles in Geo Education and Policy.
# Martin Isenburg, founder of [http://rapidlasso.com rapidlasso GmbH] and creator of [http://rapidlasso.com/LASzip LASzip], [http://rapidlasso.com/LAStools LAStools], and [http://rapidlasso.com/PulseWaves PulseWaves].
# Cameron Shorter, GeoSpatial Director at [http://lisasoft.com LISAsoft]. Core contributor and coordinator of [http://live.osgeo.org OSGeo-Live]. Contributor to numerous OGC testbeds, technical lead on a range of previous Australian and New Zealand Open Government initiatives.
# Stefan Keller, founder and director of [http://www.hsr.ch/geometalab Geometa Lab]; Professor in GIS, databases, open (government) data and interoperability; maintainer of GeoConverter; contributor to open source software (GDAL/OGR, QGIS).
# Patrick Hogan, NASA World Wind Project Manager, committed to the US National Spatial Data Infrastructure principles, one being "to make geographic data more accessible to the public" [http://www.fgdc.gov/nsdi/nsdi.html NSDI]. Open standards are essential for this.
# Lene Fischer, Associate Professor, Department of Geosciences and Natural Resource Management, University of Copenhagen. User of Open and free Data from The Danish Geodata Agency - Using LAZ and LAS http://download.kortforsyningen.dk/content/dhmpunktsky.
# [http://www.ege-como.polimi.it/index.php?content=maria_brovelli Maria Antonia Brovelli], Full Professor, Department of Civil and Environmental Engineering, Politecnico di Milano. Geo For All, committed to Open Principles in Geo Education and Policy. Committed to Open Principles in Research.
# Ron Fortunato, President of [http://www.trilliumlearning.com/AmericaBridge/ Trillium Learning] LLC. Committed to open data standards that are necessary for education and all levels of communication.
# [http://www.geodatawiz.com/armin-schmidt Armin Schmidt], Chief Developer at [http://www.GeodataWIZ.com GeodataWIZ Ltd] and Chairman of [http://www.archprospection.org ISAP], committed to better science through Open Data.
# [http://www.linkedin.com/in/gconti Giuseppe Conti], CTO Trilogis Srl, Italy. Committed to open data standards that maximize opportunity for innovative solutions, unencumbered by artificial obstacles to data exchange.
# [http://pt.linkedin.com/pub/jorge-rocha/1b/560/499 Jorge Gustavo Rocha], Professor, Computer Science Department, University of Minho, Portugal, committed to better science through [http://www.gistam.org/EventChairs.aspx?y=2016 Open Data].
# [http://people.eecs.ku.edu/~miller/ Jim Miller], University of Kansas, Professor, Computer Science. Open standards for data exchange are essential for education and research.
# [http://www.linkedin.com/pub/brandt-melick/22/869/261 Brandt Melick], Information Technology Department Director, Springfield Oregon USA. The need to promote open solutions is paramount.
# Alex Paza Makini, National University Solomon Islands, Natural Resources and Applied Science. Committed to open data standards for education and research, and everything beyond.
# Jorg M. Hacker, Professor, Director/Chief Scientist of [http://www.airborneresearchaustralia.com Airborne Research Australia], Flinders University, Adelaide, Australia. Open formats have always been a great benefit to airborne LiDAR.
# Didier Richard, Head of IS Training Dept. in Education and Research Directorate of [http://www.ign.fr Institut National de l'Information Géographique et Forestière], France. OGC user, Contributor to OSGeO projects like GDAL.
# [http://www.linkedin.com/pub/adryane-gorayeb/74/517/96a Adryane Gorayeb], [http://www.ufc.br/ Federal University of Ceará Brazil], Geography Department. Open standards for data exchange are essential for education and research.
# [http://www.linkedin.com/in/yuryryabov Yury Ryabov], PhD, Senior researcher at [http://www.istc.ru/istc/db/inst.nsf/wsu/i0001823 Russian Scientific-Research Centre for Ecological Safety], [http://www.interacademies.net/Academies/ByRegion/CentralEasternEurope/13383.aspx Russian Academy of Sciences], Saint Petersburg, Russia. Open data formats are essential for successful and reproducible scientific research.
# [http://www.linkedin.com/pub/teresa-lamelas-gracia/40/4a7/20b María Teresa Lamelas], [http://cud.unizar.es/ Centro Universitario de la Defensa Zaragoza], [http://geoforest.unizar.es/es/index.php GeoForest-IUCA]. Committed to open data standards for education and research.
# [http://www.linkedin.com/in/davidherries David Herries], [http://www.interpine.co.nz/SitePages/Home.aspx Using LiDAR for forest yield modelling at Interpine Innovation]. Establishing open data standards provide scope for exponential growth in innovation. This is key to a rapidly developing technology like LiDAR.
# [[User:Ivansanchez|Iván Sánchez Ortega]], [http://www.mazemap.no Mazemap]. OSGeo Charter member and Open Data nerd.
# [[User:AnitaGraser|Anita Graser]], GIS specialist with AIT Austrian Institute of Technology, OSGeo Charter member and QGIS team member. Committed to open data standards for education and research.
# [[User:vehrka|Pedro-Juan Ferrer]], [http://www.geomaticblog.net Geomaticblog]. OSGeo Charter member and member of the Open Knowledge Foundation.
# [http://www.linkedin.com/pub/karl-donert/3/160/571 Professor Karl Donert], President European Association of Geographers (http://www.eurogeo.nl/ EUROGEO)
# Drew Fenton, Boulder Creek, CA [http://www.savetheredwoods.org/redwoods/coast-redwoods/ Countdown to the Last Coast Redwood]. Please protect Open Standards for geospatial data!
# [[User:Bolosig|Wladimir Szczerban]], [http://www.geoinquiets.cat Geoinquiets] Geogeek & OSGeo Spanish Local Chapter Member, Spain
# [http://vmx.cx Volker Mische], OSGeo Charter member and creator of GeoCouch
# [http://www.linkedin.com/in/clquintanilla Carlos López Quintanilla], [http://www.psig.es PSIG] [http://www.geoinquiets.cat Geoinquiets] GIS consultant, Spain
# [[User:woodbri|Stephen Woodbridge]], [http://imaptools.com iMaptools], OSGeo Charter member.
# [[User:odoepner|Oliver Doepner]], [http://oliver.doepner.net doepner.net], Software Engineer (Java,Linux), Open Standards and Open Source advocate
# [[User:Lucadelu|Luca Delucchi]], [http://gis.cri.fmach.it Fondazione Edmund Mach], OSGeo Charter member, FOSS4G and Open Data developer, advocate, contributor and user.
# Antoine Cottin, CTO of [http://www.carbomap.com Carbomap Ltd.] and creator of [http://github.com/carbomap/Fleurdelas Fleurdelas], Edinburgh, United Kingdom.
# [http://strk.keybit.net Sandro Santilli], [http://strk.keybit.net/services.html NetLab], Free Software Hacker. There are already too many users slave to their tools, let's stop that!
# [http://www.itopen.it Alessandro Pasotti], [http://www.itopen.it ItOpen], GIS Free Software Developer.
# [http://www.roccatello.com Eduard Roccatello], [http://www.3dgis.it 3DGIS], 3DGIS CTO and co-Founder
# [[User:moovida|Andrea Antonello]], [http://www.hydrologis.com HydroloGIS], OSGeo Charter member, Open Source GIS developer, HydroloGIS co-founder.
# [http://www.associazionegfoss.it Stefano Campus], President of [http://www.associazionegfoss.it GFOSS.it] Association (Associazione Italiana per l'Informazione Geografica Libera), Italian Local Chapter of OSGeo Foundation.
# [http://wiki.osgeo.org/wiki/User:Madi Margherita Di Leo], OSGeo Charter Member
# [http://wiki.osgeo.org/wiki/User:Sacosta Sergio Acosta y Lara], OSGeo Charter Member
# [http://wiki.osgeo.org/wiki/User:Maximdubinin Maxim Dubinin], CEO at NextGIS, OSGeo Charter Member. Another 'standard' proprietary format? No, thank you.
# [[User:Steko|Stefano Costa]], Soprintendenza Archeologia della Liguria, Ministero dei Beni e delle Attività Culturali e del Turismo, Italy
# [http://www.geog.illinois.edu/people/jgrn Jonathan Greenberg], Assistant Professor, [http://publish.illinois.edu/jgrn/ GEARS Laboratory], Department of Geography and Geographic Information Science, University of Illinois at Urbana-Champaign.
# Bob Basques, Saint Paul, Mn., Technical Director for SharedGeo.
# [http://wiki.osgeo.org/wiki/User:Maning Maning Sambale], OSGeo Charter Member
# [http://wiki.osgeo.org/wiki/User:Pcav Paolo Cavallini], QGIS PSC
# [http://wiki.osgeo.org/wiki/User:Dr Phillip Davis], Member OSGeo Geo For All education advisory board, Director @ GeoAcademy
# [http://wiki.osgeo.org/wiki/User:Nbozon Nicolas Bozon], [http://zoo-project.org ZOO-Project PSC], OSGeo Charter Member
# [http://www.linkedin.com/in/ruslanrainis Ruslan Rainis], Professor, Director, [http://www.research.usm.my/default.asp?tag=36 Centre for Research Initiatives in Liberal Arts & Social Sciences](CRI-LASS). Open GeoInformation for a Sustainable Tomorrow and the Bottom Billions.
# [[User:Silli|Silvia Franceschi]], [http://www.hydrologis.com HydroloGIS], OSGeo Charter member, Environmental Engineer Open Source GIS power user, HydroloGIS co-founder.
# Oscar Martinez Rubi [http://esciencecenter.nl Netherlands eScience Center] eScience engineer.
# Werner Macho, QGIS team member. Committed to open data standards for education and research.
# Giuseppe Patti, Geologist and Freelance Geospatial Advisor, GFOSS supporter.
# [http://wiki.osgeo.org/wiki/User:Drappo Daniel Rappo], Professor, University of Applied Sciences and Arts Western Switzerland, School of Business and Engineering Vaud.
# [[User:nachouve|Juan Ignacio Varela]], Freelance Geospatial Advisor and OSGeo Local Chapter Member.
# [[User:dmorissette|Daniel Morissette]], President at [http://mapgears.com Mapgears], OSGeo Charter member.
# [http://www.linkedin.com/in/raulnanclares Raul Nanclares], RS&GIS Specialist
# [http://www.ing.unitn.it/dica/hp/index_eng.php?user=rigon Riccardo Rigon], Professor at University of Trento (Italy)
# [[User:Siki| Zoltan Siki]] Budapest University of Technology and Economics (Hungary), OSGeo Charter member.
# [http://lefsky.org Michael Lefsky], Professor of Remote Sensing Science, Colorado State University and Director, Center for Ecological Applications of Lidar.
# [http://www.linkedin.com/pub/lucas-c-villa-real/7/a0b/b06 Lucas Villa Real], Research software engineer at IBM Research - Brazil.
# [http://terraremote.com Loren Dawe], GIS Manager at Terra Remote Sensing Inc. Lidar Supplier and Open Standards Advocate
# [http://wiki.osgeo.org/wiki/User:Warmerda Frank Warmerdam], Software Developer, OSGeo Charter member
# [http://ch.linkedin.com/pub/jens-ingensand/0/836/6b0 Jens Ingensand], Professor, University of Applied Sciences and Arts Western Switzerland, [http://www.heig-vd.ch/international School of Business and Engineering Vaud].
# [http://nsidc.org/research/bios/khalsa.html Siri Jodha Khalsa], Research Scientist, National Snow and Ice Data Center, [http://cires.colorado.edu/ Cooperative Institute for Research in Environmental Sciences], University of Colorado, Boulder, USA
# [http://gis.uster.ch/ Andreas Neumann], GIS manager, City of Uster, Kanton Zurich, Switzerland
# [http://www.iwmi.org/ Yann Chemin], Researcher - Remote Sensing, International Water Management Institute, Colombo, Sri Lanka
# [http://www.linkedin.com/in/etiennebracine Etienne B. Racine], Geomatics and remote sensing project manager, WSP, Canada
# [http://www.linkedin.com/pub/alejandro-hinojosa/7/33b/342 Alejandro Hinojosa], [http://cicese.mx CICESE Research Center], Earth Sciences Division, GIS & Remote Sensing Lab, Ensenada, Mexico
# [http://wiki.osgeo.org/wiki/User:epifanio Massimo Di Stefano], OSGeo Charter Member

=Background=
==About LiDAR==

[http://en.wikipedia.org/wiki/Lidar LiDAR] (Light Detection And Ranging) is a form of high precision range measurement, much like a radar system, that uses laser light instead of electromagnetic waves. The standard LiDAR product is a 3D point cloud that can be conceptualized as a series of point measurements representing distance between the sensor to a returned emission.

For over a decade (since 2003), there has been a common format for storing LiDAR data, the [http://www.asprs.org/Committee-General/LASer-LAS-File-Format-Exchange-Activities.html “LAS” format], and open source libraries have been developed to read, write and process these LAS files: [http://live.osgeo.org/en/overview/liblas_overview.html libLAS] and [http://github.com/LASlib/LASlib LASlib]. These libraries have been incorporated within many LiDAR applications, allowing read/write access to a common exchange format, and resulting in full interoperability between the applications. There is also an open source compression algorithm for the LAS format called [http://laszip.org LASzip] that many LiDAR data portals use to compress LAS into smaller LAZ files for faster download. Many LiDAR software packages have added [http://laszip.org/#software-with-native-laz-support native support] for these compressed LAZ files.

==LAS Limitations==

Quoting [http://boundlessgeo.com/2014/01/lidar-format-wars/ Paul Ramsey]:

: LAS format is not without its drawbacks:

:* While it is a binary format and does not waste any space unnecessarily, neither does it apply any compression to the data it stores. That’s not good for archival use.
:* Also, LAS stores points in scan order, so accessing any particular chunk of points involves reading the whole file. That’s not good for random access.
: Clearly there is a little more work to be done. Can LAS be improved? In fact, it already has been:
:* An open source compression library, LASzip can apply 20''':'''1 lossless compression to LAS files, making them great for archival purposes.
:* Other LAS users have experimented with re-ordering points in a LAS or LASzip file to allow random access to internal chunks of the LIDAR point cloud.
: Basically, making LAS smaller and faster is not rocket science, and if the work were incorporated into libLAS then the whole LIDAR community could leverage it together, and the user community would only have one file type to interchange.

=="Optimized LAS" A ''' ''Proprietary'' ESRI Format'''==
ESRI has announced the release of an [http://www.lidarnews.com/content/view/10214 "Optimized LAS"] format which is claimed to provide faster access and smaller file sizes (similar to the open [http://laszip.org LASzip] format). This announcement created a outburst of vocal protest in the LiDAR community [[http://rapidlasso.com/2013/12/30/new-compressed-las-format-by-esri/ 1] [http://boundlessgeo.com/2014/01/lidar-format-wars/ 2] [http://www.spatiallyadjusted.com/2014/01/15/las-laz-lazzip-zlas-and-you/ 3] [http://www.northrivergeographic.com/archives/lidar-software 4] [http://boundlessgeo.com/2014/01/lidar-format-wars-2/ 5] [http://boundlessgeo.com/2014/02/lidar-format-wars-3/ 6]].

The "Optimized LAS" format is neither published, nor available under any open license, which provides both technical as well as legal barriers for other applications reading and/or writing to this proprietary format. This creates a vendor lock-in scenario which is contrary to the principles of the Open Geospatial Consortium, the OSGeo Foundation, and many government IT procurement policies.

One year after releasing the "Optimized LAS" format, ESRI released a free Windows DLL that is claimed to convert between LAS and "Optimized LAS". Note there is a distinct difference between "free" and "open". Unless the Windows DLL is released under an "open" license, libLAS and related products will be legally prevented from incorporating ESRI's reader/writer code into their codebase, or from fixing any underlying bugs or performance limitations which may exist in ESRI's product.

==OGC's Efforts For An ''' ''Open'' LiDAR Standard'''==

The [http://www.opengeospatial.org/ Open Geospatial Consortium (OGC)] has indicated their interest in developing a standard LiDAR format.

Carl Reed (formerly on OGC staff) provided the following information on OGC's previous efforts to work toward enabling Open Standards in LiDAR:

: "Over the last 8 or so years, the OGC approached ASPRS at least twice regarding LAS and worked with ASPRS to bring LAS into the OGC for consideration as both a Best Practice and an OGC standard. OGC member Rick Pearsall worked diligently on this. Rick worked for NGA, was active in the OGC, and was also the Standards Committee chair at ASPRS. Rick and Carl tried and failed. These attempts go back to [http://www.asprs.org/a/society/divisions/ppd/ppd_meetings/2007springppdreport.pdf at least 2007]. More recently, Carl Reed had an email dialogue with Lewis Graham to bring LAS into OGC as an OGC Best Practice. Carl thought progress was being made, but then for some reason all communication stopped."

[http://www.opengeospatial.org/ogc/organization/staff/ssimmons Scott Simmons] (Executive Director, Standards Program) has explained the OGC's continuing interest in pursuing point cloud encoding standards, including a member-initiated mechanism to extend LAS data with OGC-standard XML content.
: The OGC invites interested members who wish to work on this effort to please contact Scott Simmons (Executive Director, Standards Program E-mail : ssimmons@opengeospatial.org) to register their interest and discuss details. OGC will also be holding an ad hoc session at the OGC's next [http://www.opengeospatial.org/event/1506tc Technical Committee meeting in Boulder, CO, USA in early June] to bring together all interested parties from all sectors (government, industry, academia) for this and plan next steps.

==History: LAS and ESRI's "Optimized LAS"==

Martin Isenburg, one of the leading experts in LIDAR formats, and creator of [http://rapidlasso.com/LASzip LASzip], [http://rapidlasso.com/LAStools LAStools] and [http://rapidlasso.com/PulseWaves PulseWaves], explains the history of LAS and "Optimized LAS":

: '''Summary:'''

:* The LAS format has been used successfully for over a decade.
:* Within last couple of years, ESRI has added native LAS support into ESRI products.
:* ESRI discussed embracing the open [http://laszip.org LAZ] format and simultaneously developed a proprietary "Optimized LAS" format.
:* The open geospatial community offered, on numerous occasions, to work with ESRI to avoid format fragmentation.
:* ESRI's proprietary "Optimized LAS" format is very similar in design and performance to the open [http://laszip.org LASzip] format.

: '''1998: Original LAS format definition'''

: The original development of the LAS format started in 1998 according to [http://groups.google.com/forum/#!topic/lasroom/zKqchDj1JL4/discussion Lewis Graham]. The effort was at first led by pioneers of the LiDAR industry until the format was donated to the [http://www.asprs.org/Committee-General/LASer-LAS-File-Format-Exchange-Activities.html ASPRS]. Since then ASPRS's [http://www.asprs.org/LD-Division/LAS-Working-Group.html LAS Working Group (LWG)] has been maintaining the LAS format, guiding it from the initial LAS 1.0 version until today's LAS 1.4 version. This effort successfully created an open data exchange format for discrete LiDAR points that is currently supported by practically every LiDAR-related software program.

: '''2011: ESRI joins LAS Working Group'''

: ESRI did not join the LWG of the ASPRS until rather late, the 24th of August in 2011. At that time ESRI was not a significant "player" in the LiDAR market given they did not have much support for LiDAR in any of their products. That was to change soon as they were planning to add LAS as a native data type in ArcGIS 10.1.

: Shortly before that, in June 2011, Martin Isenburg received a personal message from the ESRI development team: "I have a question about LAS compression. I’m evaluating some potential enhancements and support for [LAS and] LAZ is one of them. Compression time and amount is impressive." When inquiring two months later about the status of [http://laszip.org LAZ] integration Martin was told: "We’re in beta and working to finish the current release. I very much doubt LAZ will make it in because it’s too big a change at this time. So, we’ll be considering, for the following release, [for] what we want to do regarding compression and spatial indexing."

: '''June 2012: ArcGIS 10.1 includes [proprietary] LAS Dataset file'''

: In June 2012 ESRI released ArcGIS 10.1 and introduced the proprietary "LAS Dataset file (*.lasd)" that groups collections of files into one logical unit. This format of this useful LAS container file was not shared with others despite several private and eventually [http://groups.google.com/d/topic/lastools/jwHpi0efUgA/discussion public] requests.

: '''2012/2013: Collaboration Discussions'''

: There were encouraging follow-ups from the ESRI team about adopting the open LAZ format in January 2012: "I would be interested in having a more in depth meeting with you to better understand the great work you are doing with LAS and how we can possibly better partner on this." and again in December 2012: "If you have time, I'd like to set some time aside Tuesday afternoon to meet with <an important person> at the ESRI booth. Does 2pm sound okay?" The meeting went well and it looked as if ESRI was going to embrace the LAZ format because shortly after the meeting Martin got word that: "I hear from <an important person> that it was a success and that he had a good meeting with you. I wanted to see if we can have a telephone discussion on Wednesday or Thursday this week related to the potential of incorporating LAZ into ArcGIS."

: Then the first signs of hesitation showed. First there were legal issues raised in February 2013: "Currently the legal aspects are being reviewed. They were having some issues separating the LPGL aspects from LASzip from the remainder of LAStools etc." and then in April 2013 concerns about the code were made: "We have started to look into the integration of LAZ, but came across some issues. We don’t want to copy files from the other package, mix and match or hack around. We were hoping for an API to stream points out of a LAZ file as well as write LAZ files. There should be a simple code sample for that?" and - following up on that - in June 2013 Martin was told "I see value in LASzip becoming a de-facto standard that provides compression to the LAS format. If this is to happen then it needs to be bundled together with appropriate reference implementations, examples and documentation as a standard and so ensure that issues as defined earlier in email do not occur."

: '''June 2013: ESRI asked to sponsor clean LASzip DLL'''

: At that time [http://laszip.org LASzip] was an open source project without sponsorship. The original funding from [http://www.erdc.usace.army.mil/Locations/ColdRegionsResearchandEngineeringLaboratory.aspx USACE] that had turned [http://laszip.org LASzip] from an academic prototype into an industry strength compression engine had long run out. So Martin asked ESRI to become a sponsor to create the clean [http://laszip.org LASzip] API that ESRI was after. The answer was: "ESRI often helps in the financing of Open Source projects and I could foresee ESRI possibly helping in LASzip. [...] If you are interested in promoting LASzip as such a standard and doing the required work then I would recommend you put together a proposal and I can look to get ESRI as a sponsor."

: Immediately Martin proposed to ESRI: "I hereby propose to write an easy to use open source DLL wrapper for LASzip that will make it easier to integrate LASzip in a standardized manner into other software products such as ArcGIS, LP 360, or Terrasolid. This will come with example code on how to use the DLL for reading and writing LAZ files and include a few compressed example files. I hereby ask ESRI to provide funding for this effort without imposing any limitations on the produced DLL API."

: '''July 2013: ArcGIS 10.2 includes [proprietary] LAS indexing '''

: With the release of ArcGIS 10.2 in July 2013, ESRI introduced spatial indexing to speed up area-of-interest queries. Their new proprietary *.lasx files were seemingly identical in functionality to the open *.lax files that had been [http://groups.google.com/d/topic/lastools/j0qA8NBMHJs/discussion announced] two years earlier - in May 2011 - and were [http://rapidlasso.com/2012/12/03/lasindex-spatial-indexing-of-lidar-data/ presented] at ELMF in November 2012.

: '''July 2013: Open LASzip API released'''

: After more requests for an easier interface to [http://laszip.org LASzip] (in particular for [http://forsys.cfr.washington.edu/fusion/fusionlatest.html USDA's FUSION]), Martin [http://groups.google.com/d/topic/lastools/oplsDhhnhDQ/discussion released] a clean, well-documented, and easy-to-use LASzip DLL (without ESRI funding). Martin expected that developers at ESRI would now use it to add read and write support for [http://laszip.org LAZ] to their next release of ArcGIS.

: '''December 2013 : ESRI discovered to be secretly developing proprietary LAS format'''

: In December of 2013, several LAStools users contacted Martin with suspicions that ESRI may be creating a proprietary LAS compression. Martin [http://rapidlasso.com/2013/12/30/new-compressed-las-format-by-esri/ broke the news] as soon as it became evident that ESRI had used the time it needed to resolve "legal issues" and "code problems" to put together their own proprietary compressed format with near-identical performance and functionality to [http://laszip.org LASzip]. A few days later ESRI released an [http://www.lidarnews.com/content/view/10214/ official FAQ] to confirming this was the case.

: From day one, Martin has worked with stakeholders, including ESRI, to avoid format fragmentation. Martin's core argument for resolving this to everybody's benefit was that - coincidentally - a natural break was happening in the LAS format with the introduction of the new LAS 1.4 point types. Martin outlined a detailed plan for how a joint development of [http://laszip.org LASzip] for LAS 1.4 between rapidlasso and ESRI could exploit this natural break in the LAS format to accomplish two things at once:
:# Add the unspecified technical additions that ESRI had hinted at desiring, and
:# Extend the [http://laszip.org LASzip] compression scheme to handle the new point types introduced with the LAS 1.4 specification. As there was no pressing need at the time to handle LAS 1.4 Martin had delayed the extension of [http://laszip.org LASzip] to the new LAS 1.4 point types to make sure a cooperation with ESRI would remain a viable option.

: '''1 April 2014: Positive reception to "Optimized LAS" / LASzip collaboration April Fools announcement'''

: In an attempt to convince ESRI management of the community desire for an open standard, Martin released an April Fools' Day [http://rapidlasso.com/2014/04/01/esri-and-rapidlasso-develop-joint-lidar-compressor/ prank press release] pretending that ESRI had already agreed to the envisioned collaboration to develop a joint LiDAR compressor. Community [http://rapidlasso.com/2014/04/01/esri-and-rapidlasso-develop-joint-lidar-compressor/ jubilant reactions (see comments)] left no doubt about the sentiment on this issue within the LiDAR community.

: '''October 2014: Announcement of [open] LAS Compatibility mode'''

: [http://www.csc.noaa.gov/digitalcoast/ Digital Coast, NOAA Coastal Services Center] became a Gold Sponsor of [http://laszip.org LASzip] for the development of the [http://rapidlasso.com/2014/10/06/rapidlasso-announces-laszip-compatibility-mode-for-las-1-4/ LAS 1.4 compatibility mode] that was [http://groups.google.com/d/topic/lastools/nUFMkKSz53g/discussion beta-released] in November 2014. This allowed support for the new point types in [http://laszip.org LASzip] without closing the door on a potential cooperation with ESRI for a joint LAS 1.4 compressor.

: '''November 2014: ESRI announces proprietary extension to LAS 1.4'''

: In November 2014 [http://blog.lidarnews.com/esri-las-optimizer-updated ESRI announced] that they had added their [http://blog.lidarnews.com/esri-las-optimizer-updated own extension] for the new LAS 1.4 point types to "Optimized LAS", dismissing the opportunity to develop a joint compressor and avoid format fragmentation by exploiting this "natural break" in the LAS format as Martin had suggested.

: Since then, ESRI has been [http://rapidlasso.com/2014/11/06/keeping-esri-honest/ promoting] "Optimized LAS". By including the term "LAS" in "Optimized LAS" and "zLAS", the distinction between the open LAS format and proprietary format is blurred. This is likely to mislead novice and future users, thereby endangering many years of standardization work. To date, [April 2014], the [http://www.asprs.org/a/society/committees/standards/LAS_1_4_r13.pdf custodians of the LAS format], the LAS Working Group (LWG) of the ASPRS has [http://rapidlasso.com/2015/02/22/lidar-las-asprs-esri-and-the-laz-clone/ yet to make an official statement] regarding use of the "LAS" name in promoting a proprietary LiDAR format.

=Value of Standards=

The importance of Open Standards is described in most government IT policies. For instance, the United Kingdom policy states:
: … Government assets should be interoperable and open for re-use in order to maximise return on investment, avoid technological or supplier lock-in, reduce operational risk in ICT projects and provide responsive services for citizens and business. This should also lower barriers to entry for more diverse sources of IT services, including citizens and SMEs. <ref>All about Open Source – [http://www.gov.uk/government/uploads/system/uploads/attachment_data/file/78959/All_About_Open_Source_v2_0.pdf An Introduction to Open Source Software for Government IT], Version 2.0, United Kingdom Cabinet Office</ref>

The value of Open Standards has been described in numerous national studies on the effects of standards on economic growth.

: ... the national studies demonstrate that standards have a positive influence on economic growth due to the resulting improved diffusion of knowledge. The contribution of standards to the growth rate in each country is equivalent to 0.9% in Germany, 0.8% in 0.3% in the UK and 0.2% in Canada. <ref>Prof. Dr. Knut Blind, Prof. Dr. Andre Jungmittag, Dr. Axel Mangelsdorf [http://www.din.de/sixcms_upload/media/2896/DIN_GNN_2011_engl_akt_neu.pdf "The Economic Benefits of Standardization"], ''DINN, 2000''. Retrieved March 2015.</ref>

=Further Reading=

# [http://boundlessgeo.com/2014/01/lidar-format-wars/ Paul Ramsey provides background to LAS vs Optimised LAS]
# [http://rapidlasso.com/2015/02/22/lidar-las-asprs-esri-and-the-laz-clone/ Running commentary by Martin Isenburg, author of LASlib]
# [http://rapidlasso.com/2014/11/06/keeping-esri-honest/ Earlier comment from Martin Isenburg]
# [http://rapidlasso.com/2013/12/30/new-compressed-las-format-by-esri/ First call-to-action by Martin Isenburg]
# [http://blog.lidarnews.com/esri-announces-las-compression/ ESRI Announces "Optimised LAS"]
# [http://www.lidarnews.com/content/view/10214 ESRI description of "Optimised LAS"]
# [http://lists.osgeo.org/pipermail/ica-osgeo-labs/2015-March/001225.html Discussion background on this topic at Geo for All list]

=References=

<references />

Live GIS GSoC 2015

2015-04-07T03:07:04Z

Wiki-Epifanio:

= OSGeo-Live Google Summer of Code ideas 2015 =

=Integration of geospatial OSS in educational notebooks=

[http://www.google-melange.com/gsoc/proposal/public/google/gsoc2015/massimo_di_stefano/5643440998055936 complete proposal]

==About==

OSGeo-Live is a self-contained bootable DVD, USB thumb drive or Virtual Machine based on Lubuntu, that allows you to try a wide variety of open source geospatial software without installing anything. It is composed entirely of free software, allowing it to be freely distributed, duplicated and passed around. It provides pre-configured applications for a range of geospatial use cases, including storage, publishing, viewing, analysis and manipulation of data. It also contains sample datasets and documentation.

This GSoC 2015 Idea will focus on the development of a cross-projects python library with the aim of bridging together the several software libraries already installed on the live through the use of the Jupyter notebook server [1] in a series of "topic-oriented" geospatial notebooks.

This work will not only include python libraries, but thanks to recently added support for different type of kernels, will support R, Octave Bash and more. Because it supports Bash, it is now possible to include in a notebook any command line tool installed on OSGeo-Live. Since one of the main goals of OSGeo-Live is for education, this will substantially improve the user experience in having access to many tools under the OSGeo umbrella. The OSGeo-Live user will learn how to bring all this software together as well as learn how to process geospatial data using other standard scientific tools for data exploration. Each notebook will guide the user on how to build new information from the dataset already available on the OSGeo-live disc.

The "topic-oriented" notebooks can include :
* I/O raster and vector data (import export between several formats, subsetting, sql query)
* raster vector reprojection
* access to web resources using OGC standard (WMS, WFS, WCS trough CSW catalogs)
* raster algebra (single array operation, filtering, band merge, band-ratio, time-series)
* satellite derived product (working with landsat, image enhancements, bande merge, pansharpening, mosaic .. )
* time series of gridded data
* intro to geostatistics
* simple web-gis products (publish result of processing in projects based on js library like openlayers, leaflet and similar)
...

Part of this idea is to develop a software library written in python, to simplify the usage of geospatial data inside the notebook. Providing wrapper function to assolve general tasks like I/O, Database connections, map display using gui widgets and rich text for data documentation and report building.

This idea integrates several projects such as GDAL, GRASS, OSSIM, R, OTB, Numpy, Scipy, Pandas, R, owslib, netcdf4-python, pycsw, openlayer/leaflet/cesium, qgis-browser, gmt, postgis, in addition to the python specific projects (e.g. fiona, shapely, geopandas, scikit-image, pysal, cartopy, iris, and more). Generally each library that has python bindings and or is accessible from the command line.
Part of this idea is to :

* Develop topic oriented geospatial notebooks as described above (topics TBD)
* implement a software library written in python, to simplify the usage of geospatial data inside the notebook. This library will provide helper function to work with geospatial data (e.g. general tasks like I/O, Database connections, map display using gui widgets and rich text for data documentation and report building) taking advantage of the api provided by Jupyter.
* Reorganize the way how python libraries are installed on the live by packaging, as .deb, each python project that is missing a proper debian package. Resulting deb can then be upload on the ubuntu gis repository (before approval to ubuntu/debian gis official repository, the packages can can be hosted on an ad-hoc OSgeo-Live debian repository in incubation state)
* Revisiting and upgrading existent OsGeo-Live Quickstart documentation for each project involved in this idea (the rst file format used by OSGeo-Live documentation can be generated on the fly by running notebooks in batch mode, this will integrate quickstart testing and document building in a single process, keeping the quickstarter (notebbok-enabled) up-to-date)

[1] http://jupyter.org/

== Student ==
* Massimo Di Stefano (@epifanio GitHub id)

== Willing to Mentor ==

* Cameron Shorter (@camerons GitHub id)
* Rich Signell (@rsignell-usgs GitHub id)
* Angelos Tzotsos (@kalxas GitHub id)

[[Category: Live-demo]]

https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015/massimo_di_stefano/5643440998055936

Live GIS GSoC 2015

2015-04-07T03:05:53Z

Wiki-Epifanio:

= OSGeo-Live Google Summer of Code ideas 2015 =

=Integration of geospatial OSS in educational notebooks=

[https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015/massimo_di_stefano/5643440998055936 complete proposal]

==About==

OSGeo-Live is a self-contained bootable DVD, USB thumb drive or Virtual Machine based on Lubuntu, that allows you to try a wide variety of open source geospatial software without installing anything. It is composed entirely of free software, allowing it to be freely distributed, duplicated and passed around. It provides pre-configured applications for a range of geospatial use cases, including storage, publishing, viewing, analysis and manipulation of data. It also contains sample datasets and documentation.

This GSoC 2015 Idea will focus on the development of a cross-projects python library with the aim of bridging together the several software libraries already installed on the live through the use of the Jupyter notebook server [1] in a series of "topic-oriented" geospatial notebooks.

This work will not only include python libraries, but thanks to recently added support for different type of kernels, will support R, Octave Bash and more. Because it supports Bash, it is now possible to include in a notebook any command line tool installed on OSGeo-Live. Since one of the main goals of OSGeo-Live is for education, this will substantially improve the user experience in having access to many tools under the OSGeo umbrella. The OSGeo-Live user will learn how to bring all this software together as well as learn how to process geospatial data using other standard scientific tools for data exploration. Each notebook will guide the user on how to build new information from the dataset already available on the OSGeo-live disc.

The "topic-oriented" notebooks can include :
* I/O raster and vector data (import export between several formats, subsetting, sql query)
* raster vector reprojection
* access to web resources using OGC standard (WMS, WFS, WCS trough CSW catalogs)
* raster algebra (single array operation, filtering, band merge, band-ratio, time-series)
* satellite derived product (working with landsat, image enhancements, bande merge, pansharpening, mosaic .. )
* time series of gridded data
* intro to geostatistics
* simple web-gis products (publish result of processing in projects based on js library like openlayers, leaflet and similar)
...

Part of this idea is to develop a software library written in python, to simplify the usage of geospatial data inside the notebook. Providing wrapper function to assolve general tasks like I/O, Database connections, map display using gui widgets and rich text for data documentation and report building.

This idea integrates several projects such as GDAL, GRASS, OSSIM, R, OTB, Numpy, Scipy, Pandas, R, owslib, netcdf4-python, pycsw, openlayer/leaflet/cesium, qgis-browser, gmt, postgis, in addition to the python specific projects (e.g. fiona, shapely, geopandas, scikit-image, pysal, cartopy, iris, and more). Generally each library that has python bindings and or is accessible from the command line.
Part of this idea is to :

* Develop topic oriented geospatial notebooks as described above (topics TBD)
* implement a software library written in python, to simplify the usage of geospatial data inside the notebook. This library will provide helper function to work with geospatial data (e.g. general tasks like I/O, Database connections, map display using gui widgets and rich text for data documentation and report building) taking advantage of the api provided by Jupyter.
* Reorganize the way how python libraries are installed on the live by packaging, as .deb, each python project that is missing a proper debian package. Resulting deb can then be upload on the ubuntu gis repository (before approval to ubuntu/debian gis official repository, the packages can can be hosted on an ad-hoc OSgeo-Live debian repository in incubation state)
* Revisiting and upgrading existent OsGeo-Live Quickstart documentation for each project involved in this idea (the rst file format used by OSGeo-Live documentation can be generated on the fly by running notebooks in batch mode, this will integrate quickstart testing and document building in a single process, keeping the quickstarter (notebbok-enabled) up-to-date)

[1] http://jupyter.org/

== Student ==
* Massimo Di Stefano (@epifanio GitHub id)

== Willing to Mentor ==

* Cameron Shorter (@camerons GitHub id)
* Rich Signell (@rsignell-usgs GitHub id)
* Angelos Tzotsos (@kalxas GitHub id)

[[Category: Live-demo]]

https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015/massimo_di_stefano/5643440998055936

Google Summer of Code 2015 Ideas

2015-03-21T09:48:30Z

Wiki-Epifanio: /* OSGeo Foundation member projects */

[[Image:GoogleSummer_2015logo.png|600px|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 2015]] 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]], [[Google Summer of Code 2013 Ideas|2013]] and [[Google Summer of Code 2014 Ideas|2014]].
-----

== OSGeo Google Summer of Code 2015 ==

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: check out the [[Google Summer of Code Recommendations for Students]] page. If you need more information on how to apply you can contact all the mentors via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])

* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.

* 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 2015]] wiki page.

== 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/2015 '''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_2015 '''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_2015_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.com/en/web/guest/products/gvsig-desktop Desktop]. The gvSIG project looks for students with Java or Python skills that want to develop new ideas on this software.

[[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:Logo_OTB.png|60px|right]]
* [http://wiki.orfeo-toolbox.org/index.php/Proposals_for_GSoC_2015 '''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.

[[Image:Mapserver.png|100px|right]]
* [http://wiki.osgeo.org/wiki/MapServer_2015_SOC_Ideas '''Mapserver''' SoC Ideas]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.

[[Image:Logo-istSOS.png|60px|right]]
* [http://sourceforge.net/p/istsos/wiki/GSoC%20ideas%202015/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] (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-geoserver-crop.png|50px|right]]
* [https://github.com/geoserver/geoserver/wiki/GSOC-Ideas GSOC Ideas]: [http://live.osgeo.org/en/overview/geoserver_overview.html '''GeoServer'''] is a web server that allows you to serve maps and data from a variety of formats to standard clients such as web browsers and desktop GIS applications. GeoServer works with the Open Geospatial Consortium (OGC) standards Web Feature Service (WFS), Web Coverage Service (WCS), Web Processing Service (WPS) and Web Map Service (WMS) standards.
:* The GeoServer team asks applicants to introduce themselves on the geoserver-devel list ( Communicating in public is a key success factor to open source development )

[[Image:Geotools-logo.png|50px|right]]
* [http://docs.codehaus.org/display/GEOTOOLS/Google+Summer+of+Code ''GSOC'']: [http://live.osgeo.org/en/overview/geotools_overview.html '''GeoTools'''] GeoTools is an open source Java library for working with geospatial data, including both data access, data structures, processing and a powerful rendering engine. GeoTools is a modular library used in a wide range of web service, command line tools and desktop applications.

[[Image:ZOO-Project-mini.png|right]]
* [http://zoo-project.org/trac/wiki/ZOO_SoC_Idea_2015 '''ZOO-Project''' Soc Ideas]: ZOO-Project is a WPS (Web Processing Service) open source project released under MIT/X-11 style license. It provides an OGC WPS compliant developer-friendly framework to create and chain WPS Web services.





[[Image:Osgeo-live.png|230px|right]]
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2015 '''Osgeo-Live''' SoC Ideas]: [http://live.osgeo.org/en/index.html OSGeo-Live] is a self-contained bootable DVD, USB thumb drive or Virtual Machine based on Lubuntu, that allows you to try a wide variety of open source geospatial software without installing anything. It is composed entirely of free software, allowing it to be freely distributed, duplicated and passed around. It provides pre-configured applications for a range of geospatial use cases, including storage, publishing, viewing, analysis and manipulation of data. It also contains sample datasets and documentation.

=== Guest projects ===

Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact [[User:Madi|Madi]] or Anne.

[[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-2015-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.

[[Image:logo-uDig.png|60px|right]]
* [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-Ideas-2015 '''JGrasstools''' and '''uDig''' Spatial Toolbox SoC Ideas]: The JGrasstools project is a geospatial modules library dedicated to hydrology and geomorphology. It is the base of the modules for uDig's Spatial Toolbox.

[[Image:otp-logo.png|80px|right]]
* [http://github.com/opentripplanner/OpenTripPlanner/wiki/2015-Google-Summer-of-Code-Ideas '''OpenTripPlanner''' Ideas]: [http://github.com/opentripplanner/OpenTripPlanner OpenTripPlanner] is an open source multi-modal trip planner. It depends on open data in open standard file formats (GTFS and OpenStreetMap), includes a REST API for journey planning, a map-based Javascript client, and an [http://github.com/CUTR-at-USF/OpenTripPlanner-for-Android/wiki Android App].









=== See also ===

Other like minded projects do not participate to GSoC under OSGeo umbrella, but with their own organization. You may want to visit also their page:

* [https://wiki.52north.org/bin/view/Projects/GSoC2015ProjectIdeas '''52°North''' Ideas]


* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2015/Project_Ideas '''OpenStreetMap''' Ideas]



=== Don't see in the list the project you're interested in? ===

Contact them in their developers mailing list! Feel free to propose your own idea and get feedback!

== I want to apply as a student ==

Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.

=== 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]]

=== Important dates ===

* [http://www.google-melange.com/gsoc/events/google/gsoc2015 '''The official timeline''']


* March 2nd: Google announces accepted organizations.
: Please start talking to the dev communities you are interested in ''now''.
* March 16: 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 27: Student application deadline.
* April 27: '''Accepted student proposals are announced and Community Bonding Period begins.'''
* May 25: '''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 26: Mid-term evaluation begins
* August 17-21: '''Pencils down!'''
* August 28: Final evaluations
* August 28: Students begin submitting required code samples to Google
* August 31: Final results announced

[Back to [[Google Summer of Code 2015]] @ OSGeo]
[[Category: Google Summer of Code]]

Google Summer of Code 2015 Ideas

2015-03-21T09:46:48Z

Wiki-Epifanio: /* OSGeo Foundation member projects */

[[Image:GoogleSummer_2015logo.png|600px|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 2015]] 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]], [[Google Summer of Code 2013 Ideas|2013]] and [[Google Summer of Code 2014 Ideas|2014]].
-----

== OSGeo Google Summer of Code 2015 ==

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: check out the [[Google Summer of Code Recommendations for Students]] page. If you need more information on how to apply you can contact all the mentors via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])

* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.

* 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 2015]] wiki page.

== 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/2015 '''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_2015 '''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_2015_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.com/en/web/guest/products/gvsig-desktop Desktop]. The gvSIG project looks for students with Java or Python skills that want to develop new ideas on this software.

[[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:Logo_OTB.png|60px|right]]
* [http://wiki.orfeo-toolbox.org/index.php/Proposals_for_GSoC_2015 '''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.

[[Image:Mapserver.png|100px|right]]
* [http://wiki.osgeo.org/wiki/MapServer_2015_SOC_Ideas '''Mapserver''' SoC Ideas]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.

[[Image:Logo-istSOS.png|60px|right]]
* [http://sourceforge.net/p/istsos/wiki/GSoC%20ideas%202015/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] (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-geoserver-crop.png|50px|right]]
* [https://github.com/geoserver/geoserver/wiki/GSOC-Ideas GSOC Ideas]: [http://live.osgeo.org/en/overview/geoserver_overview.html '''GeoServer'''] is a web server that allows you to serve maps and data from a variety of formats to standard clients such as web browsers and desktop GIS applications. GeoServer works with the Open Geospatial Consortium (OGC) standards Web Feature Service (WFS), Web Coverage Service (WCS), Web Processing Service (WPS) and Web Map Service (WMS) standards.
:* The GeoServer team asks applicants to introduce themselves on the geoserver-devel list ( Communicating in public is a key success factor to open source development )

[[Image:Geotools-logo.png|50px|right]]
* [http://docs.codehaus.org/display/GEOTOOLS/Google+Summer+of+Code ''GSOC'']: [http://live.osgeo.org/en/overview/geotools_overview.html '''GeoTools'''] GeoTools is an open source Java library for working with geospatial data, including both data access, data structures, processing and a powerful rendering engine. GeoTools is a modular library used in a wide range of web service, command line tools and desktop applications.

[[Image:ZOO-Project-mini.png|right]]
* [http://zoo-project.org/trac/wiki/ZOO_SoC_Idea_2015 '''ZOO-Project''' Soc Ideas]: ZOO-Project is a WPS (Web Processing Service) open source project released under MIT/X-11 style license. It provides an OGC WPS compliant developer-friendly framework to create and chain WPS Web services.





[[Image:Osgeo-live.png|230px|right]]
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2015 '''Osgeo-:ive''' Soc Ideas]: [http://live.osgeo.org/en/index.html OSGeo-Live] is a self-contained bootable DVD, USB thumb drive or Virtual Machine based on Lubuntu, that allows you to try a wide variety of open source geospatial software without installing anything. It is composed entirely of free software, allowing it to be freely distributed, duplicated and passed around. It provides pre-configured applications for a range of geospatial use cases, including storage, publishing, viewing, analysis and manipulation of data. It also contains sample datasets and documentation.

=== Guest projects ===

Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact [[User:Madi|Madi]] or Anne.

[[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-2015-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.

[[Image:logo-uDig.png|60px|right]]
* [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-Ideas-2015 '''JGrasstools''' and '''uDig''' Spatial Toolbox SoC Ideas]: The JGrasstools project is a geospatial modules library dedicated to hydrology and geomorphology. It is the base of the modules for uDig's Spatial Toolbox.

[[Image:otp-logo.png|80px|right]]
* [http://github.com/opentripplanner/OpenTripPlanner/wiki/2015-Google-Summer-of-Code-Ideas '''OpenTripPlanner''' Ideas]: [http://github.com/opentripplanner/OpenTripPlanner OpenTripPlanner] is an open source multi-modal trip planner. It depends on open data in open standard file formats (GTFS and OpenStreetMap), includes a REST API for journey planning, a map-based Javascript client, and an [http://github.com/CUTR-at-USF/OpenTripPlanner-for-Android/wiki Android App].









=== See also ===

Other like minded projects do not participate to GSoC under OSGeo umbrella, but with their own organization. You may want to visit also their page:

* [https://wiki.52north.org/bin/view/Projects/GSoC2015ProjectIdeas '''52°North''' Ideas]


* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2015/Project_Ideas '''OpenStreetMap''' Ideas]



=== Don't see in the list the project you're interested in? ===

Contact them in their developers mailing list! Feel free to propose your own idea and get feedback!

== I want to apply as a student ==

Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.

=== 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]]

=== Important dates ===

* [http://www.google-melange.com/gsoc/events/google/gsoc2015 '''The official timeline''']


* March 2nd: Google announces accepted organizations.
: Please start talking to the dev communities you are interested in ''now''.
* March 16: 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 27: Student application deadline.
* April 27: '''Accepted student proposals are announced and Community Bonding Period begins.'''
* May 25: '''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 26: Mid-term evaluation begins
* August 17-21: '''Pencils down!'''
* August 28: Final evaluations
* August 28: Students begin submitting required code samples to Google
* August 31: Final results announced

[Back to [[Google Summer of Code 2015]] @ OSGeo]
[[Category: Google Summer of Code]]

Google Summer of Code 2015 Ideas

2015-03-21T09:40:24Z

Wiki-Epifanio: /* OSGeo Foundation member projects */

[[Image:GoogleSummer_2015logo.png|600px|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 2015]] 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]], [[Google Summer of Code 2013 Ideas|2013]] and [[Google Summer of Code 2014 Ideas|2014]].
-----

== OSGeo Google Summer of Code 2015 ==

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: check out the [[Google Summer of Code Recommendations for Students]] page. If you need more information on how to apply you can contact all the mentors via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])

* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.

* 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 2015]] wiki page.

== 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/2015 '''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_2015 '''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_2015_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.com/en/web/guest/products/gvsig-desktop Desktop]. The gvSIG project looks for students with Java or Python skills that want to develop new ideas on this software.

[[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:Logo_OTB.png|60px|right]]
* [http://wiki.orfeo-toolbox.org/index.php/Proposals_for_GSoC_2015 '''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.

[[Image:Mapserver.png|100px|right]]
* [http://wiki.osgeo.org/wiki/MapServer_2015_SOC_Ideas '''Mapserver''' SoC Ideas]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.

[[Image:Logo-istSOS.png|60px|right]]
* [http://sourceforge.net/p/istsos/wiki/GSoC%20ideas%202015/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] (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-geoserver-crop.png|50px|right]]
* [https://github.com/geoserver/geoserver/wiki/GSOC-Ideas GSOC Ideas]: [http://live.osgeo.org/en/overview/geoserver_overview.html '''GeoServer'''] is a web server that allows you to serve maps and data from a variety of formats to standard clients such as web browsers and desktop GIS applications. GeoServer works with the Open Geospatial Consortium (OGC) standards Web Feature Service (WFS), Web Coverage Service (WCS), Web Processing Service (WPS) and Web Map Service (WMS) standards.
:* The GeoServer team asks applicants to introduce themselves on the geoserver-devel list ( Communicating in public is a key success factor to open source development )

[[Image:Geotools-logo.png|50px|right]]
* [http://docs.codehaus.org/display/GEOTOOLS/Google+Summer+of+Code ''GSOC'']: [http://live.osgeo.org/en/overview/geotools_overview.html '''GeoTools'''] GeoTools is an open source Java library for working with geospatial data, including both data access, data structures, processing and a powerful rendering engine. GeoTools is a modular library used in a wide range of web service, command line tools and desktop applications.

[[Image:ZOO-Project-mini.png|right]]
* [http://zoo-project.org/trac/wiki/ZOO_SoC_Idea_2015 '''ZOO-Project''' Soc Ideas]: ZOO-Project is a WPS (Web Processing Service) open source project released under MIT/X-11 style license. It provides an OGC WPS compliant developer-friendly framework to create and chain WPS Web services.





[[Image:Osgeo-live.png|230px|right]]
* [http://zoo-project.org/trac/wiki/ZOO_SoC_Idea_2015 '''ZOO-Project''' Soc Ideas]: ZOO-Project is a WPS (Web Processing Service) open source project released under MIT/X-11 style license. It provides an OGC WPS compliant developer-friendly framework to create and chain WPS Web services.

=== Guest projects ===

Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact [[User:Madi|Madi]] or Anne.

[[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-2015-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.

[[Image:logo-uDig.png|60px|right]]
* [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-Ideas-2015 '''JGrasstools''' and '''uDig''' Spatial Toolbox SoC Ideas]: The JGrasstools project is a geospatial modules library dedicated to hydrology and geomorphology. It is the base of the modules for uDig's Spatial Toolbox.

[[Image:otp-logo.png|80px|right]]
* [http://github.com/opentripplanner/OpenTripPlanner/wiki/2015-Google-Summer-of-Code-Ideas '''OpenTripPlanner''' Ideas]: [http://github.com/opentripplanner/OpenTripPlanner OpenTripPlanner] is an open source multi-modal trip planner. It depends on open data in open standard file formats (GTFS and OpenStreetMap), includes a REST API for journey planning, a map-based Javascript client, and an [http://github.com/CUTR-at-USF/OpenTripPlanner-for-Android/wiki Android App].









=== See also ===

Other like minded projects do not participate to GSoC under OSGeo umbrella, but with their own organization. You may want to visit also their page:

* [https://wiki.52north.org/bin/view/Projects/GSoC2015ProjectIdeas '''52°North''' Ideas]


* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2015/Project_Ideas '''OpenStreetMap''' Ideas]



=== Don't see in the list the project you're interested in? ===

Contact them in their developers mailing list! Feel free to propose your own idea and get feedback!

== I want to apply as a student ==

Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.

=== 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]]

=== Important dates ===

* [http://www.google-melange.com/gsoc/events/google/gsoc2015 '''The official timeline''']


* March 2nd: Google announces accepted organizations.
: Please start talking to the dev communities you are interested in ''now''.
* March 16: 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 27: Student application deadline.
* April 27: '''Accepted student proposals are announced and Community Bonding Period begins.'''
* May 25: '''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 26: Mid-term evaluation begins
* August 17-21: '''Pencils down!'''
* August 28: Final evaluations
* August 28: Students begin submitting required code samples to Google
* August 31: Final results announced

[Back to [[Google Summer of Code 2015]] @ OSGeo]
[[Category: Google Summer of Code]]

Live GIS Disc

2015-03-19T13:40:50Z

Wiki-Epifanio: /* Google Summer of Code */

= 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

== Want to help? ==
We love volunteers, and would love to hear from you if you would like to help out. Here are some ideas about things that you might want to help with:
; Translations: Know another language? Why not join our team of translators:
: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Translate

; Testing:
; Quickstarts:
; Debian Packaging:

== 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=19&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]]
* Twitter [https://twitter.com/osgeolive @osgeolive]

== 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 July 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
* 8 August 2014, [[Live GIS Disc Press Release 53]] - Final OSGeo-Live 8.0 testing sprint
* 25 August 2014, [[Live GIS Disc Press Release 54]] - '''OSGeo-Live 8.0 released'''
* 10 November 2014, [[Live GIS Disc Press Release 55]] - Starting build cycle for OSGeo-Live 8.5
* 1 February 2015, [[Live GIS Disc Press Release 56]] - One week to translate OSGeo-Live 8.5 Documentation
* 2 February 2015, [[Live GIS Disc Press Release 57]] - Final OSGeo-Live 8.5 testing sprint
* 22 February 2015, [[Live GIS Disc Press Release 58]] - '''OSGeo-Live 8.5 released'''

=== Twitter ===
We also announce press releases on twitter.

* Major Builds
* Calls for Testing
* Calls for Translation
* Retweets of events featuring OSGeo-Live

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

== Testimonials ==
[[Live GIS Testimonials]]

== 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]]
* [[Live GIS GSoC 2015]]
* [https://github.com/hotosm/HOT-Project-Ideas/issues/15 Cross project OSGeo-Live and HOT in GSoC 2015]

== OSGeo Incubation ==

* [[ Live GIS Incubation Graduation Checklist ]]

= 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)
* [http://imincik.github.io/gis-lab/ GIS.lab] - Automatic deployment of GIS infrastructure

= 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 GSoC 2015

2015-03-19T05:51:21Z

Wiki-Epifanio: /* Willing to Mentor */

= OSGeo-Live Google Summer of Code ideas 2015 =

=Integration of geospatial OSS in educational notebooks=

==About==

OSGeo-Live is a self-contained bootable DVD, USB thumb drive or Virtual Machine based on Lubuntu, that allows you to try a wide variety of open source geospatial software without installing anything. It is composed entirely of free software, allowing it to be freely distributed, duplicated and passed around. It provides pre-configured applications for a range of geospatial use cases, including storage, publishing, viewing, analysis and manipulation of data. It also contains sample datasets and documentation.

This GSoC 2015 Idea will focus on the development of a cross-projects python library with the aim of bridging together the several software libraries already installed on the live through the use of the Jupyter notebook server [1] in a series of "topic-oriented" geospatial notebooks.

This work will not only include python libraries, but thanks to recently added support for different type of kernels, will support R, Octave Bash and more. Because it supports Bash, it is now possible to include in a notebook any command line tool installed on OSGeo-Live. Since one of the main goals of OSGeo-Live is for education, this will substantially improve the user experience in having access to many tools under the OSGeo umbrella. The OSGeo-Live user will learn how to bring all this software together as well as learn how to process geospatial data using other standard scientific tools for data exploration. Each notebook will guide the user on how to build new information from the dataset already available on the OSGeo-live disc.

The "topic-oriented" notebooks can include :
* I/O raster and vector data (import export between several formats, subsetting, sql query)
* raster vector reprojection
* access to web resources using OGC standard (WMS, WFS, WCS trough CSW catalogs)
* raster algebra (single array operation, filtering, band merge, band-ratio, time-series)
* satellite derived product (working with landsat, image enhancements, bande merge, pansharpening, mosaic .. )
* time series of gridded data
* intro to geostatistics
* simple web-gis products (publish result of processing in projects based on js library like openlayers, leaflet and similar)
...

Part of this idea is to develop a software library written in python, to simplify the usage of geospatial data inside the notebook. Providing wrapper function to assolve general tasks like I/O, Database connections, map display using gui widgets and rich text for data documentation and report building.

This idea integrates several projects such as GDAL, GRASS, OSSIM, R, OTB, Numpy, Scipy, Pandas, R, owslib, netcdf4-python, pycsw, openlayer/leaflet/cesium, qgis-browser, gmt, postgis, in addition to the python specific projects (e.g. fiona, shapely, geopandas, scikit-image, pysal, cartopy, iris, and more). Generally each library that has python bindings and or is accessible from the command line.
Part of this idea is to :

* Develop topic oriented geospatial notebooks as described above (topics TBD)
* implement a software library written in python, to simplify the usage of geospatial data inside the notebook. This library will provide helper function to work with geospatial data (e.g. general tasks like I/O, Database connections, map display using gui widgets and rich text for data documentation and report building) taking advantage of the api provided by Jupyter.
* Reorganize the way how python libraries are installed on the live by packaging, as .deb, each python project that is missing a proper debian package. Resulting deb can then be upload on the ubuntu gis repository (before approval to ubuntu/debian gis official repository, the packages can can be hosted on an ad-hoc OSgeo-Live debian repository in incubation state)
* Revisiting and upgrading existent OsGeo-Live Quickstart documentation for each project involved in this idea (the rst file format used by OSGeo-Live documentation can be generated on the fly by running notebooks in batch mode, this will integrate quickstart testing and document building in a single process, keeping the quickstarter (notebbok-enabled) up-to-date)

[1] http://jupyter.org/

== Student ==
* Massimo Di Stefano (@epifanio GitHub id)

== Willing to Mentor ==

* Cameron Shorter (@camerons GitHub id)
* Rich Signell (@rsignell-usgs GitHub id)
* Angelos Tzotsos (@kalxas GitHub id)

[[Category: Live-demo]]

Live GIS GSoC 2015

2015-03-18T03:48:36Z

Wiki-Epifanio: /* Willing to Mentor */

= OSGeo-Live Google Summer of Code ideas 2015 =

=Integration of geospatial OSS in educational notebooks=

==About==

OSGeo-Live is a self-contained bootable DVD, USB thumb drive or Virtual Machine based on Lubuntu, that allows you to try a wide variety of open source geospatial software without installing anything. It is composed entirely of free software, allowing it to be freely distributed, duplicated and passed around. It provides pre-configured applications for a range of geospatial use cases, including storage, publishing, viewing, analysis and manipulation of data. It also contains sample datasets and documentation.

This GSoC 2015 Idea will focus on the development of a cross-projects python library with the aim of bridging together the several software libraries already installed on the live through the use of the Jupyter notebook server [1] in a series of "topic-oriented" geospatial notebooks.

This work will not only include python libraries, but thanks to recently added support for different type of kernels, will support R, Octave Bash and more. Because it supports Bash, it is now possible to include in a notebook any command line tool installed on OSGeo-Live. Since one of the main goals of OSGeo-Live is for education, this will substantially improve the user experience in having access to many tools under the OSGeo umbrella. The OSGeo-Live user will learn how to bring all this software together as well as learn how to process geospatial data using other standard scientific tools for data exploration. Each notebook will guide the user on how to build new information from the dataset already available on the OSGeo-live disc.

The "topic-oriented" notebooks can include :
* I/O raster and vector data (import export between several formats, subsetting, sql query)
* raster vector reprojection
* access to web resources using OGC standard (WMS, WFS, WCS trough CSW catalogs)
* raster algebra (single array operation, filtering, band merge, band-ratio, time-series)
* satellite derived product (working with landsat, image enhancements, bande merge, pansharpening, mosaic .. )
* time series of gridded data
* intro to geostatistics
* simple web-gis products (publish result of processing in projects based on js library like openlayers, leaflet and similar)
...

Part of this idea is to develop a software library written in python, to simplify the usage of geospatial data inside the notebook. Providing wrapper function to assolve general tasks like I/O, Database connections, map display using gui widgets and rich text for data documentation and report building.

This idea integrates several projects such as GDAL, GRASS, OSSIM, R, OTB, Numpy, Scipy, Pandas, R, owslib, netcdf4-python, pycsw, openlayer/leaflet/cesium, qgis-browser, gmt, postgis, in addition to the python specific projects (e.g. fiona, shapely, geopandas, scikit-image, pysal, cartopy, iris, and more). Generally each library that has python bindings and or is accessible from the command line.
Part of this idea is to :

* Develop topic oriented geospatial notebooks as described above (topics TBD)
* implement a software library written in python, to simplify the usage of geospatial data inside the notebook. This library will provide helper function to work with geospatial data (e.g. general tasks like I/O, Database connections, map display using gui widgets and rich text for data documentation and report building) taking advantage of the api provided by Jupyter.
* Reorganize the way how python libraries are installed on the live by packaging, as .deb, each python project that is missing a proper debian package. Resulting deb can then be upload on the ubuntu gis repository (before approval to ubuntu/debian gis official repository, the packages can can be hosted on an ad-hoc OSgeo-Live debian repository in incubation state)
* Revisiting and upgrading existent OsGeo-Live Quickstart documentation for each project involved in this idea (the rst file format used by OSGeo-Live documentation can be generated on the fly by running notebooks in batch mode, this will integrate quickstart testing and document building in a single process, keeping the quickstarter (notebbok-enabled) up-to-date)

[1] http://jupyter.org/

== Student ==
* Massimo Di Stefano (@epifanio GitHub id)

== Willing to Mentor ==

* Cameron Shorter (@rsignell-usgs GitHub id)
* Rich Signell (@kalxas GitHub id)
* Angelos Tzotsos (@kalxas GitHub id)

[[Category: Live-demo]]