[GRASS-dev] Re: [GRASS-trac] #7: Location wizard: should predefine
DB connection for new location
GRASS-trac
trac at osgeo.org
Tue Jan 1 15:08:32 EST 2008
#7: Location wizard: should predefine DB connection for new location
----------------------+-----------------------------------------------------
Reporter: neteler | Owner: grass-dev at lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone: 6.3.0
Component: default | Version: svn-trunk
Resolution: | Keywords:
----------------------+-----------------------------------------------------
Comment (by cmbarton):
Replying to [comment:5 neteler]:
> I disagree and think that new locations should be valid locations - or -
*all* modules should be able to work with locations lacking the VAR file.
I see no point in having this trivial thing lacking and then make the user
stumble about several commands not functioning.
>
> The "file system noise" is in average 70 bytes (!) per MAPSET which can
be just ignored as a problem.
>
> If we have a default DBMI driver (which is yet DBF), we also have to set
default settings. No complaints in 6.2 probably because use cases are
different.
>
> Scripts like v.db.add* cannot run that automatically because we don't
want to hardcode DBF (or whatever driver) many times scattered all over
the source code but only in a single place (which was the init script and
I still complain that this was removed leading to broken DBMI settings -
see the archive for this).
>
> Markus
I agree with Markus. All locations should be equal. This extra file is
irrelevant to those working only with raster, essentially invisible, and
takes up no space. The alternative is fine also (i.e., the lack of VAR
causes no problem with any module; it is simply created when needed). But
we should not be creating locations that have hidden gotchas.
Michael
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/7#comment:6>
GRASS-trac <http://grass.osgeo.org>
Commonly referred to as GRASS, this is a Geographic Information System (GIS) used for geospatial data management and analysis, image processing, graphics/maps production, spatial modeling, and visualization. GRASS is currently used in academic and commercial settings around the world, as well as by many governmental agencies and environmental consulting companies.
More information about the grass-dev
mailing list