GRASS Community Sprint Bonn 2016: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
m (Updated activities)
m (Updated activity)
Line 300: Line 300:


=== Nikos ===
=== Nikos ===
===== Done =====


* CRO related tasks
* CRO related tasks
* Patched [https://trac.osgeo.org/grass/changeset/69012/grass/trunk/imagery/i.atcorr/create_iwave.py create_iwave.py], see {{trac|3027}} -- mentored by Moritz. | Scratching a new version for it -- vision: one Class to rule them all.
* Patched [https://trac.osgeo.org/grass/changeset/69012/grass/trunk/imagery/i.atcorr/create_iwave.py create_iwave.py], see {{trac|3027}} -- mentored by Moritz.  
* Working on {{Cmd|i.rgb.his}} and {{Cmd|i.his.rgb}} to allow for 16-bit input data (DCELL?) -- see latest diff(s) in {{trac|774}}!
* Rewrote {{Cmd|i.rgb.his}} to allow for 16-bit input data -- need to test more though.
* Corrected erroneous function in {{AddonCmd|i.landsat8.swlst}} -- thanks to Stefan Blumentrath!
 
===== On-Going =====
 
* Rewrite: {{Cmd|i.his.rgb}} -- see {{trac|774}}!
 
===== Ideas =====
 
* Scratching a new version for `create_iwave.py` -- vision: one Class to rule them all.
* Reviewing options to fuse {{Cmd|i.pansharpen}} with/into {{AddonCmd|i.fusion.hpf}}
* Reviewing options to fuse {{Cmd|i.pansharpen}} with/into {{AddonCmd|i.fusion.hpf}}


[[Category: Workshops]]
[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: Code Sprint]]
[[Category: 2016]]
[[Category: 2016]]

Revision as of 21:50, 27 August 2016

During the FOSS4G 2016 , 21-28 August 2016, Bonn, Germany, the GRASS GIS project will join the code sprint

Important dates:

  • CodeSprint I: Sun 21.08.2016 12:00 - Tue 23.08.2016 (open end) (see also here)
  • FOSS4G 2016 Schedule
  • CodeSprint II: Sat 27.08.2016 - Sun 28.08.2016 12:00 p.m. (see also here)

Purpose

Get together of GRASS GIS project members to take decisions and tackle small and larger problems.

For this meeting, we welcome people committed to improving the GRASS GIS project. This includes developers, documenters, bug reporters, translators, and users!

Sponsors

If you are interested to sponsor the GRASS Community Sprint, please read about
    sponsoring the GRASS project at http://grass.osgeo.org/donations/
and, if needed, contact Markus Neteler <neteler at osgeo.org>. Any surplus at the end of the event will be turned over to the GRASS GIS project.

The GRASS Community Sprint is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet in Bonn. The community sprint is an important opportunity for the GRASS developers to discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. Please see below for the more detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community sprint will be directly contributed back into the GRASS project to the benefit of everyone who uses it.

Thanks to our sponsors

Venue

Bonn, Germany: Basecamp

How to get to FOSS4G2016 OSGeo Code Sprint?

By train

By Car

  • Coming from the highway A59 Basecamp is located at the end of the highway A562. For navigation systems it is best to type Basecamp's address: "In der Raste 3, 53129 Bonn")

Accommodation and Costs

  • to be defined

Weather

Agenda - What we plan to do

Note: The program is generally open for your ideas. Please edit this wiki page!

More core developers with SVN write access

  • Develop a strategy to refresh the group with core SVN write access

Web site

Promo

  • Finalize the new GRASS GIS flyer prepared by Vincent Bain
    • needed: catchy time series screenshot

New Releases

Minor releases:

Major release:

Documentation and translation

  • Add examples to manual pages
  • Add examples to Wiki pages
    • GRASS-R/R-GRASS handling of raster time series
    • Sentinel-2 processing
  • Translation of messages
  • Translation of Wiki pages

Source code Quality Assessment

Bug squashing

Testing

Please test in GRASS 7.2.svn!

Improvements

  • improve r.modis addons
  • integrate Google Summer of Code projects (where adequate)
  • continue working on OBIA toolchain:
  • add R-batch files to OSGeo4W-winGRASS7 see osgeo4w/ticket 413
  • GUI: Implement an optional session "kickstart" in GRASS with LatLong predefined, then open import wizard | switch projection inside (like most other GIS do!)
  • TGRASS:
    • suffix option for output mapnames in t.rast.mapcalc and t.rast.algebra (tickets #2294 and #2736)
    • pattern option to list and remove space-time data sets (ticket #2804)
    • t.rast.what: input file with coordinates (ticket #2721)
    • t.remove: dual step removal (ticket #2752)
    • support for space-time datasets in g.gui.gmodeler (ticket #2977)

Better integration of git into development

... YOUR IDEA HERE ...

Planned participation

For organizational reasons, please additionally register at: https://wiki.osgeo.org/wiki/FOSS4G_2016_Code_Sprint

In person

Please add your name here or contact Luca Delucchi <lucadeluge at gmail com>:

No Participant Country Arrival Departure Topic T-Shirt Notes
1 Luca Delucchi Italy August 21 August 28 L
2 Martin Landa Czech Republic August 21 August 28 L
3 Markus Neteler Italy August 21 August 28 Releases, project coordination, bug hunting, getting more ppl involved M
4 Nikos Alexandris Switzerland August 21 August 28 CRO, create_iwave.py, i.[rgb|his].[his|rgb] S or M
5 Veronica Andreo Argentina August 26 August 28 S
6 Moritz Lennert Belgium August 21 August 27 Releases, OBIA toolchain, GSoC module integration M
7 Stefan Blumentrath Norway August 26 August 28 Port some Addons to python? (or whatever you put me up to) L
8 Milena Nowotarska Poland August 21 August 28 M
9 Anna Zanchetta Italy - Israel August 22 August 27 Implementing and improving some imagery modules, inshallah S

Via IRC chat

(IRC is a nice archaic chat system, see IRC)

No Participant Country
1 Yann Chemin France
2 Helmut Kudrnovsky Austria

Individual Preparation

Photos

We have to remember to take at least one group photo! :-)

FAQ

  • Is the GRASS Community Sprint just a coding event?
    • It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project.
    • On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software
  • Is the GRASS Community Sprint for developers only?
    • No: anybody can help, with testing, checking out bugs and fixes, documentation and more.
  • Where can I get help and more information about the community sprint?

Participants and Reports

Moritz

  • OBIA Toolchain
    • Cleaned up r.object.geometry and moved it to addons r69187 + r69188, r.object.geometry
    • Modified i.segment.stats to user.object.geometry instead of v.to.db
    • Improved error handling in i.segment.stats and use temporary files on disk to reduce memory use
    • Modified i.segment.uspo to also allow testing new mean shift algorithm (currently only available in sandbox) r69236
    • Tested mean shift algorithm
  • Working on 6.4.6 release
    • General bug triaging
    • Backported fix of trac #1444 to release_64
    • Backported fix of trac #2558 to release_64
  • Scratched an old itch and implement a flag in g.region to allow shell style output in flat (one line) style r69240

Markus

  • assist CRO in cleaning PSC election voter email addresses
  • minor pseudo-mercator discussions
  • major datum shift file discussions with Even Rouault (GDAL) and fellow GRASS sprinters: libproj cleanup of local copies of NAD and datum shift files which are indeed used from GDAL; extended documentation in README.txt (trac #2456, r2456)

Anna Petrasova

Martin Landa

Vero

  • Tutorial: R-GRASS integration for raster time series handling/processing. Work in progress.

Nikos

Done
On-Going
Ideas
  • Scratching a new version for `create_iwave.py` -- vision: one Class to rule them all.
  • Reviewing options to fuse i.pansharpen with/into i.fusion.hpf