Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Mercy Corps

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 83 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  

HOWTO Home

Current HOWTO: GIS-GRASS


The Future of GRASS?

8. The Future of GRASS?

Excellent question! Several possible answers have been thrown out:

  1. USA/CERL's announced intention is to use GRASS and COTS (commercial off-the-shelf software) for internal uses, to leave the GRASS public web- and ftp-site on its system indefinitely, and to sign cooperative research and development agreements with three companies: (1) the Environmental Sciences Research Institute (ESRI), (2) Intergraph, and (3) Logiciels et Applications Scientifiques (L.A.S.) Inc. The first two agreements encouraged the incorporation of GRASS concepts into ESRI's and Intergraph's commercial GISs. The third encouraged the adaptation of GRASS' concepts and code into a new commercial GIS by L.A.S. L.A.S. also offered to encourage the continuation of a public domain GRASS, as a viable stand-alone system and as a potential source of new ideas and code for L.A.S.'s GRASSLAND. One observer noted that the first two agreements might be akin to someone signing Linux over to Microsoft. The same observer considers the experiment by/with L.A.S. to be an interesting possibility - an attempt to keep viable public domain and commercial versions of GRASS.

  2. Some people believe that GRASS will wither without USA/CERL's central management. Some believe that the Open GIS Consortium will successfully guide industry into an open architecture that will benefit all developers and users. Others believe that OGIS' effort will lead to a cacophony of almost similar (but not quite interoperable) vendor-specific "standards," so the loss of GRASS as an open development platform will be felt sorely.

  3. Some people believe that developments on some campuses and other sites may result in those institutes keeping GRASS for awhile, but in non-standard forms. In short, GRASS will undergo "cell division" and lead to a cacophony of internally valuable, but externally unused, GISs.

  4. Others hope that GRASS' previous management model under USA/CERL has left it ready for a new model. Perhaps:

    1. Under a new mentor, such as NASA (which needs an open, powerful and scientific, GIS integrated with image processing system for its Earth Observing System).

    2. Under a distributed management model... perhaps somewhat like Linux?

    3. Perhaps a bit of a hybrid? Perhaps a Web-based effort could spawn a series of usenet discussion groups beginning with

      • comp.infosystems.gis.grass, and evolving to:

      • comp.infosystems.gis.grass.academics

      • comp.infosystems.gis.grass.publicservice

      • comp.infosystems.gis.grass.commercialvalueadded

      • comp.infosystems.gis.grass.commercialdistributors

      • comp.infosystems.gis.grass.programming

      • comp.infosystems.gis.grass.users

      • comp.infosystems.gis.grass.centralcommittee

      Clearly the topics are a bit tongue-in-cheek. However, under this model, a Central Committee (including representation of academic, public service [government and nongovernmental organizations], commercial distributors and value added firms, programmers, and users) would guide overall grass development and testing. The other special interest groups would serve their user communities. Academics, for example, would involve GIS and GRASS education, but would also try to pull GRASS development in its direction. Value added commercial developers would serve their own interests, including trying to pull GRASS development in a direction that would help their businesses. Users would help each other learn GRASS, develop workarounds to bugs, etc.

GRASS offers considerable potential for:

  • Use as a scientific, as well as a traditional graphically oriented GIS. Many GISs can make pretty maps. Many of those GISs cannot easily perform certain scientific analytical functions as easily or powerfully as GRASS. GRASS was designed and developed in response to a perceived need for scientific GIS, specifically for environmental analysis, and the environmental management/protection of public lands. Incidentally, there is at least one Web-based GRASS version. GRASSLINKS, developed at The University of California at Berkeley, uses Web forms to submit commands to the server, which creates .gif-based display output, places the images into pages, and serves them up to the requester. More on that later.

  • Education. GRASS is easier to teach and learn than some other GISs. It is easier to modify (for those that want to learn GIS as computer science, rather than as "geography") than most other GISs that come without source code and treat the program as a magical black box. And, of course, it is more affordable for the student of GIS than many other GISs.

  • Applications research and development. Many universities have used GRASS. Its available source code, easy modification, easy scriptability, etc., give it distinct advantages over some more closed systems.

  • Public Service. GRASS has been used as a scientific GIS for many public service applications. There is considerable value in continuing a robust GIS that can ba packaged with any UNIX workstation. There is considerably more value if that UNIX workstation universe can include Linux (but is not constrained only to Linux).

  • GIS research and development. For example - do you want to experiment with a different data model? Add it to GRASS!

  • Commercialization. This document gives contact information for a commercial version of GRASS. That company (and perhaps others?) may welcome your help in enhancing/supporting their product.

Who would be the Linus Torvalds equivalent in this management model? Perhaps no single person. I have been involved in GRASS for about a decade, when GRASS was the only GIS that satisfied my needs in scientific data management and GIS application. Indeed, I had been a dedicated avoider of the user-unfriendly UNIX environment until GRASS forced me to learn it. Several senior GRASS developers are active in GRASS-related activities and would like to see the continued vitality of an open GRASS. It's likely that a reborn GRASS would attract a new crop of friends. Thus the concept of a "Central Committee" to collectively lead GRASS' transition to a more open management and development style.

In short, the Linux community has an opportunity to take under its wing a killer ap. GRASS' current public domain status is slightly different from Linux's. However, that status could be discussed....

Comments would be appreciated!


The Linux Tutorial completely respects the rights of authors and artists to decide for themselves if and how their works can be used, independent of any existing licenses. This means if you are the author of any document presented on this site and do no wish it to be displayed as it is on this site or do not wish it to be displayed at all, please contact us and we will do our very best to accommodate you. If we are unable to accommodate you, we will, at your request, remove your document as quickly as possible.

If you are the author of any document presented on this site and would like a share of the advertising revenue, please contact us using the standard Feedback Form.


  

Looking for a "printer friendly" version?


Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
The Linux Tutorial welcomes your suggestions and ideas.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.16 Seconds