https://grasswiki.osgeo.org/w/api.php?action=feedcontributions&feedformat=atom&user=Lucadelu 2026-05-25T19:43:52Z User contributions MediaWiki 1.41.0 https://grasswiki.osgeo.org/w/index.php?title=GRASS_GSoC_Ideas_2024&diff=27387 2024-02-15T05:28:49Z

<p>Lucadelu: /* Ideas */ added EODAG GSoC 2024 idea</p> <hr /> <div><br /> == About ==<br /> <br /> * [https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2024 The OSGeo GSoC 2024 main page]<br /> * [https://summerofcode.withgoogle.com/ Official GSoC page at Google]<br /> <br /> == Ideas ==<br /> If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list],[https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].<br /> <br /> You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],<br /> [https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],<br /> [https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],<br /> [https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],<br /> [https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],<br /> [https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],<br /> [https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],<br /> [https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])<br /> which have not yet been implemented.<br /> You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''<br /> <br /> Include &quot;GRASS GIS&quot; in the title of our idea to easily distinguish ideas and projects inside OSGeo.<br /> <br /> <br /> === Parallelization of existing tools ===<br /> <br /> There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.horizon, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance,...<br /> For overview of current state, see [[Raster_Parallelization_with_OpenMP]].<br /> <br /> * Requirements: familiarity with C, OpenMP<br /> * Mentor: Huidae Cho<br /> * Co-mentor: Vaclav Petras, Anna Petrasova<br /> * Project length: 175 or 350 hours (take your pick)<br /> * Rating: medium<br /> * Expected Outcomes: parallelized module or modules, depending on complexity<br /> * Test of skills: suggest/implement solution for https://github.com/OSGeo/grass/issues/2644<br /> <br /> === Improve GRASS user experience in Jupyter Notebook ===<br /> [[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]<br /> Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as adding parallelization for rendering, increasing interactivity of displayed data using ipyleaflet (e.g., capture mouse clicks to show information about vector line, pixel), adding API for managing projects and subprojects (i.e., locations/mapsets), simplifing display of attribute data, ...<br /> <br /> * Requirements: Python<br /> * Mentor: Anna Petrasova<br /> * Co-mentor: Vaclav Petras, Helena Mitasova<br /> * Project length: 175 or 350 hours (take your pick)<br /> * Rating: easy to medium<br /> * Expected Outcomes: improved user experience when using GRASS through notebooks<br /> * Test of skills: https://github.com/OSGeo/grass/issues/3276, or write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here].<br /> <br /> === Add JSON output to different tools in C ===<br /> There are several tools in GRASS that would benefit from a JSON-formatted output, see [https://github.com/OSGeo/grass/issues/3020 this issue for a list of tools]. Besides adding the JSON output, the work would also include adding tests and basic documentation.<br /> * Requirements: C, Python for tests<br /> * Mentor: Vaclav Petras<br /> * Co-mentor: Anna Petrasova, Corey White<br /> * Project length: 175 or 350 hours (take your pick)<br /> * Rating: easy to medium<br /> * Expected Outcomes: one or more (depending on project length and complexity of the tool) tools with well tested JSON output<br /> * Test of skills: Address https://github.com/OSGeo/grass/issues/1044 for r.surf.fractal<br /> <br /> === Support writing tests with pytest ===<br /> <br /> * The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.<br /> * ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.<br /> * Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.<br /> * An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).<br /> * Two main things needed:<br /> ** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.<br /> ** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More <br /> * Additional things needed:<br /> ** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.<br /> <br /> * Requirements: Python<br /> * Project length: 175 or 350 hours (take your pick)<br /> * Mentor: Vaclav Petras<br /> * Co-mentor: Stefan Blumentrath<br /> * Proposed by: Vaclav Petras<br /> * Rating: easy to medium<br /> * Expected Outcomes: Convenient way of writing tests with pytest<br /> * Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.<br /> <br /> === New easy-to-use CLI and API for GRASS GIS ===<br /> <br /> * Make running of GRASS GIS modules as easy as it is to run GDAL commands.<br /> ** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`<br /> ** CLI like GDAL has.<br /> ** No GRASS Database, Location, Mapset to deal with.<br /> ** No import, export from user perspective.<br /> ** Reasonable defaults for things like region.<br /> ** CLI and API still allows user to specify any of the above.<br /> * Idea page with details: wiki:GSoC/2021/EasyToUseCliAndApiIdea<br /> * Project length: 350 hours<br /> * Rating: medium<br /> * Requirements:<br /> ** Language: Python<br /> ** Proposal: Student needs to show sufficient understanding of the GRASS GIS Database structure and significantly extend on text below in terms of more concrete formulation of ideas and identification of missing and existing parts.<br /> * Mentors: Vaclav Petras<br /> * Co-mentors: Stefan Blumentrath<br /> * Proposed by: Vaclav Petras<br /> * Expected outcomes: New subcommand which easily runs a GRASS module on GeoTiff and GeoPackage.<br /> * Test and training tasks:<br /> ** Solve one of the tickets linked at the idea page.<br /> ** Add features to `grass` executable interface:<br /> *** Make it possible to associate `*.gxw` files with `grass` executable (#1204) or at least add `--gui-workspace` or preferably just recognize it in the command line (distinguish it from database/location/mapset).<br /> ** Extend `--exec` functionality:<br /> *** Add `--region` to set a temporary computational region for the execution, e.g. `--region=&quot;raster=raster_name&quot;`<br /> *** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).<br /> *** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).<br /> <br /> === STAC (SpatioTemporal Asset Catalog) Integration ===<br /> <br /> Create new import and export capabilities for GRASS GIS which allow users to easily ingest data from STAC catalogs and export locations and mapsets as STAC specs for data discovery within STAC browsers. <br /> <br /> * Requirements: familiar with python, STAC specs<br /> * Mentor: Corey White<br /> * Co-mentor: Vaclav Petras, Anna Petrasova<br /> * Project length: 175 or 350 hours (take your pick)<br /> * Rating: medium<br /> * Expected Outcomes: completion of t.in.stac and t.out.stac<br /> * Test of skills:<br /> ** suggest or implement solution for implementing t.out.stac using the prototype STAC spec https://github.com/tomorrownow/grass-stac-extension <br /> ** suggest/implement solution for completing https://github.com/OSGeo/grass-addons/pull/802<br /> <br /> === Add EODAG support to ===<br /> <br /> EODAG is a Python library useful to download several satellite dataset from different provider. It could be useful to implement as possible back-end for several i.*.import (sentinel e landas in primis)<br /> <br /> * Requirements: familiar with Python<br /> * Project length: 175 or 350 hours<br /> * Mentor: Luca Delucchi<br /> * Co-mentor: Veronica Andreo<br /> * Proposed by: Luca Delucchi<br /> * Rating: medium<br /> * Expected Outcomes: 175 hours EODAG core library to be able to download products; 350 library + application at least to i.sentinel.download but hopefully also to i.landsat.download<br /> * Test of skills: <br /> <br /> <br /> === Add {your research idea} to GRASS GIS ===<br /> <br /> * In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS GIS.<br /> * Requirements:<br /> ** Language:<br /> *** Depends on the project, often Python, sometimes C.<br /> *** Adding your latest ecological analysis <br /> ** Proposal:<br /> *** Discuss relevance to GRASS GIS.<br /> *** Describe technical steps needed for integration.<br /> *** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.<br /> *** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.<br /> *** Specify who will provide the research expertise.<br /> * Project length: 175 or 350 hours (take your pick)<br /> * Rating: from low to hard<br /> * Mentors:<br /> ** GRASS GIS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.<br /> ** Possible technical mentors: Vaclav Petras, Anna Petrasova<br /> ** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).<br /> * Proposed by: Vaclav Petras<br /> * Expected outcome: Working feature which is integrated and merged at the end of the project.<br /> * Test and training tasks:<br /> ** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.<br /> <br /> === Title of idea ===<br /> <br /> Description here<br /> <br /> * Requirements:<br /> * Project length: (175 or 350 hours) <br /> * Mentor: <br /> * Proposed by: <br /> * Rating: <br /> * Expected Outcomes: <br /> * Test of skills: <br /> * Other:<br /> <br /> == Tips for students ==<br /> <br /> * If you have your own ideas we encourage you to propose them. Explain them on the [https://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list].<br /> * If you like some idea here or from previous yeas, write about it on [https://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list] and any ideas of your own which could improve it.<br /> * Follow some good practices in your ideas and proposals:<br /> ** Stress why the project would be useful.<br /> ** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.<br /> ** Be specific in the implementation (or at least as specific as you can).<br /> ** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.<br /> ** Explain how the idea relates to existing GRASS GIS functions, features, and needs.<br /> ** Do not include steps such as &quot;install GRASS&quot;, &quot;compile GRASS libraries (on my machine)&quot;, &quot;read about the API&quot;. You should do this before applying to GSoC.<br /> * Compile GRASS GIS from source and prepare environment for development:<br /> ** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file] and [https://grasswiki.osgeo.org/wiki/Compile_and_Install compilation instructions].<br /> ** If you get stuck with the setup, feel free to consult the [https://lists.osgeo.org/listinfo/grass-user grass-user mailing list].<br /> ** Familiarize yourself with wiki:Submitting rules.<br /> * Prove your worth by being active on the GRASS mailing lists ([https://lists.osgeo.org/listinfo/grass-user grass-user], [https://lists.osgeo.org/listinfo/grass-dev grass-dev]) or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], [https://gitter.im/grassgis/community Gitter]), fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC. <br /> * Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.<br /> <br /> * Every year GRASS GIS hopes to participate and participates in GSoC as part of the [https://www.osgeo.org/ OSGeo Foundation]'s GSoC program umbrella. See the official OSGeo template for application details and other important information at the [https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students OSGeo Recommendations for Students].</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=AddOns&diff=26137 2020-03-29T22:01:51Z

<p>Lucadelu: </p> <hr /> <div>This page contains references to user contributions and add-ons (the original GRASS GIS software can be downloaded [http://grass.osgeo.org/download/ here]).<br /> <br /> __TOC__<br /> <br /> == Overview ==<br /> <br /> '''[http://grass.osgeo.org/grass7/manuals/addons/ GRASS GIS 7 Addons Manual pages] - a complete overview of available Addons'''<br /> <br /> == Building and installing AddOns ==<br /> <br /> === Common users ===<br /> <br /> '''Graphical user interface:'''&lt;br&gt;<br /> We recommend to use the [[wxGUI]] [[WxGUI#Extension Manager|Extension Manager]] (''Settings -&gt; Addon extensions -&gt; Install extensions from addons'') to install Addons.<br /> <br /> '''Command line:'''&lt;br&gt;<br /> You can also use the {{cmd|g.extension}} module, e.g. to install &lt;tt&gt;r.fuzzy.system&lt;/tt&gt; run:<br /> <br /> g.extension extension=r.fuzzy.system<br /> <br /> To remove installed AddOns run<br /> <br /> g.extension extension=r.fuzzy.system operation=remove<br /> <br /> === Power users (not recommended for Windows users) ===<br /> <br /> For manual compiling see the [[Compile and Install#Addons|compile and install]] wiki page.<br /> <br /> == AddOns source code repository ==<br /> <br /> The AddOns source code is hosted in [https://github.com/osgeo/grass-addons GRASS-AddOns Github repository].<br /> <br /> == Adding something new ==<br /> <br /> === How to obtain write-access ===<br /> <br /> Please read [http://trac.osgeo.org/grass/wiki/HowToContribute#WriteaccesstotheGRASS-Addons-SVNrepository how to get write access to the GRASS-Addons-SVN repository] and contact the [http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev] mailing list if you would like to host your module there.<br /> <br /> Please announce your add-on to the GRASS users' mailing list so that others may be aware of your work. Also please consider adding your module to one of the [[Applications]] pages.<br /> <br /> === Copyright and licensing information ===<br /> <br /> ''Please be sure to include copyright and licensing information in the header comments of your code so that others may know how they can use, extend, modify, and redistribute your work.''<br /> <br /> e.g. at the top of a shell script:<br /> &lt;source lang=bash&gt;<br /> #!/bin/sh<br /> ############################################################################<br /> #<br /> # MODULE: v.in.e00<br /> #<br /> # AUTHOR(S): Markus Neteler, Otto Dassau<br /> #<br /> # PURPOSE: Import E00 data into a GRASS vector map<br /> # Imports single and split E00 files (.e00, .e01, .e02 ...)<br /> #<br /> # COPYRIGHT: (c) 2004, 2005 GDF Hannover bR, http://www.gdf-hannover.de<br /> #<br /> # This program is free software under the GNU General Public<br /> # License (&gt;=v2). Read the file COPYING that comes with GRASS<br /> # for details.<br /> #<br /> #############################################################################<br /> #<br /> # REQUIREMENTS:<br /> # - avcimport: http://avce00.maptools.org<br /> <br /> [script follows]<br /> &lt;/source&gt;<br /> <br /> === Coding standards ===<br /> <br /> Please have a look at our {{src|SUBMITTING}} for C-programs, {{src|SUBMITTING_PYTHON}} for Python scripts or {{src|SUBMITTING_SCRIPTS|branch=branches/develbranch_6}} for Bash scripts coding standards before submitting here.<br /> <br /> === Documenting your code ===<br /> <br /> You can have an help page template auto-generated by using the GRASS [[module command line parser | command line parser]] with the &lt;tt&gt;--html-description&lt;/tt&gt; command line option. Please, see also the {{cmd|g.parser}} help page.<br /> <br /> == Miscellaneous Add-ons ==<br /> <br /> * [http://trac.osgeo.org/grass/browser/grass-addons/grass6/misc/utm_which_zone utm_which_zone.sh] is a shell script to determine UTM zone from Lat/Lon input. Requires [http://www.octave.org Octave] or Matlab to be installed. A shell-only version is [http://dcalvelo.free.fr/grass/utm_which_zone_sh.sh available] which only requires awk.&lt;BR&gt;'''Authors''': Hamish Bowman (Octave part), Markus Neteler (shell script wrapper), Daniel Calvelo (sh+awk version)<br /> <br /> <br /> * Perl scripts for converting data forth and back between Excel files and PostgreSQL: [http://dcalvelo.free.fr/grass/pg2xls.pl pg2xls.pl] reads data from PostgreSQL and produces an excel workbook; [http://dcalvelo.free.fr/grass/xls2sql.pl xls2sql.pl] reads excel files and outputs SQL statements to be fed into an RDBMS. Both scripts need modules from [http://www.cpan.org CPAN], especially [http://search.cpan.org/dist/Spreadsheet-ParseExcel/ Spreadsheet::ParseExcel] for xls2sql.pl and [http://search.cpan.org/~tmtm/Spreadsheet-WriteExcel-FromDB Spreadsheet::WriteExcel::FromDB] and its dependencies for pg2sql.pl. Check the source headers for more info.&lt;BR&gt;'''Authors:''' Daniel Calvelo (xls2sql.pl), Markus Neteler (pg2xls.pl)<br /> <br /> <br /> * [http://dream.lrrl.arch.tu-muenchen.de/~wqual/perl/dbf2sql.tgz dbf2sql] is a Perl script for translating dbf-tables into a sql-command. dbf-tables are read using dbfdump-command from dbd-xbase-perl module ([http://search.cpan.org/~janpaz/DBD-XBase-0.241/ dbd::xbase] and [http://search.cpan.org/~jv/Getopt-Long-2.35/lib/Getopt/Long.pm getopt::long] have to be installed from CPAN first). There are problems, if the last column of the table contains characters. Suggestions for improvements welcome! &lt;BR&gt;'''Author:'''Wolfgang Qual<br /> <br /> <br /> * [http://www.igc.usp.br/pessoais/guano/downloads/azimuth2.c azimuth2.c] is a small C program to calculate the azimuth and length of vector lines exported by GRASS-GIS as ASCII files (like this: v.out.ascii input=vector output=ascii format=standard). It is useful for create rose diagrams of lineament maps. Improvements on the original code after suggestions by Örs Téglásy, Hungary.&lt;BR&gt;'''Author:''' Carlos Henrique Grohmann<br /> <br /> <br /> * [http://www.wgug.org/index.php?option=com_content&amp;view=article&amp;id=56&amp;Itemid=9 ann.*] is the set of GRASS modules (in python) which implements artificial neural network using FANN library. The package requires Fast Artificial Neural Network Library ([http://leenissen.dk/fann/wp/ FANN]) v2.x. &lt;BR&gt;'''Author:''' Pawel Netzel<br /> <br /> <br /> * [http://trac.osgeo.org/grass/browser/grass-addons/tools/csv_dequote.pl csv_dequote.pl] is a Perl script to convert comma separated .csv files (including &quot;quoted&quot; text strings containing commas) into a form ready for {{Cmd|v.in.ascii}}. Comma separators are converted to pipes (|), commas in quoted strings are preserved, and &quot;quotes&quot; are removed where it is appropriate to do so. It doesn't need GRASS to run, but it does need the Text::CSV Perl Module (&lt;tt&gt;apt-get install libtext-csv-perl&lt;/tt&gt;).&lt;BR&gt;'''Author''': Hamish Bowman<br /> <br /> ==GRASS 7.x (current)==<br /> <br /> * See [[AddOns/GRASS 7]]<br /> <br /> == GRASS 6.x (previous) ==<br /> <br /> * See [[AddOns/GRASS 6]]<br /> <br /> ==GRASS 5.x (old)==<br /> <br /> * See [[AddOns/GRASS 5]]<br /> <br /> ==GRASS 4.x (very old)==<br /> <br /> * See [[AddOns/GRASS 4]]<br /> <br /> {{AddOns}}</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GIS_Community_Sprint_Prague_2019&diff=25950 2019-11-12T10:18:58Z

<p>Lucadelu: /* Via video-call */</p> <hr /> <div>{{toc|right}}<br /> <br /> == Timing, Venue ==<br /> <br /> '''December 2 (Mon) - 6 (Fri), 2019'''<br /> <br /> '''Czech Technical University, Faculty of Civil Engineering, Department of Geomatics, Czech Republic'''<br /> <br /> Location: Thákurova 7/2077, Prague ([https://www.openstreetmap.org/node/296790285 OSM Map])<br /> <br /> == Sponsors ==<br /> <br /> &lt;!--<br /> Faculty of Civil Engineering, Czech Technical University in Prague: Free provision of meeting rooms and internet access.<br /> --&gt;<br /> <br /> Donation from OSGeo. Please check more info [[GRASS GIS Budget 2019]].<br /> <br /> We also welcome direct '''financial contributions''' to help reducing traveling and accommodation expenses for GRASS developers with far arrival. If you are interested to sponsor the GRASS Community Sprint, please read about<br /> <br /> :::'''sponsoring the GRASS project''' via our [https://www.paypal.com/pools/c/86YKZiIEPV Paypal money pool]<br /> <br /> [[Image:Btn_donate_SM.gif|center|link=http://grass.osgeo.org/donations/]]<br /> <br /> For any questions, please contact [[User:Landa|Martin Landa]]. Any surplus at the end of the event will be turned over to the GRASS GIS project.<br /> <br /> This GRASS GIS 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.<br /> <br /> == Agenda - What we plan to do ==<br /> <br /> === New website ===<br /> <br /> * work on https://github.com/osgeo/grass-website<br /> * goal: publish at grass.osgeo.org<br /> <br /> == Planned participation ==<br /> <br /> For organizational reasons. <br /> <br /> === In person ===<br /> <br /> Please add your name here:<br /> <br /> {|class=&quot;wikitable sortable&quot; border=&quot;2&quot; cellspacing=&quot;0&quot; cellpadding=&quot;4&quot; rules=&quot;all&quot; style=&quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;&quot; <br /> |width=50px|'''No'''<br /> |width=130px|'''Participant '''<br /> |width=100px|'''Country'''<br /> |width=100px|'''Arrival'''<br /> |width=100px|'''Departure'''<br /> |'''Topics'''<br /> |width=75px|'''T-Shirt'''<br /> |'''Notes'''<br /> |-<br /> |1<br /> |[[User:Landa|Martin Landa]]<br /> |Czech Republic<br /> |2 at 9pm<br /> |6 at 6pm<br /> | trac tickets -&gt; github issues, website <br /> |L<br /> |<br /> |-<br /> |2<br /> |[[User:Annakrat|Anna Petrasova]]<br /> |USA/Czech Republic<br /> |Dec 2nd<br /> |Dec 6th<br /> | Windows packaging, tickets<br /> |M<br /> |<br /> |-<br /> |3<br /> |[[User:Wenzeslaus|Vaclav Petras]]<br /> |USA/Czech Republic<br /> |Dec 2nd<br /> |Dec 6th<br /> | packaging, CI/CD, usage from Python, &quot;try&quot; links for website<br /> |M<br /> |<br /> |-<br /> |4<br /> |[[User:pesekon2|Ondřej Pešek]]<br /> |Czech Republic<br /> |02/12<br /> |06/12<br /> | work on the PyWPS export from gmodeler, gmodeler-related tickets (#3923...), ANN<br /> |M<br /> |<br /> |-<br /> |5<br /> | ...<br /> | ...<br /> | ...<br /> | ...<br /> | ... <br /> | ...<br /> |<br /> |}<br /> <br /> == Accomodation ==<br /> <br /> There are several Hotels etc. in walking distance.<br /> <br /> * [https://www.booking.com/hotel/cz/masarykova-kolej.cs.html?aid=319857;label=masarykova-kolej-TngsSqgmY%2AocIfWpdmiXowS260938285165%3Apl%3Ata%3Ap1%3Ap2%3Aac%3Aap1t1%3Aneg%3Afi%3Atikwd-15484732688%3Alp9050622%3Ali%3Adec%3Adm;sid=514199703cd3971e6e4e79d182dc6cfd;dest_id=-553173;dest_type=city;dist=0;group_adults=2;group_children=0;hapos=1;hpos=1;no_rooms=1;room1=A%2CA;sb_price_type=total;sr_order=popularity;srepoch=1573147043;srpvid=2f697991408f000f;type=total;ucfs=1&amp;#hotelTmpl Masarykova Kolej Hotel]<br /> * [https://www.booking.com/hotel/cz/vienna-house-diplomat-prague.cs.html?aid=318615;label=New_Czech_CS_5226362425-hguKzeUDx5wVngMHZ4sx6AS73336449145%3Apl%3Ata%3Ap1%3Ap2%3Aac%3Aap1t1%3Aneg;sid=514199703cd3971e6e4e79d182dc6cfd;dest_id=-553173;dest_type=city;dist=0;group_adults=2;group_children=0;hapos=1;hpos=1;no_rooms=1;room1=A%2CA;sb_price_type=total;sr_order=popularity;srepoch=1573147109;srpvid=130879b2918b00a2;type=total;ucfs=1&amp;#hotelTmpl Vienna House Diplomat Prague]<br /> * ...<br /> <br /> == Venue ==<br /> <br /> === Points of contact ===<br /> <br /> * Martin Landa: landa.martin AT gmail DOT com<br /> <br /> ==== Address ====<br /> <br /> Czech Technical University in Prague, Faculty of Civil Engineering, Thákurova 7/2077, Prague ([https://www.openstreetmap.org/node/296790285 OSM Map])<br /> <br /> ==== Public transport ====<br /> <br /> Public transportation works nicely in general.<br /> <br /> ===== Subway / Metro =====<br /> <br /> * From Airport: take bus 119 to Nadrazi Veleslavin (end station), change to underground (green line) and go to Dejvicka station<br /> * From (Main) Railway Station: take underground (red line) to Muzeum change to green line and go to Dejvicka station<br /> <br /> ==== Rooms &amp; hours ====<br /> <br /> '''TBD'''<br /> <br /> ==== Dangers &amp; Annoyances ====<br /> <br /> '''TBD'''<br /> <br /> == Recreation and cultural events ==<br /> <br /> '''TBD'''<br /> <br /> == Tasks ==<br /> <br /> === Pre-event tasks ===<br /> <br /> ==== Remaining tasks ====<br /> <br /> * Book room<br /> * Internet connection<br /> * Plan/order catering<br /> * Discuss swag (t-shirts ? mugs ?)<br /> * consider whatsapp(or similar) channel for last minute communication<br /> * consider side events: <br /> ** Group picture ?<br /> ** Fancy dinner ?<br /> <br /> ==== Completed tasks ====<br /> <br /> * {{done}}: TBD<br /> <br /> === Via IRC chat ===<br /> <br /> (IRC is a nice archaic chat system, see [[IRC]])<br /> <br /> {|class=&quot;wikitable sortable&quot; border=&quot;2&quot; cellspacing=&quot;0&quot; cellpadding=&quot;4&quot; rules=&quot;all&quot; style=&quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;&quot; <br /> |width=50px|'''No'''<br /> |width=130px|'''Participant '''<br /> |width=100px|'''Country'''<br /> |'''Note'''<br /> |-<br /> |@#<br /> |...<br /> |<br /> |<br /> |-<br /> |}<br /> <br /> === Via video-call ===<br /> <br /> We can use Hangouts, Zoom, Jitsi or Skype... Plenty of options!<br /> <br /> {|class=&quot;wikitable sortable&quot; border=&quot;2&quot; cellspacing=&quot;0&quot; cellpadding=&quot;4&quot; rules=&quot;all&quot; style=&quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;&quot; <br /> |width=50px|'''No'''<br /> |width=130px|'''Participant '''<br /> |width=100px|'''Country'''<br /> |'''Note'''<br /> |-<br /> |1<br /> |[[User:Veroandreo|Veronica Andreo]]<br /> |Argentina<br /> |<br /> |-<br /> |2<br /> |[[User:Lucadelu|Luca Delucchi]]<br /> |Italy<br /> |Website improvements<br /> |-<br /> |...<br /> |<br /> |<br /> |<br /> |-<br /> |}<br /> <br /> == Individual Preparation ==<br /> <br /> * Bring your own computer<br /> * Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:Schuko_plug_and_socket.png Czech Republic]). See also http://www.power-plugs-sockets.com/<br /> * Install git, and the compiler tools, and come with a working GRASS development environment if possible.<br /> <br /> == Photos ==<br /> <br /> == Reports ==<br /> <br /> See [[Talk:GRASS GIS Community Sprint Prague 2019]]<br /> <br /> == FAQ ==<br /> <br /> * ''Is the GRASS Community Sprint just a coding event?''<br /> ** 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.<br /> ** 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<br /> * ''Is the GRASS Community Sprint for developers only?''<br /> ** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.<br /> * ''Where can I get help and more information about the community sprint?''<br /> ** Contact Martin Landa &lt;tt&gt;landa.martin gmail.com&lt;/tt&gt;<br /> <br /> [[Category: Workshops]]<br /> [[Category: Code Sprint]]<br /> [[Category: 2019]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=Image_classification&diff=25333 2018-09-20T13:31:16Z

<p>Lucadelu: </p> <hr /> <div>== Image classification ==<br /> <br /> '''Classification methods in GRASS'''<br /> <br /> {| {{table}}<br /> | ||'''radiometric&lt;BR&gt;unsupervised'''||'''radiometric&lt;BR&gt;supervised 1'''||'''radiometric&lt;BR&gt;supervised 2'''||'''radiometric &amp; geometric&lt;BR&gt;supervised'''<br /> |-<br /> | '''Image Preprocessing''' || colspan=&quot;4&quot; style=&quot;text-align: center;&quot;| {{AddonCmd|r.smooth.seg}} (optional, in case of noisy original data)<br /> |-<br /> | '''Segmentation''' || colspan=&quot;4&quot; style=&quot;text-align: center;&quot;| {{cmd|i.segment}}<br /> |-<br /> | '''Preprocessing'''||{{cmd|i.cluster}}||{{cmd|i.class}} (monitor digitizing), {{cmd|g.gui.iclass|version=70}} (in GRASS 70)||{{cmd|i.gensig}} (using training maps)||{{cmd|i.gensigset}} (using training maps)<br /> |-<br /> | '''Classification'''||{{cmd|i.maxlik}}||{{cmd|i.maxlik}}||{{cmd|i.maxlik}}||{{cmd|i.smap}}<br /> |-<br /> | '''Remarks'''||automated run based||requires digitalization||requires digitalization||requires digitalization<br /> |-<br /> | ||on image statistics||of training areas||of training areas||of training areas<br /> |}<br /> <br /> You can digitize training areas with either r.digit (not recommended) or &lt;strike&gt;v.digit&lt;/strike&gt; [[GRASS Digitizing tool]] + v.to.rast (recommended)<br /> <br /> <br /> === Image Preprocessing (optional) ===<br /> * {{AddonCmd|r.smooth.seg}} - produces a smooth approximation of the data and performs discontinuity detection. The module is based on the Mumford-Shah variational model for image segmentation. Used as pre-analysis for a subsequent classification.<br /> : For details, see the {{AddonCmd|r.smooth.seg}} manual (formerly called: r.seg)<br /> * {{cmd|i.segment}} - identifies segments (objects) from imagery data based (currently) on a region growing and merging algorithm. The image segmentation results can be useful (on their own or) as a preprocessing step for image classification, i.e. reduce noise and speed up the classification.<br /> ** Classification of these segments: see below in &quot;Unsupervised classification&quot;.<br /> <br /> === Interactive setup ===<br /> <br /> * {{cmd|i.class}} - Generates spectral signatures for an image by allowing the user to outline regions of interest.<br /> : The resulting signature file can be used as input for {{cmd|i.maxlik}} or as a seed signature file for {{cmd|i.cluster}}.<br /> * {{cmd|g.gui.iclass|version=70}} - Tool for supervised classification of imagery data.<br /> <br /> === Preprocessing ===<br /> <br /> * {{cmd|i.cluster}} - Generates spectral signatures for land cover types in an image using a clustering algorithm.<br /> : The resulting signature file is used as input for {{cmd|i.maxlik}}, to generate an unsupervised image classification.<br /> * {{cmd|i.gensig}} - Generates statistics for {{cmd|i.maxlik}} from raster map layer.<br /> * {{cmd|i.gensigset}} - Generate statistics for {{cmd|i.smap}} from raster map layer.<br /> <br /> Background information concerning {{cmd|i.cluster}}:<br /> * Discussion: [https://lists.osgeo.org/pipermail/grass-user/2012-October/066046.html Is &quot;i.cluster&quot; an implementation of the ISODATA algorithm?]<br /> * [[User:NikosA/About Clustering|About Clustering]]<br /> <br /> === Unsupervised classification ===<br /> <br /> For an introduction, see for example {{wikipedia|Cluster_analysis}}.<br /> <br /> * {{cmd|i.maxlik}} - Classifies the cell spectral reflectances in imagery data.<br /> : Classification is based on the spectral signature information generated by {{cmd|i.cluster}} (see above)<br /> * GRASS GIS 7: {{cmd|i.segment}}<br /> ** Classification of these segments could be achieved with these addons: {{AddonCmd|v.class.mlR}}, {{AddonCmd|v.class.mlpy}}, {{AddonCmd|v.class.ml}}.<br /> <br /> See example below.<br /> <br /> === Supervised classification ===<br /> <br /> * {{cmd|i.maxlik}} - Classifies the cell spectral reflectances in imagery data.<br /> : Classification is based on the spectral signature information generated by either {{cmd|i.class}}, or {{cmd|i.gensig}}.<br /> * {{cmd|g.gui.iclass}} - Tool for supervised classification of imagery data.<br /> * {{cmd|i.smap}} - Performs contextual (image segmentation) image classification using sequential maximum a posteriori (SMAP) estimation.<br /> * {{AddonCmd|r.learn.ml}} - Supervised Machine Learning classification and regression of GRASS rasters using the python scikit-learn package <br /> * In case of panchromatic maps or limited amount of channels, it is often recommended to generate synthetic channels through texture analysis ({{cmd|r.texture}})<br /> <br /> See example below.<br /> <br /> == Object-based classification and image segmentation ==<br /> ''Created based on [http://lists.osgeo.org/pipermail/grass-user/2014-June/070384.html Summary of object-based classification possibilities in GRASS GIS (June 2014)]. Feel free to merge this with other content or with different page.''<br /> <br /> Related commands:<br /> * {{cmd|i.segment}} - Identifies segments (objects) from imagery data. <br /> * {{AddonCmd|i.segment.hierarchical}} performs a hierarchical segmentation on an image (group). The module uses internally {{cmd|i.segment}}<br /> * {{AddonCmd|i.segment.stats}} calculates statistics describing raster area.<br /> * extra: {{AddonCmd|r.smooth.seg}} - Generates a piece-wise smooth approximation of the input raster and a discontinuity map.<br /> <br /> Background information:<br /> * [http://lists.osgeo.org/pipermail/grass-dev/2013-October/066181.html Moritz's steps and the main discussion: Object-based image classification in GRASS] ([http://osgeo-org.1560.x6.nabble.com/Object-based-image-classification-in-GRASS-td5086693.html nabble link])<br /> * [http://geo.fsv.cvut.cz/gwiki/153ZODH_/_15._cvi%C4%8Den%C3%AD Moritz's steps in a nice guide by Martin, in Czech with images] ([http://translate.google.com/translate?sl=cs&amp;tl=en&amp;js=n&amp;prev=_t&amp;hl=en&amp;ie=UTF-8&amp;u=http%3A%2F%2Fgeo.fsv.cvut.cz%2Fgwiki%2F153ZODH_%2F_15._cvi%25C4%258Den%25C3%25AD&amp;act=url English Google-translation])<br /> * [http://lists.osgeo.org/pipermail/grass-user/2013-November/069254.html Alternative notes by Moritz: Classification of segments] ([http://osgeo-org.1560.x6.nabble.com/Re-Classification-of-segments-td5088837.html nabble link])<br /> * [http://lists.osgeo.org/pipermail/grass-dev/2014-January/066804.html Pietro's steps and tools] ([http://osgeo-org.1560.x6.nabble.com/Object-based-image-classification-in-GRASS-tp5086693p5096826.html nabble link])<br /> * [http://lists.osgeo.org/pipermail/grass-dev/2013-August/065287.html Another discussion about what variables to use: Object-based classification] ([http://osgeo-org.1560.x6.nabble.com/i-segment-invalid-region-id-0-tp5066102p5070201.html nabble link])<br /> <br /> Source code and scripts:<br /> * The source code of the classification tools (for inspiration in writing your own scripts):<br /> ** v.class.ml: http://svn.osgeo.org/grass/grass-addons/grass7/vector/v.class.ml/ (Pietro's tool)<br /> ** v.class.mlpy: http://svn.osgeo.org/grass/grass-addons/grass7/vector/v.class.mlpy/ (Vaclav's tool)<br /> ** i.mlpy.py: http://svn.osgeo.org/grass/sandbox/turek/i.mlpy.py (Stepan's tool)<br /> * List of Python machine learning libraries:<br /> ** scikit-learn, http://scikit-learn.org/ (used by v.class.ml)<br /> ** mlpy, http://mlpy.sourceforge.net/ (used by v.class.ml, v.class.mlpy and i.mlpy)<br /> ** Pandas, http://pandas.pydata.org/<br /> ** Milk, http://luispedro.org/software/milk<br /> <br /> <br /> == Small classification tutorial ==<br /> <br /> Required: GRASS &gt;= 6.4<br /> <br /> We are using Landsat satellite data prepared for the [http://www.grassbook.org/data_menu3rd.php North Carolina] sampling site. It is a multispectral dataset where each channel is stored in a separate map.<br /> <br /> We are using the North Carolina location here.<br /> <br /> === Warming up with Landsat TM ===<br /> <br /> # look what maps are there<br /> g.list rast<br /> # set to one of the color channels and print current region settings<br /> g.region rast=lsat7_2002_10 -p<br /> <br /> # look at some Landsat map (1: blue, 2: green, 3: red, 4: near infrared etc.)<br /> d.mon x0<br /> d.rast lsat7_2002_10<br /> d.rast lsat7_2002_20<br /> d.rast lsat7_2002_30 <br /> d.rast lsat7_2002_40<br /> <br /> We can easily query the spectrum for individual points:<br /> d.what.rast lsat7_2002_10,lsat7_2002_20,lsat7_2002_30,lsat7_2002_40<br /> <br /> Histogram of a channel:<br /> d.histogram lsat7_2002_10<br /> <br /> Create RGB view on the fly, true and false color:<br /> d.rgb b=lsat7_2002_10 g=lsat7_2002_20 r=lsat7_2002_30<br /> d.rgb b=lsat7_2002_70 g=lsat7_2002_20 r=lsat7_2002_30<br /> d.rgb b=lsat7_2002_70 g=lsat7_2002_50 r=lsat7_2002_30<br /> d.rgb b=lsat7_2002_70 g=lsat7_2002_50 r=lsat7_2002_10<br /> <br /> Check thermal channel (encoded to fit into 0.255 data range):<br /> # http://landsathandbook.gsfc.nasa.gov/handbook/handbook_htmls/chapter11/chapter11.html<br /> # Look up LMIN/LMAX: &quot;Table 11.2 ETM+ Spectral Radiance Range watts/(meter squared * ster * µm)&quot;<br /> # we won't go into details here, r.mapcalc would be used to convert to Kelvoin/degree Celsius.<br /> <br /> # look at encoded thermal channel<br /> d.rast lsat7_2002_61<br /> <br /> NDVI as example for map algebra:<br /> r.mapcalc &quot;ndvi = 1.0 * (lsat7_2002_40 - lsat7_2002_30)/(lsat7_2002_40 + lsat7_2002_30)&quot;<br /> d.rast.leg ndvi<br /> r.colors ndvi color=ndvi<br /> d.rast.leg ndvi<br /> <br /> Show selected NDVI &quot;classes&quot;:<br /> d.rast ndvi val=0.3-1.0<br /> d.rast ndvi val=-1.0--0.1<br /> d.rast ndvi val=0.0-0.2<br /> d.rast ndvi val=0.0-0.3<br /> <br /> Look at panchromatic channel, compare resolution:<br /> g.region rast=lsat7_2002_80 -p<br /> d.erase -f<br /> d.rast lsat7_2002_80<br /> d.zoom<br /> d.rast lsat7_2002_30<br /> d.rast lsat7_2002_80<br /> <br /> === Image Classification ===<br /> <br /> Set region setting to red image:<br /> g.region rast=lsat7_2002_30 -p<br /> <br /> Create a group<br /> i.group group=lsat7_2002 subgroup=lsat7_2002 \<br /> input=lsat7_2002_10,lsat7_2002_20,lsat7_2002_30,lsat7_2002_40,lsat7_2002_50,lsat7_2002_70<br /> <br /> ==== Unsupervised classification====<br /> <br /> Generate unsupervised statistics<br /> i.cluster group=lsat7_2002 subgroup=lsat7_2002 sigfile=lsat7_2002_sig classes=10 reportfile=lsat7_2002.txt<br /> <br /> # look at report file<br /> gedit lsat7_2002.txt <br /> <br /> Assign pixels to classes, check quality of assignment:<br /> i.maxlik group=lsat7_2002 subgroup=lsat7_2002 sigfile=lsat7_2002_sig class=lsat7_2002_class reject=lsat7_2002_reject<br /> <br /> # false color composite<br /> d.mon x0 ; d.font Vera<br /> d.rgb b=lsat7_2002_70 g=lsat7_2002_50 r=lsat7_2002_10<br /> # classification result<br /> d.mon x1 ; d.font Vera<br /> d.rast.leg lsat7_2002_class<br /> # rejection map<br /> d.mon x2 ; d.font Vera<br /> d.rast.leg lsat7_2002_reject<br /> # rejection histogram<br /> d.mon x3 ; d.font Vera<br /> d.histogram lsat7_2002_reject<br /> <br /> <br /> &lt;center&gt;<br /> {|<br /> | [[Image:Map_lsat7_2002_r1g5b7.png|thumb|center|300px|NC Landsat map 2002 - false color composite]]<br /> | [[Image:Map_lsat7_2002_class.png|thumb|center|300px|unsupervised classification]]<br /> |}<br /> &lt;/center&gt;<br /> &lt;center&gt;<br /> {|<br /> | [[Image:Histogram_lsat7_2002_reject.png|thumb|center|300px|unsupervised classification rejection map histogram]]<br /> | [[Image:Map_lsat7_2002_reject.png|thumb|center|300px|unsupervised classification rejection map]]<br /> |}<br /> &lt;/center&gt;<br /> <br /> <br /> <br /> Play with different cluster separations:<br /> i.cluster group=lsat7_2002 subgroup=lsat7_2002 sigfile=lsat7_2002_sig classes=10 reportfile=lsat7_2002.txt separation=1.5<br /> i.maxlik group=lsat7_2002 subgroup=lsat7_2002 sigfile=lsat7_2002_sig class=lsat7_2002_class2 reject=lsat7_2002_reject2<br /> d.mon x4<br /> d.rast.leg lsat7_2002_class2<br /> d.rast.leg lsat7_2002_reject2<br /> d.rast.leg lsat7_2002_reject<br /> d.rast.leg lsat7_2002_reject2<br /> d.rast.leg lsat7_2002_reject<br /> d.rast.leg lsat7_2002_reject2<br /> d.rast.leg lsat7_2002_class2<br /> <br /> Compare to RGB:<br /> d.rgb b=lsat7_2002_70 g=lsat7_2002_50 r=lsat7_2002_10<br /> d.rast lsat7_2002_class2 cat=1 -o<br /> d.rgb b=lsat7_2002_70 g=lsat7_2002_50 r=lsat7_2002_10<br /> d.rast lsat7_2002_class cat=1 -o<br /> d.rgb b=lsat7_2002_70 g=lsat7_2002_50 r=lsat7_2002_10<br /> d.rast lsat7_2002_class cat=1 -o<br /> <br /> We do a 3rd attempt with more classes<br /> i.cluster group=lsat7_2002 subgroup=lsat7_2002 sigfile=lsat7_2002_sig classes=15 reportfile=lsat7_2002.txt <br /> i.maxlik group=lsat7_2002 subgroup=lsat7_2002 sigfile=lsat7_2002_sig class=lsat7_2002_class3 reject=lsat7_2002_reject3<br /> d.rast.leg lsat7_2002_class3<br /> <br /> [[Image:Map_lsat7_2002_class_unsupervised_15.png|thumb|center|300px|unsupervised classification with 15 classes]]<br /> <br /> ====Supervised classification====<br /> <br /> Launch GUI for digitizer:<br /> g.gui wxpython<br /> <br /> Now digitize training areas of water, asphalt, forest, uncovered soil on RGB composite in GUI.<br /> Digitize polygons/centroids with attributes. The advantage: we know what the classes are.<br /> <br /> [[Image:Training_map_supervised.png|thumb|center|300px|NC Landsat map 2002 - training areas]]<br /> <br /> Assign also numerical ID for each class in new column<br /> v.db.select lsat7_training<br /> v.db.addcol lsat7_training col=&quot;id integer&quot;<br /> v.db.select lsat7_training<br /> v.db.update lsat7_training col=id where=&quot;name = 'water'&quot; val=1<br /> v.db.update lsat7_training col=id where=&quot;name = 'forest'&quot; val=2<br /> v.db.update lsat7_training col=id where=&quot;name = 'asphalt'&quot; val=3<br /> v.db.update lsat7_training col=id where=&quot;name = 'soil'&quot; val=4<br /> v.db.select lsat7_training<br /> <br /> Transform vector training map to raster model:<br /> g.region vect=lsat7_training align=lsat7_2002_10 -p<br /> v.to.rast in=lsat7_training out=lsat7_training use=attr col=id labelcol=name --o<br /> <br /> d.mon x0<br /> d.rast.leg lsat7_training <br /> <br /> Generate statistics from training areas<br /> i.gensigset group=lsat7_2002 subgroup=lsat7_2002 sig=lsat7_2002_smap training=lsat7_training<br /> <br /> Perform supervised classification<br /> i.smap group=lsat7_2002 subgroup=lsat7_2002 sig=lsat7_2002_smap out=smap<br /> <br /> Colorize:<br /> r.colors smap rules=- &lt;&lt; EOF<br /> <br /> 1 aqua<br /> 2 green<br /> 3 180 180 180<br /> 4 brown<br /> EOF<br /> <br /> d.rast.leg smap<br /> d.rgb b=lsat7_2002_10 g=lsat7_2002_20 r=lsat7_2002_30<br /> <br /> &lt;center&gt;<br /> {|<br /> | [[Image:Map_lsat7_2002_r1g5b7.png|thumb|center|300px|NC Landsat map 2002 - false color composite]]<br /> | [[Image:Map_lsat7_2002_class_supervised.png|thumb|center|300px|SMAP supervised classification]]<br /> |}<br /> &lt;/center&gt;<br /> <br /> Vectorize result:<br /> r.to.vect smap out=smap feat=area<br /> d.rgb b=lsat7_2002_10 g=lsat7_2002_20 r=lsat7_2002_30<br /> d.vect smap type=boundary col=red<br /> <br /> That's it :)<br /> <br /> <br /> == Further reading on classification with GRASS GIS ==<br /> * Georganos, S., Lennert, M., Grippa, T., Vanhuysse, S., Johnson, B., Wolff, E., 2018. Normalization in Unsupervised Segmentation Parameter Optimization: A Solution Based on Local Regression Trend Analysis. Remote Sensing 10, 222. https://doi.org/10.3390/rs10020222<br /> * Grippa, T., Lennert, M., Beaumont, B., Vanhuysse, S., Stephenne, N., Wolff, E., 2017. An Open-Source Semi-Automated Processing Chain for Urban Object-Based Classification. Remote Sensing 9, 358. https://doi.org/10.3390/rs9040358<br /> * Beaumont, B., Grippa, T., Lennert, M., Vanhuysse, S.G., Stephenne, N.R., Wolff, E., 2017. Toward an operational framework for fine-scale urban land-cover mapping in Wallonia using submeter remote sensing and ancillary vector data. JARS, JARSC4 11, 036011. https://doi.org/10.1117/1.JRS.11.036011<br /> * Micha Silver: [https://www.surfaces.co.il/analyzing-acacia-tree-health-in-the-arava-with-grass-gis/ Analyzing acacia tree health in the Arava with GRASS GIS]<br /> * Perrygeo: [http://www.perrygeo.net/wordpress/?p=104 Impervious surface deliniation with GRASS]<br /> * Dylan Beaudette: [http://casoilresource.lawr.ucdavis.edu/drupal/node/159 Working with Landsat Data]<br /> * Dylan Beaudette: [http://casoilresource.lawr.ucdavis.edu/drupal/node/548 Canopy Quantification via Image Classification]<br /> * [http://istgeo.ist.supsi.ch/site/node/24 Segmentazione o classificazione d'immagini con GRASS] (in italiano)<br /> * Di Palma, F.; Amato, F.; Nolè, G.; Martellozzo, F.; Murgante, B. 2016: A SMAP Supervised Classification of Landsat Images for Urban Sprawl Evaluation. ISPRS Int. J. Geo-Inf. 2016, 5, 109. PDF: http://www.mdpi.com/2220-9964/5/7/109<br /> <br /> == Further reading on OBIA with GRASS GIS ==<br /> <br /> * A complete toolchain for object-based image analysis with GRASS GIS<br /> ** Abstract: https://frab.fossgis-konferenz.de/en/foss4g-2016/public/events/1289<br /> ** Video: https://av.tib.eu/media/20409<br /> ** Software: https://github.com/tgrippa/Opensource_OBIA_processing_chain<br /> <br /> [[Category: Documentation]]<br /> [[Category: Tutorial]]<br /> [[Category: Image processing]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=Talk:GRASS_Community_Sprint_Bonn_2018&diff=25184 2018-03-25T14:06:07Z

<p>Lucadelu: </p> <hr /> <div>= Participants and Reports =<br /> <br /> == Martin Landa ==<br /> <br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=martinl&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update SVN log] overview<br /> * Show computation region extent settings, see {{trac|3519}}<br /> * wxGUI/datacatalog: zoom to first added map (sync with lmgr behaviour)<br /> * wxGUI/preferences: add new option for random colors (vector) <br /> * Read EPSG codes with PROJ v.5 fails, see {{trac|3514}} <br /> * wxGUI/datacatalog: display layer on double click <br /> * disable to_text_string() in grass.py, see {{trac|3508}} <br /> * rename r.sentinel -&gt; i.sentinel (work in progress), see {{trac|3522}} <br /> * v.random restrict wrong categories assigned, see {{trac|3524}} <br /> * Currently ​G7:v.random with restrict parameter transfers categories {{trac|3528}}<br /> * wxGUI: set up default map display properties when new display is open<br /> * libgis: improve parser UI description error reporting <br /> * v.to.rast: add support for centroids<br /> * wxGUI/dbmgr: better handling of text values in SQLBuilder <br /> * wxGUI/dbmgr: get sample/all values tuning <br /> * wxGUI: implement widget for SQL WHERE params <br /> [[File:Wxgui-sqlwhere-select.png|500px|thumb|center]]<br /> <br /> == Moritz Lennert ==<br /> <br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=mlennert&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update SVN log] overview<br /> * Committed fix for r.texture to avoid overwrite of existing output maps<br /> * Committed fix for i.segment.uspo to avoid zero division error<br /> * Worked on and discussed new startup mockup, created [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/New_Startup wiki page] for brainstorming<br /> * Use of '_' in i.zc module parameter in i.cutlines to enable parallelization of i.zc. Thanks to Pietro for making this possible in pygrass.<br /> * Some testing for [https://trac.osgeo.org/grass/ticket/3361 #3361] on slowness of v.select with GEOS. Added explanation to man page to clarify that GRASS' &quot;overlap' = GEOS 'intersects'.<br /> * Testing Ondrej' artificial neural networks modules + discussions on further improvements<br /> * Discussion of new website design<br /> * Discussion on move to github.<br /> <br /> == Markus Metz ==<br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=mmetz&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update%20SVN%20log SVN log] overview<br /> * Support of new PROJ 5 API<br /> <br /> == Markus Neteler ==<br /> <br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=neteler&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update%20SVN%20log SVN log] overview<br /> * set up [https://docs.google.com/spreadsheets/d/1BgFMiYlLosFjsVUlUCWwssoxiQB_G7gpkVFgG29gZBM/edit?usp=sharing Budget] for this community sprint<br /> * testing of {{AddonCmd|i.nightlights.intercalibration}} with DMSP-OLS data, parser fix (contributed by Anika Bettge) and HTML fixes<br /> * Web: activation of roles in http://staging.grass.osgeo.org/<br /> * svn to git migration discussions<br /> ** Following https://trac.osgeo.org/gdal/wiki/rfc71_github_migration with interest<br /> * Ticket {{trac|3527}} (i.atcorr: discrepancy in sensor band numbering in the manual)<br /> * added &quot;How to add keywords in code&quot; submitting rules for [https://trac.osgeo.org/grass/wiki/Submitting/Python#Addingdescriptionandkeywords Python] and [https://trac.osgeo.org/grass/wiki/Submitting/C#Addingdescriptionandkeywords C]<br /> * work together with Vero on https://grasswiki.osgeo.org/wiki/GRASS-Wiki/CMS_migration_plan_2018<br /> * i.atcorr: sync to trunk (updated spectral curves for various satellites; fix band order for Worldview2; addition of Sentinel-2B, improvement of numerical stability {{rev|72557}}<br /> <br /> == Veronica Andreo ==<br /> <br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=veroandreo&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update%20SVN%20log SVN log] overview<br /> * tested {{cmd|r.texture}}, see {{trac|3492}}<br /> * committed {{cmd|i.atcorr}} manual example and figure contributed by Zofie Cimburova to perform atmospheric correction on Sentinel-2 bands<br /> * performed general clean-up on i.atcorr manual page<br /> * completed [https://grasswiki.osgeo.org/wiki/SENTINEL Sentinel wiki] (kinda). Editions, corrections and more examples are welcome.<br /> * discussion about new flag and flag behavior for {{cmd|t.remove}} with Luca {{trac|3362}}<br /> * revised and tested old t.* related tickets; closed some old ones as wontfix or worksforme accordingly.<br /> * created patch for {{trac|3264}} with Luca's help<br /> * tested -h flag in {{cmd|t.info}}, see {{trac|3322}}<br /> * added example to {{cmd|t.register}} (contributed by Ondrej Pesek) + correction of typos and minor text edition<br /> * tweeted and RT from GRASS account and posted in FB GRASS GIS group<br /> * completed revision and clean-up of the [https://grasswiki.osgeo.org/wiki/Temporal_data_processing Temporal data processing] wiki<br /> * opened tickets for {{cmd|g.gui.tplot}} (after discussions with Nikos and Luca)<br /> * tested {{trac|3223}} and {{trac|3302}}<br /> * prepared small extra [https://grass.osgeo.org/sampledata/north_carolina/nc_spm_mapset_modis2015_2016_lst.zip mapset] with MODIS LST time series data (2015-2016) for NC location<br /> * created draft roadmap of priorities for the migration of the web site (work together with MarkusN): see [https://grasswiki.osgeo.org/wiki/GRASS-Wiki/CMS_migration_plan_2018 wiki]<br /> * created draft [https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures76 GRASS 7.6. New Features] page to start adding the cool stuff that will be shipped with 76<br /> * added examples for the new features implemented in {{cmd|g.gui.tplot}}<br /> * edited the GRASS GIS page at: https://www.osgeo.org/projects/grass-gis/<br /> * Spanish translations in transifex<br /> <br /> == Ondřej Pešek ==<br /> <br /> * Working on artificial neural network modules (see [https://github.com/ctu-geoforall-lab-projects/dp-pesek-2018/compare/master@%7B18/3/2018%7D...master github commits] overview)<br /> * g.gui.gmodeler: Support parameterization and GUI generation in python script; export to PyWPS script (see [https://github.com/ctu-yfsg/2017-d-grass-modeler-pywps/compare/master@%7B18/03/2018%7D...master github commits] overview)<br /> * Working on SOS modules (see [https://github.com/pesekon2/GRASS-GIS-SOS-tools/compare/master@%7B17/03/2018%7D...master github commits] overview)<br /> <br /> == Luca Delucchi ==<br /> <br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=lucadelu&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update%20SVN%20log SVN log] overview<br /> * {{cmd|g.region}} improved grow option<br /> * renamed r.modis addons to {{AddonCmd|i.modis}}<br /> * working on temporal framework open tickets<br /> * discussion about new flag and flag behavior for {{cmd|t.remove}} with Vero {{trac|3362}}<br /> * created three new modules to work with signature files {{AddonCmd|i.signature.list}}, {{AddonCmd|i.signature.copy}}, {{AddonCmd|i.signature.remove}}<br /> * worked with Markus Metz on {{cmd|i.ortho.transform}} command<br /> * fixed some bug in {{cmd|g.gui.tplot}} {{rev|72485}} {{rev|72489}}, one related to {{trac|3294}}<br /> * {{cmd|g.gui.tplot}} added capabilities to set labels for title, x and y axes {{rev|72523}} {{rev|72526}}<br /> * {{cmd|g.gui.tplot}} added capabilities to export plotted data to CSV file {{rev|72528}} {{rev|72529}} related to {{trac|3533}}<br /> * review GSoC proposals<br /> * Italian translation<br /> * added tests from other people {{rev|72530}}, {{rev|72546}}<br /> * {{cmd|r.in.srtm}} added support for SRTM SWBD {{rev|72569}} related to {{trac|3246}}, removed unzip dependencies<br /> <br /> == Nikos Alexandris ==<br /> <br /> * Discussion about GRASS GIS, HPC and distributed file systems with Markus Neteler, Soeren Gebert, Markus Metz. Respective wiki pages to be updated.<br /> * Tests related to https://trac.osgeo.org/grass/ticket/774 available at https://github.com/NikosAlexandris/test_color_space_conversions<br /> * Support for vector input in r.clip, see https://trac.osgeo.org/grass/attachment/ticket/3538/r.clip_patch_for_vector_input<br /> <br /> == Stefan Blumentrath ==<br /> <br /> * Made his first commit to trunk {{rev|72444}} and fixed {{trac|3322}}<br /> * worked on an AddOn [https://trac.osgeo.org/grass/browser/sandbox/sbl/t.rast.aggregate.update/t.rast.aggregate.update.py t.rast.aggegate.update] for updating aggregated STRDS from t.rast.aggregate (please test)<br /> * wrote a patch for improving performance of v.rast.stats that allows multiple input {{trac|3523}} (testing/feedback very welcome)<br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=sbl&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update%20SVN%20log SVN log] overview<br /> <br /> == Sören Gebbert ==<br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=huhabla&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update%20SVN%20log SVN log] overview<br /> * temporal algebra bugfixing<br /> <br /> == Radek Novotný ==<br /> <br /> * Implementation of new --exec funcionalities (--tmp-location,--no-clean), see {{trac|3537}}<br /> * Creating [https://docs.google.com/document/d/1XlxRHvtaiebVIOvlq8G6Q5FuUkFigZ8DlQbaQ-y9keQ/edit?ts=5ab51252 GSoC poroposal]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=Talk:GRASS_Community_Sprint_Bonn_2018&diff=25160 2018-03-23T16:26:53Z

<p>Lucadelu: </p> <hr /> <div>= Participants and Reports =<br /> <br /> == Martin Landa ==<br /> <br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=martinl&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update SVN log] overview<br /> * Show computation region extent settings, see {{trac|3519}}<br /> * wxGUI/datacatalog: zoom to first added map (sync with lmgr behaviour)<br /> * wxGUI/preferences: add new option for random colors (vector) <br /> * Read EPSG codes with PROJ v.5 fails, see {{trac|3514}} <br /> * wxGUI/datacatalog: display layer on double click <br /> * disable to_text_string() in grass.py, see {{trac|3508}} <br /> * rename r.sentinel -&gt; i.sentinel (work in progress), see {{trac|3522}} <br /> * v.random restrict wrong categories assigned, see {{trac|3524}} <br /> * Currently ​G7:v.random with restrict parameter transfers categories {{trac|3528}}<br /> * wxGUI: set up default map display properties when new display is open<br /> * libgis: improve parser UI description error reporting <br /> * v.to.rast: add support for centroids<br /> <br /> == Moritz Lennert ==<br /> <br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=mlennert&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update SVN log] overview<br /> * Committed fix for r.texture to avoid overwrite of existing output maps<br /> * Committed fox for i.segment.uspo to avoid zero division error<br /> * Worked on and discussed new startup mockup, created [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/New_Startup wiki page] for brainstorming<br /> * Use of '_' in i.zc module parameter in i.cutlines to enable parallelization of i.zc. Thanks to Pietro for making this possible in pygrass.<br /> * Some testing for [https://trac.osgeo.org/grass/ticket/3361 #3361] on slowness of v.select with GEOS. Added explanation to man page to clarify that GRASS' &quot;overlap' = GEOS 'intersects'.<br /> * Testing Ondrej' artificial neural networks modules + discussions on further improvements<br /> * Discussion of new website design<br /> * Discussion on move to github.<br /> <br /> == Markus Neteler ==<br /> <br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=neteler&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update%20SVN%20log SVN log] overview<br /> * set up [https://docs.google.com/spreadsheets/d/1BgFMiYlLosFjsVUlUCWwssoxiQB_G7gpkVFgG29gZBM/edit?usp=sharing Budget] for this community sprint<br /> * testing of {{AddonCmd|i.nightlights.intercalibration}} with DMSP-OLS data, parser fix (contributed by Anika Bettge) and HTML fixes<br /> * Web: activation of roles in http://staging.grass.osgeo.org/<br /> * svn to git migration discussions<br /> ** Following https://trac.osgeo.org/gdal/wiki/rfc71_github_migration with interest<br /> * Ticket {{trac|3527}} (i.atcorr: discrepancy in sensor band numbering in the manual)<br /> * added &quot;How to add keywords in code&quot; submitting rules for [https://trac.osgeo.org/grass/wiki/Submitting/Python#Addingdescriptionandkeywords Python] and [https://trac.osgeo.org/grass/wiki/Submitting/C#Addingdescriptionandkeywords C]<br /> <br /> == Veronica Andreo ==<br /> <br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=veroandreo&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update%20SVN%20log SVN log] overview<br /> * tested {{cmd|r.texture}}<br /> * committed {{cmd|i.atcorr}} manual example and figure contributed by Zofie Cimburova to perform atmospheric correction on Sentinel-2 bands<br /> * performed general clean-up on i.atcorr manual page<br /> * completed [https://grasswiki.osgeo.org/wiki/SENTINEL Sentinel wiki] (kinda). Editions, corrections and more examples are welcome.<br /> * discussion about new flag and flag behavior for {{cmd|t.remove}} with Luca {{trac|3362}}<br /> * revised and tested old t.* related tickets; closed some old ones as wontfix or worksforme accordingly.<br /> * created patch for {{trac|3264}} with Luca's help<br /> * tested -h flag in {{cmd|t.info}}, see {{trac|3322}}<br /> * added example to {{cmd|t.register}} (contributed by Ondrej Pesek) + correction of typos and minor text edition<br /> * tweeted and RT from GRASS account and posted in FB GRASS GIS group<br /> * completed revision and clean-up of the [https://grasswiki.osgeo.org/wiki/Temporal_data_processing Temporal data processing] wiki<br /> * opened tickets for {{cmd|g.gui.tplot}} (after discussions with Nikos and Luca)<br /> * tested {{trac|3223}} and {{trac|3302}}<br /> * prepared small extra [https://grass.osgeo.org/sampledata/north_carolina/nc_spm_mapset_modis2015_2016_lst.zip mapset] with MODIS LST time series data (2015-2016) for NC location<br /> * created draft roadmap of priorities for the migration of the web site: see [https://grasswiki.osgeo.org/wiki/GRASS-Wiki/CMS_migration_plan_2018 wiki]<br /> <br /> == Ondřej Pešek ==<br /> <br /> * Working on artificial neural network modules (see [https://github.com/ctu-geoforall-lab-projects/dp-pesek-2018/compare/master@%7B18/3/2018%7D...master github commits] overview)<br /> * g.gui.gmodeler: Support parameterization and GUI generation in python script; export to PyWPS script (see [https://github.com/ctu-yfsg/2017-d-grass-modeler-pywps/compare/master@%7B18/03/2018%7D...master github commits] overview)<br /> * Working on SOS modules (see [https://github.com/pesekon2/GRASS-GIS-SOS-tools/compare/master@%7B17/03/2018%7D...master github commits] overview)<br /> <br /> == Luca Delucchi ==<br /> <br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=lucadelu&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update%20SVN%20log SVN log] overview<br /> * {{cmd|g.region}} improved grow option<br /> * renamed r.modis addons to {{AddonCmd|i.modis}}<br /> * working on temporal framework open tickets<br /> * discussion about new flag and flag behavior for {{cmd|t.remove}} with Vero {{trac|3362}}<br /> * created three new modules to work with signature files {{AddonCmd|i.signature.list}}, {{AddonCmd|i.signature.copy}}, {{AddonCmd|i.signature.remove}}<br /> * worked with Markus Metz on {{cmd|i.ortho.transform}} command<br /> * fixed some bug in {{cmd|g.gui.tplot}} {{rev|72485}} {{rev|72489}}, one related to {{trac|3294}}<br /> * {{cmd|g.gui.tplot}} added capabilities to set labels for title, x and y axes {{rev|72523}} {{rev|72526}}<br /> * {{cmd|g.gui.tplot}} added capabilities to export plotted data to CSV file {{rev|72528}} {{rev|72529}} related to {{trac|3533}}<br /> * review GSoC proposals<br /> <br /> == Nikos Alexandris ==<br /> <br /> * Discussion about GRASS GIS, HPC and distributed file systems with Markus Neteler, Soeren Gebert, Markus Metz. Respective wiki pages to be updated.<br /> * Tests related to https://trac.osgeo.org/grass/ticket/774 available at https://github.com/NikosAlexandris/test_color_space_conversions<br /> <br /> <br /> == Stefan Blumentrath ==<br /> <br /> * Made his first commit to trunk {{rev|72444}} and fixed {{trac|3322}}<br /> * worked on an AddOn [https://trac.osgeo.org/grass/browser/sandbox/sbl/t.rast.aggregate.update/t.rast.aggregate.update.py t.rast.aggegate.update] for updating aggregated STRDS from t.rast.aggregate (please test)<br /> * wrote a patch for improving performace of v.rast.stats that allows multiple input {{trac|3523}} (testing/feedback very welcome)<br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=sbl&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update%20SVN%20log SVN log] overview</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=Talk:GRASS_Community_Sprint_Bonn_2018&diff=25154 2018-03-23T09:41:18Z

<p>Lucadelu: </p> <hr /> <div>= Participants and Reports =<br /> <br /> == Martin Landa ==<br /> <br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=martinl&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update SVN log] overview<br /> * Show computation region extent settings, see {{trac|3519}}<br /> * wxGUI/datacatalog: zoom to first added map (sync with lmgr behaviour)<br /> <br /> == Moritz Lennert ==<br /> <br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=mlennert&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update SVN log] overview<br /> * Committed fix for r.texture to avoid overwrite of existing output maps<br /> * Committed fox for i.segment.uspo to avoid zero division error<br /> * Worked on and discussed new startup mockup, created [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/New_Startup wiki page] for brainstorming<br /> * Use of '_' in i.zc module parameter in i.cutlines to enable parallelization of i.zc. Thanks to Pietro for making this possible in pygrass.<br /> * Some testing for [https://trac.osgeo.org/grass/ticket/3361 #3361] on slowness of v.select with GEOS. Added explanation to man page to clarify that GRASS' &quot;overlap' = GEOS 'intersects'.<br /> * Testing Ondrej' artificial neural networks modules + discussions on further improvements<br /> * Discussion of new website design<br /> * Discussion on move to github.<br /> <br /> == Markus Neteler ==<br /> <br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=neteler&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update%20SVN%20log SVN log] overview<br /> * set up [https://docs.google.com/spreadsheets/d/1BgFMiYlLosFjsVUlUCWwssoxiQB_G7gpkVFgG29gZBM/edit?usp=sharing Budget] for this community sprint<br /> * testing of {{AddonCmd|i.nightlights.intercalibration}} with DMSP-OLS data, parser fix (contributed by Anika Bettge) and HTML fixes<br /> * Web: activation of roles in http://staging.grass.osgeo.org/<br /> * svn to git migration discussions<br /> ** Following https://trac.osgeo.org/gdal/wiki/rfc71_github_migration with interest<br /> * Ticket {{trac|3527}} (i.atcorr: discrepancy in sensor band numbering in the manual)<br /> * added &quot;How to add keywords in code&quot; submitting rules for [https://trac.osgeo.org/grass/wiki/Submitting/Python#Addingdescriptionandkeywords Python] and [https://trac.osgeo.org/grass/wiki/Submitting/C#Addingdescriptionandkeywords C]<br /> <br /> == Veronica Andreo ==<br /> <br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=veroandreo&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update%20SVN%20log SVN log] overview<br /> * tested {{cmd|r.texture}}<br /> * committed {{cmd|i.atcorr}} manual example and figure contributed by Zofie Cimburova to perform atmospheric correction on Sentinel-2 bands<br /> * performed general clean-up on i.atcorr manual page<br /> * completed [https://grasswiki.osgeo.org/wiki/SENTINEL Sentinel wiki] (kinda). Editions, corrections and more examples are welcome.<br /> * discussion about new flag and flag behavior for {{cmd|t.remove}} with Luca {{trac|3362}}<br /> * revised and tested old t.* related tickets; closed some old ones as wontfix or worksforme accordingly.<br /> * created patch for {{trac|3264}} with Luca's help<br /> * tested -h flag in {{cmd|t.info}}, see {{trac|3322}}<br /> * added example to {{cmd|t.register}} (contributed by Ondrej Pesek) + correction of typos and minor text edition<br /> * tweeted and RT from GRASS account and posted in FB GRASS GIS group<br /> * completed revision and clean-up of the [https://grasswiki.osgeo.org/wiki/Temporal_data_processing Temporal data processing] wiki<br /> * opened tickets for {{cmd|g.gui.tplot}} (after discussions with Nikos and Luca)<br /> * tested {{trac|3223}} and {{trac|3302}}<br /> * created draft roadmap of priorities for the migration of the web site: see [https://grasswiki.osgeo.org/wiki/GRASS-Wiki/CMS_migration_plan_2018 wiki]<br /> <br /> == Ondřej Pešek ==<br /> <br /> * Working on artificial neural network modules (see [https://github.com/ctu-geoforall-lab-projects/dp-pesek-2018/compare/master@%7B18/3/2018%7D...master github commits] overview)<br /> * g.gui.gmodeler: Support parameterization and GUI generation in python script; export to PyWPS script (see [https://github.com/ctu-yfsg/2017-d-grass-modeler-pywps/compare/master@%7B18/03/2018%7D...master github commits] overview)<br /> * Working on SOS modules (see [https://github.com/pesekon2/GRASS-GIS-SOS-tools/compare/master@%7B17/03/2018%7D...master github commits] overview)<br /> <br /> == Luca Delucchi ==<br /> <br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=lucadelu&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update%20SVN%20log SVN log] overview<br /> * {{cmd|g.region}} improved grow option<br /> * renamed r.modis addons to {{AddonCmd|i.modis}}<br /> * working on temporal framework open tickets<br /> * discussion about new flag and flag behavior for {{cmd|t.remove}} with Vero {{trac|3362}}<br /> * created three new modules to work with signature files {{AddonCmd|i.signature.list}}, {{AddonCmd|i.signature.copy}}, {{AddonCmd|i.signature.remove}}<br /> * worked with Markus Metz on {{cmd|i.ortho.transform}} command<br /> * fixed some bug in {{cmd|g.gui.tplot}} {{rev|72485}} {{rev|72489}}, one related to {{trac|3294}}<br /> * review GSoC proposals<br /> <br /> == Nikos Alexandris ==<br /> <br /> * Discussion about GRASS GIS, HPC and distributed file systems with Markus Neteler, Soeren Gebert, Markus Metz. Respective wiki pages to be updated.<br /> * Tests related to https://trac.osgeo.org/grass/ticket/774 available at https://github.com/NikosAlexandris/test_color_space_conversions</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=Talk:GRASS_Community_Sprint_Bonn_2018&diff=25132 2018-03-20T16:11:07Z

<p>Lucadelu: </p> <hr /> <div>= Participants and Reports =<br /> <br /> == Martin Landa ==<br /> <br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=martinl&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update SVN log] overview<br /> * Show computation region extent settings, see {{trac|3519}}<br /> * wxGUI/datacatalog: zoom to first added map (sync with lmgr behaviour)<br /> <br /> == Moritz Lennert ==<br /> <br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=mlennert&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update SVN log] overview<br /> * Committed fix for r.texture to avoid overwrite of existing output maps<br /> * Committed fox for i.segment.uspo to avoid zero division error<br /> * Worked on and discussed new startup mockup, created [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/New_Startup wiki page] for brainstorming<br /> * Use of '_' in i.zc module parameter in i.cutlines to enable parallelization of i.zc. Thanks to Pietro for making this possible in pygrass.<br /> * Some testing for [https://trac.osgeo.org/grass/ticket/3361 #3361] on slowness of v.select with GEOS. Added explanation to man page to clarify that GRASS' &quot;overlap' = GEOS 'intersects'.<br /> * Testing Ondrej' artificial neural networks modules + discussions on further improvements<br /> * Discussion of new website design<br /> * Discussion on move to github.<br /> <br /> == Markus Neteler ==<br /> <br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=neteler&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update%20SVN%20log SVN log] overview<br /> * set up [https://docs.google.com/spreadsheets/d/1BgFMiYlLosFjsVUlUCWwssoxiQB_G7gpkVFgG29gZBM/edit?usp=sharing Budget] for this community sprint<br /> * testing of {{AddonCmd|i.nightlights.intercalibration}} with DMSP-OLS data, parser fix (contributed by Anika Bettge) and HTML fixes<br /> * Web: activation of roles in http://staging.grass.osgeo.org/<br /> * svn to git migration discussions<br /> <br /> == Veronica Andreo ==<br /> <br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=veroandreo&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update%20SVN%20log SVN log] overview<br /> * Tested {{cmd|r.texture}}<br /> * Commited {{cmd|i.atcorr}} manual example and figure contributed by Zofie Cimburova to perform atmospheric correction on Sentinel-2 bands<br /> * Performed general clean-up on i.atcorr manual page<br /> * [https://grasswiki.osgeo.org/wiki/SENTINEL Sentinel wiki] (kinda) completed. Editions, corrections and more examples are welcome.<br /> * revision of t.* related tickets and closed some old ones as wontfix or worksforme accordingly<br /> * patch for {{trac|3264}} with Luca's help<br /> * discussion about new flag and flag behavior for {{cmd|t.remove}} with Luca {{trac|3362}}<br /> <br /> == Ondřej Pešek ==<br /> <br /> * Working on artificial neural network modules (see [https://github.com/ctu-geoforall-lab-projects/dp-pesek-2018/compare/master@%7B18/3/2018%7D...master github commits] overview)<br /> * g.gui.gmodeler: Support parameterization and GUI generation in python script; export to PyWPS script (see [https://github.com/ctu-yfsg/2017-d-grass-modeler-pywps/compare/master@%7B18/03/2018%7D...master github commits] overview)<br /> * Working on SOS modules (see [https://github.com/pesekon2/GRASS-GIS-SOS-tools/compare/master@%7B17/03/2018%7D...master github commits] overview)<br /> <br /> == Luca Delucchi ==<br /> <br /> * [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&amp;daysback=7&amp;authors=lucadelu&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;update=Update%20SVN%20log SVN log] overview<br /> * {{cmd|g.region}} improved grow option<br /> * renamed r.modis addons to {{AddonCmd|i.modis}}<br /> * working on temporal framework open tickets<br /> * discussion about new flag and flag behavior for {{cmd|t.remove}} with Vero {{trac|3362}}</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GCI_Ideas_2017&diff=24998 2018-01-18T16:37:18Z

<p>Lucadelu: /* Add testsuites to different modules */ added more GCI results</p> <hr /> <div>&lt;center&gt;<br /> [[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]]&lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:GCI-logo.jpg|300px|link=https://developers.google.com/open-source/gci/]] &lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]<br /> &lt;/center&gt;<br /> <br /> = About =<br /> <br /> This is the GRASS page for [https://wiki.osgeo.org/wiki/Google_Code_In_2017 Google Code-In] 2017. Here we will list task ideas and other information related to the GRASS GCI projects.<br /> <br /> == What is Google Code-In? ==<br /> <br /> Pre-university students ages 13 to 17 are invited to take part in Google Code-in: Our global, online, contest introducing teenagers to the world of open source. With a wide variety of bite-sized tasks, it’s easy for beginners to jump in and get started no matter what skills they have. Mentors from our participating organizations lend a helping hand as participants learn what it’s like to work on an open source project. For more details, see [https://developers.google.com/open-source/gci/ Google Code-In] main page. <br /> <br /> == How does it work? ==<br /> <br /> # Students search for a '''task''' that interests them and claim it. They have at least ''three days and up to five'' to complete it.<br /> # The student works on the task, getting guidance from mentors, if needed.<br /> # Once the student has finished, he/she submits the work for review through the contest website.<br /> # Mentors from the organization evaluate the work, provide feedback, and if it's complete, accept it! Otherwise, specific feedback is provided, and the student goes back to step #2!<br /> # Go to step #1 and repeat!<br /> <br /> More details can be found at: [https://developers.google.com/open-source/gci/how-it-works https://developers.google.com/open-source/gci/how-it-works]<br /> <br /> == Tasks ==<br /> <br /> The organizations should create a large list of short (3-5 hour) tasks for students to work on. Tasks are categorized as: Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface. Some examples of tasks of different categories can be found [https://developers.google.com/open-source/gci/resources/example-tasks here].<br /> <br /> == Details about the tasks and lessons learnt ==<br /> <br /> * Translations are not allowed by Google Code In as tasks.<br /> <br /> * A strategic plan is needed to generate a pool of tasks doable in 3-5 hours (from beginner to advanced tasks); '''from ~50 up to ~100 tasks!!'''<br /> <br /> * A '''large mentor pool''' that can tackle evaluations of about ~ 100 tasks!! Importantly, the revision of tasks should be rather quick, since the students should complete as many tasks as possible to win the contest.<br /> <br /> = Available mentors =<br /> List of available mentors to follow the tasks<br /> <br /> * [[User:Veroandreo|Veronica Andreo]]<br /> * [[User:Lucadelu|Luca Delucchi]]<br /> * ...<br /> <br /> Note: To sign up as a mentor, write an email to: gsoc-admin@osgeo.org.<br /> <br /> = Results =<br /> <br /> == Install GRASS GIS on your computer and download North Carolina dataset ==<br /> * 38 students completed the task successfully, 48 abandoned and 27 ran out of time.<br /> <br /> == Compile GRASS GIS ==<br /> * 5 students completed the task successfully and 3 other abandoned.<br /> <br /> == Add examples and/or screenshots to different manual pages ==<br /> * added examples and screenshots to {{cmd|i.albedo}} manual: {{rev|71903}}, {{rev|71904}}, {{rev|71904}}<br /> * added examples to {{cmd|r.support}} manual: {{rev|71906}}, {{rev|71907}}, {{rev|71908}}<br /> * added screenshot to {{cmd|d.rgb}} manual: {{rev|71924}}, {{rev|71925}}, {{rev|71926}}<br /> * added screenshot to {{cmd|d.mon}} manual: {{rev|71927}}, {{rev|71928}}, {{rev|71929}}<br /> * added screenshots to {{cmd|d.grid}} manual: {{rev|71930}}, {{rev|71931}}, {{rev|71932}}<br /> * added screenshots to {{cmd|d.rast}} manual: {{rev|71947}}, {{rev|71948}}, {{rev|71949}}<br /> * added examples and screenshots to {{cmd|d.histogram}} manual: {{rev|71956}}, {{rev|71957}}, {{rev|71958}}<br /> * added example and screenshot to {{cmd|r.topidx}} manual: {{rev|71959}}, {{rev|71960}}, {{rev|71961}}<br /> * added examples to {{cmd|g.message}} manual: {{rev|72001}}, {{rev|72002}}, {{rev|72003}} <br /> * added examples to {{cmd|g.mapset}} manual: {{rev|72004}}, {{rev|72005}}, {{rev|72006}}<br /> * added examples and screenshots to {{cmd|v.perturb}} manual: {{rev|72044}}, {{rev|72045}}, {{rev|72046}}<br /> * added screenshots to {{cmd|d.text}} manual: {{rev|72067}}<br /> <br /> == Add testsuites to different modules ==<br /> * added testsuite to {{cmd|r.report}}: {{rev|71997}} (done also by Jerry Huang)<br /> * added testsuite to {{cmd|r.info}}: {{rev|72050}} (done also by Jerry Huang)<br /> * added testsuite to {{cmd|v.univar}}: {{rev|72049}}<br /> * added testsuite to {{cmd|r.in.ascii}}: {{rev|72060}}<br /> * added testsuite to {{cmd|i.vi}}: {{rev|72064}}<br /> * added testsuite to {{cmd|r.texture}}: {{rev|72070}}<br /> * added testsuite to {{cmd|v.extract}}: {{rev|72074}}<br /> * added testsuite to {{cmd|v.select}}: {{rev|72077}}<br /> * added testsuite to {{cmd|v.reclass}}: {{rev|72078}}<br /> * added testsuite to {{cmd|r.to.vect}}: {{rev|72096}}<br /> * added testsuite to {{cmd|v.vect.stats}}: {{rev|72097}}<br /> <br /> == Designs ==<br /> <br /> ''Note'': Students that have failed to submit a proper SVG won't get their tasks uploaded in SVN<br /> <br /> === Splash screen for GRASS GIS GUI start-up ===<br /> * {{rev|71941}}: splash screen by tfang<br /> * {{rev|72024}}: splash screen by Eric1234<br /> * {{rev|72047}}: splash screen by Raghu Ranganathan<br /> * {{rev|72048}}: splash screen by Tom Davies<br /> * {{rev|72065}}: splash screen by Abhishek Bana<br /> <br /> === T-shirt for 2018 Code Sprint ===<br /> * {{rev|72000}}: 2 t-shirt designs by Eric1234 <br /> * {{rev|72025}}: t-shirt design by Ilaya Suriya<br /> * {{rev|72052}}: t-shirt design by Tom Davies<br /> * {{rev|72053}}: t-shirt design by Mihika Krishna<br /> * {{rev|72079}}: t-shirt design by Janith Chathuranga Yapa<br /> * t-shirt design by Lahari. C. Krishna<br /> * t-shirt design by Abhishek Bana<br /> * t-shirt design by Sarthak Gupta<br /> * t-shirt design by Shaan Sachdeva<br /> * t-shirt design by Harini S Chopperla<br /> <br /> === Banner for location wizard ===<br /> * {{rev|72061}}: banner by Hatim Aliasger<br /> <br /> == Blog entry about GRASS GIS ==<br /> * {{rev|72056}}: blog entry by Shreya Sandurkar<br /> * blog entry by Taylor Fang: https://grass.osgeo.org/news/72/15/GRASS-GIS-as-described-by-a-Google-Code-In-student/<br /> <br /> == Videos ==<br /> === How to create a location ===<br /> * https://www.youtube.com/watch?v=trvy0B0Qz78 (by Sunveer Singh)<br /> * https://youtu.be/1BBGQZTkBb0 (by Eric1234)<br /> * https://www.youtube.com/watch?v=yHPdiQFfMpE (by Shailesh Kadam)<br /> <br /> === Give a talk about GRASS GIS ===<br /> * by Anan Afrida<br /> <br /> &lt;!-- Please, edit this page and add further info --&gt;<br /> <br /> [[Category: Development]]<br /> [[Category: Community]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GCI_Ideas_2017&diff=24995 2018-01-18T16:27:22Z

<p>Lucadelu: </p> <hr /> <div>&lt;center&gt;<br /> [[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]]&lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:GCI-logo.jpg|300px|link=https://developers.google.com/open-source/gci/]] &lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]<br /> &lt;/center&gt;<br /> <br /> = About =<br /> <br /> This is the GRASS page for [https://wiki.osgeo.org/wiki/Google_Code_In_2017 Google Code-In] 2017. Here we will list task ideas and other information related to the GRASS GCI projects.<br /> <br /> == What is Google Code-In? ==<br /> <br /> Pre-university students ages 13 to 17 are invited to take part in Google Code-in: Our global, online, contest introducing teenagers to the world of open source. With a wide variety of bite-sized tasks, it’s easy for beginners to jump in and get started no matter what skills they have. Mentors from our participating organizations lend a helping hand as participants learn what it’s like to work on an open source project. For more details, see [https://developers.google.com/open-source/gci/ Google Code-In] main page. <br /> <br /> == How does it work? ==<br /> <br /> # Students search for a '''task''' that interests them and claim it. They have at least ''three days and up to five'' to complete it.<br /> # The student works on the task, getting guidance from mentors, if needed.<br /> # Once the student has finished, he/she submits the work for review through the contest website.<br /> # Mentors from the organization evaluate the work, provide feedback, and if it's complete, accept it! Otherwise, specific feedback is provided, and the student goes back to step #2!<br /> # Go to step #1 and repeat!<br /> <br /> More details can be found at: [https://developers.google.com/open-source/gci/how-it-works https://developers.google.com/open-source/gci/how-it-works]<br /> <br /> == Tasks ==<br /> <br /> The organizations should create a large list of short (3-5 hour) tasks for students to work on. Tasks are categorized as: Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface. Some examples of tasks of different categories can be found [https://developers.google.com/open-source/gci/resources/example-tasks here].<br /> <br /> == Details about the tasks and lessons learnt ==<br /> <br /> * Translations are not allowed by Google Code In as tasks.<br /> <br /> * A strategic plan is needed to generate a pool of tasks doable in 3-5 hours (from beginner to advanced tasks); '''from ~50 up to ~100 tasks!!'''<br /> <br /> * A '''large mentor pool''' that can tackle evaluations of about ~ 100 tasks!! Importantly, the revision of tasks should be rather quick, since the students should complete as many tasks as possible to win the contest.<br /> <br /> = Available mentors =<br /> List of available mentors to follow the tasks<br /> <br /> * [[User:Veroandreo|Veronica Andreo]]<br /> * [[User:Lucadelu|Luca Delucchi]]<br /> * ...<br /> <br /> Note: To sign up as a mentor, write an email to: gsoc-admin@osgeo.org.<br /> <br /> = Results =<br /> <br /> == Install GRASS GIS on your computer and download North Carolina dataset ==<br /> * 37 students completed the task successfully, 48 abandoned and 23 ran out of time.<br /> <br /> == Compile GRASS GIS ==<br /> * 5 students completed the task successfully and 3 other abandoned.<br /> <br /> == Add examples and/or screenshots to different manual pages ==<br /> * added examples and screenshots to {{cmd|i.albedo}} manual: {{rev|71903}}, {{rev|71904}}, {{rev|71904}}<br /> * added examples to {{cmd|r.support}} manual: {{rev|71906}}, {{rev|71907}}, {{rev|71908}}<br /> * added screenshot to {{cmd|d.rgb}} manual: {{rev|71924}}, {{rev|71925}}, {{rev|71926}}<br /> * added screenshot to {{cmd|d.mon}} manual: {{rev|71927}}, {{rev|71928}}, {{rev|71929}}<br /> * added screenshots to {{cmd|d.grid}} manual: {{rev|71930}}, {{rev|71931}}, {{rev|71932}}<br /> * added screenshots to {{cmd|d.rast}} manual: {{rev|71947}}, {{rev|71948}}, {{rev|71949}}<br /> * added examples and screenshots to {{cmd|d.histogram}} manual: {{rev|71956}}, {{rev|71957}}, {{rev|71958}}<br /> * added example and screenshot to {{cmd|r.topidx}} manual: {{rev|71959}}, {{rev|71960}}, {{rev|71961}}<br /> * added examples to {{cmd|g.message}} manual: {{rev|72001}}, {{rev|72002}}, {{rev|72003}} <br /> * added examples to {{cmd|g.mapset}} manual: {{rev|72004}}, {{rev|72005}}, {{rev|72006}}<br /> * added examples and screenshots to {{cmd|v.perturb}} manual: {{rev|72044}}, {{rev|72045}}, {{rev|72046}}<br /> * added screenshots to {{cmd|d.text}} manual: {{rev|72067}}<br /> <br /> == Add testsuites to different modules ==<br /> * added testsuite to {{cmd|r.report}}: {{rev|71997}}<br /> * added testsuite to {{cmd|r.info}}: {{rev|72050}}<br /> * added testsuite to {{cmd|v.univar}}: {{rev|72049}}<br /> * added testsuite to {{cmd|r.in.ascii}}: {{rev|72060}}<br /> * added testsuite to {{cmd|i.vi}}: {{rev|72064}}<br /> * added testsuite to {{cmd|r.texture}}: {{rev|72070}}<br /> * added testsuite to {{cmd|v.extract}}: {{rev|72074}}<br /> * added testsuite to {{cmd|v.select}}: {{rev|72077}}<br /> * added testsuite to {{cmd|v.reclass}}: {{rev|72078}}<br /> * added testsuite to {{cmd|r.to.vect}}: {{rev|72096}}<br /> * added testsuite to {{cmd|v.vect.stats}}: {{rev|72097}}<br /> <br /> == Designs ==<br /> <br /> ''Note'': Students that have failed to submit a proper SVG won't get their tasks uploaded in SVN<br /> <br /> === Splash screen for GRASS GIS GUI start-up ===<br /> * {{rev|71941}}: splash screen by tfang<br /> * {{rev|72024}}: splash screen by Eric1234<br /> * {{rev|72047}}: splash screen by Raghu Ranganathan<br /> * {{rev|72048}}: splash screen by Tom Davies<br /> * {{rev|72065}}: splash screen by Abhishek Bana<br /> <br /> === T-shirt for 2018 Code Sprint ===<br /> * {{rev|72000}}: 2 t-shirt designs by Eric1234 <br /> * {{rev|72025}}: t-shirt design by Ilaya Suriya<br /> * {{rev|72052}}: t-shirt design by Tom Davies<br /> * {{rev|72053}}: t-shirt design by Mihika Krishna<br /> * {{rev|72079}}: t-shirt design by Janith Chathuranga Yapa<br /> * t-shirt design by Lahari. C. Krishna<br /> * t-shirt design by Abhishek Bana<br /> * t-shirt design by Sarthak Gupta<br /> * t-shirt design by Shaan Sachdeva<br /> * t-shirt design by Harini S Chopperla<br /> <br /> === Banner for location wizard ===<br /> * {{rev|72061}}: banner by Hatim Aliasger<br /> <br /> == Blog entry about GRASS GIS ==<br /> * {{rev|72056}}: blog entry by Shreya Sandurkar<br /> * blog entry by Taylor Fang: https://grass.osgeo.org/news/72/15/GRASS-GIS-as-described-by-a-Google-Code-In-student/<br /> <br /> == Videos ==<br /> === How to create a location ===<br /> * https://www.youtube.com/watch?v=trvy0B0Qz78 (by Sunveer Singh)<br /> * https://youtu.be/1BBGQZTkBb0 (by Eric1234)<br /> * https://www.youtube.com/watch?v=yHPdiQFfMpE (by Shailesh Kadam)<br /> <br /> === Give a talk about GRASS GIS ===<br /> * by Anan Afrida<br /> <br /> &lt;!-- Please, edit this page and add further info --&gt;<br /> <br /> [[Category: Development]]<br /> [[Category: Community]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GCI_Ideas_2017&diff=24987 2018-01-15T15:35:42Z

<p>Lucadelu: </p> <hr /> <div>&lt;center&gt;<br /> [[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]]&lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:GCI-logo.jpg|300px|link=https://developers.google.com/open-source/gci/]] &lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]<br /> &lt;/center&gt;<br /> <br /> = About =<br /> <br /> This is the GRASS page for [https://wiki.osgeo.org/wiki/Google_Code_In_2017 Google Code-In] 2017. Here we will list task ideas and other information related to the GRASS GCI projects.<br /> <br /> == What is Google Code-In? ==<br /> <br /> Pre-university students ages 13 to 17 are invited to take part in Google Code-in: Our global, online, contest introducing teenagers to the world of open source. With a wide variety of bite-sized tasks, it’s easy for beginners to jump in and get started no matter what skills they have. Mentors from our participating organizations lend a helping hand as participants learn what it’s like to work on an open source project. For more details, see [https://developers.google.com/open-source/gci/ Google Code-In] main page. <br /> <br /> == How does it work? ==<br /> <br /> # Students search for a '''task''' that interests them and claim it. They have at least ''three days and up to five'' to complete it.<br /> # The student works on the task, getting guidance from mentors, if needed.<br /> # Once the student has finished, he/she submits the work for review through the contest website.<br /> # Mentors from the organization evaluate the work, provide feedback, and if it's complete, accept it! Otherwise, specific feedback is provided, and the student goes back to step #2!<br /> # Go to step #1 and repeat!<br /> <br /> More details can be found at: [https://developers.google.com/open-source/gci/how-it-works https://developers.google.com/open-source/gci/how-it-works]<br /> <br /> == Tasks ==<br /> <br /> The organizations should create a large list of short (3-5 hour) tasks for students to work on. Tasks are categorized as: Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface. Some examples of tasks of different categories can be found [https://developers.google.com/open-source/gci/resources/example-tasks here].<br /> <br /> == Details about the tasks and lessons learnt ==<br /> <br /> * Translations are not allowed by Google Code In as tasks.<br /> <br /> * A strategic plan is needed to generate a pool of tasks doable in 3-5 hours (from beginner to advanced tasks); '''from ~50 up to ~100 tasks!!'''<br /> <br /> * A '''large mentor pool''' that can tackle evaluations of about ~ 100 tasks!! Importantly, the revision of tasks should be rather quick, since the students should complete as many tasks as possible to win the contest.<br /> <br /> = Available mentors =<br /> List of available mentors to follow the tasks<br /> <br /> * [[User:Veroandreo|Veronica Andreo]]<br /> * [[User:Lucadelu|Luca Delucchi]]<br /> * ...<br /> <br /> Note: To sign up as a mentor, write an email to: gsoc-admin@osgeo.org.<br /> <br /> = Results =<br /> <br /> == Add examples and/or screenshots to different manual pages ==<br /> * added examples and screenshots to {{cmd|i.albedo}} manual: {{rev|71903}}, {{rev|71904}}, {{rev|71904}}<br /> * added examples to {{cmd|r.support}} manual: {{rev|71906}}, {{rev|71907}}, {{rev|71908}}<br /> * added screenshot to {{cmd|d.rgb}} manual: {{rev|71924}}, {{rev|71925}}, {{rev|71926}}<br /> * added screenshot to {{cmd|d.mon}} manual: {{rev|71927}}, {{rev|71928}}, {{rev|71929}}<br /> * added screenshots to {{cmd|d.grid}} manual: {{rev|71930}}, {{rev|71931}}, {{rev|71932}}<br /> * added screenshots to {{cmd|d.rast}} manual: {{rev|71947}}, {{rev|71948}}, {{rev|71949}}<br /> * added examples and screenshots to {{cmd|d.histogram}} manual: {{rev|71956}}, {{rev|71957}}, {{rev|71958}}<br /> * added example and screenshot to {{cmd|r.topidx}} manual: {{rev|71959}}, {{rev|71960}}, {{rev|71961}}<br /> * added examples to {{cmd|g.message}} manual: {{rev|72001}}, {{rev|72002}}, {{rev|72003}} <br /> * added examples to {{cmd|g.mapset}} manual: {{rev|72004}}, {{rev|72005}}, {{rev|72006}}<br /> * added examples and screenshots to {{cmd|v.perturb}} manual: {{rev|72044}}, {{rev|72045}}, {{rev|72046}}<br /> * added screenshots to {{cmd|d.text}} manual: {{rev|72067}}<br /> <br /> == Add testsuites to different modules ==<br /> * added testsuite to {{cmd|r.report}}: {{rev|71997}}<br /> * added testsuite to {{cmd|r.info}}: {{rev|72050}}<br /> * added testsuite to {{cmd|v.univar}}: {{rev|72049}}<br /> * added testsuite to {{cmd|r.in.ascii}}: {{rev|72060}}<br /> * added testsuite to {{cmd|i.vi}}: {{rev|72064}}<br /> * added testsuite to {{cmd|r.texture}}: {{rev|72070}}<br /> * added testsuite to {{cmd|v.extract}}: {{rev|72074}}<br /> * added testsuite to {{cmd|v.select}}: {{rev|72077}}<br /> * added testsuite to {{cmd|v.reclass}}: {{rev|72078}}<br /> <br /> == Install GRASS GIS on your computer and download North Carolina dataset ==<br /> * 36 students completed the task successfully, 48 abandoned and 22 ran out of time.<br /> <br /> == Compile GRASS GIS ==<br /> * 5 students completed the task successfully and 2 other abandoned.<br /> <br /> == Designs ==<br /> <br /> ''Note'': Students that have failed to submit a proper SVG won't get their tasks uploaded in SVN<br /> <br /> === Splash screen for GRASS GIS GUI start-up ===<br /> * {{rev|71941}}: splash screen by tfang<br /> * {{rev|72024}}: splash screen by Eric1234<br /> * {{rev|72047}}: splash screen by Raghu Ranganathan<br /> * {{rev|72048}}: splash screen by Tom Davies<br /> * {{rev|72065}}: splash screen by Abhishek Bana<br /> <br /> === T-shirt for 2018 Code Sprint ===<br /> * {{rev|72000}}: 2 t-shirt designs by Eric1234 <br /> * {{rev|72025}}: t-shirt design by Ilaya Suriya<br /> * {{rev|72052}}: t-shirt design by Tom Davies<br /> * {{rev|72053}}: t-shirt design by Mihika Krishna<br /> * {{rev|72079}}: t-shirt design by Janith Chathuranga Yapa<br /> * t-shirt design by Lahari. C. Krishna<br /> * t-shirt design by Abhishek Bana<br /> * t-shirt design by Sarthak Gupta<br /> * t-shirt design by Shaan Sachdeva<br /> <br /> === Banner for location wizard ===<br /> * {{rev|72061}}: banner by Hatim Aliasger<br /> <br /> == Blog entry about GRASS GIS ==<br /> * {{rev|72056}}: blog entry by Shreya Sandurkar<br /> <br /> == Videos ==<br /> === How to create a location ===<br /> * https://www.youtube.com/watch?v=trvy0B0Qz78 (by Sunveer Singh)<br /> * https://youtu.be/1BBGQZTkBb0 (by Eric1234)<br /> * https://www.youtube.com/watch?v=yHPdiQFfMpE (by Shailesh Kadam)<br /> <br /> === Give a talk about GRASS GIS ===<br /> * by Anan Afrida<br /> <br /> &lt;!-- Please, edit this page and add further info --&gt;<br /> <br /> [[Category: Development]]<br /> [[Category: Community]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GCI_Ideas_2017&diff=24986 2018-01-15T13:38:29Z

<p>Lucadelu: /* How to create a location */ added new location video from GCI 2017</p> <hr /> <div>&lt;center&gt;<br /> [[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]]&lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:GCI-logo.jpg|300px|link=https://developers.google.com/open-source/gci/]] &lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]<br /> &lt;/center&gt;<br /> <br /> = About =<br /> <br /> This is the GRASS page for [https://wiki.osgeo.org/wiki/Google_Code_In_2017 Google Code-In] 2017. Here we will list task ideas and other information related to the GRASS GCI projects.<br /> <br /> == What is Google Code-In? ==<br /> <br /> Pre-university students ages 13 to 17 are invited to take part in Google Code-in: Our global, online, contest introducing teenagers to the world of open source. With a wide variety of bite-sized tasks, it’s easy for beginners to jump in and get started no matter what skills they have. Mentors from our participating organizations lend a helping hand as participants learn what it’s like to work on an open source project. For more details, see [https://developers.google.com/open-source/gci/ Google Code-In] main page. <br /> <br /> == How does it work? ==<br /> <br /> # Students search for a '''task''' that interests them and claim it. They have at least ''three days and up to five'' to complete it.<br /> # The student works on the task, getting guidance from mentors, if needed.<br /> # Once the student has finished, he/she submits the work for review through the contest website.<br /> # Mentors from the organization evaluate the work, provide feedback, and if it's complete, accept it! Otherwise, specific feedback is provided, and the student goes back to step #2!<br /> # Go to step #1 and repeat!<br /> <br /> More details can be found at: [https://developers.google.com/open-source/gci/how-it-works https://developers.google.com/open-source/gci/how-it-works]<br /> <br /> == Tasks ==<br /> <br /> The organizations should create a large list of short (3-5 hour) tasks for students to work on. Tasks are categorized as: Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface. Some examples of tasks of different categories can be found [https://developers.google.com/open-source/gci/resources/example-tasks here].<br /> <br /> == Details about the tasks and lessons learnt ==<br /> <br /> * Translations are not allowed by Google Code In as tasks.<br /> <br /> * A strategic plan is needed to generate a pool of tasks doable in 3-5 hours (from beginner to advanced tasks); '''from ~50 up to ~100 tasks!!'''<br /> <br /> * A '''large mentor pool''' that can tackle evaluations of about ~ 100 tasks!! Importantly, the revision of tasks should be rather quick, since the students should complete as many tasks as possible to win the contest.<br /> <br /> = Available mentors =<br /> List of available mentors to follow the tasks<br /> <br /> * [[User:Veroandreo|Veronica Andreo]]<br /> * [[User:Lucadelu|Luca Delucchi]]<br /> * ...<br /> <br /> Note: To sign up as a mentor, write an email to: gsoc-admin@osgeo.org.<br /> <br /> = Results =<br /> <br /> == Add examples and/or screenshots to different manual pages ==<br /> * added examples and screenshots to {{cmd|i.albedo}} manual: {{rev|71903}}, {{rev|71904}}, {{rev|71904}}<br /> * added examples to {{cmd|r.support}} manual: {{rev|71906}}, {{rev|71907}}, {{rev|71908}}<br /> * added screenshot to {{cmd|d.rgb}} manual: {{rev|71924}}, {{rev|71925}}, {{rev|71926}}<br /> * added screenshot to {{cmd|d.mon}} manual: {{rev|71927}}, {{rev|71928}}, {{rev|71929}}<br /> * added screenshots to {{cmd|d.grid}} manual: {{rev|71930}}, {{rev|71931}}, {{rev|71932}}<br /> * added screenshots to {{cmd|d.rast}} manual: {{rev|71947}}, {{rev|71948}}, {{rev|71949}}<br /> * added examples and screenshots to {{cmd|d.histogram}} manual: {{rev|71956}}, {{rev|71957}}, {{rev|71958}}<br /> * added example and screenshot to {{cmd|r.topidx}} manual: {{rev|71959}}, {{rev|71960}}, {{rev|71961}}<br /> * added examples to {{cmd|g.message}} manual: {{rev|72001}}, {{rev|72002}}, {{rev|72003}} <br /> * added examples to {{cmd|g.mapset}} manual: {{rev|72004}}, {{rev|72005}}, {{rev|72006}}<br /> * added examples and screenshots to {{cmd|v.perturb}} manual: {{rev|72044}}, {{rev|72045}}, {{rev|72046}}<br /> * added screenshots to {{cmd|d.text}} manual: {{rev|72067}}<br /> <br /> == Add testsuites to different modules ==<br /> * added testsuite to {{cmd|r.report}}: {{rev|71997}}<br /> * added testsuite to {{cmd|r.info}}: {{rev|72050}}<br /> * added testsuite to {{cmd|v.univar}}: {{rev|72049}}<br /> * added testsuite to {{cmd|r.in.ascii}}: {{rev|72060}}<br /> * added testsuite to {{cmd|i.vi}}: {{rev|72064}}<br /> * added testsuite to {{cmd|r.texture}}: {{rev|72070}}<br /> <br /> == Install GRASS GIS on your computer and download North Carolina dataset ==<br /> * 36 students completed the task successfully, 48 abandoned and 22 ran out of time.<br /> <br /> == Compile GRASS GIS ==<br /> * 5 students completed the task successfully and 2 other abandoned.<br /> <br /> == Designs ==<br /> <br /> ''Note'': Students that have failed to submit a proper SVG won't get their tasks uploaded in SVN<br /> <br /> === Splash screen for GRASS GIS GUI start-up ===<br /> * {{rev|71941}}: splash screen by tfang<br /> * {{rev|72024}}: splash screen by Eric1234<br /> * {{rev|72047}}: splash screen by Raghu Ranganathan<br /> * {{rev|72048}}: splash screen by Tom Davies<br /> * {{rev|72065}}: splash screen by Abhishek Bana<br /> <br /> === T-shirt for 2018 Code Sprint ===<br /> * {{rev|72000}}: 2 t-shirt designs by Eric1234 <br /> * {{rev|72025}}: t-shirt design by Ilaya Suriya<br /> * {{rev|72052}}: t-shirt design by Tom Davies<br /> * {{rev|72053}}: t-shirt design by Mihika Krishna<br /> * t-shirt design by Lahari. C. Krishna<br /> * t-shirt design by Abhishek Bana<br /> * t-shirt design by Sarthak Gupta<br /> * t-shirt design by Shaan Sachdeva<br /> <br /> === Banner for location wizard ===<br /> * {{rev|72061}}: banner by Hatim Aliasger<br /> <br /> == Blog entry about GRASS GIS ==<br /> * {{rev|72056}}: blog entry by Shreya Sandurkar<br /> <br /> == Videos ==<br /> === How to create a location ===<br /> * https://www.youtube.com/watch?v=trvy0B0Qz78 (by Sunveer Singh)<br /> * https://youtu.be/1BBGQZTkBb0 (by Eric1234)<br /> * https://www.youtube.com/watch?v=yHPdiQFfMpE (by Shailesh Kadam)<br /> <br /> === Give a talk about GRASS GIS ===<br /> * by Anan Afrida (to be added)<br /> <br /> &lt;!-- Please, edit this page and add further info --&gt;<br /> <br /> [[Category: Development]]<br /> [[Category: Community]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GCI_Ideas_2017&diff=24973 2018-01-10T07:27:04Z

<p>Lucadelu: </p> <hr /> <div>&lt;center&gt;<br /> [[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]]&lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:GCI-logo.jpg|300px|link=https://developers.google.com/open-source/gci/]] &lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]<br /> &lt;/center&gt;<br /> <br /> = About =<br /> <br /> This is the GRASS page for [https://wiki.osgeo.org/wiki/Google_Code_In_2017 Google Code-In] 2017. Here we will list task ideas and other information related to the GRASS GCI projects.<br /> <br /> == What is Google Code-In? ==<br /> <br /> Pre-university students ages 13 to 17 are invited to take part in Google Code-in: Our global, online, contest introducing teenagers to the world of open source. With a wide variety of bite-sized tasks, it’s easy for beginners to jump in and get started no matter what skills they have. Mentors from our participating organizations lend a helping hand as participants learn what it’s like to work on an open source project. For more details, see [https://developers.google.com/open-source/gci/ Google Code-In] main page. <br /> <br /> == How does it work? ==<br /> <br /> # Students search for a '''task''' that interests them and claim it. They have at least ''three days and up to five'' to complete it.<br /> # The student works on the task, getting guidance from mentors, if needed.<br /> # Once the student has finished, he/she submits the work for review through the contest website.<br /> # Mentors from the organization evaluate the work, provide feedback, and if it's complete, accept it! Otherwise, specific feedback is provided, and the student goes back to step #2!<br /> # Go to step #1 and repeat!<br /> <br /> More details can be found at: [https://developers.google.com/open-source/gci/how-it-works https://developers.google.com/open-source/gci/how-it-works]<br /> <br /> == Tasks ==<br /> <br /> The organizations should create a large list of short (3-5 hour) tasks for students to work on. Tasks are categorized as: Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface. Some examples of tasks of different categories can be found [https://developers.google.com/open-source/gci/resources/example-tasks here].<br /> <br /> == Details about the tasks and lessons learnt ==<br /> <br /> * Translations are not allowed by Google Code In as tasks.<br /> <br /> * A strategic plan is needed to generate a pool of tasks doable in 3-5 hours (from beginner to advanced tasks); '''from ~50 up to ~100 tasks!!'''<br /> <br /> * A '''large mentor pool''' that can tackle evaluations of about ~ 100 tasks!! Importantly, the revision of tasks should be rather quick, since the students should complete as many tasks as possible to win the contest.<br /> <br /> = Available mentors =<br /> List of available mentors to follow the tasks<br /> <br /> * [[User:Veroandreo|Veronica Andreo]]<br /> * [[User:Lucadelu|Luca Delucchi]]<br /> * ...<br /> <br /> Note: To sign up as a mentor, write an email to: gsoc-admin@osgeo.org.<br /> <br /> = Results =<br /> <br /> == Add examples and/or screenshots to different manual pages ==<br /> * added examples and screenshots to {{cmd|i.albedo}} manual: {{rev|71903}}, {{rev|71904}}, {{rev|71904}}<br /> * added examples to {{cmd|r.support}} manual: {{rev|71906}}, {{rev|71907}}, {{rev|71908}}<br /> * added screenshot to {{cmd|d.rgb}} manual: {{rev|71924}}, {{rev|71925}}, {{rev|71926}}<br /> * added screenshot to {{cmd|d.mon}} manual: {{rev|71927}}, {{rev|71928}}, {{rev|71929}}<br /> * added screenshots to {{cmd|d.grid}} manual: {{rev|71930}}, {{rev|71931}}, {{rev|71932}}<br /> * added screenshots to {{cmd|d.rast}} manual: {{rev|71947}}, {{rev|71948}}, {{rev|71949}}<br /> * added examples and screenshots to {{cmd|d.histogram}} manual: {{rev|71956}}, {{rev|71957}}, {{rev|71958}}<br /> * added example and screenshot to {{cmd|r.topidx}} manual: {{rev|71959}}, {{rev|71960}}, {{rev|71961}}<br /> * added examples to {{cmd|g.message}} manual: {{rev|72001}}, {{rev|72002}}, {{rev|72003}} <br /> * added examples to {{cmd|g.mapset}} manual: {{rev|72004}}, {{rev|72005}}, {{rev|72006}}<br /> * added examples and screenshots to {{cmd|v.perturb}} manual: {{rev|72044}}, {{rev|72045}}, {{rev|72046}}<br /> * screenshots to {{cmd|d.text}} manual: to be added to svn<br /> <br /> == Add testsuites to different modules ==<br /> * added testsuite to {{cmd|r.report}}: {{rev|71997}}<br /> * added testsuite to {{cmd|r.info}}: {{rev|72050}}<br /> * added testsuite to {{cmd|v.univar}}: {{rev|72049}}<br /> * added testsuite to {{cmd|r.in.ascii}}: {{rev|72060}}<br /> * added testsuite to {{cmd|i.vi}}: {{rev|72064}}<br /> <br /> == Install GRASS GIS on your computer and download North Carolina dataset ==<br /> * 29 students completed the task successfully, 42 abandoned and 22 ran out of time.<br /> <br /> == Compile GRASS GIS ==<br /> * 3 students completed the task successfully and 3 other abandoned.<br /> <br /> == Designs ==<br /> <br /> ''Note'': Students that have failed to submit a proper SVG won't get their tasks uploaded in SVN<br /> <br /> === Splash screen for GRASS GIS GUI start-up ===<br /> * {{rev|71941}}: splash screen by tfang<br /> * {{rev|72024}}: splash screen by Eric1234<br /> * {{rev|72047}}: splash screen by Raghu Ranganathan<br /> * {{rev|72048}}: splash screen by Tom Davies<br /> <br /> === T-shirt for 2018 Code Sprint ===<br /> * {{rev|72000}}: 2 t-shirt designs by Eric1234 <br /> * {{rev|72025}}: t-shirt design by Ilaya Suriya<br /> * {{rev|72052}}: t-shirt design by Tom Davies<br /> * {{rev|72053}}: t-shirt design by Mihika Krishna<br /> * t-shirt design by Lahari. C. Krishna<br /> * t-shirt design by Abhishek Bana<br /> <br /> === Banner for location wizard ===<br /> * {{rev|72061}}: banner by Hatim Aliasger<br /> <br /> == Blog entry about GRASS GIS ==<br /> * {{rev|72056}}: blog entry by Shreya Sandurkar<br /> <br /> == Videos ==<br /> === How to create a location ===<br /> * https://www.youtube.com/watch?v=trvy0B0Qz78 (by Sunveer Singh)<br /> * https://youtu.be/1BBGQZTkBb0 (by Eric1234)<br /> <br /> === Give a talk about GRASS GIS ===<br /> * by Anan Afrida (to be added)<br /> <br /> &lt;!-- Please, edit this page and add further info --&gt;<br /> <br /> [[Category: Development]]<br /> [[Category: Community]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GCI_Ideas_2017&diff=24960 2018-01-08T07:38:26Z

<p>Lucadelu: </p> <hr /> <div>&lt;center&gt;<br /> [[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]]&lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:GCI-logo.jpg|300px|link=https://developers.google.com/open-source/gci/]] &lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]<br /> &lt;/center&gt;<br /> <br /> = About =<br /> <br /> This is the GRASS page for [https://wiki.osgeo.org/wiki/Google_Code_In_2017 Google Code-In] 2017. Here we will list task ideas and other information related to the GRASS GCI projects.<br /> <br /> == What is Google Code-In? ==<br /> <br /> Pre-university students ages 13 to 17 are invited to take part in Google Code-in: Our global, online, contest introducing teenagers to the world of open source. With a wide variety of bite-sized tasks, it’s easy for beginners to jump in and get started no matter what skills they have. Mentors from our participating organizations lend a helping hand as participants learn what it’s like to work on an open source project. For more details, see [https://developers.google.com/open-source/gci/ Google Code-In] main page. <br /> <br /> == How does it work? ==<br /> <br /> # Students search for a '''task''' that interests them and claim it. They have at least ''three days and up to five'' to complete it.<br /> # The student works on the task, getting guidance from mentors, if needed.<br /> # Once the student has finished, he/she submits the work for review through the contest website.<br /> # Mentors from the organization evaluate the work, provide feedback, and if it's complete, accept it! Otherwise, specific feedback is provided, and the student goes back to step #2!<br /> # Go to step #1 and repeat!<br /> <br /> More details can be found at: [https://developers.google.com/open-source/gci/how-it-works https://developers.google.com/open-source/gci/how-it-works]<br /> <br /> == Tasks ==<br /> <br /> The organizations should create a large list of short (3-5 hour) tasks for students to work on. Tasks are categorized as: Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface. Some examples of tasks of different categories can be found [https://developers.google.com/open-source/gci/resources/example-tasks here].<br /> <br /> == Details about the tasks and lessons learnt ==<br /> <br /> * Translations are not allowed by Google Code In as tasks.<br /> <br /> * A strategic plan is needed to generate a pool of tasks doable in 3-5 hours (from beginner to advanced tasks); '''from ~50 up to ~100 tasks!!'''<br /> <br /> * A '''large mentor pool''' that can tackle evaluations of about ~ 100 tasks!! Importantly, the revision of tasks should be rather quick, since the students should complete as many tasks as possible to win the contest.<br /> <br /> = Available mentors =<br /> List of available mentors to follow the tasks<br /> <br /> * [[User:Veroandreo|Veronica Andreo]]<br /> * [[User:Lucadelu|Luca Delucchi]]<br /> * ...<br /> <br /> Note: To sign up as a mentor, write an email to: gsoc-admin@osgeo.org.<br /> <br /> = Results =<br /> <br /> == Add examples, screenshots or both to different manual pages ==<br /> * added examples and screenshots to {{cmd|i.albedo}} manual: {{rev|71903}}, {{rev|71904}}, {{rev|71904}}<br /> * added examples to {{cmd|r.support}} manual: {{rev|71906}}, {{rev|71907}}, {{rev|71908}}<br /> * added screenshot to {{cmd|d.rgb}} manual: {{rev|71924}}, {{rev|71925}}, {{rev|71926}}<br /> * added screenshot to {{cmd|d.mon}} manual: {{rev|71927}}, {{rev|71928}}, {{rev|71929}}<br /> * added screenshots to {{cmd|d.grid}} manual: {{rev|71930}}, {{rev|71931}}, {{rev|71932}}<br /> * added screenshots to {{cmd|d.rast}} manual: {{rev|71947}}, {{rev|71948}}, {{rev|71949}}<br /> * added examples and screenshots to {{cmd|d.histogram}} manual: {{rev|71956}}, {{rev|71957}}, {{rev|71958}}<br /> * added example and screenshot to {{cmd|r.topidx}} manual: {{rev|71959}}, {{rev|71960}}, {{rev|71961}}<br /> * added examples to {{cmd|g.message}} manual: {{rev|72001}}, {{rev|72002}}, {{rev|72003}} <br /> * added examples to {{cmd|g.mapset}} manual: {{rev|72004}}, {{rev|72005}}, {{rev|72006}}<br /> * examples and screenshots to {{cmd|v.perturb}} manual: {{rev|72044}}, {{rev|72045}}, {{rev|72046}}<br /> * screenshots to {{cmd|d.text}} manual: to be added to svn<br /> <br /> == Add testsuites to different modules ==<br /> * added testsuite to {{cmd|r.report}}: {{rev|71997}}<br /> * added testsuite to {{cmd|r.info}}: {{rev|72050}}<br /> * added testsuite to {{cmd|v.univar}}: {{rev|72049}}<br /> <br /> == Install GRASS GIS on your computer and download North Carolina dataset ==<br /> * 27 students completed the task successfully, 38 abandoned and 20 ran out of time.<br /> <br /> == Compile GRASS GIS ==<br /> * 3 students completed the task successfully and 3 other abandoned.<br /> <br /> == Videos ==<br /> === How to create a location ===<br /> * https://www.youtube.com/watch?v=trvy0B0Qz78 (by Sunveer Singh)<br /> * https://youtu.be/1BBGQZTkBb0 (by Eric1234)<br /> <br /> === Give a talk about GRASS GIS ===<br /> * by Anan Afrida (to be added)<br /> <br /> == Design a splash screen for GRASS GIS GUI start-up ==<br /> * {{rev|71941}}: splash screen by tfang<br /> * {{rev|72024}}: splash screen by Eric1234<br /> * {{rev|72047}}: splash screen by Raghu Ranganathan<br /> * {{rev|72048}}: splash screen by Tom Davies<br /> <br /> == Design a t-shirt for 2018 Code Sprint ==<br /> * {{rev|72000}}: 2 t-shirt designs by Eric1234 <br /> * {{rev|72025}}: t-shirt design by Ilaya Suriya<br /> * t-shirt design by Lahari. C. Krishna (to be added to svn)<br /> * {{rev|72052}}: t-shirt design by Tom Davies<br /> * {{rev|72053}}: t-shirt design by Mihika Krishna<br /> <br /> == Design a banner for location wizard ==<br /> * by Hatim Aliasger (to be added to svn)<br /> <br /> == Blog entry about GRASS GIS ==<br /> * by Shreya Sandurkar (to be added)<br /> <br /> &lt;!-- Please, edit this page and add further info --&gt;<br /> <br /> [[Category: Development]]<br /> [[Category: Community]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GCI_Ideas_2017&diff=24957 2018-01-07T23:25:08Z

<p>Lucadelu: </p> <hr /> <div>&lt;center&gt;<br /> [[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]]&lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:GCI-logo.jpg|300px|link=https://developers.google.com/open-source/gci/]] &lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]<br /> &lt;/center&gt;<br /> <br /> = About =<br /> <br /> This is the GRASS page for [https://wiki.osgeo.org/wiki/Google_Code_In_2017 Google Code-In] 2017. Here we will list task ideas and other information related to the GRASS GCI projects.<br /> <br /> == What is Google Code-In? ==<br /> <br /> Pre-university students ages 13 to 17 are invited to take part in Google Code-in: Our global, online, contest introducing teenagers to the world of open source. With a wide variety of bite-sized tasks, it’s easy for beginners to jump in and get started no matter what skills they have. Mentors from our participating organizations lend a helping hand as participants learn what it’s like to work on an open source project. For more details, see [https://developers.google.com/open-source/gci/ Google Code-In] main page. <br /> <br /> == How does it work? ==<br /> <br /> # Students search for a '''task''' that interests them and claim it. They have at least ''three days and up to five'' to complete it.<br /> # The student works on the task, getting guidance from mentors, if needed.<br /> # Once the student has finished, he/she submits the work for review through the contest website.<br /> # Mentors from the organization evaluate the work, provide feedback, and if it's complete, accept it! Otherwise, specific feedback is provided, and the student goes back to step #2!<br /> # Go to step #1 and repeat!<br /> <br /> More details can be found at: [https://developers.google.com/open-source/gci/how-it-works https://developers.google.com/open-source/gci/how-it-works]<br /> <br /> == Tasks ==<br /> <br /> The organizations should create a large list of short (3-5 hour) tasks for students to work on. Tasks are categorized as: Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface. Some examples of tasks of different categories can be found [https://developers.google.com/open-source/gci/resources/example-tasks here].<br /> <br /> == Details about the tasks and lessons learnt ==<br /> <br /> * Translations are not allowed by Google Code In as tasks.<br /> <br /> * A strategic plan is needed to generate a pool of tasks doable in 3-5 hours (from beginner to advanced tasks); '''from ~50 up to ~100 tasks!!'''<br /> <br /> * A '''large mentor pool''' that can tackle evaluations of about ~ 100 tasks!! Importantly, the revision of tasks should be rather quick, since the students should complete as many tasks as possible to win the contest.<br /> <br /> = Available mentors =<br /> List of available mentors to follow the tasks<br /> <br /> * [[User:Veroandreo|Veronica Andreo]]<br /> * [[User:Lucadelu|Luca Delucchi]]<br /> * ...<br /> <br /> Note: To sign up as a mentor, write an email to: gsoc-admin@osgeo.org.<br /> <br /> = Results =<br /> <br /> == Add examples, screenshots or both to different manual pages ==<br /> * added examples and screenshots to {{cmd|i.albedo}} manual: {{rev|71903}}, {{rev|71904}}, {{rev|71904}}<br /> * added examples to {{cmd|r.support}} manual: {{rev|71906}}, {{rev|71907}}, {{rev|71908}}<br /> * added screenshot to {{cmd|d.rgb}} manual: {{rev|71924}}, {{rev|71925}}, {{rev|71926}}<br /> * added screenshot to {{cmd|d.mon}} manual: {{rev|71927}}, {{rev|71928}}, {{rev|71929}}<br /> * added screenshots to {{cmd|d.grid}} manual: {{rev|71930}}, {{rev|71931}}, {{rev|71932}}<br /> * added screenshots to {{cmd|d.rast}} manual: {{rev|71947}}, {{rev|71948}}, {{rev|71949}}<br /> * added examples and screenshots to {{cmd|d.histogram}} manual: {{rev|71956}}, {{rev|71957}}, {{rev|71958}}<br /> * added example and screenshot to {{cmd|r.topidx}} manual: {{rev|71959}}, {{rev|71960}}, {{rev|71961}}<br /> * added examples to {{cmd|g.message}} manual: {{rev|72001}}, {{rev|72002}}, {{rev|72003}} <br /> * added examples to {{cmd|g.mapset}} manual: {{rev|72004}}, {{rev|72005}}, {{rev|72006}}<br /> * examples and screenshots to {{cmd|v.perturb}} manual: {{rev|72044}}, {{rev|72045}}, {{rev|72046}}<br /> * screenshots to {{cmd|d.text}} manual: to be added to svn<br /> <br /> == Add testsuites to different modules ==<br /> * added testsuite to {{cmd|r.report}}: {{rev|71997}}<br /> * added testsuite to {{cmd|r.info}}: {{rev|72050}}<br /> * added testsuite to {{cmd|v.univar}}: {{rev|72049}}<br /> <br /> == Install GRASS GIS on your computer and download North Carolina dataset ==<br /> * 26 students completed the task successfully, 33 abandoned and 20 ran out of time.<br /> <br /> == Compile GRASS GIS ==<br /> * 2 students completed the task successfully and 3 other abandoned.<br /> <br /> == Videos ==<br /> === How to create a location ===<br /> * https://www.youtube.com/watch?v=trvy0B0Qz78 (by Sunveer Singh)<br /> * https://youtu.be/1BBGQZTkBb0 (by Eric1234)<br /> <br /> === Give a talk about GRASS GIS ===<br /> * by Anan Afrida (to be added)<br /> <br /> == Design a splash screen for GRASS GIS GUI start-up ==<br /> * {{rev|71941}}: splash screen by tfang<br /> * {{rev|72024}}: splash screen by Eric1234<br /> * {{rev|72047}}: splash screen by Raghu Ranganathan<br /> * {{rev|72048}}: splash screen by Tom Davies<br /> <br /> == Design a t-shirt for 2018 Code Sprint ==<br /> * {{rev|72000}}: 2 t-shirt designs by Eric1234 <br /> * {{rev|72025}}: t-shirt design by Ilaya Suriya<br /> * t-shirt design by Lahari. C. Krishna (to be added to svn)<br /> * {{rev|72052}}: t-shirt design by Tom Davies<br /> <br /> == Design a banner for location wizard ==<br /> * by Hatim Aliasger (to be added to svn)<br /> <br /> == Blog entry about GRASS GIS ==<br /> * by Shreya Sandurkar (to be added)<br /> <br /> &lt;!-- Please, edit this page and add further info --&gt;<br /> <br /> [[Category: Development]]<br /> [[Category: Community]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GCI_Ideas_2017&diff=24956 2018-01-07T22:04:20Z

<p>Lucadelu: </p> <hr /> <div>&lt;center&gt;<br /> [[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]]&lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:GCI-logo.jpg|300px|link=https://developers.google.com/open-source/gci/]] &lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]<br /> &lt;/center&gt;<br /> <br /> = About =<br /> <br /> This is the GRASS page for [https://wiki.osgeo.org/wiki/Google_Code_In_2017 Google Code-In] 2017. Here we will list task ideas and other information related to the GRASS GCI projects.<br /> <br /> == What is Google Code-In? ==<br /> <br /> Pre-university students ages 13 to 17 are invited to take part in Google Code-in: Our global, online, contest introducing teenagers to the world of open source. With a wide variety of bite-sized tasks, it’s easy for beginners to jump in and get started no matter what skills they have. Mentors from our participating organizations lend a helping hand as participants learn what it’s like to work on an open source project. For more details, see [https://developers.google.com/open-source/gci/ Google Code-In] main page. <br /> <br /> == How does it work? ==<br /> <br /> # Students search for a '''task''' that interests them and claim it. They have at least ''three days and up to five'' to complete it.<br /> # The student works on the task, getting guidance from mentors, if needed.<br /> # Once the student has finished, he/she submits the work for review through the contest website.<br /> # Mentors from the organization evaluate the work, provide feedback, and if it's complete, accept it! Otherwise, specific feedback is provided, and the student goes back to step #2!<br /> # Go to step #1 and repeat!<br /> <br /> More details can be found at: [https://developers.google.com/open-source/gci/how-it-works https://developers.google.com/open-source/gci/how-it-works]<br /> <br /> == Tasks ==<br /> <br /> The organizations should create a large list of short (3-5 hour) tasks for students to work on. Tasks are categorized as: Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface. Some examples of tasks of different categories can be found [https://developers.google.com/open-source/gci/resources/example-tasks here].<br /> <br /> == Details about the tasks and lessons learnt ==<br /> <br /> * Translations are not allowed by Google Code In as tasks.<br /> <br /> * A strategic plan is needed to generate a pool of tasks doable in 3-5 hours (from beginner to advanced tasks); '''from ~50 up to ~100 tasks!!'''<br /> <br /> * A '''large mentor pool''' that can tackle evaluations of about ~ 100 tasks!! Importantly, the revision of tasks should be rather quick, since the students should complete as many tasks as possible to win the contest.<br /> <br /> = Available mentors =<br /> List of available mentors to follow the tasks<br /> <br /> * [[User:Veroandreo|Veronica Andreo]]<br /> * [[User:Lucadelu|Luca Delucchi]]<br /> * ...<br /> <br /> Note: To sign up as a mentor, write an email to: gsoc-admin@osgeo.org.<br /> <br /> = Results =<br /> <br /> == Add examples, screenshots or both to different manual pages ==<br /> * added examples and screenshots to {{cmd|i.albedo}} manual: {{rev|71903}}, {{rev|71904}}, {{rev|71904}}<br /> * added examples to {{cmd|r.support}} manual: {{rev|71906}}, {{rev|71907}}, {{rev|71908}}<br /> * added screenshot to {{cmd|d.rgb}} manual: {{rev|71924}}, {{rev|71925}}, {{rev|71926}}<br /> * added screenshot to {{cmd|d.mon}} manual: {{rev|71927}}, {{rev|71928}}, {{rev|71929}}<br /> * added screenshots to {{cmd|d.grid}} manual: {{rev|71930}}, {{rev|71931}}, {{rev|71932}}<br /> * added screenshots to {{cmd|d.rast}} manual: {{rev|71947}}, {{rev|71948}}, {{rev|71949}}<br /> * added examples and screenshots to {{cmd|d.histogram}} manual: {{rev|71956}}, {{rev|71957}}, {{rev|71958}}<br /> * added example and screenshot to {{cmd|r.topidx}} manual: {{rev|71959}}, {{rev|71960}}, {{rev|71961}}<br /> * added examples to {{cmd|g.message}} manual: {{rev|72001}}, {{rev|72002}}, {{rev|72003}} <br /> * added examples to {{cmd|g.mapset}} manual: {{rev|72004}}, {{rev|72005}}, {{rev|72006}}<br /> * examples and screenshots to {{cmd|v.perturb}} manual: {{rev|72044}}, {{rev|72045}}, {{rev|72046}}<br /> * screenshots to {{cmd|d.text}} manual: to be added to svn<br /> <br /> == Add testsuites to different modules ==<br /> * added testsuite to {{cmd|r.report}}: {{rev|71997}}<br /> * added testsuite to {{cmd|r.info}}: {{rev|72050}}<br /> * added testsuite to {{cmd|v.univar}}: {{rev|72049}}<br /> <br /> == Install GRASS GIS on your computer and download North Carolina dataset ==<br /> * 26 students completed the task successfully, 33 abandoned and 20 ran out of time.<br /> <br /> == Compile GRASS GIS ==<br /> * 2 students completed the task successfully and 3 other abandoned.<br /> <br /> == Videos ==<br /> === How to create a location ===<br /> * https://www.youtube.com/watch?v=trvy0B0Qz78 (by Sunveer Singh)<br /> * https://youtu.be/1BBGQZTkBb0 (by Eric1234)<br /> <br /> === Give a talk about GRASS GIS ===<br /> * by Anan Afrida (to be added)<br /> <br /> == Design a splash screen for GRASS GIS GUI start-up ==<br /> * {{rev|71941}}: splash screen by tfang<br /> * {{rev|72024}}: splash screen by Eric1234<br /> * {{rev|72047}}: splash screen by Raghu Ranganathan<br /> * {{rev|72048}}: splash screen by Tom Davies<br /> <br /> == Design a t-shirt for 2018 Code Sprint ==<br /> * {{rev|72000}}: 2 t-shirt designs by Eric1234 <br /> * {{rev|72025}}: t-shirt design by Ilaya Suriya<br /> * t-shirt design by Lahari. C. Krishna (to be added to svn)<br /> * t-shirt design by Tom Davies (to be added to svn)<br /> <br /> == Design a banner for location wizard ==<br /> * by Hatim Aliasger (to be added to svn)<br /> <br /> == Blog entry about GRASS GIS ==<br /> * by Shreya Sandurkar (to be added)<br /> <br /> &lt;!-- Please, edit this page and add further info --&gt;<br /> <br /> [[Category: Development]]<br /> [[Category: Community]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GCI_Ideas_2017&diff=24955 2018-01-07T20:31:15Z

<p>Lucadelu: </p> <hr /> <div>&lt;center&gt;<br /> [[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]]&lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:GCI-logo.jpg|300px|link=https://developers.google.com/open-source/gci/]] &lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]<br /> &lt;/center&gt;<br /> <br /> = About =<br /> <br /> This is the GRASS page for [https://wiki.osgeo.org/wiki/Google_Code_In_2017 Google Code-In] 2017. Here we will list task ideas and other information related to the GRASS GCI projects.<br /> <br /> == What is Google Code-In? ==<br /> <br /> Pre-university students ages 13 to 17 are invited to take part in Google Code-in: Our global, online, contest introducing teenagers to the world of open source. With a wide variety of bite-sized tasks, it’s easy for beginners to jump in and get started no matter what skills they have. Mentors from our participating organizations lend a helping hand as participants learn what it’s like to work on an open source project. For more details, see [https://developers.google.com/open-source/gci/ Google Code-In] main page. <br /> <br /> == How does it work? ==<br /> <br /> # Students search for a '''task''' that interests them and claim it. They have at least ''three days and up to five'' to complete it.<br /> # The student works on the task, getting guidance from mentors, if needed.<br /> # Once the student has finished, he/she submits the work for review through the contest website.<br /> # Mentors from the organization evaluate the work, provide feedback, and if it's complete, accept it! Otherwise, specific feedback is provided, and the student goes back to step #2!<br /> # Go to step #1 and repeat!<br /> <br /> More details can be found at: [https://developers.google.com/open-source/gci/how-it-works https://developers.google.com/open-source/gci/how-it-works]<br /> <br /> == Tasks ==<br /> <br /> The organizations should create a large list of short (3-5 hour) tasks for students to work on. Tasks are categorized as: Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface. Some examples of tasks of different categories can be found [https://developers.google.com/open-source/gci/resources/example-tasks here].<br /> <br /> == Details about the tasks and lessons learnt ==<br /> <br /> * Translations are not allowed by Google Code In as tasks.<br /> <br /> * A strategic plan is needed to generate a pool of tasks doable in 3-5 hours (from beginner to advanced tasks); '''from ~50 up to ~100 tasks!!'''<br /> <br /> * A '''large mentor pool''' that can tackle evaluations of about ~ 100 tasks!! Importantly, the revision of tasks should be rather quick, since the students should complete as many tasks as possible to win the contest.<br /> <br /> = Available mentors =<br /> List of available mentors to follow the tasks<br /> <br /> * [[User:Veroandreo|Veronica Andreo]]<br /> * [[User:Lucadelu|Luca Delucchi]]<br /> * ...<br /> <br /> Note: To sign up as a mentor, write an email to: gsoc-admin@osgeo.org.<br /> <br /> = Results =<br /> <br /> == Add examples, screenshots or both to different manual pages ==<br /> * added examples and screenshots to {{cmd|i.albedo}} manual: {{rev|71903}}, {{rev|71904}}, {{rev|71904}}<br /> * added examples to {{cmd|r.support}} manual: {{rev|71906}}, {{rev|71907}}, {{rev|71908}}<br /> * added screenshot to {{cmd|d.rgb}} manual: {{rev|71924}}, {{rev|71925}}, {{rev|71926}}<br /> * added screenshot to {{cmd|d.mon}} manual: {{rev|71927}}, {{rev|71928}}, {{rev|71929}}<br /> * added screenshots to {{cmd|d.grid}} manual: {{rev|71930}}, {{rev|71931}}, {{rev|71932}}<br /> * added screenshots to {{cmd|d.rast}} manual: {{rev|71947}}, {{rev|71948}}, {{rev|71949}}<br /> * added examples and screenshots to {{cmd|d.histogram}} manual: {{rev|71956}}, {{rev|71957}}, {{rev|71958}}<br /> * added example and screenshot to {{cmd|r.topidx}} manual: {{rev|71959}}, {{rev|71960}}, {{rev|71961}}<br /> * added examples to {{cmd|g.message}} manual: {{rev|72001}}, {{rev|72002}}, {{rev|72003}} <br /> * added examples to {{cmd|g.mapset}} manual: {{rev|72004}}, {{rev|72005}}, {{rev|72006}}<br /> * examples and screenshots to {{cmd|v.perturb}} manual: {{rev|72044}}, {{rev|72045}}, {{rev|72046}}<br /> * screenshots to {{cmd|d.text}} manual: to be added to svn<br /> <br /> == Add testsuites to different modules ==<br /> * added testsuite to {{cmd|r.report}}: {{rev|71997}}<br /> <br /> == Install GRASS GIS on your computer and download North Carolina dataset ==<br /> * 26 students completed the task successfully, 33 abandoned and 20 ran out of time.<br /> <br /> == Compile GRASS GIS ==<br /> * 2 students completed the task successfully and 3 other abandoned.<br /> <br /> == Videos ==<br /> === How to create a location ===<br /> * https://www.youtube.com/watch?v=trvy0B0Qz78 (by Sunveer Singh)<br /> * https://youtu.be/1BBGQZTkBb0 (by Eric1234)<br /> <br /> === Give a talk about GRASS GIS ===<br /> * by Anan Afrida (to be added)<br /> <br /> == Design a splash screen for GRASS GIS GUI start-up ==<br /> * {{rev|71941}}: splash screen by tfang<br /> * {{rev|72024}}: splash screen by Eric1234<br /> * {{rev|72047}}: splash screen by Raghu Ranganathan<br /> <br /> == Design a t-shirt for 2018 Code Sprint ==<br /> * {{rev|72000}}: 2 t-shirt designs by Eric1234 <br /> * {{rev|72025}}: t-shirt design by Ilaya Suriya<br /> * t-shirt design by Lahari. C. Krishna (to be added to svn)<br /> * t-shirt design by Tom Davies (to be added to svn)<br /> <br /> == Design a banner for location wizard ==<br /> * by Hatim Aliasger (to be added to svn)<br /> <br /> == Blog entry about GRASS GIS ==<br /> * by Shreya Sandurkar (to be added)<br /> <br /> &lt;!-- Please, edit this page and add further info --&gt;<br /> <br /> [[Category: Development]]<br /> [[Category: Community]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GIS_Community_Sprint_Bonn_2018&diff=24954 2018-01-07T20:09:38Z

<p>Lucadelu: /* In person */ fixed a typo, add new topic</p> <hr /> <div>{{toc|right}}<br /> <br /> The '''GRASS GIS community''' will join the general '''OSGeo Code Sprint''' at BaseCamp in Bonn, following the annual FOSSGIS conference (German Speaking OSGeo Local Chapter conference in Bonn, Germany)<br /> <br /> <br /> &lt;center&gt;<br /> [[File:GRASS_GIS_Code_Sprint_2018.png|320px]] <br /> &lt;/center&gt;<br /> <br /> == Timing, Venue ==<br /> <br /> OSGeo Code Sprint: '''March 18 - 25, 2018 at BaseCamp. Bonn, Germany'''.<br /> <br /> == Sponsors ==<br /> <br /> Please check more info on the Bonn Code Sprint 2018 [https://wiki.osgeo.org/wiki/OSGeo_Code_Sprint_2018 here].<br /> <br /> We also welcome direct '''financial contributions''' 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<br /> <br /> :::'''sponsoring the GRASS project''' at '''[http://grass.osgeo.org/donations http://grass.osgeo.org/donations]'''<br /> <br /> Note that it is also possible to &lt;b&gt;buy a round of beer for the developers with a quick click&lt;/b&gt; using the PayPal &quot;Buy [pizza/beer/...] Now&quot; button [[Image:Btn_donate_SM.gif|center|link=http://grass.osgeo.org/donations/]]<br /> <br /> For any questions, please contact [[User:Neteler|Markus Neteler]] &lt;tt&gt;&lt;neteler at osgeo.org&gt;&lt;/tt&gt;. Any surplus at the end of the event will be turned over to the GRASS GIS project.<br /> <br /> This GRASS GIS 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.<br /> This Bonn event is especially interesting since '''important OSGeo projects come together'''!<br /> <br /> <br /> <br /> == Agenda - What we plan to do ==<br /> <br /> === Move to Git ===<br /> <br /> * Choose among different options: OSGeo Git, Github, GitLab<br /> * Participants are invited to study Git in advance :-)<br /> <br /> === New website ===<br /> <br /> * Choose among different options: Wordpress, Sphinx, ... ?<br /> <br /> === Port wxGUI to wxPython 4 ===<br /> <br /> * Finish porting wxGUI code to the new wxPython 4<br /> * It also includes porting code to Python 3<br /> <br /> === Finish complete Python 3 support === <br /> <br /> * Includes also wxGUI support for wxPython 4<br /> * ...<br /> <br /> == Planned participation ==<br /> <br /> For organizational reasons, please '''additionally register''' at: https://wiki.osgeo.org/wiki/OSGeo_Code_Sprint_2018#Participants &lt;&lt;--- important!<br /> <br /> === In person ===<br /> <br /> Please add your name here or contact [[User:Lucadelu|Luca Delucchi]] &lt;tt&gt;&lt;lucadeluge at gmail com&gt;&lt;/tt&gt;:<br /> <br /> {|class=&quot;wikitable sortable&quot; border=&quot;2&quot; cellspacing=&quot;0&quot; cellpadding=&quot;4&quot; rules=&quot;all&quot; style=&quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;&quot; <br /> |width=50px|'''No'''<br /> |width=130px|'''Participant '''<br /> |width=100px|'''Country'''<br /> |width=100px|'''Arrival'''<br /> |width=100px|'''Departure'''<br /> |'''Topic'''<br /> |width=75px|'''T-Shirt'''<br /> |'''Notes'''<br /> |-<br /> |1<br /> |[[User:Neteler|Markus Neteler]]<br /> |Germany<br /> |18.3.<br /> |25.3.<br /> |Migration to git discussion, GRASS GIS 8<br /> |M<br /> |<br /> |-<br /> |2<br /> |[[User:Ychemin|Yann Chemin]]<br /> |France<br /> |18.3.<br /> |25.3.<br /> |ISIS-GRASS, Planetary projections, i.ortho.photo, bundle blocks, GRASS GIS 8<br /> |XL<br /> |<br /> |-<br /> |3<br /> |[[User:Landa|Martin Landa]]<br /> |Czech Republic<br /> |18.3.<br /> |25.3.<br /> |Migration to git discussion, website discussion, GRASS GIS 8<br /> |L<br /> |<br /> |-<br /> |4<br /> |Stefan Blumentrath<br /> |Germany/Norway<br /> |??.??.<br /> |25.3.<br /> |Flexible<br /> |L<br /> |<br /> |-<br /> |5<br /> |[[User:Veroandreo|Veronica Andreo]]<br /> |Argentina/Netherlands<br /> |18.3<br /> |??.??<br /> |TGRASS, Documentation, website discussion<br /> |S<br /> |<br /> |-<br /> |6<br /> |[[User:Lucadelu|Luca Delucchi]]<br /> |Italy<br /> |18.3<br /> |??.??<br /> |Migration to git discussion, TGRASS, testsuite, website discussion<br /> |L<br /> |<br /> |-<br /> |#<br /> |... <br /> |<br /> |<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |}<br /> <br /> === Via IRC chat ===<br /> <br /> (IRC is a nice archaic chat system, see [[IRC]])<br /> <br /> {|class=&quot;wikitable sortable&quot; border=&quot;2&quot; cellspacing=&quot;0&quot; cellpadding=&quot;4&quot; rules=&quot;all&quot; style=&quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;&quot; <br /> |width=50px|'''No'''<br /> |width=130px|'''Participant '''<br /> |width=100px|'''Country'''<br /> |-<br /> |Add<br /> |your<br /> |self..<br /> |-<br /> |}<br /> <br /> == Individual Preparation ==<br /> <br /> * Bring your own computer<br /> * Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:Schuko_plug_and_socket.png Germany]). See also http://www.power-plugs-sockets.com/<br /> * Install subversion and the compiler tools, and come with a working GRASS development environment if possible.<br /> <br /> == Photos ==<br /> <br /> We have to remember to take at least one group photo! :-)<br /> <br /> == Reports ==<br /> <br /> See [[Talk:GRASS_Community_Sprint_Bonn_2018]]<br /> <br /> == FAQ ==<br /> <br /> * ''Is the GRASS Community Sprint just a coding event?''<br /> ** 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.<br /> ** 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<br /> * ''Is the GRASS Community Sprint for developers only?''<br /> ** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.<br /> * ''Where can I get help and more information about the community sprint?''<br /> ** Contact [[User:Lucadelu|Luca Delucchi]] &lt;tt&gt;&lt;lucadeluge at gmail com&gt;&lt;/tt&gt;<br /> <br /> [[Category: Workshops]]<br /> [[Category: Code Sprint]]<br /> [[Category: 2018]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GIS_Community_Sprint_Bonn_2018&diff=24953 2018-01-07T20:08:16Z

<p>Lucadelu: /* In person */</p> <hr /> <div>{{toc|right}}<br /> <br /> The '''GRASS GIS community''' will join the general '''OSGeo Code Sprint''' at BaseCamp in Bonn, following the annual FOSSGIS conference (German Speaking OSGeo Local Chapter conference in Bonn, Germany)<br /> <br /> <br /> &lt;center&gt;<br /> [[File:GRASS_GIS_Code_Sprint_2018.png|320px]] <br /> &lt;/center&gt;<br /> <br /> == Timing, Venue ==<br /> <br /> OSGeo Code Sprint: '''March 18 - 25, 2018 at BaseCamp. Bonn, Germany'''.<br /> <br /> == Sponsors ==<br /> <br /> Please check more info on the Bonn Code Sprint 2018 [https://wiki.osgeo.org/wiki/OSGeo_Code_Sprint_2018 here].<br /> <br /> We also welcome direct '''financial contributions''' 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<br /> <br /> :::'''sponsoring the GRASS project''' at '''[http://grass.osgeo.org/donations http://grass.osgeo.org/donations]'''<br /> <br /> Note that it is also possible to &lt;b&gt;buy a round of beer for the developers with a quick click&lt;/b&gt; using the PayPal &quot;Buy [pizza/beer/...] Now&quot; button [[Image:Btn_donate_SM.gif|center|link=http://grass.osgeo.org/donations/]]<br /> <br /> For any questions, please contact [[User:Neteler|Markus Neteler]] &lt;tt&gt;&lt;neteler at osgeo.org&gt;&lt;/tt&gt;. Any surplus at the end of the event will be turned over to the GRASS GIS project.<br /> <br /> This GRASS GIS 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.<br /> This Bonn event is especially interesting since '''important OSGeo projects come together'''!<br /> <br /> <br /> <br /> == Agenda - What we plan to do ==<br /> <br /> === Move to Git ===<br /> <br /> * Choose among different options: OSGeo Git, Github, GitLab<br /> * Participants are invited to study Git in advance :-)<br /> <br /> === New website ===<br /> <br /> * Choose among different options: Wordpress, Sphinx, ... ?<br /> <br /> === Port wxGUI to wxPython 4 ===<br /> <br /> * Finish porting wxGUI code to the new wxPython 4<br /> * It also includes porting code to Python 3<br /> <br /> === Finish complete Python 3 support === <br /> <br /> * Includes also wxGUI support for wxPython 4<br /> * ...<br /> <br /> == Planned participation ==<br /> <br /> For organizational reasons, please '''additionally register''' at: https://wiki.osgeo.org/wiki/OSGeo_Code_Sprint_2018#Participants &lt;&lt;--- important!<br /> <br /> === In person ===<br /> <br /> Please add your name here or contact [[User:Lucadelu|Luca Delucchi]] &lt;tt&gt;&lt;lucadeluge at gmail com&gt;&lt;/tt&gt;:<br /> <br /> {|class=&quot;wikitable sortable&quot; border=&quot;2&quot; cellspacing=&quot;0&quot; cellpadding=&quot;4&quot; rules=&quot;all&quot; style=&quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;&quot; <br /> |width=50px|'''No'''<br /> |width=130px|'''Participant '''<br /> |width=100px|'''Country'''<br /> |width=100px|'''Arrival'''<br /> |width=100px|'''Departure'''<br /> |'''Topic'''<br /> |width=75px|'''T-Shirt'''<br /> |'''Notes'''<br /> |-<br /> |1<br /> |[[User:Neteler|Markus Neteler]]<br /> |Germany<br /> |18.3.<br /> |25.3.<br /> |Migration to git discussion, GRASS GIS 8<br /> |M<br /> |<br /> |-<br /> |2<br /> |[[User:Ychemin|Yann Chemin]]<br /> |France<br /> |18.3.<br /> |25.3.<br /> |ISIS-GRASS, Planetary projections, i.ortho.photo, bundle blocks, GRASS GIS 8<br /> |XL<br /> |<br /> |-<br /> |3<br /> |[[User:Landa|Martin Landa]]<br /> |Czech Republic<br /> |18.3.<br /> |25.3.<br /> |Migration to git discussion, website discussion, GRASS GIS 8<br /> |L<br /> |<br /> |-<br /> |4<br /> |Stefan Blumentrath<br /> |Germany/Norway<br /> |??.??.<br /> |25.3.<br /> |Flexible<br /> |L<br /> |<br /> |-<br /> |5<br /> |[[User:Veroandreo|Veronica Andreo]]<br /> |Argentina/Netherlands<br /> |18.3<br /> |??.??<br /> |TGRASS, Documentation, website discussion<br /> |S<br /> |<br /> |-<br /> |5<br /> |[[User:Lucadelu|Luca Delucchi]]<br /> |Italy<br /> |18.3<br /> |??.??<br /> |TGRASS, testsuite, website discussion<br /> |L<br /> |<br /> |-<br /> |#<br /> |... <br /> |<br /> |<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |}<br /> <br /> === Via IRC chat ===<br /> <br /> (IRC is a nice archaic chat system, see [[IRC]])<br /> <br /> {|class=&quot;wikitable sortable&quot; border=&quot;2&quot; cellspacing=&quot;0&quot; cellpadding=&quot;4&quot; rules=&quot;all&quot; style=&quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;&quot; <br /> |width=50px|'''No'''<br /> |width=130px|'''Participant '''<br /> |width=100px|'''Country'''<br /> |-<br /> |Add<br /> |your<br /> |self..<br /> |-<br /> |}<br /> <br /> == Individual Preparation ==<br /> <br /> * Bring your own computer<br /> * Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:Schuko_plug_and_socket.png Germany]). See also http://www.power-plugs-sockets.com/<br /> * Install subversion and the compiler tools, and come with a working GRASS development environment if possible.<br /> <br /> == Photos ==<br /> <br /> We have to remember to take at least one group photo! :-)<br /> <br /> == Reports ==<br /> <br /> See [[Talk:GRASS_Community_Sprint_Bonn_2018]]<br /> <br /> == FAQ ==<br /> <br /> * ''Is the GRASS Community Sprint just a coding event?''<br /> ** 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.<br /> ** 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<br /> * ''Is the GRASS Community Sprint for developers only?''<br /> ** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.<br /> * ''Where can I get help and more information about the community sprint?''<br /> ** Contact [[User:Lucadelu|Luca Delucchi]] &lt;tt&gt;&lt;lucadeluge at gmail com&gt;&lt;/tt&gt;<br /> <br /> [[Category: Workshops]]<br /> [[Category: Code Sprint]]<br /> [[Category: 2018]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GCI_Ideas_2017&diff=24931 2017-12-29T23:10:20Z

<p>Lucadelu: /* Results */ added new results to GCI 2017</p> <hr /> <div>&lt;center&gt;<br /> [[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]]&lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:GCI-logo.jpg|300px|link=https://developers.google.com/open-source/gci/]] &lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]<br /> &lt;/center&gt;<br /> <br /> = About =<br /> <br /> This is the GRASS page for [https://wiki.osgeo.org/wiki/Google_Code_In_2017 Google Code-In] 2017. Here we will list task ideas and other information related to the GRASS GCI projects.<br /> <br /> == What is Google Code-In? ==<br /> <br /> Pre-university students ages 13 to 17 are invited to take part in Google Code-in: Our global, online, contest introducing teenagers to the world of open source. With a wide variety of bite-sized tasks, it’s easy for beginners to jump in and get started no matter what skills they have. Mentors from our participating organizations lend a helping hand as participants learn what it’s like to work on an open source project. For more details, see [https://developers.google.com/open-source/gci/ Google Code-In] main page. <br /> <br /> == How does it work? ==<br /> <br /> # Students search for a '''task''' that interests them and claim it. They have at least ''three days and up to five'' to complete it.<br /> # The student works on the task, getting guidance from mentors, if needed.<br /> # Once the student has finished, he/she submits the work for review through the contest website.<br /> # Mentors from the organization evaluate the work, provide feedback, and if it's complete, accept it! Otherwise, specific feedback is provided, and the student goes back to step #2!<br /> # Go to step #1 and repeat!<br /> <br /> More details can be found at: [https://developers.google.com/open-source/gci/how-it-works https://developers.google.com/open-source/gci/how-it-works]<br /> <br /> == Tasks ==<br /> <br /> The organizations should create a large list of short (3-5 hour) tasks for students to work on. Tasks are categorized as: Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface. Some examples of tasks of different categories can be found [https://developers.google.com/open-source/gci/resources/example-tasks here].<br /> <br /> == Details about the tasks and lessons learnt ==<br /> <br /> * Translations are not allowed by Google Code In as tasks.<br /> <br /> * A strategic plan is needed to generate a pool of tasks doable in 3-5 hours (from beginner to advanced tasks); '''from ~50 up to ~100 tasks!!'''<br /> <br /> * A '''large mentor pool''' that can tackle evaluations of about ~ 100 tasks!! Importantly, the revision of tasks should be rather quick, since the students should complete as many tasks as possible to win the contest.<br /> <br /> = Available mentors =<br /> List of available mentors to follow the tasks<br /> <br /> * [[User:Veroandreo|Veronica Andreo]]<br /> * [[User:Lucadelu|Luca Delucchi]]<br /> * ...<br /> <br /> Note: To sign up as a mentor, write an email to: gsoc-admin@osgeo.org.<br /> <br /> = Results =<br /> <br /> == Commits related to CGI 2017 ==<br /> * improvements in {{cmd|i.albedo}} manual {{rev|71903}} {{rev|71904}} {{rev|71904}}<br /> * added examples to {{cmd|r.support}} manual {{rev|71906}} {{rev|71907}} {{rev|71908}}<br /> * added screenshot to {{cmd|d.rgb}} manual {{rev|71924}} {{rev|71925}} {{rev|71926}}<br /> * added screenshot to {{cmd|d.mon}} manual {{rev|71927}} {{rev|71928}} {{rev|71929}}<br /> * added screenshots to {{cmd|d.grid}} manual {{rev|71930}} {{rev|71931}} {{rev|71932}}<br /> * added screenshots to {{cmd|d.rast}} manual {{rev|71947}} {{rev|71948}} {{rev|71949}}<br /> * added examples and screenshots to {{cmd|d.histogram}} manual {{rev|71956}} {{rev|71957}} {{rev|71958}}<br /> * added example and screenshot to {{cmd|r.topidx}} manual {{rev|71959}} {{rev|71960}} {{rev|71961}}<br /> * added testsuite to {{cmd|r.report}} {{rev|71997}}<br /> <br /> <br /> == Videos ==<br /> === How to create a location ===<br /> * https://www.youtube.com/watch?v=trvy0B0Qz78<br /> <br /> == Design a splash screen for GRASS GIS GUI start-up ==<br /> * added tfang version {{rev|71941}}<br /> <br /> == Design a t-shirt for 2018 Code Sprint ==<br /> * added 2 versions proposed by Eric {{rev|72000}}<br /> <br /> &lt;!-- Please, edit this page and add further info --&gt;<br /> <br /> [[Category: Development]]<br /> [[Category: Community]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GCI_Ideas_2017&diff=24924 2017-12-19T22:59:16Z

<p>Lucadelu: </p> <hr /> <div>&lt;center&gt;<br /> [[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]]&lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:GCI-logo.jpg|300px|link=https://developers.google.com/open-source/gci/]] &lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]<br /> &lt;/center&gt;<br /> <br /> = About =<br /> <br /> This is the GRASS page for [https://wiki.osgeo.org/wiki/Google_Code_In_2017 Google Code-In] 2017. Here we will list task ideas and other information related to the GRASS GCI projects.<br /> <br /> == What is Google Code-In? ==<br /> <br /> Pre-university students ages 13 to 17 are invited to take part in Google Code-in: Our global, online, contest introducing teenagers to the world of open source. With a wide variety of bite-sized tasks, it’s easy for beginners to jump in and get started no matter what skills they have. Mentors from our participating organizations lend a helping hand as participants learn what it’s like to work on an open source project. For more details, see [https://developers.google.com/open-source/gci/ Google Code-In] main page. <br /> <br /> == How does it work? ==<br /> <br /> # Students search for a '''task''' that interests them and claim it. They have at least ''three days and up to five'' to complete it.<br /> # The student works on the task, getting guidance from mentors, if needed.<br /> # Once the student has finished, he/she submits the work for review through the contest website.<br /> # Mentors from the organization evaluate the work, provide feedback, and if it's complete, accept it! Otherwise, specific feedback is provided, and the student goes back to step #2!<br /> # Go to step #1 and repeat!<br /> <br /> More details can be found at: [https://developers.google.com/open-source/gci/how-it-works https://developers.google.com/open-source/gci/how-it-works]<br /> <br /> == Tasks ==<br /> <br /> The organizations should create a large list of short (3-5 hour) tasks for students to work on. Tasks are categorized as: Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface. Some examples of tasks of different categories can be found [https://developers.google.com/open-source/gci/resources/example-tasks here].<br /> <br /> == Details about the tasks and lessons learnt ==<br /> <br /> * Translations are not allowed by Google Code In as tasks.<br /> <br /> * A strategic plan is needed to generate a pool of tasks doable in 3-5 hours (from beginner to advanced tasks); '''from ~50 up to ~100 tasks!!'''<br /> <br /> * A '''large mentor pool''' that can tackle evaluations of about ~ 100 tasks!! Importantly, the revision of tasks should be rather quick, since the students should complete as many tasks as possible to win the contest.<br /> <br /> = Available mentors =<br /> List of available mentors to follow the tasks<br /> <br /> * [[User:Veroandreo|Veronica Andreo]]<br /> * [[User:Lucadelu|Luca Delucchi]]<br /> * ...<br /> <br /> Note: To sign up as a mentor, write an email to: gsoc-admin@osgeo.org.<br /> <br /> = Results =<br /> <br /> == Commits related to CGI 2017 ==<br /> * improvements in {{cmd|i.albedo}} manual {{rev|71903}} {{rev|71904}} {{rev|71904}}<br /> * added examples to {{cmd|r.support}} {{rev|71906}} {{rev|71907}} {{rev|71908}}<br /> * added screenshot to {{cmd|d.rgb}} {{rev|71924}} {{rev|71925}} {{rev|71926}}<br /> * added screenshot to {{cmd|d.mon}} {{rev|71927}} {{rev|71928}} {{rev|71929}}<br /> * added screenshots to {{cmd|d.grid}} {{rev|71930}} {{rev|71931}} {{rev|71932}}<br /> * added screenshots to {{cmd|d.rast}} {{rev|71947}} {{rev|71948}} {{rev|71949}}<br /> * added examples and screenshots to {{cmd|d.histogram}} {{rev|71956}} {{rev|71957}} {{rev|71958}}<br /> * added example and screenshot to {{cmd|r.topidx}} {{rev|71959}} {{rev|71960}} {{rev|71961}}<br /> <br /> == Videos ==<br /> === How to create a location ===<br /> * https://www.youtube.com/watch?v=trvy0B0Qz78<br /> <br /> == Design a splash screen for GRASS GIS GUI start-up ==<br /> * added tfang version {{rev|71941}}<br /> <br /> &lt;!-- Please, edit this page and add further info --&gt;<br /> <br /> [[Category: Development]]<br /> [[Category: Community]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GCI_Ideas_2017&diff=24923 2017-12-19T22:58:45Z

<p>Lucadelu: </p> <hr /> <div>&lt;center&gt;<br /> [[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]]&lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:GCI-logo.jpg|300px|link=https://developers.google.com/open-source/gci/]] &lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]<br /> &lt;/center&gt;<br /> <br /> = About =<br /> <br /> This is the GRASS page for [https://wiki.osgeo.org/wiki/Google_Code_In_2017 Google Code-In] 2017. Here we will list task ideas and other information related to the GRASS GCI projects.<br /> <br /> == What is Google Code-In? ==<br /> <br /> Pre-university students ages 13 to 17 are invited to take part in Google Code-in: Our global, online, contest introducing teenagers to the world of open source. With a wide variety of bite-sized tasks, it’s easy for beginners to jump in and get started no matter what skills they have. Mentors from our participating organizations lend a helping hand as participants learn what it’s like to work on an open source project. For more details, see [https://developers.google.com/open-source/gci/ Google Code-In] main page. <br /> <br /> == How does it work? ==<br /> <br /> # Students search for a '''task''' that interests them and claim it. They have at least ''three days and up to five'' to complete it.<br /> # The student works on the task, getting guidance from mentors, if needed.<br /> # Once the student has finished, he/she submits the work for review through the contest website.<br /> # Mentors from the organization evaluate the work, provide feedback, and if it's complete, accept it! Otherwise, specific feedback is provided, and the student goes back to step #2!<br /> # Go to step #1 and repeat!<br /> <br /> More details can be found at: [https://developers.google.com/open-source/gci/how-it-works https://developers.google.com/open-source/gci/how-it-works]<br /> <br /> == Tasks ==<br /> <br /> The organizations should create a large list of short (3-5 hour) tasks for students to work on. Tasks are categorized as: Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface. Some examples of tasks of different categories can be found [https://developers.google.com/open-source/gci/resources/example-tasks here].<br /> <br /> == Details about the tasks and lessons learnt ==<br /> <br /> * Translations are not allowed by Google Code In as tasks.<br /> <br /> * A strategic plan is needed to generate a pool of tasks doable in 3-5 hours (from beginner to advanced tasks); '''from ~50 up to ~100 tasks!!'''<br /> <br /> * A '''large mentor pool''' that can tackle evaluations of about ~ 100 tasks!! Importantly, the revision of tasks should be rather quick, since the students should complete as many tasks as possible to win the contest.<br /> <br /> = Available mentors =<br /> List of available mentors to follow the tasks<br /> <br /> * [[User:Veroandreo|Veronica Andreo]]<br /> * [[User:Lucadelu|Luca Delucchi]]<br /> * ...<br /> <br /> Note: To sign up as a mentor, write an email to: gsoc-admin@osgeo.org.<br /> <br /> = Results =<br /> <br /> == Commits related to CGI 2017 ==<br /> * improvements in {{cmd|i.albedo}} manual {{rev|71903}} {{rev|71904}} {{rev|71904}}<br /> * added examples to {{cmd|r.support}} {{rev|71906}} {{rev|71907}} {{rev|71908}}<br /> * added screenshot to {{cmd|d.rgb}} {{rev|71924}} {{rev|71925}} {{rev|71926}}<br /> * added screenshot to {{cmd|d.mon}} {{rev|71927}} {{rev|71928}} {{rev|71929}}<br /> * added screenshots to {{cmd|d.grid}} {{rev|71930}} {{rev|71931}} {{rev|71932}}<br /> * added screenshots to {{cmd|d.rast}} {{rev|71947}} {{rev|71948}} {{rev|71949}}<br /> * added examples and screenshots to {{cmd|d.histogram}} {{rev|71956}} {{rev|71957}} {{rev|71958}}<br /> * added example and screenshot to {cmd|r.topidx}} {{rev|71959}} {{rev|71960}} {{rev|71961}}<br /> <br /> == Videos ==<br /> === How to create a location ===<br /> * https://www.youtube.com/watch?v=trvy0B0Qz78<br /> <br /> == Design a splash screen for GRASS GIS GUI start-up ==<br /> * added tfang version {{rev|71941}}<br /> <br /> &lt;!-- Please, edit this page and add further info --&gt;<br /> <br /> [[Category: Development]]<br /> [[Category: Community]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GCI_Ideas_2017&diff=24921 2017-12-18T08:41:51Z

<p>Lucadelu: </p> <hr /> <div>&lt;center&gt;<br /> [[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]]&lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:GCI-logo.jpg|300px|link=https://developers.google.com/open-source/gci/]] &lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]<br /> &lt;/center&gt;<br /> <br /> = About =<br /> <br /> This is the GRASS page for [https://wiki.osgeo.org/wiki/Google_Code_In_2017 Google Code-In] 2017. Here we will list task ideas and other information related to the GRASS GCI projects.<br /> <br /> == What is Google Code-In? ==<br /> <br /> Pre-university students ages 13 to 17 are invited to take part in Google Code-in: Our global, online, contest introducing teenagers to the world of open source. With a wide variety of bite-sized tasks, it’s easy for beginners to jump in and get started no matter what skills they have. Mentors from our participating organizations lend a helping hand as participants learn what it’s like to work on an open source project. For more details, see [https://developers.google.com/open-source/gci/ Google Code-In] main page. <br /> <br /> == How does it work? ==<br /> <br /> # Students search for a '''task''' that interests them and claim it. They have at least ''three days and up to five'' to complete it.<br /> # The student works on the task, getting guidance from mentors, if needed.<br /> # Once the student has finished, he/she submits the work for review through the contest website.<br /> # Mentors from the organization evaluate the work, provide feedback, and if it's complete, accept it! Otherwise, specific feedback is provided, and the student goes back to step #2!<br /> # Go to step #1 and repeat!<br /> <br /> More details can be found at: [https://developers.google.com/open-source/gci/how-it-works https://developers.google.com/open-source/gci/how-it-works]<br /> <br /> == Tasks ==<br /> <br /> The organizations should create a large list of short (3-5 hour) tasks for students to work on. Tasks are categorized as: Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface. Some examples of tasks of different categories can be found [https://developers.google.com/open-source/gci/resources/example-tasks here].<br /> <br /> == Details about the tasks and lessons learnt ==<br /> <br /> * Translations are not allowed by Google Code In as tasks.<br /> <br /> * A strategic plan is needed to generate a pool of tasks doable in 3-5 hours (from beginner to advanced tasks); '''from ~50 up to ~100 tasks!!'''<br /> <br /> * A '''large mentor pool''' that can tackle evaluations of about ~ 100 tasks!! Importantly, the revision of tasks should be rather quick, since the students should complete as many tasks as possible to win the contest.<br /> <br /> = Available mentors =<br /> List of available mentors to follow the tasks<br /> <br /> * [[User:Veroandreo|Veronica Andreo]]<br /> * [[User:Lucadelu|Luca Delucchi]]<br /> * ...<br /> <br /> Note: To sign up as a mentor, write an email to: gsoc-admin@osgeo.org.<br /> <br /> = Results =<br /> <br /> == Commits related to CGI 2017 ==<br /> * improvements in {{cmd|i.albedo}} manual {{rev|71903}} {{rev|71904}} {{rev|71904}}<br /> * added examples to {{cmd|r.support}} {{rev|71906}} {{rev|71907}} {{rev|71908}}<br /> * added screenshot to {{cmd|d.rgb}} {{rev|71924}} {{rev|71925}} {{rev|71926}}<br /> * added screenshot to {{cmd|d.mon}} {{rev|71927}} {{rev|71928}} {{rev|71929}}<br /> * added screenshots to {{cmd|d.grid}} {{rev|71930}} {{rev|71931}} {{rev|71932}}<br /> * added screenshots to {{cmd|d.rast}} {{rev|71947}} {{rev|71948}} {{rev|71949}}<br /> <br /> == Videos ==<br /> === How to create a location ===<br /> * https://www.youtube.com/watch?v=trvy0B0Qz78<br /> <br /> == Design a splash screen for GRASS GIS GUI start-up ==<br /> * added tfang version {{rev|71941}}<br /> <br /> &lt;!-- Please, edit this page and add further info --&gt;<br /> <br /> [[Category: Development]]<br /> [[Category: Community]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GCI_Ideas_2017&diff=24919 2017-12-16T06:48:15Z

<p>Lucadelu: </p> <hr /> <div>&lt;center&gt;<br /> [[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]]&lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:GCI-logo.jpg|300px|link=https://developers.google.com/open-source/gci/]] &lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]<br /> &lt;/center&gt;<br /> <br /> = About =<br /> <br /> This is the GRASS page for [https://wiki.osgeo.org/wiki/Google_Code_In_2017 Google Code-In] 2017. Here we will list task ideas and other information related to the GRASS GCI projects.<br /> <br /> == What is Google Code-In? ==<br /> <br /> Pre-university students ages 13 to 17 are invited to take part in Google Code-in: Our global, online, contest introducing teenagers to the world of open source. With a wide variety of bite-sized tasks, it’s easy for beginners to jump in and get started no matter what skills they have. Mentors from our participating organizations lend a helping hand as participants learn what it’s like to work on an open source project. For more details, see [https://developers.google.com/open-source/gci/ Google Code-In] main page. <br /> <br /> == How does it work? ==<br /> <br /> # Students search for a '''task''' that interests them and claim it. They have at least ''three days and up to five'' to complete it.<br /> # The student works on the task, getting guidance from mentors, if needed.<br /> # Once the student has finished, he/she submits the work for review through the contest website.<br /> # Mentors from the organization evaluate the work, provide feedback, and if it's complete, accept it! Otherwise, specific feedback is provided, and the student goes back to step #2!<br /> # Go to step #1 and repeat!<br /> <br /> More details can be found at: [https://developers.google.com/open-source/gci/how-it-works https://developers.google.com/open-source/gci/how-it-works]<br /> <br /> == Tasks ==<br /> <br /> The organizations should create a large list of short (3-5 hour) tasks for students to work on. Tasks are categorized as: Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface. Some examples of tasks of different categories can be found [https://developers.google.com/open-source/gci/resources/example-tasks here].<br /> <br /> == Details about the tasks and lessons learnt ==<br /> <br /> * Translations are not allowed by Google Code In as tasks.<br /> <br /> * A strategic plan is needed to generate a pool of tasks doable in 3-5 hours (from beginner to advanced tasks); '''from ~50 up to ~100 tasks!!'''<br /> <br /> * A '''large mentor pool''' that can tackle evaluations of about ~ 100 tasks!! Importantly, the revision of tasks should be rather quick, since the students should complete as many tasks as possible to win the contest.<br /> <br /> = Available mentors =<br /> List of available mentors to follow the tasks<br /> <br /> * [[User:Veroandreo|Veronica Andreo]]<br /> * [[User:Lucadelu|Luca Delucchi]]<br /> * ...<br /> <br /> Note: To sign up as a mentor, write an email to: gsoc-admin@osgeo.org.<br /> <br /> = Results =<br /> <br /> == Commits related to CGI 2017 ==<br /> * improvements in {{cmd|i.albedo}} manual {{rev|71903}} {{rev|71904}} {{rev|71904}}<br /> * added examples to {{cmd|r.support}} {{rev|71906}} {{rev|71907}} {{rev|71908}}<br /> * added screenshot to {{cmd|d.rgb}} {{rev|71924}} {{rev|71925}} {{rev|71926}}<br /> * added screenshot to {{cmd|d.mon}} {{rev|71927}} {{rev|71928}} {{rev|71929}}<br /> * added screenshot to {{cmd|d.grid}} {{rev|71930}} {{rev|71931}} {{rev|71932}}<br /> <br /> == Videos ==<br /> === How to create a location ===<br /> * https://www.youtube.com/watch?v=trvy0B0Qz78<br /> <br /> == Design a splash screen for GRASS GIS GUI start-up ==<br /> * added tfang version {{rev|71941}}<br /> <br /> &lt;!-- Please, edit this page and add further info --&gt;<br /> <br /> [[Category: Development]]<br /> [[Category: Community]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GCI_Ideas_2017&diff=24908 2017-12-13T00:25:30Z

<p>Lucadelu: </p> <hr /> <div>&lt;center&gt;<br /> [[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]]&lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:GCI-logo.jpg|300px|link=https://developers.google.com/open-source/gci/]] &lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]<br /> &lt;/center&gt;<br /> <br /> = About =<br /> <br /> This is the GRASS page for [https://wiki.osgeo.org/wiki/Google_Code_In_2017 Google Code-In] 2017. Here we will list task ideas and other information related to the GRASS GCI projects.<br /> <br /> == What is Google Code-In? ==<br /> <br /> Pre-university students ages 13 to 17 are invited to take part in Google Code-in: Our global, online, contest introducing teenagers to the world of open source. With a wide variety of bite-sized tasks, it’s easy for beginners to jump in and get started no matter what skills they have. Mentors from our participating organizations lend a helping hand as participants learn what it’s like to work on an open source project. For more details, see [https://developers.google.com/open-source/gci/ Google Code-In] main page. <br /> <br /> == How does it work? ==<br /> <br /> # Students search for a '''task''' that interests them and claim it. They have at least ''three days and up to five'' to complete it.<br /> # The student works on the task, getting guidance from mentors, if needed.<br /> # Once the student has finished, he/she submits the work for review through the contest website.<br /> # Mentors from the organization evaluate the work, provide feedback, and if it's complete, accept it! Otherwise, specific feedback is provided, and the student goes back to step #2!<br /> # Go to step #1 and repeat!<br /> <br /> More details can be found at: [https://developers.google.com/open-source/gci/how-it-works https://developers.google.com/open-source/gci/how-it-works]<br /> <br /> == Tasks ==<br /> <br /> The organizations should create a large list of short (3-5 hour) tasks for students to work on. Tasks are categorized as: Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface. Some examples of tasks of different categories can be found [https://developers.google.com/open-source/gci/resources/example-tasks here].<br /> <br /> == Details about the tasks and lessons learnt ==<br /> <br /> * Translations are not allowed by Google Code In as tasks.<br /> <br /> * A strategic plan is needed to generate a pool of tasks doable in 3-5 hours (from beginner to advanced tasks); '''from ~50 up to ~100 tasks!!'''<br /> <br /> * A '''large mentor pool''' that can tackle evaluations of about ~ 100 tasks!! Importantly, the revision of tasks should be rather quick, since the students should complete as many tasks as possible to win the contest.<br /> <br /> = Available mentors =<br /> List of available mentors to follow the tasks<br /> <br /> * [[User:Veroandreo|Veronica Andreo]]<br /> * [[User:Lucadelu|Luca Delucchi]]<br /> * ...<br /> <br /> Note: To sign up as a mentor, write an email to: gsoc-admin@osgeo.org.<br /> <br /> = Results =<br /> <br /> == Commits related to CGI 2017 ==<br /> * improvements in i.albedo manual {{rev|71903}} {{rev|71904}} {{rev|71904}}<br /> * added examples to r.support {{rev|71906}} {{rev|71907}} {{rev|71908}}<br /> * added screenshot to r.rgb {{rev|71924}} {{rev|71925}} {{rev|71926}}<br /> <br /> == Design a splash screen for GRASS GIS GUI start-up ==<br /> <br /> <br /> &lt;!-- Please, edit this page and add further info --&gt;<br /> <br /> [[Category: Development]]<br /> [[Category: Community]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GCI_Ideas_2017&diff=24907 2017-12-12T07:39:01Z

<p>Lucadelu: added first results of GCI 2017</p> <hr /> <div>&lt;center&gt;<br /> [[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]]&lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:GCI-logo.jpg|300px|link=https://developers.google.com/open-source/gci/]] &lt;font size=&quot;+3&quot;&gt; @ &lt;/font&gt; [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]<br /> &lt;/center&gt;<br /> <br /> = About =<br /> <br /> This is the GRASS page for [https://wiki.osgeo.org/wiki/Google_Code_In_2017 Google Code-In] 2017. Here we will list task ideas and other information related to the GRASS GCI projects.<br /> <br /> == What is Google Code-In? ==<br /> <br /> Pre-university students ages 13 to 17 are invited to take part in Google Code-in: Our global, online, contest introducing teenagers to the world of open source. With a wide variety of bite-sized tasks, it’s easy for beginners to jump in and get started no matter what skills they have. Mentors from our participating organizations lend a helping hand as participants learn what it’s like to work on an open source project. For more details, see [https://developers.google.com/open-source/gci/ Google Code-In] main page. <br /> <br /> == How does it work? ==<br /> <br /> # Students search for a '''task''' that interests them and claim it. They have at least ''three days and up to five'' to complete it.<br /> # The student works on the task, getting guidance from mentors, if needed.<br /> # Once the student has finished, he/she submits the work for review through the contest website.<br /> # Mentors from the organization evaluate the work, provide feedback, and if it's complete, accept it! Otherwise, specific feedback is provided, and the student goes back to step #2!<br /> # Go to step #1 and repeat!<br /> <br /> More details can be found at: [https://developers.google.com/open-source/gci/how-it-works https://developers.google.com/open-source/gci/how-it-works]<br /> <br /> == Tasks ==<br /> <br /> The organizations should create a large list of short (3-5 hour) tasks for students to work on. Tasks are categorized as: Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface. Some examples of tasks of different categories can be found [https://developers.google.com/open-source/gci/resources/example-tasks here].<br /> <br /> == Details about the tasks and lessons learnt ==<br /> <br /> * Translations are not allowed by Google Code In as tasks.<br /> <br /> * A strategic plan is needed to generate a pool of tasks doable in 3-5 hours (from beginner to advanced tasks); '''from ~50 up to ~100 tasks!!'''<br /> <br /> * A '''large mentor pool''' that can tackle evaluations of about ~ 100 tasks!! Importantly, the revision of tasks should be rather quick, since the students should complete as many tasks as possible to win the contest.<br /> <br /> = Available mentors =<br /> List of available mentors to follow the tasks<br /> <br /> * [[User:Veroandreo|Veronica Andreo]]<br /> * [[User:Lucadelu|Luca Delucchi]]<br /> * ...<br /> <br /> Note: To sign up as a mentor, write an email to: gsoc-admin@osgeo.org.<br /> <br /> = Results =<br /> <br /> == Commits related to CGI 2017 ==<br /> * improvements in i.albedo manual {{rev|71903}} {{rev|71904}} {{rev|71904}}<br /> * added examples to r.support {{rev|71906}} {{rev|71907}} {{rev|71908}}<br /> <br /> == Design a splash screen for GRASS GIS GUI start-up ==<br /> <br /> <br /> &lt;!-- Please, edit this page and add further info --&gt;<br /> <br /> [[Category: Development]]<br /> [[Category: Community]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GIS_Budget_2018&diff=24813 2017-10-24T05:59:56Z

<p>Lucadelu: /* Expenses */</p> <hr /> <div>''Note: all numbers are written as is in the page. Please edit sums and totals accordingly. Or use LibreOffice/Excel and convert with &lt;nowiki&gt;http://excel2wiki.net&lt;/nowiki&gt;''<br /> <br /> '''--- DRAFT ---'''<br /> <br /> Currency: Euro<br /> <br /> == Income ==<br /> {| {{table}}<br /> | align=&quot;center&quot; style=&quot;background:#f0f0f0;&quot;|'''Source'''<br /> | align=&quot;center&quot; style=&quot;background:#f0f0f0;&quot;|'''Amount'''<br /> | align=&quot;center&quot; style=&quot;background:#f0f0f0;&quot;|'''Notes'''<br /> |-<br /> | [[GRASS GIS Budget 2017|Surplus from 2017]] || TBD ||<br /> |-<br /> | Donations || ... ||<br /> |-<br /> | '''Total''' || '''x''' ||<br /> |-<br /> |}<br /> <br /> == Expenses ==<br /> <br /> {| {{table}}<br /> | align=&quot;center&quot; style=&quot;background:#f0f0f0;&quot;|'''Source'''<br /> | align=&quot;center&quot; style=&quot;background:#f0f0f0;&quot;|'''Amount'''<br /> | align=&quot;center&quot; style=&quot;background:#f0f0f0;&quot;|'''Notes'''<br /> |-<br /> | '''Administration'''<br /> |-<br /> | Bank fees (base pkg, wire fees, paypal feels, etc.) || ... ||<br /> |-<br /> | '''Events'''<br /> |-<br /> | [[GRASS GIS Community Sprint Bonn 2018]] || ... || <br /> |-<br /> | '''Other'''<br /> |-<br /> | T-shirts funding || ... ||<br /> |-<br /> | Printing of stickers and flyers for events (Community sprint, FOSS4G conferences, EGU, FOSSDEM...)] || ... ||<br /> |-<br /> | '''TOTAL''' || '''x''' ||<br /> |-<br /> |}<br /> <br /> <br /> [[Category: Budget]]<br /> [[Category: 2017]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GCI_Ideas_2017&diff=24774 2017-10-02T21:25:10Z

<p>Lucadelu: added mentors section</p> <hr /> <div>= About =<br /> <br /> This is the GRASS page for [https://wiki.osgeo.org/wiki/Google_Code_In_2017 Google Code In] 2017. Here we will list task ideas and other information related to the GRASS GCI projects.<br /> <br /> = Ideas for tasks =<br /> <br /> Some ideas collected so far:<br /> <br /> * Create a screenshot for the next 74 release announcement <br /> * Design the t-shirt for the next code-sprint<br /> * Add examples to manual pages<br /> * Make a promo video for GRASS GIS<br /> * Make new tutorial videos for GRASS GIS<br /> * Enhance the visual index<br /> * Make screenshots to populate the visual change log in new features pages (e.g., for [https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures74 New Features GRASS 7.4])<br /> * Create icons/phrases to include in sticker sheets<br /> * Give a talk about GRASS GIS to classmates<br /> * Submit a patch for a certain bug or enhancement ticket<br /> * Contribute tests for modules<br /> * ''add your own idea...''<br /> <br /> == Details about the tasks ==<br /> <br /> There should be some very simple and introductory tasks such as installing GRASS GIS and making a screenshot, intermediate tasks, and more advanced ones as those involving a bit (more) of coding. A certain large task might also be split into smaller tasks.<br /> <br /> Those general ideas like &quot;make examples for manual pages&quot; might then be replicated for several modules, for example, and each one will constitute a task.<br /> <br /> Translations are not allowed by Google Code In as tasks.<br /> <br /> = Available mentors =<br /> List of available mentors to follow the tasks<br /> <br /> * [[User:Veroandreo|Veronica Andreo]]<br /> * [[User:Lucadelu|Luca Delucchi]]<br /> * ...<br /> <br /> &lt;!-- Please, edit this page and add further info --&gt;</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GIS_Community_Sprint_Bonn_2018&diff=24745 2017-09-10T07:13:37Z

<p>Lucadelu: improved page</p> <hr /> <div>{{toc|right}}<br /> <br /> The GRASS community will join the general OSGeo Code Sprint in BaseCamp Bonn, following the annual FOSSGIS conference (German Speaking Local OSGeo Chapter conference from 18 - 25 March 2018 in Bonn, Germany)<br /> <br /> == Timing, Venue ==<br /> <br /> '''OSGeo Code Sprint 2018 in BaseCamp Bonn, Germany, from 18 - 25 March 2018'''<br /> <br /> == Sponsors ==<br /> <br /> Please check more info on the Bonn Code Sprint 2018.<br /> <br /> We also welcome direct '''financial contributions''' 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<br /> <br /> :::'''sponsoring the GRASS project''' at '''[http://grass.osgeo.org/donations http://grass.osgeo.org/donations]'''<br /> <br /> Note that it is also possible to &lt;b&gt;buy a round of beer for the developers with a quick click&lt;/b&gt; using the PayPal &quot;Buy [pizza/beer/...] Now&quot; button [[Image:Btn_donate_SM.gif|center|link=http://grass.osgeo.org/donations/]]<br /> <br /> For any questions, please contact [[User:Neteler|Markus Neteler]] &lt;tt&gt;&lt;neteler at osgeo.org&gt;&lt;/tt&gt;. Any surplus at the end of the event will be turned over to the GRASS GIS project.<br /> <br /> This GRASS GIS 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.<br /> This Bonn event is especially interesting since '''important OSGeo projects come together'''!<br /> <br /> <br /> <br /> == Agenda - What we plan to do ==<br /> <br /> === Move to GIT ===<br /> * Choose between different ways: OSGeo Git, Github, GitLab<br /> * Participant are invited to study GIT before :-)<br /> <br /> == Planned participation ==<br /> <br /> For organizational reasons, please '''additionally register''' at: https://wiki.osgeo.org/wiki/OSGeo_Code_Sprint_2018#Participants<br /> <br /> === In person ===<br /> <br /> Please add your name here or contact [[User:Lucadelu|Luca Delucchi]] &lt;tt&gt;&lt;lucadeluge at gmail com&gt;&lt;/tt&gt;:<br /> <br /> {|class=&quot;wikitable sortable&quot; border=&quot;2&quot; cellspacing=&quot;0&quot; cellpadding=&quot;4&quot; rules=&quot;all&quot; style=&quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;&quot; <br /> |width=50px|'''No'''<br /> |width=130px|'''Participant '''<br /> |width=100px|'''Country'''<br /> |width=100px|'''Arrival'''<br /> |width=100px|'''Departure'''<br /> |'''Topic'''<br /> |width=75px|'''T-Shirt'''<br /> |'''Notes'''<br /> |-<br /> |1<br /> |<br /> |<br /> |<br /> |<br /> | <br /> |<br /> |<br /> |-<br /> |}<br /> <br /> === Via IRC chat ===<br /> <br /> (IRC is a nice archaic chat system, see [[IRC]])<br /> <br /> {|class=&quot;wikitable sortable&quot; border=&quot;2&quot; cellspacing=&quot;0&quot; cellpadding=&quot;4&quot; rules=&quot;all&quot; style=&quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;&quot; <br /> |width=50px|'''No'''<br /> |width=130px|'''Participant '''<br /> |width=100px|'''Country'''<br /> |-<br /> |Add<br /> |your<br /> |self..<br /> |-<br /> |}<br /> <br /> == Individual Preparation ==<br /> <br /> * Bring your own computer<br /> * Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:Schuko_plug_and_socket.png Germany]). See also http://www.power-plugs-sockets.com/<br /> * Install subversion and the compiler tools, and come with a working GRASS development environment if possible.<br /> <br /> == Photos ==<br /> <br /> We have to remember to take at least one group photo! :-)<br /> <br /> == Reports ==<br /> <br /> See [[Talk:GRASS_Community_Sprint_Bonn_2018]]<br /> <br /> == FAQ ==<br /> <br /> * ''Is the GRASS Community Sprint just a coding event?''<br /> ** 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.<br /> ** 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<br /> * ''Is the GRASS Community Sprint for developers only?''<br /> ** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.<br /> * ''Where can I get help and more information about the community sprint?''<br /> ** Contact [[User:Lucadelu|Luca Delucchi]] &lt;tt&gt;&lt;lucadeluge at gmail com&gt;&lt;/tt&gt;<br /> <br /> [[Category: Workshops]]<br /> [[Category: Code Sprint]]<br /> [[Category: 2018]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GIS_Community_Sprint_Bonn_2018&diff=24643 2017-08-02T06:23:59Z

<p>Lucadelu: /* Timing, Venue */</p> <hr /> <div>{{toc|right}}<br /> <br /> The GRASS community will join the general OSGeo-CodeSprint in BaseCamp Bonn, following the annual FOSSGIS conference (German Speaking Local OSGeo Chapter conference from 21 - 23 March 2018 in Bonn, Germany)<br /> <br /> == Timing, Venue ==<br /> <br /> '''OSGeo-CodeSprint in BaseCamp Bonn, Germany, from 19 - 25 March 2018'''<br /> <br /> == Sponsors ==<br /> <br /> Please check more info on the Bonn Code Sprint 2018.<br /> <br /> We also welcome direct '''financial contributions''' 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<br /> <br /> :::'''sponsoring the GRASS project''' at '''[http://grass.osgeo.org/donations http://grass.osgeo.org/donations]'''<br /> <br /> Note that it is also possible to &lt;b&gt;buy a round of beer for the developers with a quick click&lt;/b&gt; using the PayPal &quot;Buy [pizza/beer/...] Now&quot; button [[Image:Btn_donate_SM.gif|center|link=http://grass.osgeo.org/donations/]]<br /> <br /> For any questions, please contact [[User:Neteler|Markus Neteler]] &lt;tt&gt;&lt;neteler at osgeo.org&gt;&lt;/tt&gt;. Any surplus at the end of the event will be turned over to the GRASS GIS project.<br /> <br /> This GRASS GIS 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.<br /> <br /> This Bonn event is especially interesting since '''important OSGeo projects come together'''!<br /> <br /> == Agenda - What we plan to do ==<br /> <br /> [[Category: Workshops]]<br /> [[Category: Code Sprint]]<br /> [[Category: 2018]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_GIS_Community_Sprint_Bonn_2018&diff=24290 2017-06-23T09:53:52Z

<p>Lucadelu: created page for code sprint in Bonn 2018</p> <hr /> <div>{{toc|right}}<br /> <br /> The GRASS community will join the [https://wiki.osgeo.org/wiki/Paris_Code_Sprint_2016 Paris Code Sprint 2016] organized by [http://www.osgeo.org OSGeo].<br /> <br /> == Timing, Venue ==<br /> <br /> Please refer to the main page of the code sprint in the OSGeo wiki, this page will be only used for the GRASS GIS Agenda.<br /> <br /> == Sponsors ==<br /> <br /> Please check more info on the Bonn Code Sprint 2018.<br /> <br /> We also welcome direct '''financial contributions''' 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<br /> <br /> :::'''sponsoring the GRASS project''' at '''[http://grass.osgeo.org/donations http://grass.osgeo.org/donations]'''<br /> <br /> Note that it is also possible to &lt;b&gt;buy a round of beer for the developers with a quick click&lt;/b&gt; using the PayPal &quot;Buy [pizza/beer/...] Now&quot; button [[Image:Btn_donate_SM.gif|center|link=http://grass.osgeo.org/donations/]]<br /> <br /> For any questions, please contact [[User:Neteler|Markus Neteler]] &lt;tt&gt;&lt;neteler at osgeo.org&gt;&lt;/tt&gt;. Any surplus at the end of the event will be turned over to the GRASS GIS project.<br /> <br /> This GRASS GIS 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.<br /> <br /> This Bonn event is especially interesting since '''important OSGeo projects come together'''!<br /> <br /> == Agenda - What we plan to do ==<br /> <br /> [[Category: Workshops]]<br /> [[Category: Code Sprint]]<br /> [[Category: 2018]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=File:FOSS4G-Europe-2017.png&diff=24181 2017-06-12T09:47:49Z

<p>Lucadelu: </p> <hr /> <div></div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=Global_datasets&diff=24178 2017-06-12T09:22:52Z

<p>Lucadelu: copied Natural Earth also to vector</p> <hr /> <div>= Raster data =<br /> <br /> == Elevation data ==<br /> <br /> === ASTER topography (GDEM V1) ===<br /> <br /> Improved ASTER GDEM 1 from 2009:<br /> <br /> GDEM global 30m elevation calculated from stereo-pair images collected by the Terra satellite.<br /> ''&quot;This is the most complete, consistent global digital elevation data yet made available to the world.&quot;''<br /> This is a very new dataset, at version 1 (treat as ''experimental''). Accuracy will be improved in forthcoming versions (validation with SRTM, etc.; [http://blog.neteler.org/aster-gdem-30m-quality-assessment/ see assessment here] and [http://www.viewfinderpanoramas.org/reviews.html#aster here]).<br /> <br /> * ''[https://lpdaac.usgs.gov/lpdaac/about/news_archive/monday_june_22_20092 pre-release announcement]''<br /> * [http://www.nasa.gov/home/hqnews/2009/jun/HQ_09-150_ASTER_Topographic_Map.html NASA press release]<br /> * [https://wist.echo.nasa.gov/~wist/api/imswelcome/ Warehouse Inventory Search Tool] or [http://www.gdem.aster.ersdac.or.jp/search.jsp Easy search tool] (Data download)<br /> <br /> '''Tutorial:''' [[ASTER topography]]<br /> <br /> ''See also: [http://blog.neteler.org/aster-gdem-30m-quality-assessment/ ASTER GDEM 30m quality assessment]''<br /> <br /> === ASTER topography (GDEM V2) ===<br /> <br /> Improved ASTER GDEM 2 from 2011:<br /> * https://lpdaac.usgs.gov/products/aster_products_table/astgtm<br /> <br /> The ASTER GDEM covers land surfaces between 83°N and 83°S and is comprised of 22,702 tiles. Tiles that contain at least 0.01% land area are included. The ASTER GDEM is distributed as Geographic Tagged Image File Format (GeoTIFF) files with geographic coordinates (latitude, longitude). The data are posted on a '''1 arc-second''' (approximately '''30–m at the equator''') grid and referenced to the 1984 World Geodetic System (WGS84)/ 1996 Earth Gravitational Model (EGM96) geoid. <br /> <br /> '''Notes:''' this DEM can be rather well filtered and smoothed with the [http://personalpages.manchester.ac.uk/staff/neil.mitchell/mdenoise/ Sun's denoising algorithm] (using GDAL and free / open source program &lt;mdenoise&gt; or simply GRASS add-on {{AddonCmd|r.denoise}}.<br /> <br /> Experiments showed that the best smoothing of ASTER GDEM 2 is reached with such parameters of &lt;mdenoise&gt;:<br /> * threshold = 0.8<br /> * iterations = 10-20<br /> <br /> Also filtering with {{cmd|r.neighbors}} by &quot;average&quot; method and window size &gt;=5 is quite useful to remove some noise from DEM.<br /> <br /> ''See also: [http://www.isprs2012.org/abstract/299.asp Validation of the ASTER Global Digital Elevation Model Version 2 over the Conterminous United States]''<br /> <br /> === ACE2 ===<br /> <br /> The ACE2 Global Digital Elevation Model is available at 3&quot;, 30&quot; and 5' spatial resolutions.<br /> <br /> * http://tethys.eaprs.cse.dmu.ac.uk/ACE2/<br /> <br /> Import example:<br /> r.in.bin -f input=&quot;00N105E_3S.ACE2&quot; output=&quot;ACE2_00N105E&quot; bytes=4 \<br /> order=&quot;native&quot; north=15 south=0 east=120 west=105 \<br /> rows=18000 cols=18000<br /> <br /> === CleanTOPO2 (DEM) ===<br /> <br /> * [http://www.shadedrelief.com/cleantopo2/ CleanTOPO2 download]: Edited SRTM30 Plus World Elevation Data<br /> <br /> Import in GRASS:<br /> r.in.gdal CleanTOPO2.tif out=cleanTOPO2.tmp -l -o<br /> g.region rast=cleanTOPO2 -p -g<br /> # rescale from odd integer values to true world values<br /> r.rescale cleanTOPO2.tmp out=cleanTOPO2 to=-10701,8248<br /> r.colors cleanTOPO2_final col=terrain<br /> <br /> [[Image:CleanTOPO2_map.png|thumb|center|300px|Rescaled ClearTOPO2 map]]<br /> <br /> === EGM2008 Geoid Data (Earth Gravitational Model) ===<br /> <br /> Global 2.5 Minute Geoid Undulations:<br /> * download GIS Format at http://earth-info.nga.mil/GandG/wgs84/gravitymod/egm2008/egm08_gis.html<br /> <br /> [[Image:Trentino_egm2008_map_5m_resampled.jpg|thumb|center|300px|Geoid undulations in Trentino, Italy]]<br /> <br /> Verifications of points can be done with the http://geographiclib.sourceforge.net/cgi-bin/GeoidEval<br /> <br /> === ETOPO (DEM) ===<br /> <br /> The ETOPO datasets provide global topography and bathymetry at 1', 2', and 5' per-cell resolutions.<br /> <br /> ==== ETOPO1 (DEM) ====<br /> <br /> * http://www.ngdc.noaa.gov/mgg/global/<br /> <br /> * '''The ''cell registered'' version can be loaded directly into a lat/lon location'''. GRASS raster data is cell registered (see the [[GRASS raster semantics]] page)<br /> <br /> <br /> * Special care must be taken with the ''grid registered'' version. It can not be loaded directly into a lat/lon location as the parameters found in the .hdr file exceed the limits of polar coordinate space: they have N,S rows which go 1/2 a cell beyond 90 latitude, when considered in the ''cell registered'' convention.<br /> : So the data needs to have those 90deg N,S rows cropped away, and while we're at it we crop away a redundant overlapping column at 180 longitude. To do this we have to first tell the GIS a little fib during import to squeeze the data into lat/lon space, then crop away the spurious rows and column, then finally reset the resulting map's bounds to its true extent.<br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> # Import grid registered binary float, fibbing about its true extent<br /> r.in.bin -f in=etopo1_bed_g.flt out=etopo1_bed_g.raw \<br /> n=90 s=-90 e=180 w=-180 rows=10801 cols=21601 anull=-9999<br /> <br /> # reduce the working region by 1 cell<br /> g.region rast=etopo1_bed_g.raw<br /> eval `g.region -g`<br /> g.region n=n-$nsres s=s+$nsres e=e-$ewres -p<br /> <br /> # save smaller raster and remove original<br /> r.mapcalc &quot;etopo1_bed_g.crop = etopo1_bed_g.raw&quot;<br /> g.remove etopo1_bed_g.raw<br /> <br /> # re-establish the correct bounds, now that they'll fit<br /> r.region etopo1_bed_g.crop n=89:59:30N s=89:59:30S w=179:59:30E e=179:59:30E<br /> g.region rast=etopo1_bed_g.crop<br /> <br /> # check that N,S,E,W and Res are all nice and clean:<br /> r.info etopo1_bed_g.crop<br /> <br /> # looks good, so accept the results by resetting the map name<br /> g.rename etopo1_bed_g.crop,etopo1_bed_g<br /> <br /> # set to use appropriate color rules<br /> r.colors etopo1_bed_g color=etopo2<br /> <br /> # set the 'units' metadata field (for elevation data contained within the map)<br /> r.support etopo1_bed_g units=meters<br /> &lt;/source&gt;<br /> <br /> * For the problematic ''grid registered'' version, the resulting {{cmd|r.info}} report should look like:<br /> | Rows: 10799 |<br /> | Columns: 21600 |<br /> | Total Cells: 233258400 |<br /> | Projection: Latitude-Longitude |<br /> | N: 89:59:30N S: 89:59:30S Res: 0:01 |<br /> | E: 179:59:30E W: 179:59:30E Res: 0:01 |<br /> | Range of data: min = -10898 max = 8271 |<br /> (the east and west bounds of the map touch 1/2 a cell west of 180 longitude)<br /> <br /> * For the problematic ''grid registered'' version, since the data's grid is 1/2 a cell shifted from nicely rounded 1 arc-minutes (0:01), you'll need to ensure that the mapset's region preserves that alignment after zooming or panning:<br /> g.region align=etopo1_bed_g -p<br /> : (or oversample and set the region resolution to 1/2 arc-minutes (0:00:30), which will be four times as slow)<br /> <br /> ==== ETOPO2 (DEM) ====<br /> <br /> * See the ETOPO2 (2' global) article by M.H. Bowman in the [http://grass.osgeo.org/newsletter/GRASSNews_vol1.pdf GRASS Newsletter, 1:8-11, August 2004].<br /> : [http://www.ngdc.noaa.gov/mgg/fliers/01mgg04.html ETOPO2v2 data download] (take for example the ETOPO2v2g_f4_LSB.flt file)<br /> <br /> === GTOPO30 (DEM) ===<br /> <br /> * Data [http://eros.usgs.gov/#/Find_Data/Products_and_Data_Available/gtopo30_info download] - Import with {{cmd|r.in.gdal}}.<br /> <br /> ''Note:'' To avoid that the GTOPO30 data are read incorrectly, you can add a new line &quot;PIXELTYPE SIGNEDINT&quot; in the .HDR to force interpretation of the file as signed rather than unsigned integers. Then the .DEM file can be imported. Finally, e.g. the 'terrain' color table can be assigned to the imported map with r.colors.<br /> <br /> <br /> === Global Multi-resolution Terrain Elevation Data 2010 (GMTED2010) ===<br /> <br /> * Data download: [https://lta.cr.usgs.gov/GMTED2010 Web] and [http://topotools.cr.usgs.gov/GMTED_viewer/gmted2010_global_grids.php FTP] - Import with {{cmd|r.in.gdal}}. See also [https://erouault.blogspot.de/2011/12/seamless-access-to-remote-global-multi.html related GDAL blog post]<br /> <br /> Tiles: Import of GMTED2010 tiles in GRASS GIS:<br /> <br /> r.in.gdal 30N000E_20101117_gmted_mea075.tif out=gmted2010_30N000E_20101117<br /> r.colors gmted2010_30N000E_20101117 color=elevation<br /> g.region rast=gmted2010_30N000E_20101117<br /> r.relief input=gmted2010_30N000E_20101117 output=gmted2010_30N000E_20101117.shade<br /> r.shade shade=gmted2010_30N000E_20101117.shade color=gmted2010_30N000E_20101117 \<br /> output=gmted2010_30N000E_20101117_shaded<br /> d.mon wx0<br /> d.rast gmted2010_30N000E_20101117_shaded<br /> d.grid 1 color=red textcolor=red<br /> <br /> [[Image:Gmted2010_30N000E_20101117_shaded.png|thumb|center|300px|GMTED2010 example: Trento - Garda Lake - Verona area (Northern Italy)]]<br /> <br /> Full maps:<br /> <br /> # mean elevation global GMTED2010 map, 30 arc-sec<br /> wget http://edcintl.cr.usgs.gov/downloads/sciweb1/shared/topo/downloads/GMTED/Grid_ZipFiles/mn30_grd.zip<br /> unzip mn30_grd.zip<br /> <br /> Unfortunately the GMTED2010 map exceeds the -180°..+180° range etc, indicating a shift of the map:<br /> <br /> # the center is not in the center :(<br /> gdalinfo mn30_grd<br /> ...<br /> Origin = (-180.000138888888927,83.999860415111328)<br /> Pixel Size = (0.008333333300000,-0.008333333300000)<br /> Corner Coordinates:<br /> Upper Left (-180.0001389, 83.9998604) (180d 0' 0.50&quot;W, 83d59'59.50&quot;N)<br /> Lower Left (-180.0001389, -90.0001389) (180d 0' 0.50&quot;W, 90d 0' 0.50&quot;S)<br /> Upper Right ( 179.9998597, 83.9998604) (179d59'59.49&quot;E, 83d59'59.50&quot;N)<br /> Lower Right ( 179.9998597, -90.0001389) (179d59'59.49&quot;E, 90d 0' 0.50&quot;S)<br /> Center ( -0.0001396, -3.0001392) ( 0d 0' 0.50&quot;W, 3d 0' 0.50&quot;S)<br /> ...<br /> <br /> Workaround: Shift the GMTED2010 map slightly into the right position using gdal_translate:<br /> <br /> # coords are shifted, fix raster map<br /> # -a_ullr Assign/override the georeferenced bounds (note: N_max=84N) of the output file<br /> # use larger cache and compress result<br /> gdal_translate --config GDAL_CACHEMAX 1200 -a_ullr -180 84 180 -90 \<br /> -co &quot;COMPRESS=LZW&quot; mn30_grd gmted2010_mn30_grd_fixed.tif<br /> # verify (the center remains slightly shifted but at least the boundaries are now fixed:<br /> gdalinfo gmted2010_mn30_grd_fixed.tif<br /> ...<br /> Upper Left (-180.0000000, 84.0000000) (180d 0' 0.00&quot;W, 84d 0' 0.00&quot;N)<br /> Lower Left (-180.0000000, -90.0000000) (180d 0' 0.00&quot;W, 90d 0' 0.00&quot;S)<br /> Upper Right ( 180.0000000, 84.0000000) (180d 0' 0.00&quot;E, 84d 0' 0.00&quot;N)<br /> Lower Right ( 180.0000000, -90.0000000) (180d 0' 0.00&quot;E, 90d 0' 0.00&quot;S)<br /> Center ( 0.0000000, -3.0000000) ( 0d 0' 0.01&quot;E, 3d 0' 0.00&quot;S)<br /> ...<br /> <br /> This map can now be imported into a LatLong location (or the location be generated from the map itself).<br /> <br /> === GEBCO Bathymetric Chart ===<br /> <br /> * The General Bathymetric Chart of the Oceans (original 1' release 2003, new 1' and 30&quot; releases 2008)<br /> : http://www.gebco.net/data_and_products/gridded_bathymetry_data/<br /> : http://www.bodc.ac.uk/data/online_delivery/gebco/<br /> <br /> {{cmd|r.in.gdal}} can be used to import the GMT netCDF files directly, or if that doesn't work you can use GMT tools to convert to an old-style native GMT format and import that with {{cmd|r.in.bin}}.<br /> : example: (GEBCO 2003 1' data)<br /> <br /> # convert to an old style GMT binary .grd using grdreformat<br /> $ grdreformat 3n24s47w14w.grd 3n24s47w14w_Native.grd=bs<br /> <br /> # then import into GRASS,<br /> GRASS&gt; r.in.bin -h -s bytes=2 in=3n24s47w14w_Native.grd out=3n24s47w14w<br /> <br /> # and set some nice colors<br /> GRASS&gt; r.colors 3n24s47w14w rules=- &lt;&lt; EOF<br /> nv magenta<br /> 0% black<br /> -7740 0:0:168<br /> 0 84:176:248<br /> 0 40:124:0<br /> 522 68:148:24<br /> 1407 148:228:108<br /> 1929 232:228:108<br /> 2028 232:228:92<br /> 2550 228:160:32<br /> 2724 216:116:8<br /> 2730 grey<br /> 2754 grey<br /> 2760 252:252:252<br /> 2874 252:252:252<br /> 2883 192:192:192<br /> 2913 192:192:192<br /> 100% 252:252:252<br /> EOF<br /> <br /> === Global Multi-Resolution Topography (GMRT DEM) ===<br /> : ''From Columbia University's Lamont-Doherty Earth Observatory''<br /> (it is reported that this is what Google Maps uses for their global bathymetry)<br /> <br /> * Global ~1 arc-second (~90 m) topography using multi-beam and satellite data in the oceans combined with SRTM on land.<br /> * Full information at: http://www.marine-geo.org/portals/gmrt/<br /> * Accessible via [http://www.geomapapp.org/ GeoMapApp] or [http://www.virtualocean.org/ Virtual Ocean] software.<br /> * Very convenient to download into GRASS via wget:<br /> <br /> export `g.region -g`<br /> wget &quot;http://www.marine-geo.org/cgi-bin/getgridB?west=${w}&amp;east=${e}&amp;south=${s}&amp;north=${n}&amp;resolution=1&quot; -O /tmp/test.grd<br /> r.in.gdal /tmp/test.grd output=GMRT -o<br /> rm /tmp/test.grd<br /> <br /> * Note: Downloaded file contains no projection information, but is EPSG:4326 (WGS84 Geographic). The file size is limited, but lower resolution (resolution=2,4,8) data can be downloaded for larger areas.<br /> <br /> === Smith and Sandwell DEM ===<br /> <br /> * Merge info here from the [[Marine Science]] wiki page<br /> <br /> === SRTM DEM ===<br /> <br /> [http://www2.jpl.nasa.gov/srtm/ Space Shuttle Radar Topography Mission] - several SRTM Data Products are available:<br /> * Original data - SRTM 3 V001 arc-seconds Non-Void Filled elevation data (US: 1 arc-second (approximately 30 meters); outside the US at 3 arc-seconds (approximately 90 meters))<br /> * SRTM V003 3 Arc-Second Global Void Filled elevation data, with voids filled using interpolation algorithms in conjunction with other sources of elevation data (US: 1 arc-second (approximately 30 meters); outside the US at 3 arc-seconds (approximately 90 meters))<br /> ** SRTM V3 tiles at 3 arc seconds resolution from: http://e4ftl01.cr.usgs.gov/SRTM/SRTMGL3.003/2000.02.11/ - or simply use {{AddonCmd|r.in.srtm.region}}<br /> * '''SRTM V003 1 Arc-Second Global elevation data''' offer worldwide coverage of '''void filled''' data at a resolution of 1 arc-second (30 meters) and provide open distribution of this high-resolution global data set.<br /> ** [http://earthexplorer.usgs.gov/ EarthExplorer] can be used to search, preview, and download Shuttle Radar Topography Mission (SRTM) 1 Arc-Second Global data. The collections are located under the Digital Elevation category.<br /> ** FTP download: http://e4ftl01.cr.usgs.gov/SRTM/SRTMGL1.003/2000.02.11/ - or simply use {{AddonCmd|r.in.srtm.region}}<br /> <br /> Import:<br /> * Using {{cmd|r.in.gdal}} or {{cmd|r.import}} or {{cmd|r.in.srtm}} or {{AddonCmd|r.in.srtm.region}}<br /> * see [[HOWTO import SRTM elevation data]], focused on the SRTM 3 arc-seconds Non-Void Filled elevation data<br /> <br /> === SRTM30plus data DEM ===<br /> <br /> SRTM30plus data consists of 33 files of global topography in the same format as the SRTM30 products distributed by the USGS EROS data center. The grid resolution is 30 seconds which is roughly one kilometer (1 km).<br /> <br /> Land data are based on the 1-km averages of topography derived from the USGS SRTM30 grided DEM data product created with data from the NASA Shuttle Radar Topography Mission. GTOPO30 data are used for high latitudes where SRTM data are not available.<br /> <br /> Ocean data are based on the Smith and Sandwell global 2-minute grid between latitudes +/- 72 degrees. Higher resolution grids have been added from the LDEO Ridge Multibeam Synthesis Project and the NGDC Coastal Relief Model. Arctic bathymetry is from the International Bathymetric Chart of the Oceans (IBCAO).<br /> <br /> All data are derived from public domain sources and these data are also in the public domain.<br /> <br /> GRASS 6 script {{{cmd|r.in.srtm}}} described in GRASSNews vol. 3 won't work with this dataset (as it was made for the original SRTM HGT files). But you can import SRTM30plus tiles into GRASS this way:<br /> <br /> r.in.bin -sb input=e020n40.Bathymetry.srtm output=e020n40_topex bytes=2 \<br /> north=40 south=-10 east=60 west=20 r=6000 c=4800<br /> r.colors e020n40_topex rules=etopo2<br /> <br /> ; Source<br /> : GRASS Users Mailing List http://lists.osgeo.org/pipermail/grass-user/2005-August/030063.html<br /> ; Getting as SRTM30plus tiles: ftp://topex.ucsd.edu/pub/srtm30_plus/srtm30/data/<br /> ; Getting as SRTM30plus huge file: ftp://topex.ucsd.edu/pub/srtm30_plus/topo30/<br /> ; SRTMPLUS WCS server: http://svn.osgeo.org/gdal/trunk/autotest/gdrivers/data/srtmplus.wcs (read with {{cmd|r.external}})<br /> <br /> === SRTM Water Body Database SRTMSWBD V003 ===<br /> <br /> SRTM Water Body Database V003<br /> * Format documentation: https://lpdaac.usgs.gov/dataset_discovery/measures/measures_products_table/srtmswbd_v003<br /> * FTP raster data (30m res water bodies): http://e4ftl01.cr.usgs.gov/SRTM/SRTMSWBD.003/<br /> <br /> Import into GRASS GIS 7 (lat-long location):<br /> r.in.bin -sb input=N00E108.raw output=N00E108_swbd bytes=1 north=0 south=-10 east=108 west=98 r=3601 c=3601 &lt;&lt;= DRAFT - TODO fix n,s,e,w - calculate from filename<br /> <br /> == Soil data ==<br /> <br /> === Harmonized World Soil Database (HWSD Database) ===<br /> <br /> Download: http://webarchive.iiasa.ac.at/Research/LUC/External-World-soil-database/HTML/<br /> <br /> [http://webarchive.iiasa.ac.at/Research/LUC/External-World-soil-database/HTML/DataDesc.html?sb=12 Spatial reference system:] [http://spatialreference.org/ref/epsg/4326/ EPSG:4326] (LatLong WGS84)<br /> <br /> Import:<br /> grass70 -c EPSG:4326 ~/grassdata/hwsd<br /> # -e: expand location to dataset; -o: override (missing) projection in input dataset:<br /> r.in.gdal input=hwsd.bil output=hwSoil -e -o<br /> g.region raster=hwSoil -p<br /> r.category hwSoil<br /> <br /> The data is distributed with an MSAccess .mdb which contains additional data for each of the categories in the raster file. Opening the file in access, the data is found in the query &quot;HWSD_Q&quot;. Save this query in .csv format (with a name like &quot;HWSD_Q.csv&quot;) so that it may then be imported into GRASS. After that, it is necessary to replace the commas with dots (find &amp; replace) in the .csv file. Before you can import it, you also need a file &quot;HWSD_Q.csvt&quot;, which contains a single line listing the type for each column in the database:<br /> &quot;Integer&quot;,&quot;String&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;String&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;Real&quot;,&quot;Integer&quot;,&quot;String&quot;,&quot;Integer&quot;,&quot;String&quot;,&quot;Integer&quot;,&quot;String&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;Real&quot;,&quot;Real&quot;,&quot;Real&quot;,&quot;Real&quot;,&quot;Real&quot;,&quot;Real&quot;,&quot;Real&quot;,&quot;Real&quot;,&quot;Real&quot;,&quot;Real&quot;,&quot;Real&quot;,&quot;Real&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;Integer&quot;,&quot;Real&quot;,&quot;Real&quot;,&quot;Real&quot;,&quot;Real&quot;,&quot;Real&quot;,&quot;Real&quot;,&quot;Real&quot;,&quot;Real&quot;,&quot;Real&quot;,&quot;Real&quot;,&quot;Real&quot;,&quot;Real&quot;<br /> <br /> <br /> With both the .csv and the .csvt file in the same directory, you can then import them into GRASS:<br /> db.in.ogr input=~/grassdata/hwsd/HWSD_Q.csv output=hwsdData<br /> <br /> The data cannot be connected directly to the raster, it must be converted to a vector first:<br /> g.region raster=hwSoil<br /> r.to.vect -v input=hwSoil output=hwSoil feature=area<br /> v.db.droptable hwSoil<br /> db.droptable -f hwSoil # delete the table completely<br /> <br /> Note that the table includes multiple rows for each polygon, corresponding<br /> to the dominant and various numbers of subdominant soils. To select only<br /> the dominant soil layer:<br /> <br /> db.select table=hwsdData sql='select * from hwsdData where SEQ = 1' \<br /> output=domSoil.csv separator=,<br /> <br /> This saves a copy of the table that contains only the dominant soil type for each polygon as domSoil.csv. This needs to be reloaded into the GRASS database. Since it has the same columns as HWSD_Q.csv, we can use the labels for that file:<br /> <br /> cp HWSD_Q.csvt domSoil.csvt<br /> <br /> Then we can load domSoil.csv:<br /> <br /> db.in.ogr \<br /> input=~/grassdata/downloads/harmonized_world_soil_database/domSoil.csv \<br /> output=domSoil <br /> <br /> Now at last we can connect the database to the vector file:<br /> <br /> v.db.connect -o map=hwsd table=domSoil driver=sqlite key=MU_GLOBAL<br /> <br /> To create a new raster map taking the values from the table:<br /> g.region raster=hwSoil ## make sure we get the whole map<br /> v.to.rast in=hwSoil out=T_SAND col=T_SAND<br /> <br /> === SoilGrids.org 250m soil taxonomy map ===<br /> <br /> SoilGrids is a system for automated soil mapping based on global soil profile and environmental covariate data. SoilGrids represents a collection of updatable soil property and class maps of the world at 1 km and 250 m spatial resolution produced using automated soil mapping based on machine learning algorithms. It aims at becoming OpenStreetMap and/or OpenWeatherMap for soil data. SoilGrids predictions are updated on a regular basis (at least every few months). For more details about the SoilGrids system, please refer to the SoilGrids project site: https://www.soilgrids.org/#/?layer=geonode:taxnwrb_250m<br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> URL=ftp://ftp.soilgrids.org/data/recent/TAXNWRB_250m_ll.tif<br /> <br /> # the Soilgrids GeoTIFF data suffer from a resolution precision problem:<br /> # resolution is stored as 0.002083333000000 while it should be 0.002083333333333, hence the geometry is not fully correct<br /> <br /> export NAME=`basename $URL .tif`<br /> wget $URL<br /> <br /> gdal_translate --config GDAL_CACHEMAX 2000 -a_ullr $COORDS -co &quot;COMPRESS=DEFLATE&quot; $NAME.tif ${NAME}_fixed.tif<br /> gdalinfo ${NAME}_fixed.tif<br /> <br /> grass72 -c ${NAME}_fixed.tif ~/grassdata/latlong --exec r.import input=${NAME}_fixed.tif output=${NAME}<br /> &lt;/source&gt;<br /> <br /> == Landcover data ==<br /> <br /> === ESA Globcover dataset ===<br /> <br /> Download: http://due.esrin.esa.int/page_globcover.php<br /> <br /> Or via command line:<br /> wget http://due.esrin.esa.int/files/Globcover2009_V2.3_Global_.zip<br /> unzip Globcover2009_V2.3_Global_.zip<br /> # rm -f Globcover2009_V2.3_Global_.zip<br /> <br /> Note, also a coloured version of the map in GeoTIFF format is available at: http://due.esrin.esa.int/files/GLOBCOVER_L4_200901_200912_V2.3.color.tif<br /> <br /> Unfortunately the Globcover map exceeds the -180°..+180° range etc, indicating a shift of the map (see also [http://www.cosmo-model.org/content/tasks/workGroups/wg3b/meetings/2012-soilveg/EXTPAR-GLOBCOVER.pdf this assessment by DWD]):<br /> &lt;pre&gt;<br /> gdalinfo GLOBCOVER_L4_200901_200912_V2.3.tif<br /> Driver: GTiff/GeoTIFF<br /> Files: GLOBCOVER_L4_200901_200912_V2.3.tif<br /> Size is 129600, 55800<br /> Coordinate System is:<br /> GEOGCS[&quot;WGS 84&quot;,<br /> ...<br /> Origin = (-180.001388888888897,90.001388888888883)<br /> ...<br /> Corner Coordinates:<br /> Upper Left (-180.0013889, 90.0013889) (180d 0' 5.00&quot;W, 90d 0' 5.00&quot;N)<br /> Lower Left (-180.0013889, -64.9986111) (180d 0' 5.00&quot;W, 64d59'55.00&quot;S)<br /> Upper Right ( 179.9986111, 90.0013889) (179d59'55.00&quot;E, 90d 0' 5.00&quot;N)<br /> Lower Right ( 179.9986111, -64.9986111) (179d59'55.00&quot;E, 64d59'55.00&quot;S)<br /> Center ( -0.0013889, 12.5013889) ( 0d 0' 5.00&quot;W, 12d30' 5.00&quot;N)<br /> ...<br /> &lt;/pre&gt;<br /> <br /> How to fix this?<br /> <br /> '''Option 1:''' You can use the -l flag of {{cmd|r.in.gdal}} to constrain the map coordinates to legal values ([https://pvanb.wordpress.com/2011/05/10/importing-global-rasters-in-grass-gives-me-illegal-latitude-for-north-message/ ref]. But the resulting pixels will no longer have the original resolution. We will not do that.<br /> <br /> '''Option 2:''' Shift the Globcover map slightly into the right position using [http://www.gdal.org/gdal_translate.html gdal_translate]:<br /> <br /> &lt;pre&gt;<br /> # coords are shifted, fix raster map<br /> # -a_ullr Assign/override the georeferenced bounds of the output file<br /> # use larger cache and compress result<br /> gdal_translate --config GDAL_CACHEMAX 1200 -a_ullr -180 90 180 -65 \<br /> -co &quot;COMPRESS=LZW&quot; GLOBCOVER_L4_200901_200912_V2.3.tif GLOBCOVER_L4_200901_200912_V2.3_fixed.tif<br /> <br /> # result:<br /> gdalinfo GLOBCOVER_L4_200901_200912_V2.3_fixed.tif<br /> ...<br /> Origin = (-180.000000000000000,90.000000000000000)<br /> Pixel Size = (0.002777777777778,-0.002777777777778)<br /> ...<br /> Corner Coordinates:<br /> Upper Left (-180.0000000, 90.0000000) (180d 0' 0.00&quot;W, 90d 0' 0.00&quot;N)<br /> Lower Left (-180.0000000, -65.0000000) (180d 0' 0.00&quot;W, 65d 0' 0.00&quot;S)<br /> Upper Right ( 180.0000000, 90.0000000) (180d 0' 0.00&quot;E, 90d 0' 0.00&quot;N)<br /> Lower Right ( 180.0000000, -65.0000000) (180d 0' 0.00&quot;E, 65d 0' 0.00&quot;S)<br /> Center ( 0.0000000, 12.5000000) ( 0d 0' 0.01&quot;E, 12d30' 0.00&quot;N)<br /> &lt;/pre&gt;<br /> <br /> Voilà! Now we can import the map into GRASS GIS:<br /> <br /> r.in.gdal input=GLOBCOVER_L4_200901_200912_V2.3_fixed.tif output=esa_globcover2009<br /> <br /> '''Legend conversion''': The ZIP file contains a XLS table describing the classes and the RGB colors. Using ogr2ogr can directly convert XLS --&gt; CSV:<br /> <br /> ogr2ogr -f CSV Globcover2009_Legend.csv Globcover2009_Legend.xls<br /> <br /> '''Applying the legend:'''<br /> <br /> # suppress table header and only consider category value and label, apply on the fly:<br /> cat Globcover2009_Legend.csv | grep -v '^Value' | cut -d',' -f1-2 | r.category esa_globcover2009 separator=comma rules=-<br /> # verify (0E, 0N is the Atlantic Ocean)<br /> r.what esa_globcover2009 coor=0,0 -f<br /> 0|0||210|Water bodies<br /> <br /> === Global Forest Change ===<br /> <br /> * http://earthenginepartners.appspot.com/science-2013-global-forest <br /> * Download info on: http://earthenginepartners.appspot.com/science-2013-global-forest/download_v1.3.html<br /> <br /> == Imagery ==<br /> <br /> === AVHRR ===<br /> <br /> * see the [[AVHRR]] wiki page<br /> <br /> === Blue Marble imagery ===<br /> <br /> NASA's Blue Marble is a 500m-8 degree per-cell world wide visual image of the Earth from space, with the clouds removed.<br /> <br /> * see the [[Blue Marble]] wiki page<br /> <br /> === EO-1 imagery ===<br /> <br /> (Earth Observing-1)<br /> * &quot;''Advanced Land Imager (ALI) provides image data from ten spectral bands (band designations). The instrument operates in a pushbroom fashion, with a spatial resolution of 30 meters for the multispectral bands and 10 meters for the panchromatic band.''&quot;<br /> :-- http://eros.usgs.gov/products/satellite/eo1.php<br /> * On-board Atmospheric Corrections<br /> <br /> === Global Land Cover Characteristics ===<br /> <br /> USGS ''et al.'' generated dataset at 1km resolution. Provides global landcover characteristics.<br /> <br /> * see the [[Global Land Cover Characteristics]] wiki page<br /> <br /> === LANDSAT imagery ===<br /> <br /> Since October 1, 2008 all Landsat 7 ETM+ scenes held in the [http://landsat.usgs.gov/ USGS EROS archive] are available for download at no charge.<br /> * Download via the [http://glovis.usgs.gov/ Glovis] online search tool (req. Java)<br /> * Download via the USGS's [http://edcsns17.cr.usgs.gov/EarthExplorer/ EarthExplorer] interface<br /> <br /> ==== Import Modules ====<br /> <br /> * {{cmd|r.in.gdal}} - Main import tool for complete multiband scenes<br /> * {{cmd|r.in.wms}} - Download data covering current map region via WMS server<br /> * [[GRASS_AddOns#r.in.onearth|r.in.onearth]] - WMS frontend for NASA's OnEarth Global Landsat Mosaic<br /> <br /> ==== Color balancing modules ====<br /> * {{cmd|i.landsat.rgb}} (GRASS 6.x) | {{cmd|i.colors.enhance|version=70}} (GRASS 7.x) - Color balancing/enhancement tool<br /> <br /> ==== See also ====<br /> <br /> * Processing tips can be found on the [[LANDSAT]] wiki page<br /> <br /> === Miscellaneous ===<br /> <br /> ==== Data sources ====<br /> <br /> * Some datasource links: http://www.ruf.rice.edu/~ben/gmt.html<br /> * [http://www.geotorrent.org/browse.php Geotorrent.org]<br /> <br /> ==== Import Modules ====<br /> * The {{cmd|r.in.gdal}} modules may be used to import data of [http://www.gdal.org/formats_list.html many formats], including GMT netCDF<br /> * The {{cmd|r.in.bin}} module may be used to import raw binary files<br /> <br /> === MODIS imagery ===<br /> <br /> * see the [[MODIS]] wiki page<br /> <br /> === Natural Earth imagery ===<br /> <br /> * [http://www.naturalearthdata.com/ Natural Earth II]: World environment map in natural color. GeoTIFF (use the {{cmd|r.in.gdal}} module)<br /> * see also 1:10 million, 1:50 million and 1:110million scale maps from http://www.naturalearthdata.com/<br /> <br /> === Orthoimagery ===<br /> <br /> * [http://worldwindcentral.com/wiki/Sources_of_free_orthoimagery Sources of free orthoimagery]<br /> <br /> === Pathfinder AVHRR SST imagery ===<br /> <br /> * see the Pathfinder [[AVHRR]] SST wiki page<br /> <br /> === QuickBird imagery ===<br /> <br /> * See the [[QuickBird]] wiki page<br /> <br /> === SeaWiFS imagery ===<br /> <br /> * see the [[SeaWiFS]] wiki page<br /> <br /> === SPOT Vegetation imagery ===<br /> <br /> SPOT Vegetation (1km) global: NDVI data sets<br /> <br /> * [http://free.vgt.vito.be/ SPOT Vegetation (1km, global) NDVI data set server]<br /> * for import, see {{cmd|i.in.spotvgt}}<br /> <br /> === True Marble imagery ===<br /> <br /> * [http://www.unearthedoutdoors.net/global_data/true_marble/download True Marble]: 250m world wide visual image of the Earth from space, with the clouds removed. GeoTIFF (use the {{cmd|r.in.gdal}} module)<br /> <br /> == Climatic data ==<br /> <br /> === OGC WCS - Albedo example ===<br /> <br /> TODO: update this example e.g. to http://demo.mapserver.org/cgi-bin/wcs?SERVICE=wcs&amp;VERSION=1.0.0&amp;REQUEST=GetCapabilities<br /> <br /> GRASS imports OGC Web Coverage Service data. Example server (please suggest a better one!)<br /> &lt;WCS_GDAL&gt;<br /> &lt;ServiceURL&gt;http://laits.gmu.edu/cgi-bin/NWGISS/NWGISS?&lt;/ServiceURL&gt;<br /> &lt;CoverageName&gt;AUTUMN.hdf&lt;/CoverageName&gt;<br /> &lt;Timeout&gt;90&lt;/Timeout&gt;<br /> &lt;Resample&gt;nearest&lt;/Resample&gt;<br /> &lt;/WCS_GDAL&gt;<br /> <br /> Save this as albedo.xml. Import into a LatLong WGS84 location:<br /> r.in.gdal albedo.xml out=albedo<br /> <br /> Unfortunately this server sends out the map shifted by 0.5 pixel. This requires a fix to the map boundary coordinates:<br /> r.region albedo n=90 s=-90 w=-180 e=180<br /> <br /> Now apply color table and look at the map:<br /> r.colors albedo color=byr<br /> d.mon x0<br /> d.rast albedo<br /> <br /> === SNODAS maps ===<br /> <br /> [http://nsidc.org/data/docs/noaa/g02158_snodas_snow_cover_model/index.html Snow Data Assimilation System] data that support hydrological modeling and analysis. First download the data, and untar them (once for each month, and once for each day), and you should get pairs of “.dat” and “.Hdr” files. The data files are stored in flat 16-bit binary format, so assuming that “snowdas_in.dat” is the name of the input file, at the GRASS prompt:<br /> <br /> r.in.bin -bs bytes=2 rows=3351 cols=6935 north=52.874583333332339 \<br /> south=24.949583333333454 east=-66.942083333334011 west=-124.733749999998366 \<br /> anull=-9999 input=snowdas_input.dat output=snowdas<br /> <br /> === CHELSA climate maps ===<br /> <br /> CHELSA – Climatologies at high resolution for the earth’s land surface areas is a high resolution (30 arc sec) climate data set for the earth land surface areas currently under development, see http://chelsa-climate.org/<br /> <br /> Version 1.1 has some coordinate issues originating from the underlying GMTED2010 data being used which come with coordinate issues (see above).<br /> <br /> &lt;source lang=&quot;shell&quot;&gt;<br /> # WARNING: dirty hack - Better wait for the new release V1.2 of CHELSA!<br /> <br /> for i in `ls /scratch/chelsa_climate/*.zip` ; do<br /> unzip $i<br /> NAME=`basename $i .zip`<br /> gdal_translate --config GDAL_CACHEMAX 2000 -a_ullr -180 84 180 -90 -co &quot;COMPRESS=DEFLATE&quot; $NAME.tif ${NAME}_fixed.tif<br /> rm -f $NAME.tif<br /> done<br /> &lt;/source&gt;<br /> <br /> === WorldClim maps ===<br /> <br /> [http://www.worldclim.org/ WorldClim] is a set of global climate layers (climate grids) with a spatial resolution of a square kilometer. Besides long-term average climate layers (representing the period 1950 - 2000) it also includes projections for future conditions based on downscaled global climate model (GCM) data from CMIP5 (IPPC Fifth Assessment) and projections of past conditions (downscaled global climate model output).<br /> * Load into a Lat/Lon WGS84 location (EPSG:4326)<br /> * The data set is provided in two formats: BIL and ESRI Grd. Import with {{cmd|r.in.bin}} or {{cmd|r.in.gdal}}. Version 1.4 has some coordinate issues:<br /> <br /> a) BIL: binary format is 2 byte integer. Multiply by 10 using {{cmd|r.mapcalc}} to convert units. See http://www.worldclim.org/format.htm for more information and the [[MODIS]] help page for example of converting raw to data units. Note that the file header is missing a line. To fix:<br /> <br /> # fix WorldClim's BIL; tmean example<br /> for i in $(seq 1 12); do echo “PIXELTYPE SIGNEDINT” &gt;&gt;tmean$i.hdr; done<br /> <br /> b) ESRI grd files: Note that the WorldClim ESRI grd files suffer from a quality issue of coordinate precision. See [https://lists.osgeo.org/pipermail/grass-user/2011-January/059358.html here] for a solution.<br /> <br /> # fix WorldClim's ESRI Grd; tmean example<br /> export GDAL_CACHEMAX=2000<br /> mkdir -p ~/tmp/<br /> # fix broken WorldClim files, see https://lists.osgeo.org/pipermail/grass-user/2011-January/059358.html<br /> # note: 60S, not 90S<br /> for i in $(seq 1 12); do gdal_translate -a_ullr -180 90 180 -60 tmean_$i $HOME/tmp/tmean_${i}_fixed.tif; done<br /> #<br /> # import<br /> for i in $(seq 1 12) ; do r.in.gdal input=$HOME/tmp/tmean_${i}_fixed.tif out=tmp --o ; g.region raster=tmp -p ; r.mapcalc &quot;tmean_${i} = 0.1 * tmp&quot; --o ; r.colors tmean_${i} color=celsius ; done<br /> #<br /> # clean up<br /> g.remove raster name=tmp -f<br /> rm -f ~/tmp/tmean_?_fixed.tif ; rm -f ~/tmp/tmean_??_fixed.tif<br /> <br /> === Africlim maps ===<br /> <br /> [https://www.york.ac.uk/environment/research/kite/resources/ Africlim] provides four baseline data sets for current climate, including:<br /> * CRU CL 2.0<br /> * WorldClim v1.4<br /> * TAMSAT TARCAT v2.0 (rainfall only)<br /> * CHIRPS v1.8 (rainfall only). <br /> <br /> It furthermore provides data sets with projections of future climates based on combinations of ten general circulation models (GCMs), downscaled using five regional climate models (RCMs) and the four above mentioned contemporary baselines, under two representative concentration pathways of the IPCC-AR5 (RCP4.5 and RCP8.5). The data layers are available as GeoTIF files at spatial resolutions of 10', 5', 2.5', 1' and 30&quot;.<br /> <br /> == Population maps ==<br /> <br /> === WorldPop ===<br /> <br /> * http://www.worldpop.org.uk/<br /> <br /> === Gridded Population of the World ===<br /> <br /> * http://sedac.ciesin.columbia.edu/gpw/global.jsp<br /> <br /> Import with {{cmd|r.in.gdal}}, assign population color table with {{cmd|r.colors}}<br /> <br /> == Topographic maps ==<br /> === Soviet topographic maps ===<br /> <br /> * [http://en.poehali.org/maps Soviet topographic maps] as geocoded GeoTIFFs<br /> <br /> = Vector data =<br /> <br /> === Natural Earth ===<br /> <br /> * http://www.naturalearthdata.com/ data scaled for 1:10 million, 1:50 million and 1:110million<br /> <br /> === CDC Geographic Boundary and Public Health Maps ===<br /> <br /> * http://www.cdc.gov/epiinfo/maps.htm<br /> <br /> === Global Administrative Areas ===<br /> <br /> * GADM is a database of the location of the world's administrative areas (boundaries) available in shapefiles.<br /> : http://gadm.org (extracted by country [http://gadm.org/country here])<br /> <br /> * World Borders Dataset including ISO 3166-1 Country codes available in shapefiles.<br /> : http://thematicmapping.org/downloads/world_borders.php<br /> * Free GIS data from Mapping Hacks<br /> : http://mappinghacks.com/data/<br /> <br /> === GSHHS World Coastline ===<br /> <br /> GSHHS is a high resolution shoreline dataset. It is derived from data in the public domain and licensed as GPL. The shorelines are constructed entirely from hierarchically arranged closed polygons. It is closely linked to the [[GMT]] project.<br /> <br /> ==== Availability ====<br /> <br /> * Download the original data set from http://www.soest.hawaii.edu/pwessel/gshhg/index.html. Also available at http://www.ngdc.noaa.gov/mgg/shorelines/data/gshhg/latest/.<br /> <br /> * The data set, or parts from it, can be extracted from [http://www.ngdc.noaa.gov/mgg/shorelines/shorelines.html NOAA's shoreline extractor].<br /> :For GRASS 6 you can download 1:250,000 shoreline data from NOAA's site in Mapgen format, which can be imported with the {{cmd|v.in.mapgen}} module.<br /> <br /> * '''ESRI Shapefiles''' of the latest version are available at http://www.ngdc.noaa.gov/mgg/shorelines/data/gshhg/latest/. The old 1.6 version is available at ftp://ftp.ihg.uni-duisburg.de/GIS/GISData/GSHHS/.<br /> <br /> ==== Import ====<br /> <br /> * Import with the GRASS6 add-on module {{AddonCmd|v.in.gshhs}}<br /> <br /> === OpenStreetMap ===<br /> <br /> See the [[OpenStreetMap]] wiki page.<br /> <br /> === SALB ===<br /> <br /> Second Administrative Level Boundaries: ''&quot;The SALB dataset is a global digital dataset consisting of digital maps and codes that can be downloaded on a country by country basis.&quot;''<br /> <br /> * http://www.who.int/whosis/database/gis/salb/salb_home.htm<br /> <br /> === VMap0 ===<br /> <br /> 1:1 million vector data. Formerly known as ''Digital Chart of the World''<br /> <br /> * see the two articles in [http://grass.osgeo.org/newsletter/index.php ''GRASS Newsletter vol. 3 (June 2005)'']<br /> <br /> Check the [http://en.wikipedia.org/wiki/Vector_Map Wikipedia page] on VMAP, see the links at the bottom of that article to shapefile versions of VMAP0 and VMAP1. Those look like the versions that were, several years ago, on a NIMA (predecessor to NGA, and successor to the Defense Mapping Agency that managed the Digital Chart of the World and VMAP project) Website. Many GRASS users may prefer the shapefiles to the original Vector Product Format data.<br /> <br /> * [http://gis-lab.info/qa/vmap0-eng.html VMap0 data in ESRI shape format]<br /> <br /> <br /> <br /> = See also =<br /> <br /> * [http://spatial-analyst.net/wiki/index.php?title=Global_datasets Global datasets] list by T. Hengl (with dataset download)<br /> * http://freegisdata.rtwilson.com/<br /> * The FreeGIS.org database: http://www.freegis.org/database/<br /> * http://finder.geocommons.com/<br /> * http://wiki.openstreetmap.org/wiki/Potential_Datasources<br /> * http://www.geonames.org/data-sources.html<br /> * [http://ckan.net/tag/read/geo Open Knowledge Foundation link collection]<br /> * [http://openweathermap.org/ Open Weather Map] free weather data and forecast API suitable for any cartographic services like web and smartphones applications. Ideology is inspired by OpenStreetMap and Wikipedia that make information free and available for everybody. <br /> <br /> === Metadata Catalogues ===<br /> Catalog Service for the Web (CSW) is an OGC standard for offering access to catalogues of geospatial information over the Internet (HTTP). CSW allow for discovering, browsing, and querying metadata about data, services, and similar resources. A list of Metadata Catalogues / CSW services from member states of the European Union can be found here:&lt;br /&gt;<br /> * [http://inspire-geoportal.ec.europa.eu/INSPIRERegistry/ http://inspire-geoportal.ec.europa.eu/INSPIRERegistry/]&lt;br /&gt;<br /> And here: [http://inspire-geoportal.ec.europa.eu/discovery/ http://inspire-geoportal.ec.europa.eu/discovery/] one can search European Metadata Catalogues online.<br /> <br /> === European datasets ===<br /> <br /> * [[European datasets]]<br /> * [http://preview.grid.unep.ch/index3.php?preview=data&amp;lang=eng Global Risk Data Platform]<br /> * [http://open-data.europa.eu/open-data/data/ European Commission Opendata Portal]: 5800+ datasets<br /> * [http://eca.knmi.nl/download/ensembles/download.php E-OBS] This is the download page for the ENSEMBLES daily gridded observational dataset for precipitation, temperature and sea level pressure in Europe<br /> * [http://mars.jrc.ec.europa.eu/mars/About-us/AGRI4CAST/Data-distribution MARS @ JRC] Temperature, vapour pressure, rainfall, relative humidity, cloud cover, solar radiation, wind speed.<br /> * [http://www.efas.eu/ EFAS @ JRC] is a High resolution pan-European dataset for hydrologic modelling.<br /> * [http://data.jrc.ec.europa.eu/ JRC Data Portal] In this catalogue, you can find an inventory of data that produced by the JRC in accordance with the JRC data policy. The content is continuously updated and shall not be seen as a complete inventory of JRC data. Currently, the inventory describes only a small subset of JRC data.<br /> <br /> === National datasets ===<br /> <br /> * [http://asdd.ga.gov.au/asdd/tech/zap/basic.html Australian Spatial Data Directory]<br /> * [http://aekos.org.au/home Australian Ecological Knowledge and Observation System]<br /> * [http://wiki.gfoss.it/index.php/GIS_Open_Data Italian Geodata collection]<br /> * [http://koordinates.com/ New Zealand] data from Koordinates.com<br /> * United States from NOAA/USGSs data portal (FIXME: link?)<br /> * [http://geodata.gov.gr/geodata/ Greek Public Geodata] (in Greek)<br /> <br /> === Various datasets worldwide ===<br /> <br /> * [http://geospatial.edublogs.org/ GEOSPATIAL DATA REPORT]: Finding and Using GIS Data<br /> * [http://www.edenextdata.com/?q=data Edenext data portal]: Land Cover, Transport networks, Elevation, Orthoimagery, Human health and safety, Species Distribution, Atmospheric Conditions and Meteorological Geographical Features, Training Program Presentations and Data, Utility and governmental services, Hydrography, Soil, Bio geographical regions, Population distribution and Demographics<br /> * [http://gdex.cr.usgs.gov/gdex/ Global Data Explorer USGS]: ASTER, SRTM, GTOPO etc<br /> * [http://www.landcover.org/ landcover]<br /> * [http://www.gripweb.org/gripweb/?q=data-information GRIPWEB’s Data &amp; Informational Portal]: hazard &amp; risk<br /> * [http://sedac.ciesin.columbia.edu/data/sets/browse SEDAC]: Agriculture, Climate, Conservation, Framework Data, Governance, Hazards, Health, Infrastructure, Land Use, Marine and Coastal, Population, Poverty, Remote Sensing, Sustainability, Urban, Water<br /> * [http://www.preventionweb.net/english/professional/maps/?pid:6&amp;pih:2 Prevention Web]: hazard &amp; risk<br /> * [http://data.un.org/Default.aspx UNdata]: UN database<br /> * [http://www.undp.org/content/undp/en/home.html UNDP home page]<br /> * [http://www.cgiar-csi.org/data global climatic data]<br /> * [http://csi.cgiar.org/cgiargeospatialtools.asp cosortium for spatial information CGIAR-CSI GeoSpatial Toolkits]<br /> * [http://freegisdata.rtwilson.com/ Links to over 300 sites providing freely available geographic datasets]<br /> * [http://www.diva-gis.org/Data Free Spatial Data]<br /> * [http://edc2.usgs.gov/glcc/globe_int.php Global Land Cover Characteristics Data Base Version 2.0]<br /> * [http://opentopo.sdsc.edu/gridsphere/gridsphere?cid=datasets A Portal to High-Resolution Topography Data and Tools]<br /> * [http://www.metoffice.gov.uk/hadobs/hadghcnd/ HadGHCND] is a gridded daily temperature dataset based upon near-surface maximum (TX) and minimum (TN) temperature observations.<br /> <br /> === WMS servers ===<br /> <br /> * See [[WMS]] page<br /> <br /> === River discharge data ===<br /> <br /> * [http://www.bafg.de/GRDC/EN/Home/homepage_node.html Global Runoff Data Centre]<br /> * [http://www.sage.wisc.edu/riverdata/ Global River Discharge Database]<br /> * [http://csdms.colorado.edu/wiki/River_discharge_data CSDMS]<br /> <br /> [[Category: Geodata]]<br /> [[Category: Import]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_messages_translation&diff=24120 2017-04-22T07:01:44Z

<p>Lucadelu: /* Get the translated po files */ improved a little bit transifex instructions</p> <hr /> <div>== Help page translations ==<br /> <br /> * For translations of full help (man) pages see [[Updating GRASS Documentation#Translations]]<br /> <br /> == GRASS messages translation project ==<br /> <br /> Many users prefer to use software in their mother tongue which is mostly not English. This requires that all GRASS software messages have to be translated to languages other than English. The GRASS Development Team is seeking translators. Please subscribe to the dedicated mailing list at<br /> <br /> GRASS translations mailing list<br /> http://lists.osgeo.org/mailman/listinfo/grass-translations<br /> <br /> Translation related issues may be discussed there. This is an opportunity for non-programmers to contribute as messages can be easily translated. No programming skills required!<br /> <br /> * Join the [[GRASS_Translation_Team#Members_of_Translation_Team|team]]<br /> <br /> === Wanted languages ===<br /> <br /> Simple Chinese, Swahili, Hindi, Greek, Tamil, Russian, Telugu, Português, ... Please join us!<br /> <br /> == How to change the language ==<br /> <br /> * see [[GRASS_messages_translation#Testing_different_languages|Testing different languages]] below.<br /> <br /> == How to start or update translations ==<br /> <br /> * For terminology, please refer to the [[GRASS Translation Glossary]].<br /> <br /> === Files to be edited (downloaded) ===<br /> <br /> ==== GRASS GIS 6 ====<br /> In GRASS GIS 6, we have 5 types of .po files per language (the files are stored in the source code, in directory locale/po/; &lt;br&gt;<br /> or simply '''[http://svn.osgeo.org/grass/grass/branches/releasebranch_6_4/locale/po/ download .po files here]'''):<br /> <br /> * &lt;tt&gt;grasslibs_LANG.po&lt;/tt&gt;: messages from libraries<br /> * &lt;tt&gt;grassmods_LANG.po&lt;/tt&gt;: messages from commands (&quot;modules&quot;)<br /> * &lt;tt&gt;grassnviz_LANG.po&lt;/tt&gt;: messages from NVIZ Tcl/Tk graphical user interface (GRASS 6)<br /> * &lt;tt&gt;grasstcl_LANG.po&lt;/tt&gt;: messages from Tcl/Tk graphical user interface (GRASS 6)<br /> * &lt;tt&gt;grasswxpy_LANG.po&lt;/tt&gt;: messages from wxgrass/wxPython graphical user interface<br /> <br /> where &quot;LANG&quot; in the above file names is a two character code which indicates the language. It is based on the Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column). Example: &lt;tt&gt;grasswxpy_pl.po&lt;/tt&gt; for Polish.<br /> <br /> ==== GRASS GIS 7 ====<br /> In GRASS GIS 7, we have only 3 types of .po files per language (the files are stored in the source code, in directory locale/po/; &lt;br&gt;<br /> or simply '''[http://svn.osgeo.org/grass/grass/branches/releasebranch_7_0/locale/po/ download .po files here]'''):<br /> <br /> * &lt;tt&gt;grasslibs_LANG.po&lt;/tt&gt;: messages from libraries<br /> * &lt;tt&gt;grassmods_LANG.po&lt;/tt&gt;: messages from commands (&quot;modules&quot;)<br /> * &lt;tt&gt;grasswxpy_LANG.po&lt;/tt&gt;: messages from wxgrass/wxPython graphical user interface<br /> <br /> where &quot;LANG&quot; in the above file names is a two character code which indicates the language. It is based on the Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column). Example: &lt;tt&gt;grasswxpy_pl.po&lt;/tt&gt; for Polish.<br /> <br /> === Continuing an existing translation ===<br /> <br /> The file(s) are there but partially outdated? Read on.<br /> <br /> First '''announce''' on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] that you plan to continue the translation of a certain language. Why? Because sometimes people silently translate already and we need these efforts to be coordinated to avoid doing it twice...<br /> <br /> Then get these four .po files for your language and start. If a file is missing, just ask on the list to get it generated or see next section. To get these .po files (the files are in the directory locale/po/):<br /> <br /> * either [http://svn.osgeo.org/grass/grass/branches/releasebranch_7_0/locale/po/ download current .po files] directly from SVN (click on file name to download),<br /> * or [http://trac.osgeo.org/grass/wiki/DownloadSource#GRASS7.0 download source code package] from SVN,<br /> * or download the recent [http://grass.osgeo.org/grass70/source/snapshot/ source code snapshot],<br /> * or ask on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] for these files.<br /> <br /> Then edit the files with a .po file editor (poEDIT or kbabel or..., see below). Take care to maintain layout and special characters. And '''submit often''' - if you wait for weeks, the messages may already be outdated and your time wasted. Just keep in touch on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list]!<br /> <br /> === Starting a new translation ===<br /> <br /> The language you want isn't yet there? Read on.<br /> <br /> Briefly, the steps to create new messages files are (if you find this too complicated, ask on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] to get these files done for you!):<br /> <br /> # Get the latest source code development version from either the SVN repository or as SVN snapshot (see [http://grass.osgeo.org/download/index.php Download]).<br /> # run: './configure --with-nls [... other parameters]' to configure the GRASS source code <br /> # run: 'cd locale' to change into the translation directory<br /> # run: 'make pot' to create grass*.pot template files (to extract original messages)<br /> # run: copy these file from templates/ into po/; rename them to contain the two characters language code (see Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1]) and to .po extension; update the file headers either manually or with your .po editing software<br /> (Example: Polish language):<br /> mv ./templates/grasslibs.pot ./po/grasslibs_pl.po<br /> mv ./templates/grassmods.pot ./po/grassmods_pl.po<br /> mv ./templates/grassnviz.pot ./po/grassnviz_pl.po<br /> mv ./templates/grasstcl.pot ./po/grasstcl_pl.po<br /> mv ./templates/grasswxpy.pot ./po/grasswxpy_pl.po<br /> <br /> Now translate the messages in these po/*.po files (using poEDIT or other editor, see below)<br /> <br /> From time to time messages need to be updated from the originals. This is usually done by the GRASS translation manager.<br /> <br /> == Software to translate: .po file editors ==<br /> <br /> * [http://userbase.kde.org/Lokalize Lokalize]: (previously KBabel) is a set of tools for editing and managing gettext PO files, cross-platform, comes with KDE SC (works also under MS-Windows)<br /> * [http://www.poedit.net/download.php poEdit]: poEdit is gettext catalogs (.po files) editor (works also under MS-Windows)<br /> * [http://translate.sourceforge.net/wiki/virtaal/index Virtaal] Virtaal is cross-platform graphical translation tool with terminology help from [http://open-tran.eu Open-Tran.eu]<br /> * '''[https://www.transifex.com/grass-gis/grass72/ Web based solution Transifex]''' (''see below, join us!'')<br /> * [http://www.omegat.org/ Java based solution OmegaT]<br /> &lt;!--<br /> '''How to use Transifex to translate messages online in a browser:'''<br /> <br /> [[Image:Transifex register signin.png|center|450px|Register and sign in]]<br /> <br /> [[Image:Transifex edit online.png|center|450px|Click to edit online]]<br /> --&gt;<br /> <br /> == Transifex ==<br /> <br /> === How to translate ===<br /> '''''NOTE: THIS IS FOR TRANSLATOR'''''<br /> <br /> Register your self on [https://www.transifex.com/ Transifex website], join the [https://www.transifex.com/grass-gis/ GRASS GIS project] and start to translate (grasswxpy is the GUI translation and it should be the first translated).<br /> <br /> === Create a new project ===<br /> <br /> '''''NOTE: CORE DEVELOPERS ONLY!'''''<br /> <br /> A project should be done for each stable release, only an Organization Administrators can create a project. From the dashboard in the left bottom corner there is &quot;'''New project'''&quot; button. Fill all the field in the form. More info in [https://docs.transifex.com/projects/creating-a-project Transifex documentation]<br /> <br /> Once the new project is created you need to upload the resources (the pot file to translate).<br /> To create the pot files you can execute<br /> make pot<br /> <br /> inside the '''locale''' folder. Now you can load in the Resource section, after you added them you can link the pot file with an online version to get updates. To do this click on &quot;'''Auto update resources'''&quot; bottom (read also the [https://docs.transifex.com/projects/uploading-content Transifex documentation].<br /> <br /> At this point you need to load the translated po files, for each language and file you have to upload the translation po file. Some errors could appear, resolution of this problems is a TODO<br /> <br /> === Get the translated po files ===<br /> <br /> '''''NOTE: THIS IS FOR DEVELOPER OR POWER USER'''''<br /> <br /> It is possible to get back the translated po files automatically using the [https://docs.transifex.com/client/introduction Transifex client], install it first.<br /> <br /> To download the file it is required to create a folder to initialize the Transifex project using the command, so enter in the locale folder of your GRASS source code and create a new folder called transifex.<br /> <br /> mkdir transifex<br /> cd transifex<br /> tx init --user=USERNAME --passwd=PASSWORD<br /> <br /> --user and --passwd option are useful to create the ''.transifexrc'' file in your $HOME to save user and password, otherwise you can create the file by your self, like the following one<br /> <br /> [ https://www.transifex.com ]<br /> hostname = https://www.transifex.com<br /> password = PASSWORD<br /> token = <br /> username = USERNAME<br /> <br /> At this point you need to configure the repository modifying the ''.tx/config'' file created in your folder. The following file is working for [https://www.transifex.com/grass-gis/grass72 GRASS 7.2 project], you need to add a section for each resource. <br /> <br /> [main]<br /> host = https://www.transifex.com<br /> <br /> [grass72.grasslibspot]<br /> type = PO<br /> source_lang = en<br /> source_file = ../templates/grasslibs.pot<br /> <br /> [grass72.grassmodspot]<br /> type = PO<br /> source_lang = en<br /> source_file = ../templates/grassmods.pot<br /> <br /> [grass72.grasswxpypot]<br /> type = PO<br /> source_lang = en<br /> source_file = ../templates/grasswxpy.pot<br /> <br /> '''''NOTE: THIS SHOULD NOT BE RUN IF YOU WANT TO RUN transifex_merge.sh (you can find it in grass-addons/tools/) '''''<br /> <br /> Now you can download all the translated po files with the following command<br /> <br /> tx pull -a<br /> <br /> == Testing different languages ==<br /> <br /> Testing different languages requires that the respective language environment and, if needed, fonts are installed.<br /> Check what languages are currently installed on your system with:<br /> locale -a<br /> <br /> To change to a certain language environment (locale), do the following steps (here, example for Unix style environment):<br /> <br /> 1. Define/check language settings:<br /> echo $LANG<br /> echo $LANGUAGE<br /> echo $LC_MESSAGES<br /> <br /> 2. Change it (example for to Japanese):<br /> a) bash shell:<br /> export LANG=ja_JP.UTF-8<br /> export LANGUAGE=ja_JP.UTF-8<br /> export LC_MESSAGES=ja_JP.UTF-8<br /> <br /> <br /> b) (t)csh shell:<br /> setenv LANG ja_JP.UTF-8<br /> setenv LANGUAGE ja_JP.UTF-8<br /> setenv LC_MESSAGES ja_JP.UTF-8<br /> <br /> Now launch GRASS in this terminal. If you launch it from an icon, you have to change the LOCALE in the computer setup program instead.<br /> <br /> Other common languages useful for testing are &lt;tt&gt;de_DE&lt;/tt&gt; for German, &lt;tt&gt;fr_FR&lt;/tt&gt; for French, or &quot;C&quot; for none (effectively &lt;tt&gt;en_US&lt;/tt&gt;, which for GRASS is the base language).<br /> <br /> === Creating startup scripts for different languages ===<br /> <br /> GRASS in English language, save as &quot;grass64eng&quot; (executable flag set, store in path):<br /> #!/bin/sh<br /> export LANG=en_US<br /> export LANGUAGE=en_US<br /> export LC_MESSAGES=en_US<br /> exec grass64 &quot;$@&quot;<br /> <br /> GRASS in Japanese language, save as &quot;grass64ja&quot; (executable flag set, store in path):<br /> #!/bin/sh<br /> export LANG=ja_JA.UTF-8<br /> export LANGUAGE=ja_JA.UTF-8<br /> export LC_MESSAGES=ja_JA.UTF-8<br /> grass64 &quot;$@&quot;<br /> <br /> == Coordination among translators ==<br /> <br /> If several translators work on the same language files, obviously some coordination is needed. Please announce work via the &quot;translations&quot; mailing list at http://lists.osgeo.org/mailman/listinfo/grass-translations <br /> <br /> Also the translation manager is listening there to the upload the changed files into the GRASS source code repository.<br /> <br /> == Best practices ==<br /> <br /> * Italiano: [http://tp.linux.it/buona_traduzione.html Regole per la buona traduzione]<br /> <br /> == Installation of language packages ==<br /> <br /> Example: Chinese<br /> <br /> * Mandriva: urpmi locales-zh kde-l10n-zh_CN fonts-ttf-default-zh_CN<br /> * Fedora: the locales should be already present<br /> ** list all valid locales on the system: localectl list-locales<br /> ** show current settings: localectl status<br /> ** set new locale: localectl set-locale LANG=zh_CN.utf8 LC_MESSAGES=zh_CN.utf8<br /> <br /> == Updating messages in the source code ==<br /> <br /> Generally, to support i18N multiple languages, message strings in GRASS must be modified by adding so-called [https://www.gnu.org/software/gettext/ gettext macros] &lt;tt&gt;'''_('''&quot;...&quot;''')'''&lt;/tt&gt;.<br /> <br /> === C programming language ===<br /> <br /> Change from<br /> fprintf ( ..., &quot;...\n&quot;, ...);<br /> to either<br /> fprintf ( ..., _(&quot;...\n&quot;), ...);<br /> or usually (while omitting \n)<br /> G_message ( _(&quot;...&quot;), ...);<br /> <br /> === Python programming language ===<br /> <br /> In Python, the macro is used like this:<br /> &lt;source lang=&quot;python&quot;&gt;<br /> grass.message(_('Raster map &lt;{name}&gt; unpacked'.format(name=map_name)))<br /> &lt;/source&gt;<br /> <br /> === Important hints ===<br /> <br /> Beware:<br /> * G_message should be used for messages - information about the process for user while fprintf(stdout...) for data output.<br /> * G_message output is not expected to be send to pipe or file.<br /> * fprintf(stdout...) output is usually send to pipe or file.<br /> <br /> Programming details are available in the file locale/[https://svn.osgeo.org/grass/grass/trunk/locale/README README].<br /> <br /> Important:<br /> * [https://trac.osgeo.org/grass/wiki/MessageStandardization Message Standardization]: How should Errors/Warnings/Messages be formatted, Macros etc<br /> <br /> == See also ==<br /> <br /> * Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column)<br /> <br /> <br /> [[Category: Development]]<br /> [[Category: Documentation]]<br /> [[Category: FAQ]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=Talk:GRASS_Community_Sprint_Genova_2017&diff=24074 2017-03-29T14:14:56Z

<p>Lucadelu: </p> <hr /> <div>== Participants and Reports ==<br /> <br /> === Martin Landa ===<br /> <br /> * {{trac|3270}}<br /> * {{trac|3266}}<br /> * {{trac|2460}}<br /> * {{trac|3224}}<br /> * fix cs po file (plural forms)<br /> * {{trac|3280}}<br /> * fix broken table/column dependecies, see {{rev|70518}}<br /> * {{trac|3244}}<br /> * {{trac|2055}}<br /> * See [https://trac.osgeo.org/grass/timeline?from=Feb+12%2C+2017&amp;daysback=4&amp;authors=martinl&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;sfp_email=&amp;sfph_mail=&amp;update=Update SVN logs overview]<br /> <br /> === Elena Mezzini ===<br /> <br /> * GRASS GUI Italian translation.<br /> * update of Transifex Italian Glossary for GRASS project<br /> <br /> Planned:<br /> * Hope to reach 500 untranslated strings (or less) [she did it but [[User:Lucadelu|lucadelu]] broke some translations :-/ ]<br /> <br /> === Luca Delucchi ===<br /> <br /> * apply Veronica Andreo patch for r.modis<br /> * removed pyModis lib from r.modis, now it is using the system one {{rev|70528}}<br /> * closed ticket {{trac|3268}}<br /> * improve Transifex transition:<br /> ** create script to download po files from Transifex {{rev|70526}}<br /> ** added info in the wiki page<br /> ** added more translation files in Transifex<br /> ** added [[GRASS_Translation_Glossary]] to [https://www.transifex.com/grass-gis/settings/glossary/ Transifex glossary]<br /> <br /> == Funding ==<br /> === What is to be funded? ===<br /> <br /> Food, drinks and transport<br /> <br /> === How many participants are expected? ===<br /> <br /> 3 participants<br /> <br /> === How to fund? (financially, with material resources, in-kind ...) ===<br /> <br /> Financially<br /> <br /> === How much money is needed? ===<br /> <br /> {| {{table}}<br /> | align=&quot;center&quot; style=&quot;background:#f0f0f0;&quot;|'''Community Sprint cost estimate'''<br /> | align=&quot;center&quot; style=&quot;background:#f0f0f0;&quot;|'''Euro'''<br /> |-<br /> | Reimbursements for participants || 322 €<br /> |-<br /> | Public Transport || 22.5 €<br /> |-<br /> | Promo (T-Shirts + stickers) || 0.00<br /> |-<br /> | Office stuff || 0.00<br /> |-<br /> | Food + Drinks || 234 €<br /> |-<br /> | align=&quot;center&quot; style=&quot;background:#f0f0f0;&quot; | '''TOTAL COST''' || '''578.50 €'''<br /> |-<br /> |}<br /> <br /> More detailed budget [https://docs.google.com/spreadsheets/d/18Jx74WEqsuydSErTvCOfa_nhze54RUzc2BH5I49Z4Vg here]<br /> <br /> === What relationship has the proposed project to GRASS GIS? ===<br /> <br /> The event is fully related to GRASS development.<br /> <br /> === Is the event additionally sponsored by others? ===<br /> <br /> No.<br /> <br /> === What are the consequences of funding / non-funding? ===<br /> <br /> The participants would need to pay expenses out of their own pocket.<br /> <br /> === What kind of documentation / reporting will be delivered after the event? ===<br /> <br /> Wiki report similar to [[GRASS GIS contributors meetings in Solany/December 2015|last meeting]].<br /> <br /> === Contact info ===<br /> <br /> [[User:Lucadelu]]<br /> <br /> === Mail to PSC mailing list sent? ===<br /> <br /> <br /> <br /> === Decision taken ===<br /> <br /> === Report after the event ===<br /> Yes, it is above<br /> <br /> = Comments from community =<br /> <br /> [[Category: Workshops]]<br /> [[Category: Code Sprint]]<br /> [[Category: 2017]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=Talk:GRASS_Community_Sprint_Genova_2017&diff=24072 2017-03-26T22:49:31Z

<p>Lucadelu: /* How much money is needed? */ final costs</p> <hr /> <div>== Participants and Reports ==<br /> <br /> === Martin Landa ===<br /> <br /> * {{trac|3270}}<br /> * {{trac|3266}}<br /> * {{trac|2460}}<br /> * {{trac|3224}}<br /> * fix cs po file (plural forms)<br /> * {{trac|3280}}<br /> * fix broken table/column dependecies, see {{rev|70518}}<br /> * {{trac|3244}}<br /> * {{trac|2055}}<br /> * See [https://trac.osgeo.org/grass/timeline?from=Feb+12%2C+2017&amp;daysback=4&amp;authors=martinl&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;sfp_email=&amp;sfph_mail=&amp;update=Update SVN logs overview]<br /> <br /> === Elena Mezzini ===<br /> <br /> * GRASS GUI Italian translation.<br /> * update of Transifex Italian Glossary for GRASS project<br /> <br /> Planned:<br /> * Hope to reach 500 untranslated strings (or less) [she did it but [[User:Lucadelu|lucadelu]] broke some translations :-/ ]<br /> <br /> === Luca Delucchi ===<br /> <br /> * apply Veronica Andreo patch for r.modis<br /> * removed pyModis lib from r.modis, now it is using the system one {{rev|70528}}<br /> * closed ticket {{trac|3268}}<br /> * improve Transifex transition:<br /> ** create script to download po files from Transifex {{rev|70526}}<br /> ** added info in the wiki page<br /> ** added more translation files in Transifex<br /> ** added [[GRASS_Translation_Glossary]] to [https://www.transifex.com/grass-gis/settings/glossary/ Transifex glossary]<br /> <br /> == Funding ==<br /> === What is to be funded? ===<br /> <br /> Food, drinks and transport<br /> <br /> === How many participants are expected? ===<br /> <br /> 3 participants<br /> <br /> === How to fund? (financially, with material resources, in-kind ...) ===<br /> <br /> Financially<br /> <br /> === How much money is needed? ===<br /> <br /> {| {{table}}<br /> | align=&quot;center&quot; style=&quot;background:#f0f0f0;&quot;|'''Community Sprint cost estimate'''<br /> | align=&quot;center&quot; style=&quot;background:#f0f0f0;&quot;|'''Euro'''<br /> |-<br /> | Reimbursements for participants || 322 €<br /> |-<br /> | Public Transport || 22.5 €<br /> |-<br /> | Promo (T-Shirts + stickers) || 0.00<br /> |-<br /> | Office stuff || 0.00<br /> |-<br /> | Food + Drinks || 234 €<br /> |-<br /> | align=&quot;center&quot; style=&quot;background:#f0f0f0;&quot; | '''TOTAL COST''' || '''578.50 €'''<br /> |-<br /> |}<br /> <br /> === What relationship has the proposed project to GRASS GIS? ===<br /> <br /> The event is fully related to GRASS development.<br /> <br /> === Is the event additionally sponsored by others? ===<br /> <br /> No.<br /> <br /> === What are the consequences of funding / non-funding? ===<br /> <br /> The participants would need to pay expenses out of their own pocket.<br /> <br /> === What kind of documentation / reporting will be delivered after the event? ===<br /> <br /> Wiki report similar to [[GRASS GIS contributors meetings in Solany/December 2015|last meeting]].<br /> <br /> === Contact info ===<br /> <br /> [[User:Lucadelu]]<br /> <br /> === Mail to PSC mailing list sent? ===<br /> <br /> <br /> <br /> === Decision taken ===<br /> <br /> === Report after the event ===<br /> Yes, it is above<br /> <br /> = Comments from community =<br /> <br /> [[Category: Workshops]]<br /> [[Category: Code Sprint]]<br /> [[Category: 2017]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=Talk:GRASS_Community_Sprint_Genova_2017&diff=24028 2017-03-23T16:36:46Z

<p>Lucadelu: /* How much money is needed? */ added costs</p> <hr /> <div>== Participants and Reports ==<br /> <br /> === Martin Landa ===<br /> <br /> * {{trac|3270}}<br /> * {{trac|3266}}<br /> * {{trac|2460}}<br /> * {{trac|3224}}<br /> * fix cs po file (plural forms)<br /> * {{trac|3280}}<br /> * fix broken table/column dependecies, see {{rev|70518}}<br /> * {{trac|3244}}<br /> * {{trac|2055}}<br /> * See [https://trac.osgeo.org/grass/timeline?from=Feb+12%2C+2017&amp;daysback=4&amp;authors=martinl&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;sfp_email=&amp;sfph_mail=&amp;update=Update SVN logs overview]<br /> <br /> === Elena Mezzini ===<br /> <br /> * GRASS GUI Italian translation.<br /> * update of Transifex Italian Glossary for GRASS project<br /> <br /> Planned:<br /> * Hope to reach 500 untranslated strings (or less) [she did it but [[User:Lucadelu|lucadelu]] broke some translations :-/ ]<br /> <br /> === Luca Delucchi ===<br /> <br /> * apply Veronica Andreo patch for r.modis<br /> * removed pyModis lib from r.modis, now it is using the system one {{rev|70528}}<br /> * closed ticket {{trac|3268}}<br /> * improve Transifex transition:<br /> ** create script to download po files from Transifex {{rev|70526}}<br /> ** added info in the wiki page<br /> ** added more translation files in Transifex<br /> ** added [[GRASS_Translation_Glossary]] to [https://www.transifex.com/grass-gis/settings/glossary/ Transifex glossary]<br /> <br /> == Funding ==<br /> === What is to be funded? ===<br /> <br /> Food, drinks and transport<br /> <br /> === How many participants are expected? ===<br /> <br /> 3 participants<br /> <br /> === How to fund? (financially, with material resources, in-kind ...) ===<br /> <br /> Financially<br /> <br /> === How much money is needed? ===<br /> <br /> {| {{table}}<br /> | align=&quot;center&quot; style=&quot;background:#f0f0f0;&quot;|'''Community Sprint cost estimate'''<br /> | align=&quot;center&quot; style=&quot;background:#f0f0f0;&quot;|'''Euro'''<br /> |-<br /> | Reimbursements for participants || 322 €<br /> |-<br /> | Public Transport || 22.5€<br /> |-<br /> | Promo (T-Shirts + stickers) || 0.00<br /> |-<br /> | Office stuff || 0.00<br /> |-<br /> | Food + Drinks || 225 €<br /> |-<br /> | align=&quot;center&quot; style=&quot;background:#f0f0f0;&quot; | '''TOTAL COST''' || '''75.00'''<br /> |-<br /> |}<br /> <br /> === What relationship has the proposed project to GRASS GIS? ===<br /> <br /> The event is fully related to GRASS development.<br /> <br /> === Is the event additionally sponsored by others? ===<br /> <br /> No.<br /> <br /> === What are the consequences of funding / non-funding? ===<br /> <br /> The participants would need to pay expenses out of their own pocket.<br /> <br /> === What kind of documentation / reporting will be delivered after the event? ===<br /> <br /> Wiki report similar to [[GRASS GIS contributors meetings in Solany/December 2015|last meeting]].<br /> <br /> === Contact info ===<br /> <br /> [[User:Lucadelu]]<br /> <br /> === Mail to PSC mailing list sent? ===<br /> <br /> <br /> <br /> === Decision taken ===<br /> <br /> === Report after the event ===<br /> Yes, it is above<br /> <br /> = Comments from community =<br /> <br /> [[Category: Workshops]]<br /> [[Category: Code Sprint]]<br /> [[Category: 2017]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=Talk:GRASS_Community_Sprint_Genova_2017&diff=24027 2017-03-23T16:29:53Z

<p>Lucadelu: create section for funds of GRASS Community Sprint Genova 2017</p> <hr /> <div>== Participants and Reports ==<br /> <br /> === Martin Landa ===<br /> <br /> * {{trac|3270}}<br /> * {{trac|3266}}<br /> * {{trac|2460}}<br /> * {{trac|3224}}<br /> * fix cs po file (plural forms)<br /> * {{trac|3280}}<br /> * fix broken table/column dependecies, see {{rev|70518}}<br /> * {{trac|3244}}<br /> * {{trac|2055}}<br /> * See [https://trac.osgeo.org/grass/timeline?from=Feb+12%2C+2017&amp;daysback=4&amp;authors=martinl&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;sfp_email=&amp;sfph_mail=&amp;update=Update SVN logs overview]<br /> <br /> === Elena Mezzini ===<br /> <br /> * GRASS GUI Italian translation.<br /> * update of Transifex Italian Glossary for GRASS project<br /> <br /> Planned:<br /> * Hope to reach 500 untranslated strings (or less) [she did it but [[User:Lucadelu|lucadelu]] broke some translations :-/ ]<br /> <br /> === Luca Delucchi ===<br /> <br /> * apply Veronica Andreo patch for r.modis<br /> * removed pyModis lib from r.modis, now it is using the system one {{rev|70528}}<br /> * closed ticket {{trac|3268}}<br /> * improve Transifex transition:<br /> ** create script to download po files from Transifex {{rev|70526}}<br /> ** added info in the wiki page<br /> ** added more translation files in Transifex<br /> ** added [[GRASS_Translation_Glossary]] to [https://www.transifex.com/grass-gis/settings/glossary/ Transifex glossary]<br /> <br /> == Funding ==<br /> === What is to be funded? ===<br /> <br /> Food, drinks and transport<br /> <br /> === How many participants are expected? ===<br /> <br /> 3 participants<br /> <br /> === How to fund? (financially, with material resources, in-kind ...) ===<br /> <br /> Financially<br /> <br /> === How much money is needed? ===<br /> <br /> {| {{table}}<br /> | align=&quot;center&quot; style=&quot;background:#f0f0f0;&quot;|'''Community Sprint cost estimate'''<br /> | align=&quot;center&quot; style=&quot;background:#f0f0f0;&quot;|'''Euro'''<br /> |-<br /> | Reimbursements for participants || ??<br /> |-<br /> | Public Transport || ??<br /> |-<br /> | Promo (T-Shirts + stickers) || 0.00<br /> |-<br /> | Office stuff || 0.00<br /> |-<br /> | Food + Drinks || ??<br /> |-<br /> | align=&quot;center&quot; style=&quot;background:#f0f0f0;&quot; | '''TOTAL COST''' || '''75.00'''<br /> |-<br /> |}<br /> <br /> === What relationship has the proposed project to GRASS GIS? ===<br /> <br /> The event is fully related to GRASS development.<br /> <br /> === Is the event additionally sponsored by others? ===<br /> <br /> No.<br /> <br /> === What are the consequences of funding / non-funding? ===<br /> <br /> The participants would need to pay expenses out of their own pocket.<br /> <br /> === What kind of documentation / reporting will be delivered after the event? ===<br /> <br /> Wiki report similar to [[GRASS GIS contributors meetings in Solany/December 2015|last meeting]].<br /> <br /> === Contact info ===<br /> <br /> [[User:Lucadelu]]<br /> <br /> === Mail to PSC mailing list sent? ===<br /> <br /> <br /> <br /> === Decision taken ===<br /> <br /> === Report after the event ===<br /> Yes, it is above<br /> <br /> = Comments from community =<br /> <br /> [[Category: Workshops]]<br /> [[Category: Code Sprint]]<br /> [[Category: 2017]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=Talk:GRASS_Community_Sprint_Genova_2017&diff=23978 2017-02-24T15:22:31Z

<p>Lucadelu: /* Elena Mezzini */</p> <hr /> <div>== Participants and Reports ==<br /> <br /> === Martin Landa ===<br /> <br /> * {{trac|3270}}<br /> * {{trac|3266}}<br /> * {{trac|2460}}<br /> * {{trac|3224}}<br /> * fix cs po file (plural forms)<br /> * {{trac|3280}}<br /> * fix broken table/column dependecies, see {{rev|70518}}<br /> * {{trac|3244}}<br /> * {{trac|2055}}<br /> * See [https://trac.osgeo.org/grass/timeline?from=Feb+12%2C+2017&amp;daysback=4&amp;authors=martinl&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;sfp_email=&amp;sfph_mail=&amp;update=Update SVN logs overview]<br /> <br /> === Elena Mezzini ===<br /> <br /> * GRASS GUI Italian translation.<br /> * update of Transifex Italian Glossary for GRASS project<br /> <br /> Planned:<br /> * Hope to reach 500 untranslated strings (or less) [she did it but [[User:Lucadelu|lucadelu]] broke some translations :-/ ]<br /> <br /> === Luca Delucchi ===<br /> <br /> * apply Veronica Andreo patch for r.modis<br /> * removed pyModis lib from r.modis, now it is using the system one {{rev|70528}}<br /> * closed ticket {{trac|3268}}<br /> * improve Transifex transition:<br /> ** create script to download po files from Transifex {{rev|70526}}<br /> ** added info in the wiki page<br /> ** added more translation files in Transifex<br /> ** added [[GRASS_Translation_Glossary]] to [https://www.transifex.com/grass-gis/settings/glossary/ Transifex glossary]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=Talk:GRASS_Community_Sprint_Genova_2017&diff=23946 2017-02-11T23:23:52Z

<p>Lucadelu: </p> <hr /> <div>== Participants and Reports ==<br /> <br /> === Martin Landa ===<br /> <br /> * {{trac|3270}}<br /> * {{trac|3266}}<br /> * {{trac|2460}}<br /> * {{trac|3224}}<br /> * fix cs po file (plural forms)<br /> * {{trac|3280}}<br /> * fix broken table/column dependecies, see {{rev|70518}}<br /> * {{trac|3244}}<br /> * {{trac|2055}}<br /> * See [https://trac.osgeo.org/grass/timeline?from=Feb+12%2C+2017&amp;daysback=4&amp;authors=martinl&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;sfp_email=&amp;sfph_mail=&amp;update=Update SVN logs overview]<br /> <br /> === Elena Mezzini ===<br /> <br /> * GRASS GUI Italian translation.<br /> * update of Transifex Italian Glossary for GRASS project<br /> <br /> Planned:<br /> * Hope to reach 500 untranslated strings (or less)<br /> <br /> === Luca Delucchi ===<br /> <br /> * apply Veronica Andreo patch for r.modis<br /> * removed pyModis lib from r.modis, now it is using the system one {{rev|70528}}<br /> * closed ticket {{trac|3268}}<br /> * improve Transifex transition:<br /> ** create script to download po files from Transifex {{rev|70526}}<br /> ** added info in the wiki page<br /> ** added more translation files in Transifex<br /> ** added [[GRASS_Translation_Glossary]] to [https://www.transifex.com/grass-gis/settings/glossary/ Transifex glossary]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_Translation_Glossary&diff=23945 2017-02-11T22:25:34Z

<p>Lucadelu: </p> <hr /> <div>This table provides a list of GRASS and GIS related terms. The glossary shall help to harmonize translation work of GRASS docs currently hosted at the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS Translation Project].<br /> <br /> == Help pages ==<br /> <br /> I don't know how AltaVista feels about live linking, but on the wiki I've added experimental links to the Babelfish translator for the 6.3 online help pages:<br /> <br /> * [[Updating_GRASS_Documentation#Translations]]<br /> <br /> == Language specific notes ==<br /> <br /> Note for French translators : les mots en caractères italiques signalent les anglicismes et les calques sur l'anglais qui sont néanmoins des termes d'usage courant, à chacun de choisir la traduction qu'il juge la plus adaptée et la plus compréhensible pour ses lecteurs.&lt;br&gt;<br /> <br /> Note for Spanish translators: la terminología empleada aquí viene de la guía de inicio GRASS traducida por Guillermo Martínez.<br /> <br /> Σημείωση για τους Έλληνες μεταφραστές: η ορολογία που εμφανίζεται είναι ενδεικτική, αποτελεί αντικείμενο συζήτησης μεταξύ των ενδιαφερόμενων και αναρτήθηκε από τον Κίμωνα Παπαδημτρίου.&lt;br&gt;<br /> <br /> Note for Portuguese translators: Indicar a variante regional, quando houver. Os termos empregados provém na maioria da tradução brasileira, feita inicialmente por Paulo Marcondes.&lt;br&gt;<br /> <br /> Note for Korean translators: GRASS의 한글화에 관심이 있으신 분은 [http://groups.google.com/group/osgeo-kr OSGeo 한국어 지부]에 참여해 주세요.<br /> <br /> == Glossary ==<br /> <br /> ''' PLEASE DO NOT UPDATE THIS TABLE ANYMORE, USE THE [https://www.transifex.com/grass-gis/settings/glossary/56216/en/ TRANSIFEX GLOSSARY] INSTEAD'''<br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable sortable&quot; style=&quot;margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaaaaa solid; border-collapse: collapse;&quot;<br /> |-<br /> ! bgcolor=&quot;#99CCCC&quot; | ENGLISH<br /> ! bgcolor=&quot;#99CCCC&quot; | FRENCH<br /> ! bgcolor=&quot;#99CCCC&quot; | GERMAN<br /> ! bgcolor=&quot;#99CCCC&quot; | SPANISH<br /> ! bgcolor=&quot;#99CCCC&quot; | [http://wiki.gfoss.it/index.php/Traduzioni ITALIAN]<br /> ! bgcolor=&quot;#99CCCC&quot; | GREEK<br /> ! bgcolor=&quot;#99CCCC&quot; | FINNISH<br /> ! bgcolor=&quot;#99CCCC&quot; | [[Traducao | PORTUGUESE]]<br /> ! bgcolor=&quot;#99CCCC&quot; | CZECH<br /> ! bgcolor=&quot;#99CCCC&quot; | [http://gis-lab.info/docs/grass/glossary.html RUSSIAN]<br /> ! bgcolor=&quot;#99CCCC&quot; | CHINESE(Simplified)<br /> ! bgcolor=&quot;#99CCCC&quot; | KOREAN<br /> <br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot; | GRASS <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | GRASS<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;es&quot; | GRASS<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | GRASS<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fi&quot; | GRASS<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | GRASS <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;cz&quot; | tráva <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | GRASS<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | GRASS<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | GRASS<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot; | 2D <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | 2D ; bidimensionnel <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | 2D ; zweidimensional<br /> | bgcolor=&quot;#FFFFCC&quot; | 2D/bidimensional <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | 2D/bidimensionale<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | 2Δ/ διδιάστατο <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fi&quot; | 2D ; kaksidimensioinen <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | 2D ; bidimensional<br /> | bgcolor=&quot;#FFFFCC&quot; | 2D<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | 2D, двухмерный<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 2D；2维<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 2차원<br /> <br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot; | 2.5D <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | 2D1/2 ; pseudo tridimensionnel <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | 2,5D ; zweieinhalbdimensional <br /> | bgcolor=&quot;#FFFFFF&quot; | 2,5D / pseudotridimensional<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | 2,5D / 2 ½ D / pseudo-tridimensionale <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | 2,5Δ/ ψευδοτριδιάστατο <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fi&quot; | 2,5D <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | 2,5D <br /> | bgcolor=&quot;#FFFFFF&quot; | 2,5D <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | 2.5D, псевдодвухмерный<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 2.5D；2.5维<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 2.5차원<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot; | 3D <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | 3D ; tridimensionnel <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | 3D, dreidimensional <br /> | bgcolor=&quot;#FFFFCC&quot; | 3D/tridimensional <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | 3D / tridimensionale <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | 3Δ/ τριδιάστατο <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fi&quot; | 3D| ; kolmedimensioinen <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | 3D; tridimensional<br /> | bgcolor=&quot;#FFFFCC&quot; | 3D <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | 3D, трехмерный<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 3D；3维<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 3차원<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot; | area <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | surface ; entité surfacique <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Fläche <br /> | bgcolor=&quot;#FFFFFF&quot; | área; polígono <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | superficie&lt;br /&gt;poligono <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | επιφάνεια<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fi&quot; | alue<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | área; polígono <br /> | bgcolor=&quot;#FFFFFF&quot; | plocha <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | площадь <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 面积<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 면<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot; | area size <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | aire <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Fläche, Flächengröße <br /> | bgcolor=&quot;#FFFFCC&quot; | área del polígono<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | Area del poligono <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | εμβαδόν επφάνειας <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fi&quot; | alueen koko<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | área do polígono <br /> | bgcolor=&quot;#FFFFCC&quot; | vým&amp;#283;ra plochy <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | площадь<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 面积大小<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 면 크기<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot; | aspect <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | exposition <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Exposition <br /> | bgcolor=&quot;#FFFFFF&quot; | orientación<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | esposizione <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | προσανατολισμός, έκθεση <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fi&quot; | rinnesuunta ; viiste <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | orientação <br /> | bgcolor=&quot;#FFFFFF&quot; | expozice <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | экспозиция <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 方位<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 향<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot; | average <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | moyenne <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Durchschnitt, Mittelwert <br /> | bgcolor=&quot;#FFFFCC&quot; | media<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | medio/a <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | μέσος όρος <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fi&quot; | keskiarvo <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | média <br /> | bgcolor=&quot;#FFFFCC&quot; | pr&amp;#367;m&amp;#283;r <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | среднее <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 平均<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 평균<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot; | bearing <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | gisement<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; |<br /> | bgcolor=&quot;#FFFFFF&quot; | <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fi&quot; | suuntima<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | <br /> | bgcolor=&quot;#FFFFFF&quot; | <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 方位<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | <br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot; | boundaries <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | contours <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | boundaries, Flächengrenze, Grenze <br /> | bgcolor=&quot;#FFFFCC&quot; | contornos<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | confini <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | ισαριθμικές (ισοϋψείς) <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fi&quot; | rajat<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | contornos <br /> | bgcolor=&quot;#FFFFCC&quot; | hranice <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | границы <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 边界<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 경계<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot; | buffer <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | zone tampon ; &lt;em&gt;buffer&lt;/em&gt; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Puffer <br /> | bgcolor=&quot;#FFFFFF&quot; | buffer <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | buffer&lt;br /&gt;area adiacente <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | περιοχή επεξεργασίας (περιφερειακή ζώνη) ; buffer <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fi&quot; | puskuri<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | área de influência <br /> | bgcolor=&quot;#FFFFFF&quot; | buffer, obalová (vyrovnávací) zóna <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | буфер, буферная зона<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 缓冲<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 버퍼<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot; | bulk-labeling <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | étiquetage en masse<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Massenbeschriftung<br /> | bgcolor=&quot;#FFFFCC&quot; | <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | etichettatura di massa <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fi&quot; | massanimiöinti<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | <br /> | bgcolor=&quot;#FFFFCC&quot; | <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 批量标注<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | <br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot; | category <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | catégorie <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Kategorie [pl. Kategorien]<br /> | bgcolor=&quot;#FFFFFF&quot; | categoría<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | categoria <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | κατηγορία <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fi&quot; | luokka <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | categoria <br /> | bgcolor=&quot;#FFFFFF&quot; | kategorie <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | категория <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 类别<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 분류<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot; | cell <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | cellule<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Zelle [pl. Zellen]<br /> | bgcolor=&quot;#FFFFCC&quot; | celda<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | cella<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | κελί<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fi&quot; | solu <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | <br /> | bgcolor=&quot;#FFFFCC&quot; | <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | ячейка <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 单元<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 셀<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot; | [supervised/unsupervised] classification <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | classification [dirigée/non dirigée];[cl. &lt;em&gt;supervisée/non-supervisée&lt;/em&gt; ] <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | [überwachte/unüberwachte] Klassifikation <br /> | bgcolor=&quot;#FFFFFF&quot; | clasificación (supervisada/no supervisada) <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | classificazione (guidata/automatica) <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | [καθοδηγούμενη/αυτόματη] ταξινόμηση <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fi&quot; | [ohjattu / ohjaamaton] luokittelu <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | classificação supervisionada/não supervisionada (pt_BR) [guiada/automática](pt)<br /> | bgcolor=&quot;#FFFFFF&quot; | [&amp;#345;ízená/ne&amp;#345;ízená] klasifikace <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | классификация с обучением/без обучения<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | [监督/非监督] 分类<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | [감독/무감독] 분류<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot; | classify (to) <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | faire une classification <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | klassifizieren <br /> | bgcolor=&quot;#FFFFFF&quot; | clasificar <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | classificare <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | ταξινομώ <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fi&quot; | luokitella <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | classificar <br /> | bgcolor=&quot;#FFFFFF&quot; | klasifikovat <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | классифицировать <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 归类<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 분류하다<br /> <br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot; | cluster <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | grappe ; &lt;em&gt;cluster&lt;/em&gt; <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | cluster <br /> | bgcolor=&quot;#FFFFCC&quot; | grupo; racimo<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | cluster&lt;br /&gt;raggruppamento&lt;br /&gt;grappolo (?) <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | συστάδα (συσταδοποίηση)<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fi&quot; | klusteri <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | agrupamento, ''cluster''<br /> | bgcolor=&quot;#FFFFCC&quot; | cluster, shluk <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | кластер, группа<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 聚类<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 군집<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot; | color table <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | table de couleurs <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Farbtabelle <br /> | bgcolor=&quot;#FFFFFF&quot; | tabla de colores<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | tavola dei colori&lt;br /&gt;tavolozza <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | πίνακας χρωμάτων, χρωματικός πίνακας<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fi&quot; | väritaulu <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | paleta de cores <br /> | bgcolor=&quot;#FFFFFF&quot; | tabulka barev <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | таблица цветов<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 颜色表<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 색상표<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| command <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | commande <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Befehl, Befehlszeile <br /> | bgcolor=&quot;#FFFFCC&quot; | comando <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | comando <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | εντολή <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fi&quot; | komento <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | comando <br /> | bgcolor=&quot;#FFFFCC&quot; | p&amp;#345;íkaz <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | команда <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 命令<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 명령<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| compilation <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | compilation <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Kompilierung <br /> | bgcolor=&quot;#FFFFFF&quot; | compilación <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | compilazione <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | μεταγλώττιση <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fi&quot; | käännös <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | compilação <br /> | bgcolor=&quot;#FFFFFF&quot; | kompilace <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | компиляция <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 编译<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | &amp;nbsp;<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| compile (to) <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | compiler <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | kompilieren <br /> | bgcolor=&quot;#FFFFCC&quot; | compilar <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | compilare <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | μεταγλωττίζω <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fi&quot; | kääntää <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | compilar <br /> | bgcolor=&quot;#FFFFCC&quot; | kompilovat <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | компилировать <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 编译<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | &amp;nbsp;<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| connection <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | connexion <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Verbindung <br /> | bgcolor=&quot;#FFFFFF&quot; | conexión<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | connessione <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | σύνδεση<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fi&quot; | yhteys <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | conexão <br /> | bgcolor=&quot;#FFFFFF&quot; | spojení <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | соединение <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 连接<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 연결<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| curvature <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | courbure <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Krümmung <br /> | bgcolor=&quot;#FFFFCC&quot; | curvatura<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | καμπυλότητα <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fi&quot; | kaarevuus<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | curvatura <br /> | bgcolor=&quot;#FFFFCC&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | кривизна<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 曲率<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 지형만곡<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| dangles <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | arcs/nœuds pendants <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Dangle; Überstände<br /> | bgcolor=&quot;#FFFFFF&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | sporgenza <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | ασυνέχειες<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fi&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | solto (?)<br /> | bgcolor=&quot;#FFFFFF&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | висящие узлы<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 悬挂<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | &amp;nbsp;<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| [relational] database <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | base de données [relationnelle] <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | [relationale] Datenbank <br /> | bgcolor=&quot;#FFFFCC&quot; | base de datos [relacional] <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | base di dati [relazionale]&lt;br /&gt;database [relazionale]<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | [σχεσιακή] βάση δεδομένων <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fi&quot; | [relaatio] tietokanta <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | base (banco) de dados [relacional] <br /> | bgcolor=&quot;#FFFFCC&quot; | [rela&amp;#269;ní] databáze <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | реляционная база данных<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | [关系]数据库<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | [관계형] 데이타베이스<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| [Spearfish] database <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | Base de Données Géographiques [Spearfish] ; &lt;em&gt;géodatabase [Spearfish]&lt;/em&gt; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | [Spearfish] Datensatz<br /> | bgcolor=&quot;#FFFFFF&quot; | base de datos geográficos [Spearfish] <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | base di dati geografici [Spearfish] <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | βάση δεδομένων [Spearfish] <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fi&quot; | [Spearfish] tietokanta <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | base de dados geográficos [Spearfish] <br /> | bgcolor=&quot;#FFFFFF&quot; | dataset [Spearfish] <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | база данных [Spearfish]<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | [Spearfish]数据库<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | [Spearfish] 데이타베이스<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| datum <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | datum <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Datum [pl. Datums] <br /> | bgcolor=&quot;#FFFFCC&quot; | Datum [pl. Datums] <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | ''datum'' <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | datum <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fi&quot; | päiväys <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | datum<br /> | bgcolor=&quot;#FFFFCC&quot; | datum <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | датум<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 大地基准面<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 데이텀<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| DBMS <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | SGBD <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | DBMS <br /> | bgcolor=&quot;#FFFFFF&quot; | SGBD/DBMS <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | DBMS <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | DBMS (σύστημα διαχείρισης βάσεων δεδομένων)<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fi&quot; | DBMS <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | SGBD / DBMS<br /> | bgcolor=&quot;#FFFFFF&quot; | databázový systém <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | СУБД <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 数据库管理系统<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 데이타베이스 시스템<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| digitalization <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | numérisation ; vectorisation ; &lt;em&gt;digitalisation&lt;/em&gt; <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Digitalisierung <br /> | bgcolor=&quot;#FFFFCC&quot; | digitalización <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | digitalizzazione <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | ψηφιακοποίηση (ψηφιοποίηση)<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fi&quot; | digitointi <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | digitalização <br /> | bgcolor=&quot;#FFFFCC&quot; | digitalizace <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | оцифровка, векторизация<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 数字化<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 디지탈화<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| digitize (to) <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | numériser ; vectoriser ; &lt;em&gt;digitaliser&lt;/em&gt; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | digitalisieren <br /> | bgcolor=&quot;#FFFFFF&quot; | digitalizar <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | digitalizzare <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | ψηφιακοποιώ (ψηφιοποιώ)<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fi&quot; | digitoida <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | digitalizar <br /> | bgcolor=&quot;#FFFFFF&quot; | digitalizovat <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | оцифровывать, векторизовать<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 数字化<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 디지탈화하다<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| driver <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | pilote <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Treiber <br /> | bgcolor=&quot;#FFFFCC&quot; | controlador <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | driver <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | οδηγός (πρόγραμμα) ; driver<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fi&quot; | ajuri <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | dispositivo, ''driver'' <br /> | bgcolor=&quot;#FFFFCC&quot; | ovlada&amp;#269; <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | драйвер <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 驱动<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 드라이버<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| ellipsoid <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | ellipsoïde <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Ellipsoid <br /> | bgcolor=&quot;#FFFFFF&quot; | elipsoide<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | ellissoide <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | ελλειψοειδές <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fi&quot; | ellipsoidi <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | elipsóide <br /> | bgcolor=&quot;#FFFFFF&quot; | elipsoid <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | эллипсоид <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 椭球体<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 타원체<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| error matrix <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | matrice de confusion <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Konfusionsmatrix oder Fehlermatrix <br /> | bgcolor=&quot;#FFFFCC&quot; | Matriz de errores<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | matrice di errore <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | μήτρα σφάλματος <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fi&quot; | virhematriisi <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | matriz de erros <br /> | bgcolor=&quot;#FFFFCC&quot; | chybová matice <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | матрица ошибок<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 误差矩阵<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 오류행렬<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| export <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | exportation ; &lt;em&gt;export&lt;/em&gt; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Export <br /> | bgcolor=&quot;#FFFFFF&quot; | exportación <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | esportazione <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | εξαγωγή <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fi&quot; | vienti <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | exportação <br /> | bgcolor=&quot;#FFFFFF&quot; | export <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | экспорт <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 输出<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 내보내기<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| export (to) <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | exporter <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | exportieren <br /> | bgcolor=&quot;#FFFFCC&quot; | exportar <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | esportare <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | εξάγω<br /> | bgcolor=&quot;#FFFFCC&quot; | viedä <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | exportar (para)<br /> | bgcolor=&quot;#FFFFCC&quot; | exportovat <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | экспортировать<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 输出成<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 내보내다<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| file <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | fichier <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Datei <br /> | bgcolor=&quot;#FFFFFF&quot; | archivo<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | file <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | αρχείο<br /> | bgcolor=&quot;#FFFFFF&quot; | tiedosto <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | ficheiro (pt), arquivo (pt_BR)<br /> | bgcolor=&quot;#FFFFFF&quot; | soubor <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | файл <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 文件<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 파일<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| file header <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | en-tête de fichier <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Datei Header <br /> | bgcolor=&quot;#FFFFCC&quot; | encabezado; cabecera<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | header del file <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | κεφαλίδα αρχείου<br /> | bgcolor=&quot;#FFFFCC&quot; | <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | cabeçalho do ficheiro (pt) /cabeçalho do arquivo (pt_BR)<br /> | bgcolor=&quot;#FFFFCC&quot; | hlavi&amp;#269;ka souboru <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | заголовок файла<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 文件头<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 파일헤더<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| format <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | format <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Format <br /> | bgcolor=&quot;#FFFFFF&quot; | formato<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | formato <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | μορφότυπο<br /> | bgcolor=&quot;#FFFFFF&quot; | formaatti ; muoto <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | formato <br /> | bgcolor=&quot;#FFFFFF&quot; | formát <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | формат <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 格式（化）<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 양식<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| free software <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | logiciel libre <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Freie Software <br /> | bgcolor=&quot;#FFFFCC&quot; | Software libre <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | Software libero <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | ελεύθερο λογισμικό<br /> | bgcolor=&quot;#FFFFCC&quot; | vapaa ohjelmisto <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | ''software'' livre <br /> | bgcolor=&quot;#FFFFCC&quot; | svobodný software <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | свободное программное обеспечение<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 自由[免费]软件<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 프리소프트웨어<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| geographic information sciences <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | géomatique ; sciences de l'information géographique <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Geographische Informationswissenschaften<br /> | bgcolor=&quot;#FFFFFF&quot; | geomática <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | geomatica <br /> | bgcolor=&quot;#FFFFFF&quot;lang=&quot;gr&quot; | επιστήμες γεωγραφικών πληροφοριών, γεωπληροφορική<br /> | bgcolor=&quot;#FFFFFF&quot; | geoinformatiikka <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | ciências de informação geográfica , geomática<br /> | bgcolor=&quot;#FFFFFF&quot; | geoinforma&amp;#269;ní v&amp;#283;dy <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | геоинформатика <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 地理信息科学<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 지리정보과학<br /> <br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| Geographic Information System (GIS) <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | Système d'Information Géographique (SIG) <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Geographisches Informationssystem (GIS) <br /> | bgcolor=&quot;#FFFFCC&quot; | Sistema de Información Geográfica (SIG)<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | Sistema Informativo Geografico (GIS) <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | Σύστημα Γεωγραφικών Πληροφοριών (ΣΓΠ)<br /> | bgcolor=&quot;#FFFFCC&quot; | paikkatietojärjestelmä ; GIS<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | Sistemas de Informação Geográfica (SIG) <br /> | bgcolor=&quot;#FFFFCC&quot; | geografický informa&amp;#269;ní systém (GIS) <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | Географическая Информационная Система (ГИС)<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 地理信息系统<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 지리정보시스템<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| GIS manager <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | gestionnaire SIG <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | GIS Manager <br /> | bgcolor=&quot;#FFFFFF&quot; | Administrador GIS <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | Gestore GIS <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | διαχειριστής GIS (περιβάλλον διαχείρισης ΣΓΠ/ΓΠΣ)<br /> | bgcolor=&quot;#FFFFFF&quot; | paikkatietokannan hoitaja <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | administrador (pt), Gerenciador (pt_BR) SIG <br /> | bgcolor=&quot;#FFFFFF&quot; | GIS manager <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | менеджер ГИС<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 地理信息系统管理员<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | GIS 관리자<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| GRASS shell <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | console GRASS <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | GRASS Shell <br /> | bgcolor=&quot;#FFFFCC&quot; | consola de comandos GRASS <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | console testuale GRASS <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | περιβάλλον ελέγχου του GRASS<br /> | bgcolor=&quot;#FFFFCC&quot; | GRASS komentotulkki <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | consola (pt) , console (pt_BR) GRASS<br /> | bgcolor=&quot;#FFFFCC&quot; | p&amp;#345;íkazový &amp;#345;ádek GRASSu <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | оболочка, командная строка GRASS<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | GRASS外壳程序<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | GRASS 명령입력창<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| grid <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | grille <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Raster <br /> | bgcolor=&quot;#FFFFFF&quot; | malla, rejilla, cuadrícula<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | ''grid'' <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | κάνναβος (πλέγμα)<br /> | bgcolor=&quot;#FFFFFF&quot; | ruudukko ; hila <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | malha, grade, ''grid'' <br /> | bgcolor=&quot;#FFFFFF&quot; | m&amp;#345;ížka <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | сетка<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 网格（格网）<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 격자<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| graphics monitor<br /> | bgcolor=&quot;#FFFFFF&quot; | &amp;nbsp;<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Grafik-Fenster<br /> | bgcolor=&quot;#FFFFFF&quot; | monitor gráfico<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | monitor grafico<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | οθόνη γραφικών, μηνύτορας γραφικών<br /> | bgcolor=&quot;#FFFFFF&quot; | graafinen monitori <br /> | bgcolor=&quot;#FFFFFF&quot; | &amp;nbsp;<br /> | bgcolor=&quot;#FFFFFF&quot; | &amp;nbsp;<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | графический монитор<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 图形监视器<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 그래픽 모니터<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| gray scale <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | niveaux de gris <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Graustufen <br /> | bgcolor=&quot;#FFFFCC&quot; | escala de grises<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | scala di grigi <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | κλίμακα του γκρι<br /> | bgcolor=&quot;#FFFFCC&quot; | harmaasävy <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | escala de cinzas <br /> | bgcolor=&quot;#FFFFCC&quot; | stupn&amp;#283; šedi <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | полутоновой, градации серого<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 灰度<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 흑백 스케일<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| Ground Control Points <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | points d'amer <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Passpunkt; Ground Control Points (GCPs) <br /> | bgcolor=&quot;#FFFFFF&quot; | Puntos de Control sobre el Terreno<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | punti di controllo sul terreno <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | φωτοσταθερά (σημεία ελέγχου στο έδαφος)<br /> | bgcolor=&quot;#FFFFFF&quot; | Ground Control Points ;<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | Pontos de Controle Sobre o Terreno<br /> | bgcolor=&quot;#FFFFFF&quot; | identické (vlícovací) body <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | точки привязки<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 地面控制点<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 지상기준점<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| import <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | importation ; &lt;em&gt;import&lt;/em&gt; <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Import <br /> | bgcolor=&quot;#FFFFCC&quot; | importación <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | importazione <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | εισαγωγή (δεδομένων)<br /> | bgcolor=&quot;#FFFFCC&quot; | tuonti ; syöte <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | importar, importação <br /> | bgcolor=&quot;#FFFFCC&quot; | import <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | импорт<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 导入<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 가져오기<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| import (to) <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | importer <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | importieren <br /> | bgcolor=&quot;#FFFFFF&quot; | tuoda <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | importare <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | εισάγω (δεδομένα)<br /> | bgcolor=&quot;#FFFFFF&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | importar<br /> | bgcolor=&quot;#FFFFFF&quot; | importovat <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | импортировать <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 导入<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 가져오다<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| input <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | entrée ; source <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Eingabe <br /> | bgcolor=&quot;#FFFFCC&quot; | entrada <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | inserimento di dati, ''input''<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | είσοδος<br /> | bgcolor=&quot;#FFFFCC&quot; | syöte <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | entrada, digitação<br /> | bgcolor=&quot;#FFFFCC&quot; | vstup <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | ввод<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 输入<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 입력<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| kappa parameter <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | paramètre kappa <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | kappa Parameter <br /> | bgcolor=&quot;#FFFFFF&quot; | parámetro kappa<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | parametro kappa <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | παράμετρος κ (κάππα)<br /> | bgcolor=&quot;#FFFFFF&quot; | kappa parametri <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | parâmetro kappa <br /> | bgcolor=&quot;#FFFFFF&quot; | koeficient kappa <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | коэффициент каппа<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | kappa参数<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | &amp;nbsp;<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| key column <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | clef primaire <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Schlüssel-Spalte <br /> | bgcolor=&quot;#FFFFCC&quot; | llave primaria <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | chiave primaria <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | πεδίο (στήλη) κλειδιού<br /> | bgcolor=&quot;#FFFFCC&quot; | avainsarake <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | coluna primária <br /> | bgcolor=&quot;#FFFFCC&quot; | sloupec s klí&amp;#269;em <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | ключевое поле<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 关键列<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | &amp;nbsp;<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| label <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | étiquette <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Label <br /> | bgcolor=&quot;#FFFFFF&quot; | etiqueta<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | etichetta <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | ετικέτα<br /> | bgcolor=&quot;#FFFFFF&quot; | nimiö <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | etiqueta, rótulo<br /> | bgcolor=&quot;#FFFFFF&quot; | štítek <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | метка <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 标注<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 이름표<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| line <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | ligne <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Linie <br /> | bgcolor=&quot;#FFFFCC&quot; | línea <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | linea <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | γραμμή<br /> | bgcolor=&quot;#FFFFCC&quot; | viiva <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | linha <br /> | bgcolor=&quot;#FFFFCC&quot; | linie <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | линия <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 行<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 선<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| line of sight analysis <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | analyse de type 'horizon visuel' <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Sichtbarkeitsanalyse <br /> | bgcolor=&quot;#FFFFFF&quot; | análisis de línea de horizonte / análisis de visibilidad <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | analisi di visibilità / orizzonte visuale<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | ανάλυση οπτικού πεδίου<br /> | bgcolor=&quot;#FFFFFF&quot; | näkymäanalyysi <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | análise de visibilidade <br /> | bgcolor=&quot;#FFFFFF&quot; | analýza dohlednosti <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | анализ линии видимости<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 视线分析<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 시정선 분석<br /> |-<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| location <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | secteur ; &lt;em&gt;Location&lt;/em&gt; <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Location <br /> | bgcolor=&quot;#FFFFCC&quot; | Localización<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | ''location'' <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | γεωγραφική περιοχή (τοποθεσία)<br /> | bgcolor=&quot;#FFFFCC&quot; | sijainti <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | locação, localização <br /> | bgcolor=&quot;#FFFFCC&quot; | location, lokace <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | область <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 位置<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 위치<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| [analogic] map <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | carte [papier] <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | [analoge] Karte <br /> | bgcolor=&quot;#FFFFFF&quot; | mapa [analógico]<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | mappa cartacea <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | [αναλογικός] χάρτης<br /> | bgcolor=&quot;#FFFFFF&quot; | [analoginen] kartta<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | mapa (papel) <br /> | bgcolor=&quot;#FFFFFF&quot; | [analogová] mapa <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | [аналоговая] карта?<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | [类比] 地图<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | &amp;nbsp;<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| map layer <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | couche <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Kartenebene <br /> | bgcolor=&quot;#FFFFCC&quot; | capa de mapa<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | tematismo di una mappa <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | χαρτογραφικό επίπεδο<br /> | bgcolor=&quot;#FFFFCC&quot; | karttataso <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | capa (pt), camada (pt_BR)<br /> | bgcolor=&quot;#FFFFCC&quot; | mapová vrstva <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | слой<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 地图图层<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 지도 레이어<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| mapset <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | jeu de cartes ; &lt;em&gt;mapset&lt;/em&gt; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Mapset <br /> | bgcolor=&quot;#FFFFFF&quot; | directorio de mapas <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | ''mapset'' <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | χαρτογραφικά δεδομένα<br /> | bgcolor=&quot;#FFFFFF&quot; | karttajoukko ; mapset <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | ''mapset'' <br /> | bgcolor=&quot;#FFFFFF&quot; | mapset - soubor map <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | набор (часть области)<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 地图集<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 지도세트<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| mask <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | masque <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Maske <br /> | bgcolor=&quot;#FFFFCC&quot; | máscara<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | maschera <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | μάσκα<br /> | bgcolor=&quot;#FFFFCC&quot; | maski <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | máscara <br /> | bgcolor=&quot;#FFFFCC&quot; | maska <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | маска <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 掩膜<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 마스크<br /> <br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| MASK <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | MASK <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | MASK <br /> | bgcolor=&quot;#FFFFFF&quot; | 'MASK' <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | MASK <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | MASK <br /> | bgcolor=&quot;#FFFFFF&quot; | MASKI <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | ''MASK'' <br /> | bgcolor=&quot;#FFFFFF&quot; | MASK <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | MASK <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 掩膜<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 마스크<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| monitor <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | moniteur <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Grafik-Fenster <br /> | bgcolor=&quot;#FFFFCC&quot; | monitor <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | monitor <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | οθόνη, μηνύτορας<br /> | bgcolor=&quot;#FFFFCC&quot; | monitori ; näyttö <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | monitor <br /> | bgcolor=&quot;#FFFFCC&quot; | monitor <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | наблюдать, монитор<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 监视器<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 모니터<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| network <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | réseau ; graphe de réseau <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Netzwerk <br /> | bgcolor=&quot;#FFFFFF&quot; | red <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | rete <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | δίκτυο<br /> | bgcolor=&quot;#FFFFFF&quot; | verkosto <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | rede <br /> | bgcolor=&quot;#FFFFFF&quot; | sí&amp;#357; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | сеть <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 网络<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 네트워크<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| node <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | nœud <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Knoten <br /> | bgcolor=&quot;#FFFFCC&quot; | nodo<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | nodo <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | κόμβος<br /> | bgcolor=&quot;#FFFFCC&quot; | solmu <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | nodo (pt), nó (pt_BR)<br /> | bgcolor=&quot;#FFFFCC&quot; | uzel <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | узел <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 节点<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 교점<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| output <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | sortie ; cible <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Ausgabe <br /> | bgcolor=&quot;#FFFFFF&quot; | salida (de datos)<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | uscita, risultato&lt;br /&gt;''output'' <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | έξοδος<br /> | bgcolor=&quot;#FFFFFF&quot; | tuloste <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | saída, resultado <br /> | bgcolor=&quot;#FFFFFF&quot; | výstup <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | вывод, результат<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 输出<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 출력<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| overwrite (to) <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | écraser <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | überschreiben <br /> | bgcolor=&quot;#FFFFCC&quot; | sobrescribir<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | sovrascrivere <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | επεγγράφω (αντικαθιστώ)<br /> | bgcolor=&quot;#FFFFCC&quot; | ylikirjoittaa <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | sobrescrever <br /> | bgcolor=&quot;#FFFFCC&quot; | p&amp;#345;epsat <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | перезаписать<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 改写<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 덮어쓰다<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| [software] package <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | paquet logiciel ; &lt;em&gt;paquetage [logiciel]&lt;/em&gt; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | [Software]paket <br /> | bgcolor=&quot;#FFFFFF&quot; | paquete [software]<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | pacchetto software <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | πακέτο λογισμικού<br /> | bgcolor=&quot;#FFFFFF&quot; | [ohjelmisto] paketti<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | paquete (pt), pacote (pt_BR) de [''software''] <br /> | bgcolor=&quot;#FFFFFF&quot; | [softwarový] balí&amp;#269;ek <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | пакет [программ]<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 软件包<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | [소프트웨어] 패키지<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| partial derivatives <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | dérivées partielles <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | partielle Ableitung <br /> | bgcolor=&quot;#FFFFCC&quot; | derivadas parciales<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | derivate parziali <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | μερικές παράγωγοι<br /> | bgcolor=&quot;#FFFFCC&quot; | osittaisderivaatat <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | derivações (pt), derivadas (pt_BR) parciais <br /> | bgcolor=&quot;#FFFFCC&quot; | parciální derivace <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | частные производные<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 偏导数<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 편미분<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| PERMANENT mapset <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | jeu de cartes PERMANENT ; j. de c. souche <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | PERMANENT Mapset <br /> | bgcolor=&quot;#FFFFFF&quot; | directorio de mapas PERMANENT <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | ''mapset'' PERMANENT <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | PERMANENT χαρτογραφικά δεδομένα (ΥΠΟΒΑΘΡΟ) <br /> | bgcolor=&quot;#FFFFFF&quot; | PERMANENT mapset <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | ''PERMANENT mapset''<br /> | bgcolor=&quot;#FFFFFF&quot; | mapset PERMANENT <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | ПОСТОЯННЫЙ набор<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | PERMANENT 图集<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | PERMANENT 지도세트<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| plug-in <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | extension ; greffon ; &lt;em&gt;plug-in&lt;/em&gt; <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Plugin <br /> | bgcolor=&quot;#FFFFCC&quot; | complemento<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | estesione del programma&lt;br /&gt;plugin <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | επέκταση, (επί-) πρόσθετο (plug-in)<br /> | bgcolor=&quot;#FFFFCC&quot; | liitännäinen <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | extensão, ''plug-in'' <br /> | bgcolor=&quot;#FFFFCC&quot; | zásuvný modul <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | подключаемый модуль<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 插件<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 플러그인<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| point <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | point <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Punkt <br /> | bgcolor=&quot;#FFFFFF&quot; | punto <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | punto <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; |σημείο<br /> | bgcolor=&quot;#FFFFFF&quot; | piste <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | ponto <br /> | bgcolor=&quot;#FFFFFF&quot; | bod <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | точка<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 点<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 점<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| pop-up window <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | &lt;em&gt;fenêtre pop-up&lt;/em&gt; <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Pop-up Fenster <br /> | bgcolor=&quot;#FFFFCC&quot; | Ventana emergente<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | finestra pop-up <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | αναδυόμενο παράθυρο μηνύματος<br /> | bgcolor=&quot;#FFFFCC&quot; | ponnahdusikkuna <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | janela ''pop-up'' <br /> | bgcolor=&quot;#FFFFCC&quot; | vyskakovací okno <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | всплывающее окно<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 弹出窗口<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 팝업창<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| profile <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | profil <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Profil <br /> | bgcolor=&quot;#FFFFFF&quot; | perfil<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | profilo <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; |κατατομή (μηκοτομή)<br /> | bgcolor=&quot;#FFFFFF&quot; | profiili <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | perfil <br /> | bgcolor=&quot;#FFFFFF&quot; | profil <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | профиль <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 廓线<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 단면<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| project <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | projet <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Projekt <br /> | bgcolor=&quot;#FFFFCC&quot; | proyecto <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | progetto <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | έργο<br /> | bgcolor=&quot;#FFFFCC&quot; | projekti <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | projecto, projeto<br /> | bgcolor=&quot;#FFFFCC&quot; | projekt <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | проект<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 投影；项目<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 투영하다, 프로젝트<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| projection <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | projection <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Projektion <br /> | bgcolor=&quot;#FFFFFF&quot; | proyección <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | proiezione (cartografica) <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; |προβολή<br /> | bgcolor=&quot;#FFFFFF&quot; | projektio <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | projecção, projeção<br /> | bgcolor=&quot;#FFFFFF&quot; | projekce (mapová) <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | проекция<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 投影<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 투영<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| prune (to) <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | élaguer <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | säubern, putzen<br /> | bgcolor=&quot;#FFFFCC&quot; | podar <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; |ελαχιστοποιώ (μειώνω)<br /> | bgcolor=&quot;#FFFFCC&quot; | karsia <br /> | bgcolor=&quot;#FFFFCC&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFCC&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | обрезать <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 裁剪<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | &amp;nbsp;<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| raster map <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | carte matricielle ; &lt;em&gt;carte raster&lt;/em&gt; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Rasterkarte <br /> | bgcolor=&quot;#FFFFFF&quot; | mapa ráster <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | mappa ráster <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; |ψηφιδωτό (ψηφιδωτά δεδομένα)<br /> | bgcolor=&quot;#FFFFFF&quot; | rasterikartta <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | mapa ''raster'' <br /> | bgcolor=&quot;#FFFFFF&quot; | rastrová mapa <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | растр <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 栅格地图<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 레스터 지도<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| read (to) <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | lire <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | lesen <br /> | bgcolor=&quot;#FFFFCC&quot; | leer <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | leggere <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; |διαβάζω<br /> | bgcolor=&quot;#FFFFCC&quot; | lukea <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | ler <br /> | bgcolor=&quot;#FFFFCC&quot; | &amp;#269;íst <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | читать<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 读取<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 읽어들이다<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| rectification <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | recalage <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Georeferenzierung <br /> | bgcolor=&quot;#FFFFFF&quot; | rectificación <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | rettificazione&lt;br /&gt;raddrizzamento <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; |γεωαναφορά<br /> | bgcolor=&quot;#FFFFFF&quot; | oikaisu <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | rectificação, retificação<br /> | bgcolor=&quot;#FFFFFF&quot; | rektifikace <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | ректификация, трансформация<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 纠正<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 기하보정<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| rectify (to) <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | recaler <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | georeferenzieren <br /> | bgcolor=&quot;#FFFFCC&quot; | rectificar <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | rettificare <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; |γεωαναφέρω<br /> | bgcolor=&quot;#FFFFCC&quot; | oikaista <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | rectificar, retificar<br /> | bgcolor=&quot;#FFFFCC&quot; | rektifikovat <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | трансформировать <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 纠正<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 기하보정하다<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| region <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | région <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Region; Gebietsausdehnung <br /> | bgcolor=&quot;#FFFFFF&quot; | región <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | ''region'' <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; |περιοχή<br /> | bgcolor=&quot;#FFFFFF&quot; | alue ; seutu <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | região <br /> | bgcolor=&quot;#FFFFFF&quot; | region - zájmové území <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | географический охват, фрагмент<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 区域<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 영역<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| [computational] region <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | région [de calcul] <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFFF&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | regione computazionale (impostata tramite g.region) <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; |&amp;nbsp; <br /> | bgcolor=&quot;#FFFFFF&quot; | [laskennallinen] alue <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFFF&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | [计算的] 区域<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | &amp;nbsp; <br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| resample (to) <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | rééchantillonner <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | resamplen <br /> | bgcolor=&quot;#FFFFCC&quot; | remuestrear <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | ricampionare <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; |επανασυστώ <br /> | bgcolor=&quot;#FFFFCC&quot; | uudelleen näytteistää <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | reamostrar<br /> | bgcolor=&quot;#FFFFCC&quot; | p&amp;#345;evzorkovat <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | пересчитывать(изменять разрешение)<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 重采样<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 리샘플링하다<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| resampling <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | rééchantillonnage <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | resample <br /> | bgcolor=&quot;#FFFFFF&quot; | remuestreo<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | ricampionamento <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; |επανασύσταση<br /> | bgcolor=&quot;#FFFFFF&quot; | uudelleen näytteistäminen <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | reamostragem <br /> | bgcolor=&quot;#FFFFFF&quot; | p&amp;#345;evzorkování <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | ресэмплинг, пересчет<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 重采样<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 리샘플링<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| RGB (Red Green Blue) <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | RVB (Rouge Vert Bleu) ; &lt;em&gt;RGB&lt;/em&gt; <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | RGB (rot grün blau) <br /> | bgcolor=&quot;#FFFFCC&quot; | RGB (Rojo Verde Azul)<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | RGB (Red Green Blue) <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | RGB (κόκκινο πράσινο μπλε) [βασικά χρώματα]<br /> | bgcolor=&quot;#FFFFCC&quot; | RGB (Punainen Vihreä Sininen) <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | ''RGB'' (Vermelho Verde Azul) <br /> | bgcolor=&quot;#FFFFCC&quot; | RGB (&amp;#269;ervená, zelená, modrá) <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | RGB (красный, зеленый, синий)<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | RGB（红绿蓝）<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | RGB (빨강 초록 파랑)<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| RMS error (Root Mean Square) <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | erreur RMS <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | RMS-Fehler <br /> | bgcolor=&quot;#FFFFFF&quot; | Error Medio Cuadrático (RMS)<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | Scarto quadratico medio <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; |σφάλμα RMS, ενεργό σφάλμα<br /> | bgcolor=&quot;#FFFFFF&quot; | keskineliövirheen neliöjuuri <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | erro ''RMS'' (Erro Médio Quadrático) <br /> | bgcolor=&quot;#FFFFFF&quot; | chyba RMS (st&amp;#345;ední kvadratická chyba) <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | ошибка RMS (среднеквадратическая ошибка)<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 均方根<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 평균제곱근오차<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| root <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | administrateur <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Administrator, root <br /> | bgcolor=&quot;#FFFFCC&quot; | root, administrador <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | root, amministratore <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; |διαχειριστής [administrator]<br /> | bgcolor=&quot;#FFFFCC&quot; | root, admistraattori <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | root, administrador <br /> | bgcolor=&quot;#FFFFCC&quot; | root (administrátor) <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | root (админстратор)<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 根；管理员<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 관리자<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| save (to) <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | sauvegarder <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | speichern <br /> | bgcolor=&quot;#FFFFFF&quot; | guardar<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | salvare <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; |αποθηκεύω<br /> | bgcolor=&quot;#FFFFFF&quot; | tallentaa <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | guardar (pt), salvar (pt_BR) <br /> | bgcolor=&quot;#FFFFFF&quot; | ukládat <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | сохранять <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 保存（为）<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 저장하다<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| scan <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | scan <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Scan <br /> | bgcolor=&quot;#FFFFCC&quot; | escaneado <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | scansione <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; |σάρωση<br /> | bgcolor=&quot;#FFFFCC&quot; | skannaus <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | digitalização, escaneamento (pt_BR)<br /> | bgcolor=&quot;#FFFFCC&quot; | scan <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | [от]сканированное изображение<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 扫描<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 스캔<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| scan (to) <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | scanner <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | scannen <br /> | bgcolor=&quot;#FFFFFF&quot; | escanear <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | scansionare <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; |σαρώνω<br /> | bgcolor=&quot;#FFFFFF&quot; | skannata <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | digitalizar, escanear (pt_BR)<br /> | bgcolor=&quot;#FFFFFF&quot; | skenovat <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | сканировать<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 扫描<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 스캔하다<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| shell <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | invite de commande ; &lt;em&gt; shell &lt;/em&gt;<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Shell, Kommandozeile <br /> | bgcolor=&quot;#FFFFCC&quot; | consola de comandos UNIX <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | terminale&lt;br /&gt;linea di comando <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; |περιβάλλον ελέγχου (γραμμή εντολών UNIX)<br /> | bgcolor=&quot;#FFFFCC&quot; | komentotulkki <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | linha de comandos, console, shell<br /> | bgcolor=&quot;#FFFFCC&quot; | p&amp;#345;íkazový &amp;#345;ádek <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | оболочка, командная строка<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 外壳程序<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 명령입력창<br /> <br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| sites map <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | couche de données ponctuelles ; &lt;em&gt;c. de d. sites&lt;/em&gt; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | 'Site' Karte <br /> | bgcolor=&quot;#FFFFFF&quot; | mapa de puntos<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | mappa di siti (punti) <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; |χάρτης θέσεων (περιοχής)<br /> | bgcolor=&quot;#FFFFFF&quot; | kohdekartta <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | mapa de sítios, mapa de pontos<br /> | bgcolor=&quot;#FFFFFF&quot; | bodová mapa <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | точечный слой<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 点数据图<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 대상지 지도<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| slope <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | pente <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Hangneigung, Neigung <br /> | bgcolor=&quot;#FFFFCC&quot; | pendiente<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | pendio; inclinazione <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | κλίσης (μέτρο κλίσης)<br /> | bgcolor=&quot;#FFFFCC&quot; | rinne <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | declive, declividade<br /> | bgcolor=&quot;#FFFFCC&quot; | sklon <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | склон <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 斜面；斜率<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 경사<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| socket <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | &lt;em&gt;socket&lt;/em&gt; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Socket <br /> | bgcolor=&quot;#FFFFFF&quot; | socket <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | ''socket'' <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; |υποδοχή<br /> | bgcolor=&quot;#FFFFFF&quot; | socket <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | soquete, ''socket''<br /> | bgcolor=&quot;#FFFFFF&quot; | skocket <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | сокет <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 套接字<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 소켓<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| space time * dataset <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | <br /> | bgcolor=&quot;#FFFFFF&quot; | <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | dataset spazio temporale * <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; |<br /> | bgcolor=&quot;#FFFFFF&quot; | <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | <br /> | bgcolor=&quot;#FFFFFF&quot; | <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | <br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| spectral signature file <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | fichier de signatures spectrales <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | spektrale Signatur <br /> | bgcolor=&quot;#FFFFCC&quot; | archivo de la firma espectral<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | file della firma spettrale <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; |αρχείο φασματικής υπογραφής (φασματικών χαρακτηριστικών-ιδιοτήτων)<br /> | bgcolor=&quot;#FFFFCC&quot; | spektristen signaalien tiedosto <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | ficheiro [arquivo] de assinatura espectral <br /> | bgcolor=&quot;#FFFFCC&quot; | soubor se spektrálními charakteristikami <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | файл спектральной сигнатуры<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 光谱特征文件<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | &amp;nbsp;<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| SQL clause <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | clause SQL <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | SQL-Befehl<br /> | bgcolor=&quot;#FFFFFF&quot; | cláusula SQL <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | clausola SQL <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; |πρόταση (διατύπωση) SQL<br /> | bgcolor=&quot;#FFFFFF&quot; | SQL lauseke <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | cláusula SQL <br /> | bgcolor=&quot;#FFFFFF&quot; | klauzule SQL <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | оператор SQL<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | SQL语句<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | SQL 구문<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| SQL query <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | requête SQL <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | SQL-Anfrage <br /> | bgcolor=&quot;#FFFFCC&quot; | consulta SQL <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | query SQL&lt;br /&gt;interrograzione SQL <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; |ερώτημα SQL<br /> | bgcolor=&quot;#FFFFCC&quot; | SQL kysely <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | consulta SQL <br /> | bgcolor=&quot;#FFFFCC&quot; | dotaz SQL <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | запрос SQL<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | SQL查询<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | SQL 질의<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| standard deviation <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | écart-type <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Standardabweichung <br /> | bgcolor=&quot;#FFFFFF&quot; | desviación estandard<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | Deviazione standard <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; |τυπική απόκλιση<br /> | bgcolor=&quot;#FFFFFF&quot; | keskihajonta <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | desvio padrão<br /> | bgcolor=&quot;#FFFFFF&quot; | standardní odchylka <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | стандартное отклонение<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 标准偏差<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 표준편차<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| steepness <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | raideur ; escarpement<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Steilheit <br /> | bgcolor=&quot;#FFFFCC&quot; | inclinación<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | Pendenza <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | κλίση (απόκρημνο – απότομο)<br /> | bgcolor=&quot;#FFFFCC&quot; | jyrkkyys <br /> | bgcolor=&quot;#FFFFCC&quot; | inclinação, declividade <br /> | bgcolor=&quot;#FFFFCC&quot; | p&amp;#345;íklonnost <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | крутизна <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 坡度<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 가파르기<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| surface <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | surface <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Oberfläche <br /> | bgcolor=&quot;#FFFFFF&quot; | superficie<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | superficie <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; |ανάγλυφο<br /> | bgcolor=&quot;#FFFFFF&quot; | pinta <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | superfície <br /> | bgcolor=&quot;#FFFFFF&quot; | povrch <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | поверхность <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 表面<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 표면<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| [attribute] table <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | table [attributaire] <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Attributtabelle <br /> | bgcolor=&quot;#FFFFCC&quot; | tabla [de atributos ]<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | tabella [degli attributi] <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; |πίνακας [ιδιοτήτων]<br /> | bgcolor=&quot;#FFFFCC&quot; | [attribuutti] taulu <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | tabela [atributos] <br /> | bgcolor=&quot;#FFFFCC&quot; | [atributová] tabulka <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | таблица [атрибутов]<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | [属性]表<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | [속성]표<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| thematic mapping<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | <br /> | bgcolor=&quot;#FFFFFF&quot; | <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | mappa tematica<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | <br /> | bgcolor=&quot;#FFFFFF&quot; | <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | <br /> | bgcolor=&quot;#FFFFFF&quot; |<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; |<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | <br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| timestamp <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | étiquette date&amp;amp;heure ; &lt;em&gt;timestamp&lt;/em&gt; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Zeitstempel <br /> | bgcolor=&quot;#FFFFFF&quot; | indicador de tiempo<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | χρονοσφραγίδα<br /> | bgcolor=&quot;#FFFFFF&quot; | aikaleima <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | etiqueta de data <br /> | bgcolor=&quot;#FFFFFF&quot; | &amp;#269;asová zna&amp;#269;ka <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | временная метка<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 时间戳<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 타임스탬프<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| transect <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | transect <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Transekt, Profilschnitt <br /> | bgcolor=&quot;#FFFFCC&quot; | transecto<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | transetto <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; |τομή<br /> | bgcolor=&quot;#FFFFCC&quot; | linja <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | trajecto, perfil<br /> | bgcolor=&quot;#FFFFCC&quot; | transekt (profil) <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | трансекта, профиль<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 横断面<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 횡단하다<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| variance <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | variance <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Varianz <br /> | bgcolor=&quot;#FFFFFF&quot; | varianza<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | varianza <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; |μεταβλητότητα<br /> | bgcolor=&quot;#FFFFFF&quot; | varianssi <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | variância <br /> | bgcolor=&quot;#FFFFFF&quot; | variance <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | вариация <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 方差<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 변동<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| vector map <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | carte vecteur ; carte vectorielle <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Vektorkarte <br /> | bgcolor=&quot;#FFFFCC&quot; | mapa vectorial <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | mappa vettoriale <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | διανυσματικά δεδομένα (διανύσματα)<br /> | bgcolor=&quot;#FFFFCC&quot; | vektorikartta <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | mapa vectorial [vetorial]<br /> | bgcolor=&quot;#FFFFCC&quot; | vektorová mapa <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | векторная карта<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 矢量地图<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 벡터 지도<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| vectorization <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | vectorisation <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Vektorisierung <br /> | bgcolor=&quot;#FFFFFF&quot; | vectorización <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | Digitalizzazione/Vettorizzazione <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | διανυσματοποίηση<br /> | bgcolor=&quot;#FFFFFF&quot; | vektorointi <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | vectorização, vetorização<br /> | bgcolor=&quot;#FFFFFF&quot; | vektorizace <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | векторизация<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 矢量化<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 벡터화<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| vectorize (to) <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | vectoriser <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | vektorisieren <br /> | bgcolor=&quot;#FFFFCC&quot; | vectorizar <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | vettorizzare&lt;br /&gt;digitalizzare (mappe cartacee)<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | διανυσματοποιώ (ψηφιοποιώ)<br /> | bgcolor=&quot;#FFFFCC&quot; | vektoroida <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | vectorizar [vetorizar]<br /> | bgcolor=&quot;#FFFFCC&quot; | vektorizovat <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | векторизовать<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 矢量化<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 벡터화하다<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| vertice <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | vertex, (Pl) vertices <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Vertex, (Pl) Vertices<br /> | bgcolor=&quot;#FFFFFF&quot; | vértice <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | linea vettoriale <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | κορυφή<br /> | bgcolor=&quot;#FFFFFF&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | vértice <br /> | bgcolor=&quot;#FFFFFF&quot; | lomový (op&amp;#283;rný) bod <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | узел, вершина<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 顶点<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 정점<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| viewer <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | visualiseur <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Betrachter, Viewer <br /> | bgcolor=&quot;#FFFFCC&quot; | visor <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | visualizzatore <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | θέαση (μέσο οπτικοποίησης)<br /> | bgcolor=&quot;#FFFFCC&quot; | katsoja <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | vizualizador <br /> | bgcolor=&quot;#FFFFCC&quot; | prohlíže&amp;#269; <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | визуализатор, программа просмотра <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 查看器<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 뷰어<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot;| workspace <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | espace de travail<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Workspace <br /> | bgcolor=&quot;#FFFFCC&quot; | entorno de trabajo <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | Ambiente di lavoro<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; |χώρος εργασίας<br /> | bgcolor=&quot;#FFFFCC&quot; | työtila <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | <br /> | bgcolor=&quot;#FFFFCC&quot; | <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | рабочее пространство, проект<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | 工作区<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | 작업공간<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot;| write (to) <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | écrire <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | schreiben <br /> | bgcolor=&quot;#FFFFFF&quot; | escribir <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | scrivere <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; |εγγράφω<br /> | bgcolor=&quot;#FFFFFF&quot; | kirjoittaa <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | escrever <br /> | bgcolor=&quot;#FFFFFF&quot; | zapsat <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | записать <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | 写入<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | 쓰다<br /> |}<br /> <br /> == GUI Glossary ==<br /> <br /> {| border=&quot;1&quot; class=&quot;wikitable sortable&quot; style=&quot;margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaaaaa solid; border-collapse: collapse;&quot;<br /> |-<br /> ! bgcolor=&quot;#99CCCC&quot; | ENGLISH<br /> ! bgcolor=&quot;#99CCCC&quot; | FRENCH<br /> ! bgcolor=&quot;#99CCCC&quot; | GERMAN<br /> ! bgcolor=&quot;#99CCCC&quot; | SPANISH<br /> ! bgcolor=&quot;#99CCCC&quot; | [http://wiki.gfoss.it/index.php/Traduzioni ITALIAN]<br /> ! bgcolor=&quot;#99CCCC&quot; | GREEK<br /> ! bgcolor=&quot;#99CCCC&quot; | FINNISH<br /> ! bgcolor=&quot;#99CCCC&quot; | [[Traducao | PORTUGUESE]]<br /> ! bgcolor=&quot;#99CCCC&quot; | CZECH<br /> ! bgcolor=&quot;#99CCCC&quot; | [http://gis-lab.info/docs/grass/glossary.html RUSSIAN]<br /> ! bgcolor=&quot;#99CCCC&quot; | CHINESE(Simplified)<br /> ! bgcolor=&quot;#99CCCC&quot; | KOREAN<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot; | GRASS GIS Layer Manager<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | Gestionnaire de couches GRASS GIS<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Ebenen-Manager<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;es&quot; | &amp;nbsp;Administrador de capas GRASS GIS<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | GRASS GIS Gestore Layer<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | &amp;nbsp;<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fi&quot; | GRASS GIS tason hallinta <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;cz&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | &amp;nbsp;<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | GRASS GIS图层管理面板<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | &amp;nbsp;<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot; | GRASS GIS Map Display<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | Affichage de cartes GRASS GIS<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | Kartenfenster<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;es&quot; | &amp;nbsp;Visualizador de mapas GRASS GIS<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | GRASS GIS Visualizzatore Mappe <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | &amp;nbsp;<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fi&quot; | GRASS GIS Karttanäyttö <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;cz&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | &amp;nbsp;<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | GRASS GIS地图显示<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | &amp;nbsp;<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot; | GRASS GIS Raster Map Calculator<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | Calculateur de carte raster GRASS GIS<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;es&quot; | &amp;nbsp;Calculadora de mapas ráster GRASS GIS<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | GRASS GIS Calcolatore per Raster Map Algebra<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | &amp;nbsp;<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fi&quot; | GRASS GIS Rasterikartan laskin <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;cz&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | &amp;nbsp;<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | GRASS GIS栅格地图计算器<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | &amp;nbsp;<br /> |-<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;en&quot; | GRASS GIS Cartographic Composer<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fr&quot; | Composeur cartographique GRASS GIS<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;de&quot; | ???<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;es&quot; | &amp;nbsp;Diseñador cartográfico GRASS GIS<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;it&quot; | GRASS GIS Compositore Cartografico<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;gr&quot; | &amp;nbsp;<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;fi&quot; | GRASS GIS Kartografinen muotoilija <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;pt&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;cz&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ru&quot; | &amp;nbsp;<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;zh_cn&quot; | GRASS GIS地图设计面板<br /> | bgcolor=&quot;#FFFFCC&quot; lang=&quot;ko&quot; | &amp;nbsp;<br /> |-<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;en&quot; | GRASS GIS Attribute Table Manager<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fr&quot; | Gestionnaire de table attributaire GRASS GIS<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;de&quot; | Attributtabellen-Manager<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;es&quot; | &amp;nbsp;Administrador de tabla de atributos GRASS GIS<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;it&quot; | GRASS GIS Gestore Tabella degli Attributi<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;gr&quot; | &amp;nbsp;<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;fi&quot; | GRASS GIS Attribuuttitaulun hallinta <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;pt&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;cz&quot; | &amp;nbsp; <br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ru&quot; | &amp;nbsp;<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;zh_cn&quot; | GRASS GIS属性表面板<br /> | bgcolor=&quot;#FFFFFF&quot; lang=&quot;ko&quot; | &amp;nbsp;<br /> |-<br /> |}<br /> <br /> == See also ==<br /> <br /> * [http://wiki.osgeo.org/wiki/SIG:_Glossário_Português SIG: Glossário Português]<br /> [[Category:Documentation]]<br /> * [http://ec.europa.eu/comm/eurostat/research/index.htm?http://www.europa.eu.int/en/comm/eurostat/research/isi/&amp;1 ISI glossary of statistical terms]<br /> <br /> [[Category: Translation]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=Talk:GRASS_Community_Sprint_Genova_2017&diff=23943 2017-02-10T15:00:06Z

<p>Lucadelu: </p> <hr /> <div>== Participants and Reports ==<br /> <br /> === Martin Landa ===<br /> <br /> * {{trac|3270}}<br /> * {{trac|3266}}<br /> * {{trac|2460}}<br /> * {{trac|3224}}<br /> * fix cs po file (plural forms)<br /> * {{trac|3280}}<br /> * fix broken table/column dependecies, see {{rev|70518}}<br /> * {{trac|3244}}<br /> * {{trac|2055}}<br /> * See [https://trac.osgeo.org/grass/timeline?from=Feb+12%2C+2017&amp;daysback=4&amp;authors=martinl&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;sfp_email=&amp;sfph_mail=&amp;update=Update SVN logs overview]<br /> <br /> Planned:<br /> * {{trac|2564}}<br /> * mediawiki upgrade<br /> <br /> === Elena Mezzini ===<br /> <br /> * GRASS GUI Italian translation.<br /> * update of Transifex Italian Glossary for GRASS project<br /> <br /> Planned:<br /> * Hope to reach 500 untranslated strings (or less)<br /> <br /> === Luca Delucchi ===<br /> <br /> * apply Veronica Andreo patch for r.modis<br /> * removed pyModis lib from r.modis, now it is using the system one {{rev|70528}}<br /> * closed ticket {{trac|3268}}<br /> * improve Transifex transition:<br /> ** create script to download po files from Transifex {{rev|70526}}<br /> ** added info in the wiki page<br /> ** added more translation files in Transifex</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=Talk:GRASS_Community_Sprint_Genova_2017&diff=23942 2017-02-10T14:24:44Z

<p>Lucadelu: </p> <hr /> <div>== Participants and Reports ==<br /> <br /> === Martin Landa ===<br /> <br /> * {{trac|3270}}<br /> * {{trac|3266}}<br /> * {{trac|2460}}<br /> * {{trac|3224}}<br /> * fix cs po file (plural forms)<br /> * {{trac|3280}}<br /> * fix broken table/column dependecies, see {{rev|70518}}<br /> * {{trac|3244}}<br /> * {{trac|2055}}<br /> * See [https://trac.osgeo.org/grass/timeline?from=Feb+12%2C+2017&amp;daysback=4&amp;authors=martinl&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;sfp_email=&amp;sfph_mail=&amp;update=Update SVN logs overview]<br /> <br /> Planned:<br /> * {{trac|2564}}<br /> * mediawiki upgrade<br /> <br /> === Elena Mezzini ===<br /> <br /> * GRASS GUI Italian translation.<br /> * update of Transifex Italian Glossary for GRASS project<br /> <br /> Planned:<br /> * Hope to reach 500 untranslated strings (or less)<br /> <br /> === Luca Delucchi ===<br /> <br /> * apply Veronica Andreo patch for r.modis<br /> * removed pyModis lib from r.modis, now it is using the system one {{rev|70528}}<br /> * improve Transifex transition:<br /> ** create script to download po files from Transifex {{rev|70526}}<br /> ** added info in the wiki page<br /> ** added more translation files in Transifex</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=Talk:GRASS_Community_Sprint_Genova_2017&diff=23940 2017-02-10T10:55:01Z

<p>Lucadelu: improved report for community sprint</p> <hr /> <div>== Participants and Reports ==<br /> <br /> === Martin Landa ===<br /> <br /> * {{trac|3270}}<br /> * {{trac|3266}}<br /> * {{trac|2460}}<br /> * {{trac|3224}}<br /> * fix cs po file (plural forms)<br /> * {{trac|3280}}<br /> * fix broken table/column dependecies, see {{rev|70518}}<br /> * {{trac|3244}}<br /> * See [https://trac.osgeo.org/grass/timeline?from=Feb+12%2C+2017&amp;daysback=4&amp;authors=martinl&amp;milestone=on&amp;ticket=on&amp;changeset=on&amp;wiki=on&amp;sfp_email=&amp;sfph_mail=&amp;update=Update SVN logs overview]<br /> <br /> Planned:<br /> * {{trac|2055}}<br /> * {{trac|2564}}<br /> <br /> * mediawiki upgrade<br /> <br /> === Elena Mezzini ===<br /> <br /> * GRASS GUI Italian translation.<br /> * update of Transifex Italian Glossary for GRASS project<br /> <br /> Planned:<br /> * Hope to reach 500 untranslated strings (or less)<br /> <br /> === Luca Delucchi ===<br /> <br /> * apply Veronica Andreo patch for r.modis<br /> * improve Transifex transition:<br /> * create script to download po files from Transifex {{rev|70526}}<br /> * added info in the wiki page</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_messages_translation&diff=23939 2017-02-10T10:46:35Z

<p>Lucadelu: improved transifex doc</p> <hr /> <div>== Help page translations ==<br /> <br /> * For translations of full help (man) pages see [[Updating GRASS Documentation#Translations]]<br /> <br /> == GRASS messages translation project ==<br /> <br /> Many users prefer to use software in their mother tongue which is mostly not English. This requires that all GRASS software messages have to be translated to languages other than English. The GRASS Development Team is seeking translators. Please subscribe to the dedicated mailing list at<br /> <br /> GRASS translations mailing list<br /> http://lists.osgeo.org/mailman/listinfo/grass-translations<br /> <br /> Translation related issues may be discussed there. This is an opportunity for non-programmers to contribute as messages can be easily translated. No programming skills required!<br /> <br /> * Join the [[GRASS_Translation_Team#Members_of_Translation_Team|team]]<br /> <br /> === Wanted languages ===<br /> <br /> Simple Chinese, Swahili, Hindi, Greek, Tamil, Russian, Telugu, Português, ... Please join us!<br /> <br /> == How to change the language ==<br /> <br /> * see [[GRASS_messages_translation#Testing_different_languages|Testing different languages]] below.<br /> <br /> == How to start or update translations ==<br /> <br /> * For terminology, please refer to the [[GRASS Translation Glossary]].<br /> <br /> === Files to be edited (downloaded) ===<br /> <br /> ==== GRASS GIS 6 ====<br /> In GRASS GIS 6, we have 5 types of .po files per language (the files are stored in the source code, in directory locale/po/; &lt;br&gt;<br /> or simply '''[http://svn.osgeo.org/grass/grass/branches/releasebranch_6_4/locale/po/ download .po files here]'''):<br /> <br /> * &lt;tt&gt;grasslibs_LANG.po&lt;/tt&gt;: messages from libraries<br /> * &lt;tt&gt;grassmods_LANG.po&lt;/tt&gt;: messages from commands (&quot;modules&quot;)<br /> * &lt;tt&gt;grassnviz_LANG.po&lt;/tt&gt;: messages from NVIZ Tcl/Tk graphical user interface (GRASS 6)<br /> * &lt;tt&gt;grasstcl_LANG.po&lt;/tt&gt;: messages from Tcl/Tk graphical user interface (GRASS 6)<br /> * &lt;tt&gt;grasswxpy_LANG.po&lt;/tt&gt;: messages from wxgrass/wxPython graphical user interface<br /> <br /> where &quot;LANG&quot; in the above file names is a two character code which indicates the language. It is based on the Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column). Example: &lt;tt&gt;grasswxpy_pl.po&lt;/tt&gt; for Polish.<br /> <br /> ==== GRASS GIS 7 ====<br /> In GRASS GIS 7, we have only 3 types of .po files per language (the files are stored in the source code, in directory locale/po/; &lt;br&gt;<br /> or simply '''[http://svn.osgeo.org/grass/grass/branches/releasebranch_7_0/locale/po/ download .po files here]'''):<br /> <br /> * &lt;tt&gt;grasslibs_LANG.po&lt;/tt&gt;: messages from libraries<br /> * &lt;tt&gt;grassmods_LANG.po&lt;/tt&gt;: messages from commands (&quot;modules&quot;)<br /> * &lt;tt&gt;grasswxpy_LANG.po&lt;/tt&gt;: messages from wxgrass/wxPython graphical user interface<br /> <br /> where &quot;LANG&quot; in the above file names is a two character code which indicates the language. It is based on the Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column). Example: &lt;tt&gt;grasswxpy_pl.po&lt;/tt&gt; for Polish.<br /> <br /> === Continuing an existing translation ===<br /> <br /> The file(s) are there but partially outdated? Read on.<br /> <br /> First '''announce''' on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] that you plan to continue the translation of a certain language. Why? Because sometimes people silently translate already and we need these efforts to be coordinated to avoid doing it twice...<br /> <br /> Then get these four .po files for your language and start. If a file is missing, just ask on the list to get it generated or see next section. To get these .po files (the files are in the directory locale/po/):<br /> <br /> * either [http://svn.osgeo.org/grass/grass/branches/releasebranch_7_0/locale/po/ download current .po files] directly from SVN (click on file name to download),<br /> * or [http://trac.osgeo.org/grass/wiki/DownloadSource#GRASS7.0 download source code package] from SVN,<br /> * or download the recent [http://grass.osgeo.org/grass70/source/snapshot/ source code snapshot],<br /> * or ask on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] for these files.<br /> <br /> Then edit the files with a .po file editor (poEDIT or kbabel or..., see below). Take care to maintain layout and special characters. And '''submit often''' - if you wait for weeks, the messages may already be outdated and your time wasted. Just keep in touch on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list]!<br /> <br /> === Starting a new translation ===<br /> <br /> The language you want isn't yet there? Read on.<br /> <br /> Briefly, the steps to create new messages files are (if you find this too complicated, ask on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] to get these files done for you!):<br /> <br /> # Get the latest source code development version from either the SVN repository or as SVN snapshot (see [http://grass.osgeo.org/download/index.php Download]).<br /> # run: './configure --with-nls [... other parameters]' to configure the GRASS source code <br /> # run: 'cd locale' to change into the translation directory<br /> # run: 'make pot' to create grass*.pot template files (to extract original messages)<br /> # run: copy these file from templates/ into po/; rename them to contain the two characters language code (see Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1]) and to .po extension; update the file headers either manually or with your .po editing software<br /> (Example: Polish language):<br /> mv ./templates/grasslibs.pot ./po/grasslibs_pl.po<br /> mv ./templates/grassmods.pot ./po/grassmods_pl.po<br /> mv ./templates/grassnviz.pot ./po/grassnviz_pl.po<br /> mv ./templates/grasstcl.pot ./po/grasstcl_pl.po<br /> mv ./templates/grasswxpy.pot ./po/grasswxpy_pl.po<br /> <br /> Now translate the messages in these po/*.po files (using poEDIT or other editor, see below)<br /> <br /> From time to time messages need to be updated from the originals. This is usually done by the GRASS translation manager.<br /> <br /> == Software to translate: .po file editors ==<br /> <br /> * [http://userbase.kde.org/Lokalize Lokalize]: (previously KBabel) is a set of tools for editing and managing gettext PO files, cross-platform, comes with KDE SC (works also under MS-Windows)<br /> * [http://www.poedit.net/download.php poEdit]: poEdit is gettext catalogs (.po files) editor (works also under MS-Windows)<br /> * [http://translate.sourceforge.net/wiki/virtaal/index Virtaal] Virtaal is cross-platform graphical translation tool with terminology help from [http://open-tran.eu Open-Tran.eu]<br /> * '''[https://www.transifex.com/grass-gis/grass72/ Web based solution Transifex]''' (''see below, join us!'')<br /> * [http://www.omegat.org/ Java based solution OmegaT]<br /> &lt;!--<br /> '''How to use Transifex to translate messages online in a browser:'''<br /> <br /> [[Image:Transifex register signin.png|center|450px|Register and sign in]]<br /> <br /> [[Image:Transifex edit online.png|center|450px|Click to edit online]]<br /> --&gt;<br /> <br /> == Transifex ==<br /> <br /> === How to translate ===<br /> '''''NOTE: THIS IS FOR TRANSLATOR'''''<br /> <br /> Register your self on [https://www.transifex.com/ Transifex website], join the [https://www.transifex.com/grass-gis/ GRASS GIS project] and start to translate (grasswxpy is the GUI translation and it should be the first translated).<br /> <br /> === Create a new project ===<br /> <br /> '''''NOTE: CORE DEVELOPERS ONLY!'''''<br /> <br /> A project should be done for each stable release, only an Organization Administrators can create a project. From the dashboard in the left bottom corner there is &quot;'''New project'''&quot; button. Fill all the field in the form. More info in [https://docs.transifex.com/projects/creating-a-project Transifex documentation]<br /> <br /> Once the new project is created you need to upload the resources (the pot file to translate).<br /> To create the pot files you can execute<br /> make pot<br /> <br /> inside the '''locale''' folder. Now you can load in the Resource section, after you added them you can link the pot file with an online version to get updates. To do this click on &quot;'''Auto update resources'''&quot; bottom (read also the [https://docs.transifex.com/projects/uploading-content Transifex documentation].<br /> <br /> At this point you need to load the translated po files, for each language and file you have to upload the translation po file. Some errors could appear, resolution of this problems is a TODO<br /> <br /> === Get the translated po files ===<br /> <br /> '''''NOTE: THIS IS FOR DEVELOPER OR POWER USER'''''<br /> <br /> It is possible to get back the translated po files automatically using the [https://docs.transifex.com/client/introduction Transifex client]<br /> <br /> To download the file it is required to create a folder to initialize the Transifex project using the command<br /> <br /> tx init --user=USERNAME --passwd=PASSWORD<br /> <br /> --user and --passwd option are useful to create the ''.transifexrc'' file in your $HOME to save user and password, otherwise you can create the file by your self, like the following one<br /> <br /> [https://www.transifex.com]<br /> hostname = https://www.transifex.com<br /> password = PASSWORD<br /> token = <br /> username = USERNAME<br /> <br /> At this point you need to configure the repository modifying the ''.tx/config'' file created in your folder. The following file is working for [https://www.transifex.com/grass-gis/grass72 GRASS 7.2 project], you need to add a section for each resource. <br /> <br /> [main]<br /> host = https://www.transifex.com<br /> <br /> [grass72.grasslibspot]<br /> type = PO<br /> source_lang = en<br /> source_file = ../templates/grasslibs.pot<br /> <br /> [grass72.grassmodspot]<br /> type = PO<br /> source_lang = en<br /> source_file = ../templates/grassmods.pot<br /> <br /> [grass72.grasswxpypot]<br /> type = PO<br /> source_lang = en<br /> source_file = ../templates/grasswxpy.pot<br /> <br /> '''''NOTE: THIS SHOULD NOT BE RUN IF YOU WANT TO RUN transifex_merge.sh '''''<br /> <br /> Now you can download all the translated po files with the following command<br /> <br /> tx pull -a<br /> <br /> == Testing different languages ==<br /> <br /> Testing different languages requires that the respective language environment and, if needed, fonts are installed.<br /> Check what languages are currently installed on your system with:<br /> locale -a<br /> <br /> To change to a certain language environment (locale), do the following steps (here, example for Unix style environment):<br /> <br /> 1. Define/check language settings:<br /> echo $LANG<br /> echo $LANGUAGE<br /> echo $LC_MESSAGES<br /> <br /> 2. Change it (example for to Japanese):<br /> a) bash shell:<br /> export LANG=ja_JP.UTF-8<br /> export LANGUAGE=ja_JP.UTF-8<br /> export LC_MESSAGES=ja_JP.UTF-8<br /> <br /> <br /> b) (t)csh shell:<br /> setenv LANG ja_JP.UTF-8<br /> setenv LANGUAGE ja_JP.UTF-8<br /> setenv LC_MESSAGES ja_JP.UTF-8<br /> <br /> Now launch GRASS in this terminal. If you launch it from an icon, you have to change the LOCALE in the computer setup program instead.<br /> <br /> Other common languages useful for testing are &lt;tt&gt;de_DE&lt;/tt&gt; for German, &lt;tt&gt;fr_FR&lt;/tt&gt; for French, or &quot;C&quot; for none (effectively &lt;tt&gt;en_US&lt;/tt&gt;, which for GRASS is the base language).<br /> <br /> === Creating startup scripts for different languages ===<br /> <br /> GRASS in English language, save as &quot;grass64eng&quot; (executable flag set, store in path):<br /> #!/bin/sh<br /> export LANG=en_US<br /> export LANGUAGE=en_US<br /> export LC_MESSAGES=en_US<br /> exec grass64 &quot;$@&quot;<br /> <br /> GRASS in Japanese language, save as &quot;grass64ja&quot; (executable flag set, store in path):<br /> #!/bin/sh<br /> export LANG=ja_JA.UTF-8<br /> export LANGUAGE=ja_JA.UTF-8<br /> export LC_MESSAGES=ja_JA.UTF-8<br /> grass64 &quot;$@&quot;<br /> <br /> == Coordination among translators ==<br /> <br /> If several translators work on the same language files, obviously some coordination is needed. Please announce work via the &quot;translations&quot; mailing list at http://lists.osgeo.org/mailman/listinfo/grass-translations <br /> <br /> Also the translation manager is listening there to the upload the changed files into the GRASS source code repository.<br /> <br /> == Best practices ==<br /> <br /> * Italiano: [http://tp.linux.it/buona_traduzione.html Regole per la buona traduzione]<br /> <br /> == Installation of language packages ==<br /> <br /> Example: Chinese<br /> <br /> * Mandriva: urpmi locales-zh kde-l10n-zh_CN fonts-ttf-default-zh_CN<br /> * Fedora: the locales should be already present<br /> ** list all valid locales on the system: localectl list-locales<br /> ** show current settings: localectl status<br /> ** set new locale: localectl set-locale LANG=zh_CN.utf8 LC_MESSAGES=zh_CN.utf8<br /> <br /> == Updating messages in the source code ==<br /> <br /> Generally, to support i18N multiple languages, message strings in GRASS must be modified by adding so-called [https://www.gnu.org/software/gettext/ gettext macros] &lt;tt&gt;'''_('''&quot;...&quot;''')'''&lt;/tt&gt;.<br /> <br /> === C programming language ===<br /> <br /> Change from<br /> fprintf ( ..., &quot;...\n&quot;, ...);<br /> to either<br /> fprintf ( ..., _(&quot;...\n&quot;), ...);<br /> or usually (while omitting \n)<br /> G_message ( _(&quot;...&quot;), ...);<br /> <br /> === Python programming language ===<br /> <br /> In Python, the macro is used like this:<br /> &lt;source lang=&quot;python&quot;&gt;<br /> grass.message(_('Raster map &lt;{name}&gt; unpacked'.format(name=map_name)))<br /> &lt;/source&gt;<br /> <br /> === Important hints ===<br /> <br /> Beware:<br /> * G_message should be used for messages - information about the process for user while fprintf(stdout...) for data output.<br /> * G_message output is not expected to be send to pipe or file.<br /> * fprintf(stdout...) output is usually send to pipe or file.<br /> <br /> Programming details are available in the file locale/[https://svn.osgeo.org/grass/grass/trunk/locale/README README].<br /> <br /> Important:<br /> * [https://trac.osgeo.org/grass/wiki/MessageStandardization Message Standardization]: How should Errors/Warnings/Messages be formatted, Macros etc<br /> <br /> == See also ==<br /> <br /> * Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column)<br /> <br /> <br /> [[Category: Development]]<br /> [[Category: Documentation]]<br /> [[Category: FAQ]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_messages_translation&diff=23937 2017-02-10T10:37:09Z

<p>Lucadelu: improved transifex doc</p> <hr /> <div>== Help page translations ==<br /> <br /> * For translations of full help (man) pages see [[Updating GRASS Documentation#Translations]]<br /> <br /> == GRASS messages translation project ==<br /> <br /> Many users prefer to use software in their mother tongue which is mostly not English. This requires that all GRASS software messages have to be translated to languages other than English. The GRASS Development Team is seeking translators. Please subscribe to the dedicated mailing list at<br /> <br /> GRASS translations mailing list<br /> http://lists.osgeo.org/mailman/listinfo/grass-translations<br /> <br /> Translation related issues may be discussed there. This is an opportunity for non-programmers to contribute as messages can be easily translated. No programming skills required!<br /> <br /> * Join the [[GRASS_Translation_Team#Members_of_Translation_Team|team]]<br /> <br /> === Wanted languages ===<br /> <br /> Simple Chinese, Swahili, Hindi, Greek, Tamil, Russian, Telugu, Português, ... Please join us!<br /> <br /> == How to change the language ==<br /> <br /> * see [[GRASS_messages_translation#Testing_different_languages|Testing different languages]] below.<br /> <br /> == How to start or update translations ==<br /> <br /> * For terminology, please refer to the [[GRASS Translation Glossary]].<br /> <br /> === Files to be edited (downloaded) ===<br /> <br /> ==== GRASS GIS 6 ====<br /> In GRASS GIS 6, we have 5 types of .po files per language (the files are stored in the source code, in directory locale/po/; &lt;br&gt;<br /> or simply '''[http://svn.osgeo.org/grass/grass/branches/releasebranch_6_4/locale/po/ download .po files here]'''):<br /> <br /> * &lt;tt&gt;grasslibs_LANG.po&lt;/tt&gt;: messages from libraries<br /> * &lt;tt&gt;grassmods_LANG.po&lt;/tt&gt;: messages from commands (&quot;modules&quot;)<br /> * &lt;tt&gt;grassnviz_LANG.po&lt;/tt&gt;: messages from NVIZ Tcl/Tk graphical user interface (GRASS 6)<br /> * &lt;tt&gt;grasstcl_LANG.po&lt;/tt&gt;: messages from Tcl/Tk graphical user interface (GRASS 6)<br /> * &lt;tt&gt;grasswxpy_LANG.po&lt;/tt&gt;: messages from wxgrass/wxPython graphical user interface<br /> <br /> where &quot;LANG&quot; in the above file names is a two character code which indicates the language. It is based on the Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column). Example: &lt;tt&gt;grasswxpy_pl.po&lt;/tt&gt; for Polish.<br /> <br /> ==== GRASS GIS 7 ====<br /> In GRASS GIS 7, we have only 3 types of .po files per language (the files are stored in the source code, in directory locale/po/; &lt;br&gt;<br /> or simply '''[http://svn.osgeo.org/grass/grass/branches/releasebranch_7_0/locale/po/ download .po files here]'''):<br /> <br /> * &lt;tt&gt;grasslibs_LANG.po&lt;/tt&gt;: messages from libraries<br /> * &lt;tt&gt;grassmods_LANG.po&lt;/tt&gt;: messages from commands (&quot;modules&quot;)<br /> * &lt;tt&gt;grasswxpy_LANG.po&lt;/tt&gt;: messages from wxgrass/wxPython graphical user interface<br /> <br /> where &quot;LANG&quot; in the above file names is a two character code which indicates the language. It is based on the Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column). Example: &lt;tt&gt;grasswxpy_pl.po&lt;/tt&gt; for Polish.<br /> <br /> === Continuing an existing translation ===<br /> <br /> The file(s) are there but partially outdated? Read on.<br /> <br /> First '''announce''' on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] that you plan to continue the translation of a certain language. Why? Because sometimes people silently translate already and we need these efforts to be coordinated to avoid doing it twice...<br /> <br /> Then get these four .po files for your language and start. If a file is missing, just ask on the list to get it generated or see next section. To get these .po files (the files are in the directory locale/po/):<br /> <br /> * either [http://svn.osgeo.org/grass/grass/branches/releasebranch_7_0/locale/po/ download current .po files] directly from SVN (click on file name to download),<br /> * or [http://trac.osgeo.org/grass/wiki/DownloadSource#GRASS7.0 download source code package] from SVN,<br /> * or download the recent [http://grass.osgeo.org/grass70/source/snapshot/ source code snapshot],<br /> * or ask on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] for these files.<br /> <br /> Then edit the files with a .po file editor (poEDIT or kbabel or..., see below). Take care to maintain layout and special characters. And '''submit often''' - if you wait for weeks, the messages may already be outdated and your time wasted. Just keep in touch on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list]!<br /> <br /> === Starting a new translation ===<br /> <br /> The language you want isn't yet there? Read on.<br /> <br /> Briefly, the steps to create new messages files are (if you find this too complicated, ask on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] to get these files done for you!):<br /> <br /> # Get the latest source code development version from either the SVN repository or as SVN snapshot (see [http://grass.osgeo.org/download/index.php Download]).<br /> # run: './configure --with-nls [... other parameters]' to configure the GRASS source code <br /> # run: 'cd locale' to change into the translation directory<br /> # run: 'make pot' to create grass*.pot template files (to extract original messages)<br /> # run: copy these file from templates/ into po/; rename them to contain the two characters language code (see Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1]) and to .po extension; update the file headers either manually or with your .po editing software<br /> (Example: Polish language):<br /> mv ./templates/grasslibs.pot ./po/grasslibs_pl.po<br /> mv ./templates/grassmods.pot ./po/grassmods_pl.po<br /> mv ./templates/grassnviz.pot ./po/grassnviz_pl.po<br /> mv ./templates/grasstcl.pot ./po/grasstcl_pl.po<br /> mv ./templates/grasswxpy.pot ./po/grasswxpy_pl.po<br /> <br /> Now translate the messages in these po/*.po files (using poEDIT or other editor, see below)<br /> <br /> From time to time messages need to be updated from the originals. This is usually done by the GRASS translation manager.<br /> <br /> == Software to translate: .po file editors ==<br /> <br /> * [http://userbase.kde.org/Lokalize Lokalize]: (previously KBabel) is a set of tools for editing and managing gettext PO files, cross-platform, comes with KDE SC (works also under MS-Windows)<br /> * [http://www.poedit.net/download.php poEdit]: poEdit is gettext catalogs (.po files) editor (works also under MS-Windows)<br /> * [http://translate.sourceforge.net/wiki/virtaal/index Virtaal] Virtaal is cross-platform graphical translation tool with terminology help from [http://open-tran.eu Open-Tran.eu]<br /> * '''[https://www.transifex.com/grass-gis/grass72/ Web based solution Transifex]''' (''see below, join us!'')<br /> * [http://www.omegat.org/ Java based solution OmegaT]<br /> &lt;!--<br /> '''How to use Transifex to translate messages online in a browser:'''<br /> <br /> [[Image:Transifex register signin.png|center|450px|Register and sign in]]<br /> <br /> [[Image:Transifex edit online.png|center|450px|Click to edit online]]<br /> --&gt;<br /> <br /> == Transifex ==<br /> <br /> === Create a new project ===<br /> <br /> '''''NOTE: CORE DEVELOPERS ONLY!'''''<br /> <br /> A project should be done for each stable release, only an Organization Administrators can create a project. From the dashboard in the left bottom corner there is &quot;'''New project'''&quot; button. Fill all the field in the form. More info in [https://docs.transifex.com/projects/creating-a-project Transifex documentation]<br /> <br /> Once the new project is created you need to upload the resources (the pot file to translate).<br /> To create the pot files you can execute<br /> make pot<br /> <br /> inside the '''locale''' folder. Now you can load in the Resource section, after you added them you can link the pot file with an online version to get updates. To do this click on &quot;'''Auto update resources'''&quot; bottom (read also the [https://docs.transifex.com/projects/uploading-content Transifex documentation].<br /> <br /> At this point you need to load the translated po files, for each language and file you have to upload the translation po file. Some errors could appear, resolution of this problems is a TODO<br /> <br /> === Get the translated po files ===<br /> <br /> '''''NOTE: THIS IS FOR DEVELOPER OR POWER USER'''''<br /> <br /> It is possible to get back the translated po files automatically using the [https://docs.transifex.com/client/introduction Transifex client]<br /> <br /> To download the file it is required to create a folder to initialize the Transifex project using the command<br /> <br /> tx init --user=USERNAME --passwd=PASSWORD<br /> <br /> --user and --passwd option are useful to create the ''.transifexrc'' file in your $HOME to save user and password, otherwise you can create the file by your self, like the following one<br /> <br /> [https://www.transifex.com]<br /> hostname = https://www.transifex.com<br /> password = PASSWORD<br /> token = <br /> username = USERNAME<br /> <br /> At this point you need to configure the repository modifying the ''.tx/config'' file created in your folder. The following file is working for [https://www.transifex.com/grass-gis/grass72 GRASS 7.2 project], you need to add a section for each resource. <br /> <br /> [main]<br /> host = https://www.transifex.com<br /> <br /> [grass72.grasslibspot]<br /> type = PO<br /> source_lang = en<br /> source_file = ../templates/grasslibs.pot<br /> <br /> [grass72.grassmodspot]<br /> type = PO<br /> source_lang = en<br /> source_file = ../templates/grassmods.pot<br /> <br /> [grass72.grasswxpypot]<br /> type = PO<br /> source_lang = en<br /> source_file = ../templates/grasswxpy.pot<br /> <br /> '''''NOTE: THIS SHOULD NOT BE RUN IF YOU WANT TO RUN transifex_merge.sh '''''<br /> <br /> Now you can download all the translated po files with the following command<br /> <br /> tx pull -a<br /> <br /> == Testing different languages ==<br /> <br /> Testing different languages requires that the respective language environment and, if needed, fonts are installed.<br /> Check what languages are currently installed on your system with:<br /> locale -a<br /> <br /> To change to a certain language environment (locale), do the following steps (here, example for Unix style environment):<br /> <br /> 1. Define/check language settings:<br /> echo $LANG<br /> echo $LANGUAGE<br /> echo $LC_MESSAGES<br /> <br /> 2. Change it (example for to Japanese):<br /> a) bash shell:<br /> export LANG=ja_JP.UTF-8<br /> export LANGUAGE=ja_JP.UTF-8<br /> export LC_MESSAGES=ja_JP.UTF-8<br /> <br /> <br /> b) (t)csh shell:<br /> setenv LANG ja_JP.UTF-8<br /> setenv LANGUAGE ja_JP.UTF-8<br /> setenv LC_MESSAGES ja_JP.UTF-8<br /> <br /> Now launch GRASS in this terminal. If you launch it from an icon, you have to change the LOCALE in the computer setup program instead.<br /> <br /> Other common languages useful for testing are &lt;tt&gt;de_DE&lt;/tt&gt; for German, &lt;tt&gt;fr_FR&lt;/tt&gt; for French, or &quot;C&quot; for none (effectively &lt;tt&gt;en_US&lt;/tt&gt;, which for GRASS is the base language).<br /> <br /> === Creating startup scripts for different languages ===<br /> <br /> GRASS in English language, save as &quot;grass64eng&quot; (executable flag set, store in path):<br /> #!/bin/sh<br /> export LANG=en_US<br /> export LANGUAGE=en_US<br /> export LC_MESSAGES=en_US<br /> exec grass64 &quot;$@&quot;<br /> <br /> GRASS in Japanese language, save as &quot;grass64ja&quot; (executable flag set, store in path):<br /> #!/bin/sh<br /> export LANG=ja_JA.UTF-8<br /> export LANGUAGE=ja_JA.UTF-8<br /> export LC_MESSAGES=ja_JA.UTF-8<br /> grass64 &quot;$@&quot;<br /> <br /> == Coordination among translators ==<br /> <br /> If several translators work on the same language files, obviously some coordination is needed. Please announce work via the &quot;translations&quot; mailing list at http://lists.osgeo.org/mailman/listinfo/grass-translations <br /> <br /> Also the translation manager is listening there to the upload the changed files into the GRASS source code repository.<br /> <br /> == Best practices ==<br /> <br /> * Italiano: [http://tp.linux.it/buona_traduzione.html Regole per la buona traduzione]<br /> <br /> == Installation of language packages ==<br /> <br /> Example: Chinese<br /> <br /> * Mandriva: urpmi locales-zh kde-l10n-zh_CN fonts-ttf-default-zh_CN<br /> * Fedora: the locales should be already present<br /> ** list all valid locales on the system: localectl list-locales<br /> ** show current settings: localectl status<br /> ** set new locale: localectl set-locale LANG=zh_CN.utf8 LC_MESSAGES=zh_CN.utf8<br /> <br /> == Updating messages in the source code ==<br /> <br /> Generally, to support i18N multiple languages, message strings in GRASS must be modified by adding so-called [https://www.gnu.org/software/gettext/ gettext macros] &lt;tt&gt;'''_('''&quot;...&quot;''')'''&lt;/tt&gt;.<br /> <br /> === C programming language ===<br /> <br /> Change from<br /> fprintf ( ..., &quot;...\n&quot;, ...);<br /> to either<br /> fprintf ( ..., _(&quot;...\n&quot;), ...);<br /> or usually (while omitting \n)<br /> G_message ( _(&quot;...&quot;), ...);<br /> <br /> === Python programming language ===<br /> <br /> In Python, the macro is used like this:<br /> &lt;source lang=&quot;python&quot;&gt;<br /> grass.message(_('Raster map &lt;{name}&gt; unpacked'.format(name=map_name)))<br /> &lt;/source&gt;<br /> <br /> === Important hints ===<br /> <br /> Beware:<br /> * G_message should be used for messages - information about the process for user while fprintf(stdout...) for data output.<br /> * G_message output is not expected to be send to pipe or file.<br /> * fprintf(stdout...) output is usually send to pipe or file.<br /> <br /> Programming details are available in the file locale/[https://svn.osgeo.org/grass/grass/trunk/locale/README README].<br /> <br /> Important:<br /> * [https://trac.osgeo.org/grass/wiki/MessageStandardization Message Standardization]: How should Errors/Warnings/Messages be formatted, Macros etc<br /> <br /> == See also ==<br /> <br /> * Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column)<br /> <br /> <br /> [[Category: Development]]<br /> [[Category: Documentation]]<br /> [[Category: FAQ]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_Community_Sprint_Genova_2017&diff=23893 2017-01-30T16:09:03Z

<p>Lucadelu: added more info about the community sprint</p> <hr /> <div>The GRASS GIS team will organize a '''GRASS Developer and Power User Meeting, aka 'GRASS Community Sprint'''' from '''6-12 Feb, 2017'''. The sprint is at the same time of the XVIII Meeting degli Utenti Italiani Grass e Gfoss, 9-10 Feb 2017, University of Genova, Polytechnic School of Engineering, [http://en.wikipedia.org/wiki/Genoa Genova], [http://en.wikipedia.org/wiki/Italy Italy].<br /> <br /> == Purpose ==<br /> <br /> This next edition of the GRASS GIS community sprint 2017 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.<br /> <br /> 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.<br /> <br /> == Sponsors ==<br /> <br /> 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<br /> <br /> :::'''sponsoring the GRASS project at [http://grass.osgeo.org/donations/ http://grass.osgeo.org/donations/]'''<br /> <br /> For questions, please contact [[User:Lucadelu|Luca Delucchi]] &lt;tt&gt;&lt;lucadeluge at gmail.com&gt;&lt;/tt&gt;. Any surplus at the end of the event will be turned over to the GRASS GIS project.<br /> <br /> The third 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.<br /> <br /> == Timing ==<br /> <br /> '''When''': 6-12 Feb, 2017<br /> <br /> Of course you are free to join or leave the community sprint whenever you want.<br /> <br /> '''Duration''': 7 days<br /> <br /> == Venue ==<br /> <br /> Two rooms (A8 and A9) are booked from 6th to 10th February at University of Genova, Polytechnic School of Engineering in [http://osm.org/go/xX0mu8L~Z?m= Villa Cambiaso]<br /> <br /> 11th and 12th February TBD<br /> <br /> == Accommodation and Costs ==<br /> <br /> Some beds are available in Luca's granma house, others are available in the FOSS4G.it website <br /> <br /> == Agenda == <br /> <br /> === Timeline ===<br /> <br /> ==== Monday, 6 February ====<br /> <br /> * End Transifex setting<br /> <br /> ==== Tuesday, 7 February ====<br /> <br /> ==== Wednesday, 8 February ====<br /> <br /> ==== Thursday, 9 February ====<br /> <br /> * Official FOSS4G.it dinner<br /> <br /> ==== Friday, 10 February ====<br /> <br /> * Unofficial FOSS4G.it dinner<br /> <br /> ==== Saturday, 11 February ====<br /> <br /> * Santa Margherita and Portofino visit related to OSM mapping party. capabilities to work there<br /> <br /> == Participation ==<br /> <br /> === In person (planned) ===<br /> <br /> {|class=&quot;wikitable sortable&quot; border=&quot;2&quot; cellspacing=&quot;0&quot; cellpadding=&quot;4&quot; rules=&quot;all&quot; style=&quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;&quot; <br /> !width=50px|'''Number'''<br /> !width=130px|'''Participant '''<br /> !width=100px|'''Country'''<br /> !width=100px|'''Arrival'''<br /> !width=100px|'''Departure'''<br /> !'''Topic'''<br /> !width=75px|'''T-Shirt'''<br /> !'''Notes'''<br /> |-<br /> |1<br /> |[[User:Lucadelu|Luca Delucchi]]<br /> |Italy<br /> | Feb 3<br /> | Feb 12<br /> |<br /> | L<br /> |<br /> |-<br /> |2<br /> |[[User:Ychemin|Yann Chemin]]<br /> |Italy<br /> | Feb 5<br /> | Feb 12<br /> | GDAL-GRASS planetary IAU2000/2009 integration<br /> | XXL<br /> |<br /> |-<br /> |3<br /> |[[User:Landa|Martin Landa]]<br /> |Czech Republic<br /> | Feb 6<br /> | Feb 12<br /> | Various<br /> | L<br /> | <br /> |-<br /> |4<br /> |[[User:NikosAlexandris|Nikos Alexandris]]<br /> |?<br /> | Feb 3<br /> | Feb 12<br /> | Various<br /> | M<br /> | Not yet confirmed<br /> |}<br /> <br /> === Via IRC chat or hangout===<br /> <br /> : [irc://freenode/grass #grass] on Freenode<br /> : [http://www.google.com/+/learnmore/hangouts/ G+ hangout] (to be investigated; smartphones only? is Jitsi on a desktop computer compatible?)<br /> <br /> For details, see [[IRC]]<br /> <br /> Please add yourself here below (please add also your gmail account for G+ hangout):<br /> * ADD YOUR SELF<br /> <br /> == Individual Preparation ==<br /> <br /> * Bring your own computer<br /> * Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed ([http://en.wikipedia.org/wiki/File:L_plug.jpg Italy])<br /> * Install subversion and the compiler tools, and come with a working GRASS development environment if possible.<br /> <br /> == Photos ==<br /> <br /> == FAQ ==<br /> <br /> * '''How was it last time?'''<br /> ** Very cool, see [[GRASS Community Sprint Bonn 2016]]!<br /> <br /> * '''Is the GRASS Community Sprint just a coding event?'''<br /> ** 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.<br /> ** On demand, however, we can do some presentations of current working GRASS implementations and new upcoming features to spread the idea of Open Source GIS software.<br /> <br /> * '''Is the GRASS Community Sprint for developers only?'''<br /> ** ''Not at all!'' Anybody can help with testing, checking out bugs and fixes, documentation and more.<br /> <br /> * '''Where can I get help and more information about the community sprint?'''<br /> ** Contact [[User:Lucadelu|Luca Delucchi]] &lt;tt&gt;&lt;lucadeluge at gmail dot com&gt;&lt;/tt&gt; or [[User:Neteler|Markus Neteler]]<br /> <br /> [[Category: Workshops]]<br /> [[Category: Code Sprint]]<br /> [[Category: 2017]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_messages_translation&diff=23874 2017-01-25T15:59:40Z

<p>Lucadelu: </p> <hr /> <div>== Help page translations ==<br /> <br /> * For translations of full help (man) pages see [[Updating GRASS Documentation#Translations]]<br /> <br /> == GRASS messages translation project ==<br /> <br /> Many users prefer to use software in their mother tongue which is mostly not English. This requires that all GRASS software messages have to be translated to languages other than English. The GRASS Development Team is seeking translators. Please subscribe to the dedicated mailing list at<br /> <br /> GRASS translations mailing list<br /> http://lists.osgeo.org/mailman/listinfo/grass-translations<br /> <br /> Translation related issues may be discussed there. This is an opportunity for non-programmers to contribute as messages can be easily translated. No programming skills required!<br /> <br /> * Join the [[GRASS_Translation_Team#Members_of_Translation_Team|team]]<br /> <br /> === Wanted languages ===<br /> <br /> Simple Chinese, Swahili, Hindi, Greek, Tamil, Russian, Telugu, Português, ... Please join us!<br /> <br /> == How to change the language ==<br /> <br /> * see [[GRASS_messages_translation#Testing_different_languages|Testing different languages]] below.<br /> <br /> == How to start or update translations ==<br /> <br /> * For terminology, please refer to the [[GRASS Translation Glossary]].<br /> <br /> === Files to be edited (downloaded) ===<br /> <br /> ==== GRASS GIS 6 ====<br /> In GRASS GIS 6, we have 5 types of .po files per language (the files are stored in the source code, in directory locale/po/; &lt;br&gt;<br /> or simply '''[http://svn.osgeo.org/grass/grass/branches/releasebranch_6_4/locale/po/ download .po files here]'''):<br /> <br /> * &lt;tt&gt;grasslibs_LANG.po&lt;/tt&gt;: messages from libraries<br /> * &lt;tt&gt;grassmods_LANG.po&lt;/tt&gt;: messages from commands (&quot;modules&quot;)<br /> * &lt;tt&gt;grassnviz_LANG.po&lt;/tt&gt;: messages from NVIZ Tcl/Tk graphical user interface (GRASS 6)<br /> * &lt;tt&gt;grasstcl_LANG.po&lt;/tt&gt;: messages from Tcl/Tk graphical user interface (GRASS 6)<br /> * &lt;tt&gt;grasswxpy_LANG.po&lt;/tt&gt;: messages from wxgrass/wxPython graphical user interface<br /> <br /> where &quot;LANG&quot; in the above file names is a two character code which indicates the language. It is based on the Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column). Example: &lt;tt&gt;grasswxpy_pl.po&lt;/tt&gt; for Polish.<br /> <br /> ==== GRASS GIS 7 ====<br /> In GRASS GIS 7, we have only 3 types of .po files per language (the files are stored in the source code, in directory locale/po/; &lt;br&gt;<br /> or simply '''[http://svn.osgeo.org/grass/grass/branches/releasebranch_7_0/locale/po/ download .po files here]'''):<br /> <br /> * &lt;tt&gt;grasslibs_LANG.po&lt;/tt&gt;: messages from libraries<br /> * &lt;tt&gt;grassmods_LANG.po&lt;/tt&gt;: messages from commands (&quot;modules&quot;)<br /> * &lt;tt&gt;grasswxpy_LANG.po&lt;/tt&gt;: messages from wxgrass/wxPython graphical user interface<br /> <br /> where &quot;LANG&quot; in the above file names is a two character code which indicates the language. It is based on the Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column). Example: &lt;tt&gt;grasswxpy_pl.po&lt;/tt&gt; for Polish.<br /> <br /> === Continuing an existing translation ===<br /> <br /> The file(s) are there but partially outdated? Read on.<br /> <br /> First '''announce''' on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] that you plan to continue the translation of a certain language. Why? Because sometimes people silently translate already and we need these efforts to be coordinated to avoid doing it twice...<br /> <br /> Then get these four .po files for your language and start. If a file is missing, just ask on the list to get it generated or see next section. To get these .po files (the files are in the directory locale/po/):<br /> <br /> * either [http://svn.osgeo.org/grass/grass/branches/releasebranch_7_0/locale/po/ download current .po files] directly from SVN (click on file name to download),<br /> * or [http://trac.osgeo.org/grass/wiki/DownloadSource#GRASS7.0 download source code package] from SVN,<br /> * or download the recent [http://grass.osgeo.org/grass70/source/snapshot/ source code snapshot],<br /> * or ask on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] for these files.<br /> <br /> Then edit the files with a .po file editor (poEDIT or kbabel or..., see below). Take care to maintain layout and special characters. And '''submit often''' - if you wait for weeks, the messages may already be outdated and your time wasted. Just keep in touch on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list]!<br /> <br /> === Starting a new translation ===<br /> <br /> The language you want isn't yet there? Read on.<br /> <br /> Briefly, the steps to create new messages files are (if you find this too complicated, ask on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] to get these files done for you!):<br /> <br /> # Get the latest source code development version from either the SVN repository or as SVN snapshot (see [http://grass.osgeo.org/download/index.php Download]).<br /> # run: './configure --with-nls [... other parameters]' to configure the GRASS source code <br /> # run: 'cd locale' to change into the translation directory<br /> # run: 'make pot' to create grass*.pot template files (to extract original messages)<br /> # run: copy these file from templates/ into po/; rename them to contain the two characters language code (see Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1]) and to .po extension; update the file headers either manually or with your .po editing software<br /> (Example: Polish language):<br /> mv ./templates/grasslibs.pot ./po/grasslibs_pl.po<br /> mv ./templates/grassmods.pot ./po/grassmods_pl.po<br /> mv ./templates/grassnviz.pot ./po/grassnviz_pl.po<br /> mv ./templates/grasstcl.pot ./po/grasstcl_pl.po<br /> mv ./templates/grasswxpy.pot ./po/grasswxpy_pl.po<br /> <br /> Now translate the messages in these po/*.po files (using poEDIT or other editor, see below)<br /> <br /> From time to time messages need to be updated from the originals. This is usually done by the GRASS translation manager.<br /> <br /> == Software to translate: .po file editors ==<br /> <br /> * [http://userbase.kde.org/Lokalize Lokalize]: (previously KBabel) is a set of tools for editing and managing gettext PO files, cross-platform, comes with KDE SC (works also under MS-Windows)<br /> * [http://www.poedit.net/download.php poEdit]: poEdit is gettext catalogs (.po files) editor (works also under MS-Windows)<br /> * [http://translate.sourceforge.net/wiki/virtaal/index Virtaal] Virtaal is cross-platform graphical translation tool with terminology help from [http://open-tran.eu Open-Tran.eu]<br /> * [https://www.transifex.net/projects/p/grass6/ Web based solution Transifex] (''help needed to revive'')<br /> * [http://www.omegat.org/ Java based solution OmegaT]<br /> &lt;!--<br /> '''How to use Transifex to translate messages online in a browser:'''<br /> * (''currently '''offline''' due to 2011 transifex website transition. please contact the translations mailing list (or Markus N) if you'd like to help with that'')<br /> <br /> [[Image:Transifex register signin.png|center|450px|Register and sign in]]<br /> <br /> [[Image:Transifex edit online.png|center|450px|Click to edit online]]<br /> --&gt;<br /> == Transifex ==<br /> <br /> === New project ===<br /> A project should be done for each stable release, only an Organization Administrators can create a project. From the dashboard in the left bottom corner there is &quot;'''New project'''&quot; button. Fill all the field in the form. More info in [https://docs.transifex.com/projects/creating-a-project Transifex documentation]<br /> <br /> Once the new project is created you need to upload the resources (the pot file to translate).<br /> To create the pot files you can execute<br /> make pot<br /> <br /> inside '''locale''' folder. Now you can load in the Resource section, after you added them you can link the pot file with an online version to get updates. To do this click on &quot;'''Auto update resources'''&quot; bottom (read also the [https://docs.transifex.com/projects/uploading-content Transifex documentation].<br /> <br /> At this point you need to load the translated po files, for each language and file you have to upload the translation po file. Some errors could appear, resolution of this problems is a TODO<br /> <br /> === Get the translated po files ===<br /> It is possible to get back the translated po files automatically using the [https://docs.transifex.com/client/introduction Transifex client]<br /> <br /> To download the file it is required to create a folder to initialize the Transifex project using the command<br /> <br /> tx init --user=USERNAME --passwd=PASSWORD<br /> <br /> --user and --passwd option are useful to create the ''.transifexrc'' file in your $HOME to save user and password, otherwise you can create the file by your self, like the following one<br /> <br /> [https://www.transifex.com]<br /> hostname = https://www.transifex.com<br /> password = PASSWORD<br /> token = <br /> username = USERNAME<br /> <br /> At this point you need to configure the repository modifying the ''.tx/config'' file created in your folder. The following file is working for [https://www.transifex.com/grass-gis/grass72 GRASS 7.2 project], you need to add a section for each resource. <br /> <br /> [main]<br /> host = https://www.transifex.com<br /> <br /> [grass72.grasslibspot]<br /> type = PO<br /> source_lang = en<br /> source_file = ../templates/grasslibs.pot<br /> <br /> [grass72.grassmodspot]<br /> type = PO<br /> source_lang = en<br /> source_file = ../templates/grassmods.pot<br /> <br /> [grass72.grasswxpypot]<br /> type = PO<br /> source_lang = en<br /> source_file = ../templates/grasswxpy.pot<br /> <br /> Now you can download all the translated po files with the following command<br /> <br /> tx pull -a<br /> <br /> == Testing different languages ==<br /> <br /> Testing different languages requires that the respective language environment and, if needed, fonts are installed.<br /> Check what languages are currently installed on your system with:<br /> locale -a<br /> <br /> To change to a certain language environment (locale), do the following steps (here, example for Unix style environment):<br /> <br /> 1. Define/check language settings:<br /> echo $LANG<br /> echo $LANGUAGE<br /> echo $LC_MESSAGES<br /> <br /> 2. Change it (example for to Japanese):<br /> a) bash shell:<br /> export LANG=ja_JP.UTF-8<br /> export LANGUAGE=ja_JP.UTF-8<br /> export LC_MESSAGES=ja_JP.UTF-8<br /> <br /> <br /> b) (t)csh shell:<br /> setenv LANG ja_JP.UTF-8<br /> setenv LANGUAGE ja_JP.UTF-8<br /> setenv LC_MESSAGES ja_JP.UTF-8<br /> <br /> Now launch GRASS in this terminal. If you launch it from an icon, you have to change the LOCALE in the computer setup program instead.<br /> <br /> Other common languages useful for testing are &lt;tt&gt;de_DE&lt;/tt&gt; for German, &lt;tt&gt;fr_FR&lt;/tt&gt; for French, or &quot;C&quot; for none (effectively &lt;tt&gt;en_US&lt;/tt&gt;, which for GRASS is the base language).<br /> <br /> === Creating startup scripts for different languages ===<br /> <br /> GRASS in English language, save as &quot;grass64eng&quot; (executable flag set, store in path):<br /> #!/bin/sh<br /> export LANG=en_US<br /> export LANGUAGE=en_US<br /> export LC_MESSAGES=en_US<br /> exec grass64 &quot;$@&quot;<br /> <br /> GRASS in Japanese language, save as &quot;grass64ja&quot; (executable flag set, store in path):<br /> #!/bin/sh<br /> export LANG=ja_JA.UTF-8<br /> export LANGUAGE=ja_JA.UTF-8<br /> export LC_MESSAGES=ja_JA.UTF-8<br /> grass64 &quot;$@&quot;<br /> <br /> == Coordination among translators ==<br /> <br /> If several translators work on the same language files, obviously some coordination is needed. Please announce work via the &quot;translations&quot; mailing list at http://lists.osgeo.org/mailman/listinfo/grass-translations <br /> <br /> Also the translation manager is listening there to the upload the changed files into the GRASS source code repository.<br /> <br /> == Best practices ==<br /> <br /> * Italiano: [http://tp.linux.it/buona_traduzione.html Regole per la buona traduzione]<br /> <br /> == Installation of language packages ==<br /> <br /> Example: Chinese<br /> <br /> * Mandriva: urpmi locales-zh kde-l10n-zh_CN fonts-ttf-default-zh_CN<br /> * Fedora: the locales should be already present<br /> ** list all valid locales on the system: localectl list-locales<br /> ** show current settings: localectl status<br /> ** set new locale: localectl set-locale LANG=zh_CN.utf8 LC_MESSAGES=zh_CN.utf8<br /> <br /> == Updating messages in the source code ==<br /> <br /> Generally, to support i18N multiple languages, message strings in GRASS must be modified by adding so-called [https://www.gnu.org/software/gettext/ gettext macros] &lt;tt&gt;'''_('''&quot;...&quot;''')'''&lt;/tt&gt;.<br /> <br /> === C programming language ===<br /> <br /> Change from<br /> fprintf ( ..., &quot;...\n&quot;, ...);<br /> to either<br /> fprintf ( ..., _(&quot;...\n&quot;), ...);<br /> or usually (while omitting \n)<br /> G_message ( _(&quot;...&quot;), ...);<br /> <br /> === Python programming language ===<br /> <br /> In Python, the macro is used like this:<br /> &lt;source lang=&quot;python&quot;&gt;<br /> grass.message(_('Raster map &lt;{name}&gt; unpacked'.format(name=map_name)))<br /> &lt;/source&gt;<br /> <br /> === Important hints ===<br /> <br /> Beware:<br /> * G_message should be used for messages - information about the process for user while fprintf(stdout...) for data output.<br /> * G_message output is not expected to be send to pipe or file.<br /> * fprintf(stdout...) output is usually send to pipe or file.<br /> <br /> Programming details are available in the file locale/[https://svn.osgeo.org/grass/grass/trunk/locale/README README].<br /> <br /> Important:<br /> * [https://trac.osgeo.org/grass/wiki/MessageStandardization Message Standardization]: How should Errors/Warnings/Messages be formatted, Macros etc<br /> <br /> == See also ==<br /> <br /> * Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column)<br /> <br /> <br /> [[Category: Development]]<br /> [[Category: Documentation]]<br /> [[Category: FAQ]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_messages_translation&diff=23873 2017-01-25T14:17:58Z

<p>Lucadelu: </p> <hr /> <div>== Help page translations ==<br /> <br /> * For translations of full help (man) pages see [[Updating GRASS Documentation#Translations]]<br /> <br /> == GRASS messages translation project ==<br /> <br /> Many users prefer to use software in their mother tongue which is mostly not English. This requires that all GRASS software messages have to be translated to languages other than English. The GRASS Development Team is seeking translators. Please subscribe to the dedicated mailing list at<br /> <br /> GRASS translations mailing list<br /> http://lists.osgeo.org/mailman/listinfo/grass-translations<br /> <br /> Translation related issues may be discussed there. This is an opportunity for non-programmers to contribute as messages can be easily translated. No programming skills required!<br /> <br /> * Join the [[GRASS_Translation_Team#Members_of_Translation_Team|team]]<br /> <br /> === Wanted languages ===<br /> <br /> Simple Chinese, Swahili, Hindi, Greek, Tamil, Russian, Telugu, Português, ... Please join us!<br /> <br /> == How to change the language ==<br /> <br /> * see [[GRASS_messages_translation#Testing_different_languages|Testing different languages]] below.<br /> <br /> == How to start or update translations ==<br /> <br /> * For terminology, please refer to the [[GRASS Translation Glossary]].<br /> <br /> === Files to be edited (downloaded) ===<br /> <br /> ==== GRASS GIS 6 ====<br /> In GRASS GIS 6, we have 5 types of .po files per language (the files are stored in the source code, in directory locale/po/; &lt;br&gt;<br /> or simply '''[http://svn.osgeo.org/grass/grass/branches/releasebranch_6_4/locale/po/ download .po files here]'''):<br /> <br /> * &lt;tt&gt;grasslibs_LANG.po&lt;/tt&gt;: messages from libraries<br /> * &lt;tt&gt;grassmods_LANG.po&lt;/tt&gt;: messages from commands (&quot;modules&quot;)<br /> * &lt;tt&gt;grassnviz_LANG.po&lt;/tt&gt;: messages from NVIZ Tcl/Tk graphical user interface (GRASS 6)<br /> * &lt;tt&gt;grasstcl_LANG.po&lt;/tt&gt;: messages from Tcl/Tk graphical user interface (GRASS 6)<br /> * &lt;tt&gt;grasswxpy_LANG.po&lt;/tt&gt;: messages from wxgrass/wxPython graphical user interface<br /> <br /> where &quot;LANG&quot; in the above file names is a two character code which indicates the language. It is based on the Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column). Example: &lt;tt&gt;grasswxpy_pl.po&lt;/tt&gt; for Polish.<br /> <br /> ==== GRASS GIS 7 ====<br /> In GRASS GIS 7, we have only 3 types of .po files per language (the files are stored in the source code, in directory locale/po/; &lt;br&gt;<br /> or simply '''[http://svn.osgeo.org/grass/grass/branches/releasebranch_7_0/locale/po/ download .po files here]'''):<br /> <br /> * &lt;tt&gt;grasslibs_LANG.po&lt;/tt&gt;: messages from libraries<br /> * &lt;tt&gt;grassmods_LANG.po&lt;/tt&gt;: messages from commands (&quot;modules&quot;)<br /> * &lt;tt&gt;grasswxpy_LANG.po&lt;/tt&gt;: messages from wxgrass/wxPython graphical user interface<br /> <br /> where &quot;LANG&quot; in the above file names is a two character code which indicates the language. It is based on the Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column). Example: &lt;tt&gt;grasswxpy_pl.po&lt;/tt&gt; for Polish.<br /> <br /> === Continuing an existing translation ===<br /> <br /> The file(s) are there but partially outdated? Read on.<br /> <br /> First '''announce''' on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] that you plan to continue the translation of a certain language. Why? Because sometimes people silently translate already and we need these efforts to be coordinated to avoid doing it twice...<br /> <br /> Then get these four .po files for your language and start. If a file is missing, just ask on the list to get it generated or see next section. To get these .po files (the files are in the directory locale/po/):<br /> <br /> * either [http://svn.osgeo.org/grass/grass/branches/releasebranch_7_0/locale/po/ download current .po files] directly from SVN (click on file name to download),<br /> * or [http://trac.osgeo.org/grass/wiki/DownloadSource#GRASS7.0 download source code package] from SVN,<br /> * or download the recent [http://grass.osgeo.org/grass70/source/snapshot/ source code snapshot],<br /> * or ask on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] for these files.<br /> <br /> Then edit the files with a .po file editor (poEDIT or kbabel or..., see below). Take care to maintain layout and special characters. And '''submit often''' - if you wait for weeks, the messages may already be outdated and your time wasted. Just keep in touch on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list]!<br /> <br /> === Starting a new translation ===<br /> <br /> The language you want isn't yet there? Read on.<br /> <br /> Briefly, the steps to create new messages files are (if you find this too complicated, ask on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] to get these files done for you!):<br /> <br /> # Get the latest source code development version from either the SVN repository or as SVN snapshot (see [http://grass.osgeo.org/download/index.php Download]).<br /> # run: './configure --with-nls [... other parameters]' to configure the GRASS source code <br /> # run: 'cd locale' to change into the translation directory<br /> # run: 'make pot' to create grass*.pot template files (to extract original messages)<br /> # run: copy these file from templates/ into po/; rename them to contain the two characters language code (see Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1]) and to .po extension; update the file headers either manually or with your .po editing software<br /> (Example: Polish language):<br /> mv ./templates/grasslibs.pot ./po/grasslibs_pl.po<br /> mv ./templates/grassmods.pot ./po/grassmods_pl.po<br /> mv ./templates/grassnviz.pot ./po/grassnviz_pl.po<br /> mv ./templates/grasstcl.pot ./po/grasstcl_pl.po<br /> mv ./templates/grasswxpy.pot ./po/grasswxpy_pl.po<br /> <br /> Now translate the messages in these po/*.po files (using poEDIT or other editor, see below)<br /> <br /> From time to time messages need to be updated from the originals. This is usually done by the GRASS translation manager.<br /> <br /> == Software to translate: .po file editors ==<br /> <br /> * [http://userbase.kde.org/Lokalize Lokalize]: (previously KBabel) is a set of tools for editing and managing gettext PO files, cross-platform, comes with KDE SC (works also under MS-Windows)<br /> * [http://www.poedit.net/download.php poEdit]: poEdit is gettext catalogs (.po files) editor (works also under MS-Windows)<br /> * [http://translate.sourceforge.net/wiki/virtaal/index Virtaal] Virtaal is cross-platform graphical translation tool with terminology help from [http://open-tran.eu Open-Tran.eu]<br /> * [https://www.transifex.net/projects/p/grass6/ Web based solution Transifex] (''help needed to revive'')<br /> * [http://www.omegat.org/ Java based solution OmegaT]<br /> &lt;!--<br /> '''How to use Transifex to translate messages online in a browser:'''<br /> * (''currently '''offline''' due to 2011 transifex website transition. please contact the translations mailing list (or Markus N) if you'd like to help with that'')<br /> <br /> [[Image:Transifex register signin.png|center|450px|Register and sign in]]<br /> <br /> [[Image:Transifex edit online.png|center|450px|Click to edit online]]<br /> --&gt;<br /> == Transifex ==<br /> <br /> === New project ===<br /> A project should be done for each stable release, only an Organization Administrators can create a project. From the dashboard in the left bottom corner there is &quot;'''New project'''&quot; button. Fill all the field in the form. More info in [https://docs.transifex.com/projects/creating-a-project Transifex documentation]<br /> <br /> Once the new project is created you need to upload the resources (the pot file to translate).<br /> To create the pot files you can execute<br /> make pot<br /> <br /> inside '''locale''' folder. Now you can load in the Resource section, after you added them you can link the pot file with an online version to get updates. To do this click on &quot;'''Auto update resources'''&quot; bottom (read also the [https://docs.transifex.com/projects/uploading-content Transifex documentation].<br /> <br /> At this point you need to load the translated po files, for each language and file you have to upload the translation po file. Some errors could appear, resolution of this problems is a TODO<br /> <br /> === Get the translated po files ===<br /> It is possible to get back the translated po files automatically using the [https://docs.transifex.com/client/introduction Transifex client]<br /> <br /> == Testing different languages ==<br /> <br /> Testing different languages requires that the respective language environment and, if needed, fonts are installed.<br /> Check what languages are currently installed on your system with:<br /> locale -a<br /> <br /> To change to a certain language environment (locale), do the following steps (here, example for Unix style environment):<br /> <br /> 1. Define/check language settings:<br /> echo $LANG<br /> echo $LANGUAGE<br /> echo $LC_MESSAGES<br /> <br /> 2. Change it (example for to Japanese):<br /> a) bash shell:<br /> export LANG=ja_JP.UTF-8<br /> export LANGUAGE=ja_JP.UTF-8<br /> export LC_MESSAGES=ja_JP.UTF-8<br /> <br /> <br /> b) (t)csh shell:<br /> setenv LANG ja_JP.UTF-8<br /> setenv LANGUAGE ja_JP.UTF-8<br /> setenv LC_MESSAGES ja_JP.UTF-8<br /> <br /> Now launch GRASS in this terminal. If you launch it from an icon, you have to change the LOCALE in the computer setup program instead.<br /> <br /> Other common languages useful for testing are &lt;tt&gt;de_DE&lt;/tt&gt; for German, &lt;tt&gt;fr_FR&lt;/tt&gt; for French, or &quot;C&quot; for none (effectively &lt;tt&gt;en_US&lt;/tt&gt;, which for GRASS is the base language).<br /> <br /> === Creating startup scripts for different languages ===<br /> <br /> GRASS in English language, save as &quot;grass64eng&quot; (executable flag set, store in path):<br /> #!/bin/sh<br /> export LANG=en_US<br /> export LANGUAGE=en_US<br /> export LC_MESSAGES=en_US<br /> exec grass64 &quot;$@&quot;<br /> <br /> GRASS in Japanese language, save as &quot;grass64ja&quot; (executable flag set, store in path):<br /> #!/bin/sh<br /> export LANG=ja_JA.UTF-8<br /> export LANGUAGE=ja_JA.UTF-8<br /> export LC_MESSAGES=ja_JA.UTF-8<br /> grass64 &quot;$@&quot;<br /> <br /> == Coordination among translators ==<br /> <br /> If several translators work on the same language files, obviously some coordination is needed. Please announce work via the &quot;translations&quot; mailing list at http://lists.osgeo.org/mailman/listinfo/grass-translations <br /> <br /> Also the translation manager is listening there to the upload the changed files into the GRASS source code repository.<br /> <br /> == Best practices ==<br /> <br /> * Italiano: [http://tp.linux.it/buona_traduzione.html Regole per la buona traduzione]<br /> <br /> == Installation of language packages ==<br /> <br /> Example: Chinese<br /> <br /> * Mandriva: urpmi locales-zh kde-l10n-zh_CN fonts-ttf-default-zh_CN<br /> * Fedora: the locales should be already present<br /> ** list all valid locales on the system: localectl list-locales<br /> ** show current settings: localectl status<br /> ** set new locale: localectl set-locale LANG=zh_CN.utf8 LC_MESSAGES=zh_CN.utf8<br /> <br /> == Updating messages in the source code ==<br /> <br /> Generally, to support i18N multiple languages, message strings in GRASS must be modified by adding so-called [https://www.gnu.org/software/gettext/ gettext macros] &lt;tt&gt;'''_('''&quot;...&quot;''')'''&lt;/tt&gt;.<br /> <br /> === C programming language ===<br /> <br /> Change from<br /> fprintf ( ..., &quot;...\n&quot;, ...);<br /> to either<br /> fprintf ( ..., _(&quot;...\n&quot;), ...);<br /> or usually (while omitting \n)<br /> G_message ( _(&quot;...&quot;), ...);<br /> <br /> === Python programming language ===<br /> <br /> In Python, the macro is used like this:<br /> &lt;source lang=&quot;python&quot;&gt;<br /> grass.message(_('Raster map &lt;{name}&gt; unpacked'.format(name=map_name)))<br /> &lt;/source&gt;<br /> <br /> === Important hints ===<br /> <br /> Beware:<br /> * G_message should be used for messages - information about the process for user while fprintf(stdout...) for data output.<br /> * G_message output is not expected to be send to pipe or file.<br /> * fprintf(stdout...) output is usually send to pipe or file.<br /> <br /> Programming details are available in the file locale/[https://svn.osgeo.org/grass/grass/trunk/locale/README README].<br /> <br /> Important:<br /> * [https://trac.osgeo.org/grass/wiki/MessageStandardization Message Standardization]: How should Errors/Warnings/Messages be formatted, Macros etc<br /> <br /> == See also ==<br /> <br /> * Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column)<br /> <br /> <br /> [[Category: Development]]<br /> [[Category: Documentation]]<br /> [[Category: FAQ]]</div>

Lucadelu https://grasswiki.osgeo.org/w/index.php?title=GRASS_Community_Sprint_Genova_2017&diff=23674 2016-10-20T10:03:25Z

<p>Lucadelu: /* Venue */</p> <hr /> <div>The GRASS GIS team will organize a '''GRASS Developer and Power User Meeting, aka 'GRASS Community Sprint'''' from '''6-12 Feb, 2017'''. The sprint is at the same time of the XVIII Meeting degli Utenti Italiani Grass e Gfoss, 9-10 Feb 2017, University of Genova, Polytechnic School of Engineering, [http://en.wikipedia.org/wiki/Genoa Genova], [http://en.wikipedia.org/wiki/Italy Italy].<br /> <br /> == Purpose ==<br /> <br /> This next edition of the GRASS GIS community sprint 2017 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.<br /> <br /> 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.<br /> <br /> == Sponsors ==<br /> <br /> 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<br /> <br /> :::'''sponsoring the GRASS project at [http://grass.osgeo.org/donations/ http://grass.osgeo.org/donations/]'''<br /> <br /> For questions, please contact [[User:Lucadelu|Luca Delucchi]] &lt;tt&gt;&lt;lucadeluge at gmail.com&gt;&lt;/tt&gt;. Any surplus at the end of the event will be turned over to the GRASS GIS project.<br /> <br /> The third 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.<br /> <br /> == Timing ==<br /> <br /> '''When''': 6-12 Feb, 2017<br /> <br /> Of course you are invited to join or leave the community sprint whenever you want.<br /> <br /> '''Duration''': 7 days<br /> <br /> == Venue ==<br /> <br /> Two rooms (A8 and A9) are booked from 6th to 10th February at University of Genova, Polytechnic School of Engineering in [http://osm.org/go/xX0mu8L~Z?m= Villa Cambiaso]<br /> <br /> 11th and 12th February TBD<br /> <br /> == Accommodation and Costs ==<br /> <br /> == Agenda == <br /> <br /> === Timeline ===<br /> <br /> == Participation ==<br /> <br /> === In person (planned) ===<br /> <br /> {|class=&quot;wikitable sortable&quot; border=&quot;2&quot; cellspacing=&quot;0&quot; cellpadding=&quot;4&quot; rules=&quot;all&quot; style=&quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;&quot; <br /> !width=50px|'''Number'''<br /> !width=130px|'''Participant '''<br /> !width=100px|'''Country'''<br /> !width=100px|'''Arrival'''<br /> !width=100px|'''Departure'''<br /> !'''Topic'''<br /> !width=75px|'''T-Shirt'''<br /> !'''Notes'''<br /> |-<br /> |1<br /> |[[User:Lucadelu|Luca Delucchi]]<br /> |Italy<br /> | Feb 3<br /> | Feb 12<br /> |<br /> | L<br /> |<br /> |<br /> |-<br /> |1<br /> |[[User:Ychemin|Yann Chemin]]<br /> |Italy<br /> | Feb 5<br /> | Feb 12<br /> | GDAL-GRASS planetary IAU2000/2009 integration<br /> | XXL<br /> |<br /> |}<br /> <br /> === Via IRC chat or hangout===<br /> <br /> : [irc://freenode/grass #grass] on Freenode<br /> : [http://www.google.com/+/learnmore/hangouts/ G+ hangout] (to be investigated; smartphones only? is Jitsi on a desktop computer compatible?)<br /> <br /> For details, see [[IRC]]<br /> <br /> Please add yourself here below (please add also your gmail account for G+ hangout):<br /> * ADD YOUR SELF<br /> <br /> == Individual Preparation ==<br /> <br /> * Bring your own computer<br /> * Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed ([http://en.wikipedia.org/wiki/File:L_plug.jpg Italy])<br /> * Install subversion and the compiler tools, and come with a working GRASS development environment if possible.<br /> <br /> == Photos ==<br /> <br /> == FAQ ==<br /> <br /> * '''How was it last time?'''<br /> ** Very cool, see [[GRASS Community Sprint Bonn 2016]]!<br /> <br /> * '''Is the GRASS Community Sprint just a coding event?'''<br /> ** 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.<br /> ** On demand, however, we can do some presentations of current working GRASS implementations and new upcoming features to spread the idea of Open Source GIS software.<br /> <br /> * '''Is the GRASS Community Sprint for developers only?'''<br /> ** ''Not at all!'' Anybody can help with testing, checking out bugs and fixes, documentation and more.<br /> <br /> * '''Where can I get help and more information about the community sprint?'''<br /> ** Contact [[User:Lucadelu|Luca Delucchi]] &lt;tt&gt;&lt;lucadeluge at gmail dot com&gt;&lt;/tt&gt; or [[User:Neteler|Markus Neteler]]<br /> <br /> [[Category: Workshops]]<br /> [[Category: Code Sprint]]<br /> [[Category: 2017]]</div>

Lucadelu