<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Here is my problem. I have a few e00 rasters from ArcGIS. When I view
<br>them in ArcMap, everything is fine. When I import using GRASS, with<br>avcimport and e00conv installed, the maps display properly (I can see<br>the different categories, etc.). However, the z value is simply a *.<br>So when I query the file in a monitor, I get UTM-X | UTM-Y | *
<br></blockquote><div><br>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?
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>Clearly, this is not the intended outcome! I do not get errors during<br>the import, and I have tried exporting the e00 in different formats
<br>from ArcCatalog, and wondered if I should be converting my files to a<br>different format instead of dealing with ESRI e00?</blockquote><div><br>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.
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br>The other thing I attempted is to convert the e00 to an ASCII file in<br>ArcInfo, then to import the ESRI ASCII in GRASS. Again, same result
<br>as above.<br></blockquote><div><br>I'd stick with the ASCII grid file for interchanging. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Am I having projection issues? Do I need to first import the e00/<br>ASCII to a mapset with the same projection settings as the original<br>e00, then re-project, or is this unrelated? I think I had tried that<br>already, with the same result as above, but am willing to try again
<br>if need be.<br></blockquote><div><br>Is all your data in the same projection? What projection is your GRID/raster in, and what projection is your other data in?<br><br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>What other conversion options may work from within Arc?</blockquote><div><br>for rasters, I found the ASCII GRID format to be the best for importing/exporting data.<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br>Thanks,<br>Brandon<br><br>_______________________________________________<br>grass-user mailing list<br><a href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/grass-user" target="_blank">
http://lists.osgeo.org/mailman/listinfo/grass-user</a><br></blockquote></div><br>