they are arc binary data correct. Is there anyway I can use these
with GRASS or QGIS?
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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.
they are arc binary data correct. Is there anyway I can use these
with GRASS or QGIS?
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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.
the arc “adf” type files i’ve imported have had filenames like w001001.adf and that is what i’ve specified when using r.in.gdal and it has worked, however i also have in the same directory a hdr.adf file and i think if that file is missing it gives me an error.
have you tried using r.in.gdal and specifying some of the .adf files in your dataset? i usually look for whatever file is the biggest and specify that one, assuming it is the one containing all the data i want to import.
they are arc binary data correct. Is there anyway I can use these
with GRASS or QGIS?
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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.
they are arc binary data correct. Is there anyway I can use these
with GRASS or QGIS?
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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.
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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.
That's what I figured. Then I am fairly sure this is what you're
after, http://grass.osgeo.org/grass64/manuals/html64_user/v.in.ogr.html.
Arc Vector coverages are stored in 2 directories. One for geometry
(the directory is the name of the coverage) and the database is
contained in an 'info' directory. The examples below are not clear to
me how it addresses this, but it does state it will do it. I could
try some testing tomorrow if not figured out by then.
# Arc Coverage
We import the Arcs and Label points, the module takes care to build areas:
# E00 file (see also v.in.e00)
First we have to convert the E00 file to an Arc Coverage with
'avcimport' (AVCE00 tools, use e00conv first in case that avcimport
fails):
they are arc binary data correct. Is there anyway I can use these
with GRASS or QGIS?
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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.
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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.
Much to my delight, v.in.ogr reads the binary arc coverages. I copied
over the directory (which is the coverage name) and the info directory
to a place on the Linux machine which has GRASS installed. (not sure
if the 'info' directory is needed, but it did preserve attributes).
For the OGR datasource name, I pointed it to the "arc.adf" file, and
it imported the coverage as a GRASS vector with points, lines and
polygon features. Attributes also preserved.
Please let me know if you have any issues with this. First time I
tried this, and great to know it can read the binary coverages.
Mark
On Mon, Jul 12, 2010 at 8:02 PM, Mark Seibel <mseibel@gmail.com> wrote:
That's what I figured. Then I am fairly sure this is what you're
after, http://grass.osgeo.org/grass64/manuals/html64_user/v.in.ogr.html.
Arc Vector coverages are stored in 2 directories. One for geometry
(the directory is the name of the coverage) and the database is
contained in an 'info' directory. The examples below are not clear to
me how it addresses this, but it does state it will do it. I could
try some testing tomorrow if not figured out by then.
# Arc Coverage
We import the Arcs and Label points, the module takes care to build areas:
# E00 file (see also v.in.e00)
First we have to convert the E00 file to an Arc Coverage with
'avcimport' (AVCE00 tools, use e00conv first in case that avcimport
fails):
they are arc binary data correct. Is there anyway I can use these
with GRASS or QGIS?
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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.
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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.
I don't have an info directory. I tried using v.in.ogr to no avail.
So, I downloaded the nation hydrography dataset and now I am trying to
find out projection information.
thanks,
STephen
On Tue, Jul 13, 2010 at 8:10 AM, Mark Seibel <mseibel@gmail.com> wrote:
Much to my delight, v.in.ogr reads the binary arc coverages. I copied
over the directory (which is the coverage name) and the info directory
to a place on the Linux machine which has GRASS installed. (not sure
if the 'info' directory is needed, but it did preserve attributes).
For the OGR datasource name, I pointed it to the "arc.adf" file, and
it imported the coverage as a GRASS vector with points, lines and
polygon features. Attributes also preserved.
Please let me know if you have any issues with this. First time I
tried this, and great to know it can read the binary coverages.
Mark
On Mon, Jul 12, 2010 at 8:02 PM, Mark Seibel <mseibel@gmail.com> wrote:
That's what I figured. Then I am fairly sure this is what you're
after, http://grass.osgeo.org/grass64/manuals/html64_user/v.in.ogr.html.
Arc Vector coverages are stored in 2 directories. One for geometry
(the directory is the name of the coverage) and the database is
contained in an 'info' directory. The examples below are not clear to
me how it addresses this, but it does state it will do it. I could
try some testing tomorrow if not figured out by then.
# Arc Coverage
We import the Arcs and Label points, the module takes care to build areas:
# E00 file (see also v.in.e00)
First we have to convert the E00 file to an Arc Coverage with
'avcimport' (AVCE00 tools, use e00conv first in case that avcimport
fails):
they are arc binary data correct. Is there anyway I can use these
with GRASS or QGIS?
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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.
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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.
How did you obtain the coverage? They are typically distributed as
e00 files, which when imported create a directory for the geometry and
an info directory for the attributes.
Mark
On Wed, Jul 14, 2010 at 9:20 AM, stephen sefick <ssefick@gmail.com> wrote:
I don't have an info directory. I tried using v.in.ogr to no avail.
So, I downloaded the nation hydrography dataset and now I am trying to
find out projection information.
thanks,
STephen
On Tue, Jul 13, 2010 at 8:10 AM, Mark Seibel <mseibel@gmail.com> wrote:
Much to my delight, v.in.ogr reads the binary arc coverages. I copied
over the directory (which is the coverage name) and the info directory
to a place on the Linux machine which has GRASS installed. (not sure
if the 'info' directory is needed, but it did preserve attributes).
For the OGR datasource name, I pointed it to the "arc.adf" file, and
it imported the coverage as a GRASS vector with points, lines and
polygon features. Attributes also preserved.
Please let me know if you have any issues with this. First time I
tried this, and great to know it can read the binary coverages.
Mark
On Mon, Jul 12, 2010 at 8:02 PM, Mark Seibel <mseibel@gmail.com> wrote:
That's what I figured. Then I am fairly sure this is what you're
after, http://grass.osgeo.org/grass64/manuals/html64_user/v.in.ogr.html.
Arc Vector coverages are stored in 2 directories. One for geometry
(the directory is the name of the coverage) and the database is
contained in an 'info' directory. The examples below are not clear to
me how it addresses this, but it does state it will do it. I could
try some testing tomorrow if not figured out by then.
# Arc Coverage
We import the Arcs and Label points, the module takes care to build areas:
# E00 file (see also v.in.e00)
First we have to convert the E00 file to an Arc Coverage with
'avcimport' (AVCE00 tools, use e00conv first in case that avcimport
fails):
they are arc binary data correct. Is there anyway I can use these
with GRASS or QGIS?
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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.
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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.
They were sent to me by some folk I am working with. I don't know how
they generated the coverages.
On Wed, Jul 14, 2010 at 8:59 AM, Mark Seibel <mseibel@gmail.com> wrote:
How did you obtain the coverage? They are typically distributed as
e00 files, which when imported create a directory for the geometry and
an info directory for the attributes.
Mark
On Wed, Jul 14, 2010 at 9:20 AM, stephen sefick <ssefick@gmail.com> wrote:
I don't have an info directory. I tried using v.in.ogr to no avail.
So, I downloaded the nation hydrography dataset and now I am trying to
find out projection information.
thanks,
STephen
On Tue, Jul 13, 2010 at 8:10 AM, Mark Seibel <mseibel@gmail.com> wrote:
Much to my delight, v.in.ogr reads the binary arc coverages. I copied
over the directory (which is the coverage name) and the info directory
to a place on the Linux machine which has GRASS installed. (not sure
if the 'info' directory is needed, but it did preserve attributes).
For the OGR datasource name, I pointed it to the "arc.adf" file, and
it imported the coverage as a GRASS vector with points, lines and
polygon features. Attributes also preserved.
Please let me know if you have any issues with this. First time I
tried this, and great to know it can read the binary coverages.
Mark
On Mon, Jul 12, 2010 at 8:02 PM, Mark Seibel <mseibel@gmail.com> wrote:
That's what I figured. Then I am fairly sure this is what you're
after, http://grass.osgeo.org/grass64/manuals/html64_user/v.in.ogr.html.
Arc Vector coverages are stored in 2 directories. One for geometry
(the directory is the name of the coverage) and the database is
contained in an 'info' directory. The examples below are not clear to
me how it addresses this, but it does state it will do it. I could
try some testing tomorrow if not figured out by then.
# Arc Coverage
We import the Arcs and Label points, the module takes care to build areas:
# E00 file (see also v.in.e00)
First we have to convert the E00 file to an Arc Coverage with
'avcimport' (AVCE00 tools, use e00conv first in case that avcimport
fails):
they are arc binary data correct. Is there anyway I can use these
with GRASS or QGIS?
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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.
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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.
Probably the did not send you the entire thing since Arc coverages
have data in the info folder. Maybe if they export the coverage as an
e00 file or as a shapefile it would be better.
Daniel
On Wed, Jul 14, 2010 at 11:01 AM, stephen sefick <ssefick@gmail.com> wrote:
They were sent to me by some folk I am working with. I don't know how
they generated the coverages.
On Wed, Jul 14, 2010 at 8:59 AM, Mark Seibel <mseibel@gmail.com> wrote:
How did you obtain the coverage? They are typically distributed as
e00 files, which when imported create a directory for the geometry and
an info directory for the attributes.
Mark
On Wed, Jul 14, 2010 at 9:20 AM, stephen sefick <ssefick@gmail.com> wrote:
I don't have an info directory. I tried using v.in.ogr to no avail.
So, I downloaded the nation hydrography dataset and now I am trying to
find out projection information.
thanks,
STephen
On Tue, Jul 13, 2010 at 8:10 AM, Mark Seibel <mseibel@gmail.com> wrote:
Much to my delight, v.in.ogr reads the binary arc coverages. I copied
over the directory (which is the coverage name) and the info directory
to a place on the Linux machine which has GRASS installed. (not sure
if the 'info' directory is needed, but it did preserve attributes).
For the OGR datasource name, I pointed it to the "arc.adf" file, and
it imported the coverage as a GRASS vector with points, lines and
polygon features. Attributes also preserved.
Please let me know if you have any issues with this. First time I
tried this, and great to know it can read the binary coverages.
Mark
On Mon, Jul 12, 2010 at 8:02 PM, Mark Seibel <mseibel@gmail.com> wrote:
That's what I figured. Then I am fairly sure this is what you're
after, http://grass.osgeo.org/grass64/manuals/html64_user/v.in.ogr.html.
Arc Vector coverages are stored in 2 directories. One for geometry
(the directory is the name of the coverage) and the database is
contained in an 'info' directory. The examples below are not clear to
me how it addresses this, but it does state it will do it. I could
try some testing tomorrow if not figured out by then.
# Arc Coverage
We import the Arcs and Label points, the module takes care to build areas:
# E00 file (see also v.in.e00)
First we have to convert the E00 file to an Arc Coverage with
'avcimport' (AVCE00 tools, use e00conv first in case that avcimport
fails):
they are arc binary data correct. Is there anyway I can use these
with GRASS or QGIS?
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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.
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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.
On Wed, Jul 14, 2010 at 9:33 AM, Daniel Victoria
<daniel.victoria@gmail.com> wrote:
Probably the did not send you the entire thing since Arc coverages
have data in the info folder. Maybe if they export the coverage as an
e00 file or as a shapefile it would be better.
Daniel
On Wed, Jul 14, 2010 at 11:01 AM, stephen sefick <ssefick@gmail.com> wrote:
They were sent to me by some folk I am working with. I don't know how
they generated the coverages.
On Wed, Jul 14, 2010 at 8:59 AM, Mark Seibel <mseibel@gmail.com> wrote:
How did you obtain the coverage? They are typically distributed as
e00 files, which when imported create a directory for the geometry and
an info directory for the attributes.
Mark
On Wed, Jul 14, 2010 at 9:20 AM, stephen sefick <ssefick@gmail.com> wrote:
I don't have an info directory. I tried using v.in.ogr to no avail.
So, I downloaded the nation hydrography dataset and now I am trying to
find out projection information.
thanks,
STephen
On Tue, Jul 13, 2010 at 8:10 AM, Mark Seibel <mseibel@gmail.com> wrote:
Much to my delight, v.in.ogr reads the binary arc coverages. I copied
over the directory (which is the coverage name) and the info directory
to a place on the Linux machine which has GRASS installed. (not sure
if the 'info' directory is needed, but it did preserve attributes).
For the OGR datasource name, I pointed it to the "arc.adf" file, and
it imported the coverage as a GRASS vector with points, lines and
polygon features. Attributes also preserved.
Please let me know if you have any issues with this. First time I
tried this, and great to know it can read the binary coverages.
Mark
On Mon, Jul 12, 2010 at 8:02 PM, Mark Seibel <mseibel@gmail.com> wrote:
That's what I figured. Then I am fairly sure this is what you're
after, http://grass.osgeo.org/grass64/manuals/html64_user/v.in.ogr.html.
Arc Vector coverages are stored in 2 directories. One for geometry
(the directory is the name of the coverage) and the database is
contained in an 'info' directory. The examples below are not clear to
me how it addresses this, but it does state it will do it. I could
try some testing tomorrow if not figured out by then.
# Arc Coverage
We import the Arcs and Label points, the module takes care to build areas:
# E00 file (see also v.in.e00)
First we have to convert the E00 file to an Arc Coverage with
'avcimport' (AVCE00 tools, use e00conv first in case that avcimport
fails):
they are arc binary data correct. Is there anyway I can use these
with GRASS or QGIS?
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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.
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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.
--
Stephen Sefick
____________________________________
| Auburn University |
| Department of 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.