#7: Location wizard: should predefine DB connection for new location
--+-
Reporter: neteler | Owner: hamish
Type: defect | Status: closed
Priority: major| Milestone:
#7: Location wizard: should predefine DB connection for new location
--+-
Reporter: neteler | Owner: hamish
Type: defect | Status: closed
Priority: major| Milestone:
#7: Location wizard: should predefine DB connection for new location
--+-
Reporter: neteler | Owner: hamish
Type: defect | Status: closed
Priority: major| Milestone:
#7: Location wizard: should predefine DB connection for new location
--+-
Reporter: neteler | Owner: hamish
Type: defect | Status: assigned
Priority: major| Milestone: 6.4.0
#7: Location wizard: should predefine DB connection for new location
--+-
Reporter: neteler | Owner: hamish
Type: defect | Status: assigned
Priority: major| Milestone: 6.4.0
#7: Location wizard: should predefine DB connection for new location
--+-
Reporter: neteler | Owner: hamish
Type: defect | Status: assigned
Priority: major| Milestone: 6.4.0
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
#7: Location wizard: should predefine DB connection for new location
--+-
Reporter: neteler | Owner: hamish
Type: defect | Status: assigned
Priority: major| Milestone: 6.4.0
#7: Location wizard: should predefine DB connection for new location
--+-
Reporter: neteler | Owner: hamish
Type: defect | Status: assigned
Priority: major| Milestone: 6.4.0
On Thu, 13 Mar 2008, GRASS GIS wrote:
for 6.3.0 I have re-enabled automatic VAR creation if it doesn't exist.
more soon.
Attached is a patch (completely untested) that illustrates my idea for
solving the problem. I think there should also be something in
lib/gis/make_mapset.c (used by
#7: Location wizard: should predefine DB connection for new location
--+-
Reporter: neteler | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major|
Sorry, just noticed there was a call to action by me in that bug report
which I missed. Anyway, I think the key issue here is whether or not the
database connection file is considered an essential part of a valid GRASS
location.
1. If it *is*, then creation of it should be added to the places
On Feb 18, 2008, at 4:00 AM, GRASS GIS wrote:
#7: Location wizard: should predefine DB connection for new location
--
+-
Reporter: neteler | Owner: grass-dev@lists.osgeo.org
Type: defect |
13 matches
Mail list logo
