142 lines
2.6 KiB
HTML
142 lines
2.6 KiB
HTML
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>Continued Assessment of Future GRASS Management</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.56"><LINK
|
|
REL="HOME"
|
|
TITLE="The Geographic Information Systems: GRASS HOWTO"
|
|
HREF="index.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="A Re-Invogorated GRASS Management Model"
|
|
HREF="managementmodel.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="System Requirements for GRASS"
|
|
HREF="requirements.html"></HEAD
|
|
><BODY
|
|
CLASS="SECT1"
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#840084"
|
|
ALINK="#0000FF"
|
|
><DIV
|
|
CLASS="NAVHEADER"
|
|
><TABLE
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TH
|
|
COLSPAN="3"
|
|
ALIGN="center"
|
|
>The Geographic Information Systems: GRASS HOWTO</TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="managementmodel.html"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
></TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="requirements.html"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="SECT1"
|
|
><H1
|
|
CLASS="SECT1"
|
|
><A
|
|
NAME="FUTUREMANAGEMENT"
|
|
>3.2. Continued Assessment of Future GRASS Management</A
|
|
></H1
|
|
><P
|
|
> Note: An ad-hoc group (which includes myself) is exploring the basic issue
|
|
of continued, reconfigured, yea perhaps increased, value of GRASS as a
|
|
public test-bed for GIS technology. It is exploring shepherding the
|
|
testing and release of GRASS5.0, and exploring possibilities for a more
|
|
distributed management model for GRASS design and development. It is
|
|
exploring the universe of public domain spatial data processing software
|
|
(including geographic information and image processing systems), and
|
|
perhaps tabular data base management systems. How can such knowledge be
|
|
(1) optimized as an open, public test bed for such technology and (2)
|
|
better used by the public? Might this involve a Linux management model,
|
|
perhaps? See Section 8 for more discussion on this topic.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="NAVFOOTER"
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"><TABLE
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="managementmodel.html"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="index.html"
|
|
>Home</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="requirements.html"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
>A Re-Invogorated GRASS Management Model</TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
> </TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>System Requirements for GRASS</TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |