GRASS-Wiki - User contributions [en]

GRASS-Wiki/it

2017-08-02T18:56:51Z

⚠️MilenaN: small update

__NOTOC__
{| width="100%"
|-
| width="68%" style="vertical-align:top" |
<div style="margin:0; margin-right:10px; border:1px solid #dfdfdf; background-color:#f8f8ff;">

<div style="padding:0.3em 1em 0.7em 1em;">

[[Image:grasslogo_vector_small.png|right|link=http://grass.osgeo.org]]

=== Benvenuti nel Wiki degli utenti di GRASS GIS ===

{{website|documentation/general-overview|'''GRASS GIS'''}} è un [http://en.wikipedia.org/wiki/Geographic_information_system Sistema informativo geografico] utilizzato per la gestione dei dati geospaziali e di analisi, elaborazione di immagini, grafica e produzione di mappe, modellazione spaziale, e visualizzazione.

Su questo Wiki si possono ottenere e fornire informazioni relative a GRASS, documenti e programmi aggiuntivi forniti dagli utenti. Per modificare le pagine del wiki bisogna essere registrati ed eseguire l'accesso (si veda il collegamento in alto a destra).

Per una rapida sintesi di GRASS si veda [[core features|caratteristiche principali]]. Per vedere alcuni esempi, consultare la [http://grass.osgeo.org/screenshots Galleria di GRASS GIS] e [[Applications|Applicazioni]].
</div>
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#FFE5E5;">
'''Cosa bolle in pentola:'''
* <font size="+2">[http://trac.osgeo.org/grass/wiki/Release/7.2.1-News '''GRASS GIS 7.2.1''' è arrivato!]</font> {{bullet}} [http://grass.osgeo.org/download download] {{bullet}} [https://trac.osgeo.org/grass/report/16 segnalare qualsiasi problema]
* Ora: [[GRASS SoC Ideas 2013|Google Summer of Code 2013]]
* In corso: [http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures Elenco di nuove funzionalità in GRASS GIS 7] (date una mano per [http://grass.osgeo.org/download/software/#g72x testarle])
* Completato: [[GRASS Community Sprint Paris 2017]]
* Prova il [[Quick wxGUI tutorial|breve tutorial di wxGUI]]
* Supporto per i dati temporali e altre nuove [[Initiatives|Iniziative]]
* [[Cartography#Display_monitors|Nuove scale grafiche e indicatori del nord]]
</div>

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

==== Documentazione e supporto per gli utenti ====
* [[GRASS Help/it|GRASS Help e iniziare a lavorare con GRASS]]
* [[GRASS Documents|Documentazione approfondita di GRASS]]
* [[Installation Guide|Guida d'installazione]] per l'installer di GRASS
* [[Faq|FAQ]]: domande frequenti
* [[wxGUI]] - Interfaccia grafica scritta in wxPython
</div>

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

==== Comunità ====
* [[GRASS Community|Comunità di GRASS]]: contattare la comunità
* [[Applications|Applicazioni]]: impieghi di GRASS nei vari settori
* [[GRASS migration hints|Migrare a GRASS]]
* [[GRASS Blogger]]
* Coinvolgiti nel progetto: [[Project jobs]]
* [http://grass.osgeo.org/wiki/Special:Recentchanges?feed=rss RSS feed] dei cambiamenti recenti a questo Wiki
</div>

<div>Consulta la mappa mondiale degli utenti di GRASS GIS [http://grass.osgeo.org/community/ GRASS GIS User Online]. Se usi GRASS GIS, per cortesia inserisci qui i tuoi dati.
</div>

<div><p>''[[GRASS-Wiki:Language policy/it|Traduci questo Wiki]]''</p></div>


| width="38%" style="vertical-align:top" |
<div style="margin:0; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#f8f8ff;">
[[Image:OSGeo 220pix.png|center|220px|link=http://www.osgeo.org]]
<center>[http://www.osgeo.org OSGeo] Foundation Project</center>
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:1em 1em 1em 1em; background-color:#f8f8ff;">
[[Image:Btn_donate_SM.gif|center|link=http://grass.osgeo.org/donation.php]]
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#f8f8ff;">
* [http://grass.osgeo.org/screenshots/index.php Galleria di GRASS GIS]
* [http://trac.osgeo.org SVN/trac] Repository del codice sorgente
* [http://grass.osgeo.org/community/support.php Mailing lists] e [http://grass.osgeo.org/community/support.php#irc IRC]
* [http://trac.osgeo.org/grass/ Segnalazione di errori]
* [https://svn.osgeo.org/grass/grass/branches/releasebranch_6_4/COPYING Rilasciato con licenza GNU GPL]
</div>

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

==== Download ====
* [http://grass.osgeo.org/download/ Codice sorgente e binari]
* [[GRASS AddOns|Moduli aggiuntivi di GRASS]]
* [[Promotional material|Materiale promozionale]]
* [[Sample datasets|Dataset di esempio]]
* [[Global datasets]]
</div>

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

==== Sviluppo ====
* [[Compile and Install|Compilazione e Installazione]] del codice sorgente
* [[Development|Intro Sviluppo di GRASS]]
* [http://trac.osgeo.org/grass/wiki GRASS-trac]: Wiki degli sviluppatori, bugtracker, browser codice sorgente
* [[Release Roadmap]]
* [[GRASS 7 ideas collection|Raccolta idee per GRASS 7]]
* [[GRASS SoC Ideas|Raccolta idee per Google Summer of Code]]
* [http://trac.osgeo.org/grass/wiki/HowToContribute Come contribuire a GRASS] (accesso in scrittura etc.)
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#f8f8ff;">
Project Metrics tramite [http://www.ohloh.net/projects/3666 Ohloh].
{{#widget:Ohloh Project|id=3666|type=partner_badge}}
</div>
|}

[[Category:Languages/it]]

GRASS-Wiki/pl

2017-08-02T18:49:37Z

⚠️MilenaN: small update

__NOTOC__
{| width="100%"
|-
| width="68%" style="vertical-align:top" |
<div style="margin:0; margin-right:10px; border:1px solid #dfdfdf; background-color:#f8f8ff;">

<div style="padding:0.3em 1em 0.7em 1em;">

[[Image:grasslogo_vector_small.png|right]]

=== Witaj w Wiki użytkowników GRASS GIS ===

[http://grass.osgeo.org Geographic Resources Analysis Support System], zwykle zwany '''GRASS-em''',
jest Systemem Informacji Geograficznej ([http://en.wikipedia.org/wiki/Geographic_information_system GIS]) wykorzystywanym do zarządzania i analiz danych przestrzennych, przetwarzania obrazów satelitarnych i zdjęć lotniczych, produkcji prezentacji graficznych oraz map, modelowania przestrzennego i wizualizacji. GRASS jest obecnie używany przez środowiska akademickie i komercyjne na całym śwecie, jak i przez wiele agencji rządowych i firm zajmujących się stanem środowiska naturalnego. GRASS GIS jest projektem [http://www.osgeo.org Open Source Geospatial Foundation]. <br>
Ta WIKI stanowi oficjalną stronę społeczności użytkowników projektu GRASS GIS. Aby zobaczyć przykłady analiz, idź do [http://grass.osgeo.org/screenshots/index.php Galerii GRASS GIS].

Na tej Wiki możesz znaleźć informacje o GRASS-ie, dokumenty oraz dodatkowe programy związane z projektem, a także rozbudowywać je. Aby móc edytować Wiki, zaloguj się - link w prawym górnym rogu.
</div>
</div>
<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#FFE5E5;">

'''Gorący temat:'''
* <font size="+1">[http://trac.osgeo.org/grass/wiki/Release/7.2.1-News '''GRASS GIS 7.2.1''' już jest!]</font> {{bullet}} [https://grass.osgeo.org/download/software/#g72x pobierz] {{bullet}} [https://trac.osgeo.org/grass/report/19 zgłoś problem]
* <font size="+1">[[GRASS Community Sprint Paris 2017]]</font>
* [http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures Lista nowych funkcji w GRASS GIS 7] ([https://grass.osgeo.org/download/software/#g72x pomóż nam testować])
* <font size="+0">[https://grass.osgeo.org/news/58/15/GRASS-GIS-6-4-6-released/ '''GRASS GIS 6.4.6''' is here!]</font> {{bullet}} [https://grass.osgeo.org/download pobierz] {{bullet}} [https://trac.osgeo.org/grass/report/16 zgłoś problem]

* Wypróbuj [[Quick wxGUI tutorial]]
* Temporal support i inne nowe[[Initiatives| Inicjatywy]]
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em
1em 1em 1em; background-color:#f8f8ff;">
==== Dokumentacja i pomoc dla użytkowników ====
* [[GRASS Help|Pomoc GRASS-a i Jak Zacząć]]
* [[GRASS Documents|Szczegółowa dokumentacja GRASS-a]]
* [[Installation Guide|Przewodnik instalacji]] prekompilowanych pakietów binarnych
* [[Faq|FAQ]]
* [[Applications|Zastosowania]] - przykłady użycia GRASS w różnych dyscyplinach
* [[wxGUI]] - Graficzny Interfejs Użytkownika w wxPython'ie
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em

1em 1em 1em; background-color:#f8f8ff;">

==== Społeczność====
* [[GRASS Community|Społeczność GRASS-a]]: Bądź w kontakcie
* [[Applications|Research applications]]: Co inni robią w GRASS-ie
* [[GRASS migration hints|Przejście na System GRASS]]
* [[GRASS Blogger]]
* Zaangażuj się: [[Project jobs|Prace przy projekcie]]
* [http://grass.osgeo.org/wiki/Special:Recentchanges?feed=rss RSS feed] ostatnie zmiany tej Wiki
</div>

<div>Zerknij na mapę użytkowników GRASS GIS na świecie [http://grass.osgeo.org/community/ GRASS GIS User Online]. Jeśli używasz GRASS GIS, dopisz się do mapy.
</div>

<div><p>''[[GRASS-Wiki:Language policy|Przetłumacz tę Wiki]]''</p></div>


| width="38%" style="vertical-align:top" |
<div style="margin:0; border:1px solid #dfdfdf; padding:0em 1em 1em 1em;

background-color:#f8f8ff;">
[[Image:OSGeo 220pix.png|center|220px]]
<center>Projekt Fundacji OSGeo</center>
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:1em 1em 1em 1em; background-color:#f8f8ff;">
[[Image:Btn_donate_SM.gif|center|link=http://grass.osgeo.org/donation.php]]<center>[http://grass.osgeo.org/donation.php Donate via PayPal.com]</center>
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding: 0em 1em 1em 1em;

background-color:#f8f8ff;">
* [http://grass.osgeo.org/screenshots/index.php Galeria Systemu GRASS]
* [http://trac.osgeo.org SVN/trac] Repozytorium Kodu Źródłowego
* [http://grass.osgeo.org/community/support.php Listy mailingowe] i [http://grass.osgeo.org/community/support.php#irc IRC]
* [http://trac.osgeo.org/grass/ Zgłaszanie błędów i życzeń]
* [https://svn.osgeo.org/grass/grass/branches/releasebranch_6_4/COPYING Licencja GNU GPL]
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em;

background-color:#f8f8ff;">

==== Pobierz ====
* [http://grass.osgeo.org/download/ Kod źródłowy i pakiety binarne]
* [[GRASS AddOns|Dodatki Systemu GRASS]]
* [[Promotional material|Materiały promocyjne]]
* [[Sample datasets|Przykładowe zestawy danych]]
* [[Global datasets|Globalne zestawy danych]]
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em;

background-color:#f8f8ff;">

==== Development ====
* [[Compile and Install]] of Source Code
* [[Development|GRASS Development]] intro
* [http://trac.osgeo.org/grass/wiki GRASS-trac]: the development Wiki, bugtracker, source code browser
* [[Release Roadmap]]
* [[GRASS 7 ideas collection]]
* [[GRASS SoC Ideas|Google Summer of Code ideas collection]]
* [http://trac.osgeo.org/grass/wiki/HowToContribute How to contribute to GRASS development] (getting write access and such)
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em;

background-color:#f8f8ff;">
Project Metrics provided by [http://www.ohloh.net/projects/3666 Ohloh].
{{#ohloh: account=3666}}
</div>
|}
{{Trans|Polish|English}}

[[Category:Languages/pl]]

GRASS-Wiki/es

2017-08-02T18:48:07Z

⚠️MilenaN: small update

__NOTOC__
{| width="100%"
|-
| width="68%" style="vertical-align:top" |
<div style="margin:0; margin-right:10px; border:1px solid #dfdfdf; background-color:#f8f8ff;">

<div style="padding:0.3em 1em 0.7em 1em;">

[[Image:grasslogo_vector_small.png|right|link=https://grass.osgeo.org]]

=== Bienvenido a la Wiki de usuario de GRASS GIS ===

{{website|documentation/general-overview|'''GRASS GIS'''}} es un [https://es.wikipedia.org/wiki/Sistema_de_informaci%C3%B3n_geogr%C3%A1fica Sistema de Información Geográfica] usado para administración y análisis de datos geospaciales, procesamiento de imágenes, producción de gráficos/mapas, modelación espacial, y visualización.

En esta Wiki, puedes obtener y contribuir información relacionada con GRASS, documentos y Complementos generados por la comunidad. Para editar, es necesario registrarse e ingresar (enlace superior izquierdo).

Para echar un vistazo, ver las funciones principales [[core features]]. Para ver ejemplos de uso, ver la [https://grass.osgeo.org/screenshots galería] y algunas [[Applications]].

Los servidores espejo del Wiki (actualizados diariamente): http://grass.fsv.cvut.cz/wiki-mirror/
</div>
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#FFE5E5;">
'''What's hot:'''
* <font size="+1">[http://trac.osgeo.org/grass/wiki/Release/7.2.1-News '''GRASS GIS 7.2.1''' ¡está disponible!]</font> {{bullet}} [https://grass.osgeo.org/download/software/#g72x descargar] {{bullet}} [https://trac.osgeo.org/grass/report/19 reportar algún problema]
* <font size="+1">[[GRASS Community Sprint Paris 2017]]</font>
* [http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures Lista de características nuevas en GRASS GIS 7] ([https://grass.osgeo.org/download/software/#g72x help testing])
* <font size="+0">[https://grass.osgeo.org/news/58/15/GRASS-GIS-6-4-6-released/ '''GRASS GIS 6.4.6''' está listo!]</font> {{bullet}} [https://grass.osgeo.org/download descargar] {{bullet}} [https://trac.osgeo.org/grass/report/16 reportar algún problema]

* Probar el tutorial [[Quick wxGUI tutorial]]
* Soporte temporal y otras nuevas [[Initiatives]]
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#f8f8ff;">
==== Documentación y soporte ====
* [[GRASS Help|Ayuda de GRASS y cómo empezar con GRASS]]
* [[GRASS Documents|Documentación profunda de GRASS]]
* [[Installation Guide]] binarios precompilados
* '''[[Faq|FAQ]] - Preguntas Frecuentes'''
* [[Applications]] - casos de usos de GRASS en varias disciplinas
* [[wxGUI]] - Interfaz Gráfica de Usuario basada en wxPython
</div>

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

==== Community ====
* [[GRASS Community]]: Contacto
* [[Applications|Research applications]]: Qué está haciendo la gente con GRASS
* [[GRASS migration hints|Migrando a GRASS]]
* [[GRASS Blogger]]
* Involúcrate: [[Project jobs]]
* [https://grass.osgeo.org/wiki/Special:Recentchanges?feed=rss RSS feed] de cambios recientes de esta Wiki
</div>

<div>Echa un vistazo a los grupos de usuarios de GRASS GIS en el mundo [https://grass.osgeo.org/community Usuarios Online de GRASS GIS]. Si opera una instalación de GRASS GIS, puedes ingresar tus datos ahí.
</div>

<div><p>''[[GRASS-Wiki:Language policy|Translate this Wiki]]''</p></div>


| width="38%" style="vertical-align:top" |
<div style="margin:0; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#f8f8ff;">
[[Image:OSGeo 220pix.png|center|220px|link=http://www.osgeo.org]]
<center>[http://www.osgeo.org OSGeo] Foundation Project</center>
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:1em 1em 1em 1em; background-color:#f8f8ff;">
[[Image:Btn_donate_SM.gif|center|link=https://grass.osgeo.org/donations/]]
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#f8f8ff;">
* [https://grass.osgeo.org/screenshots GRASS Screenshots]
* [https://trac.osgeo.org SVN/trac] Repositorio de Código fuente
* [https://grass.osgeo.org/support/mailing-lists Listas de correos] y [[IRC]]
* [https://trac.osgeo.org/grass/ Reportar errores o deseos]
* [https://svn.osgeo.org/grass/grass/branches/releasebranch_7_0/COPYING Licencia bajo GNU GPL]
</div>

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

==== Descargables ====
* [https://grass.osgeo.org/download Código fuente y binarios]
* '''[[AddOns]]'''
* [[Promotional material]]
* [[Sample datasets]]
* [[Global datasets]]
</div>

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

==== Desarrollo ====
* [[Compile and Install]] código fuente
* [[Development|GRASS Development]] intro
* [http://trac.osgeo.org/grass/wiki GRASS-trac]: Wiki de desarrolladores, bugtracker, navegador de código fuente
* [[Release Roadmap]]
* [[GRASS 7 ideas collection]]
* [[GRASS SoC Ideas|Conjunto de ideas para Google Summer of Code]]
* [http://trac.osgeo.org/grass/wiki/HowToContribute Cómo contribuir al desarrollo de GRASS]] (obtener acceso a escritura y demás)
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#f8f8ff;">
Mediciones del proyecto proveidas por [https://www.openhub.net/p/grass_gis Ohloh].

{{#widget:Ohloh Project|id=3666|type=partner_badge}}
</div>
|}
[[Category:Languages/es]]

GRASS-Wiki/pl

2017-08-02T18:42:25Z

⚠️MilenaN: small update

__NOTOC__
{| width="100%"
|-
| width="68%" style="vertical-align:top" |
<div style="margin:0; margin-right:10px; border:1px solid #dfdfdf; background-color:#f8f8ff;">

<div style="padding:0.3em 1em 0.7em 1em;">

[[Image:grasslogo_vector_small.png|right]]

=== Witaj w Wiki użytkowników GRASS GIS ===

[http://grass.osgeo.org Geographic Resources Analysis Support System], zwykle zwany '''GRASS-em''',
jest Systemem Informacji Geograficznej ([http://en.wikipedia.org/wiki/Geographic_information_system GIS]) wykorzystywanym do zarządzania i analiz danych przestrzennych, przetwarzania obrazów satelitarnych i zdjęć lotniczych, produkcji prezentacji graficznych oraz map, modelowania przestrzennego i wizualizacji. GRASS jest obecnie używany przez środowiska akademickie i komercyjne na całym śwecie, jak i przez wiele agencji rządowych i firm zajmujących się stanem środowiska naturalnego. GRASS GIS jest projektem [http://www.osgeo.org Open Source Geospatial Foundation]. <br>
Ta WIKI stanowi oficjalną stronę społeczności użytkowników projektu GRASS GIS. Aby zobaczyć przykłady analiz, idź do [http://grass.osgeo.org/screenshots/index.php Galerii GRASS GIS].

Na tej Wiki możesz znaleźć informacje o GRASS-ie, dokumenty oraz dodatkowe programy związane z projektem, a także rozbudowywać je. Aby móc edytować Wiki, zaloguj się - link w prawym górnym rogu.
</div>
</div>
<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#FFE5E5;">

'''Gorący temat:'''
* <font size="+1">[http://trac.osgeo.org/grass/wiki/Release/7.2.1-News '''GRASS GIS 7.2.1''' już jest!]</font> {{bullet}} [https://grass.osgeo.org/download/software/#g72x pobierz] {{bullet}} [https://trac.osgeo.org/grass/report/19 zgłoś problem]
* <font size="+1">[[GRASS Community Sprint Paris 2017]]</font>
* [http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures Lista nowych funkcji w GRASS GIS 7] ([https://grass.osgeo.org/download/software/#g72x pomóż nam testować])
* <font size="+0">[https://grass.osgeo.org/news/45/15/GRASS-GIS-6-4-6-released/ '''GRASS GIS 6.4.6''' is here!]</font> {{bullet}} [https://grass.osgeo.org/download pobierz] {{bullet}} [https://trac.osgeo.org/grass/report/16 zgłoś problem]

* Wypróbuj [[Quick wxGUI tutorial]]
* Temporal support i inne nowe[[Initiatives| Inicjatywy]]
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em
1em 1em 1em; background-color:#f8f8ff;">
==== Dokumentacja i pomoc dla użytkowników ====
* [[GRASS Help|Pomoc GRASS-a i Jak Zacząć]]
* [[GRASS Documents|Szczegółowa dokumentacja GRASS-a]]
* [[Installation Guide|Przewodnik instalacji]] prekompilowanych pakietów binarnych
* [[Faq|FAQ]]
* [[Applications|Zastosowania]] - przykłady użycia GRASS w różnych dyscyplinach
* [[wxGUI]] - Graficzny Interfejs Użytkownika w wxPython'ie
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em

1em 1em 1em; background-color:#f8f8ff;">

==== Społeczność====
* [[GRASS Community|Społeczność GRASS-a]]: Bądź w kontakcie
* [[Applications|Research applications]]: Co inni robią w GRASS-ie
* [[GRASS migration hints|Przejście na System GRASS]]
* [[GRASS Blogger]]
* Zaangażuj się: [[Project jobs|Prace przy projekcie]]
* [http://grass.osgeo.org/wiki/Special:Recentchanges?feed=rss RSS feed] ostatnie zmiany tej Wiki
</div>

<div>Zerknij na mapę użytkowników GRASS GIS na świecie [http://grass.osgeo.org/community/ GRASS GIS User Online]. Jeśli używasz GRASS GIS, dopisz się do mapy.
</div>

<div><p>''[[GRASS-Wiki:Language policy|Przetłumacz tę Wiki]]''</p></div>


| width="38%" style="vertical-align:top" |
<div style="margin:0; border:1px solid #dfdfdf; padding:0em 1em 1em 1em;

background-color:#f8f8ff;">
[[Image:OSGeo 220pix.png|center|220px]]
<center>Projekt Fundacji OSGeo</center>
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:1em 1em 1em 1em; background-color:#f8f8ff;">
[[Image:Btn_donate_SM.gif|center|link=http://grass.osgeo.org/donation.php]]<center>[http://grass.osgeo.org/donation.php Donate via PayPal.com]</center>
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding: 0em 1em 1em 1em;

background-color:#f8f8ff;">
* [http://grass.osgeo.org/screenshots/index.php Galeria Systemu GRASS]
* [http://trac.osgeo.org SVN/trac] Repozytorium Kodu Źródłowego
* [http://grass.osgeo.org/community/support.php Listy mailingowe] i [http://grass.osgeo.org/community/support.php#irc IRC]
* [http://trac.osgeo.org/grass/ Zgłaszanie błędów i życzeń]
* [https://svn.osgeo.org/grass/grass/branches/releasebranch_6_4/COPYING Licencja GNU GPL]
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em;

background-color:#f8f8ff;">

==== Pobierz ====
* [http://grass.osgeo.org/download/ Kod źródłowy i pakiety binarne]
* [[GRASS AddOns|Dodatki Systemu GRASS]]
* [[Promotional material|Materiały promocyjne]]
* [[Sample datasets|Przykładowe zestawy danych]]
* [[Global datasets|Globalne zestawy danych]]
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em;

background-color:#f8f8ff;">

==== Development ====
* [[Compile and Install]] of Source Code
* [[Development|GRASS Development]] intro
* [http://trac.osgeo.org/grass/wiki GRASS-trac]: the development Wiki, bugtracker, source code browser
* [[Release Roadmap]]
* [[GRASS 7 ideas collection]]
* [[GRASS SoC Ideas|Google Summer of Code ideas collection]]
* [http://trac.osgeo.org/grass/wiki/HowToContribute How to contribute to GRASS development] (getting write access and such)
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em;

background-color:#f8f8ff;">
Project Metrics provided by [http://www.ohloh.net/projects/3666 Ohloh].
{{#ohloh: account=3666}}
</div>
|}
{{Trans|Polish|English}}

[[Category:Languages/pl]]

Talk:GRASS Community Sprint Paris 2017

2017-07-22T15:18:25Z

⚠️MilenaN: /* Participants and Reports */

= Participants and Reports =

== Photos of the event ==
* Nice collection at [https://www.flickr.com/groups/3522675@N24/pool/ Flickr]

[[Image: Paris2017sprint.jpg.jpg|500px|GRASS GIS 7 sprint team at FOSS4G 2017, France]]

GRASS GIS 7 sprint team at FOSS4G 2017, France

== Martin Landa ==

* [https://trac.osgeo.org/grass/timeline?from=Jul+22%2C+2017&daysback=1&authors=martinl&milestone=on&ticket=on&changeset=on&wiki=on&update=Update SVN log] overview

== Markus Neteler ==

* FreeBSD ticket: {{trac|2940}}
* v.rast.stats -d ticket: {{trac|3357}}
* [https://trac.osgeo.org/grass/timeline?from=Jul+22%2C+2017&daysback=1&authors=NETELER&milestone=on&ticket=on&changeset=on&wiki=on&update=Update SVN log] overview
* discussions with Astrid Emde on https://git.osgeo.org/gogs/foss4g-europe/foss4g-europe-2017-paris

== Anna Petrasova ==

* [https://trac.osgeo.org/grass/timeline?from=Jul+22%2C+2017&daysback=1&authors=annakrat&milestone=on&ticket=on&changeset=on&wiki=on&update=Update SVN log] overview
* working on improving data catalog

== Vaclav Petras ==

* [https://trac.osgeo.org/grass/timeline?from=Jul+22%2C+2017&daysback=1&authors=wenzeslaus&milestone=on&ticket=on&changeset=on&wiki=on&update=Update SVN log] overview
* Change wxGUI Map Display title from <tt>GRASS GIS ''version'' Map Display: ''name'' - Location: ''location@mapset''</tt> to <tt>GRASS GIS Map Display: ''name'' - ''location/mapset''</tt> ({{rev|71301}})

== Milena Nowotarska ==

* translation of GRASS GIS GUI to Polish language

Talk:GRASS Community Sprint Paris 2017

2017-07-22T15:17:39Z

⚠️MilenaN: + Milena

Talk:GRASS Community Sprint Paris 2017

2017-07-22T15:15:03Z

⚠️MilenaN: /* Photos of the event */ added a photo

File:Paris2017sprint.jpg.jpg

2017-07-22T15:11:28Z

⚠️MilenaN:

GRASS team at FOSS4G code sprint Paris 2017

Talk:GRASS Community Sprint Paris 2017

2017-07-22T14:56:58Z

⚠️MilenaN: Added the link to photos on Flickr

= Participants and Reports =

== Photos of the event ==
* Nice collection at [https://www.flickr.com/groups/3522675@N24/pool/ Flickr]

TODO: INSERT GROUP PHOTO HERE

== Martin Landa ==

* [https://trac.osgeo.org/grass/timeline?from=Jul+22%2C+2017&daysback=1&authors=martinl&milestone=on&ticket=on&changeset=on&wiki=on&update=Update SVN log] overview

== Markus Neteler ==

* FreeBSD ticket: {{trac|2940}}
* v.rast.stats -d ticket: {{trac|3357}}
* [https://trac.osgeo.org/grass/timeline?from=Jul+22%2C+2017&daysback=1&authors=NETELER&milestone=on&ticket=on&changeset=on&wiki=on&update=Update SVN log] overview
* discussions with Astrid Emde on https://git.osgeo.org/gogs/foss4g-europe/foss4g-europe-2017-paris

== Anna Petrasova ==

* [https://trac.osgeo.org/grass/timeline?from=Jul+22%2C+2017&daysback=1&authors=annakrat&milestone=on&ticket=on&changeset=on&wiki=on&update=Update SVN log] overview
* working on improving data catalog

GRASS Community Sprint Paris 2017

2017-07-16T17:24:21Z

⚠️MilenaN: /* In person */

{{toc|right}}
During the [https://europe.foss4g.org/2017/ FOSS4G Europe 2017] , 18-22 July 2017, [http://en.wikipedia.org/wiki/Marne-la-Vallée Marne-la-Vallée], [https://en.wikipedia.org/wiki/ France], the GRASS GIS project will join the code sprint

'''Important dates:'''

* CodeSprint: Sat 22.07.2017 (see also [https://europe.foss4g.org/2017/Code_Sprint])

* 9:00 - 12:00 Morning session
* 13:00 - 17:00 Afternoon session

== 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<br>
    '''sponsoring the GRASS project at [http://grass.osgeo.org/donations/ http://grass.osgeo.org/donations/]'''<br>
and, if needed, contact [[User:Neteler|Markus Neteler]] <tt><neteler at osgeo.org></tt>. 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 ==

Room L006

Ecole Nationale des Sciences Géographiques

6 et 8 Avenue Blaise Pascal

Cité Descartes - Champs-sur-Marne

77455 Marne la Vallée Cedex 2

How to get to FOSS4G-E 2017 OSGeo Code Sprint?
* https://europe.foss4g.org/2017/Getting_to_ENSG
* http://www.openstreetmap.org/?mlat=48.84115&mlon=2.58744#map=15/48.8411/2.5856

== Accommodation and Costs ==

* to be defined

== Agenda - What we plan to do ==

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

* GSOC support
* Preparation of GRASS GIS 7.4.0 new stable release
* Documentation
* oss-fuzz integration
* wxPython 4.0 (wxGUI integration)
* Web CMS: MediaWiki upgrade
* PyWPS support integration in wxGUI Modeler
* v.clip integration into trunk
* add [https://scan.coverity.com/travis_ci Coverity Scan Addon for Travis CI] for instant code quality checking
* Discuss start of GRASS GIS 8

... YOUR IDEA HERE ...

== Planned participation ==

For organizational reasons, please '''additionally register''' at: https://wiki.osgeo.org/wiki/FOSS4G-Europe_2017_Code_sprint

=== In person ===

Please add your name 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:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=130px|'''Participant '''
|width=100px|'''Country'''
|width=100px|'''Arrival'''
|width=100px|'''Departure'''
|'''Topic'''
|width=75px|'''T-Shirt'''
|'''Notes'''
|-
|1
|[[User:Lucadelu|Luca Delucchi]]
|
|
|
|
|
|
|-
|2
|[[User:Neteler|Markus Neteler]]
|DE
|17.7.
|23.7.
|Release planning, CI, new features, ...
|M
|
|-
|3
|[[User:Veroandreo|Veronica Andreo]]
|AR/NL
|17.7
|23.7
|Documentation, testing, ...
|S/XS
|
|-
|4
|[[User:Madi|Margherita Di Leo]]
|
|
|
|
|
|
|-
|5
|[[User:Landa|Martin Landa]]
| CZ
| 17.7.
| 23.7.
| oos-fuzz, WxPython 4.0
| L
|
|-
|6
|[[User:MilenaN|Milena Nowotarska]]
| PL
| 17.7.
| 23.7.
| Documentation, website
| M
|
|-
|}

=== Via IRC chat ===

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

{|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:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=130px|'''Participant '''
|width=100px|'''Country'''
|-
|1
|[your name here]
|
|-
|}

== Individual Preparation ==

* Bring your own computer
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:E_plug_and_socket.jpg France]). See also http://www.power-plugs-sockets.com/
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== Photos ==

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

== Reports ==

See [[Talk:GRASS_Community_Sprint_Paris_2017]]

== 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?''
** Contact [[User:Lucadelu|Luca Delucchi]] <tt><lucadeluge at gmail com></tt>

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2017]]

GRASS Community Sprint Paris 2017

2017-06-28T21:42:13Z

⚠️MilenaN: Creating GRASS Community Sprint Paris 2017

{{toc|right}}
During the [https://europe.foss4g.org/2017/ FOSS4G Europe 2017] , 18-22 July 2017, [http://en.wikipedia.org/wiki/Marne-la-Vallée Marne-la-Vallée], [https://en.wikipedia.org/wiki/ France], the GRASS GIS project will join the code sprint

'''Important dates:'''

* CodeSprint: Sat 22.07.2017 (see also [https://europe.foss4g.org/2017/Code_Sprint])

* 9:00 - 12:00 Morning session
* 13:00 - 17:00 Afternoon session

== 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<br>
    '''sponsoring the GRASS project at [http://grass.osgeo.org/donations/ http://grass.osgeo.org/donations/]'''<br>
and, if needed, contact [[User:Neteler|Markus Neteler]] <tt><neteler at osgeo.org></tt>. 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 ==

Room L006

Ecole Nationale des Sciences Géographiques

6 et 8 Avenue Blaise Pascal

Cité Descartes - Champs-sur-Marne

77455 Marne la Vallée Cedex 2

How to get to FOSS4G-E 2017 OSGeo Code Sprint?
* https://europe.foss4g.org/2017/Getting_to_ENSG
* http://www.openstreetmap.org/?mlat=48.84115&mlon=2.58744#map=15/48.8411/2.5856

== Accommodation and Costs ==

* to be defined

== Agenda - What we plan to do ==

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

* GSOC support
* Preparation of GRASS GIS 7.4.0 new stable release
* Documentation

... YOUR IDEA HERE ...

== Planned participation ==

For organizational reasons, please '''additionally register''' at: https://wiki.osgeo.org/wiki/FOSS4G-Europe_2017_Code_sprint

=== In person ===

Please add your name 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:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=130px|'''Participant '''
|width=100px|'''Country'''
|width=100px|'''Arrival'''
|width=100px|'''Departure'''
|'''Topic'''
|width=75px|'''T-Shirt'''
|'''Notes'''
|-
|1
|[[User:Lucadelu|Luca Delucchi]]
|
|
|
|
|
|
|-
|2
|[[User:Neteler|Markus Neteler]]
|
|
|
|
|
|
|-
|3
|[[User:Veroandreo|Veronica Andreo]]
|
|
|
|
|
|
|-
|4
|[[User:Madi|Margherita Di Leo]]
|
|
|
|
|
|
|-
|5
|[[User:Landa|Martin Landa]]
|
|
|
|
|
|
|-
|6
|[[User:MilenaN|Milena Nowotarska]]
|
|
|
|
|
|
|-
|}

=== Via IRC chat ===

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

{|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:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=130px|'''Participant '''
|width=100px|'''Country'''
|-
|1
|[your name here]
|
|-
|}

== Individual Preparation ==

* Bring your own computer
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:E_plug_and_socket.jpg France]). See also http://www.power-plugs-sockets.com/
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== Photos ==

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

== Reports ==

See [[Talk:GRASS_Community_Sprint_Paris_2017]]

== 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?''
** Contact [[User:Lucadelu|Luca Delucchi]] <tt><lucadeluge at gmail com></tt>

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2017]]

WxNviz/pl

2016-08-23T13:57:29Z

⚠️MilenaN: update to en version

''(Wróć do strony [[WxPython-based GUI for GRASS|wxGUI]].)''

'''wxNviz''' jest rozszerzeniem [[wxGUI]] pozwalającym na realistyczne renderowanie multiple surfaces (danych rastrowych) w przestrzeni 3D z możliwością kolorowania tematycznego, nakładania danych wektorowych 2D na powierzchnie, przestrzennego wyświetlania danych wektorowych 3D oraz wizualizację danych volume (danych rastrowych 3D).

Zobacz również [http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Nviz.html instrukcję] do wxNviz.

__TOC__
== Zrzuty ekranowe ==
<center>
<gallery perrow=3 widths=200>
Image:Wxnviz-alpha-0.png|2008-06-27: Display raster map from layer tree in 2.5D (surface)
Image:Wxnviz-alpha-1.png|2008-07-05: Dodana obsługa danych wektorowych (linie 2D)
Image:Wxnviz-alpha-2.png|2008-07-26: Obsługa punktowych danych wektorowych
Image:Wxnviz-alpha-3.png|2008-08-02: Obsługa danych wektorowych 3D
Image:Wxnviz-alpha-4.png|2008-08-09: Wstępna obsługa danych volumetrycznych
Image:Wxnviz-lmgr.png|2010-05-31: 3D view tools window integrated into Layer Manager
Image:Wxnviz-light.png|Lighting control panel in Layer Manager (2010-06-17)
Image:Wxnviz-fringe.png|Fringe control panel in Layer Manager (2010-06-23)
Image:Wxnviz-redirect.png|Redirect messages to wxGUI (2010-08-08)
Image:Wxnviz-volumes.png|Displaying raster (surface), 2D vector and 3D raster (volume) in the 3D space (2010-08-16)
Image:WxNviz surface page.png|Surface page of WxNviz modified (2011-06-02)
Image:WxNviz_constant_surface_page.png|Constant surface page added (2011-06-02)
Image:WxNviz_lighting.png|Lighting fixed (2011-05-02)
Image:WxNviz_cutting_planes_1.png|Cutting planes (shading blend) (2011-06-10)
Image:WxNviz_cutting_planes_2.png|Cutting planes (shading top color) (2011-06-10)
Image:WxNviz_view_page.png|View page modified (2011-06-10)
Image:Nviz_cmd_cutting_planes.png‎|Picture of surfaces cut by two planes (generated by nviz_cmd) (2011-06-30)
Image:WxNviz_generate_command.png‎|Command for nviz_cmd generated by wxNviz (2011-07-01)
Image:WxNviz_north_arrow.png‎|North Arrow implemented (2011-07-08)
Image:WxNviz_volumes.png‎|Colored isosurfaces with transparency (2011-07-08)
Image:WxNviz_volume_slices_1.png‎|Partially transparent slice (2011-07-14)
Image:WxNviz_volume_slices_2.png‎|Combination of slices and isosurface (2011-07-14)
Image:WxNviz_overlays.png‎|Raster legend, text label and north arrow (2011-07-22)
Image:WxNviz_thematic_points_colors‎.png|Thematic mapping (colors) for points (2011-08-05)
Image:WxNviz_colorrules_dialog.png|Dialog for {{cmd|v.colors}} opened from 3D view (2011-08-05)
</gallery>
</center>

== Animacje ==

{{YouTube|AByFPKHvgu4|desc=Using fly-through mode for creating animation}}

== Tutoriale wideo ==

{{YouTube|ib1-mBbWkv4|desc=Loading data, settings layer properties}}
{{YouTube|ZLDstyumxv0|desc=Wizualizacja sieci i strzałki północy}}
{{YouTube|CmK-fEyf2SY|desc=3D raster maps (volumes) in the space (isosurface and slice mode)}}
{{YouTube|13wj5KWEweE|desc=Color thematic mapping}}

=== Starsze tutoriale (2010) ===

{{YouTube|Ej_rBc9sgvE|desc=Loading data, settings layer properties}}
{{YouTube|iWyaBL2Krto|desc=Visualizing fringes}}
{{YouTube|ioE_hHMHqKg|desc=3D raster maps (volumes) in the space}}

== Pomysły ==

* Mgła (zobacz [http://gpwiki.org/index.php/OpenGL:Tutorials:Tutorial_Framework:Light_and_Fog], [http://www.swiftless.com/tutorials/opengl/fog.html], [http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=16])
* Vertical labels (take from geonames.org point data): like in http://tev.fbk.eu/marmota/blog/?p=82
* Second interactive light source for isosurface visualization
* Tick marks and coordinate values to x,y,z axis when drawing fringe

<strike></strike>

== Rozwiązania problemów ==

* Nic się nie renderuje:
: Please note that with wxGTK port of wxPython (Linux systems), a problem might appear during wxNviz initialization (nothing is rendered at all) or when rendering vectors (bad order of rendering surfaces and vectors). If you encounter such problems, try to change a depth buffer number in wxGUI Menu > Settings > Preferences > Map Display > Advanced (possible numbers are 0, 16, 24, 32). It is currently not possible to automatically find out the right number which is working for your computer.

== Znane problemy ==

#Lista [http://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~wxNviz otwartych ] i [http://trac.osgeo.org/grass/query?status=assigned&status=closed&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~wxNviz zamkniętych] biletów
#<strike>Adding vector data crashes wxGUI on Mac</strike>
#<strike>Viewing height sometimes sets to 1 after switching to 2D and back to 3D View (or with the simultaneous 2D view - very nice feature) and even after View is reset, it keeps getting back at 1 each time the slider is touched</strike>
#:Fixed in {{rev|46208}}
#Adding draw, draw current and clear button may be useful
#Thematic mapping is available in GRASS 7 only
#Display region in 3D does not change accordingly to display region in 2D in version <= 6.5
#Appearance:
## I <strike>need to click View tab to get the arrow draw, same for the scale bar </strike>
##add legend > OK: nothing gets drawn in 3D but the legend shows up when I switch to 2D but when I clicked delete scalebar (which was not drawn), my surface disapeared but the legend showed up along with white and black background (which I assume was supposed to be transparent, because when I moved the legend the surface was under it - we already discussed this, it may be my problem, because it works for Michael).
#General
##<strike>when I go from 3D view to 2D and then back to 3D I lose most of my settings </strike>
##<strike>similarly, when I add volume to Map layers I lose my view settings and the 3D view goes back to default </strike>
#Volumes:
##change of region by g.region seems to be ignored (or I missed something), I had to restart GRASS with the new region to get the 3D region for volumes right. Given that the default top, botom is 1,0, if GRASS starts with the default 3D region settings volumes do not work because there is just one level.
##<strike>isosurfaces work with my terrestrial lidar data but the slices don't, it seems that it is due my resolution being 0.3m, when I change it to 1m I get at least some limited slicing
###this may be in ogsf becuase slices in nviz do not work with this data either </strike>
#<strike>changing color to constant did not change the color of the isosurface</strike>

== Porównanie funkcjinalności Tcl/Tk nviz i wxNviz ==
Czego brakuje w wxNviz:
* scaled difference
* lighting - follow surface viewpoint
* keyframe animation
* text rendering (in OpenGl)

Co działa jedynie częściowo:
* legenda, etykiety
* thematic mapping - nviz allows to choose also icon and multiple classification
* basic support of animations

Co jest nowego w wxNviz:
* it is possible to change view more interactively using mouse

Uwagi:
* Scripting functionality is replaced by m.nviz.image module
* stan wxNviz jest zapisany w polu pracy

== Google Summer of Code ==

=== [[wxNviz GSoC 2008|2008]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#wxNvizdevelopmentforenhanced34Dvisualizationandanalysis Zaakceptowany projekt Google Summer of Code 2008]

=== [[wxNviz GSoC 2010|2010]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#wxNvizdevelopmentforenhanced34Dvisualizationandanalysis Zaakceptowany projekt Google Summer of Code 2010]

=== [[wxNviz GSoC 2011|2011]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#CompletionofwxGUINvizextensionfor3DdatavisualizationinGRASSGIS Accepted Google Summer of Code 2011 project]

== Zobacz również ==

* http://lists.osgeo.org/pipermail/grass-dev/2008-February/035792.html

{{Trans|Polish|English}}
{{WxGUI}}
[[Category:NVIZ]]
[[Category:Visualization]]
[[Category:Languages/pl]]

GRASS Help/pl

2016-08-22T18:31:49Z

⚠️MilenaN: translation pl

== Jak zacząć ==

''Większość tutoriali i przykładów używa próbnego zestawu danych [[#Sample Datasets | Spearfish County, SD]].'' Nowe przykłady bazują również na bogatym zestawie danych [http://www.grassbook.org/data_menu3rd.php OSGeo Educational Dataset] (North Carolina, USA)

=== Instalacja ===

* W przewodniku instalacyjnym [[Installation Guide]]

=== Często zadawane pytania ===

* [[Faq|FAQ]]
* Możesz skontaktować się z użytkownikami GRASS przez [[How to participate in IRC communication|IRC]]
* [[How the Open Source software development model works]]

=== Dokumentacja na początek ===

* [[GRASS 6 Terminology | Terminologia GRASS 6]]

* [[Gis Concepts|Podstawowe koncepcje GIS]] i jak GRASS je implementuje

* [http://grass.osgeo.org/grass64/manuals/html64_user/helptext.html GRASS Quickstart] strona z pomocą

* [[Importing data|Importowanie danych]]: jak przenieść swoje dane do GRASS

* [http://grass.osgeo.org/grass64/manuals/html64_user/index.html strony pomocy GRASS] łącznie z podstawowymi instrukcjami

==== Krótkie tutoriale ====

* [[Quick_wx_tutorial|Szybkie wprowadzenie do 6.4 wxGUI i map rastrowych]]

* Materiały z kursu [http://geostat-course.org/Topic_NetelerMetz_2011 Wprowadzenie do GRASS GIS], Geostat 2011, Landau, Niemcy, M. Neteler i M. Metz

* [http://trac.osgeo.org/grass/wiki/HowToTestGrass6 Jak testować GRASS6] - łatwe do powtórzenia kroki w GRASS 6.3+ i QGIS

* [[GRASS 6 Tutorial]] (w opracowaniu; mile widziana pomoc)

* [http://www.grassbook.org/neteler/osg05/ GRASS 6 in a nutshell] M. Neteler (2005, krótki tutorial, przetłumaczony również na hiszpański i francuski)

* [http://www.gdf-hannover.de/lit_html/grass60_v1.2_en/index.html An introduction to the practical use of the Free Geographical Information System GRASS 6.0] by GDF Hannover - [http://www.gdf-hannover.de/media.php?id=0&lg=en More tutorials] from GDF Hannover

==== Książki ====

* [http://www.grassbook.org Open Source GIS: A GRASS GIS Approach. 3rd ed. 2008] by M. Neteler and H. Mitasova (Springer book; focus is on GRASS 6.3)

==== Samodzielne moduły ====

* Synopsis of GRASS modules, including menu positions ({{website|gdp/grassmanuals/grass64_module_list.pdf|PDF, 100k}}) ({{website|gdp/grassmanuals/grass64_module_list.html|HTML version}})
: ''Create current list with'' "<tt>make html2pdfdoc</tt>" or "<tt>cd tools; ./module_synopsis.sh</tt>" ''in GRASS 6.3+''

* Individual GRASS module [http://grass.osgeo.org/grass64/manuals/html64_user/index.html reference manuals]

* All GRASS module reference manuals (PDF Book)
: ''Create current set with'' "<tt>make html2pdfdoccomplete</tt>" ''in GRASS 6.3+''

=== Dane przykładowe ===

* [http://www.grassbook.org/data_menu3rd.php North Carolina, USA (OSGeo Edu dataset)] - bogaty zestaw danych przygotowany w latach 2007/2008
* [http://grass.osgeo.org/download/data6.php Spearfish County, SD, USA] (okolice Mount Rushmore) z [http://mpa.itc.it/markus/osg05/ danymi dodatkowymi]
** Mount Rushmore: [43°53' N, 103°28' W]

* [[Global datasets|Globalne zestawy danych]]

* [http://grass.osgeo.org/download/data.php Więcej danych przykładowych]

== Czytaj dalej ==

* [[Documents|Pełna dokumentacja GRASS]]

* [[GRASS_Education_%28Free_GIS_education%29#Teaching_Materials | Materiały szkoleniowe]] dostarczone przez społeczność.<BR>(Tutoriale, kursy, wideo szkoleniowe, etc.)

* More GRASS documentation and tutorials from the old [http://grass.osgeo.org/gdp/index.php GRASS Documentation Project].<BR>[''content is slowly being merged into this Wiki'']

* [[GRASS and its siblings%3B a guide for the novice]]

== Migracja z innego oprogramowania GIS ==

* [[GRASS_migration_hints|Wskazówki migracji GRASS]]
* [[GIS to GRASS command translation|GIS Software to GRASS command translation table and discussion]]
* [[Tips for Arc users| Wskazóki dla użytkowników Arc]]

== Współpraca z zewnętrznymi programami ==

* [[Tips_and_Tricks#Using_QGIS_as_a_frontend_to_GRASS| QGIS]] frontend

* [[GRASS_and_Rstat|R statistics]] interface

* [[GRASS_and_GMT|GMT mapping]] cartography

* [[GRASS_and_MapServer| MapServer]] web server

* External databases ({{cmd|db.connect}})
* External raster data ({{cmd|r.external}})
* External vector data ({{cmd|v.external}})
* [[GRASS and Paraview|Paraview]] 3D visualization ({{cmd|r.out.vtk}}, {{cmd|r3.out.vtk}}, {{cmd|v.out.vtk}})
* [[POV-Ray|POVray]] 3D visualization ({{cmd|r.out.pov}}, {{cmd|v.out.pov}})
* [[OpenSceneGraph]] 3D visualization
* [[GRASS vector export to Inkscape]]

== Misc. Help ==

* [[:Category:FAQ|GRASS FAQ]] (see also: [[GRASS 6 Tutorial]])
* [[Tips and Tricks]]
* [[Compile and install GRASS and QGIS with GDAL/OGR Plugin]]
* [[How to interpolate point value using kriging method with R and GRASS 6]]

--------
* [[Help|Pomoc]] Wiki (jak edytować strony po zalogowaniu)

[[Category: Documentation]]
[[Category:Languages/pl]]

Computational region/pl

2016-08-22T15:27:02Z

⚠️MilenaN: translation pl

Bieżący region lub region obliczeniowy to aktualne ustawienie granic zasięgu regionu i bieżąca rozdzielczość rastra.

Generalne zasady w systemie GRASS:

#Mapy rastrowe są zawsze '''zaimportowane całkowicie''' w swojej natywnej rozdzielczości (wyjątek: importowane warstwy WMS).
#Mapy wektorowe są zawsze '''zaimportowane całkowicie'''.
#W obliczeniach,
##rastrowe mapy '''wejściowe''' są automatycznie przycięte/ograniczone i przeskalowane (z użyciem resamplingu najbliższego sąsiada) do bieżącego regionu, aby utworzyć wyjściową mapę rastrową lub odpytywać wartości.
##Rastrowe mapy '''wyjściowe''' mają zasięg i rozdzielczość tożsamą z mapami w bieżącym regione obliczeniowym.
##Mapy wektorowe są zawsze '''całkowicie przetwarzane'''.

'''Wskazówka''' dla użytkowników przechodzących z innych systemów GIS:<br>
Bieżący region lub region obliczeniowy mogą być rozumiane jako ''region zainteresowania'' (ang. ROI).

=== FAQs ===

'''Q:''' Nic nie widać!

'''A:''' Zazwyczaj region obliczeniowy jest ustawiony na obszar nie pokrywający się
z mapą zainteresowania. Użyj {{cmd|g.region}} aby dopasować ustawienia
regionu obliczeniowego, np.: poprzez ustawienie go do zasięgu mapy rastrowej:

<source lang="bash">
g.region rast=myrastermap -p
</source>

'''W graficznym interfejsie:'''

Ustaw wyświetlanie do wybranej mapy:

[[Image:Wxgui zoom to raster.png|350px|center|thumb|wxGUI:
ustaw wyświetlanie mapy do wybranej mapy (menu kontekstowe pod prawym przyciskiem myszy na nazwie mapy)]]

Ustaw region obliczeniowy do wybranej mapy:

[[Image:Wxgui computat region to raster.png|350px|center|thumb|wxGUI:
ustaw region obliczeniowy do wybranej mapy (menu kontekstowe pod prawym przyciskiem myszy na nazwie mapy)]]

<br> '''Q:''' Rozdzielczość mojego regionu jest inna niż chciałem!

'''A:''' Czasami rozdzielczośćregionu obliczeniowego nie zgadza się dokładnie z rozdzielczością
wprowadzoną w {{cmd|g.region}}. Oto przykład:
<source lang="bash">
g.region rast=myrastermap res=1 -p
(...)
nsres: 0.9993515
ewres: 1.00025576
(...)
</source>

Aby wymusić zgodność regionu obliczeniowego z wprowadzoną rozdzielczością, użyj flagi -a:
<source lang="bash">
g.region rast=myrastermap res=1 -ap
(...)
nsres: 1
ewres: 1
(...)
</source>

<br> '''Q:''' Mapa rastrowa źle wygląda.

'''A:''' Rozdzielczość regionu obliczeniowego nie pasuje do rozdzielczości mapy rastrowej.
Użyj {{cmd|g.region}} aby dopasować ustawienia rozdzielczości regionu obliczeniowego lub ustaw ją do do mapy rastrowej (zobacz wyżej).

<br> '''Q:''' Dostaję błąd modułu "xyz module: G_malloc error".

'''A:''' Prawdopodobnie chcesz użyć więcej pamięci niż oferuje twój komputer, co jest często spowodowane zbyt dużą rozdzielczością
(lub zbyt dużym regionem obliczeniowym). Np.: bezcelowe jest obliczanie danych DEM w nanometrowej rozdzielczości rastra.
Ustaw zasięg regionu i rozdzielczość rastra dokładnie przy użyciu {{cmd|g.region}} ( w graficznym interfejsie: menu Ustawienia -> Region -> Display Region | Set Region).

'''Q:''' Potrzebuję fragment mapy rastrowej!

'''A:''' Chociaż jest to wykonywane w locie przez odpowiednie ustawienie regionu obliczeniowego, ciągle możesz utworzyć
kopię fragmenut mapy rastrowej poprzez
<source lang="bash">
r.mapcalc "subset = original_map"
</source>

=== Zobacz również ===

* [[Location and Mapsets]]

[[Category: Documentation]]
[[Category: FAQ]]
[[Category: Tutorial]]
[[Category:Languages/pl]]

Importing data/pl

2016-08-22T14:00:15Z

⚠️MilenaN: update to en version

== Wprowadzanie swoich danych do systemu GRASS ==

GRASS obsługuje wiele popularnych formatów danych, a także wiele rzadkich.

The primary import/export tool is called [http://www.gdal.org GDAL/OGR]. It is the Rosetta Stone of the free GIS world:

* [http://www.gdal.org/formats_list.html formaty rastrowe] obsługiwane są przez {{cmd|r.in.gdal}}
* [http://www.gdal.org/ogr/ogr_formats.html formaty wektorowe] obsługiwane są przez {{cmd|v.in.ogr}}

W oknie powitalnym programu, przy pomocy Kreatora lokacji utwórz nową lokację o właściwym układzie współrzędnych dla swoich danych. Następnie wybierz z menu:
Dla rastrów: Plik → Import raster data using GDAL
Dla wektorów: Plik → Import vector data using OGR

Zazwyczaj GDAL/OGR automatycznie wykryje format pliku.

* Wiele [http://www.gpsbabel.org/capabilities.shtml formatów GPS] może być zaimportowanych przy pomocy [http://www.gpsbabel.org GPSBabel] oraz narzędzia {{cmd|v.in.gpsbabel}}.

After the map has been imported you can add it to the display layer list in the Layer Manager window. You will most likely want to right click on the map in the layer list and select "Zoom to selected map(s)". Otherwise when you go to view the map you could be far away and just see a white display canvas.

To view a raster map, add it to the Layer Manager with the grid-like button with a (+), to add a vector map to the Layer Manager use the button with lines and points on it to the right of the add raster map button. The left hand button in the Map Display window will re-render the map if needed.

The "[[computational region]]" is a very important concept in GRASS and is distinct from the "display window" you see in the Map Display window. You can also read about it in the {{cmd|rasterintro}} help page. You can set the computational region and cell resolution to match a specific map with the {{cmd|g.region}} module.

{| border="1"
| After importing your data you need to run "<tt>g.region -p rast=your_map</tt>" or "<tt>g.region -p vect=your_map</tt>" to set the region bounds/zoom to match that of the newly imported map. Be careful with the region resolution when doing this with vector maps, you may have to run "<tt>g.region -a res=</tt>" to clean that up and keep it reasonable (for example 2000x2000 rows and columns).
|}

=== Tutoriale wideo dotyczące importu ===

* zobacz[[WxGUI#Video_tutorials]]

=== Linki zewnętrzne ===

Możesz podłączyć dane zamiast importowania.

* {{cmd|r.external}}: full support for external raster data (all GDAL supported formats)
* {{cmd|v.external}}: basic support for external vector data with some topology limitations (all OGR supported formats)

=== Masowy import danych ===

Menu [[wxGUI]] zawiera uproszczone narzędzia importu.

==== Import wielu danych wektorowych (np. SHAPE) ====

<center>
{|
|
[[Image:WxGUI_vector_bulk_import1.png|400px|thumb|Masowy import danych wektorowych przez menu]]
||
[[Image:WxGUI_vector_bulk_import2.png|250px|thumb|Masowy import wielu danych SHAPE poprzez menu (pliki są wybierane automatycznie)]]
|
|}
</center>

==== Import wielu danych rastrowych (np. GeoTIFF) ====

<center>
{|
|
[[Image:WxGUI bulk raster import1.png|300px|thumb|Masowy import danych GeoTIFF poprzez menu]]
||
[[Image:WxGUI bulk raster import2.png|320px|thumb|Masowy import danych GeoTIFF poprzez menu (pliki są wybierane automatycznie)]]
|
|}
</center>

=== Duże dane ===

When importing large raster maps with {{cmd|r.in.gdal}} the default internal settings may be slow, with a large percentage of the CPU locked up in kernel system operations. In these cases you should increase the ''memory='' option to be larger than:
tile_height * raster_width * band_count * sizeof_datatype

You can find those values with <tt>gdalinfo</tt>.

Setting the ''r.in.gdal memory='' option has the same effect as setting the GDAL_CACHEMAX environment variable.

=== Moduły ===
==== Rastrowe ====
* {{cmd|r.in.arc}}
* {{cmd|r.in.aster}}
* {{cmd|r.in.gdal}}
* {{cmd|r.in.mat}}
* {{cmd|r.in.poly}}
* {{cmd|r.in.wms}}
* {{cmd|r.in.ascii}}
* {{cmd|r.in.bin}}
* {{cmd|r.in.gridatb}}
* {{AddonCmd|r.in.onearth}}
* {{cmd|r.in.srtm}}
* {{cmd|r.in.xyz}}

==== Wektorowe oraz punktowe ====
* {{cmd|v.in.ascii}}
* {{cmd|v.in.e00}}
* {{cmd|v.in.gns}}
* {{cmd|v.in.mapgen}}
* {{cmd|v.in.region}}
* {{cmd|v.in.wfs}}
* {{cmd|v.in.db}}
* {{cmd|v.in.garmin}}
* {{cmd|v.in.gpsbabel}}
* {{AddonCmd|v.in.mbsys_fnv}}
* {{cmd|v.in.sites}}
* {{cmd|v.in.dxf}}
* {{cmd|v.in.geonames}}
* {{cmd|v.in.lines}}
* {{cmd|v.in.ogr}}
* {{cmd|v.in.sites.all}}

=== Formaty danych ===

* Wiele popularnych [[Data formats|formatów danych]]
* [[Global datasets|Globalne zbiory danych]]
* [[Tips_for_Arc_users|Import/eksport danych ESRI]]
* [[Import DXF|Import danych DXF]]
* [[Import XYZ|Import danych XYZ]]
* [[HOWTO_import_SRTM_elevation_data| Import danych SRTM]]
* [[HOWTO_import_USGS_elevation_data|Import danych wysokościowych USGS]]
* [[S-57 data| Dane NOAA ENC S-57]]
* [[Import_Mio_C230_GPS_track_maps|Ślady GPS Mio]]

{{Trans|Polish|English}}

[[Category: Documentation]]
[[Category: FAQ]]
[[Category: Languages/pl]]
[[Category: Import]]

Vector network analysis/pl

2016-08-22T12:37:19Z

⚠️MilenaN: update to en version

Narzędzia GRASS do analiz sieciowych bazują na bibliotece [http://trac.osgeo.org/grass/browser/grass/trunk/lib/vector/dglib/ DGlib] Directed Graph Library.

GRASS 7 has [[WxGUI Vector Network Analysis Tool]] front-end, which supports some of the vector network analysis modules.

__TOC__

== Zaimplementowane algorytmy ==

Poniższe algorytmy są zaimplementowane (w GRASS 6.5+):

* Utrzymanie sieci: {{cmd|v.net|version=70}}
* Najkrótsza trasa: {{cmd|d.path|version=64}} and {{cmd|v.net.path|version=70}}
* Najkrótsza trasa pomiędzy wszystkimi parami punktów: {{cmd|v.net.allpairs|version=70}}
* Wyznaczanie podsieci (tworzenie podsieci, np. police station zones): {{cmd|v.net.alloc|version=70}}
* Strefy jednakowych odległości (ze środków): {{cmd|v.net.iso|version=70}}
* Obliczanie mostów i punktów artykulacji: {{cmd|v.net.bridge|version=70}}
* Computes degree, centrality, betweeness, closeness and eigenvector centrality measures: {{cmd|v.net.centrality|version=70}}
* Obliczanie dobrze i słabo połączonych komponentów: {{cmd|v.net.components|version=70}}
* Obliczanie stopnia połączenia pomiędzy dwoma zestawami punktów: {{cmd|v.net.connectivity|version=70}}
* Obliczanie najkrótszej drogi w sieci pomiędzy zadanymi zestawami obiektów: {{cmd|v.net.distance|version=70}}
* Obliczanie maksymalnego przepływu pomiędzy dwoma zestawami punktów: {{cmd|v.net.flow|version=70}}
* Obliczanie minimalnego drzewa rozpinającego: {{cmd|v.net.spanningtree|version=70}}
* Minimalne drzewa Steinera (star-like connections, e.g. broadband cable connections): {{cmd|v.net.steiner|version=70}}
* Znajdowanie najkrótszej drogi z użyciem rozkładów jazdy: {{cmd|v.net.timetable|version=70}}
* Analizy komiwojażera (round trip): {{cmd|v.net.salesman|version=70}}

Vector directions are defined by the digitizing direction (a-->--b). You can navigate either omnidirectionally or differently in each directions as both directions are supported. Network modules provide parameters to assign attribute columns to the forward and backward direction. To see how a vector is directed, use the "display" parameter of {{cmd|d.vect}} (set display=dir).
Use [[Turntable]] to assign costs to turns on the network.

* strona pomocy {{cmd|vectorintro}} "vector map processing and network analysis"

== Przykład: Najkrótsza droga ==

* zobacz strony opisujące {{cmd|v.net.path}} i {{cmd|d.path}}

== Najważniejsze parametry ==

* '''input''' - This is the name of input vector map or data source for direct OGR access.

* '''output''' - This is the name for output vector map.

* '''type''' - This parameter defines arc type, which can be line or boundary.

* '''alayer''' - This parameter is a number and defines the arc layer. Vector features can have category values in different layers. This number determines which layer to use. When used with direct OGR access this is the layer name.

* '''nlayer''' - This parameter is a number and defines the node layer. Vector features can have category values in different layers. This number determines which layer to use. When used with direct OGR access this is the layer name.

* '''afcolumn''' - This is name of the cost column for moving in forward direction or forward and backward directions together.

* '''abcolumn''' - This is name of the cost column for moving in backward direction.

* '''ncolumn''' - This is name of the cost column for moving through nodes.

If you are not familiar with layers concept in GRASS see [[Vector Database Management]].

== Nowe pomysły ==

* [[Vector network analysis ideas]] (pomóż w realizacji)

=== Zrzuty ekranu z GRASS GIS 7 ===

[[Image:Grass7_vector_network_tool_salesman.png|center|600px|thumb|Travelling salesman ({{cmd|v.net.salesman}})]]

[[Image:Grass7_vector_network_tool_alloc.png|center|600px|thumb|Subsets for nearest centers ({{cmd|v.net.alloc}})]]

[[Image:wxgui-vnet-alloc.png|center|600px|thumb|Subsets for nearest centers ({{cmd|v.net.alloc}})]]

Zobacz też
* [[WxGUI Vector Network Analysis Tool]]
* więcej zrzutów ekranu [https://grass.osgeo.org/screenshots/vector/ ze strony GRASS]

=== Zrzuty ekranu ze starszej wersji GRASS 5 ===

<center>
{|
| [[Image:V.net.iso.png|center|400px|thumb|{{cmd|v.net.iso}} - Split net to bands between cost isolines (direction from centre). Costs of centre node are used in calculation.]]
|[[Image:V.net.alloc.png|center|400px|thumb|{{cmd|v.net.alloc}} - Allocates subnets for nearest centres (direction from centre). Costs of centre node are used in calculation.]]
|-
|[[Image:D.path.jpg|center|400px|thumb|{{cmd|d.path}} - Znajduje najkrótszą drogę dla wybranych początkowych i końcowych punktów.]]
| 
|}
</center>

== See also ==

* [[Turntable]]
* [[GSoC Network Analysis]]: wiele nowych modułów!

== Linki zewnętrzne ==

* [http://www.ossgis.co.cc/2009/01/grass-gis-network-analysis-subnets.html GRASS GIS: Network Analysis (Subnets within a vector network)]

[[Category:Documentation]]
[[Category:Vector]]
[[Category:Languages/pl]]
[[Category:Network Analysis]]

GRASS-Wiki/pl

2016-08-21T17:48:27Z

⚠️MilenaN: /* Witaj w Wiki użytkowników GRASS GIS */ - update to en version

__NOTOC__
{| width="100%"
|-
| width="68%" style="vertical-align:top" |
<div style="margin:0; margin-right:10px; border:1px solid #dfdfdf; background-color:#f8f8ff;">

<div style="padding:0.3em 1em 0.7em 1em;">

[[Image:grasslogo_vector_small.png|right]]

=== Witaj w Wiki użytkowników GRASS GIS ===

[http://grass.osgeo.org Geographic Resources Analysis Support System], zwykle zwany '''GRASS-em''',
jest Systemem Informacji Geograficznej ([http://en.wikipedia.org/wiki/Geographic_information_system GIS]) wykorzystywanym do zarządzania i analiz danych przestrzennych, przetwarzania obrazów satelitarnych i zdjęć lotniczych, produkcji prezentacji graficznych oraz map, modelowania przestrzennego i wizualizacji. GRASS jest obecnie używany przez środowiska akademickie i komercyjne na całym śwecie, jak i przez wiele agencji rządowych i firm zajmujących się stanem środowiska naturalnego. GRASS GIS jest projektem [http://www.osgeo.org Open Source Geospatial Foundation]. <br>
Ta WIKI stanowi oficjalną stronę społeczności użytkowników projektu GRASS GIS. Aby zobaczyć przykłady analiz, idź do [http://grass.osgeo.org/screenshots/index.php Galerii GRASS GIS].

Na tej Wiki możesz znaleźć informacje o GRASS-ie, dokumenty oraz dodatkowe programy związane z projektem, a także rozbudowywać je. Aby móc edytować Wiki, zaloguj się - link w prawym górnym rogu.
</div>
</div>
<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#FFE5E5;">

'''Gorący temat:'''
* <font size="+1">[http://trac.osgeo.org/grass/wiki/Release/7.0.4-News '''GRASS GIS 7.0.4''' już jest!]</font> {{bullet}} [https://grass.osgeo.org/download/software/#g70x pobierz] {{bullet}} [https://trac.osgeo.org/grass/report/19 zgłoś problem]
* <font size="+1">[[GRASS Community Sprint Bonn 2016]]</font>
* [http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures Lista nowych funkcji w GRASS GIS 7] ([https://grass.osgeo.org/download/software/#g70x pomóż nam testować])
* <font size="+0">[https://grass.osgeo.org/news/45/15/GRASS-GIS-6-4-5-released/ '''GRASS GIS 6.4.5''' is here!]</font> {{bullet}} [https://grass.osgeo.org/download pobierz] {{bullet}} [https://trac.osgeo.org/grass/report/16 zgłoś problem]

* Wypróbuj [[Quick wxGUI tutorial]]
* Temporal support i inne nowe[[Initiatives| Inicjatywy]]
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em
1em 1em 1em; background-color:#f8f8ff;">
==== Dokumentacja i pomoc dla użytkowników ====
* [[GRASS Help|Pomoc GRASS-a i Jak Zacząć]]
* [[GRASS Documents|Szczegółowa dokumentacja GRASS-a]]
* [[Installation Guide|Przewodnik instalacji]] prekompilowanych pakietów binarnych
* [[Faq|FAQ]]
* [[Applications|Zastosowania]] - przykłady użycia GRASS w różnych dyscyplinach
* [[wxGUI]] - Graficzny Interfejs Użytkownika w wxPython'ie
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em

1em 1em 1em; background-color:#f8f8ff;">

==== Społeczność====
* [[GRASS Community|Społeczność GRASS-a]]: Bądź w kontakcie
* [[Applications|Research applications]]: Co inni robią w GRASS-ie
* [[GRASS migration hints|Przejście na System GRASS]]
* [[GRASS Blogger]]
* Zaangażuj się: [[Project jobs|Prace przy projekcie]]
* [http://grass.osgeo.org/wiki/Special:Recentchanges?feed=rss RSS feed] ostatnie zmiany tej Wiki
</div>

<div>Zerknij na mapę użytkowników GRASS GIS na świecie [http://grass.osgeo.org/community/ GRASS GIS User Online]. Jeśli używasz GRASS GIS, dopisz się do mapy.
</div>

<div><p>''[[GRASS-Wiki:Language policy|Przetłumacz tę Wiki]]''</p></div>


| width="38%" style="vertical-align:top" |
<div style="margin:0; border:1px solid #dfdfdf; padding:0em 1em 1em 1em;

background-color:#f8f8ff;">
[[Image:OSGeo 220pix.png|center|220px]]
<center>Projekt Fundacji OSGeo</center>
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:1em 1em 1em 1em; background-color:#f8f8ff;">
[[Image:Btn_donate_SM.gif|center|link=http://grass.osgeo.org/donation.php]]<center>[http://grass.osgeo.org/donation.php Donate via PayPal.com]</center>
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding: 0em 1em 1em 1em;

background-color:#f8f8ff;">
* [http://grass.osgeo.org/screenshots/index.php Galeria Systemu GRASS]
* [http://trac.osgeo.org SVN/trac] Repozytorium Kodu Źródłowego
* [http://grass.osgeo.org/community/support.php Listy mailingowe] i [http://grass.osgeo.org/community/support.php#irc IRC]
* [http://trac.osgeo.org/grass/ Zgłaszanie błędów i życzeń]
* [https://svn.osgeo.org/grass/grass/branches/releasebranch_6_4/COPYING Licencja GNU GPL]
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em;

background-color:#f8f8ff;">

==== Pobierz ====
* [http://grass.osgeo.org/download/ Kod źródłowy i pakiety binarne]
* [[GRASS AddOns|Dodatki Systemu GRASS]]
* [[Promotional material|Materiały promocyjne]]
* [[Sample datasets|Przykładowe zestawy danych]]
* [[Global datasets|Globalne zestawy danych]]
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em;

background-color:#f8f8ff;">

==== Development ====
* [[Compile and Install]] of Source Code
* [[Development|GRASS Development]] intro
* [http://trac.osgeo.org/grass/wiki GRASS-trac]: the development Wiki, bugtracker, source code browser
* [[Release Roadmap]]
* [[GRASS 7 ideas collection]]
* [[GRASS SoC Ideas|Google Summer of Code ideas collection]]
* [http://trac.osgeo.org/grass/wiki/HowToContribute How to contribute to GRASS development] (getting write access and such)
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em;

background-color:#f8f8ff;">
Project Metrics provided by [http://www.ohloh.net/projects/3666 Ohloh].
{{#ohloh: account=3666}}
</div>
|}
{{Trans|Polish|English}}

[[Category:Languages/pl]]

GRASS Community Sprint Bonn 2016

2016-08-16T17:20:24Z

⚠️MilenaN: /* In person */

{{toc|right}}
During the [http://2016.foss4g.org/ FOSS4G 2016] , 21-28 August 2016, [http://en.wikipedia.org/wiki/Bonn Bonn], [https://en.wikipedia.org/wiki/Germany 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)
* [http://2016.foss4g.org/#page9 FOSS4G 2016 Schedule]
* CodeSprint II: Sat 27.08.2016 - Sun 28.08.2016 12:00 a.m

== 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<br>
    '''sponsoring the GRASS project at [http://grass.osgeo.org/donations/ http://grass.osgeo.org/donations/]'''<br>
and, if needed, contact [[User:Neteler|Markus Neteler]] <tt><neteler at osgeo.org></tt>. 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: http://www.basecamp-bonn.de

== Accommodation and Costs ==

* to be defined

== Weather ==

* https://en.wikipedia.org/wiki/Bonn#Climate

== Agenda - What we plan to do ==

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

=== Web site ===
* Migrate the good old CMSMS to Wordpress

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

=== New Releases ===
Minor releases:
* Release GRASS GIS 6.4.6:
** Coordination is done here: http://trac.osgeo.org/grass/wiki/Grass6Planning
** Changes are tracked at: https://trac.osgeo.org/grass/wiki/Release/6.4.6-News
* Release GRASS GIS 7.0.5:
** Coordination is done here: https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.0.5tobebackported
** Changes are tracked at: https://trac.osgeo.org/grass/wiki/Release/7.0.5-News

'''Major release''':
* Release GRASS GIS 7.2.0:
** Coordination is done here: https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.2.0
** Changes are tracked at: https://trac.osgeo.org/grass/wiki/Release/7.2.0-News

=== Documentation and translation ===
* Add examples to manual pages
* Translation of messages
* Translation of Wiki pages

=== Bug squashing ===
* Open bugs concerning GRASS 7: https://trac.osgeo.org/grass/report/19
* {{trac|2864}}: Add link to source code in the documentation pages (almost done, let's finish it!)

=== Improvements ===
* improve r.modis addons
* integrate Google Summer of Code projects (where adequate)
* continue working on OBIA toolchain:
** Testing of mean shift in i.segment
** Finalization of r.object.geometry and its integration into i.segment.uspo
* add R-batch files to OSGeo4W-winGRASS7 see [https://trac.osgeo.org/osgeo4w/ticket/413 osgeo4w/ticket 413]

=== Better integration of git into development ===
* since github/gitlab/bitbucket etc are a valuable and recognized source of new source code, we should be able to receive such contributions easily

... YOUR IDEA HERE ...

== 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 [[User:Lucadelu|Luca Delucchi]] <tt><lucadeluge at gmail com></tt>:

{|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:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=130px|'''Participant '''
|width=100px|'''Country'''
|width=100px|'''Arrival'''
|width=100px|'''Departure'''
|'''Topic'''
|width=75px|'''T-Shirt'''
|'''Notes'''
|-
|1
|[[User:Lucadelu|Luca Delucchi]]
|Italy
| August 21
| August 28
|
| L
|
|-
|2
|[[User:Landa|Martin Landa]]
|Czech Republic
| August 21
| August 28
|
| L
|
|-
|3
|[[User:Neteler|Markus Neteler]]
|Italy
| August 21
| August 28
| Releases, project coordination, bug hunting, getting more ppl involved
| M
|
|-
|4
|[[User:NikosA|Nikos Alexandris]]
|Switzerland
| August 21
| August 28
|
| S or M
|
|-
|5
|[[User:Veroandreo|Veronica Andreo]]
|Argentina
| August 26
| August 28
|
| S
|
|-
|6
|[[User:mlennert|Moritz Lennert]]
|Belgium
| August 21
| August 27
|
| M
|
|-
|7
|[[User:sbl|Stefan Blumentrath]]
|Norway
| August 26
| August 28
|
| L
|
|-
|8
|[[User:MilenaN|Milena Nowotarska]]
|Poland
| August 21
| August 28
|
| M
|
|-
|}

=== Via IRC chat ===

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

{|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:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=130px|'''Participant '''
|width=100px|'''Country'''
|-
|1
|[[User:Ychemin|Yann Chemin]]
|France
|-
|2
|[[User:hellik|Helmut Kudrnovsky]]
|Austria
|-
|}

== Individual Preparation ==

* Bring your own computer
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed ([https://en.wikipedia.org/wiki/File:Schuko_plug_and_socket.png Germany])
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== 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?''
** Contact [[User:Lucadelu|Luca Delucchi]] <tt><lucadeluge at gmail com></tt>

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

GRASS Community Sprint Bonn 2016

2016-08-16T17:17:58Z

⚠️MilenaN: /* In person */ + MilenaN

{{toc|right}}
During the [http://2016.foss4g.org/ FOSS4G 2016] , 21-28 August 2016, [http://en.wikipedia.org/wiki/Bonn Bonn], [https://en.wikipedia.org/wiki/Germany 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)
* [http://2016.foss4g.org/#page9 FOSS4G 2016 Schedule]
* CodeSprint II: Sat 27.08.2016 - Sun 28.08.2016 12:00 a.m

== 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<br>
    '''sponsoring the GRASS project at [http://grass.osgeo.org/donations/ http://grass.osgeo.org/donations/]'''<br>
and, if needed, contact [[User:Neteler|Markus Neteler]] <tt><neteler at osgeo.org></tt>. 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: http://www.basecamp-bonn.de

== Accommodation and Costs ==

* to be defined

== Weather ==

* https://en.wikipedia.org/wiki/Bonn#Climate

== Agenda - What we plan to do ==

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

=== Web site ===
* Migrate the good old CMSMS to Wordpress

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

=== New Releases ===
Minor releases:
* Release GRASS GIS 6.4.6:
** Coordination is done here: http://trac.osgeo.org/grass/wiki/Grass6Planning
** Changes are tracked at: https://trac.osgeo.org/grass/wiki/Release/6.4.6-News
* Release GRASS GIS 7.0.5:
** Coordination is done here: https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.0.5tobebackported
** Changes are tracked at: https://trac.osgeo.org/grass/wiki/Release/7.0.5-News

'''Major release''':
* Release GRASS GIS 7.2.0:
** Coordination is done here: https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.2.0
** Changes are tracked at: https://trac.osgeo.org/grass/wiki/Release/7.2.0-News

=== Documentation and translation ===
* Add examples to manual pages
* Translation of messages
* Translation of Wiki pages

=== Bug squashing ===
* Open bugs concerning GRASS 7: https://trac.osgeo.org/grass/report/19
* {{trac|2864}}: Add link to source code in the documentation pages (almost done, let's finish it!)

=== Improvements ===
* improve r.modis addons
* integrate Google Summer of Code projects (where adequate)
* continue working on OBIA toolchain:
** Testing of mean shift in i.segment
** Finalization of r.object.geometry and its integration into i.segment.uspo
* add R-batch files to OSGeo4W-winGRASS7 see [https://trac.osgeo.org/osgeo4w/ticket/413 osgeo4w/ticket 413]

=== Better integration of git into development ===
* since github/gitlab/bitbucket etc are a valuable and recognized source of new source code, we should be able to receive such contributions easily

... YOUR IDEA HERE ...

== 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 [[User:Lucadelu|Luca Delucchi]] <tt><lucadeluge at gmail com></tt>:

{|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:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=130px|'''Participant '''
|width=100px|'''Country'''
|width=100px|'''Arrival'''
|width=100px|'''Departure'''
|'''Topic'''
|width=75px|'''T-Shirt'''
|'''Notes'''
|-
|1
|[[User:Lucadelu|Luca Delucchi]]
|Italy
| August 21
| August 28
|
| L
|
|-
|2
|[[User:Landa|Martin Landa]]
|Czech Republic
| August 21
| August 28
|
| L
|
|-
|3
|[[User:Neteler|Markus Neteler]]
|Italy
| August 21
| August 28
| Releases, project coordination, bug hunting, getting more ppl involved
| M
|
|-
|4
|[[User:NikosA|Nikos Alexandris]]
|Switzerland
| August 21
| August 28
|
| S or M
|
|-
|5
|[[User:Veroandreo|Veronica Andreo]]
|Argentina
| August 26
| August 28
|
| S
|
|-
|6
|[[User:mlennert|Moritz Lennert]]
|Belgium
| August 21
| August 27
|
| M
|
|-
|7
|[[User:sbl|Stefan Blumentrath]]
|Norway
| August 26
| August 28
|
| L
|
|-
|7
|[[User:MilenaN|Milena Nowotarska]]
|Poland
| August 21
| August 28
|
| M
|
|-
|}

=== Via IRC chat ===

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

{|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:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=130px|'''Participant '''
|width=100px|'''Country'''
|-
|1
|[[User:Ychemin|Yann Chemin]]
|France
|-
|2
|[[User:hellik|Helmut Kudrnovsky]]
|Austria
|-
|}

== Individual Preparation ==

* Bring your own computer
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed ([https://en.wikipedia.org/wiki/File:Schuko_plug_and_socket.png Germany])
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== 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?''
** Contact [[User:Lucadelu|Luca Delucchi]] <tt><lucadeluge at gmail com></tt>

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

Talk:GRASS Community Sprint Vienna 2014

2014-03-31T21:33:05Z

⚠️MilenaN: /* Individual reports */ + Milena

== Reports ==
<center>
[[File:Vienna2014 code sprint panorama tiny.jpg]]<br>
... way more than 50 participants present!
</center>

=== *** NEWS *** ===

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#98ff98;">
First beta release of GRASS GIS 7.0.0:
* Draft announcement: http://trac.osgeo.org/grass/wiki/Release/7.0.0beta-News
* Overview: http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures
* Downloads:
** Source code package: http://grass.osgeo.org/grass70/source/ (grass-7.0.0beta1.tar.gz)
** Binaries: http://grass.osgeo.org/download/
* Source code:
** SVN branch: http://trac.osgeo.org/grass/browser/grass/branches/releasebranch_7_0
** SVN tag: http://trac.osgeo.org/grass/browser/grass/tags/release_20140327_grass_7_0_0beta1
* Development started in April 2008!
</div>

=== Individual reports ===
==== [[User:lucadelu|Luca Delucchi]] ====
* fix ''locn_is_latlong'' function in Python/script/core {{rev|59306}}
* fix ''v.in.geopaparazzi'' {{rev|59310}}
* update ''r.modis'' {{rev|59323}}
* update ''i.oif'' to work with several bands {{rev|59350}} {{rev|59353}} ({{trac|2057}})
* several improvement of ''g.gui.rlisetup'' {{rev|59367}} {{rev|59394}} {{rev|59424}} {{rev|59437}} {{rev|59453}}
* fix problem in r.li.setup using circle to select testing areas {{rev|59413}}

==== [[User:Neteler|Markus Neteler]] ====

* Manual intro {{cmd|helptext|version=70}}: location structure graphics beautified (contributed by Milena Nowotarska)
* demolocation: [http://www.naturalearthdata.com/downloads/110m-cultural-vectors/ country_boundaries] vector map added in {{rev|59303}}
* r.li.*: backport of rewrite in trunk to GRASS 6.4.svn in {{rev|59305}} and 6.5.svn in {{rev|59304}} ({{trac|1214}})
* walking through the [http://trac.osgeo.org/grass/report/19 GRASS 7 bug reports]
* v.what.rast: centroid support added in {{rev|59341}}
* Updated the QGIS Processing for GRASS GIS 7 (in parallel to GRASS GIS 6 support) - submitted to Pirmin and Victor

==== [[User:Landa|Martin Landa]] ====

* Fix db.login on Windows {{rev|59318}} + {{rev|59319}}
* Update history when running module from dialog {{rev|59307}}
* Various fixes relalated to Windows - {{rev|59338}}, {{rev|59347}}
* New <tt>-gtext</tt> switch added - {{rev|59379}}
* Move <tt>r.stream.*</tt> modules from addons to trunk
* Rename <tt>r.statistics2</tt> and <tt>r.statistics3</tt> to <tt>r.stats.zonal</tt> and <tt>r.stats.quantile</tt>

==== [[User:Turek|Stepan Turek]] ====

* WMS fixes {{rev|59312}}, {{rev|59328}} and improvements {{rev|59316}}, {{rev|59325}}, {{rev|59327}}
* WMS windows fix {{trac|1872}}
* wx plot improvements {{rev|59332}}, {{rev|59342}}
* turns support for GRASS - soon to be commited in trunk

==== [[User:Hellik|Helmut Kudrnovsky]] ====

* review of GRASS7-r.stream.*-tools (unifying keywords and options, manuals, typos, ...) - {{rev|59340}} {{rev|59363}} {{rev|59368}} {{rev|59370}} {{rev|59373}} {{rev|59377}} {{rev|59403}} {{rev|59416}} {{rev|59422}} {{rev|59423}} {{rev|59426}} {{rev|59434}} {{rev|59435}} {{rev|59438}} {{rev|59439}} {{rev|59444}} {{rev|59447}}
* review, discuss and close open tickets - {{trac|1418}} {{trac|1428}} {{trac|1940}} {{trac|2144}} {{trac|2153}}

==== [[User:Madi|Margherita Di Leo]] ====

* Together with [[User:Hellik|Helmut Kudrnovsky]] and [[User:Landa|Martin Landa]], review of GRASS7-r.stream.*-tools (unifying keywords and options, manuals, typos, ...) in preparation for their moving to trunk. {{rev|59354}}, {{rev|59371}}, {{rev|59377}}, {{rev|59411}}, {{rev|59419}}, {{rev|59430}}, {{rev|59436}}, {{rev|59446}}.
* update r.basin {{rev|59333}}, {{rev|59508}}, {{rev|59511}}, {{rev|59512}}

==== [[User:MilenaN|Milena Nowotarska]] ====

* Improvements of manual v.split, v.parallel, v.segment {{rev|59355}}, {{rev|59320}}
* location structure graphics beautified
* testing vector modules on winGRASS
* translation continued

== Photos ==

See http://vienna2014.sprint.osgeo.org/2014/03/27/photos.html

== Press release ==

TODO

Talk:GRASS Community Sprint Prague 2013

2013-07-16T16:31:28Z

⚠️MilenaN: /* Milena Nowotarska */

== Participant comments and plans ==

...

=== Joint efforts ===

(see [[GRASS_Community_Sprint_Prague_2013#In_person|here]] for participants' names)

* Creating 3D vector test data (for 3D interpolation) - ES, SG, MN
* Added [[Image_processing#General_introduction|General introduction]] (based on manual of G7/i.vi by Yann Chemin) - MN, MN, YC
* Discussions on Bundle Block Adjustments - YC, ST
* wxGUI refactoring - AP, VP
* Presentation of state of image processing in GRASS 7 - YC, MN
* Presentation of state of Temporal GIS Algebra in GRASS 7 - SG, TL
* ISIS-GRASS bridge port to GRASS7 - YC, VP, ML, MN
* Discussions on potential integration of Rasdaman software as raster data backend - SG, YC, and Jachym (virtually)
* Presentation on vector conflation - TF with discussion
* ...

=== Individual Reports ===

Here the (very incomplete) list of individual efforts:

==== Martin Landa ====

* Community Sprint organization
* OSGeo4W GRASS 6.4.3RC4 package published
* Fix {{cmd|v.pack|version=70}} on MS Windows, {{rev|57117}}
* Fix {{cmd|v.unpack|version=70}} on MS Windows, {{rev|57121}}

==== Markus Neteler ====

* Community Sprint Budget management (available on request)
* r.wf Addon fixed: {{rev|57075}} and {{rev|57076}}
* r.ipso Addon fixed: {{rev|57077}}
* Draft Doxygen'iation of the CDHC [http://grass.osgeo.org/programming7/cdhclib.html library for testing normality & exponentiality]
* Added [[Image_processing#General_introduction|General introduction]] to the image processing wiki/manual page (based on manual of G7/i.vi by Yann Chemin) - MN, MN, YC

==== Yann Chemin ====

* ISIS-GRASS bridge port to GRASS7 (with Vaclav, Martin and MarkusN)
If ISIS (http://isis.astrogeology.usgs.gov) is installed,
GRASS will load it in the background,
the banner and prompt will change to ISIS-GRASS.
Both ISIS and GRASS commands are available at the ISIS-GRASS prompt.

* g.isis3mt exports a ISIS3 template from current location, ported into GRASS 7

* Tested direct access of ISIS3 data into G7, r.in.gdal and r.external both work (tested Mars MOLA and Dawn test_datasets)

* Discussed with Soeren, Vaclav and Jachym about Rasdaman, Voxel lib and Raster handling in Grass 8, we agreed on investigating handling, interfaces and performances.

* Went through the Bundle Block Adjustment files with Stepan

* Landsat 7 chain processing using pyGRASS goes in testing mode with MarkusN and Soeren

* Worked more on r.crater

==== Margherita Di Leo ====

* r.basin ported to G7 {{rev|57091}}, {{rev|57096}}
* r.basin html fixed {{rev|57110}}

==== Markus Metz ====

* r.stream.* modules: clean up before moving from addons to trunk {{rev|57151}}, {{rev|57152}}
* GRASS wiki image processing update (MM, MN, YC)
* standardizing options for v.db.* and db.* modules, updating respective manuals

==== Anne Ghisla aka aghisla ====

* Google Summer of Code live discussions
* v.krige fixed in G7 {{rev|57146}} and following

==== Sören Gebbert aka huhabla ====

* Google Summer of Code Temporal Algebra presentation and implementation support
* Discussion of RASDAMAN GRASS integration
* Discussion and implementation of the new temporal module t.rast.accumulate and the use of a modified version of r.gdd (implemented by Markus Metz) instead of r.mapcalc
* Writing and updating of many temporal modules manual pages
* Implementing a prototype that uses Python multiprocessing and a new display C-library function derived from g.pnmcomp to speedup the image composition in the wx GUI

==== Stepan Turek ====

* Working on Google Summer of Code project
* Went through the Bundle Block Adjustment files with Yann
* Released source code of scatter plot backend to baclend {{rev|57180}} and turns backend {{rev|57179}}
* Discussed GSoC with Martin and Soren

==== Thomas Leppelt ====

* Working on GSoC Project: Temporal Algebra
* Implementing functions for if-statements in the temporal algebra

==== Milena Nowotarska ====

* GUI translation to Polish {{rev|57166}}
* i18n fixes
* winGRASS testing

==== Anna Petrasova ====

* attempts to compile wxPython with wxGTK3/Broadway (HTML5) backend, so far not successfull, see [http://wxpython-users.1045709.n5.nabble.com/wxPython-with-wxGTK3-Broadway-HTML5-based-backend-td5718030.html discussion]
* wxGUI refactoring
* wxGUI design
* toolboxes: discussion, adding <addons> tag

==== Vaclav Petras ====

* compiling wxPython with wxGTK3/Broadway with Anna
* discussion of Rasdaman GRASS integration
* wxGUI refactoring
* wxGUI design
* toolboxes: discussion
* ISIS-GRASS bridge port to GRASS7 with Yann
* discussing wxGUI programming with Stepan
* tests for toolboxes

==== Eva Stopková ====
* debug of plotting variogram output in module v.kriging (not published yet)
* discussion about kriging methods in GRASS GIS with Anne
* discussion about optimalization and testing modules (not published yet) v.kriging (2D/3D kriging) and v.nna (2D/3D Nearest Neighbour Analysis) with Marcus N. and Soeren G.
* improving and debugging other functions of module v.kriging
* numerical testing of v.kriging

==== Tereza Fiedlerová ====
* learning something about GRASS GIS vector modules
* discussion about own QGIS plugin and C++ library for vector conflation and its possible implementation to GRASS
* beginning to write C API for vector conflation library (needed for GRASS implementation)

== Video-conferencing options ==

Q: is Google Hangouts smartphones only?
: ''not sure, but I'm pretty sure you can get a web browser plugin for all major desktop OSs''

Q: do you have to be signed up with a Google+ social media account?
: ''in theory no, but in practice they strongly funnel you that way''

Q: is Jitsi on a desktop computer compatible with G+?
: ''at the text chat level, yes. video and voice via Google Talk, reported to work with Voice, not sure about video''

; [http://www.jitsi.org Jitsi]
: ''It is compatible with GoogleTalk instant messaging (and most other instant messaging including the XMPP RFC like Facebook; Skype is the notable one that it doesn't work with), not sure about GoogleTalk's voice calls, I'd give that a 80% chance of working.
: An interesting side-project Jisti offers its own work-alike free multi-person video chat for XMPP(Jabber compatibles) which is not limited to 10 people: [https://jitsi.org/Projects/JitsiVideobridge VideoBridge]. Given enough bandwidth and a modern desktop CPU acting as the bridge server, you can have someone in a G+ hangout share their desktop to pass through the other members of the video hangout.
: Also there's a functional alpha-release Android client.
: For Jitsi <-> Jitsi video you may need a valid XMPP account. Many (federated in a single grid) providers for that, so it doesn't matter much who. Jitsi run a simple registry at http://jit.si
: All quite interesting possiblies and the development is quite active -- but is it there yet? I'm not sure, probably a not far away "almost"; if so, perhaps we could run the bridge on Adhoc for a few days (can run as an unprivilidged user, needs Java 6, chat "host" user needs shell access to set magic pass word and get the assigned port numbers to plug into their client), or perhaps host it at fsv.cvut.cz? (i.e. locate it at the shortest hop to max number of participants using it) --HB''

Talk:GRASS Community Sprint Prague 2013

2013-07-15T17:20:57Z

⚠️MilenaN: /* Individual Reports */ +Milena

== Participant comments and plans ==

...

=== Joint efforts ===

(see [[GRASS_Community_Sprint_Prague_2013#In_person|here]] for participants' names)

* Creating 3D vector test data (for 3D interpolation) - ES, SG, MN
* Added [[Image_processing#General_introduction|General introduction]] (based on manual of G7/i.vi by Yann Chemin) - MN, MN, YC
* Discussions on Bundle Block Adjustments - YC, ST
* wxGUI refactoring - AP, VP
* Presentation of state of image processing in GRASS 7 - YC, MN
* Presentation of state of Temporal GIS Algebra in GRASS 7 - SG, TL
* ISIS-GRASS bridge port to GRASS7 - YC, VP, ML, MN
* Discussions on potential integration of Rasdaman software as raster data backend - SG, YC, and Jachym (virtually)
* Presentation on vector conflation - TF with discussion
* ...

=== Individual Reports ===

Here the (very incomplete) list of individual efforts:

==== Martin Landa ====

* Community Sprint organization
* OSGeo4W GRASS 6.4.3RC4 package published
* Fix {{cmd|v.pack|version=70}} on MS Windows, {{rev|57117}}
* Fix {{cmd|v.unpack|version=70}} on MS Windows, {{rev|57121}}

==== Markus Neteler ====

* Community Sprint Budget management (available on request)
* r.wf Addon fixed: {{rev|57075}} and {{rev|57076}}
* r.ipso Addon fixed: {{rev|57077}}
* Draft Doxygen'iation of the CDHC [http://grass.osgeo.org/programming7/cdhclib.html library for testing normality & exponentiality]
* Added [[Image_processing#General_introduction|General introduction]] (based on manual of G7/i.vi by Yann Chemin) - MN, MN, YC

==== Yann Chemin ====

* ISIS-GRASS bridge port to GRASS7 (with Vaclav, Martin and MarkusN)
If ISIS (http://isis.astrogeology.usgs.gov) is installed,
GRASS will load it in the background,
the banner and prompt will change to ISIS-GRASS.
Both ISIS and GRASS commands are available at the ISIS-GRASS prompt.

* g.isis3mt exports a ISIS3 template from current location, ported into GRASS 7

* Tested direct access of ISIS3 data into G7, r.in.gdal and r.external both work (tested Mars MOLA and Dawn test_datasets)

* Discussed with Soeren, Vaclav and Jachym about Rasdaman, Voxel lib and Raster handling in Grass 8, we agreed on investigating handling, interfaces and performances.

* Went through the Bundle Block Adjustment files with Stepan

* Landsat 7 chain processing using pyGRASS goes in testing mode with MarkusN and Soeren

* Worked more on r.crater

==== Margherita Di Leo ====

* r.basin ported to G7 {{rev|57091}}, {{rev|57096}}
* r.basin html fixed {{rev|57110}}

==== Markus Metz ====

* r.stream.* modules: clean up before moving from addons to trunk {{rev|57151}}, {{rev|57152}}
* GRASS wiki image processing update (MM, MN, YC)

==== Anne Ghisla aka aghisla ====

* Google Summer of Code live discussions
* v.krige fixed in G7 {{rev|57146}} and following

==== Sören Gebbert aka huhabla ====

* Google Summer of Code Temporal Algebra presentation and implementation support
* Discussion of RASDAMAN GRASS integration
* Discussion and implementation of the new temporal module t.rast.accumulate and the use of a modified version of r.gdd (implemented by Markus Metz) instead of r.mapcalc
* Writing and updating of many temporal modules manual pages

==== Stepan Turek ====

* Working on Google Summer of Code project
* Went through the Bundle Block Adjustment files with Yann

==== Thomas Leppelt ====

* Working on GSoC Project: Temporal Algebra
* Implementing functions for if-statements in the temporal algebra

==== Milena Nowotarska ====

* GUI translation to Polish

== Video-conferencing options ==

Q: is Google Hangouts smartphones only?
: ''not sure, but I'm pretty sure you can get a web browser plugin for all major desktop OSs''

Q: do you have to be signed up with a Google+ social media account?
: ''in theory no, but in practice they strongly funnel you that way''

Q: is Jitsi on a desktop computer compatible with G+?
: ''at the text chat level, yes. video and voice via Google Talk, reported to work with Voice, not sure about video''

; [http://www.jitsi.org Jitsi]
: ''It is compatible with GoogleTalk instant messaging (and most other instant messaging including the XMPP RFC like Facebook; Skype is the notable one that it doesn't work with), not sure about GoogleTalk's voice calls, I'd give that a 80% chance of working.
: An interesting side-project Jisti offers its own work-alike free multi-person video chat for XMPP(Jabber compatibles) which is not limited to 10 people: [https://jitsi.org/Projects/JitsiVideobridge VideoBridge]. Given enough bandwidth and a modern desktop CPU acting as the bridge server, you can have someone in a G+ hangout share their desktop to pass through the other members of the video hangout.
: Also there's a functional alpha-release Android client.
: For Jitsi <-> Jitsi video you may need a valid XMPP account. Many (federated in a single grid) providers for that, so it doesn't matter much who. Jitsi run a simple registry at http://jit.si
: All quite interesting possiblies and the development is quite active -- but is it there yet? I'm not sure, probably a not far away "almost"; if so, perhaps we could run the bridge on Adhoc for a few days (can run as an unprivilidged user, needs Java 6, chat "host" user needs shell access to set magic pass word and get the assigned port numbers to plug into their client), or perhaps host it at fsv.cvut.cz? (i.e. locate it at the shortest hop to max number of participants using it) --HB''

GRASS Community Sprint Prague 2013

2013-06-28T19:59:49Z

⚠️MilenaN: /* In person */

{{toc|right}}
The GRASS GIS [[team]] will organize the '''4th GRASS Developer and Power User Meeting, aka 'GRASS GIS Community Sprint'''' from '''July 12 to July 18, 2013'''. The sprint is following the [http://geoinformatics.fsv.cvut.cz/gwiki/Geoinformatics_FCE_CTU_2013 Geoinformatics conference], 11-12 July 2013, Czech Technical University in {{wikipedia|Prague}}, {{wikipedia|Czech Republic}}.


'''Important dates:'''

* <font color="grey">11 (Thusday) - 12 (Friday) July 2013: [http://geoinformatics.fsv.cvut.cz/gwiki/Geoinformatics_FCE_CTU_2013 Geoinformatics conference]</font>

* '''12 (Friday) - 18 (Thusday) July 2013: GRASS GIS Community Sprint''' @ [http://www.fsv.cvut.cz/ FCE CTU]

== Purpose ==

This fourth edition of the GRASS GIS Community Sprint 2013 is a great occasion for folks to support the development by actively contributing to the source code, manuals or likewise. The '''community''' sprint is a get-together for GRASS project members and supporters and related [http://www.osgeo.org OSGeo] projects to make decisions and tackle larger problems. For this meeting, we welcome people committed to improving the GRASS GIS project and the interfaces to [[QGIS GRASS Cookbook|QGIS]], [[GDAL]], [[PostGIS]], [[R statistics]], [[GRASS and Sextante|Sextante, gvSIG]], OGC Services (esp. [[WPS]]) and more. This includes developers, documenters, bug reporters, translators and others.

For this meeting, we welcome people committed to improving the GRASS GIS and related projects. This includes developers, document writers, wish and bug reporters, translators etc.

== Sponsors ==

We welcome '''financial contributions''' to support the meeting and we are looking for sponsors to cover costs such as meals or to help reducing travelling and accommodation expenses for GRASS developers with far arrival If you are interested to sponsor the GRASS Community Sprint, please read about

:::'''sponsoring the GRASS project at [http://grass.osgeo.org/donations http://grass.osgeo.org/donations]'''

For questions, please contact [[User:Neteler|Markus Neteler]] <tt><neteler at osgeo.org></tt>. Any surplus at the end of the event will be turned over to the GRASS GIS project.

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

We are grateful for the support which we have received to organize this GRASS Community Sprint:


== Timing ==

'''When''': 12-18 July, 2013

Of course you are invited to join or leave the community sprint whenever you want.

'''Duration''': tbd

* Friday (12. July) is day of arrival
** First meeting in the afternoon (after the [http://geoinformatics.fsv.cvut.cz/gwiki/Geoinformatics_FCE_CTU_2013 Geoinformatics conference]) to define the agenda
* Saturday to Wednesday
** Full days
* Thursday (18. July) is day of departure
** Probably hacking for people with a flight later in the evening

== Venue ==
[[Image:logo_cvut.jpg|130px|left]]
Department of Mapping and Cartography<br>
[http://www.fsv.cvut.cz Faculty of Civil Engineering]<br>
[http://www.cvut.cz Czech Technical University in Prague], {{wikipedia|Czech Republic}}<br>
[http://geoinformatics.fsv.cvut.cz/gwiki/Room_B367 Room B367] <br>

'''[http://geoinformatics.fsv.cvut.cz/gwiki/Where_you_can_find_us Location & Transportations]'''

Prague has an international [http://www.prg.aero/en/ airport] and is also reachable by train, bus or car.

== Accommodation and Costs ==

Participants should plan for the following costs:

* The participation is free of charge
* Travel to Prague, variable depending on where you come from
* Accommodation and meals (with the donated sponsorship money we will try to cover some expenses of the participants)
'''Please note''': The currency in Czech Republic is {{wikipedia|Czech crown}} (CZK, koruna, Kč). 100 Czech crowns are about 4 Euros (see [http://www.cnb.cz/en/financial_markets/foreign_exchange_market/exchange_rate_fixing/daily.jsp current rates]).

'''[http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague Accommodation in Prague]'''

:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Masarykova_Kolej_Hotel Masarykova Kolej Hotel]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_DAP Hotel DAP]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_Krystal Hotel Krystal]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Pension_Hanspaulka Pension Hanspaulka]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_Silenzio Hotel Silenzio]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Student_hostels_.28CTU.29 Student hostels (CTU)]
:* Special offer: ''sleeping for free in the kindergarten'' (30min by city urban mass transportation from the university campus, sleeping bag required, kitchen and WC available, no showers, in working days available only from 8 p.m. to 8 a.m.), contact [[User:Landa|Martin Landa]] for details
:* See also http://www.hotel.cz/praha-6/accommodation/

Please let us know your time of arrival and leaving, so we can book for the accommodations and organize the logistics.

Financial support: (partial) travel grants can be payed upon request thanks to our sponsors!

== Weather and Common Item Prices ==

* In July the weather in Prague is usually warm ([http://www.prague-spot.com/climate 20 or more degrees by day])
* A espresso coffee is about 25 CZK (1 euro), a beer (half of liter) in a common pub is around 30 CZK (1 euro 20 cents), can be more in special pubs. In Prague you can have a full meal (see {{wikipedia|Czech cuisine}} for details) for 100 - 150 CZK (4 - 6 euros), but beware of tourist restaurants, the price can easily rise. It's quite easy to find in Prague also Italian or Chinese restaurants.

== Agenda - What we plan to do ==

'''Note:''' The program is generally open for your ideas. Please write an email to the [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developer list] to discuss your contribution.

Further details about the action items you '''find [[Talk:GRASS Community Sprint Prague 2013|here]]''' and below. Topics cover non-technical, semi-technical, and technical issues.

=== Timeline ===

==== Friday, 12 July ====
* ''(time to be defined)'': Kick-off in the Faculty of Civil Engineering, building B, room 367 (3rd floor, [http://geoinformatics.fsv.cvut.cz/gwiki/Where_you_can_find_us map])
* Participants presentation


==== Saturday, 13 July ====

* 9:00-evening


==== Sunday, 14 July ====

* 9:00-evening


==== Monday, 15 July ====

* 9:00-evening


==== Tuesday, 16 July ====

* 9:00-evening


==== Wednesday, 17 July ====

* 9:00-evening
* '''30 YEARS OF GRASS GIS''' party!!

==== Thursday, 18 July ====

* Last meeting
* Farewell and have a good trip home

== Participation ==

We are planning for an attendance of 20 people (i.e., coding places) but of course you are welcome to join us and bring new ideas with you: we'll make more places available. Please add your name here or contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>:

=== In person ===

{|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:#edf9c7; font-size:95%; empty-cells:show;"
!width=50px|'''Number'''
!width=130px|'''Participant '''
!width=100px|'''Country'''
!width=100px|'''Arrival'''
!width=100px|'''Departure'''
!'''Topic'''
!width=75px|'''T-Shirt'''
!'''Notes'''
|-
|1
|[[User:Landa|Martin Landa]]
|Czech Republic
| July 12
| July 18
| Toolbox concept, vector engine in GRASS 7, wxGUI, PostGIS Topology support, 3D topology
| L
|
|-
|2
| [[User:Neteler|Markus Neteler]]
| Italy
| July 12
| July 19
| Preparation of GRASS 7.0 release, automated unit testing on grass.osgeo.org
| M
|
|-
|3
| [[User:Helena|Helena Mitasova]]
| USA
| July 16 pm
| July 18
| Data exchange, metadata, GRASS7 data sets, temporal data
| M
|
|-
|4
| [[User:benducke|Benjamin Ducke]]
| Germany
| July 15 (+/- 1)
| July 18 (+/- 1)
| 3D interpolation in GRASS 7 (GSoC), misc.
| M
|
|-
|5
| [[User:ychemin|Yann Chemin]]
| France
| July 11 at 15.00
| July 16 at 09.55
| image processing, planetary integration
| XXL
|
|-
|6
| [[User:huhabla|Sören Gebbert]]
| Germany
| July 12
| July 16 (pm)
| GRASS GIS Temporal Framework, Temporal GIS Algebra, WPS, visualization and animation of spatio-temporal data
| XL
|
|-
|7
| [[User:annakrat|Anna Petrasova]]
| Czech Republic
| July 11
| July 18
| wxGUI (toolboxes, refactoring, wxNviz, animations)
| M
|
|-
|8
| [[User:wenzeslaus|Vaclav Petras]]
| Czech Republic
| July 11
| July 18
| wxGUI (toolboxes, refactoring), Programmer's manual Doxygen issues
| M
|
|-
|9
| [[User:turek|Štěpán Turek]]
| Czech Republic
| July 11
| July 18
| Scatter Plot, Bundle Adjustment, Turns in vnet.*
| L
|
|-
|10
| [[User:mmetz|Markus Metz]]
| Italy
| July 12
| July 18
| vector engine in GRASS 7, image processing, orthorectification
| L
|
|-
|11
| [[User:mastho|Thomas Leppelt]]
| Germany
| July 12
| July 16
| Temporal GIS Algebra
| M
|
|-
|12
| [[User:Tereza|Tereza Fiedlerová]]
| Czech Republic
| July 11
| July 18
| vector-to-vector conflation
| S
|
|-
|13
| [[User:Eva|Eva Stopková]]
| Slovak Republic
| July 11
| July 18
| 3D kriging, 3D Nearest Neighbour Analysis
| S
|
|-
|14
| <strike>[[User:Madi|Margherita Di Leo]]</strike>
| Italy
|
|
| Pest risk analysis, wildfires, hydrology, documentation
| XL
| Unable to come :-(
|-
|15
|[[User:MilenaN|Milena Nowotarska]]
|Poland
|July 14
|July 18
|translation, wxGUI
|S
|
|-
|16
| ''and you ...''
|
|
|
|
|
|
|-
|}

=== Via IRC chat or hangout===

==== IRC ====
: [irc://freenode/grass #grass] on Freenode

For details, see [[IRC]]

==== Hangout/Videobridge ====

There is the option to use Google+ Hangout, it's limited to 10 people and may require everyone to have G+ social media accounts to participate. (?)

Similarly multi-video conference calls can be done with Skype if the conference call initiator is a paid-up commercial Skype customer.

The FOSS [http://www.jitsi.org Jitsi] VoIP, IM, and video conferencing software produces a trivial to set up [https://jitsi.org/Projects/JitsiVideobridge VideoBridge] server software to the same.

Further discussion on the pros and cons of these can be found on the [[Talk:GRASS_Community_Sprint_Prague_2013|Talk side of this wiki page]].

* [http://www.google.com/+/learnmore/hangouts/ Information on G+ hangout]

Please add yourself here below (please add also your gmail account for G+ hangout):

* [[User:Landa|Martin Landa]], [http://www.timeanddate.com/worldclock/city.html?n=204 timezone]. Gmail is <landa.martin@> expanded
* ...

==== Timing of hangout meetings ====

* Date, time: [http://doodle.com/f2qfqixqeqkkmskh doodle-poll]

=== Collaborative document scratching ===

(Power) users from all over the world are kindly invited to assist with testing of new and existing functionality. To collect results and notes, we set up an interactive, collaborative editing tool (an Etherpad instance) which works in real-time:

Please check http://titanpad.com/grass-sprint-july2013
: (example from last time: http://titanpad.com/I51nq1SrNc)


== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC adapter|power connector adapter}} if needed (Czech Republic: 230V, 50Hz, {{wikipedia|File:Euro-Flachstecker_2.jpg|Type C Europlugs}} are common and also {{wikipedia|File:French_plug_and_socket.jpg|Type E}})
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== Broadcast & Video ==

During the event :)

== Photos ==

Also during the event :)

== FAQ ==

* '''How was it last time?'''
** Very nice, see [[GRASS Community Sprint Genova 2013]]!
* ''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?''
** Contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>

== Press Release ==

''(to be done)''


[[Category: Workshops]]

GRASS-Wiki/pl

2012-11-17T13:39:22Z

⚠️MilenaN: polish translation update

__NOTOC__
{| width="100%"
|-
| width="68%" style="vertical-align:top" |
<div style="margin:0; margin-right:10px; border:1px solid #dfdfdf; background-color:#f8f8ff;">

<div style="padding:0.3em 1em 0.7em 1em;">

[[Image:grasslogo_vector_small.png|right]]

=== Witaj w Wiki użytkowników GRASS GIS ===

[http://grass.osgeo.org Geographic Resources Analysis Support System], zwykle zwany '''GRASS-em''',
jest Systemem Informacji Geograficznej ([http://en.wikipedia.org/wiki/Geographic_information_system GIS]) wykorzystywanym do zarządzania i analiz danych przestrzennych, przetwarzania obrazów satelitarnych i zdjęć lotniczych, produkcji prezentacji graficznych oraz map, modelowania przestrzennego i wizualizacji. GRASS jest obecnie używany przez środowiska akademickie i komercyjne na całym śwecie, jak i przez wiele agencji rządowych i firm zajmujących się stanem środowiska naturalnego. GRASS GIS jest projektem [http://www.osgeo.org Open Source Geospatial Foundation]. <br>
Ta WIKI stanowi oficjalną stronę społeczności użytkowników projektu GRASS GIS. Aby zobaczyć przykłady analiz, idź do [http://grass.osgeo.org/screenshots/index.php Galerii GRASS GIS].

Na tej Wiki możesz znaleźć informacje o GRASS-ie, dokumenty oraz dodatkowe programy związane z projektem, a także rozbudowywać je. Aby móc edytować Wiki, zaloguj się - link w prawym górnym rogu.
</div>
</div>
<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#FFE5E5;">

'''Gorący temat:'''

* '''[http://grass.osgeo.org Strona GRASS GIS w nowej odsłonie!]'''
* <font size="+1">[http://grass.osgeo.org/announces/announce_grass642.html '''GRASS 6.4.2''' został wydany!]</font>
** '''[http://grass.osgeo.org/download/ Pobierz teraz], następnie wypróbuj [[Quick wxGUI tutorial]]'''
* '''[[GRASS Community Sprint Genova 2013]]''' - 2-7 lutego2013, Genova, Włochy
* '''[[PSC election 2012| Wybory PSC 2012]]'''
* '''Nowe [[Initiatives|Inicjatywy]]'''
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em
1em 1em 1em; background-color:#f8f8ff;">
==== Dokumentacja i pomoc dla użytkowników ====
* [[GRASS Help|Pomoc GRASS-a i Jak Zacząć]]
* [[GRASS Documents|Szczegółowa dokumentacja GRASS-a]]
* [[Installation Guide|Przewodnik instalacji]] prekompilowanych pakietów binarnych
* [[Faq|FAQ]]
* [[Applications|Zastosowania]] - przykłady użycia GRASS w różnych dyscyplinach
* [[wxGUI]] - Graficzny Interfejs Użytkownika w wxPython'ie
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em

1em 1em 1em; background-color:#f8f8ff;">

==== Społeczność====
* [[GRASS Community|Społeczność GRASS-a]]: Bądź w kontakcie
* [[Applications|Research applications]]: Co inni robią w GRASS-ie
* [[GRASS migration hints|Przejście na System GRASS]]
* [[GRASS Blogger]]
* Zaangażuj się: [[Project jobs|Prace przy projekcie]]
* [http://grass.osgeo.org/wiki/Special:Recentchanges?feed=rss RSS feed] ostatnie zmiany tej Wiki
</div>

<div>Zerknij na mapę użytkowników GRASS GIS na świecie [http://grass.osgeo.org/community/ GRASS GIS User Online]. Jeśli używasz GRASS GIS, dopisz się do mapy.
</div>

<div><p>''[[GRASS-Wiki:Language policy|Przetłumacz tę Wiki]]''</p></div>


| width="38%" style="vertical-align:top" |
<div style="margin:0; border:1px solid #dfdfdf; padding:0em 1em 1em 1em;

background-color:#f8f8ff;">
[[Image:OSGeo 220pix.png|center|220px]]
<center>Projekt Fundacji OSGeo</center>
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:1em 1em 1em 1em; background-color:#f8f8ff;">
[[Image:Btn_donate_SM.gif|center|link=http://grass.osgeo.org/donation.php]]<center>[http://grass.osgeo.org/donation.php Donate via PayPal.com]</center>
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding: 0em 1em 1em 1em;

background-color:#f8f8ff;">
* [http://grass.osgeo.org/screenshots/index.php Galeria Systemu GRASS]
* [http://trac.osgeo.org SVN/trac] Repozytorium Kodu Źródłowego
* [http://grass.osgeo.org/community/support.php Listy mailingowe] i [http://grass.osgeo.org/community/support.php#irc IRC]
* [http://trac.osgeo.org/grass/ Zgłaszanie błędów i życzeń]
* [https://svn.osgeo.org/grass/grass/branches/releasebranch_6_4/COPYING Licencja GNU GPL]
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em;

background-color:#f8f8ff;">

==== Pobierz ====
* [http://grass.osgeo.org/download/ Kod źródłowy i pakiety binarne]
* [[GRASS AddOns|Dodatki Systemu GRASS]]
* [[Promotional material|Materiały promocyjne]]
* [[Sample datasets|Przykładowe zestawy danych]]
* [[Global datasets|Globalne zestawy danych]]
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em;

background-color:#f8f8ff;">

==== Development ====
* [[Compile and Install]] of Source Code
* [[Development|GRASS Development]] intro
* [http://trac.osgeo.org/grass/wiki GRASS-trac]: the development Wiki, bugtracker, source code browser
* [[Release Roadmap]]
* [[GRASS 7 ideas collection]]
* [[GRASS SoC Ideas|Google Summer of Code ideas collection]]
* [http://trac.osgeo.org/grass/wiki/HowToContribute How to contribute to GRASS development] (getting write access and such)
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em;

background-color:#f8f8ff;">
Project Metrics provided by [http://www.ohloh.net/projects/3666 Ohloh].
{{#ohloh: account=3666}}
</div>
|}
{{Trans|Polish|English}}

[[Category:Languages/pl]]

GRASS-Wiki

2012-10-06T11:41:13Z

⚠️MilenaN: Reverted edits by Samarali (talk) to last revision by Landa

__NOTOC__
{| width="100%"
|-
| width="68%" style="vertical-align:top" |
<div style="margin:0; margin-right:10px; border:1px solid #dfdfdf; background-color:#f8f8ff;">

<div style="padding:0.3em 1em 0.7em 1em;">

[[Image:grasslogo_vector_small.png|right|link=http://grass.osgeo.org]]

=== Welcome to the GRASS GIS Users Wiki ===

{{website|intro/general.php|'''GRASS GIS'''}} is a [http://en.wikipedia.org/wiki/Geographic_information_system Geographic Information System] used for geospatial data management and analysis, image processing, graphics/map production, spatial modeling, and visualization.

On this Wiki, you can get and contribute to GRASS related information, documents and community provided add-ons programs. To edit here, you need to register and login first (see top right link).

For GRASS at a glance, see [[core features]]. For usage examples, see the [http://grass.osgeo.org/screenshots/index.php screenshots gallery] and [[Applications]].
</div>
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#FFE5E5;">
'''What's hot:'''
* [http://grass.osgeo.org/announces/announce_grass642.html '''GRASS 6.4.2''' released!] {{bullet}} [http://grass.osgeo.org/download/ Download it now], then try the [[Quick wxGUI tutorial]]
* '''[[GRASS Community Sprint Prague 2012]]''' - 23-28 May 2012, Prague, Czech Republic
* [[GRASS_SoC_Ideas_2012#Accepted_Ideas|'''We've secured slots for three students in the Google Summer of Code 2012''']] scholarship program!
* Temporal support and other new [[Initiatives]]
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#f8f8ff;">
==== User Documentation and Support ====
* [[GRASS Help|GRASS Help and Getting Started]]
* [[GRASS Documents|In depth GRASS Documentation]]
* [[Installation Guide]] for precompiled binaries
* '''[[Faq|FAQ]] - Frequently Asked Questions'''
* [[Applications]] - use cases of GRASS in various disciplines
* [[wxGUI]] - Graphical User Interface based on wxPython
</div>

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

==== Community ====
* [[GRASS Community]]: Getting in touch
* [[Applications|Research applications]]: What people are doing with GRASS
* [[GRASS migration hints|Migrating to GRASS]]
* [[GRASS Blogger]]
* Get involved: [[Project jobs]]
* [http://grass.osgeo.org/wiki/Special:Recentchanges?feed=rss RSS feed] of recent changes of this Wiki
</div>

<div>Have a look at the GRASS GIS users worldwide [http://grass.osgeo.org/community/ GRASS GIS User Online]. If you operate a GRASS GIS installation, you are welcome to enter your user data there.
</div>

<div><p>''[[GRASS-Wiki:Language policy|Translate this Wiki]]''</p></div>


| width="38%" style="vertical-align:top" |
<div style="margin:0; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#f8f8ff;">
[[Image:OSGeo 220pix.png|center|220px|link=http://www.osgeo.org]]
<center>[http://www.osgeo.org OSGeo] Foundation Project</center>
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:1em 1em 1em 1em; background-color:#f8f8ff;">
[[Image:Btn_donate_SM.gif|center|link=http://grass.osgeo.org/donation.php]]<center>[http://grass.osgeo.org/donation.php Donate]</center>
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#f8f8ff;">
* [http://grass.osgeo.org/screenshots/index.php GRASS Screenshots]
* [http://trac.osgeo.org SVN/trac] Source Code Repository
* [http://grass.osgeo.org/community/support.php Mailing lists] and [http://grass.osgeo.org/community/support.php#irc IRC]
* [http://trac.osgeo.org/grass/ Report errors or wishes]
* [https://svn.osgeo.org/grass/grass/branches/releasebranch_6_4/COPYING Licensed under GNU GPL]
</div>

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

==== Download ====
* [http://grass.osgeo.org/download/ Source code and binaries]
* '''[[GRASS AddOns]]'''
* [[Promotional material]]
* [[Sample datasets]]
* [[Global datasets]]
</div>

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

==== Development ====
* [[Compile and Install]] of Source Code
* [[Development|GRASS Development]] intro
* [http://trac.osgeo.org/grass/wiki GRASS-trac]: the development Wiki, bugtracker, source code browser
* [[Release Roadmap]]
* [[GRASS 7 ideas collection]]
* [[GRASS SoC Ideas|Google Summer of Code ideas collection]]
* [http://trac.osgeo.org/grass/wiki/HowToContribute How to contribute to GRASS development] (getting write access and such)
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#f8f8ff;">
Project Metrics provided by [http://www.ohloh.net/projects/3666 Ohloh].

{{#widget:Ohloh Project|id=3666|type=partner_badge}}
</div>
|}

WxNviz/pl

2012-09-21T07:48:42Z

⚠️MilenaN: update to En version

Z powrotem do strony [[WxPython-based GUI for GRASS|wxGUI]].

Zobacz również [http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Nviz.html instrukcję] do wxNviz.

'''wxNviz''' jest rozszerzeniem [[wxGUI]] pozwalającym na realistyczne renderowanie multiple surfaces (danych rastrowych) w przestrzeni 3D z możliwością kolorowania tematycznego, nakładania danych wektorowych 2D na powierzchnie, przestrzennego wyświetlania danych wektorowych 3D oraz wizualizację danych volume (danych rastrowych 3D).
__TOC__
== Zrzuty ekranowe ==
<center>
<gallery perrow=3 widths=200>
Image:Wxnviz-alpha-0.png|2008-06-27: Display raster map from layer tree in 2.5D (surface)
Image:Wxnviz-alpha-1.png|2008-07-05: Dodana obsługa danych wektorowych (linie 2D)
Image:Wxnviz-alpha-2.png|2008-07-26: Obsługa punktowych danych wektorowych
Image:Wxnviz-alpha-3.png|2008-08-02: Obsługa danych wektorowych 3D
Image:Wxnviz-alpha-4.png|2008-08-09: Wstępna obsługa danych volumetrycznych
Image:Wxnviz-lmgr.png|2010-05-31: 3D view tools window integrated into Layer Manager
Image:Wxnviz-light.png|Lighting control panel in Layer Manager (2010-06-17)
Image:Wxnviz-fringe.png|Fringe control panel in Layer Manager (2010-06-23)
Image:Wxnviz-redirect.png|Redirect messages to wxGUI (2010-08-08)
Image:Wxnviz-volumes.png|Displaying raster (surface), 2D vector and 3D raster (volume) in the 3D space (2010-08-16)
Image:WxNviz surface page.png|Surface page of WxNviz modified (2011-06-02)
Image:WxNviz_constant_surface_page.png|Constant surface page added (2011-06-02)
Image:WxNviz_lighting.png|Lighting fixed (2011-05-02)
Image:WxNviz_cutting_planes_1.png|Cutting planes (shading blend) (2011-06-10)
Image:WxNviz_cutting_planes_2.png|Cutting planes (shading top color) (2011-06-10)
Image:WxNviz_view_page.png|View page modified (2011-06-10)
Image:Nviz_cmd_cutting_planes.png‎|Picture of surfaces cut by two planes (generated by nviz_cmd) (2011-06-30)
Image:WxNviz_generate_command.png‎|Command for nviz_cmd generated by wxNviz (2011-07-01)
Image:WxNviz_north_arrow.png‎|North Arrow implemented (2011-07-08)
Image:WxNviz_volumes.png‎|Colored isosurfaces with transparency (2011-07-08)
Image:WxNviz_volume_slices_1.png‎|Partially transparent slice (2011-07-14)
Image:WxNviz_volume_slices_2.png‎|Combination of slices and isosurface (2011-07-14)
Image:WxNviz_overlays.png‎|Raster legend, text label and north arrow (2011-07-22)
Image:WxNviz_thematic_points_colors‎.png|Thematic mapping (colors) for points (2011-08-05)
Image:WxNviz_colorrules_dialog.png|Dialog for {{cmd|v.colors}} opened from 3D view (2011-08-05)
</gallery>
</center>

== Animacje ==

{{YouTube|AByFPKHvgu4|desc=Using fly-through mode for creating animation}}

== Tutoriale wideo ==

{{YouTube|ib1-mBbWkv4|desc=Loading data, settings layer properties}}
{{YouTube|ZLDstyumxv0|desc=Wizualizacja sieci i strzałki północy}}
{{YouTube|CmK-fEyf2SY|desc=3D raster maps (volumes) in the space (isosurface and slice mode)}}
{{YouTube|13wj5KWEweE|desc=Color thematic mapping}}

=== Starsze tutoriale (2010) ===

{{YouTube|Ej_rBc9sgvE|desc=Loading data, settings layer properties}}
{{YouTube|iWyaBL2Krto|desc=Visualizing fringes}}
{{YouTube|ioE_hHMHqKg|desc=3D raster maps (volumes) in the space}}

== Pomysły ==

* Mgła (zobacz [http://gpwiki.org/index.php/OpenGL:Tutorials:Tutorial_Framework:Light_and_Fog], [http://www.swiftless.com/tutorials/opengl/fog.html], [http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=16])
* Vertical labels (take from geonames.org point data): like in http://tev.fbk.eu/marmota/blog/?p=82
* Second interactive light source for isosurface visualization
* Tick marks and coordinate values to x,y,z axis when drawing fringe

<strike></strike>

== Znane problemy ==

#List of [http://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~wxNviz open] and [http://trac.osgeo.org/grass/query?status=assigned&status=closed&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~wxNviz closed] tickets
#<strike>Adding vector data crashes wxGUI on Mac</strike>
#<strike>Viewing height sometimes sets to 1 after switching to 2D and back to 3D View (or with the simultaneous 2D view - very nice feature) and even after View is reset, it keeps getting back at 1 each time the slider is touched</strike>
#:Fixed in {{rev|46208}}
#Adding draw, draw current and clear button may be useful
#Thematic mapping is available in GRASS 7 only
#Display region in 3D does not change accordingly to display region in 2D in version <= 6.5
#Appearance:
## I <strike>need to click View tab to get the arrow draw, same for the scale bar </strike>
##add legend > OK: nothing gets drawn in 3D but the legend shows up when I switch to 2D but when I clicked delete scalebar (which was not drawn), my surface disapeared but the legend showed up along with white and black background (which I assume was supposed to be transparent, because when I moved the legend the surface was under it - we already discussed this, it may be my problem, because it works for Michael).
#General
##<strike>when I go from 3D view to 2D and then back to 3D I lose most of my settings </strike>
##<strike>similarly, when I add volume to Map layers I lose my view settings and the 3D view goes back to default </strike>
#Volumes:
##change of region by g.region seems to be ignored (or I missed something), I had to restart GRASS with the new region to get the 3D region for volumes right. Given that the default top, botom is 1,0, if GRASS starts with the default 3D region settings volumes do not work because there is just one level.
##<strike>isosurfaces work with my terrestrial lidar data but the slices don't, it seems that it is due my resolution being 0.3m, when I change it to 1m I get at least some limited slicing
###this may be in ogsf becuase slices in nviz do not work with this data either </strike>
#<strike>changing color to constant did not change the color of the isosurface</strike>

== Google Summer of Code ==

=== [[wxNviz GSoC 2008|2008]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#wxNvizdevelopmentforenhanced34Dvisualizationandanalysis Zaakceptowany projekt Google Summer of Code 2008]

=== [[wxNviz GSoC 2010|2010]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#wxNvizdevelopmentforenhanced34Dvisualizationandanalysis Zaakceptowany projekt Google Summer of Code 2010]

=== [[wxNviz GSoC 2011|2011]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#CompletionofwxGUINvizextensionfor3DdatavisualizationinGRASSGIS Accepted Google Summer of Code 2011 project]

== Zobacz również ==

* http://lists.osgeo.org/pipermail/grass-dev/2008-February/035792.html

{{Trans|Polish|English}}
{{WxGUI}}
[[Category:Languages/pl]]

Vector network analysis/pl

2012-09-10T12:42:15Z

⚠️MilenaN: /* Zaimplementowane algorytmy */

= Vector network analysis =

GRASS provides support for vector network analysis using the [http://trac.osgeo.org/grass/browser/grass/trunk/lib/vector/dglib/ DGlib] Directed Graph Library.

== Zaimplementowane algorytmy ==

Poniższe algorytmy są zaimplementowane (w GRASS 6.5+):

* Utrzymanie sieci: {{cmd|v.net|version=70}}
* Najkrótsza trasa: {{cmd|d.path|version=64}} and {{cmd|v.net.path|version=70}}
* Najkrótsza trasa pomiędzy wszystkimi parami punktów: {{cmd|v.net.allpairs|version=70}}
* Wyznaczanie podsieci (tworzenie podsieci, np. police station zones): {{cmd|v.net.alloc|version=70}}
* Strefy jednakowych odległości (ze środków): {{cmd|v.net.iso|version=70}}
* Obliczanie mostów i punktów artykulacji: {{cmd|v.net.bridge|version=70}}
* Computes degree, centrality, betweeness, closeness and eigenvector centrality measures: {{cmd|v.net.centrality|version=70}}
* Obliczanie dobrze i słabo połączonych komponentów: {{cmd|v.net.components|version=70}}
* Obliczanie stopnia połączenia pomiędzy dwoma zestawami punktów: {{cmd|v.net.connectivity|version=70}}
* Obliczanie najkrótszej drogi w sieci pomiędzy zadanymi zestawami obiektów: {{cmd|v.net.distance|version=70}}
* Obliczanie maksymalnego przepływu pomiędzy dwoma zestawami punktów: {{cmd|v.net.flow|version=70}}
* Obliczanie minimalnego drzewa rozpinającego: {{cmd|v.net.spanningtree|version=70}}
* Minimalne drzewa Steinera (star-like connections, e.g. broadband cable connections): {{cmd|v.net.steiner|version=70}}
* Znajdowanie najkrótszej drogi z użyciem rozkładów jazdy: {{cmd|v.net.timetable|version=70}}
* Analizy komiwojażera (round trip): {{cmd|v.net.salesman|version=70}}

Vector directions are defined by the digitizing direction (a-->--b). You can navigate either omnidirectionally or differently in each directions as both directions are supported. Network modules provide parameters to assign attribute columns to the forward and backward direction. To see how a vector is directed, use the "display" parameter of {{cmd|d.vect}} (set display=dir).

* see the {{cmd|vectorintro}} "vector map processing and network analysis" help page

== Example: Shortest path routing ==

* zobacz strony opisujące {{cmd|v.net.path}} i {{cmd|d.path}}

== Nowe pomysły ==

* [[Vector network analysis ideas]] (pomóż w realizacji)

== Zrzuty ekranu ==
* more screenshots [http://grass.osgeo.org/screenshots/vector.php from the GRASS website]

[[Image:V.net.iso.png|center|600px|thumb|{{cmd|v.net.iso}} - Split net to bands between cost isolines (direction from centre). Costs of centre node are used in calculation.]]

[[Image:V.net.alloc.png|center|600px|thumb|{{cmd|v.net.alloc}} - Allocates subnets for nearest centres (direction from centre). Costs of centre node are used in calculation.]]

[[Image:D.path.jpg|center|600px|thumb|{{cmd|d.path}} - Find shortest path for selected starting and ending node.]]

== See also ==

* [[GSoC Network Analysis]]: many new modules!

== Linki zewnętrzne ==

* [http://www.ossgis.co.cc/2009/01/grass-gis-network-analysis-subnets.html GRASS GIS: Network Analysis (Subnets within a vector network)]

[[Category:Documentation]]
[[Category:Vector]]
[[Category:Languages/pl]]

Vector network analysis/pl

2012-09-10T12:37:51Z

⚠️MilenaN: /* Zaimplementowane algorytmy */ pl translation

= Vector network analysis =

GRASS provides support for vector network analysis using the [http://trac.osgeo.org/grass/browser/grass/trunk/lib/vector/dglib/ DGlib] Directed Graph Library.

== Zaimplementowane algorytmy ==

Poniższe algorytmy są zaimplementowane (w GRASS 6.5+):

* Utrzymanie sieci: {{cmd|v.net|version=70}}
* Najkrótsza trasa: {{cmd|d.path|version=64}} and {{cmd|v.net.path|version=70}}
* Najkrótsza trasa pomiędzy wszystkimi parami punktów: {{cmd|v.net.allpairs|version=70}}
* Wyznaczanie podsieci (tworzenie podsieci, np. police station zones): {{cmd|v.net.alloc|version=70}}
* Jednakowe odległości (ze środków): {{cmd|v.net.iso|version=70}}
* Obliczanie mostów i punktów artykulacji: {{cmd|v.net.bridge|version=70}}
* Computes degree, centrality, betweeness, closeness and eigenvector centrality measures: {{cmd|v.net.centrality|version=70}}
* Obliczanie dobrze i słabo połączonych komponentów: {{cmd|v.net.components|version=70}}
* Obliczanie stopnia połączenia pomiędzy dwoma zestawami punktów: {{cmd|v.net.connectivity|version=70}}
* Obliczanie najkrótszej drogi w sieci pomiędzy zadanymi zestawami obiektów: {{cmd|v.net.distance|version=70}}
* Obliczanie maksymalnego przepływu pomiędzy dwoma zestawami punktów: {{cmd|v.net.flow|version=70}}
* Obliczanie minimalnego drzewa rozpinającego: {{cmd|v.net.spanningtree|version=70}}
* Minimalne drzewa Steinera (star-like connections, e.g. broadband cable connections): {{cmd|v.net.steiner|version=70}}
* Znajdowanie najkrótszej drogi z użyciem rozkładów jazdy: {{cmd|v.net.timetable|version=70}}
* Analizy komiwojażera (round trip): {{cmd|v.net.salesman|version=70}}

Vector directions are defined by the digitizing direction (a-->--b). You can navigate either omnidirectionally or differently in each directions as both directions are supported. Network modules provide parameters to assign attribute columns to the forward and backward direction. To see how a vector is directed, use the "display" parameter of {{cmd|d.vect}} (set display=dir).

* see the {{cmd|vectorintro}} "vector map processing and network analysis" help page

== Example: Shortest path routing ==

* zobacz strony opisujące {{cmd|v.net.path}} i {{cmd|d.path}}

== Nowe pomysły ==

* [[Vector network analysis ideas]] (pomóż w realizacji)

== Zrzuty ekranu ==
* more screenshots [http://grass.osgeo.org/screenshots/vector.php from the GRASS website]

[[Image:V.net.iso.png|center|600px|thumb|{{cmd|v.net.iso}} - Split net to bands between cost isolines (direction from centre). Costs of centre node are used in calculation.]]

[[Image:V.net.alloc.png|center|600px|thumb|{{cmd|v.net.alloc}} - Allocates subnets for nearest centres (direction from centre). Costs of centre node are used in calculation.]]

[[Image:D.path.jpg|center|600px|thumb|{{cmd|d.path}} - Find shortest path for selected starting and ending node.]]

== See also ==

* [[GSoC Network Analysis]]: many new modules!

== Linki zewnętrzne ==

* [http://www.ossgis.co.cc/2009/01/grass-gis-network-analysis-subnets.html GRASS GIS: Network Analysis (Subnets within a vector network)]

[[Category:Documentation]]
[[Category:Vector]]
[[Category:Languages/pl]]

Vector network analysis/pl

2012-09-10T11:53:29Z

⚠️MilenaN: pl translation

= Vector network analysis =

GRASS provides support for vector network analysis using the [http://trac.osgeo.org/grass/browser/grass/trunk/lib/vector/dglib/ DGlib] Directed Graph Library.

== Zaimplementowane algorytmy ==

Poniższe algorytmy są zaimplementowane (w GRASS 6.5+):

* Utrzymanie sieci: {{cmd|v.net|version=70}}
* Najkrótsza trasa: {{cmd|d.path|version=64}} and {{cmd|v.net.path|version=70}}
* Najkrótsza trasa pomiędzy wszystkimi parami punktów: {{cmd|v.net.allpairs|version=70}}
* Wyznaczanie podsieci (tworzenie podsieci, np. police station zones): {{cmd|v.net.alloc|version=70}}
* Jednakowe odległości (ze środków): {{cmd|v.net.iso|version=70}}
* Computes bridges and articulation points: {{cmd|v.net.bridge|version=70}}
* Computes degree, centrality, betweeness, closeness and eigenvector centrality measures: {{cmd|v.net.centrality|version=70}}
* Obliczanie dobrze i słabo połączonych komponentów: {{cmd|v.net.components|version=70}}
* Computes vertex connectivity between two sets of nodes: {{cmd|v.net.connectivity|version=70}}
* Obliczanie najkrótszej drogi w sieci pomiędzy zadanymi zestawami obiektów: {{cmd|v.net.distance|version=70}}
* Obliczanie maksymalnego przepływu pomiędzy dwoma zestawami punktów: {{cmd|v.net.flow|version=70}}
* Computes minimum spanning tree: {{cmd|v.net.spanningtree|version=70}}
* Minimum drzewa Steinera (star-like connections, e.g. broadband cable connections): {{cmd|v.net.steiner|version=70}}
* Znajdowanie najkrótszej drogi z użyciem rozkładów jazdy: {{cmd|v.net.timetable|version=70}}
* Analizy komiwojażera (round trip): {{cmd|v.net.salesman|version=70}}

Vector directions are defined by the digitizing direction (a-->--b). You can navigate either omnidirectionally or differently in each directions as both directions are supported. Network modules provide parameters to assign attribute columns to the forward and backward direction. To see how a vector is directed, use the "display" parameter of {{cmd|d.vect}} (set display=dir).

* see the {{cmd|vectorintro}} "vector map processing and network analysis" help page

== Example: Shortest path routing ==

* zobacz strony opisujące {{cmd|v.net.path}} i {{cmd|d.path}}

== Nowe pomysły ==

* [[Vector network analysis ideas]] (pomóż w realizacji)

== Zrzuty ekranu ==
* more screenshots [http://grass.osgeo.org/screenshots/vector.php from the GRASS website]

[[Image:V.net.iso.png|center|600px|thumb|{{cmd|v.net.iso}} - Split net to bands between cost isolines (direction from centre). Costs of centre node are used in calculation.]]

[[Image:V.net.alloc.png|center|600px|thumb|{{cmd|v.net.alloc}} - Allocates subnets for nearest centres (direction from centre). Costs of centre node are used in calculation.]]

[[Image:D.path.jpg|center|600px|thumb|{{cmd|d.path}} - Find shortest path for selected starting and ending node.]]

== See also ==

* [[GSoC Network Analysis]]: many new modules!

== Linki zewnętrzne ==

* [http://www.ossgis.co.cc/2009/01/grass-gis-network-analysis-subnets.html GRASS GIS: Network Analysis (Subnets within a vector network)]

[[Category:Documentation]]
[[Category:Vector]]
[[Category:Languages/pl]]

Vector network analysis/pl

2012-09-10T11:33:52Z

⚠️MilenaN: pl translation

= Vector network analysis =

GRASS provides support for vector network analysis using the [http://trac.osgeo.org/grass/browser/grass/trunk/lib/vector/dglib/ DGlib] Directed Graph Library.

== Zaimplementowane algorytmy ==

Poniższe algorytmy są zaimplementowane (w GRASS 6.5+):

* Utrzymanie sieci: {{cmd|v.net|version=70}}
* Najkrótsza droga: {{cmd|d.path|version=64}} and {{cmd|v.net.path|version=70}}
* Najkrótsza droga pomiędzy wieloma parami punktów {{cmd|v.net.allpairs|version=70}}
* Allocation of sources (tworzenie podsieci, np. police station zones): {{cmd|v.net.alloc|version=70}}
* Jednakowe odległości (ze środków): {{cmd|v.net.iso|version=70}}
* Computes bridges and articulation points: {{cmd|v.net.bridge|version=70}}
* Computes degree, centrality, betweeness, closeness and eigenvector centrality measures: {{cmd|v.net.centrality|version=70}}
* Computes strongly and weakly connected components: {{cmd|v.net.components|version=70}}
* Computes vertex connectivity between two sets of nodes: {{cmd|v.net.connectivity|version=70}}
* Computes shortest distance via the network between the given sets of features: {{cmd|v.net.distance|version=70}}
* Computes the maximum flow between two sets of nodes: {{cmd|v.net.flow|version=70}}
* Computes minimum spanning tree: {{cmd|v.net.spanningtree|version=70}}
* Minimum Steiner trees (star-like connections, e.g. broadband cable connections): {{cmd|v.net.steiner|version=70}}
* Znajdowanie najkrótszej drogi z użyciem rozkładów jazdy: {{cmd|v.net.timetable|version=70}}
* Traveling salesman (round trip): {{cmd|v.net.salesman|version=70}}

Vector directions are defined by the digitizing direction (a-->--b). You can navigate either omnidirectionally or differently in each directions as both directions are supported. Network modules provide parameters to assign attribute columns to the forward and backward direction. To see how a vector is directed, use the "display" parameter of {{cmd|d.vect}} (set display=dir).

* see the {{cmd|vectorintro}} "vector map processing and network analysis" help page

== Example: Shortest path routing ==

* zobacz strony opisujące {{cmd|v.net.path}} i {{cmd|d.path}}

== Nowe pomysły ==

* [[Vector network analysis ideas]] (pomóż w realizacji)

== Zrzuty ekranu ==
* more screenshots [http://grass.osgeo.org/screenshots/vector.php from the GRASS website]

[[Image:V.net.iso.png|center|600px|thumb|{{cmd|v.net.iso}} - Split net to bands between cost isolines (direction from centre). Costs of centre node are used in calculation.]]

[[Image:V.net.alloc.png|center|600px|thumb|{{cmd|v.net.alloc}} - Allocates subnets for nearest centres (direction from centre). Costs of centre node are used in calculation.]]

[[Image:D.path.jpg|center|600px|thumb|{{cmd|d.path}} - Find shortest path for selected starting and ending node.]]

== See also ==

* [[GSoC Network Analysis]]: many new modules!

== Linki zewnętrzne ==

* [http://www.ossgis.co.cc/2009/01/grass-gis-network-analysis-subnets.html GRASS GIS: Network Analysis (Subnets within a vector network)]

[[Category:Documentation]]
[[Category:Vector]]

Vector network analysis/pl

2012-09-10T11:28:37Z

⚠️MilenaN: /* Nowe pomysły */ translated to pl

= Vector network analysis =

GRASS provides support for vector network analysis using the [http://trac.osgeo.org/grass/browser/grass/trunk/lib/vector/dglib/ DGlib] Directed Graph Library.

== Implemented algorithms ==

The following algorithms are implemented (GRASS 6.5+):

* Utrzymanie sieci: {{cmd|v.net|version=70}}
* Najkrótsza droga: {{cmd|d.path|version=64}} and {{cmd|v.net.path|version=70}}
* Najkrótsza droga pomiędzy wieloma parami punktów {{cmd|v.net.allpairs|version=70}}
* Allocation of sources (create subnetworks, e.g. police station zones): {{cmd|v.net.alloc|version=70}}
* Iso-distances (from centers): {{cmd|v.net.iso|version=70}}
* Computes bridges and articulation points: {{cmd|v.net.bridge|version=70}}
* Computes degree, centrality, betweeness, closeness and eigenvector centrality measures: {{cmd|v.net.centrality|version=70}}
* Computes strongly and weakly connected components: {{cmd|v.net.components|version=70}}
* Computes vertex connectivity between two sets of nodes: {{cmd|v.net.connectivity|version=70}}
* Computes shortest distance via the network between the given sets of features: {{cmd|v.net.distance|version=70}}
* Computes the maximum flow between two sets of nodes: {{cmd|v.net.flow|version=70}}
* Computes minimum spanning tree: {{cmd|v.net.spanningtree|version=70}}
* Minimum Steiner trees (star-like connections, e.g. broadband cable connections): {{cmd|v.net.steiner|version=70}}
* Znajdowanie najkrótszej drogi z użyciem rozkładów jazdy: {{cmd|v.net.timetable|version=70}}
* Traveling salesman (round trip): {{cmd|v.net.salesman|version=70}}

Vector directions are defined by the digitizing direction (a-->--b). You can navigate either omnidirectionally or differently in each directions as both directions are supported. Network modules provide parameters to assign attribute columns to the forward and backward direction. To see how a vector is directed, use the "display" parameter of {{cmd|d.vect}} (set display=dir).

* see the {{cmd|vectorintro}} "vector map processing and network analysis" help page

== Example: Shortest path routing ==

* see the {{cmd|v.net.path}} and {{cmd|d.path}} help pages

== Nowe pomysły ==

* [[Vector network analysis ideas]] (pomóż w realizacji)

== Zrzuty ekranu ==
* more screenshots [http://grass.osgeo.org/screenshots/vector.php from the GRASS website]

[[Image:V.net.iso.png|center|600px|thumb|{{cmd|v.net.iso}} - Split net to bands between cost isolines (direction from centre). Costs of centre node are used in calculation.]]

[[Image:V.net.alloc.png|center|600px|thumb|{{cmd|v.net.alloc}} - Allocates subnets for nearest centres (direction from centre). Costs of centre node are used in calculation.]]

[[Image:D.path.jpg|center|600px|thumb|{{cmd|d.path}} - Find shortest path for selected starting and ending node.]]

== See also ==

* [[GSoC Network Analysis]]: many new modules!

== Linki zewnętrzne ==

* [http://www.ossgis.co.cc/2009/01/grass-gis-network-analysis-subnets.html GRASS GIS: Network Analysis (Subnets within a vector network)]

[[Category:Documentation]]
[[Category:Vector]]

Vector network analysis/pl

2012-09-10T11:26:55Z

⚠️MilenaN: polish translation started

= Vector network analysis =

GRASS provides support for vector network analysis using the [http://trac.osgeo.org/grass/browser/grass/trunk/lib/vector/dglib/ DGlib] Directed Graph Library.

== Implemented algorithms ==

The following algorithms are implemented (GRASS 6.5+):

* Utrzymanie sieci: {{cmd|v.net|version=70}}
* Najkrótsza droga: {{cmd|d.path|version=64}} and {{cmd|v.net.path|version=70}}
* Najkrótsza droga pomiędzy wieloma parami punktów {{cmd|v.net.allpairs|version=70}}
* Allocation of sources (create subnetworks, e.g. police station zones): {{cmd|v.net.alloc|version=70}}
* Iso-distances (from centers): {{cmd|v.net.iso|version=70}}
* Computes bridges and articulation points: {{cmd|v.net.bridge|version=70}}
* Computes degree, centrality, betweeness, closeness and eigenvector centrality measures: {{cmd|v.net.centrality|version=70}}
* Computes strongly and weakly connected components: {{cmd|v.net.components|version=70}}
* Computes vertex connectivity between two sets of nodes: {{cmd|v.net.connectivity|version=70}}
* Computes shortest distance via the network between the given sets of features: {{cmd|v.net.distance|version=70}}
* Computes the maximum flow between two sets of nodes: {{cmd|v.net.flow|version=70}}
* Computes minimum spanning tree: {{cmd|v.net.spanningtree|version=70}}
* Minimum Steiner trees (star-like connections, e.g. broadband cable connections): {{cmd|v.net.steiner|version=70}}
* Znajdowanie najkrótszej drogi z użyciem rozkładów jazdy: {{cmd|v.net.timetable|version=70}}
* Traveling salesman (round trip): {{cmd|v.net.salesman|version=70}}

Vector directions are defined by the digitizing direction (a-->--b). You can navigate either omnidirectionally or differently in each directions as both directions are supported. Network modules provide parameters to assign attribute columns to the forward and backward direction. To see how a vector is directed, use the "display" parameter of {{cmd|d.vect}} (set display=dir).

* see the {{cmd|vectorintro}} "vector map processing and network analysis" help page

== Example: Shortest path routing ==

* see the {{cmd|v.net.path}} and {{cmd|d.path}} help pages

== Nowe pomysły ==

* [[Vector network analysis ideas]] (please help to realize)

== Zrzuty ekranu ==
* more screenshots [http://grass.osgeo.org/screenshots/vector.php from the GRASS website]

[[Image:V.net.iso.png|center|600px|thumb|{{cmd|v.net.iso}} - Split net to bands between cost isolines (direction from centre). Costs of centre node are used in calculation.]]

[[Image:V.net.alloc.png|center|600px|thumb|{{cmd|v.net.alloc}} - Allocates subnets for nearest centres (direction from centre). Costs of centre node are used in calculation.]]

[[Image:D.path.jpg|center|600px|thumb|{{cmd|d.path}} - Find shortest path for selected starting and ending node.]]

== See also ==

* [[GSoC Network Analysis]]: many new modules!

== Linki zewnętrzne ==

* [http://www.ossgis.co.cc/2009/01/grass-gis-network-analysis-subnets.html GRASS GIS: Network Analysis (Subnets within a vector network)]

[[Category:Documentation]]
[[Category:Vector]]

Talk:GRASS Community Sprint Prague 2012

2012-05-26T14:02:02Z

⚠️MilenaN: + report

== Reports ==

=== [[User:Landa|Martin Landa]] ===

* OSGeo4W GRASS package configuration: add liblas support (http://liblas.org/osgeo4w.html) - {{rev|51677}} & {{rev|51679}}
* various wxGUI fixes

=== [[User:Neteler|Markus Neteler]] ===

* Fundraising for this Community Sprint (with great help from Arnulf Christl)
* PSC composition discussion
* fix r.lake segfault for seed map ({{rev|51752}}) together with Markus Metz

=== [[User:Annakrat|Anna Kratochvilova]] ===
* wxGUI/digitizer: add help button to digitizer toolbar ({{rev|51742}})

=== [[User:MilenaN|Milena Nowotarska]] ===
* WinGRASS bug hunting
* translation

== Wishes for the Community Sprint ==

* Visual Guide to GRASS GIS modules: scratch a collection of per-module dedicated||or tutorial/task oriented, simple, minimalistic yet attractive, bullet-proof visual examples
**exemplify what GRASS modules do rather than how they do it, thus different than the manuals -- ''rephrase title?''
***make use of existing grass modules list(s), like (this old) [http://grass.itc.it/gdp/grassmanuals/grass63_module_list.pdf GRASS GIS 6.3 Command list (PDF document)]
***visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***ignore modules which cannot be visualised?
**check if (and some-how) task-oriented visual examples could be build out of per-modules examples
**setup specific styling rules (?)
***only one descriptive sentence per module or task
***visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***limited caption(s) describing visuals
**end-up with some independent and beautiful TeXy PDF
**visually enrich existing manuals and/or grass-wiki
** or consider Sphinx

* Review of the python + ctypes example scripts.
: The examples given in the code for {{src|doc/python/raster_example_ctypes.py|version=trunk}}, vector_example_ctypes.py and on the [[Python Ctypes Examples|Ctypes wiki page]] have so far for me all been broken in some way or another. Either grass7 API in grass6 example, typos, incomplete, etc. have made almost all of them fail out of the box. As this is teaching code we should make sure it's perfect :-). See also bug in trac about possible memory leak in r.example.

* Extend {{cmd|r.colors}} documentation by an example for a user-generated logarithmic color table.

== Testing by power users ==

(Power) users from all over the world are kindly invited to assist with testing of new and existing functionality. To collect results and notes, we set up an interactive, collaborative editing tool which works in real-time:

Please check http://titanpad.com/I51nq1SrNc

== Non-Technical ==

=== Discuss role and current composition of GRASS-PSC ===

Discussion about GRASS [[PSC]]:
* Every year members are requested to confirm to continue their work in the PSC.
* After the Community Sprint 2012, the Chair will request updates to the [[RFC1]] from the PSC members.
* Answer within five business days needed.
* In case of no continuation/no answer, a member is replaced in order to refresh the PSC.
* To be eligible for PSC membership, a person should have a demonstrated and substantial involvement in GRASS GIS (operation of the PSC is defined at [[RFC1]]).

=== Misc ===

* Discuss Google Summer of Code (two students are here)
* Discuss GRASS 6.4.3 and 7.0 release schedule
* Define make a manual test procedure for users to simplify testing before new releases, write this up in the wiki ([http://trac.osgeo.org/grass/wiki/HowToTestGrass6 example])

== Semi-Technical ==

=== Improve Web site or use CMS ===
* Discussion about [[CMS]]
** Prototype site: http://grass.fem-environment.eu/
** Problem: enormous job
** Involvement of people, see nice example at http://www.mageia.org/en/contribute/

=== Misc ===
* Document tips & tricks for GRASS compilation with the wxGUI
: there is [http://trac.osgeo.org/grass/wiki/CompileOnWindows Compilation on MS-Windows]
* Discuss new GRASS Book 4th edition in conjunction with the GRASS GIS 7.0 release in early 2013

== Technical ==

=== OSGeo4W ===

* [{{done}} (martinl) - {{rev|51677}} & {{rev|51679}}] GRASS package configuration: add liblas support (http://liblas.org/osgeo4w.html) ([http://wingrass.fsv.cvut.cz/grass64/ download])

=== Android ===

* continue the Android compilation (needs especially the elimination of XDR in rast and rast3d)

=== QGIS-Sextante-GRASS interface ===

* work on new integration with [http://plugins.qgis.org/plugins/sextante/ QGIS-Sextante]

=== Update the GDAL-GRASS interface to GRASS 7 ===

* see http://trac.osgeo.org/gdal/ticket/2953
* LGPL grass IO code written from scratch?

=== Rules Based programming and Agent Based Modelling ===

* Tutorial/Documentation on g.infer
* [http://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.agent r.agent] in GRASS 7

=== Time series ===

* Seminar on Temporal GIS framework demo and discussion: by Soeren Gebbert, done on 24 May 2012
* Add content to http://grass.osgeo.org/grass70/manuals/html70_user/temporalintro.html from Soeren's tutorial
* Discuss temporal GIS wxGUI and WPS integration
* Discuss massive parallel computation of spatio-temporal datasets

=== Automated command user statistics ===

* modify g.parser to write out the list of used commands (without parameters) into a text file for simple, automated command user statistics

=== Mobile: inventory of mobile and touch implementations ===

* [http://code.google.com/p/geopaparazzi/ Geopaparazzi], v.in.geopaparazzi
* GRASS on Android (patches by MN)

=== Cloud computing ===

* g.cloud
* cluster usage best practices

=== GSoC 2012 ===

* v.net.* front end, WMS
* Python API
* Image Segmentation

=== GRASS 7 ===
* PostGIS Topology support
* New features for vector engine
* Discuss Toolbox concept
* Discuss how to implement [[GRASS Metadata Management]]
* [{{done}} (lucadelu) - {{rev|51735}}] Fix category in v.in.mapgen
* New module r.massmov

=== Model integration ===

* GRASS and [http://www.coulthard.org.uk/CAESAR.html Caesar model]

=== GRASS modules fixes ===

* i.atcorr debugging
** Figure out how to get visibility/aerosol depth at 550nm (perhaps from MODIS atmosphere?)
** Under certain circumstances i.atcorr produces NULL data
* GRASS 6.4.3 - [http://trac.osgeo.org/grass/query?status=new&status=assigned&status=reopened&group=type&order=priority&priority=blocker&priority=critical&milestone=6.4.3&milestone=6.4.2&milestone=6.4.1&milestone=6.4.0 Release critical issues to be fixed]

=== Signal handling ===

* The Python based scripts should catch CTRL-C to avoid that clutter is left behind and that ugly traceback is printed into the terminal.

Suggestion by Anne Ghisla (yet not working... ):
<source lang="python">
Index: lib/init/grass.py
===================================================================
--- lib/init/grass.py (revision 51604)
+++ lib/init/grass.py (working copy)
@@ -30,7 +30,12 @@
import subprocess
import re
import platform
+import signal

+# catch user-sent CTRL-C
+signal.signal(signal.SIGINT, lambda a,b:cleanup())
+signal.siginterrupt(signal.SIGINT, False)
+
# Variables substituted during build process
if os.environ.has_key('GISBASE'):
gisbase = os.environ['GISBASE']
</source>

* Currently if vector creation modules fail to create/import they still leave behind the empty skeleton of a map, so you need to use --o for the next time. It would be nice if cleanup could occur. This doesn't happen (visibly) with raster maps as they are composed in $MAPSET/.tmp/ and only moved into the main $MAPSET elements once everything is finished. Vector maps on the otherhand write to the MAPSET in-place.

=== Fix wxGUI problems ===

==== Add a "change language" option in GRASS GUI ====

Implement the diff provided here: http://trac.osgeo.org/grass/ticket/879

==== Fix several issues ====

A. Clerici: please fix:
* ticket https://trac.osgeo.org/grass/ticket/1564
* ticket https://trac.osgeo.org/grass/ticket/1570
* wxGUI bugs (GRASS6.4.2RC3 under Fedora 16):
** In the 'Create histogram of raster map' function, the style pie and the Color for text and axes options are not working. The options run fine on the tcltk GUI and in command line mode.
** In the 'Add scalebar and north arrow', the scale can be modified only once and the option can't be re-entered nor the scale can't be deleted. Also in this case there are no problems with the tcltk GUI.
** the option 'Add raster cell arrows' seems not to work properly. It seems that the arrows in the Map Display cannot zoomed in. It can be checked by the following steps:
*** Load and display the aspect (Spearfish) map.
*** Open the d.rast.arrows panel through the GUI button and choose the same map aspect. Click Apply: the Map Display appears green as expected for the very high resolution.
*** Choose 10 for the 'Draw arrow every Nth grid cell:' option and none as 'Color for drawing grid or “none”' option. The arrows are displayed on the cells of aspect map.
*** To make the arrows visible choose slope as 'Raster map containing values used for arrow length:' and 10.0 as 'Scale factor for arrows'. Zoom in a very small area: the cells of aspect map are enlarged, but the density of arrows remains the same
*** The direction is correctly the same for all arrows inside the same cell but it seems that instead of having an arrow each 10 aspect cells, there is an arrow each 10 pixel of the screen (with tcltk GUI the procedure works fine)
* Fix wx0..6 monitors

==== Layout ====

Optionally, have all-in-one GUI window (requested by many new users!):
<center>
{|
|-
| [[Image:Wxgui_current.png|250px|thumb|center|Current wxGUI layout with detached window components]]
| [[Image:Wxgui_proposal.png|200px|thumb|center|'''Proposal''' for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus by simple rearrangement into one frame)]]
|-
|}
</center>

Proposed solution: wxLayoutAlgorithm(), see [[WxGUI#What_others_do]]

Optionally, a minimalistic cointegration of a map display and the command console. See also this post in grass-user [http://lists.osgeo.org/pipermail/grass-user/2011-April/060346.html Re: [GRASS-user<nowiki>]</nowiki> replacement for d.mon in GRASS 7.0?]
<center>
{|
|-
|[[Image:grass-gis_minimalistic_map-display_with_comman-console__layout_mockup.png|200px|thumb|left|alt text]]
|}
</center>

==== r.li.setup ====
work on r.li.setup for GRASS7

==== Saving History ====

* when using the wxGUI, it needs to write back to the shell history
: `cat wxgui_history.log >> $MAPSET/.bash_history`
: Since the wxGUI shell quoting is not perfect, maybe it is better not to write directly to real shell history, but maintain its own in ~/.grass7/history.

==== Digitizing toolbar ====

* missing string "Select vector map" from the drop-down widget on digitizing toolbar
: on winGRASS, nightly build of 24th May
* after editing vector objects and saving, the changes are not applied on the map. Must be some refresh problem.
* Highlighting problem
: objects selected in the attribute table are not highlighted on the map
: objects selected ton the map are not highlighted in the attribute table.
* Bounding box of a layer broken after deletion of some objects with broken geometry, also displaying of the attribute table broken with a message that the map layer is not a vector one,
: closing the layer from the layer tree also not possible
: after closing GRASS6.4.3 and reopening the project, the layer is restored with all the changes applayed.

==== Attribute manager ====

* Editing attribute table broken
: cannot delete a row, permission denied
: different than selected row dissapears after not succesful row deletion but is back after refreshing the table.
* Not able to insert a value into a table, permision to the temp file denied.
* Too small area for displaying the table data after connecting a table to the vector map.
: Add a table to the vector layer in wxGUI GRASS6.4.3 with: Show attribute table > Manage layers tab.
: Go to Browse data tab, the area to thisplay the attributes is extreemly small and cannot be stretched.
: After closing the table manager and reopening, the area is normal wide again.

==== Map Display ====

* Clicking with a Query tool on a vector object randomly not able to find an object to display its attributes.

==== I18N ====

* Solve module description string duplication in both grassmods.po and grasswxpy.po files.
: Before fixing this problem in code, please find a way to automagically copy the translated strings to the proper .po files for all the languages.

==== Project file ====
* Find a way to succesfully open a project file made in GRASS6.4 in GRASS7.
: Due to changes (e.g. removal of some flags), the project file is not opened in a correct way. The user can see the layers in the layer tree, but they cannot be displayed in the map canvas. A warning would help.

=== Not to forget about the next time ===

First day:
* presentation of participants

First or second day:
* group photo

Talk:GRASS Community Sprint Prague 2012

2012-05-26T13:57:14Z

⚠️MilenaN: /* Attribute manager */

== Reports ==

=== [[User:Landa|Martin Landa]] ===

* OSGeo4W GRASS package configuration: add liblas support (http://liblas.org/osgeo4w.html) - {{rev|51677}} & {{rev|51679}}
* various wxGUI fixes

=== [[User:Neteler|Markus Neteler]] ===

* Fundraising for this Community Sprint (with great help from Arnulf Christl)
* PSC composition discussion
* fix r.lake segfault for seed map ({{rev|51752}}) together with Markus Metz

=== [[User:Annakrat|Anna Kratochvilova]] ===
* wxGUI/digitizer: add help button to digitizer toolbar ({{rev|51742}})

== Wishes for the Community Sprint ==

* Visual Guide to GRASS GIS modules: scratch a collection of per-module dedicated||or tutorial/task oriented, simple, minimalistic yet attractive, bullet-proof visual examples
**exemplify what GRASS modules do rather than how they do it, thus different than the manuals -- ''rephrase title?''
***make use of existing grass modules list(s), like (this old) [http://grass.itc.it/gdp/grassmanuals/grass63_module_list.pdf GRASS GIS 6.3 Command list (PDF document)]
***visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***ignore modules which cannot be visualised?
**check if (and some-how) task-oriented visual examples could be build out of per-modules examples
**setup specific styling rules (?)
***only one descriptive sentence per module or task
***visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***limited caption(s) describing visuals
**end-up with some independent and beautiful TeXy PDF
**visually enrich existing manuals and/or grass-wiki
** or consider Sphinx

* Review of the python + ctypes example scripts.
: The examples given in the code for {{src|doc/python/raster_example_ctypes.py|version=trunk}}, vector_example_ctypes.py and on the [[Python Ctypes Examples|Ctypes wiki page]] have so far for me all been broken in some way or another. Either grass7 API in grass6 example, typos, incomplete, etc. have made almost all of them fail out of the box. As this is teaching code we should make sure it's perfect :-). See also bug in trac about possible memory leak in r.example.

* Extend {{cmd|r.colors}} documentation by an example for a user-generated logarithmic color table.

== Testing by power users ==

(Power) users from all over the world are kindly invited to assist with testing of new and existing functionality. To collect results and notes, we set up an interactive, collaborative editing tool which works in real-time:

Please check http://titanpad.com/I51nq1SrNc

== Non-Technical ==

=== Discuss role and current composition of GRASS-PSC ===

Discussion about GRASS [[PSC]]:
* Every year members are requested to confirm to continue their work in the PSC.
* After the Community Sprint 2012, the Chair will request updates to the [[RFC1]] from the PSC members.
* Answer within five business days needed.
* In case of no continuation/no answer, a member is replaced in order to refresh the PSC.
* To be eligible for PSC membership, a person should have a demonstrated and substantial involvement in GRASS GIS (operation of the PSC is defined at [[RFC1]]).

=== Misc ===

* Discuss Google Summer of Code (two students are here)
* Discuss GRASS 6.4.3 and 7.0 release schedule
* Define make a manual test procedure for users to simplify testing before new releases, write this up in the wiki ([http://trac.osgeo.org/grass/wiki/HowToTestGrass6 example])

== Semi-Technical ==

=== Improve Web site or use CMS ===
* Discussion about [[CMS]]
** Prototype site: http://grass.fem-environment.eu/
** Problem: enormous job
** Involvement of people, see nice example at http://www.mageia.org/en/contribute/

=== Misc ===
* Document tips & tricks for GRASS compilation with the wxGUI
: there is [http://trac.osgeo.org/grass/wiki/CompileOnWindows Compilation on MS-Windows]
* Discuss new GRASS Book 4th edition in conjunction with the GRASS GIS 7.0 release in early 2013

== Technical ==

=== OSGeo4W ===

* [{{done}} (martinl) - {{rev|51677}} & {{rev|51679}}] GRASS package configuration: add liblas support (http://liblas.org/osgeo4w.html) ([http://wingrass.fsv.cvut.cz/grass64/ download])

=== Android ===

* continue the Android compilation (needs especially the elimination of XDR in rast and rast3d)

=== QGIS-Sextante-GRASS interface ===

* work on new integration with [http://plugins.qgis.org/plugins/sextante/ QGIS-Sextante]

=== Update the GDAL-GRASS interface to GRASS 7 ===

* see http://trac.osgeo.org/gdal/ticket/2953
* LGPL grass IO code written from scratch?

=== Rules Based programming and Agent Based Modelling ===

* Tutorial/Documentation on g.infer
* [http://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.agent r.agent] in GRASS 7

=== Time series ===

* Seminar on Temporal GIS framework demo and discussion: by Soeren Gebbert, done on 24 May 2012
* Add content to http://grass.osgeo.org/grass70/manuals/html70_user/temporalintro.html from Soeren's tutorial
* Discuss temporal GIS wxGUI and WPS integration
* Discuss massive parallel computation of spatio-temporal datasets

=== Automated command user statistics ===

* modify g.parser to write out the list of used commands (without parameters) into a text file for simple, automated command user statistics

=== Mobile: inventory of mobile and touch implementations ===

* [http://code.google.com/p/geopaparazzi/ Geopaparazzi], v.in.geopaparazzi
* GRASS on Android (patches by MN)

=== Cloud computing ===

* g.cloud
* cluster usage best practices

=== GSoC 2012 ===

* v.net.* front end, WMS
* Python API
* Image Segmentation

=== GRASS 7 ===
* PostGIS Topology support
* New features for vector engine
* Discuss Toolbox concept
* Discuss how to implement [[GRASS Metadata Management]]
* [{{done}} (lucadelu) - {{rev|51735}}] Fix category in v.in.mapgen
* New module r.massmov

=== Model integration ===

* GRASS and [http://www.coulthard.org.uk/CAESAR.html Caesar model]

=== GRASS modules fixes ===

* i.atcorr debugging
** Figure out how to get visibility/aerosol depth at 550nm (perhaps from MODIS atmosphere?)
** Under certain circumstances i.atcorr produces NULL data
* GRASS 6.4.3 - [http://trac.osgeo.org/grass/query?status=new&status=assigned&status=reopened&group=type&order=priority&priority=blocker&priority=critical&milestone=6.4.3&milestone=6.4.2&milestone=6.4.1&milestone=6.4.0 Release critical issues to be fixed]

=== Signal handling ===

* The Python based scripts should catch CTRL-C to avoid that clutter is left behind and that ugly traceback is printed into the terminal.

Suggestion by Anne Ghisla (yet not working... ):
<source lang="python">
Index: lib/init/grass.py
===================================================================
--- lib/init/grass.py (revision 51604)
+++ lib/init/grass.py (working copy)
@@ -30,7 +30,12 @@
import subprocess
import re
import platform
+import signal

+# catch user-sent CTRL-C
+signal.signal(signal.SIGINT, lambda a,b:cleanup())
+signal.siginterrupt(signal.SIGINT, False)
+
# Variables substituted during build process
if os.environ.has_key('GISBASE'):
gisbase = os.environ['GISBASE']
</source>

* Currently if vector creation modules fail to create/import they still leave behind the empty skeleton of a map, so you need to use --o for the next time. It would be nice if cleanup could occur. This doesn't happen (visibly) with raster maps as they are composed in $MAPSET/.tmp/ and only moved into the main $MAPSET elements once everything is finished. Vector maps on the otherhand write to the MAPSET in-place.

=== Fix wxGUI problems ===

==== Add a "change language" option in GRASS GUI ====

Implement the diff provided here: http://trac.osgeo.org/grass/ticket/879

==== Fix several issues ====

A. Clerici: please fix:
* ticket https://trac.osgeo.org/grass/ticket/1564
* ticket https://trac.osgeo.org/grass/ticket/1570
* wxGUI bugs (GRASS6.4.2RC3 under Fedora 16):
** In the 'Create histogram of raster map' function, the style pie and the Color for text and axes options are not working. The options run fine on the tcltk GUI and in command line mode.
** In the 'Add scalebar and north arrow', the scale can be modified only once and the option can't be re-entered nor the scale can't be deleted. Also in this case there are no problems with the tcltk GUI.
** the option 'Add raster cell arrows' seems not to work properly. It seems that the arrows in the Map Display cannot zoomed in. It can be checked by the following steps:
*** Load and display the aspect (Spearfish) map.
*** Open the d.rast.arrows panel through the GUI button and choose the same map aspect. Click Apply: the Map Display appears green as expected for the very high resolution.
*** Choose 10 for the 'Draw arrow every Nth grid cell:' option and none as 'Color for drawing grid or “none”' option. The arrows are displayed on the cells of aspect map.
*** To make the arrows visible choose slope as 'Raster map containing values used for arrow length:' and 10.0 as 'Scale factor for arrows'. Zoom in a very small area: the cells of aspect map are enlarged, but the density of arrows remains the same
*** The direction is correctly the same for all arrows inside the same cell but it seems that instead of having an arrow each 10 aspect cells, there is an arrow each 10 pixel of the screen (with tcltk GUI the procedure works fine)
* Fix wx0..6 monitors

==== Layout ====

Optionally, have all-in-one GUI window (requested by many new users!):
<center>
{|
|-
| [[Image:Wxgui_current.png|250px|thumb|center|Current wxGUI layout with detached window components]]
| [[Image:Wxgui_proposal.png|200px|thumb|center|'''Proposal''' for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus by simple rearrangement into one frame)]]
|-
|}
</center>

Proposed solution: wxLayoutAlgorithm(), see [[WxGUI#What_others_do]]

Optionally, a minimalistic cointegration of a map display and the command console. See also this post in grass-user [http://lists.osgeo.org/pipermail/grass-user/2011-April/060346.html Re: [GRASS-user<nowiki>]</nowiki> replacement for d.mon in GRASS 7.0?]
<center>
{|
|-
|[[Image:grass-gis_minimalistic_map-display_with_comman-console__layout_mockup.png|200px|thumb|left|alt text]]
|}
</center>

==== r.li.setup ====
work on r.li.setup for GRASS7

==== Saving History ====

* when using the wxGUI, it needs to write back to the shell history
: `cat wxgui_history.log >> $MAPSET/.bash_history`
: Since the wxGUI shell quoting is not perfect, maybe it is better not to write directly to real shell history, but maintain its own in ~/.grass7/history.

==== Digitizing toolbar ====

* missing string "Select vector map" from the drop-down widget on digitizing toolbar
: on winGRASS, nightly build of 24th May
* after editing vector objects and saving, the changes are not applied on the map. Must be some refresh problem.
* Highlighting problem
: objects selected in the attribute table are not highlighted on the map
: objects selected ton the map are not highlighted in the attribute table.
* Bounding box of a layer broken after deletion of some objects with broken geometry, also displaying of the attribute table broken with a message that the map layer is not a vector one,
: closing the layer from the layer tree also not possible
: after closing GRASS6.4.3 and reopening the project, the layer is restored with all the changes applayed.

==== Attribute manager ====

* Editing attribute table broken
: cannot delete a row, permission denied
: different than selected row dissapears after not succesful row deletion but is back after refreshing the table.
* Not able to insert a value into a table, permision to the temp file denied.
* Too small area for displaying the table data after connecting a table to the vector map.
: Add a table to the vector layer in wxGUI GRASS6.4.3 with: Show attribute table > Manage layers tab.
: Go to Browse data tab, the area to thisplay the attributes is extreemly small and cannot be stretched.
: After closing the table manager and reopening, the area is normal wide again.

==== Map Display ====

* Clicking with a Query tool on a vector object randomly not able to find an object to display its attributes.

==== I18N ====

* Solve module description string duplication in both grassmods.po and grasswxpy.po files.
: Before fixing this problem in code, please find a way to automagically copy the translated strings to the proper .po files for all the languages.

==== Project file ====
* Find a way to succesfully open a project file made in GRASS6.4 in GRASS7.
: Due to changes (e.g. removal of some flags), the project file is not opened in a correct way. The user can see the layers in the layer tree, but they cannot be displayed in the map canvas. A warning would help.

=== Not to forget about the next time ===

First day:
* presentation of participants

First or second day:
* group photo

Talk:GRASS Community Sprint Prague 2012

2012-05-26T13:49:30Z

⚠️MilenaN: /* Project file */

== Reports ==

=== [[User:Landa|Martin Landa]] ===

* OSGeo4W GRASS package configuration: add liblas support (http://liblas.org/osgeo4w.html) - {{rev|51677}} & {{rev|51679}}
* various wxGUI fixes

=== [[User:Neteler|Markus Neteler]] ===

* Fundraising for this Community Sprint (with great help from Arnulf Christl)
* PSC composition discussion
* fix r.lake segfault for seed map ({{rev|51752}}) together with Markus Metz

=== [[User:Annakrat|Anna Kratochvilova]] ===
* wxGUI/digitizer: add help button to digitizer toolbar ({{rev|51742}})

== Wishes for the Community Sprint ==

* Visual Guide to GRASS GIS modules: scratch a collection of per-module dedicated||or tutorial/task oriented, simple, minimalistic yet attractive, bullet-proof visual examples
**exemplify what GRASS modules do rather than how they do it, thus different than the manuals -- ''rephrase title?''
***make use of existing grass modules list(s), like (this old) [http://grass.itc.it/gdp/grassmanuals/grass63_module_list.pdf GRASS GIS 6.3 Command list (PDF document)]
***visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***ignore modules which cannot be visualised?
**check if (and some-how) task-oriented visual examples could be build out of per-modules examples
**setup specific styling rules (?)
***only one descriptive sentence per module or task
***visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***limited caption(s) describing visuals
**end-up with some independent and beautiful TeXy PDF
**visually enrich existing manuals and/or grass-wiki
** or consider Sphinx

* Review of the python + ctypes example scripts.
: The examples given in the code for {{src|doc/python/raster_example_ctypes.py|version=trunk}}, vector_example_ctypes.py and on the [[Python Ctypes Examples|Ctypes wiki page]] have so far for me all been broken in some way or another. Either grass7 API in grass6 example, typos, incomplete, etc. have made almost all of them fail out of the box. As this is teaching code we should make sure it's perfect :-). See also bug in trac about possible memory leak in r.example.

* Extend {{cmd|r.colors}} documentation by an example for a user-generated logarithmic color table.

== Testing by power users ==

(Power) users from all over the world are kindly invited to assist with testing of new and existing functionality. To collect results and notes, we set up an interactive, collaborative editing tool which works in real-time:

Please check http://titanpad.com/I51nq1SrNc

== Non-Technical ==

=== Discuss role and current composition of GRASS-PSC ===

Discussion about GRASS [[PSC]]:
* Every year members are requested to confirm to continue their work in the PSC.
* After the Community Sprint 2012, the Chair will request updates to the [[RFC1]] from the PSC members.
* Answer within five business days needed.
* In case of no continuation/no answer, a member is replaced in order to refresh the PSC.
* To be eligible for PSC membership, a person should have a demonstrated and substantial involvement in GRASS GIS (operation of the PSC is defined at [[RFC1]]).

=== Misc ===

* Discuss Google Summer of Code (two students are here)
* Discuss GRASS 6.4.3 and 7.0 release schedule
* Define make a manual test procedure for users to simplify testing before new releases, write this up in the wiki ([http://trac.osgeo.org/grass/wiki/HowToTestGrass6 example])

== Semi-Technical ==

=== Improve Web site or use CMS ===
* Discussion about [[CMS]]
** Prototype site: http://grass.fem-environment.eu/
** Problem: enormous job
** Involvement of people, see nice example at http://www.mageia.org/en/contribute/

=== Misc ===
* Document tips & tricks for GRASS compilation with the wxGUI
: there is [http://trac.osgeo.org/grass/wiki/CompileOnWindows Compilation on MS-Windows]
* Discuss new GRASS Book 4th edition in conjunction with the GRASS GIS 7.0 release in early 2013

== Technical ==

=== OSGeo4W ===

* [{{done}} (martinl) - {{rev|51677}} & {{rev|51679}}] GRASS package configuration: add liblas support (http://liblas.org/osgeo4w.html) ([http://wingrass.fsv.cvut.cz/grass64/ download])

=== Android ===

* continue the Android compilation (needs especially the elimination of XDR in rast and rast3d)

=== QGIS-Sextante-GRASS interface ===

* work on new integration with [http://plugins.qgis.org/plugins/sextante/ QGIS-Sextante]

=== Update the GDAL-GRASS interface to GRASS 7 ===

* see http://trac.osgeo.org/gdal/ticket/2953
* LGPL grass IO code written from scratch?

=== Rules Based programming and Agent Based Modelling ===

* Tutorial/Documentation on g.infer
* [http://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.agent r.agent] in GRASS 7

=== Time series ===

* Seminar on Temporal GIS framework demo and discussion: by Soeren Gebbert, done on 24 May 2012
* Add content to http://grass.osgeo.org/grass70/manuals/html70_user/temporalintro.html from Soeren's tutorial
* Discuss temporal GIS wxGUI and WPS integration
* Discuss massive parallel computation of spatio-temporal datasets

=== Automated command user statistics ===

* modify g.parser to write out the list of used commands (without parameters) into a text file for simple, automated command user statistics

=== Mobile: inventory of mobile and touch implementations ===

* [http://code.google.com/p/geopaparazzi/ Geopaparazzi], v.in.geopaparazzi
* GRASS on Android (patches by MN)

=== Cloud computing ===

* g.cloud
* cluster usage best practices

=== GSoC 2012 ===

* v.net.* front end, WMS
* Python API
* Image Segmentation

=== GRASS 7 ===
* PostGIS Topology support
* New features for vector engine
* Discuss Toolbox concept
* Discuss how to implement [[GRASS Metadata Management]]
* [{{done}} (lucadelu) - {{rev|51735}}] Fix category in v.in.mapgen
* New module r.massmov

=== Model integration ===

* GRASS and [http://www.coulthard.org.uk/CAESAR.html Caesar model]

=== GRASS modules fixes ===

* i.atcorr debugging
** Figure out how to get visibility/aerosol depth at 550nm (perhaps from MODIS atmosphere?)
** Under certain circumstances i.atcorr produces NULL data
* GRASS 6.4.3 - [http://trac.osgeo.org/grass/query?status=new&status=assigned&status=reopened&group=type&order=priority&priority=blocker&priority=critical&milestone=6.4.3&milestone=6.4.2&milestone=6.4.1&milestone=6.4.0 Release critical issues to be fixed]

=== Signal handling ===

* The Python based scripts should catch CTRL-C to avoid that clutter is left behind and that ugly traceback is printed into the terminal.

Suggestion by Anne Ghisla (yet not working... ):
<source lang="python">
Index: lib/init/grass.py
===================================================================
--- lib/init/grass.py (revision 51604)
+++ lib/init/grass.py (working copy)
@@ -30,7 +30,12 @@
import subprocess
import re
import platform
+import signal

+# catch user-sent CTRL-C
+signal.signal(signal.SIGINT, lambda a,b:cleanup())
+signal.siginterrupt(signal.SIGINT, False)
+
# Variables substituted during build process
if os.environ.has_key('GISBASE'):
gisbase = os.environ['GISBASE']
</source>

* Currently if vector creation modules fail to create/import they still leave behind the empty skeleton of a map, so you need to use --o for the next time. It would be nice if cleanup could occur. This doesn't happen (visibly) with raster maps as they are composed in $MAPSET/.tmp/ and only moved into the main $MAPSET elements once everything is finished. Vector maps on the otherhand write to the MAPSET in-place.

=== Fix wxGUI problems ===

==== Add a "change language" option in GRASS GUI ====

Implement the diff provided here: http://trac.osgeo.org/grass/ticket/879

==== Fix several issues ====

A. Clerici: please fix:
* ticket https://trac.osgeo.org/grass/ticket/1564
* ticket https://trac.osgeo.org/grass/ticket/1570
* wxGUI bugs (GRASS6.4.2RC3 under Fedora 16):
** In the 'Create histogram of raster map' function, the style pie and the Color for text and axes options are not working. The options run fine on the tcltk GUI and in command line mode.
** In the 'Add scalebar and north arrow', the scale can be modified only once and the option can't be re-entered nor the scale can't be deleted. Also in this case there are no problems with the tcltk GUI.
** the option 'Add raster cell arrows' seems not to work properly. It seems that the arrows in the Map Display cannot zoomed in. It can be checked by the following steps:
*** Load and display the aspect (Spearfish) map.
*** Open the d.rast.arrows panel through the GUI button and choose the same map aspect. Click Apply: the Map Display appears green as expected for the very high resolution.
*** Choose 10 for the 'Draw arrow every Nth grid cell:' option and none as 'Color for drawing grid or “none”' option. The arrows are displayed on the cells of aspect map.
*** To make the arrows visible choose slope as 'Raster map containing values used for arrow length:' and 10.0 as 'Scale factor for arrows'. Zoom in a very small area: the cells of aspect map are enlarged, but the density of arrows remains the same
*** The direction is correctly the same for all arrows inside the same cell but it seems that instead of having an arrow each 10 aspect cells, there is an arrow each 10 pixel of the screen (with tcltk GUI the procedure works fine)
* Fix wx0..6 monitors

==== Layout ====

Optionally, have all-in-one GUI window (requested by many new users!):
<center>
{|
|-
| [[Image:Wxgui_current.png|250px|thumb|center|Current wxGUI layout with detached window components]]
| [[Image:Wxgui_proposal.png|200px|thumb|center|'''Proposal''' for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus by simple rearrangement into one frame)]]
|-
|}
</center>

Proposed solution: wxLayoutAlgorithm(), see [[WxGUI#What_others_do]]

Optionally, a minimalistic cointegration of a map display and the command console. See also this post in grass-user [http://lists.osgeo.org/pipermail/grass-user/2011-April/060346.html Re: [GRASS-user<nowiki>]</nowiki> replacement for d.mon in GRASS 7.0?]
<center>
{|
|-
|[[Image:grass-gis_minimalistic_map-display_with_comman-console__layout_mockup.png|200px|thumb|left|alt text]]
|}
</center>

==== r.li.setup ====
work on r.li.setup for GRASS7

==== Saving History ====

* when using the wxGUI, it needs to write back to the shell history
: `cat wxgui_history.log >> $MAPSET/.bash_history`
: Since the wxGUI shell quoting is not perfect, maybe it is better not to write directly to real shell history, but maintain its own in ~/.grass7/history.

==== Digitizing toolbar ====

* missing string "Select vector map" from the drop-down widget on digitizing toolbar
: on winGRASS, nightly build of 24th May
* after editing vector objects and saving, the changes are not applied on the map. Must be some refresh problem.
* Highlighting problem
: objects selected in the attribute table are not highlighted on the map
: objects selected ton the map are not highlighted in the attribute table.
* Bounding box of a layer broken after deletion of some objects with broken geometry, also displaying of the attribute table broken with a message that the map layer is not a vector one,
: closing the layer from the layer tree also not possible
: after closing GRASS6.4.3 and reopening the project, the layer is restored with all the changes applayed.

==== Attribute manager ====

* Editing attribute table broken
: cannot delete a row, permission denied
: different than selected row dissapears after not succesful row deletion but is back after refreshing the table.
* Not able to insert a value into a table, permision to the temp file denied.

==== Map Display ====

* Clicking with a Query tool on a vector object randomly not able to find an object to display its attributes.

==== I18N ====

* Solve module description string duplication in both grassmods.po and grasswxpy.po files.
: Before fixing this problem in code, please find a way to automagically copy the translated strings to the proper .po files for all the languages.

==== Project file ====
* Find a way to succesfully open a project file made in GRASS6.4 in GRASS7.
: Due to changes (e.g. removal of some flags), the project file is not opened in a correct way. The user can see the layers in the layer tree, but they cannot be displayed in the map canvas. A warning would help.

=== Not to forget about the next time ===

First day:
* presentation of participants

First or second day:
* group photo

Talk:GRASS Community Sprint Prague 2012

2012-05-26T13:42:43Z

⚠️MilenaN: /*I18N */

== Reports ==

=== [[User:Landa|Martin Landa]] ===

* OSGeo4W GRASS package configuration: add liblas support (http://liblas.org/osgeo4w.html) - {{rev|51677}} & {{rev|51679}}
* various wxGUI fixes

=== [[User:Neteler|Markus Neteler]] ===

* Fundraising for this Community Sprint (with great help from Arnulf Christl)
* PSC composition discussion
* fix r.lake segfault for seed map ({{rev|51752}}) together with Markus Metz

=== [[User:Annakrat|Anna Kratochvilova]] ===
* wxGUI/digitizer: add help button to digitizer toolbar ({{rev|51742}})

== Wishes for the Community Sprint ==

* Visual Guide to GRASS GIS modules: scratch a collection of per-module dedicated||or tutorial/task oriented, simple, minimalistic yet attractive, bullet-proof visual examples
**exemplify what GRASS modules do rather than how they do it, thus different than the manuals -- ''rephrase title?''
***make use of existing grass modules list(s), like (this old) [http://grass.itc.it/gdp/grassmanuals/grass63_module_list.pdf GRASS GIS 6.3 Command list (PDF document)]
***visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***ignore modules which cannot be visualised?
**check if (and some-how) task-oriented visual examples could be build out of per-modules examples
**setup specific styling rules (?)
***only one descriptive sentence per module or task
***visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***limited caption(s) describing visuals
**end-up with some independent and beautiful TeXy PDF
**visually enrich existing manuals and/or grass-wiki
** or consider Sphinx

* Review of the python + ctypes example scripts.
: The examples given in the code for {{src|doc/python/raster_example_ctypes.py|version=trunk}}, vector_example_ctypes.py and on the [[Python Ctypes Examples|Ctypes wiki page]] have so far for me all been broken in some way or another. Either grass7 API in grass6 example, typos, incomplete, etc. have made almost all of them fail out of the box. As this is teaching code we should make sure it's perfect :-). See also bug in trac about possible memory leak in r.example.

* Extend {{cmd|r.colors}} documentation by an example for a user-generated logarithmic color table.

== Testing by power users ==

(Power) users from all over the world are kindly invited to assist with testing of new and existing functionality. To collect results and notes, we set up an interactive, collaborative editing tool which works in real-time:

Please check http://titanpad.com/I51nq1SrNc

== Non-Technical ==

=== Discuss role and current composition of GRASS-PSC ===

Discussion about GRASS [[PSC]]:
* Every year members are requested to confirm to continue their work in the PSC.
* After the Community Sprint 2012, the Chair will request updates to the [[RFC1]] from the PSC members.
* Answer within five business days needed.
* In case of no continuation/no answer, a member is replaced in order to refresh the PSC.
* To be eligible for PSC membership, a person should have a demonstrated and substantial involvement in GRASS GIS (operation of the PSC is defined at [[RFC1]]).

=== Misc ===

* Discuss Google Summer of Code (two students are here)
* Discuss GRASS 6.4.3 and 7.0 release schedule
* Define make a manual test procedure for users to simplify testing before new releases, write this up in the wiki ([http://trac.osgeo.org/grass/wiki/HowToTestGrass6 example])

== Semi-Technical ==

=== Improve Web site or use CMS ===
* Discussion about [[CMS]]
** Prototype site: http://grass.fem-environment.eu/
** Problem: enormous job
** Involvement of people, see nice example at http://www.mageia.org/en/contribute/

=== Misc ===
* Document tips & tricks for GRASS compilation with the wxGUI
: there is [http://trac.osgeo.org/grass/wiki/CompileOnWindows Compilation on MS-Windows]
* Discuss new GRASS Book 4th edition in conjunction with the GRASS GIS 7.0 release in early 2013

== Technical ==

=== OSGeo4W ===

* [{{done}} (martinl) - {{rev|51677}} & {{rev|51679}}] GRASS package configuration: add liblas support (http://liblas.org/osgeo4w.html) ([http://wingrass.fsv.cvut.cz/grass64/ download])

=== Android ===

* continue the Android compilation (needs especially the elimination of XDR in rast and rast3d)

=== QGIS-Sextante-GRASS interface ===

* work on new integration with [http://plugins.qgis.org/plugins/sextante/ QGIS-Sextante]

=== Update the GDAL-GRASS interface to GRASS 7 ===

* see http://trac.osgeo.org/gdal/ticket/2953
* LGPL grass IO code written from scratch?

=== Rules Based programming and Agent Based Modelling ===

* Tutorial/Documentation on g.infer
* [http://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.agent r.agent] in GRASS 7

=== Time series ===

* Seminar on Temporal GIS framework demo and discussion: by Soeren Gebbert, done on 24 May 2012
* Add content to http://grass.osgeo.org/grass70/manuals/html70_user/temporalintro.html from Soeren's tutorial
* Discuss temporal GIS wxGUI and WPS integration
* Discuss massive parallel computation of spatio-temporal datasets

=== Automated command user statistics ===

* modify g.parser to write out the list of used commands (without parameters) into a text file for simple, automated command user statistics

=== Mobile: inventory of mobile and touch implementations ===

* [http://code.google.com/p/geopaparazzi/ Geopaparazzi], v.in.geopaparazzi
* GRASS on Android (patches by MN)

=== Cloud computing ===

* g.cloud
* cluster usage best practices

=== GSoC 2012 ===

* v.net.* front end, WMS
* Python API
* Image Segmentation

=== GRASS 7 ===
* PostGIS Topology support
* New features for vector engine
* Discuss Toolbox concept
* Discuss how to implement [[GRASS Metadata Management]]
* [{{done}} (lucadelu) - {{rev|51735}}] Fix category in v.in.mapgen
* New module r.massmov

=== Model integration ===

* GRASS and [http://www.coulthard.org.uk/CAESAR.html Caesar model]

=== GRASS modules fixes ===

* i.atcorr debugging
** Figure out how to get visibility/aerosol depth at 550nm (perhaps from MODIS atmosphere?)
** Under certain circumstances i.atcorr produces NULL data
* GRASS 6.4.3 - [http://trac.osgeo.org/grass/query?status=new&status=assigned&status=reopened&group=type&order=priority&priority=blocker&priority=critical&milestone=6.4.3&milestone=6.4.2&milestone=6.4.1&milestone=6.4.0 Release critical issues to be fixed]

=== Signal handling ===

* The Python based scripts should catch CTRL-C to avoid that clutter is left behind and that ugly traceback is printed into the terminal.

Suggestion by Anne Ghisla (yet not working... ):
<source lang="python">
Index: lib/init/grass.py
===================================================================
--- lib/init/grass.py (revision 51604)
+++ lib/init/grass.py (working copy)
@@ -30,7 +30,12 @@
import subprocess
import re
import platform
+import signal

+# catch user-sent CTRL-C
+signal.signal(signal.SIGINT, lambda a,b:cleanup())
+signal.siginterrupt(signal.SIGINT, False)
+
# Variables substituted during build process
if os.environ.has_key('GISBASE'):
gisbase = os.environ['GISBASE']
</source>

* Currently if vector creation modules fail to create/import they still leave behind the empty skeleton of a map, so you need to use --o for the next time. It would be nice if cleanup could occur. This doesn't happen (visibly) with raster maps as they are composed in $MAPSET/.tmp/ and only moved into the main $MAPSET elements once everything is finished. Vector maps on the otherhand write to the MAPSET in-place.

=== Fix wxGUI problems ===

==== Add a "change language" option in GRASS GUI ====

Implement the diff provided here: http://trac.osgeo.org/grass/ticket/879

==== Fix several issues ====

A. Clerici: please fix:
* ticket https://trac.osgeo.org/grass/ticket/1564
* ticket https://trac.osgeo.org/grass/ticket/1570
* wxGUI bugs (GRASS6.4.2RC3 under Fedora 16):
** In the 'Create histogram of raster map' function, the style pie and the Color for text and axes options are not working. The options run fine on the tcltk GUI and in command line mode.
** In the 'Add scalebar and north arrow', the scale can be modified only once and the option can't be re-entered nor the scale can't be deleted. Also in this case there are no problems with the tcltk GUI.
** the option 'Add raster cell arrows' seems not to work properly. It seems that the arrows in the Map Display cannot zoomed in. It can be checked by the following steps:
*** Load and display the aspect (Spearfish) map.
*** Open the d.rast.arrows panel through the GUI button and choose the same map aspect. Click Apply: the Map Display appears green as expected for the very high resolution.
*** Choose 10 for the 'Draw arrow every Nth grid cell:' option and none as 'Color for drawing grid or “none”' option. The arrows are displayed on the cells of aspect map.
*** To make the arrows visible choose slope as 'Raster map containing values used for arrow length:' and 10.0 as 'Scale factor for arrows'. Zoom in a very small area: the cells of aspect map are enlarged, but the density of arrows remains the same
*** The direction is correctly the same for all arrows inside the same cell but it seems that instead of having an arrow each 10 aspect cells, there is an arrow each 10 pixel of the screen (with tcltk GUI the procedure works fine)
* Fix wx0..6 monitors

==== Layout ====

Optionally, have all-in-one GUI window (requested by many new users!):
<center>
{|
|-
| [[Image:Wxgui_current.png|250px|thumb|center|Current wxGUI layout with detached window components]]
| [[Image:Wxgui_proposal.png|200px|thumb|center|'''Proposal''' for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus by simple rearrangement into one frame)]]
|-
|}
</center>

Proposed solution: wxLayoutAlgorithm(), see [[WxGUI#What_others_do]]

Optionally, a minimalistic cointegration of a map display and the command console. See also this post in grass-user [http://lists.osgeo.org/pipermail/grass-user/2011-April/060346.html Re: [GRASS-user<nowiki>]</nowiki> replacement for d.mon in GRASS 7.0?]
<center>
{|
|-
|[[Image:grass-gis_minimalistic_map-display_with_comman-console__layout_mockup.png|200px|thumb|left|alt text]]
|}
</center>

==== r.li.setup ====
work on r.li.setup for GRASS7

==== Saving History ====

* when using the wxGUI, it needs to write back to the shell history
: `cat wxgui_history.log >> $MAPSET/.bash_history`
: Since the wxGUI shell quoting is not perfect, maybe it is better not to write directly to real shell history, but maintain its own in ~/.grass7/history.

==== Digitizing toolbar ====

* missing string "Select vector map" from the drop-down widget on digitizing toolbar
: on winGRASS, nightly build of 24th May
* after editing vector objects and saving, the changes are not applied on the map. Must be some refresh problem.
* Highlighting problem
: objects selected in the attribute table are not highlighted on the map
: objects selected ton the map are not highlighted in the attribute table.
* Bounding box of a layer broken after deletion of some objects with broken geometry, also displaying of the attribute table broken with a message that the map layer is not a vector one,
: closing the layer from the layer tree also not possible
: after closing GRASS6.4.3 and reopening the project, the layer is restored with all the changes applayed.

==== Attribute manager ====

* Editing attribute table broken
: cannot delete a row, permission denied
: different than selected row dissapears after not succesful row deletion but is back after refreshing the table.
* Not able to insert a value into a table, permision to the temp file denied.

==== Map Display ====

* Clicking with a Query tool on a vector object randomly not able to find an object to display its attributes.

==== I18N ====

* Solve module description string duplication in both grassmods.po and grasswxpy.po files.
: Before fixing this problem in code, please find a way to automagically copy the translated strings to the proper .po files for all the languages.

=== Not to forget about the next time ===

First day:
* presentation of participants

First or second day:
* group photo

Talk:GRASS Community Sprint Prague 2012

2012-05-25T13:23:32Z

⚠️MilenaN: /* Attribute manager */

== Reports ==

=== [[User:Landa|Martin Landa]] ===

* OSGeo4W GRASS package configuration: add liblas support (http://liblas.org/osgeo4w.html) - {{rev
|51677}} & {{rev
|51679}}

=== [[User:Neteler|Markus Neteler]] ===

* Fundraising for this Community Sprint (with great help from Arnulf Christl)
* PSC composition discussion

== Wishes for the Community Sprint ==

* Visual Guide to GRASS GIS modules: scratch a collection of per-module dedicated||or tutorial/task oriented, simple, minimalistic yet attractive, bullet-proof visual examples
**exemplify what GRASS modules do rather than how they do it, thus different than the manuals -- ''rephrase title?''
***make use of existing grass modules list(s), like (this old) [http://grass.itc.it/gdp/grassmanuals/grass63_module_list.pdf GRASS GIS 6.3 Command list (PDF document)]
***visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***ignore modules which cannot be visualised?
**check if (and some-how) task-oriented visual examples could be build out of per-modules examples
**setup specific styling rules (?)
***only one descriptive sentence per module or task
***visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***limited caption(s) describing visuals
**end-up with some independent and beautiful TeXy PDF
**visually enrich existing manuals and/or grass-wiki
** or consider Sphinx

* Review of the python + ctypes example scripts.
: The examples given in the code for {{src|doc/python/raster_example_ctypes.py|version=trunk}}, vector_example_ctypes.py and on the [[Python Ctypes Examples|Ctypes wiki page]] have so far for me all been broken in some way or another. Either grass7 API in grass6 example, typos, incomplete, etc. have made almost all of them fail out of the box. As this is teaching code we should make sure it's perfect :-). See also bug in trac about possible memory leak in r.example.

* Extend {{cmd|r.colors}} documentation by an example for a user-generated logarithmic color table.

== Testing by power users ==

(Power) users from all over the world are kindly invited to assist with testing of new and existing functionality. To collect results and notes, we set up an interactive, collaborative editing tool which works in real-time:

Please check http://titanpad.com/I51nq1SrNc

== Non-Technical ==

=== Discuss role and current composition of GRASS-PSC ===

Discussion about GRASS [[PSC]]:
* Every year members are requested to confirm to continue their work in the PSC.
* After the Community Sprint 2012, the Chair will request updates to the [[RFC1]] from the PSC members.
* Answer within five business days needed.
* In case of no continuation/no answer, a member is replaced in order to refresh the PSC.
* To be eligible for PSC membership, a person should have a demonstrated and substantial involvement in GRASS GIS (operation of the PSC is defined at [[RFC1]]).

=== Misc ===

* Discuss Google Summer of Code (two students are here)
* Discuss GRASS 6.4.3 and 7.0 release schedule
* Define make a manual test procedure for users to simplify testing before new releases, write this up in the wiki ([http://trac.osgeo.org/grass/wiki/HowToTestGrass6 example])

== Semi-Technical ==

=== Improve Web site or use CMS ===
* Discussion about [[CMS]]
** Prototype site: http://grass.fem-environment.eu/
** Problem: enormous job
** Involvement of people, see nice example at http://www.mageia.org/en/contribute/

=== Misc ===
* Document tips & tricks for GRASS compilation with the wxGUI
: there is [http://trac.osgeo.org/grass/wiki/CompileOnWindows Compilation on MS-Windows]
* Discuss new GRASS Book 4th edition in conjunction with the GRASS GIS 7.0 release in early 2013

== Technical ==

=== OSGeo4W ===

* [{{done}} (martinl) - {{rev|51677}} & {{rev|51679}}] GRASS package configuration: add liblas support (http://liblas.org/osgeo4w.html) ([http://wingrass.fsv.cvut.cz/grass64/ download])

=== Android ===

* continue the Android compilation (needs especially the elimination of XDR in rast and rast3d)

=== QGIS-Sextante-GRASS interface ===

* work on new integration with [http://plugins.qgis.org/plugins/sextante/ QGIS-Sextante]

=== Update the GDAL-GRASS interface to GRASS 7 ===

* see http://trac.osgeo.org/gdal/ticket/2953
* LGPL grass IO code written from scratch?

=== Rules Based programming and Agent Based Modelling ===

* Tutorial/Documentation on g.infer
* [http://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.agent r.agent] in GRASS 7

=== Time series ===

* Seminar on Temporal GIS framework demo and discussion: by Soeren Gebbert, done on 24 May 2012
* Add content to http://grass.osgeo.org/grass70/manuals/html70_user/temporalintro.html from Soeren's tutorial
* Discuss temporal GIS wxGUI and WPS integration
* Discuss massive parallel computation of spatio-temporal datasets

=== Automated command user statistics ===

* modify g.parser to write out the list of used commands (without parameters) into a text file for simple, automated command user statistics

=== Mobile: inventory of mobile and touch implementations ===

* [http://code.google.com/p/geopaparazzi/ Geopaparazzi], v.in.geopaparazzi
* GRASS on Android (patches by MN)

=== Cloud computing ===

* g.cloud
* cluster usage best practices

=== GSoC 2012 ===

* v.net.* front end, WMS
* Python API
* Image Segmentation

=== GRASS 7 ===
* PostGIS Topology support
* New features for vector engine
* Discuss Toolbox concept
* Discuss how to implement [[GRASS Metadata Management]]
* [{{done}} (lucadelu) - {{rev|51735}}] Fix category in v.in.mapgen
* New module r.massmov

=== Model integration ===

* GRASS and [http://www.coulthard.org.uk/CAESAR.html Caesar model]

=== GRASS modules fixes ===

* i.atcorr debugging
** Figure out how to get visibility/aerosol depth at 550nm (perhaps from MODIS atmosphere?)
** Under certain circumstances i.atcorr produces NULL data
* GRASS 6.4.3 - [http://trac.osgeo.org/grass/query?status=new&status=assigned&status=reopened&group=type&order=priority&priority=blocker&priority=critical&milestone=6.4.3&milestone=6.4.2&milestone=6.4.1&milestone=6.4.0 Release critical issues to be fixed]

=== Signal handling ===

* The Python based scripts should catch CTRL-C to avoid that clutter is left behind and that ugly traceback is printed into the terminal.

Suggestion by Anne Ghisla (yet not working... ):
<source lang="python">
Index: lib/init/grass.py
===================================================================
--- lib/init/grass.py (revision 51604)
+++ lib/init/grass.py (working copy)
@@ -30,7 +30,12 @@
import subprocess
import re
import platform
+import signal

+# catch user-sent CTRL-C
+signal.signal(signal.SIGINT, lambda a,b:cleanup())
+signal.siginterrupt(signal.SIGINT, False)
+
# Variables substituted during build process
if os.environ.has_key('GISBASE'):
gisbase = os.environ['GISBASE']
</source>

* Currently if vector creation modules fail to create/import they still leave behind the empty skeleton of a map, so you need to use --o for the next time. It would be nice if cleanup could occur. This doesn't happen (visibly) with raster maps as they are composed in $MAPSET/.tmp/ and only moved into the main $MAPSET elements once everything is finished. Vector maps on the otherhand write to the MAPSET in-place.

=== Fix wxGUI problems ===

==== Add a "change language" option in GRASS GUI ====

Implement the diff provided here: http://trac.osgeo.org/grass/ticket/879

==== Fix several issues ====

A. Clerici: please fix:
* ticket https://trac.osgeo.org/grass/ticket/1564
* ticket https://trac.osgeo.org/grass/ticket/1570
* wxGUI bugs (GRASS6.4.2RC3 under Fedora 16):
** In the 'Create histogram of raster map' function, the style pie and the Color for text and axes options are not working. The options run fine on the tcltk GUI and in command line mode.
** In the 'Add scalebar and north arrow', the scale can be modified only once and the option can't be re-entered nor the scale can't be deleted. Also in this case there are no problems with the tcltk GUI.
** the option 'Add raster cell arrows' seems not to work properly. It seems that the arrows in the Map Display cannot zoomed in. It can be checked by the following steps:
*** Load and display the aspect (Spearfish) map.
*** Open the d.rast.arrows panel through the GUI button and choose the same map aspect. Click Apply: the Map Display appears green as expected for the very high resolution.
*** Choose 10 for the 'Draw arrow every Nth grid cell:' option and none as 'Color for drawing grid or “none”' option. The arrows are displayed on the cells of aspect map.
*** To make the arrows visible choose slope as 'Raster map containing values used for arrow length:' and 10.0 as 'Scale factor for arrows'. Zoom in a very small area: the cells of aspect map are enlarged, but the density of arrows remains the same
*** The direction is correctly the same for all arrows inside the same cell but it seems that instead of having an arrow each 10 aspect cells, there is an arrow each 10 pixel of the screen (with tcltk GUI the procedure works fine)
* Fix wx0..6 monitors

==== Layout ====

Optionally, have all-in-one GUI window (requested by many new users!):
<center>
{|
|-
| [[Image:Wxgui_current.png|250px|thumb|center|Current wxGUI layout with detached window components]]
| [[Image:Wxgui_proposal.png|200px|thumb|center|'''Proposal''' for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus by simple rearrangement into one frame)]]
|-
|}
</center>

Proposed solution: wxLayoutAlgorithm(), see [[WxGUI#What_others_do]]

==== r.li.setup ====
work on r.li.setup for GRASS7

==== Saving History ====

* when using the wxGUI, it needs to write back to the shell history
: `cat wxgui_history.log >> $MAPSET/.bash_history`
: Since the wxGUI shell quoting is not perfect, maybe it is better not to write directly to real shell history, but maintain its own in ~/.grass7/history.

==== Digitizing toolbar ====

* missing string "Select vector map" from the drop-down widget on digitizing toolbar
: on winGRASS, nightly build of 24th May
* after editing vector objects and saving, the changes are not applied on the map. Must be some refresh problem.
* Highlighting problem
: objects selected in the attribute table are not highlighted on the map
: objects selected ton the map are not highlighted in the attribute table.
* Bounding box of a layer broken after deletion of some objects with broken geometry, also displaying of the attribute table broken with a message that the map layer is not a vector one,
: closing the layer from the layer tree also not possible
: after closing GRASS6.4.3 and reopening the project, the layer is restored with all the changes applayed.

==== Attribute manager ====

* Editing attribute table broken
: cannot delete a row, permission denied
: different than selected row dissapears after not succesful row deletion but is back after refreshing the table.
* Not able to insert a value into a table, permision to the temp file denied.

==== Map Display ====

* Clicking with a Query tool on a vector object randomly not able to find an object to display its attributes.

=== Not to forget about the next time ===

First day:
* presentation of participants

First or second day:
* group photo

Talk:GRASS Community Sprint Prague 2012

2012-05-25T10:23:54Z

⚠️MilenaN: /* Map Display */

== Reports ==

=== [[User:Landa|Martin Landa]] ===

* OSGeo4W GRASS package configuration: add liblas support (http://liblas.org/osgeo4w.html) - {{rev
|51677}} & {{rev
|51679}}

=== [[User:Neteler|Markus Neteler]] ===

* Fundraising for this Community Sprint (with great help from Arnulf Christl)
* PSC composition discussion

== Wishes for the Community Sprint ==

* Visual Guide to GRASS GIS modules: scratch a collection of per-module dedicated||or tutorial/task oriented, simple, minimalistic yet attractive, bullet-proof visual examples
**exemplify what GRASS modules do rather than how they do it, thus different than the manuals -- ''rephrase title?''
***make use of existing grass modules list(s), like (this old) [http://grass.itc.it/gdp/grassmanuals/grass63_module_list.pdf GRASS GIS 6.3 Command list (PDF document)]
***visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***ignore modules which cannot be visualised?
**check if (and some-how) task-oriented visual examples could be build out of per-modules examples
**setup specific styling rules (?)
***only one descriptive sentence per module or task
***visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***limited caption(s) describing visuals
**end-up with some independent and beautiful TeXy PDF
**visually enrich existing manuals and/or grass-wiki
** or consider Sphinx

* Review of the python + ctypes example scripts.
: The examples given in the code for {{src|doc/python/raster_example_ctypes.py|version=trunk}}, vector_example_ctypes.py and on the [[Python Ctypes Examples|Ctypes wiki page]] have so far for me all been broken in some way or another. Either grass7 API in grass6 example, typos, incomplete, etc. have made almost all of them fail out of the box. As this is teaching code we should make sure it's perfect :-). See also bug in trac about possible memory leak in r.example.

* Extend {{cmd|r.colors}} documentation by an example for a user-generated logarithmic color table.

== Testing by power users ==

(Power) users from all over the world are kindly invited to assist with testing of new and existing functionality. To collect results and notes, we set up an interactive, collaborative editing tool which works in real-time:

Please check http://titanpad.com/I51nq1SrNc

== Non-Technical ==

=== Discuss role and current composition of GRASS-PSC ===

Discussion about GRASS [[PSC]]:
* Every year members are requested to confirm to continue their work in the PSC.
* After the Community Sprint 2012, the Chair will request updates to the [[RFC1]] from the PSC members.
* Answer within five business days needed.
* In case of no continuation/no answer, a member is replaced in order to refresh the PSC.
* To be eligible for PSC membership, a person should have a demonstrated and substantial involvement in GRASS GIS (operation of the PSC is defined at [[RFC1]]).

=== Misc ===

* Discuss Google Summer of Code (two students are here)
* Discuss GRASS 6.4.3 and 7.0 release schedule
* Define make a manual test procedure for users to simplify testing before new releases, write this up in the wiki ([http://trac.osgeo.org/grass/wiki/HowToTestGrass6 example])

== Semi-Technical ==

=== Improve Web site or use CMS ===
* Discussion about [[CMS]]
** Prototype site: http://grass.fem-environment.eu/
** Problem: enormous job
** Involvement of people, see nice example at http://www.mageia.org/en/contribute/

=== Misc ===
* Document tips & tricks for GRASS compilation with the wxGUI
: there is [http://trac.osgeo.org/grass/wiki/CompileOnWindows Compilation on MS-Windows]
* Discuss new GRASS Book 4th edition in conjunction with the GRASS GIS 7.0 release in early 2013

== Technical ==

=== OSGeo4W ===

* {{done}} <strike>GRASS package configuration: add liblas support (http://liblas.org/osgeo4w.html)</strike> (martinl) - {{rev
|51677}} & {{rev
|51679}} ([http://wingrass.fsv.cvut.cz/grass64/ download])

=== Android ===

* continue the Android compilation (needs especially the elimination of XDR in rast and rast3d)

=== QGIS-Sextante-GRASS interface ===

* work on new integration with [http://plugins.qgis.org/plugins/sextante/ QGIS-Sextante]

=== Update the GDAL-GRASS interface to GRASS 7 ===

* see http://trac.osgeo.org/gdal/ticket/2953
* LGPL grass IO code written from scratch?

=== Rules Based programming and Agent Based Modelling ===

* Tutorial/Documentation on g.infer
* [http://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.agent r.agent] in GRASS 7

=== Time series ===

* Seminar on Temporal GIS framework demo and discussion: by Soeren Gebbert, done on 24 May 2012
* Add content to http://grass.osgeo.org/grass70/manuals/html70_user/temporalintro.html from Soeren's tutorial
* Discuss temporal GIS wxGUI and WPS integration
* Discuss massive parallel computation of spatio-temporal datasets

=== Automated command user statistics ===

* modify g.parser to write out the list of used commands (without parameters) into a text file for simple, automated command user statistics

=== Mobile: inventory of mobile and touch implementations ===

* [http://code.google.com/p/geopaparazzi/ Geopaparazzi], v.in.geopaparazzi
* GRASS on Android (patches by MN)

=== Cloud computing ===

* g.cloud
* cluster usage best practices

=== GSoC 2012 ===

* v.net.* front end, WMS
* Python API
* Image Segmentation

=== GRASS 7 ===
* PostGIS Topology support
* New features for vector engine
* Discuss Toolbox concept
* Discuss how to implement [[GRASS Metadata Management]]

=== Model integration ===

* GRASS and [http://www.coulthard.org.uk/CAESAR.html Caesar model]

=== GRASS modules fixes ===

* i.atcorr debugging
** Figure out how to get visibility/aerosol depth at 550nm (perhaps from MODIS atmosphere?)
** Under certain circumstances i.atcorr produces NULL data
* GRASS 6.4.3 - [http://trac.osgeo.org/grass/query?status=new&status=assigned&status=reopened&group=type&order=priority&priority=blocker&priority=critical&milestone=6.4.3&milestone=6.4.2&milestone=6.4.1&milestone=6.4.0 Release critical issues to be fixed]

=== Signal handling ===

* The Python based scripts should catch CTRL-C to avoid that clutter is left behind and that ugly traceback is printed into the terminal.

Suggestion by Anne Ghisla (yet not working... ):
<source lang="python">
Index: lib/init/grass.py
===================================================================
--- lib/init/grass.py (revision 51604)
+++ lib/init/grass.py (working copy)
@@ -30,7 +30,12 @@
import subprocess
import re
import platform
+import signal

+# catch user-sent CTRL-C
+signal.signal(signal.SIGINT, lambda a,b:cleanup())
+signal.siginterrupt(signal.SIGINT, False)
+
# Variables substituted during build process
if os.environ.has_key('GISBASE'):
gisbase = os.environ['GISBASE']
</source>

* Currently if vector creation modules fail to create/import they still leave behind the empty skeleton of a map, so you need to use --o for the next time. It would be nice if cleanup could occur. This doesn't happen (visibly) with raster maps as they are composed in $MAPSET/.tmp/ and only moved into the main $MAPSET elements once everything is finished. Vector maps on the otherhand write to the MAPSET in-place.

=== Fix wxGUI problems ===
A. Clerici: please fix:
* ticket https://trac.osgeo.org/grass/ticket/1564
* ticket https://trac.osgeo.org/grass/ticket/1570
* wxGUI bugs (GRASS6.4.2RC3 under Fedora 16):
** In the 'Create histogram of raster map' function, the style pie and the Color for text and axes options are not working. The options run fine on the tcltk GUI and in command line mode.
** In the 'Add scalebar and north arrow', the scale can be modified only once and the option can't be re-entered nor the scale can't be deleted. Also in this case there are no problems with the tcltk GUI.
** the option 'Add raster cell arrows' seems not to work properly. It seems that the arrows in the Map Display cannot zoomed in. It can be checked by the following steps:
*** Load and display the aspect (Spearfish) map.
*** Open the d.rast.arrows panel through the GUI button and choose the same map aspect. Click Apply: the Map Display appears green as expected for the very high resolution.
*** Choose 10 for the 'Draw arrow every Nth grid cell:' option and none as 'Color for drawing grid or “none”' option. The arrows are displayed on the cells of aspect map.
*** To make the arrows visible choose slope as 'Raster map containing values used for arrow length:' and 10.0 as 'Scale factor for arrows'. Zoom in a very small area: the cells of aspect map are enlarged, but the density of arrows remains the same
*** The direction is correctly the same for all arrows inside the same cell but it seems that instead of having an arrow each 10 aspect cells, there is an arrow each 10 pixel of the screen (with tcltk GUI the procedure works fine)
* Fix wx0..6 monitors

==== Layout ====

Optionally, have all-in-one GUI window (requested by many new users!):
<center>
{|
|-
| [[Image:Wxgui_current.png|250px|thumb|center|Current wxGUI layout with detached window components]]
| [[Image:Wxgui_proposal.png|200px|thumb|center|'''Proposal''' for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus by simple rearrangement into one frame)]]
|-
|}
</center>

Proposed solution: wxLayoutAlgorithm(), see [[WxGUI#What_others_do]]

==== r.li.setup ====
work on r.li.setup for GRASS7

==== Saving History ====

* when using the wxGUI, it needs to write back to the shell history
: `cat wxgui_history.log >> $MAPSET/.bash_history`
: Since the wxGUI shell quoting is not perfect, maybe it is better not to write directly to real shell history, but maintain its own in ~/.grass7/history.

==== Digitizing toolbar ====

* missing string "Select vector map" from the drop-down widget on digitizing toolbar
: on winGRASS, nightly build of 24th May
* after editing vector objects and saving, the changes are not applied on the map. Must be some refresh problem.
* Highlighting problem
: objects selected in the attribute table are not highlighted on the map
: objects selected ton the map are not highlighted in the attribute table.
* Bounding box of a layer broken after deletion of some objects with broken geometry, also displaying of the attribute table broken with a message that the map layer is not a vector one,
: closing the layer from the layer tree also not possible
: after closing GRASS6.4.3 and reopening the project, the layer is restored with all the changes applayed.

==== Attribute manager ====

* Editing attribute table broken
: cannot delete a row, permission denied
: different than selected row dissapears after not succesful row deletion but is back after refreshing the table.

==== Map Display ====

* Clicking with a Query tool on a vector object randomly not able to find an object to display its attributes.

Talk:GRASS Community Sprint Prague 2012

2012-05-25T10:17:22Z

⚠️MilenaN: /* Digitizing toolbar */

== Reports ==

=== [[User:Landa|Martin Landa]] ===

* OSGeo4W GRASS package configuration: add liblas support (http://liblas.org/osgeo4w.html) - {{rev
|51677}} & {{rev
|51679}}

=== [[User:Neteler|Markus Neteler]] ===

* Fundraising for this Community Sprint (with great help from Arnulf Christl)
* PSC composition discussion

== Wishes for the Community Sprint ==

* Visual Guide to GRASS GIS modules: scratch a collection of per-module dedicated||or tutorial/task oriented, simple, minimalistic yet attractive, bullet-proof visual examples
**exemplify what GRASS modules do rather than how they do it, thus different than the manuals -- ''rephrase title?''
***make use of existing grass modules list(s), like (this old) [http://grass.itc.it/gdp/grassmanuals/grass63_module_list.pdf GRASS GIS 6.3 Command list (PDF document)]
***visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***ignore modules which cannot be visualised?
**check if (and some-how) task-oriented visual examples could be build out of per-modules examples
**setup specific styling rules (?)
***only one descriptive sentence per module or task
***visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***limited caption(s) describing visuals
**end-up with some independent and beautiful TeXy PDF
**visually enrich existing manuals and/or grass-wiki
** or consider Sphinx

* Review of the python + ctypes example scripts.
: The examples given in the code for {{src|doc/python/raster_example_ctypes.py|version=trunk}}, vector_example_ctypes.py and on the [[Python Ctypes Examples|Ctypes wiki page]] have so far for me all been broken in some way or another. Either grass7 API in grass6 example, typos, incomplete, etc. have made almost all of them fail out of the box. As this is teaching code we should make sure it's perfect :-). See also bug in trac about possible memory leak in r.example.

* Extend {{cmd|r.colors}} documentation by an example for a user-generated logarithmic color table.

== Testing by power users ==

(Power) users from all over the world are kindly invited to assist with testing of new and existing functionality. To collect results and notes, we set up an interactive, collaborative editing tool which works in real-time:

Please check http://titanpad.com/I51nq1SrNc

== Non-Technical ==

=== Discuss role and current composition of GRASS-PSC ===

Discussion about GRASS [[PSC]]:
* Every year members are requested to confirm to continue their work in the PSC.
* After the Community Sprint 2012, the Chair will request updates to the [[RFC1]] from the PSC members.
* Answer within five business days needed.
* In case of no continuation/no answer, a member is replaced in order to refresh the PSC.
* To be eligible for PSC membership, a person should have a demonstrated and substantial involvement in GRASS GIS (operation of the PSC is defined at [[RFC1]]).

=== Misc ===

* Discuss Google Summer of Code (two students are here)
* Discuss GRASS 6.4.3 and 7.0 release schedule
* Define make a manual test procedure for users to simplify testing before new releases, write this up in the wiki ([http://trac.osgeo.org/grass/wiki/HowToTestGrass6 example])

== Semi-Technical ==

=== Improve Web site or use CMS ===
* Discussion about [[CMS]]
** Prototype site: http://grass.fem-environment.eu/
** Problem: enormous job
** Involvement of people, see nice example at http://www.mageia.org/en/contribute/

=== Misc ===
* Document tips & tricks for GRASS compilation with the wxGUI
: there is [http://trac.osgeo.org/grass/wiki/CompileOnWindows Compilation on MS-Windows]
* Discuss new GRASS Book 4th edition in conjunction with the GRASS GIS 7.0 release in early 2013

== Technical ==

=== OSGeo4W ===

* {{done}} <strike>GRASS package configuration: add liblas support (http://liblas.org/osgeo4w.html)</strike> (martinl) - {{rev
|51677}} & {{rev
|51679}} ([http://wingrass.fsv.cvut.cz/grass64/ download])

=== Android ===

* continue the Android compilation (needs especially the elimination of XDR in rast and rast3d)

=== QGIS-Sextante-GRASS interface ===

* work on new integration with [http://plugins.qgis.org/plugins/sextante/ QGIS-Sextante]

=== Update the GDAL-GRASS interface to GRASS 7 ===

* see http://trac.osgeo.org/gdal/ticket/2953
* LGPL grass IO code written from scratch?

=== Rules Based programming and Agent Based Modelling ===

* Tutorial/Documentation on g.infer
* [http://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.agent r.agent] in GRASS 7

=== Time series ===

* Seminar on Temporal GIS framework demo and discussion: by Soeren Gebbert, done on 24 May 2012
* Add content to http://grass.osgeo.org/grass70/manuals/html70_user/temporalintro.html from Soeren's tutorial
* Discuss temporal GIS wxGUI and WPS integration
* Discuss massive parallel computation of spatio-temporal datasets

=== Automated command user statistics ===

* modify g.parser to write out the list of used commands (without parameters) into a text file for simple, automated command user statistics

=== Mobile: inventory of mobile and touch implementations ===

* [http://code.google.com/p/geopaparazzi/ Geopaparazzi], v.in.geopaparazzi
* GRASS on Android (patches by MN)

=== Cloud computing ===

* g.cloud
* cluster usage best practices

=== GSoC 2012 ===

* v.net.* front end, WMS
* Python API
* Image Segmentation

=== GRASS 7 ===
* PostGIS Topology support
* New features for vector engine
* Discuss Toolbox concept
* Discuss how to implement [[GRASS Metadata Management]]

=== Model integration ===

* GRASS and [http://www.coulthard.org.uk/CAESAR.html Caesar model]

=== GRASS modules fixes ===

* i.atcorr debugging
** Figure out how to get visibility/aerosol depth at 550nm (perhaps from MODIS atmosphere?)
** Under certain circumstances i.atcorr produces NULL data
* GRASS 6.4.3 - [http://trac.osgeo.org/grass/query?status=new&status=assigned&status=reopened&group=type&order=priority&priority=blocker&priority=critical&milestone=6.4.3&milestone=6.4.2&milestone=6.4.1&milestone=6.4.0 Release critical issues to be fixed]

=== Signal handling ===

* The Python based scripts should catch CTRL-C to avoid that clutter is left behind and that ugly traceback is printed into the terminal.

Suggestion by Anne Ghisla (yet not working... ):
<source lang="python">
Index: lib/init/grass.py
===================================================================
--- lib/init/grass.py (revision 51604)
+++ lib/init/grass.py (working copy)
@@ -30,7 +30,12 @@
import subprocess
import re
import platform
+import signal

+# catch user-sent CTRL-C
+signal.signal(signal.SIGINT, lambda a,b:cleanup())
+signal.siginterrupt(signal.SIGINT, False)
+
# Variables substituted during build process
if os.environ.has_key('GISBASE'):
gisbase = os.environ['GISBASE']
</source>

* Currently if vector creation modules fail to create/import they still leave behind the empty skeleton of a map, so you need to use --o for the next time. It would be nice if cleanup could occur. This doesn't happen (visibly) with raster maps as they are composed in $MAPSET/.tmp/ and only moved into the main $MAPSET elements once everything is finished. Vector maps on the otherhand write to the MAPSET in-place.

=== Fix wxGUI problems ===
A. Clerici: please fix:
* ticket https://trac.osgeo.org/grass/ticket/1564
* ticket https://trac.osgeo.org/grass/ticket/1570
* wxGUI bugs (GRASS6.4.2RC3 under Fedora 16):
** In the 'Create histogram of raster map' function, the style pie and the Color for text and axes options are not working. The options run fine on the tcltk GUI and in command line mode.
** In the 'Add scalebar and north arrow', the scale can be modified only once and the option can't be re-entered nor the scale can't be deleted. Also in this case there are no problems with the tcltk GUI.
** the option 'Add raster cell arrows' seems not to work properly. It seems that the arrows in the Map Display cannot zoomed in. It can be checked by the following steps:
*** Load and display the aspect (Spearfish) map.
*** Open the d.rast.arrows panel through the GUI button and choose the same map aspect. Click Apply: the Map Display appears green as expected for the very high resolution.
*** Choose 10 for the 'Draw arrow every Nth grid cell:' option and none as 'Color for drawing grid or “none”' option. The arrows are displayed on the cells of aspect map.
*** To make the arrows visible choose slope as 'Raster map containing values used for arrow length:' and 10.0 as 'Scale factor for arrows'. Zoom in a very small area: the cells of aspect map are enlarged, but the density of arrows remains the same
*** The direction is correctly the same for all arrows inside the same cell but it seems that instead of having an arrow each 10 aspect cells, there is an arrow each 10 pixel of the screen (with tcltk GUI the procedure works fine)
* Fix wx0..6 monitors

==== Layout ====

Optionally, have all-in-one GUI window (requested by many new users!):
<center>
{|
|-
| [[Image:Wxgui_current.png|250px|thumb|center|Current wxGUI layout with detached window components]]
| [[Image:Wxgui_proposal.png|200px|thumb|center|'''Proposal''' for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus by simple rearrangement into one frame)]]
|-
|}
</center>

Proposed solution: wxLayoutAlgorithm(), see [[WxGUI#What_others_do]]

==== r.li.setup ====
work on r.li.setup for GRASS7

==== Saving History ====

* when using the wxGUI, it needs to write back to the shell history
: `cat wxgui_history.log >> $MAPSET/.bash_history`
: Since the wxGUI shell quoting is not perfect, maybe it is better not to write directly to real shell history, but maintain its own in ~/.grass7/history.

==== Digitizing toolbar ====

* missing string "Select vector map" from the drop-down widget on digitizing toolbar
: on winGRASS, nightly build of 24th May
* after editing vector objects and saving, the changes are not applied on the map. Must be some refresh problem.
* Highlighting problem
: objects selected in the attribute table are not highlighted on the map
: objects selected ton the map are not highlighted in the attribute table.
* Bounding box of a layer broken after deletion of some objects with broken geometry, also displaying of the attribute table broken with a message that the map layer is not a vector one,
: closing the layer from the layer tree also not possible
: after closing GRASS6.4.3 and reopening the project, the layer is restored with all the changes applayed.

==== Attribute manager ====

* Editing attribute table broken
: cannot delete a row, permission denied
: different than selected row dissapears after not succesful row deletion but is back after refreshing the table.

Talk:GRASS Community Sprint Prague 2012

2012-05-25T09:45:28Z

⚠️MilenaN: /* Digitizing toolbar */ + more issues

== Reports ==

=== [[User:Landa|Martin Landa]] ===

* OSGeo4W GRASS package configuration: add liblas support (http://liblas.org/osgeo4w.html) - {{rev
|51677}} & {{rev
|51679}}

=== [[User:Neteler|Markus Neteler]] ===

* Fundraising for this Community Sprint (with great help from Arnulf Christl)
* PSC composition discussion

== Wishes for the Community Sprint ==

* Visual Guide to GRASS GIS modules: scratch a collection of per-module dedicated||or tutorial/task oriented, simple, minimalistic yet attractive, bullet-proof visual examples
**exemplify what GRASS modules do rather than how they do it, thus different than the manuals -- ''rephrase title?''
***make use of existing grass modules list(s), like (this old) [http://grass.itc.it/gdp/grassmanuals/grass63_module_list.pdf GRASS GIS 6.3 Command list (PDF document)]
***visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***ignore modules which cannot be visualised?
**check if (and some-how) task-oriented visual examples could be build out of per-modules examples
**setup specific styling rules (?)
***only one descriptive sentence per module or task
***visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***limited caption(s) describing visuals
**end-up with some independent and beautiful TeXy PDF
**visually enrich existing manuals and/or grass-wiki
** or consider Sphinx

* Review of the python + ctypes example scripts.
: The examples given in the code for {{src|doc/python/raster_example_ctypes.py|version=trunk}}, vector_example_ctypes.py and on the [[Python Ctypes Examples|Ctypes wiki page]] have so far for me all been broken in some way or another. Either grass7 API in grass6 example, typos, incomplete, etc. have made almost all of them fail out of the box. As this is teaching code we should make sure it's perfect :-). See also bug in trac about possible memory leak in r.example.

* Extend {{cmd|r.colors}} documentation by an example for a user-generated logarithmic color table.

== Testing by power users ==

(Power) users from all over the world are kindly invited to assist with testing of new and existing functionality. To collect results and notes, we set up an interactive, collaborative editing tool which works in real-time:

Please check http://titanpad.com/I51nq1SrNc

== Non-Technical ==

=== Discuss role and current composition of GRASS-PSC ===

Discussion about GRASS [[PSC]]:
* Every year members are requested to confirm to continue their work in the PSC.
* After the Community Sprint 2012, the Chair will request updates to the [[RFC1]] from the PSC members.
* Answer within five business days needed.
* In case of no continuation/no answer, a member is replaced in order to refresh the PSC.
* To be eligible for PSC membership, a person should have a demonstrated and substantial involvement in GRASS GIS (operation of the PSC is defined at [[RFC1]]).

=== Misc ===

* Discuss Google Summer of Code (two students are here)
* Discuss GRASS 6.4.3 and 7.0 release schedule
* Define make a manual test procedure for users to simplify testing before new releases, write this up in the wiki ([http://trac.osgeo.org/grass/wiki/HowToTestGrass6 example])

== Semi-Technical ==

=== Improve Web site or use CMS ===
* Discussion about [[CMS]]
** Prototype site: http://grass.fem-environment.eu/
** Problem: enormous job
** Involvement of people, see nice example at http://www.mageia.org/en/contribute/

=== Misc ===
* Document tips & tricks for GRASS compilation with the wxGUI
: there is [http://trac.osgeo.org/grass/wiki/CompileOnWindows Compilation on MS-Windows]
* Discuss new GRASS Book 4th edition in conjunction with the GRASS GIS 7.0 release in early 2013

== Technical ==

=== OSGeo4W ===

* {{done}} <strike>GRASS package configuration: add liblas support (http://liblas.org/osgeo4w.html)</strike> (martinl) - {{rev
|51677}} & {{rev
|51679}} ([http://wingrass.fsv.cvut.cz/grass64/ download])

=== Android ===

* continue the Android compilation (needs especially the elimination of XDR in rast and rast3d)

=== QGIS-Sextante-GRASS interface ===

* work on new integration with [http://plugins.qgis.org/plugins/sextante/ QGIS-Sextante]

=== Update the GDAL-GRASS interface to GRASS 7 ===

* see http://trac.osgeo.org/gdal/ticket/2953
* LGPL grass IO code written from scratch?

=== Rules Based programming and Agent Based Modelling ===

* Tutorial/Documentation on g.infer
* [http://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.agent r.agent] in GRASS 7

=== Time series ===

* Seminar on Temporal GIS framework demo and discussion: by Soeren Gebbert, done on 24 May 2012
* Add content to http://grass.osgeo.org/grass70/manuals/html70_user/temporalintro.html from Soeren's tutorial
* Discuss temporal GIS wxGUI and WPS integration
* Discuss massive parallel computation of spatio-temporal datasets

=== Automated command user statistics ===

* modify g.parser to write out the list of used commands (without parameters) into a text file for simple, automated command user statistics

=== Mobile: inventory of mobile and touch implementations ===

* [http://code.google.com/p/geopaparazzi/ Geopaparazzi], v.in.geopaparazzi
* GRASS on Android (patches by MN)

=== Cloud computing ===

* g.cloud
* cluster usage best practices

=== GSoC 2012 ===

* v.net.* front end, WMS
* Python API
* Image Segmentation

=== GRASS 7 ===
* PostGIS Topology support
* New features for vector engine
* Discuss Toolbox concept
* Discuss how to implement [[GRASS Metadata Management]]

=== Model integration ===

* GRASS and [http://www.coulthard.org.uk/CAESAR.html Caesar model]

=== GRASS modules fixes ===

* i.atcorr debugging
** Figure out how to get visibility/aerosol depth at 550nm (perhaps from MODIS atmosphere?)
** Under certain circumstances i.atcorr produces NULL data
* GRASS 6.4.3 - [http://trac.osgeo.org/grass/query?status=new&status=assigned&status=reopened&group=type&order=priority&priority=blocker&priority=critical&milestone=6.4.3&milestone=6.4.2&milestone=6.4.1&milestone=6.4.0 Release critical issues to be fixed]

=== Signal handling ===

* The Python based scripts should catch CTRL-C to avoid that clutter is left behind and that ugly traceback is printed into the terminal.

Suggestion by Anne Ghisla (yet not working... ):
<source lang="python">
Index: lib/init/grass.py
===================================================================
--- lib/init/grass.py (revision 51604)
+++ lib/init/grass.py (working copy)
@@ -30,7 +30,12 @@
import subprocess
import re
import platform
+import signal

+# catch user-sent CTRL-C
+signal.signal(signal.SIGINT, lambda a,b:cleanup())
+signal.siginterrupt(signal.SIGINT, False)
+
# Variables substituted during build process
if os.environ.has_key('GISBASE'):
gisbase = os.environ['GISBASE']
</source>

* Currently if vector creation modules fail to create/import they still leave behind the empty skeleton of a map, so you need to use --o for the next time. It would be nice if cleanup could occur. This doesn't happen (visibly) with raster maps as they are composed in $MAPSET/.tmp/ and only moved into the main $MAPSET elements once everything is finished. Vector maps on the otherhand write to the MAPSET in-place.

=== Fix wxGUI problems ===
A. Clerici: please fix:
* ticket https://trac.osgeo.org/grass/ticket/1564
* ticket https://trac.osgeo.org/grass/ticket/1570
* wxGUI bugs (GRASS6.4.2RC3 under Fedora 16):
** In the 'Create histogram of raster map' function, the style pie and the Color for text and axes options are not working. The options run fine on the tcltk GUI and in command line mode.
** In the 'Add scalebar and north arrow', the scale can be modified only once and the option can't be re-entered nor the scale can't be deleted. Also in this case there are no problems with the tcltk GUI.
** the option 'Add raster cell arrows' seems not to work properly. It seems that the arrows in the Map Display cannot zoomed in. It can be checked by the following steps:
*** Load and display the aspect (Spearfish) map.
*** Open the d.rast.arrows panel through the GUI button and choose the same map aspect. Click Apply: the Map Display appears green as expected for the very high resolution.
*** Choose 10 for the 'Draw arrow every Nth grid cell:' option and none as 'Color for drawing grid or “none”' option. The arrows are displayed on the cells of aspect map.
*** To make the arrows visible choose slope as 'Raster map containing values used for arrow length:' and 10.0 as 'Scale factor for arrows'. Zoom in a very small area: the cells of aspect map are enlarged, but the density of arrows remains the same
*** The direction is correctly the same for all arrows inside the same cell but it seems that instead of having an arrow each 10 aspect cells, there is an arrow each 10 pixel of the screen (with tcltk GUI the procedure works fine)
* Fix wx0..6 monitors

==== Layout ====

Optionally, have all-in-one GUI window (requested by many new users!):
<center>
{|
|-
| [[Image:Wxgui_current.png|250px|thumb|center|Current wxGUI layout with detached window components]]
| [[Image:Wxgui_proposal.png|200px|thumb|center|'''Proposal''' for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus by simple rearrangement into one frame)]]
|-
|}
</center>

Proposed solution: wxLayoutAlgorithm(), see [[WxGUI#What_others_do]]

==== r.li.setup ====
work on r.li.setup for GRASS7

==== Saving History ====

* when using the wxGUI, it needs to write back to the shell history
: `cat wxgui_history.log >> $MAPSET/.bash_history`
: Since the wxGUI shell quoting is not perfect, maybe it is better not to write directly to real shell history, but maintain its own in ~/.grass7/history.

==== Digitizing toolbar ====

* missing string "Select vector map" from the drop-down widget on digitizing toolbar
: on winGRASS, nightly build of 24th May
* after editing vector objects and saving, the changes are not applied on the map. Must be some refresh problem.
* Highlighting problem
: objects selected in the attribute table are not highlighted on the map
: objects selected ton the map are not highlighted in the attribute table.
* Bounding box of a layer broken after deletion of some objects with broken geometry, also displaying of the attribute table broken with a message that the map layer is not a vector one.

==== Attribute manager ====

* Editing attribute table broken
: cannot delete a row, permission denied
: different than selected row dissapears after not succesful row deletion but is back after refreshing the table.

Talk:GRASS Community Sprint Prague 2012

2012-05-25T09:15:39Z

⚠️MilenaN: /* Digitizing toolbar */ + more issues

== Reports ==

=== [[User:Landa|Martin Landa]] ===

* OSGeo4W GRASS package configuration: add liblas support (http://liblas.org/osgeo4w.html) - {{rev
|51677}} & {{rev
|51679}}

=== [[User:Neteler|Markus Neteler]] ===

* Fundraising for this Community Sprint (with great help from Arnulf Christl)
* PSC composition discussion

== Wishes for the Community Sprint ==

* Visual Guide to GRASS GIS modules: scratch a collection of per-module dedicated||or tutorial/task oriented, simple, minimalistic yet attractive, bullet-proof visual examples
**exemplify what GRASS modules do rather than how they do it, thus different than the manuals -- ''rephrase title?''
***make use of existing grass modules list(s), like (this old) [http://grass.itc.it/gdp/grassmanuals/grass63_module_list.pdf GRASS GIS 6.3 Command list (PDF document)]
***visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***ignore modules which cannot be visualised?
**check if (and some-how) task-oriented visual examples could be build out of per-modules examples
**setup specific styling rules (?)
***only one descriptive sentence per module or task
***visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***limited caption(s) describing visuals
**end-up with some independent and beautiful TeXy PDF
**visually enrich existing manuals and/or grass-wiki
** or consider Sphinx

* Review of the python + ctypes example scripts.
: The examples given in the code for {{src|doc/python/raster_example_ctypes.py|version=trunk}}, vector_example_ctypes.py and on the [[Python Ctypes Examples|Ctypes wiki page]] have so far for me all been broken in some way or another. Either grass7 API in grass6 example, typos, incomplete, etc. have made almost all of them fail out of the box. As this is teaching code we should make sure it's perfect :-). See also bug in trac about possible memory leak in r.example.

* Extend {{cmd|r.colors}} documentation by an example for a user-generated logarithmic color table.

== Testing by power users ==

(Power) users from all over the world are kindly invited to assist with testing of new and existing functionality. To collect results and notes, we set up an interactive, collaborative editing tool which works in real-time:

Please check http://titanpad.com/I51nq1SrNc

== Non-Technical ==

Discuss role and current composition of GRASS-[[PSC]]:
* Every year members are requested to confirm to continue their work in the PSC.
* After the Community Sprint 2012, the Chair will request updates to the [[RFC1]] from the PSC members.
* Answer within five business days needed.
* In case of no continuation/no answer, a member is replaced in order to refresh the PSC.
* To be eligible for PSC membership, a person should have a demonstrated and substantial involvement in GRASS GIS (operation of the PSC is defined at [[RFC1]]).

Further issues:
* Discuss Google Summer of Code (two students are here)
* Discuss GRASS 6.4.3 and 7.0 release schedule
* Define make a manual test procedure for users to simplify testing before new releases, write this up in the wiki ([http://trac.osgeo.org/grass/wiki/HowToTestGrass6 example])

== Semi-Technical ==

* Improve Web site or use [[CMS]]
** Prototype site: http://grass.fem-environment.eu/
* Document tips & tricks for GRASS compilation with the wxGUI
: there is [http://trac.osgeo.org/grass/wiki/CompileOnWindows Compilation on MS-Windows]
* Discuss new GRASS Book 4th edition in conjunction with the GRASS GIS 7.0 release in early 2013

== Technical ==

=== OSGeo4W ===

* {{done}} <strike>GRASS package configuration: add liblas support (http://liblas.org/osgeo4w.html)</strike> (martinl) - {{rev
|51677}} & {{rev
|51679}} ([http://wingrass.fsv.cvut.cz/grass64/ download])

=== Android ===

* continue the Android compilation (needs especially the elimination of XDR in rast and rast3d)

=== QGIS-Sextante-GRASS interface ===

* work on new integration with [http://plugins.qgis.org/plugins/sextante/ QGIS-Sextante]

=== Update the GDAL-GRASS interface to GRASS 7 ===

* see http://trac.osgeo.org/gdal/ticket/2953
* LGPL grass IO code written from scratch?

=== Rules Based programming and Agent Based Modelling ===

* Tutorial/Documentation on g.infer
* [http://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.agent r.agent] in GRASS 7

=== Time series ===

* Seminar on Temporal GIS framework demo and discussion: by Soeren Gebbert, done on 24 May 2012
* Add content to http://grass.osgeo.org/grass70/manuals/html70_user/temporalintro.html from Soeren's tutorial
* Discuss temporal GIS wxGUI and WPS integration
* Discuss massive parallel computation of spatio-temporal datasets

=== Automated command user statistics ===

* modify g.parser to write out the list of used commands (without parameters) into a text file for simple, automated command user statistics

=== Mobile: inventory of mobile and touch implementations ===

* [http://code.google.com/p/geopaparazzi/ Geopaparazzi], v.in.geopaparazzi
* GRASS on Android (patches by MN)

=== Cloud computing ===

* g.cloud
* cluster usage best practices

=== GSoC 2012 ===

* v.net.* front end, WMS
* Python API
* Image Segmentation

=== GRASS 7 ===
* PostGIS Topology support
* New features for vector engine
* Discuss Toolbox concept
* Discuss how to implement [[GRASS Metadata Management]]

=== Model integration ===

* GRASS and [http://www.coulthard.org.uk/CAESAR.html Caesar model]

=== GRASS modules fixes ===

* i.atcorr debugging
** Figure out how to get visibility/aerosol depth at 550nm (perhaps from MODIS atmosphere?)
** Under certain circumstances i.atcorr produces NULL data
* GRASS 6.4.3 - [http://trac.osgeo.org/grass/query?status=new&status=assigned&status=reopened&group=type&order=priority&priority=blocker&priority=critical&milestone=6.4.3&milestone=6.4.2&milestone=6.4.1&milestone=6.4.0 Release critical issues to be fixed]

=== Signal handling ===

* The Python based scripts should catch CTRL-C to avoid that clutter is left behind and that ugly traceback is printed into the terminal.

Suggestion by Anne Ghisla (yet not working... ):
<source lang="python">
Index: lib/init/grass.py
===================================================================
--- lib/init/grass.py (revision 51604)
+++ lib/init/grass.py (working copy)
@@ -30,7 +30,12 @@
import subprocess
import re
import platform
+import signal

+# catch user-sent CTRL-C
+signal.signal(signal.SIGINT, lambda a,b:cleanup())
+signal.siginterrupt(signal.SIGINT, False)
+
# Variables substituted during build process
if os.environ.has_key('GISBASE'):
gisbase = os.environ['GISBASE']
</source>

* Currently if vector creation modules fail to create/import they still leave behind the empty skeleton of a map, so you need to use --o for the next time. It would be nice if cleanup could occur. This doesn't happen (visibly) with raster maps as they are composed in $MAPSET/.tmp/ and only moved into the main $MAPSET elements once everything is finished. Vector maps on the otherhand write to the MAPSET in-place.

=== Fix wxGUI problems ===
A. Clerici: please fix:
* ticket https://trac.osgeo.org/grass/ticket/1564
* ticket https://trac.osgeo.org/grass/ticket/1570
* wxGUI bugs (GRASS6.4.2RC3 under Fedora 16):
** In the 'Create histogram of raster map' function, the style pie and the Color for text and axes options are not working. The options run fine on the tcltk GUI and in command line mode.
** In the 'Add scalebar and north arrow', the scale can be modified only once and the option can't be re-entered nor the scale can't be deleted. Also in this case there are no problems with the tcltk GUI.
** the option 'Add raster cell arrows' seems not to work properly. It seems that the arrows in the Map Display cannot zoomed in. It can be checked by the following steps:
*** Load and display the aspect (Spearfish) map.
*** Open the d.rast.arrows panel through the GUI button and choose the same map aspect. Click Apply: the Map Display appears green as expected for the very high resolution.
*** Choose 10 for the 'Draw arrow every Nth grid cell:' option and none as 'Color for drawing grid or “none”' option. The arrows are displayed on the cells of aspect map.
*** To make the arrows visible choose slope as 'Raster map containing values used for arrow length:' and 10.0 as 'Scale factor for arrows'. Zoom in a very small area: the cells of aspect map are enlarged, but the density of arrows remains the same
*** The direction is correctly the same for all arrows inside the same cell but it seems that instead of having an arrow each 10 aspect cells, there is an arrow each 10 pixel of the screen (with tcltk GUI the procedure works fine)
* Fix wx0..6 monitors

==== Layout ====

Optionally, have all-in-one GUI window (requested by many new users!):
<center>
{|
|-
| [[Image:Wxgui_current.png|250px|thumb|center|Current wxGUI layout with detached window components]]
| [[Image:Wxgui_proposal.png|200px|thumb|center|'''Proposal''' for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus by simple rearrangement into one frame)]]
|-
|}
</center>

Proposed solution: wxLayoutAlgorithm(), see [[WxGUI#What_others_do]]

==== r.li.setup ====
work on r.li.setup for GRASS7

==== Saving History ====

* when using the wxGUI, it needs to write back to the shell history
: `cat wxgui_history.log >> $MAPSET/.bash_history`
: Since the wxGUI shell quoting is not perfect, maybe it is better not to write directly to real shell history, but maintain its own in ~/.grass7/history.

==== Digitizing toolbar ====

* missing string "Select vector map" from the drop-down widget on digitizing toolbar
: on winGRASS, nightly build of 24th May
* after editing vector objects and saving, the changes are not applied on the map. Must be some refresh problem.
* Highlighting problem
: objects selected in the attribute table are not highlighted on the map
: objects selected ton the map are not highlighted in the attribute table.

==== Attribute manager ====

* Editing attribute table broken
: cannot delete a row, permission denied
: different than selected row dissapears after not succesful row deletion but is back after refreshing the table.

Talk:GRASS Community Sprint Prague 2012

2012-05-25T08:52:45Z

⚠️MilenaN: /* Digitizing toolbar */ added refresh problem

== Reports ==

=== [[User:Landa|Martin Landa]] ===

* OSGeo4W GRASS package configuration: add liblas support (http://liblas.org/osgeo4w.html) - {{rev
|51677}} & {{rev
|51679}}

=== [[User:Neteler|Markus Neteler]] ===

* Fundraising for this Community Sprint (with great help from Arnulf Christl)
* PSC composition discussion

== Wishes for the Community Sprint ==

* Visual Guide to GRASS GIS modules: scratch a collection of per-module dedicated||or tutorial/task oriented, simple, minimalistic yet attractive, bullet-proof visual examples
**exemplify what GRASS modules do rather than how they do it, thus different than the manuals -- ''rephrase title?''
***make use of existing grass modules list(s), like (this old) [http://grass.itc.it/gdp/grassmanuals/grass63_module_list.pdf GRASS GIS 6.3 Command list (PDF document)]
***visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***ignore modules which cannot be visualised?
**check if (and some-how) task-oriented visual examples could be build out of per-modules examples
**setup specific styling rules (?)
***only one descriptive sentence per module or task
***visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***limited caption(s) describing visuals
**end-up with some independent and beautiful TeXy PDF
**visually enrich existing manuals and/or grass-wiki
** or consider Sphinx

* Review of the python + ctypes example scripts.
: The examples given in the code for {{src|doc/python/raster_example_ctypes.py|version=trunk}}, vector_example_ctypes.py and on the [[Python Ctypes Examples|Ctypes wiki page]] have so far for me all been broken in some way or another. Either grass7 API in grass6 example, typos, incomplete, etc. have made almost all of them fail out of the box. As this is teaching code we should make sure it's perfect :-). See also bug in trac about possible memory leak in r.example.

* Extend {{cmd|r.colors}} documentation by an example for a user-generated logarithmic color table.

== Testing by power users ==

(Power) users from all over the world are kindly invited to assist with testing of new and existing functionality. To collect results and notes, we set up an interactive, collaborative editing tool which works in real-time:

Please check http://titanpad.com/I51nq1SrNc

== Non-Technical ==

Discuss role and current composition of GRASS-[[PSC]]:
* Every year members are requested to confirm to continue their work in the PSC.
* After the Community Sprint 2012, the Chair will request updates to the [[RFC1]] from the PSC members.
* Answer within five business days needed.
* In case of no continuation/no answer, a member is replaced in order to refresh the PSC.
* To be eligible for PSC membership, a person should have a demonstrated and substantial involvement in GRASS GIS (operation of the PSC is defined at [[RFC1]]).

Further issues:
* Discuss Google Summer of Code (two students are here)
* Discuss GRASS 6.4.3 and 7.0 release schedule
* Define make a manual test procedure for users to simplify testing before new releases, write this up in the wiki ([http://trac.osgeo.org/grass/wiki/HowToTestGrass6 example])

== Semi-Technical ==

* Improve Web site or use [[CMS]]
** Prototype site: http://grass.fem-environment.eu/
* Document tips & tricks for GRASS compilation with the wxGUI
: there is [http://trac.osgeo.org/grass/wiki/CompileOnWindows Compilation on MS-Windows]
* Discuss new GRASS Book 4th edition in conjunction with the GRASS GIS 7.0 release in early 2013

== Technical ==

=== OSGeo4W ===

* {{done}} <strike>GRASS package configuration: add liblas support (http://liblas.org/osgeo4w.html)</strike> (martinl) - {{rev
|51677}} & {{rev
|51679}} ([http://wingrass.fsv.cvut.cz/grass64/ download])

=== Android ===

* continue the Android compilation (needs especially the elimination of XDR in rast and rast3d)

=== QGIS-Sextante-GRASS interface ===

* work on new integration with [http://plugins.qgis.org/plugins/sextante/ QGIS-Sextante]

=== Update the GDAL-GRASS interface to GRASS 7 ===

* see http://trac.osgeo.org/gdal/ticket/2953
* LGPL grass IO code written from scratch?

=== Rules Based programming and Agent Based Modelling ===

* Tutorial/Documentation on g.infer
* [http://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.agent r.agent] in GRASS 7

=== Time series ===

* Seminar on Temporal GIS framework demo and discussion: by Soeren Gebbert, done on 24 May 2012
* Add content to http://grass.osgeo.org/grass70/manuals/html70_user/temporalintro.html from Soeren's tutorial
* Discuss temporal GIS wxGUI and WPS integration
* Discuss massive parallel computation of spatio-temporal datasets

=== Automated command user statistics ===

* modify g.parser to write out the list of used commands (without parameters) into a text file for simple, automated command user statistics

=== Mobile: inventory of mobile and touch implementations ===

* [http://code.google.com/p/geopaparazzi/ Geopaparazzi], v.in.geopaparazzi
* GRASS on Android (patches by MN)

=== Cloud computing ===

* g.cloud
* cluster usage best practices

=== GSoC 2012 ===

* v.net.* front end, WMS
* Python API
* Image Segmentation

=== GRASS 7 ===
* PostGIS Topology support
* New features for vector engine
* Discuss Toolbox concept
* Discuss how to implement [[GRASS Metadata Management]]

=== Model integration ===

* GRASS and [http://www.coulthard.org.uk/CAESAR.html Caesar model]

=== GRASS modules fixes ===

* i.atcorr debugging
** Figure out how to get visibility/aerosol depth at 550nm (perhaps from MODIS atmosphere?)
** Under certain circumstances i.atcorr produces NULL data
* GRASS 6.4.3 - [http://trac.osgeo.org/grass/query?status=new&status=assigned&status=reopened&group=type&order=priority&priority=blocker&priority=critical&milestone=6.4.3&milestone=6.4.2&milestone=6.4.1&milestone=6.4.0 Release critical issues to be fixed]

=== Signal handling ===

* The Python based scripts should catch CTRL-C to avoid that clutter is left behind and that ugly traceback is printed into the terminal.

Suggestion by Anne Ghisla (yet not working... ):
<source lang="python">
Index: lib/init/grass.py
===================================================================
--- lib/init/grass.py (revision 51604)
+++ lib/init/grass.py (working copy)
@@ -30,7 +30,12 @@
import subprocess
import re
import platform
+import signal

+# catch user-sent CTRL-C
+signal.signal(signal.SIGINT, lambda a,b:cleanup())
+signal.siginterrupt(signal.SIGINT, False)
+
# Variables substituted during build process
if os.environ.has_key('GISBASE'):
gisbase = os.environ['GISBASE']
</source>

* Currently if vector creation modules fail to create/import they still leave behind the empty skeleton of a map, so you need to use --o for the next time. It would be nice if cleanup could occur. This doesn't happen (visibly) with raster maps as they are composed in $MAPSET/.tmp/ and only moved into the main $MAPSET elements once everything is finished. Vector maps on the otherhand write to the MAPSET in-place.

=== Fix wxGUI problems ===
A. Clerici: please fix:
* ticket https://trac.osgeo.org/grass/ticket/1564
* ticket https://trac.osgeo.org/grass/ticket/1570
* wxGUI bugs (GRASS6.4.2RC3 under Fedora 16):
** In the 'Create histogram of raster map' function, the style pie and the Color for text and axes options are not working. The options run fine on the tcltk GUI and in command line mode.
** In the 'Add scalebar and north arrow', the scale can be modified only once and the option can't be re-entered nor the scale can't be deleted. Also in this case there are no problems with the tcltk GUI.
** the option 'Add raster cell arrows' seems not to work properly. It seems that the arrows in the Map Display cannot zoomed in. It can be checked by the following steps:
*** Load and display the aspect (Spearfish) map.
*** Open the d.rast.arrows panel through the GUI button and choose the same map aspect. Click Apply: the Map Display appears green as expected for the very high resolution.
*** Choose 10 for the 'Draw arrow every Nth grid cell:' option and none as 'Color for drawing grid or “none”' option. The arrows are displayed on the cells of aspect map.
*** To make the arrows visible choose slope as 'Raster map containing values used for arrow length:' and 10.0 as 'Scale factor for arrows'. Zoom in a very small area: the cells of aspect map are enlarged, but the density of arrows remains the same
*** The direction is correctly the same for all arrows inside the same cell but it seems that instead of having an arrow each 10 aspect cells, there is an arrow each 10 pixel of the screen (with tcltk GUI the procedure works fine)
* Fix wx0..6 monitors

==== Layout ====

Optionally, have all-in-one GUI window (requested by many new users!):
<center>
{|
|-
| [[Image:Wxgui_current.png|250px|thumb|center|Current wxGUI layout with detached window components]]
| [[Image:Wxgui_proposal.png|200px|thumb|center|'''Proposal''' for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus by simple rearrangement into one frame)]]
|-
|}
</center>

Proposed solution: wxLayoutAlgorithm(), see [[WxGUI#What_others_do]]

==== r.li.setup ====
work on r.li.setup for GRASS7

==== Saving History ====

* when using the wxGUI, it needs to write back to the shell history
: `cat wxgui_history.log >> $MAPSET/.bash_history`
: Since the wxGUI shell quoting is not perfect, maybe it is better not to write directly to real shell history, but maintain its own in ~/.grass7/history.

==== Digitizing toolbar ====

* missing string "Select vector map" from the drop-down widget on digitizing toolbar
: on winGRASS, nightly build of 24th May
* after editing vector objects and saving, the changes are not applied on the map. Must be some refresh problem.

Talk:GRASS Community Sprint Prague 2012

2012-05-24T13:15:12Z

⚠️MilenaN: + new wxGUI issue to be fixed

GRASS Community Sprint Prague 2012

2012-05-21T19:01:06Z

⚠️MilenaN: /* In person */

The GRASS GIS team will organize a '''GRASS Developer and Power User Meeting, aka 'GRASS Community Sprint'''' from '''May 23 to May 28, 2012'''. The sprint is following the [http://foss4g-cee.org/ FOSS4G-CEE] & [http://geoinformatics.fsv.cvut.cz/gwiki/Geoinformatics_FCE_CTU_2012 Geoinformatics] ''(Free and Open Source Software for Geospatial in Central and East Europe)'', 21-23 May 2012, Czech Technical University in [http://en.wikipedia.org/wiki/Prague Prague], [http://en.wikipedia.org/wiki/Czech_Republic Czech Republic].

'''Important dates:'''

* 21 (Monday) - 23 (Wednesday) May 2012: [http://foss4g-cee.org/ FOSS4G-CEE & Geoinformatics conference]

* '''23 (Wednesday) - 28 (Monday) May 2012: GRASS GIS Community Sprint''' @ [http://www.fsv.cvut.cz/ FCE CTU]

== Purpose ==

This second edition of the GRASS GIS community sprint 2012 is a great occasion for folks to support the development by actively contributing to the source code, manuals or likewise. The '''community''' sprint is a get-together for GRASS project members and supporters and related [http://www.osgeo.org/ OSGeo] projects to make decisions and tackle larger problems. For this meeting, we welcome people committed to improving the GRASS GIS project and the interfaces to [[QGIS GRASS Cookbook|QGIS]], [[GDAL]], [[PostGIS]], [[R statistics]], [[GRASS and Sextante|Sextante, gvSIG]], OGC Services (esp. [[WPS]]) and more. This includes developers, documenters, bug reporters, translators and others.

For this meeting, we welcome people committed to improving the GRASS GIS and related projects. This includes developers, document writers, wish and bug reporters, translators etc.

== Sponsors ==

We welcome financial contributions to support the meeting and we are looking for sponsors to cover costs such as meals or to help reducing travelling and accommodation expenses for GRASS developers with far arrival If you are interested to sponsor the GRASS Community Sprint, please read about

:::'''sponsoring the GRASS project at [http://grass.osgeo.org/donation.php http://grass.osgeo.org/donation.php]'''

and, if needed, contact [[User:Neteler|Markus Neteler]] <tt><neteler at osgeo.org></tt>. Any surplus at the end of the event will be turned over to the GRASS GIS project.

The first 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 Prague. 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 ===

We are grateful for the support which we have received to organize this GRASS Community Sprint:

* remainder from the 2011 edition of the Community Sprint and small donations (via [http://www.gfoss.it/ GFOSS.it], the Italian OSGeo chapter) - 1400 Euro
* [http://www.osgeo.org/ Open Source Geospatial Foundation] (OSGeo) - 1000 Euro
* [http://www.fossgis.de/ FOSSGIS e.V.] - 1000 Euro
* Stefan Sylla, [http://sylla-consult.de/en/ sylla-consult], Frankfurt, Germany - 500 Euro

== Timing ==

'''When''': Wednesday, May 23, 2012 (day of arrival) - Monday, May 28, 2012 (day of departure)

Of course you are invited to join or leave the community sprint whenever you want.

'''Duration''':

* Wednesday is day of arrival
** First meeting in the evening (after the [http://foss4g-cee.org/ FOSS4G-CEE & Geoinfomatics conference]) to define the agenda
* Thursday to Sunday
** Full days
* Monday is day of departure
** Probably hacking for people with a flight later in the evening

== Venue ==
[[Image:logo_cvut.jpg|130px|left]]
Department of Mapping and Cartography<br>
[http://www.fsv.cvut.cz Faculty of Civil Engineering]<br>
[http://www.cvut.cz Czech Technical University in Prague], [http://en.wikipedia.org/wiki/Czech_Republic Czech Republic]<br>
[http://geoinformatics.fsv.cvut.cz/gwiki/Room_B367 Room B367] <br>

'''[http://geoinformatics.fsv.cvut.cz/gwiki/Where_you_can_find_us Location & Transportations]'''

Prague has an international [http://www.prg.aero/en/ airport] and is also reachable by train, bus or car.

== Accommodation and Costs ==

Participants should plan for the following costs:

* The participation is free of charge
* Travel to Prague, variable depending on where you come from
* Accommodation and meals (with the donated sponsorship money we will try to cover some expenses of the participants)
'''Please note''': The currency in Czech Republic is [http://en.wikipedia.org/wiki/Czech_crown crown] (CZK, koruna, Kč). 100 Czech crowns are about 4 Euros (see [http://www.cnb.cz/en/financial_markets/foreign_exchange_market/exchange_rate_fixing/daily.jsp current rates]).

'''[http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague Accommodation in Prague]'''

:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Masarykova_Kolej_Hotel Masarykova Kolej Hotel]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_DAP Hotel DAP]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_Krystal Hotel Krystal]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Pension_Hanspaulka Pension Hanspaulka]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_Silenzio Hotel Silenzio]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Student_hostels_.28CTU.29 Student hostels (CTU)]
:* Special offer: ''sleeping for free in the kindergarten'' (30min by city urban mass transportation from the university campus, sleeping bag required, kitchen and WC available, no showers, in working days available only from 8 p.m. to 8 a.m.), contact [[User:Landa|Martin Landa]] for details
:* See also http://www.hotel.cz/praha-6/accommodation/

Please let us know your time of arrival and leaving, so we can book for the accommodations and organize the logistics.

Financial support: (partial) travel grants can be payed upon request thanks to our sponsors!

== Weather and Common Item Prices ==

* In May the weather in Prague is usually quite warm ([http://www.prague-spot.com/climate 15 or more degrees by day])
* A espresso coffee is about 20 CZK (80 cents), a beer (half of liter) in a common pub is around 25 CZK (1 euro), can be more in special pubs. In Prague you can have a full meal (see [http://en.wikipedia.org/wiki/Czech_cuisine Czech cuisine]) for still 75 - 150 CZK (3 - 6 euros), but beware of tourist restaurants, the price can easily rise. It's quite easy to find in Prague also Italian or Chinese restaurants.

== Agenda - What we plan to do ==

'''Note:''' The program is generally open for your ideas. Please write an email to the [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developer list] to discuss your contribution.

@TODO

=== Timeline ===

==== Wednesday, 23 May ====
* Kick-off at ''<time to be defined>''

@TODO

=== Topics ===

==== Non-technical ====

* see [[Talk:GRASS_Community_Sprint_Prague_2012]]

==== Semi-technical ====

* see [[Talk:GRASS_Community_Sprint_Prague_2012]]

==== Technical ====

* see [[Talk:GRASS_Community_Sprint_Prague_2012]]

== Participation ==

We are planning for attendance of 20 people (i.e., hacking places) but of course you are welcome to join us and bring new ideas with you, as more places are available. Please add your name here or contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>:

=== In person ===

{|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:#edf9c7; font-size:95%; empty-cells:show;"
!width=50px|'''No'''
!width=130px|'''Participant '''
!width=100px|'''Country'''
!width=100px|'''Arrival'''
!width=100px|'''Departure'''
!'''Topic'''
!width=75px|'''T-Shirt'''
!'''Notes'''
|-
|1
|[[User:Landa|Martin Landa]]
|Czech Republic
| May 20
| May 28
|Toolbox concept, vector engine in GRASS 7, wxGUI, PostGIS Topology support
| L
|
|-
|2
|[[User:Neteler|Markus Neteler]]
|Italy
| May 20
| May 28
|GRASS on Android, QGIS-Sextante-GRASS interface, high performance computing, g.cloud, singing & beer in pub, Toolbox, ...
| M + S
|
|-
|3
|[[User:Lucadelu|Luca Delucchi]]
|Italy
| May 20
| May 26
| r.modis, r.li.setup gui, v.in.geopaparazzi (only if andrea antonello comes to Prague)
| L
|
|-
|4
|[[User:moovida|Andrea Antonello]]
|Italy
| May 21/22
| May 25/26
| v.in.geopaparazzi, GRASS [[http://www.coulthard.org.uk/CAESAR.html Caesar model]] input module with Silvia, singing at the pub with Luca Delucchi and Peter Loewe
| L
|
|-
|5
|[[User:silli|Silvia Franceschi]]
|Italy
| May 21/22
| May 25/26
| GRASS [[http://www.coulthard.org.uk/CAESAR.html Caesar model]] input module
| S
|
|-
|6
|[[User:peter.loewe|Peter Loewe]]
|Germany
| May 20/21
| May 25/26
| collecting beer-money while Luca and Andrea sing in pubs ; i.atcorr debugging ; g.cloud ? ; r.tsunami ? ; Tutorial/Documentation on g.infer
| S
|
|-
|7
|[[User:Annakrat|Anna Kratochvilova]]
|Czech Republic
| May 20
| May 28
| imagery, wxGUI
| S
|
|-
|8
|[[User:Vaclav|Vaclav Petras]]
|Czech Republic
| May 20
| May 28
| imagery, wxGUI, Toolbox concept ?
| M
|
|-
|9
|[[User:Helena|Helena Mitasova]]
|USA
|May 21
|May 25/26
|toolbox concept, student sandbox, wxnviz z-scale, inventory of mobile and touch implementations, GRASS on-line and cloud
|
|
|-
|10
|[[User:Huhabla|Sören Gebbert]]
|Germany
|May 20
|May 27
|Temporal GIS framework demo and discussion, Temporal GIS wxGUI and WPS integration, massive parallel computation of spatio-temporal datasets, Cloud computing
| L
|
|-
|11
|[[User:Turek|Štěpán Turek]]
|Czech Republic
|May 20
|May 28
|v.net.* front end, WMS
| L
|
|-
|12
|Radim Blažek
|Czech Republic
|May 24/25
|May 24/25
|QGIS interface
| -
|
|-
|13
|[[User:Pietro|Pietro Zambelli]]
|Italy
|May 23/24
|May 28/29
|GSoC2012: High level map interaction
| L
|-
|14
|Markus Metz
|Italy
|May 23
|May 26
|
|
|
|-
|15
|[[User:NikosA|Nikos Alexandris]]
|Greece
|May 24
|May 27/28
|(wannabe) bughunter, assist documentation and tutorials
|
|-
|16
|[[User:MilenaN|Milena Nowotarska]]
|Poland
|May 23
|May 27
|translation, wxGUI
|S
|-
|}

=== Via IRC chat ===

: [irc://freenode/grass #grass] on Freenode

For details, see [[IRC]]

=== Collaborative document scratching ===

* EtherPad: http://etherpad.osuosl.org

== Individual Preparation ==

* Bring your own computer
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country power connector adapter] if needed (Czech Republic: 230V, 50Hz, [http://en.wikipedia.org/wiki/File:Euro-Flachstecker_2.jpg Type C Europlugs] are common and also [http://en.wikipedia.org/wiki/File:French_plug_and_socket.jpg Type E])
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== Broadcast & Video ==

During the event :)

== Photos ==

Also during the event :)

== FAQ ==

* How was it last year?
** Very nice, see [[GRASS Community Sprint Prague 2011]]!
* ''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?''
** Contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>

[[Category: Workshops]]

Talk:GRASS Documents

2012-04-10T12:42:55Z

⚠️MilenaN: Reverted edits by Tiaormond (talk) to last revision by Neteler

Hi, we have a partial Italian translation of the GRASS Manual pages [http://wiki.gfoss.it/index.php/GRASS_6.0.2_Reference_Manual here]. Can we place a link on this page or should it go somewhere else? --[[User:Steko|Steko]] 22:33, 5 February 2007 (CET)

: In an ideal world this would be maintained in GRASS itself, translating the original pages. We also have some french HTML pages already. -- Markus [[User:Neteler|Neteler]] 16:52, 7 February 2007 (CET)

GRASS-Wiki

2012-03-20T22:26:56Z

⚠️MilenaN: + GRASS Community Sprint

__NOTOC__
{| width="100%"
|-
| width="68%" style="vertical-align:top" |
<div style="margin:0; margin-right:10px; border:1px solid #dfdfdf; background-color:#f8f8ff;">

<div style="padding:0.3em 1em 0.7em 1em;">

[[Image:grasslogo_vector_small.png|right|link=http://grass.osgeo.org]]

=== Welcome to the GRASS GIS Users Wiki ===

{{website|intro/general.php|'''GRASS GIS'''}} is a [http://en.wikipedia.org/wiki/Geographic_information_system Geographic Information System] used for geospatial data management and analysis, image processing, graphics/map production, spatial modeling, and visualization.

On this Wiki, you can get and contribute to GRASS related information, documents and community provided add-ons programs. To edit here, you need to register and login first (see top right link).

For GRASS at a glance, see [[Core features]]. For usage examples, see the [http://grass.osgeo.org/screenshots/index.php screenshots gallery] and [[Applications]].
</div>
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#FFE5E5;">
'''What's hot:'''
* <font size="+1">[http://grass.osgeo.org/announces/announce_grass642.html '''GRASS 6.4.2''' released!]</font>
** [http://grass.osgeo.org/download/ Download it now], then try the [[Quick wxGUI tutorial]]
* [[GRASS Community Sprint Prague 2012]] - 23-28 May 2012, Prague, Czech Republic
* [[GRASS_SoC_Ideas_2012|We're collecting ideas for the Google Summer of Code 2012]] student scholarship program
* Temporal support and other new [[Initiatives]]
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#f8f8ff;">
==== User Documentation and Support ====
* [[GRASS Help|GRASS Help and Getting Started]]
* [[GRASS Documents|In depth GRASS Documentation]]
* [[Installation Guide]] for precompiled binaries
* '''[[Faq|FAQ]] - Frequently Asked Questions'''
* [[Applications]] - use cases of GRASS in various disciplines
* [[wxGUI]] - Graphical User Interface based on wxPython
</div>

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

==== Community ====
* [[GRASS Community]]: Getting in touch
* [[Applications|Research applications]]: What people are doing with GRASS
* [[GRASS migration hints|Migrating to GRASS]]
* [[GRASS Blogger]]
* Get involved: [[Project jobs]]
* [http://grass.osgeo.org/wiki/Special:Recentchanges?feed=rss RSS feed] of recent changes of this Wiki
</div>

<div>Have a look at the GRASS GIS users worldwide [http://grass.osgeo.org/community/ GRASS GIS User Online]. If you operate a GRASS GIS installation, you are welcome to enter your user data there.
</div>

<div><p>''[[GRASS-Wiki:Language policy|Translate this Wiki]]''</p></div>


| width="38%" style="vertical-align:top" |
<div style="margin:0; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#f8f8ff;">
[[Image:OSGeo 220pix.png|center|220px|link=http://www.osgeo.org]]
<center>[http://www.osgeo.org OSGeo] Foundation Project</center>
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:1em 1em 1em 1em; background-color:#f8f8ff;">
[[Image:Btn_donate_SM.gif|center|link=http://grass.osgeo.org/donation.php]]<center>[http://grass.osgeo.org/donation.php Donate]</center>
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#f8f8ff;">
* [http://grass.osgeo.org/screenshots/index.php GRASS Screenshots]
* [http://trac.osgeo.org SVN/trac] Source Code Repository
* [http://grass.osgeo.org/community/support.php Mailing lists] and [http://grass.osgeo.org/community/support.php#irc IRC]
* [http://trac.osgeo.org/grass/ Report errors or wishes]
* [https://svn.osgeo.org/grass/grass/branches/releasebranch_6_4/COPYING Licensed under GNU GPL]
</div>

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

==== Download ====
* [http://grass.osgeo.org/download/ Source code and binaries]
* '''[[GRASS AddOns]]'''
* [[Promotional material]]
* [[Sample datasets]]
* [[Global datasets]]
</div>

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

==== Development ====
* [[Compile and Install]] of Source Code
* [[Development|GRASS Development]] intro
* [http://trac.osgeo.org/grass/wiki GRASS-trac]: the development Wiki, bugtracker, source code browser
* [[Release Roadmap]]
* [[GRASS 7 ideas collection]]
* [[GRASS SoC Ideas|Google Summer of Code ideas collection]]
* [http://trac.osgeo.org/grass/wiki/HowToContribute How to contribute to GRASS development] (getting write access and such)
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#f8f8ff;">
Project Metrics provided by [http://www.ohloh.net/projects/3666 Ohloh].

{{#widget:Ohloh Project|id=3666|type=partner_badge}}
</div>
|}

GRASS-Wiki/pl

2012-03-14T21:07:14Z

⚠️MilenaN: updated hot topics

__NOTOC__
{| width="100%"
|-
| width="68%" style="vertical-align:top" |
<div style="margin:0; margin-right:10px; border:1px solid #dfdfdf; background-color:#f8f8ff;">

<div style="padding:0.3em 1em 0.7em 1em;">

[[Image:grasslogo_vector_small.png|right]]

=== Witaj w Wiki użytkowników GRASS GIS ===

[http://grass.osgeo.org Geographic Resources Analysis Support System], zwykle zwany '''GRASS-em''',
jest Systemem Informacji Geograficznej ([http://en.wikipedia.org/wiki/Geographic_information_system GIS]) wykorzystywanym do zarządzania i analiz danych przestrzennych, przetwarzania obrazów satelitarnych i zdjęć lotniczych, produkcji prezentacji graficznych oraz map, modelowania przestrzennego i wizualizacji. GRASS jest obecnie używany przez środowiska akademickie i komercyjne na całym śwecie, jak i przez wiele agencji rządowych i firm zajmujących się stanem środowiska naturalnego. GRASS GIS jest projektem [http://www.osgeo.org Open Source Geospatial Foundation]. <br>
Ta WIKI stanowi oficjalną stronę społeczności użytkowników projektu GRASS GIS. Aby zobaczyć przykłady analiz, idź do [http://grass.osgeo.org/screenshots/index.php Galerii GRASS GIS].

Na tej Wiki możesz znaleźć informacje o GRASS-ie, dokumenty oraz dodatkowe programy związane z projektem, a także rozbudowywać je. Aby móc edytować Wiki, zaloguj się - link w prawym górnym rogu.
</div>
</div>
<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#FFE5E5;">

'''Gorący temat:'''
* <font size="+1">[http://grass.osgeo.org/announces/announce_grass642.html '''GRASS 6.4.2''' został wydany!]</font>
** [http://grass.osgeo.org/download/ Pobierz teraz], następnie wypróbuj [[Quick wxGUI tutorial]]
* [[GRASS Community Sprint Prague 2012]] - 23-28 maja 2012, Praga, Czechy
* [[GRASS_SoC_Ideas_2012|Zbieramy pomysły na Google Summer of Code 2012]] program praktyk studenckich
* Nowe [[Initiatives|Inicjatywy]]
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em
1em 1em 1em; background-color:#f8f8ff;">
==== Dokumentacja i pomoc dla użytkowników ====
* [[GRASS Help|Pomoc GRASS-a i Jak Zacząć]]
* [[GRASS Documents|Szczegółowa dokumentacja GRASS-a]]
* [[Installation Guide|Przewodnik instalacji]] prekompilowanych pakietów binarnych
* [[Faq|FAQ]]
* [[Applications|Zastosowania]] - przykłady użycia GRASS w różnych dyscyplinach
* [[wxGUI]] - Graficzny Interfejs Użytkownika w wxPython'ie
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em

1em 1em 1em; background-color:#f8f8ff;">

==== Społeczność====
* [[GRASS Community|Społeczność GRASS-a]]: Bądź w kontakcie
* [[Applications|Research applications]]: Co inni robią w GRASS-ie
* [[GRASS migration hints|Przejście na System GRASS]]
* [[GRASS Blogger]]
* Zaangażuj się: [[Project jobs|Prace przy projekcie]]
* [http://grass.osgeo.org/wiki/Special:Recentchanges?feed=rss RSS feed] ostatnie zmiany tej Wiki
</div>

<div>Zerknij na mapę użytkowników GRASS GIS na świecie [http://grass.osgeo.org/community/ GRASS GIS User Online]. Jeśli używasz GRASS GIS, dopisz się do mapy.
</div>

<div><p>''[[GRASS-Wiki:Language policy|Przetłumacz tę Wiki]]''</p></div>


| width="38%" style="vertical-align:top" |
<div style="margin:0; border:1px solid #dfdfdf; padding:0em 1em 1em 1em;

background-color:#f8f8ff;">
[[Image:OSGeo 220pix.png|center|220px]]
<center>Projekt Fundacji OSGeo</center>
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:1em 1em 1em 1em; background-color:#f8f8ff;">
[[Image:Btn_donate_SM.gif|center|link=http://grass.osgeo.org/donation.php]]<center>[http://grass.osgeo.org/donation.php Donate via PayPal.com]</center>
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding: 0em 1em 1em 1em;

background-color:#f8f8ff;">
* [http://grass.osgeo.org/screenshots/index.php Galeria Systemu GRASS]
* [http://trac.osgeo.org SVN/trac] Repozytorium Kodu Źródłowego
* [http://grass.osgeo.org/community/support.php Listy mailingowe] i [http://grass.osgeo.org/community/support.php#irc IRC]
* [http://trac.osgeo.org/grass/ Zgłaszanie błędów i życzeń]
* [https://svn.osgeo.org/grass/grass/branches/releasebranch_6_4/COPYING Licencja GNU GPL]
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em;

background-color:#f8f8ff;">

==== Pobierz ====
* [http://grass.osgeo.org/download/ Kod źródłowy i pakiety binarne]
* [[GRASS AddOns|Dodatki Systemu GRASS]]
* [[Promotional material|Materiały promocyjne]]
* [[Sample datasets|Przykładowe zestawy danych]]
* [[Global datasets|Globalne zestawy danych]]
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em;

background-color:#f8f8ff;">

==== Development ====
* [[Compile and Install]] of Source Code
* [[Development|GRASS Development]] intro
* [http://trac.osgeo.org/grass/wiki GRASS-trac]: the development Wiki, bugtracker, source code browser
* [[Release Roadmap]]
* [[GRASS 7 ideas collection]]
* [[GRASS SoC Ideas|Google Summer of Code ideas collection]]
* [http://trac.osgeo.org/grass/wiki/HowToContribute How to contribute to GRASS development] (getting write access and such)
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em;

background-color:#f8f8ff;">
Project Metrics provided by [http://www.ohloh.net/projects/3666 Ohloh].
{{#ohloh: account=3666}}
</div>
|}
{{Trans|Polish|English}}

[[Category:Languages/pl]]

Agriculture and HPC

2011-12-30T21:38:03Z

⚠️MilenaN: Reverted edits by Reverse22 (talk) to last revision by Radenko

=== Introduction ===
Agricultural activity monitoring, e.g. enclosed quantifying the irrigation scheduling, tracing the soil hydraulic properties, generating the crop calendar etc., is necessary for efficient food security management at country level. The near real time monitoring or prediction on crop parameters such as crop growth in terms of planting date, date of emergence, extents, acreage, planting intensity, water stress, biomass, yield and etc. is important. It can contribute to better policymaking, timely countermeasures, optimization of water resources distributions, damage assessment and finally to supply food security and stable market. Researchers of agriculture also try to analyze various information about crops in order to take measures if they had some problems. Particularly, when an on-going experiment covers large area such as a country, satellite imagery plays a vital role by providing useful information over large/provincial area. However, some information, or crop parameters, is not visible through satellite images such as sowing dates, cropping intensity, growth, stress etc., which reflects a practical problem that we can not generate or observe those parameters from remote places. To collect those data, time by time basis field experiments are required. This is a time consuming, complex and expensive procedure. To overcome such problems, crop or simulation models can help. Usually, crop models calculate those missing information by analyzing the crop information with real fields' experiment data. Indirect methods such as inverse modeling with crop model can be used to obtain those basic input parameters. One such method is the manual calibration by "trial and error" procedure, which is very subjective and time consuming, and uncertainty associated with them can not be quantified. A more robust way of inverse modeling is to combine the model and assimilate data with optimization algorithm.

Thus, the challenge for the future is to obtain besides the more direct observable data (land cover, leaf area index, digital elevation model and evapotranspiration), non-visible data (soil characteristics, groundwater depth and irrigation practices) from satellite images.

=== Crop Assimilation Model (CAM) ===
Crop models, Soil-Water-Air-Plant (SWAP)<ref> [http://www.wiz.uni-kassel.de/model_db/mdb/swap.html Soil Water Atmosphere Plant-General Model Information]</ref> or Decision Support System for Agrotechnology Transfer (DSSAT) <ref>[http://www.icasa.net/dssat/ ICASA DSSAT software Introduction]</ref>, have capacity to simulate soil, water and crop processes and serve as crop productivity monitoring tool. Crop Assimilation Model (CAM) predicts parameters of crop models with satelite images. A new methodology was developed in <ref>[http://www.hydrol-earth-syst-sci.net/6/49/2002/hess-6-49-2002.html Inverse modelling in estimating soil hydraulic functions: a Genetic Algorithm approach]</ref>, CAM-GA, to analyze the crop model (SWAP) parameters assimilation with Remote Sensing (RS) data and that parameters assimilation procedure was optimized by an evolutionary searching technique called Genetic Algorithm (GA). Due to the changing in input parameters of SWAP model for pixel-to-pixel basis, the assimilation search space is very large. Evolutionary search algorithms are performing well in such conditions. Similar works in <ref>[http://www.sciencedirect.com/science?_ob=ArticleURL&_udi=B6VCF-4FPJBB4-1&_user=126251&_rdoc=1&_fmt=&_orig=search&_sort=d&_docanchor=&view=c&_searchStrId=1016133229&_rerunOrigin=google&_acct=C000010218&_version=1&_urlVersion=0&_userid=126251&md5=93a7735a8b4bcbfc2bea9cde9bf4e66a On quantifying agricultural and water management practices from low spatial resolution RS data using genetic algorithms: A numerical study for mixed-pixel environment]</ref> and <ref>[http://www.aars-acrs.org/acrs/proceeding/ACRS2004/Papers/DF204-6.htm SWAP crop model Parameter Identification using SPOT Vegetation in Suphanburi, Thailand]</ref> used some remotely sensed information combined with a binary GA <ref>[http://www.amazon.com/reader/3540606769?_encoding=UTF8&ref_=sib%5Fdp%5Fpt#reader-link]</ref> and SWAP model for optimizing soil hydraulic parameters. CAM with double layers GA, CAM-DLGA <ref>[http://www.freewebs.com/ychemin/2006_IEEE_TGRS_chemin_honda.pdf Spatiotemporal Fusion of Rice Actual Evapotranspiration With Genetic Algorithms and an Agrohydrological Model]</ref>, uses directly visible multi-resolution RS images (ASTER <ref>[http://asterweb.jpl.nasa.gov/ Advanced Spaceborne Thermal Emission and Reflection Radiometer]</ref>, MODIS <ref>[http://modis.gsfc.nasa.gov/ Moderate Resolution Imaging Spectroradiometer]</ref>) and inversely assimilates to SWAP model data for estimating the non-visible model parameters. One of the advantages of the GA is that they operate well even in domains, where little information is known. However, the main difficulty on GA is to decide an appropriate set of parameters, such as population size, number of generation, selection rate, crossover probability, and mutation probability. Other models, e.g., CAM-PSO <ref>[http://www.igarss08.org/Abstracts/pdfs/2357.pdf Combining remote sensing maeasurements and model estimates through hybrid data assimilation scheme to predict hydrological fluxes at a watershed scale]</ref> and CAM-PEST <ref>[http://www.itc.nl/library/papers_2003/msc/wrem/minur_dorji.pdf]</ref>, use different evolutionary searching technique. They were developed and provided the similar functionality as CAM-GA. However, processing the agricultural information with CAM has a problem in practicality, that is, they require a huge amount of processing times. It becomes necessary to introduce methods for using higher processing power such as High Performance Computing (HPC) technologies.

=== Rationale ===
Multi computer based distributed systems (clusters and Grids) have a large processing capacity for a lower cost, naturally, choice turns towards developing HPC applications. However, it is not an easy job to port CAM in HPC environment. The application performance is significantly affected by the data distribution and task distribution methods on the HPC, and developers of agriculture or satellite image processing applications need to solve the problem of both data and task distribution, or how to distribute data and tasks among single or multiple clusters environment. The workload in HPC, the bandwidth, the processors speed, parameters of evaluation methods and data size are additional concerning factors. Moreover, interoperability between the agriculture application and existing RS image processing software is also necessary to improve practicality. However, users need to manually extract satellite data from some databases in the existing CAM works. Some researches separately focused on the agricultural models activities or satellite image processing performance on HPC and a few of them are in the merging domains with satellite image processing, agriculture and HPC. Still, the merging domain researches are mainly in hypothetical or conjectural theme rather than practical implementation. Thus, agricultural researchers require a web based system or tool for the agricultural activity monitoring so that they do not need to concern about the implementation issues for agricultural models or RS image processing on HPC.

=== Research Objectives ===
Thus, the main focus of the research is to propose a new software system to support agriculture activities using both Remote Sensing (RS) and HPC. Processing satellite images automatically through HPC, CAM HPC implementation with appropriate data and task distribution schemes, web portal system on HPC are the vital sectors for modeling the overall distributed agriculture monitoring scheme and require individual experiments. Therefore, the research question is "Does the HPC system help to improve the performance in each sector separately?". In this study, the performance in HPC system for each sector is successfully examined and experimented with different targeted applications. The applications are being implemented first time in HPC platform and their performance results are quite impressive and acceptable.

GRASS GIS (Geographical Resources Analysis Support System) is a free, open source software/tool and has been used for RS and GIS data analysis and visualization. GRASS module [[r.vi]] is used as a test example for experimenting on HPC ([[r.vi.mpi]], [[r.vi.grid]]) <ref>[http://www.osgeo.org/ojs/index.php/journal/article/view/93 Porting a GRASS raster module to distributed computing Examples for MPI and Ninf-G]</ref>. Moreover, temporally splined procedure such as Local Maximum Fitting (LMF) processing methodology is improved to reduce the processing time by combining the parallelization of data and task distribution together on multi-cluster Grids<ref>[http://j-geoinfo.net/Content/Dec2008/p02.html Asynchronous Grid LMF Processing of Vegetation Index for Asia]</ref>. CAM-GA, is implemented in grid testbed and the impact on the performance of parallelization methods is discussed. Additionally, a new CAM called CAM-PLDLGA is proposed and implemented <ref>[http://www.alab.ip.titech.ac.jp/papers/shamim-ICCSA-Jul2009.pdf Parameter-Less GA Based Crop Parameter Assimilation with Satellite Image]</ref>. A CAM-GA web interface with MapServer and PHPMapscripts is implemented. Thereafter, an implementation methodology with Python based Web Processing Service (PyWPS), Embrio Interface and MapServer are discussed for future extension.

'''Shamim Akhter,18-9-2009'''

P.S: The complete research, ''Study on High Performance Computing of Crop Parameter Identification with The Grid, PhD dissertation, 2009, Information Processing,Tokyo Institute of Technology'', will be sent upon mail request to Shamim Akhter (shamimakhter@gmail.com).

=== References ===
<references/>

[[Category:Applications]]

GRASS-Wiki

2011-12-30T21:37:59Z

⚠️MilenaN: Reverted edits by Reverse22 (talk) to last revision by Landa

__NOTOC__
{| width="100%"
|-
| width="68%" style="vertical-align:top" |
<div style="margin:0; margin-right:10px; border:1px solid #dfdfdf; background-color:#f8f8ff;">

<div style="padding:0.3em 1em 0.7em 1em;">

[[Image:grasslogo_vector_small.png|right|link=http://grass.osgeo.org]]

=== Welcome to the GRASS GIS Users Wiki ===

{{website|intro/general.php|'''GRASS GIS'''}} is a [http://en.wikipedia.org/wiki/Geographic_information_system Geographic Information System] used for geospatial data management and analysis, image processing, graphics/map production, spatial modeling, and visualization.

On this Wiki, you can get and contribute to GRASS related information, documents and community provided add-ons programs. To edit here, you need to register and login first (see top right link).

For GRASS at a glance, see [[Core features]]. For usage examples, see the [http://grass.osgeo.org/screenshots/index.php screenshots gallery] and [[Applications]].
</div>
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#FFE5E5;">
'''What's hot:'''
* [http://grass.osgeo.org/download/ '''GRASS 6.4.2RC2''' available for testing - get it now!]
* Then try the [[Quick wxGUI tutorial]]
* Temporal support and other new [[Initiatives]]
* [http://www.osgeo.org/node/1069 Helena Mitasova Receives Sol Katz Award 2010]
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#f8f8ff;">
==== User Documentation and Support ====
* [[GRASS Help|GRASS Help and Getting Started]]
* [[GRASS Documents|In depth GRASS Documentation]]
* [[Installation Guide]] for precompiled binaries
* '''[[Faq|FAQ]] - Frequently Asked Questions'''
* [[Applications]] - use cases of GRASS in various disciplines
* [[wxGUI]] - Graphical User Interface based on wxPython
</div>

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

==== Community ====
* [[GRASS Community]]: Getting in touch
* [[Applications|Research applications]]: What people are doing with GRASS
* [[GRASS migration hints|Migrating to GRASS]]
* [[GRASS Blogger]]
* Get involved: [[Project jobs]]
* [http://grass.osgeo.org/wiki/Special:Recentchanges?feed=rss RSS feed] of recent changes of this Wiki
</div>

<div>Have a look at the GRASS GIS users worldwide [http://grass.osgeo.org/community/ GRASS GIS User Online]. If you operate a GRASS GIS installation, you are welcome to enter your user data there.
</div>

<div><p>''[[GRASS-Wiki:Language policy|Translate this Wiki]]''</p></div>


| width="38%" style="vertical-align:top" |
<div style="margin:0; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#f8f8ff;">
[[Image:OSGeo 220pix.png|center|220px|link=http://www.osgeo.org]]
<center>OSGeo Foundation Project</center>
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:1em 1em 1em 1em; background-color:#f8f8ff;">
[[Image:Btn_donate_SM.gif|center|link=http://grass.osgeo.org/donation.php]]<center>[http://grass.osgeo.org/donation.php Donate via PayPal.com]</center>
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#f8f8ff;">
* [http://grass.osgeo.org/screenshots/index.php GRASS Screenshots]
* [http://trac.osgeo.org SVN/trac] Source Code Repository
* [http://grass.osgeo.org/community/support.php Mailing lists] and [http://grass.osgeo.org/community/support.php#irc IRC]
* [http://trac.osgeo.org/grass/ Report errors or wishes]
* [https://svn.osgeo.org/grass/grass/branches/releasebranch_6_4/COPYING Licensed under GNU GPL]
</div>

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

==== Download ====
* [http://grass.osgeo.org/download/ Source code and binaries]
* '''[[GRASS AddOns]]'''
* [[Promotional material]]
* [[Sample datasets]]
* [[Global datasets]]
</div>

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

==== Development ====
* [[Compile and Install]] of Source Code
* [[Development|GRASS Development]] intro
* [http://trac.osgeo.org/grass/wiki GRASS-trac]: the development Wiki, bugtracker, source code browser
* [[Release Roadmap]]
* [[GRASS 7 ideas collection]]
* [[GRASS SoC Ideas|Google Summer of Code ideas collection]]
* [http://trac.osgeo.org/grass/wiki/HowToContribute How to contribute to GRASS development] (getting write access and such)
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#f8f8ff;">
Project Metrics provided by [http://www.ohloh.net/projects/3666 Ohloh].

{{#widget:Ohloh Project|id=3666|type=partner_badge}}
</div>
|}

Archeology

2011-12-30T21:37:54Z

⚠️MilenaN: Reverted edits by Reverse22 (talk) to last revision by Neteler

GRASS GIS is used in many archaeological projects.

== Mailing list threads ==

* [http://thread.gmane.org/gmane.comp.gis.grass.user/27990 Who's using GRASS for archaeological applications?]

== Sample archeological data sets ==

* [http://www.tuarc.trentu.ca/~aspweb/en/downloads.shtml Antikythera Survey Project (ASP)]

== See also ==

* Barton, C.M., Ullah, I. & Mitasova, H., 2010. ''Computational modeling and neolithic socioecological dynamics: A case study from southwest Asia''. Am antiquity, 75(2), 364-386. [ [http://sagunto.la.asu.edu:8080/medlandweb/Barton_etal2010.pdf PDF] ]
* M. Neteler, 2009: ''[http://www.slideshare.net/markusN/grass-and-osgeo-a-framework-for-archeology GRASS GIS and OSGeo: A framework for archeology]'' (Invited keynote). Quarto Workshop Italiano [http://www.archeo-foss.org/ "Open Source, Free Software e Open Format nei processi di ricerca archeologica"], CNR di Roma, 27-28 April 2009
* Conolly, J., Lake, M., 2006. Geographical Information Systems in Archaeology (Cambridge Manuals in Archaeology) [ [http://www.amazon.co.uk/Geographical-Information-Systems-Archaeology-Cambridge/dp/0521797446/ Book] ]
* A. Bezzi, L. Bezzi, D. Francisci, R. Gietl, 2006. ''L'utilizzo di Voxel in campo archeologico'', Geomatics workbooks 6 [ [http://geomatica.como.polimi.it/workbooks/n6/list.php PDF] ]

== Some archaeological links related to GRASS ==

* http://wiki.iosa.it/ Quantitative Archaeology Wiki (check out the "Spatial Analysis" section)
* http://arc-team-open-research.blogspot.com/ - GRASS and Blender in archaeology
* http://arkygeek.blogspot.com/
* http://www.arc-team.com/wiki/doku.php - ArcheOS - The first GNU/Linux distribution for archaeology ([http://www.arc-team.com/archeos/wiki/doku.php?id=screenshots screenshots])
* [http://undine-lieberwirth.info/?page_id=8 Voxels and GRASS] in Archeology (animations)
* http://tdx.cat/TESIS_UB/AVAILABLE/TDX-0720109-092434/ - PhD Dissertation about conflict archaeology, with extensive use of GRASS and QGIS.

[[Category:Applications]]
[[Category:Documentation]]