[GRASS-user] import e00? sorry for repeat topic, but...

GRASS GRASS user
1

I solved the problem by once again exporting from Arc in ASCII format, and importing the .txt file with r.in.arc. But I'll answer the questions posed earlier to clarify the issues for anyone else's future reference!
(And, since I completely eliminated my version info from the original posting, here's what it was: OS X, GRASS 6.3 from Kyngesbury's build, but not the most recent one (I'm updating today)).

Here is my problem. I have a few e00 rasters from ArcGIS. When I view
them in ArcMap, everything is fine. When I import using GRASS, with
avcimport and e00conv installed, the maps display properly (I can see
the different categories, etc.). However, the z value is simply a *.
So when I query the file in a monitor, I get UTM-X | UTM-Y | *

The * value is for NULL data. Is there any region clipping occurring or MASK applied? Someone else may be able to intelligently speak to the issue of data displaying ok (colors/categories) but having a NULL data value. That I cant understand. Is your location setup properly, with broad enough extents to encompass the raster?

I was importing to a location that was created with other files of the same extent/projection, and I've been using the location for quite some time. Again, until I re-tried the ASCII version, the other e00 imports were problematic. No region clipping, and no mask.

Clearly, this is not the intended outcome! I do not get errors during
the import, and I have tried exporting the e00 in different formats
from ArcCatalog, and wondered if I should be converting my files to a
different format instead of dealing with ESRI e00?

I had some issues with the e00's. I cant recall specicifally. for best raster interoperability, I found the in Arc, you can export to raster to ASCII (.txt file by default) or export from GRASS as ASCII (*.txt), and use the conversion toolbox "from raster/to raster" to import export.

This is what I will do from now on with GRID files - it certainly seems to be the smoothest way to go.

The other thing I attempted is to convert the e00 to an ASCII file in
ArcInfo, then to import the ESRI ASCII in GRASS. Again, same result
as above.

I'd stick with the ASCII grid file for interchanging.

Am I having projection issues? Do I need to first import the e00/
ASCII to a mapset with the same projection settings as the original
e00, then re-project, or is this unrelated? I think I had tried that
already, with the same result as above, but am willing to try again
if need be.

Is all your data in the same projection? What projection is your GRID/raster in, and what projection is your other data in?

Yep. All NAD83 state plane feet, New Mexico.

What other conversion options may work from within Arc?

for rasters, I found the ASCII GRID format to be the best for importing/exporting data.

Thanks again.
Brandon

2

Hi Brandon,

A couple of additional pointers besides exporting as ASCII grids from
ArcGIS.

Using r.in.gdal, GRASS can directly read ArcInfo grid files. When opening
them, select the *.HDR file as your data source. No need to export.

Similarly, v.in.ogr can directly read ArcGIS shape files. Select the
*directory* in which the shape files live as the data source (no "/" on the
end); select the shape file (omit the ".shp" extension) as the data layer.
Again, no need to export.

With both, depending on how they were made, you might have to override the
projection info (or rather it's lack) in the ESRI file. But as long as you
know that your ESRI file and GRASS location share the same projection,
that's OK.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

3

Thanks Michael,

I've imported lots of shapefiles by simply selecting the *.shp file as the data source; does your method produce a different result (such as transferring metadata, etc. to the GRASS directories)? I had always understood that for the *.shp vectors, GRASS just needed the *.shp file.

I'll try the *.hdr import with r.in.gdal as well; that would save a step and eliminate the need for Arc on my system!

Brandon

_______________________
Brandon M. Gabler
Doctoral Candidate
Department of Anthropology
University of Arizona
Tucson, AZ 85721
Phone: (520) 621-8455
Fax: (520) 621-2088
bgabler@email.arizona.edu

"Who? When? Whither? are the questions with which the archaeologist challenges the refuse heaps, scattered potsherds, and broken shafts, to tell of the builders who came and lived and went their way into the templed past." -- Edgar Lee Hewett, in Pajarito Plateau and its Ancient People, 1938

On Nov 20, 2007, at 8:34 AM, Michael Barton wrote:

Hi Brandon,

A couple of additional pointers besides exporting as ASCII grids from
ArcGIS.

Using r.in.gdal, GRASS can directly read ArcInfo grid files. When opening
them, select the *.HDR file as your data source. No need to export.

Similarly, v.in.ogr can directly read ArcGIS shape files. Select the
*directory* in which the shape files live as the data source (no "/" on the
end); select the shape file (omit the ".shp" extension) as the data layer.
Again, no need to export.

With both, depending on how they were made, you might have to override the
projection info (or rather it's lack) in the ESRI file. But as long as you
know that your ESRI file and GRASS location share the same projection,
that's OK.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

4

On 11/20/07 11:19 AM, "Brandon M. Gabler" <bgabler@email.arizona.edu> wrote:

Thanks Michael,

I've imported lots of shapefiles by simply selecting the *.shp file
as the data source; does your method produce a different result (such
as transferring metadata, etc. to the GRASS directories)? I had
always understood that for the *.shp vectors, GRASS just needed the
*.shp file.

Brandon,

This is news to me. But I just tried it and (contrary to the documentation)
it works fine. Both approaches seem to give the same result. But your way is
easier to do and to explain than the method explained in the help.

Michael

I'll try the *.hdr import with r.in.gdal as well; that would save a
step and eliminate the need for Arc on my system!

This does make life easier.

Hope the research is going well.

Michael

Brandon

_______________________
Brandon M. Gabler
Doctoral Candidate
Department of Anthropology
University of Arizona
Tucson, AZ 85721
Phone: (520) 621-8455
Fax: (520) 621-2088
bgabler@email.arizona.edu

"Who? When? Whither? are the questions with which the archaeologist
challenges the refuse heaps, scattered potsherds, and broken shafts,
to tell of the builders who came and lived and went their way into
the templed past." -- Edgar Lee Hewett, in Pajarito Plateau and its
Ancient People, 1938

On Nov 20, 2007, at 8:34 AM, Michael Barton wrote:

Hi Brandon,

A couple of additional pointers besides exporting as ASCII grids from
ArcGIS.

Using r.in.gdal, GRASS can directly read ArcInfo grid files. When
opening
them, select the *.HDR file as your data source. No need to export.

Similarly, v.in.ogr can directly read ArcGIS shape files. Select the
*directory* in which the shape files live as the data source (no
"/" on the
end); select the shape file (omit the ".shp" extension) as the data
layer.
Again, no need to export.

With both, depending on how they were made, you might have to
override the
projection info (or rather it's lack) in the ESRI file. But as long
as you
know that your ESRI file and GRASS location share the same projection,
that's OK.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

__________________________________________
Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

5

Brandon wrote:
> I've imported lots of shapefiles by simply selecting the *.shp file
> as the data source; does your method produce a different result (such
> as transferring metadata, etc. to the GRASS directories)? I had
> always understood that for the *.shp vectors, GRASS just needed the
> *.shp file.

Michael:

This is news to me. But I just tried it and (contrary to the documentation)
it works fine. Both approaches seem to give the same result. But your way is
easier to do and to explain than the method explained in the help.

It works both ways. v.in.ogr help page now updated to show both methods.

Hamish

      ____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs

6

On 21/11/07 03:07, Hamish wrote:

Brandon wrote:

I've imported lots of shapefiles by simply selecting the *.shp file
as the data source; does your method produce a different result (such
as transferring metadata, etc. to the GRASS directories)? I had
always understood that for the *.shp vectors, GRASS just needed the
*.shp file.

Michael:

This is news to me. But I just tried it and (contrary to the documentation)
it works fine. Both approaches seem to give the same result. But your way is
easier to do and to explain than the method explained in the help.

It works both ways. v.in.ogr help page now updated to show both methods.

Isn't this just due to the fact that ogr ignores the file you point to and just takes account of the directory if the datasource should be a directory (i.e. for shapefiles) ?

So, the original description is correct (i.e. that for shapefiles dsn is a directory), but in practice it doesn't matter since ogr takes care of that.

Moritz

7

Moritz Lennert wrote:

Isn't this just due to the fact that ogr ignores the file you point to
and just takes account of the directory if the datasource should be a
directory (i.e. for shapefiles) ?

So, the original description is correct (i.e. that for shapefiles dsn is
a directory), but in practice it doesn't matter since ogr takes care of
that.

If you point OGR at a directory, it takes it for a "data
source", and the OGR supported vector files inside for
available "OGR layers" (at least in case of ESRI Shapefiles
and MapInfo files).

If you point it directly at an *.shp file, the whole "data
source" is that single shapefile, and the only "layer"
available at the same time.

Try "ogrinfo -al -so /path/to/dir/with/shapefiles" or
"v.in.ogr -l dsn=/path/to/dir/with/shapefiles".

Maciek

8

On 26/11/07 17:58, Maciej Sieczka wrote:

Moritz Lennert wrote:

Isn't this just due to the fact that ogr ignores the file you point to
and just takes account of the directory if the datasource should be a
directory (i.e. for shapefiles) ?

So, the original description is correct (i.e. that for shapefiles dsn is
a directory), but in practice it doesn't matter since ogr takes care of
that.

If you point OGR at a directory, it takes it for a "data
source", and the OGR supported vector files inside for
available "OGR layers" (at least in case of ESRI Shapefiles
and MapInfo files).

If you point it directly at an *.shp file, the whole "data
source" is that single shapefile, and the only "layer"
available at the same time.

Try "ogrinfo -al -so /path/to/dir/with/shapefiles" or
"v.in.ogr -l dsn=/path/to/dir/with/shapefiles".

Yes, I get it. Thanks for the explanation.

Moritz