i would gladly be a part of a arc/info to grass translation team, or illustrating feature comparisons. <br><br><div><span class="gmail_quote">On 6/14/06, <b class="gmail_sendername">Thomas Adams</b> <<a href="mailto:Thomas.Adams@noaa.gov">
Thomas.Adams@noaa.gov</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Along these same lines, it would be *really* valuable (for many) to list
<br>side-by-side the features of GRASS vs ArcGIS and also layout arguments<br>supporting the use of GRASS over ArcGIS. I'm trying to do this, but I<br>could very much use some help. I am on a National team within the US<br>
National Weather Service to make a recommendation on what direction to<br>go with GIS. Clearly, there are plusses and minuses with both. I have a<br>table of GIS requirements for River Forecast Centers and GRASS seems to<br>
meet the vast majority of needs, however I am up against prejudice in<br>much the same way that Apple Computer has struggled against MS-Windows<br>users; much stemming from people who have never tried using GRASS GIS,<br>
or at least, not in the past 4-5 years!<br><br>Tom<br><br><br>David Finlayson wrote:<br>> I think it would be perfect for the wiki. A few other issues would be<br>> the difference between grass region vs. setwindow/mapextent; grass
<br>> LOCATION/MAPSET vs. ArcInfo's directory structure (none). And of<br>> course, how to convert your data back and forth.<br>><br>> On 6/14/06, Dylan Beaudette <<a href="mailto:dylan.beaudette@gmail.com">
dylan.beaudette@gmail.com</a>> wrote:<br>>> Hi Jonathan,<br>>><br>>> How about a section on the wiki, i am not so sure if it would be a<br>>> good idea to pollute the standard man pages with arcinfo stuff.
<br>>> Perhaps something like the table which compares GRASS 5 features to<br>>> GRASS 6.<br>>><br>>> any volunteers? :)<br>>><br>>> Dylan<br>>><br>>> On 6/14/06, Jonathan Greenberg <
<a href="mailto:jgreenberg@arc.nasa.gov">jgreenberg@arc.nasa.gov</a>> wrote:<br>>> > It occurs to me it would be really useful to have an "arc/info<br>>> equivalent"<br>>> > portion of the GRASS website, since many of us come from an ESRI
<br>>> background<br>>> > -- basically have a listing of arc commands and their respective grass<br>>> > commands, with maybe some notes on differences between the two.<br>>> Thoughts?<br>>> > A wiki-like approach to building this up might be the best, so each
<br>>> of us<br>>> > who is working on an arc-> grass conversion project can post info on<br>>> > comparisons of the functions. Thoughts?<br>>> ><br>>> > --j<br>>> ><br>
>> > --<br>>> ><br>>> > Jonathan A. Greenberg, PhD<br>>> > NRC Research Associate<br>>> > NASA Ames Research Center<br>>> > MS 242-4<br>>> > Moffett Field, CA 94035-1000
<br>>> > Phone: 415-794-5043<br>>> > AIM: jgrn3007<br>>> > MSN: <a href="mailto:jgrn3007@hotmail.com">jgrn3007@hotmail.com</a><br>>> ><br>>> ><br>>> > _______________________________________________
<br>>> > grassuser mailing list<br>>> > <a href="mailto:grassuser@grass.itc.it">grassuser@grass.itc.it</a><br>>> > <a href="http://grass.itc.it/mailman/listinfo/grassuser">http://grass.itc.it/mailman/listinfo/grassuser
</a><br>>> ><br>>><br>>> _______________________________________________<br>>> grassuser mailing list<br>>> <a href="mailto:grassuser@grass.itc.it">grassuser@grass.itc.it</a><br>>> <a href="http://grass.itc.it/mailman/listinfo/grassuser">
http://grass.itc.it/mailman/listinfo/grassuser</a><br>>><br>><br>><br><br><br>--<br>Thomas E Adams<br>National Weather Service<br>Ohio River Forecast Center<br>1901 South State Route 134<br>Wilmington, OH 45177
<br><br>EMAIL: <a href="mailto:thomas.adams@noaa.gov">thomas.adams@noaa.gov</a><br><br>VOICE: 937-383-0528<br>FAX: 937-383-0033<br><br>_______________________________________________<br>grassuser mailing list<br><a href="mailto:grassuser@grass.itc.it">
grassuser@grass.itc.it</a><br><a href="http://grass.itc.it/mailman/listinfo/grassuser">http://grass.itc.it/mailman/listinfo/grassuser</a><br></blockquote></div><br>