I saw a paper on this list the other day, but have deleted the original email. Is this the appropriate thing to cite when referring to GRASS GIS in a paper?
many thanks,
--
Stephen Sefick
**************************************************
Auburn University
Biological Sciences
331 Funchess Hall
Auburn, Alabama
36849
**************************************************
sas0025@auburn.edu http://www.auburn.edu/~sas0025
**************************************************
Let's not spend our time and resources thinking about things that are so little or so large that all they really do for us is puff us up and make us feel like gods. We are mammals, and have not exhausted the annoying little problems of being mammals.
-K. Mullis
"A big computer, a complex algorithm and a long time does not equal science."
On Wed, Dec 14, 2011 at 5:22 PM, Stephen Sefick <sas0025@auburn.edu> wrote:
I saw a paper on this list the other day, but have deleted the original email. Is this the appropriate thing to cite when referring to GRASS GIS in a paper?
many thanks,
–
Stephen Sefick
Auburn University
Biological Sciences
331 Funchess Hall
Auburn, Alabama
36849
Let’s not spend our time and resources thinking about things that are so little or so large that all they really do for us is puff us up and make us feel like gods. We are mammals, and have not exhausted the annoying little problems of being mammals.
-K. Mullis
“A big computer, a complex algorithm and a long time does not equal science.”
The holidays are coming and I thought I would introduce some mystery...
On Wed 14 Dec 2011 01:31:31 PM CST, Marcello Gorini wrote:
Humm I think you forgot "the thing" , no?
On Wed, Dec 14, 2011 at 5:22 PM, Stephen Sefick <sas0025@auburn.edu <mailto:sas0025@auburn.edu>> wrote:
I saw a paper on this list the other day, but have deleted the
original email. Is this the appropriate thing to cite when
referring to GRASS GIS in a paper?
many thanks,
-- Stephen Sefick
******************************__********************
Auburn University
Biological Sciences
331 Funchess Hall
Auburn, Alabama
36849
******************************__********************
sas0025@auburn.edu <mailto:sas0025@auburn.edu> http://www.auburn.edu/~sas0025 <http://www.auburn.edu/~sas0025>
******************************__********************
Let's not spend our time and resources thinking about things that
are so little or so large that all they really do for us is puff
us up and make us feel like gods. We are mammals, and have not
exhausted the annoying little problems of being mammals.
-K. Mullis
"A big computer, a complex algorithm and a long time does not
equal science."
--
Stephen Sefick
**************************************************
Auburn University Biological Sciences 331 Funchess Hall Auburn, Alabama 36849 **************************************************
sas0025@auburn.edu http://www.auburn.edu/~sas0025 **************************************************
Let's not spend our time and resources thinking about things that are so little or so large that all they really do for us is puff us up and make us feel like gods. We are mammals, and have not exhausted the annoying little problems of being mammals.
-K. Mullis
"A big computer, a complex algorithm and a long time does not equal science."
On Wed, Dec 14, 2011 at 8:22 PM, Stephen Sefick <sas0025@auburn.edu> wrote:
I saw a paper on this list the other day, but have deleted the original
email. Is this the appropriate thing to cite when referring to GRASS GIS in
a paper?
* GRASS Development Team, 2010. Geographic Resources Analysis Support
System (GRASS) Software, Version 6.4. Open Source Geospatial
Foundation. http://grass.osgeo.org
* GRASS Development Team, 2010. Geographic Resources Analysis Support
System (GRASS) Programmer's Manual. Open Source Geospatial Foundation.
Electronic document: http://grass.osgeo.org/programming6/
Or the GRASS book:
* M. Neteler, H. Mitasova, Open Source GIS: A GRASS GIS Approach. 3rd
edition, Springer, 2008.
Or the new review paper (pages to be assigned soon):
* Neteler, M., Bowman, M.H., Landa, M. and Metz, M. (2012): GRASS GIS:
a multi-purpose Open Source GIS. Environmental Modelling & Software.
DOI 10.1016/j.envsoft.2011.11.014
I saw a paper on this list the other day, but have deleted the original
email. Is this the appropriate thing to cite when referring to GRASS GIS in
a paper?
GRASS Development Team, 2010. Geographic Resources Analysis Support
System (GRASS) Software, Version 6.4. Open Source Geospatial
Foundation. http://grass.osgeo.org
GRASS Development Team, 2010. Geographic Resources Analysis Support
System (GRASS) Programmer’s Manual. Open Source Geospatial Foundation.
Electronic document: http://grass.osgeo.org/programming6/
In three days time I will be submitting a paper to Geomorphology where the main research was made entirely with GRASS.
I was willing to ask you: right now when I mention I used GRASS I refer to it like
and then when I talk about a specific module I say like
“…the minimum-watershed-size threshold was set to 100 cells (GRASS GIS 6.4.0svn Reference Manual, 2010)…”
Is it correct? If so, should I use the same two aforementioned references at the reference list, but replacing “Programmer’s Manual” by “Reference Manual”?
Thanks for the help. I really want to do it right.
On Thu, Dec 15, 2011 at 1:03 AM, Marcello Gorini <gorini@gmail.com> wrote:
Stephen Sefick:
> I saw a paper on this list the other day, but have deleted the original
> email. Is this the appropriate thing to cite when referring to GRASS
> GIS in
> a paper?
* GRASS Development Team, 2010. Geographic Resources Analysis Support
System (GRASS) Software, Version 6.4. Open Source Geospatial
Foundation. http://grass.osgeo.org
* GRASS Development Team, 2010. Geographic Resources Analysis Support
System (GRASS) Programmer's Manual. Open Source Geospatial Foundation.
Electronic document: http://grass.osgeo.org/programming6/
... I just realize that it should be 2011.
In three days time I will be submitting a paper to Geomorphology where the
main research was made entirely with GRASS.
I was willing to ask you: right now when I mention I used GRASS I refer to
it like