On Wed, 21 Mar 2012, Daniel Lee wrote:
I've also had trouble with using Postgres tables in GRASS and then changing them. If I deleted the tables in the past, it was always very difficult to be able to delete the corresponding vector maps. My only real positive experience in that regard has been to delete the mapset and start anew, but of course that's about as far from elegant as you can get. Sorry that I don't know more about the way GRASS interacts with Postgres and where the connection is stored.
Daniel, I'm sure that the grass-postgres interface could use a lot of tuning, but the developers are probably focused more on other aspects. For one project, deleting a couple of locations/mapsets would be a hassle, but do-able as a last resort. The other project has several dozen maps and postgres tables and I'd hate to have to recreate them all. What puzzles me is that db.connect -p shows the new database name, but when I try to import an .e00 file or re-project the vector map, the GUI crashes; if I do it on the command line, I still get the errors that caused the GUI to leave. Thanks, Rich _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
