Eric: >> Thanks for the pointer. I'll hardcode my database paths for now.
Hamish: > see the db.connect help page example for DBF (I usually just cut and > paste that to the command line when needed). It accepts variable > LOCATION, MAPSET, you don't need to hardcode it. (Be sure to keep the > path with $VARIABLES in single quotes!) Should each of $GISDABSE, $LOCATION_NAME, and $MAPSET have populated values on location startup? These variables always remain blank for each location that I try: ~ >echo $GISDBASE ~ >echo $LOCATION_NAME ~ >echo $MAPSET ~ > are these variables only available from the shell if I export `g.gisenv` or eval `g.gisenv` first? ~ Eric.
<<winmail.dat>>
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
