<span class="q" id="q_1129efc7c18722e0_0">Hello all,<br><br>I have been using FOSS GIS tools, especially GRASS, for last few<br>years. We are trying to promote the use of FOSS GIS over here. As part<br>of this, we have conducted a course on "FOSS GIS", conducted by my
<br>organisation, Kerala State Electronics Development Corporation<br>(KELTRON), for a transport research and development organisation named<br>NATPAC over here. This mail is to share the experience, and some<br>feedbacks and suggestions we got.
<br><br>It was a seven day course, conducted in two batches, having around 10<br>participants per batch. The group included a few AutoCAD digitisation<br>people, a few ArcGIS experts and some scientists. In general, FOSS GIS
<br>has been accepted by the all participants. Almost all requirements of<br>the people could easily be done in FOSS GIS, and some are much better<br>than proprietary counter parts (GRASS vector architecture, etc). They<br>
will be using FOSS GIS for some of their projects.<br><br>We used Ubuntu GNU/Linux as operating system. A custom CD covering<br>major FOSS GIS tools was created to support the course. Major<br>suggestions from the participants are,
<br><br>a. Undo/Redo facility in GRASS digitisation (or GRASS-QGIS digitisation)<br><br>b. Copy-paste facility for copying features during digitisation<br><br>c. Facility for displaying Graphs and Charts in QGIS (Like<br>
d.vect.chart in QGIS)<br><br>d. Improvements in GRASS GUI (I think no need to mention)<br><br></span>
<div style="direction: ltr;">I am attaching a detailed note herewith. Shall I add them as feature requests<br>in issue tracker?<br></div>
<span class="q">--<br>Sajith VK<br>Change the rules, or the rules will change you :Kumaranasan</span>